Oracle Value Chain Planning

Oracle Value Chain Planning (earlier called Oracle Advance Planning and Scheduling) is an integrated set of mules which enables companies to efficiently design, plan and service their value chains from 'factory to shelf'.

Interfaces

Inventory

• Item Import
  
  
  
  
  

Legacy System --> Mtl_System_Items_Interface --> Item Import Program --> Mtl_System_Items_B (or Mtl_Interface_Errors)

• Material Transactions

Interface Tables to be used are:
MTL_TRANSACTIONS_INTERFACE
MTL_TRANSACTION_LOTS_INTERFACE
MTL_SERIAL_NUMBERS_INTERFACE

Transaction Type ID should be 2 (for "Subinventory Transfers") and "Material Transactions Manager" will process the records from the Interface tables.

If there are any errors while processing, the details of the errors will be available in MTL_INTERFACE_ERRORS table.

Cost Management

• Item Cost Import

Sample insert statement to populate the Item Cost Interface table

INSERT INTO CST_ITEM_CST_DTLS_INTERFACE
(INVENTORY_ITEM_ID
,ORGANIZATION_ID
,COST_TYPE_ID
,LAST_UPDATE_DATE
,LAST_UPDATED_BY
,CREATION_DATE
,CREATED_BY
,LAST_UPDATE_LOGIN
,Process_Flag
,Item_Cost
,Cost_Element_ID
,USAGE_RATE_OR_AMOUNT
)
SELECT INVENTORY_ITEM_ID
,ORGANIZATION_ID
,COST_TYPE_ID
,SYSDATE
,1441
,SYSDATE
,1441
,14411441
,1
,5
,1
,5
from cst_item_costs where inventory_item_id = 13433714 --12456335
AND Cost_Type_ID = 3

Payables

• Invoice Import

Interface Tables
AP_INVOICE _INTERFACE is the header info
AP_INVOICES_LINES_INTERFACE is the lines table.

RUN PAYABLES INVOICE IMPORT CONCURRENT PROGRAM

Base Tables
AP_INVOICE_ALL is also the header information is stored.
AP_INVOICES_DISTRIBUTIONS_ALL is the lines information table.
AP_PAYMENTS_SCHEDULES_ALL (AMOUNT_REMAINING stores balance amount to be paid)
AP_INVOICE_PAYMENTS_ALL (INVOICE_ID)
AP_CHECKS_ALL (CHECK_ID)

AP_INTERFACE_REJECTIONS (REJECT_LOOKUP_CODE stores the error occurred during the invoice import ex: account required, invalid supplier site )

Oracle Inventory

Move orders

are formal requests to move material within (one subinventory to another) the same inventory organization.

There are three types:

Requisition Move Orders - Manually crearted. User may choose to print a pick slip for the material handler to know where to get the material from.

Source Types --> subinventory transfer and account transfer

Replenishment Move Orders - pre-approved move orders that are created automatically from Min-Max Planning, Replenishment Counting, Kanban replenishment.

Source Type --> Subinventory

Pickwave Move Orders -  used in Order Management. The Oracle Shipping Execution pick release process generates a Pick Wave Move Order to move the material from its source location to the Staging subinventory.

Backend Story:

SELECT header_id, h.* FROM apps.MTL_TXN_REQUEST_HEADERS h

WHERE Request_Number IN ('16788419', '16874441');

SELECT line_status, l.* FROM apps.MTL_TXN_REQUEST_LINES l
WHERE header_id IN (16788751, 16870925); -- 5 is Closed
Select *from apps.mfg_lookups
where lookup_type LIKE 'MTL_TXN_REQUEST%'; --_STATUS';
SELECT * FROM apps.MTL_TXN_SOURCE_TYPES;