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.

Similar Messages

  • IDOC to EDI scenario

    Dear All,
    need your help on how to configure and deploy a scenario for a IDOC to EDI (856)  .  I believe this is like "IDoc to X12 - > X12 to EDI" using AS2 adapter.  BASIS has configured the B2B addon installation and I am not sure about the EDI part in this scenario..
    can you please inform what that the steps (A to Z) needs to be followed and would be great if example scenarios can be uploaded .
    Thanks
    Fernando

    Hi Fernando,
    I guess you're referring to this thread: IDOC to EDI scenario
    For that reason, please do close this one.
    Thank you.
    Dimitri

  • 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

  • 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

  • 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

  • Unable to do IDoc to File Scenario ; Please help me....

    Hi Experts!!!,
                     I am trying to convert an IDoc to an .Txt or .Xml file, But I am un able to do it. Whenever I m trying to configure the Idoc adapter , it's not allowing me to select as "sender" (default it will be on the recvr side). Please help me in this regard. 
    Do I need to use RFC adapet, or BAPI instead of IDoc or any other way..to complete IDoc to File scenario...
    THANKS IN ADVANCE!!!
    Sunil K Shetty.

    HI,
    No need to use Sender Idoc adapter , default , IDoc adapter resides on Integration Engine. No sender communication channel and sender agreement also
    see the below links
    /people/prateek.shah/blog/2005/06/08/introduction-to-idoc-xi-file-scenario-and-complete-walk-through-for-starters - IDoc to File
    IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
    Idoc settings https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/73527b2c-0501-0010-5398-c4ac372c9692
    Regards
    Chilla

  • Scenario mapping - help required

    Scenario:
    A Customer sends a material (for e.g., SUGARCANE) to the company (SAP Implementing). It processes it and send back as SUGAR.
    The customer is charged for the services rendered.
    The stock of sugarcane/sugar should be visible in the system.
    Please guide me how to map this scenario.
    I will be very much grateful.
    Regards,
    Anbu

    This sales process is referred as Job Work in SAP.
    Refer following SDN thread that can be helpful to you in understanding / reference:
    - Sales Process of JOB WORK
    If in case you have any concern or doubt about the process, do revert back.
    But don't forget to put a effort search more information on JOB WORK for reference/understanding. So that you can specific to your requirement.
    Regards
    JP

  • Idoc to File Scenario(SFTP) with special requirement

    Hi experts,
    We have a scenario Idoc-->File(SFTP), in which one field which is having multi-line and we want that field as structured below.
    Expected Output-
    <?xml version="1.0" encoding="UTF-"> <ggol_xml_payment><cust_payment_header><sender_id>SGCI</sender_id><receiver_id>RBOSNL2A</receiver_id>
    <file_creation_date>140314</file_creation_date><file_creation_time>105426</file_creation_time><transaction_count>0</transaction_count>
    <file_ref_nu>510703</file_ref_nu><format>PEXR</format></cust_payment_header>
    <payment>EDI_DC40_U0040000000113461553701
    3014
    E2EDP02001                   
    0040000000113461557000021000013030105100001110                                                                                                             
    E2IDLU5                      
    00400000001134615570000220000000200240000            
    JPY                                                                                    
    E2IDLU5                      
    0040000000113461557000023000000020030                 JPY   
    </payment></ggol_xml_payment>
    As you can see in the expected output, the payment node is itself a flat file king of structure. And it should be as its shown above.
    Can this be done with any custom module or ABAP code? Please suggest over the scenario.
    Thanks a lot!
    Regards,
    Nidhi Srivastava

    Thanks for your replies.
    I know the requirement is bit unclear. Now, the client gave a second option.
    They are telling if the file say xyz.txt(flat file content- mapped to payment node) is there in unix directory and PI picks the file there. Now, the XMLtags needs to be added to this picked file as shown in the above structure.
    xyz.txt
    EDI_DC40_U0040000000113461553701
    3014
    E2EDP02001                   
    0040000000113461557000021000013030105100001110                                                                                                             
    E2IDLU5                      
    00400000001134615570000220000000200240000            
    JPY                                                                                    
    E2IDLU5                      
    0040000000113461557000023000000020030                 JPY   
    Expected Output-
    <?xml version="1.0" encoding="UTF-"> <ggol_xml_payment><cust_payment_header><sender_id>SGCI</sender_id><receiver_id>RBOSNL2A</receiver_id>
    <file_creation_date>140314</file_creation_date><file_creation_time>105426</file_creation_time><transaction_count>0</transaction_count>
    <file_ref_nu>510703</file_ref_nu><format>PEXR</format></cust_payment_header>
    <payment>EDI_DC40_U0040000000113461553701
    3014
    E2EDP02001                   
    0040000000113461557000021000013030105100001110                                                                                                             
    E2IDLU5                      
    00400000001134615570000220000000200240000            
    JPY                                                                                    
    E2IDLU5                      
    0040000000113461557000023000000020030                 JPY   
    </payment></ggol_xml_payment>
    Is this possible anyways? I am not sure if we can write adapter module for adding the tags.
    Please suggest if we can achieve this by any means?
    Thanks!
    Regards,
    Nidhi

  • PP Scenario Mapping help Needed

    Hi Guys
    Can anyone please help to map the following scenario?
    <b>Scenario:</b> SAP PP
    <b>Product:</b> Ingot
    <b>Size:</b> Ingot 100 X 100, Ingot 125 X 125, Ingot 160 X160
    <b>Grade:</b> A, B, C,……
    <b>Saleable Item:</b> Ingot100 X100 Grade A, Ingot100 X100 Grade B, Ingot160 X160 Grade C etc. (i.e. combination of Grade & Size will determine the saleable items.)
    <b>Characteristics to determine Grades:</b> Carbon%, Phos%, Mn%,………
    <b>Requirement:</b>
    1.     Planning scenario make to Stock and stock will be maintained size and grade basis(e.g. Ingot100 X100 Grade A = 110 TO, Ingot 100X100 Grade B = 124 TO etc.).
    2.     Planning will be done at Ingot level.
    3.     Batch no will be used to track the heat number during GR of Billet.
    4.     There will be a BOM & Routing to produce Billet.
    5.     Size and grade will be determined during quality Inspection i.e. as per MIC (Carbon%, Phos%, Mn%,………etc) value.
    <b>SAP requirement:</b>
    1.     Planning Strategy for Ingot.
    2.     In which Stage production confirmation will be carried out.
    3.     Process mapping for saleable items.(Whether it’s necessary to open individual material code for each saleable items. If yes what will be the planning strategy for saleable items. But if no what will be the mapping)
    4.     Costing basis (at Ingot level or at saleable item level? If at saleable item level then what will be the cost components in between Ingot and saleable item level)
    Looking forward for any valuable suggestion.
    With Best Regards
    Soumya Das
    SAP PP-PS Consultant
    Kolkata
    Hello: +919755138074

    Basically I am FI/CO consultant and worked on CO implementation project. So based on my costing view ,I can give you some  rough Idea.
    1) As your planning is make to stock  , but still  does your production planning flows from your sales planning or not. In SAP you can  create your production planning either directly or from your sales planning.
    2) You can Plan your material down the bill of material also i.e
    at the raw material level level also. Technically each of your finished product might have standard BOM quantity and standard tak time (cycle time ) for each process which is defined in routing.So when BOM is exploded at the time of demand creation ,it explodes both your bill of material as well as your routing.Inshort if your FG  is made up of  X quantity of A and Y quanitity of B plus it goes machining activity of 5 minutes for each quantity produced . So If my production planning is of 1000 unit . Then after explosion it will plan
    1000X of A and 1000Y of B plus 5000 minutes machine time will ple planned.And based on production lead time,procurement lead time and available stock,and available capacity for production,it will schedule the production.
    3) Confirmation will be done again based on the requirement.If you want calculate WIP stock at each stage .Then it has to be confirmed at each stage to know the WIP stages. Plus at what process you do the quality inspection.In that case you have to confirm the process and then make the qc and then you have to start the new operation.
    4) Yes you have to open the seperate material code for the saleable material as well as semifinished material.Your SFG will also contain the BOM and routing
    5) Costing will be basically your raw material cost(which will come from bom),material overhead(come from costing sheet), Process cost(come from routing),manufacturing obverhead(come from costing sheet),administrative overhead(come from costing sheet) and sales and distribution overhead(come from costing sheet) depending on the costing requirement.
    Regards
    Sameer Kumar

  • 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<i>.trim())))
                   returnString = returnString +" "+ LKOND<i> +" "+ LKTEXT<i>;
                   result.addValue(returnString);                   
    catch(Exception e)
         e.printStackTrace();
    and the condition on the 'count' of QUALF (if = 2 then else)
    Thanks,
    Regards,
    Jamal

  • EDI file Mapping.. problem with UNT segment..!!

    Hi all,
    Anyone who worked on EDI files, pls help me..
    Doing Idoc to EDI scenario..
    I done for all the mapping for all the fields except for the UNT segment and field D_0074
    Here i need to provide no of segments in the EDI file...
    like
    *UNBUNOA:393777:ZZ93139:ZZ080108:09080+++1'
    UNH0000016334368DESADV:D:01B:UN:EAN007'
    BGM3510094147783+9'
    DTM+137:200801080934:203'
    DTM+11:200801080934:203'
    DTM+17:200801100000:203'
    ALI++168165'
    RFF+ON:R-08007E'
    DTM+171:20080107:102'
    NADSU377996::92'
    NADST9418GR::92'
    CPS1+5'
    PAC9+09::9'
    MEAPDAAA+KGM:6306.628'
    MEACTNPP+NAR:9' 
    CPS21+3'
    PAC109::9F:CHEP'
    MEAPDAAA+KGM:256.828'
    PCI+33E'
    GINAW393100471000832922'
    LIN1+19310047208023:SRV'
    QTY+12:44'
    DTM+36:20090505:102'
    CNT+2:2'
    UNT240000016334368'
    If you observe the above file which is my resultant file.. I need to count all the segments above UNT and pass the value( here total segments are 24) to D_0074 field .
    Is it any way we can count all the segments.. and pass the value??
    Kindly suggest me ..
    waiting for your replys..
    Regards
    Seema.

    Problem here is ..
    They have created only SCv  Seebutger_EDI_Adpater 
    but they haven't created for Seebutger_GENERIC_EDI ..
    all those mappings will be under Seebutger_GENERIC_EDI .. which they haven;t installed..
    thats the problem..
    If any one has that UDF .. kindly let me know..
    -Seema.

  • I have a scenario,  ECC-PI-Message broker. ECC sending IDOC to  PI, PI execute mapping and  sending data to Message borker.(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI  after mapping we need to save file in SAP fold

    I have a scenario,  ECC-PI-Message broker. ECC sending IDOC to  PI, PI execute mapping and  sends data to Message borker(thru JMS channel).(with almost one to one mapping)., IDOC(AAE)-PI-JMS. Now my requirement is., from PI  after mapping we need to create file with same data what ever send to Message broker and put the file in SAP folder without touching mapping. Is it possible? Please advise with the steps. We are using the ICO for this senario. Quick response is appriciated.

    Hi Pratik,
         http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/502991a2-45d9-2910-d99f-8aba5d79fb42?quicklink=index&overridelayout=true
    This link might help.
    regards
    Anupam

  • 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 Scenario. Acknowledgement help required

    Hi All,
    I have made a IDOC to file scenario  (IDOC has business system and file has business service) which is working fine.
    But In sxmb_moni of XI it says Acknowledgement not possible.
    "<SAP:Stack>Unable to convert the sender service File_Receiver_BusService to an ALE logical system</SAP:Stack>"
    Please explain me and send be blogs to send Acknowledgement back to R/3.
    Regards

    Hello Rick,
    "<SAP:Stack>Unable to convert the sender service File_Receiver_BusService to an ALE logical system</SAP:Stack>"
    Check the Logical system name in SLD and in ID's Service->AdapterSpecific Identifies matches are not, go through the following link for step by step prcedure.
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    https://wiki.sdn.sap.com/wiki/display/XI/Unable%20to%20convert%20Sender%20system%20to%20ALE%20logical%20system
    Check this for providing Acknowledgments.
    https://wiki.sdn.sap.com/wiki/display/ABAP/HandlingIdocAcknowledgements
    Regards,
    Prasanna

  • 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

Maybe you are looking for