Idoc are posting to ECC with Status 64

Hi All,
We are receiving IDOC with status 64 from PI.
We used tried by changing the options in partner profiles
--> Trigger by Background program
The inbound IDoc is processed in the background. In this case, make sure, that the report RBDAPP01 is scheduled in the transaction SM37 as a regular job with the correct variant to process all IDoc´s, which have this processing option maintained.
--> Trigger immediately
When using this setting, it is important to have sufficient resources for the immediate processing of the inbound IDoc´s. One dialog work process must be available for every single IDoc.
If this dialog work process is not available, the IDoc cannot be processed and stays in status 64.
I reffered the notes
555229 ‘IDocs hang in status 64 for tRFC with immediate processing’
734576   ‘IDocs retain status 64, but should be processed immediately’
1055679 ‘IDoc-tRFC inbound with immediate processing may not work’
Still the idocs are in 64 status, every time im re-processing them manually. even after re-processing some of them are going to 51 or 54.
Please help me.
Regards
Bhargava Krishna

Hello,
Can you please explain your issue is with "Trigger by Background program" or "Trigger immediately"?
For Trigger immediately, if there is no free dialog work process available than IDocs are posted with status 64.
For Trigger by Background program, Background job RBDAPP01 will process IDocs depending on variant you define to select & process IDocs(i.e., IDoc Status = 64).
It is always recommended to use "Trigger by Background program" for high volume interface which has large number of IDocs.
Help on RBDAPP01
Regards,
Sameer

