Blanket Purchase Order (BPO): The Summary Sheet for Some Company Level Commit Records Do Not Match the BPO Summary Template Structure
(Doc ID 3007162.1)
Last updated on MARCH 06, 2024
Applies to:
Primavera Unifier Cloud Service - Version N/A and laterPrimavera Unifier - Version 9.7 and later
Information in this document applies to any platform.
Symptoms
For the Blanket Purchase Order (BPO), which is a Cost Commit at the company level, Summary Sheet:
Expected Result
All of the Summary Sheets, for all of the records, should match the BPO Summary Template structure.
Actual Result
Only some Summary Sheets match the BPO Summary Template structure.
Steps To Reproduce
-
Navigate to Company Workspace in Admin mode > Business Process Setup > NameOfBPO*, select NameOfBPO in the log and Open the BPO Template.
-
Notice the structure
-
example: Blanket PO, Change PO, Remaining Balance
-
-
- In User mode, navigate to and open the Business Process (BP) Log that contains the BPO records.
- Open a record, click on the More Actions button, select Summary Sheet.
- Notice that the Blanket PO Sheet does not match the BPO Template
- example: BPO (Approved), CO (Approved), CO (Pending), Remaining Balance
- Notice that the Blanket PO Sheet does not match the BPO Template
- Open another record, or Create a New record and Send/Submit it through the Terminal Status.
- Click on the More Actions button, select Summary Sheet.
-
Notice that the Blanket PO Sheet matches the BPO Template
-
example: Blanket PO, Change PO, Remaining Balance
-
-
*Where this would be the name of the Cost Commit at the company level in uDesigner.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Cause |
Solution |
References |