IDoc to EDI mapping problem (Invoic01 to 810 v4010)

Hi,
I have a problem with my invoice mapping.
I need to exclude children parts from the outbound EDI invoice.
In my mapping I was able to control the number of lines that should go out from the top line item node level using:
G_SIT1 -> If E1EDP02-QUALF = 002 then E1EDP02-ZEILE->Remove Context->SplitByValue->CollapseContext->G_STI1
I have the right amount of lines but the fields under G_STI1 are wrong since I'm missing the last ones.
Then I tried different combinations + playing with the contexts and played again with the top node and my conclusion is that it might be easier to exclude them in IDoc in SAP using an UserExit?!?
Anybody was able to get around this problem without changing the IDoc in R/3?

Can I filter on a partner type KU? I need to customize an outboud invoice to not send some segments.
Or is it only for type LS?
Rgds,
Yves

Similar Messages

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

IDOC to File Mapping problem.

Hi all,
I am working on IDOC to file scenario. Here I need to create CSV file for some fields of the IDOC. Actually flat file should contain around 65 comma separated fields irrespective (independent of the segment presence in the IDOC) of the existence of the corresponding filed in the idoc structure. So could you please tell me how to handle this situation?
Here file is supposed to be created with 65 fields. But it only contains few of those, as some segments in the IDOC are missing. Is there any dependency between the filed and its header/segment?
Thanks in advance,
-Kanth.

Hi Prasad,
But it only contains few of those, as some segments in the IDOC are missing. Is there any dependency between the filed and its header/segment? - yes, if your source IDOC is having some segments missing, then your target will not have those segments, so some of your target data will be lost.......
To avoid this you can go for a JAVA mapping.....
Thanks,
Rajeev Gupta

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

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

Message mapping challenge in IDOC to EDI scenario

Dear PI message mapping experts,
I'm a newbie in PI and facing a mapping problem using graphical message mapping.
I'm in an IDOC (INVOIC.INVOICE02) to FILE (EDI) scenario.
Here after is the mapping i need to perform :
Source structure IDOC :
<E1EDKA1> (0..99)
 <NAME1> A </NAME1> (0..1)
 <NAME2> B </NAME2> (0..1)
 <NAME3> C </NAME3> (0..1)
 <NAME4> D </NAME4> (0..1)
</E1EDKA1>
Target structure :
<AccountingCustomerParty> (1..1)
 <Party> (0..1)
 <PartyName> (0..unbounded)
 <Name>A</Name> (1..1)
 </PartyName>
 <PartyName>
 <Name>B</Name>
 </PartyName>
 <PartyName>
 <Name>C</Name>
 </PartyName>
 <PartyName>
 <Name>D</Name>
 </PartyName>
 </Party>
</AccountingCustomerParty>
I know i have to play with context and queues with stanard function or UDF but cannot succeed to do it.
Could you please help me ?
Thanks in advance,
Alysee

One approach out of available few ways to implement this:
NAME1 - Exists - CreateIf - PartyName[0]
NAME2 - Exists - CreateIf - PartyName[1] (Create deuplicate segment)
NAME3 - Exists - CreateIf - PartyName[2] (Create deuplicate segment)
NAME4 - Exists - CreateIf - PartyName[3] (Create deuplicate segment)
Srikanth Srinivasan

Facing Problem in IDOC to EDI FLAT File Scenario

Hi,
I am working on a scenario IDOC to EDI FLAT File. For this I have used ABAP mapping.
The problem i am facing is that the EDI FILE contains the segment name as E1EDK01 for eg. while I need the name as per the latest segment definiton released. I have also tried this using File port and it gives the required segment names in file. But we dont have to use File ports. Please suggest me if something is missing in PI Abap stack ?? Why I am not getting the segments name as per latest segment definition mainatined in R3.
Thanks
Neha

Hi Neha,
Please check the segment name in sxmb_moni. Is this showing new value or the old value?
If SXMB_MONI shows old value then the source SAP (R/3) system which is sending the idoc may not have released the segment after changing the name. You need to ensure that the idoc segment has been released properly. Then re-import the iodc into PI server again. Finally delete entry of the iodc structure in idx2 transaction, no need to re-import the idoc structute again in idx2, since once you run the scenario the metadata automatically gets imported.
regards
Anupam

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

Mapping Problem ORDERS Idoc to Edifact

