Delete PO line item

[Former Member]

Hi All,

I have a requirement to delete PO line items after PO has been ordered but not confirmed or invoiced. PO to Vendor is manual process. We are in SRM5.0 ECS on SP15. I am not sure how to delete a PO line item after it has been ordered. Line item shows Delete indicator when I delete the PO line item but does not get reflected in backend. Please advise. Greatly appreciated.

Regards

Rao

[Former Member · Accepted solution]

Hi Rao,

Looking at the issue you are facing, i see that the PO is not replicating changes done during deletion of line item. So, it is not taking Extended Classic PO properties when item is deleted. Please check if this is the cause:

1. Global control:

Path: SPRO>SAP Implementation Guide>SAP Supplier Relationship Management>SRM Server>Cross-Application Basic Settings>Activate Extended Classic Scenario>

2. Badi:

Path:SPRO>SAP Implementation Guide>SAP Supplier Relationship Management>SRM Server>Business Add-Ins (BAdIs)>Control Extended Classic Scenario> Activate Extended Classic Scenario Method: DETERMINE_EXTPO_CREATE

In this case, the global control makes the manual creation of PO as local. In order to make the PO to behave as extended classic for a certain transaction type, we need to set the value of bbp_extpo_gl-bbpexpo to X.

In case of manual creation of PO, product category does not decide the behavior (local/extended) but the transaction type.

Please modify the method IF_EX_BBP_EXTLOCALPO_BADI~DETERMINE_EXTPO_CREATE for the transaction type ECPP to behave as extended classic

See if this helps.

Best Regards,

Anu

[Former Member · Accepted solution]

Thank you all for your suggestions. The issue I had was with this specific PO which was created from SC and then changed in PO processing(added line items). Since this PO has already encumbered, client was trying to change / delete line item which there was the issue of not flagging for deletion. I was able to change other POs and delete line items aswell which reflected in ECC.

So this was a specific issue. I still have the issue open and investigating other options to liquidate the funds which got encumbered from this PO.

By deleting PO records in FM does not really solve the issue of liquidating the funds as it ties to GM too. Other option is to control AVC check to PO a new PO to this GM/FM structure and process the PO. This AVC control will be set for just this structure only temporarily just to process a new PO.

I will post my updates when I accomplish it.

BTW all BADI and config settings were correct and properly set. Like I said this was special case.

Regards

Rao

[summer_wang1 · Accepted solution]

Hello ,

Actully I agree with lauren that BAPI_PO_CHANGE should be check , if there is any error issued in MM, FI CO PSM ,If you are using such functions in backend system.

About how to create test data in BAPI_PO_CHANGE ,please check the following ducment :

/people/summer.wang/blog/2010/05/11/trouble-shooting-of-srm-po-transfer-error

If you get the error in Return table in BAPI_PO_CHANGE , things is much easier

Good luck

Summer

[Former Member]

Thankyou all, a OSS Note was applied and the system works well. The issue was that attachments for the PO lines items were not recognized. After applying note 1427276 (although the description of it is irrelevant) the system was able to recognize the attachments and was able to delete the PO line items.

[Former Member]

Check whether change version has active status in tr:BBP_PD, if yes, check whether WF has errors for this version.

You need clear the error if have.

Best Regards

Lauren

[Former Member]

Thanks Lauren,

I checked and there are no errors in WF or BBP_PD. I looking to delete PO line item. when I delete a PO line item, it does put a delete indicator but nothing happens (when PO is in 'ordered' status). When PO is in 'Held' status, then it reflects in backend. So how do I delete the PO line item.

Thanks

Rao

[Former Member]

Hi, Rao

If workflow has been completed, so changes has been approved from SRM side, deletion flag of item level should replicate to backend. In order to clarify it's problem of backend system or SRM , you can test the BAPI_PO_CHANGE in your backend system. Fill the input data of the BAPI_PO_CHANGE in your backend system with the function

FBGENDAT.

To do this, please see note with the number 539978.

Here it's the summary of it, please:

- Set the Parameter FBGENDAT 'X' in the backend system for the

RFC user of the SRM system

- Execute the report FBGENDAT in the mode 'A' or 'B'.

- Delete PO item from the SRM system and order the PO, check whether

a test data record was generated in the Function Builder

BAPI_PO_CHANGE(tr:SE37).

- Deactivate the generation of test data records by deleting the

entries in report FBGENDAT and resetting the user parameter.

Now in backend, check test data which captured. Field: POITEM-DELETE_IND has X or not ? If has value, means, SRM

passed deletion flag correctly to backend, so this will be a backend problem.

Hope these information is helpful for you.

Regards

Lauren