IDOC to EDI Seeburger Mapping Issue

Hi,
I am new to seeburger, Currently I am working on PAYEXT IDOC to EDI scenario using seeburger adapter.
As per my little knowledge i can understand that i need two step mapping:
1) IDOC XML to EDI XML
2) EDI XML to EDI
Now the problem is how can i do 1st mapping if i have to do 1:1 mapping in PI mapper than it will be a tedious task as I dont know which idoc field is mapped to which EDI XML field.
Also i dont know how i can map the 2nd mapping.
when we installed seeburger adapter than i got three files from basis guys related to PAYEXT
msg_PAYEXT_UN_D96A.xml
msg_XML_PAYEXT_UN_D96A.xml
XML_PAYEXT_UN_D96A.xsd
Note: I imported .xsd file in IR, but i dont know what to do with these xml files.
Please experts reply soon as it is delaying my project
Regards,
Shradha

Shradha,
You can check the seeburger software component versions where all the mappings would be provided by Seeburger as part of the package.
You can have a look whether PAYEXT is there and would be useful
To start with
1. You need a functional or EDI Business analyst to guide you on the various mapping specifications needed.
2. You should also liase with your business partners to prepare an business rules and other conditions.
3.Also decide whether you are going to deliver it via AS2 communication or via VAN
4. Accordingly you need to configure the seeburger adapters.
5.The mappings provided to you are from XML to EDI and EDI to XML which is a second stage automatically done by seeburger once you specify the module steps in the comms channel.
I am afraid that without knowing business rules or mapping specifications, you can't work on EDI.
Regards
Krish

Similar Messages

Idoc to edi scenarios (mapping help is required)

hi expects ,
    i am working on idoc to edi scenarios in which i am using seeburger abapter.and i have to use java mapping with using some standard function.
INPUT IDOC :
                    Name                         M/C     Min Use      Max Use        Description
INPUT*                                              M               1           1
Record EDI_DC40*                                 C               0           1                       Control Record
Record E2EDK01*                                  C               0           1                       Document Header General Data
     Record E2EDK14*                                  C               0          12                       Header Organizational Data
     Record E2EDK03*                                  C               0          10                       Header Date Segment
Record TEMP_DATE*                                C               0           1                       Temporary Date Segment
     Record DEL_DATE*                                 C               0           1                       Temporary Date Segment
     Record E2EDK04*                                  C               0          10                       Header Taxes
Record E2EDK05*                                  C               0          16                       Header Conditions
Record E2EDKA1*                                  C               0       99999                       Header Partner Info
Record TEMP_SHIP_TO*                             C               0           1                       Ship-to Info
Record TEMP_SOLD_TO*                             C               0           1                       Sold-to Info
Record TEMP_PAYER*                               C               0           1                       Payer Info
Record TEMP_CARRIER*                             C               0           1                       Carrier Info
Record TEMP_DISCHARGE_PORT*                      C               0           1                       Port of Discharge info
     Record TEMP_NOTIFY*                              C               0           1                       Notify Info
Record TEMP_NOTIFY_ALSO*                         C               0           1                       Notify Also Info
Record TEMP_EXIT_PORT*                           C               0           1                       Port of Exit Info
Record TEMP_CONSIGNEE*                           C               0           1                       Consignee
Record TEMP_SHIPPER_INFO*                        C               0           1
Record E2EDK02*                                  C               0          10                       Header Reference Data
     Record TEMP_E2EDK02*                             C               0           1                       Temp E2EDK02
Record TEMP_PO_STRING*                           C               0           1                       TEMP PO STRING
Record E2EDK17*                                  C               0         999                       Header Terms of Delivery
     Record TEMP_E2EDK17*                             C               0           1                       Temp transportation terms
     Record E2EDK18*                                  C               0          99                       Header Terms of Payment
     Record TEMP_TERMS*                               C               0           1
