Last updated on AUGUST 01, 2016
Applies to:Oracle Advanced Pricing - Version 12.0.0 and later
Oracle Inventory Management - Version 12.0.0 and later
Information in this document applies to any platform.
INCIAR - Intercompany Invoicing
WSHINTERFACE module: Interface Trip Stop
On : 12.1.3 version, Pricing Engine
Finds that when using a custom product attribute on a modifier, it does not apply on intercompany transfer price
The custom product attribute is setup under product context = Inventory Level
with attribute mapping for Request type: IC: Inter Company Invoicing and application name: Inventory
as user source type: PL/SQL
and user value string: XXST_COMMON.GET_INV_LEVEL(INV_IC_ORDER_PUB.G_LINE.INVENTORY_ITEM_ID,INV_IC_ORDER_PUB.G_LINE.FROM_ORGANIZATION_ID)
Expects this modifier to apply on the intercompany transfer price
The issue can be reproduced at will with the following steps:
1.) Create internal requisition
2.) Run create internal orders
3.) Run order import
4.) Pick release internal order
5.) Ship confirm internal order
6.) Run Interface Trip Stop to calculate intercompany transfer price
Modifier Additional Notes
1) uses a custom product attribute defined for intercompany invoicing.
the inventory item and "from_organization_id are passed in as parameters
the custom function returns the type of product (either RAW or FG or Sub Assy)
Assigned to Inventory_Items Pricing_attribute40
2) Modifier is setup with this product attribute and qualified by the Shipping OU and Selling OU
3) Price List uses formula (GET_CUSTOM_PRICE = formula name)
step 1 function GET CUSTOM PRICE
step 2 numeric constant = 0
step 3 numeric constant = 1
4) Modifier that does not have the custom product attribute and do work fine:
5) Modifiers that do have the custom product attribute and do NOT work fine:
6) Modifiers only have line qualifiers
Even though the Modifier details report tends to indicate multiple qualifiers for selling OU / Shipping OU in grouping number = -1
this is not the case shown live. Only one in grouping nbr -1 (Shipping OU) and one in grouping number = 1 (Selling OU).
The issue has the following business impact:
Client is not able to distinguish between finished and raw materials when applying the intercompany price mark-up.
They price based on how the product is transferred as it can be a markup (surcharge) or a discount.
The determining factor is the value for the Shipping Operating Unit (OU) and the value for the OU sold to (Selling Operating Unit).
Now they wish to add one more condition to how products are priced.
They wish to markup differently based on whether the item is a finished good (FG), raw material (RAW) or a sub assembly (Sub Assy).
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms