topic Re: Inbound Idoc in Application Development and Automation Discussions

Inbound Idoc

former_member557020 — Thu, 27 Dec 2007 07:57:11 GMT

Hi Experts,

I am using the standard program to upload the Idoc file coming from other system.

My doubt is whether how this program will trigger the posting program?

Please provide the configuration to be needed for inbound idoc

Thanks,

Samba

Re: Inbound Idoc

former_member557020 — Thu, 27 Dec 2007 07:58:25 GMT

I am using the standard program RSEINB00

Re: Inbound Idoc

Former Member — Thu, 03 Jan 2008 11:32:47 GMT

hello Samba,

just visit the link given below u will understand the whole procedure which is required to be done for Idoc inbound processing.

https://www.saptechnical.com/

just go to LSMW tab in that refer LSMW using BAPI.

do reward points well

regards,

Brajvir

Re: Inbound Idoc

Former Member — Thu, 03 Jan 2008 12:43:31 GMT

Hi,

According to my understanding

The ALE sytem will check various partner profiles and see if the message type for the IDOC is linked to the partner profiles.

2.If there is a linkage the message type is linked to the process code which in turn calls the Inbound function module.

This is the way how an Inbound function module is triggerd for an IDOC.

Hope this helps

Regards

Re: Inbound Idoc

Former Member — Thu, 03 Jan 2008 13:52:33 GMT

hi samba,

Inbound Process in IDocs:

An inbound process used IDoc structure, posting programs, filter objects, conversion rules, a partner profile, service programs, and configuration tables to post an application document from an IDoc.

Posting Program:

Posting programs, which are implemented as function modules, read data from an IDoc and create an application document from it. A posting program exists for each message. Each posting program is assigned a process code. A process code can point to a function module or a work flow. In the standard program process codes always point to a function module.

Ex. The posting program for message type MATMAS is IDOC_INPUT_MATMAS which has a process code MATM.

Workflow:

A workflow represents a sequence of customized steps to be carried out for a process. The workflow management system is used to model the sequence, identify information required to carry out the steps and identify the person responsible for the dialog steps.

Partner Profile;

A partner profile specifies the components used in an inbound process (partner number, message type, and process code), the mode in which IDocs are processed (batch versus immediate), and the person to be notified in case of errors.

Process flow for the Inbound process via a Function Module:

In this process, IDocs are received from another system and passed to the posting function module directly.

1. Processing in the communication Layer:

The IDOC_INBOUND_ASYCHRONOUS program, triggered as a result of an RFC from the sending system, acts as the entry point for all inbound ALE processes. The IDoc to be processed is passed as an input parameter. Control is transferred to the ALE/EDI layer.

2. Processing in the ALE/EDI Interface Layer:

• Basic integrity check: A basic integrity check is performed on the control record.

• Segment Filtering and conversion: Filtering out unwanted segments and carry out any required conversion of field values.

• Creation of Application IDoc: The application IDoc is created and stored in the database and a syntax check is performed. If there are errors it gets status code of 60 (Error during Syntax check of IDoc – Inbound). At this point a tangible IDoc, which can be monitored via one of the monitoring transactions, is created and the IDoc gets status code 50 (IDoc Added).

• IDoc Marked ready for Dispatch: IDoc gets the status code 64 (IDoc ready to be passed to application).

• IDoc is passed to the posting program: The partner profile table is read. If the value of the Processing field is set to Process Immediately, the IDoc is passed to the posting program immediately using the program RBDAPP01.

3. Processing in the Posting Module:

The process code in the partner profile points to a posting module for the specific message in the IDoc. The posting program implemented as a function module either calls a standard SAP transaction by using the Call Transaction command for posting the document or invokes a direct input function module.

The results of execution are passed back via the function module’s output parameters. If the posting is successful IDoc gets the status code 53 (Application Document Posted) or it gets status code 51 (Error: Application Document Not Posted).

Reward if usful,

Thanks,

Srikanth.A

Re: Inbound Idoc

Former Member — Fri, 04 Jan 2008 10:46:21 GMT

Hi,

The RSEINB00 assumes that the first record in your file is the control record.

Then it uses the information in that control record to post the idoc in your SAP System.

The control record has a structure of type EDIDC. If you look at the structure in data dictionary you will find that the control record should have the following information :

Basic type (IDOCTP)

Message Type (MESTYP)

Partner Type of Receiver (RCVPRT)

Partner Number of Receiver (RCVPRN)

Partner Type of Sender (SNDPRT)

Partner Number of Sender (SNDPRN)

These are the main fields which should be available in the control record of the file and these are also the parameters which should be set up in your system, so that the idoc can be posted successfully.

If you are using a standard message type ( example MATMAS ) and standard idoc type attached to it ( example MATMAS03 ) your work becomes easier.

Then you only need to create the partner profiles using WE20, and the program should work.

Thanks,

Urmila