Filter-out function for combination of non-rebatable suppliers and items

Description	In the previous releases, the filtering in ION is only done for SupplierPartyMaster, PurchaseOrder, and ReceiveDelivery BODs with suppliers which are not rebatable. Non-rebatable items are only flagged and the ItemMaster BOD still gets routed to Supplier Rebate inbox. As an enhancement, the Item master data, which are not eligible for supplier rebate agreements, are now filtered-out in ION. You can use the field User-defined field 3 - item (MMCFI3) of 'Item. Open' (MMS001/G) in M3 to tag these items. In the generated ItemMaster BOD, this is mapped to the element ItemFreeField3 under UserArea. A value of 0 or No indicates that the item is non-rebatable. ReceiveDelivery BODs for these items are also filtered-out in ION.
	For the existing items that are already replicated in Supplier Rebate prior to updating the data flow, flagging it as non-rebatable in M3 will not remove it from the corresponding SR tables. You must purge the item data in the Supplier Rebate application. Then, the ItemMaster must rerun in 'Initial Load. Open' (EVS006) using the BOD verb Sync. When you change the Item from non-rebatable to rebatable, you must also rerun initial load for PurchaseOrder and ReceiveDelivery, so previously filtered-out BODs are routed correctly. These BODs inherit the ItemFreeField3 value from the item master record at the time of publishing. The SRRebatable fields of existing records in SRPOLine and SRPOReceipt tables are not automatically updated based on ItemMaster BOD updates.
	To handle purchase orders having multiple lines with different item rebatable flag values, a new parameter Filter non-rebatable PO Line items is added in Process Defaults to provide option for saving lines of purchase orders coming in to ISR. The default value is set to 0 which saves all PO Line items, regardless of item rebatable flag. A value of 1 indicates that the PO lines are checked and only those lines with items tagged as rebatable are saved in SRPOLine table. When a Replace PurchaseOrder BOD is received, with an updated PO line rebatable flag from non-rebatable to rebatable, it will be queued in TransactionOnQueue and be 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: First, if the Filter non-rebatable PO Line items parameter value is 0, SRRebatable field in SRPOLine table is updated to 0. Second, if the Filter non-rebatable PO Line items parameter value is 1, the PO line record is deleted from SRPOLine table. Also, it is no longer displayed in Non-Accruing Purchase Orders report. No changes are done automatically to existing accrual and claim records in Supplier Rebate. The affected agreements shows the Regenerate Indicator, and you should manually trigger the regeneration process.
Limitation	You must not change the item rebatable flag frequently as it requires initial load (using BOD verb Sync) to accurately compute for accruals. There is no available selection for verb Sync for initial load in on-premise environments. Using verb Show does not route the BODs into the created filters for the rebatable flags in ION. When you change the item rebatable flag, the initial load of purchase transactions should also be done to capture the previous data. Otherwise, activating a new agreement only creates accruals for transactions moving forward. If only future transactions are required, the current processing for real-time BODs should suffice.
KB Article	2197235

Description

In the previous releases, the filtering in ION is only done for SupplierPartyMaster, PurchaseOrder, and ReceiveDelivery BODs with suppliers which are not rebatable. Non-rebatable items are only flagged and the ItemMaster BOD still gets routed to Supplier Rebate inbox.

As an enhancement, the Item master data, which are not eligible for supplier rebate agreements, are now filtered-out in ION. You can use the field User-defined field 3 - item (MMCFI3) of 'Item. Open' (MMS001/G) in M3 to tag these items. In the generated ItemMaster BOD, this is mapped to the element ItemFreeField3 under UserArea. A value of 0 or No indicates that the item is non-rebatable. ReceiveDelivery BODs for these items are also filtered-out in ION.

For the existing items that are already replicated in Supplier Rebate prior to updating the data flow, flagging it as non-rebatable in M3 will not remove it from the corresponding SR tables. You must purge the item data in the Supplier Rebate application. Then, the ItemMaster must rerun in 'Initial Load. Open' (EVS006) using the BOD verb Sync. When you change the Item from non-rebatable to rebatable, you must also rerun initial load for PurchaseOrder and ReceiveDelivery, so previously filtered-out BODs are routed correctly. These BODs inherit the ItemFreeField3 value from the item master record at the time of publishing. The SRRebatable fields of existing records in SRPOLine and SRPOReceipt tables are not automatically updated based on ItemMaster BOD updates.

To handle purchase orders having multiple lines with different item rebatable flag values, a new parameter Filter non-rebatable PO Line items is added in Process Defaults to provide option for saving lines of purchase orders coming in to ISR. The default value is set to 0 which saves all PO Line items, regardless of item rebatable flag. A value of 1 indicates that the PO lines are checked and only those lines with items tagged as rebatable are saved in SRPOLine table.

When a Replace PurchaseOrder BOD is received, with an updated PO line rebatable flag from non-rebatable to rebatable, it will be queued in TransactionOnQueue and be 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:

First, if the Filter non-rebatable PO Line items parameter value is 0, SRRebatable field in SRPOLine table is updated to 0.

Second, if the Filter non-rebatable PO Line items parameter value is 1, the PO line record is deleted from SRPOLine table. Also, it is no longer displayed in Non-Accruing Purchase Orders report.

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

Limitation

You must not change the item rebatable flag frequently as it requires initial load (using BOD verb Sync) to accurately compute for accruals.

There is no available selection for verb Sync for initial load in on-premise environments. Using verb Show does not route the BODs into the created filters for the rebatable flags in ION.

When you change the item rebatable flag, the initial load of purchase transactions should also be done to capture the previous data. Otherwise, activating a new agreement only creates accruals for transactions moving forward. If only future transactions are required, the current processing for real-time BODs should suffice.

KB Article

2197235