Idoc to edifact

Hi all,
I need to convert an INVOIC2 idoc to an EDIFACT file format using SEEBURGER's VAN adapter.
Please help me out with the VAN adapter configuration.
When I search for the VAN adapter, the search results contain only the information about the VAN network (value added networks) but no info about the VAN adapter is available.
Please help me with this case.
Its very urgent.Also send me the ALE settings needed for the source IDOC both in XI and R/3.
thanks in Advance.

HI Rambabu,
I think I have given you the VAN adapter information and the configuration which needs to be done for the same.
Have you refer my thread which signifies the configuration for AS2 adapter you need to follow the same for the sender and receiver adapter.
Please go through the thread again It will help you.
Re: SEEBURGER's VAN Adapter
I have also given you the module name which needs to be put in the adapter module for the conversion.
See_X2E_INVOIC_UN_D96A
See_X2E_INVOIC_UN_D99A
IDOC configuration :
This is expalined both the scenarios:
Refer the help:
/people/swaroopa.vishwanath/blog/2007/01/22/ale-configuration-for-pushing-idocs-from-sap-to-xi - ALE settings for R3-XI
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/e07dcaa0-a92b-2a10-3a96-b3d942bd1539
Please follow the below process for configuration:
Pre-requisites for Inbound IDoc to R/3 from PI:
Configuration required at Xi side:
Go to IDX1: configure the port.
Go to IDX2: load the DOC metadata.
Go to SM59: Create RFC destination which points to R3 system this is require in the case where your IDOC is sent to R 3 system,
Configiration required at R3 side:
Maintain Logical System for PI (SALE transaction):
Maintain Partner Profile for XI system(WE20):
Pre-requisites for Outbound IDoc from R/3 to PI:
Configurations required in R/3:
Maintain Logical System (SALE)
Define RFC Destination (SM59) which points to PI system
Maintain Port (WE21)
Maintain partner profile. (WE20):
Maintain Distribution Model (BD64):
Thanks and Regards,
Chirag Gohil

