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

Similar Messages

  • EDI 860 PO Change and 865 PO Change Acknowledgement

    Currenlty we handle our EDI 860 PO Changes not via the ORDCHG Message Type but rather we send the change via email and the users manually change the order. This was done because the users did not want SAP to automatically update the order. Now we have a mandatate by a customer to do the 865 PO Change Acknowledgment. Can anyone tell me if there is a standard way to do the 860 and 865 in SAP, without having the 860 ORDCHG automatically update the order? Any help would be great.
    Thank You
    Dave Ackerman

    Is that the only difference in the EDI mapping for 850 PO change compared to 850 PO?
    I still don't understand how the system will know which sales order corresponds to the incoming PO change. In the TCode VA02, we have to input the Sales Order # in order to change the sales order. How would the system know how to do this when a PO change is sent through EDI?

  • Request to send EDI 865 only EDI 860 is received

    Hello SAP Gurus,
        We have a request from a customer to return an order response messages (EDI 865) only when they send in a Change Order message (EDI 860).
    Can anyone please let me know whether is is possible.
    thanks,
    Krishna

    Hi Dan,
    One possibility which immediately comes to mind is using the user exit: ZXM06U02.
    This exit is trigerred while sending the EDI from PO. You can place a logic in here, to show an error if there is already a IDOC sent for that PO.
    We are using this exit for doing some other custom check.
    I hope this helps.
    Kind Regards,
    Prakash

  • 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

  • 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

  • EDI idoc inbound statuses

    We're running SAP in a different partition from EDI (TrustedLink) on an iSeries.  I'm getting inbound documents just fine, but no inbound statuses.  I see that the status documents make it over to the SAP partition but they're not visible in WE05 - so all of my successful outbound 850s are at at status of 18 & that's it.  I've looked at authorities etc but am still missing something.  Thanks in advance if anyone can point me in the right direction.  Susan

    try this
    enter tcode we21,
    Go to system , click on status
    Then you can see the programe name , Double click on programe name, you can see ABAP editior screen.
    Then you can see go to tan and click on object directry Tab.
    You can see package for which object is created.
    Now use tocde Smod, select F4 for enchancement , in package you can enter SED.
    You can get follwing user exit
    Exit name Short text
    SIDOC001 Customer function for module pool EDI1
    SIDOC002 CA-EDI: Exits in Function Group EDI6 (Partner Profile)
    Technically all EDI-IDOC inbound and outbound programs are wirtten as FUCNTION MODUELS.In the every fucntion moudle you can find large number of user-exits.For outbound idoc after filling every segment you have a user exit like CALL CUSTOMER FUNCITON '001'.You can find by using the keyword search CALL CUSTOMER FUNCITON in that funciton module.
    In inbound also you can find after every segment you can find user-exit.
    For funciton module search you can search in se37 by using idoc type,For example ORDERS01 search in se37 by using *ORDERS8.
    regards,
    sapsd

  • 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.

  • Park inbound EDI Invoices on iDoc failure from a workflow?

    Hello all,
    We have seen note 501524 that talks about parking inbound invoices by default.
    Our situation is this. We are expanding our use of EDI for inbound invoices. As such we would like to automate the validations steps as much as possible. To date with our limited use we have set up a workflow to notify on idoc failures and then a few agents have access to BD87 to make the idoc right and reprocess. We don't want to continue this process.
    Our preference would be to continue to allow the iDoc to fail, the workflow fires but at this point we communicate the failure to the appropriate person and park the invoice.
    Does this sound like a reasonable approach?
    Can we even park a red lighted iDoc?
    Once parked can the invoice be dealt with without using BD87?
    Has anyone ever tried this?
    Thanks,
    Doug

    Hi Ralph,
       In my opinion, you must have a PO Number for Invoice if you want to use standard functionality. You will probably need to create IDOC using an ABAP program which reads this file and search for PO based on the information available to you. I also notice that you are missing material number as well, how do you match the item number in the PO ?
       I don't see a way aroung without writing an ABAP program to handle this logic, but you can still use IDOC ( which comes with the standard processing logic and that is a big advantage ) so that you need to write only the PO matching logic.
      or if you are not inclined to write a separate program for uploading file into SAP and formatting IDOC, you can write your own process code (FM)for INVOICE01. Inside this process code (FM), you can put your PO matching logic and then call standard FM (process code). This is what I usually do.
    Cheers,
    Sanjeev
    Cheers,
    Sanjeev

  • 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

  • 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

  • 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.

  • EDI Seperator Issue for INbound EDI Scenario

    Hi Experts,
    Am using latest service pack and SP12 and patch 5 it seems.
    Still am getting same error.
    Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: senderChannel 'fbesfd4b25331eabe67a1d04ec4acf': Catching exception calling messaging system
    I configured simple scenario.
    I have set up the 2 ID flows :
    - Partner 1 (Sender File) > (Partner 2) Receiver EDISeprator (didnt used any conversion modules)
    - Partner 3 (Sender EDISeparator with Edifact Module) > to SOAP sending B2B XML to another PI system.
    Done B2B **** Pit file Association.
    Tested in B2B COckpit and it is working fine but working in E2E
    Also note that this is not a Custom EDI. This is just Order D93A Standard message file containing multiple Orders in same file.
    Also let me know one thing Is it required to make KEY Associations for standard EDIFACT Structure Secnario as well?
    I understand from the above error that is able to lookUP the 2nd flow EDI Sender Channel ID but it is unable to deliver/despatch the message content to that flow.
    KINDLY HELP ME>

    Hi Dimitri,
    I tested again now with changing control key association.
    am getting below error::
    Message could not be forwarded to the JCA adapter. Reason: com.sap.aii.adapter.ediseparator.ra.integration.DispatchException: Message cannot be dispatched: Message cannot be dispatched: senderChannel 'a9e6939add043c39883683175abea3ba': Catching exception calling messaging system
    I delcared key associations for both flows.
    FILE-->EDI Seperator and EDI Seperator to SOAP.
    Could you please review it and guide me?
    Regards
    Amarsrinivas Eli

Maybe you are looking for

  • Migrating from SonicWALL to RRAS - questions on functionality for business network setup & monitoring

    At my organization we are planning to move away from using SonicWALL and using Microsoft Server 2012 RRAS to handle IPv4 NAT routing and VPN connections for remote employees.  I am trying to plan for all the functionality I currently have in our Soni

  • How do I view Time Machine from a different Mac?

    Using Pondini's excellent tutorial, I navigated to the Time Machine backups from an earlier Mac (on the same "Time Machine" partition of an external HDD.) First, I was at the level of Macintosh HD/Users, and I could see my earlier Mac's users, but th

  • How to use e4x to extract complex data like this ?

    The xml object structure like the following : <TEXTFORMAT LEADING="2">     <P ALIGN="LEFT">         <FONT FACE="Verdana" SIZE="16" COLOR="#0B333C" LETTERSPACING="0" KERNING="0">            First Item                       <FONT SIZE="10">           

  • ORA-29516 Aurora Assertion Error

    Has anyone encountered Auror Assertion error while using Java and PL/SQL with loadjava utility? Thanks for any suggestions/comments.

  • Download Lion without installing

    I have a 24 and 27 inch iMac. The 24 inch iMacs drive died so I put a new one in. I do not have the osx disks that came with it, lost miss placed who knows. My 27 iMac as 10.6.7, I can not upgrade to 10.6.8 due to some work related software that will