Scribd Logo
Upload

Welcome to Scribd!

  • Idoc

    Uploaded by

    Sap Knowledgebank
    13 views5 pages
    The document provides steps for configuring IDoc (Intermediate Document) in SAP systems for data exchange between different systems. It includes steps like creating logical systems, ports, IDoc types, message types, linking them, and assigning function modules. Transactions like WE20, WE21, WE30, WE31, WE57, WE60, WE64 are used for configuration and testing. IDocs act as shells that contain data exchanged via files or tRFC between systems using BAPIs (Business Application Programming Interfaces). The received IDoc data is stored before processing, unlike direct BAPI calls.

    Original Description:

    Copyright

    © © All Rights Reserved

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    Report this Document
    The document provides steps for configuring IDoc (Intermediate Document) in SAP systems for data exchange between different systems. It includes steps like creating logical systems, ports, IDoc types, message types, linking them, and assigning function modules. Transactions like WE20, WE21, WE30, WE31, WE57, WE60, WE64 are used for configuration and testing. IDocs act as shells that contain data exchanged via files or tRFC between systems using BAPIs (Business Application Programming Interfaces). The received IDoc data is stored before processing, unlike direct BAPI calls.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    13 views5 pages

    Idoc

    Uploaded by

    Sap Knowledgebank
    The document provides steps for configuring IDoc (Intermediate Document) in SAP systems for data exchange between different systems. It includes steps like creating logical systems, ports, IDoc types, message types, linking them, and assigning function modules. Transactions like WE20, WE21, WE30, WE31, WE57, WE60, WE64 are used for configuration and testing. IDocs act as shells that contain data exchanged via files or tRFC between systems using BAPIs (Business Application Programming Interfaces). The received IDoc data is stored before processing, unlike direct BAPI calls.

    Copyright:

    © All Rights Reserved
    Download as DOCX, PDF, TXT or read online from Scribd
    Flag for inappropriate content
    Download as docx, pdf, or txt
    of 5

    https://blogs.sap.

    com/2016/07/05/steps-in-idoc-configuration-for-beginners/

    https://sapintegrationhub.com/abap/ale-idoc/how-to-create-configure-custom-idoc-type-in-sap/

    https://www.guru99.com/all-about-idocdefinition-architecture-implementation.html

    SAP to E2NET

    SA – ORDERS05 -- ORDERS ORDERS05

    GR – DELVRY03 -- STPPOD DELVRY03

    BD54 – create/register logical system (source of partner no. in WE20)

    SM59 – check RFC connection to target system

    WE21 – create ports to target destination

    WE30 – display/develop idoc type

    WE31 – create segment editor (extension)

    WE81 – create customer Idoc message type

    WE82 – link idoc type (either extension) to idoc message type

    WE20 – idoc entry for the partner profile either outbound or inbound parameter ( partner no. type,
    port, output control, process code, function module)

    WE41 – double click process code.

    SE37 – to get enhancement package

    WE57 - Assign FM to Message Type/Basic Type combination

    SMOD- to look for enhancement user exit appropriate.

    CMOD – to build project and user exit.

    WE02/05 – display idoc

    WE19 – test idoc

    WE60 - You can obtain complete documentation on any IDoc by using transaction WE60

    WE64 – process code


    -For outbound parameters ,maintain port and IDOC details, because port describes to which system the
    IDOC has to flow.

    Whereas in Inbound IDOC,mention the process code details which determines the inbound function
    module for processing the data.
    Therefore, for data migration projects, we strongly recommend using the Trigger by background
    program setting, which will keep inbound IDocs waiting in Status 64 ready for processing by either
    manual start (Transaction BD87) or background processing by scheduled Report RBDAPP01.
    A BAPI is a function module with predefined call parameters. Most of the BAPIs you will need are
    already delivered by SAP with the BAPI/ALE interface, including an IDoc message type, IDoc basic type,
    and both outbound and inbound function modules. The IDoc acts like a shell for the BAPI, and the data is
    sent via IDoc (either file or tRFC) rather than a direct function call (or RFC). The advantage is that the
    IDoc data is received and stored before it’s processed, unlike in a classical BAPI call.

    https://www.toolbox.com/tech/enterprise-software/question/changing-the-data-in-the-inbound-idoc-
    segments-082710/
    Via WE21 SAPKLD

    You might also like