Shipment Receipt Guidelines (.csv)

See How to Use this Guide before selecting the below fields.

Message Type: PT_SHIPMENT_RECEIPT

When sending an element in Date or DateTime format, a valid date must be given. "00" is not a valid day or month value and "0000" is not a valid year value.
Data Element Occurs Format Length Enum Req Description
PTShipmentReceiptMessage [1...1] - - - M Root element of message.
  ControlFileHeader [1...1] - - - M This section identifies the file routing header information.
  Flag [1...1] String [3/3] - M Populate Flag with HDR constant tag. *1
  FileControlNumber [1...1] String [1/*] - M Unique file control ID number. *2
  FileSenderNumber [1...1] String [1/20] - M File sender's company identifier. *3
  FileReceiverNumber [1...1] String [1/20] - M File recipient's company identifier. *4
  FileDate [1...1] Date [10/10] - M Date file generated in YYYY-MM-DD date format. *5
  FileTime [1...1] Time [9/9] - M Time file generated in HH:MM:SSZ time format (must be GMT). *6
  BOD [1...1] - - - M This section identifies the Location where the receiving occurs.
  Flag [1...1] String [3/3] - M Populate Flag with BOD constant tag. *7
  LocationType [0...1] String [1/*] Location C Attribute identifies the location types.  *8
Mandatory if Location is populated.
  Location [0...1] String [1/*] - C Location where the receiving occurs and the inventory for the Transaction Histories (THs) will reside. This will associate the THs with that location. *9

If the Product Track application is configured to use Locations to model your facilities, populate this element with one of the configured location values. If the Product Track application is not configured to use Locations, omit this element.
  ReceiptType [1...1] String [1/*] ReceiptType M Indicates if receipt is for a purchase or transfer of goods from one facility to another (e.g. warehouse to warehouse, 3PL transfer, pharmacy to pharmacy). For intra-company transfer receipts, a transfer shipment must have been initiated. TH/quantities transferred are made accessible to the new location. *10
  DeliveryNumber [1...1] String [1/*] - M The delivery number for the shipment. The system will use the Delivery Number to match against THs received from a supplier (against the Delivery Number in the ASN), or to match against the transfer Delivery Number associated with transferred THs for an intra-company transfer. *11
  IsPharmacy [0...1] Boolean [0/*] - C Identifies if receiving entity is a pharmacy. Used only when ReceiptType = Purchase.

Valid values: *12

  • True
    • Indicates receiving party is a pharmacy.
    • LotNumber is optional.
  • False or empty
    • Indicates receiving party is not a pharmacy.
    • LotNumber required.
    • Empty means that this element is omitted.
  ITM [1...*] - - - M This section identifies the list of one or more products and quantities received against the delivery. Create as many ITM rows as needed, one for each NDC and Lot received.
  Flag [1...1] String [3/3] - M Populate Flag with ITM constant tag.
  NDCType [1...1] String [1/*] NDCType M Attribute identifies the NDC type. *13
  NDC [1...1] String [1/*] - M The NDC of the product being received WITHOUT hyphen separators. *14
  LotNumber [0...1] String [0/*] - C The lot/batch number of the product being received. If IsPharmacy is set to false or not populated, LotNumber is required. If IsPharmacy is set to true, LotNumber is optional. *15
  Quantity [1...1] Integer - - M The each/unit quantity of the product being received. This value will be used to represent the quantity received against the Transaction History. Subsequent picks against the Transaction History will be against this quantity and the unit of measures (each/unit) must be consistent. Reverse receipts are supported by providing a negative quantity. This quantity is decremented from the received quantity of the matching Transaction History. *16
  ReferenceIdentifier [0...1] String [0/*] - O An identifier assigned to the Transaction History. This value is used to precisely match against the Transaction History in subsequent operations, such as Pick/Ship and Update (void). The ReferenceIdentifier can be used with both Purchase and Transfer receipts and will set the Reference Identifier against the at the TH receiving location. *17
If a ReferenceIdentifier is assigned to a Transaction History, it must be used to subsequently reference the Transaction History for any operation that can be performed on that Transaction History. Once assigned, the ReferenceIdentifier is the only way to access the Transaction History.
  ProductOrigin [0...1] String [0/*] ProductOrigin C Indicates how the product was sourced and will inform the fields that will appear on the outbound Transaction History when the product is sold. If this value is not provided in the receiving interface, the NDC must be populated in Product Master Data, with the ProductOrigin flag set. *18
  • OriginatorExclusiveDistributor indicates the company that purchased this product is the Exclusive Distributor of the Product. In this case, the Exclusive Distributor will set ProductOrigin to be OriginatorExclusiveDistirbutor, and NOT DirectPurchaseManufacturer, even though the Exclusive Distributor did purchase from the manufacturer. This will ensure that outbound Transaction Histories for this product will start with the Exclusive Distributor and not "continue" the received Transaction History.
  • ProductOrigin is used only for a Purchase receipt type. Does not apply to Transfer Receipts as the Transaction History was already tagged on initial inbound receipt from purchase.
  TransactionIdentifierType [1...1] String [1/*] TransactionIdentifier C Attribute that identifies the message identifier type. Attribute is required if TransactionIdentifier is populated. *19
  TransactionIdentifier [0...1] String [0/*] - O Business transaction identifier for the business transaction that initiated the product receipt (e.g. PO Number, Transfer Number, etc). *20