Reflect changes to existing data

Complete these actions if the changes must take effect in the previous data already in Supplier Rebate.

  1. Purge either or both the supplier and item data in the Supplier Rebate application.
  2. Run the initial load for either or both SupplierPartyMaster and ItemMaster using the Sync BOD verb. Using the BOD verb Show does not route the data into the filters for non-rebatable flags.
  3. Rerun the initial load for PurchaseOrder and ReceiveDelivery.
    Note: The SRRebatable fields of existing records in SRPOLine and SRPOReceipt tables are not automatically updated based on ItemMaster BOD updates. These BODs inherit either or both the supplier and item rebatable flag from the master record at the time of publishing. If the change in rebatable flag should only affect future transactions, the current processing for real-time BODs should suffice.

    When a Replace PurchaseOrder BOD is received, with an updated PO line rebatable flag from non-rebatable to rebatable, it is queued in TransactionOnQueue and then processed in real-time through agreement validation and accrual creation.

    These are the results if the update is from being rebatable to non-rebatable and matches these configurations:
    • If the Filter non-rebatable PO Line items parameter value is 0, SRRebatable field in SRPOLine table is updated to 0.
    • If the Filter non-rebatable PO Line items parameter value is 1, the PO line record is deleted from SRPOLine table.

    No changes are done automatically to existing accrual and claim records in Supplier Rebate. The affected agreements shows the Regenerate Indicator, and you must manually trigger the regeneration process.