Record E2EDK35*                                  C               0          10                       Additional Data
Group E2EDKT1:2*
OUTPUT FIELD:
Segment B2*                                      M               1           1                       BEGINNING SEGMENT FOR SHIPMENT INFORMATION TRANSACTION
     Segment B2A*                                     C               0           1                       SET PURPOSE
Segment N9:6*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:7*                                    C               0           1                       REFERENCE IDENTIFICATION
     Segment N9:8*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:9*                                    C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:10*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment N9:11*                                   C               0          99                       REFERENCE IDENTIFICATION
     Segment CUR*                                     C               0           1                       CURRENCY
Segment ITD*                                     C               0           1                       TERMS OF SALE/DEFERRED TERMS OF SALE
     Group DTM_GROUP*                                 C               0           1
Segment DTM*                                  C               0           1                       DATE/TIME REFERENCE
Segment DTM:2*                                C               0           1                       DATE/TIME REFERENCE
Segment DTM:3*

Hi,
To do the mapping,,,,even you can go for graphical mapping....
But some of the context handling issues you need to deal with,
like....
1.Never map set context of source fields to element level but Segment level.
2. Always you need to check for qualifiers while mapping it to Traget field.
Thanks & Regards
Akshay.
Dont Forget TO Give Points.

Issue with IDOC occurence and SeeBurger message mapping

Hey Guys
While developing a EDI 850 to IDOC scenario i came across this issue with pre-delivered Seeburger mapping(A_850_V4010_to_I_ORDERS05).
I actually need to post multiple IDOC's to SAP system in the same message so i changed the IDOC occurence to unbounded and re-imported that as a .XSD file in Integration repository.
Earlier the pre-delivered message mappings provided by SeeBurger(under SEEBURGER_HIGH-TECH, 1.7.1 of seeburger) was working fine for me since i was posting only 1 IDOC but now the mapping is failing as the IDOC occurence has changed(unbounded).
Is there a way we can do some settings on SeeBurger server or Bic so that we can use the pre-delivered mapping for Multiple IDOC's as well?
I just want to make sure before i start off with doing whole of the mapping manually.
Thanx
Aamir

Thanx for the input guys
@Deepthi.
Doing whole of mapping manualy is definitely the last option but i m looking for ways to re-use the pre-delivered SeeBurger mapping.
>>Seeburger Mapping is only just to convert XML to EDI and EDI to XML.
Bic mapping designer does this,i m dealing with message mapping of XI(convert source to target) not Bic designer right now,and Bic does more than just XML to EDI and vice versa,it handles other industry standards too.
@Jens
>>The XI message mappings from Seeburger in the Industry solutions are mapping templates
Yeah,but the mapping template i have deals with 850 to ORDERS05,when i change IDOC occurence and re-import it back in Integration repository,it doesn't stays as ORDERS05,it has to be changed to user defined message interface(in my case MI_ORDERS05) so i m unable to use 850 to ORDERS05 template.
@Seshagiri
>>Open the Seeburger SWCV From the IR--goto External Def---Select the right one and copy it and paste it in notepad.
Changing the occurence is not an issue,i want to re-use the pre-delivered mapping in Integration repository,which is not working.
Looks like i need to do it manually
Thanx
Aamir

PI EDI help: What is the source of ISA13 in a IDOC to EDI mapping

Hello Experts,
It would be of great help if you can provide the field mapping for ISA 13 in outbound from IDOC sceanrio:
IDOC: INVOIC02 - to - EDI 810 mapping.
Is it the best practice to have ECC send the value in a particular IDOC field ( like RFINT) or PI has to use a custom function to populate the ISA13 field.?
Thank you,
Patrick.

Hi,
ISA13 is for Interchange Control Number. It is a control number assigned by the interchange sender.
Normally its Sequential number starting with 000000001 and incremented by 1 for each subsequent ISA between sender and receiver.
This is a very useful value to include. It creates an explicit link between the IDoc and the EDI transmission. This number eases Production Support greatly. When there's an issue with a Partner EDI transmission, the Partner's EDI support people want to know the Interchange Control Number
The IDoc interface does not process or check this field.
regards
Ganga

