EDI 810 signal

Hi Experts,
I need a small help. currently I'm working on scenario wherein XML file is sent to customer via EDI. The PI system picks up the XML file and convert it into EDI 810 ANSI X12 5010 Version and sends to customer. The problem is PI system generating EDI XML and while sending it to Seeburger below error message is showing Runtime Workbench.
MP: Exception caught with cause javax.resource.ResourceException: --- Conversion of synchronous request from module chain ended with errors ---[Error:ID=3069;LEVEL=3] SegmentDescription: checkAndResetChildrenCounter() not enough repetitions of the segment S_ST found: 0 instead of 1 offset :2175 DESCRIPTION: SegmentDescription Warning: Not enough repetitions of the segment S_ST ([not specified]/[not specified]).
I copied the EDI XML data and executed in BIC and it is converting into EDI ANSI X12 format, but failing in RWB. Can anybody help me out. Let me know how to resolve it?
Thanks
Faisal

HI Failsal,
From error message i could see that, the segment S_ST should have a value 1. In Module parameter you should modifiy the parameter for this segment and check your scenario, because method checkAndResetChildrenCounter() expects the S_ST to be repeated atleast 1 times not 0 times.
Regards,
RK

Similar Messages

  • Partner Profile configuration for EDI 810

    Hi,
    I am configuring partner profile for EDI 810 (Invoice). In the message control tab, what values should be entered for
    1. Application
    2. Message Type and
    3. Process Code
    Thank you.

    Hi,
    - Check Transaction NACE to see what applicatios you can use for different objects.
    - Check transaction WE42 for all outbound process codes
    - Check transaction WE41 for all inbound process codes.
    - Check transaction WE64 for inboud / outbound message types and related process codes.
    <b>EDI 850:</b>
    Application - EF
    Process code - ME10
    Message type - NEU ( or your custom message type setup for EDI  )
    IDOC - ORDERS01 to ORDER05
    <b>EDI 810:</b>
    Application - V3
    Process code - SD09
    Message type - RD00 (  or your custom message type setup for EDI  )
    IDOC - INVOIC01 , INVOIC02.
    <b>EDI 820:</b>
    i think this is for inbound idoc of  <b>Payment Order/Remittance Advice</b>. When yuo setup inbound partner profile, you do not need to know application
    Process code - LOBX
    Message type - LOCKBX
    IDOC - PEXR2002
    Let me know if you need any other information.
    Regards,
    RS

  • Multi-mapping for EDI 810 Interface

    Hi,
    I am building EDI 810 interface. We have following requirements.
    Source system is SAP. Target systems is AAFES and COSTCO.
    1 Source system and 2 target System.
    For example: Can i have Interface mapping as shown below?
    Invoice IDoc -> MM_EDI_810_AAFES  -> EDI_810
                    MM_EDI_810_COSTCO
    Based on DUNS number can i re-direct the interface to choose one of the mapping and accordingly choose the communication channel?
    Thanks,
    Gowri

    Hi,
    You can do this in any of the following ways:
    Content based routing in XI can be done during
    1) Receiver Determinations (Integration Directory) --- Used for entering a condition for
    forwarding a message to one or more receivers
    http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/content.htm
    2)Interface Determinations (Integration Directory) --- Used for entering a condition for forwarding a message to multiple inbound interfaces
    3) Designing Integration Processes (ccBPM) (Integration Repository) --- Used for entering a condition for processing process steps (see Step Types)
    At all the 3 places u will use the Condition editor,
    http://help.sap.com/saphelp_nw04/helpdata/en/67/49767669963545a071a190b77a9a23/content.htm
    Hope this helps you.
    Regards,
    Abhy

  • Seeburger Module Runtime Error when I am executing the 810 signal

    Hi,
    My Scenarios is Idoc to EDI (810), for testing purpose I configured the receiver File adapter with modules, when i send the data from RWB Integrationengine test tab, I am getting the below runtime error
    "Message processing failed. Cause: com.sap.engine.services.jndi.persistent.exceptions.NameNotFoundException: Object not found in lookup of CallBicXIRaBean."
    Receiver File adapter modules
    Processing Sequence:
    localejbs/CallBicXIRaBean  Local Enterprise Bean  bic
    localejbs/ModuleProcessorExitBean  Local Enterprise Bean  exit
    Module configuration
    bic  destSourceMsg  MainDocument
    bic  destTargetMsg  MainDocument
    bic  mappingName  SDC_X2E_ANSIX12_810_V4010
    bic  JANDIName  deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
    Thanks
    Ramesh
    Edited by: Venkataramesh Boppana on Nov 8, 2010 8:55 PM

    Hi Ramesh,
    same thing like Classifier module.
    "Object not found in lookup of CallBicXIRaBean..." Did you deploy SeeBICXI.sca?
    regards,
    Daniel

  • Seeburger help required for Supplier Invoice (EDI 810) and Dispatch Advice

    Hi All,
    Pls let me blog/steps for scenario for Supplier Invoice and Dispatch Advice using Seeburger.
    For Supplier Invoice I assume R/3 will send data to Vendor (810).
    1. Pls let me know for R/3 to XI will we use INVOCE IDOC?
    2. Pls let me know for R/3 to XI Communication do we will use same Distributiion Model setup?
    3. Pls let me know what Seeburger BIC modules I need to use in Seeburger AS2/File Receiver Adapter
    4. Which Interface and Adapter  I need to use for 810 and which Interface and Adapter  I need to use for 997.
        Pls send its setup with its Mappings defined in Modules.
    5. What is Disptach Advice?  Is it also same like Supplier Invoice ? Does it also have EDI Number and if yes then what?
    Pls send me blogs for the above Supplier Invoice and Dispatch Advice settings.
    Regards

    >
    Rickkk wrote:
    > Hi Ravi and All
    >
    > I am thankful to all of you for great help of yours.
    >
    > Steps:
    >
    > 1) I wil create an INvoice in your backend system. It will generate an IDOC.
    > 2) This IDOC will be sent to my XI system.
    > 3) I will map the IDOC to the Target XML 810 --- From where I will get this Target XML 810 ?
    YOu have to login to the Physical box in which XI is installed (Take Basis Help.
    In one of the drives, you will find a folder called seeburger.
    Inside that folder, you can browse to find the XSD structure for your 810 .
    YOu will find different XSDs for different versions of 810.
    Suppose your EDI 810 version is 4010, then you have to use the XSD for 810 4010 version (There will be separate folders for each transaction set/version combination.
    It will be there also in the software CD that seeburger provides when you buy it.
    > 4) I need a seeburger receiver AS2 adapter that consist of modules that will convert the XML 810 docuemnt to EDI document.
    >
    > Below are the modules will be present in you suggested seeburger receiver AS2 adapter
    > module key                  Parameter name               Parameter value
    > bic                                destSourceMsg               MainDocument
    > bic                                destTargetMsg                MainDocument
    > bic                                mappingName                  <the name of your X2E mapping for 810>
    > exit                               JNDIName                         deployedAdapters/SeeXIAS2/shareable/SeeXIAS2
    >
    Yes.
    > 5. As per blog  -
    /people/rajeshkumar.pasupula/blog/2009/08/05/wanna-implement-seeburger-for-edi-find-the-booster
    >
    > For 997 Interface we are using seeburger Sender adapter and for 850 Interface we are using Split997 Sender adapter -- Reverse order
    >
    > For this scenario will it be like this again like
    > For 997 Interface we will use Seeburger Receiver AS2 Adapter where the above modules are configured -- Pls suggest
    >
    > For 810  Interface we will use Split997 Receiver adapter -- No modules configured Pls suggest
    >
    > I request you to kindly send me snapshots or blogs which has snapsot for this scenario.
    >
    No need of split 997 in outbound case. In this case, you will send the 810 and the partner will send the 997.
    So, to receive that 997 file, you need another scenario. You need the split 997 communication channel only in inbound case like in 850, but not in outbound case.
    > Last point -- is Dispatch advice direction is like 850 (Inbound ) or its direction is like 810 (outbound)?
    > Do we have IDOC or something like that present and its mapping ?
    >
    like I said earlier, it is an outbound document if your company is the vendor.
    It will be inbound if your company is the Customer to some other company.
    The IDOC that is used usually will be DESADV idoc.
    > Regards

  • EDI 810: Basic Type /NFM/INVOIC02,LIFNR and ROUTE Field

    Hi Sap Guru,
    When EDI 850 has been trigger, the sales order has been get created with IDoc. In IDoc we are getting LIFNR (vendor at customer place) as shown below in segment E1EDKA1 WE. But the same thing is not getting reflected at EDI 810.
    So please help me in this..... and also ROUTE field is not getting reflected in same EDI 810.
    I hope you will help me to get out from this asap.
    Thanks in advance...
    Regards,
    Kundan

    For the customer invoice EDI, the vendor number is not same for all customer. Each customer will assign a vendor number to the company. Hence you may need to go with user exit to populate the data.
    For route, I am not sure why customer is looking for route in billing document. Route mostly used in delivery related documents. So if a field is not available for route in IDOC INVOIC02, then you need add a Z-segment to populate the route value. Discuss with an ABAP'er for solutions.
    Regards,

  • EDI 810 Inbound - Vendor Invoice

    Hi
    What is the Message type, Basic type, Process code and Function module for Inbound Vendor Invoice (EDI 810 Inbound) ?
    Thanks
    Maruthi

    Hi
    I am  working on the Invoice receipt thru EDI-IDoc from Vendors (EDI-810 INBOUND). I am getting certain errors.
    Error 1:
    Customer , Vendor XXXXXXX not known
    Message no. FD110
    Error 2:
    G/L Account XXXXXXX can only be posted internally.
    Message no. F5562
    I have tried to trigger IDocs using basic types INVOIC01 and INVOIC02. But all in vain.
    Please rush your answer,
    Cheers
    Maruthi

  • EDI 810 Inbound

    Hi,
    i am trying to post an Inbound Idoc through message type:INVOIC.I have configured every thing and now able to post the Idoc by using WE19,Now i have file in application server with naming format OH_810_xxxxxxx.EDI. I am using the existing FILE port and have given the application server path in INDOUND FILE tab and the FM:EDI_PATH_CREATE_CLIENT_DOCNUM.
    the issue is now the file is not picking....how to automate it like when ever the file comes in application server the idoc should be trigered.

    Hi
    I am  working on the Invoice receipt thru EDI-IDoc from Vendors (EDI-810 INBOUND). I am getting certain errors.
    Error 1:
    Customer , Vendor XXXXXXX not known
    Message no. FD110
    Error 2:
    G/L Account XXXXXXX can only be posted internally.
    Message no. F5562
    I have tried to trigger IDocs using basic types INVOIC01 and INVOIC02. But all in vain.
    Please rush your answer,
    Cheers
    Maruthi

  • Interface program to transmit billing docs as edi 810

    Hi experts,
        I am new to ale/edi/idocs. I need to develop an interface program to transmit billing documents in a text file for sending them as edi 810 docs. Can anyone give me some idea on how to deal with this?
    Thanks a lot...
    Regards,
    Abhinav
    Message was edited by:
            Neo

    thanks karthikeyan...but i need help in the part after message control configuration in the edi outbound process...

  • EDI 810

    Hi,
      What are the mapping procedures for an incoming EDI 810 invoice file to IDOC(INVOIC).
    Please send your suggestions,
    Rajesh.

    Hi,
    Check this links:
    http://www.riyaz.net/blog/index.php/2008/01/19/beginners-guide-to-ale-and-idocs-a-step-by-step-approach/
    Sales Order Idoc Extension.
    http://www.*******************/2007/11/abap-idocs-basic-tools.html
    Regards
    Adil

  • Third party tool link for EDI 810

    Hi,
      What is the third party tool for mapping EDI 810
    and link.
    Thanks
    avi

    Hi avinash,
    Check the links below
    http://www.covalentworks.com/edi-810-invoice.asp
    http://www.caiso.com/docs/1999/01/15/1999011506424228685.pdf
    http://www.seagate.com/support/edi/o810c306.html
    http://edi.stylusstudio.com/msg01070.htm

  • EDI 810 OAG Invoice XML tranforming to InvoiceEBO.xsd

    Hi,
    Oracle 11g trying to use AIA InvoiceEBO.xsd for transforming an EDI XML message.
    Trying to transform an EDI OAG XML to InvoiceEBO.xsd.
    Can any one let know if any one has already implemented the EDI 810 Invoice outbound using the InvoiceEBO.xsd

    Are you facing any issue with the mapping?
    Regards,
    Anuj

  • Subscribe EDI 810 Invoice using Apps Adapter

    I am confused with subscribing to EDI X12 810 outbound Invoice. When I try to subcribe to EDI 810 outbound Invoice using App adapter , it shows XMLGateway(4), EDI (1), PL/SQL(1) , CON_PROGRAMS(1), Interface views (1). I dont understand to which I should subscribe.
    I appreciate your help.
    Thanks.
    Morasa

    Hello Morasa,
    Please refer the below link.
    http://www.oracle.com/technology/products/integration/adapters/pdf/adapter-Tutorial1-InvokingOracleApplicationsAPI.pdf
    Kindly note that this forum is mainly intended to discuss primarily on B2B and integration issues, for BPEL please refer SOA forum
    SOA Suite
    Rgds,Ramesh

  • EDI 810 ,856

    Hi all,
    Please doea any body can provide the step by step process for EDI 810 & 856 . i donno how to create edi 810 and 856.
    Thanks in advance.

    Hello Shweta
    EDI 810 = Invoice, e.g. [EDI 810 Invoice Defined|http://www.edipipeline.com/810.asp]
    EDI 856 = Advanced Ship Notice, e.g. [EDI Engineu2122 \ Translation \ ASC X12 \ 856 (Advance Ship Notice/Manifest)|http://www.123edi.com/edi-856.asp]
    The basic steps of EDI are:
    1. Send SAP invoice / outbound delivery as EDI output (IDoc message types: INVOIC and SHPORD (DELVRY03)).
    2. Receive IDocs at EDI conversion platform (e.g. SAP-XI).
    3. Convert IDoc-XML to EDI-XML.
    4. Convert EDI-XML into flat EDI message.
    5. Send EDI message to receiver mailbox (e.g. via VAN or AS2 or OFTP)
    Regards
      Uwe

  • Generating EDI 810 Outbound File in 4030 version

    Hi All,
    I am working in EDI 810 outbound file generation. Is there any versions in it? What are the steps to generate the outbound file in 4030 version?
    Thanks in advance

    Hi,
    Please see
    How To Setup EDI 810 Outbound and 812 Outbound [ID 198252.1]
    Thanks

Maybe you are looking for