Copying Rebate Records

Copying is available only for approved rebate records and only for users with the Administer Rebate Records role. Once you create a copy, you are taken to the Detail view of the record where all of the values are copied in the Override status. For each copied value there is a quick menu:

Override result – Allows you to enter your own value.
Negate result value – Makes the value negative.
Remove override – Clears the value.

Note also that each copied record has the flag 'isManual'.

Submitting Rebate Records

Rebate Records can be submitted for approval only if there is no error or a critical alert.

Mass submit is available for Rebate Records too. For mass submit, it is necessary to have a default Rebate Calculation in place; see the note in Rebate Calculations on how this is handled so that the mass submit can always be executed. Mass approval/denial of Rebate Records is available as well.

You can review the workflow status and details after clicking the View Workflow button.

Revoking Rebate Records

The Revoke action is available only for approved records – in the Rebate Record detail view – and only for users with the Administer Rebate Records role. This action is useful when the Rebate Record was approved in Pricefx, integration did not happen yet and there is nothing to reverse in ERP. When this action is used, the record changes its status to Revoked.

Working with Integration Status Fields

The general rule is that an already approved object cannot be modified. However, these three Rebate Records fields can be updated. The rebaterecord.update endpoint makes an exception when the payload (data block) specifies these ‘integration status’ fields:

Integration Status (intgStatus)
Integration Status Details (intgStatusDetails)
Integration ERP Reference (intgStatusErpReference)

These fields help you keep track of the integration updates. They can be customized (type, name).

You can also use these fields for filtering. On each such update, an IntegrationStatusHistory object (typeCode = ‘ISH’) is created, which stores the integration field values as well as {{itemTypedId}} := RebateRecord.typedId.

If your update request contains non-integration fields as well, you will see this error in the log: ”…updateRebateRecord: integration fields updated, but overrides not allowed on approved RebateRecord”. This has no functional impact, it just guides you how to create proper integration status update requests.

Creating a Data Source from Rebate Records

You can create a Data Source from the Rebate Records table using the Data Source template. The data can be synchronized anytime later by clicking the Sync Metadata button in the Data Source detail.

Browser not supported