Oracle Purchasing: Restrict Creation of PO without A Requisition

Start Here

Get in touch with a
TriCore Solutions specialist

Blog | Jan 24, 2017

Oracle Purchasing: Restrict Creation of PO without A Requisition


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. The blog discusses two different methods to achieve this goal.

Introduction:
Sometimes businesses require a requistion in order to raise a Purachase Order (PO). In this blog you will learn how to restrict a user from creating PO without a requisition. In Oracle Purchasing we can create the PO in two ways:

1) Manual PO through Purchase order form

2) Automatically from requisition through Autocreate form

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. Below are the two methods to for how to achieve this goal .

1) Through form personalization on Oracle Purchasing form POXPOEPO

This requires two personalization, one on the PO Header Block and another on the PO Line block. First, the personalization needs to be done on the PO header block. Here you can use the event "When Validate Record". You need to add a condition to check if the PO number (segment1) is null, if yes, then you can raise an error message. Segment1 null means that you are trying to create a new PO on Purchase order form so we restrict it here.

create new purchase order

oracle ebs support

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

    how to create purchase order

    oracle purchasing support

    2) Through menu exclusions

    To utilize menu exclusions, you will have to exclude several functions at the responsibility level to ensure that a user is not able to create the PO manually. Keep in mind to add it on all responsibilities where we want to restrict this functionality. Two functions which need to be excluded are:

  3. Purchase Orders
  4. PO Summary: Create New PO

    po summary

    There is one limitation in the second approach. There is one limitation in the second approach. The limitation is that a user is not able to edit the POs (which were created through the auto-create functionality) from responsibilities on  which functions "Purchase Orders" and " PO Summary: Create New PO" are excluded.

    Conclusion:
    You can use any of the approaches outlined above to achieve your goal . If you need that a user should be able to edit the PO after creating it from a requisition then you should follow the first approach of form personalization. In the case, that a user can just create it from Autocreate and does not require to edit it, then the second approach is the way to go. I hope you find these hints valuable and are able to put them to good use.  If you have any doubts feel free to reach out to me by clicking on the button below. You can also leave your comments and feedback in the field below.
    Ask Amit