Skip to end of metadata
Go to start of metadata

Purpose

This is to explain the PO response creation and the related  trouble shooting suggestion

Overview

You are creating a PO response, and some issue occurs. With this wiki page you can understand how the PO response can be created and where to set break point for debugging.

PO Response can be created in following ways from PO POWL using “Purchase Order Response” dropdown menu by Purchaser User or Secretary User.

  • You can create a purchase order response manually
  • You can completely accept the purchase order
  • You can completely reject the purchase order

In all the three scenarios when PO Response is created by a secretary user, the header leave document status remains as ‘In Process’, as the changes done by secretary user are not copied to PO. This PO Response created by Secretary User goes to the respective purchaser for approval. Here on Approving or declining the PO Response by Purchaser user changes get copied to PO and the old POR achieves status of ‘Out of Date’ and a new POR with status copied to POis created.

Creating a POR Manually

 For a purchase order that has already been transmitted to the supplier, the Purchase Order Response dropdown menu is activated when you select the purchase order in your POWL. To create a POR, select Create Manually from the Purchase Order Response dropdown menu.

You can edit the following fields:

  • Quantity
  • Price
  • Delivery Date/ Delivery Schedule
  • and, in the case of service items: Service Provider

User can also enter the changes to delivery date and quantity under   Items Details Delivery .

Under Delivery in the item details, you can set a schedule line when entering purchase order responses. This way a supplier can distribute quantities over multiple delivery dates, or services over multiple performance periods.

Here the user can set different item level status for different items (Open, Accepted, Rejected).

Prerequisite:

  • Purchase Order output should be generated.
  • The user should have purchaser role. Or purchase order response can be created by purchase assistant. Further this would be approved by the  purchaser and changes would be copied to purchase Order.

Business Scenario:

Customer does not have a system for vendor to enter the purchase order response. The response details would be sent to the purchaser via fax, email, letter or telephone.

From SUS

Flow:

  • Find the PO in SUS.
  • After clicking on the Process button under Display Purchase Order, the SUS user has the option to either Confirm or Reject an item under the Item Overview.
  • Once the SUS user is done with the required changes press the Send  button and the document comes back to SRM.
  • The document comes back to the Purchaser’s inbox with a subject such   as ‘Check PCO No. XXX for PO No. XXXX
  • When the purchaser clicks on this work item, the Purchase Order Response screen comes up with Approve and Decline buttons enabled.
  • Clicking on the Approve button signifies that the Purchaser agrees to the SUS User’s changes completely.
  • Clicking on the Decline button signifies that the Purchaser disagrees completely with the SUS User’s changes.

.

Prerequisite:

  • SRM system should be integrated with SUS system.
  • Purchase Order should be available in SUS system.
  • Approval process should be configured to accept the purchase order response if there is any changes in purchase order response when compared with purchase order.

Business Scenario:

Customer has SRM system integrated with SUS system. He has given privilege to vendor to create acknowledgement or Purchase order response in SUS system.

Debugging tips

 
FM : BBP_PD_PCO_CREATE

Class Interface      /SAPSRM/CL_PDO_BO_POR

CREATE_NEW_INSTANCE

CREATE_PCO_DB

CREATE_POR_HEADER

CREATE_POR_ITEM

PO_POR_DIFF

UPDATE_PO_FROM_POR

BADIs

BBP_DOC_CHANGE_BADI
BBP_DOC_SAVE_BADI
BBP_DOC_CHECK_BADI