New REST APIs to Perform Transactions on Manufacturing Work Orders
In order to provide customers using Manufacturing and WMS the ability to directly issue components to work orders, we are introducing a new Manufacturing Transaction API which allows Manufacturing, Inventory Management or any other application to record Material Issues or Product Completions and transaction reversals. This provides a common API which supports both material issues and product completions.
This feature delivers services, core application enhancements, and pre-delivered OIC-based integration mappings to integrate direct work order transactions generated in Oracle Fusion Cloud Manufacturing or Oracle Fusion Cloud Maintenance to Oracle Fusion Cloud Warehouse Management.
MANUFACTURING TRANSACTION API
The new Manufacturing Transaction API allows you to integrate direct work order transactions between Oracle Fusion Cloud Manufacturing, Oracle Fusion Cloud Maintenance, Oracle Fusion Cloud Inventory Management, and Oracle Fusion Cloud Warehouse Management.
URL
POST.../wms/lgfapi/v10/inventory/manufacturing_transaction
The following data is passed in JSON format:
| Column | Mandatory | Comments |
|---|---|---|
| mfg_work_order_transaction_list | ||
| transaction_id | yes |
Unique Identifier for the transaction shared by fusion inventory. |
| location | yes |
location pass can correspond to active or reserve location or drop location type. |
| lpn_nbr |
will be required for product completions and product returns. |
|
| transaction_type |
The following are the transaction types shared from Inventory Management:
|
|
| mfg_work_order_nbr | yes | work order number against which transaction is recorded. |
| mfg_operation_seq_nbr | work order operation sequence against which transaction is recorded. | |
| external_transaction_date_time | Holds the transaction date and time when it was performed at the source system. | |
| resend_flg | by default the value will be No. If set to yes, Inventory Management has an ability to resend the transaction in case of any failures. | |
| inventory_list | ||
| item_alternate_code | Application expects either item alternate code or combination of item_parts. | |
| item_part_a | ||
| item_part_b | ||
| item_part_c | ||
| item_part_d | ||
| item_part_e | ||
| item_part_f | ||
| qty | yes | corresponds to the quantity. Can be either + or - depending on the transaction type. |
| uom_code | uom_code in which the transaction quantity is recorded in. For Prebuilt integration | |
| batch_nbr | lot number for lot tracking item. | |
| expiry date | expiry date in case sku is only expiry tracked. | |
| invn_attr_a | ||
| invn_attr_b | ||
| invn_attr_c | ||
| invn_attr_d | ||
| invn_attr_e | ||
| invn_attr_f | ||
| invn_attr_g | ||
| invn_attr_h | ||
| invn_attr_i | ||
| invn_attr_j | ||
| invn_attr_k | ||
| invn_attr_l | ||
| invn_attr_m | ||
| invn_attr_n | ||
| invn_attr_o | ||
| serial_number_list | Corresponding serial numbers associated with the transaction. |
Steps to Enable
Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.