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

Similar Messages

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

IDOC EDI mapping ..

hi,
Please let me know if my understanding is correct. In SAP EDI setup two people involved, ABAP programmer who customzes the IDOCS, sets up the EDI setup on SAP side like number ranges, partner profiles, condition records, message control etc and monitors the IDOC status till it is transmitted to the EDI subsystem and also the IDOCs received at SAP end.
The other person is an EDI specialist who will map the IDOCs to the EDI doc set based on trading partner requirements in the EDI subsystem.
So the ABAP deveoper need not know anything about the mapping done at EDI subsystem ?? His job is only at the SAP end ?? Am I right ??
thanks
Edited by: sdnuser1 sdnsurname on Mar 20, 2008 6:03 AM

Hi,
Ur assumptions are correct up to some extent...
What will happen SAP EDI implementation proejcts is most of the times it is the SAP technical people responsibility to do the EDI mapping also.
So an ABAPer with EDI knowledege(ABAP/EDI consultant) will take care of SAP EDI settings at SAP side and he/she will develop the mapping document and hand over the same to EDI sybsystem provider.
EDI subsystem people will feed the mapping instructions into EDI subsystem based on ur mapping document.Core EDI people will not understand the SAP terminology and as ABAP/EDI consultant will take of both settings.For an ABAP/EDI consultant also will not be given full access of EDI subsystem and u will only hand over the mapping docuemnt(IDOC segments to EDI standards mapping ) and they will feed the instructiona and get back 2 u for any doubts..
Hope this help.Let me know if u need any help for further understanding..
Rward if helpfulll
ramesh

Which field from idoc INVOIC01 maps to Item Text field in MIRO transaction?

Hi
Will anybody please tell me which of the field in which segment of IDOC INVOIC01 maps to Item text (INVFO-SGTXT) field in Basic data tab of MIRO transaction

Thanks Ravi for your response.
But I have tried with all fielsd related to texts in IDOC but it is not being filled in transcation .
If you see the F4 help in text field then Text Id is four character and when I manually assign this in transactin then it is putting = symbol in fron of the id. And then if we save or go to other tab then it is filling text.
I am not able to find the error bcoz document is being posted through idoc but text field is not getting filled.

IDOC field mapping

We currently use PEXR2002 IDOC for outbound payments. Is there a place in SAP where I can see what data in SAP is mapped to what fields in IDOC? I am specifically looking for segment E1IDBW1, currently this segment is blank, not sure what data goes into this segment in the standard payment processing without using any user exits.

The is a Structure table called E1IDBW1 (for special instructions). To be found via SE16-> Use the drop down box->Tick Information System->Fill the field Table Name with E1IDBW1. make sure you select the Structures in the additional selection tab. -> execute->stand on the table name->Hit Display.

PI 7.11: IDoc Message mapping

Hi there,
I'm currently working on a graphical message mapping using IDoc HRMD_A06 as source structure (HR master data transferred via PFAL).
In my result structure I have to fill a field CostCenter with the following logic:
If field KOSTL (cost center) is filled in node E1P0315, map this field to CostCenter in result structure, otherwise take KOSTL of node E1P0001.
The end date (ENDDA) has to be '99991231' in each case.
This is how the result structure looks like:
<e> [1...1]
<CostCenter> [1...1]
</e>
This is the simplified source structure:
<E1PLOGI SEGMENT="1">
<E1PITYP SEGMENT="1"> [0...n]
 <E1P0001 SEGMENT="1"> [0...n]
 <INFTY>0001</INFTY> [0...1]
 <ENDDA>99991231</ENDDA> [0...1]
 <KOSTL>0000012345</KOSTL> [0...1]
 </E1P0001>
</E1PITYP>
<E1PITYP SEGMENT="1"> [0...n]
 <E1P0315 SEGMENT="1"> [0...n]
 <INFTY>0315</INFTY> [0...1]
 <ENDDA>99991231</ENDDA> [0...1]
 <KOSTL>0000024001</KOSTL> [0...1]
 </E1P0315>
