IDOC sent printouts after 3 months !

[former_member84399]

Hello all,

I have noticed a very strange situation on my BI 7.0 production system

Every day, there are some printouts coming out of the printer like below:

-

---

The following IDOCs have been sent to the application

IDOC no. Messg.Type Status StatusGRPG Status Text

1710162 RSINFO 53 # Application document posted

-

---

The IDOCs that are being printed are approximartely 3 months old. Every day, I get new printouts. For example,

yesterday I got printouts with IDOCs that were created on the 10th of March. Today, I got printouts from IDOCs

that were created on the 11th of March and so on.

All the IDOCs have RSINFO message type and Status 53.

There are no spool jobs in SP01 that I can find that have these output. I have neither found any background jobs causing this.

Any ideas ?

Many thanks

Andreas

[former_member66264 · Accepted solution]

Hi,

Can you check in if there are was a status change on the idoc?

- Can you open WE05,

- enter idoc number 1710162

- delete all other criteria.

- open the status records

- open the top status ( 53?)

- double click the status line

- post the data from the logging tab (specially user, program and subroutine if applicable)

Also post the status history from the idocs.

in meanwhile:

Do check for RBDMANI2 and RBDAPP01jobs around that time , but i can also be a manual action from we05 or WE02

FYI: Maybe the spool is gone because its deleted after printing.

Thx..

[former_member84399 · Accepted solution]

Hello Nico,

I looked at the status tab, the last time the IDOC was changed was on the 09.03.2010

</p>

</b>

In the logging tab, the only information available is the user information, ALEREMOTE.

</p>

</b>

That user is the user that interfaces those two production systems.

</p>

</b>

This iDoc was sent from our production ERP system to the production BW system on 09.03.2010

at 19:48:23.

</p>

</b>

There are 4 status records for the IDOC, all taking place at the same time. In case the below

doesn't appear in proper format, here is a summary:

</p>

</b>

Status 50 :IDoc added

</p>

</b>

Status 53 :Application document posted

</p>

</b>

Status 62 :IDoc passed to application

</p>

</b>

Status 64 :IDoc ready to be transferred to application

</p>

</b>

10.06.2010 Dynamic List Display 1

</p>

</b>

-

---

</p>

</b>

Status records for IDoc0000000001710162

</p>

</b>

-

---

</p>

</b>

Fld

Value

</p>

</b>

-

---

</p>

</b>

Status record no.

1

</p>

</b>

Status

50 :IDoc added

</p>

</b>

Logged On

20100309

</p>

</b>

|Logged At |194823 |</p>

</b>

|Database Changed On |20100309 |</p>

</b>

|Database Changed At |194823 |</p>

</b>

|Last Processed By |ALEREMOTE |</p>

</b>

|Status by Program | |</p>

</b>

|Status by Subroutine| |</p>

</b>

|Status record no. |2 |</p>

</b>

|Status |53 :Application document posted |</p>

</b>

|Status Code |SAPRSAR109 |</p>

</b>

|Message |IDoc was successfully transferred to the monitor updating|</p>

</b>

|Logged On |20100309 |</p>

</b>

|Logged At |194823 |</p>

</b>

|Database Changed On |20100309 |</p>

</b>

|Database Changed At |194823 |</p>

</b>

|Last Processed By |ALEREMOTE |</p>

</b>

|Status by Program | |</p>

</b>

|Status by Subroutine| |</p>

</b>

|Status record no. |3 |</p>

</b>

|Status |62 :IDoc passed to application |</p>

</b>

|Status Code |SAPB1042 |</p>

</b>

|Message |Direct call started |</p>

</b>

|Logged On |20100309 |</p>

</b>

|Logged At |194823 |</p>

</b>

|Database Changed On |20100309 |</p>

</b>

|Database Changed At |194823 |</p>

</b>

|Last Processed By |ALEREMOTE |</p>

</b>

|Status by Program |SAPLBD20 |</p>

</b>

|Status by Subroutine| |</p>

</b>

|Status record no. |4 |</p>

</b>

|Status |64 :IDoc ready to be transferred to application |</p>

</b>

|Status Code |SAPB1005 |</p>

</b>

|Message |& &, &, &. |</p>

</b>

| Parameter.......2 |No filters |</p>

</b>

| Parameter.......3 |No conversion |</p>

</b>

| Parameter.......4 |No version change |</p>

</b>

|Logged On |20100309 |</p>

</b>

|Logged At |194823 |</p>

</b>

