Vendor on Sale rebates created through SX.API calls

You can receive Vendor on Sale rebate records through sxapiPDRebateMnt calls. The rebate level must be Level 1 Product and have a rebate calculation type of amount. Manual rebates and share rebates are supported. Existing rebate records cannot be updated by information in an SX.API call.

This method of receiving rebate records is an alternate method to receiving EDI 845 Price Authorization Acknowledgment/Status documents, which is not supported in the cloud.

One SX.API call consists 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 without user intervention.

Note: The Create Opposite Shipment Type in OEET setting in SA Administrator Options-Products-Rebates for manual rebates is not applied when rebate records are created through SX.API calls.

If an inbound rebate document generates a warning, a record is created in PD Mass Maintenance Entry, but 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.

You can view the status of inbound rebates in the EDI Electronic Transaction Control Center (ETCC). SXAPI/PD Rebate Maintenance must be allowed on the Other Options page of your operator record.

In ETCC, each rebate document with a processed status is a processed transaction set. Each rebate document with an error status is a record with a warning, fatal, or duplicate error.

These business rules can be set up to control rebate record processing:

Default Rebate Start Date to Current Date
If a start date for a rebate is not included in the API call or is an invalid value, this business rule determines if the current date is used as the start date.
Default Rebate End Date
If an end date for a rebate is not included in the API call or is an invalid value, this business rule calculates the end date by adding the Rule Value to the start date.
Allow Multiple Rebates for a Contract
If an inbound rebate record is identical to an existing rebate record except for the start date, this business rule determines if a duplicate record is created or a duplicate error occurs.

Events can be set up in SA Event Manager Activate Entry records to notify you of rebates without errors, rebates with errors, and transaction set summaries.

Set up is required to receive Vendor on Sale rebate records through sxapiPDRebateMnt calls.

See the Infor CloudSuite Distribution Setup and Administration Guide for EDI.