SAP NetWeaver Master Data Management

Transcription

1 Upgrade Guide GDS 2.1 Document Version: Global Data Synchronization Option 2.1

2 Typographic Conventions Type Style Example Description Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options. Textual cross-references to other documents. Example EXAMPLE Example Example <Example> Emphasized words or expressions. Technical names of system objects. These include report names, program names, transaction codes, table names, and key concepts of a programming language when they are surrounded by body text, for example, SELECT and INCLUDE. Output on the screen. This includes file and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools. Exact user entry. These are words or characters that you enter in the system exactly as they appear in the documentation. Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. EXAM PLE Keys on the keyboard, for example, F2 or EN TER SAP AG or an SAP affiliate company. All rights reserved. Typographic Conventions

3 Document History Caution Before you start the implementation, make sure that you have the latest version of this document that is available on SAP Service Marketplace at The following table provides an overview of the most important document changes. Version Date Change Added information about upgrading from 2.0 to 2.1 up to SP03 (see sections 1 and 2). Moved the document content to a new template. Document History 2015 SAP AG or an SAP affiliate company. All rights reserved. 3

4 Table of Contents 1 Introduction Upgrading your GDS 2.0 Installation to GDS Upgrading the MDM Server and GDS Exporting and Importing the GDS Table Content Running the GDS 2.1 Configuration Tool GDS 2.1: SAP NetWeaver Process Integration Content Activities Validations Publication Screen Performance Improvement Testing the Application Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete) Archiving the Current GDS 1.0 Repository (Obsolete) Preparing the New Repository (Obsolete) Collecting Migration XML Files from GDS 1.0 (Obsolete) Running the GDS 2.1 Configuration Tool (Obsolete) Running Trade Item Status and Link Checks in the Configuration Tool (Obsolete) GDS 2.1: SAP NetWeaver Process Integration Content Activities (Obsolete) Validations (Obsolete) Testing the Application (Obsolete) SAP AG or an SAP affiliate company. All rights reserved. Table of Contents

