IB Shipment Detail

Field	Type
cust_date_1	Date
cust_date_2	Date
cust_date_3	Date
cust_date_4	Date
cust_date_5	Date
cust_decimal_1	Decimal
cust_decimal_2	Decimal
cust_decimal_3	Decimal
cust_decimal_4	Decimal
cust_decimal_5	Decimal
cust_field_1	String
cust_field_2	String
cust_field_3	String
cust_field_4	String
cust_field_5	String
cust_long_text_1	String
cust_long_text_2	String
cust_long_text_3	String
cust_number_1	Integer
cust_number_2	Integer
cust_number_3	Integer
cust_number_4	Integer
cust_number_5	Integer
cust_short_text_1	String
cust_short_text_2	String
cust_short_text_3	String
cust_short_text_4	String
cust_short_text_5	String
cust_short_text_6	String
cust_short_text_7	String
cust_short_text_8	String
cust_short_text_9	String
cust_short_text_10	String
cust_short_text_11	String
cust_short_text_12	String
inv_attr_a	String
inv_attr_b	String
inv_attr_c	String
inv_attr_d	String
inv_attr_e	String
inv_attr_f	String
inv_attr_g	String
inv_attr_h	String
inv_attr_i	String
inv_attr_j	String
inv_attr_k	String
inv_attr_l	String
inv_attr_m	String
inv_attr_n	String
inv_attr_o	String

Make Changes During Different Shipment Statuses

You can also make changes to IB Shipment Detail fields through PATCH API when the Shipment status is in "Receiving Started" or "Receiving Complete" based on the status of the shipment.

Note:

The following are the fields which are allowed to be updated in different statuses:

Field	Type
shipped_qty	String
container_nbr	String
item_id	String
po_dtl_id	String
pallet_nbr	String
batch_nbr	String
expiry_date	String
priority_date	String
invn_attr (a-o)	String
lpn_weight	String
lpn_volume	String
lpn_length	String
lpn_height	String
lpn_width	String
lpn_is_physical_pallet_flg	String
dtl_recv_flag	String
putawaytype_id	String
receipt_advice_line	String
marked_for_qc	String

Inventory Attributes supported using IB Shipment Detail Patch API

Example Request:

PATCH .../wms/lgfapi/v10/entity/ib_shipment_dtl/123/

where 123 is the id of the IB Shipment Detail that needs to be updated.

JSON sample of the request body:

{

"fields": {

"invn_attr_id":

{ "invn_attr_a": "a", "invn_attr_b": "b", "invn_attr_c": "c" }
,

"cust_field_1": "cust1"

}

}

Validations

If invn_attr_id is provided, additional validations are needed.IB shipment header status should be less than Receiving-Completed.the IB Shipment detail should not have started receiving. received_qty shouldbe 0.If the ib shipment detail has po_dtl_id already populated, meaning it is linked to a PO, we will not support updating the invn attributes and the validation will fail.

If these validations fail, the request should fail (so any other fields likecustom fields provided in this request will not be updated even though theymay have more lenient validations).Validate that the invn-attribute record matches the facility/company.If no invn_attr_id is provided then the current validations for custom fields should apply.