Vendor on Sale rebates created through SX.API calls or ION BODs

You can receive Vendor on Sale rebate records through sxapiPDRebateMnt API calls or Process SXContractPricing ION BODs. 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 with information in an SX.API call or ION BOD.

The SX.API 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 without user intervention.

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

If an inbound rebate document generates a warning, a 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.

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.

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 an API call or ION BOD does not contain a start date or contains an invalid value, this business rule determines if the current date can be used as the start date.
Default Rebate End Date
If an API call or ION BOD does not contain an end date or contains 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 API calls or Process SXContractPricing BODs.

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