5 1 Introduction This document describes the upgrade procedure for migration of trade item data from a GDS 2.0 system to a GDS 2.1 (up to SP03) system. that an accompanying guide describes the upgrade procedure for migrating from a GDS 2.1 (SP03) system to GDS 2.1 (SP04 or higher). It also provides guidelines on how to upgrade GDS 2.0 Process Integration (PI) content to the desired GDS 2.1. GDS 2.1 SP03 and lower versions do not support modular trade items as defined in GS1 ( Major Release 3 (MjR3). For MjR3 support, see the accompanying Upgrade Guide. that the upgrade procedure from GDS 1.0 has become obsolete as GDS 1.0 is not directly supported any more. Introduction 2015 SAP AG or an SAP affiliate company. All rights reserved. 5

6 2 Upgrading your GDS 2.0 Installation to GDS Upgrading the MDM Server and GDS Upgrade the MDM 7.1 installation to MDM 7.1 SP03 or above. For more information, see the MDM Upgrade Guide at Netweaver SAP NetWeaver MDM SAP NetWeaver MDM 7.1 Upgrade MDM 7.1 Upgrade Guide. For GDS 2.1, install a new application server as mentioned in the GDS 2.1 Installation Guide. For more information, see the installation guide for GDS on SAP Service Marketplace at Industry Solutions Industry Solution Guides SAP for Consumer Products SAP MDM GDS Exporting and Importing the GDS Table Content For GDS 2.0 and higher, configuration data, such as UI field configurations and menu item structure information, is stored in database tables. In your GDS 2.0 installation, these tables exist in a database named after the J2EE instance. When you upgrade to GDS 2.1 and deploy the GDS content onto the new application server, these tables are created under the database named after the J2EE instance. However, they are empty and the content of these tables must be manually transferred from the old database to the new one. SAP recommends that a database expert perform this activity. The exact method and tool used during the transfer depend on the type of database you are using. For more information about transporting data from your old installation to the new installation, see SAP Recommendation Do not change the underlying database when upgrading from the GDS 2.0 installation to the GDS 2.1 installation. 2.3 Running the GDS 2.1 Configuration Tool You use the GDS 2.1 configuration tool to migrate a GDS 2.0 system to GDS 2.1. The following steps are performed as part of the migration process: Creation of additional menu item structure necessary for GDS 2.1 Creation of additional application operations necessary for GDS 2.1 Assigning additional operations, menu items, validations, and so on, to the Admin role SAP AG or an SAP affiliate company. All rights reserved. Upgrading your GDS 2.0 Installation to GDS 2.1

7 Creation of additional repository metadata (system and user tables) necessary for GDS 2.1 Changing the repository structure to enable price synchronization with GDS 2.1 Changing the repository structure to enable some new features of GDS 2.1, for example, catalog. Running the Configuration Tool 1. Paste the following link into your browser: 2. Log on with the GDS administrator user name and password. 3. Choose the Initial Configuration tab. 4. To initiate the update process, choose Upgrade existing GDS 2.0 to GDS 2.1, and then Start Repository Update. Once you have initiated the update process, do not log out as you will otherwise lose control of migration. Migration will continue to run in the background but you will be unable to obtain any information on its progress. The update process may take some time depending on your repository. The Process Status dialog box does not refresh automatically, so you must repeat this step at intervals to monitor the state of the process. A message appears in the Process Status dialog box to confirm that the update was successful or point out that an error occurred. Examining the Detailed Output Messages in the Server Log 1. Start the SAP Netweaver Administrator (NWA): 2. Log on with the administrator user of your SAP NetWeaver Java server. 3. To navigate to the log viewer, choose System Management Monitoring Logs and Traces. 4. Filter for the entries generated by the configuration process: o Select SAP Logs from the predefined views o If not visible, expand the SAP Logs tray o Create a filter in the Filter by Content table by selecting the filter Category, the condition Contains, and entering Migrate as a value o Choose Apply Filters. 5. Review log items. In case of faulty ones (red), try to fix the reported error. 6. If an error occurred during the configuration process, run the process again. The repository must be loaded before retrying. Upgrading your GDS 2.0 Installation to GDS SAP AG or an SAP affiliate company. All rights reserved. 7

8 Successful updates will not be repeated. 2.4 GDS 2.1: SAP NetWeaver Process Integration Content Activities GDS 2.1 provides new PI Content, which you can download and import to your PI system. Importing the GDS 2.1 PI Content 1. Log on to the Enterprise Services Repository (Enterprise Services Builder) of your PI system. 2. Go to Tools Import Design Objects..., and choose Server or Client depending on the location of the downloaded GDS 2.1 PI Content. To complete the import process, select the corresponding TPZ file. Import the GDS 2.1 PI Content to your PI system before you proceed with the following upgrade changes. To use the GDS 2.1 PI Content, you must have SAP NetWeaver Process Integration 7.1 or higher. Updating the Mappings Objects 1. In the Enterprise Services Repository (Enterprise Services Builder) of your PI system, go to the Software Component Version (SWCV) where you store your customized GDS mapping objects. 2. Open the Message Mapping Objects that relate to your GDS operation and load the corresponding message types of the mapping objects to replace the original message types as described below: Message Mappings (or Your Similar Customized Objects) BommatBommat04_TradeItems New Message Types to Replace the Existing Message Types Location: Target Message Type Name: MT_TradeItems Namespace: Software Component Version: GDS 2.1 MatmasGdsMatmas05_TradeItems Location: Target Message Type Name: MT_TradeItems Namespace: Software Component Version: GDS 2.1 ResponseProxy_DataPoolResponse Location: Target Message Type Name: MT_ DataPoolResponse SAP AG or an SAP affiliate company. All rights reserved. Upgrading your GDS 2.0 Installation to GDS 2.1

9 Message Mappings (or Your Similar Customized Objects) New Message Types to Replace the Existing Message Types Namespace: Software Component Version: GDS 2.1 TradeItemExport_CatalogueRequestProxy Location: Source Message Type Name: MT_ TradeItemExport Namespace: Software Component Version: GDS Open the Operation Mapping Objects that relate to your GDS operation and load the corresponding operation types (message interfaces) of the mapping objects to replace the original message interfaces as described below: Operation Mappings (or Your Similar Customized Objects) BommatBommat04_TradeItems New Service Interfaces to Replace the Existing Service (Message) Interfaces Location: Target Operation Name: MI_TradeItems_In Namespace: Software Component Version: GDS 2.1 MatmasGdsMatmas05_TradeItems Location: Target Operation Name: MI_TradeItems_In Namespace: Software Component Version: GDS 2.1 ResponseProxy_DataPoolResponse Location: Target Operation Name: MI_DataPoolResponse_In Namespace: Software Component Version: GDS 2.1 TradeItemExport_CatalogueRequestProxy Location: Source Operation Name: MI_TradeItemExport_Out Namespace: Software Component Version: GDS 2.1 The GDS 2.1 message types and service interfaces have exactly the same names as those in GDS 2.0. However, the GDS 2.1 message types and service interfaces are located in a different software component version and namespace. 4. Save and activate your mapping objects. 5. In the Integration directory (Integration Builder) of your PI system, create the new set of the configuration. Update the corresponding configuration objects (such as receiver determination, interface determinations, and collaboration agreement) with the new service interfaces and namespaces. Upgrading your GDS 2.0 Installation to GDS SAP AG or an SAP affiliate company. All rights reserved. 9

10 For more information about the SAP NetWeaver PI content activities, see the Upgrade Master Guide for SAP NetWeaver Process Integration 7.1 on SAP Service Marketplace at SAP NetWeaver SAP NetWeaver PI 7.1 Upgrade Planning Upgrade Master Guide - SAP NetWeaver PI Validations Update the description and error messages of the following validations using SAP Netweaver MDM data manager. Validation Name {OneSyncValidationsBean}Quantity_Of_Next_ Level_Item_in_Hierarchy {OneSyncValidationsBean}All_Lower_Level_O f_hierarchy_must_be_a_base Composition Depth, Composition Width, Num of Complete Layers Cont in Item - Qty of Next Level Item(s) Dependency Composition Depth, Composition Width, Num of Complete Layers Cont in Item - Is Trade Item Packed Irregularly Dependency New Validation Description The value of the attribute Qty of Next Level Item(s) for a parent item must be equal to the sum of the quantities (contained in the link) for all the child items. The lowest level in a hierarchy must be marked with Base Unit Indicator = YES If available, product of Composition Depth, Composition Width, Num of Complete Layers Cont in Item must be equal to Qty of Next Level Item(s) Attributes Composition Depth, Composition Width, Num of Complete Layers Cont in Item must not be populated when Is Trade Item Packed Irregularly is true 2.6 Publication Screen Performance Improvement To enable the performance improvement for the publication screens, create a calculated field in the repository using SAP Netweaver MDM console: Name: Publication Status Cache Code: PublicationStatusCache Type: Text Large Multi-Lingual: No Calculated: Yes Calculation: Publications.Party.GLN & Publications.PublicationState.Name. 2.7 Testing the Application 1. When the configuration process is complete, restart the application. 2. Start the console using the following URL: SAP AG or an SAP affiliate company. All rights reserved. Upgrading your GDS 2.0 Installation to GDS 2.1

11 3. Log on with your GDS user, and check that everything works correctly. Upgrading your GDS 2.0 Installation to GDS SAP AG or an SAP affiliate company. All rights reserved. 11

12 3 Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete) 3.1 Archiving the Current GDS 1.0 Repository (Obsolete) 1. Archive the GDS 1.0 repository from the current server: o Start the MDM 5.5 console o Choose SAP MDM Servers and then right-click and select Mount MDM Server. o Select your MDM 5.5 server from the list or enter its host name o Select the repository containing GDS data and choose Archive Repository from the Context menu o Enter a file name. You can find the created archive (<MDM 5.5 Install root>/server/archives) in your server s archives directory 2. Install MDM 7.1 and GDS 2.1 onto the new application server. For more information, see the Installation Guide for GDS on SAP Service Marketplace at Industry Solutions Industry Solution Guides SAP for Consumer Products SAP MDM GDS Preparing the New Repository (Obsolete) 1. Unarchive the previously archived repository: o Start the MDM 7.1 console o Choose SAP MDM Servers and then right-click and select Mount MDM Server o Select your MDM 7.1 server from the list or enter its host name o Copy the previously created repository archive file to your MDM 7.1 server s archive directory: <MDM 7.1 Install root>/mds00/mdm/archives o Select the mounted MDM 7.1 server and choose Unarchive Repository from the Context menu o Enter your database administrator user name and password o Choose Next and select your repository archive from the dropdown list o Enter the name of your repository. It should be the same value that you set in the application properties previously while installing the application. 2. Update the repository by selecting your repository and then choosing Update. 3. Connect to the repository o Select your repository and choose Connect to Repository from the Context menu o Use the same administrator user name and password as under GDS Create the GDSAdmin user SAP AG or an SAP affiliate company. All rights reserved. Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete)

