Sweden.08. Nothing herein should be construed as constituting an additional warranty. OS/2. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. Inc. VideoFrame. DB2 Universal Database. XML. X/Open. IBM. XHTML and W3C are trademarks or registered trademarks of W3C®. iSeries. AS/400. OSF/1. Tivoli. SAP NetWeaver. and MultiWin are trademarks or registered trademarks of Citrix Systems. Java is a registered trademark of Sun Microsystems. MVS/ESA. DB2. mySAP. and SAP Group shall not be liable for errors or omissions with respect to the materials. MetaFrame. Intelligent Miner. These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only. if any. OS/400. and Motif are registered trademarks of the Open Group. Data contained in this document serves informational purposes only. and Informix are trademarks or registe red trademarks of IBM Corporation in the United States and/or other countries. WebSphere. Outlook. UNIX. JavaScript is a registered trademark of Sun Microsystems. R/3. All rights reserved. OS/390. SAP. AFP. xApps. WinFrame. Inc. National product specifications may vary. z/OS. Program Neighborhood. HTML. These materials are subject to change without notice. Windows. 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. Citrix. Netfinity. The information contained h erein may be changed without prior notice. AIX. Oracle is a registered trademark of Oracle Corporation. Microsoft. Massachusetts Institute of Technology. Upgrade Guide 2 . without representation or warranty of any kind. S/390. xSeries. Inc. MaxDB is a trademark of MySQL AB. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. and PowerPoint are registered trademarks of Micros oft Corporation. xApp. pSeries. zSeries.2005 Copyright © Copyright 2005 SAP AG. All other product and service names mentioned are the trademarks of their respective companies.com.04. mySAP.. World Wide Web Consortium. 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. Parallel Sysplex. used under license for technology invented and implemented by Netscape. ICA.

and key concepts of a programming language when they are surrounded by body text. F2 or ENTER. menu paths. pushbuttons labels. transaction codes. and menu options. menu names. table names. for example. Technical names of system objects.08. Exact user entry. program names. These include field names. Example text <Example text> EXAMPLE TEXT Upgrade Guide 3 . SELECT and INCLUDE. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system. and table titles.2005 Icons in Body Text Icon Meaning Caution Note Example Recommendation Typographic Conventions Type Style Example text Description Words or characters quoted from the screen. graphic titles. screen titles. These include report names. Example text EXAMPLE TEXT Emphasized words or phrases in body text.04. Cross-references to other documentation. for example. Variable user entry. Keys on the keyboard. These are words or characters that you enter in the system exactly as they appear in the documentation.

...... 8 Actions Before Upgrade for Special Cases .............................................................................................................................................................................................................................................................................. 6 Categories ..................................... 9 Possible Errors and Remedial Action After Upgrade ........... 11 Upgrade Guide 4 ............................................................................................................................................................................................................................................................................................. 6 Technical Changes.................2005 Processes to Upgrade Grids and Categories .08.....................................................................................................04.............................................................. 5 Technical Changes................................................. 7 What Happens During the Category Upgrade? ....................................................................................................................................................................................................................... 11 Error.............. 11 Reason ....................................0B to AFS 5.......................................................................... 7 Actions Before Upgrading from AFS 3.................... 11 Solution................................................................ 5 Grid.......................... 8 Switching of Structures.....0 ................................... 6 What Happens During the Grid Upgrade? .............................................

and you can now only create category structures from characteristics. t he basic structure of the grids has not changed much. Upgrade Guide 5 . 5. IDoc processing for grids has changed and you must use the new grid IDoc type J3AGRI02. You sort the grid values in accordance with the order of the values entered in characteristics maintenance. Create your grid from the characteristics that you defined. the basic data for grids and category structures has been enhanced. Enter transaction CT04. Choose the number of characters of the technical keys of your characteristic values. Save the characteristic. Take great care when setting the relevancies. Set the characteristics group to AFS Characteristics for Dimensions (/AFS/SAP-D). Set the status to Released. proceed as follows: 1. Choose the Values tab page and enter the relevant values. 4. you can still use the old IDoc type J3AGRI01 for inbound processing of characteristics that have names of less than eight characters. 2. Grid Aside from the change from grid dimensions to characteristics.08. because you are not permitted to change them once the characteristic is used in a grid. You maintain the relevance of the characteristics by choosing Relevance in the Basic Data view. 3. You map the conversion by choosing Conversion in the Basic Data view of characteristics maintenance. Choose change mode for the characteristic and choose Relevance in the Basic Data view to maintain the relevancies. To create your grid using the characteristics.0. The Sort Sequence function that was associated with dimensions is no longer valid. The Customizing dialog for dimensions is no longer available.2005 Processes to Upgrade Grids and Categories As of SAP AFS 5. Grid dimensions have been replaced by characteristics. The conversion-relevant Customizing settings remain the same. 8. 6. 7. Ensure that CHAR is entered in the Data Type field. However. You can create characteristics for grids and category structures in transaction CT04.04.

