Invoices for interfaced external purchase orders

If you are receiving invoices for purchase orders that are created in a third-party system and then interfaced to FSM there are three data substitution records to help mapping received transactions for those orders.

MAP_TO_INTERFACED_PO

  • Configuration
  • Optional
  • Default Behavior:
  • Related:
Field Value Example Comment
List Name MAP_TO_INTERFACED_PO
Your Value Y
Partner Value <tpid> or *

Use when you will be only receiving inbound transactions from a trading partner for POs interfaced from third-party systems. An example might be a pharmacy system which creates purchase orders and a file which is used to load those orders into FSM. When enabled the 810 Purchase Order from BEG04 will be mapped to the Interfaced Purchase Order field and Purchase Order field will be empty.

LOOKUP_INTERFACE_PO

  • Configuration
  • Optional
  • Default Behavior: No lookup in Interfaced Purchase Order is performed.
  • Related:
Field Value Example Comment
List Name LOOKUP_INTERFACE_PO
Your Value Y
Partner Value <tpid> or *

Use when you are receiving inbound transactions from a supplier for both interfaced third-party system POs and FSM original Purchase Orders. Enables a lookup of the purchase order in Interfaced Purchase Order table. If an Interfaced Purchase Order record found the FSM purchase order is mapped. If a record is not found, the original 810 Purchase Order from BIG04 is mapped.

LOOKUP_MIGRATED_PO

  • Configuration
  • Optional
  • Default Behavior: No lookup in Interfaced Purchase Order is performed.
  • Related: INCLUDE_PO_RELEASE
Field Value Example Comment
List Name LOOKUP_MIGRATED_PO
Your Value Y
Partner Value <tpid> or *

Use when you have migrated from a v10 or earlier system and have open Purchases Orders that you expect to receive transactions for. When enabled, the translation process looks for the 810 PO Number in Interfaced Purchase Order table. If a match is found, the result will be mapped to the Purchase Order field. If an Interfaced Purchase Order record is not found, the original 810 Purchase Order will be mapped. After all migrated POs are closed you can delete this record.

INCLUDE_PO_RELEASE

  • Configuration
  • Optional
  • Default Behavior: PO Release is not included by default.
  • Related: Required if INCLUDE_PO_RELEASE is enabled for outbound Purchase Orders
Field Value Example Comment
List Name INCLUDE_PO_RELEASE
Your Value Y
Partner Value <tpid> or *

Legacy mapping configuration to include the PO Release Number in the Purchase Order value sent the purchase order 850. Print, fax, and email POs would include the release number as part the Purchase Order number. This data substitution made the EDI PO numbers look like the printed PO numbers. Format was PO-Release-POCode. For example, 12345-1-STOCK. If you enable include PO release for outbound POs, you must enable it for inbound transactions with this data substitution record.