Hi,
I have a mapping problem with the IDOC ORDERS:
I get the IDOC with several E1EDP01. Each E1EDP01 has several E1EDPT1, where i want only the first one (which I get over the TDID value). Each E1EDPT1 has min. 1 E1EDPT2.
Now I have to map each field TDLINE from first two E1EDPT2 of the first E1EDPT1 to the Edifact fields /LIST/S_UNB/S_UNH/G_SSG25/S_LIN/S_IMD[1]/C_C273/D_7008 (from the first E1EDPT2) and, if a second E1EDPT2 exists in /LIST/S_UNB/S_UNH/G_SSG25/S_LIN/S_IMD[1]/C_C273/D_7008_2.
I use following UDF:
//a = TDLINE
//b = Number of entry in the List
int pos =Integer.parseInt(b[0]);
if ( pos < a.length )
result.addValue(a[pos]);
else
result.addValue(ResultList.SUPPRESS);
Unfortunatly, I think becaus of the context problems (not every E1EDPT1 has two E1EDPT2), it's not working. Could somebody help me with this problem?
Thanks in advance
Dominic

Dear Dominic ,
I had same problem when I was trying to do the same thing for FTX segment.
Your UDF is fine but you don't need else condition.
//a = TDLINE
//b = Number of entry in the List
int pos =Integer.parseInt(b[0]);
if ( pos < a.length )
result.addValue(a[pos]);
for C_C273 assigned contant value and
D_7008 assigned TDLINE but change the context to E1EDPT1
and for D_7008_2
TDLINE(context to E1EDPT1 )
====>UDF====>D_7008_2
Contant(=1)
It should work becasue my map is working fine. If not let me know error message.
Thanks
Shubhankar

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.

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

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

Generating IDoc DDF structures for EDI mapping

Hello all,
I am looking for a way to generate IDoc DDF structures to use them in the EDI mapping in Gentran.
I was able to find one on ERPGenie.com (developed by Kevin Wilson) but it is only available for ECC 4.x. We are on ECC 6 and the program gives me an ABAP dump when I try to run it.
Does anyone have the fix for this code? Or perhaps another way to accomplish this task?
Actually, I am only interested in generating the MBGMCR02 IDoc
Thanks for your help
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Apr 7, 2008 12:36 PM

It's been a long time since I have done any IDOC processing.
Go to SE37 and enter the function module IDOC_INPUT_ORDERS. Display the source code. Search for "CALL CUSTOMER". You should see several "CALL CUSTOMER-FUNCTION" lines. These are enhancements where you can manipulate the IDOC data. If you locate the correct one (where the data is read from the IDOC but not yet validated), you should be able to map the partner function value. Double-clicking on the number in quotes will bring you to an "EXIT_" function module. A "ZX" INCLUDE program is referenced. If you haven't used the exit yet, double-clicking on the ZX INCLUDE will create it. The values passed into the function module are available in the INCLUDE.
Ideally, you should create a project in transaction CMOD that references the chosen enhancement. This way you can activate/deactivate without commenting/uncommenting the code in the INCLUDE.

Mapping Problem(file to 2 basic idocs)

Hi,
In my scenario sender File(divided into 3 parts) and receiver 2 basic IDOCS
I am having the conditions,
1) file field Trans_id(part-1 field) = 20 or 30 then only entire mapping required to transfer the file fields into SAP.(total scenario required to execute)
a)In that po_no( part-2 field) is coming from file then need to map part-2 fields of file to one idoc.
else need to map (file part1 and 2) fields to same IDOC-A
b)If all the fields of part-2 and part-3 equal then part-1 and part-2 fields to one IDOC-A and Part-3 fields to another IDOC-B.
which mapping is suggested to achive the requirement and procedure.
Thanks,
Praveen.

hi,
i Hope useful to you
/people/krishna.moorthyp/blog/2005/06/09/walkthrough-with-bpm - Walk through BPM
/people/siva.maranani/blog/2005/05/22/schedule-your-bpm - Schedule BPM
/people/sriram.vasudevan3/blog/2005/01/11/demonstrating-use-of-synchronous-asynchronous-bridge-to-integrate-synchronous-and-asynchronous-systems-using-ccbpm-in-sap-xi - Use of Synch - Asynch bridge
in ccBPM
https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/1403 [original link is broken] [original link is broken] [original link is broken] - Use of Synch - Asynch bridge
in ccBPM
Regards

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

IDoc to EDI mapping problem (Invoic01 to 810 v4010)

Similar Messages

Maybe you are looking for