Mapping from PEXR2002 iDoc to EDI 820

We are planning to use XI to map from the payment advice (PEXR2002) iDoc to EDI 820.
We have 2 options: (1) Use XI and an EDI adapter (e.g. Seeburger); or (2) Use XI's own mapping functionality.
If you have done iDoc to EDI mapping with either of the above 2 options, please briefly advise about your experiences and how much efforts it took to develop the mapping.
Thank-you
Bac Quan

Hi Bac,
Although it is possible to create an EDI message in an XI mapping (or XSLT), this is not very nice. The use of an EDI adapter (iWay or SeeBurger) is strongly recommended.
The other way around (rom EDI to XML) is hardly feasiable without an EDI adapter. Although I haven't worked the SeeBurger adapter, it looks quite nice.
Kind regards, Guy Crets

Mapping issue in idoc to JDBC scenario

mapping issue in idoc to JDBC scenario
source structure
E1KNB1M
BUKRS = 1000
E1KNB1M
BUKRS= 9000
E1KNB1M
BUKRS= 2000
THE NODE E1KNB1M is repeated many times and the field BUKRS is also repeated with E1KNB1M as above
TARGET field : ISFRANCHISE
if any where value of BUKRS =9000 we have to pass Y to the target filed, else N
if BUKRS = 9000   THEN ISFRANCHISE= Y
               ELSE
            ISFRANCHISE=N
I've done the mapping as below
BUKRS = 9000--> IF THEN Y ELSE N--
> ISFRANCHISE
BUT everry time the target value is N only
pl suggest
rgds
mojib

mapped like this
BUKRS--->SORT---->
                                             EQUALS --------IF---THEN    Y
9000------------------------>                                               ----------------->ISFRANCHISE
                                                              ELSE   N
context of BUKRS set to parent node
its worked
thanks to all for valuable suggestions
rgds
mojib

Problem with mapping [Idoc to EDI]

Hi experts,
i am facing a new problem in my mapping (idoc to edi scenario)
my target is as follow:
InvoiceDME
>Invoice 1..1
>>InvoiceHeader 1..1
>>>IncotermsCode 1..1
My Idoc is as follow:
IDOC
>E1EDK17 0..20
>>QUALF
>>LKOND
>>LKTEXT
There can be 2 scenarios in my source:
1st:
IDOC
>E1EDK17
>>QUALF = 001
>>LKOND = lkond001
>>LKTEXT
2nd:
IDOC
>E1EDK17
>>QUALF = 001
>>LKOND = lkond001
>>LKTEXT
>E1EDK17
>>QUALF = 002
>>LKOND = lkond002
>>LKTEXT = lktext002
If QUALF=002 then I have to take both values of LKOND and LKTEXT and map them to incotermcode
else if qualf=001 alone, then map LKOND to incotermcode
my mapping is as follow:
http://www.flickr.com/photos/30317046@N05/2862446903/
as you can see, the problem is if i am in my second scenario, i get the wrong value in incotercode (lkond001 instead of the concatenate of LKOND and LKTEXT for QUALF = 002)
Do you have any idea how I can solve this??
Thanks a lot,
Regards,
Jamal

Actually i used java mapping:
 //write your code here
try
 String returnString = "";
 for (int i = 0; i < QUALF.length; i++)
 if (("002".equals(QUALF.trim())))
 returnString = returnString +" "+ LKOND +" "+ LKTEXT;
 result.addValue(returnString);
catch(Exception e)
 e.printStackTrace();
and the condition on the 'count' of QUALF (if = 2 then else)
Thanks,
Regards,
Jamal

Mapping issue: FCC: Idoc for each record in file

