Both must be activated if you want to use the duplicate check for both organizations/groups and for persons. ICM_RULESET contains two separate rule sets for these object types. Note: In SA17, the entry “BUT000, field PARTNER” covers both organizations/groups and persons. Rule set RULESET_PERS for the duplicate check of business partners (persons) RULESET_ORG for the duplicate check of business partners (organization and group) Run Transaction ICM_RULESET and activate corresponding rulesets Run Transaction SE18 and enter ADDRESS_SEARCHĭeactivate all active implementations first (marked yellow)Īctivate Implementation SIC_ADDR_DUPL_CHECK Push button ‘Application-Side Enablement (SA24)’įor integration of ICM duplicate check a standard BAdI implementation needs to be activated. Push button ‘Application-Side Enablement (SA17)’Īctivate Duplicate Check for GUI Transaction BP For a threshold value of 90 you can say a duplicate is found with of 90 percent of equal data. Higher treshold value leads to a more restrictive duplicate determination. This means duplicates are identified based on a threshold. Recommended threshold values are between 75 and 90. T001W – Plants/Branches (Plant addresses)īUT000 – BP: General data I (Business Partner) MOM052 – Workplace Addresses (used at Employee Business User) LFA1 – Supplier Master (General Section) -> not used is SAP S/4HANA (XKxx transactions are not available any more) KNVK – Customer/Vendor Master Contact Partner -> not used is SAP S/4HANA (XDxx and XKxx transactions are not available any more) KNA1 – General Data in Customer Master -> not used is SAP S/4HANA (XDxx transactions are not available any more) used at Contact Persons and Relationship dependent addresses which are synchronized into KNVK) Following meaning of available tables:īUT052 – Relationship Addresses (e.g. Run Transaction ICM_RULESET and navigate into ‘Global Settings’.ĭependent on available tables for duplicate check you have to set check on relevant tables active and define a threshold value. In Transaction ICM_RULESET check navigation to ‘Global Settings’ and ‘Maintain Display Fields’ if they are working well. After the check you can close the SE11 session. Repeat this step for all of the Views mentioned above. Create a new SAP GUI session and run Transaction SE11. To check if ICM Framework is available check mentioned in ‘PART 4 – test’ of SAP Note 2834389 – ICM: New infrastructure for duplicate check on SAP HANA should be executed.Īt least all shown Ruleset IDs and View Names should be available in status ‘inactive’.Īre active in ABAP dictionary. 43Ĭheck Prerequisits Check SAP_BASIS release If you want to use the rule set for the address-independent duplicate check, the following minimum versions are required: SAP HANA 2 SPS03 Rev. When a CP relationship or employee relationship is changedīelow SAP_BASIS 755 please consider SAP noteĢ834389 – ICM: New infrastructure for duplicate check on SAP HANA (implementation note)Īt least SAP HANA 2 Support Package Stack SPS02.The check is carried out only if an address was assigned. When a CP relationship (or an employee relationship) is created with a firm’s address.Duplicate check of the address data for relationships.When a business partner is created with address data.
Related SAP Notes will show necessary steps to downport this functionality to lower SAP Netweaver releases. With this infrastructure a duplicate check without 3rd party systems can be implemented. With SAP_BASIS release 755 a new infrastructure for ICM duplicate check based on HANA is provided. This duplicate check is using fuzzy search ICM (Information Consistency Management) based on address data index. For lower releases please consult SAP Note 2833993 and referenced SAP Notes. All settings will be relevant for newer releases as well. This blog post is created based on a SAP S/4HANA 2020 Release. This blog post is created based on SAP Note 2833993 – ICM: Steps for activation of duplicate check on SAP HANA – new infrastructure via transaction ICM_RULESETĮnriched with screenshotes and some guidance. To keep data clean and reduce duplicates in Business Partners at SAP S/4HANA, duplicate check in BP transaction will help to reduce duplicates. Data Cleansing on customer/verndor master data is one of the presteps in ECC on the way to S/4HANA.
0 kommentar(er)
