IDOC--PI--SEEBURGER

Hi Experts,
we are sending orders IDOC to seeburger through PI. The format on receiver side is XCBL the adapter I am using is AS2(receiver) so I want to clarify onething
In the content type parameter i gave application/xcbl (for ex when we use edifact we gve as application/edifact).Is I am giving the correct content type in AS2 ADAPTER?
In the module tab in module configuration I gave paramter value as See_X2E_XCBL_Order_Def( for ex if it is edifact we gve as See_X2E_ORDERS_UN_D01B). Is I am giving the correct parameter value?
when i am sending file i am getting below error.
SEEBURGER BICXIADAPTER --- CONVERSION ERROR ---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping: See_X2E_XCBL_Order_Def you are trying to load cannot be found in the classpath! Maybe you forgot to compile or to activate the mapping! DESCRIPTION: BICMapping Error: The mapping [not specified] you are trying to load cannot be found in the right path! Maybe you forgot to compile or to activate the mapping!
As I said in the example if I keep like that I am getting the below error
SEEBURGER BICXIADAPTER --- CONVERSION ERROR ---Error: [Error:ID=2099;LEVEL=1] InhouseDocReader doSyntaxCheck(): offset[122]: the found segment Order is not in the message description. DESCRIPTION: InhouseDocReader Error: The Segment Order is missing in the message description. Check your file.
Can anyone please help me where I am doing rong.

You are making many conceptual mistakes
>>So now one of our supplier(procurement scenario) want us to send in XCBL format.
So my interface is like IDOC(ORDERS>PI>SEEBURGER)
Here you only want to use Seeburger AS2 adapter. This doesn't mean the use of module is mandatory.
>>So I am confused what i need to specify in receiver AS2 adapter in parameter content type and in module cofig what name i need to give for mapping
As I said earlier, you don't need Any module. So simply remove Seeburger modules from module chain.
>>as i said earlier mapping name for EDIFACT was See_X2E_ORDER_UN_D01B which is external defination name ORDER_UN_D01B
There is no connection between External Definition name and mapping name. It was just a coincidence that these names were similar. The name of mapping used depends upon what is deployed on server.
>>When I provided with XCBL_Order_Def which is external def name it is givng mapping error
It will give error because as I said 1. You don't need mapping and 2. the name of mapping was not deployed on PI and has no connection with ED.
>>l our procurement scenarios was using this since 3yrs but all these inteface were with http but now it is seeburger
When using HTTP, check the module chain of HTTP channel, it will be empty. Similarly, you have to keep module chain of your AS2 channel empty. Just concentrate on other AS2 parameters. You DONT NEED ANY MODULE.
Regards,
Prateek Raj Srivastava

