E1: 43: Purchase Order Commitment Period is Determined Based on the General Ledger (G/L) Date (Doc ID 2806199.1)

Last updated on SEPTEMBER 16, 2021

Applies to:

Goal

What is considered to be the Date when the  Commitment is recorded (TRDJ(Order Date) or approval date or other option) ?

In the case of 2 options the user needs to identify the Commitment start date using approval process:

1. Create a Blanket Order (OB) (i.e., PDDJ(Promised Delivery Date)=01/01/2022 and DRQJ(Requested Date)=31/12/2022). Can be done using P4310_ZJDE0007 or creating a new version copying the standard one.
   1. Generate monthly POs (i.e., PO Jan PDDJ(Promised Delivery Date)=01/01/2022 and DRQJ(Requested Date)=31/01/2022; PO Feb PDDJ(Promised Delivery Date)=01/02/2022 and DRQJ(Requested Date)=28/02/2022, etc.).
   2. Receive the monthly PO (P4312) based on the proof of services.
2. Create an OP (i.e., PDDJ(Promised Delivery Date)=01/01/2022 and DRQJ(Requested Date)=31/12/2022). Can be done using P4310_ZJDE0005 or creating a new version copying the standard one.
   1. This could mimic the Blanket Order (OB) in terms of period covered.
   2. Receive the monthly PO (P4312) based on the proof of services.

This can be done the last working day of the month, manually.

In both cases budget control is also active in P4310.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.