MDM 71 Vendor Content Information
Short Description
Download MDM 71 Vendor Content Information...
Description
SAP NetWeaver MDM Content
MDM 7.1 Vendor Content Applicable Releases: SAP NetWeaver MDM 7.1 SP3 (and newer) Topic Area: Information Management SAP Note 1318478 Capability: Master Data Management Summary: The MDM Vendor content can be used to consolidate and harmonize Vendors from SAP ERP systems. This document describes the different parts of the MDM Vendor content for the SAP NetWeaver MDM Release Version 7.1. Furthermore it contains some tips and tricks how to use the content as well as some links to additional information. Note The SAP MDM Vendor content supports the generic MDM scenarios Consolidation and Harmonization only. You cannot use this content for a central maintenance of Vendor data. If you want to do this, please contact SAP.
Version 1.06 October 2011
© Copyright 2011 SAP AG. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc. JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.
These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. These materials are provided “as is” without a warranty of any kind, either express or implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP shall not be liable for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use of these materials. SAP does not warrant the accuracy or completeness of the information, text, graphics, links or other items contained within these materials. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third party web pages nor provide any warranty whatsoever relating to third party web pages. SAP NetWeaver “How-to” Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting. Any software coding and/or code lines / strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent. Disclaimer Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components. Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.
Document History The following table highlights the changes in the document. Ensure to read chapter Change History thoroughly to obtain the complete information about content changes in the different release versions.
Document Version
Description
1.06
MDM 7.1 SP8 Patch 0 Refined Payment Methods, Recipient Types, Withholding Tax Codes and Withholding Tax Countries for Company Code Data (SAP Note 1619538)
1.05
MDM 7.1 SP7 Patch 0 Rebuilt the archive
1.04
MDM 7.1 SP6 Patch 0 Rebuilt the archive
1.03
MDM 7.1 SP5 Patch 0 Added Dunning Data support (SAP Note 1451228) Added Web Dynpro Configuration Updated the Performance Tuning chapter that is now a subchapter of the MDM Repository chapter
1.02
MDM 7.1 SP4 Patch 0 Added Company Code Data & Purchasing Organization support (SAP Notes 1403879, 1404964, and 1407978) Added Regional Structure File support for Addresses Added explanation of the port length issue in R/3 4.7 (SAP Note 1391292) Added Web information (e.g. Homepages, FTP) support for Communication Data Added some information about possible „Out of Memory“ issues during import Unified definition for flat and hierarchy lookup tables Resolved limitation for Instruction Key
1.01
MDM 7.1 SP3 Patch 1 Updated Validations & Main Table Banks Resolved limitation for EU Tax Numbers (SAP Note 1381987)
1.00
MDM 7.1 SP3 Patch 0 – first delivery of the new content
Icons Icon
Description Caution Note or Important Example Recommendation or Tip
Glossary Abbreviation
Description
BAPI
Business Application Programming Interface
BuPa
Business Partner
cMDM
Central Master Data Maintenance defines the required processes for the central creation of various types of master data in an interactive manner in MDM and the distribution of the data into a heterogeneous environment. It includes leveraging the results to perform enterprise-wide analytics (e.g. global spend analyses). The common process consists of the steps: -
create master data centrally in MDM distribute master data to remote systems to create new or update existing records in the systems distribute related key and/or grouping information to BW for analytics
cMDM requires usually the execution of the MDH scenario at least once to initialize the central MDM system with the already existing master data of the current environment. DBMS
Database Management System
EhP
Enhancement Package for SAP ERP remote systems
LT
Lookup Table is a MDM specific data structure
MDC
Master Data Consolidation defines the required processes for cleansing various types of master data in an interactive manner in particular within a heterogeneous environment. It includes for example leveraging the results to perform enterprise-wide analytics (e.g. global spend analyses). The common process consists of the steps: -
load master data - including its related reference data - into MDM enrich and cleanse master data in MDM distribute related key and/or grouping information to BW for analytics
MDC does not include the re-distribution of master data records into their original source systems. MDIS
Master Data Import Server
MDH
Master Data Harmonization defines the required processes for cleansing and distribution of various types of master data in an interactive manner in particular within a heterogeneous environment. It includes leveraging the results to perform enterprisewide analytics (like global spend analyses). The common process consists of the steps: -
load master data - including its related reference data - into MDM cleanse and enrich master data in MDM re-distribute master data back to the original source systems distribute related key and/or grouping information to BW for analytics
MDH means that you can only update already existing master data records in their original source systems. You can neither create new master data records in any source system based on the consolidated data nor create new records centrally in MDM. MDM
Master Data Management
MDS
Master Data Server
Abbreviation
Description
MDSS
Master Data Syndication Server
MT
Main Table is a MDM specific data structure
NW
NetWeaver
PI (XI)
Process Integration (eXchange Infrastucture)
QLT
Qualified Lookup Table is a MDM specific data structure
UI
User Interface
VAT
Value Added Tax is a tax that is added on to the value of a product when it is manufactured and is paid by the customer at the time of purchase
XML
eXtensible Markup Language is the file format used by the MDM standard repositories for data exchange with SAP remote systems
XSLT
eXtensible Stylesheet Language Transformations is used by the MDM PI content to transform XML messages both structurally and sometimes for the contained values
Table of Contents 1.
MDM Vendor Content ......................................................................................................1
2.
MDM Vendor Repository .................................................................................................3 2.1 2.2
2.3 2.4
2.5 2.6
3.
MDM Vendor PI Content ................................................................................................17 3.1 3.2 3.3
4.
MDM Repository Files...............................................................................................3 Repository Structure .................................................................................................3 2.2.1 Overview ......................................................................................................3 2.2.2 Main Table & Tuple Fields ............................................................................4 2.2.3 Lookup Tables ..............................................................................................4 Users and Roles .......................................................................................................5 Repository Values.....................................................................................................6 2.4.1 Validations....................................................................................................6 2.4.2 Matching Content .......................................................................................11 2.4.3 Workflows ................................................................................................... 11 Import and Syndication Content .............................................................................. 12 Performance Tuning ...............................................................................................13 2.6.1 Key Mapping ..............................................................................................13 2.6.2 Keyword and Sort Indices ...........................................................................14 2.6.3 Search Tabs ...............................................................................................15
Overview ................................................................................................................17 Download and Installation .......................................................................................17 Software Component Versions for Remote System Message Types ........................ 18 3.3.1 Business Scenario: MDM710_Inbound ....................................................... 19 3.3.2 Business Scenario: MDM710_Outbound ..................................................... 20
Web Dynpro Configuration ........................................................................................... 22 4.1
4.2
Deliverables ............................................................................................................22 4.1.1 Search ........................................................................................................22 4.1.2 Result Set ...................................................................................................22 4.1.3 Item Details ................................................................................................22 Usage .....................................................................................................................22
5.
Sample Data...................................................................................................................23
6.
Import of Reference Data ..............................................................................................24 6.1 6.2 6.3 6.4
7.
Banks .....................................................................................................................24 Lookup Hierarchy Tables ........................................................................................25 Unique Constraints .................................................................................................25 Import Sequence ....................................................................................................26
Import of Master Data ....................................................................................................29 7.1 7.2 7.3 7.4 7.5
Message Flow ........................................................................................................29 Interface (XSLT) Mappings .....................................................................................29 Field Mappings .......................................................................................................29 Value Mappings ......................................................................................................31 Import of Lookup Main Relationships....................................................................... 31
7.6 7.7 8.
Syndication of Master Data ...........................................................................................35 8.1 8.2 8.3 8.4
8.5 8.6 8.7 9.
Message Flow ........................................................................................................35 Interface (XSLT) Mappings .....................................................................................35 Field Mappings .......................................................................................................36 8.3.1 Bank Details & Bank Master .......................................................................37 Predefined Field Values for CREMDM04................................................................. 37 8.4.1 Begin & Segment Attributes ........................................................................37 8.4.2 Message Function Element.........................................................................37 8.4.3 Specific Address Values ............................................................................. 38 Predefined Field Values for GenericVendor............................................................. 38 Completion of the delivered Map Templates............................................................ 38 MDSS usage ..........................................................................................................40
Known Issues and Limitations......................................................................................41 9.1
9.2
9.3
10.
7.5.1 Bank Details ...............................................................................................31 7.5.2 Main Table Vendors....................................................................................32 Import of Tuples ......................................................................................................32 MDIS usage ............................................................................................................34
Data Modeling ........................................................................................................41 9.1.1 Comparison to the CREMDM IDoc.............................................................. 41 9.1.2 Communication Comments .........................................................................41 9.1.3 International Address Versions ................................................................... 41 9.1.4 Payment Transactions ................................................................................41 9.1.5 Time Dependency.......................................................................................41 9.1.6 Schema Transport & Validation Groups ......................................................41 Data Distribution .....................................................................................................42 9.2.1 Import/Syndication from/to CRM and SRM .................................................. 42 9.2.2 Import into Tuples .......................................................................................42 9.2.3 “Out of Memory” issues during Import ......................................................... 42 9.2.4 MDM PI Adapter Usage ..............................................................................42 Data Processing .....................................................................................................43 9.3.1 Merge of Records with Lookup Main Relationships ..................................... 43 9.3.2 Portal Maintenance for Main Table Banks ................................................... 43 9.3.3 Hierarchy table Validations ......................................................................... 43 9.3.4 Central Master Data Maintenance ............................................................... 43
Change History ..............................................................................................................45 10.1 MDM 7.1 .................................................................................................................45
11.
Related Information .......................................................................................................50
12.
MDM 7.1 vs. MDM 5.5 Vendor........................................................................................51 12.1 12.2 12.3 12.4
13.
New Content in MDM 7.1 Vendor ............................................................................51 Changed Content in MDM 7.1 Vendor .....................................................................56 Removed Content in MDM 7.1 Vendor ....................................................................59 Migration from MDM 5.5 to MDM 7.1 Vendor...........................................................60
SAP ERP Vendors ......................................................................................................... 61
13.1 13.2 13.3 13.4 13.5 13.6 13.7 13.8
Administrative Data .................................................................................................61 General Data: Address............................................................................................63 General Data: Control .............................................................................................67 General Data: Payment Transactions ......................................................................68 Company Code Data: Accounting Information ......................................................... 70 Company Code Data: Payment Transactions .......................................................... 71 Company Code Data: Correspondence Accounting ................................................. 72 Purchasing Organization Data.................................................................................74
MDM 7.1 Vendor Content
1.
MDM Vendor Content
MDM Content is used as a synonym for “content for SAP NetWeaver MDM Server”. MDM content shipped by SAP covers all MDM related development artifacts (like repository definition, workflows, mappings, and so on) that are specific for a master data object type (like Vendor or Material). MDM content does neither include MDM core nor generic MDM service deliverables. MDM content is not only related to MDM software components. It also covers client system connectivity, in example everything that is needed for connecting SAP remote systems to a MDM server in order to send or receive data from or to MDM. The MDM Vendor content consists of: SAP Note 1318478 MDM 7.1 Vendor Content (current document) Content Strings – an Excel file containing all field and table strings translated into all supported languages Field Mapping and Check Tables – an Excel file showing the fields of the repository and how they relate to the supported SAP remote systems MDM Vendor Match and Merge – a how-to guide in PDF format explaining the Vendor’s Matching content using the Sample Data. The guide is usable for demo purposes, too. MDM Vendor repository MDM Vendor specific PI content MDM Vendor specific Portal content MDM Vendor specific Web Dynpro Configuration MDM Vendor specific content for the remote system extractors MDMGX and MDM_CLNT_EXTR Sample Data Important The Vendor content as described in this document is useable for MDM version 7.1 SP 3 and newer. If you want to use the Vendor content with a lower SP of MDM 7.1, it is strongly recommended to upgrade your MDM landscape to the latest MDM 7.1 SP first. The Vendor content for MDM 5.5 is described in SAP Note 1252883. You can download the content from SAP Software Distribution Center. The business content of MDM 7.1 is either part of the full MDM delivery (in case of support packages with patch level 0) or part of the MDM component delivery (in case of a patch for a support package). To download the business content as part of the full MDM delivery, choose in the menu on the left side “Download Installations and Upgrades Entry by Application Group”. Then continue on the main web page “SAP NetWeaver SAP MDM SAP NETWEAVER MDM 7.1”. Note The business content is part of the full MDM delivery. You have to unzip this package and then navigate to the specific Vendor content within the “MDM\Business_Content” folder.
October 2011
1
MDM 7.1 Vendor Content
To download the business content as part of the MDM Component delivery, choose in the menu on the left side “Download Support Packages and Patches Entry by Application Group”. Then SAP MDM SAP MDM 7.1 Master Data continue on the main web page “SAP NetWeaver Server MDM Business Content 7.1”. Note The business content package contains the complete content for all pre-delivered SAP objects. You have to unzip this package and use the specific Vendor content.
October 2011
2
MDM 7.1 Vendor Content
2.
MDM Vendor Repository
The repository is the SAP NetWeaver MDM specific part of the complete MDM Vendor content. It consists of: The MDM repository file (*.a2a) Predefined repository structures (tables, fields) Predefined users and roles Predefined validations, matching strategies and workflows Predefined import and syndication content Note The Vendor repository is release dependant. You can use the repository only with its related MDM release. If you apply an older version of a repository to a new MDM release, you have to update the repository first. Refer to chapter Change History to get an overview about all changes of the Vendor content in the different MDM releases. You cannot use a repository that was built with a newer MDM release on an older MDM release.
2.1
MDM Repository Files
The Vendor repository is part of the downloadable MDM content. The current version is: “MDM71800_VENDOR.a2a” for MDM 7.1 SP6 Patch 0 If you require other versions of the repository, please contact SAP.
2.2 2.2.1
Repository Structure Overview
The repository has been built following the maximize approach: it intends to cover all fields of the supported views that are available for Vendor creation in SAP ERP (see chapter SAP ERP Vendors and/or the attached excel file Field Mapping and Check Tables Vendor.xls for details). Nevertheless the repository structure is considered as a template. You can modify the structure (e.g. add specific fields, deleted not required tables, and so on) so that the final repository fits exactly to your specific requirements. Important All tables and fields in the repository have been defined to support the Harmonization scenario. In this case it is important that an IDoc segment is completely covered by the related MDM data model as SAP ERP remote systems interpret missing and/or empty IDoc elements as a deletion of existing values! Example The ERP Vendor and the Vendor repository include four name fields. If you’d delete two of them in the MDM repository, you might delete data during distribution. You would send four names to MDM, but MDM is only capable to handle two. If you send the same record back to ERP, the IDoc would contain only two names. Those would be stored by ERP in the Vendor data; the missing names would be deleted!
October 2011
3
MDM 7.1 Vendor Content
2.2.2
Main Table & Tuple Fields
This chapter describes only special data modeling and settings of the repository.
Main Table Vendors Main table Vendors contains a field Instruction Key. This field as modeled as a text field in MDM although it relates to a customizing table in SAP ERP systems. Unfortunately the CREMDM IDoc does not contain enough information to create the correct customizing key so that modeling the field as a lookup field is not possible in MDM.
Tuple Company Code Data Tuple Company Code Data contains a field Payment Method. This is a multi-valued lookup field to the hierarchy table Payment Methods. In ERP payment methods are related to the country of the current company code. Since this information is not known in the MDM repository, the payment methods depend on the company code directly. During maintenance the selection is automatically reduced. Still you can select one or more payment methods.
Tuple Web Tuple Web reflects the SAP ERP FTP and URL addresses that are part of the communication data. In SAP ERP web addresses may have only 132 characters if they are maintained in the UI. Longer addresses (up to 2048 characters) can be added using a BAPI. The Web tuple consists of several URI fields. Field URI is related to the 132 character screen field in ERP. Fields URI (Part 1 to 9) reflect the 2048 characters URI. The long URI is separated in the MDM repository as this structure is the same as in the CREMDM IDoc.
2.2.3
Lookup Tables
All lookup tables of the repository follow a specific modeling approach. All display fields of the lookup tables are defined with the Sort Index property Normal to speed up the record matching during the import of data into the tables. Flat lookup tables usually consist of a Name and a Code field. The name field reflects the related customizing text field (not all customizing tables have texts). It can be multilingual according to its source. The code field is a clone of the remote key – the value used in the CREMDM IDoc. It is set as a unique field to ensure a high quality of your lookup table data. Note Lookup table Languages does not use the unique constraint for its Code field. The reason is that the unique checks are not case sensitive. Instead the ISO Code field of a language is used. Hierarchy lookup tables use the same modeling approach. As a hierarchy consists of two or more code fields, related fields are added to the hierarchy table as lookup fields. Example A region usually consists of a region code and a related country. In the MDM repository, the country is added as an additional flat lookup field in the Region hierarchy lookup table. The unique constraint for hierarchy lookup tables consists of all hierarchy code fields.
October 2011
4
MDM 7.1 Vendor Content
Note Lookup table House Banks uses different fields. Instead of the Name field it contains a field Bank Key. This is a concatenation of the House Bank ID and its Bank Number. Additionally the Bank Country is part of the hierarchy table.
2.3
Users and Roles
The repository contains some predefined users and roles. Both are used for the user mapping of the generic Portal content. Nevertheless the users and roles are templates that you can adjust according to your needs. CAUTION Please do not change the user & role sapsupport. Both are used to guarantee an easy, read-only access for SAP Support to your repository in case of errors. The table below lists the predefined users and roles:
Role Name
Role Description
Assigned User
Admin
This is the standard administrative role in MDM providing full access to all SAP MDM and repository functions.
Admin
Business Expert
This role provides read-only access to the MDM data and its distribution functions.
User
Default
This is a standard role in MDM but not used by MDM content.
Not used
Distributor
This role provides access to the distribution functions (import and syndication) only.
Distributor
Master Data Expert
This role provides full access to the MDM data and its distribution functions.
Expert
Sapsupport
This is a read only role used by SAP support.
sapsupport
Important MDM 7.1 delivers all users with predefined passwords. Each user has the same password sapmdm assigned. The user detail setting User must change password is set to No. It is recommended that you change these settings (except for user sapsupport) according to your needs. If you change the password for user sapsupport, too, ensure to mention the new password in the secure area of OSS messages.
October 2011
5
MDM 7.1 Vendor Content
2.4 2.4.1
Repository Values Validations
You can use MDM Data Manager to have a look at the predefined validations. Validations are visible for their related main table and/or tuple only. Ensure to select the correct main table and/or tuple. Tip Each predefined validation has to be executed manually in MDM Data Manager. If you want to automate the execution, set the validation property Automatic Execution either to Error or to Warning. This activates the validation checks when saving one or more records. Note The major part of validations within a SAP ERP remote system is actually system customizing. Validations in the repository do not guarantee that they exactly fit to your remote system. The predefined validations use the settings of the latest SAP ERP release. Nevertheless it might be possible that your SAP ERP remote system uses different settings, e.g. for mandatory fields. Adjust the validations in the MDM repository according to your needs.
ERP Mandatory Fields (Validation Group) This validation group consists of several single mandatory field checks. It checks all MDM repository fields for values that are marked as mandatory in a common SAP ERP remote system. Checks are performed for the fields: Table / Tuple
Fields
Vendors
Vendor Number, Account Group, Language, Name 1, Search Term 1, Country
Bank Details
Bank, Bank Account Number
Company Code Data
Company Code
Dunning Data
Dunning Procedure
E-Mail Addresses
Is Standard E-Mail Address, Sequence Number
EU Tax Numbers
Country
Fax Numbers
Is Standard Fax Number, Fax Country, Sequence Number
Phone Numbers
Is Standard Number, Phone Country, Phone Number Type, Sequence Number
Purchasing Organization Data
Order Currency
Web
Is Standard URI, URI Type, Sequence Number Tip This example shows how validation groups can be used. Anyways you can create a single validation that checks for all mandatory fields in one run, too.
October 2011
6
MDM 7.1 Vendor Content
MDM Execute All Validations (Validation Group) This validation group simply collects all existing validations of the repository. This allows the execution of all validations in a single action.
MDM Hierarchy Lookup Consistency (Validation Group) This validation group consists of several single consistency checks for hierarchy lookup tables. It checks all MDM repository hierarchy fields for their related lookup values to ensure the consistency of the hierarchies. Example A region usually consists of a region code and a related country. In the MDM repository, the country is added as an additional flat lookup field in the Region hierarchy lookup table. Nevertheless the actual Country and Region are independent fields of the main table. The validation checks if the actual country and the region’s country are identical. Checks are performed for the fields: Table / Tuple
Fields
Vendors
Region, Region for PO Box, Regional Structure Additional City, Regional Structure City, Regional Structure District, Regional Structure PO Box City, Regional Structure Street, Transportation Zone
Company Code Data
Accounting Clerk, House Bank, Payment Methods, Recipient Types, Reconciliation Account, Tolerance Groups, Withholding Tax Codes, Withholding Tax Countries
MDM Calculate Full Address This validation is used as a function for the calculated field Full Address in the Vendors main table: IF(IS_NOT_NULL(Street),Street&” “) & IF(IS_NOT_NULL(House Number),House Number&”, “) & IF(IS_NOT_NULL(City Postal Code),City Postal Code&” “) & IF(IS_NOT_NULL(City),City&”, “) & IF(IS_NOT_NULL(Country.Name),Country.Name&”, “) & IF(IS_NOT_NULL(Region.Name),Region.Name)
MDM Calculate Full Bank Address This validation is used as a function for the calculated field Bank Address in the Banks main table: IF(IS_NOT_NULL(Street),Street&” “) & IF(IS_NOT_NULL(City),City&”, “) & IF(IS_NOT_NULL(Bank Country.Name),Bank Country.Name)
October 2011
7
MDM 7.1 Vendor Content
MDM Calculate Full Name This validation is used as a function for the calculated field Full Name in the Vendors main table: IF(IS_NOT_NULL(Title.Name),Title.Name&” “) & IF(IS_NOT_NULL(Name 1),Name 1&” “) & IF(IS_NOT_NULL(Name 2),Name 2&” “) & IF(IS_NOT_NULL(Name 3),Name 3&” “) & IF(IS_NOT_NULL(Name 4),Name 4)
MDM Check Bank Master Mandatory Fields This validation is used to check the Banks main table for mandatory fields. IS_NOT_NULL(Bank Country.[Record], Bank Name, Bank Key)
MDM Check Company Code Numeric Fields The MDM data types differ from the SAP ERP data types. Some ERP data types (like NUMC, numeric characters) are not known in MDM. Those fields are usually using the text type in MDM. This validation is used to check if affected Company Code Data tuple fields use numbers only: Check Cashing Time, Personnel Number HAS_ALL_CHARS(Check Cashing Time, “0” , “9”) AND HAS_ALL_CHARS(Personnel Number, “0” , “9”)
MDM Check Company Code Payment Advice This validation is used to check the Company Code Data tuple for the Payment Advice fields. You can either send Payment Advices by EDI or XML only. IS_NOT_NULL(Payment Advice by XML.[Record], Send Payment Advices by EDI?.[Record])
MDM Check Delivery Service This validation is used to check the Vendors main table fields Delivery Service Number and Delivery Service Type. If a delivery service is maintained, SAP ERP requires values for both fields. IF(IS_NOT_NULL(Delivery Service Number) OR IS_NOT_NULL(Delivery Service Type.[Record]), IS_NOT_NULL(Delivery Service Number) AND IS_NOT_NULL(Delivery Service Type.[Record]))
MDM Check Dunning Data Numeric Fields The MDM data types differ from the SAP ERP data types. Some ERP data types (like NUMC, numeric characters) are not known in MDM. Those fields are usually using the text type in MDM. This validation is used to check if affected Dunning Data tuple fields use numbers only: Dunning Level HAS_ALL_CHARS(Dunning Level, “0” , “9”)
MDM Check E-Mail Address Format This validation is used to check if the E-Mail Addresses tuple field E-Mail Address has the correct format. It checks if the string contains at least a “@” and “.” character. FIND(E-Mail Address, ”@“) AND FIND(E-Mail Address, ”.“)
October 2011
8
MDM 7.1 Vendor Content
MDM Check E-Mail Address Sequence Number This validation is used to check if the E-Mail Addresses tuple field Sequence Number has the correct format. It checks if the string consists of exactly three digits. HAS_ALL_CHARS(Sequence Number, ”0“ , ”9“) AND LEN(Sequence Number) = 3
MDM Check Fax Number Sequence Number This validation is used to check if the Fax Number tuple field Sequence Number has the correct format. It checks if the string consists of exactly three digits. HAS_ALL_CHARS(Sequence Number, ”0“ , ”9“) AND LEN(Sequence Number) = 3
MDM Check Phone Number Sequence Number This validation is used to check if the Phone Number tuple field Sequence Number has the correct format. It checks if the string consists of exactly three digits. HAS_ALL_CHARS(Sequence Number, ”0“ , ”9“) AND LEN(Sequence Number) = 3
MDM Check PO Box vs. Company Postal Code This validation is used to check the Vendors main table fields PO Box Postal Code and Company Postal Code. SAP ERP allows the maintenance of either a PO Box Postal Code or a Company Postal Code only. IS_NOT_NULL(PO Box Postal Code, Company Postal Code)
MDM Check PO Box vs. Delivery Service This validation is used to check the Vendors main table fields PO Box, Delivery Service Number and Delivery Service Type. SAP ERP allows the maintenance of either a PO Box or a Delivery Service only. IS_NOT_NULL(PO Box) AND (IS_NOT_NULL(Delivery Service Number) OR IS_NOT_NULL(Delivery Service Type.[Record]))
MDM Check PO Box vs. PO Box w/o Number This validation is used to check the Vendors main table fields PO Box and PO Box without Number. If the flag PO Box without Number is set, the PO Box must not have a value. IS_NOT_NULL(PO Box) AND PO Box without Number = ‘X’
MDM Check Purchasing Organization Incoterms This validation is used to check the Purchasing Organizations tuple fields Incoterms (Part 1) and Incoterms (Part 2). If an Incoterm is maintained, SAP ERP requires values for both fields. IF(IS_NOT_NULL(Incoterms (Part 1).[Record]) OR IS_NOT_NULL(Incoterms (Part 2)), IS_NOT_NULL(Incoterms (Part 1).[Record]) AND IS_NOT_NULL(Incoterms (Part 2)))
MDM Check Purchasing Organization Numeric Fields The MDM data types differ from the SAP ERP data types. Some ERP data types (like NUMC, numeric characters) are not known in MDM. Those fields are usually using the text type in MDM. This validation is used to check if affected Purchasing Organization Data tuple fields use numbers only: Planned Delivery Time in Days, Staging Time in Days
October 2011
9
MDM 7.1 Vendor Content
HAS_ALL_CHARS(Planned Delivery Time in Days, “0” , “9”) AND HAS_ALL_CHARS(Staging Time in Days, “0” , “9”)
MDM Check Purchasing Organization Transportation Chain and Staging Time This validation is used to check the Purchasing Organizations tuple fields Transportation Chain and Staging Time in Days. If one of the fields is maintained, SAP ERP requires values for both fields. IF(IS_NOT_NULL(Transportation Chain.[Record]) OR IS_NOT_NULL(Staging Time in Days), IS_NOT_NULL(Transportation Chain.[Record]) AND IS_NOT_NULL(Staging Time in Days))
MDM Check Purchasing Organization Vendor Service Level This validation is used to check the Purchasing Organizations tuple field Vendor Service Level. The field is a decimal field in SAP ERP having one decimal place. The value format must be ., e.g. 100.0 or 44.8. The validation checks first if the characters up to the dot are numeric. The dot itself must be placed at the penultimate position of the value. The last character must be again numeric. HAS_ALL_CHARS(LEFT(Vendor Service Level, FIND(Vendor Service Level, “.”) – 1), “0”, “9”) AND FIND(Vendor Service Level, “.”) = LEN(Vendor Service Level) – 1 AND HAS_ALL_CHARS(RIGHT(Vendor Service Level, 1), “0”, “9”)
MDM Check Vendor Numeric Fields The MDM data types differ from the SAP ERP data types. Some ERP data types (like NUMC, numeric characters) are not known in MDM. Those fields are usually using the text type in MDM. This validation is used to check if affected Vendors main table fields use numbers only: Int. Location Number 1, Int. Location Number 2, Check Digit HAS_ALL_CHARS(Int. Location No. 1, “0” , “9”) AND HAS_ALL_CHARS(Int. Location No. 2, “0” , “9”) AND HAS_ALL_CHARS(Check Digit, “0” , “9”)
MDM Check Web Sequence Number This validation is used to check if the Web tuple field Sequence Number has the correct format. It checks if the string consists of exactly three digits. HAS_ALL_CHARS(Sequence Number, ”0“ , ”9“) AND LEN(Sequence Number) = 3
MDM Check Web URI This validation is used to check if the Web tuple field URI has the same characters as the field URI (Part 1). It checks the first 132 characters. IF(IS_NOT_NULL(URI) OR IS_NOT_NULL(URI (Part 1)) IS_NOT_NULL(URI) AND IS_NOT_NULL(URI (Part 1)) AND URI = LEFT(URI (Part 1), 132))
MDM Sample Check Mandatory Field Check if the field Vendors main table field Vendor Number has a value: IS_NOT_NULL(Vendor Number)
October 2011
10
MDM 7.1 Vendor Content
Tip This validation shows how-to create validations for mandatory checks. Use it as a template for your own fields.
MDM Sample Check VAT Registration Number This validation is used to check the format of the VAT Registration Number in the Vendors main table. First the country of the current record is identified. Depending on the country, the related specific VAT check is executed. IF(Country.Code = “DE”, MDM Sample Check German VAT, IF(Country.Code = “FR”, MDM Sample Check French VAT)) MDM Sample Check French VAT This validation is used to check the format of a French VAT Registration Number in the Vendors main table. The number must be exactly 13 characters long, start with the French Country Code and must not contain any blanks. LEFT(VAT Registration Number, 2) = “FR” AND LEN(VAT Registration Number) = 13 AND FIND(VAT Registration Number, “ ”) = 0 MDM Sample Check German VAT This validation is used to check the format of a German VAT Registration Number in the Vendors main table. The number must be exactly 11 characters long, start with the German Country Code and must not contain any blanks. LEFT(VAT Registration Number, 2) = “DE” AND LEN(VAT Registration Number) = 11 AND FIND(VAT Registration Number, “ ”) = 0
2.4.2
Matching Content
Matching content consists of transformations, rules and strategies. The Vendor repository contains several transformations, rules and a single matching strategy: Transformations for Company and Full Names, Addresses and Search Terms Rules for Full Names, Addresses, Search Terms and the VAT Registration Number Full Vendor Matching strategy Note The predefined matching content is a template only. It is created in relation to the Vendor Sample Data. Use these templates for creating your own, more specific matching content. Refer to the Vendor: Match and Merge how-to guide that is attached to this note for more details.
2.4.3
Workflows
MDM Full Vendor Matching
This sample workflow can be started manually in Data Manager. The workflow performs a check out of the records and runs through the predefined Full Vendor Matching strategy using Records vs.
October 2011
11
MDM 7.1 Vendor Content
Records as Match Records Scope. It requires manual interaction to merge the records. Finally the workflow checks in the records.
MDM Mandatory Fields Validation
This sample workflow can be started directly with an Import Map or manually in Data Manager. The workflow performs a checkout of the records and runs through the all validations of the group ERP Mandatory Fields. It indicates records that do not have all mandatory fields maintained. Before those can be checked in, the user has to correct the issues. Note The predefined import map for Vendor import does not launch the workflow automatically. You have to change the import map first using the Import Manager. After loading the map, choose Configuration Options in the top menu. Change property Checkout/Workflow and select the workflow you want to start automatically after a data import.
MDM Syndication
This is a sample workflow usable to distribute records with the Data Manager. By adding records manually to this workflow and executing it, you trigger the syndication via a configured port. Ensure that MDSS is running for a successful distribution.
2.5
Import and Syndication Content
Import and syndication content consists of: Remote System templates within the repository for SAP BI and SAP ERP. XML Schemas usable for data import and syndication. The XSD files are delivered additionally as a part of the downloadable content, too. GenericVendor describes the message structure for sending generic Vendor records to SAP BI. “ReferenceData R/3 & ERP describes the message structure for importing reference data being extracted with MDMGX from a SAP R/3 or ERP system. “CREMDM04 describes the message structure for importing MDM Vendor records being extracted with MDM_CLNT_EXTR from a SAP remote system respectively for sending MDM Vendor records to a SAP remote system. The structure itself is synchronized with the related SAP ERP IDoc. Import and Syndication maps to ensure the import of reference and master data respectively the distribution of master data. The import and syndication maps are delivered additionally as a part of the downloadable content, too. Import and Syndication ports for automated import and distribution using MDIS respectively MDSS.
October 2011
12
MDM 7.1 Vendor Content
2.6
Performance Tuning
There are a few settings in MDM Console in regard to the data model that have impacts on the repository’s performance (e.g. loading time, syndication, and so on).
2.6.1
Key Mapping
The current repository uses key mapping for the main and the lookup tables. During data distribution (import and/or syndication) the messages that are sent to MDM or sent by MDM to a remote system usually contain a lot of codes instead of texts. Especially for lookup tables key mapping is used to ensure that the correct code is used for the same value.
October 2011
13
MDM 7.1 Vendor Content
Example Your system landscape consists of two remote systems. In remote system A the country Germany has a code GER; in remote system B the same country has code DE. During the import of reference data you create a single record for country Germany with two remote keys (GER for remote system A and DE for remote system B). This ensures that during the import of master data the code that is used in the message is mapped to the correct lookup value. Key mapping itself has some impacts on the loading of the repository and the syndication. It takes more time to create additional indices for key mapping. The distribution of key mapping is slower than the distribution of lookup values. If you are sure that your reference data is 100% identical in your remote systems (following the example above: each of your remote system uses DE as code for country Germany) you could think about including the key mapping codes as single fields of the lookup table and disable the Key Mapping option of the table in MDM Console. Note The predefined import and syndication maps are built using the key mapping on lookup tables. If you change the settings in MDM Console, you have to redefine the maps accordingly.
2.6.2
Keyword and Sort Indices
Each field of a MDM repository can be added to the keyword and/or sort index. The keyword index enables the keyword search for this specific field. The sort index enables sorting all repository records upon the field (refer to the MDM Console Reference Guide for details). Both settings can be done when defining a field in the Field Detail pane in MDM Console. Creating keyword and sort indices require a specific amount of time during the repository load. The table lists all fields with enabled properties for the Vendor repository:
Table / Tuple
Field
Vendors
ID
X
Vendor Number
X
X
Full Name
X
X
Search Term 1
X
X
Search Term 2
X
X
Full Address
X
X
City
X
City Postal Code
X
PO Box
X
PO Box Postal Code
X
VAT Registration Number
X
Bank Key
X
X
Bank Name
X
X
Banks
October 2011
Sort
Keyword
14
MDM 7.1 Vendor Content
Table / Tuple
Field Bank Address
Bank Details
Sort
Keyword
X
X
Bank Bank Account Number
X X
Account Holder Company Code Data
Dunning Data
X
Company Code
X
X
Payment Terms
X
X
Dunning Area
X
Dunning Procedure
X
E-Mail Addresses
E-Mail Address
Purchasing Organization Data
ABC Classification
X
Payment Term
X
X
Purchasing Organization
X
X
Web
URI
X
X
As the fields listed above are only a proposal, you should check if you require more or less fields for keyword search and/or sorting. Recommendation If a field has the type Lookup [flat], it is not necessary to activate the sort index on this field as lookups are prepared for sorting by MDM anyways. If you want to use a specific field within a matching rule, you have to set the Sort Index to Normal.
2.6.3
Search Tabs
Search Tabs are defined on field level. They are useable for lookup (flat & hierarchy) fields only. The property activates the Search Tab in the Search Parameters pane of MDM Data Manager. The following list shows all fields having an activated Search Tab:
Table / Tuple
Fields
Vendors
Account Group, Central Posting Block, Central Purchasing Block, Central Deletion Flag, Country, Gender, Industry Sector, Forwarding Agent Freight Group, Language, Natural Person, PO Box Country, Region, Region for PO Box, Tax Number Type, Tax Type, Title, Transportation Zone
Banks
Bank Country
Company Code Data
Company Code
Dunning Data
Dunning Area, Dunning Procedure
Phone Numbers
Phone Number Type
Purchasing Organization Data
Purchasing Organization
October 2011
15
MDM 7.1 Vendor Content
Table / Tuple
Fields
Web
URI Type
As the fields listed above are only a proposal, you should check if you require more or less fields using the Search Tab in MDM Data Manager.
October 2011
16
MDM 7.1 Vendor Content
3. 3.1
MDM Vendor PI Content Overview
The PI content for MDM delivers interfaces, interface mappings and communication channel templates tailored to the supported SAP remote system and the shipped MDM repositories. In addition it delivers integration scenarios that reduce the manual effort required to define the communication between MDM and the SAP remote systems. The “Software Component Versions for Remote System Message Types” section lists the additional software component versions needed in PI to process IDoc and/or XML Proxy messages from SAP remote systems. The “Business Scenario” sections list the interfaces, interface mappings and communication channel templates contained in the PI content for MDM to transform the message from remote system format to the expected MDM XML format and vice versa. The following MDM PI Content versions are available: Namespace:
http://sap.com/xi/MDEApplicationContent
Software Component Versions:
MDM BUSINESS CONTENT 7.1
3.2
(usable for MDM 7.1 with SAP PI 7.0 and 7.1 (NetWeaver 7.0 and 7.1))
Download and Installation
You can download the MDM PI Content from SAP Software Distribution Center. MDM 7.1 PI content is either part of the full MDM delivery (in case of support packages with patch level 0) or part of the MDM component delivery (in case of a patch for a support package). To download the PI Content as part of the full MDM delivery, choose in the menu on the left “Download Installations and Upgrades Group”. Then continue on the main web page “SAP NetWeaver SAP MDM SAP NETWEAVER MDM 7.1”.
Entry by Application
Note The PI Content is part of the full MDM delivery. You have to unzip this package and then navigate to the specific PI content within the “MDM\XI_Content” folder. To download the PI Content as part of the MDM component delivery, choose in the menu on the left “Download Support Packages and Patches by Application Group”. Then continue on the main web page “SAP NetWeaver SAP MDM SAP NETWEAVER MDM 7.1”.
Entry
Deploy the MDM PI Content (TPZ file) into the PI repository. For PI 7.0 use the Integration Repository tool. For more information see Importing Process Integration Content on the SAP Help Portal. For PI 7.1 use the Enterprise Services Builder tool (ESR). For more information see Importing ESR Content on the SAP Help Portal. October 2011
17
MDM 7.1 Vendor Content
3.3
Software Component Versions for Remote System Message Types
SAP remote system
IDoc (sent to MDM)
IDoc (received from MDM)
CREMDM
CREMAS
ADRMAS
R/3 Enterprise 4.7
PI 2004_1_470
SAP APPL 4.7
SAP ABA 6.20
ERP 2004 / ECC 5.0
PI 2004_1_500
SAP APPL 5.0
SAP BASIS 6.40
ERP 2005 / ECC 6.0
SAP APPL 6.0
SAP APPL 6.0
SAP BASIS 7.00
+ EhP 2
SAP APPL 6.02
SAP APPL 6.02
SAP BASIS 7.00
+ EhP 3
SAP APPL 6.03
SAP APPL 6.03
SAP BASIS 7.00
+ EhP 4
SAP APPL 6.04
SAP APPL 6.04
SAP BASIS 7.01
+ EhP 5
SAP APPL 6.05
SAP APPL 6.05
SAP BASIS 7.02
SAP remote system
Proxy XML structures (sent to MDM)
Proxy XML structures (received from MDM)
GenericVendorOut
GenericVendorIn
BI CONT 7.03
BI CONT 7.03
1
NW 2004s BI
If the required message type is not available in your PI Content of the software component version, you have to: Either download and install the latest version of the PI Content for the corresponding software component from Service Market Place. Or import the IDoc or XML Proxies manually.
1
Extension Set 1.10 or 2.00
October 2011
18
MDM 7.1 Vendor Content
3.3.1
Business Scenario: MDM710_Inbound
MDM 7.1 Inbound Processing – SAP remote system sending data to MDM server MDS Receives Data
MDM 7.1
Sender Communication Channel Template [none] Systems based on NW2004 MDC
Outbound Interface
Interface Mapping
Inbound Interface
Sends Data
Receiver Communication Channel Template
R/3 47x110
CREMDM.CREMDM04
Cremdm04_470AddressFilterIn
CREMDM.CREMDM04
FTP_CREMDM_MDMIn
PI 2004_1_470
MDM BUSINESS CONTENT 7.1 (7.00)
PI 2004_1_470
MDM BUSINESS CONTENT 7.1 (7.00)
ERP 2004
CREMDM.CREMDM04
Cremdm04_500AddressFilterIn
CREMDM.CREMDM04
FTP_CREMDM_MDMIn
PI 2004_1_500
MDM BUSINESS CONTENT 7.1 (7.00)
PI 2004_1_500
MDM BUSINESS CONTENT 7.1 (7.00)
Interface Mapping
Inbound Interface
Receiver Communication
Systems based on NW 7.0 MDC
Outbound Interface
Sends Data ERP 2005
October 2011
Channel Template CREMDM.CREMDM04
Cremdm04_600AddressFilterIn
CREMDM.CREMDM04
FTP_CREMDM_MDMIn
SAP APPL 6.0
MDM BUSINESS CONTENT 7.1 (7.00)
SAP APPL 6.0
MDM BUSINESS CONTENT 7.1 (7.00)
19
MDM 7.1 Vendor Content
3.3.2
Business Scenario: MDM710_Outbound
MDM 7.1 Outbound Processing – MDM Server sending data to SAP remote system MDS Sends Data
MDM 7.1
Systems based on NW2004 MDC Receives Data
Outbound Interface
Sender Communication Channel Template
Interface Mapping
Inbound Interface
Receiver Communication Channel Template
R/3 4.7x110
CREMDM.CREMDM04
FTP_CREMDM_MDMOut
Cremdm04_470ToCremas04_470Out
CREMAS.CREMAS04
IDOC_Receiving_MDMOut
PI2004_1_470
MDM BUSINESS CONTENT
MDM BUSINESS CONTENT 7.1 (7.00)
SAP APPL 4.70
MDM BUSINESS CONTENT 7.1 (7.00)
Cremdm04_470ToAdremas02_470Out
ADRMAS.ADRMAS02
IDOC_Receiving_MDMOut
MDM BUSINESS CONTENT 7.1 (7.00)
SAP ABA 6.20
MDM BUSINESS CONTENT 7.1 (7.00)
7.1 (7.00)
“
ERP 2004
“
CREMDM.CREMDM04
FTP_CREMDM_MDMOut
Cremdm04_500ToCremas04_500Out
CREMAS.CREMAS04
IDOC_Receiving_MDMOut
PI2004_1_500
MDM BUSINESS CONTENT
MDM BUSINESS CONTENT 7.1 (7.00)
SAP APPL 5.0
MDM BUSINESS CONTENT 7.1 (7.00)
Cremdm04_500ToAdremas03_500Out
ADRMAS.ADRMAS03
IDOC_Receiving_MDMOut
MDM BUSINESS CONTENT 7.1 (7.00)
SAP ABA 6.40
MDM BUSINESS CONTENT 7.1 (7.00)
7.1 (7.00)
“
October 2011
“
20
MDM 7.1 Vendor Content
Systems based on NW 7.0 MDC Receives Data
Outbound Interface
Sender Communication Channel Template
Interface Mapping
Inbound Interface
Receiver Communication Channel Template
ERP 2005
CREMDM.CREMDM04
FTP_CREMDM_MDMOut
Cremdm04_600ToCremas05_600Out
CREMAS.CREMAS05
IDOC_Receiving_MDMOut
SAP APPL 6.0
MDM BUSINESS CONTENT 7.1
MDM BUSINESS CONTENT 7.1 (7.00)
SAP APPL 6.0
MDM BUSINESS CONTENT 7.1
Cremdm04_600ToAdremas03_600Out
ADRMAS.ADRMAS03
IDOC_Receiving_MDMOut
MDM BUSINESS CONTENT 7.1 (7.00)
SAP Basis 7.00
MDM BUSINESS CONTENT 7.1
(7.00)
“
(7.00)
“
(7.00)
NW2004s BI
GenericVendorOut
FTP_GenericVendor_MDMOut
GenericVendorIn
HTTP_Receiving_MDMOut
MDM BUSINESS CONTENT
MDM BUSINESS CONTENT 7.1
BI CONT 7.03
MDM BUSINESS CONTENT 7.1
7.1 (7.00)
(7.00)
October 2011
(7.00)
21
MDM 7.1 Vendor Content
4.
Web Dynpro Configuration
Starting with MDM 7.1 SP4 there is a new tool to create Java Web Dynpro UIs based upon a MDM repository. The new MDM Web Dynpro Configurator (see section Development and Customization MDM Web Dynpro Components) supports you to fulfill this task. The existing documentation helps to include the new Web Dynpro UIs in a MDM project.
4.1
Deliverables
The current MDM content contains a predefined XML file for importing in the Web Dynpro Configurator. The file is located in the business content ZIP file, next to the actual MDM repository. It is named MDM71800_VENDOR_WDC.xml. The predefined UI consists of the following Web Dynpro Components for the both main tables: Search Result Set Item Details Note All predefined Web Dynpro Components are templates only. You can change all components so that they fit exactly to your project requirements. Nevertheless it is not possible to combine two main tables into a single component.
4.1.1
Search
The search UI highlights both a Free-Form and a Lookup Search. You can change both according to your project needs.
4.1.2
Result Set
The result set defines a table displaying all records of a resulting search. The predefined result set uses the fields ID, Account Group, Full Name, Full Address, Company Code Data, and Purchasing Organization Data. It allows the export of the result records as XML. You can change the fields and settings according to your project needs.
4.1.3
Item Details
The item details component consists of all main table fields and tuples. The sorting of the fields and tuples into the different tabs is similar to the UI layout in SAP ERP remote systems. Nevertheless you can change the full UI according to your project needs.
4.2
Usage
The Web Dynpro Configuration is currently not used by any consumer. It is a stand-alone delivery that shall support you to create your own Web Dynpro based applications on the repository. Refer to the Web Dynpro Component How-to Guide (see section Development and Customization MDM Web Dynpro Components) for details. If you have setup the Web Dynpro Components with the predefined default values, you can immediately check the Vendor UI with the following link: http://:/webdynpro/dispatcher/sap.com/tc~mdm~wdcomps~master~wd/MASTER?proj= VENDOR&rs=VENDOR_RESULT&s=VENDOR_SEARCH&id=VENDOR_DETAILS
October 2011
22
MDM 7.1 Vendor Content
5.
Sample Data
The Vendor content contains a file named “Data.zip”. This MDM Vendor data package contains two types of data files. All files within the "MasterFiles" folder are those XML files that have been used by SAP to create the import maps. The master files MUST NOT be used for data import within a productive environment. You may use these files for (re-) building the import maps only. All files within the "SampleData" folder are samples useable for data import. The sample files MUST NOT be used within a productive environment. You may use the files for demo purposes only. Both folders contain batch files that copy the files into the related port folders. To enable the batch files, you have to copy the parent folders into the repository’s distribution root folder. The MasterFiles respectively SampleData folder has to exist on the same level as the repository Inbound and Outbound folders. Otherwise the batch files are not able to find the correct path to the port folders. The batch files have been built on a windows environment. If you want to execute the files on a shared MDS folder, please check http://support.microsoft.com/kb/156276/en for details.
October 2011
23
MDM 7.1 Vendor Content
6.
Import of Reference Data
You extract customizing data from SAP remote systems using the generic customizing data extractor MDMGX (see MDMGX Documentation for details). The configuration file “MDMGX_71800_Vendor.txt” is available in the downloadable Business Content. CAUTION SAP remote system R/3 4.7 has a limitation regarding the length of the MDMGX port. Its name must not exceed 30 characters. You have to adjust the following ports by both renaming the port in the MDMGX text file and changing the related port code in the repository. Affected ports are: Activity Codes For Social Insurance (34) Interest Calculation Frequencies (32) Interest Calculation Indicators (32) Price Determination Date Controls (33) Profiles For Material Data Transfer (34) Regional Structure Check Status (31) Refer to SAP Note 1391292 for details. If you use the Vendor repository to consolidate more than one R/3 or ERP system, it makes sense to check and add some key mapping information for some of the Vendor lookup tables. The reason is that the customizing values you extract from the various systems might differ. This should be checked and corrected before loading any object data. The predefined import maps use the customizing values for matching (the names/descriptions but not the keys/codes). That means if you load reference data from multiple remote systems, MDIS checks if the value already exists depending on its name. If yes, it updates the key mapping information of the existing record; if not, it creates a new record. MDIS is only able to identify perfect matches. Slightly different values lead to different records. Note The following chapters describe some tips regarding the import of reference data.
6.1
Banks
Main table Banks contains the Bank Master Data (like name of the bank, bank address, and so on). Although the data is designed as a main table, it is used a lookup for each Vendor record only. The link between the Vendors and the Banks main table is established in the Vendor’s tuple Bank Details. The import of Bank Master Data happens with MDMGX. Related customizing entries are maintained in the MDMGX text file. The import of Bank Details is part of the Vendor import. CAUTION The Bank Master Data in the repository has been enhanced to cover more information from the related ERP Bank Master table BNKA. The enhancement includes an update of the related MDMGX Bank Details extractor, too. Ensure that you have applied SAP Note 1349089 to your ERP system before you start the load of reference data into your repository!
October 2011
24
MDM 7.1 Vendor Content
6.2
Lookup Hierarchy Tables
Starting with the release of MDM 7.1 SP4 the MDMGX content of the Vendor uses the new function module MDM_ERP_MULTI_HIERARCHIES_EXTR to extract customizing data for its hierarchy lookup tables. The default configuration does not use the parameter SHOWMISSINGTRANSLATION. The Name field of a hierarchy is usually built upon the combination of texts (e.g. the Region shows the Country Name and the Region Name). MDMGX needs to deliver a concatenated text so that Import Manager respectively MDIS are able to split the text into a hierarchy during import. As the texts are usually extracted from different customizing tables, there are a few combinations possible regarding the multilingual definition of the hierarchy name field:
MDM Console
Source Parent
Source Child
MDMGX action
Name field is multilingual
Text is multilingual
Text is multilingual
Extract and concatenate parent and child texts in multilingual versions
Name field is multilingual
Text is not multilingual
Text is multilingual
Extract the default text of the parent and concatenate it with the multilingual version of the child. This is the case for all multilingual hierarchies that relate to the Company Code or Plant as neither the company code nor the plant text is not multilingual
Name field is not multilingual
Text is not multilingual
Text is not multilingual
Extract and concatenate parent and child texts in the default versions
Name field is not multilingual
Text is multilingual
Text is not multilingual
Extract the parent text in the logon language of the user that performs the extraction. Concatenate the default version of the child text. This is the case for the hierarchy lookup tables Payment Methods, Regional Structure Districts and Withholding Tax Codes. You can control the language version of the parent text by logging on to the SAP remote system with a different logon language.
CAUTION Ensure that you have applied SAP Notes 1403879, 1404964 and 1407978 to enable the import of the new lookup hierarchy tables in your ERP remote system.
6.3
Unique Constraints
Flat and hierarchy lookup tables use unique constraint for their specific code fields. The code is usually a clone of the record’s remote key. The unique constraint ensures a high quality of your reference data. When you import reference data for multiple remote systems, MDM Import Manager and/or MDIS check the unique constraints. This prevents importing invalid names for the same code values. The import fails with the structural or value exception “Unique constraint violation” so that you can check your customizing values accordingly.
October 2011
25
MDM 7.1 Vendor Content
Example Your system landscape consists of two remote systems. System A contains a country Germany having the code DE. System B contains country Gremany having the code DE. The import of System A’s reference data works fine. The import of System B’s reference data fails due to a unique constraint violation. The reason is that MDM Import Manager respectively MDIS match on the Country name. In this case Germany differs from Gremany. MDM Import Manager respectively MDIS try to create a new record for Gremany. This new record would have the Code DE – but this code already exists in the repository. To indicate this issue, the unique constraint violation is thrown. To clean up the issue, you can either adjust the mapping in MDM Import Manager or correct the wrong customizing entry in your remote system and re-extract the correct values (which is the recommended solution, of course). CAUTION MDM Import Manager and MDIS check all fields for unique constraints that are defined as unique fields in MDM Console. If the unique field is multilingual, each language layer is checked independently for unique constraints. Additionally remote keys must be unique, too.
6.4
Import Sequence
Each lookup table of the MDM Vendor repository can be imported automatically using MDIS. Related ports are part of the repository. Importing reference data requires a specific sequence as some of the lookup tables depend on each other. To ensure a correct sequence of importing, the Vendor content uses the MDMGX Process Level concept. The lists below show the ports using process levels 0 to 2. CAUTION You have to execute MDMGX three times: one time for each process level. Before you start the extraction of process level 1, make sure that MDIS has successfully imported all files of process level 0. Process Level 0 Port
Port
LT_AccountGroups
LT_ActivityCodesForSocialInsurance
LT_ActivityProfiles
LT_ActualQMSystems
LT_BlockFunctions
LT_BusinessTypes
LT_CommunicationTypes
LT_CompanyCodes
LT_ConfirmationControlKeys
LT_Countries
LT_Currencies
LT_DeliveryServiceTypes
LT_DMEIndicators
LT_DunningBlocks
LT_DunningNoticeGroupingKeys
LT_DunningProcedures
LT_ExemptionAuthorities
LT_FactoryCalendars
LT_FreightGroups
LT_Genders
LT_GroupsForCalculationSchema
LT_Incoterms
October 2011
26
MDM 7.1 Vendor Content
Port
Port
LT_IndustrialSectors
LT_IndustryTypes
LT_InterestCalculationFrequencies
LT_InterestCalculationIndicators
LT_Languages
LT_MinorityIndicators
LT_PaymentAdvicesByXML
LT_PaymentBlocks
LT_PaymentGroupingKeys
LT_PaymentMethodSupplements
LT_PaymentTerms
LT_PeriodicAccountStatements
LT_PhoneNumberTypes
LT_PlanningGroups
LT_Plants
LT_PODIndicators
LT_PrepaymentRelevances
LT_PriceDeterminationDateControls
LT_PriceMarkingAgreements
LT_ProfilesForMaterialDataTransfer
LT_PurchasingGroups
LT_PurchasingOrganizations
LT_RegionalStructureCheckStatus
LT_RegionalStructureGroupings
LT_ReleaseApprovalGroups
LT_RestrictionProfiles
LT_ServiceAgentProcedureGroups
LT_ShippingConditions
LT_SortCriteriaForMaterials
LT_SortKeys
LT_SubsidyIndicators
LT_TaxBases
LT_TaxNumberTypes
LT_TaxTypes
LT_TimeZones
LT_Titles
LT_TransportationChains
LT_TransportationServiceAgents
LT_UndeliverableReasons
LT_UnitOfMeasureGroups
LT_URITypes
LT_YesNoIndicator
Process Level 1 Port
Dependent Port
LT_Clerks
LT_CompanyCodes
LT_CustomsOffices
LT_Countries
LT_DunningAreas
LT_CompanyCodes
LT_HouseBanks
LT_CompanyCodes
LT_ModesOfTransport
LT_Countries
LT_PaymentMethods
LT_CompanyCodes
LT_PlanningCalendars
LT_Plants
LT_RecipientTypes
LT_CompanyCodes
LT_ReconciliationAccounts
LT_CompanyCodes
LT_RegionalStructureCities
LT_Countries
October 2011
27
MDM 7.1 Vendor Content
Port
Dependent Port
LT_RegionalStructureStreets
LT_Countries
LT_Regions
LT_Countries
LT_RoundingProfiles
LT_Plants
LT_ToleranceGroupsBupaGl
LT_CompanyCodes
LT_ToleranceGroupsInvoice
LT_CompanyCodes
LT_TradingPartners
LT_Countries
LT_TransportationZones
LT_Countries
LT_WithholdingTaxCodes
LT_CompanyCodes
LT_WithholdingTaxCountries
LT_CompanyCodes
Process Level 2 Port
Dependent Port
LT_BankDetails
LT_Regions
LT_RegionalStructureDistricts
LT_RegionalStructureCities
October 2011
28
MDM 7.1 Vendor Content
7.
Import of Master Data
7.1
Message Flow
You extract master data from SAP ERP remote systems using the generic master data extractor MDM_CLNT_EXTR (see MDM CLNT_EXTR Documentation for details). The import requires a correct setup of the SAP remote systems and PI. Refer to the IT Scenario Configuration Guide available on SAP Service Market Place and chapter MDM Vendor PI Content of this note for details. The (recommended) message flow between SAP ERP remote systems and MDM is realized with the CREMDM IDoc type. MDM_CLNT_EXTR is able to collect ERP vendor records into this IDoc. The IDoc is transferred via the IDoc Adapter from ERP to PI. PI is responsible for the transformation of the IDoc into a XML format (see Interface (XSLT) Mapping) and the correct routing to MDM. The transfer from PI to MDM is either done via FTP or the MDM PI Adapter.
7.2
Interface (XSLT) Mappings
The Vendor repository is able to import XMLs having the same structure as the CREMDM IDoc. The Interface (XSLT) Mappings provided by the Vendor PI content do not perform any changes regarding the message structure. Nevertheless the mapping is mandatory as some segment specific values mappings are happening on PI. International Address Versions of the segments (address data) and (address notes) are filtered on PI. The value for the Payment Methods in segment needs to be re-formatted so that Import Manager respectively MDIS is able to import the data into the multi-valued hierarchy lookup table. The data in the IDoc is a single string consisting of the remote keys of the payment methods. The required format is a coma-separated string including the related company code for each payment method. Example A record for Company Code 0001 in ERP has four payment methods 1, 7, A, and C. The element in the company code data segment carries the value 0001. The payment method element in the same segment carries the value 17AC. The XSLT mapping on PI transforms the value into the required format 00011, 00017, 0001A, 0001C. Import Manager respectively MDIS are now able to map the single field to the corresponding entries of the hierarchy lookup table.
7.3
Field Mappings
Field mappings are generally listed in the attached Excel file Field Mapping and Check Tables Vendor.xls. In a few cases the Vendor Import Map uses partitions and/or cloned fields to concatenate and/or duplicate some values:
Dest. Table / Tuple
Destination Field
Source Field(s)
Vendors
Remote Key
Clone: LIFNR
Region
Partition: COUNTRY + REGION
October 2011
29
MDM 7.1 Vendor Content
Dest. Table / Tuple
Destination Field
Source Field(s)
Region for PO Box
Partition: POBOX_CTRY + PO_BOX_REG
Regional Structure Additional City
Partition: COUNTRY (4) + HOMECITYNO
Regional Structure City
Partition: COUNTRY (3) + CITY_NO
Regional Structure District
Partition: COUNTRY (5) + CITY_NO + DISTRICT_NO
Regional Structure PPO Box City
Partition: POBOX_CTRY (2) + PBOXCIT_NO
Regional Structure Street
Partition: COUNTRY (6) + STREET_NO
Transportation Zone
Partition: COUNTRY (2) + TRANSPZONE
Bank Details
Bank
Partition: BANKS + BANKL
Company Code Data
Accounting Clerk
Partition: BUKRS (2) + BUSAB
House Bank
Partition: BUKRS (4) + HBKID
Recipient Type
Partition: BUKRS (6) + QSREC
Reconciliation Account
Partition: BUKRS + AKONT
Tolerance Group (Business Partner)
Partition: BUKRS (3) + TOGRU
Tolerance Group (Invoice)
Partition: BUKRS (3) + TOGRR
Withholding Tax Code
Partition: BUKRS (7) + QSSKZ
Withholding Tax Country
Partition: BUKRS (8) + QLAND
Dunning Area
Partition: BUKRS + MABER
Dunning Clerk
Partition: BUKRS (2) + BUSAB
Mode of Transport for Foreign Trade
Partition: LAND1 (4) + EXPVZ
Office of Exit or Entry for Foreign Trade
Partition: LAND1 (5) + ZOLLA
Planning Calendar
Partition: WERKS + MRPPP
Planning Cycle
Partition: WERKS (2) + LFHRY
Dunning Data
Purchasing Organization Data
October 2011
30
MDM 7.1 Vendor Content
Dest. Table / Tuple
7.4
Destination Field
Source Field(s)
Rounding Profile
Partition: WERKS (3) + RDPRF
Value Mappings
The Import Maps for Vendor records do not contain any value mapping. The reason is that customizing values can differ for each remote system. It hardly possible to predict all values that might occur in your systems. It is your task to enrich the Import Maps with the correct value mappings. You can use MDM Import Manager to have a full control about the value mapping. Depending on the Import Map configuration, Import Manager tries to map the values automatically. Note In general field values will only be mapped automatically if: a) there is value mapping information stored in the import map b) the source value is NULL and the Import Map configuration option Automatically map NULL values is set to yes c) the destination field has the type lookup table with key mapping and the source values are the keys If MDM Import Manager is not able to map all values automatically, you have to map the missing values manually. Tip If you know all of your customizing values that occur in your records, you could think about creating a dummy XML file containing all possible values. Then use this dummy file once to update the Import Map with all value mappings. As soon as you have saved the map with all value mappings, you could automate the import. MDIS is able to handle unmapped values, too. This depends on the configuration options of the Import Map. The screenshot below shows the default settings used by the predefined Import Map.
Figure: MDIS Value Mapping
7.5
Import of Lookup Main Relationships
General information about the import of lookup main relationships is available in the MDM Import Manager Reference Guide. The following chapters below list some special cases within the Vendor repository.
7.5.1
Bank Details
The Bank Details tuple is part of the Vendors main table. The tuple includes a lookup to the secondary Banks main table. To enable a successful link between a Bank Details tuple record to its related
October 2011
31
MDM 7.1 Vendor Content
Banks master record, only the remote keys of the Banks main table are mapped within the Vendor import map. This remote key is a concatenation of the source field BANKS (Bank Country) and BANKL (Bank Key) that is mapped to the destination field Bank of the Bank Details tuple. All further mapped fields (like BANKN (Bank Account Number), BKREF (Reference Details), and so on) specify the Bank Details tuple record only. They do not change the related Banks master record itself. Recommendation To ensure that the import of Bank Details works smoothly, ensure that all required Banks master records already exist in your repository.
7.5.2
Main Table Vendors
Fields Alternative Payee, Fiscal Address and Tax Office of the Vendors main table are all lookup main fields that relate to a different record of the Vendors main table. Fields Alternative Payee and Head Office of the Company Code Data tuple are all lookup main fields that relate to a different record of the Vendors main table. Field Dunning Recipient of the Dunning Data tuple is a lookup main field that relates to a record of the Vendors main table. CAUTION Remember that a lookup to a main table record can only be imported if the lookup record already exists in the repository. It is not possible to import a new main table record and use the very same record as a lookup main record for a different record in a single message. MDM Import Manager respectively MDIS are not able to identify the new record as a valid lookup main record in this case. If you are facing a similar situation for your master data records, you have to execute the import of the message twice. The first import creates all main table records without the lookup main relationships. The second import updated the now existing records with the missing lookup main relationship information.
7.6
Import of Tuples
Tuples can be understood as sub-records of your main record. The import of tuples requires a specific logic to decide if a tuple record should be added, updated, and so on. This setting can be specified either generally for all tuples using the Import Map Configuration Options, or specifically for each tuple being part of your repository. The default setting as defined in the delivered Import Map is shown in the screenshot below.
Figure: Default Tuple Import Configuration Depending on the data you’re going to import, you have to decide if the default settings are useable for you, or if you have to redefine some or all properties. Matching tuple fields defines those fields that MDM Import Manager respectively MDIS use to identify if the source values should be used to create a new tuple record or update an existing one.
October 2011
32
MDM 7.1 Vendor Content
Recommendation As mentioned above, you can define the tuple import for each tuple of the repository independently. Therefore switch to the Map Fields/Values tab in MDM Import Manager. Locate a tuple in the Destination Fields pane. Right-click on it and choose Set Tuple Update… from the context menu.
Figure: Specific Tuple Import Configuration (I) MDM Import Manager shows a pop-up window where you can define the matching fields and import actions specifically for this tuple.
Figure: Specific Tuple Import Configuration (II) Note Additionally the handling of NULL values differs for tuples. The property Set NULL Interpretation (see the screenshot on the previous page) is set to ignore for all tuples and their member fields.
October 2011
33
MDM 7.1 Vendor Content
7.7
MDIS usage
Currently the inbound ports for importing MDM Vendor XML messages are defined as manual ports. This configuration setting has been made for some reasons. All predefined maps do not yet contain any specific value mapping and only a common definition for the tuple import. Both rely strongly on the data you’re going to import. Therefore SAP cannot predefine these settings. Recommendation Use MDM Import Manger at least once for having a full control of the value and tuple mapping. As soon as you have saved the Import Map including your specific value and tuple mapping, you can switch to automatic import via MDIS by changing the corresponding port configuration in MDM Console.
October 2011
34
MDM 7.1 Vendor Content
8. 8.1
Syndication of Master Data Message Flow
The syndication requires a correct setup of the SAP remote systems and PI. Refer to the IT Scenario Configuration Guide available on SAP Service Market Place, Tips and Tricks for MDM Vendor Distribution and chapter MDM Vendor PI Content of this document for details. The (recommended) message flow between MDM and SAP ERP remote systems is realized with the CREMDM, CREMAS and ADRMAS IDoc types. MDM sends CREMDM XML messages to PI. The transfer from MDM to PI is either done via FTP or the MDM PI Adapter. PI is responsible for the transformation and splitting of the XML message into the ADRMAS and CREMAS IDocs (see Interface (XSLT) Mappings) and the correct routing to ERP. The IDocs are transferred via the IDoc Adapter from PI to ERP. CAUTION It is absolutely mandatory that you configure PI in a correct way. Ensure that the message split has the correct sequence. Address IDocs must be sent always before the Vendor IDocs. Otherwise ERP will not be able to process the IDocs correctly.
8.2
Interface (XSLT) Mappings
As mentioned above the CREMDM message that is sent from MDM to PI is split into different IDoc messages. The resulting Vendor (CREMAS) IDocs carry one single record as the ALE inbound processing in R/3 or ERP is not mass capable. Furthermore the address information is sent to R/3 or ERP using a specific IDoc (ADRMAS). Some fields of the Vendor (CREMAS) IDoc are available in the Address IDoc, too. As the Address IDoc is the first, leading IDoc the duplicate fields of the Vendor IDocs are marked with the No Data Sign that is a slash /. ALE inbound is using the already existing values of the address IDoc instead (refer to SAP Note 384462 for details). CAUTION It is absolutely mandatory that you configure PI in a correct way. Ensure that the message split has the correct sequence. Address IDocs must be sent always before the Vendor IDocs. Otherwise ALE will not be able to process the IDocs correctly. MDM is using the message split to enable the Business Address Service (BAS) usage. BAS supports an additional amount of address fields as well as the possibility to define extended address checks. An additional bonus is that using the BAS ensures that all address fields have exactly the same Meta Data (field length, customizing data, and so on) through all SAP systems. It’s strongly recommended to do the message split and to use BAS. Furthermore the Payment Method element of the company code data segment is re-formatted. As the source of this field is a multi-valued hierarchy in MDM, the value of the field is a comma separated string. The XSLT mapping removes the delimiters from the string. Example The record in MDM has four payment methods 1, 7, A, and C. The output of Syndicator respectively MDSS for element in the company code data segment is the value 1, 7, A, C. The XSLT mapping on PI transforms the value into the required format 17AC.
October 2011
35
MDM 7.1 Vendor Content
8.3
Field Mappings
Field mappings are generally listed in the attached Excel file Field Mapping and Check Tables Vendor.xls. In a few cases the Vendor Syndication Map uses codes and/or cloned fields instead of the remote keys and/or mentioned field mappings:
Table / Tuple
Field
Destination Fields
Vendors
Remote Key Value
Clone: LIFNR, OBJID, LIFNR, LIFNR. LIFNR, LIFNR
Language Remote Key
Clone: LANGU_CR, LANGU
Language ISO Code
Clone: LANGU_ISO, LANGU_ISO
Regional Structure Additional City Code
HOMECITYNO
Regional Structure City Code
CITY_NO
Regional Structure District Code
DISTRICT_NO
Regional Structure PO Box City Code
PBOXCIT_NO
Regional Structure Street Code
STREET_NO
Region Code
Region
Region for PO Box Code
PO_BOX_REG
Transportation Zone Code
TRANSPZONE
Bank Details
Region Code
PROV2
Company Code Data
Accounting Clerk Code
BUSAB
House Bank Code
HBKID
Payment Methods Code
ZWELS
Recipient Type Code
QSREC
Reconciliation Account Code
AKONT
Tolerance Group (BP/GL) Code
TOGRU
Tolerance Group (Invoice) Code
TOGRR
Withholding Tax Codes Code
QSSKZ
Withholding Tax Country Code
QLAND
Dunning Area Code
MABER
Dunning Clerk Code
BUSAB
Mode of Transport for Foreign Trade
EXPVZ
Dunning Data
Purchasing Organization Data
October 2011
36
MDM 7.1 Vendor Content
Table / Tuple
8.3.1
Field
Destination Fields
Office of Exit or Entry for Foreign Trade
ZOLLA
Planning Calendar
MRPPP
Planning Cycle
LFHRY
Rounding Profile
RDPRF
Bank Details & Bank Master
The syndication of Bank Details and Bank Master records differs from the import. The reason is that the SAP ERP remote system requires a full set of the data within the IDoc segment . Missing and/or empty elements are interpreted as value deletions. The Syndication Map uses both fields of the Bank Details tuple and its Bank lookup main field to create a complete segment.
8.4
Predefined Field Values for CREMDM04
Some fields of the Syndication Map carry predefined values. The values are set in MDM Syndicator as Static Text for the following Destination Items (IDoc fields or attributes). CAUTION If you change the existing Vendor Syndication Map or create one of your own, you must keep in mind that the SAP ERP remote system always expects a complete segment for IDoc inbound processing. Any missing and/or empty field is handled as a value deletion in SAP ERP.
8.4.1
Begin & Segment Attributes
Both the BEGIN and the SEGMENT attributes are mandatory within the CREMDM IDoc. The BEGIN attribute belongs to the segment whereas the SEGMENT attribute is part of each data carrying segment like , , and so on. It is mandatory that the BEGIN attribute and all SEGMENT attributes of used IDoc segments contain the value 1. Otherwise the IDoc inbound processing in the SAP ERP remote system might fail.
8.4.2
Message Function Element
The Message Function Element is usually a part of data carrying segments like , , and so on (exception: and all of its children do not use the message function). The message function defines the inbound processing action of the SAP ERP remote system. The Vendor Syndication Map is always using value 005 that triggers a replacement of previous information. Other valid values and their related actions are: 003 Delete: Message contains objects to be deleted 004 Change: Message contains changes 005 Replace: This message replaces previous messages 009 Original: First message for process 023 Wait/Adjust: Data should not be imported 018 Resend
October 2011
37
MDM 7.1 Vendor Content
8.4.3
Specific Address Values
To ensure the correct inbound processing of Vendor (CREMAS) and Address (ADRMAS) IDocs in SAP ERP remote systems, the CREMDM IDoc created by the Vendor Syndication Map must contain some specific information. Specific Values Fields in segment must have the following values: OBJ_TYPE = LFA1 CONTEXT = 0001 Fields in segment must have the following values: ADDR_GROUP = BP No Data Sign Some fields of the Vendor IDoc are available in the Address IDoc, too. As the Address IDoc is the first, leading IDoc the duplicate fields of the Vendor IDocs are marked with the “No Data Sign” that is a slash “/”. ALE inbound is using the already existing values of the address IDoc instead (refer to SAP Note 384462 for details). The fields in segment are: ANRED, DATLT, LAND1, NAME1, NAME2, NAME3, NAME4, ORT01, ORT02 PFACH, PSTL2, PSTLZ, REGIO, SORTL, SPRAS, STRAS, TELBX, TELF1 TELF2, TELFX, TELTX, TELX1, ADRNR, PFORT, TXJCD, LZONE, The field in segment is: LFURL
8.5
Predefined Field Values for GenericVendor
If you distribute data to a new BI system that uses a web service base data source for inbound processing, the XML file requires the correct by namespace. The namespace is defined in the syndication map (see screenshot below).
Figure: Generic Vendor Map Properties
8.6
Completion of the delivered Map Templates
All delivered syndication maps are templates. You have to add some specific settings before you can use them in a productive environment. Therefore open a syndication map with MDM Syndicator. Switch to tab Map Properties. Check that property Remote Key Override is set to your remote system. This setting ensures that MDM Syndicator respectively MDSS use the correct key mapping information when creating the XML message. Using this property you can control which keys shall be distributed to your BI system.
October 2011
38
MDM 7.1 Vendor Content
Check that property Suppress Records without Key is marked. This ensures that only those records are distributed back to the remote systems that were previously imported from the same system. Use properties XML File Output and Max Records Per Output File to control the amount of records to be distributed in one single XML message. Use property Suppress Unchanged Records to control if you want to send always all records or changed records (delta distribution) only. The screenshot below shows the default properties of map _CREMDM04.
Figure: Syndication Map _CREMDM04 default Properties Completing the map is a mandatory step to use the automatic syndication!
October 2011
39
MDM 7.1 Vendor Content
8.7
MDSS usage
Currently the outbound ports for distributing MDM Vendor XML messages are defined as manual ports. This configuration setting has been made for some reasons. The delivered Syndication Maps are not yet complete. You have to complete the maps according to your distribution scenario and furthermore to add some system landscape specific information in the maps. As SAP neither knows your distribution scenario nor your system landscape, these values cannot be predefined. Use MDM Syndicator once to finish the maps. Then you can use MDM Console to configure the outbound ports for automatic processing.
October 2011
40
MDM 7.1 Vendor Content
9.
Known Issues and Limitations
9.1 9.1.1
Data Modeling Comparison to the CREMDM IDoc
The predefined repository does not support the full CREMDM IDoc structure. Supported segments are mentioned in the excel file Field Mapping and Check Tables that is attached to this note.
9.1.2
Communication Comments
Communication Comments (remarks for phone and fax numbers, E-Mail addresses, and so on) are not supported by the MDM Vendor content. The reason is the transport of the data in a different IDoc segment () that is not directly linked its related communication type. CAUTION If records from MDM are syndicated to ERP, existing values in ERP are deleted.
9.1.3
International Address Versions
International Address Versions are not supported by the MDM Vendor content. CAUTION If records from MDM are syndicated to ERP, existing values in ERP are deleted. If you are using International Address Version in your environment, refer to SAP Note 985296 respectively SAP for details.
9.1.4
Payment Transactions
Some parts of the Vendor’s Payment Transactions are not supported by the MDM Vendor content. This is valid for the Permitted Payee. The reason is a missing implementation in MDM_CLNT_EXTR and a missing related segment in the CREMDM IDoc. Note If records from MDM are syndicated to ERP, existing values in ERP are not deleted.
9.1.5
Time Dependency
The time dependency concept of SAP systems is not supported by the MDM Vendor content.
9.1.6
Schema Transport & Validation Groups
If you use the MDM Schema Transport Mechanism to create a new repository from the existing Vendor repository, Validation Groups are not being transported. You lose all validation groups and have to add them manually in your new repository (see chapter Validations for details). As soon as you have added the groups, ensure to check the workflow MDM Mandatory Fields Validation, too. This workflow executes the Validation Group ERP Mandatory Fields.
October 2011
41
MDM 7.1 Vendor Content
9.2 9.2.1
Data Distribution Import/Syndication from/to CRM and SRM
The import of Suppliers from respectively the syndication of Suppliers to SAP CRM and SRM remote systems is not supported by the MDM Vendor content.
9.2.2
Import into Tuples
In some special cases MDM Import Manager or MDIS might create empty tuples while importing data. The reason is the handling of missing versus empty message elements. SAP ERP sends an empty element for the Yes/No Indicator as “No” value. This is mapped accordingly. As long as a full message segment (for example phone numbers) exists, the mapping works fine. The issue occurs only if a record does not have the segment at all (for example a Vendor without phone numbers). In this case SAP ERP excludes the complete segment from the message. Nevertheless MDM Import Manager and MDIS currently handle these missing elements in the same way as empty ones. The mapping of the missing Yes/No Indicator element is performed and an empty tuple is created. The issue is already under investigation and should be fixed within the next releases. The current workaround is either changing the Import Map for Vendors before import or a manual deletion of the empty tuples after import.
9.2.3
“Out of Memory” issues during Import
If you import source files that consist of a high amount of sub-segments (e.g. a Vendor has several company codes, purchasing organizations, phone & fax numbers, and so on) you might run into an “Out of Memory” issue during the import. The reason is the way MDM Import Manager and/or MDIS are handling this kind of source file. To resolve the issue, split the import into several runs. The first run shall import all main table data including the key mapping for a record. Other runs use only the key mapping information to identify the record and update the already existing record with additional tuple data. Note that you have to split the import map only. You can use the same source file for each import. The predefined content contains a set of split import maps in the Import.zip file. The maps are not part of the repository. If you need to use the maps, you have to import them and create related ports accordingly. If you want to automate the copy of the source file into the different new ports, you can use PI with additional communication channels for this purpose.
9.2.4
MDM PI Adapter Usage
Starting with MDM 7.1 a new, MDM specific PI Adapter can be used for the message distribution. If you want to use the adapter in your scenario, you have to change some configuration settings. First of all the adapter requires the usage of MDIS and MDSS. You have to change the corresponding port configuration in MDM console to automatic processing. Secondly the current PI Integration Scenarios still use the FTP Adapter for the Communication Channels between PI and MDM. You have to choose the PI Adapter instead during the configuration of your system landscape on PI. Refer to the MDM 7.1 PI Adapter Guide for more details.
October 2011
42
MDM 7.1 Vendor Content
9.3
Data Processing
9.3.1
Merge of Records with Lookup Main Relationships
If a main table record A is linked to another (different) main table record B (lookup main relationship), record A cannot be merged with any other record. MDM Data Manager reports a related error message. This behavior is by design.
9.3.2
Portal Maintenance for Main Table Banks
The current Portal content does not provide iViews for maintaining records of the additional main table Banks.
9.3.3
Hierarchy table Validations
Some hierarchy lookup tables for Company Code Data use the Vendor’s Country as dependent field. Currently it is not possible to include a main table field in a validation for a tuple record. Therefore hierarchy consistency checks cannot be done for the Company Code Data fields Payment Method, Recipient Type, Withholding Tax Code and Withholding Tax Country. Some hierarchy lookup tables for Dunning Data use the Vendor’s Company Code as dependent field. Currently it is not possible to include a parent tuple field in a validation for a tuple record. Therefore hierarchy consistency checks cannot be done for the Dunning Data fields Dunning Area and Dunning Clerk. Some hierarchy lookup tables for Purchasing Organization Data use the Vendor’s Country or Plant as dependent field. Currently it is not possible to include a main table field in a validation for a tuple record. Therefore hierarchy consistency checks cannot be done for the Purchasing Organization Data fields Customs Offices, Modes of Transport, Planning Calendars and Rounding Profiles.
9.3.4
Central Master Data Maintenance
The pre-defined content as it is currently delivered is not yet usable for a central master data maintenance scenario. The content covers all requirements for a master data consolidation and/or harmonization only. A cMDM scenario has additional requirements that are not yet covered by the content like: Validations Although the content contains some validations, these are not the complete set of existing validations (e.g. in a SAP ERP system). Furthermore validations are in many cases customizing settings of the actual system. Therefore the actual validation can differ from system to system. It must be clearly defined by the implementation project which validation shall be run in MDM and how each validation shall look like. Approval Process The central maintenance of master data usually requires a sophisticated approval process, in many times implemented within a more or less workflow. This is currently not implemented by the predefined content. It must be clearly defined by the implementation project which approval process shall be executed in MDM. Remote Key Creation If you create data in MDM, a major task is the creation of the record’s key, both in the MDM system as well as in SAP ERP systems. Although MDM is able to create remote keys for the target systems, you might run into issues with the customizing settings of the target system. Usually SAP ERP systems differentiate between internal and external number ranges for keys. Internal number ranges mean that the system assigns the key; whereas an external number range accepts keys given by the sender of
October 2011
43
MDM 7.1 Vendor Content
the data. In case of internal number ranges there is currently no mechanism that sends the created key back to MDM in an automated manner. This needs to be defined by the implementation project. Disclaimer The items above list the major issues that may appear if the pre-defined content is used for cMDM. The completeness of the list is not guaranteed.
October 2011
44
MDM 7.1 Vendor Content
10. Change History 10.1 MDM 7.1 SP8 Patch 0 Update: Change of Payment Methods, Recipient Types, Withholding Tax Codes, and Withholding Tax Countries handling according to SAP Note 1619538 Changed Lookup Table (hierarchy) Payment Methods, Recipient Types, Withholding Tax Codes and Withholding Tax Countries. Deleted field Country. Added field Company Code. Unique fields set to Company Code + Code. Updated XML Schemas CREMDM04 and ReferenceData R/3 & ERP. Added new Validation for company codes to check Payment Methods, Recipient Types, Withholding Tax Codes and Withholding Tax Countries. Updated Master and Sample XML files. Updated Import Map LT_PaymentMethods, LT_RecipientTypes, LT_WithholdingTaxCodes, and LT_WithholdingTaxCountries. Updated Import Map _CREMDM04. Changed mappings for fields Recipient Type, Withholding Tax Code and Withholding Tax Country. Ensure that SAP Note 1619538 is applied to your PI and ERP remote system. SP7 Patch 0 Update: rebuilt the archive for the new MDM release SP6 Patch 0 Update: rebuilt the archive for the new MDM release This is mandatory as the upgrade to MDM 7.1 SP6 requires a schema update. Furthermore the archive format has been improved in SP6. SP5 Patch 0 New: add tuple Dunning Data to support the Company Code Dunning information in MDM Enhance Tuple Company Code Data with a multi valued tuple field Dunning Data Add new flat lookup tables: Dunning Blocks, Dunning Procedures Add new hierarchy lookup tables: Dunning Areas CAUTION Ensure that you have applied SAP Note 1451228 to enable the Dunning Data support in your ERP remote system. Enhance ERP Reference Data XSD Enhance Master and Sample XML files Enhance Maps and Ports for Import & Syndication Enhance Validations New: Web Dynpro Configuration New: Validation Group MDM Execute All Validations Update: Translation according to the structural changes in the repository. SP4 Patch 0 New: add tuple Company Code Data to support the Company Code related information in MDM Enhance the Vendors main table with a multi valued tuple field Company Code Data
October 2011
45
MDM 7.1 Vendor Content
Add new flat lookup tables Company Codes, Dunning Notice Grouping Keys, Exemption Authorities, Interest Calculation Frequencies, Interest Calculation Indicators, Minority Indicators, Payment Advices by XML, Payment Blocks, Payment Grouping Keys, Payment Method Supplements, Payment Terms, Periodic Account Statements, Planning Groups, Prepayment Relevances, Release Approval Groups, Sort Keys, Subsidy Indicators Add new Hierarchy Lookup Tables Clerks, House Banks, Payment Methods, Recipient Types, Reconciliation Accounts, Tolerance Groups (Business Partner or G/L Account), Tolerance Groups (Invoice), Withholding Tax Codes, Withholding Tax Countries Add new Validations for hierarchy lookup consistency checks (see below) and numeric fields Enhance the Reference Data XSD for R/3 and ERP remote systems with the new lookup tables Enhance the Master XML for Reference Data import with the new lookup tables Add Import Maps & Ports for each lookup table Provide Sample Data XMLs for each lookup table Enhance MDMGX for extracting the related customizing tables CAUTION Ensure that you have applied SAP Notes 1403879, 1404964 and 1407978 to enable the Company Code Data support in your ERP remote system. Enhance the PI Content to handle the Payment Methods correctly CAUTION Ensure that you have applied the current PI Content in your PI System. New: add tuple Purchasing Organization Data to support the Purchasing Organization related information in MDM Enhance the Vendors main table with the fields: multi valued tuple field Purchasing Organization Data lookup flat fields Factory Calendar, Plant, Plant Level Relevant and Sub-Range Relevant Add new Flat Lookup Tables Activity Profiles, Confirmation Control Keys, Currencies, Factory Calendars, Groups for Calculation Schema, Incoterms, Payment Terms, Plants, Price Determination Date Controls, Price Marking Agreements, Profiles for Material Data Transfer, Purchasing Groups, Purchasing Organizations, Restriction Profiles, Shipping Conditions, Sort Criteria for Materials, Transportation Chains, Unit of Measure Groups Add new Hierarchy Lookup Tables Customs Offices, Modes of Transport, Planning Calendars, Rounding Profiles Add new Validations for numeric fields Enhance the Reference Data XSD for R/3 and ERP remote systems with the new lookup tables Enhance the Master XML for Reference Data import with the new lookup tables Add Import Maps & Ports for each lookup table Provide Sample Data XMLs for each lookup table
October 2011
46
MDM 7.1 Vendor Content
Enhance MDMGX for extracting the related customizing tables CAUTION Ensure that you have applied SAP Notes 1403879, 1404964 and 1407978 to enable the Purchasing Organization support in your ERP remote system. New: add tuple Web to support storage of web information (homepages, FTP, and so on) for communication data in MDM Enhance the Vendors main table with a multi valued tuple field Web Add new Flat Lookup Table URI Types Add new validations EPR Check Mandatory Web fields, MDM Check Web Sequence Number and MDM Check Web URI Enhance the Reference Data XSD for R/3 and ERP remote systems with the new lookup table Enhance the Master XML for Reference Data import with the new lookup table Add Import Maps & Ports for the lookup table Provide Sample Data XMLs for the lookup table Enhance MDMGX for extracting the related customizing tables New: add field Instruction Key to the Vendors main table New: add new Validation Group MDM Hierarchy Lookup Consistency The group includes the already existing validations for Vendors main table fields Region, Region for PO Box, and Transportation Zone Add new validations related to the Regional Structure support for Vendors main table fields Regional Structure Additional City, Regional Structure City, Regional Structure District, Regional Structure PO Box City and Regional Structure Street Add new Validations related to tuple Company Code data for fields Accounting Clerk, House Bank, Reconciliation Account, Tolerance Group (both) New: SP4 introduces a Code field for Validations. Adjust the validations in the repository accordingly. Update: change Role Business Expert to be read-only Updated: enhance Tuple E-Mail Addresses with a single field Is TNEF enabled Updated: enable Regional Structure File support for Addresses Add new Flat Lookup Tables Regional Structure Check Status Add new Hierarchy Lookup Tables Regional Structure Cities, Regional Structure Districts, Regional Structure Streets Add the Vendors main table fields Regional Structure Check Status Lookup to Flat Table Regional Check Status Regional Structure Additional City Lookup to Hierarchy Table Regional Structure Cities Change the Vendors main table fields City Code for City New name: Regional Structure City New type: Lookup to Hierarchy Table Regional Structure Cities City PO Box Code
October 2011
47
MDM 7.1 Vendor Content
New name: Regional Structure PO Box City New type: Lookup to Hierarchy Table Regional Structure Cities District Code for City New name: Regional Structure District New type: Lookup to Hierarchy Table Regional Structure Districts Street Code for City New name: Regional Structure City New type: Lookup to Hierarchy Table Regional Structure Streets Enhance the Reference Data XSD for R/3 and ERP remote systems with the new lookup tables Enhance the Master XML for Reference Data import with the new lookup tables Add Import Maps & Ports for each lookup table Provide Sample Data XMLs for each lookup table Enhance MDMGX for extracting the related customizing tables CAUTION Ensure that you have applied SAP Notes 1403879, 1404964 and 1407978 to enable the Regional Structure file for Addresses support in your ERP remote system. Updated: set all Display Fields of Lookup Tables to Sort Index = Normal to speed up import Updated: change definition of Hierarchy Lookup Tables Regions and Transportation Zones Change the Import Maps accordingly Change the Validations for the Vendors main table fields Region, Region for PO Box, and Transportation Zone accordingly Updated: change MDMGX Process Level for LT_BankDetails, LT_Regions and LT_Transportation_Zones Updated: enhance Master Data Sample files according to the structural changes in the repository Updated: modify the Vendor CREMDM04 XSD for R/3 and ERP remote systems Updated: modify CREMDM04 Import and Syndication Maps according to the structural changes in the repository Updated: Translation according to the structural changes in the repository. SP3 Patch 1 New: add the following Validations (see chapter Validations for details): MDM Check E-Mail Address Format MDM Check E-Mail Address Sequence Number MDM Check Fax Number Sequence Number MDM Check Mandatory Bank Master Fields MDM Check Phone Number Sequence Number MDM Check PO Box Region MDM Check PO Box vs. PO Box w/o Number MDM Check Transportation Zone MDM Check Vendor Numeric Fields New: add Create and Update Stamps for Main Table Banks Updated: enhance ERP Mandatory Fields Validation for Bank Details, Language, Phone & Fax Number and E-Mail Address checks (see chapter Validations for details)
October 2011
48
MDM 7.1 Vendor Content
SP3 Patch 0 First release of the new MDM Vendor content.
October 2011
49
MDM 7.1 Vendor Content
11. Related Information MDM Documentation (SAP Service Market Place) MDMGX Enhanced Extraction of Bank Details (SAP Note) MDMGX Enhanced Extraction of Hierarchies – Framework Part (SAP Note) MDMGX Enhanced Extraction of Hierarchies – Extractor Part (SAP Note) MDMGX Enhanced Extraction of Payment Terms (SAP Note) MDMGX Port Name Issue (SAP Note) MDM CLNT_EXTR Documentation (SAP Note) Tips and Tricks for MDM Vendor Distribution (SAP Note) Vendor: Match and Merge (How-to Guide attached to this note) MDM Vendor Content Information (Release 5.5) (SAP Note)
October 2011
50
MDM 7.1 Vendor Content
12. MDM 7.1 vs. MDM 5.5 Vendor The new Vendor repository is completely built from scratch using the new MDM 7.1 tools. MDM 7.1 offers some new possibilities for MDM Content creation. These are reflected in the new repository. Furthermore one intention of the new content is to synchronize similar content of different repositories (e.g. Vendor and Customer). The following chapters compare the new repository with the old one and give some reasons and explanations why the repository changed.
12.1 New Content in MDM 7.1 Vendor The table below lists the new content of the MDM 7.1 Vendor. Reasons are: DS = prevent Data loss in Syndication PT = Performance Tuning RE = Repository Enhancement RS = Repository Synchronization Component Lookup Tables in general
What is new? Only the display fields within lookup tables are defined for sorting. This is required to improve the import performance. All other fields are not sorted. This decreases the repository's load time.
Reason PT, RS
Each lookup table contains a Code field. The code is generally a copy of the (remote) key field. This enables user to switch of key mapping on lookup tables if they can ensure that the keys of customizing data are always identical for each remote system. Import and Syndication Maps have to be adjusted in this case. The length of all Name fields has been aligned to the related length in the remote systems. Lookup [Hierarchy] Tables in general
Hierarchy lookup tables contain additional codes as separate fields. The reason is that the Code field within hierarchy lookups is not unique. The additional codes combined with the actual code guarantee the uniqueness of a single record. Example: The unique code of a region consists of the concatenation of country code and region code.
RS
LT Business Types
This is a flat lookup table named Business Types used by the Vendors main table.
DS
LT Communication Types
This is a flat lookup named Communication Types used by the Vendors main table.
DS
LT Delivery Service Types
This is a flat lookup named Delivery Service Types used by the Vendors main table.
DS
LT Industry Types
This is a flat lookup named Industry Types used by the Vendors main table.
DS
LT Phone Number Types
This table is a flat lookup named Phone Number Types used by the Phone Numbers tuple definition.
RS
LT POD Indicators
This table is a flat lookup named POD Indicators used by the Vendors main table.
DS
LT Plants
This table is a flat lookup named Plants used by the Vendor main table. It is required for the Purchasing Organization enhancement.
RE, RS
October 2011
51
MDM 7.1 Vendor Content
Component
What is new?
Reason
LT Undeliverable Reasons
This table is a flat lookup named Undeliverable Reasons used by the Vendors main table.
DS
MT Banks
This main table covers the Bank Master Data. The table consists of thirteen member fields in a fixed order:
RS
1) ID is an MDM Auto ID field used as simple counter. 2) Bank Country is a lookup to flat lookup table _Countries_. 3) Bank Name is a text field for the name of the bank. 4) Bank Key is a text field for the key of the bank. The combination of bank country and bank key has to be unique. Country, Name and Key fields are used as display fields of the main table. 5) Bank Address is a calculated field showing the full bank address. 6) Street is a text field for the bank's street and house number. 7) City is a text field for the postal code and city. 8) Region is a hierarchy lookup for the region. 9) SWIFT Code is a text field for the SWIFT code. 10) Bank Group is a text field for the bank group. 11) Bank Number is a text field for the bank number. 12) Bank Branch is a text field for the bank branch. 13) Postbank Account is a flat lookup linked with the Yes/No Indicator. MT Vendors
The field Address Note is a fixed text field.
DS
MT Vendors
The field Alternative Payee is a main lookup field to Vendors.
DS
MT Vendors
The field Business Type is a flat lookup field to Business Types.
DS
MT Vendors
The field Communication Type is a flat lookup field to Communication Types.
DS
MT Vendors
The field Customer is a fixed text field.
DS
MT Vendors
The field Delivery Service Number is a fixed text field.
DS
MT Vendors
The field Delivery Service Type is a flat lookup field to Delivery Service Types.
DS
MT Vendors
The field Different City is a fixed text field.
DS
MT Vendors
The field Fiscal Address is a main lookup field to Vendors.
DS
MT Vendors
The field Full Address is a calculated field. It shows the street, house number, postal code, city, country and region as concatenated value within a single string.
RS
MT Vendors
The field Full Name is a calculated field. It shows the title and all the names as concatenated value within a single string.
RS
MT Vendors
The field Industry Type is a flat lookup field to Industry Types.
DS
MT Vendors
The field Instruction Key is a fixed text field.
DS
MT Vendors
The field Last Review (External) is a literal date field.
DS
MT Vendors
The field Name of Representative is a fixed text field.
DS
October 2011
52
MDM 7.1 Vendor Content
Component
What is new?
Reason
MT Vendors
The field Plant is a flat lookup field to Plants. It is required for the Purchasing Organization enhancement.
RE
MT Vendors
The field Plant Level Relevant is a flat lookup field to Yes/No Indicator. It is required for the Purchasing Organization enhancement.
RE
MT Vendors
The field PO Box Address Undeliverable Reason is a flat lookup field to Undeliverable Reasons.
DS
MT Vendors
The field PO Box Lobby is a fixed text field.
DS
MT Vendors
The field POD-Relevant is a flat lookup field to POD Indicators.
DS
MT Vendors
The field QM System valid to is a literal date field.
DS
MT Vendors
The field Street Address Undeliverable Reason is a flat lookup to Undeliverable Reasons.
DS
MT Vendors
The field Tax Number is a fixed text field.
DS
MT Vendors
The Field Tax Office is a main lookup field to Vendors.
DS
Tuple Bank Details
This tuple definition covers Bank Details (Bank Accounts). It consists of seven member fields in a fixed order.
RS
1) Bank is a single-valued lookup to main table Banks. 2) Bank Account Number is a text field for the bank account number. It is the only display field of the tuple as long as MDM has the limitation of not being able to use lookup main fields as display fields within tuple definition. As soon as this limitation is resolved, the lookup main Bank will be an additional display field. 3) Bank Control Key is a text field for the bank control key. 4) Partner Bank Type is a text field for the partner bank type. 5) Reference Details is a text field for the reference details. 6) Account Holder is a text field for the account holder name. 7) Collection Authorization is a lookup to flat lookup Yes/No Indicator. Related multi-valued tuple fields within the object main table and/or other tuple definitions carry the same name Bank Details, too. Tuple Company Code Data
This tuple definition covers the Company Code related fields. It consists of 52 fields in a fixed order. Furthermore it includes new lookup tables:
RE, RS
Company Codes, Dunning Notice Grouping Keys, Exemption Authorities, Interest Calculation Frequencies, Interest Calculation Indicators, Minority Indicators, Payment Advices by XML, Payment Blocks, Payment Grouping Keys, Payment Method Supplements, Payment Terms, Periodic Account Statements, Planning Groups, Prepayment Relevances, Release Approval Groups, Sort Keys, Subsidy Indicators Clerks, House Banks, Payment Methods, Recipient Types, Reconciliation Accounts, Tolerance Groups (Business Partner or G/L Account), Tolerance Groups (Invoice), Withholding Tax Codes, Withholding Tax Countries
October 2011
53
MDM 7.1 Vendor Content
Component Tuple E-Mail Addresses
What is new? This tuple definition covers E-Mail Addresses. It consists of five member fields in a fixed order.
Reason RS
1) Is Standard E-Mail Address is a lookup to the flat lookup Yes/No Indicator. 2) E-Mail Address is a text field for the E-Mail Address itself. First and second fields are the only display fields of the tuple definition. 3) Sequence Number is a text field that is a counter of the e-Mail addresses. The format is fixed (three digits with leading zeros). 4) Not Used is a lookup to the flat lookup Yes/No Indicator. 5) Is TNEF enabled? Is a lookup to the flat lookup Yes/No Indicator. Related multi-valued tuple fields within the object main table and/or other tuple definitions carry the same name E-Mail Addresses, too. Tuple EU Tax Numbers
This tuple definition covers additional European VAT Registration Numbers for a main record. It consists of two member fields in a fixed sequence. Country is a lookup to the flat lookup table Countries. It indicates the country of the VAT Registration Number that is the second field. Both fields are display fields whereas the VAT is the first, the Country the second.
RS
Related multi-valued tuple fields within the object main table carry the same name EU Tax Numbers, too. Tuple Fax Numbers
This tuple definition covers Fax Numbers. It consists of seven member fields in a fixed sequence.
RS
1) Is Standard Fax Number is a lookup to flat lookup Yes/No Indicator. It is the first display field of the tuple. 2) Fax Country is a lookup to flat lookup Countries. 3) Fax Number is a text field for the fax dialing code and number. 4) Fax Extension is a text field for the fax number extension. 5) Complete Fax Number is a text field for the complete fax number. It is the second display field of the tuple. 6) Sequence Number is a text field that is a counter of the fax numbers. The format is fixed (three digits with leading zeros). 7) Not Used is a lookup to the flat lookup Yes/No Indicator. Related multi-valued tuple fields within the object main table and/or other tuple definitions carry the same name Fax Numbers, too. Tuple Phone Numbers
This tuple definition covers Phone Numbers. It consists of nine member fields in a fixed sequence.
RS
1) Is Standard Phone Number is a lookup to flat lookup Yes/No Indicator. It is the first display field of the tuple. 2) Phone Country is a lookup to flat lookup Countries. 3) Phone Number is a text field for the phone dialing code and number. 4) Phone Extension is a text field for the phone number extension. 5) Complete Phone Number is a text field for the complete phone number. It is the second display field of the tuple. 6) Phone Number Type is a lookup to the flat lookup Phone Number
October 2011
54
MDM 7.1 Vendor Content
Component
What is new?
Reason
Types. 7) Is SMS enabled is a lookup to the flat lookup Yes/No Indicator. 8) Sequence Number is a text field that is a counter of the phone numbers. The format is fixed (three digits with leading zeros). 9) Not Used is a lookup to the flat lookup Yes/No Indicator. Related multi-valued tuple fields within the object main table and/or other tuple definitions carry the same name Phone Numbers, too. Tuple Purchasing Organization Data
This tuple definition covers the Purchasing Organization related fields. It consists of 50 fields in a fixed order. Furthermore it includes new lookup tables:
RE
Activity Profiles, Confirmation Control Keys, Currencies, Groups for Calculation Schema, Incoterms, Payment Terms, Plants, Price Determination Date Controls, Price Marking Agreements, Profiles for Material Data Transfer, Purchasing Groups, Purchasing Organizations, Restriction Profiles, Shipping Conditions, Sort Criteria for Materials, Transportation Chains, Unit of Measure Groups Customs Offices, Modes of Transport, Planning Calendars, Rounding Profiles Tuple Web
This duple definition covers the FTP and URL Address related fields for communication data. It consists of 14 fields in a fixed order. Furthermore it includes a new flat lookup table URI Types.
Import Maps
All changes as described above are reflected within the Import Maps.
MDMGX
All changes as described above are reflected within the MDMGX configuration text file.
MDMGX
The repository initialization (load of reference data) is now using the MDMGX Process Levels. Process levels handle the import of dependent customizing entries.
MDMGX
MDMGX extractors have been enhanced to cover the Company Code and Purchasing Organization customizing extraction.
RE
PI Content
The XSLTs MDM71CreDebmdmAddressFilterIn.xsl and MDM71CreDebmdmToCreDebmasSplit have been enhanced to handle the Company Code’s Payment Methods correctly.
RE
Portal Content
All changes as described above are reflected within the Portal Content.
Sample Data
All changes as described above are reflected within the Sample Data.
Syndication Maps
All changes as described above are reflected within the Syndication Maps.
Validations
Validations have been completely re-worked according to the current MDM features
RE, RS
Workflows
Workflows have been completely re-worked according to the current MDM features
RE, RS
October 2011
RE
55
MDM 7.1 Vendor Content
12.2 Changed Content in MDM 7.1 Vendor The table below lists the changed content of the MDM 7.1 Vendor. Reasons are: E5 = Error in the MDM 5.5. Vendor RE = Repository Enhancement RS = Repository Synchronization Component
What is changed?
Reason
LT Countries
This table is a flat lookup named Countries having key mapping enabled. It consists of three member fields in a fixed sequence. Each field has identical names and properties. First field Name covers the multilingual texts for countries. It is the only display field of the lookup table. Second field ISO Code refers to the three character ISO Code for countries. It is the only unique field in the table. Third field Code includes the SAP country code that is added to the key mapping, too.
RS
LT Genders
This table is a flat lookup named Genders. It is used instead of the former lookup table Sex. The related main table field is named Gender.
RS
LT Industrial Sectors
This table is a flat lookup named Industrial Sectors. It is used instead of the former lookup table Industries and/or Industry Sectors. The related main table field is named Industry Sector.
RS
LT Regions
This table is a hierarchy lookup named Regions. It consists of three member fields in a fixed sequence. First field Name covers the multilingual text for regions. It is the only display field of the lookup table. Second field Code includes the SAP region code. Third field Country is a lookup for the region's country. This field is useable for the unique identification of a region.
RS
The region lookup is designed as a hierarchy to allow a better maintenance of regions. MDM Data Manager shows first a list of existing countries and below each country the related regions. This enables the user to assign correct countries and regions for master data objects. A validation can be used to check this, too. During reference data import the Import Map creates the concatenated keys (format: ). During object import the related import map must concatenate the country and region keys itself to ensure a correct mapping to an existing region. The Syndication Map uses the region code only for distribution. LT Time Zones
This table is a flat lookup named Time Zones. It is used instead of the former lookup table Address Time Zones. Related main table and/or tuple definition fields specifying the time zone of an address are named Address Time Zone.
RS
LT Trading Partners
The existing table Trading Partners has been enhanced with some member fields to create more meaningful information in the repository.
RS
October 2011
56
MDM 7.1 Vendor Content
Component
What is changed?
LT Transportation Zones
This table is a hierarchy lookup named Transportation Zones. It consists of three member fields in a fixed sequence. First field Name covers the multilingual text for transportation zones. It is the only display field of the lookup table. Second field Code includes the SAP transportation zone code. Third field Country is a lookup flat for the transportation zone's country.
Reason RS
The transportation zone lookup is designed as a hierarchy to allow a better maintenance of transportation zones. MDM Data Manager shows first a list of existing countries and below each country the related transportation zones. This enables the user to assign correct countries and transportation zones for master data objects. During reference data import the Import Map creates the concatenated keys (format: ). During object import the related import map must concatenate the country and transportation zone keys itself to ensure a correct mapping to an existing transportation zone. The Syndication Map uses the transportation zone code only for distribution. LT Yes/No Indicator
This table is a flat lookup named Yes/No Indicator. The Yes/No Indicator is basically the SAP system domain XFELD, a common yes/no flag. Using the Boolean field type in MDM is not an option as most of the message types require a NULL value for No respectively an X for Yes.
RS
MT Vendors
The field Authorization Group is changed from field type lookup flat to fixed text. There is no check table for Authorization Groups assigned in ERP
E5
MT Vendors
The field Check Digit is changed from field type Integer to fixed text with length 1 as the SAP ERP remote system field type is NUMC 1.
E5
MT Vendors
The field EU Tax Numbers is renamed from the old name VAT Numbers. The insufficient naming in old repository lead to a unique constraint violation in the MDM Schema Migration.
RS
MT Vendors
The field External Manufacturer is renamed from the old name Ext. Manufacturer.
RS
MT Vendors
The field Gender is renamed from the old name Sex. It is linked to the flat lookup Genders.
RS
MT Vendors
The field Industry Sector is renamed from the old name Industry. It is linked to the flat lookup Industrial Sectors.
RS
MT Vendors
The field PBC/ISR Number is renamed from the old name PBC/POR Number.
E5
MT Vendors
The field Natural Person is linked to the flat lookup Yes/No Indicator. Although the field uses a different domain in the remote systems, the domain fixed values are identical with the Yes/No Indicator.
RS
MT Vendors
The field Registered for Social Insurance is renamed from the old name Social Insurance.
E5
MT Vendors
The field Standard Carrier Access Code is renamed from the old name
E5
October 2011
57
MDM 7.1 Vendor Content
Component
What is changed?
Reason
SCAC. MT Vendors
The field Subject to Equalization Tax is renamed from the old name Sales Equalization Tax. The flat lookup table assignment is changed from the old lookup table Sales Equalization Tax to the new lookup table Yes/No Indicator.
Import Maps
All changes as described above are reflected within the Import Maps.
MDMGX
All changes as described above are reflected within the MDMGX configuration text file.
MDMGX
The Bank Details extractor has been enhanced to cover the additional fields in the Banks main table
RE
PI Content
The XSLT MDM71CreDebmdmAddressFilterIn.xsl has been enhanced to filter out comments related to international address versions during inbound mapping.
RE
Portal Content
All changes as described above are reflected within the Portal Content.
Sample Data Syndication Maps
October 2011
RS
All changes as described above are reflected within the Sample Data. All changes as described above are reflected within the Syndication Maps.
58
MDM 7.1 Vendor Content
12.3 Removed Content in MDM 7.1 Vendor The table below lists the removed content of the MDM 7.1 Vendor. Reasons are: E5 = Error in the MDM 5.5. Vendor RS = Repository Synchronization Component
What is removed?
Reason
LT Authorization Groups
The complete lookup table is removed.
E5
LT Natural Person
The complete lookup table is removed.
RS
LT Sales Equalization Tax
The complete lookup table is removed.
RS
QLT Bank Details
The complete lookup table is removed as it is replaced by the tuple definition Bank Details and main table Banks.
RS
QLT E-Mail Addresses
The complete lookup table is removed as it is replaced by the tuple definition E-Mail Addresses.
RS
QLT EU Tax Numbers
The complete lookup table is removed as it is replaced by the tuple definition EU Tax Numbers.
RS
QLT Fax Numbers
The complete lookup table is removed as it is replaced by the tuple definition Fax Numbers.
RS
QLT Phone Numbers
The complete lookup table is removed as it is replaced by the tuple definition Phone Numbers.
RS
Import Maps
All changes as described above are reflected within the Import Maps.
MDMGX
All changes as described above are reflected within the MDMGX configuration text file.
Portal Content
All changes as described above are reflected within the Portal Content.
Sample Data Syndication Maps
October 2011
All changes as described above are reflected within the Sample Data. All changes as described above are reflected within the Syndication Maps.
59
MDM 7.1 Vendor Content
12.4 Migration from MDM 5.5 to MDM 7.1 Vendor Both the MDM 5.5 and the MDM 7.1 Vendor content are considered as templates that can be enhanced and/or modified by customers. Therefore there is no general, default migration path available. Nevertheless there are a few guidelines you can follow if you want to migrate from your MDM 5.5 Vendor to the new MDM 7.1 Vendor. 1. Compare your custom MDM Content with the SAP standard content template. You should have a detailed look at your currently used content. Compare the repository tables and fields. If you have enhanced the old SAP content template, you should do the same with the new template. Keep in mind that the content consists of more than the repository only. Compare your MDMGX configuration, PI content, Portal content, Validations, & Workflows, and so on, too. Ensure that both your old and new MDM content are 100% synchronized. 2. Initialize the new repository. As the lookup table structure has changed in the new Vendor repository, the easiest way to go is a full initialization of the new repository from scratch. This ensures that you use the latest customizing data of your remote system. 3. Move Vendor records from the old to the new repository. You can use the CREMDM04 Syndication Map of the old repository to export your Vendor records into XML format. Then use the CREMDM04 Import Map of the new repository to import the Vendor records accordingly. Repeat this procedure for each of your remote systems to ensure that the related key mapping is successfully transported from the old to the new repository, too. 4. Update Vendor records in the new repository. The new Vendor repository contains more fields and tables compared to the old repository. If the new fields contain data in your remote system, re-extract the records from your remote systems to update the records in MDM.
October 2011
60
MDM 7.1 Vendor Content
13. SAP ERP Vendors CAUTION All screenshots are taken from the SAP ERP 6.0 EhP 5 development system. Screens as well as mandatory fields might vary in your local environment!
13.1 Administrative Data Transaction XK01: Create Vendor XK01 is the only way to define a Vendor Number and its related Account Group. Depending on the Account Group that is a mandatory field you either have to maintain a number, or leave the field blank so that the system assigns a number. A MDM Validation checks the mandatory Vendor Number and Account Group. Furthermore you can specify a Company Code and/or Purchasing Organization if you want to maintain data for these sections. Transaction XK02: Change Vendor In change mode (XK02) the Vendor number, Company Code and Purchasing Organization are used for selection only. You cannot change the values at all. The screen only allows selecting existing vendors and their specific sections for change.
October 2011
61
MDM 7.1 Vendor Content
General: Blocked Data Blocked Data shows all blocks for the current Vendor. To maintain data, choose in the top-menu: Extras Blocked Data.
General: Deletion Flags Deletion Flags show all deletion flags for the current Vendor. To maintain data, choose in the top-menu: Extras Deletion Flags.
October 2011
62
MDM 7.1 Vendor Content
13.2 General Data: Address Name Section
Name 1 is a mandatory field. Validation implemented in MDM. Search Term Section
Search Term 1 is a mandatory field. Validation implemented in MDM.
Street Address Section
Country is a mandatory field. Validation implemented in MDM Region is related to country. You can select only those regions that belong to the chosen country. Region is modeled as a LT [Hierarchy] in MDM. You select the country and a region for the country. As the country field itself is an independent field in MDM, a validation checks that the country field is equal to the region’s country. Transportation Zone is related to country. You can select only those transportation zones that belong to the chosen country. Transportation Zone is modeled as a LT [Hierarchy] in MDM. You select the country and a transportation zone for the country. As the country field itself is an independent field in MDM, a validation checks that the country field is equal to the transportation zone’s country. Undeliverable is named Street Address Undeliverable Reason in MDM.
October 2011
63
MDM 7.1 Vendor Content
PO Box Address Section
PO Box w/o no. is named PO Box without Number in MDM. If the flag is set, field PO Box must not contain a value. Validation implemented in MDM. If PO Box contains a value, the fields for Delivery Service must not contain any values. Validation implemented in MDM. If Delivery Service is used, both fields must have values. Validation implemented in MDM. Either PO Box Postal Code or Company Postal Code may have values. Validation implemented in MDM. Other City, Other Country and Other Region are named PO Box City, PO Box Country and Region for PO Box in MDM. PO Box Region is related to PO Box Country. You can select only those regions that belong to the chosen country. PO Box Region is modeled as a LT [Hierarchy] in MDM. You select the country and a region for the country. As the country field itself is an independent field in MDM, a validation checks that the country field is equal to the region’s country. Undeliverable is named PO Box Address Undeliverable Reason in MDM: International Address Versions
International Address Versions are currently not supported in MDM (see chapter Known Issues and Limitations for details). Communication Section
October 2011
64
MDM 7.1 Vendor Content
Language is automatically set with a default value in ERP. MDM treats this as a mandatory field and implements a related Validation.
Country is automatically set with a default value in ERP. Furthermore the Standard Flag and ID (Sequence Number) have to be set. MDM treats this as a mandatory field and implements a related Validation. Notes (ADRT) are not supported in MDM (see chapter Known Issues and Limitations for details).
Country is automatically set with a default value in ERP. Furthermore the Standard Flag and ID (Sequence Number) have to be set. MDM treats this as a mandatory field and implements a related Validation. Notes (ADRT) are not supported in MDM (see chapter Known Issues and Limitations for details).
E-Mail Address must contain a “@” and “.” character. Validation implemented in MDM. Notes (ADRT) are not supported in MDM (see chapter Known Issues and Limitations for details).
October 2011
65
MDM 7.1 Vendor Content
Additional Communication Data
The Standard Flag and ID (Sequence Number) have to be set. MDM treats this as a mandatory field and implements a related Validation. Notes (ADRT) are not supported in MDM (see chapter Known Issues and Limitations for details).
Address Comments
October 2011
66
MDM 7.1 Vendor Content
13.3 General Data: Control Account Control
Customer should exist in ERP Customers Table (KNA1). Validation cannot be implemented in MDM as there is no link to Customers. Tax Information
VAT Registration Number uses format checks. Sample Validations implemented in MDM.
EU Tax Numbers
October 2011
67
MDM 7.1 Vendor Content
Reference Data
Person Subject to Withholding Tax
13.4 General Data: Payment Transactions Bank Details
The screen above shows the maintenance for records in table LFBK (Bank Details for Vendors). Country, Bank Key and Bank Account are mandatory fields. Validation implemented in MDM. Bank Master
The screen above shows the maintenance for records in table BNKA (Bank Master).
October 2011
68
MDM 7.1 Vendor Content
Bank Country, Bank Key and Bank Name are mandatory fields. Validation implemented in MDM. Payment Transactions
Instruction Key is a text field in MDM (see chapter Repository Structure for details). Alternative Payee in Document
Spec per reference is set as soon as a Permitted Payee is maintained. Permitted Payee is not supported in MDM (see chapter Known Issues and Limitations for details).
Permitted Payee is not supported in MDM (see chapter Known Issues and Limitations for details).
October 2011
69
MDM 7.1 Vendor Content
13.5 Company Code Data: Accounting Information Administrative Data
The Company Code is already defined/selected and displayed only. Blocked Data Blocked Data shows all blocks for the current Vendor. To maintain data, choose in the top-menu: Extras Blocked Data. If you have assigned a specific company code to a Vendor, you can choose to either block all company codes centrally, or just the current company code. Deletion Flags Deletion Flags show all deletion flags for the current Vendor. To maintain data, choose in the top-menu: Extras Deletion Flags. If you have assigned a specific company code to a Vendor, you can choose to either delete or block all company codes centrally, or just the current company code. Accounting Information
Reconciliation Account is related to company code. You can select only those accounts that belong to the chosen company code. Reconciliation Account is modeled as a LT [Hierarchy] in MDM. You select the company code and a reconciliation account for the company code. As the company code field itself is an independent field in MDM, a validation checks that the company code field is equal to the reconciliation account’s company code. Cash Management Group is named Planning Group in MDM. Interest Calculation
October 2011
70
MDM 7.1 Vendor Content
Withholding Tax
Withholding Tax Code, Withholding Tax Country and Recipient Type are related to country. You can select only those values that belong to the chosen country. All lookups are modeled as a LT [Hierarchy] in MDM. You select the country and a related value for the country. As the country field itself is an independent field in MDM, a validation should check that the country field is equal to the related values country. This is currently not possible (see chapter Known Issues and Limitations for details). Reference Data
13.6 Company Code Data: Payment Transactions Payment Data
Tolerance Group is named Tolerance Group (Business Partner or G/L Account) in MDM. It is related to company code. You can select only those groups that belong to the chosen company code. Tolerance Group is modeled as a LT [Hierarchy] in MDM. You select the company code and a group for the company code. As the company code field itself is an independent field in MDM, a validation checks that the company code field is equal to the tolerance group’s company code. Automatic Payment Transactions
House Bank is related to company code. You can select only those banks that belong to the chosen company code. House Bank is modeled as a LT [Hierarchy] in MDM. You select the company code and a bank for the company code. As the company code field itself is an independent field in MDM, a validation checks that the company code field is equal to the house bank’s company code. You can either set the flag for Payment Advice by EDI or Payment Advice by XML. A validation in MDM checks this dependency.
October 2011
71
MDM 7.1 Vendor Content
Payment Method maintenance is done in an additional popup window. The ERP system offers several payment methods that rely on the Vendor’s country. The keys of the picked payment methods are stored as a single string. In MDM the Payment Methods themselves are modeled as LT [Hierarchy] to enforce the dependency to the country. Furthermore to lookup field itself is multivalued to allow a multiple assignment of payment methods.
Invoice Verification
Tolerance Group is named Tolerance Group (Invoice) in MDM. It is related to company code. You can select only those groups that belong to the chosen company code. Tolerance Group is modeled as a LT [Hierarchy] in MDM. You select the company code and a group for the company code. As the company code field itself is an independent field in MDM, a validation checks that the company code field is equal to the tolerance group’s company code.
13.7 Company Code Data: Correspondence Accounting Dunning Data
Dunning Data belongs to a sub-segment of the company code data: . An exemption is the field Grouping Key as it is stored in table LFB1 and therefore transported in segment .
October 2011
72
MDM 7.1 Vendor Content
Dunning Procedure is mandatory in ERP. Validation implemented in MDM. Dunning Level is a numeric value in ERP. Validation implemented in MDM. Correspondence
Accounting Clerk is related to company code. You can select only those clerks that belong to the chosen company code. Accounting Clerk is modeled as a LT [Hierarchy] in MDM. You select the company code and a clerk for the company code. As the company code field itself is an independent field in MDM, a validation checks that the company code field is equal to the accounting clerk’s company code
October 2011
73
MDM 7.1 Vendor Content
13.8 Purchasing Organization Data Administrative
The Purchasing Organization is already defined/selected and displayed only. Blocked Data Blocked Data shows all blocks for the current Vendor. To maintain data, choose in the top-menu: Extras Blocked Data. If you have assigned a specific purchasing organization to a Vendor, you can choose to either block all purchasing organizations centrally, or just the current one. Deletion Flags Deletion Flags show all deletion flags for the current Vendor. To maintain data, choose in the top-menu: Extras Deletion Flags. If you have assigned a specific purchasing organization to a Vendor, you can choose to delete all purchasing organizations centrally, or just the current one Conditions
Order Currency is a mandatory field. Validation implemented in MDM. Both fields for Incoterms can either be empty or must have values. Validation implemented in MDM. Order optimum restriction is named Restriction Profile for PO-Based Load Building. Sales Data
October 2011
74
MDM 7.1 Vendor Content
Control Data
Modes of Transport and Office of Entry are related to country. You can select only those values that belong to the chosen country. All lookups are modeled as a LT [Hierarchy] in MDM. You select the country and a related value for the country. As the country field itself is an independent field in MDM, a validation should check that the country field is equal to the related values country. This is currently not possible (see chapter Known Issues and Limitations for details). Default Data Material
Planned Delivery Time accepts numeric values only. Validation implemented in MDM. Rounding Profile, Planning Calendar and Planning Cycle (both hidden!) are related to plant. You can select only those values that belong to the chosen plant. All lookups are modeled as a LT [Hierarchy] in MDM. You select the plant and a related value for the plant. As the plant field itself is an independent field in MDM, a validation should check that the plant field is equal to the related values plant. This is currently not possible (see chapter Known Issues and Limitations for details). Service Data
Service Level accepts numeric values only with one decimal place. The format must be .. Validation implemented in MDM.
October 2011
75
MDM 7.1 Vendor Content
Procurement Monitoring
Both fields can either be empty or must have values. Furthermore Staging Time accepts numeric values only. Validation implemented in MDM. Vendor specific Information If you add a purchasing organization to your Vendor, the purchasing organization itself changes some values of the actual Vendor table (LFA1 in ERP respectively main table Vendors in MDM). The maintenance in ERP is in the top-menu: Extras
Additional Purchasing Data
The fields as above are part of the Vendors main table: Plant
Plant
Data retent. at VSR level allowed
Sub-Range
Data retent. at plant level allowed
Plant Level relevant
October 2011
76
www.sdn.sap.com/irj/sdn/howtoguides
View more...
Comments