Hi,
I have file to Idoc scenario.
I receive csv file with multiple records.
The requirement is to create an Idoc for each record.
For eg.
source file
A1,B1,C1
A2,B2,C2
A3,B3,C3
After FCC
<MT>
<TRANS>
<ROW>
<A>A1</A>
B1
<C>C1</C>
</ROW>
<ROW>
<A>A2</A>
B2
<C>C2</C>
</ROW>
<ROW>
<A>A3</A>
B3
<C>C3</C>
</ROW>
</TRANS>
<MT>
I have first tested it with only 1 record to test end to end connectivity. It works as expected and Idoc is posted to target system.
Now when I am trying to send multiple records, I am getting some issues.
Below are the steps that I have taken to process multiple records:
1. Changed the cardinality of ROW (child of RecordSet) from 1 to Unbounded.
2. Changed the occurance of Idoc to Unbounded.
3. Mapped ROW to Idoc root.
I have tested the mapping in IR and it generates multiple IDOCs.
When I send the test file, it fails with error Tag found instead of tag IDOC BEGIN=
I can see the xml message created with multiple ROWs in XI by File adapter in sxmb_moni.
When I do Test Configuration in ID, with the XML message extracted from sxmbmoni, the result that I got was:_
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1></ns0:Message1></ns0:Messages>
This means that idoc was not created while mapping.
But the same sample message works OK in IR!
Pls help where I have missed.
Regards,
Anirudh.

Sudhir,
Thanks for your response.
FCC is working fine. I have taken the XML message in XI created after FCC from csv sample message.
I have tested this message in IR by placing it between
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge">
<ns0:Message1>
</ns0:Message1>
</ns0:Message>
It is working fine and Idocs are created in mapping in IR.
But the same sample message is creating below output ID!
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Messages xmlns:ns0="http://sap.com/xi/XI/SplitAndMerge"><ns0:Message1></ns0:Message1></ns0:Messages>
Regards,
Anirudh.

IDOC to EDI file scenario and EDI file to IDOC scenario without Seeburger

Hi All,
IDOC (Invoice) to EDI file scenario without Seeburger
Pls let me know if anybody have blogs for the same
EDI file to IDOC (Orders) scenario without Seeburger
Pls let me know if anybody have blogs for the same
Regards

Hi Rachit,
>>Can anybody send me blogs to convert IDoc structure to EDI or EDI to IDoc structure using Conversion Agent or using JAVA Mappings.
Using conversion Agent there is no coding, If you have a conversion agent insatlled in your landscape you will have better understanding..
Also java code for IDoc to EDI have some problems:
1. The EDI format differs based on requirement so there will always be a customized code for it.. Like we have IDco to EDIFACT and ANSX12...
2. Because most of these codes are propriety materials I doubt whether anyone be sharing the complete code here in SDN. Better to have a java consultant at your end and put him with your requirement.. From the reply in above threads you should be clear that what you are looking for can be done from java coding..
All the best
Regards
Suraj

File - XI - Idoc : mapping issue

Hello gurus,
I have a mapping issue:
I have a mapping between FICABillingNotification to FKK_EBS_DOC_TREE
Some fields are mapped one to one, others a mapped to constants.
But for some reason i don't know, not all fields get the right value.
For example:
Working:
Constant 1 --> BEGIN
Constant LS --> RCVPRT (Receiver Partner Type)
Not working:
Constant FILE-->RCVPOR (Receiver Port)
I had an other value the first time i tried it, but now i changed it to FILE but this value is not used by the mapping.
Any help would be welcome
Thanks
Thomas
Edited by: Thomas Pary on May 28, 2008 3:36 PM