|Database Changed On |20100309 |</p>

</b>

|Database Changed At |194823 |</p>

</b>

|Last Processed By |ALEREMOTE |</p>

</b>

|Status by Program |SAPLEDIR |</p>

</b>

Status by Subroutine

IDOC_STATUS_64OR65_SET

</p>

</b>

-

---

</p>

</b>

Some of the prinouts happened at the weekend, at a time that nobody would normally be logged in the system, so it has to be a

background job. Nevertheless, I have seen background jobs in BW creating kicking off dialog processes to work for them for parallelism reasons, so it might have been something like this. I say that because I do not see anything in the spool outputs of the background jobs neither

</p>

</b>

Greeting from your old colleague fron the P&G/HP years! Hope all is well!

</p>

</b>

Andreas

</p>

</b>

Edited by: support team on Jun 10, 2010 3:40 PM

[former_member66264]

Hi Andreas! ( is it Arlt or Malandrinos?)

interesting problem you have...

first of all , the sequencing seems wrong, but I assume it's a copy /past error ( normally its 50 64 62 53 from the bottem up) , let me know if its not.

Based on the feedback received (that i don't see here BTW ), we can almost be sure that the idoc itself did not get touched after the initial posting date, now I can only imagine that there must be a WF active ( that ends after x-months) , or its a 'very" delayed spool....

let's check option 1:

can you check in the idoc if there are WF attached?

again we 05, idoc number , select, in the idoc display there is button on top ( know as Service for object) workflow , workflow overview.

if there is a wf attached, check the content of the flow

this document can help in removing it ( or checking it) http://help.sap.com/printdocu/core/print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf

more background is here: http://help.sap.com/saphelp_nw70ehp2/helpdata/en/72/c18ee5546a11d182cc0000e829fbfe/frameset.htm

option 2:

can you post an idoc via RBDAPP01 ( copy the same idoc via wE19 for example, standard inbound, note the number created, se38 RBDAPP01, enter the number , execute in background print on the specific printer, and check if the report has the same layout ( i tested on a 6.40 and the output is a bit different)

-

---

The following IDocs have been passed to the application:

IDoc Message Type Serialinfo St Description

0000000032899016 ZSEDI_UTILTS 53 Application document posted

-

---

but if it it's the same, we can assume the spool comes from the posting via RBDAPP01

during printing , there is an option to delay the printing... ( it creates an output request in the future,)

( should not be your case since you don't see a spool in first place) but still worth to check all RBAPP01 jobs ( also the scheduled/released ones)

___________

further checks:

in SM50/51 select the SPO process, process traces , display, and check at the time of the print if there are spools for that printer:

S Thu Jun 10 18:24:27 2010

S 1 pages (List) printed in 1 seconds, avg. 1.0 pages

S Timeinfo 212660/1 (IA02): 1 1 List ( 0 0 0 0 0 0 )

spool nr -- / \---- printer

this to check that the delay is not further down the line ( unix, wintel , printer, etc...)

let me know how it goes...

Nico

[former_member84399]

Hello Nico ( it is Malandrinos in fact!)

Thank you for your help so far, I have managed to make some progress.

I haven't copied and pasted in the wrong order, I checked the output again and it is as a pasted it. Not sure if this is an issue or not.

We do not have workflows associated with the IDOCs , so we can rule this out

However, you are right about the report that created this output, it is RBDAPP01. I checked all spool requests of user ALEREMOTE and I found some of them that are not printed yet, whose output looks identical to what I get in the printer every day. These spools names is as follows

LIST1S HH01 RBDAPP01_ALE

HH01 is the name of the printer and RBDAPP01_ALE is the <ABAP>_<three first characters of the user> that created it.

I have now enough information to go back to the BI team and have a look at their jobs. In sm37, I do not see any job with RBDAPP01 but I am sure that the BI jobs that run daily and load data from ERP create the IDOC postings (most of them come from the ERP production system)

ALEREMOTE's default printer is HH01, I might have to set it to LP01 to avoid wasting pages every day until I find the guilty job!

I tried to find info in the spool process trace, I even increased the trace level but got nowhere with it.

Thanks a lot for your help

Andreas

[former_member66264]

Hi Andreas M,

Nice to see you back in these forums !

It's strange the status is displayed in the wrong order... is this for all you idocs like that?

maybe check for those spools if there planned output request.

Jut FYI: you can also deactivate the flag "output immediatly" , then you can also find back when the spool is created and find the associated program ...

CY around!

Nico B.