My Oracle Support Banner

Autocreate Purchase Order Using Createpo Workflow Has Rate_date Null for Functional Currency (Doc ID 2031458.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Purchasing - Version 12.1.3 and later
Information in this document applies to any platform.


When a requisition is autocreated to a purchase order using the CREATEPO workflow, the rate_date in the Purchase Order header and distribution is null when the purchase order currency is the same as the functional currency. If it's autocreated from the Auto create window or directly created from the Enter PO form, the rate_date is populated with the system date.

Expect the rate_date in the purchase order to be populated with the system date (creation date) irrespective of how the Purchase order is created.

The issue can be reproduced at will with the following steps:
1. Setup ASL and sourcing rules for using CREATEPO workflow
2. Create a requisition in iProcurement or from the Enter Requisition form
3. Purchase Order is created with rate_date as null

The issue has the following business impact:
Due to this issue,
- the POs which have the rate_date populated as the system uses the PO rate during create accounting process
- and the ones which has rate date as null uses the receipt date for secondary ledger conversion

This makes the secondary ledger conversion inconsistent. Customers wants the system to default PO creation date as rate date, so that the system is consistent with the conversion in secondary ledger.


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

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