IDOC WMMBXY outbound - R3 idoc posting error

Hi! All
In a file(inbound) to IDOC scenario using the IDOC WMMBXY.WMMBID02(outbound), i have the following status notification and status grouping is also in red when the idoc is posted to R3...
IDOC: 0000000000605076 Status: Application document not posted
Qty and / or "delivery completed" ind. or final issue ind. are missing
It would be very helpful, if you can let me know ...what i did wrong in the mapping/design.
Thank you,
Patrick

Jones,
The error states:
<i>Qty and / or "delivery completed" ind. or final issue ind. are missing</i>
So please check in the idoc whether you are passing the values for Qty and "delivery completed" or final issue ind. I think to post into R3 you need to have these values.
Regards,
---Satish

Similar Messages

  • Segment mising in IDOC for outbound with status 3

    Hi ,
    Segment mising for IDOC for outbound and IDOC status in 03 . What could be the possible reason for segment missing ?
    Edited by: Raghavendra Balegar on Jan 11, 2010 8:26 AM

    how do you create the IDOC?
    which IDOC?
    what segment?

  • GR posting using inbound Idoc against Outbound delivery

    Hi,
    We are doing SAP ISR integration with third party POS and there we have a scanario where we have to post GR against outbound delivery using inbound Idoc. Can anybody help me out, how can we do it.
    In SAP processing would happen using MIGO against outbound delivery number and movement type 101. We tried the same with Idoc WMMBXY message type but not suceed.
    Looking for positive reply.
    Regards
    Vikrant pathak

    Hi,
    You can never do a GR against an outbound delivery, but where as you can do a GR against PO with reference to corresponding sales order with special stock indicator.
    That means when the GR is done the goods what ever you have received is going to be blocked against the corresponding sales order and when you do the outbound delivery against the sales order stock is already available and the goods issue will happen smoothly without any errors.
    We have implemented the same in my earlier project.
    Thanks,
    Mahesh.

  • There is large time differnce in Outbound IDoc's for Interest Run posting

    Hi Experts,
    When i posting Interest Run (T.code : FINT) i am executing for a range of Customers(For 4500 Customers)
    using Background Job it took nearly 3 days to execute the job in Production and i found that there is
    no Partner Profile in WE20,IDoc's went in Error.Until this its fine.
    The major problem is there are group of 100 idoc's created in no time span and it took 4 hrs time gap to create
    another idoc 100 more idoc's.
    In between these 2 bunch of idoc's another 700 idoc's created for different message types.
    Can you please let me know why there is that much time gap for the same message type for Interest Run.
    Thanks in Advance.
    Regards,
    Sudhakar Reddy Allam.

    Bhishma,
    Just clarrification for you...when you said..
    "R/3 sends an IDOC with IDOC number 100. XI (by default) submits this IDOC to the 3'rd party system with IDOC number 200 (it's own internally generated number)."
    Here Idoc number 100 is outbound idoc from R/2 where as Idoc number 200 is inbound idoc...n they are totally different idocs..not same
    I think there is work around...while mapping data from XI --> 3rd party assign / store outbound idoc in one of the unused field of inbound idoc...and while mapping back use this field to map it back...I think this will work.
    Let us know the result.
    Nilesh

  • Error in ALE-IDOC related to HR data posting in ECC 6.0

    Hello People,
    Upgradation done from 4.6B to ECC 6.0.
    Here the data comes from the 3rd part s/w and then gets posted through a Z program which in tern calls SAP standard program " RSEINB00" and FM "IDOC_INBOUND_FROM_FILE" is used in this std program to post the data to the corresponding HR tables through IDOC postings.
    ALE-IDOC Z program works fine in 4.6B but gives error in ECC 6.0.
    Error in subroutine read_namtb for structure of infotype Message no. 5-109 Diagnosis An error has occurred in subroutine read_namtb for structure of infotype .
    Procedure
    Check the entry for infotype in table T777D (structure, IDoc segment, expanded structure) and the corresponding structures.
    As per the error message it seems that some table () needs to be maintained with some values, but this was working fine with the 4.6 B with current settings.
    Is this error due to version change to ECC 6.0? What extra settings need to be done with respect to IDOC so that the posting program works fine without giving the stated error. Kindly let me know.
    Thanks and regards,
    Gaurav Joshi.

    Please keep in mind ECC 6.0 is an UniCode based system.
    as 4.6C was not,
    did the Z-program have been tested before in the current environment?
    Some special functions (keywords hints ...) are no longer supported after the upgrade.,
    this was shown during the upgrade in the unicode migration tools
    For sure all the own programms needs to be verfied, after an upgrade.
    commonly this should be done
    in the quality assurance test to avoid touble in production.

  • How to catch Posting error in File to IDoc Scenario?

    I have successfully completed File to IDoc Scenario. Now I am interested in catching posting error. i.e., if mapping goes well and when IDoc is being sent to Recipient system then if any posting error is encountered, then a mail should go to a recipient.
    Can anybody suggest the solution.
    Regards,
    Suraj Kumar

    Hi Suraj,
    this can be done by triggerring an alert to the recipient.chk out these links to trigger a alert
    /people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
    /people/sap.user72/blog/2005/01/14/alert-management--improving-monitoring-of-your-landscape
    regards
    jithesh

  • REG: Error in IDoc adapter outbound processing

    Hi All,
          I had a couple of doubts regarding these IDoc's.
    1)        I am dealing with the web services to IDoc Scenario. When i am activated my wed services it               is giving an error like
    "IDOC_ADAPTER.ATTRIBUTE_BE_NOT_SUPP" and "Only asynchronous processing supported for IDoc adapter outbound processing"
    Can any one help me to Solve my Problem
    2) How to find out whether the IDoc is of synchronous or Asynchronous mode
        and how to  handle the synchronous type of IDoc's
    Thanks in advance.
    with Regards,
    Kalyan Dannapaneni.

    Hi Kalyan,
    IDOCs are only Aynchronous (EO or EOIO).
    If you want to call Synchronious, you will have to find remote enabled function modules (RFCs, BAPIs).
    Or you have to use the ccBPM Synch-Async pattern to have an synchronos call passed to an IDoc, waiting for the Acknowledgement. In your situation I would check if a similar BAPI/RFC exists on your Backend SAP system.
    Best regards,
    Silvia

  • Posting Subsequent Adjustment (MB04) with idoc WMMBXY

    Hi,
    I need to receive goods movement from a supplier who does subcontracting with  idoc WMMBXY that contains wastes related to a specific PO. Tha waste quantities arrive at the end of production, so they're not related to a finished product quantity.
    I've tried with two positions, one for mvt 121, quantity 0 for the finished product and one for mvt 543, quantity xx for the component, but the system doesn't allow me to put null quantities.
    Then I've tried only with the second one, but the system blocks the post saying special stocks not supported.
    Have any of you tried this management and tell me which field must be filled and how or can suggest another one way to do this with idocs?
    Thank you very much for your suggestions
    Anna

    Ok, I've found where's the problem is.
    During the checks, the system can't correlate through line_id and parent_id the connection between finished product and its components.
    How can I indicate the relationship in the idoc?
    Here's the point in FM MB_CREATE_GOODS_MOVEMENT where the check is done:
    Analyze IMSEG for document structure and assign LINE_IDs if necessary
      CALL METHOD cl_mmim_line_id_manager=>analyze_mb_create
    Thanks again!

  • IDOC inbound Posting Error no 51

    Hi Friends,
      I am triggering Inbound error using XI.
    I am getting Error no 51(Application document notposted), when i am checking in WE05.
    Can any one guide me how to trace further error???
    Cause of Error????
    If data is incorrect in IDOC how can i check, that error is due which field record????
    Please guide me and give some T.Codes to trace error in inbound IDOCs
    Thanks & Regards
    Umesh

    the hint with the status record is correct: If you double-click it, you may have a button 'application log' - but only if the inbound processing creates a log.
    SAP knows thousands of IDOC basic types, message types, process codes and almost nothing is handled the same way.
    So first get the details about Idoc and message types, find out how the inbound IDOC is processed, get the function modules name, use the debugger to see where what error is issued.
    You may also have a look at the IDOC's segments contents and see if some data is obviously wrong.
    Or just tell the readers here what business process you try to handle using what IDOC - experience may be just one click away.
    regards,
    Clemens

  • Trying to change Inbound IDOC to Outbound IDOC for testing....

    Hi Friends,
    I am trying to do the following
    1) In our legacy system SAP R/3 3.1H we have received an IDOC from our partner. This has been stored correctly.
    2) We now need the same functionality in our SAP R/3 4.6C system so I have created the IDOC type + segments accordingly. I have also set up the partner profiles
    3) We need test data but our partner can not send yet so the only other way is to send this INBOUND IDOC from 3.1H to 4.6C.
    4) HOWEVER, i have tried everything to do this like using WE19 to edit the idoc, but I can not process it for OUTBOUND processing.... You can in 4.6C but there is no option in 3.1H.
    HELP!! Rewards

    Hi Friend,
            The test programs allow you to skip certain sections of the processing chain between applications to localize errors. However, they can also be used to simulate an entire business process (for example, purchase order on the customer side with posting of the purchase order on the vendor side) in an SAP System (without any other systems). For this reason, the test programs are an important tool for configuring the IDoc Interface and defining new IDoc types.
    Use
    You can use the test tool to generate an IDoc manually and send the IDoc for either inbound or outbound processing. You are not restricted to a specific port type. You can start with an IDoc type (an “empty” IDoc) or use an old IDoc as a template and edit the IDoc, that is, add segments or change data. This is a good way to test new IDoc types, in particular.
    You can forward your new IDoc for standard inbound processing (checking partner profiles and so on). You can also call a function module directly. You can therefore test new function modules for new IDoc types.
    Activities
    ·        Start the test tool with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Test Tool (WE19). You can use a template for your test IDoc.
    You can choose IDoc types as a template, either directly or according to a specific message type. You can use the F4 Help for IDocs used as a template, which searches for IDocs by selection criteria, in the same way, for example, to IDoc Display. When an IDoc file is used as a template, the IDocs are read from this file and are available to you for selection. A default value for the IDoc file gives you the system using your test port which you can enter in IDoc Administration . This test port must therefore be of the “file“ type. The default file is the inbound file entered there.
    ·        You generate the IDoc using .
    The IDoc is displayed as a tree structure. If you do not use a template to create the IDoc type, at least one more segment must be added.
    ·        To create segments in the form of tree nodes (colored fields) place the cursor on an existing node (for example a control record at the top) and choose .
    You can cut, paste or copy individual segments or entire segment groups by positioning the cursor on the relevant segment and selecting the required action from the Edit menu.
    ·        Click on the white fields to change data in the segments.
    In the case of the control record, only the fields which are relevant for standard inbound processing are displayed. Do not forget the required entries in the partner profiles if you want to send the IDoc for standard inbound processing! You can also change all of the control record data by choosing All fields in the edit screen.
    In the All fields editor screen you must enter the non-language specific partner function (for example AG for vendor). This is the only screen in the IDoc Interface in which the partner function is not translated into your language (in English AG becomes vendor VD) - in the partner profiles or in the IDoc display the field is always translated. Thus, you see the partner functions here in the way they are saved in the database. This is a unique value in the SAP System and therefore protected against mistakes.
    ·        The additional procedure depends on whether you want to test inbound or outbound processing.
    Test: Outbound Processing from MC
    Use
    Use this test program if you have chosen the Message Control module and want to test generation of an outbound IDoc from an existing message status record (table NAST).
    Prerequisites
    You must be able to post the application documents which are to be converted into IDocs by the Message Control module correctly so that a message status record can be generated. In the case of the Materials Management (MM) and Sales and Distribution (SD) components, the following entries are required:
    ·        Customer or vendor records
    ·        Material records
    ·        Info records
    ·        MC condition record: The output medium 6 (for EDI) must be entered here. The condition records are maintained as “messages” from the respective application.
    The appropriate file ports and partner profiles must exist in the IDoc Interface.
    Outbound processing must be stopped when the message status record has been generated to allow the test program to intervene. To do so, you must set the Message Control dispatch time to “1” (output with selection run) in the corresponding condition record in the application. This test program, therefore, is simply used to start a selection run which retrieves the Message Control records and sends them for further outbound processing. The program is report RSNAST00, which is also generally scheduled with dispatch time 1 in live operation.
    Activities
    Once the application document has been posted, outbound processing stops after the message status record has been generated and is triggered again by the test program. Choose SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from MC.
    Errors are stored in the Message Control processing log (document header) and in the status records of the IDocs. The status records, however, are only available if the IDoc was successfully generated.
    Use
    This test program selects one or more outbound IDocs and forwards them to the external system. You can choose the IDocs according to various criteria (for example, recipient or business message).
    Prerequisites
    You require outbound IDocs which were generated without errors (no error status). The partner profiles, therefore, must be maintained completely.
    Outbound processing must stop when the outbound IDocs have been generated to allow the test program to intervene. You can check this by setting the output mode to “Collect IDocs” in the partner profile for the IDoc Interface. If you now generate an outbound IDoc for the partner (for example, using the application or the test tool), the IDoc is only generated in the SAP System and is not forwarded to the external system. This test program, therefore, is simply used to start a selection run which retrieves your IDoc(s) and sends them to the external system. The program is report RSEOUT00, which is also generally scheduled with the output mode “Collect IDocs” in live operation.
    Activities
    You start the test program by choosing SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Outbound ® Outbound from IDoc (WE14).
    You can decide whether the output mode is set to “Start subsystem” or “Do not start subsystem” in the partner profile. This defines whether the external (sub) system processes the IDocs further.
    Use
    This program is used to test whether status confirmations for an outbound IDoc are sent correctly from the external system to the SAP System. The port type here must be set to “File”.
    Prerequisites
    A correct status file which can be generated by an EDI subsystem, for example, is required. The status file must refer to an existing outbound IDoc in the SAP System. You can also generate such a status file yourself.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The SAP System reads the status file. The IDoc number contained in the file refers to the outbound IDoc, to which the status confirmation relates. The confirmed statuses are “credited” to the relevant IDoc in the form of status records in the SAP System.
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Status ® Edit Status File (WE17) and pass the inbound port, name and directory of the file. These entries overwrite the standard values which you have stored in IDoc administration using the test port.
    Test: Inbound Processing: Modified Outbound File
    Use
    This program converts an outbound file with IDocs to a correct inbound file and sends the new file for inbound processing. The outbound file is not modified and can therefore be used more than once. The port type here must be set to “File”.
    Prerequisites
    You need a correct outbound file, for example, a file which is generated by the test tool or using a standard outbound processing. In this case, a port of the type “File” must be specified in the partner profile for the IDoc Interface, so that the IDoc(s) can be written to a file.
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program imports sender and recipient data as input parameters from the user. The program reads the IDoc file and changes the corresponding entries in the IDoc control record. The changed data is written to a second IDoc file at the operating system level.
    Standard inbound processing is then triggered;
    ·        Reading the modified file
    ·        Generating the IDoc(s) in the SAP System
    ·        Processing in the application
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Mod. Outb. File (WE12).
    Set the sender and recipient data, as well as the outbound file and the inbound file to be generated (path and name). Your entries for the inbound file overwrite the standard values which you have stored in IDoc administration.
    The recipient in this case is the SAP System. The port is used for identification purposes:
    ·        SAP (for example RSMITH
    Test: Inbound Processing: Original Inbound File
    Use
    This program reads an inbound file and sends the file for inbound processing. If all data has been successfully read, the file is deleted.
    Prerequisites
    You require a correct inbound file. In this case, correct means that the:
    ·        Sender and recipient in the control record are correct
    ·        Direction in the control record is set to 2 (inbound)
    ·        Client in the control record and data records are correct or empty
    The sender port must be recognized by the receiving system. The port must therefore be maintained as a port of type “File” in the port definition for the IDoc Interface. The entry for the inbound file must also be given here.
    Features
    The program reads the IDoc(s) from the inbound file and sends them for standard inbound processing (with processing within the application).
    The file is deleted after being read successfully!
    Activities
    Start the test program with SAP Menu ® Tools ® IDoc Interface/ALE ® Test ® Inbound ® Inb. Orig. Inb.File (WE16) and pass the following data:
    ·        Inbound port
    ·        Name and directory of the file
    These entries overwrite the standard values, which you have stored in IDoc Administration using the test port.
    Thanks

  • Outbound Delivery IDOC not updating values from MKPF for goods receipt

    hi all,
    I have a question say I am generating an outbound delivery IDOC. which  has fields Goods Issues & Goods Receipt date retrieve from MKPF(BUDAT).
    say when i post goods issues, MKPF is updated and  IDOC is gernerated with issues date taken from MKPF.
    and when i tried to goods receipt, MKPf is updated and IDOC is generated but no receipt date taken from MKPF. then i check in MKPF, date is there and then once again I triggered the IDOC, receipt date comes......so my doubt is the time issues say when IDOC is triggeres, no value in MKPF...but when i check the time it is 4 mins difference from the MKPF time and the IDOC time...
    and also 1 more thing for doing goods receipt, we do in different transaction and for good issue we do in Vl02n.
    so bit confused.
    kindly help

    True , but in BKPF only Issues date are stored not the receipt date say if the document type = WE.
    Please let me know is there any other options to fetch rather than MKPF.
    because at the time of IDOC generation, there is not entries in MKPF. I tried to do using WAIT UP TO 50 seconds , even that didnt work.
    Please guide me
    thanks

  • File to IDoc scenario-CREMAS not getting posted

    Hi Experts,
    i am doing a file to idoc scenario in which i am giving the xml file from MDM ,consisting of Vendor Master data and posting the address and the general data into the ADRMAS and CREMAS idocs into the R/3 system.
    The problem that i am facing is that the ARMAS is getting posted correctly but the CREMAS is getting posted with the red signal,status 51.It says "Not authorized to change the Vendor Centrally."
    Can anyone please tell me what is the reason and the solution for this problem?
    Is this a data error or XI error?
    Thanks in advance,
    Shweta.

    Hi Shweta
    Status 51, 52 means Posting error 
    Please check wheteher all the configuration has been done or not
    SM59-rfc destination
    IDX1-port
    IDX2-load metadata
    we05-IDoc status records
    BD54-Create Partner Number
    We20-Create Partner Profile
    WE19-Testing IDoc Processing
    After That check the solution it is due to Authorization
    File to idoc - IDX5 Error
    Regards
    Abhishek Mahajan
    *Please reward points if helpful**

  • Inbound IDoc w/message ORDERS - issues with error processing

    We are using inbound IDoc ORDERS05 with message type ORDERS to create the sales orders in SAP. In WE20 we have the following settings:
    - partner type LS (= Sales Org VKORG)
    - process code ORDE
    - trigger by background program
    - post-processing agent of type US (user) with a user ID.
    We create IDocs through an ABAP program and use RBDAPP01 to post the IDocs. When there is an application error in the IDoc posting we expect the designated user to receive a workflow item in the SAP Inbox, but for some reason this is not happening.
    I did some research and went through all the possible settings for workflow, task, etc. and everything seems to be set up correctly. When debugging RBDAPP01 I have noticed that it calls FM APPLICATION_IDOC_POST_IMMEDIAT, which, in turn, calls IDOC_START_INBOUND. If IDOC_START_INBOUND returns SY-SUBRC = 1 then the workflow item is sent correctly to the designated user, exactly as we want. But for some reason it returns 0 (I changed it to 1 in the debugger).
    It seems that IDOC_START_INBOUND reads TEDE2 records (TEVE2-EVCODE = ORDE) and sy-subrc = 1 is only possible when EDIVR2 is 1,2,3 or 4. In our case TEDE2-EDIVR2 = 6. It seems that TEDE2 is maintained in the transaction WE42. However, I tried to change the settings there but it affects the IDoc processing in whole (IDoc gets some odd status and doesn't get processed as before). I've also tried to use process code ORDE_BY_WORKFLOW in WE20 with the same "success".
    What do we need to do to get a workflow item for the errors that happen in the application layer when IDoc is posted? Is it even possible with this message type?
    Any ideas would be appreciated.

    Hi,
    Can you please share how do you overcome the problem, so that it can be helpful for others.

  • Error: Idoc name IDoc cannot find request IDoc in Integration Server

    Hi,
    I am getting an error while working on a scenario.
    scenario is Idoc to file. when the Idoc is posted, i am getting the error "ALEAUDIT IDoc cannot find request IDoc in Integration Server"  when i see the status in SXMB_MONI
    I have tested the message mapping and configuration induvidually. They are working fine.
    Kindly help me out in solving this issue.
    please reply

    Hi,
    The AleAduit sent in the case of Idoc to File if the file is posted successfuly is not actually a App Ack, and that is why we get the info Ack not possible.
    But, as the R3 might expect this Idoc, XI still sends it back to the Source R3 system.
    Regards,
    phani

  • How to build outbound ACC_GL_POSTING IDOC

    We have a requirement where we need to build ACC_GL_POSTING IDOC's outbound from SAP. These will be sent to a middleware system where it will be translated and then posted in a separate SAP system using the same IDOC.
    Is there an easy way to build the structure in ABAP without causing it to post in the source SAP system??

    Let me clarify:
    We need to send GL posting information from one SAP system to another. Call the source SAP system, SAP system A.
    One method proposed was wrapping up a file and putting all the info in there, parsing it in the middleware, and then posting teh ACC_GL_POSTING IDOC into the target system, SAP system B.
    We'd rather use IDOC's on each side of the interface. We know for sure we can use ACC_GL_POSTING in SAP system B to make the postings. We'd like to know how to populate the same IDOC in SAP system A(source) so we can use standard ALE and avoid flat files.

Maybe you are looking for