EDI 845 Inbound Contract Pricing Processing

The vendor sends the EDI 845 Inbound Contract Pricing Processing document to transmit data related to the vendor status or changes made to the outstanding price authorizations for Vendor on Sale rebates. This type of rebate is vendor-specific and is based on the product being sold to a customer or a group of customers. The rebate can be issued as cash, credit, or another form. A contract number is required.

EDI 845 documents can be received in these formats:
  • SXAPIs, if the PD Inbound Contract Pricing Processing (845) check box is cleared on the SA Administrator Options - Integrations - ION Interface Options screen.
  • ION BODs, if the PD Inbound Contract Pricing Processing (845) check box is selected on the SA Administrator Options - Integrations - ION Interface Options screen.

You can receive rebate records without user intervention through the sxapiPDRebateMnt API call or Process SXContractPricing ION BOD, if these conditions are met:

  • The rebate level is Product.
  • The rebate calculation type is Amount.

Manual rebates and share rebates are supported. Existing rebate records cannot be updated through the SX.api call or ION BOD.

Note: The Create Opposite Shipment Type in OEET setting on the SA Administrator Options-Products-Rebates screen for manual rebates is ignored when rebate records are created through an SX.api call or ION BOD.

One API call or ION BOD can include a transaction set that contains multiple rebate documents. The data for each document is mapped to temp tables, and the data is validated. If the data is valid, rebate records are created on the PD Pricing Setup screen.

If an inbound rebate document generates a warning, a rebate record is created on the PD Mass Maintenance Entry screen. You must correct and update the record. If an inbound rebate document generates a duplicate error or a fatal error, a rebate record is not created. You can review the originating XML document to determine if the rebate with the duplicate or fatal error is valid. If the record is valid, you must manually create the rebate record or correct the inbound data and resubmit for API or BOD processing.

Note:  PD Pricing Setup and PD Mass Maintenance Entry records are always created in the vendor currency using the amount from the inbound document. No exchange rate conversion is required.

You can view the status of inbound rebates on the EDI Electronic Transaction Control Center (ETCC) screen, if the user has the correct security on the operator record.

The inbound electronic document must be translated into a format that can be read by the sxapiPDRebateMnt API call or Process SXContractProcessing BOD. You can use ION to map the inbound XML document to the API-specified temp tables. Contact your Infor Consulting Services representative for assistance.

See information about mapping in the Infor ION User Guide (Cloud).