This was allready done (sorry i didn't answered that question).
But Ok now i see, that for this RCVPOR the value of the constant "FILE" is mapped, and i can see it in the payload in SXMB_MONI after the mapping. But it isn't populated to the IDoc field :-s
Another problem is, that like the one said above, some of my values are not mapped :
<FICAExternalBilling>
--<DocumentHeader> mapped to EF1KK_EBS_DOC_HEADER
<BillFromId>25001254</BillFromId> mapped to REF_DOC_NUMBER
<PostingDate>20080520</PostingDate> mapped to POST_DATE
<DocumentDate>20080520</DocumentDate> mapped to DOC_DATE
<OriginTypeId>IV</OriginTypeId> mapped to EXT_DOC_TYPE
<ObjectType/>
<ObjectKey/>
<PendingCommitmentGroupID/>
<InvoiceReferenceID/>
<DisputeDocumentReferenceID/>
--</DocumentHeader>
The value of OriginTypeId is not mapped, but the value of DocumentDate and PostingDate are mapped.

IDOC to EDI Scenario using Seeburger....

Hi Experts,
On the Scenario IDOC to EDI when will I use As2 adapters or SFTP adapters of seeburger or just a simple FIle adapter?
and any idea what are the modules I need to import on my comm channel using file adapter?
Thanks.

Hello
Check this blog: /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
Regards
Mark

Functional Specs for Mapping Idocs to EDI

Hello Friends ..
Am new to world of EDI...
can any one explain ..wat do u mean by devolping functional specs for mapping IDocs to EDI..
If you can provide me with examples or if you guys can suggest any site where i can browse some material about EDI..i wud really appreciate...
Best Regards

Hi Rohan,
>>>do u mean by devolping functional specs for mapping IDocs to EDI..
you have to know which idoc fields you have to map to EDI message fields
take a look at those links:
they will show how do you map different IDOC message types to EDI messages
IDOC - EDI mappings:
http://www.sapgenie.com/sapedi/mapping.htm
Analysis of the compatibility of EDIFACT messages in the form of SIMPL-EDI with the IDoc Interface:
http://www.sapgenie.com/sapgenie/docs/SIMPL-EDI-E_ORDERS.doc
Regards,
michal

PI Seeburger Map Problem

Hi,
Plzz help me on this issue,
I am working on edi to idoc scenarion using seeburger.
I want to map EDI850 to Idoc. In PI Repository I have standard Mappings with version 4010.BUt,
I need Version 4030 Mappings. Where do i get these version mappings.
Can use same version mappings. Plzz help me on this.
Thanks,
Singh.

Hi Seenu/Singh ( Why mutiple names??),
When you say mappings, there are two types of mapping in Seeburger EDI scenarios.
1) EDI2XML, XML2EDI mappings which convert the ED formatI to XML and vice versa.
2) The actual EDIXML data to the IDOCXML data.
The first type of mappings, you should use BIC mapping designer to develop and then deploy in the PI server.
The second mapping, you have to create in your Integration repository(Within PI system).
The External definition that you see is not the one you want.
If you want to map the IDOC to the EDI 850 V4030, then you should do the following.
1) Login into the physical server of the PI system using Remote Desktop (The userid and pwd are not the ones u use for logging into IR or ID. Contact your basis team to get access to the physical server of PI system)
2) Open the file explorer in that system and navigate to a directory by name seeburger. Inder that you have to search for XSD file corresponding to your EDI Document and version.
3) Copy that file and paste it on your desktop.
4) Then open your IR.
5) Right Click on the external definitions node and click on new.
6) Then import the xsd file which is now tehre on your desktop into PI system.
7) Now, create a message mapping under the mappings node.
8) Drag your IDOC structure as the source and External Definition as your target.
9) Then you can do your mapping as per the requirement.
Regards,
Ravi Kanth talagana

IDOC to EDI