</E1PITYP>
</E1PLOGI>
How can I do the check if field KOSTL of node E1P0315 is null?
I've tried an existence check for the whole node (E1P0315->exists), but then it fails, because all E1PITYP nodes are processed.
I hope my problem is clear to you.
Would it be better to use another mapping type?
As I'm an ABAP developer, I would of course prefer some lines of code to this graphical drag&drop thing.
Thanks in advance!

Cheers, guys!
I did it now like that:
http://www.abload.de/image.php?img=mappingflknz.jpg
Click on the image to enlarge it!
The logic is as following (ABAP Pseudo-code ):
IF 0315_KOSTL and 0315_ENDDA are populated.
IF 0315_ENDDA equals '99991231'.
 map 0315_KOSTL to Cost_Center.
ENDIF.
ELSE.
IF 0001_KOSTL and 0001_ENDDA are populated.
 IF 0001_ENDDA equals '99991231'.
 map 0001_KOSTL to Cost_Center.
 ENDIF.
ENDIF.
ENDIF.
Is that a good way to do that mapping?
Do I also have to use the removeContexts function or is it ok like that?
Could I also do that with an ABAP mapping program?
Thanks in advance!

Reg : IDOC data mapping

Hi All,
Which is the function module which Extracts the data from the application document ( Sales order or quotes ) and populates to the SAP message type Idoc segments.
what are the SAP table involved in doing this mapping.
Thanks & Regards.
vijay

