Workflow not getting released on SRM PO

[mithun_kukke]

We have a scenario where the user created a shopping cart and it was approved and further created a PO automatically. We do not have any approvals for the PO and therefore it needs to get completed.

For some reason when the user made changes on the PO and saved it the system did not transmit the PO to the backend. The status in BBP_PD is

Stats:

Status Description Inactiv

HEADER I1015 Awaiting Approval X

HEADER I1021 Created

HEADER I1038 Complete

HEADER I1043 Ordered

HEADER I1080 In Transfer to Execution Syst. X

HEADER I1120 Change was Transmitted

HEADER I1132 Transfer Failed (E.Sys.)

HEADER I1180 Document Completed

0000000001 I1021 Created

0000000002 I1021 Created

0000000003 I1021 Created

Also when the user tries to change the document it throws an error.

Document still in process in the backend. Try again later.

Also we investigated and determined that the workflow was not getting released on the latest version of the document.

Versions:

GUID Type No. Closed

DD73B5EAEF856CF1863600145ECE6F3D

48C994696D1A0DEDE10080000AD0C835 C C1 X

48F7A79D68710CB6E10080000AD0C835 C C2 X

48F8E299C8A602A6E10080000AD0C835 C C3

We tried completing the workflow manually and this allows the user to make changes bu again gets stuck in this workflow and does not post the document in the backend.

We tried running FM BBP_PDCV_UPDATE_ACTIVE_WFL but nothing worked to our satisfaction.

Can anybody throw light onto what we might be doing wrong or what would be ideal steps to take.

[laurent_touillaud]

Hi Mithun,

Try this :

Delete the corresponding line(s) in table BBP_DOCUMENT_TAB.

Then try to transfer the PO again.

Best regards,

Laurent.

Remind points if helpfull.

[mithun_kukke]

We checked entries in BBP_DOCUMENT_TAB also but there are no entries in that table relating to this transaction

[laurent_touillaud]

Ok,

message is "Document still in process in the backend. Try again later." so try to see if document is not locked in the backend using SM21 or by checking ME23n.

Best regards,

Laurent.

[mithun_kukke]

The document has not been created in ECC yet since it already has the status I1132.