Inbound edi problem

hi ,
   i have problem with inbound EDI for po acknowledgment(855) ,message type used ordrsp process code ORDR and basic type is orders05. i am testing the idoc in we19.for the segment E1EDP19 i specified qualifier 001 (means Material number used by customer) and IDTNR (marterial no) matnr in PO  it runs successfully and idoc is posted to application.but if i specify qualifier- 002 (means Material number used by vendor ) it is not working and idoc is not posting to application with message ‘Material number differs from that of ordered material’. I have even assign value IDTNR (material no) from material info record i.e. vendor material no from table EINA but still idoc is not posting to application. Can anyone spot why this error occurs and give the solution.Is there any other table which maintains vendor material no. is there any OSS note available for this error?
Relevant points will be awarded for the solution.

This might be due to the material inventory being locked if these idocs contain the same material. The ideal would be to process these sequentially. if its process immediately in WE20, then multipe idocs can get processed simultaneously and ending in error if all are using the same material.

Similar Messages

  • Inbound EDI 852

    Can anyone of you please tell me about the inbound edi 852?
    What would the IDoc file look like? What are the mandatory fields and what values should go in there etc...
    Also , what transaction or tables are being accessed in SAP to post this data.
    Your help is much appreciated.

    Hi Sara,
    In the E1ADRM1 segment, what values should we get?
    The values should be 'WE' for customer and 'LF' for supplier.
    Also where r the checks performed ? VOE2 , VOE4 ?
    The data check is performed in FM IDOC_INPUT_PROACT.
    Do you have any sample Idoc file for inbound 852?
    Sorry, I don't have any IDoc sample. But you can use WE19 (Test tool) to simulate the IDoc and try to process using standard FM IDOC_INPUT_PROACT.
    Again, hope this will help to start with.
    Regards,
    Ferry Lianto

  • Inbound EDI multiple customers using 1 partner profile

    I would think that it's possible to set up a single partner profile in WE20 through which you can process multiple idocs against multiple customers for order processing. Can anyone guide me on how to achieve this.
    Thanks, Mart

    Absolutely. You could have an EDI Partner called 'GENERIC' for example, and could use that to process inbound EDI Sales Orders. Obviously you would need an identifier to represent the correct Customer account, ideally this would be the Sold-to number. If it's not your Internal Sold-to, but another unique number, then you should be able to add mapping via transaction VOE4 to table EDPAR. I.e the Customers sends an external number 123 representing their Store Id, you map that back to your internal Customer Number. Only trouble with this is if two different Customers had the same external Id, as you would have no control over that. For our generic EDI Partners, the Customer Number is mandatory.
    Cheers, Paul.

  • Unable to process inbound EDI docs from TP-multiple Host ID's,1 transaction

    Issue:
    Unable to process inbound EDI documents from trading partners
    (Same doctype and revision, but diff receiver ID’s for host)
    Host: ISA ID’s are HOSTA, HOSTB
    Transaction: X12, 210, 5010
    Trading Partner A: sends EDI document with these values
    Interchange Sender ID: TPA
    Application Sender's Code: TPA
    Interchange Receiver ID: HOSTA
    Application Receiver's Code: HOSTA
    B2B setups are as below
    Business action: Process_210
    Operational Capability for Trading Partner A : Process_210_Initiator It has
    Interchange Sender ID as TPA
    Interchange Receiver ID as TPA
    Application Sender's Code: TPA
    Application Receiver's Code: TPA
    This creates a Process_210_Responder for HOST
    It has
    Interchange Sender ID as HOSTA
    Interchange Receiver ID as HOSTA
    Application Sender's Code: HOSTA
    Application Receiver's Code: HOSTA
    Validated Agreement and deployed, Result is success and everything works fine until here
    Note: B2B validates taking everything from Process_210_Initiator except the Interchange Receiver ID that it gets from the Process_210_Responder
    New Trading Partner B also sends us an X12, 210, 5010 but he uses Receiver ID as HOSTB
    Trading Partner B: sends EDI document with these values
    Interchange Sender ID: TPB
    Application Sender's Code: TPB
    Interchange Receiver ID : HOSTB
    Application Receiver's Code: HOSTB
    B2B setups are as below
    Business action: Process_210
    Operational Capability for Trading Partner B : Process_210_Initiator It has
    Interchange Sender ID as TPB
    Interchange Receiver ID as TPB
    Application Sender's Code: TPB
    Application Receiver's Code: TPB
    This doesn’t create a new Process_210_Responder for HOST It has
    Interchange Sender ID as HOSTA
    Interchange Receiver ID as HOSTA
    Application Sender's Code : HOSTA
    Application Receiver's Code : HOSTA
    Validated Agreement and deployed, Result the document fails with error
    Validation of Interchange parameters failed. Please verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid
    Upon looking at the log file it fails, as the Interchange Receiver ID in data is HOSTB where as in Process_210_Responder it is setup as HOSTA
    Work Around that we tried, but could not succeed
    Create a new business action called Process_210_HOSTB, created a new Document Protocol Revision X12_5010_HOSTB,Created a doc type 210 version 5010 under that
    Used this new Business action for Trading Partner B so the new setups look like this
    Business action : Process_210_HOSTB
    Operational Capability for Trading Partner B : Process_210_HOSTB_Initiator It has
    Interchange Sender ID as TPB
    Interchange Receiver ID as TPB
    Application Sender's Code : TPB
    Application Receiver's Code : TPB
    This creates a new Process_210_HOSTB_Responder for HOST It has
    Interchange Sender ID as HOSTB
    Interchange Receiver ID as HOSTB
    Application Sender's Code : HOSTB
    Application Receiver's Code : HOSTB
    Validated Agreement, but could not deploy as I was getting AIP-11016 SQL error , may be integrity constraint issue
    Note: I was able to deploy this agreement if I change the Document Type from 210 to something else like 210_new, but since the document is EDI I can’t have the Document Type as anything except 210

    Ramesh,
    Sorry for the delay , but this was the first thing I tried and it didn't work, I tried again just to be sure, it didn't work I am getting this error
    When group Receiver ID didn't match
    "Validation of Group parameters failed. Please verify all the Group parameters in the B2B configuration match the Group parameters in the message. The following parameters do not match the configured parameters in B2B"
    In addition, when Interchange Receiver ID did not match
    "Validation of Interchange parameters failed. Please verify all the Interchange parameters in the B2B configuration match the Group parameters in the message. Make sure that the ecs file for this Interchange is valid"
    Here is the log file extract
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Enter
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl validateEnvelope = true
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:ISelectorImpl Leave
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@12d8ecd
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SeverityConfig
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@1fa5e5e
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Enter
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:reset Leave
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@497062
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverQual, val = [02]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [02]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderID, val = [REMOTETP]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [REMOTETP]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeReceiverID, val = [SLCY]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [SLCY]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = Standard, val = [X12]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [X12]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeControlVersion, val = [00200]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [00200]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Interchange]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = InterchangeSenderQual, val = [02]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [02]
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = true
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = ecsFileKey
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = 60DD87849FFE4147BFCEB66842A33298-26-1-4
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValueBlob Param Name = ecsOptFileBlob
    2008.07.28 at 14:31:24:917: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValueBlob Param Name = ecsFileBlob
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getStream Enter
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getStream Leave
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = SeverityConfig
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = null
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:setControlNumber sName = Interchange, controlNumber = 210011217
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:setControlNumber return = true
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = RemoteTP
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit NodeGUID = {156BEDFC-931E-4923-840D-3AC0BAB670F2} position = 0
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Enter
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:cloneSelector Return = oracle.tip.adapter.b2b.document.edi.ISelectorImpl@1b5c22f
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Enter
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupReceiverID, val = [STMSLCY]
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [SLCY]
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup Value and doc parameter don't match2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupVersionNumber, val = [005010]
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [005010]
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = ec_DataNodeName, val = [Group]
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup key = GroupSenderID, val = [REMOTETP]
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup param = [REMOTETP]
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = false
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doLookup return = false
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Param Name = TPName
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:getValue Value = RemoteTP
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Enter
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit getLookUpError Key = key = [GroupReceiverID] value = [STMSLCY] param = [SLCY] Value = null
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit NodeGUID = {6EE88EFC-B084-4FA8-8EE8-8C7BD397E9F1} position = 0
    2008.07.28 at 14:31:25:011: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.edi.ISelectorImpl:doCommit Leave
    2008.07.28 at 14:31:25:073: Thread-10: B2B - (DEBUG) iAudit report :
    Error Brief :
    5082: XEngine error - Guideline look-up failed.

  • Inbound EDI Issue

    Hi Experts,
    We are using SAP PI 7.0 with AS2 System (Seeburger) in Quality System to exchange EDI Documents with our Customers and 4PL partners. We are able send EDI Documents (Outbound) to our partners successfully but facing issues related to Inbound EDI Documents (Incoming) i.e., when customers/4PL Partners are trying to send the EDI Documents it is not reaching to our Test System.
    We thought it could be Web Dispatcher issue and restarted it but that didn’t solve the issue. In XI system no changes have been made in IR and ID. Below is the error message our partner is getting while sending the EDI Documents.
    Response: "400 Connection Failed (VLProxy.java.net.ConnectException: Connection timed out: connect)"
    Result "Error""400 Connection Failed (VLProxy.java.net.ConnectException: Connection timed out:connect)" Source file not deleted
    Your Help is highly appreciated.
    Regards
    Faisal.

    Hello Abdul,
    I have to agree with Harish regarding the Connection Timeouts. To verify if the incoming AS2 requests reach the AS2-Server or already have some issues on network-level, I would recommend to take a look at the AS2-Trace (and set the trace-level to debug)
    Attached a quick description to setup the Logging...
    Easy Log Configuration - How To Guide for Seeburger Adapters
    Some question to consider would also be:
    Did it work before and suddenly stopped working or are you just setting up this connection initially ?
    Are other partners able to send to your system ?
    Kind Regards
    Stefan

  • Issue with inbound EDI idocs

    Hi
    we are receiving inbound EDI idocs throgh third party.  Third party received EDI file having 5000 transactions .
    It was transalated same number of idocs text document and posted in SAP.  But after 4 hours same file processed in SAP.
    Third party saying they sent only once .
    Is there any way in SAP file placed two times or one time .
    Any table stores this information . we are using TRFC port .  I know EDIF12 table but it was not used here.
    Any clue on this.
    Thanks

    HI
    ANY Clue on this issue

  • How to configure inbound EDI invoice

    Hi all,
    Can any one provide me the steps to configure inbound edi invoice.
    Regards,
    Marella.

    Hi Arif, yes I did read that one.
    after reading that I got those doubts.
    In general, please help me to have a clear understanding in the following points.
    We have 4.6c.
    Please see my quries below and help me.
    SAP Tax codes
    Can an inbound MM invoice contain items belonging to different POs?
    Can the tax codes be different for different items in the same invoice?
    How to get tax codes for invoice items? Do we take these from the corresponding item in the PO? or from material master or from vendor master or some where else?
    What will be the tax code at the invoice header level?
    Regards,
    Marella.

  • Inbound edi

    hi,
    can any one say me step by step process for inbound edi.

    Following link is helpful
    http://www.erpgenie.com/sap/sapedi/index.htm
    Also in SAP help, read the following section
    http://help.sap.com/saphelp_nw2004s/helpdata/en/dc/6b7eee43d711d1893e0000e8323c4f/frameset.htm

  • Inbound EDI 820

    Hi Guys,
    What is the relevant SAP tables that holds Inbound EDI 820 (PEXR2002) in SAP. Your help is highly appreciated....

    [Does this posting help?|IDOCS;

  • Custom delimiters in inbound EDI

    Hello All,
    Can the SAP B2B Add-On and its Converter Modules handle custom delimiters in case of inbound EDI Message.
    We have scenarios where partners can choose to use their own delimiters.
    Does the Converter Modules handle them automatically or there is a place to configure these delimiters.
    I guess for the outbound EDI, the custom delimiters can be set in the mapping and converter module produces the EDI output accordingly.
    Thanks.
    Best Regards,
    Sudharshan N A

    Hi Sudarshan,
    In the ISA segment , we have
    first field - D_DATAELEMENTSEPARATOR
    16th field- Component Element Separator and
    17th- D_SEGMENTTERMINATOR
    There are a few restrictions on choosing custom delimiters.
    1) special (escape) character of length =1
    2) should not be an alphanumeric character
    3) not an ASCII symbol whose hex value is out of range (hex length > 3)
    All such exceptions are handled by x12 converter at conversion level.
    Your EDI file can have control characters eg. NAK (which are not valid for an XML representation in the PI box)
    but this again is handled at converter level it eliminates the control character and treats it as default
    For more information on this, please see Separators in ANSI X12 EDI Message
    Please let me know if this answers your question,
    Kind Regards,
    Pooja

  • Chargeback Inbound EDI

    Hi All
    Present i am working on chargeback inbound EDI.
    In this data is comming to Idoc -Orders05.
    my requirement is that When Partner function'RR'  Then customer Addres details has to be changed or overwritten
    Sehment E1EDPA1 contain all the data ..
    When i degub one exsisting idoc the addres data is comming from idoc and it is updating the sales order.there the partner function is "YR' address uploaded to sales order item level.
    Here i hav a lit bit confusion that whether i hav to develop any thing for this or it is taking automatically in SAP.
    Any one hav idea on this plz giv me an idea wht is the process i need to fallow.

    Hi,
    try this way...
    If control_record_out-IDOCTP = 'ORDERS05' and
    control_record_out-MESTYP  = 'ORDERS'.
    "write your logic in include 'zxvedu03'
    endif.
    Prabhudas

  • Change inbound EDI order types

    Hi Gurus,
    Is there a transaction where in we could change inbound EDI orders from customers to process warranty orders.
    Thanks
    Anusha

    Look at this blog..Will tell you how to troubleshoot your IDoc issues..
    <a href="/people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process of ALE Process</a>
    Raja T

  • Outbound EDI 860/Inbound EDI 865 Integrated to JDE 9

    Has anyone successfully integrated an outbound EDI 860 and an inbound EDI 865 into JDE 9?

    Hi,
    I think Order05 should work for you. Let me try to answer your questions
    1) which IDOC message type should i use for this transaction, to send an 865 ?
    A: ORDERS. Basic type should be ORDERS05
    2) What program and Form routine should i use to send an 865 , while configuring the output type in V/30 ?
    A: RSNASTED. Form routine: EDI_PROCESSING which is pretty standard. You can use BA00 output type which is standard again.
    3) Please advice me the SAP setting we need to do for an 865 (order change Ack) .
    A:  i. You should have the EDI settings done by your Basis team. (Else Idocs will not generate)
         ii. You should create a partner profile in WE20 for KU customer, outbound.
        iii. In the Outbound options mention the port and other stuff. Maintain the message control. Note that you put in BA00 there in  the message type and put the right process code (Should be SD01).
    I think these are the only things. Try and this should work for you.
    Regards,
    Mukund S

  • SO via inbound EDI. partner problem LIFNR - PARTN

    Hi,
    Working on PO -> SO interface. Question on populating VOE4 (EDPAR).
    in the inbound IDOC I have this segment:
    E1EDKA1:
    PARVW: AG
    PARTN: external customer number (in my case it is purchasing organisation)
    LIFNR: 'blank'
    In forums it is told that segment LIFNR should be populated by external customer number.
    What is the difference between PARVW and LIFNR? Does VOE4 look at PARTN for substitution?
    in my case seems that it ignores PARTN at all..
    Thanks,
    Artashes

    I think what you need is the following.
    On the EDIDC record, field SNDPRN, you need to have the Sold To customer number mapped.  You'll also need to have the SoldTo setup in WE20 with a partner profile.
    You can send in an Order to SAP with a Logical System in the above field but you then have to have the PARTN fields filled in with the correct Sold To Ship To.  Which you typically would not have.
    On the KA1 segments, you'll need two KA1 segments, one for the Sold To and the Other for the Ship To.  Since you already would know the Sold To since you put it in the EDIDC record, just fill it in the PARTN field, unless your partner wants their store number back.  Personally I would set it up this way with the external store number.
    So you'll want a KA1 record with the AG qualifier for the Sold To and the LIFNR field filled in with the partners external number for the Sold To.  This could be the Duns number or N1/04 code. 
    On the second KA1 for the ship to, set the qualifier to WE for Ship To and then fill in the LIFNR with the external store number.
    You'll now need entries in VOE4 for each KA1.  Customer would be the same as the Customer in the EDIDC record, field SNDPRN.  external function is either SP or SH.  External Number is the external number, either the DUNS number for the Sold To (Most likely) or the N1/04 code for the ship to.  Int No is the Internal customer number for the Sold To and Ship To. 
    Sold To 55555
    Customer Sender ID/Dunning #  123456789
    External Ship To Store #  321
    WE20 setup for  Sold To 55555
    VOE4 setup for 55555    SP    SOLD TO   123456789  55555
    VOE4 setup for 55555    SH    SHIP TO     321              55555
    I think what SAP Messed up on is the fact that we should not have an external cross reference or hard coding mechanism to populat the SNDPRN  with a customer number for inbound transactions in order for the EDPAR table to work correctly.  You can have a logical system at the EDIDC level but would need to populate the correct Sold To and Ship To on the KA1 segments.  When using the LIFNR fields, SAP Uses the SNDPRN, External Partner Number and Partner Function on the KA1 record to determine the Internal Customer Number. 
    If anyone else has an opinion please let me know.   I would love a way to be able to cross reference the Dunning Number for a partner to a Sold To within SAP and allow for the LIFNR fields to be used for the Ship To's.

  • EDI Inbound Idoc problem

    Hi,
    We are facing an issue with Inbound IDoc.
    We have a PO inbound idoc which is in status '53' but the PO document did not get created.
    Can you please help us if anyone faced similar issue.
    Thanks,
    Anil

    Hello,
    sounds strange.
    1. check the status record of 53 Idocs you should find a message like:  Standard oder nnnnnnnnnn has been saved.
    2. If order number nnnnnnnnnnn does not exists  check transaction SM13, ST22 for errors.
    3. for testing change inbound options in WE20 to <trigger by background programm>  and book the idoc in forground.

Maybe you are looking for