Hi all,
I am working on Idoc to EDI ANSI X12 Invoice 810 scenario, I created a receiver communication channel with File adapter and included those modules. But I am not sure is there any other additional module parameter that needs to be specified other than the once that are mentioned below.
Processing sequence:
localejbs/CallBicXIRaBean bic
CallSapAdapter 0
and
Module configuration:
bic destSourceMsg MainDocument
bic destTargetMsg MainDocument
bic mappingName See_X2E_ANSIX12_810_V4010.
I am getting the following error in receiver communication channel,
"Message processing failed. Cause: java.lang.Exception: Cannot cast to XI message. Reason: BIC module error: Message which was recieved from module processor was null"
But the file in getting generated in the target directory as an xml file, actually the file has to be in EDI format.
Please let me know whether the module is not properly configured or the File adapter does not handle the IDOC to EDI conversion eventhough the module used does the conversion.
Regards,
Nithiyanandam

Hi,
Seeburger tool will not fail to conver the data into file format,they all are already predefined mappings and ANSI X12 is a common mapping used by most of the users and the module parameters which u have specified i dont find any thing more u have to give.
Check ur mapping which u have done and also check all the setting onces
any way iam giving some links on Seeburger check them.
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
/people/william.li/blog/2006/03/17/how-to-get-started-using-conversion-agent-from-itemfield
/people/paul.medaille/blog/2005/11/17/more-on-the-sap-conversion-agent-by-itemfield
http://www.stylusstudio.com/edi/XML_to_X12.html
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/b0b355ae-0501-0010-3b83-8f2bb566fa47
Details on XI EDI adapter from seeburger
Check this for Conversions-
/people/bla.suranyi/blog/2006/06/08/sap-xi-supports-edifact
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
SAP Adapters
EDI with XI
http://www.seeburger.com
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
http://www.seeburger.com
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.seeburger.com/fileadmin/com/pdf/AS2_General_Overview.pdf
http://www.seeburger.it/fileadmin/it/pdf/2005_04_sapphire_Ferrero_transcript.pdf
http://www.seeburger.com/fileadmin/com/pdf/SEEBURGER_SAP_Adapter_engl.pdf
http://www.seeburger.com/fileadmin/com/pdf/Butler_Group_SEEBURGER_Technology_Audit.pdf
http://www.sap.com/france/company/events/2006/02-01-Automotive-Seeburger.pdf
http://h41123.www4.hp.com/presentations/ISUG/XISeeBurger.ppt
http://www.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
Regards,
phani
Reward points if Helpful

XSLT mapping issue in parent child relation

Hi Guys,
i have one XSLT mapping issue. Mapping scenario is from IDoc to file.
IDoc structure is as below
<ZLOIPRO1>
<E1AFKOL>
 <A></A>
 
 <E1RESBL>
 <MATNR>1</MATNR>
 <CHARG>1</CHARG>
 <ZSBL>
 <MTART>ABC</MTART>
 </ZSB>
 </E1RESBL>
 <E1RESBL>
 <MATNR>2</MATNR>
 <CHARG>2</CHARG>
 <ZSBL>
 <MTART>ZHA1</MTART>
 </ZSB>
 </E1RESBL>
 <E1RESBL>
 <MATNR>3</MATNR>
 <CHARG>3</CHARG>
 <ZSBL>
 <MTART>ZHA1</MTART>
 </ZSB>
 </E1RESBL>
</E1AFKOL>
</ZLOIPRO1>
As you can see 'E1RESBL' is repeatative. Now my issue is i need to select 'MATNR' and 'CHARG' from 'E1RESBL' segment when first occurance of 'ZSBL/MTART' with value 'ZHA1' appears. i.e. my output would be MATNR = 2 and CHARG = 2.
I hope i am clear. Please let me know if any solution for this.

Hi,
Try this
<xsl:if test="./ZSBL/MTART == 'ZHA1'">
<xsl:for-each select="./E1RESBL">
<MATNR>
 <xsl:value-of select="./MATNR"/>
</MATNR>
<BATCH>
 <xsl:value-of select="./CHARG"/>
</BATCH>
</xsl:for-each>
</xsl:if>
You might need to do some changes in the above.
Thanks,
Prakash

IDOC to EDI Seeburger Mapping Issue

Similar Messages

Maybe you are looking for