Unfortunately the mapping is not in any table but in the source code as extracted here:
e1cuins-class_type        cuins-class_type
e1cuins-inst_id           cuins-inst_id
e1cuins-obj_key           cuins-obj_key
e1cuins-obj_txt           cuins-obj_txt
e1cuins-obj_type          cuins-obj_type
e1cuins-quantity          cuins-quantity
e1cuprt-class_type        cuprt-class_type
e1cuprt-inst_id           cuprt-inst_id
e1cuprt-obj_key           cuprt-obj_key
e1cuprt-obj_type          cuprt-obj_type
e1cuprt-parent_id         cuprt-parent_id
e1cuprt-part_of_no        cuprt-part_of_no
e1cuval-author            cuval-author
e1cuval-charc             cuval-charc
e1cuval-charc_txt         cuval-charc_txt
e1cuval-inst_id           cuval-inst_id
e1cuval-value             cuval-value
e1cuval-value_txt         cuval-value_txt
e1edk01-autlf             xvbak-autlf
e1edk01-belnr             ekko-ebeln
e1edk01-bsart             ekko-bsart
e1edk01-curcy             iso_waers
e1edk01-kzabs             pekko-kzabs
e1edk01-kzazu             xvbkd-kzazu
e1edk01-lifsk             xvbak-lifsk
e1edk01-recipnt_no        ekko-lifnr
e1edk01-vsart             xvbak-vsbed
e1edk01-zterm             ekko-zterm
e1edk02-belnr             ekko-angnr
e1edk02-belnr             ekko-ebeln
e1edk02-belnr             ekko-konnr
e1edk02-belnr             ekko-submi
e1edk02-belnr             pekko-labnr
e1edk02-datum             ekko-bedat
e1edk02-uzeit             sy-uzeit
e1edk03-datum             ekko-angdt
e1edk03-datum             ekko-bedat
e1edk03-datum             ekko-bnddt
e1edk03-datum             ekko-bwbdt
e1edk03-datum             ekko-ihran
e1edk03-datum             ekko-kdatb
e1edk03-datum             ekko-kdate
e1edk03-datum             pekko-eindt
e1edk03-datum             sy-datlo
e1edk14-orgid             ekko-bsart
e1edk14-orgid             ekko-bukrs
e1edk14-orgid             ekko-ekgrp
e1edk14-orgid             ekko-ekorg
e1edk17-lkond             ekko-inco1
e1edk17-lkond             xvbkd-inco1
e1edk17-lktext            ekko-inco2
e1edk17-lktext            xvbkd-inco2
e1edk18-prznt             ekko-zbd1p
e1edk18-prznt             ekko-zbd2p
e1edk18-tage              ekko-zbd1t
e1edk18-tage              ekko-zbd2t
e1edk18-tage              ekko-zbd3t
e1edka1-bname             ekko-verkf
e1edka1-bname             t024-eknam
e1edka1-ihrez             ekko-ihrez
e1edka1-ihrez             ekko-unsez
e1edka1-ilnnr             h_iln_vendor
e1edka1-lifnr             h_pekko_werks
e1edka1-lifnr             pekko-werks
e1edka1-orgtx             t024e-ekotx
e1edka1-pagru             ekko-ekgrp
e1edka1-paorg             ekko-ekorg
e1edka1-partn             ekko-lifnr
e1edka1-partn             ekko-logsy
e1edka1-partn             lfa1-lifnr
e1edka1-partn             lfb1-eikto
e1edka1-partn             pekko-kunnr
e1edka1-partn             t000-logsys
e1edka1-partn             xvbpa_we-kunnr
e1edka1-parvw             'EZ'
e1edka1-parvw             h_parvw
e1edka1-parvw             'LF'
e1edka1-parvw             'WE'
e1edka1-spras             ekko-spras
e1edka1-telf1             ekko-telf1
e1edka1-telf1             t024-ektel
e1edka1-telfx             t024-telfx
e1edkd1-ekgrp             ekko-ekgrp
e1edkd1-ekorg             ekko-ekorg
e1edkp1-defpa             xekpa-defpa
e1edkp1-ekorg             xekpa-ekorg
e1edkp1-lifn2             xekpa-lifn2
e1edkp1-ltsnr             xekpa-ltsnr
e1edkp1-parvw             xekpa-parvw
e1edkp1-werks             xekpa-werks
e1edkt1-tdid              xt166a_del-tdid
e1edkt1-tdid              xt166k_del-tdid
e1edkt1-tsspras           ekko-spras
e1edp01-abftz             ekpo-abftz
e1edp01-antlf             xvbap-antlf
e1edp01-bmng2             ekpo-ktmng
e1edp01-bmng2             ekpo-menge
e1edp01-bpumn             ekpo-bpumn
e1edp01-bpumz             ekpo-bpumz
e1edp01-brgew             e1edp01-menge*ekpo-brgew
e1edp01-evers             ekpo-evers
e1edp01-gewei             ekpo-gewei
e1edp01-kzabs             ekpo-kzabs
e1edp01-lgort             ekpo-lgort
e1edp01-matkl             ekpo-matkl
e1edp01-matnr             ekpo-matnr
e1edp01-menee             ekpo-meins
e1edp01-menge             ekpo-ktmng
e1edp01-menge             ekpo-menge
e1edp01-netwr             ekpo-netwr*cur_factor
e1edp01-ntgew             e1edp01-menge*ekpo-ntgew
e1edp01-peinh             ekpo-peinh
e1edp01-pmene             ekpo-bprme
e1edp01-posex             ekpo-ebelp
e1edp01-posguid           xvbap-posguid
e1edp01-pstyp             ekpo-pstyp
e1edp01-uepos             ekpo-uebpo
e1edp01-vprei             ekpo-netpr*cur_factor
e1edp01-werks             ekpo-werks
e1edp02-belnr             ekpo-aktnr
e1edp02-belnr             ekpo-konnr
e1edp02-belnr             ekpo-labnr
e1edp02-belnr             h_xvbkd-bstkd_e
e1edp02-belnr             xvbap-werks_ext
e1edp02-belnr             xvbkd-bstkd_e
e1edp02-bsark             h_xvbkd-bsark_e
e1edp02-bsark             xvbkd-bsark_e
e1edp02-ihrez             h_xvbkd-ihrez_e
e1edp02-ihrez             xvbkd-ihrez_e
e1edp02-zeile             ekpo-ktpnr
e1edp02-zeile             h_xvbkd-posex_e
e1edp02-zeile             xvbkd-posex_e
e1edp03-datum             ekpo-abdat
e1edp03-datum             ekpo-agdat
e1edp17-lkond             ekpo-inco1
e1edp17-lkond             xvbkd-inco1
e1edp17-lktext            ekpo-inco2
e1edp17-lktext            xvbkd-inco2
e1edp19-idtnr             ekpo-ematn
e1edp19-idtnr             ekpo-idnlf
e1edp19-idtnr             ekpo-matnr
e1edp19-ktext             ekpo-txz01
e1edp20-ameng             xeket-ameng
e1edp20-ameng             xeket-wemng
e1edp20-edatu             xeket-eindt
e1edp20-ezeit             xeket-uzeit
e1edp20-wmeng             xeket-menge
e1edpa1-partn             ekpo-kunnr
e1edpa1-partn             xvbpa_we-kunnr
e1edpd1-bednr             xekpo-bednr
e1edpd1-bstae             xekpo-bstae
e1edpd1-insmk             xekpo-insmk
e1edpd1-knttp             xekpo-knttp
e1edpd1-kzabs             xekpo-kzabs
e1edpd1-labnr             xekpo-labnr
e1edpd1-lgort             xekpo-lgort
e1edpd1-mahn1             xekpo-mahn1
e1edpd1-mahn2             xekpo-mahn2
e1edpd1-mahn3             xekpo-mahn3
e1edpd1-mwskz             xekpo-mwskz
e1edpd1-prsdr             xekpo-prsdr
e1edpd1-schpr             xekpo-schpr
e1edpd1-spinf             xekpo-spinf
e1edpd1-uebtk             xekpo-uebtk
e1edpd1-uebto             xekpo-uebto
e1edpd1-untto             xekpo-untto
e1edpd1-webre             xekpo-webre
e1edpd1-werks             xekpo-werks
e1edpt1-tdid              xt166p_del-tdid
e1edpt1-tsspras           ekko-spras
e1eds01-summe             ekko-ktwrt*cur_factor
e1eds01-summe             pekko-netwr*cur_factor
e1eds01-sunit             iso_waers
Whenever you have qualifiers, the segments appear multiple with diefferent fields.
Regards,
Clemens

