Hanging iDoc

Hi Gururs,
Would someone please let me know what will happen if I deleted a Hanging iDoc via WE11 and not via deletion in transaction /weinbqueue?
This hanging iDoc cannot be open in /weinbqueue transaction as runtime error id occuring and my last option is to delete via WE11?
Any advice would really help,
Thanks,
Raymond

Hi Pavan
I did that
I deleted even the port and recreated it both from idx1 and idx2 , but as soon I execute the scenario then the Old metada data is created.
I checked in SAP system and only the new structure of the IDoc exists.
I don not know where does the old metadata come from
Thanks.

Similar Messages

No IDocs could be sent to BI using RFC.

We are experiencing this error while loading data from R/3 to BI 7.0. The exact problem is that these Idocs eventually get transferred to BI but at a very very slow rate:
For a job that takes 10secs to load, you can have it running for 4hours.
How can we resolve fast pls?
Note there have been steps taken by our basis team all to no avail.
SM58 on BI doesnt throw up any hanging Idocs
=============================================
Errors while sending packages from OLTP to BI
Diagnosis
No IDocs could be sent to BI using RFC.
System Response
There are IDocs in the source system ALE outbox that did not arrive in the ALE inbox of BI.
Further analysis:
Check the TRFC log.
You can access this log using the wizard or the menu path "Environment -> Transact. RFC -> In source system".
Error handling:
If the TRFC is incorrect, check whether the source system is fully connected to BI. In particular, check the authorizations of the background user in the source system.
============================================
regards,
Nneka

Hi
I think that you should perform with your basis some checks in your R3 environment.
First go to we20 / we21 and check if you have the RS* message configured in the LSR3SID system.
Also ask to your technical team if they saw some RFC response time issue in the environment. Sometimes you have a large wait time and you can set a RFC groups in order to avoid that.
Be sure that the user used in the RFC connections are correct and if the roles assigned are the necesary.
If all of this points are correct you can try to reduce the amount of records and the size in every InfoPackage .
hope this help you

0CUSTOMER Delta Error

My recent delta from R/3 for a customer showed his street address and REGION being changed , however R/3 shows the change occured last september.
Info Object - 0CUSTOMER
Data source is Delta
Any ideas....
All teh deltas are running fine, in fact we did a full/init recently and deltas all doing good.
Any help in this is appreciated.

Hi Gopikrishna,
We had a similar issue recently when soem records that should have been in a delta load 4 months back, suddenly were loaded to BW. The issue was caught due to a date we maintain in the data and the sequence messed up the data (this was a transactional load). The reason turned out to be that the IDocs for this load were "stuck" on R/3 since Feb and another job that is supposed to process all 'hanging' IDocs was executed.
But as your situation is with master data, I guess it would not be a problem...

Delta error in production

Hi,,,
we are updating one cube through DSO during last delta its showing reuest to be red n wen we see the monitor screen its showing yellow.... plz let me know what steps shud be taken to repeat delta at DSO itself .
urgent
help wud b appreciated

Chk for any jobs in SM37 or any background process related to the load in SM66 or SM50. In datatarget if the load is running for long time it might change to red..that doesnt mean the laod has failed. Chk for any hanged IDOCS in sm58.
Regards,
B

Regarding Delta loads at multiple times

Hi,
We have one infopack which loads from same datasource into same Cube, but has included in two process chains which run at different times.
The first process chain failed, thus load from infopack also failed giving some hanging IDOc error. We did not do the repeat delta.
Next process chain ran successfully and pulled few deltas. My question is has all the delta's been pulled by this second process chain? Or do I need to delete the both these requests (from two process chains) and do the repeat delta manually?
Please note the first request is in red status and second request is in green status.
Regards,
Vikrant.

Hi Anil,
Thanks for replying. But are you sure that missing delta's too would have come? Becasue my understanding was that until we don't set the request to 'red' manually (even if its in red status), missing delta's wont come.
But in our case:
1. First load failed
2. We 'did not set' it to red manually
3. Second load was successful and pulled few records.
Now do u think that we don't have to do anything extra other than deleting the red request from the Cube?
Please let me know.
Regards,
Vikrant.

Old IDoc metada hanging

Hi
I have to remove one field from the extended IDoc , reimported the new IDoc to PI and deleted the old metadata and tried to create the new metadata in IDX2
my problem is the old metadata is always being created , even the Idoc structure does not have any more the removed field, it seems that the old metada is hanging somewhere and and the new metada is not allowed to be created
plz suggest.

Hi Pavan
I did that
I deleted even the port and recreated it both from idx1 and idx2 , but as soon I execute the scenario then the Old metada data is created.
I checked in SAP system and only the new structure of the IDoc exists.
I don not know where does the old metadata come from
Thanks.