To switch to the plant-independent structures in the old release. This routine will convert the characteristic internal number to characteristic name and then display. It also updates the relevant tables by replacing the dimensions with information about the characteristics. Only for AFS 3.2005 Technical Changes The following are the details of the old dimension tables that will be mapped to the new characteristic tables: Old Tables J_3ADITU. Migration to a plant-independent environment is therefore mandatory. If an existing characteristic is assigned to a dimension. the XPRA /AFS/NDIF_CREATE_CHAR is run for all clients. This recrea tes the AFS Configuration Master Data. For further information. then that characteristic replaces the dimension. The conversion routine ATINN is attached to the domain. Mass update report /AFS/NDIF_MASS_UPDATE.0. Mass reorganization report /AFS/NDIF_MASS_REORG. The grid header table J_3APGHD will now hold the characteristic internal number instead of the old dimension name. all valid stock category combinations automatically become valid requirement combinations. In addition. In the plant-independent environment. 2. What Happens During the Grid Upgrade? During upgrade. you must run the following two reports in the specified sequence: 1. This means that when a requirement field is created for a structure.0: To avoid any inconsistencies in the AFS Configuration Master Data. This means that the Upgrade Guide 6 . It converts all the dimensions into characteristics and updates the grid header. use the report /AFS/NDIF_SWITCH_STRUCTURES. there is always a one-to-one correspondence and relationship between the stock side and the requirement side. for the plant-independent coverage strategy.1/4.08.0 and going for upgrade to AFS 5. Categories Only plant-independent structures are supported for categories in AFS 5.04. The internal number of the characteristic is updated in the tables that have references to dimension names.0B installations having connectivity to ISA 3. This deletes all the existing AFS Configuration Master Data. see SAP Note 778122. The same applies to all tables with a reference to the dimension names. a corresponding stock field is also created in the background. J_3ADITP J_3ADICH J_3ADITY J_3ADICT J_3ASORT New Tables CABN CAWN CABNT CAWNT No corresponding mapping The domain J_3ABEZG was changed from char8 to char10 to hold the characteristic internal number (ATINN).

The relevancy information about category fields will not be located at structure level. 5. What Happens During the Category Upgrade? During upgrade. The XPRA detects that the field has different relevancies in the two structures and consequently creates a new characteristic with the different relevancy. Set the status to Released. J_4KREIT . Choose the Values tab page and enter the relevant values. Technical Changes The following are the details of the user-defined category field information that will be mapped to the characteristic table: Old Tables J_4KUDCF_H J_4KUDCFLH J_4KUDCF_V J_4KUDCFLV New Tables CABN CABNT CAWN CAWNT The category field table J_4KCATS will contain a new key field ATINN that will hold the characteristic information.04. 4.2005 valid combinations are the same on both sides. 6. The fields J_4KREFT. 3. Create category structures using these characteristics. To create category structures using characteristics. Enter transaction CT04. the XPRA creates new characteristics for each instance. The table /afs/dim_rels will now hold the relevancy information. 2. 8. If a reference field is used in more than one category structure and if the relevancies are different. Consider a case where a category field is used in more than one structure and the relevancies for the field differ in the two structures. It converts all category structure fields to characteristics and updates the category tables. proceed as follows: 1. the XPRA /AFS/NDIF_CREATE_CAT_CHAR runs for all clients.08. 7. Consequently. This is necessary because the Upgrade Guide 7 . you can only maintain stock category combinations in Customizing. Choose the number of characters of the technical keys of your characteristic values. Save the characteristic. Set the characteristics group to AFS Characteristics for Categories (/AFS/SAP-C). J_4KREFF. Choose change mode for the characteristic and choose Relevance in the Basic Data view to maintain relevancies. This means that the table J_4KCATR would be redundant. and J_4KREIF will no longer contain any information. Ensure that CHAR is entered in the Data Type field. but at characteristic level.

Repeat steps 1-7 for all user-defined fields of the old structure. 4.0B to AFS 5. 2. 6. The length should be the same as that of the user-defined field in the old category structure. 7. 8.2005 relevancy is linked to the actual characteristic and not to the structure field. The rest of the procedure is the same as for creating a structure. Follow the steps below to define your new plant-independent structure from the characteristics that you created: o o o Define your new fields while creating your new structure Enter C for the first field and choose Enter in the Origin of Values and Infotext frame Choose F4 in the Reference field and you can see your newly created characteristic. Choose the Values tab page and enter the relevant values. Ensure that CHAR is entered in the Data Type field. The report studies the old plant-dependent structure along with its coverage strategy and updates the materials with the new plant-independent category structure and strategy. Set the characteristics group to AFS Characteristics for Categories (/AFS/SAP-C) 5.04.0 You need to perform some steps before upgrading from AFS 3. Switching of Structures In AFS 3. proceed as follows: 1. Enter a suitable name for your characteristic. as was previously the case. Choose the number of characters of the technical keys of your characteristic values.08. Set the status to Released. 3.0B.0B to AFS 5. Create and save the characteristic.0. report /AFS/NDIF_SWITCH_STRUCTURES enables you to switch from plantdependent structures and strategies to plant-independent structures and strategies. To switch the structures. Actions Before Upgrading from AFS 3. You create the plant-independent structures from characteristics. All the values of the userdefined field should also be valid for the characteristic. Enter transaction CT04. Upgrade Guide 8 .

