Skip to Content
author's profile photo Former Member
Former Member

How to find Idocs for BW Load

Dear SDNers,

Today I got an issue; the jobs of BW data loads were struck up due to they were in released state(Delayed more than Hrs). So one of my colleague got processed/pushed out Idocs. After that loads went successfull. How do we know the Idoc Number of particular load/data source. I read some SDN forums to process them using BD87 but how to find the exact Idoc Numbers . As we can find Idoc Number in monitor for successful load but here how do we get exact info.

Thanks,

Swathi

Add a comment
10|10000 characters needed characters exceeded

Related questions

3 Answers

  • Best Answer
    Posted on Jun 28, 2011 at 04:49 AM

    Hi,

    Check the DataSource in RSA3, if it is working fine and able to see the data in RSA3, there is no problem in DS level, then check the Mappings and any routines in BW for that DS, if this is also fine then check the below options.

    See Dumps in ST22, SM21 also.

    Check RFC Connection between ECC and BW systems, i.e. RSA1-->Source System->Right Click on Source system and Check.

    You must have the following profiles to BWREMOTE or ALEREMOTE users.So add it. Bcoz either of these two users will use in background to get extract the data from ECC, so add these profiels in BW.

    S_BI-WHM_RFC, S_BI-WHM_SPC, S_BI-WX_RFC

    And also check the following things.

    1.Connections from BW to ECC and ECC to BW in SM59

    2.Check Port,Partner Profiles,and Message Types in WE20 in ECC & BW.

    3.Check Dumps in ST22, and SM21.

    4.If Idocs are stuck i.e see the OLTP Idoc numbers in RSMO Screen in (BW) detials tab see in bottom, you can see OLTP Idoc number and take the Idoc numbers and then goto to ECC see the status in WE05 or WE02, if error then check the log else goto to BD87 in ECC and give the Idoc numbers and execute manually and see in RSMO and refresh.

    5.Check the LUWs struck in SM58,User Name = * (star) and run it and see Strucked LUWs and select our LUW and execute manually and see in RSMO in BW.

    See in SDN

    loading-error-in-the-production-system

    IDOC getting struck at TRFC (SM58)

    1.Reorg of table (ARFCSSTATE )

    2.Incraesing the resources in the system (no of processes and memory ) , as this issue happens owing to this.

    Source system tries to send TRFC to target and if there are no WP's available it will come to Transaction Recorded state, and form here it will not try to send this TRFC.So you have to execute this manually.

    Also we can increase the timeout parameter so that it can try few more times to send before actually it comes to recorded state.

    Thanks

    Reddy

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jun 28, 2011 at 05:04 AM

    hi,

    as additional info to the above:

    you can find the idocs in we02/we05 by putting the partner port (your bw system) and by the date/time (begin and end of your load)

    in order to automatically reprocess the hung idocs, you can schedule report RBDAPP01 to run on a regular basis.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Aug 17, 2016 at 03:18 PM

    Thanks a lot Mr.Surendra Kumar,

    I am Struggling to find Idoc number, your post has helped me.😊

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.