My Oracle Support Banner

POR: PO: Unable To Create Draft Purchase Order Via REST API With PO Variance Account And/Or PO Accrual Account Attributes Populated (Doc ID 2780068.1)

Last updated on MAY 27, 2021

Applies to:

Oracle Fusion Purchasing Cloud Service - Version 11.13.21.01.0 and later
Oracle Fusion Purchasing - Version 11.12.1.0.0 and later
Information in this document applies to any platform.

Symptoms

Draft Purchase Order REST API

ACTUAL BEHAVIOR
 
Draft Purchase Order REST API
Valid
Charge Account
Accrual Account
Variance Account
combinations are passed in REST Payload

purchase order/line is created successfully, however only
Charge Account
is populated in the purchase order

Accrual Account
Variance Account
values are null

The response does not show errors with these attributes, it only ignores them.

If you open the document generated,  and attempt to Validate the document, Validate returns an error

You must provide a value for the PO Accrual Account attribute

You must provide a value for the PO Variance Account attribute

If you attempt to calculate these values automatically via Rebuild
Purchase Order > Edit Distribution > Rebuild
Rebuild does not work for these purchase orders distributions, no errors are retrieved, fields remain blank.

EXPECTED BEHAVIOR
 
Draft Purchase Order REST API to create lines with
Charge Account
Accrual Account
Variance Account
populated.

STEPS
 
The issue can be reproduced at will with the following steps:
 
1. Make sure that the combination of
Charge Account
Accrual Account
Variance Account
are valid by creating a new document manually via Create Order UI/validating the document. Make sure that Validation does not return errors. 

2. Create a Draft Purchase Order REST API body with
Charge Account
Accrual Account
Variance Account
populated with the exact same values entered in Create Order UI test.
 
3. Purchase order/line is created successfully , however only
Charge Account
is populated in the purchase order.
 
Accrual Account
Variance Account
values are null

4. Review the response payload. It does not show errors with these attributes, but their values show null.

5. Unable to further process these purchase orders/lines.
If you open the document generated
Edit Distribution
Rebuild
Rebuild does not work for these purchase orders distributions, no errors, fields remain blank.

 

Changes

 

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
Changes
Cause
Solution
References


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