832 processing

This table shows detail fields in the Contract Interface Catalog and how they are used for processing:
Field Description
Working Contract ID This field is used in Contract Interface Catalog records to group records. It does not reference an existing contract in Contract Management.

The EDI Trading Partner Run Group field value is mapped to Working Contract ID. The Trading Partner Run Group value default is from the Trading Partner EDI Number but you can specify any value. The Run Group field is used on other inbound translations such as Purchase Order Acknowledgments (855), Receipt (856), and Invoices (810).
Effective Date and Expiration Date Date values are communicated in a DTM segment. Specific qualifiers identify whether the date is an effective date or an expiration date.
  • 007-Effective and 092-Contract Effective are recognized as Effective Date qualifiers.
  • 036-Expiration and 093-Contract Expiration are recognized as Expiration Date qualifiers.

If a DTM segment is included at the line level, then effective or expiration date, or both are set on the line detail record. Otherwise, they are set on the Contract Header.

The first two example DTM segments indicate a contract effective date of 3/1/2020. The last two DTM segment examples contain an Expiration Date of 3/1/2021.

DTM^007^20200301

DTM^092^20200301

DTM^036^20210301

DTM^093^20210301
Contract Lines An LIN segment identifies a contract line. Some elements contain qualifiers, which are used to identify the type of value in this element:

LIN^1^IN^000041^VC^005700P225^MG^GR8758~

This list shows the segment values:

  • IN - Buyer Item Number identifies your item number, if it exists
  • VC - Vendor Catalog Number identifies the Vendor's item number
  • MG - Manufacturer Number identifies the manufacturer's item number
Base and Tiers Base and Tiers

Contract prices and units of measure are communicated in CTP segments. Using this example, 41.1817 is the Base Cost and BX is the base UOM.

CTP^WH^QTE^41.1817^1^BX~

Tiers

If the 832 contains tier pricing information, then the tiers must be identified by the CTP02 element.

  • Valid tier identifiers are C01-C30.

    A maximum of five tiers are supported.

  • During processing, the tier is set by removing the C from the tier identifier. C01 is tier 01, C27 is tier 27.
  • Base cost and UOM are set by the first tier if they are blank.

    CTP^C01.05^1^EA

    CTP^C02.10^1^BX

    CTP^^C03^2^1^CA

    CTP^^C11^5.01^1^CT

    CTP^^C12^1000^1^CP

    CTP^^C13^200000^1^DT

Using the example above, this list shows the results:

  • Tier 01 cost is $0.05. The base cost is also set to $.05 and the UOM to EA.
  • Tier 11 is $5.01.

    Tier C13 is not mapped in the example because a maximum of five tiers are supported and there are already five CTP segments with tier identifiers.