EDI 870 & 888

Hi guru,
   Did anyone worked on the EDI 870 & 888.  Please send me the flow and tcodes used for this EDI transactions and also the message types and Idoc types used.
870 Order Status Report (inbound)
888 Item Maintenance (outbound)
Thanks,
Priya

Hi,
I would like to know the Message type and basic type for EDI 870 (Outbound).
I guess the message type is ORDRSP, and you can choose any IDOC Type between ORDERS01-ORDERS05, better to use ORDERS05.
In what instance it is triggered.
It can be configured to be triggered as soon as an Order is created using message control - output type.
Should i create an abap report ??
Well it depends on how you want this handled and how your customer wants the status of the orders(since you have mentioned EDI 870, i presume you want it sent via EDI). You don't need to create a report as it can be achieved by using message control.
The flow as far as my understanding goes is as below, As soon as a Sales Order is created against the customer PO, you can choose send the status of that particular Order immediately/accumulate them to send it using a batch job. The details of the order are sent via an IDOC - In this case ORDERS05.
There is sufficient information on the internet on how to configure using message control, go through the same.
http://help.sap.com/saphelp_di46c2/helpdata/EN/c8/19878343b111d1896f0000e8322d00/frameset.htm
Regards,
Chen

Similar Messages

  • EDI 870 - Order Status Report

    Hi,
    I would like to know the Message type and basic type for EDI 870 (Outbound).
    In what instance it is triggered.
    Should i create an abap report ??
    Thanks in advance...

    Hi,
    I would like to know the Message type and basic type for EDI 870 (Outbound).
    I guess the message type is ORDRSP, and you can choose any IDOC Type between ORDERS01-ORDERS05, better to use ORDERS05.
    In what instance it is triggered.
    It can be configured to be triggered as soon as an Order is created using message control - output type.
    Should i create an abap report ??
    Well it depends on how you want this handled and how your customer wants the status of the orders(since you have mentioned EDI 870, i presume you want it sent via EDI). You don't need to create a report as it can be achieved by using message control.
    The flow as far as my understanding goes is as below, As soon as a Sales Order is created against the customer PO, you can choose send the status of that particular Order immediately/accumulate them to send it using a batch job. The details of the order are sent via an IDOC - In this case ORDERS05.
    There is sufficient information on the internet on how to configure using message control, go through the same.
    http://help.sap.com/saphelp_di46c2/helpdata/EN/c8/19878343b111d1896f0000e8322d00/frameset.htm
    Regards,
    Chen

  • EDI 870  sales order status

    Hi All,
    We are implementing the sales order status using EDI 870. Does anybody implemented the same and if so please share IDOC/Message type name or process.
    Thanks & Regards,
    Harish

    VBUK-GBSTK Stores the overall status of the order. ' ' - Not relevant, 'A' - Not yet processed, 'B' - Partially processed , 'C' - Completely Processed.
    If you are looking the status based on Object status, then use the function module "STATUS_SHOW_CHANGE_DOCUMENTS"
    Regards
    Vinod
    Edited by: Vinod Kumar on Apr 8, 2010 1:47 PM

  • OUTBOUND EDI 870

    I was just wondering if anyone has implemented a Outbound EDI 870 - Order Status Report.
    Which Msg & IDOC Type can I use in SAP?
    Any ideas or places to look would be great.

    Hi,
      If 870 is a order status report kind of a document, you may have to go by the ABAP Proxy route.
    Have an abap program that pulls out all the information that is needed for 870 and create a proxy for such an interface in your R/3 system.
    Regards,
    Ravi

  • EDI Transactions

    Hi,  Can anyone explain about the list of EDI Transactions below.  I need the steps and flow of those EDI Transactions.  Please help me out in the below...
    846 Inventory Advice (inbound)
    870 Order Status Report (inbound)
    888 Item Maintenance (outbound)
    940 Warehouse Shipping Order (outbound)
    943 Warehouse Stock Transfer Shipping Advice (outbound)
    944 Warehouse Stock Transfer Receipt Advice (inbound)
    945 Warehouse Shipping Advice (inbound)
    946 Warehouse Inventory Adjustment (inbound & outbound) 
    Thanks,
    Priya

    Please visit these links for information:
    http://xml.coverpages.org/ASCX12-EDI-Transactions200206.html
    >>EDI transaction sets such as 850 orders, 810 invoice, 214 ASN.
    >>Can anybody give more head on EDI sets and examples?.
    http://www.tea.state.tx.us/textbooks/emat/edistd.html
    http://www.tgiltd.com/supported_edi_transaction_sets.html
    http://www.erpgenie.com/saptech/transactions.htm
    http://www.erpgenie.com/sapedi/index.htm
    Transaction Set for EDIFACT
    http://msdn2.microsoft.com/en-us/library/aa560100(d=printer).aspx
    Transaction Set for ANSI X12
    https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/00415e14-0b01-0010-10a5-97e2cebb167c
    http://www.erpgenie.com/sapedi/ansix12transactionsets.htm
    Points rewarded if it is useful..

  • IDOC Types for 215, 870, 852, 857, 858 and 838

    Hi,
    Can anyone let me know the IDOC types in SAP for
    215, 870, 852, 857, 858 and 838 messages (X12 Messages).
    Thanks,
    Sudheer

    Hi Sudheer
    Check these links,
    http://www.sap-edi.com/sap_r3/ansi.asp
    http://www.geocities.com/sap_edi/ANSI.htm
    http://www.sapgenie.com/sapedi/message_types.htm
    Hope they give you the required information
    Regards
    Vishnu

  • EDI Transaction

    Hi Any body plz give me EDI transaction flow

    Ash,
    Can anybody give more head on EDI sets and examples?.
    >> following are transaction sets
    180 - Return Merchandise
    210 - Freight Invoice
    503 - Pricing History
    805 - Contract Pricing
    810 - Invoice
    811 - Invoice Summary
    812 - Credit/Debit Adjustments
    820 - Payment/Remittance Advice
    823 - Lockbox
    824 - Application Advice
    830 - Production Schedule & Release
    832 - Price/Sales Catalog
    836 - Contract Award
    840 - Request for Quotation
    842 - Nonconformance Report
    843 - Request for Quotation Response
    844 - Product Transfer Adjustment
    845 - Price Authorization
    846 - Inventory Inquiry
    847 - Material Claim
    850 - Purchase Order
    853 - Routing and Carrier Instruction
    855 - PO Acknowledgment
    856 - ASN
    857 - Shipment & Billing Notification
    858 - Shipment Information
    860 - Purchase Order Change
    861 - Receiving Advice
    862 - Shipment Schedule/Release
    864 - Text Message
    865 - Purchase Order Change Acknowledgment
    866 - Production Sequence
    867 - Resale Report
    869 - Order Status Inquiry
    870 - Order Status Report
    879 - Price Change
    997 - Functional Acknowledgment

  • EDI ANSI X12 and relavent IDOC types and messages...

    Hi ,
        Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
    210 -Motor Carrier Freight Details and Invoice
    240 -Motor Carrier Package Status
    753 -Request for Routing Instructions
    754 -Routing Instructions
    816-ORGANIZATIONAL RELATIONSHIPS
    828-Debit Authorization
    846- Inventory Inquiry/Advice
    870-Order Status Report
    Could you please help me?
    Thanks and regards,
    gowri

    EDI ANSI X12 and relavent IDOC types and messages...
    Posted: May 25, 2006 8:44 PM        Reply      E-mail this post 
    Hi Ravi,
         Thanks a lot for the reply. I have already checked this. In the ittoolbox.com is having some info about 214 but not about 210 and 240. I have already gone through the sapgenie.com but could able to get the relevant info on below transactions.I am basically looking for relevant idoc types and messages  in SAP for the below ansix12 transactions .
    Is there any place where we can get the relevant Idoc types and messages for EDI Transacitons below:
    210 -Motor Carrier Freight Details and Invoice
    240 -Motor Carrier Package Status
    753 -Request for Routing Instructions
    754 -Routing Instructions
    816-ORGANIZATIONAL RELATIONSHIPS
    828-Debit Authorization
    846- Inventory Inquiry/Advice
    870-Order Status Report

  • Does the 870 has any option for 3G

    hello experts!!!
    we're doing wifi hotspots and will use 870 to backhaul the mesh network.
    is there an option module for the 870 router for 3G? i haven't seen this router and still searching cisco.com.
    if not, what type of cisco routers similar to 870 size, weight and capacity, have support for 3G?
    thanks for any reply.

    Here is the information about router which support the 3G which will help you
    CISCO881G-K9 Cisco 881 Ethernet Security Router with 3G
    CISCO881GW-GN-A-K9 Cisco 881 Ethernet Security Router with 3G
    CISCO881GW-GN-E-K9 Cisco 881 Ethernet Security Router with 3G
    CISCO881GW-GN-P-K9 Cisco 881 Ethernet Security Router with 3G
    CISCO888G-K9 Cisco 888 G.SHDSL Router with 3G.

  • Two ISA segment in the EDI data

    Hi
    We are getting two ISA segments in the EDI data from the B2B.
    ISA~00~Authorizat~00~Security I~  ~               ~01~Interchange Rec~081210~1018~U~00401~000001012~0~I~\
    GS~  ~  ~EDI Receiver App~20090216~1419~1012~X~004010
    ISA~00~~00~~12~8006218070~~STFM   SF000014 ~090216~1418~U~004010~000000041~0~T~0x1f
    GS~SP~8006218070~AESTPRINT000100~20090216~1418~000000041~X~004010.
    As per the requirement we need to generate a unique number for the ISA, we maintain a counter and populate the ISA with the number incrementing each time.
    We populate the ISA with the number from the counter in xml file and pass the same to the B2B. How can i configure B2B to take the values in the XML and not add one more segment
    Thanks

    Hi,
    I set Internal-properties and i am getting the XEngine error - Invalid guideline.
    B2B log:
    2009.02.24 at 16:29:42:860: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:traceParameters Parameter ReplacementChar = 0x7c
    2009.02.24 at 16:29:42:861: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:getControlNumberFromEDIRepository CtlNum (RF): Interchange = 1000, Functional Group = 1000, Transaction Set = 1000
    2009.02.24 at 16:29:42:861: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
    2009.02.24 at 16:29:42:861: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl fullOutboundBatching = false
    2009.02.24 at 16:29:42:861: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = false
    2009.02.24 at 16:29:42:862: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
    2009.02.24 at 16:29:42:882: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
    2009.02.24 at 16:29:42:882: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverQual, val = [ZZ]
    2009.02.24 at 16:29:42:882: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [ZZ]
    2009.02.24 at 16:29:42:882: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderID, val = [Interchange Sen]
    2009.02.24 at 16:29:42:882: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [Interchange Sen]
    2009.02.24 at 16:29:42:883: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverID, val = [Interchange Rec]
    2009.02.24 at 16:29:42:883: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [Interchange Rec]
    2009.02.24 at 16:29:42:883: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = Standard, val = [X12]
    2009.02.24 at 16:29:42:883: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [X12]
    2009.02.24 at 16:29:42:883: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeControlVersion, val = [00401]
    2009.02.24 at 16:29:42:884: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [00401]
    2009.02.24 at 16:29:42:884: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Interchange]
    2009.02.24 at 16:29:42:884: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderQual, val = [ZZ]
    2009.02.24 at 16:29:42:884: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [ZZ]
    2009.02.24 at 16:29:42:884: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
    2009.02.24 at 16:29:42:884: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
    2009.02.24 at 16:29:42:885: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
    2009.02.24 at 16:29:42:885: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@1588325
    2009.02.24 at 16:29:42:887: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
    2009.02.24 at 16:29:42:887: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupReceiverID, val = [Interchange Rec]
    2009.02.24 at 16:29:42:887: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [Interchange Rec]
    2009.02.24 at 16:29:42:887: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupVersionNumber, val = [00401]
    2009.02.24 at 16:29:42:887: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [00401]
    2009.02.24 at 16:29:42:888: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Group]
    2009.02.24 at 16:29:42:889: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupSenderID, val = [Interchange Sen]
    2009.02.24 at 16:29:42:889: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [Interchange Sen]
    2009.02.24 at 16:29:42:889: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
    2009.02.24 at 16:29:42:889: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
    2009.02.24 at 16:29:42:889: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
    2009.02.24 at 16:29:42:890: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@a2a38
    2009.02.24 at 16:29:42:891: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
    2009.02.24 at 16:29:42:891: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = TransactionID, val = [841]
    2009.02.24 at 16:29:42:891: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [841]
    2009.02.24 at 16:29:42:892: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Transaction]
    2009.02.24 at 16:29:42:892: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
    2009.02.24 at 16:29:42:892: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
    2009.02.24 at 16:29:42:892: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
    2009.02.24 at 16:29:42:892: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@159ea8e
    2009.02.24 at 16:29:42:893: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ReplacementChar
    2009.02.24 at 16:29:42:893: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0x7c
    2009.02.24 at 16:29:42:893: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ecsFileKey
    2009.02.24 at 16:29:42:894: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 631CA4A49B1B4F88E04400144F96EEDE-274-1-31
    2009.02.24 at 16:29:42:904: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SeverityConfig
    2009.02.24 at 16:29:42:904: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
    2009.02.24 at 16:29:43:289: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Enter
    2009.02.24 at 16:29:43:290: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Leave
    2009.02.24 at 16:29:43:290: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
    2009.02.24 at 16:29:43:291: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = RF
    2009.02.24 at 16:29:43:291: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ecsFileKey
    2009.02.24 at 16:29:43:291: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 0A4DBD5D11FA872577F000001D6747B0
    2009.02.24 at 16:29:43:292: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SeverityConfig
    2009.02.24 at 16:29:43:292: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
    2009.02.24 at 16:29:43:294: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ecsFileKey
    2009.02.24 at 16:29:43:294: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
    2009.02.24 at 16:29:43:294: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValueBlob Param Name = ecsOptFileBlob
    2009.02.24 at 16:29:43:294: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValueBlob Param Name = ecsFileBlob
    2009.02.24 at 16:29:43:295: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ecsFilePath
    2009.02.24 at 16:29:43:295: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
    2009.02.24 at 16:29:43:295: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ecsFileBlob
    2009.02.24 at 16:29:43:295: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
    2009.02.24 at 16:29:43:296: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ecsFileBlob
    2009.02.24 at 16:29:43:296: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
    2009.02.24 at 16:29:43:297: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
    2009.02.24 at 16:29:43:298: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = RF
    2009.02.24 at 16:29:43:298: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
    2009.02.24 at 16:29:43:298: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Fulloutboundbatching = false
    2009.02.24 at 16:29:43:299: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit OutControlNumber: Interchange = 382580034, Functional Group = null, Transaction Set = null
    2009.02.24 at 16:29:43:299: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
    2009.02.24 at 16:29:43:299: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
    2009.02.24 at 16:29:43:299: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = RF
    2009.02.24 at 16:29:43:300: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
    2009.02.24 at 16:29:43:300: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Fulloutboundbatching = false
    2009.02.24 at 16:29:43:300: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit OutControlNumber: Interchange = 382580034, Functional Group = 25, Transaction Set = null
    2009.02.24 at 16:29:43:301: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
    2009.02.24 at 16:29:43:301: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument XML = 1
    2009.02.24 at 16:29:43:301: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument no result from XDataToNative
    2009.02.24 at 16:29:43:338: Thread-27: B2B - (DEBUG) iAudit report :
    Error Brief :
    5081: XEngine error - Invalid guideline.
    iAudit Report :
    <?xml version="1.0" encoding="UTF-16"?><AnalyzerResults Guid="{08FF2957-9002-DE11-AF0E-0003BA1C53E2}" InterchangeReceived="1" InterchangeProcessed="1" InterchangeAccepted="0"> <ExecutionDate>Tuesday, February 24, 2009</ExecutionDate> <ExecutionTime>04:29:42 PM (GMT)</ExecutionTime> <AnalyzerReturn>Failed</AnalyzerReturn> <NumberOfErrors>1</NumberOfErrors> <ErrorByCategory> <Category Name="Rejecting"> <Severity Name="Normal">1</Severity> </Category> </ErrorByCategory> <Status>Finished</Status> <DataFile> <FilePath/> <FileName/> <LastModified/> <FileSize/> <DataURL>file://</DataURL> </DataFile> <Interchange Guid="{86B52C57-9002-DE11-AF0E-0003BA1C53E2}" InterchangeAckCode="R" FunctionalGroupReceived="1" FunctionalGroupProcessed="1" FunctionalGroupAccepted="0" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>50127</Size> </DataXPointer> <GuidelineInfo> <GuidelineFile> <FilePath>ByteStream</FilePath> <FileName>ByteStream</FileName> <LastModified/> <FileSize/> <GuidelineURL>file://ByteStream</GuidelineURL> </GuidelineFile> <DetailGuidelineInfo> <IID>4</IID> <ID>ES</ID> <Name>ENVELOPE SEGMENTS</Name> <Standard>X12</Standard> <StdVersion>SERVICE SEGMENTS</StdVersion> </DetailGuidelineInfo> </GuidelineInfo> <NodeInfo> <Links> <Link Name="InterchangeSenderQual">ZZ</Link> <Link Name="InterchangeSenderID">Interchange Sen</Link> <Link Name="InterchangeReceiverQual">ZZ</Link> <Link Name="InterchangeReceiverID">Interchange Rec</Link> <Link Name="InterchangeControlVersion">00401</Link> <Link Name="Standard">X12</Link> </Links> <Properties> <Property Name="Standard">X12</Property> <Property Name="InterchangeAuthorizationInfoQual">00</Property> <Property Name="InterchangeAuthorizationInfo">Authorizat</Property> <Property Name="InterchangeSecurityInfoQual">00</Property> <Property Name="InterchangeSecurityInfo">Security I</Property> <Property Name="InterchangeSenderQual">ZZ</Property> <Property Name="InterchangeSenderID">Interchange Sen</Property> <Property Name="InterchangeReceiverQual">ZZ</Property> <Property Name="InterchangeReceiverID">Interchange Rec</Property> <Property Name="InterchangeDate">081023</Property> <Property Name="InterchangeTime">0830</Property> <Property Name="InterchangeControlStandard_RepeatingSeparator">U</Property> <Property Name="InterchangeControlVersion">00401</Property> <Property Name="InterchangeControlNumber">382580034</Property> <Property Name="InterchangeAckRequested">0</Property> <Property Name="InterchangeUsageIndicator">P</Property> <Property Name="DecimalSeparator">0x300x780x340x30</Property> <Property Name="ReleaseCharacter">0x300x780x320x35</Property> <Property Name="InterchangeChildCount">1</Property> <Property Name="InterchangeTrailerControlNumber">382580034</Property> <Property Name="SegmentDelimiter">0x2b</Property> <Property Name="ElementDelimiter">0x7e</Property> <Property Name="SubelementDelimiter">0x5c</Property> <Property Name="RepeatingSeparator">0x24</Property> <Property Name="ReplacementChar">0x7c</Property> <Property Name="InterchangeComponentElementSep">0x3f</Property> <Property Name="TPName">RF</Property> </Properties> </NodeInfo> <FunctionalGroup Guid="{72BE2D57-9002-DE11-AF0E-0003BA1C53E2}" FunctionalGroupAckCode="R" TransactionSetsIncluded="1" TransactionSetsReceived="1" TransactionSetsProcessed="1" TransactionSetsAccepted="0" RError="1" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>50127</Size> </DataXPointer> <GuidelineInfo> <GuidelineFile> <FilePath>ByteStream</FilePath> <FileName>ByteStream</FileName> <LastModified/> <FileSize/> <GuidelineURL>file://ByteStream</GuidelineURL> </GuidelineFile> <DetailGuidelineInfo> <IID>4</IID> <ID>ES</ID> <Name>ENVELOPE SEGMENTS</Name> <Standard>X12</Standard> <StdVersion>SERVICE SEGMENTS</StdVersion> </DetailGuidelineInfo> </GuidelineInfo> <NodeInfo> <Links> <Link Name="GroupSenderID">Interchange Sen</Link> <Link Name="GroupReceiverID">Interchange Rec</Link> <Link Name="GroupVersionNumber">00401</Link> </Links> <Properties> <Property Name="GroupID">PO</Property> <Property Name="GroupSenderID">Interchange Sen</Property> <Property Name="GroupReceiverID">Interchange Rec</Property> <Property Name="GroupDate">20080927</Property> <Property Name="GroupTime">235959</Property> <Property Name="GroupControlNumber">25</Property> <Property Name="GroupAgencyCode">X</Property> <Property Name="GroupVersionNumber">00401</Property> <Property Name="GroupChildCount">1</Property> <Property Name="GroupTrailerControlNumber">25</Property> <Property Name="TPName">RF</Property> </Properties> </NodeInfo> <Transaction Guid="{82E6EC01-9A01-DE11-9FFB-0003BA1C53E2}" TransactionAckCode="R" RError="0" NError="0" OtherWI="0"> <DataXPointer> <StartPos>0</StartPos> <Size>50127</Size> </DataXPointer> <GuidelineInfo> <GuidelineFile> <FilePath>ByteStream</FilePath> <FileName>ByteStream</FileName> <LastModified/> <FileSize/> <GuidelineURL>file://ByteStream</GuidelineURL> </GuidelineFile> <DetailGuidelineInfo> <IID>4</IID> <ID>841</ID> <Name>SPECIFICATIONS/TECHNICAL INFORMATION</Name> <GroupID>SP</GroupID> <Standard>X12</Standard> <StdVersion>V4010</StdVersion> </DetailGuidelineInfo> </GuidelineInfo> <NodeInfo> <Links> <Link Name="TransactionID">841</Link> </Links> <Properties> <Property Name="TransactionID">841</Property> <Property Name="TransactionImplementationReference"/> <Property Name="TransactionChildCount">80</Property> <Property Name="TransactionTrailerControlNumber">1234</Property> <Property Name="TransactionControlNumber">882534256</Property> </Properties> </NodeInfo> </Transaction> <FunctionalGroupErrors> <Error ErrorCode="{AD01846F-A68B-409D-A264-AA1ECAE7FBA3}" Severity="Normal" Category="Rejecting" Index="1" ID="50810000"> <ErrorBrief>5081: XEngine error - Invalid guideline.</ErrorBrief> <ErrorMsg>Failed guideline.</ErrorMsg> <ErrorObjectInfo> <Parameter Name="ErrorLevel">0</Parameter> <Parameter Name="Name">XData2Native</Parameter> <Parameter Name="_ec_dn_guid_">{72BE2D57-9002-DE11-AF0E-0003BA1C53E2}</Parameter> <Parameter Name="_ec_index">0</Parameter> <Parameter Name="ec_error_scope">Group</Parameter> </ErrorObjectInfo> <ErrorDataInfo> <Part1/> <ErrData/> <Part3/> <DataXPointer> <StartPos>0</StartPos> <Size>0</Size> </DataXPointer> </ErrorDataInfo> </Error> </FunctionalGroupErrors> </FunctionalGroup> </Interchange></AnalyzerResults>
    2009.02.24 at 16:29:43:340: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sErrorGuid = {AD01846F-A68B-409D-A264-AA1ECAE7FBA3}
    2009.02.24 at 16:29:43:341: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sDescription = Failed guideline.
    2009.02.24 at 16:29:43:341: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sBrDescription = 5081: XEngine error - Invalid guideline.
    2009.02.24 at 16:29:43:341: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ErrorLevel sParameterValue = 0
    2009.02.24 at 16:29:43:341: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = Name sParameterValue = XData2Native
    2009.02.24 at 16:29:43:342: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecdn_guid_ sParameterValue = {72BE2D57-9002-DE11-AF0E-0003BA1C53E2}
    2009.02.24 at 16:29:43:342: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ecindex sParameterValue = 0
    2009.02.24 at 16:29:43:342: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument sParameterName = ec_error_scope sParameterValue = Group
    2009.02.24 at 16:29:43:342: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument added Hash Key = {72BE2D57-9002-DE11-AF0E-0003BA1C53E2}
    2009.02.24 at 16:29:43:343: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin:processOutgoingDocument batch Position = 0
    2009.02.24 at 16:29:43:344: Thread-27: B2B - (ERROR) Error -: AIP-51505: General Validation Error
    at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2232)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1614)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:972)
    at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1166)
    at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
    at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
    at java.lang.Thread.run(Thread.java:534)
    2009.02.24 at 16:29:43:344: Thread-27: B2B - (ERROR) Error -: AIP-51505: General Validation Error
    at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2232)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1614)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:972)
    at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1166)
    at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
    at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
    at java.lang.Thread.run(Thread.java:534)
    2009.02.24 at 16:29:43:345: Thread-27: B2B - (ERROR) Error -: AIP-51505: General Validation Error
    at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2286)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1614)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:972)
    at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1166)
    at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
    at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
    at java.lang.Thread.run(Thread.java:534)
    2009.02.24 at 16:29:43:345: Thread-27: B2B - (ERROR) Error -: AIP-51505: General Validation Error: Error -: AIP-51505: General Validation Error
    at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2286)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequestPostColab(Request.java:1614)
    at oracle.tip.adapter.b2b.msgproc.Request.outgoingRequest(Request.java:972)
    at oracle.tip.adapter.b2b.engine.Engine.processOutgoingMessage(Engine.java:1166)
    at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:833)
    at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:400)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: Error -: AIP-51505: General Validation Error
    at oracle.tip.adapter.b2b.document.edi.EDIDocumentPlugin.processOutgoingDocument(EDIDocumentPlugin.java:2232)
    ... 6 more
    2009.02.24 at 16:29:43:346: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processOutgoingMessage B2BDomainException
    2009.02.24 at 16:29:43:346: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Error Message: Error -: AIP-51505: General Validation Error
    2009.02.24 at 16:29:43:346: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Enter
    2009.02.24 at 16:29:43:350: Thread-27: B2B - (DEBUG) AccessRepo:findBusinessMessageByB2BMessageId Found Successfull message with B2bMessageId : 86984217 and ProtocolMessageId 86984217
    2009.02.24 at 16:29:43:351: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Wire message not found.
    2009.02.24 at 16:29:43:351: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Updating business message error information
    2009.02.24 at 16:29:43:356: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateWireBusinessToErrorState Exit
    2009.02.24 at 16:29:43:356: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updating Native Event Tbl Row
    2009.02.24 at 16:29:43:356: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
    2009.02.24 at 16:29:43:359: Thread-27: B2B - (DEBUG) AccessRepo:findBusinessMessageByB2BMessageId Found Successfull message with B2bMessageId : 86984217 and ProtocolMessageId 86984217
    2009.02.24 at 16:29:43:360: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
    ** DbAccess:updateNativeEvtTblRow:tip_wireMsg wiremsg not found
    2009.02.24 at 16:29:43:360: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException notifying App
    2009.02.24 at 16:29:43:360: Thread-27: B2B - (DEBUG) Engine:notifyApp Enter
    2009.02.24 at 16:29:43:361: Thread-27: B2B - (DEBUG) Enqueue Engine AQJMSCorrelationID = 63ADA032E94517C7E04400144F96EEDE
    2009.02.24 at 16:29:43:361: Thread-27: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
    <Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <correlationId>86984217</correlationId>
    <b2bMessageId>86984217</b2bMessageId>
    <errorCode>AIP-51505</errorCode>
    <errorText>5081: XEngine error - Invalid guideline.</errorText>
    <errorDescription>
    <![CDATA[Machine Info:
    Failed guideline.  ]]>
    </errorDescription>
    <errorSeverity>2</errorSeverity>
    </Exception>
    2009.02.24 at 16:29:43:362: Thread-27: B2B - (DEBUG) AQJMSCorrelationID = 63ADA032E94517C7E04400144F96EEDE
    2009.02.24 at 16:29:43:373: Thread-27: B2B - (DEBUG) Engine:notifyApp Exit
    2009.02.24 at 16:29:43:373: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:handleOutboundException Updated the Error Message Successfully: Error -: AIP-51505: General Validation Error
    2009.02.24 at 16:29:43:373: Thread-27: B2B - (DEBUG) DBContext commit: Enter
    2009.02.24 at 16:29:43:390: Thread-27: B2B - (DEBUG) DBContext commit: Transaction.commit()
    2009.02.24 at 16:29:43:390: Thread-27: B2B - (DEBUG) DBContext commit: Leave
    2009.02.24 at 16:29:43:391: Thread-27: B2B - (DEBUG) oracle.tip.adapter.b2b.data.MsgListener:onMessage Exit

  • Standard Idocs for the EDI's

    Hi,
      Where can i find the IDOCs' for the EDI's
    812, 816, 822, 846, 860, 867, 870 and EDIFACT INVRPT
    Is there any specific tcode to find the IDOC's for the particular EDI's ?

    Hi,
    Please check my previous reply in this thread.
    Re: IDOC Types and their equivalent messages in EDIFACT and ANSI X12
    Regards,
    Ferry Lianto

  • EDI singelton pattern

    I am using singleton pattern in EDI. To find out last message I use to check message type . If it is 997 then I took  BTS.InterchangeSequenceNumber for it. As 997 will be last message.
    But one of my client , I pull by FTP . There I have 2 files for same transaction (870), where sender and receiver are different.
    When I pull this two file and process, probably two instance of orchestration starts.  Inside I check for 997. Many times I saw zombie occurs.  My theory is as I am looking type 997 it don't know which 997 it should be and so it stops there and
    all other messages become zombies.
       Big problem here is my two files have different size, so processing time is always different. One solution could be write two different FTP script to poll and schedule different time.  
       But want to check is there any other criteria I can add to check for 997 which will make sure this 997 instance is correct.
    Please let me know is my theory is correct and what I can do to avoid it.

    I implement correlation based on interchangeid. Weird thing I am observing one of customer file is creating zombie error.Not sure it is real zombie or not as when I process same file again in same environment or  different environment, it process all
    without such error.
       I am not understanding why exactly it is happening and how it could resolve. One different in file compare to other vendor is they send some value in PO1 segment where get some validation fails.Not sure it could be reason.
    In singelton timeout is too big that is 15 minutes and correlation is based on interchangeid. So not understanding why it could happen? Is 997 can come earlier than other messages when validation fail happen or something. Please help me to understand it
    solve it

  • 870 document.

    Hi All,
    Can you please give me idea on how to do the following from ABAP side.
    Thanks
    Veni.
    870 document.
    The 870 document is the "partial shipment status" notification.
    We established that when Sales create the delivery document in SAP and after pick request has been confirmed, then SAP will kick off an outbound ORDERS01 document that contains partial shipment information.
    This process will be outbound from SAP ORDERS01 mapped to the EDI ANSI 870 document.
    Please check the configuration for 940 program processing
    EDI  will map the ORDERS01 IDOC structure to the ANSI 870 version in BIS TRANS QA based on Target's PRE specs.
    Thanks

    You should run your data file via the analyzer and make sure the HL loops are getting linked properly, i.e. to their respective loops / segments.
    If you copied and pasted the HL 3 times, you may need to use something in HL segment as a key field. Most likely HL segment, element position 03. In the document editor for HL03 under advance setting you will something called Key Type. You should set this to list. Then you should make sure that in each of your 3 HL loops you have included / excluded proper code values for HL03. This will then make sure that based on HL03 the data is getting linked to the proper HL loop in the guideline.
    Once you have this working and verified via the analyzer then you should make sure the proper ecs file is used in B2B during run-time.
    NOTE: making this change can also impact XSD - so you should re-create your XSD.

  • Automatic PO creation through EDI

    Hi experts,
    Please clarify me on the setup of creating PO's thru EDI in Purchasing automatically once PR is created in the system.
    My client is more or less a trading company. They buy from vendor & sell to their customer, like third party order process.
    So they create Sales Order & then PReq is created through ME57 & then they create PO through ME59.
    They want to create PO's automatically thru EDI as this can speed up the process so as the vendor is also looking for creating SO in their BaaN system automatically.
    I have configured the EDI setup for creating PO manually, meaning when I create manual PO the idoc xml file is ready for transfer.
    But I am looking for the steps so that once they create the PReq, EDI should automatically create PO in SAP & the idoc should be ready for transfer.
    Please suggest if this can be done thru any BAPI or BDC programs.
    Thanks in advance !
    Priyadarshini

    Hi Krishna,
    This is for automatically creating normal PO thru PReq. Since I have setup the EDI configs for creating PO thru manual process  thru Me21N then idoc gets generated.
    But my client is looking for the idocs to be generated automatically once the PReq are created thru Me57.
    is there a way?
    Rgds,
    Pri

  • EDI for creation of Sales Order and sending copy of Invoice

    Hello Experts,
    I am working on EDI. We have a scenario, where the purchase order created in the 3rd party system has to be converted into a sales order in our SAP system.
    Then, the regular flow would follow uptil delivery and creation of invoice in SAP.
    We have to send a copy of this Invoice back to the 3rd party system.
    So, in effect, we would have EDI at two points, while capturing the PO from the 3rd party and another when sending a copy of the Invoice back to the 3rd party.
    Please advise on how to go about implementing EDI in the above mentioned scenarios.
    Regards,
    Divyata

    Use EDI 850 Process code ORDE FM IDOC_INPUT_ORDERS for PO (Inbound)
    use EDI 810 Process code SD09  FM IDOC_OUTPUT_INVOIC for Invoic (Outbound)
    Edited by: srini korada on Jun 9, 2011 4:51 PM

Maybe you are looking for