XI IDoc ASC X12 mapping

Hi
I would like to know more abt your IDoc and X12 implementation. I am in the beginning stage of IDoc - X12 implementation using XI. We don't have the adapter yet. Which adpater is good Seeburger or some thing else. I would like to know deatils abt imlementing in seburger.

Hi ram .
R U looking for EDI or IDOC ...?
See burger is for EDI (the only XI support as of now as per my knoweldge)not for IDOC.
and IDOC adapter is inbulit in XI.
It will be nice if u tell the scenaro looking for.
thanx & regards
Vinod Ahir

Similar Messages

IDOC-X12 Mapping instructions

Hi Experts,
Can anyone please help me in preparing IDOC to X12 Mapping.
Please provide me some study materials, instructions and sample mapping
that would be helpful for preparing mapping sheet.
Thanks in Advance,
Vikram.

Hello,
Check the below Link for ANSI X-12 mapping Guidelines.
https://www.sdn.sap.com/irj/sdn?rid=/webcontent/uuid/40943d04-0b01-0010-fbae-c023e996d1b6
Thanks and Regards,
Venkat Phani Prasad Konduri

Difference in idoc adapter header mapping between SP14 and SP19

Hi All,
i have a very strange problem.......i have 2 XI systems : XI-sandbox and XI-dev.....
XI-sandbox is on XI3.0 SP19 whereas XI-dev is on XI3.0 SP14...........
I have a file->XI->idoc scenario which is same on both XI-sandbox and XI-dev....
in receiver idoc adapter, i am using header mapping for sender service and in the sender service i am using XPATH of a field of control rec of idoc.........
this scenario works fine on XI-sandbox which is on SP19 and the idocs are sent to SAP R/3 sandbox...........but this scenario on XI-dev gives error in SXMB_MONI in XI-dev of Call adapter - "No party conversion found".........
So my question is that is there any difference in idoc adapter header mapping between SP14 and SP19.........
Thanks,
Rajeev Gupta
Message was edited by:
RAJEEV GUPTA

><i>so i cant use apply control rec values from payload.........</i>
rajeev,
I know this has nothing to do with the original problem but please do bear.
If I undertood you posts correct, the Sender Partner Name is set in the Idoc Control record in the field SNDPRN in the mapping using some mapping logic.
Now, this is the partner name with which the idoc is to be posted to thge R3 system.
if yes, then like I have pointed above, using "Take Sender From Payload" in the Receivcer Idoc Adapter is a better option as pointed in the SAP help as well.
As you are already populating the idoc control ecord with SNDPRN just make the SNDPRT as LS and then select "Take Sender from Payload" in the receiver Idoc adapter and the Sender Partner Name will not be taken from SDNPRN just as you want.
This is different from "Apply Control Records From Payload" .
Regards
Bhavesh
PS : you can ignore this reply if the situatios is too late to make this change and thanks for the patience.

Idoc - to - JDBC mapping..

Can any one help me on step-by-step Idoc to JDBC mapping ..

Check this link for jdbc receiver adapter. and follow the instructions. If you need more assistance let us know with your requirement
For configuring JDBC adapter
http://help.sap.com/saphelp_nw04/helpdata/en/64/ce4e886334ec4ea7c2712e11cc567c/content.htm
For creating jdbc structure on the inbound side
http://help.sap.com/saphelp_nw04/helpdata/en/2e/96fd3f2d14e869e10000000a155106/content.htm

Retreive IDOC number and map it to a field in Target XML

Hi Experts,
IDOC to file scenario
I have a requirement where I have to retreive the number of the IDOC generated and map it to a field ID in the target XML.
Do i have to use a UDF for this? can ne one pls explain?
Regards,
Teja

Hi Ravi,
You dont need use a UDF for this.
this is a very simple requiremen.
You can get the IDOC number from source IDOc
under EDI_DC40 node field name DOCNUM.
This DOCNUM fielsd will contain the IDOC number
Map this DOCNUM field from source IDOC to target XML structure.

UN/EDIFACT and ASC X12 Templates in Java CAPS 5.1.3

Hi,
I wonder whether we have the OTDs for UN/EDIFACT and ASC X12 messages in Java CAPS 5.1.3;It is not found in sun documentation after CAPS 5.1.0;Those were available earlier in ICAN too.
If we don't have these in 5.1.3 it is very difficult for migration from earlier versions as well as for new development in EDI.
Please let me know if any one of you are using the above OTDs / templates in 5.1.3 or if you have any idea how to process them in CAPS.
Thanks in Advanace
Nag