Info IDoc received with status 8 infopackage hanging in yellow status

Hi All,
when I extract the Text data without data selection it is fetching the 14 record into BW and changing the status to green,
however when I go with data selection it has No record for this selection in RSA3 as well in BW .
when I do this data selection in infopackage in BW it is bringing ' 0 ' records and hanging in to yellow status in RSMO for more than two days. it is not turning it to red/green
it shows in Monitor with message " Info IDOC received with status" in yellow status.
I have found the OSS 713427, it is already had this correction .
when I check in SM37 job is completed immediately.
there is no short dump
Many Thanks
Ramm

Hi Robort,
thanks for reply
there is no data for this data selection and there is no IDOC processed in BD87 or we02.
I checked out the note and its only for IDOC stuckup .
may I have any other suggestion.
many thanks
Ram

Error in IDOC-XI-IDOC scenario

Hi folks,
Let me explain the issue. This is an IDOC-XI-IDOC scenario. No BPMs involved. SAX parsing used to parse the IDOCs.
We had around 35000 IDOCs coming in from Brazil system, and they are all stuck in SMQ2 (Inbound queue) in XI. The first message of every queue is in SYSFAIL status, with the status text as Problems found during the EXPORT to specified keyin table.
When I try to execute the queue manually, nothing happens, but an error comes at the bottom of the screen, saying Function module does not exist or EXCEPTION raised.
I checked the dump on ST22, and it shows 130 runtime errors yesterday. The name of the runtime error is EXPORT_TABLE_UPDATE_CONFLICT.
In the what happened? part of the dump, it says Error in ABAP application program. The current ABAP program CL_XMS_PERSIST=============CP had to be terminated because one of the statements could not be executed. This is probably due to an error in the ABAP program.
Even SXMB_MONI is not opening (for yesterdays date). When I try to open it, it hangs for a long time, and finally opens an ABAP Runtime Errors page with the runtime error titled as SNAP_NO_NEW_ENTRY and the error short text as Runtime error: Unable to write short dump
Please advise.Thanks a ton!
cheers,
Prashanth