Help needed on IDOC segents mapping

Hi All,
I have a requirement.
The scenario is File -- XI -- IDOC and inside mapping i have a RFC look up. The file is as below.
ConractNumber1, line item1 Price, line itm1UOM,etc...
ConractNumber2, line item2 Price, line itm2UOM,etc...
ConractNumber3, line item3 Price, line itm3UOM,etc...
The busniess requiremetnt is as below.
There is a existing contract data in R3 and for every contract there are line items. In the text file i have existing contract number and some line items. What i need to do is,... i need to add my line items at the end of the contrat in R3. For this reson.. there is a custum RFC is alreay in place, which takes Contratnumber as in put and returns NEXT AVAILABLE position to update line item for that contact.
Here I can write A RFC look up and get Next Availeble Position from RFC into PI mapping.... But my problem is i need to map that value IDOC Segment to look like E1EDK01[NEXT AVAILABLE Poistion].
I know that we can do this by adding subtree provision in mapping... But is is not dayamic... like if i duplicate sub tree... i will get E1EDK01[1]... But not E1EDK01[54] where 54 is value form RFC lookup.
Here Text file contains recrods 1...Infinity..
ecah and every record contains its own contract data and one line item to be added. next record may contain diffrent contract data or same contract data along with one more line item.
Kinldy share your thoughts how to go ahead. I want to know how mapping should be done for that partcular idoc segment like E1EDK01[54] where 54 is value form RFC lookup
Thnx
Subbu

Hi,
I could not understand why you want the next available position to appear with E1EDK01 segment. I think as per your requirment you need to look for a field in IDOC where you can pass the next available position so that while posting the IDOC the Line item is posted at right place.
Regards,
Shweta

Inbound Idoc Data mapping sheet

Hi experts,
I need a data mapping sheet of Inbound Idoc that will help me for mapping the segments (header, Item) both for creating material, vendor, customer etc.
That sheet will help for mapping tables and fields that are mandatory for that segments.
Thanks & Regards.
Ankur Garg.