They are now part of the B2B suite documented here: http://docs.sun.com/app/docs/coll/1650.2.
However the libraries are essentially the same, therefore the upgrade should be easy.
Note that B2B2 Suite 5.1.1 runs on Java CAPS 5.1.3.
Please contact SUN Support: if you have the libraries for a previous release of ICAN of Java CAPS, the upgrade should be part of your contract.
Edited by: eric.lerognon on May 11, 2008 11:08 PM

Idoc with XSLT Mapping ALE service error

Hi all,
I have the same problem with "converting to an ALE logical system".
In this case I have a Business System without logical system name in the SLD. This information for the IDoc control record, like SNDPOR, I will map with a xslt mapping.
In weblogs from Michael are the properties for the directory described.
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
I selected in the comminication channel the last two check boxes, as described in SAP help.
"Take Sender from Payload
If you want to take the sender of the message from the payload and not from the configuration information in the Integration Directory, set this indicator.
If you do not set the indicator, the information is taken from the configuration in the Integration Directory.
Take Receiver from Payload
If you want to take the receiver of the message from the payload and not from the configuration information in the Integration Directory, set this indicator.
If you do not set the indicator, the information is taken from the configuration in the Integration Directory.
If you set both of the above indicators, you do not require a heading mapping and do not need to set the alternative identifiers.
However, you must ensure that the SNDPRN, SNDPRT, RCVPRN, and RCVPRT fields are set in the IDoc control record.
Setting the senders and receivers of a message from the payload simplifies configuration and speeds up processing.
If the sender and receiver are not set correctly in the payload, the resulting error is only visible in the receiving system. "
In my XSLT-Mapping I set the appropriate Idoc fields:
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:output method="xml"/>
<xsl:preserve-space elements="*"/>
<xsl:template match="DATEN">
<_-XXX_-018_XXXXX_XIDATEN>
<IDOC>
<xsl:attribute name="BEGIN">1</xsl:attribute>
<EDI_DC40>
<xsl:attribute name="SEGMENT">1</xsl:attribute>
<TABNAM>EDI_DC40</TABNAM>
<DOCREL></DOCREL>
<DIRECT>2</DIRECT>
<IDOCTYP>_-XXX_-018_XXXXX_XIDATEN</IDOCTYP>
<MESTYP>_-XXX_-018_XXXXX_XIDATEN</MESTYP>
<SNDPOR></SNDPOR>
<SNDPRN>XXXXX01IN</SNDPRN>
<SNDPRT>LS</SNDPRT>
<RCVPOR>xxx</RCVPOR>
<RCVPRN>xxx</RCVPRN>
<RCVPRT>LS</RCVPRT>
</EDI_DC40>
<xsl:variable name="pid" select="substring(.,1,1)"/>
But in the sxmb_moni the message is red with the error message :" converting to an ALE logical system"
Have you any idea?
With another interface I used a graphic Mapping and the same properties in the directory and it works.
Bye
Stefan

Hi togehter,
it works now, after cpa_cache and sxi_cache.
and and ...
<IDOCTYP>/XXX/018_XXXXX_XIDATEN</IDOCTYP>
<MESTYP>/XXX/018_XXXXX_XIDATEN</MESTYP>
Without: _-...
I would write a blog.
Does know one how that goes here?
Thanks
SDN is great
Stefan

JDBC to IDoc ( error when mapping multiple JDBC records to IDoc)

Hi,
I am working on JDBC to IDoc scenario, I have declared row as 0 to unbounded and by default the IDoc structure is 1..1.
Inorder to map multiple rows from JDBC to get multiple IDoc's, I have changed the occurrence of IDoc in "Messages" tab of Message mapping to 0 to unbounded.
I have mapped "row" to "IDoc".
When I test the mapping, it works fine, giving the same number of IDoc's with that of row.
When I test end to end, in SXMB_MONI, it gives me following error:
<SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_RUNTIME</SAP:Code>
<SAP:P1>MSGGUID 54A3A64E895D48EC3F20C69FEFE2E82B: Tag found instead of tag IDOC BEGIN=</SAP:P1>
can any one help me out with this.
Thanks in advance.

Hi Jwalith,
Check this blog from Michel
The specified item was not found.
Make sure that you changed occurance as per this blog.
hope this is helpful
regards,
Venkat.

