Filter-out function for non-rebatable suppliers and purchase transactions in ION

Description	Most customers have thousands of suppliers but only a few hundred have actual supplier rebate agreements. To limit the volume of data to process, there should be a way to identify these suppliers and restrict the SupplierPartyMaster BODs from coming in to ISR, and their related transactions. As an enhancement, the Supplier master data, which are not eligible for supplier rebate agreements, are now filtered-out in IONDesk. M3 uses the field User-defined field 4 - item (IDCFI4) of Supplier. Open (CRS620) program to tag these suppliers. In the generated SupplierPartyMaster BOD, this is mapped to the element SupplierFreeField4 under UserArea. A value of 0 or No indicates that the supplier is non-rebatable, and do not get routed to Supplier Rebate inbox anymore. This attribute is also inherited to the purchase orders and receipts of the supplier upon publishing of the corresponding PurchaseOrder and ReceiveDelivery BODs. These transactions are also filtered-out in IONDesk given the same conditions.
	You can now use the field User-defined field 4 - item (IDCFI4) in Supplier. Open (CRS620/F) to flag Supplier Rebate-eligible suppliers. If the field value is 0 or No, the supplier is non-rebatable. Any other value, including blank, indicates that the supplier is rebatable. This flagging is inherited in the subsequent purchase orders and receipts of the supplier, and it is also reflected in the BOD element SupplierFreeField4 in PurchaseOrder and ReceiveDelivery BODs.
	In IONDesk, the newly created non-rebatable Supplier masterdata (SupplierPartyMaster BODs) and their purchase orders and receipts (PurchaseOrder and ReceiveDelivery BODs) are filtered out, and do not get routed to the Supplier Rebate inbox. For the existing suppliers 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 supplier data in the Supplier Rebate application. A checkbox for Supplier is now available in the Purge Supplier Rebate Data form for this purpose. Then, the SupplierPartyMaster must rerun in Initial Load. Open (EVS006) using the BOD verb Sync. When you change the Supplier from non-rebatable to rebatable, you must also rerun PurchaseOrder and ReceiveDelivery, so previously filtered-out BODs are routed correctly. The BODs inherit the SupplierFreeField4 value from the Supplier at the time of publishing.
	Note that BOD verb Show does not pass the BODs through the created filters in IONDesk; they are directly sent to the inbox of the specified logical ID. This means that the BODs, regardless of the supplier rebatable flag, are still received in the Supplier Rebate inbox, and then saved to the corresponding SR tables. Purging a Supplier masterdata record with previous and existing transaction records no longer displays the Supplier Name in the related reports. The existing records, including purchase orders, receipts, agreements, accruals, claims, and debit notes, retains the Supplier Number.
Limitation	First, the set conditions in IONDesk are case-sensitive and they only filter-out the value No in pascal case. Values that are translated to other languages are not supported. Use the value 0 when languages other than English is preferred. Additionally, the filtering in IONDesk applies only for suppliers that are created after the data flow has been updated. Second, the SupplierPartyMaster BOD is published in a continuous two-minute interval. Multiple changes to a newly created record may publish multiple SupplierPartyMaster BODs. The earlier modifications may fall in a different interval, and get published earlier than the latter changes. All published SupplierPartyMaster BODs are validated against the filter conditions created in IONDesk. This means that it is possible that the first published BODs are routed to the Supplier Rebate inbox, while the latter BODs are filtered out since the User-defined field 4 - item (IDCFI4) is in the latter panels of Supplier. Open (CRS620). Because of this, it is recommended to use a Supplier template with a default User-defined field 4 - item (IDCFI4) value of No during Supplier masterdata creation.
KB Article	2194857

Description

Most customers have thousands of suppliers but only a few hundred have actual supplier rebate agreements. To limit the volume of data to process, there should be a way to identify these suppliers and restrict the SupplierPartyMaster BODs from coming in to ISR, and their related transactions.

As an enhancement, the Supplier master data, which are not eligible for supplier rebate agreements, are now filtered-out in IONDesk. M3 uses the field User-defined field 4 - item (IDCFI4) of Supplier. Open (CRS620) program to tag these suppliers. In the generated SupplierPartyMaster BOD, this is mapped to the element SupplierFreeField4 under UserArea. A value of 0 or No indicates that the supplier is non-rebatable, and do not get routed to Supplier Rebate inbox anymore. This attribute is also inherited to the purchase orders and receipts of the supplier upon publishing of the corresponding PurchaseOrder and ReceiveDelivery BODs. These transactions are also filtered-out in IONDesk given the same conditions.

You can now use the field User-defined field 4 - item (IDCFI4) in Supplier. Open (CRS620/F) to flag Supplier Rebate-eligible suppliers. If the field value is 0 or No, the supplier is non-rebatable. Any other value, including blank, indicates that the supplier is rebatable. This flagging is inherited in the subsequent purchase orders and receipts of the supplier, and it is also reflected in the BOD element SupplierFreeField4 in PurchaseOrder and ReceiveDelivery BODs.

In IONDesk, the newly created non-rebatable Supplier masterdata (SupplierPartyMaster BODs) and their purchase orders and receipts (PurchaseOrder and ReceiveDelivery BODs) are filtered out, and do not get routed to the Supplier Rebate inbox.

For the existing suppliers 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 supplier data in the Supplier Rebate application. A checkbox for Supplier is now available in the Purge Supplier Rebate Data form for this purpose. Then, the SupplierPartyMaster must rerun in Initial Load. Open (EVS006) using the BOD verb Sync. When you change the Supplier from non-rebatable to rebatable, you must also rerun PurchaseOrder and ReceiveDelivery, so previously filtered-out BODs are routed correctly. The BODs inherit the SupplierFreeField4 value from the Supplier at the time of publishing.

Note that BOD verb Show does not pass the BODs through the created filters in IONDesk; they are directly sent to the inbox of the specified logical ID. This means that the BODs, regardless of the supplier rebatable flag, are still received in the Supplier Rebate inbox, and then saved to the corresponding SR tables.

Purging a Supplier masterdata record with previous and existing transaction records no longer displays the Supplier Name in the related reports. The existing records, including purchase orders, receipts, agreements, accruals, claims, and debit notes, retains the Supplier Number.

Limitation

First, the set conditions in IONDesk are case-sensitive and they only filter-out the value No in pascal case. Values that are translated to other languages are not supported. Use the value 0 when languages other than English is preferred. Additionally, the filtering in IONDesk applies only for suppliers that are created after the data flow has been updated.

Second, the SupplierPartyMaster BOD is published in a continuous two-minute interval. Multiple changes to a newly created record may publish multiple SupplierPartyMaster BODs. The earlier modifications may fall in a different interval, and get published earlier than the latter changes. All published SupplierPartyMaster BODs are validated against the filter conditions created in IONDesk. This means that it is possible that the first published BODs are routed to the Supplier Rebate inbox, while the latter BODs are filtered out since the User-defined field 4 - item (IDCFI4) is in the latter panels of Supplier. Open (CRS620). Because of this, it is recommended to use a Supplier template with a default User-defined field 4 - item (IDCFI4) value of No during Supplier masterdata creation.

KB Article

2194857