The process code you assigned to the inbound IDoc, has to be assigned to a function module which processes this IDoc, right? Now, if you use a function module of your own (CUSTOM FM!), you can do all the 'printing' you want.
So there is no option for printing by default (standard), but you will have to do it your self.
Another option would be to use a User exit. It seems there is a standard User exit (SIDOC001), or even a BAdI which you can use. I haven't used it myself, so can't help you there.
Edited by: Micky Oestreich on Mar 9, 2009 8:43 AM

Invoice IDOC data mapping

plz help in mapping of these two fields in INVOIC02 IDOC
BSCHL Posting Key
GJAHR Fiscal year
thanks ..
plz send me if you have any info about data mapping and processing a idoc...
pts ll be given to all helpful answers
Message was edited by: sharadha sharma

INVOIC02 is for billing document. If you are looking for accounting document then i think you should be looking at ACC_DOCUMENT02.

Need help with IDOC CREMAS_03 mapping

i was not able to figure out what values to assign to the following mandatory fields.
BEGIN
EDI_DC40(node not mandatory)
SEGMENT
TABNAM
DIRECT
IDOCTYP
MESTYP
SNDPOR
SNDPRT
SNDPRN
RCVPOR
RCVPRN
i am trying to map the following structure to the CREMAS_03
Vendor_MT
VendorNumber
LastName
SearchTerm
Currency
Address
Street
City
Zip
Country
i appreciate ur time and help

you dont need to map EDI_DC40, In the message mapping right click on the EDI_DC40 segment and click on disable field.
In the IDoc receiver communication channel, you should uncheck Apply control record values from payload
regards
SKM

XML to IDOC : Hierarchy mapping help needed

Hi All,
I am trying to complete graphical mapping for an XML to IDOC structure. Both structures are EXACTLY same, but data is not populating in IDOC as desired.
My incoming XML structure and IDOC structure is
Header
Data_header (1 -- 999)
|_Data_item (1 -- 3)
Trailer
If I have only 1 header, then IDOC data is populated correctly.
But when I have multiple headers and theer items, the Headers are getting populated, but items do not get populated correctly.
*Example My Input is:*
Header
Data_header
|_Item_1
|_item_2
Data_header
|_item_3
Trailer
My output is (IDOC)
Header
Data_header
|_Item_1
Data_header
|_Item_2
Trailer
As seen above Item3 of Data_header2 has gone missing._
For Data Header, I am using REMOVE_CONTEXT function and for ITEM I am using SPLITBYVALUE. Thought this should have helped, but am struggling.
Any tips, help, greatly appreciated.
Many thanks
Shirin

Hello,
Have you done one to one mapping, as u mentiong they are exactly same..
if that's the case, then mapping test should be successful.
If there is any diffrence in occurences of target structure or any other difference and let me know.
If possible send me the target structure...
Regards,
Sreenivas.

Idoc field mapping help needed

Hi xperts,
Am doing some simple mapping, but, facing context issues,
Source                                                       Target
(level 1)-FIDCC2X                                                (level 1)-ACC_DOCUMENT03
(level 2)--IDOC                                                  (level 2)--IDOC
(level 3)---EDI_DC40                                             (level 3)---EDI_DC40
(level 3)---E1FIKPF                                              (level 3)---E1BPACCR09
(level 4)----E1FISET                                             (field    )----AMT_BASE
(field    )-----H2BAS( should be mapped to AMT_BASE, when
                                   an CR09 segment is cerated)
Tried alternative options with remove_contexts & splitbyvalue.
CR09 segment is being created, But, field is not being mapped.
Any ideas, what is the correct mapping steps.....
-santosh.

Hi vkjoat,
it seems quite simple, but causing problems due to context issue.
CR09 segment is created in my test case, but value from E1FISET-H2BAS is not being populated in E1BPACCR09-AMT_BASE.
Unable to figure out the context issue.....
Cardinality of   mapping is 1:1 .
-thx.

JDBC to IDOC scenario - Mapping problem with E1FIBSEG

Hi friends,
I have problem when generate multiple Idocs (FIDCC1) an multiple positions based on an External Definition for a SQL Server table. I have selected all fields from this table from a SELECT into the JDBC configuration.
My mapping is like this:
DWCAJA.ResultSet 1..1
 IDOC.
