Error in idoc posting

We have a scenario where some 20 to 25 Idocs which r at 64 status are processed by the batch program(for rbdapp01) to post them in the system.What happens is some idocs take few extra secs for processing so the the other idocs get posted in 51 status saying material and batch is locked by the batch program....
what we do is we go reprocess the idocs manually..
This happens frequently now...
So whatz the possible solution for this...?
Pls help...
Thanks,
Larry

Here is the documentation of the program RBDAPP01 which I am sure you might have read. Packet size has a role to play in it, but locking issues are typically due to parallel processing. Also, it could be the time of the day. Say you run this when there is lot of activity, online or background that also has something to do with the material/plant/batch etc. In that case, even if you have your IDocs serialized, you will still be facing the same issue as now the locks are created by other processes.
<i>
Short text
Inbound Processing of IDocs Ready for Transfer
Description
Report for processing inbound IDocs not passed to the application immediately.
This report forwards all IDocs with:
Status 64 "ready to be passed to application"
Status 66 "IDoc is waiting for predecessor IDoc (serialization)
These match the selection criteria to be passed to the application for further processing.
Essentially there are two groups of IDocs:
IDocs to be serialized in accordance with the associated object.
All other IDocs
There are also two types of processing:
Serial processing (IDocs are processed one after each other in one process)
Parallel processing (IDocs are passed in packets to other processes for processing).
Purpose of parameter 'Packet size': For IDocs to be serialized by object and for activated parallel processing, this parameter specifies the size of a packet to be processed in a task. If applicable, independent objects are processed in a separate task as with serial processing. (Large packet sizes lowers the level of parallel processing).
For all other IDocs, as far as possible, an appropriately sized document is passed to the application. On the one hand, this supports some applications capable of mass processing.  On the other hand, the number of parallel packets is less as with activated parallel processing. (Lower system load, longer runtime).
Notes on Program Terminations in Parallel Processing
In parallel processing, processes containing the IDocs to be processed are started in parallel. If there is a termination (dump/ A message), no message is issued by RBDAPP01. The best way to identify such problems is to run RBDAPP01 without parellel mode after a scheduled RBDAPP01 with parallel mode. Then a termination is logged (dialog message or message in job log).
Output
The processed IDocs are output.</i>