Problem in idoc to file mapping

Hi Experts,
I am doing a idoc to file scenario...
There is a single idoc with multiple header and line items .
I am using multi mapping for header and lineitems.
The problem i am facing is regarding the occurences in target strucure...
at which level they should be specified so all the headers come in one strucure and line items in another...or should the occurences be o to unbounded at each field level.
Kindly help me regarding the same ...

hi
i have the same scenario : IDOC (orders) to Flat File. can you plz help in mapping. the input format to XI is in the given way
idoc
    a1---(0-1)
    a2---(0-1)
       b1--
    a3---(0-1)
       b1---(0-n)
         c1---
       b2---
         c1---
    a3---(0-n)
       b1---
       b2---
    a3---
      b1---
      b2---
    a3
      b1---
      b2---
i have created the same output DT in the same format (parent-child) for flat file. and my questions are
1. is that correct, do i need to create the same DT as the above idoc (like parent and child) or different?
2. how to map the idoc fields to my file DT..do i need to map parent to parent and child to child...or different.
plz help me out
Thanks
ram

Add new nodes to IDoc in IDoc-XML Schema Mapping with Java

Hello everyone, I'm not very sure if this is the right forum but I have a problem and I haven't being able to find the answer, my scenario is as follows:
-First of all our system characteristics: SAP ECC 6.0, SAP BASIS 700, PI BASIS 2005-1-700 and SAP APPL 600
-We are in Mexico and we are creating our own billing documents with digital signature and a digital certificate in XML format according to SAP Note 1303712 and all derived notes.
-Our actual schema is working fine: We generate our IDocs (one for SD and one for FI) in SAP and we send them to PI XI to be parsed by a JAVA program and then converted to XML.
Now we have the requirement to add new nodes (I might be wrong in the term, feel free to correct me) to the IDoc, it sounds very simple but I have only experience with ABAP and no experience with PI, also it's working only on our production landscape, so if I don't do it right it could be very dangerous.
I have already read the following notes that might help me: 1321680 and 1318342 but their configuration is just in the aplication server and don't mention anything about PI or the Java program.
So, if any one could provide me some kind of guide or important aspects that I should take care (like mapping, structures, etc) to enhance IDocs for this schema i would be very grateful.
I hope this post were clear enough, if it is not also feel free to ask me to clarify or provide more information.
Kind Regards
Omar

Hi Omar,
Since the structure of the IDoc is changing (adding a new node), you would need to do the following in PI:
1) Reimport the IDoc in ESR/IR of PI.
2) Change the mapping/transformation logic in the mapping parser defined. If it is a Java code, you would need to reimport it in the ESR/IR. Use link below to understand more on jave mapping.
http://wiki.sdn.sap.com/wiki/display/XI/BeginnersguidetoJavamappingusingDOMparserinSAPXI
3) Delete the IDoc cache using transaction IDX2, after the IDoc is reimported.
Regards,
Sanjeev.

Creating multiple idocs in ABAP mapping

Hi,
my scenario is source message (JDBC) to target message (idoc).
There can be multiple idocs (unbounded).
I am using ABAP mapping to create the Idoc XML structure. For this i use function module IDX_IDOC_TO_XML.
The idoc is getting created but the problem occurs in case of generating multiple idoc instances.
I changed the idoc occurence to unbounded & used the new idoc external definition in the interface mapping.
I also call the IDX_IDOC_TO_XML & create the output stream factory in a loop (per idoc ).
However only 1 idoc gets generated every time.
Can someone suggest how to create the multiple idocs.
Regards
Prasenjit

Hi Prasenjit,
In order to generate multiple idoc first of all you need to change the target structure with multiple occurence...that you have already done...
Now while generating XML in abap mapping you have to make sure you have element idoc(with its content) repeating for your "N" number of idocs...
can you please copy paste your final xml generated...
Nilesh

Message split - XML to IDOCs - (1:n) mapping

I have to split an incoming XML(in idoc DEBMDM format) from MDM to 2 Idocs (ADRMAS & DEBMAS).
Target message set to occurences "0:unb".
Have tested my graphical-mapping in IR and its working fine. Tested the configuration and got error in IB.
In SXMB_MONI i find the error message,
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="OUTBINDING">CO_TXT_MMF_ENGINETYPE</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="" />
<SAP:Stack>Messages in multi-message format can only be sent to one Adapter Engine</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Read in few threads about creating a "custom adapter module"...is this right? if so.... how to proceed ?
Appreciate any help.