13 o Open the content tree structure of the repository o Go to Admin Users o While Users is selected in the navigation tree, right-click on the Users table o Select Add User from the Context menu o In the User Detail screen area, change the name New User to GDSAdmin o In the User Detail screen area, select Password and choose a password You must use this password during the configuration process. o In the User Detail screen area, change Password Never Expires to Yes o In the User Detail screen area, select Roles to open the Role Selection view o Move the Admin and Everyone roles from the left table to the right table by double-clicking on them o Save your changes by clicking twice in an empty area of the Users table. 5. Create the Support role: o Open the content tree structure of the repository o Go to Admin Roles o While Roles is selected in the navigation tree, right-click on the Roles table o Select Add Role from the Context menu o In the Role Detail screen area, change the name New Role to Support o Save your changes by clicking twice in an empty area of the Roles table. o Choose Load Repository Immediate from the Context menu. 6. Delete existing import maps (if any) from the repository: o Start the MDM 7.1 Import Manager o Specify your MDM server host, repository, user, and password, and then choose Next You may get a message stating that import maps are outdated, and must be updated. In this case, choose Yes to start the update process. During the update process, a dialog box may appear several times stating that the XML schema is missing for a given map. In this case, leave the Available XML schemas for this map dropdown list as it is (selected value should be None). The Connect to Source screen appears. o In the Type dropdown list, choose Fixed Text o Prepare a text file containing a single 1 character; select this file in the File Name field o Enter 1 into the Columns field o Choose the appropriate system type (for which you have import maps defined) from the Remote System dropdown list If you have multiple systems with assigned import maps, you must repeat all of these steps for each system. o Choose Finish The MDM Import Manager main screen appears. o Choose File Open o In the File Open dialog box, delete all of your maps using the Dele te key on your keyboard Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete) 2015 SAP AG or an SAP affiliate company. All rights reserved. 13

