Support JSON Format for Additional Input and Output Interfaces
We’ve extended JSON format to support Input and Output interfaces via new APIs.
INPUT INTERFACE - ITEM FACILITY
A new API “item_facility” is introduced to Item Facility that loads the stage tables accordingly:
Post.../lgfapi/v10/stage/item_facility
OUTBOUND LOAD INTERFACE AND PLANNED OUTBOUND LOAD
The following new APIs are introduced for records to load the stage tables accordingly:
| Entity | APIs |
|---|---|
| OB Load interface |
POST.../lgf_25b_qa/wms/lgfapi/v10/stage/outbound_load |
| Planned OB Load |
POST.../lgf_25b_qa/wms/lgfapi/v10/stage/planned_ob_load |
The API exposes the following parameter:
| Name | Description |
|---|---|
| async |
If the value = no/false (default), then interface will run synchronously. If the value = yes, then interface will run in async mode. |
| only_load_flg |
If the value = no/false (default), then the API runs the interface and process corresponding records in stage tables. If the value = yes, then the API only loads the record to stage table. To process interface records, user can use run_stage_interface API. |
OUTPUT INTERFACE - INBOUND SHIPMENT VERIFICATION
We now support JSON format for IB Shipment verification output interface, generating Inbound Shipment Verification file in JSON format. We’ve enabled field selection by choosing relevant fields, reducing the payload size significantly.
- The field selection action button must be enabled when the 'interface format' for the 'inbound_shipment_verifications_export' output interface is set to JSON. The field selection lists all the available fields in the respective headers and entities.
NOTE: All the required fields mentioned in the sample file are auto enabled, by default.
- Following new fields are introduced in the IB shipment detail screen Shipment Verification JSON formats.
- shipped_uom
- shipped_uom_qty
- shipped_uom_received_qty
NOTE: The fields support both Intra class and Inter class UOM’s.
TO_MHE_DISTRIBUTION_INFO
We’ve extended DISTRIBUTION_INFO output interface type to support in JSON format.
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.