topic Re: Inbound IDOC Format (Flat File) in Application Development and Automation Discussions

Inbound IDOC Format (Flat File)

Former Member — Tue, 29 Jul 2008 14:31:45 GMT

Hi,

I'm using SAP CRM Middleware for communication between CRM and Legacy System.

I have configured Outbound IDOCs and I see something like this:

EDI_DC40 2200000000000000023700 3012 CRMXIF_PARTNER_SAVE_M01 CRMXIF_PARTNER_SAVE_M

E201CRMXIF_PARTNER_COMPLEX000 220000000000000002300000100000001CRMXIF_PARTNER_COMPLEX

E201CRMXIF_PARTNER_HEADER000 220000000000000002300000200000102CRMXIF_PARTNER_HEADER BusinessPartner U

E201CRMXIF_PARTNER_KEYS000 220000000000000002300000300000203CRMXIF_PARTNER_KEYS 0000000014488DDB8AD891249EE10080010A6CA883

The questions are:

I need to know how do the following information must be filled in an Inbound IDOC:

The first characters I understand that corresponds to the Structure name, IDOC Number, IDOC Line...

So I need how do fields like IDOC number must be filled in an Inbound IDOC

Thanx in advance..

BTW. I'm expecting IDOCs as flat files so I need to explain to the Legacy Technician how to fill this fields.

Re: Inbound IDOC Format (Flat File)

Former Member — Tue, 29 Jul 2008 14:44:25 GMT

Can you be more specific?

Refer area menu WEDI where you will find all Idoc defining transactions (like WE64) which will tell you how the control and data parts of IDOC are defined. This should give you a clue of how to map the fields to create an inbound Idoc.

You need to maintain an inbound partner profile in WE21 with parameters according to those given in the control record and can test with WE19

Re: Inbound IDOC Format (Flat File)

Former Member — Tue, 29 Jul 2008 14:46:31 GMT

hi go to we19 and check the segment and data there for the input file..

Re: Inbound IDOC Format (Flat File)

Former Member — Tue, 29 Jul 2008 14:51:46 GMT

For Example.

I need to create a Bussiness Partner through an IDOC (flat file) that a Legacy system is going to generate.

The Legacy technician is going to create an IDOC (flat file) that is going to be left in a specific path.

I need to know how do the fields concerning to IDOC number and header must be filled by the Legacy Technician in the IDOC so this way SAP can recognize it and upload it without problems.

I ask this because with an Inbound IDOC it doesn't have an IDOC number...

What about the other fields?

Re: Inbound IDOC Format (Flat File)

Former Member — Tue, 29 Jul 2008 14:54:41 GMT

first you have to know that what type of idoc is you are using and get the segment names in the tcode we31 and get the documentation in the tcode we60....then fill the idoc

Re: Inbound IDOC Format (Flat File)

Former Member — Tue, 29 Jul 2008 15:00:20 GMT

Hi,

Go to transaction WE30 and give the IDoc basictype name CRMXIF_PARTNER_REL_SAVE_M01 and press the view-button (or press F7 key).

This information you will need.

The records are builded using the following structure:

1st record contains control record information and follows the structure of table EDIDC.

Starting at where "220" is given (this is the CLIENT), it is followed by the IDoc number field DOCNUM (16 digits) and so on. Not all fields must be filled, only those that are used for inbound messaging. Keep here in mind: Less fields filled will probably work better (because SAP will add its own details on arrival of the IDoc).

All following records follow the structure of table EDID4 upto the field: HLEVEL (Hierarchy level, identical to the level found in WE30).

Thereafter it is followed by the name of the segment (including spaces) and after this it will follow the exact structure of the segment.

To view a sample, just generate a dummy (test) IDoc and use transaction WE19 to fill in the fields after changing to the correct IDoc type.

Hope this helps you out.

Regards,

Rob.