Unified Key Mapping Service in SAP PI - Overview

8/16/2019 Unified Key Mapping Service in SAP PI - Overview

http://slidepdf.com/reader/full/unified-key-mapping-service-in-sap-pi-overview 1/10

SAP COMMUNITY NETWORK SDN - sdn.sap.com | BPX - bpx.sap.com | BOC - boc.sap.com

© 2008 SAP AG 1

Unified Key Mapping Service -Overview

Applies to:

SAP NetWeaver Process Integration 7.0 (SAP PI 7.0).

For more information, visit the Master Data Management homepage and SOA Management homepage.

Summary

This document gives guidance for Unified Key Mapping Service (UKMS) in SAP-PI. In certain mappingconditions we may have to translate master and transactional data during interface processing. It is useful inlandscapes where business processes are handled across various systems (SAP and non-SAP) and eachsystem has its own way of identifying the values.

Author: Ajay Wandre

Company: IBM

Created on: 12 October 2009

Author Bio

Ajay Wandre is a SAP NetWeaver – PI Consultant from IBM Global Business Services. He has written manyarticles relating to SAP-PI which has already been published in IBM Practitioners Portal and SAP DevelopersNetwork.

https://www.sdn.sap.com/irj/sdn/nw-mdm



https://www.sdn.sap.com/irj/sdn/soa-management







Unified Key Mapping Service - Overview


© 2008 SAP AG 2

Table of Contents

UKMS Key Concepts .......................................................................................................................................... 3

Implementing UKMS ........................................................................................................................................... 4

Portal Development ......................................................................................................................................... 4

UKMS TABLES ............................................................................................................................................... 5

UKM_CONTEXT .......................................................................................................................................................... 5

UKM_AGENCY ............................................................................................................................................................ 5

1UKM/KEY<MAIN_CONTEXT>0 ................................................................................................................................. 6

1UKM/MGP<MAIN_CONTEXT>0 ................................................................................................................................ 6

Mapping using UKMS ..................................................................................................................................... 7

Related Content .................................................................................................................................................. 9

Disclaimer and Liability Notice .......................................................................................................................... 10





© 2008 SAP AG 3

UKMS Key Concepts

UKMS supports only N:1 mapping. It doesn’t support 1:N mapping.

For a source system/object and target system/object combination, multiple values from the source can bemapped to the same value at the target.

Sourcesystem

SourceObject

Value Targetsystem

TargetObject

Value

SAPMM

Material 1 XYZ Material a

SAPMM


SAPMM


UKMS supports transitive relationship.

Source

system

Source

Object

Value Target

system

Target

Object

Value

SAPMM

MATERIAL 1 XYZ MATTYPE a

XYZ MATTYPE a ASD MATVAL 2

implies that-

Sourcesystem

SourceObject

Value Targetsystem

TargetObject

Value

SAP

MM

MATERIAL 1 ASD MATVAL 2





© 2008 SAP AG 4

Implementing UKMS

Portal Development

A portal needs to be developed for maintaining and managing system/object/value combinations in SAP.

Access to the UKMS should be limited to those users that have been given the appropriate authorization.Within the portal, there will need to be several roles that are set up in order to accommodate the varioususages of the UKMS:

ROLE DESCRIPTION

UKMS_READ_ONLYThis role will allow a user to look up keymappings in read-only mode

UKMS_UPDATE

This role will be used to add or updatemappings. This role will be restricted to onlymaintain mappings for existing schemes andexisting systems

UKMS_MAINTAIN

This role will be an administrator type rolewhich will allow the user, in addition tomaintaining mappings, to add contexts,schemes and systems when required.





© 2008 SAP AG 5

UKMS TABLES

Standard SAP UKMS as part of PI 7.0 has several UKMS tables which are used to store the key mappings.

UKM_CONTEXT

This is a standard SAP table delivered with UKMS. This table is used to hold information related to eachUKMS context. The field ‘MAIN_CONTEXT’ code is used as the <MAIN_CONTEXT> parameter in thedynamically generated tables which will be described below

UKM_AGENCY

This is a standard SAP table delivered with UKMS. This table is used to hold information related to thesystems in the landscape.





© 2008 SAP AG 6

/1UKM/KEY<MAIN_CONTEXT>0

This is a standard SAP table delivered with UKMS. This table is dynamically generated the first time a keymapping is created for a new Context. The value of <MAIN_CONTEXT> is taken directly from theUKM_CONTEXT table. (In the example below, the <MAIN_CONTEXT> value is ‘ISV1’.)

This table is used to hold all individual keys within a Context.

/1UKM/MGP<MAIN_CONTEXT>0

This is a standard SAP table delivered with UKMS. This table is dynamically generated the first time a keymapping is created for a new Context. The value of <MAIN_CONTEXT> is taken directly from theUKM_CONTEXT table. (In the example below, the <MAIN_CONTEXT> value is ‘ISV1’.)

This table is used to group similar keys together, thus creating key mappings between 2 or more keys.





© 2008 SAP AG 7

Mapping using UKMS

According to the requirements, certain custom tables need to be developed which would form the part of thevalidation framework of UKMS mapping.

Certain custom programs needs to be developed based on the specifications; referring various standard SAPUKMS function modules which are meant for adding, deleting and retrieving UKMS values.

Standard UKMS function modules-





© 2008 SAP AG 8

Create a user-defined function for UKMS specifying appropriate source system/scheme/value and targetsystem/scheme which would be used in graphical mapping for tracking the target value from the database.

In graphical mapping source scheme is passed as constant TRACTOR and source value is the source fieldTRACTOR_NUM; target scheme is constant TRACTOR.

The output of the UKMS user-defined function would be the target value derived from the database andpassed to the target field.





© 2008 SAP AG 9

Related Content

www.service.sap.com

www.help.sap.com

For more information, visit the Master Data Management homepage and SOA Management homepage.

http://www.service.sap.com/


http://www.help.sap.com/
















© 2008 SAP AG 10

Disclaimer and Liability Notice

This document may discuss sample coding or other information that does not include SAP official interfaces and therefore is notsupported by SAP. Changes made based on this information are not supported and can be overwritten during an upgrade.

SAP will not be held liable for any damages caused by using or misusing the information, code or methods suggested in this document,and anyone using these methods does so at his/her own risk.

SAP offers no guarantees and assumes no responsibility or liability of any type with respect to the content of this technical article orcode sample, including any liability resulting from incompatibility between the content within this document and the materials andservices offered by SAP. You agree that you will not hold, or seek to hold, SAP responsible or liable with respect to the content of thisdocument.

Unified Key Mapping Service in SAP PI - Overview

Documents

Transcript of Unified Key Mapping Service in SAP PI - Overview