EDI 845 Price Authorization Acknowledgment/Status inbound

Note: EDI 845 documents are received through SXAPI calls, not ION BODs.

The vendor sends the EDI 845 Price Authorization Acknowledgment/Status document to transmit specific data that is relative to the status of, or changes to, outstanding price authorizations for Vendor on Sale rebates. This type of rebate is vendor-specific and based on product being sold to a customer or a group of customers. The rebate may be issued as cash, credit, or another form. A contract number is required.

You can receive rebate records without user intervention through the sxapiPDRebateMnt call 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.

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

One API call include of a transaction set that can contain 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 in PD Pricing Setup.

If an inbound rebate document generates a warning, a record is created in PD Mass Maintenance Entry. You must correct and update the record manually. If an inbound rebate document generates a duplicate error or 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 then manually create the rebate record or correct the inbound data and resubmit for API 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 in EDI Electronic Transaction Control Center (ETCC) if you have the correct security on your operator record.

The inbound electronic document must be translated into a format that can be read by the sxapiPDRebateMnt call. 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 Desk User Guide Cloud Edition.