Upgrade Learnings

Upgrade
Best Practices and Learning’s

Nov, 2009 Page 1 of 7

Best Practices & Key Learnings

Introduction:
This document provides key learning’s of an SAP upgrade from 4.6c to ECC 6.0. This document
aims at few of the common problems encountered during an upgrade and their solutions.
This document is prepared based on PwC and HGST Upgrade projects.

Learning’s:
The problems occurred in the process of upgrade after completion of SPDD & SPAU fixes and
during the ABAP Remediation and Standard transaction testing and their solutions are
documented in this document.

 Navigation problem in ABAP Editor

This problem occurs in ABAP Editor when we use double-click to execute an
external navigation from the use of an object (include, method, function module, table,
and so on) to the definition point of the object. After you choose F3, you return to the
source program.
After that if we execute another external navigation to another object, the system
displays the definition point of the first object again.
To overcome this problem implement the correction instructions specified in the
OSS Note ‘1279209’.

 In ECC 6.0, the matchcode objects are obsolete and the pooled tables generated
for these matchcode objects are not available in ECC 6.0
• The pooled tables ‘M_VMVLA’ & ‘M_VMVLC’ have been replaced with the
transparent table ‘SHP_IDX_GDSI’.
• The pooled table M_VMVAD has been replaced with the transparent table
V_VMVAD

 After you upgrade to Release ERP 6.0, index tables that replace the match code
tables are not filled with the old values.
Matchcode tables are no longer supported in the basis system. In Releases 4.70
and ECC 5.0, you could use XPRAS to transfer data to the corresponding index tables.
However, as of Release ERP 6.0, the matchcode tables are already deleted in the
shadow system with respect to the basis system and, therefore, the transfer using XPRA
is no longer possible.
As per OSS note ‘1093055’ execute the report
“RLE_SHP_IDX_TABLE_MAINTAIN” to set the index tables after completion of the
upgrade.

Nov, 2009 Page 2 of 7

Best Practices & Key Learnings

 The Collective Search helps like KART, VMVA & MAT1 are not working properly
after upgrading to BASIS patch level: 700 SAPKB70019.
If you use a search help exit or a similar option to write selection conditions in the
SELOPT_TAB of the collective search help, the system may not transfer them to the
elementary search helps. The return transport of an entry selected from an elementary
search help in the field on the screen does not work.
Implement SAP Note ‘1319466’ to change the code in the function module
“DD_SHLP_EXPAND_HELPMETHOD”

 Unicode tuning for search helps where the search help exits are used
In 4.6c: The below statement is used to map the results into record_tab internal
table.
record_tab[] = t_records[].
In ECC 6.0: The above assignment may not work properly and wrong values will
be populated to the search help fields.
To avoid this problem use the function module “F4UT_RESULTS_MAP” to map
the results to record_tab internal table.

 The structure RFPOSXEXT may not contain the special fields added by the
customer. These fields will be available in the table T021S.
In the line item display, the system does not display special fields even though
you have maintained them using Transaction SM31 in table T021S.
Using Transaction SE11, check whether the special field exists in structure
RFPOSXEXT.'U_' is prefixed to actual field names, for example, U_EBELN.
As per OSS Note ‘215798’ start program RFPOSXEXTEND using Transaction
SE38.The program regenerates structure RFPOSXEXT and consequently eliminates the
inconsistency.

 The table EDIFCT is not having any entries after upgrade to ECC 6.0
After the upgrade entries made by the customer are missing in table EDIFCT. As a
result, error message 'Function module not allowed: <name>' is displayed during the
inbound processing of IDocs and the IDoc gets status 51.
Implement the SAP Note ‘216671’ to get the entries in the table EDIFCT.

 Runtime error “DYNPRO_NOT_FOUND” in the program SAPLKACB

It is giving the dump as the sub screen 9000/9002 is not available in the program
SAPLKACB while executing the transactions FMZ1, FBL3N, MIGO and KB16N.
As per OSS Note 1322536, Re generate the sub screens using the transaction OXK1.

 The error LOAD_PROGRAM_NOT_FOUND occurs in the transactions FB60 & FB01.

These transactions gives dump as the program GBSxxSET or GBSxxSEZ does not exist.
As per OSS Note ‘79156’ execute the report “RGUGBR00” to generate these programs.

Nov, 2009 Page 3 of 7

Best Practices & Key Learnings
 The Code page IBM has been replaced with the code page 1103

 The transportation layer for the new landscape should be specified for package
which will avoid errors while releasing the transport request

 Enabling the Unicode flag of the standard programs

As per the OSS Note ‘728998’, Unicode flag can be set by executing the custom
program mentioned in the embedded document.