Similar Messages

  • 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

  • Mapping iDoc to EDIFACT: Segment Count

    Hi experts,
    I am mapping a DELVRY05 iDoc to an EDIFACT DESADV document. Everythings fine so far, but I'm encountering troubles with filling the EDIFACT UNT Segment with the number of segments in the generated message.
    I am using the OPI2 conversion module and so I get a nice xml structure for the EDIFACT message. Is there a way to count created xml nodes? I think this would solve my issue.
    Thanks for your answers!

    That is an example for the source idoc
    <?xml version="1.0" encoding="UTF-8"?>
    <DELVRY05>
       <IDOC BEGIN="1">
          <EDI_DC40 SEGMENT="1">
             <TABNAM>EDI_DC40</TABNAM>
             <MANDT>100</MANDT>
             <DOCNUM>0000000002603007</DOCNUM>
             <DOCREL>700</DOCREL>
             <STATUS>30</STATUS>
             <DIRECT>1</DIRECT>
             <OUTMOD>2</OUTMOD>
             <IDOCTYP>DELVRY05</IDOCTYP>
             <MESTYP>DESADV</MESTYP>
             <SNDPOR>SAPKTS</SNDPOR>
             <SNDPRT>LS</SNDPRT>
             <SNDPRN>KTS100</SNDPRN>
             <RCVPOR>A000000016</RCVPOR>
             <RCVPRT>KU</RCVPRT>
             <RCVPFC>WE</RCVPFC>
             <RCVPRN>0004088156</RCVPRN>
             <CREDAT>20101123</CREDAT>
             <CRETIM>115322</CRETIM>
             <SERIAL>20101123115321</SERIAL>
          </EDI_DC40>
          <E1EDL20 SEGMENT="1">
             <VBELN>0080775647</VBELN>
             <VSTEL>0132</VSTEL>
             <VKORG>0130</VKORG>
             <LGNUM>132</LGNUM>
             <INCO1>EXW</INCO1>
             <INCO2>Leonding</INCO2>
             <ROUTE>009999</ROUTE>
             <VSBED>25</VSBED>
             <BTGEW>0.500</BTGEW>
             <NTGEW>0.500</NTGEW>
             <GEWEI>KGM</GEWEI>
             <VOLUM>0.000</VOLUM>
             <ANZPK>00000</ANZPK>
             <PODAT>20101123</PODAT>
             <POTIM>115321</POTIM>
             <E1EDL22 SEGMENT="1">
                <VSTEL_BEZ>Neuson Ersatzt.Linz II</VSTEL_BEZ>
                <VKORG_BEZ>Neuson Linz</VKORG_BEZ>
                <LGNUM_BEZ>LVS Neuson Linz Ersat. II</LGNUM_BEZ>
                <INCO1_BEZ>Ab Werk</INCO1_BEZ>
                <ROUTE_BEZ>NK Linz</ROUTE_BEZ>
                <VSBED_BEZ>Spedition</VSBED_BEZ>
             </E1EDL22>
             <E1EDL21 SEGMENT="1">
                <LFART>LF</LFART>
                <EXPKZ>X</EXPKZ>
                <LIFSK>10</LIFSK>
                <LPRIO>00</LPRIO>
                <KDGRP>02</KDGRP>
                <TRAGR>0100</TRAGR>
                <TRSPG>03</TRSPG>
                <E1EDL23 SEGMENT="1">
                   <LFART_BEZ>Auslieferung</LFART_BEZ>
                   <LIFSK_BEZ>zu verpacken</LIFSK_BEZ>
                   <KDGRP_BEZ>Handel</KDGRP_BEZ>
                   <TRAGR_BEZ>Transportgr. NK</TRAGR_BEZ>
                </E1EDL23>
             </E1EDL21>
             <E1EDL18 SEGMENT="1">
                <QUALF>ORI</QUALF>
             </E1EDL18>
             <E1ADRM1 SEGMENT="1">
                <PARTNER_Q>AG</PARTNER_Q>
                <PARTNER_ID>0004088156</PARTNER_ID>
                <LANGUAGE>EN</LANGUAGE>
                <FORMOFADDR>Firma</FORMOFADDR>
                <NAME1>Caterpillar Ltd.</NAME1>
                <STREET1>Peckleton Lane</STREET1>
                <POSTL_COD1>LE9 9JT</POSTL_COD1>
                <CITY1>Leicester</CITY1>
                <TELEPHONE1>14558258-00</TELEPHONE1>
                <COUNTRY1>GB</COUNTRY1>
             </E1ADRM1>
             <E1ADRM1 SEGMENT="1">
                <PARTNER_Q>SP</PARTNER_Q>
                <PARTNER_ID>0006006873</PARTNER_ID>
                <LANGUAGE>DE</LANGUAGE>
                <NAME1>DHL Express</NAME1>
                <STREET1>BleibtreustraÃu0178e 2</STREET1>
                <POSTL_COD1>1110</POSTL_COD1>
                <CITY1>Wien</CITY1>
                <TELEPHONE1>1 76600-3286</TELEPHONE1>
                <TELEFAX>1 76600-3475</TELEFAX>
                <COUNTRY1>AT</COUNTRY1>
                <REGION>W</REGION>
             </E1ADRM1>
             <E1ADRM1 SEGMENT="1">
                <PARTNER_Q>WE</PARTNER_Q>
                <PARTNER_ID>0004088156</PARTNER_ID>
                <LANGUAGE>EN</LANGUAGE>
                <FORMOFADDR>Firma</FORMOFADDR>
                <NAME1>Caterpillar Ltd.</NAME1>
                <STREET1>Peckleton Lane</STREET1>
                <POSTL_COD1>LE9 9JT</POSTL_COD1>
                <CITY1>Leicester</CITY1>
                <TELEPHONE1>14558258-00</TELEPHONE1>
                <COUNTRY1>GB</COUNTRY1>
             </E1ADRM1>
             <E1ADRM1 SEGMENT="1">
                <PARTNER_Q>OSP</PARTNER_Q>
                <PARTNER_ID>0132</PARTNER_ID>
                <LANGUAGE>DE</LANGUAGE>
                <NAME1>Neuson Ersatzt. Linz II</NAME1>
                <COUNTRY1>AT</COUNTRY1>
             </E1ADRM1>
             <E1ADRM1 SEGMENT="1">
                <PARTNER_Q>OSO</PARTNER_Q>
                <PARTNER_ID>0130</PARTNER_ID>
                <LANGUAGE>DE</LANGUAGE>
                <COUNTRY1>AT</COUNTRY1>
             </E1ADRM1>
             <E1EDT13 SEGMENT="1">
                <QUALF>006</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDT13 SEGMENT="1">
                <QUALF>003</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDT13 SEGMENT="1">
                <QUALF>001</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDT13 SEGMENT="1">
                <QUALF>007</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDT13 SEGMENT="1">
                <QUALF>010</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDT13 SEGMENT="1">
                <QUALF>015</QUALF>
                <NTANF>20101123</NTANF>
                <NTANZ>000000</NTANZ>
                <NTEND>20101123</NTEND>
                <NTENZ>000000</NTENZ>
                <ISDD>00000000</ISDD>
                <ISDZ>000000</ISDZ>
                <IEDD>00000000</IEDD>
                <IEDZ>000000</IEDZ>
             </E1EDT13>
             <E1EDL33 SEGMENT="1">
                <ALAND>AT</ALAND>
                <EXPVZ>3</EXPVZ>
                <IEVER>3</IEVER>
                <E1EDL34 SEGMENT="1">
                   <EXPVZ_BEZ>StraÃu0178enverkehr</EXPVZ_BEZ>
                   <IEVER_BEZ>StraÃu0178enverkehr</IEVER_BEZ>
                </E1EDL34>
             </E1EDL33>
             <E1EDL28 SEGMENT="1">
                <ROUTE>009999</ROUTE>
                <ROUID>NK LINZ</ROUID>
                <DISTZ>0.000</DISTZ>
                <E1EDL29 SEGMENT="1">
                   <ROUTE_BEZ>NK Linz</ROUTE_BEZ>
                </E1EDL29>
             </E1EDL28>
             <E1EDL24 SEGMENT="1">
                <POSNR>000010</POSNR>
                <MATNR>000000001000248477</MATNR>
                <MATWA>000000001000003928</MATWA>
                <ARKTX>PNEUMATIC SPRING</ARKTX>
                <ORKTX>Gasfeder 350N/L185/Hub64</ORKTX>
                <SUGRD>0001</SUGRD>
                <MATKL>000040900</MATKL>
                <WERKS>0131</WERKS>
                <LGORT>E002</LGORT>
                <LFIMG>1.000</LFIMG>
                <VRKME>ST</VRKME>
                <LGMNG>1.000</LGMNG>
                <MEINS>ST</MEINS>
                <NTGEW>0.500</NTGEW>
                <BRGEW>0.500</BRGEW>
                <GEWEI>KGM</GEWEI>
                <VOLUM>0.000</VOLUM>
                <LADGR>0131</LADGR>
                <TRAGR>0100</TRAGR>
                <VKBUR>0131</VKBUR>
                <VTWEG>02</VTWEG>
                <SPART>01</SPART>
                <GRKOR>000</GRKOR>
                <POSEX>000000</POSEX>
                <VFDAT>00000000</VFDAT>
                <EXPIRY_DATE_EXT>0</EXPIRY_DATE_EXT>
                <VGBEL>0001416863</VGBEL>
                <VGPOS>000020</VGPOS>
                <ORMNG>         1.000</ORMNG>
                <EXPIRY_DATE_EXT_B>0</EXPIRY_DATE_EXT_B>
                <E1EDL25 SEGMENT="1">
                   <LGORT_BEZ>Ersatzteill. 02</LGORT_BEZ>
                   <LADGR_BEZ>Neuson Ersatzteile</LADGR_BEZ>
                   <TRAGR_BEZ>Transportgr. NK</TRAGR_BEZ>
                   <VKBUR_BEZ>Neuson Ersatzteile</VKBUR_BEZ>
                   <VTWEG_BEZ>NK Ersatzteile</VTWEG_BEZ>
                   <SPART_BEZ>Produktsparte 01</SPART_BEZ>
                </E1EDL25>
                <E1EDL26 SEGMENT="1">
                   <PSTYV>ZERS</PSTYV>
                   <MATKL>000040900</MATKL>
                   <PRODH>409</PRODH>
                   <UMVKZ>1</UMVKZ>
                   <UMVKN>1</UMVKN>
                   <UEBTO>0.0</UEBTO>
                   <UNTTO>0.0</UNTTO>
                   <E1EDL27 SEGMENT="1">
                      <PSTYV_BEZ>Normalpos Ersatzteil</PSTYV_BEZ>
                      <MATKL_BEZ>Gasfeder</MATKL_BEZ>
                      <PRODH_BEZ>Gasfeder</PRODH_BEZ>
                      <WERKS_BEZ>Wacker Neuson Linz GmbH ET</WERKS_BEZ>
                   </E1EDL27>
                </E1EDL26>
                <E1EDL35 SEGMENT="1">
                   <STAWN>83024900</STAWN>
                   <EXPRF>10000</EXPRF>
                   <EXART>1</EXART>
                   <HERKL>FR</HERKL>
                   <GRWRT>          0.00</GRWRT>
                   <E1EDL36 SEGMENT="1">
                      <STXT1>Beschläge und ähnliche Waren, aus</STXT1>
                      <STXT2>unedlen Metallen, für anderweit nicht</STXT2>
                      <STXT3>genannte Zwecke (ausg. Scharniere, Lauf-</STXT3>
                      <STXT4>rädchen oder -rollen und Baubeschläge)</STXT4>
                      <EXPRF_BEZ>Ausfuhr o. voran. zollr. Best.</EXPRF_BEZ>
                      <EXART_BEZ>Kauf/Verkauf</EXART_BEZ>
                      <HERKL_BEZ>Frankreich</HERKL_BEZ>
                   </E1EDL36>
                </E1EDL35>
                <E1EDL43 SEGMENT="1">
                   <QUALF>C</QUALF>
                   <BELNR>0001416863</BELNR>
                   <POSNR>000020</POSNR>
                   <DATUM>20101123</DATUM>
                </E1EDL43>
                <E1EDL41 SEGMENT="1">
                   <QUALI>001</QUALI>
                   <BSTNR>TEST FAH</BSTNR>
                   <BSTDT>20101123</BSTDT>
                </E1EDL41>
             </E1EDL24>
          </E1EDL20>
       </IDOC>
    </DELVRY05>
    and thats what for the moment is the output for the EDIFACT before OPI2 conversion module. UNT segment count is hardcoded set to 1.
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:EDIFACTMessage xmlns:ns0="http://cbsgmbh.com/xi/EDIFACT/99A">
       <Header>
          <SenderID>Test_SenderSystem</SenderID>
          <ReceiverID>Test_ReceiverSystem</ReceiverID>
          <MessageType>EDIFACTMessage</MessageType>
       </Header>
       <ListOfDespatchAdvises>
          <DespatchAdvise>
             <HEADING>
                <UNH>
                   <UNH01>0000000002603007</UNH01>
                   <UNH02>
                      <S00901>DESADV</S00901>
                      <S00902>D</S00902>
                      <S00903>98B</S00903>
                      <S00904>UN</S00904>
                   </UNH02>
                </UNH>
                <BGM>
                   <BGM01>
                      <C00201>351</C00201>
                   </BGM01>
                   <BGM02>
                      <C10601>0000000002603007</C10601>
                   </BGM02>
                   <BGM03>9</BGM03>
                </BGM>
                <DTM>
                   <DTM01>
                      <C50701>11</C50701>
                      <C50702>00201011230000</C50702>
                   </DTM01>
                </DTM>
                <DTM>
                   <DTM01>
                      <C50701>132</C50701>
                      <C50702>00201011230000</C50702>
                   </DTM01>
                </DTM>
                <DTM>
                   <DTM01>
                      <C50701>137</C50701>
                      <C50702>00201011230000</C50702>
                   </DTM01>
                </DTM>
                <MEA>
                   <MEA01>PD</MEA01>
                   <MEA02>
                      <C50201>G</C50201>
                   </MEA02>
                   <MEA03>
                      <C17401>KGM</C17401>
                      <C17402>0.500</C17402>
                   </MEA03>
                </MEA>
                <MEA>
                   <MEA01>PD</MEA01>
                   <MEA02>
                      <C50201>N</C50201>
                   </MEA02>
                   <MEA03>
                      <C17401>KGM</C17401>
                      <C17402>0.500</C17402>
                   </MEA03>
                </MEA>
                <MEA>
                   <MEA01>PD</MEA01>
                   <MEA02>
                      <C50201>WT</C50201>
                   </MEA02>
                   <MEA03>
                      <C17401>KGM</C17401>
                      <C17402>0.500</C17402>
                   </MEA03>
                </MEA>
             </HEADING>
             <DETAIL>
                <CPS>
                   <CPS01>1</CPS01>
                   <CPS03>3</CPS03>
                </CPS>
                <SG16>
                   <LIN>
                      <LIN02>000010</LIN02>
                   </LIN>
                   <PIA>
                      <PIA01>1</PIA01>
                      <PIA02>
                         <C21201>0001416863</C21201>
                         <C21202>PO</C21202>
                      </PIA02>
                   </PIA>
                   <PIA>
                      <PIA01>1</PIA01>
                      <PIA02>
                         <C21201>000020</C21201>
                         <C21202>PL</C21202>
                      </PIA02>
                   </PIA>
                   <PIA>
                      <PIA01>1</PIA01>
                      <PIA02>
                         <C21201>TEST FAH</C21201>
                         <C21202>ON</C21202>
                      </PIA02>
                   </PIA>
                </SG16>
             </DETAIL>
             <SUMMARY>
                <UNT>
                   <UNT01>1</UNT01>
                   <UNT02>0000000002603007</UNT02>
                </UNT>
             </SUMMARY>
          </DespatchAdvise>
       </ListOfDespatchAdvises>
    </ns0:EDIFACTMessage>

  • Converting INVOIC02 idoc to EDIFACT INVOIC message (Using Adapter Module

    Hi Friends,
    We are sending customer idoc (INVOIC02) from R/3 to external system through PI. We want to generate EDIFACT output file (message type : INVOIC).
    Is it possible to convert IDoc message to EDI file format through java adapter module ? Will adapter module support this  without using Seeburger adapter ?
    kindly clarify, friends.
    Kind regards,
    Jegathees P.

    There is an alternative to Seeburger.
    DataDirect also has complete EDI-XML conversion by way of deploying a module which is called from an adapter. The range of parameters with the conversion is also quite extensive, allowing tolerance for partners who may have included non-standard EDI qualifiers and such.  The XML tags make for easier mapping.  StylusStudio XML Suite includes the EDI<->XML adapter so you can try the conversions each way directly in that package.  If you are happy with it, you need to then purchase the package from DataDirect.  We did this and implemented EDI for X12 and EDIfact, including Orders and Invoices and some other messages.  The communications part was not included.  We wrote the EDI files and used a separate process to actually send and receive the files. The IDoc <-> EDI mapping  was done using the normal graphical mapping of SAP PI. The Stylus Studio package includes the functionality to generate the XSD, which we imported to SAP PI.

  • Conversion of  idoc into edifact/xml

    Hi everyone is it possible for us to convert our idoc into xml/edifact without using any adapter like seaburger.  reply me
    when you feel free.
    Thanks & Regards
    Vimarsh

    Try Function module IDOCS_OUTPUT_IN_XML_FORMAT

  • Converting Idoc to Edifact on Business Connector 4.8

    Is there any possibility to convert idoc INVOIC messages into standard EDI format (Edifact D96A) on Business Connector 4.8 without using adapter ?

    I think you would be required to use either an adapter or a custom module to do the conversion. BC or for that matter, no integration tool has the capability to do the conversion on it's own ... it will require "something" to do that conversion.

  • UNT segment generation in Idoc to EDIFACT mapping

    Hi Experts,
    I have gone through many blogs and found some of the solution.
    1) Mapping through count function, which is not working as per my understanding.
    2) Confuguration through seeburger workbench, but since we are having SAP PO 7.4 so seeburger is replaced by B2B Toolkit so this solution cannot be considered.
    The mapping is as per the snapshot :-
    UNT : 0074 - Number of Segmets in(Quantity of segments in the message) Calculated.
    Please suggest the appropriate solution, we are using SAP PO 7.4 so it would be better if we can do anthing in the mapping than configuration part.
    Thanks in advance for your valuable inputs.
    Thanks,
    Nidhi

    Hi Dimitri,
    I tried doing that but I am not able to get the result as "1" in the output if I am putting constant 1 in the UNT and UNZ segment fields.
    Output:-
    Have I done the correct settings? Is anything else need to be done?
    Please guide.
    Thanks,
    Nidhi

  • B2B in PI 7.0 - EDIFACT format to IDOC and vice versa

    We need to establish B2B scenario in PI 7.0
    IDOC to EDIFACT and EDIFACT to IDOC.
    Please let me know the solution without using any third party adapter like seeburger.
    Any example scenario of the same case will be helpful

    Hi ,
    If you are decided to not using SeeBurger then its difficult to implement B2B Scenario
    Your requirement IDOC 2 EDIFACT or Vice VERSA, you have to do more analyzation about EDIFACT.
    You can acheive using Adapter module, you have to about EJB's stuff to write Adapter module to support EDIFACT Message, Search for info about Adapter Module in SDN you wil find some lot off stuff about Adapter MODULE.
    then coming to mapping its really challenging to do Mapping between IDOC TO EDIFACT.
    You have to alalyze the EDIFACT Structure .
    I implemented B2B scebario in my project SeeBurger.
    Regards,
    Raj

  • ??? EDI Multipartner Integration with Idoc- EDIFACT X.400P7 ???

    Hi all,
    can somebody please give me an idea of how to build a EDI-scenario on XI with X.400 adapter to connect 3000 customers?
    My actual point is, that I have the SAP system sent idocs, that need to me mapped to EDIFACT messages - D99B Invoice (12 different mappings - customerdependend) and then be sent via X.400 to the MTA.  How can I have the Customernumber from the Idoc set the identifier in my receiver X.400 channel, which defines the receiver adress dynamically - without building 3000 Parties, Business Services and Channels?
    Has one of you allready build something like that?
    Thanks in advance..
    Daniel

    Hi Leonardo,
    The Seeburger adapter license is based on data volumes through the adapter, plus a fixed percentage as maintenance costs.
    If you are using Seeburger, they will have some ready maps developed between the IDOC and EDIFACT messages.
    Cheers
    Manish

  • OPI2 EDIFACT adapter - Module Exception Error

    Hi,
    We are on pI 7.0. Deployed open source custom EDI adapter (OPI2).
    Scenario: IDOC - - - xi -- - EDIFACT
    When I executed the scenario, I get the following error in comm channel monitoring.
    2010-10-14 14:19:52 Success Message successfully received by messaging system. Profile: XI URL: http://xidev:50000/MessagingSystem/receive/AFW/XI Credential (User): PIISUSER
    2010-10-14 14:19:52 Success Using connection EDIFACT_http://cbsgmbh.com/xi/EDIFACT/Adapter. Trying to put the message into the receive queue.
    2010-10-14 14:19:52 Success Message successfully put into the queue.
    2010-10-14 14:19:52 Success The message was successfully retrieved from the receive queue.
    2010-10-14 14:19:52 Success The message status set to DLNG.
    2010-10-14 14:19:52 Success Delivering to channel: CC_EDIFACT_Orders_recv
    2010-10-14 14:19:52 Success MP: Entering module processor
    2010-10-14 14:19:52 Success MP: Processing local module localejbs/opi2/edifact/CryptModule
    2010-10-14 14:19:52 Error MP: Exception caught with cause com.sap.aii.af.mp.module.ModuleException caused by: java.lang.NullPointerException
    2010-10-14 14:19:52 Error Exception caught by adapter framework: null
    Please help,
    mk

    Hi,
    I have removed "CRYPT" module from communication channel modules list since I am not using any encryption at this time. However, I get different error as below.
    MP: Exception caught with cause com.sap.aii.af.mp.module.ModuleException: Configuration lookup failed caused by: com.sap.aii.af.mp.module.ModuleException: Address normalization (alternativeID) is not defined for : agency = UNB  ZZZ  117, schema = UNBID, partyId = EDI_ATMEL
    Note: I have maintained AS2 ZZZ 117, AS2ID in both sender party & receiver party identifiers. Also, I have referred sender party and sender business system in receiver agreement header mapping.
    Please help,
    MK

  • Correlating AS2 MDN to Original IDoc?

    Hi All -
    I have got the following scenario:
    1) Backend system (ECC) sends IDoc to SAP PI.
    2) SAP PI maps IDoc to EDIFACT message and sends via AS2 to B2B Partner.
    3) B2B Partner sends back AS2 MDN to acknowledge receiving of AS2 message.
    __Question:__
    How can I now correlate the AS2 MDN to the original IDoc and so forward the acknowledgement to the Backend system?
    I was thinking to use the 'Correlation ID' which is contained in the AS2 MDN and is the same ID as the original SAP PI message.
    However, how do I practically retrieve the IDoc number (part of original IDoc message and used as identifier in the ECC system) from the persisted messages of SAP PI?
    Can I code an ABAP or JAVA program which is than called within a mapping to query the persisted messages and give back the correlating IDoc number?
    Are there other ways to achieve this?
    Thanks for your inputs.
    Best Regards, Mathias.

    Hi Mathias,
    Approach1:
    I would definately not consider using BPM overhead on a high volume scenario. As the Output file(that will be generated) will be a simple XML message with just the data required for corelating with the MDN. All MDN's are expected to received within 1 min or less than 5 min.(B'cos it is a System level Acknowledgement), Hence if the BPM is not closed within the specified time period(1min or 5 min), raise an exception.
    The Corelation file that will be generated can look like
    <MDN_Corr>
       <SenderAS1ID>        --> Will be used for Corelating the MDN
       <ReceiverAS2ID>      --> Will be used for Corelating the MDN
       <TimeStamp>
       <IDOCNumber>
       <EDI_ISA_Control_No> --> Will be used for Corelating the MDN
       <EDI_Message_Type> 
    </MDN_Corr>
    Approach2:
    It might be very resource intensive to perform payload search. (and in some cases, the messages are archived, hence might result in bad search). Hence, you can have Z-Table all the fields as mentioned in the XML message. 1:1 mapping b/n EDI_ISA control number & IDOC_Number will be your lookup key-value params
    -SM

  • Please help me in understanding the EDIFACT D96A format for INVOICE

    Hi,
    Im doing an INVOICE02 IDOC to EDIFACT D96A INVOIC scenario. Im new to EDI.
    Pls Pls Pls Pls kindly help me in understanding the following EDIFACT D96A file. 
    UNBUNOA:35410033000055:145400110000009:14070612:085511137INV96A+EANCOM1'                                        
    UNH1INVOIC:D:96A:UN:EAN008'                                        
    BGM3805010237529+9'                                        
    DTM+137:200706120000:203'                                        
    DTM+35:20070612:102'                                        
    DTM+454:20070612:102'                                        
    RFF+ON:32210'                                        
    DTM+171:20070612:102'                                        
    RFF+DQ:000030585715'                                        
    DTM+171:20070612:102'                                        
    NADSU5410148000001::9+BVBA Unilever Belgium SPRLBl.De L?'Humanité 292 292Bruxelles1190BE'                                        
    RFF+VA:BE438390312'                                        
    RFF+ARA:0438390312'                                        
    NADBY5400110000009::9+D.L.L.RUE OSSEGHEM 53-MOLENBEEKMOLENBEEK-SAINT-JEAN1080BE'                                        
    NADDP5400110000009::9+D.L.L.RUE OSSEGHEM 53-MOLENBEEKMOLENBEEK-SAINT-JEAN1080BE'                                        
    NADIV5400110000009::9+DELHAIZE FRS. CENTRALESRUE OSSEGHEM , 53BRUSSEL-MOLENBEEK1080BE'                                        
    RFF+VA:BE402206045'                                        
    RFF+ARA:0402206045'                                        
    CUX+2:EUR:4'                                        
    LIN10+8000920900987:EN'                                        
    PIA1000000000019009801:SA'                                        
    IMDF+IN:::IGLO POELEE LEGUMES CHAMPIGNONS 6X8'                                        
    QTY+47:81'                                        
    QTY+46:81'                                        
    MOA+203:1584.4'                                        
    PRI+AAA:19.56'                                        
    PRI+AAB:21.24'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:1584.4'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    ALCA++1'                                        
    PCD+1:1.96:1'                                        
    LIN20+5410148126459:EN'                                        
    PIA1000000000011264501:SA'                                        
    IMDF+IN:::Epinards hachis en portions '                                        
    QTY+47:112'                                        
    QTY+46:112'                                        
    MOA+203:1061.01'                                        
    PRI+AAA:9.47'                                        
    PRI+AAB:10.96'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:1061.01'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    ALCA++1'                                        
    PCD+1:1.96:1'                                        
    LIN40+5410148013452:EN'                                        
    PIA1000000000010134500:SA'                                        
    IMDF+IN:::15 Fish Sticks Colin d?'Alaska '                                        
    QTY+47:256'                                        
    QTY+46:256'                                        
    MOA+203:4937.63'                                        
    PRI+AAA:19.29'                                        
    PRI+AAB:20.16'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:4937.63'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    LIN50+5414807999958:EN'                                        
    PIA1000000000019999501:SA'                                        
    IMDF+IN:::Iglo Poisson Pané Epinards 7X400g'                                        
    QTY+47:180'                                        
    QTY+46:180'                                        
    MOA+203:4160.31'                                        
    PRI+AAA:23.11'                                        
    PRI+AAB:24.08'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:4160.31'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    LIN60+5410148120952:EN'                                        
    PIA1000000000011209501:SA'                                        
    IMDF+IN:::Epinards Crhme en Portions '                                        
    QTY+47:112'                                        
    QTY+46:112'                                        
    MOA+203:1594.69'                                        
    PRI+AAA:14.24'                                        
    PRI+AAB:15.92'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:1594.69'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    ALCA++1'                                        
    PCD+1:1.96:1'                                        
    LIN70+5410148124158:EN'                                        
    PIA1000000000011241503:SA'                                        
    IMDF+IN:::EPINARDS HACHES EN PORTIONS 450G'                                        
    QTY+47:144'                                        
    QTY+46:144'                                        
    MOA+203:938.01'                                        
    PRI+AAA:6.51'                                        
    PRI+AAB:7.44'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:938.01'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    ALCA++1'                                        
    PCD+1:1.96:1'                                        
    LIN120+5410148016729:EN'                                        
    PIA1000000000010167201:SA'                                        
    IMDF+IN:::Macaroni Fromage/Jambon '                                        
    QTY+47:260'                                        
    QTY+46:260'                                        
    MOA+203:4337.55'                                        
    PRI+AAA:16.68'                                        
    PRI+AAB:17.58'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:4337.55'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    LIN130+5410148441255:EN'                                        
    PIA1000000000014412503:SA'                                        
    IMDF+IN:::CHOUX ROUGES AUX POMMES 450G'                                        
    QTY+47:144'                                        
    QTY+46:144'                                        
    MOA+203:1756.99'                                        
    PRI+AAA:12.2'                                        
    PRI+AAB:13.36'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:1756.99'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    ALCA++1'                                        
    PCD+1:1.96:1'                                        
    LIN140+5410148017702:EN'                                        
    PIA1000000000010177001:SA'                                        
    IMDF+IN:::Frit?'Kot 1'                                        
    QTY+47:60'                                        
    QTY+46:60'                                        
    MOA+203:1102.6'                                        
    PRI+AAA:18.38'                                        
    PRI+AAB:22'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:1102.6'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    ALCA++1'                                        
    PCD+1:4.9:1'                                        
    LIN180+8000920801796:EN'                                        
    PIA1000000000018017901:SA'                                        
    IMDF+IN:::EPINARDS EN BRANCHES 10 X 450'                                        
    QTY+47:190'                                        
    QTY+46:190'                                        
    MOA+203:2204.2'                                        
    PRI+AAA:11.6'                                        
    PRI+AAB:12.9'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:2204.2'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    ALCA++1'                                        
    PCD+1:1.96:1'                                        
    LIN200+5410148014268:EN'                                        
    PIA1000000000010142602:SA'                                        
    IMDF+IN:::PETITS POIS EXTRA FINS 450G'                                        
    QTY+47:238'                                        
    QTY+46:238'                                        
    MOA+203:1999.6'                                        
    PRI+AAA:8.4'                                        
    PRI+AAB:9.24'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:1999.6'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    ALCA++1'                                        
    PCD+1:1.96:1'                                        
    LIN230+8000920807248:EN'                                        
    PIA1000000000018072403:SA'                                        
    IMDF+IN:::IGLO POUL ET PENNE AUX LEG.SOLEI. 6'                                        
    QTY+47:99'                                        
    QTY+46:99'                                        
    MOA+203:1727.54'                                        
    PRI+AAA:17.45'                                        
    PRI+AAB:18.3'                                        
    TAX7VAT+++:::6.000'                                        
    MOA+125:1727.54'                                        
    ALCA++1'                                        
    PCD+1:0:1'                                        
    ALCA++1'                                        
    PCD+1:1.97:1'                                        
    UNS+S'                                        
    CNT+2:12'                                        
    MOA+124:1644.27'                                        
    MOA+86:29048.8'                                        
    MOA+79:27404.53'                                        
    MOA+125:27404.53'                                        
    TAX7VAT++:::6.000S'                                        
    MOA+125:27404.50'                                        
    MOA+124:1644.27'                                        
    UNT2121'                                        
    UNZ111137'
    Advance appreciations,
    Ram.

    Its very simple:
    UNB-segment : Interchange Header
    S001     SYNTAX IDENTIFIER
    0001     Syntax Identifier                    “UNOA”
    0002     Syntax version number               “2”
    S002     INTERCHANGE RECIPIENT
    0004     Sender Identification                    “8711382000091”  (= GLN Code Tilburg)     
    0007     Identification Code Qualifier               “14”
    S003     INTERCHANGE SENDER
    0004     Recipient Identification               “8711700400008”(= GLN Code Unilever)
    0007     Identification Code Qualifier               “14”
    S004     DATE/TIME OF PREPARATION
    0017     Date                            YYMMDD
    0019     Time                            HHMM
    0020     INTERCHANGE CTRL REF.     Unique message reference number
    0026     APPLICATION REFERENCE          “WMS0330”
    UNH-segment: Message header
    0062     MESSAGE REFERENCE NUMBER      Unique sequence numbe within UNB
    S009     MESSAGE IDENTIFIER
    0065     Message type     identifier               “INVRPT”
    0052     Message type version number               “D”
    0054     Message type release number               “96A”
    0051     Controlling agency                    “EN”
    0057     Association assigned code               “EAN004”
    BGM-segment: Beginning of message
    C002     DOCUMENT/MESSAGE NAME
    1001     Document/message name, coded  35”     (= Inventory report)
    3055     Code list responsible agency, coded     “9”     (= EAN)
    1004     DOCUMENT/MESSAGE NUMBER     Unique Number assigned by CS (= Date/Time CCYYMMDDHHMMSS)
    1225     MESSAGE FUNCTION, CODED          “9”     (= Original)
    DTM-segment: Date/time/period
    C507     DATE/TIME/PERIOD
    2005     Date/time/period qualifier 137”     (=Document/message date/time)
    2380     Date/time/period     Document date
    2379     Date/time/period format qualifier     “102”     (= CCYYMMDD)
    RFF-segment: Reference
    C506     REFERENCE
    1153     Reference code qualifier “ON”     (= Order number)
    1154     Reference identifier     Agreement number
    NAD-segment: Name and address
    3035     PARTY QUALIFIER     “GY”     (= Inventory reporting party = CS)
                   “GM”     (= Inventory controller = XYZ)
    C082     PARTY IDENTIFICATION DETAILS
    3039     Party id. identification          GLN code
    3055     Code list responsible agency, coded     “9”     (= EAN)
    LIN-segment: Line item
    1082     LINE ITEM NUMBER               Unique Line Number
    C212     ITEM NUMBER IDENTIFICATION
    7140     Item number               EAN Material code
    7143     Item number type, coded          “EN”     (= EAN)
    PIA-segment: Additional Product Information
    4347     PRODUCT ID FUNCTION IDENTIFIER     "1"(= Additional Information)
    C212     ITEM NUMBER IDENTIFICATION
    7140     Item number          Promotional Variant
    7143     Item number type, coded     "PV”     (= Promotional variant)
    QTY-segment: Quantity
    C186     QUANTITY DETAILS
    6063     Quantity qualifier     “12”      (= Despatch quantity)
    6060     Quantity           Number of stock units
    PRI: Represent price
    TAX: represent tax.
    Try to go to the below website where you will able to get the information regarding all the sgements and elements of Invocie.
    http://www.edifactory.de/messages.php?s=D96A
    Also refer the below link for EDI understanding:
    http://www.gxs.com/pdfs/Tutorial/Tutor_EDIFACT_GXS.pdf
    Thnx
    Chirag Gohil

  • Need EDIFACT "DESADV" XSD Schema

    Hi,
    I need to map ASN IDOC (DELVRY) from SAP to EDI transaction type "DESADV". I need to import XSD for DESADV for mapping.
    Please help where I can find/download XSD schema for "DESADV".
    Thank you for your help,
    MK

    Hi Mallick,
    What i understand from your requirement is that you are working in IDOC to EDIFACT file scenario. Correct me if i am wrong?
    I am assuming you are using Seeburger to achieve this
    Well when you install seeburger for any EDIFACT scenario it will give you 3 standard files: 2 xml and 1 xsd.
    what you have to do, import the .xsd file in your Integration repository as target (if it is IDOC to EDI file scenario) and also import the IDOC (DELVRY) in your source and do 1:1 Pi mapping.
    After that in BIC mapper you have to import XML files and create a X2E mapping(here X2E means xml to edi mapping) and later on you have to use this mapping name in your file adapter.
    Note: BIC mapper is used to convert XML to EDI and vice versa.
    Hope this information is helpful
    Regards,
    Shradha
    Edited by: Shradha_thapliyal29 on Oct 11, 2010 8:52 AM
    Edited by: Shradha_thapliyal29 on Oct 11, 2010 8:53 AM

  • Remove Empty XML Tags using module parameters

    Hi All,
    In my lanscape I have two PI Systems.
    My scenario is an IDOC reaches 1st PI system gets converted into an EDIFACT and then goes to the 2nd PI and from there it gets routed to the respective AS2 Party.
    I am using SOAP to pass message between the PI systems and B2B Toolkit's AS2 Adapter for the communication with AS2 party.
    The issue is when the message is getting converted from IDOC to EDIFACT there are a few feilds with occurence 1..1 and due to these fields i get an empty XML tag at the output. These empty XML tags give me an error in the B2B Toolkit's AS2 Adapter Receiver Channel
    I cannot change the occurence in the structure of the EDIFACT nor can I use an XSLT mapping to remove empty tags before the message reaches the Communication Channel.
    I want to know if there are any module parameters which i can use either in SOAP Channel or the AS2 Channel to remove the XML Tags.

    Hi Muni,
    "1..1 means, you must send some values for that fields. try to find out why these are not getting any values."
    This empty tag is expected. Before using B2B Toolkit's AS2 Adapter we used to use Seeburger's AS2 Adpater and the message used to get executed successfully with these empty tags.The issue is coming only when we are using B2B Toolkit's AS2 Adapter.
    "if you want to stop sending(the fields which are not needed in target) you can you can disable the fields in the message mapping."
    I cannot disable the feild in the mapping as some other message may use this field.
    Thanks,
    Farhaan

  • BIC integration tool

    Going to support EDI interface which uses Seeburger AS2 adapter either at sender or receiver side.I have few doubts on BIC module:
    1.Do i need to install BIC tool on my laptop or it is a web based tool which i can access from seeburger workbench?
    2.For all the edi conversion using Seeburger do we need BIC module to convert messages from EDI to XML or from XML to EDI?
    3.why we need to do message mapping again if we had already done BIC mapping?
    thanks in advance.

    Got to the point answer from Shradha, Posting this thread again becouse earlier posted with differen used by mistake.
    Hi,
    1.Do i need to install BIC tool on my laptop or it is a web based tool which i can access from seeburger workbench?
    Yes you need to install BIC mapping tool in your laptop to do the mappings.
    AM Plain Text Help 
    2.For all the edi conversion using Seeburger do we need BIC module to convert messages from EDI to XML or from XML to EDI?
    Yes for all EDI conversion using Seeburger you need BIC tool. But if you have some standard mapping already given by Seeburger than you dont need BIC tool, you can directly use those mappings. Remember standard mapping will start with name SEE*
    3.why we need to do message mapping again if we had already done BIC mapping?
    BIC mapping tool is used to convert EDI to XML and vice versa. Think about a scenario when you need to convert an IDOC to EDIFACT format.
    Than first you have to do 1:1 mapping in PI where you will convert IDOC to EDIXML and than use BIC mapping tool to convert EDIXML to EDIFACT file.
    I hope above answers will help you.
    Regards,
    Shradha

Maybe you are looking for