Inbound IDOC Format (Flat File)

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.

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.

Similar Messages

Inbound idocs with flat file

Hi
Iam creating INBOUND IDOCS from flat file ...so my sending and recieving systems are same...
In WE20 i have setup the logical system and assigned inbound parameters with message type and proces code.
Iam using IDOC_INBOUND_ASYNCHRONOUS to create the inbound IDOCS but iam getting the error
EDI: Partner profile inbound not available
It looks like iam missing some settings here..
Please let me know what checks i need to make sure to get rid of this error and post the idoc.
Thanks
Govi

Hello,
You need to create partner profile in WE20 transaction code.
For more details follow the link: [creating PARTNER PROFILE|http://help.sap.com/saphelp_nw04/helpdata/en/2d/f371e4d24a11d289810000e8216438/frameset.htm].
Hope this resolves your issue!
Thanks,
Augustin.

How to create a inbound IDOC from flat file in Application server

HI All
Our requirement is to create the Inbound idocs from a flat file from application server with in R/3
Could any body please let me know the steps required for this.
Thanks
Malli

1. Read the file using OPEN DATASET and read and fill up the segment info and fill the EDIDC header data
and then call function
CALL FUNCTION 'INBOUND_IDOC_PROCESS'
    TABLES
      IDOC_CONTROL       = i_edidc
      IDOC_DATA          = i_edid4.
a®

PO Idoc in Flat File format

Hi all,
I am able to generate the PO Idoc in Flat file format using standrad FM IDOC_OUTPUT_ORDERS. but the Flat file appearing is not in a appropriate format.
I'm looking to generate the Flat file in such a way that there will be only one line for each Idoc Segment.( with Line termination).
How to Achieve this.
Regards,
S Anand

Resolved.
we can use CG3Y transaction.
Regards,
S Anand

IDOC to Flat File and XML ( Need both the Output)

Hi ,
My Scenario is IDOC to File .
I need o/p in 2 format . ie, 1) Flat File 2 ) XML file
I have a plan to go with Interface determination , 2 IM and what shd be the condition ?
or Else 2 Receiver detmination but condition ?
How to slove this ?
Need the Output from Idoc in 2 format ( Flat file and XML file )
Any Blog , Thread ...Tips...etc
Regards,
Jude

Hi Jude,
Do like this:
1. Create two inbound Service Interface (with the same target Message Type)
2. Create separate Operation mapping with the above service interfaces as target (with the same source service interface)
3. Create Interface Determination and include these two operation mapping (without any condition)
4. Create 2 receiver agreement (with two separate communication channel) for each of the target service Inetrface. In one channel use content conversion and the other one will give you normal XML output
Regards
Suraj

How to convert IDOC to flat file in XI

Hello SDNers
I have a scenario IDOC --> XI --> Flat file. My question is how to conver IDOC to flat file. At least there are two ways to do that:
1) Define a flat structure in PI that reflects the IDOC structure, then using content conversion to convert the flat structure to flat file in hte receiver communication channel.
2) There is a [document |https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a] talking about using a generic ABAP mapping to map any IDOC to flat file.
For the option 1, I don't want that way, because I would need to define a flat structure in PI for each IDOC which is too much effort. (I would have dozens of IDOC scenarios)
The second one is very attractive. However the document is not complete to follow. Basically it does not explain how the inbound flat structure looks like. I guess the generic ABAP mapping is used to map any IDOC_XML structure to a flat structure, then in the file receiver communication channel to convert the flat structure to flat file format. But the document does not mention how the flat structure looks like. Has somebody tried this scenario? If yes, can you please let me know the steps to do in ESR (IR) and ID? Basically what structure the IDOC_XML should be mapped to using the generic ABAP mapping class?
Or somebody has other ideas on how to convert IDOC to flat file?
Thank you so much
Eric

> 1) You are saying that for Java mapping and abap mapping, the target data type (messag type) is just a dummy one, the real (XML) message the receiver will recieve is the one (stream) produced by the java or abap mapping. Is that correct?
Definitely yes!
>
> 2) For the abap mapping option, I would define a dummy target data type. Do I need to do any content conversion in the receiver adapter (communication channel)?
None wat so ever.The output of your Java Mapping will be the Native Idoc Format.
>
> 3) I tried with a dummy target data type as mentioned in my second post, can you see any clue in the error message what is wrong?
Dats one thing I cant help much. Just make sure that the ABAP report is valid and take the help of a ABAP'er to debug what is going wrong. Not much of a ABAP guy, can read ABAP code, but cant write one myself
Try to test the program standalone to see how it works. Maybe take some Idoc XML file as input and then dump the output to a .txt file and so on.
Regards
Bhavesh
PS : All this is from what I have read of this guide. I have not convert Idoc XML to Native Idoc but have used this guide to convert Native Idoc to Idoc XML .