14 o Close the dialog box and exit the application. 3.3 Collecting Migration XML Files from GDS 1.0 (Obsolete) You must collect the custom XML files from your existing GDS 1.0 installation. These files allow you to automatically create the following objects in the next step, Running the GDS 2.1 Configuration Tool: System and user tabs on the user interface Roles in the system with default assigned tabs, screens operations, and validations Metadata in the repository (tables and fields). You should locate the following files: Metadata MetadataConfiguration.xsd MetadataConfiguration_ 1Sync_System.xml MetadataConfiguration_ 1Sync_User.xml UI Configurations UI_Configurations.xsd UI_Configuration_1Sync_ System.xml UI_Configuration_1Sync_ User.xml Roles Roles.xml <GDS_HOME>/Configurations/ Metadata/Metadata.xsd <GDS_HOME>/Configurations/ Metadata/MetadataConfiguration_ 1Sync_System.xml <GDS_HOME>/Configurations/ Metadata/MetadataConfiguration _1Sync_User.xml <GDS_HOME>/Configurations/UI/ UI_Configuration.xsd GDS_HOME>/Configurations/UI/ UI_Configuration_1Sync_System.xml <GDS_HOME>/Configurations/UI/ UI_Configuration_1Sync_User.xml <GDS_HOME>/Configurations/Roles/ Roles.xml Schema definition for metadata configuration files 1Sync metadata predelivered definition 1Sync metadata user definitions Schema definition for UI configuration files 1Sync predelivered UI configurations 1Sync user UI Configurations Stores roles properties You can extend the above XML files if you want, but you should adhere to the XML schema definition file rules SAP AG or an SAP affiliate company. All rights reserved. Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete)

