topic Re: Inbound Idoc programing in Application Development and Automation Discussions

Inbound Idoc programing

Former Member — Mon, 25 May 2009 05:03:08 GMT

Hi Gurus,

I will be getting the IDOCS from an external system which is also on SAP.

What I need to do is to get these IDOCS which are called Erroreneous IDOCS.

From the IDOC numbers I am able to see the message types and idoc types and data in the segments.

What all the steps and configurations I need to do for reading an IDOC data from segments and update on of the tables with the received data.

Do I need to write any inbound function module if so how. Please do let me know the steps and even what configurations I need to do?

Please help.

Regards

Mac.

Re: Inbound Idoc programing

Former Member — Mon, 25 May 2009 06:38:49 GMT

You need to do below settings and steps .

Define segments: WE31

Create new basic idoc type: WE30

Create message type: WE81

Link message type to IDOC basis type: WE82

Create RDC destination: SM59

Create logical system: SALE

Create port: WE21 "Declare Port

Create partner profile: WE20 "Add port to Partner profile

Set up distribution model (If necessary): BD64

Regards

kiran

Re: Inbound Idoc programing

Former Member — Mon, 25 May 2009 07:00:44 GMT

if your using the standard IDOC , assign the partner profile: WE20 tcode.

Re: Inbound Idoc programing

Former Member — Mon, 25 May 2009 07:14:56 GMT

Hi Mohan,

External system means , yu can use EDI...

please check the following steps :

Phase : 1

ALE Configuation settings :

Create logical system: SALE

Create RDC destination: SM59

Create port: WE21 "Declare Port

Create partner profile: WE20 "Add port to Partner profile

Set up distribution model (If necessary): BD64

Phase : 2

*Define segments: WE31*

*Create new basic idoc type: WE30*

*Create message type: WE81*

*Link message type to IDOC basis type: WE82*

Note : Sap has provided huge standard idocs and message types , so my suggestion is no need to create new idocs and message types.

Phase : 3

Once you finished first two phases , then generate the program, we have three ways to develop the program. standard alone , messagetype and change pointers.

should be call : master_idoc_distrubute

inbound means : use the tranx codes : bd11 receiveing mat, bd13 receiveing cust,bd15...

once u finish, check we02 and we05....

Reg,

Siva prasad

Re: Inbound Idoc programing

Former Member — Mon, 25 May 2009 07:55:21 GMT

Hi,

Just create inbound partner profile in transaction WE20 for your message type. You can find the message type and idoc type from idoc's control record.

1. If it is standard message type and idoc then find the corresponding process code(function module) from WE64 and assign it in partner profile.

2. If message type is standard and basic type is enhanced(z<basic type>) then find the customer-exit for the processing fumction module and write your logic.

3. If message type is customized message type then write the processing FM and create processing code in WE42. And link that FM to this processing code here.

Thanks,

Asit Purbey.

Re: Inbound Idoc programing

Former Member — Mon, 25 May 2009 11:01:01 GMT

Hi Mac ,

Yeah The inbound idoc is basically get in to sap and processed thr a i/b function module. but if you want only error idocs . It will be stored in thge tables. that u can view thr WE02 txn and you can process it manually using WE19 , sometimes using BD87 txn also .

In WE19 txn , u can see in debug and fix the bug also . there it will show whether any standard Fun.Mod is used .

Thanks,

Arun .