Go to the Customizing dialog for maintaining relevancies and maintain the new structure relevancies after comparison with the old structure relevancies. There would be materials with only plant dependent structures attached but no coverage strategies. 2. create plant-independent coverage strategies with different names than those of the plant-dependent coverage strategy. For more information. The relevancies in the new structure fields should match those in the old. or 'S'. Upgrade Guide 9 . We recommend that you restrict the materials on the basis of the old coverage strategy. Actions Before Upgrade for Special Cases Check your case. 4. The selection screen of the report contains a field in which you can enter the old coverage strategy. If the flag is not checked. Switching the structures does not have any impact on transactional data. Therefore. in the selection screen an option is provided which helps to treat these materials separately. 5. If the flag blank_st is checked . Create a new structure with characteristics. and 'S'. these special materials are considered for update and are updated with the new category structure and coverage strategy on the selection screen. Structures are not converted in special cases. it becomes mandatory to associate a plant independent coverage strategy.2005 9. If you do not make an entry in this field. Run report /AFS/NDIF_SWITCH_STRUCTURES to replace the structures. These table categories can be described as follows: • • • F: Standard via fixed domain values E: Standard via entity table of domain S: Standard via check table of table field. implement the solution. Problem 1: The category structure field has a check table category of the type 'F'.08. 10. This means that only those materials that have the old category structure and old coverage strategy are selected for updates. 3. If it is a special case. then those materials are skipped for update. To avoid inconsistencies in applications. 'E'. 'E'. see SAP Note 843028. When these materials are migrated to the plant independent world. For the characteristic that replaces the fields of check table category 'F'. all the materials that have the old category structure are updated with the new category structure and coverage strategy. Solution: To run the upgrade successfully. The upgrade will run correctly. ensure that all values for that field are filled manually. proceed as follows: 1. refer to the previous section on the ‘Switching of structures’. Switch the structure in the older release. For further information.04.

AFS 1. New plant-independent structures and their associated coverage strategies should be created in the system.0D and 2.5B customers can use report /AFS/NDIF_SWITCH_STRUCTURES to switch to plant-independent structures and strategies after upgrade to AFS 5. After evaluating the structure and category combinations. For more information. a new structure must be created in the older release.08.5B.0B releases. contact SAP. Problem 5 The structure field values are based on ranges. If you have any problems running the XPRA.2005 Problem 2 A user-defined field has a user exit to enter the values. For existing 3. this report can be run before the upgrade. Solution: Replace the user exit and enter the values manually in Customizing for user -defined fields. Solution: Use report /AFS/NDIF_SWITCH_STRUCTURES to switch the plant -dependent structures over to a plant-independent structure. There is no cause for concern after upgrade. For AFS 1. Upgrade Guide 10 .0D and 2. see SAP Note 803893. Problem 3 Non-related structure fields exist. Solution: In such cases it is advisable to replace the structure in the older release. This report analyses whether the plant-dependent structures can be replaced with the newly created structures. A report might be required to replace the problem structure with the new one. since the characteristics can be updated with the missin g values after upgrade. Problem 4 Plant-dependent structures are no longer supported. and the characteristics cannot support ranges. there are no preconditions for upgrade.0. The newly created structure field should only contain single values.04. Solution: Report the problem to SAP.

Upgrade Guide 11 . who will help you to determine the cause of this error and to find a solution. There should not be any cause for concern if only specific cases could not be migrated. In these cases.0.2005 Possible Errors and Remedial Action After Upgrade Error You have received type P errors after upgrade. to ensure that the upgrade runs smoothly. Reason You got this error because you did not follow the pre-upgrade actions for category structure migration that were described in SAP Note 789797. Then run the report /AFS/NDIF_CREATE_CAT_CHAR.04. This could be due to corrupt referencing of the structure field. In rare cases there is a chance that the XPRA fails to get the values of a category structure field.08.0B: All materials should have plant-independent structures and strategies before upgrade to AFS 5. Solution Check whether you can correct the errors issued by the XPRA. In the case of 3. You can migrate these by rerunning AFS/NDIF_CREATE_CAT_CHAR after you have corrected the problems. contact SAP support.

Sign up to vote on this title
UsefulNot useful