15 3.4 Running the GDS 2.1 Configuration Tool (Obsolete) You use the GDS 2.1 configuration tool to migrate a GDS 1.0 installation to GDS 2.1 and also to check trade item and link statuses in the repository. Upload your custom XML configuration files that you have obtained from the existing GDS 1.0. For more information about obtaining XML configuration files, see Collecting Migration XML Files from GDS 1.0. The following steps are performed as part of the migration process: Creation of default user interface configuration: System tabs and User tabs Creation of the default application menu structure Creation of application operations Creation of default roles (with assigned tabs, screens operations, and validations) Creation of repository metadata (system and user tables), using custom XML files Creation of the GDSAdmin user Creation of standard workflows Creation of ownership fields in the repository (item owner, registration owner. publication owner and link owner) and setting a default owner to the logged on user Changing the repository structure to accommodate changes in the 1Sync releases Changing the repository structure to enable price synchronization with GDS 2.1 Changing the repository structure to enable some new features of GDS 2.1, for example, catalog Setting up the default Search and Result fields for the application. These configurations are automatically available for all new users at first, and then they can change it according to their preference. Running the Configuration Tool 1. Paste the following link into your browser: 2. Log on with the GDS administrator username and password. 3. Choose the Initial Configuration tab. If GDS 1.0 was previously installed, choose Upgrade existing GDS 1.0 to GDS 2.1 and provide the required custom XML configuration files that you located in the section Collecting Migration XML Files from GDS 1.0. You must provide all the XML configuration files or you will receive an error message. 4. To initiate the update process, choose Start Repository Update. Once you have initiated the update process, do not to log out or you will lose control of migration. Migration will continue to run in the background but you will be unable to obtain any information on its progress. The update process may take some time depending on your repository. Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete) 2015 SAP AG or an SAP affiliate company. All rights reserved. 15

16 The Process Status dialog box does not refresh automatically, so you must repeat this step at intervals to monitor the state of the process. A message appears in the Process Status dialog box to confirm that the update was successful or point out that an error occurred. Examining the Detailed Output Messages in the Server Log 1. Start the SAP Netweaver Administrator (NWA): 2. Log on with the administrator user of your SAP NetWeaver Java server. 3. To navigate to the log viewer, choose System Management Monitoring Logs and Traces. 4. Filter for the entries generated by the configuration process: o Select SAP Logs from the predefined views o If not visible, expand the SAP Logs tray o Create a filter in the Filter by Content table by selecting Filter Category, Condition Contains and entering Migrate as Value o Choose Apply Filters. 5. Review log items. In the case of faulty ones (red) try to fix the reported error. You may encounter an error message in the Process Status dialog box or log indicating that an error occurred while unique fields were being set in a table. This is valid for fields already containing multiple values, which therefore cannot be made unique without human interaction. You should resolve the situation in the MDM Data Manager. 6. If an error occurred during the configuration process, run the process again. The repository must be loaded before retrying. Successful updates will not be repeated. 3.5 Running Trade Item Status and Link Checks in the Configuration Tool (Obsolete) After running the initial configuration, check whether the statuses of trade items are set correctly. The configuration tool has a feature that helps you to carry out this check. You can run the check as follows: Start the configuration tool as described in the section Running the GDS 2.1 Configuration Tool. 1. Select the Trade Item Status and Link Check tab. 2. Choose Check Status. A list of trade items showing incorrectly set statuses and proposed new statuses is displayed. 3. For these items, check the statuses at 1SYNC and correct them manually in the MDM Data Manager SAP AG or an SAP affiliate company. All rights reserved. Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete)

17 Check whether the packaging hierarchy (links) contains a loop. The configuration tool has a feature that helps you to carry out this check. You can run the check as follows: 4. Start the configuration tool as described in section Running the GDS 2.1 Configuration Tool. 5. Select the Trade Item Status and Link Check tab. 6. Choose Check Loop in Links. A list of loops is displayed. 7. For these links, check the statuses at 1SYNC and correct them manually in the MDM Data Manager. 3.6 GDS 2.1: SAP NetWeaver Process Integration Content Activities (Obsolete) SAP NetWeaver MDM GDS 2.1 has significant changes compared with version 1.0. To upgrade, import GDS 2.1 into the SAP NetWeaver Process Integration (PI) Integration Builder. The GDS 2.1 PI content contains various objects and preconfigured scenarios for the GDS 2.1 application. Uploading the PI content does not influence the existing application and PI configuration. If you have made any manual changes or Customizing settings, you must reapply those modifications to GDS 2.1 accordingly. Upgrading to GDS 2.1 also requires the creation of a new set of PI configuration objects. To create the corresponding configuration, logon to the PI Integration Directory and select the corresponding preconfigured integration scenarios to start the configuration procedure. After completion, the original PI content objects and configuration objects for GDS CONTENT 1.0 are obsolete and can therefore be removed. For more information, see the Upgrade Master Guide for SAP NetWeaver Process Integration 7.1 on SAP Service Marketplace at SAP NetWeaver SAP NetWeaver PI 7.1 Upgrade Planning Upgrade Master Guide - SAP NetWeaver PI Validations (Obsolete) You cannot create or change the validation using the MDM Java application programming interface. The MDM 7.1 transport mechanism also does not transfer validations. You must delete the following validations manually using the SAP Netweaver MDM data manager: Season Calendar Year is a 4-digit number Global Item Classification - GPC Dependency {OneSyncValidationsBean}GlobalItemClassification_must_have_value_belong_to_GPC_cate gorization {OneSyncValidationsBean}validateReplacesGtin {OneSyncValidationsBean}validateReplacedbyGtin. Then you must create the following validations manually: Name/Code Enter name as Composition Depth - Composition Depth UOM Dependency Description When you specify Composition Depth, you must Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete) 2015 SAP AG or an SAP affiliate company. All rights reserved. 17

