3

Purchase Requisition Completion in Central Procurement

 3 years ago
source link: https://blogs.sap.com/2021/01/17/purchase-requisition-completion-in-central-procurement/
Go to the source link to view the article. You can view the picture content, updated content and better typesetting reading experience. If the link is broken, please click the button below to view the snapshot at that time.
Product Information
Posted on January 17, 2021 3 minute read

Purchase Requisition Completion in Central Procurement

2 Likes 42 Views 0 Comments

Introduction

Purchase requisition completion in Central procurement is the way for approval manager of purchase requisition to update the purchase requisition as per his requirement directly instead of rejecting the purchase requisition or asking the creator of the purchase requisition to modify the same.

In case of only requisition scenario (1XI) of central procurement is configured in the landscape, central purchase requisition which is created in the Hub system by employee is replicated to connected system only after approval if workflow is configured in the Hub system. Employees are not allowed to edit the purchase requisition when purchase requisition is in approval in Hub system. After replication editing is allowed for the replicated purchase requisition in the connected system. The changed details are updated back to the purchase requisition in the Hub system.

image-3.png

In case of only purchasing scenario (2XT) of central procurement is configured in the landscape, purchase requisitions created which are created in the connected system are extracted to Hub system and workflow will be triggered in the Hub system if approval is configured. If approving manager wants any change in purchase requisition then navigation is possible to connected system purchase requisition, so that changes can be made directly to connected system purchase requisition by approving manager.

image-4.png

In case of both requisitioning and purchasing (1XI and 2XT) of central procurement is configured in landscape, recommendation is to configure the workflow for proxy purchase requisition. Purchase requisitions in connected system which are created in case of requisition scenario or standalone scenario are extracted to Hub system are extracted to Hub system and subjected to approval if approval is configured in the Hub system. If manager wants any changes to purchase requisition can perform the below steps.

image-5.png

Detailed Steps of Purchase requisition completion in case of Both 1XI and 2XT:

Step 1: Navigation link is provided in the detail page of the workflow app.

image-6.png

Step 2: After clicking the link, navigation happens to object page of manage purchase requisitions centrally app which will show the details of purchase requisition item.

image-7.png

Step 3: “Open Document” button is provided in the object page to open the purchase requisition in the connected system directly.

image-8.png

Step 4: Manager will change the purchase requisition directly in the connected system and saves the document. After that, to have updated values of purchase requisition in the Hub system, “Refresh” button in the object page of manage purchase requisitions centrally app can be clicked, or extraction of this purchase requisition can be scheduled.

image-9.png

After doing above steps, workflow will be restarted with updated values of purchase requisition.

Conclusion

By giving this provision of updating the purchase requisition directly to approval manager in the central procurement scenario helps in efficiency of the process.

Kindly share your feedback, thoughts or any queries regarding this post, in the comments section below. In case of any further queries, feel free to write back to ask or ask a question in the forum!

Central Procurement Community Page – Ask a question

For more information on SAP S/4HANA for Central Procurement, check out the below links:

SAP Help Portal Product page

Central Procurement Community Page


About Joyk


Aggregate valuable and interesting links.
Joyk means Joy of geeK