Description is not available. This will be the final destination of the carton. For a cross-dock order this will be the allocation location, otherwise it will be the direct to order location. Holds the UCC-128 carton number. Description is not available. Description is not available. Description is not available. Description is not available. Description is not available. Description is not available. Description is not available. This field represents the shipment number that manifest systems use to group multi-container shipments for a carrier. Typically a 1 of 4 type message. This is a unique tracking number that is used to track containers through carriers system. Description is not available. Not used in RWMS Description is not available. Contains any comments about the shipment container. Description is not available. Contains the Schedule identifier number. Contains the flag to enable auto receiving at SIM. Contains the location that the shipment will be delivered to. RWMS does not utilize this field. This field contains the location type of the to_location field. Valid values are 'S' = store, 'E' = finisher, and 'W' = warehouse. RWMS does not utilize this field. Indicates the store type of the to_location. This will only be populated if to_loc_type is 'S'. Valid values are: 'C' = company store, 'F' = franchise store. RWMS does not utilize this field. Indicates if the to_location is stockholding or not. Only populated if to_loc_type is 'S'. Valid values are: 'Y' = yes, 'N' = no. RWMS does not utilize this. field. For transfer and allocation shipments, this field will hold the location from which the shipment was sourced. RWMS does not utilize this field. This field contains the location type of the from_location field. Valid values are 'S' = store and 'W' = warehouse. RWMS does not utilize this field. Indicates the store type of the from_location. This will only be populated if from_location is 'S'. Valid values are: 'C' = company store, 'F' = franchise store. RWMS does not utilize this field. Indicates if the from_location is stockholding or not. Only populated if from_location is 'S'. Valid values are: 'Y' = yes, 'N' = no. RWMS does not utilize this field. Holds the advance shipping notice number associated with a shipment. This field is used to determine the ship origin. If asn_type is 'C', ship_origin will be set to '6' (ASN UCC-128) upon insert to the SHIPMENT table. Otherwise, SHIP_ORIGIN is defaulted to '0' (ASN Shipment). Description is not available. Holds the transaction sequence number on the input message from the receiving PO or transfer process. This field contains the date the transfer or PO was shipped. This field contains the estimated arrival date of a vendor PO shipment. It is updated by EDIUP856. It is used for vendor/lead time analysis. Not used in RWMS. Not used in RWMS. Not used in RWMS. Not used in RWMS. Not used in RWMS. Not used in RWMS. Not used in RWMS. Not used in RWMS. Not used in RWMS. Not used in RWMS. Not used in RWMS. Contains the courier that will deliver the shipment. Contains the service level code for the courier that will deliver the shipment. Contains the supplier who will provide the merchandise specified in the order. This element is used to validate the order number(s) in ASNInPO (ASNInPO.po_nbr). The order number must be in the table ORDHEAD, in either the ORDER_NO column or VENDOR_ORDER_NO column. Indicates the payment terms for freight charges associated with the order. Used to validate the order number(s) in ASNInPO (ASNInPO.po_nbr). The ship_pay_method in the message must match the value of the order's SHIP_PAY_METHOD in RMS (ORDHEAD table.) If the message field is blank, the ORDHEAD value must be NULL. Description is not available. Contains any comments about the shipment. Description is not available. Required if the order's pre_mark_ind is 'Y'. Validated against the ALLOC_DETAIL table. There needs to be at least one allocation with the same ORDER_NO that is in the ASNIn message, and the same TO_LOC as the final_location. Unique identifier for the item. Either vpn, item_id, or ref_item must be specified in the message. Contains the number of items expected to be received based on the supplier's ASN for this Item/Shipment combination. Description is not available. Used to find the item number, found on the ITEM_SUPPLIER table. Either vpn, item_id, or ref_item must be specified in the message. Not used in RWMS. Not used in RWMS. Contains a reference item to the item field. Either vpn, item_id, or ref_item must be specified in the message. Specifies the transfer or allocation number associated with the shipment/item/carton. This is a Y or N indicator to inform the consuming application if the distro is for a consmer direct order or not. This is the customer order number that was generated by OMS and contains multiple fulfillment numbers. Based on a customer order - OMS will generate fulfillments to specific locations based on availability. RMS will generate Transfers based on the fulfillment request. Valid Document Type Description is not available. Contains any comment about the item in the shipment. Collection of Universal Identification Numbers. Description is not available. Identifies the order number which relates to the goods delivered in the shipment. Validated against the ORDHEAD table, and also the SHIPMENT table if the message applies to an existing shipment. Description is not available. Contains the last date that delivery of the order will be accepted. Contains any comments about the shipment. Description is not available. Description is not available. Represents a Universal Identification Number. Universal Identification Number Description is not available. This field contains the location that the shipment will be delivered to. This field contains the location type of the to_location field. Valid values are 'S' = store, 'E' = finisher, and 'W' = warehouse. RWMS does not utilize this field. Indicates the store type of the to_location. This will only be populated if to_loc_type is 'S'. Valid values are: 'C' = company store, 'F' = franchise store. RWMS does not utilize this field. Indicates if the to_location is stockholding or not. Only populated if to_loc_type is 'S'. Valid values are: 'Y' = yes, 'N' = no. RWMS does not utilize this field. For transfer and allocation shipments, this field will hold the location from which the shipment was sourced. This field contains the location type of the from_location field. Valid values are 'S' = store and 'W' = warehouse. RWMS does not utilize this field. Indicates the store type of the from_location. This will only be populated if from_location is 'S'. Valid values are: 'C' = company store, 'F' = franchise store. RWMS does not utilize this field. Indicates if the from_location is stockholding or not. Only populated if from_location is 'S'. Valid values are: 'Y' = yes, 'N' = no. RWMS does not utilize this field. Holds the advance shipping notice number associated with a shipment to be deleted. ASNs originating from external vendors or SIM, the message is routed to the proper RWMS warehouse instance based on the facility type found in the routing information and the �To� location found in the payload. External app publishes ASN Inbound msgs on to the RIB System. RMS subscribes to these inbound ASAs to create shipment records. Topic Name : etASNIn Subcriber = ASNIn_sub (RMS). This Operation invokes the publishing of "Delete" event for the ASN(Inbound). ASNInRef RBO complies with the XML schema ASNInRef.xsd, for more information on RBO structure and semantics please refer to the associated XSD.

ServiceOpStatus object represents the acknowledgment from the service. It encloses the information about the Successful or Failed stataus of the publish event.

Throw this exception when an unknown "soap:Server" side problem occurs. Throw this exception when a "soap:Server" side publish problem occurs. This Operation invokes the publishing of "Modify" event for the ASN(Inbound). ASNInDesc RBO complies with the XML schema ASNInDesc.xsd, for more information on RBO structure and semantics please refer to the associated XSD.

ServiceOpStatus object represents the acknowledgment from the service. It encloses the information about the Successful or Failed stataus of the publish event.

Throw this exception when an unknown "soap:Server" side problem occurs. Throw this exception when a "soap:Server" side publish problem occurs. This Operation invokes the publishing of "Create" event for the ASN(Inbound). ASNInDesc RBO complies with the XML schema ASNInDesc.xsd, for more information on RBO structure and semantics please refer to the associated XSD.

ServiceOpStatus object represents the acknowledgment from the service. It encloses the information about the Successful or Failed stataus of the publish event.

Throw this exception when an unknown "soap:Server" side problem occurs. Throw this exception when a "soap:Server" side publish problem occurs.