18 also specify a valid Composition Depth UOM. Group Validation Expression(Create manually) Error Message Automatic Execution Callable Data IF(IS_NOT_NULL(Global Data.Composition Depth),IS_NOT_NULL(Global Data.Composition Depth UOM.Name)) AND IF(IS_NULL(Global Data.Composition Depth),IS_NULL(Global Data.Composition Depth UOM.Name)) When specifying Composition Depth you must specify a valid Composition Depth UOM Warning No Name/Code Description Group Validation Expression(Create manually) Error Message Automatic Execution Callable Goods Pickup Lead Time - Goods Pickup Lead Time UOM Dependency When you specify Goods Pickup Lead Time, you must also specify a valid Goods Pickup Lead Time UOM. Data IF(IS_NOT_NULL(Partner Specific Data.Goods Pick Up Lead Time),IS_NOT_NULL(Partner Specific Data.Goods Pickup Lead Time UOM.Name)) AND IF(IS_NULL(Partner Specific Data.Goods Pick Up Lead Time),IS_NULL(Partner Specific Data.Goods Pickup Lead Time UOM.Name)) When specifying Goods Pickup Lead Time, you must also specify a valid Goods Pickup Lead Time UOM Warning No Name/Code Description Composition Depth, Composition Width, Num of Complete Layers Cont in Item - Is Trade Item Packed Irregularly Dependency Attributes Composition Depth, Composition Width, and Num of Complete Layers Cont in Item should not be populated if Is Trade Item Packed Irregularly is true SAP AG or an SAP affiliate company. All rights reserved. Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete)

19 Group Validation Expression(Create manually) Error Message Automatic Execution Callable Data IF(Global Data.Is Trade Item Packed Irregularly.Name = True, IS_NULL(Global Data.Num of Complete Layers Cont in Item) AND IS_NULL(Global Data.Composition Depth)AND IS_NULL(Global Data.Composition Width)) Attributes Composition Depth, Composition Width, Num of Complete Layers Cont in Item should not be populated when Is Trade Item Packed Irregularly is true Warning No Name/Code Description Group Validation Expression(Create manually) Error Message Automatic Execution Callable Composition Depth, Composition Width, Num of Complete Layers Cont in Item - Qty of Next Level Item(s) Dependency If available, product of Composition Depth, Composition Width, and Num of Complete Layers Cont in Item should be equal to Qty of Next Level Item(s) Data IF(IS_NOT_NULL(Global Data.Composition Depth)AND IS_NOT_NULL(Global Data.Composition Width)AND IS_NOT_NULL(Global Data.Num of Complete Layers Cont in Item), IS_NOT_NULL(Global Data.Qty of Next Level Item(s))AND Global Data.Composition Width*Global Data.Composition Depth*Global Data.Num of Complete Layers Cont in Item=Global Data.Qty of Next Level Item(s)) If available, product of Composition Depth, Composition Width, Num of Complete Layers Cont in Item' should be equal to Qty of Next Level Item(s) Warning No Name/Code Description Composition Depth UOM valid value If specified, Composition Depth UOM can only be Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete) 2015 SAP AG or an SAP affiliate company. All rights reserved. 19