Ram,
Message Split using Graphical Mapping that ur using now supports adapter which are on same J2EE engine .
In ur case Ur trying to post IDOCS ( I suppose ) which is not
supported in using Graphical mapping.
U need to change the design.
-- Kavitha

IDOC Serialization(EOIO) using IDOC Adapter throwing Mapping error

Hello SDN Gurus,
The scenario I am working on is IDOC(PAYEXT & EUPEXR) --> XI (ABAP Mapping) --> Flat File (IDOC Structure).
The IDOCS produced in Appl system may be in the following order
PAYEXT
PAYEXT
EUPEXR
PAYEXT
PAYEXT
PAYEXT
EUPEXR
I need them to be processed in the same order into flat file.
The scenario is working good except for the serialization. So I did the following
Created two entries in IDXQUEUE one for each message type with the same Queue name in XI system.
Created a new rule for the queue and an associated function module. Used this rule in partner profile for both the message types. I used the following link to create the above two steps.
/people/community.user/blog/2006/11/04/how-to-serialize-idoc-xml-messages-fed-into-xi
The SAP system in based on WAS 6.4.
I can see the queue name & EOIO in the inbound message header.
I am getting a mapping error in ABAP program. If I inactivate the queue(in Appl system SAP ECC), I don't get any error.
Does anybody had this problem earlier? Please advice.
Thanks
Srini Vaidyam

I found an OSS note to resolve my issue. The note number is 1057573.
Whenever the queue is activated, the sender system will not send the <TABNAM> field value in EDI_DC40 structure. This note addresses this problem.
I found out this by comparing the results from SXI_MAPPING_TEST individually for the message that failed after queue is activated and the message that was successful if the queue is inactivated.
Only thing I noticed now is even if you selected the radio button "Trasfer Immediately" in Partner profile of Appl. system, the messages are not sent. They are getting collected. So we need to manually push them out using WE14.
This forum Rocks.
Thanks.
Srini Vaidyam

Idoc to file mapping

hi
i have a scenario : IDOC (orders) to Flat File. can you guys plz help in mapping.
the input format to XI is in the given way
idoc
a1---(0-1)
a2---(0-1)
b1--
a3---(0-1)
b1---(0-n)
c1---
b2---
c1---
a3---(0-n)
b1---
b2---
a3---
b1---
b2---
a3
b1---
b2---
i have created the same output DT in the same format (parent-child) for flat file. and my questions are
1. is that correct, do i need to create the same MT as the above idoc (like parent and child) or different?
2. how to map the idoc fields to my file MT segnments.do i need to map parent to parent and child to child...or different way
plz help me out
Thanks
ram

the give below is more clear form
idoc
a1---(0-1)
a2---(0-1)
b1--
a3---(0-1)
b1---(0-n)
c1---
b2---
c1---
a3---(0-n)
b1---
b2---
a3---
b1---
b2---
a3
b1---
b2---
Thanks
ram

IDoc to RFC Mapping.

Hi Everyone,
I have a problem with mapping. My Scneario is Idoc to RFC.
Eg. Sender: GSVERF03
   ->IDOC
E1EDP01 (Occ. 0 to n)
        ...Field_A
        ...Field_B
        ...E1EDP02 (Occ 0 to 25)
......          Field_C
......          Field_D
......          Field_E
Receiver: ZRFC
->T_DELVRY
... ->item
........      Field_1
........      Field_2
........      Field_3
Conditions:
If Field_A = 001, then Field_B = Field_3.
If Field_A = 001,
    then
    If Field_C = 001, then Field_D = Field_1.
    If Field_C = 001, then Field_E = Field_2.
As per my business requirement, i wont get more than one E1EDP02 segment.
How to do this mapping using Graphical mapping.
Rgds,
¬Nav

Field_3
+If Field_A = 001, then Field_B = Field_3
>
This can be achieved by IfWithoutElse
Check your condition using If and give Field_B as second parameter
Field_1
If Field_A = 001,
then
If Field_C = 001, then Field_D = Field_1.
If Field_C = 001, then Field_E = Field_2.
>
here check Field_A condition , 2nd input of this IfWithoutElse check for conditions on FIeld_C
Similar would be for Field_2
You will have to check with context. try by setting context of Field_C,Field_D,Field_E to
E1EDP01

XI IDoc ASC X12 mapping

Similar Messages

Maybe you are looking for