Thats ok and generate n IDOCs by every change of PK.
The problem is when i want to map positions because i dont have any field in source message to identify the number of positions to map with E1FISEG.
If I have two differents Pks and n rows, the result of testing is as folow:
FIDCC1
IDOC
 E1FIKPF
 E1FISEG
 E1FISEG
IDOC
 E1FIKPF
I cant obtain n BSEG segments according PK. I've mapped and all fields of row segment but those are created in the first IDOC node only,
Any suggestions?
Regards,
Pablo.-

Important: Primary key : DWSucCod + DWCajSec
Payload:
- <row>
<DWSucCod>11</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100001</DWCtaConCo>
<DWRecImp>100</DWRecImp>
</row>
- <row>
<DWSucCod>11</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100002</DWCtaConCo>
<DWRecImp>200</DWRecImp>
</row>
Result:
IDOC
 E1FIKPF
 E1FISEG
 hkont :1100001
 dmbtr : 100
 E1FISEG
 hkont :1100002
 dmbtr : 200
Payload:
- <row>
<DWSucCod>11</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100002</DWCtaConCo>
<DWRecImp>200</DWRecImp>
</row>
- <row>
<DWSucCod>12</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100003</DWCtaConCo>
<DWRecImp>300</DWRecImp>
</row>
Result:
IDOC
 E1FIKPF
 E1FISEG
 hkont :1100002
 dmbtr : 200
IDOC
 E1FIKPF
 E1FISEG
 hkont :1100001
 dmbtr : 300
Payload:
- <row>
<DWSucCod>11</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100001</DWCtaConCo>
<DWRecImp>100</DWRecImp>
</row>
- <row>
<DWSucCod>11</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100002</DWCtaConCo>
<DWRecImp>200</DWRecImp>
</row>
- <row>
<DWSucCod>12</DWSucCod>
<DWCajSec>1</DWCajSec>
<DWCtaConCo>1100003</DWCtaConCo>
<DWRecImp>300</DWRecImp>
</row>
Result:
IDOC
 E1FIKPF
 E1FISEG
 hkont :1100001
 dmbtr : 100
 E1FISEG
 hkont :1100002
 dmbtr : 200
IDOC
 E1FIKPF
 E1FISEG
 hkont :1100003
 dmbtr : 300

Flat file to idoc MATMAS05 - mapping

Hi,
I want to create 2 Idocs from one recordset.
Can any one tell me how do I map this Recordset to an Idoc?
Example source and target IDOC structures:
Source:-
 <Recordset>
 <SA010>
 <IDENTS>1234</IDENTS>
 <BEZ>Dummytxt</BEZ>
 </SA010>
 <SA088>
 <IDENTS>1234</IDENTS>
 <MARC1>010</ MARC1>
 <MARC2>020</MARC2>
 </SA088>
 </Recordset>
Target:-
 <MATMAS05>
 <IDOC BEGIN="1">
 <E1MARAM SEGMENT="1">
 <MATNR>1234</MATNR>
 <E1MARCM SEGMENT="2">
 <WERKS>010</WERKS>
 </E1MARCM>
 </E1MARAM>
 </IDOC>
 </MATMAS05>
 <MATMAS05>
 <IDOC BEGIN="1">
 <E1MARAM SEGMENT="1">
 <MATNR>1234</MATNR>
 <E1MARCM SEGMENT="2">
 <WERKS>020</WERKS>
 </E1MARCM>
 </E1MARAM>
 </IDOC>
 </MATMAS05>
Thanks and Regards,
Eren

Hello Varun,
My flat structure:
<Recordset>
<SA010>
<IDENTS>1234</IDENTS>
<BEZ>Dummytxt</BEZ>
</SA010>
<SA088>
<IDENTS>1234</IDENTS>
<MARC1>010<>
<MARC2>020</MARC2>
</SA088>
</Recordset>
The MATNR field is <IDENTS>. I can pick the value from node <SA010> or <SA088>.
Thanks

IDOC-X12 Mapping instructions

Similar Messages

Maybe you are looking for