My Oracle Support Banner

In-transit Receipt Is Costed At Unexpected Price For Backdated Transaction (Doc ID 2386656.1)

Last updated on DECEMBER 03, 2019

Applies to:

Oracle Cost Management - Version 12.1.2 and later
Information in this document applies to any platform.


The profile option "CST Transfer Pricing Option" is set to "Yes, Price as incoming cost" and FOB point = Receipt, in-transit receipt transaction is costed based on sending org price list. When sales order issue is executed with back date, internal receipt in-transit transaction is costed at a CURRENT price, not at a price of TRANSACTION DATE. Is it an expected behavior?


  1. Price list is defined as below with effective date.
    Old price = 1, End Date = May 21, 2018
    New price = 2, Start Date = May 22, 2018
  2. On May 22, internal sales order Issue is executed with transaction_date = May 21 (Backdated transaction)
  3. Int Req Intr Rcpt is costed at New price = 2, even though transaction date is May 21.


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.