GET API Enhancements
With this release, we bring you a suite of API improvements that will further bolster the seamless communication as well as integration between Oracle WMS and other external systems you may deploy.
NEW ENTITIES FOR GET API REQUESTS
SUPPORTED ENTITY | URL FOR PAGINATED RESULTS | URL FOR NON-PAGINATED RESULTS (BY SPECIFIC ID) |
---|---|---|
from_manufacturing_transaction_hdr |
|
GET.../lgfapi/v10/entity/from_manufacturing_transaction_hdr/{id} |
from_manufacturing_transaction_dtl |
GET.../lgfapi/v10/entity/from_manufacturing_transaction_dtl/ |
GET.../lgfapi/v10/entity/from_manufacturing_transaction_dtl/{id} |
from_manufacturing_transaction_dtl_serial_nbr |
GET |
GET |
NEW PARAMETER FOR PATCH ORDER API
Now, you can update the following fields for Orders having a status less than “Shipped” using the PATCH Order API:
- Priority
- Reference Number
- Special Instructions
- Sales Channel
- Gift Message
- Required Ship Date
- Start Ship Date and Stop Ship Date
PATCH URL
.../wms/lgfapi/v10/entity/order_hdr
Sample Body
{
"fields":
{
"priority": " ",
"ref_nbr": " ",
"spl_instr": " ",
"sales_channel": " ",
"gift_msg": " ",
"req_ship_date": " ",
"start_ship_date": " ",
"stop_ship_date": " "
}
}
INTRODUCTION OF NEW FIELDS
1. GET Request for Container
The field “cart_nbr” is introduced in the GET request for Container as well as all the sub-entities of Container, i.e, IB LPN and OB LPN.
ENTITY |
URL |
---|---|
container | .../wms/lgfapi/v10/entity/container |
iblpn | .../wms/lgfapi/v10/entity/iblpn |
oblpn | .../wms/lgfapi/v10/entity/oblpn |
Now, you can filter for the “container” field for the GET entities via the “fields” / “values_list” function. Similarly, you can also filter for a specific “container” / “iblpn” / “oblpn” records via the “cart_nbr” field.
2. GET Request for Parcel Shipment Detail
To aid the accurate identification of Parcel Shipment records, a new field “planned_parcel_shipment_nbr” is introduced in the GET API of “parcel_shipment_dtl” entity.
ENTITY | URL |
---|---|
parcel_shipment_dtl |
|
Now, you can filter for the “planned_parcel_shipment_nbr” field for the GET entities via the “fields” / “values_list” function. Similarly, you can also filter for a specific “parcel_shipment_dtl” records via the “planned_parcel_shipment_nbr” field.
3. GET Request for Location
The field “ignore_attr_values_for_restric_invn_attr” is introduced in the GET request for Container as well as all the sub-entities of Container, i.e, Reserve Location and Active Location.
ENTITY | URL |
---|---|
location | .../wms/lgfapi/v10/entity/location |
reserve_location | .../wms/lgfapi/v10/entity/reserve_location |
active_location | .../wms/lgfapi/v10/entity/active_location |
Now, you can filter for the “ignore_attr_values_for_restric_invn_attr” field for the GET entities via the “fields” / “values_list” function. Similarly, you can also filter for a specific “location” records via the “ignore_attr_values_for_restric_invn_attr” field.
4. GET Request for Stage Planned Outbound Load Order Detail
To aid the accurate identification of Stage Planned Outbound Load Order Detail records, the following new fields are introduced in the GET API of “stage_planned_ob_load_order_dtl” entity:
- ship_request_line
- action_code
- planned_qty
- qty_uom_code
- ob_lpn_type
ENTITY | URL |
---|---|
stage_planned_ob_load_order_dtl |
|
5. GET Request for Stage Planned Parcel Shipment Header and Stage Planned Parcel Shipment Detail
To aid the accurate identification of Stage Planned Outbound Load Order Detail records, the following new fields are introduced in the GET API of “stage_planned_ob_load_order_dtl” entity:
- id
- url
- create_user
- create_ts
- mod_user
- mod_ts
ENTITY | URL |
---|---|
stage_planned_parcel_shipment_hdr | .../wms/lgfapi/v10/entity/stage_planned_parcel_shipment_hdr |
stage_planned_parcel_shipment_dtl | .../wms/lgfapi/v10/entity/stage_planned_parcel_shipment_dtl |
Steps to Enable
You don't need to do anything to enable this feature.