Hello Prashanth,
First of all this is an XI issue and belongs in that forum.
The export problem is typical to situations where your XI DB is out of space/out of table space. Please check with your Basis team.
Function module does not exist or EXCEPTION raised- This message is a standard ABAP RFC message. For an RFC function call to succeed, you need the same RFC function to exist on both systems. However this is probably not the case- it is more likely that you're out of DB space as I already wrote.
Good Luck (don't forget to award points)
Ofer

PI 7.11 sp5 post install steps - SLD update hangs in IE browser

Hello gurus,
This is my first shot at installing PI ever. We decided to go with PI 7.1 EHP1 and SP5. I think the latest may be SP6.
At any rate, we're doing this on AIX 6.1 and Oracle 10.2.0.4.
I followed the install Guide exactly. Did the sapinst, oracle and patch. Next, I manually updated the KERNEL, IGS , JVM, Then I updated SPAM, SAP_BASIS, then all the other abap components. Then did JSPM and all those components. Everything matches SP5 for PI 7.11
https://websmp204.sap-ag.de/maintenanceNWPI71
SAP_ABA     711     0005     SAPKA71105
SAP_BASIS     711     0005     SAPKB71105
PI_BASIS     711     0005     SAPK-71105INPIBASIS
ST-PI     2008_1_710     0003     SAPKITLRE3
SAP_BW     711     0005     SAPKW71105
ST-A/PI     01M_BCO710     0001     SAPKITAB8F
Now I'm doing the post install steps that are in the instguide. THere are tons of steps, but let me go over the big ones and where I'm having a problem:
READ ALL THESE NOTES:
Note 1309239 - Configuration Wizard: PI NetWeaver initial setup
Note 1286149 - Configuration Wizard: PI Self Test for NetWeaver
Note 1107808 - Collective Note: Configuration Wizard 7.1
Note 1286428 - Configuration Wizard: PI Wizard Templates overview
Note 1115280 - PI CTC: Running SAP NW for PI in a different client
At this point, based on being at PI 7.11 and SP5, I did the client copy. from 000 SAP_UCUS to my new 400 client. Then I did 001 SAP_USER to my new 400 client.
Then I followed the steps to link the java UME from 001 to 400. No problem after restarted SAP, it goes to 400.
Now, the next step as I see it is to run the initial config wizard out of NWA. I did that, no errors.
My problem is when I get to updating the SLD. I started at cimsap 1.5.42 and CRDelta 5.0....
I updated cimsap to the cimsap51509_1-20005942.zip which took me to 1.6.9
Next, I tried to import CRDelta51509_1-20005942.ZIP. I "browse" to find it during the import, but when I click the "IMPORT" button, my browser hangs...
I don't even get to the next page where it would be one more "warning/info" before I could really start the import.
I didn't find anything in the work directory or the cluster/server0/log directory.
I search all through SDN/OSS but could not find anyone who had this problem.
Where did I mess up? Are there other config wizards I should have run before I tried to update the SLD?
--NICK

Hey Caio,
Thanks for the response but it doesn't actually answer my question. But to that point, for a "basic" PI post install, which of the NWA config tasks would you run other than the "initial config" ? And would you run them BEFORE you updated the SLD content (cimsap/CRDelta) ?
NW: PI - AS ABAP (Basic Configuration for Idoc, Proxy): Maintain
PI Adapter Engine in JPR Mode
PI Demo Client
PI Full Qualified Host Name
PI Self Test for NetWeaver
PI SLD Self Registration
Specifically, I did the SAPINST - ABAP/JAVA patches - Client copy - and THEN the initial config wizard (Setup a new local SLD, ). Also, during the initial config, I clicked the box marked "This SLD will be used as a name server for development" and my PI server hostname was already in the box marked "object server name". This config took about 30 minutes. I didn't see any errors or warnings. although I didn't view the log. I did go into Java JEE services and Filter for Services with name "XPI". All were green.
THEN I tried to update the SLD content.
any thoughts appreciated.
NICK

View the Idocs in Source System

Hello
I have triggered a ino package load to BI. Now the job is just hanging and is not bringing in any data. Please can someone tell me where can i view these idocs in the source system.
Thanks

Hi
IDocs at Source system --BD87 / WE19/WE20/WE30/WE02 are the Tcodes for IDOCs
Till42 Outbound Idocs after 50 Inbound Status Idocs.
You can even see the Idocs at Info Package -- Monitoring -- Environment - Idocs at Source system.
Check your RFC at SM58/SM59 -- If the Queue Stuck -- Execute LUWs Manually.
When the IDOCs are Taking time to process it is always better to Make the yellow request to Red and Delte the Request and Go for Repeat .
Hope it helps

Processing large volume of idocs using BPM Processing

Hi,
I have a scenario in which SAP R/3 sends large volume say 30,000 DEBMAS Idocs to XI. XI then sends data to 3 legacy systems using jdbc adapter.
I created a BPM Process which waits for 4 hrs to collect all the idocs. This is what my BPM does:
1. Wait for 4 hrs Collect the idocs
2. For every idoc do a IDOC->JDBC Message transformation.
3. Append to a Big List
4. Loop at the Big list from step 4 and in the loop for
5. Start counter from 0 and increment. Append to a Small List.
6. if counter reaches 100 then send a Batch JDBC Message in send step.
7. Reset counter after every send.
8. Process remaining list i.e if there was an odd count of say 5300 idoc then the remaining 53 idocs will be sent in anther block.
After sending 5000 idocs to above BPM following problems are there:
1. I cannot read the workflow log as system does not respond.
2. In the For Each loop which loops through the big list of say 5000 idocs only first pass of 100 was processed after that the workflow item is not moving ahead. It remains in the status as "STARTED" but I do not see further processing.
Please tell me why certain Work Items are stuck is it becuase I have reached upper limit and is this the right approach? The Main BPM Process is also hanging from last 2 days.
I have concerns about using BPM for processing such high volume of idocs in production. Please advice and thanks in advance.
Regards
Ashish

Hi Ashish,
Please read SAPs Checklist for proper usage of BPMs: http://help.sap.com/saphelp_nw04/helpdata/en/43/d92e428819da2ce10000000a1550b0/content.htm
One point i'm wondering about is why do you send the IDocs out of R/3 one by one and don't use packaging there? From a performance stand point this is much better than a bpm.
The SAP Checklist states the following:
"No Replacement for Mass Interfaces
Check whether it would not be better to execute particular processing steps, for example, collecting messages, on the sender or receiver system.
If you only want to collect the messages from one business system to forward them together to a second business system, you should do so by using a mass interface and not an integration process.
If you want to split a message up into lots of individual messages, also use a mass interface instead of an integration process. A mass interface requires only a fraction of the back-end system and Integration-Server resources that an integration process would require to carry out the same task. "
Also you might want to have a look at the IDoc packaging capabilities within XI (available since SP14 i believe): http://help.sap.com/saphelp_nw04/helpdata/en/7a/00143f011f4b2ee10000000a114084/content.htm
And here is Sravyas good blog about this topic: /people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
If for whatever reason you can't or don't want to use the IDoc packets from R/3 or XI there are other points on which you can focus for optimizing your process:
In the section "Using the Integration Server Efficiently" there is an overview on which steps are costly and which steps are not so costly in their resource consumption. Mappings are one of the steps that tend to consume a lot of resources and unless it is a multi mapping that can not be executed outside a BPM there is always the option to do the mapping in the interface determination either before or after the BPM. So i would sugges if your step 2 is not a multi mapping you should try to execute it before entering the BPM and just handle the JDBC Messages in the BPM.
Wait steps are also costly steps, so reducing the time in your wait step could potentially lead to better performance. Or if possible you could omitt the wait step and just create a process that waits for 100 messages and then processes them.
Regards
Christine

No batch input data for screen SAPMSSY3 0131 in Sales order IDOC

I am processing Sales order IDOCS in status 64 using RBDAPP01 .Some of them error out to status 51 with the message -
No batch input data for screen SAPMSSY3 0131 .
I know the standard IDOC inbound process tries to simulate the posting in a BDC like process.
Now, I went to we19 and the screen hangs up in a pop up in the partners tab with partner type 'WE' and my shipto (which is actually filled in the IDOC), missing..upon repeatedly hitting enter, it goes thru and an idoc is posted in status 53. But still unable to get through the root of this issue.
Any, insight will help.

Hi,
I think the pop-up is generated through and user-exit for which recording is missing. This is why your idoc stays in status 64...
Handle the screen recording in the user exit IDOC_INPUT_ORDERS
user exit routine
PERFORM customer_function_dynpro.
FORM CUSTOMER_FUNCTION_DYNPRO.
CALL CUSTOMER-FUNCTION '002'
    EXPORTING DXVBAK   = XVBAK
              DVTCOMAG = VTCOMAG
              DLAST_DYNPRO = LAST_DYNPRO
              DXMESCOD = IDOC_CONTRL-MESCOD
    TABLES    DXBDCDATA = BDCDATA
              DXVBAP    = XVBAP
              DXVBEP    = XVBEP
              DYVBEP    = YVBEP
              DXVBADR   = XVBADR
              DYVBADR   = YVBADR
              DXVBPA    = XVBPA
              DXVBUV    = XVBUV
              DIDOC_DATA = IDOC_DATA
              DXKOMV    = XKOMV
              DXVEKP    = XVEKP
              DYVEKP    = YVEKP
    EXCEPTIONS
              USER_ERROR = 01.
Regards,
Krishnakumar

IDoc Data Lost between ECC and MII Message Listener.

We have recently experienced some network issues which caused the IDoc's to stop flowing outbound from ECC to MII Message Listener. This happened 3 times during a network switch reconfiguration. 2 of the three occasions the MII Message listener had to be restarted on the MII server in order to get data to flow again. Interestingly some of the IDocs that were generated during this outage time were processed by the message listener and some didn't.
We are running MII 12.0 sp11 and ECC 6.0. The ECC server and MII server are located in different geographic locations.
When we look at the ECC system in WE05 we see only sucessful status for the IDoc messages saying the Data passed to port OK.
When we check the Message listener on the MII end there it only shows processed successfully. There are no failed messages or messages without rules.
Where can I check further to see the IDocs that really didn't make it to be processed by the Message Listener on the MII server?
Also is it possible that these IDocs that got lost somewhere are still sitting on the ECC or MII servers somewhere where we can re-process them?
And the Last question is, Why didn't the Message Listener handle the network issue automatically instead of needing to restart it?

Hi Robert,
Did SAP ever respond/resolve the ticket you created for this issue? Someone told me that this was a known issue, but I have yet to have it verified by SAP. They asked me to simulate the issue - but our non-prod systems are on a VM server with other systems. So I can't exactly start pulling network cables out - I did drop it from the network a few time while sending IDOCs down - but this failed to hang the processing of the IDOCs.
We're hopefully going to MII 14/15 next year - but the business is keen to resolve this issue as it has impacted production a few times. The MII sites are in some remote regions and I don't think we can really improve the WAN links much further.
@Christian - thanks for the link, we don't really have an issue with IDOC's not being received, its just the message processing just hangs and we either need to restarted the services or sometimes the system.

Very urgent:To find IDOC list in RSMO(BI 7.0)

Hi all,
Its very urgent to know,for a particular load IDOCs used to run to process the data&dialogs,in 3.5 we used to get the IDOCs list in RSMO screen itself,but in 7.0 is not having that options,please tell me for a particular load where we can find list of IDOCs?
Regards,
GTR.

Hi,
This info may be helpful.
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
Also
Check Note 561880 - Requests hang because IDocs are not processed.
thanks,
JituK

Hanging request error

hi,
can anybody pls tell me what is hanging request error and how to solve this error? where this error occur exactly?

Hanging request Error!!!!!
I Suppose you are referring to the Job or Infopackage which runs for a long time??
If so then it can occur @ few instances like
- Idoc sent but not received
- Low processes
- Huge number of Job and hence the wait period.
Hope i have understood ur question correctly and it helps u.
- amit

Hanging iDoc

Similar Messages

Maybe you are looking for