20 equal to Unit Group Validation Expression(Create manually) Error Message Automatic Execution Callable Data IF(IS_NOT_NULL(Global Data.Composition Depth UOM.Name),Global Data.Composition Depth UOM.Name=Unit) Enter error message in English[US] as If specified, Composition Depth UOM can only be equal to Unit Warning No Name/Code Description Group Validation Expression(Create manually) Error Message Automatic Execution Callable Composition Width UOM valid value If specified, Composition Depth UOM can only be equal to Unit. Data IF(IS_NOT_NULL(Global Data.Composition Width UOM.Name),Global Data.Composition Width UOM.Name=Unit) If specified, Composition Width UOM can only be equal to Unit Warning No Name/Code Description Group {OneSyncValidationsBean} startavailabilitydate_must_be_populated_t o_generic_partner If target market attributes are provided, startavailabilitydate must be populated for Generic Partner Data Validation Expression(Create manually) Error Message Automatic Execution Callable If target market attributes are provided, startavailabilitydate must be populated to Generic Partner Warning No SAP AG or an SAP affiliate company. All rights reserved. Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete)

21 Name/Code Description Group Additional Net Content 1 - Additional Net Content 1UOM Dependency Additional Net Content 1 and Additional Net Content 1 UOM are dependent; if you specify one, you have to specify the other one as well. Data Validation Expression(Create manually) IF(IS_NOT_NULL(Global Data.Net Content 1),IS_NOT_NULL(Global Data.Net Content UOM 1.Name)) AND IF(IS_NULL(Global Data.Net Content 1),IS_NULL(Global Data.Net Content UOM 1.Name)) Error Message Automatic Execution Callable Additional Net Content 1 and Additional Net Content 1 UOM are dependent, if you specify one, the other should be specified too Warning No Name/Code Description Group Additional Net Content 2 - Additional Net Content 2UOM Dependency Additional Net Content 2 and Additional Net Content 2 UOM, are dependent; if you specify one, you have to specify the other one as well. Data Validation Expression(Create manually) IF(IS_NOT_NULL(Global Data.Net Content 2),IS_NOT_NULL(Global Data.Net Content UOM 2.Name)) AND IF(IS_NULL(Global Data.Net Content 2),IS_NULL(Global Data.Net Content UOM 2.Name)) Error Message Automatic Execution Callable Additional Net Content 2 and Additional Net Content 2 UOM are dependent, if you specify one, the other should be specified too Warning No Name/Code Description Group Additional Net Content 3 - Additional Net Content 3UOM Dependency Additional Net Content 3 and Additional Net Content 3 UOM, are dependent; if you specify one, you have to specify the other one as well. Data Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete) 2015 SAP AG or an SAP affiliate company. All rights reserved. 21

22 Validation Expression(Create manually) IF(IS_NOT_NULL(Global Data.Net Content 3),IS_NOT_NULL(Global Data.Net Content UOM 3.Name)) AND IF(IS_NULL(Global Data.Net Content 3),IS_NULL(Global Data.Net Content UOM 3.Name)) Error Message Automatic Execution Callable Additional Net Content 3 and Additional Net Content 3 UOM are dependent, if you specify one, the other should be specified too Warning No Name/Code Description Group {OneSyncValidationsBean}Quantity_Of_Next_L evel_item_in_hierarchy The value of the attribute Qty of Next Level Item(s) for a parent item must be equal with the sum of the quantities (contained in the link) for all the child items Data Validation Expression(Create manually) Error Message Automatic Execution Callable The value of the attribute Qty of Next Level Item(s) for a parent item must be equal with the sum of the quantities (contained in the link) for all the child items Warning No Update the description and error message for the following validations: Validation Name {OneSyncValidationsBean}All_Lower_Level _Of_Hierarchy_Must_Be_A_Base Composition Depth, Composition Width, Num of Complete Layers Cont in Item - Qty of Next Level Item(s) Dependency Composition Depth, Composition Width, Num of Complete Layers Cont in Item - Is Trade Item Packed Irregularly Dependency New Validation Description The lowest level in a hierarchy must be marked with Base Unit Indicator = YES If available, product of Composition Depth, Composition Width, Num of Complete Layers Cont in Item must be equal to Qty of Next Level Item(s) Attributes Composition Depth, Composition Width, Num of Complete Layers Cont in Item must not be populated when Is Trade Item Packed Irregularly is true SAP AG or an SAP affiliate company. All rights reserved. Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete)

23 3.8 Testing the Application (Obsolete) 1. When the configuration process is complete, restart the application. 2. Start the console using the following URL: 3. Log on with your GDS user, and check whether everything works correctly. Upgrading your GDS 1.0 Installation to GDS 2.1 (Obsolete) 2015 SAP AG or an SAP affiliate company. All rights reserved. 23

24 SAP AG or an SAP affiliate company. 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. National product specifications may vary. 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. SAP 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 other countries. Please see for additional trademark information and notices.