How to restrict user to create Purchase Order (PO) without Purchase Requisition (PR) in Oracle / Auto Create PO in Oracle EBS R12

Restrict Creation of #PO without a #PR

Sometimes Businesses do not allow a #PO to be created manually. There are several ways through which we can restrict the creation of #PO without a requisition in #Oracle #EBS #R12. The blog discusses two different methods to achieve this goal.

Introduction: 

At times, businesses necessitate a requisition as a prerequisite for generating a #Purchase_Order (#PO). This blog will enlighten you on the procedure to prevent users from creating a #PO without a corresponding requisition. In #Oracle Purchasing, there are two methods for #PO creation:

• Manual creation via the #Purchase #Order form.

• Automatic creation from a requisition through the Autocreate function.

There are instances where manual creation of a PO is not permissible. In #Oracle #EBS, there are two distinct approaches to enforce the restriction on creating a #PO without a linked requisition:

Option 1

Employing form personalization on the #Oracle Purchasing form, specifically the POXPOEPO form. This method entails two personalization steps, one for the #PO Header Block and another for the PO Line Block. The initial personalization is executed on the PO Header Block, where you can utilize the 'When Validate Record' event. Within this personalization, you establish a condition to verify whether the PO number (segment1) is null. If it is null, an error message is triggered. A null Segment1 indicates an attempt to create a new PO via the Purchase Order form, and this action is restricted.

The next personalization is at the PO Line level. Here you can trap it at the “When New Block Instance”.

If the condition is the same i.e. if Segment1 at PO header’s level is null then take the following two actions:

1. Pass the control to PO Header block

2. Raise the error message

Option 2

To implement menu exclusions effectively, you must exclude multiple functions at the responsibility level, thereby preventing users from manually creating a PO. It's crucial to apply this exclusion to all relevant responsibilities where this restriction is desired. The two specific functions that require exclusion are:

• Purchase Orders
• PO Summary: Create New PO

Note: 

The second approach comes with a specific limitation. This limitation entails that a user is unable to edit POs that were created through the auto-create feature when using responsibilities from which the "Purchase Orders" and "PO Summary: Create New PO" functions have been excluded.

Conclusion:

You have several options available to attain your objective, as described above. If your requirement involves enabling users to edit purchase orders after they've been created from a requisition, the recommended approach is the first method of utilizing form personalization. On the other hand, if users only need to create purchase orders from Autocreate without the need for subsequent editing, then the second approach is the most suitable. I trust that you will find these suggestions helpful and be able to apply them effectively. Should you have any questions or uncertainties, please don't hesitate to contact me by clicking the button below. Additionally, you're welcome to share your comments and feedback in the designated field below.

#PurchaseOrder #EBS #Oracle #PO #PR #Autocreate #ERP #R12 #Autocreate #Requisitions #Restriction #Personalizations