Similar Messages

  • IDOC posted with error

    Hi
    working on File2 IDOC scenario..my idoc posted .. but that is red and green in SXMB_MONI... where should I check for correct the problem?

    I am getting error like this :(SXMB_MONI)
      <?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
    - <!--  Call Adapter
      -->
    - <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
      <SAP:Category>XIAdapter</SAP:Category>
      <SAP:Code area="IDOC_ADAPTER">ATTRIBUTE_IDOC_METADATA</SAP:Code>
      <SAP:P1>I::000</SAP:P1>
      <SAP:P2 />
      <SAP:P3 />
      <SAP:P4 />
      <SAP:AdditionalText />
      <SAP:ApplicationFaultMessage namespace="" />
      <SAP:Stack>Error: I::000</SAP:Stack>
      <SAP:Retry>M</SAP:Retry>
      </SAP:Error>
    please help me

  • IDOC POsting Error: Transition no. OBJ_SYS is blocked by another user

    Hi Experts,
    I m sending the XML from a third party system into SAP using XI as middleware for IDOC posting (FB01).
    I m getting an error <b>Transition no. <xx> is blocked by another user</b> while sending intercompany and cash applications. SAP is unable to process such XML directly.
    But if i login to SAP and mannually post the IDOC, it is getting posted successfully.
    Any idea what may be the cause?
    Useful answers will be rewarded for sure.
    Regards
    DhanyaR Nair

    Hi Dhanya,
            In your inbound idoc processing program, pls do use the lock mechanism for the FI document which you are processing and if it cannot be locked then keep it on wait for sometime and check for the same.
            If its a standard program check whether it can be done in XI.
          When SAP is locking the transaction it will be unlocked after the commit work and hence its happening.
      The reason why you may not be getting this in individual processing is that you are doing the same thru a single session. And the lock if am not wrong is happening in table level and not in record level.
    Cheers
    JK

  • Idoc Error - EDI: Syntax error in IDoc (segment cannot be identified)

    Hi All,
    have created a new reduced message type for our new vendor A/C group through BD53. Also done reqd config for sending the vendor master through this message type. .
    I have created couple of vendors for testing with X01 with withholding tax functionality and when try to send these vendors , Idocs are getting failed .
    When I create vendor without withholding tax functionality , idoc is getting posted succesfully . If create vendor with entries in the feild whih are related to withholding tax  . Idocs are getting failed .
    If I see the status in WE05 ,Idocs which are posted succefully are showing the basic type as CREMAS03 . For idocs which are getting failed have the basic type as CREMAS04 and also the extension  as Z1CREMAS . I don`t understand why the system is defaulting CREMA04 & Z1CREMAS when I send the vendor master with withholding tax feild entries.
    I am not much familiar with ALE /Idoc set up. Please can any body help me to resolve the issue.
    The error message in we05 as below
    EDI: Syntax error in IDoc (segment cannot be identified)
    Message no. E0078
    Diagnosis
    The segment Z1LFA1M does not occur at the current level of the basic type CREMAS04 (extension Z1CREMAS).
    This error can have several reasons:
    The segment Z1LFA1M is assigned to a group whose header segment does not occur.
    The segment Z1LFA1M does not exist in the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
    The sequence of segments in the group in which the segment appears is incorrect.
    Previous errors ('mandatory' segment or group missing) may be due to this error.
    Procedure
    Please check the IDoc or the syntax description of the basic type CREMAS04 (extension Z1CREMAS).
    Thanks

    Hi,
    I don`t understand what do you mean release after adding segment.
    Message type works i.e. Idoc get posted if I send with the  vendor w/o withholding tax field entries. Idoc fails when send vendor with withholding tax field entry.
    Regards

  • EDI: Syntax error in IDoc (mandatory segment missing)

    HI all,
    Error Message - EDI: Syntax error in IDoc (mandatory segment missing)
    Status ID - E0
    Message No - 072
    Status of the IDoc - 26
    Please help me how to solve this issue?
    Thanks,
    Srini

    Hi,
    This error normally comes up when the sequence of segments has been disturbed.
    For successfully posting an IDOC you need to maintain the sequence of the segments as in WE30.
    You can also check which segments are mandatory in WE30 by clicking on the segment name and the pop up that comes.
    Thanks,
    Manish

  • How to Debug IDOC posting

    Hi,
       Could anyone please advise how to debug an IDOC posting. I am new to ABAP.
    regards,
    Munavar Basha A.K.

    Hi,
    1)Use tcode we19 , enter your idoc no and click on the inbound function module push button then check call in debugging mode to debug.
    or
    1. Go to BD87
    2. make a right click at the IDoc and choose restrict and process.
    3. delete the check at the bottom(Background Processing)
    4. Go ahead
    5. edit -> process -> Foreground at Error
    Thanks Hope this will be Helpful
    Thanks
    Kalyan

  • All ALE configuration are right, but why errors in idocs?

    hi any anybody explains why error are occurs in IDOCs when all ALE setting are ok. please explain any scenario

    Hi,
    One of the commonly occuring error status - 26(Syntax error in Idoc) Outbound
    The reason for the occurence of this error is mostly related to the structuring of the segments in the IDoc, the normal structure should have a parent segment followed by the sub segments but in cases when that fails to happen, the Idoc is in 26 status. For correction of this error goto WE30 and check if the mandatory segment is checked.
    status 51(Application Document not posted) Inbound
    This normally occurs due to the incorrect data being populated in the segments or it could also be related to serialization.
    ~Krithika

  • Error in Idoc is 51

    I have posted one Idoc and it was succesfully generated.
    But I don't want duplicate Idocs  ( with same data ) using we19.I was using function module to avoind duplicates.
    But I have generated next Idoc...
    Have got
    Error in Idoc is 51.
    Check if invoice already entered under accounting doc. no. 1600002035 20
    Is it okay.. is it considered as stoping of duplicate Idoc generation.
    Thank you.

    Hi,
    I believe when you write avoiding duplicate Idocs ,it means same data should not get posted in SAP via IDOC.
    The error which you have got means -- there is already a document in the system posted by another IDoc & the current IDoc can't be posted due to duplicate data.
    This is avoiding duplication of invoice posting.
    Not avoiding duplicate IDoc creation.
    Thanks.
    Mark points if helpful.

  • Using INVOIC01, IDOC posts invoices against POs that weren't sent to vendor

    Does anyone have any suggestions on how to prevent the IDOC INVOIC01 invoices from posting against POs that were not originally sent to the vendor??  (BSART = INVO)
    For example, vendor (1521) sends an electronic invoice file processed as an IDOC.  Vendor 1521 includes an invoice against a PO that was sent to vendor 7549.  Since the PO exists, the IDOC posts against it.  I want to make this a hard error (a 51 status).
    Please help,
    Cindy

    Hi Cindy,
    If you are using a standard process code for this interface, you will not have this sort of problem as the combination of Vendor and PO number are validated before that is posted. If you are using a custom stuff then you need to check the table EKKO by passing the vendor number and PO number as input to that, if that combination exists go ahead otherwise throw the idoc into 51 status.
    Thanks,
    Mahesh.

  • J2iun Execution and Error in FI posting (Message no. 8I280)

    Hi ,
    At our end J2iun were never posted in SAP and all excise return are being handled manually.
    Now we are trying to execute J2iun for each month of the last year ( April '08 to march '09) and trying to update our system till march'09 so that from this month onwards , excise returns can be handled thru SAP.
    We started with April'08 and in order to get J2iun posted for the month of April'08 , we opened the desired FI periods (2008/1) thru OB52.BUT when we were trying to post J2iun for the month of April'08 , system is prompting an error
    "Error in FI posting 20090408 Message no. 8I280"
    We couldn't understand why this message is being appeared when required FI periods are already opened. ( In fact we tried with some JV enteries in that period and they are getting posted sucessfully )
    Is it because MM april'08 period is already closed ??? (in OMSY , open periods are April'09 and March'08)
    If yes , then is there any way to make April'08 MM period open ?
    If back MM period opening is not possible then what could be the best method to get GLs and Registers Balances updated with correct value of MARCH'09 closing Balances.
    So that j2iun of april'09 can be executed perfectly
    Thx in advance for all yr replies
    Regards
    Shrey

    tHX ,
    mm PERIOD SHOULD BE oPENed TO PROCESS J2IUN.
    cOMMULATIVE RUN IS NOT POSSIBLE, AS J2IUN ALWAYS PICKS THE PAYABLE BALANCE OF THE FIRST PERIOD DATE ENTERED
    REGARDS
    sHREY

  • Error in Idoc with status 26

    Hi,
    IDOC  showing an error messge when syntex check.
    EDI: Syntax error in IDoc (segment cannot be identified)
    Diagnosis:
    The segment E1EDP19 does not occur at the current level of the basic type ORDERS01 (extension ).
    This error can have several reasons:
    The segment E1EDP19 is assigned to a group whose header segment does not occur.
    The segment E1EDP19 does not exist in the syntax description of the basic type ORDERS01 (extension ).
    The sequence of segments in the group in which the segment appears is incorrect.
    Previous errors ('mandatory' segment or group missing) may be due to this error.
    Please help me....
    Regards,
    Sudha

    Hi,
    I have pasted a portion of my code:
    DATA: BEGIN OF GT_EDIDC OCCURS 0.
            INCLUDE STRUCTURE EDIDC.
    DATA :END OF GT_EDIDC.
    DATA: BEGIN OF GT_EDIDC1 OCCURS 0.
            INCLUDE STRUCTURE EDIDC.
    DATA :END OF GT_EDIDC1.
    DATA: BEGIN OF GT_EDIDD OCCURS 0.
            INCLUDE STRUCTURE EDIDD.
    DATA :END OF GT_EDIDD.
    DATA : BEGIN OF GT_Z1ZPSOBJLOC OCCURS 0.
            INCLUDE STRUCTURE Z1ZPSOBJLOC. ' segment name
    DATA : END OF GT_Z1ZPSOBJLOC.
    * Control Record
    FORM BUILD_CONTROL_RECORD .
      GT_EDIDC-MESTYP = C_MESTYP.
      GT_EDIDC-IDOCTP = C_IDOCTP.
      GT_EDIDC-DIRECT = C_1.
      APPEND GT_EDIDC.
    ENDFORM.                    " built_control_record
    *&      Form  built_data_record
    * Data record
    FORM BUILD_DATA_RECORD .
      LOOP AT GT_Z1ZPSOBJLOC INTO WA_Z1ZPSOBJLOC.
        GT_EDIDD-MANDT = SY-MANDT.
        GT_EDIDD-SEGNAM = C_SEG.
        GT_EDIDD-SDATA = WA_Z1ZPSOBJLOC.
        APPEND GT_EDIDD .
      PERFORM DISTRIBUTE_DATA.
      ENDLOOP.
    ENDFORM.                    " built_data_record
    *&      Form  distribute_data
    * Distribute Data
    FORM DISTRIBUTE_DATA .
      CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE'
        EXPORTING
          MASTER_IDOC_CONTROL            = GT_EDIDC
        TABLES
          COMMUNICATION_IDOC_CONTROL     = GT_EDIDC1
          MASTER_IDOC_DATA               = GT_EDIDD
        EXCEPTIONS
          ERROR_IN_IDOC_CONTROL          = 1
          ERROR_WRITING_IDOC_STATUS      = 2
          ERROR_IN_IDOC_DATA             = 3
          SENDING_LOGICAL_SYSTEM_UNKNOWN = 4
          OTHERS                         = 5.
      CASE SY-SUBRC.
          WHEN 1.
          MESSAGE E004.
        WHEN 2.
          MESSAGE E005.
        WHEN 3.
          MESSAGE E006.
        WHEN 4.
          MESSAGE E007.
        WHEN 5.
          MESSAGE E008.
        WHEN OTHERS.
    * Do Nothing
      ENDCASE.
      COMMIT WORK.
    * Clear IDOC data internal table after use
      CLEAR GT_EDIDD.
      REFRESH GT_EDIDD.
    ENDFORM.                    " distribute_data
    Hope it proves useful.
    Regards,
    Gayathri

  • Error: No depreciation  posting required in period 009 (current period)

    Hi,
      I am getting error " No depreciation posting required in period 009"  and  009 is my current period.
       The description of the error says " Do depreciation is posted, since according to the posting cycle no postings are required in this period".   In fact this is the first time i am running depreciation. I want to post the depreciation for 1st period. More over i could not able to see the planned values in asset explorer also.
       Whenever i am entering this asset in the asset explorer it is  giving the above error. But while i run the depreciation its not giving any error. When i check in spool to view the depreciation, its giving msg as "List contains no data" check error log.
      Could anyone help me in resolving this error.  what could be the reason for this error.
    Thanks
    Sabera

    Hi,
      I checked in TABA table, its showing that till 9 the period depreciation has been posted. But i have not posted the depreciation. If it is posted, then it has to show in the planned values as posted, but its showing as "No depreciation"  and its not even showing the depreciation for other periods.  Could you able to clear this query? I wonder why it is giving this kind of error.
    Regards
    Sabera

  • Error occurred during post handling RS_AFTER_IMPORT for UPDR L

    Hi friends,
    I need your help for 2 issues related to transport
    I am getting error while transporting the request from BW DEV to BW QAS..Please help me regarding this issue..
    1.)Error occurred during post handling RS_AFTER_IMPORT for UPDR L
           The errors affect the following components:
          BW-WHM (Warehouse Management)
    2.)Start of the after-import method RS_UPDR_AFTER_IMPORT for object type(s) UPDR (Activation Mode)
           Error when activating update rule
           IC=0CRM_PROD IS=0PR_IL_PROREF_ATTR error when checking update rules.
    Friends these are the two issues im facing while doing the transports._i have checked the update rules in the BW DEV it is working fine._please give some solutions to overcome this issues.
    Thanks
    Gnana Baskar

    Hi Gnana,
    Since u r telling tht the update rules are working fine in the Dev system, request u to perform some checks:
    1. The Update rule needs to be in active version.
    2. The InfoObjects used in the target InfoProvider should be present in the QA system/attached to the request in which u r transporting the changed Update Rule.
    3. Manually add objects, if needed all the Before/After objects in the new request and reactivate the Update rule, if it asks for a request give this new request number.
    4. Compare the data model in Dev and QA system and try finding the disconnect between them.
    Hope this helps.
    Regards,
    Kunal Gandhi

  • Error occured while posting the job schedule for JDBCAdapter

    Hi Experts,
    In Application Log in Path: "/usr/sap/<SID>/DVExxxx/j2ee/cluster/server1/log", I see the error:
    #/Applications/ExchangeInfrastructure/AdapterFramework/Services/Util
    ##com.sap.aii.af.service.scheduler.SchedulerManagerImpl.postJobScheduleOthers(String, int)
    #J2EE_GUEST#0##n/a##f7956e1f6b4711e0b851001e0b5d3ac8#SAPEngine_Application_Thread[impl:3]_23##0#0
    #Error#1#com.sap.aii.af.service.scheduler.SchedulerManagerImpl#Plain
    ###error occured while posting the job schedule for JDBCAdapter_9f0584b1bcb33b94b67ada456233bcb8 with 2#
    Frequently are created Lock's and I need remove them in Visual Admin.
    Any idea about this error?
    Tks in advance.

    Hi,
    After applying the SP 23 Patch Level 08, LOCK JDBC problems stopped.
    But now when a network error or database error, the JDBC Sender Communication channels that were open to connection, are blocked.
    Even following the instructions in [SAP Note 1083488 - XI FTP_JDBC sender channel stop polling indefinitely (04_04S)|https://websmp230.sap-ag.de/sap(bD1wdCZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1083488] the problem continues.
    I've already set the parameter "taskTimeout" and selected the option "Disconnect from Database After Each Message Processing" but not resolved.
    Any ideas?
    Thanks in advance.

  • Account Determination error during MIGO Posting

    Dear All,
    Kindly help resolve error duirng MIGO posting  "ACCOUNT DETERMINATION FOR ENTRY GBB____ZOB TF01 not possible".  This is Message no. M8 147. 
    The error happens once the transaction is being saved.
    Hoping for your positive response.
    Thanks and regards,
    ching

    Hi,
    Goto OBYC Transaction.
    Select the Procedure as ' GBB" and enter the Chart of Accounts ( for Your Company code)
    Enter the Valuation modifier as assigned to others.
    Enter the General modifier as ZOB
    Enter the Valuation class  ( with respect ROH/SFG others)
    Enter the Debit/ Credit G/L account
    save then proceed your transaction MIGO.
    rgds
    Chidanand

Maybe you are looking for