IDoc to Flat File in SAP PI 7.11

Hi Experts,
I am working on PI 7.11 and I have scenario from Idoc to Flat File.
Idoc is posted from source side R/3 system.My requirement is "With out Converting the Idoc structure to XML Structure i want to send the data to Target system i.e. File system.
But the structure of the target structure is different from source structure.
My questions are:
1). Is it Possible to send the data to Target system without converting Idoc structure in to xml format through our PI 7.11 ?
2). If possible please provide me the way that executes in the Interface is?
Could you please provide the Inputs.
Best regards,
satya.T
Edited by: satyatanuku on May 24, 2010 3:26 PM
<Moved from Trial, Preview~ forum>
Edited by: Prateek Raj Srivastava on May 25, 2010 1:02 PM

Hello Folks ,
I am also facing the same scenario please provide me any options to achieve this scenario .
I am searched in Forums of SDN but no inputs or blogs available.
Let me know i am having one solution is it right or wrong ?
we have to achieve this IDOC Tunneling .... is it right friends ?
Still inputs required....
Regards,
Ravi.

Doubts in SAP(Idoc)-XI-Flat file scenario

Dear All,
I am sending Delivery Idoc from R/3 and I am able to view the Idoc in XI in transaction IDX5. Also i m able to see the XML structure with the data of the idoc in SXMB_MONI.
Now as per my scenario I have to download this to a flat file from XI.
My question is, should I have to do the creation of Data types, message types, mapping interface & interface mapping in IR or should I directly do the designing in the ID.
waiting for your reply.
Warm regards,
N.Jain

Hi,
DT, MT, MI : you will create these things for receiver flat file only.
First create
In Integration Repository :
1.     Import structure of IDOC in your scenario, In imported objects  IDOCs
              a.     In Interface Objects
1.     Create Data type for your flat file
2.     Create Message Type
3.     Create Message Interface (inbound Asy.)
              b.     In Mapping Objects
1.     Message Mapping : IDOC to Message Type of Flat File.
2.     Create Interface Mapping : IDOC to Flat file by using Message Mapping which you have created.
Make activate all these things.
In Integration Directory :
1.     Create Communication channel for File Receiver.
2.     Sender Communication channel is not required.
3.     Create Receiver Agreement.
4.     Sender Agreement is not required.
5.     Interface Determination
6.     Receiver Determination
At sender side you will take your IDoc and at receiver side you will take your flat file.
It can help you,
Regards,
Sandeep Kaushik

IDOC to flat File----Problem in File Content Conversion at receiver

hi experts,
I am doing a IDOC to flat file secnario.
My requirment is IDOCXI-Flat file
Format of flat file is like:--
Every segment in the IDOC will be converted into a single line of file(without any delimiter). So number of lines in flat file will be equal to number of segments in IDOC.
I am facing problem in File Content conversion.
Please help me out..
Thanks
Jaideep

Check this doc...
[How To...Convert an IDoc-XML structure to a flat file and vice versa in XI 3.0 |https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/46759682-0401-0010-1791-bd1972bc0b8a]

Idoc to flat file using Integration process does not show up at all

Hello All,
I created a scenario IDOC to Flat File using Integration Process and one without IntegrationProcess. I am able to execute the one without Integration Process easily.
However when I send the IDOC from SAP then the Integration Process scenario just does not work.
I Checked SXMB_MONI There is no entry for the Integration Process.I can see entry for other without Integration Process.
SXI_CACHE : I can see my Integration Process active
SWEQADM : I have activated the Event Queue and Background job
SWF_XI_ADM_BPE : ALL BPE is showing green status.
All syntax check on IP are fine.
There is no Basis Help for me so there could be some additional basis steps which need to be configured. Has anyone faced such an issue with Integration Process?
Regards
Prashanta

