Problem in reporocessing Error Idoc

Hi,
We have created a customized Tcode to reprocess the error idocs (idocs in 64,51 status).
The report is developed using standard program RBDMANI2. The same program is used in BD87. After executing the idocs it create related sales orders.
The problem is : When we reprocess one error idoc on two differant system at the same time (probabaly at the same time upto seconds),  two sales orders are getting created.  Ideally one sales order should be created.
This is happening for only one kind of sales document type. There is no any hardcoading of document types in report.
I want to know whether there is any configuration related issue or what.
Please suggest.
Thank you,
madan shinde

Hi
You can use WE19 to debug the Idoc FM.
Check this link if it is helpful:
Debugging Idocs
Regards
Neha

Similar Messages

  • Problem in workflow Inbound error Idocs (IDOCAPPL)

    Hi All,
      First of all I am new to workflow. I have created a custom business object ZIDOCAPPL by copying standard object IDOCAPPL. My requirement is to send emails to the users with the inbound Idoc error details.
    My workflow has below tasks.
    Task 1: Create a entry in Ztable with error idoc details. (Background step)
    Task 2: Send a email to the list of users with EDIDC data.
    Task 3: Idoc foreground correction (Foreground step - Using IDOCAPPL-INPUTFOREGROUND method).
    Task 4: Delete the entry form Ztable, which was created in task 1(Background step)
    For this, I have created a ZIDOCAPPL BO and in that created methods for step 1(Create entry in ztable) and Step 4(Delete entry in Ztable).
    Triggering event (SWE2) : IDOCAPPL - INPUTERROROCCURED.
    So my problem is , I need to create below Function modules. Please suggest the logic for below function modules, as I did not understood clearly.
    1-  A new Function module for send email step, that creates the list of users. The user list need to be leveraged from Rule FM and the email through USR01. (This need to be called in my custom ZIDOCAPPL BO method and for  send email step of task 2)
    2- A new FM needs to fetch the positions (table HRP1001) under the sub org units (partners) again under the main Org unit The returned positions needs to be linked back to the task and also for the emails. ( I think this need to be linked to the Role of the idoc foreground correction task (Task 3).
    Appreciated your inputs. Thanks in advance.
    Thanks,
    Ranj.

    I recommend that you do NOT copy the object, but rather create a sub-type.

  • XI 2.0 problem: scenario xml - xi - idoc

    Hi!
    my scenario is xml -> xi -> idoc1, idoc2.
    when the interface start, if I call SXMB_MONI I see that idoc1 is correct; for idoc2 the system generate an error: idoc.adapter.generic, "MSGGUID 587E007DA385D54697B3F02220A78987: Tag ORDERHEADER found instead of tag IDOC BEGIN=.</"
    Can you help me to undestand the problem?
    10 points for you!
    Thanks,
    Gianluca

    Bruer,
    I use an interface mapping between xml (imported from SAP BBPCRM 4.0, data type OrderCreateOrChangeVendorOut) and Idoc custom. My mapping is graphical mapping without java class or xsl.
    My scenario work with one xml and two different idocs. Today I have added a second idoc. The problem is that the first one work correctly, for the new idoc generate an error for idoc_adapter.generic.
    The jar file for the mapping is mandatory for my new idoc?
    Thans you very mutch,
    Gianluca

  • Error: IDoc XML data record

    Hi all,
       We have file->XI->idoc scenario and the problem we are facing is like, when the idoc structure is prepared using XSLT mapping, when the idoc is ready to get in thru the idoc adapter we are getting the following error.
    <i><b>Error: IDoc XML data record: In segment
    Z1UKGAS_HEADR attribute  occurred instead of SEGMENT                                </b></i>
    Anyone faced the same issue....if so pls do throw some light into this issue....
      We r in XI 3.0 SP13...
    Thanks & regards,
    Jayakrishnan

    Hi,
    In an IDOC structure segment attribute is requried. From the error you posted, it looks like seqment attribute is missing.
    <Z>
       <IDOC BEGIN="">
          <ED SEGMENT="">
          </ED>
       </IDOC>
    </Z>
    Naveen

  • Problem with HR inbound IDoc

    Hi,
    I have a problem with processing inbound IDocs from an external payroll system to infotype 0008.  The process is quite simple; salary changes from the payroll system is recorded to the corresponding employee's infotype 0008.  When testing I noticed that that the new record is recorded as is.  For example if there is already an existing record with the validity dates 01.01.2010 - 31.12.9999 and the new record in the IDoc is 01.01.2011 - 31.12.9999, the new record is written as is.  I would expect the system to delimit the old record correctly - similar to what would happen if you maintain records online.  There is no error checking or any kind of processing done by the system. 
    I did some debugging and found out that the function module linked to process code HRMD writes the information directly to the database.  If this is a standard way of doing this, it is really unusual.
    Has anybody else encountered this?  Any pointers?
    Thanks.
    Edited by: Theo Droste on Jan 20, 2011 11:56 AM

    Hi
    This is correct, the ale programme writes the data directly to the database, I have faced this isssue on occassion. I once raised an oss message on this as well, and sap confirms this is what happens. If it is a sap to sap ale, it somehow seems to work, - this could be because the outgoing idocs are created by sap itself  but if it is a non sap to sap ale the onus is on us to ensure that the external system sends the correct data to sap in the way we intend it to be displayed.
    that is how it has been in my experience. It is unusual, but apparently not impossible. Please let us know if you find out anything different.

  • Error : IDoc XML data record: In segment attribute occurred instead of SEGM

    hi friends
    i am doing the file to idoc scenario. in message mapping i had done the static test. but what ever the fields i mapped in the idoc it was not populated in the idoc. and i am getting the error as
    error :IDoc XML data record: In segment attribute occurred instead of SEGMENT
    can any one solve the problem please
    thanks in advance
    Vasu

    Hi Vasudeva,
    Pls do check the nodes which you have mapped to. Also make sure that your SEGMENT field in the target structure is mapped properly.
    Cheers
    JK

  • How can we send Error Idocs via mail

    Hi,
    I have read read through forums and  understood that it can be achieved either through workflow or through report using table edidd & edids.
    If workflow option is used , does the mail trigger for every error idoc ? How can we send daily error report to user say by EOD containing all error idocs using all possible options.
    Regards,
    Rachel

    Rachel,
    I dont think so any direct Report will be available just to get Error IDOCs details. Although you can create a simple report to read the tables. An example is in below link.
    http://wiki.scn.sap.com/wiki/display/Snippets/Custom+report+for+IDOC+Monitoring
    Also, you can create a Query of EDIDC and EDIDS tables to obatin relevant information.
    Thanks,
    Ravi

  • I can't open iTunes on my pc in windows. I keep getting a Problem event: BEX error.

    can't open iTunes on my pc in windows. I keep getting a Problem event: BEX error.  How can i fix this?  need very detailed step by step instructions on how to fix. thx

    Check out this discussion link:
    https://discussions.apple.com/thread/2777410?threadID=2777410&tstart=15

  • Some of the error idocs are not falling into Workflow Inbox

    The extract of IDOC list with status 51 from WE02 transaction is not matching with Workflow inbox column "object", some of the idocs which are errored are not showing in the workflow inbox. Here we are in need to get all the errored idocs into the inbox. Please suggest me to proceed further.

    Hi Smita,
    Thanks for your reply.
    I have maintained the suggested role SAP_GRC_SPC_SCHEDULER in backend for an user id and i can able to see a job is getting completed in SM37.
    However, the task in the inbox hasnt come yet.Any idea you may have as to how much time it will take for task to come into inbox.Or is that i need to do any more extra task.
    Please advice.
    Thanks
    Ashok S

  • Problem in processing incoming IDOC

    Hi All,
    I have a problem while processing Incoming IDOC in the system.
    While I try to process and FI IDOC (without purchase order) in the system, by giving the appropriate GL account and cost centre where the document should get posted to (in transaction WE19), I find that the system creates the IDOC successfully with status 53. However, it creates a parked document in the system for the vendor.
    When I try to post the document through transaction FBV0, the system asks for a cost centre. Can you please clarify, why the system is asking for a cost object though it is given in WE19 transaction. Ideally while processing the IDOC the system should post the document directly as it has all the relevant details in the IDOC right?
    (Just for info, I have given the GL account details in segment E1EDP19 with qualifier 002 and the cost centre in segment E1EDP30 with qualifier 045)
    Expecting your help in this regard.
    Regards
    Nagarajan N

    Hi
    You can use WE19 to debug the Idoc FM.
    Check this link if it is helpful:
    Debugging Idocs
    Regards
    Neha

  • "Problem When Printing" error on Mac Mini

    Hi all,
    I just recently updated my Mac Mini from 10.3 to 10.4. Instead of Archive and Install I formatted and did a clean install.
    I have my printer set up, however whenever I try and print anything from any application I get a very unhelpful "Problem when printing" error, and nothing prints.
    I also get the same error when trying to save to PDF.
    My printer is a HP Deskjet 3750, and the driver is the one included with 10.4 (as per HP's instruction), but I don't think it's a driver problem as Save to PDF gives me the same error.
    I've already tried repairing permissions. Anyone know what could be causing this. Any help is greatly appreciated.
    Thanks.

    Bugger. PSR is often a winner
    You could try installing Gutenprint 5.0.1 available from Sourceforge (it's about 15MB). It's an updated version of the included GIMP-Print drivers and may repair/replace/install some of the core files. Otherwise you may have to contact Apple and see if you can get 10.4.9 mailed to you.

  • Error : idoc xml data record : in segment attribute instead of SEGMENT

    hi all
    i am doing the file to idoc scenario. in that i am getting the error
    error : IDOC XML Data record : In segment attribute instead of SEGMENT
    i am doing this scenario since 4 days.
    can anyone help me
    thanks a lot
    Vasu

    in ref. to my post in your earlier thread.
    >>>>
    in your mapping check, in your IDOC if Begin , segment etc are mapped to a constant say '1'.
    Also ref: In segment IDOC attribute I occurred instead of SEGMENT

  • Outbound error IDoc reprocessing

    I have a scenario like whenever an outbound idoc is in error status, should be able to correct the idoc n reprocess it.
    Suppose outbound idoc is in status 02. System process code will notify the agent assigned in partner profile. When i execute the workitem and corrected the port and try to reprocess, this status is set to 30. My requirement is once i correct the port status should become 03. How do we acheive this ? (not through report rseout00 )
    1. In general scenario how do we handle outbound error idocs?
    2. Is system process codes are used only for notifications or error processing?
    Inputs will be appreciated regd outbound error reprocessing .
    Thanks.

    Hi Indira,
    1. In general scenario how do we handle outbound error idocs?
    You can use transaction BD87 to monitor the IDoc statuses.
    and use the following programs to reprocess outbound and inbound error IDoc(s).
    RBDAGAI2 - Re-processing of IDocs after ALE Input Error
    RBDAGAIE - Reprocessing of Edited IDocs
    RBDAGAIN - Process Outbound IDocs with Errors Again
    RBDAGAIP - New Posting of Partially Posted IDocs
    RBDMANI2 - Manual Processing of IDocs: Post IDocs Not Yet Posted
    RBDINPUT
    2. Is system process codes are used only for notifications or error processing?
    The process code ise used in both ALE and EDI framework to identify the function module or API (Application Programming Interface) to be invoked for subsequent processing.  Inbound as well as outbound interfaces use process code but for different purposes. Outbound process codes are stored in table TEDE1, while inbound process codes are stored in TEDE2.
    Hoep this will help.
    Regards,
    Ferry Lianto

  • AES filing error - Idoc Outbound Processing: EDI number cannot be compiled

    Hi Gurus,
    We are configuring the AES filing.
    we've done the EDI  configI and initally we got the error that EDI partner is not maintained. As per the suggestions from this Forum we've added the cusoms office details in geography tab.
    Now when we are trying to process the same, we are getting the error "Idoc Outbound Processing: EDI number cannot be compiled"
    All suggestions are welcome.........
    Thanks in Advance.

    Hi Shiva,
    Here goes the solution: you need to maintain the Number of the Number Ranges starting with "10" and this applies only to GTS system as this is HARD-CODED in the Program, apart from 10 any number of the number range will result in an "EDI Number Range compilation" error.
    Cheers
    Harsha

  • Error idocs

    How can  we  you navigate to see the error idocs ?

    Hi
    Transact RFC error
    tRFC Error - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
    Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
    queue thats under outbound processing and click on display the IDOC which is on the menu bar.
    Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
    place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
    (Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
    Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
    to the particular TRFC request for that Idoc.
    OR
    Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
    (For this in RSMO Screen> Environment> there is a option for Job overview.)
    This Data Package TID is Transaction ID in SM58.
    OR
    SM58 > Give * / user name or background (Aleremote) user name and execute.It will show you all the pending TRFC with
    Transaction ID.
    In the Status Text column you can see two status
    Transation Recorded and Transaction Executing
    Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
    execute the "Execute LUWs"
    OR
    Directly go to SM58 > Give * / user name or background (Aleremote) user name and execute. It will show TRFCs to be executed
    for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
    EDIT ---> Execute LUW
    You can use report RBDAGAIN to send IDocs that are set to status "02".
    Refer note : 784381
    error relates to IDocs processing in source system, initially check the connection with the BI system and source system.
    If it is fine check the IDOCs in source system go to BD87->give Ur user ID and date->execute->you can find Red status Idocs select the erroneous Idoc->Rt.click and select Manual process.
    I hope it solves the issue...
    Regards
    gaurav....

Maybe you are looking for