Report stucked in bundled status in CVD1

[Former Member]

We upgraded from R/3 4.7 to ECC6 and MSDS in CVD1 are not sent but stucked in Bundled status. No error message in the Flow Trace of CVD1 but only the trace that ends with this 3 lines:

- CVEB_RDOS_GENERATE called

- user exit CVEO_RDO_BUNDLE_GENERATE started

- Shipment Order generation started

The WWI connections seems correctly configurated.

What can be the origin of this issue ?

Thanks in advance

Edited by: Francesco DF on Jul 16, 2010 2:39 PM

[christoph_bergemann · Accepted solution]

Hello

don't know if it helps but there is a recent OSS note available regarding a problem in bundling step: 1431630

With best regards

C.B.

[Former Member · Accepted solution]

Hi,

thanks for answering but in my case the report doesn't reach, looking at trace flow, the generated status. The trace flow stops at the messate "Shipment Report generation started" (i translated in english, it should be something of similar).

Other idea, please ?

Thanks a lot

[christoph_bergemann · Accepted solution]

Hello

only to make it clear to me: is the report which need to be delivered is still in status "released" or is there the need to generate a new one (Report request)?

The reason because I am asking is your first statement:

"the report doesn't reach, looking at trace flow, the generated status" which seems to indicate that one report is not there and which is something totally different in comparison that the report request is processed (here you have too some status). Here normally the report which needs be distributed is still there and the bundling step can be processed, If the report is not there the report request can not be processed (or it can only process one part) and bundling must stop. I am not sure if the system will really ship something if the customer will get by accident two MSDS because he is buying two materials or if the system will process only that one which is still there and create a report request for that which isn'T there. From business perspective it would make more sense to stop the processung (to avoid additional costs because of the letter), but here I have not enough experience to give a feedback how the system will react.

C.B.

PS: I have found no further OSS note related to your problem in a dump inquiry.

Can you process a manual distribution (using cg54) to an "internal or external customer" (internal = report recipient). If so this would indicate that the set up of the report distribution function itself is working.

Edited by: Christoph Bergemann on Jul 19, 2010 10:23 PM

Edited by: Christoph Bergemann on Jul 19, 2010 10:24 PM

Edited by: Christoph Bergemann on Jul 19, 2010 10:33 PM

Edited by: Christoph Bergemann on Jul 19, 2010 10:34 PM

Edited by: Christoph Bergemann on Jul 19, 2010 10:35 PM

Edited by: Christoph Bergemann on Jul 19, 2010 10:36 PM

[Former Member · Accepted solution]

Hi Cristoph,

looking the flow trace i see that the report switch from Released to Suspended ( I guess "Z" status).

Then it goes from Suspended to "In elaboration" ("IA" status). Maybe status code are not right so ignore it.

Then i read:

Main function CVEB_RDOS_BUNDLE was called

Starting user exit CVEN_RDO_BUNLE

Report was assigned to order bundle 0000000011111

Status switch from "In elaboration" to Bundled i translated in elaboration, maybe it could be "In work"

The report shipping order was set to status GB (BUndled)

Main function CVEB_RDOS_GENERATE was called

Starting user exit CVEO_RDO_BUNDLE_GENERATE

Generation of shipping order was started

Here ends the flow trace.

Looking at the old system (that we are upgrading) where all work ok, we should then have on flow trace also these lines that are missing in the upgraded system:

Generation of shipping complete

Status switch from Bundled to Generated

The report shippingorder was set to status AU (Generated)

SBE WWI-0000000232323

DOcument WWI-0000000232323 generated succesfully+

then it continues and, to make it short, the status switch to Packaged and the to "Terminated" (may be terminated is Created or Completed).

[christoph_bergemann · Accepted solution]

Hello

recently we have done as well an upgrade to ECC 6.0. We have encountered some problems in DMS. Do you have activated an "archive" to store the WWI documents?

WWI documents can be stored in the DMS or in an archive. Can you generate a WWI report ?

Is WWI up and running?

Are the other reports scheduled and running? is there an event to trigger the WWI ?

With best regards

C.B.

Edited by: Christoph Bergemann on Jul 20, 2010 9:34 PM

PS May be check this thread too:

Edited by: Christoph Bergemann on Jul 20, 2010 9:35 PM

Edited by: Christoph Bergemann on Jul 20, 2010 9:38 PM

[george_ainiveettil · Accepted solution]

Hi Fransesco,

I think after the user exit which calls the bundle status its coming out of the program,this means its not going to "complete" status..It will be either "errors found" or some other status i think.

I beleive the program for WWI is not running properly because of the settings in DMS and WWI as mentioned earlier. Please check the generation servers which uses for report running in CG5Z and make sure they are in active status.

Please check SAP notes 1058521,788573,1145017,549858 and see if helps

Regards

George

[Former Member · Accepted solution]

Thanks to all for help, finally i fiexed the problem. The documentation about report shipping that i found in a note was very helpful for understand the entire flow.

The matter was in some stucked jobs (still in planned status,and not released) created by another job with program RC1WWIDS. Maybe this program, before creating these jobs, check if they already exist so it found them and did not create other. But the existent ones were stucked.

Now the message proceed but immediately enter in error status. The line in the flow trace where i see the red circle states:

Document has been checked out by USERNAME for processing

The error states :

Message no. 26255

Diagnosis

You are trying to open a document that is locked

System Response

Another user has set the status type O for the document you want to open.

The status type O reserves one or more originals of this document for processing. This causes

the document info record to be locked from other users.

Procedure

If the status network allows it, you can set a new status. Check first to ensure that the other

user has finished processing the document.

Edited by: Francesco DF on Jul 23, 2010 3:24 PM

Edited by: Francesco DF on Jul 23, 2010 3:24 PM

[Former Member · Accepted solution]

Francesco

We are getting exactly the same error (ECC6.0)

Let me know if you found a solution

regards

Barry

[Former Member · Accepted solution]

If you are referring to may last post in this thread, then i I fixed with note 995736

[george_ainiveettil]

Hi Fransesco,

Please check the settings in WWI server and Document management system (DMS). Check if the document types you are using and see if the setting are done properly .

regards'

George