cancel
Showing results for 
Search instead for 
Did you mean: 

SC Follow on Document created but PO number not generated

Former Member
0 Kudos

Hi Experts,

We upgraded our SRM system from 7.0 to 7.01 on one backup server and finding one issue with existing extended classic scenario. After successful creation of SC, after SC Approval, SC Status is showing follow on Document Created but PO number is not visible in Portal. Also, In BBP_PD, PO no. showing as 1. I checked number range, it is proper. Also, I scheduled BBP_GET_STATUS_2 and CLEAN_REQREQ_UP reports. I also checked RZ20 transaction, there is no issue there. I am unable to understand where is the issue.

Can somebody help here ?

Best Regards,

Kunal Sanghavi

Accepted Solutions (1)

Accepted Solutions (1)

ricardo_cavedini
Active Contributor
0 Kudos

Hello,

Create a shopping cart in held status.

Then, take its header GUID and transfer the cart using function module BBP_PD_SC_TRANSFER.

Before executing the transfer, put a breakpoint in BBP_PD_PO_CREATE.

Once breakpoint is reached, press F7 and see if this functon returns any error.

This could be the reason for the non follow on document creation.

Regards,

Ricardo

Former Member
0 Kudos

Hi,

I Tried this way but could not get any error after F7. I analysed transaction SM13. There I saw some error as Update was terminated with FM  BBP_PD_OBJ_REL_UPDATE_VB. Strange is I am getting this issue only when I create SC using contract as a source of supply and which attemps to create auto PO. Also, I am getting PO creation successful If Buyer uses the same contract as a source of supply for SC during carry out sourcing. Also, PO creation is successful when SC is created via MDM catalog as a source of supply.

Best Regards,

Kunal Sanghavi

former_member417448
Discoverer
0 Kudos

Hello Kunal,

Did you manage to fix your issue (I have the same on my system)?

Thank you for your answer!

Best regards,

Catherine

Former Member
0 Kudos

Hi Catherine,

Please chec if any entry exists in table BBP_DOCUMENT_TAB.If so,please run the report CLEAN_REQREQ_UP to process that entry.

If no entry in above table,please run the FM BBP_PD_SC_TRANSFER to retransfer SC and then check if the PO is created.If the error still persists,debug theis FM to check where the transfer is failing.

former_member417448
Discoverer
0 Kudos

Hi Deepti,

Thanks for your reply. I have made your checks and

- table BBP_DOCUMENT_TAB is empty,

- with function module BBP_PD_SC_TRANSFER, nothing happens.

I debugged this function module and saw the error happened during the COMMIT after call of FM BBP_PD_PO_SAVE.

In SM13, I have an error : the update return code that is in error is module BBP_PD_OBJ_REL_UPDATE_VB V1.

And to complete my first reply, I try to create a local PO, with a shopping cart referring to a local contract. If I make the same cart without any reference to the contract, the PO is well created.

Thank you in advance for your help!

Best regards,

Catherine

Answers (2)

Answers (2)

Former Member
0 Kudos

Has this PO got transferred to ECC bacjend system? And , also did you check BBP_DOCUMENTS_TAB table?

Former Member
0 Kudos

PO is not getting created in SRM itself so no question of ECC backend system PO creation. Also, there is no entry in BBP_DOCUMENT_TAB table.

Regards,

Kunal Sanghavi

Former Member
0 Kudos

guess you have maintianed the docment type properly in SRM system , and also go thru this link :

http://scn.sap.com/thread/1832232

Former Member
0 Kudos

Hi Kunal,

As you have mentioned that you have upgraded to SRM 7.01 and when you upgrade by default the Extended Classic Scenario is not active, You have to activate that. Could you please check if you have that activated. You can see it under SRPO --> SAP Supplier Relationship Managment --> SRM Server --> Cross- Application Basic Settings --> Activate Extended Classic Scenario.

Also please check if there is BADI BBP_EXTLOCALPO_BADI  activated for certain items?

Hope this helps.

Thank you

Ritesh

Former Member
0 Kudos

Extended Scenario is active only as we took copy of existing SRM 7.0 server.