Similar Messages

  • How to import the IDOC into Seeburger BIC mapping designer

    Hi All,
    Can u please tell me how to import the IDOC into Seeburger BIC mapping desginer.
    I have scenario My scenario is SAP GTS 7.0.....>Seeburger BIS.....>Atlas customs system for Germany
    Idoc coming from SAP GTS to Seeburger BIS and then convert to EDIFACT send
    to Atlas systeam.
    Regards,
    Ramesh.

    Hi Ramesh
    BIC is a tool from Seeburger to transmit the XML data to EDI and EDI to XML.
    Seeburger mapping programs for transferring the XML data to EDI data and EDI data to XML data, but not for the structure changing, in the IR your mapping program is same.
    Receiver side you need AS2 Adapter for converting data to EDI target structure. we have many EDI versions are available, for converting the EDI to XML or vice versa AS2 gives some default mapping programs, xml to EDI or EDI to XML convertion done through this mapping programs.
    Seeburger AS adapter provider provides some mapping programs(for example EDI4010 version or other), if you are using the same EDI version(4010) then you can use that mapping programs, if the version is different then we can manually generate the Seeburger X2E and E2X mappings for the corresponding version and signal(850 or 810 or ..), for this seeburger provides the mapping designer tool (BIC), there we can develope the X2E and E2X mapping programs and configure this in the Seeburger work bench.
    Regards
    Ramesh

  • Seeburger help required for 810 and Dispatch Advice (IDOC type DESADV).

    Hi All,
    1. Please let me know blogs which clearly shows settings for Seeburger components for 850 (Purchase Order) to IDOC Scenario
    --- Seeburger Workbench
    --- Seeburger Mapping Designer (BIC)
    --- Seeburger Counter and Varaibles
    --- Seeburger AS2 Spoke
    --- Any other Seeburger Component setting required
    I have understand blog for 850 -- /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
    2. Anybody has blog for 810 or Dispatch Advice (IDOC type DESADV).
    3. Can anybody provide me Mapping Logic (at field level) done in XI/PI for 850, 810 , Dispatch Advice (IDOC type DESADV) .
    Regards

    Hi Rickkk,
    1. Please let me know blogs which clearly shows settings for Seeburger components for 850 (Purchase Order) to IDOC Scenario
    --- Seeburger Workbench
    --- Seeburger Mapping Designer (BIC)
    --- Seeburger Counter and Varaibles
    --- Seeburger AS2 Spoke
    --- Any other Seeburger Component setting required
    For SEEBURGER workbench please go through this blog and navigate the enbebbed links furthur to know about Seeburger workbench too.
    /people/prateek.srivastava3/blog/2009/08/01/seeburger--part-1--the-basics
    2
    2. Anybody has blog for 810 or Dispatch Advice (IDOC type DESADV).
    For 810 i think the procedure would be the same but themseeburger mapping program that validates the ANSX 810 would be different.As far as 997is concerned 997 is a functional acknowledgement.Its a genric format that is used to send acknowledgement for any EDI transaction set that has been sent.
    3. Can anybody provide me Mapping Logic (at field level) done in XI/PI for 850, 810 , Dispatch Advice (IDOC type DESADV) .
      The logic will be based on the trading partner guidelines which will contain the description of all the semantic and syntactiic description about the segments ,its feilds.we need to consider the guidelines and target side specifications too while mapping.
    Thanks,
    Ram.

  • Seeburger problem for Custom Mappings..!!!

    Hi All,
    File to Idoc using seeburger adapters(BIc & split)
    When I use standard mapping (Which starts with See_.. )in seeburger splitter configuration, ,the scenario is working perfectly.The idoc is posting in R/3 and Funcack is sending to Partner.
    But When I do for customised mappings (Like the ones which we will develop in BIC and deploy into XI and we will use the mapping name like E2X_DT_INVOICE).. then its not working.
    I tried by keeping custom mappings (E2X_DT_ORDERS) in splitter configuration. But it didn’t work.. !!
    Can anyone please tell the changes what I need to do in the modules or in splitter configuration..??
    Here is the Module parameters which i mentioned in sender File adapter.
    localejbs/SeeClassifier            C
    localejbs/CallBicXIRaBean   BIC
    localejbs/Seeburger/MessageSplitter   S
    C         attID                classifierAtt
    C         destSourceMsg        MainDocument
    C         showInAuditLog       true
    BIC       classifierAttID          classifierAtt
    BIC       destSourceMsg       MainDocument
    BIC       destTargetMsg         MainDocument
    BIC       mappingName           AUTO
    BIC       split                          true 
    1. mappingName I kept as “AUTO” for standard mappings..
    I need to change anything here for Custom Mappings???
    2. I didn’t mention anything here in split adapter in modules.
    Did I need to mention anything here when we do for custom mappings??
    Kindly let me know anyone has idea on this.
    Thanks&Regards
    Seema.

    You will also have to create this mapping on the BIC site.
    check the documentation on the classifier and functional acknowledgements
    Seeburger Classifier with customer mappings.
    In the manual Functional Acknowledgement For SAP XI3.0, Configuration Guide this is described. I add a description of how I have configured it at another customer
    In the Sender Communication Channel the classifier modules are configured (localejbs/SeeClassifier). This module expects some parameters:
    Parameter               Value
    attID                    ClassifierAtt
    classifierMappingID          XXXX (Choose something for XXXX)
    destSourcMsg               MainDocument
    showInAuditLog          true
    The parameter “mappingName” of module localejbs/Seeburger/CallBicXIRaBean should be set to AUTO otherwise the classifier functionality won’t work.
    In the BIC Mapping Designer now you have to create a program called Edifact_XXXX (have a look at page 40 of the manual)
    I generated a mapping called Edifact_XXXX from the message Edifact_service with the programs “CreateXMLMessage”, “CreateMappingXMLToEdi”, “CreateMappingEdiToXML”.
    After this I adjusted the generated program in the UNH segment I added the following rules:
    if name$ = "See_E2X_ORDERS_UN_D96B"
       copy "E2X_ORDERS_UN_D96B" to name$;
    endif
    With this code you change the mapping name that is called in the BIC to convert the EDIFACT message to XML. Or other functionalities.
    The mapping that you use here should be the same as configured in the Splitter of the Seeburger FrontEnd
    Screen prints:
    Configuration of Sender Communication Channel
    BIC MD: Generation programs
    BIC MD: New generated mapping Edifact_xxxx from message Edifact_Service
    BIC MD:Adjustment in mapping program Edifact_XXXX
    Seeburger FrontEnd Splitter configuration

  • Seeburger message mapping

    Guys,
        I  have to map A_850_V4010 to IDOC ORDERS05. I was trying to leverage the the message mapping Seeburger delivers as part of
    the B2BContent-A_850_V4010_to_I_ORDERS_05
    This is what I did ,
    a) I have imported the ORDERS05  idoc definition fromECC system into my name space. 
    b) I also imported the 850_v4010 from Seeburger Message catalogue  by importing XML_850_V4010.xsd.
    Now, when I try to copy the A_850_V4010_to_I_ORDERS_05 that into my namepsace, the XI  asks whether I want to import the Source Message LIST from http://seeburger.com/b2b  as well as ORDERS05  from http://seeburger.com/b2b .
    My questions are
    1)How is the external defintion done ? Is it like step a) and b) described above?  or, does Seeburger provide the XSD for ORDERS05 idoc? 
    2)  how do I make sure that  ORDERS05 that I got from my  ECC system is  the same structure as that of ORDERS05 in
    Seeburger?   besides going through individual fields . Ideally, I would like to use the ORDERS05 I imported in step a) as the traget message.  With  message maaping copy it seems step a) and b) is  not  relevant.
    3) I  also need to map SHPMNT05 idoc to A_856_V4010. Since Seeburger doesn't have it in the mapping list ( the  one they have is DELVRY03_To_A_856_V4010) , the mapping will be the same as the DELVRY03_To_A_856_V4010  EXCEPT that I need to get
    TKNUM  from the SHPMNT05 header. I am wondering whether Manually creating the mapping is the only way, or  is there anyway I can leverage the DELVRY03_To_A_856_V4010 mapping? Has anyone had the experience where they had to change the source Idoc but, still been able to leverage the existing mapping . I just need to change the mapping from E1EDL20 - VBELNin Delvry03  to E1EDT20-TKNUM in SHPMNT05 idoc - this will be mapped to  D_396 in S_BSN segment.
    Thanks !!

    Hey
    >>1)How is the external defintion done ? Is it like step a) and b) described above? or, does Seeburger provide the XSD for ORDERS05 idoc?
    Seeburger provides XSD's for all the major EDI structures,but somehow when i was trying to import the XSD'd and Message mapping into my own SWCV,i was getting the same issue as you have so i ended up copying them manually.it works fine after that.
    >>I am wondering whether Manually creating the mapping is the only way, or is there anyway
    DELVRY03 IDOC is different from SHPMT05 IDOC,even i had to use SHPMNT05 IDOC message mapping and since it didn't come with seeburger,i designed my own message mapping manually.
    >>experience where they had to change the source Idoc but, still been able to leverage the existing mapping
    I tried this,it doesn't works properly,gives you issues at the time of activating the mapping.
    My advice would be to go ahead and do all the steps manually,i had put in lots of effort and time but ended up doing major parts of mappings manually,the mapping you get from SeeBurger is just the base/generic mapping and is a lot different from the actual mapping required for Business partners.
    Thanx
    Aamir
    Edited by: Aamir Suhail on May 6, 2008 8:33 PM

  • Few clarification on SeeBurger adatpers.

    Hi All,
            Presently we have EDI middleware tool which converts the IDOC into EDI and EDI into IDOC. On the outbound scenerio, the converted EDI flat file is sent to VAN and on the inbound scenerio the converted IDOC file is sent to SAP system.
            We have PI system to send XML files to our non EDI partners. We decided to eliminate the existing EDI middleware tool and install SeeBurger in XI/PI.
            Based on the bussiness environment and current requirement we evaluated the list  ( [http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/f0c0d023-a296-2b10-1ea0-bb15d4498035|http://www.sdn.sap.com/irj/sdn/index?rid=/webcontent/uuid/f0c0d023-a296-2b10-1ea0-bb15d4498035] ) of SeeBurge adapters and we decided to purchase the below SeeBurger adapters.
              Retail Industry Adapter
            Cross Industry Payment Adapter.
    FYI : I'm aware that for converting the EDI XML to EDI and XML-EDI you need to have a seeburger mapping program(BIC) at the adapter module which does the conversion. For this module I need a BIC tool of seeburger which provides the different module program for EDI to XML and XML-EDI. This program needs to be deployed on XI and through adapter it has to be called for conversion.
              I believe that , to achieve this(IDOC->PI/SeeBurger->VAN) design, I don't need any additional technical adapters. Please correct me if i'm not right here.
    Thanks,

    Hi,
    VAN(Value Added Networks)
    VANs also provide an advantage with certificate replacement in AS2 transmissions. Because each node in a traditionally business-related AS2 transmission usually involves a security certificate, routing a large number of partners through a VAN can make certificate replacement much easier.
    The FTP/VAN Adapter supports the following protocols:
    • IBMIE VAN, all report options.
    • GEIS (GeMarkIII) and GeMark3000, all report options, report file is only extracted, if needed.
    • EXITE (ECODEX), EDIFACT file processing, DISPATCHED reports.
    • Sterling Commerce and Sterling IIB.
    • MCI EDI*Net.
    The following FTP options are supported:
    • SSL, both IMPLICIT and AUTH_TLS support, server authentication.
    • All popular FTP proxy types like: USERWL, USERWOL, SITEWL, OPENWOL.
    • Active and Passive connection modes.
    • "KeepAlive" feature.
    • Binary, ASCII and custom transfer types
    Regards,
    Raju.

  • Regarding Seeburger Inbound Mapping.

    Hi Everyone,
    I am doing an Inbound Mapping from ANSI to IDOC using Seeburger Mapping Tool.
    My Source Structure has the following LIN Segment
    LIN (Item Identification) has Multiple Qualifiers and ID's like
    235 (Product/Service ID Qualifier)
    234 (Product/Service ID)
    235 #2(Product/Service ID Qualifier)
    234 #2(Product/Service ID)
    235 #3(Product/Service ID Qualifier)
    234 #3(Product/Service ID)
    235 #4(Product/Service ID Qualifier)
    234 #4(Product/Service ID) ..... and so on.
    my mapping requirement is
    For every qualifier
    235  = "MG",
    235 #2 = "MG",
    235 #3 = "MG",......   i need to map source field (MATNR) to ID's  234 , 234 #2, 234 #3....
    similarly,
    so for every qualifier
    235  = "KJ",
    235 #2 = "KJ",
    235 #3 = "KJ",......    i need to map source field (INSMK) to 234, 234 #2, 234 #3....
    Please suggest me, how should i proceed, I would Appreciate if anyone could help me.
    Regards,
    Varun Reddy.K

    Hi,
    what are your source and target structures?
    Regards,
    AKshay

  • Send me documents regarding all Seeburger  adapters and scenarios

    Hi All,
    Convery my best wishes to all.
    i got objects on Seeburger scenarios, on this i don't have any experience so please send me documents soon.
    particularly TRADACOMS ORDERS( and mapping program on this), OFTP, AS2 and remaining all seeburger adapters.
    very thanks in advance.
    Thanks and Regards
    Sai

    Hi,
    check below links
    Go through this thread.
    Seeburger EDI conversion Vs XI Conversion Agent EDI conversion?
    Seeburger info:
    Re: seeburger adapter
    Re: SEEBURGER's VAN Adapter
    Seeburger Adapter
    http://www.hibcc.org/EBUS/editemplates.htm
    /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
    /people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    Check this blog also
    /people/ravikumar.allampallam/blog/2005/02/28/creating-sales-order-through-idoc
    With Seeburger we can conver to edi format to XML
    seeburger doc
    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-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
    Please see the below blogs
    /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

  • EDI Processing

    Hi All,
    I have some questions about EDI processing in XI.
    If we use seeburger adapter, do we need to write custom mapping program (eg: 850 to ORDERS) or adapter itself generate the mapping?
    How do we split the message is it Interchange level or Transaction level? How seeburger is going to handle this?
    Can anyone please forward me the related documents if you have about seeburger adapter?
    Please explain me one complete scenario EDI 2 IDOC using Seeburger adapter.
    What are the other alternatives to seeburger adapter?

    Hi,
    Please see the below links , so that you can get clear idea about EDI/seeburger
    /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.sap.com/asia/company/events/nwtechdays/presentation/australia-slides/Pre-Built_Integration.pdf
    Please let me know your prob is clear or not..
    Regards
    Chilla..

  • How to identify validation errors

    if the validation process shows an error in a CSS file is
    there any way to identify what is causing the problem?
    I have the following response from the DW validation process
    quote:
    Found 1 errors in external css files
    Affects: Internet Explorer 6.0; Internet Explorer for
    Macintosh 5.2
    However, I have no idea what might be the cause of the
    problem.
    Any suggestions would be most welcome.
    Thanks.

    Hi
    Ref this links
    http://www.hibcc.org/EBUS/editemplates.htm
    /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
    /people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    /people/ravikumar.allampallam/blog/2005/02/28/creating-sales-order-through-idoc
    With Seeburger we can conver to edi format to XML
    seeburger doc
    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
    Doc for Conversions-
    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
    Thanx
    Bommireddy.Sridhar

  • EDI Scenario - Samples

    All,
    Can you please provide some sample scenarios with EDI using Seeburger.
    I was unable to find good document with EDI Scenaios.

    Hi,
    EDI Seeburger Adapter
    http://www.hibcc.org/EBUS/editemplates.htm
    SAP XI supports EDIFACT
    How to get started using Conversion Agent from Itemfield
    More on the SAP Conversion Agent by Itemfield
    Manipulating Idoc Control Records from Payload
    The specified item was not found.
    Check this blog also
    Creating Sales Order through Idoc
    With Seeburger we can conver to edi format to XML
    seeburger doc
    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-
    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
    Regards,
    Sarvesh

  • How to Identify EDI errors in inbound IDocu0092s?

    hi,
    I just want to know how to identify EDI errors in inbound IDoc’s?

    Hi
    Ref this links
    http://www.hibcc.org/EBUS/editemplates.htm
    /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
    /people/sravya.talanki2/blog/2005/12/02/manipulating-idoc-control-records-from-payload
    /people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
    /people/ravikumar.allampallam/blog/2005/02/28/creating-sales-order-through-idoc
    With Seeburger we can conver to edi format to XML
    seeburger doc
    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
    Doc for Conversions-
    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
    Thanx
    Bommireddy.Sridhar

  • EDI Format in SAP without Gentran Subsystem

    Hello,
    Our customer currently use Gentran to generate the EDI Formats, and then send it to the WebSphere broker. They do not want to use the Gentran subsystem anymore, and  ask if there is a solution in sap for creating this EDI Formats directly. I investigated that SAP does not supply the EDI subsystem for several reasons, so i have to give the customer a valid reason if this is not possible. Also i would like to know if it is possible to send directly the Idocs to the Broker and convert it to the EDI Format there .Any help would be appreciated.
    Thanks.

    Hi Francisco,
    I am not aware about Gentran system. But i can give you some information related to EDI format with help of PI
    You can send or receive EDI files via PI with Seeburger insertion.
    Seeburger is used to convert XML to EDI or EDI to XML.
    For example I am sending an IDOC from SAP system and want an EDI file in third party system. for this scenario you have to use PI with seeburger. SAP IDOC ->PI->Seeburger->EDI file (third party)
    In PI you have to create 1:1 mapping to convert IDOC to EDI XML and this EDI XML is send to seeburger to create EDI file.
    There are many standard EDI mappings available in seeburger. You can check all the maping from there.
    I hope this answer will help you.
    Regards,
    Shradha

  • Alert Monitoring

    Hi Experts,
    I am dealing with a situation, wherein i need to monitor alerts. But, I am not sure which of the alerts are automated. Could you please suggest which of the following Tcodes could be automated??
    SMQ1
    SM58
    SXMB_MONI  / SM37
    WE19/ WE05/ BD87
    Seeburger-Idoc  Adapter
    SEEBURGER-EDI FOLDER
    SEEBURGER-MONITOR
    /SAPSLL/SPL_ST01
    /SAPSLL/CNTRY
    /SAPSLL/SPL_BLRL
    /SAPSLL/SPL_BLRL_exp
    /SAPSLL/SPL_BLBPLO
    Please suggest also, how to define them.
    Thanks & Regards,
    Sushama

    You set up alerts so that in case of an exception during message processing, the system will inform you. You can recieve alerts by email,fax or sms. Also, you will see the alerts in you alert inbox.
    Now you can set up these alerts from BPM such as by using Control step (value ThrowAlert)
    Prerequisites for alert configurations:
    1. RZ21: Alert management must be activated for PI infrastrucure.
    2. Define alert categories  with paramers like text,expiry date and time.. using tx:ALRTCATDEF
    Also you can refer the below link:
    [http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID1524276250DB01857650165891326676End?blog=/pub/wlg/2777|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417200)ID1524276250DB01857650165891326676End?blog=/pub/wlg/2777]
    Puneet

  • Seeburger IDOC-to-File scenario: Error using Classifier module

    Hello,
    I am running the following scenario: ORDERS.ORDERS05 IDOC -> XI -> X12 850 4010 File.
    In the file receiver channel, I am using Seeburger's Classifier and BIC modules as follows:
    localejbs/SeeClassifier        classifier
    localejbs/CallBicXIRaBean      bic
    CallSapAdapter                 0
    classifier   attID             classifierAtt
    classifier   destSourceMsg     MainDocument
    classifier   showInAuditLog    true
    bic          classifierAttID   classifierAtt
    bic          destEncoding      UTF8
    bic          destSourceMsg     MainDocument
    bic          destTargetMsg     MainDocument
    bic          mappingName       AUTO
    bic          newLine           true
    bic          srcEncoding       UTF8
    After conversion in XI, the file fails to write to the folder because of this error:
    Message processing failed. Cause: javax.resource.ResourceException: ---
    Conversion of synchronous request from module chain ended with errors
    ---Error: [Error:ID=1010;LEVEL=1] BICMapping runMapping() The mapping:
    See_XML_AnsiX12 you are trying to load cannot be found in the classpath!
    Maybe you forgot to compile or to activate the mapping! DESCRIPTION:
    BICMapping Error: The mapping [not specified] you are trying to load cannot
    be found in the right path! Maybe you forgot to compile or to activate the
    mapping!
    When I set the mapping directly to See_X2E_AnsiX12_850_V4010 instead of using the Classifier module, the configuration works fine.  But I want to design the receiver channel to be able to receive all types of EDI messages coming from XI.
    I am only facing this problem for the IDOC-to-File scenario.  Somehow the same configuration works for a File-to-IDOC scenario.
    I talked to our Basis team and they said that the map See_XML_AnsiX12 does not exist in Seeburger's delivered content, although I believe that it should be.  Has anyone encountered this problem before?
    Any suggestions would be appreciated.
    Thanks,
    Arianne

    Hi Yomesh,
    Here is the payload.
    <?xml version="1.0" encoding="UTF-8"?>
    <LIST>
      <S_ISA>
        <D_I01>00</D_I01>
        <D_I02/>
        <D_I03>00</D_I03>
        <D_I04/>
        <D_I05>ZZ</D_I05>
        <D_I06>CELORGS01</D_I06>
        <D_I05_2>ZZ</D_I05_2>
        <D_I07>AVX</D_I07>
        <D_I08>032008</D_I08>
        <D_I09>1718</D_I09>
        <D_I10>X</D_I10>
        <D_I11>00401</D_I11>
        <D_I12>000000008</D_I12>
        <D_I13>0</D_I13>
        <D_I14>T</D_I14>
        <D_I15>^</D_I15>
        <S_GS>
          <D_479>PO</D_479>
          <D_142>CLS01</D_142>
          <D_124>058895921</D_124>
          <D_373>20080320</D_373>
          <D_337>1718</D_337>
          <D_28>8</D_28>
          <D_455>X</D_455>
          <D_480>004010</D_480>
          <S_ST>
            <D_143>850</D_143>
            <D_329>800001</D_329>
            <S_BEG>
              <D_353>00</D_353>
              <D_92>SA</D_92>
              <D_324>4500005037</D_324>
              <D_373>20051110</D_373>
            </S_BEG>
            <S_CUR>
              <D_98>BY</D_98>
              <D_100>USD</D_100>
            </S_CUR>
            <S_FOB>
              <D_146>CC</D_146>
              <D_309>OR</D_309>
              <D_352>FREE CARRIER</D_352>
              <D_334>02</D_334>
              <D_335>FOB</D_335>
              <D_309_2>DE</D_309_2>
            </S_FOB>
            <S_ITD>
              <D_336>01</D_336>
              <D_333>3</D_333>
              <D_351>45</D_351>
            </S_ITD>
            <G_SN9>
              <S_N9>
                <D_128>L1</D_128>
                <D_369>GEN</D_369>
                <S_MSG>
                  <D_933>TEST</D_933>
                </S_MSG>
                <S_MSG>
                  <D_933>MESSAGE</D_933>
                </S_MSG>
              </S_N9>
            </G_SN9>
            <G_SN1>
              <S_N1>
                <D_98>BY</D_98>
                <D_66>92</D_66>
                <D_67>6310</D_67>
                <S_PER>
                  <D_366>BD</D_366>
                  <D_93>Graham Crawford</D_93>
                </S_PER>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>BT</D_98>
                <D_66>92</D_66>
                <D_67>6310</D_67>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>SE</D_98>
                <D_93>3M COMPANY</D_93>
                <D_66>92</D_66>
                <D_67>0000019591</D_67>
              </S_N1>
            </G_SN1>
            <G_SN1>
              <S_N1>
                <D_98>ST</D_98>
                <D_93>SAMPLE</D_93>
                <D_66>92</D_66>
                <D_67>6310</D_67>
              </S_N1>
            </G_SN1>
            <G_SPO1>
              <S_PO1>
                <D_350>00010</D_350>
                <D_330>10.000</D_330>
                <D_355>EA</D_355>
                <D_212>10</D_212>
                <D_639>PE</D_639>
                <D_235>BP</D_235>
                <D_234>230-1812-01JDS</D_234>
                <D_235_2>EC</D_235_2>
                <D_234_2>A00000000000002</D_234_2>
                <G_SPID>
                  <S_PID>
                    <D_349>F</D_349>
                    <D_352>TIE WRAP,LOCKING,PANDUIT-PLASTIC PART C</D_352>
                  </S_PID>
                </G_SPID>
                <S_REF>
                  <D_128>CO</D_128>
                  <D_127>4500005037-00010</D_127>
                </S_REF>
                <G_SSCH>
                  <S_SCH>
                    <D_380>10.000</D_380>
                    <D_355>EA</D_355>
                    <D_374>002</D_374>
                    <D_373>20051208</D_373>
                  </S_SCH>
                </G_SSCH>
              </S_PO1>
            </G_SPO1>
            <G_SCTT>
              <S_CTT>
                <D_354>1</D_354>
              </S_CTT>
            </G_SCTT>
            <S_SE>
              <D_96/>
              <D_329>800001</D_329>
            </S_SE>
          </S_ST>
          <S_GE>
            <D_97>1</D_97>
            <D_28>8</D_28>
          </S_GE>
        </S_GS>
        <S_IEA>
          <D_I16>1</D_I16>
          <D_I12>000000008</D_I12>
        </S_IEA>
      </S_ISA>
    </LIST>
    Thanks,
    Arianne

Maybe you are looking for