Inbound: Components to receive and process incoming IDocs

Last edited: 1999-07-18 18:29 +0200

In order to receive and process an incoming IDoc you will need to define a function module for processing, define

1   Partner Profile
 In a partner profile you will specify the names of the partners which are allowed to send IDocs to your system. For each partner you have to list the message types which the partner may send. For each such message type, the profile also contains the name of the IDoc type, which is a reference to the record structure of the IDoc.
Example
 The partner profile reads as follows:
  • Customer ABD_INC
    sends SALESORDERS
    via DISKFILE
    using file format ORDERS01
    using processing code CUSTOMERORDER
  • Supplier MAK_CO
    sends SHIPPING_ADVISE
    via INTERNET
    using file format SHPADV01
    using processing code SHIPMENTLEFT
  • Sales agent LOWSELL
    sends SALESORDERS
    via RFCLINK
    using file format ORDERS01
    using processing code CUSTOMERORDER
  • Sales agent SUPERSELL
    sends SALESORDERS
    via RFCLINK
    using file format ORDERS01
    using processing code AGENTORDER
2   Logical processing code
 The processing code is a logical name for the algorithm used to process the IDoc.The processing code points itself to a method or function, which is capable of processing the IDoc data.
Example
 Processing can point to predefined or self-written business objects or function modules as long as they comply with certain interface standards.
  • Processing code SALESORDER
    will call a business object ZBUS2032 
    which is defined as derivation of standard  BAPI BUS2032
    while passing the IDoc data in the object container
  • Processing code AGENTORDER
    will call a function module Z_VA01_AGENTORDER 
    which executes a  CALL TRANSACTION from the IDoc data
The processing codes allow to easily change the processing algorithm. Because the process code can be used more than one partner profile, the algorithm will be easily changed for every concerned IDoc.
3    Define a method or function to process an IDoc
 The IDoc engine will call a function module or a business object which is expected to perform the application processing for the received IDoc data. The function module must provide exactly the interface parameters which are needed to call it from the IDoc engine.
Example
 A interface parameters of a function module for IDoc input must comply strictly to a well defined standard and should look like the following. 
FUNCTION 
*"----------------------------------------------------------------------
*"*"Lokale Schnittstelle:
*"       IMPORTING
*"             VALUE(INPUT_METHOD) LIKE  BDWFAP_PAR-INPUTMETHD
*"             VALUE(MASS_PROCESSING) LIKE  BDWFAP_PAR-MASS_PROC
*"       EXPORTING
*"             VALUE(WORKFLOW_RESULT) LIKE  BDWFAP_PAR-RESULT
*"             VALUE(APPLICATION_VARIABLE) LIKE  BDWFAP_PAR-APPL_VAR
*"             VALUE(IN_UPDATE_TASK) LIKE  BDWFAP_PAR-UPDATETASK
*"             VALUE(CALL_TRANSACTION_DONE) LIKE  BDWFAP_PAR-CALLTRANS
*"       TABLES
*"              IDOC_CONTRL STRUCTURE  EDIDC
*"              IDOC_DATA STRUCTURE  EDIDD
*"              IDOC_STATUS STRUCTURE  BDIDOCSTAT
*"              RETURN_VARIABLES STRUCTURE  BDWFRETVAR
*"              SERIALIZATION_INFO STRUCTURE  BDI_SER
*"----------------------------------------------------------------------
Example
 A business object for IDoc processing requires an interface like the following BAPI BUS2032 .