Similar Messages

  • Inbound IDOC to post goods receipt with inbound delivery as reference

    Kindly let me know the message and IDOC type for
    Inbound IDOC to POST GOODS RECEIPT  with inbound delivery as reference
    I tried using WMMBXY but it didn;t work.
    Pls let me know asap.Your help is appreciated.
    Thanks and Regards
    Priti
    Edited by: Priti Adukia on Feb 11, 2008 4:48 AM

    Hi Nicole,
    What I've to do is quite the same as the case. Outbound and Inbound are in the same SAP system. If I've good understanding, I must set partner profile as follows :
    INBOUND - Parter LI with
                            Message DESADV
                            Operation code DELS
    OUTBOUND - Partner KU
                            Message DESADV
                            Operation code ???
    Please advise
    Suchart

  • EDI documents are posted to SAP with BAPI  ...How?

    how is that EDI documents are posted to SAP with BAPI....is there some step by step doc to do that.....

    Hi,
    There are couple of EDI subsystems like Meractor from where you can fire a BAPI to post a document into our SAP system.
    First the EDI subsystem receives the EDI document and from there are going to fill all the internal tables of the BAPI and call that BAPI from the EDI subsystem itself, if the BAPI is successfully executed then it will return the document number and if it fails then it will throw the error why it has failed.
    If it has failed then the EDI team will look into the reason and work on it, if it is a data related then they will take care and it is a problem with the config then they are going to intimate the SAP team to make the necessary config and they will refire the BAPI again.
    Thanks,
    Mahesh.

  • How to convert XML into idocs and post in ECC using PI

    Hello All,
    I want to configure the scenario like this MDM->PI->ECC. Using FTP I am getting able to fetch the xml file from MDM Server Ready folder. Now, I need to convert this XML file into Idocs and post it in ECC. Can anyone provide me step by step configuration in PI to achieve this. I have configured communication channel with adapter type Idoc in Itegration Builder. But, I am not sure where it will do the conversion of XML into Idoc and how do post it to ECC. I am working first time on PI 7.1. I have worked on XI 3.0 in 2006-2007. Any help to configure this step by step shall be appreciated.
    Thanks & Regards,
    Hemal

    In you have the XML from MDM you have to use the mapping provided by the funtionals in the Funtional specification documents. once you did it you must configure the Receiver IDoc Adapter. and later dont fonget to configure properly the ReceiverAgreement.
    as you receive the docuement from MDM via FTP, thats not a SAP System that means that you have to define PI as the sender of the IDoc,otherwise you will have the Error "Unable to convert the sender service to an ALE logical system"
    to do that in the receiver Agreement>Header Mapping>Sender System-->Select PI server.
    Take in mind to send IDocs to any SAP System, the system that send it must be a SAP system too. thats why you configure it
    http://help.sap.com/saphelp_nw04/helpdata/en/5d/112d20f6ce6c46ba66afb98d278fbd/frameset.htm
    Another thing is you have configure the ALE distribution Model.
    se this:
    http://wiki.sdn.sap.com/wiki/display/XI/FileToIDOC
    /people/michal.krawczyk2/blog/2005/03/29/xi-error--unable-to-convert-the-sender-service-to-an-ale-logical-system
    /people/venugopalarao.immadisetty/blog/2007/01/24/troubleshooting-file-to-idoc-scenario-in-xi
    Let us know
    Rodrigo P-.

  • Inbound Idocs Got struck with status 75

    Hi All,
    My idocs Got struck in qrfc with status 75 ,Could any body tell why they r struck with status ,even though my partner Profile setting is set to Trigger Immedeatly
    Appreciate your Replies..
    Thanks,
    Madhu

    Dude, use Search button:
    Re: Customer creation in R/3 from PI data using IDOCs

  • Inbound Idocs are not Processing

    Hi,
    Inbound IDOCS queue is not processing if any one IDOC is showing amber(error) . Please let me know the resolution to avoid this issue or let me know the BASIS setting to avoid it.
    Regards,
    PVK.

    Hello,
    Can you please explain your issue is with "Trigger by Background program" or "Trigger immediately"?
    For Trigger immediately, if there is no free dialog work process available than IDocs are posted with status 64.
    For Trigger by Background program, Background job RBDAPP01 will process IDocs depending on variant you define to select & process IDocs(i.e., IDoc Status = 64).
    It is always recommended to use "Trigger by Background program" for high volume interface which has large number of IDocs.
    Help on RBDAPP01
    Regards,
    Sameer

  • Vendor IDOCs are not uploading in LFA1 table

    Hi All,
    We have a SAP system where Vendor IDOCS are coming from MDM through SAP PI middleware. The problem we are facing is we are not able to see all Vendors in LFA1 table.
    In WE05 IDOCS are posting successfully but when we check for respective vendors in LFA1 table only few vendors are available there.
    Can anybody guide us to solve this issue? Also pls let us know the process of uploading master data into table as we are very new in ABAP.
    Regards,
    Sarita

    be open minded. SAP gives several import methods to load vendors.  one of them is per IDOC.
    But the vendor master IDOC does not automatically create the adress master.
    And even more important, if you migrate data from one SAP system to another, the IDOC method is more straight forward than the batch input, because you can send the IDOCs from legacy system to new system, you will then have a 1:1 relation of the structure in LSMW and you can create vendor masters by knowing the new vendor number from an internal number range already in LSMW, long before you actually post the vendor. With batch input you can either post with numbers from external number range, or you just dont know the new number already in LSMW.
    And you dont need to download the data to Excel. And further, the LFA1 adress data has less information than the ADRC adress data.

  • IDOC is created with status 51( application document not posted)

    Hi experts
    iam working on File-IDOC scenario, when i test the process the XML message is created with no errors and
    but the IDOC is created with status 51( application document not posted)
    the details error shows:
    An error occurred in CALL TRANSACTION USING or CALL DIALOG USING
    during a synchronous update.
    The error was caused by the transaction VA01.
    previously i used same test data that time it was working fine,
    please tell me how can i fix the issue.
    regards
    vasavi

    Key in your Idoc number in BD87, execute
    select the error message and then follow the menu path :
    EDIT --> restrict and process  (Select)
    In the next screen UNCHECK the Bkgd Processing and execute
    Now EDIT --> Process --> foreground from error or in foreground mode.
    This will lead you the screen where it errored out.
    Thx
    PSR

  • PO Rejection - ORDSP Idoc Errors in ECC with different process codes

    Hi All,
    We were testing the Scenario where the Supplier rejects a PO line item as part of the PO Collaboration. On rejecting the PO in SNC, it trigerred an ROC XML with AcceptanceStatusCode == RE. The same was passed on from XML to Idoc in the IDoc segment E1EDP01, field ACTION = "003".
    However, such ORDSP Idocs was failing on the ECC side during Inbound processing with the following errors:
    1. Acknowledgment for PO item 4400000XXX 00010 contains quantity variance: Message no. ME794
    2. Price unit 0 from IDoc differs from unit of purchase order 1: Message no. ME729
    3. Order price unit differs from unit EA from purchase order: Message no. ME728
    4. Order units differ : Message no. ME791
    5. Material number differs from that of ordered material : Message no. ME790
    Note : We dont get these errors for a normal confirmation. It happens only with Rejection.
    The deletion indciator could not be set in the ECC PO line item even after manually correcting the above errors in the Idoc and posting it.
    Then based on this SDN Post: [PO rejection in SNC does not update the items in MM with ORDRSP;, we changed the WE20 settings. i.e., for ORDSP Idoc changed the Process code from ORDR to ORDR_SUS. After this change, the the above errors were eliminated and the the rejection data was also updated on the ECC PO by setting a deletion indicator. But we are having the following issues:
    1. Though both the confirmation & rejection data are getting transferred successfully, the Idocs remain in status 52 (Application document not fully posted).
    2. The message in the status record is "Rejection of PO item 4400000XXX 00010 with reason: Message no. ME749
    3. Came across these 2 related SAP Notes:
       a. #1087422 : But this is not applicable as the note states that this error will occur only if we delete the PO line item before hand in ECC.
    b. # 66192 : This note suggets a custom solution. But actually all the info from the ORDSP Idoc are getting processed successfully (Rejection & Confirmation send in the same Idoc). Only the status of the Idoc (Status = 52) is concerning us.
    Looking forward for inputs / suggetions from those who have used the Rejection functionality in SNC without custom development.
    Regards,
    Bharath

    Hi Bharath
    Rejections is handled like that only, can you please check whether note 1529579 is helpful
    It is standard behavior, as it expects other segments to fill, but never the less the PO will be updated properly, its only problem
    with the status of the idoc....nothing wrong in the data updation. The above note should be handy.
    Regards
    Vinod

  • Inbound idoc posting directly even with 'Trigger by background' option

    We have inbound idocs coming into ECC from Siebel via PI. The partner profile is setup for "Trigger by background program' .So that we can run the job RBDAPP01 to sweep these status 64 idocs. But we don't get a chance as the idocs are getting posted directly(its already in status 51 or 53) as if we used the 'Trigger Immediately' option. Where could the problem lie ? Is there a possibility of some RFC call from PI overriding the Partner Profile config ? Any advice or useful tip is welcome!
    thanks,
    S

    Hi,
    I guess you can still check in the control record for EDIDC-EXPRSS - Overriding in inbound processing, the documentation of the Data Element EDI_EXPRSS is as below
    Short Text
    Overriding in inbound processing
    General
    This field determines for ALE whether a time schedule is to be deactivated for inbound processing and replaced by immediate processing.
    Regards,
    Chen

  • Idoc Not reaching PI even with 03 status

    Hi everybody
    There are many posts with similar question, but none of them could help me.
    I am trying to post an IDOC from one SAP system 3.1 to SAP 6.0 through PI.
    I added FIDCC1 to to my partner profile in BD64.
    I am creating a invoice and clearing it through f-30 and using the details from the invoice i am trying to trigger an idoc through a program.
    Three idocs are getting triggered
    1.when i create invoice(f-22)-automatically
    2.when I clear invoice (f-30)-automatically
    3.When I execute my program
    The first two IDOCS are reaching 6.0, but my third IDOC is not reaching. All have same port details and partner profile details.
    *All have 03 status in we02 in 3.1*. I am not able to understand why those two are reaching and why the third is not reaching.
    None of them are stuck in any queues.
    My actual requirement is only the third IDOC to reach 6.0 and I do not even want the first two IDOCs to reach 6.0.
    Pls help!
    Thank you
    Donny
    Edited by: Donnesh on Dec 27, 2011 1:14 AM

    Hi Friends,
    Thanks for the suggestions.
    I have checked with all the above provided suggestions.
    But as I have clearly mentioned in the problem that other idocs are reaching well in XI from R3 using the same Port, Partner Profile and RFC.
    The error is occuring only with only one idoc in which they have made certain changes (added new segments). I have imported the idoc in Design again and then did the mapping again with the changed idoc.
    Before the changes I could receive the Idoc successfully in XI system. I don no what happened after the changes.
    If it would have been an authorization problem then I guess the other idocs would not have reached the XI system as well.
    I guess the problem is somewhere else..
    Thanks in advance.

  • Posting Data Issue with IDOC Type : COND_A03

    Friends,
    I'm posting the data from Middleware(Message Broker) to SAP using the IDOC Type : COND_A03 with Message Type : COND_A.
    For this IDOC,I'm populating the below Segment's data.
    Segement :E1KOMG:
    Fields:
    KVEWE,KOTABNR,KAPPL ,KSCHL,VAKEY ,KONDA,MATNR .
    Segement :E1KONH:
    Fields:
    KNUMH,DATAB,DATBI
    Segement :E1KONP:
    Fields:
    KSCHL,STFKZ,KSTBM,KSTBW,KRECH ,KBETR,KONWA,KPEIN,KUMZA,KUMNE,MXWRT,GKWRT,ZAEHK_IND ,KBRUE,VALTG,
    VALDT,ANZAUF,MIKBAS,MXKBAS,KOMXWRT,KLF_STG,KLF_KAL
    Problem:  In SAP, IDOC's are processing successfully with status 53 and updating the tables : KONH,KONP  successfully.
    But Table A957 which is passing against KOTABNR field is not pupulating with the Materials passing.
    Can anyone please guide me why the Materials are not populating in the table : A957.
    Regards,
    Sreeram

    Hi,
    I guess there might be some issue with VAKEY population.
    All the key fields in A957 should be concated properly while populating VAKEY. (Leading zeros must be prefixed to the material)
    Regards,
    Ganga

  • Inbound Processing of Idocs with status other than success

    Hi,
           I am new to ALE/Idocs. Can anyone  please let me know how can I process the Idocs which have the status other than 53.
    Thanks &  Regards,
    Indira

    Hi,
    In addition to the previous posts few more programs to process failed inbound IDocs are as mentioned below.
    - Use program RBDAGAIE to process edited IDocs (IDocs with status 69)
    - Use program RBDAPP01 to process IDocs failing with serialization issue (IDocs with status 66)
    - Use program RBDAGAI2 to process IDocs after ALE inbound error (IDocs with status 56, 61, 63, 65)
    ~ Bineah

  • "Error during application input" while processing IDOC with status 51

    Hi ,
    I tried to post an error IDOC with status "51" of message type FIDCC2 using program RBDINPUT, it just creates a message "Error during application input" . It is not calling the application dialog . Does anyone have answer for this?
    Thanks,
    Hemant.

    HI,
    Kindly check the RFC entries in t-code SM58.
    If any entries are their please release them manually selecting each one and press "F6".
    Regards,
    Anil.

  • Confirmation IDOCS are stuck with BBP_CO_WE

    Hi experts,
    We are building SRM 7 with ECS. We are connected to ECC 6 EHP4.
    When we create CF, IDOC is not transmitted to backend.
    In RZ20 we have those logs :
    Backend goods receipt errors | Status attribute | BBP_CO_WE
    In ECC inbound IDOCS are not there 
    It seems the problem is related to ECC config.
    Any idea to be able to send IDOC?
    Many thanks in advance.

    Hello,
    So, your IDoc is not in error.
    Check the 'Outbound Options' tab for message type MBGMCR of R/3 backend Partner Type in WE20 transaction.
    In frame dedicated for 'Output Mode', radio-button "Transfer IDoc Immed." should be selected.
    Execute same check for message type SYNCH.
    Regards.
    Laurent.

Maybe you are looking for