Post inbound as well as outbound IDOCs through a report

Hi all,
        I have a specific requirement where i need to post an IDOC through a report which ressemble to WE05. This requirement implies for Inbound as well as Outbound for all message types. Can anyone let me know how can this be achieved. Please let me know if this can be acheived through any FM or method.
Regards
Simin.R

Hi,
To create a new inbound idoc use the following function module:
IDOC_INBOUND_SYNCHRONOUS
To Create a outbound idoc use the function module
MASTERIDOC_CREATE_* - search and decide based on your requirement.
Regards,
Baburaj

Similar Messages

  • Outbound Idoc through Workflow in CRM

    Hello,
    Consider this scenario, I need to create an opportunity document through Idoc inbound in CRM 4.0. There are certain validations done at the XIF layers as well as the application layer.
    In case if there are any errors in the Idoc or  errors the opportunity document created(application level errors), I need to send an outbound Idoc containing complete inbound Idoc data with certain rejection codes.
    Can some body let me know the best way to achieve this. I
    If this can be achieved through workflow, please provide the complete details on how to go about this.
    Thanks  In Advance,
    Kiran

    Hello,
    Consider this scenario, I need to create an opportunity document through Idoc inbound in CRM 4.0. There are certain validations done at the XIF layers as well as the application layer.
    In case if there are any errors in the Idoc or  errors the opportunity document created(application level errors), I need to send an outbound Idoc containing complete inbound Idoc data with certain rejection codes.
    Can some body let me know the best way to achieve this. I
    If this can be achieved through workflow, please provide the complete details on how to go about this.
    Thanks  In Advance,
    Kiran

  • How to send Outbound IDocs through an RFC-enabled FM

    Good day to all;
    A partner system (AS/400) wants to use a Java Connection to execute a RFC Function Module, in SAP, that will then return a collection of IDocs.
    Currently, the Function Module builds the IDocs, but I'm not exactly sure how to simply send those IDocs back to the AS/400.
    If anyone can help in this regard, that would be great.
    My current thoughts are to use Master_IDoc_Distribute, but then I imagine that requires a port configuration for the AS/400.  And if this is the case, does that mean that SAP will send the IDocs back itself instead of using the RFC interface?

    Hi Tavares,
    If you want to send outbound IDoc to AS/400 (external system), you need to setup file port (t/code WE21).
    For RFC interface, you need to setup RFC file port with RFC Destination (t/code SM59). In this case, SAP will send IDoc (individually or batch) to receiver system (AS/400). Perhaps you need a middleware for data transformation, if AS/400 does not perform data mapping for outbound IDoc. 
    For FTP interface, you need to setup flat/XML file port for outbound. then you can FTP the file to AS/400 later on.
    In addition to file port configuration, you also need to setup partner profile for outbound parameter (t/code WE20) and the distribution model (t/code BD64).
    Hope this will help.
    Regards,
    Ferry Lianto

  • Steps for configuring Outbound Idoc OILSHI01

    Hi experts,
        can anybody tell me the steps how to configure an Outbound IDOC.
        It is better if somebody can take Shipment IDOC of IS-Oil - OILSHI01.
        if not anything else will also do.
        Kindly give me steps in detailed. Since i have never done this. Including 
        distribution modle (BD64). in which case it generates the Automatic Partner
        profiles.?
    <REMOVED BY MODERATOR>
    Regards,
    Umesh
    Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:08 PM

    Hi Umesh,
    Sorry for the late reply. Let me clear your couple of misconceptions first.
    Every idoc is an application idoc. That is, if an idoc is not attached to any application, then it doesnt make business sense to generate that idoc.
    Secondly, an idoc is outbound or inbound depending upon its communication direction w.r.t. the sender system. If the idoc is going out from lets say R/3 system (where you are creating distribution model), then its an outbound idoc and if its coming inside, then its inbound idoc.
    Now the further steps:
    Since its a transactional data idoc, we dont generally go for change pointer activation. Kindly read the documentation to get more idea (if you dont have any then send me your mail id, i will send you a very good document). For transaction data, we use output type to trigger an idoc. Following are the steps to trigger an outbound idoc through output type.
    However, remember that in this case, you need help of your functional consultant at every point so that you can clearly determine your application definations and configuration.
    1. Go to transaction NACE. There you can see all the generic applications listed. Find out the one relavant to your idoc type from the functional person. If you select your relavant aplication, and click on the "Output types", you will see a list of all the output types for each business transaction defined for that application.
    2. Again, ask your functional consultant, as to which output type is configured for your  business transaction. Select that output type and go to "Processing routines".
    3. There you will be able to see different ways in which the idoc can be triggered. Most of the time , we use processing routine "A (Distribution (ALE))". There you will also see the report which will trigger the idoc.
    4. All the above mentioned customization is to be done by the functional consultant (or by technical after strictly seeking the permission). Once the output type is set, you go to the business application (IS-oil) which is triggering your idoc.
    There, you will see the option of generating delivery (or something similar, again only the person who has worked on the application can tell that). there you can populate the idoc. 
    Once the idoc is populated by the application, there are couple of ways of triggering the idoc.
         a. trigger the idoc on saving the doucment.  this triggers idoc as soon as you save the idoc.
         b. Collect for mass processing. For this you need to run the report RSNASTED after the idocs are populated to trigger them.
         c. Collect for application specific posting. For this , you need to know the transaction, specific to your business data to trigger the idoc and all you need to do is just run that transaction.
    Hope you got the points mentioned above. Kindly go through them carefully and then give me your mail id. I will send you one good document which will clear your understanding.
    Hope this was helpful.
    <REMOVED BY MODERATOR>
    Cheers,
    Karan
    Edited by: Alvaro Tejada Galindo on Apr 21, 2008 3:09 PM

  • How To Edit Failed IDocs Through Report ?

    Hi
    I have the requirement of editing (Modifying) IDocs through a report program..
    ( My program displays the content of a specified segment of failed IDocs in the ALV format..
    Then the changes made to those fields in ALV have to be updated in those failed IDocs.. So that i can reprocess the IDocs.. )
    Is there any BAPI or BADI or Any other solution to edit IDocs through a report....??
    I dont want to use BDC as the report program is meant for editing huge number of failed IDocs..
    Please help me..
    Thanks a lot,
    Raj

    There is a similar POST open in DATA TRANSFER FORUM...

  • How to trigger outbound IDOC when data changed in BP through Inbound IDOC.

    Hi,
        In our system whenever we create a new Business Partner, these data is send across to SAP R/3 (as BDOC) and to Mainframe system  (as outbound IDOC). Whenever we change any Business Partner record the data is send across to SAP R/3 (BDOC) and to Mainframe system (as outbound IDOC).
        This functionality is working fine.
        Currently we are getting a value for one standard field (Customer_Group3) of Business Partner as an inbound IDOC. The value of the inbound IDOC is reflecting in the field (Customer_Group3) in Business Partner Transaction. Once the inbound IDOC is received, the modified value is send across to SAP R/3 as BDOC. But the modified value is not send across to Mainframe system (outbound IDOC). The outbound IDOC is not getting triggered.
    Kindly help

    Is your mainframe system configured as Site in SMOEAC. If so are you using XIF Adapter.

  • Creation of Inbound Idoc for the Outbound Idoc in same client

    Hi,
    My requirement:
    Whenver an PO is created an Outbound IDOC is generated in system ABC with client 100.I want to pass this IDOC data to create an Inbound Idoc for Sales Order(SO) in the same client.
    It would be helpful if anyone can answer on how to Transfer the Outbound Idoc after it crosses the port.
    I found there is a field for function module in WE21,can this be used to get the requirement done.
    Please suggest.
    Regards,
    Amar

    Example of a program that create and post an inbound idoc....maybe that will help you:
    report  zzinbound_idoc.
    data: g_idoc_control_record like edi_dc40 occurs 0 with header line.
    data: g_edidd like edi_dd40 occurs 0 with header line.
    data: g_e1bpache09 like e1bpache09.
    parameter: mode type c default 'A'.
    refresh: g_idoc_control_record, g_edidd.
    clear:   g_idoc_control_record, g_edidd.
    *-Build Control Record -*
    g_idoc_control_record-mestyp  = 'ACC_DOCUMENT'.   "Message type
    g_idoc_control_record-idoctyp = 'ACC_DOCUMENT03'. "IDOC type
    g_idoc_control_record-direct  = '2'.              "Direction
    * Receiver
    case sy-sysid.
      when 'DE2'.
        g_idoc_control_record-rcvpor = 'SAPDE2'.     "Port
        g_idoc_control_record-rcvprn = 'IDOCLEGACY'. "Partner number
    endcase.
    g_idoc_control_record-rcvprt = 'LS'.             "Partner type
    g_idoc_control_record-rcvpfc = ''.               "Partner function
    * Sender
    g_idoc_control_record-sndpor = 'A000000002'.      "tRFC Port
    case sy-sysid.
      when 'DE2'.
        g_idoc_control_record-sndprn = 'IDOCLEGACY'. "Partner number
    endcase.
    g_idoc_control_record-sndprt = 'LS'.             "Partner type
    g_idoc_control_record-sndpfc = ''.               "Partner function
    g_idoc_control_record-refmes = 'Customer clearing'.
    append g_idoc_control_record.
    *-Build Idoc Segments -*
    *---E1KOMG
    clear g_edidd.
    clear g_e1bpache09.
    g_edidd-segnam               = 'E1BPACHE09'.
    g_edidd-segnum               = 1.
    move g_e1bpache09 to g_edidd-sdata.
    append g_edidd.
    *-Create idoc -*
    *-Syncronous
    if mode = 'S'.
      call function 'IDOC_INBOUND_SINGLE'
        exporting
          pi_idoc_control_rec_40              = g_idoc_control_record
    *     PI_DO_COMMIT                        = 'X'
    *   IMPORTING
    *     PE_IDOC_NUMBER                      =
    *     PE_ERROR_PRIOR_TO_APPLICATION       =
        tables
          pt_idoc_data_records_40             = g_edidd
        exceptions
          idoc_not_saved                      = 1
          others                              = 2.
      if sy-subrc <> 0.
        message id sy-msgid type sy-msgty number sy-msgno
                with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      endif.
    *-Asynchronus
    else.
      call function 'IDOC_INBOUND_ASYNCHRONOUS'
        in background task as separate unit
        tables
          idoc_control_rec_40 = g_idoc_control_record
          idoc_data_rec_40    = g_edidd.
      commit work.
    endif.
    write: / 'Well done!'.

  • Why does an Inbound IDoc no change and differs from an Outbound IDoc no?

    Hi Experts,
    This seems to be a basic question..! But can someone kindly clarify why an IDoc number gets changed when sent from one R/3 system to another R/3 system and how does this happen???
    i.e., whenever an IDoc was triggered from R/3 system A to R/3 system B through XI/PI, the Inbound IDoc number (in system B) differs from the Outbound IDoc number (in system A)... Why does this happen and how???
    Thanks in advance!
    Br,
    G@nesh

    Hi Ganesh,
    The IDOC numbers are always Unique,
    IDOC can be generated in SAP system as a result of internal testing (WE19), or
    can be posted from a non sap system (say PI).
    So every time a new IDOC comes, it is assigned a new number to avoid confusion and also this plays a
    critical role in the  end to end testing and validation.
    If you look at the control record of the IDOC you can see a element called DOCNUM. this stores to actual IDOC number.
    from PI side you can  use IDX5 and in ECC  We02/05 to notice the idoc numbers.
    Regards,
    Srinivas

  • 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

  • IDoc type "DELVRY03" for INBOUND delivery confirmation and Outbound Deliver

    Hi ,
    We have a requirement where we have to send Inbound delivery confirmation as well as outbound delivery notification to our same customer. (3PL case)
    We have a EDI partner who is receiving our messages and transforming them before sending it to customer.
    Now my problem is , since I am using same idoc type (DELVRY03) for both cases therefore wondering how my EDI partner will differentiate whether received message is a INBOUND delivery confirmation or OUTBound delivery notification.
    regards
    Shrey

    Thx for your reply ...
    Wondering about the impacts , if I create a new message type like ZDESADV and attach it to DELVRY03.
    In this i could have two message types DESADV and ZDESADV.
    Will it impact anywhere ?
    Regards
    Shrey

  • 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

  • Handling outbound IDOC errors through workflow TS00007989

    Hi,
    I want to sent an notification e-mail to external mail box when an outbound idoc has an error status. This needs to be achieved through a workflow template.
    I noted that there is a standard task TS00007989 in WE40 which is used for handling outbound idoc errors.
    Moreover i couldnt find any trigerring events for the above task.
    Can any one help me with a step by step guide for achieving this.
    Regards,
    Krishnakumar

    Hi,
    the single step task TS00007989 that you see is NOT TRIGGERED thru' any BO's event. It is created by the std. pgm RSEWFERR. If you go to the wflow log of the witem generated by it, you will see the Creator.
    And you can control the activation / deactivation of these single step tasks for various inbound and outbound Error IDOC's thru' Transaction WE46.
    If you want, create a single step task of your own and maintain that task here. But, you will ahve to know the exact BO like IDOCORDERS or IDOCEMBMAS etc. or look for events triggered by General IDOC objects like IDOCAPPL.
    Hope this helps.
    venu

  • Recommended Status Codes usage for Inbound & Outbound IDocs

    Hi,
        Can someone tell what status codes do we use when we go for a Custom Posting Program or Selection Program?
    I assume we use 51 for Posting Program (not 56) and
    26 for a Z-Selection Program (Not 37 or any other Code).
       Please let me know what is recommended and which status codes most of the people use while Custom Development.
    Thanks and Regards,
    Venkat.

    Hi,
    Outbound IDOC Status Codes
    The following table describes outbound IDOC status codes that generate Tivoli Enterprise Console events:
    Outbound IDOCs
    Code Error Event Severity SAP Meaning
    02 Yes Error Error passing data to port
    03 No Error if transaction SM58 indicates an RFC transmission error Data pass to port OK
    04 Yes Error Control information of EDI subsystem
    05 Yes Error Translation
    06 No Harmless Translation
    07 Yes Error Syntax check
    08 No Harmless Syntax check
    09 Yes Error Interchange handling
    10 No Harmless Interchange handling
    11 Yes Error Dispatch
    12, 13, 14 No Harmless OK
    15 Yes Warning Interchange acknowledgement negative
    16 No Harmless Functional acknowledgement
    17 Yes Warning Functional acknowledgement negative
    18 No Harmless Triggering EDI subsystem
    20 Yes Error Triggering EDI subsystem
    22 No Harmless Dispatch OK, acknowledgement still due
    23 Yes Error Retransmission
    24 No Harmless Control information of EDI subsystem
    25 Yes Warning Processing despite syntax error
    26 Yes Error Syntax check
    27 Yes Error ALE error
    29 Yes Error Error in ALE services
    30 No Harmless Ready for dispatch (ALE)
    31 No Harmless IDOC is marked for deletion
    33 No Harmless Original of an IDOC which was edited
    34 Yes Error Error in control record of IDOC
    36 Yes Error Timeout error; electronic signature not performed
    37 Yes Error IDOC added incorrectly
    38 No Harmless IDOC archived
    39 No Harmless Receive confirmed
    40 Yes Error Application document not created in target system
    41 No Harmless Application document created in target document
    Inbound IDOC Status Codes
    The following table describes the inbound IDOC status codes that generate Tivoli Enterprise Console events:
    Inbound IDOCs
    Code Error Event Severity SAP Meaning
    51, 52 Yes Error Posting error
    53 No Harmless Posting successful
    54 Yes Error Error during formal application check
    55 No Harmless Formal application check
    56 Yes Error IDOC with error added
    60 Yes Error Syntax error
    61 Yes Warning Processing despite syntax error
    62 No Harmless IDOC passed to application
    63 Yes Error Error passing IDOC to application
    64 No Harmless IDOC ready to be passed to application
    65 Yes Error ALE error
    68 No Harmless IDOC is marked for deletion
    70 No Harmless Original of an IDOC which was edited
    73 No Harmless IDOC archived
    Regards,
    Raj.

  • When we post Inbound Invoice IDocs, we are getting an error message "Enter a tax jurisdiction code".

    Hi Experts,
    When we post Inbound Invoice IDocs, we are getting an error message "Enter a tax jurisdiction code". As checked, we have configured OBCD and OBCA for the vendor and we are passing the Tax Jurisdiction code in E1EDP04 SAL segment. Can anybody give us some idea to resolve this issue.
    Regards,
    Sameek

    Hi Sameek,
    Please refer the below link. Hope it helps.
    http://scn.sap.com/thread/1435286
    Regards,
    Chandan.

  • Error while trying to post inbound idoc of message type COND_A

    Hi,
    I am getting error while trying to post inbound idoc of message type COND_A.
    If I left Usage & Condition field of segment E1KOMG then 'Table not available' idoc message is coming
    and if providing value in above fields then dump is coming.
    How to solve ?
    Plz do reply
    Thanks
    Mohit

    I do not see any reason why you would need to use COND_A04  if COND_A01 is working.
    What if you could get COND_A04 to post and you would face the same result as in COND_A01?
    If SAP does not check wrong values, then you have to do it yourself, or you report an incident at SAP (after you have searched for OSS notes that may have fixed this error already)
    For example OSS Note 1169998 - IDoc: KONP-LIFNR values not checked
    fixed a situation where the vendor number was not validated.

Maybe you are looking for