ZBI_UNICODE.doc

 Enabling the Unicode flag of BOR Objects

As per the OSS Note ‘563417’ the Unicode flag of the BOR Objects can be set
by executing the programme “SWO_SET_UC_FLAG” and passing the BOR Object type
as input to the report

 The custom transaction variants may not be copied properly after upgrade from
4.6c to ECC 6.0

• If they are not copied we need to create manually.

• If they are different from the 4.6c we need to correct them in ‘SHD0’ transaction.

• If table control is used and if some fields are invisible even though they are not
marked as invisible in SHDO, then go to the table control in transaction and click
on configuration(Button at the top right corner of table control) ->administrator
and make the required changes and click on activate button.

 In ECC6.0 the function module ”UPDATE_FEBKO_STATUS” does not exist

In ECC 6.0 the function module ‘UPDATE_FEBKO_STATUS’ was replaced with
the function module ‘UPDATE_FEBKO_VB_STATUS’.

 Errors with the IMPORT & EXPORT Statements

• If the format of the source & target structures is different then use the addition
“IGNORING STRUCTURE BOUNDARIES” with IMPORT & EXPORT
Statements.

• If the length of the Target structure or field is less than the source structure or
field then use the addition “ACCEPTING TRUNCATION” with IMPORT &
EXPORT statements.

 The generated report for SAP queries may not be available in ECC 6.0 after
upgrade from 4.6c

These reports have to be created manually in ECC 6.0

• These reports can be generated by using the function modules
“RSAQ_GENERATE_PROGRAM” and “RSAQ_REPORT_NAME”. The
parameters user group and query name have to be passed to the function
module.

Nov, 2009 Page 4 of 7

Best Practices & Key Learnings
For example for the report “AQZZZGBSD=======MARGINREPORT1=”
The user group is “ZGBSD” and the query is “MARGINREPORT1”.

 The STOP keyword in module pool program in ECC 6.0 will give runtime error.
The STOP statement should be replaced with LEAVE TO SCREEN SY-DYNNR,
SET SCREEN, EXIT or any other keyword based on the flow logic.

 Copying the content between two incompatible structures

The function module HR_99S_COPY_STRUC1_STRUC2 is used to copy the
content of one structure to another incompatible structure.

 The error ‘Held documents must be converted; read long text' occurs while using
the option held documents in transactions FB50 & FB11
As per OSS Notes 571543, 498935 execute the report ‘RFTMPBLO’ to convert
the held documents.
If the above program is going for dump then implement the OSS Note 36219 to
convert the held documents.

Best Practices:

 Migration of match code objects to search helps

The match code objects are not supported in ECC 6.0 Environment. It is
mandatory to convert match code objects to search helps based on the usage analysis of
the match code objects in 4.6c system after taking the system copy and before the start
of upgrade.

 Do not delete any objects in Shadow system during the Upgrade

Deletion of object in Shadow system during any phase of the Basis activities may
lead to errors in consequent phases stating that the deleted object is not active.

 Analyzing and fixing modified objects in SPAU & SPDD

It is the best practice to analyze the objects in SPAU & SPDD carefully and
provide the decisions to customer before taking any action. After getting the confirmation
from the customer proceed for the fixes with the final decision from the customer.

 Identifying the dangerous programs

Identify the list of dangerous programs which may harm the business process
(Such as programs deleting user data or the programs which are used to lock/unlock
users) and handle these programs carefully during the ABAP Remediation and testing.

Nov, 2009 Page 5 of 7

Best Practices & Key Learnings

 Maintaining the original system to the new ECC Upgrade system

Ensure that the original system is set to the new Upgraded ECC system to avoid
the creation of the repair transports. After setting the original system to ECC system the
changes will be saved under a development/correction transport. The original system can
be changed using the transaction SE03.

 Sequencing of the transport requests

It is a best practice to create an individual transport request for each object which
is modified during the upgrade.
After creation of transports arrange them in a sequence based on the
dependency before transporting them to quality system to avoid the failure imports in
target system due to dependency. Releasing the transports in the sequence will help to
import the transports in batches in target system without failures which reduces the total
time of importing.
The sequence of transports should be done in the below mentioned order:

Sequence of
S No Transports
1 SPDD
2 SPAU
3 Note implementations
4 IMG Activities
5 Package
6 Domains
7 Data Elements
8 Append structures
9 Structures
10 Type group
11 Tables
12 View maintenance
13 Text maintenance
14 Search help
15 Function groups
16 Function modules
17 Classes
18 BOR
19 Includes
20 Module pool
21 Subroutine pool
22 Screens
23 Reports

Nov, 2009 Page 6 of 7

Best Practices & Key Learnings
24 Enhancements

Nov, 2009 Page 7 of 7