How to create an IDoc programmatically at Inbound side?

[Former Member]

Hi,

How to create an IDoc programmatically at Inbound side?

Assume that you have a file(material master details) which is enough to create master data.

Regards,

Thiyagu

[Former Member]

Hi,

How to create an IDoc programmatically at Inbound side?

Assume that you have a file(material master details) which is enough to create master data.

Regards,

Thiyagu

[Former Member]

IDOC_INBOUND_SINGLE function module can be used to generate inbound idoc in your program .

Regards,

Deepthi

[Former Member]

Hello Deepathi,

Great.Any idea on when should we go this 'IDOC_INBOUND_ASYNCHRONOUS' function module at inbound side.

Just clarify.

Regards,

Thiyagu

[Sm1tje]

Read the documentation of this FM first:

FU IDOC_INBOUND_ASYNCHRONOUS                                                                                
____________________________________________________                                                                                
K. tekst
                                                                                IDoc inbound processing via tRFC                                                                                
Functionality
                                                                                This function module starts inbound processing in the case of port type     
    "tRFC". The function module is a successor to INBOUND_IDOC_PROCESS,         
    which processes IDocs in the Release 4.0 record types. If you are           
    processing IDocs in Release 3.X record types, the function module           
    INBOUND_IDOC_PROCESS must still be called.                                                                                
The function module checks the ID 'EDI_MES' in authorization object         
    B_ALE_RECV against the received message type.                                                                                
The IDocs are saved by the function module IDOC_INBOUND_WRITE_TO_DB (a      
    COMMIT for all IDocs) and then transferred directly to the application      
    by the dispatcher module IDOC_START_INBOUND.                                                                                
Parameter
                                                                                IDOC_CONTROL_REC_40                                                         
    IDOC_DATA_REC_40                                                                                
Exceptions
                                                                                Functiegroep                                                                                

Edited by: Micky Oestreich on Jun 11, 2009 12:52 PM

[Former Member]

Hi ,

IDOC_INBOUND_SINGLE is the successor to IDOC_INBOUND_ASYNCHRONOUS.

Check the documentation :

FU IDOC_INBOUND_SINGLE

____________________________________________________

Short text

Inbound processing for transferred IDoc

Functionality

The function module is a successor to IDOC_INBOUND_SYNCHRONOUS. The interface has been adapted to the new 4.0 record types (control record EDI_DC40, data record EDI_DD40) for IDocs. The function module returns the number of the generated IDoc. If the IDoc does not have a status which can be automatically processed further, the export parameter PE_ERROR_PRIOR_TO_APPLICATION is set to 'X'.

Significance of the parameter PI_DO_COMMIT

The parameter PI_DO_COMMIT controls whether the function module sends a "COMMIT WORK" command. Please note that a COMMIT command which is sent during posting leads to a termination.

If no COMMIT command is sent and the application carries out rollback if an error occurs, the IDoc is deleted from the database, i.e. there is no longer an IDoc in which the error could be documented. The user sees the following error message:

IDOC: Error EA613 with FM IDOC_INBOUND_SINGLE

Regards,

Deepthi