Hope this might help you. when u configure an IDoc as Sender with BPM this is how you proceed.
1. let us split the scenario into two.
a. Sender to BPM ( Integration Process).
b. BPM to Receiver.
2. First let us configure the first Sender to BPM.
a. Sender Agreement( Not required ).
b. Receiver Agreement( NOT Required).
c. Receiver Determination( Sender Service, Outbound Interface, Receiver Service(Integration Process).
d. Interface Determination( Inbound Interface(Sender Abstract Interface), Message Mapping(NOT Required if your using transformation stepin Integration Process)).
3. Now let us configure the Second BPM to Receiver.
a. Sender Agreement( NOT Required)
b. Receiver Agreement( Sender Service(Integration process), Receiver Abstarct Interface,Receiver service, Inbound Interface).
c. Receiver Determination( Sender Service(Integration Process), Receiver Abstarct Interface,Receiver Service).
d. Interface Determination( Inbound Interface, Message Mapping(NOT Required)).
So Finally we have One Receiver Agreement, Two Receiver Determinations, Two Interface Determinations.
Please let me know if you have any more queries.
Regards
Gopi

IDoc to Flat file scenario - abap mapping

Hi All,
I have to do some IDOC to Flat file scenarios. In Order to generate the file in required format I will have to add all segments(Nodes) of Idoc in FCC receiver. We also have other option of doing it through ABAP Mapping which I found in one blog.
Now my question is : Is it better way of doing it through FCC or ABAP Mapping?
Ofcourse from development point of view ABAP Mapping looks easier as FCC is very time consuming task.
Is there and performance issues in either of the approach?
Thanks and Regards,
Atul

Hi VJ and Harald,
Thanks for your replies.
I am not having PI7.1 however the given blog was very informative.
I will try using file port approach as suggested.
Thanks and Regards,
Atul

Data Extraction or IDOC to flat file

hi,
I have a project to create a flat file from SAP, for an external legacy system. There are 3 requirement.
What approach should I take. Simple data extraction OR Idoc to flat file.
There are 4 requirements:
1. first time extract all data.
2. on subsequent run, extract only changed & new records
3. if in SAP table, a record is deleted, then marked deleted in flat file.
What approach should I take if I use data extraction.
Thanks.

I read your question, my first thought would be to look at where the data is going?
What are the data requirements of the legacy system. IDOCs can speed up the development related to pushing the data out from SAP. Using ALE and change pointers you can automatically pass out the delta with a limited amount of development.
However, the receiving system then needs to parse the IDOC data. depending on the IDOC you are working with this can be a challenge especially if the legacy developer doesn't get IDOCs.
Sometimes its easier to collect and write the data from SAP using "simple data extraction". The data is more readily organized into a format the receiving system is expecting.
You can also pass the idoc to a middleware maping application if one is available and do the SAP to legacy mapping there.
Cheers

Multiple idoc to flat file

Hi,
i have a scenario from idoc to flat file.There is two idoc that send message in same file.Without flat file content messages come succesfully.the format should be following:
at the first row should be the first idoc,
at the second row should be the second idoc
01 1FONEX0045               FONEX0045               FONEX SIVI SABUN 400+850ML FLOWERS                    =>1.idoc
02 1FONEX0045               8691988000162           8691988000162                                                             =>2.idoc
01 1DOVE0199                DOVE0199                   DOVE SAC DOKULMELERINE COZUM SAC BAKIM M     =>1.idoc
02 1DOVE0199                8718114638348           8718114638348                                                               =>2.idoc
Thanks in Advance
Nurhan

Hi,
You have to MessageTransformBean Module.
The MessageTransformBean module enables conversion of XML files to flat files and vice versa. You can use this module in the sender and receiver communication channels.
In receiver communication channel, specify MessageTransformBean module before standard adapter module CallSapAdapter and use
Module Name: localejbs/AF_Modules/MessageTransformBean
Module Key : XML2Plain
Please see the below links, it might be useful to you.
/people/gabrielsagayaselvam.panneerselvam/blog/2009/12/07/standard-adapter-framework-modules-afmodules-in-pi-71-150part-2
http://help.sap.com/saphelp_nw04/helpdata/en/24/4cad3baabd4737bab64d0201bc0c6c/frameset.htm
Regards,
P.Rajesh

Develop IDOC to FLAT FILE

Hi friends,
I need help do develop a new interface using IDOC -> FLAT FILE scenario.
Please send exemples and links.
In found only XML file formats, i need FLAT FILE.
Thanks,
Marco

new interface using IDOC -> FLAT FILE scenario.
idoc to flat file scenario is very simple but you have to provide FCC Parameters in Receiver File Communication channel based on target structure and remain ecvery thing is same what was you found idoc to xml scenario.
ex for Fcc Parameters in Receiver File Communication channel :
http://www.riyaz.net/sap/xipi-file-content-conversion-for-complex-structures/79/

R/3 46C(IDOC) -- XI -- Flat file scenario

Hi
Is there anyone who could give me information on a R/3 46C(IDOC) --> XI --> Flat file scenario?
Many thanks!
br
Göran

Hi Manish
We are using a standard IDOC called PROACT.PROACT01
(We are using transaction sa38(Report RSMIPROACT) in R/3 to send our IDOC.)
First we create the technical and business systems in SLD
Second we transfer these to the repository.(I think the only thing you need to do is to update the SLD cache to get them there - Design : Integration builder --> Environment --> clear SLD cache)
Then we just use the configuration wizard(Configuration : Integration builder --> Tools --> configuration wizard) to map everything together - defining sender and receiver etc(You get the configuration wizard tool by patching XI to patch level 4 or 5).
I assume that you have made all the configurations accordingly to the XI configuration guide which you can download from the service marketplace.
This is just a hint but maybe it can give you a start.
br
Göran

Inbound IDOC Format (Flat File)

Similar Messages

Maybe you are looking for