SAP Basis Tech Supports

Symptom
This note refers to the update and enhancement of existing SAP ERP 6.0 software components with Enhancement Package 4.
Other terms
Updating and enhancing existing software components, Enhancement Package, CD51033594 1-3, 604, SAPK-604DHINEAAPPL, SAPK-604DHINEADFPS, SAPK-604DHINEAFINSRV, SAPK-604DHINSAPHR, SAPK-604DHINEAGLTRAD, SAPK-604DHINEAHR, SAPK-604DHINEAPS, SAPK-604DHINEARETAIL, SAPK-604DHINECCDIMP, SAPK-604DIINERECRUIT, SAPK-604DHINFICA, SAPK-604DHINFICAX, SAPK-604DIINFINBASIS, SAPK-604DHININSURANC, SAPK-604DHINISCWM, SAPK-604DHINISH, SAPK-604DHINISM, SAPK-604DHINISOIL, SAPK-604DHINISPSCA, SAPK-604DHINISUT, SAPK-604BGINLSOFE, SAPK-604DHINSAPAPPL, SAPK-604BGINSEMBW, SAPK-604AGINERECRUIT, SAPK-604AGINFINBASIS, SAPK-604AGINLSOFE, SAPK-604AGINSEMBW, SAPK-701BGINSAPBSFND, SAPKGEI05A, SAPK-700BGINPLMWUI
Reason and Prerequisites
You plan an update and enhancement of existing software components of SAP ERP 6.0 (this is referred to here as “installation”).
Solution
This note provides additional information about the Enhancement Package Installation Guide, which is available on SAP Service Marketplace at http://service.sap.com/erp-inst (path SAP ERP 6.0 -> SAP Enhancement Packages for SAP ERP 6.0 -> SAP Enhancement Package 4 for SAP ERP 6.0).
This note is updated constantly. Make sure you have the current version of this note before you start the installation.
Contents
1. Change history
2. Prerequisites for the installation
3. Preparing for the installation
4. Performing the installation
5. Errors during the installation
6. After the installation
7. Language support
8. Passwords
1. Change history

DateTopicShort Description2009-04-23Chapter 6Note on Business Function HCM_ERC_CI_22009-04-23Chapter 2Support Package Requirements2009-04-01Note 1321756Avoiding DDIC activation errors2009-03-16End to end installation guide2008-12-17SAPehpi PrerequisiteSAPehpi patch level 6 is a prerequisite if SLL_PI is installed2008-11-21Note releaseinitial version2. Prerequisites for the installation
The prerequisites and the procedure for selecting components is described in the Enhancement Package Installation Guide. SAP enhancement package 4: End to end installation guide http://service.sap.com/~sapidb/011000358700000293582009E.PDFCompatibility of add-ons and Enhancement Packages
Note 1226284 provides information about the released combinations of add-ons for ERP and ERP enhancement packages.SAPehpi Version.
If Add-On SLL_PI is installed in your system, you must use SAPehpi Package level 6 or higher. The use of a lower SAPehpi Package level leads to an inconsistent system status.Obtain the following notes before you begin the installation:
ERP upgrade using Maintenance Optimizer:Note 1122966SAP Enhancement Package Installer:Note 1245473Enhancement package 4 for SAP ERP: Required SWCVNote 1165438SAP Enhancement Package 4 SP Stacks:Note 1156407
Components and Support Package requirementsRegardless of the initial release, it is essential that you import EHP4 including EHP4 Support Package Stack 01(or higher)to avoid errors.
We always recommend that you include the Support Package stack that is currently proposed by SAP Solution Manager in the update process.The installation of SAP ERP 6.0 EHP4 requires at least SAP NW 7.01 Support Package stack 2 (Support Package stack 2 of EHP1 of SAP Netweaver components).If you have not yet imported the required component Support Packages into your system, you can include them in the update process.
Exception 1:Before you start the update process, you must implement the following note in your system to avoid a termination in the DDIC activation phase:
1321756(Mass activation: Object is activated instead of deleted)
Exception 2:Before you upgrade from IS-OIL 600 to IS-OIL 604, you must import SAP_BASIS 700 Support Package 12 (SAPKB70012) and implement Notes 1118861 and 1089194 or import SAP_BASIS 700 Support Package 13 (SAPKB70013) in the system. It is not sufficient to include these Support Packages in the queue.If you have installed the software component ECC-SE, the following applies: The ECC-SE release must always correspond to the installed ERP Enhancement Package release. This means that when you update to ERP Enhancement Package 4, the component ECC-SE must also be updated to Version 604.You can also install the components SEM-BW 604 (SAPK-604AGINSEMBW), FINBASIS 604 (SAPK-604AGINFINBASIS), ERECRUIT 604 (SAPK-604AGINERECRUIT) and LSOFE 604 (SAPK-604AGINLSOFE) on a pure SAP NetWeaver system (SAP NetWeaver 7.0 withEnhancement Package 1).To import EA-PS in a system that already has the level EA-APPL 604, load the attached file ACP_EAPS.SAR into your system (SPAM-> Support Package -> Load Packages -> from Frontend) before you start the import using SAPehpi. Otherwise, an error may occur in the queue calculation, which can be solved by reloading the ACP.If you have installed the software component OGSD, import Enhancement Package 4 with at least SAP_APPL 604 Support Package 02 to prevent conflicts between OGSD and SAP_APPL.If you have installed the software component version CPRXRPM 400, import Enhancement Package 4 with at least SAP_APPL 604 Support Package 03 (as soon as this is available) or load the attached file ACP_SAP_APPL-604.SAR in your system to prevent conflicts between CPRXRPM 400 and SAP_APPL. (Transaction SPAM > Support Package > Load Packages > From Front End).
3. Preparing for the installation
Use the Maintenance Optimizer of SAP Solution Manager to load the enhancement packages and the available Support Package stack into your system. A description of the procedure is available on SAP Service Marketplace at service.sap.com/solman-mopz.The attached file ACP_SAP_APPL-604.SAR contains a corrected version of the package attributes for SAP_APPL 604.
The correction concerns only the OGSD add-on.
If you have installed this add-on, you must load the file ACP_SAP_APPL-604.SAR in your system before you import EHP4, to avoid conflicts between OGSD and SAP_APPL. (Transaction SPAM > Support Package > Load Packages > From Front End).DVDs for Enhancement Package 4 are not automatically sent to customers. If you cannot use the Maintenance Optimizer for the download, request the DVD with the material number 51033594 and also the DVDs of SAP NW 7.01 (if not yet installed) from your local subsidiary, or download the DVD from SAP Service Marketplace.If you do not load the installation packages using Maintenance Optimizer, but instead load manually from the DVD:Log on as user:
<sid>admfor UNIX<SID>OFRfor AS/400<SID>admfor Windows
Switch to the directory <DIR_EPS_ROOT> of your SAP system (usually /usr/sap/trans/EPS). The directory <DIR_EPS_ROOT> is also displayed under DIR_EPS_ROOT after you execute the report RSPFPAR.Go to the higher-level directory of <DIR_EPS_ROOT>.Unpack the SAR archive of EHP3 and EHP4 on the DVD with the following statement:
SAPCAR -xvf “/<DVD_DIR>/ABAP/<Software component >604/DELT/DATA/<ARCHIV>.SAR,”on UNIXSAPCAR ‘-xvf /QOPT/<VOLID>/ABAP/<Software component >604/DELT/DATA/<ARCHIV>.SAR’on AS/400SAPCAR -xvf <DVD_DRIVE>:\ABAP\<Software component >604\DELT\DATA\<ARCHIV>.SARon Windows
The relevant files for the installation should now be in the directory <DIR_EPS_ROOT>/in: When you unpack the *.SAR archive, you can unpack up to 4 files or packages, including *.ATT (package attributes), *.PAT (package transport or attribute changes).

ERP 6.0 EHP4 DVD 51033594 also contains packages of SAP_BS_FND 701, PLMWUI 700, WEBCUIF 700 and EHP3, which are a prerequisite for the installation of EHP4. If you have not yet installed EHP3 components in your systems, unpack EHP3 and EHP4.
You will also find the following on ERP 6.0 EHP4 DVD: ERECRUIT 604, FINBASIS 604, SEM-BW 604, LSOFE 604, EA-IPPE 404.
4. Installing or including Enhancement Packages in an upgrade
Upgrade of an ERP 6.0 system to EHP4: for the delta upgrade, use the EHP installer (SAPehpi). (for 32bit systems, see Note 1256600). The procedure is described in the Enhancement Package Installation Guide. This guide also describes from where you can download the latest version of the Enhancement Package installer.
https://service.sap.com/erp-inst -> SAP ERP 6.0 -> SAP enhancement packages for SAP ERP 6.0 -> ‘SAP enhancement package .. for SAP ERP 6.0′.Upgrade from release SAP ERP 2004 (or lower) to SAP ERP 6.0: You can include the Enhancement Packages directly in the upgrade. The procedure is supported by the SAP Solution Manager (Note 1155041) and is described in the ERP Upgrade Guide at:
https://service.sap.com/erp-upgrade -> SAP ERP Upgrade Guides
In both cases, you must generate an XML using the Maintenance Optimizer of SAP Solution Manager, which maps the required target status after the installation or upgrade. This XML is required by the relevant upgrade tool (SAPehpi or SAPup) as soon as an EHP4 is contained in the target status. Note the prerequisites and notes specified under point 2.
5. Errors during the installation
To avoid all known errors, we recommend that you include all of the available Enhancement Package 4 Support Packages and the relevant Support Package stack directly in the queue. The SAP Solution Manager also proposes these.DDIC ActivationActivation errors may occur that can be solved by repeating the activation phase. If errors occur, try to correct them.The following activation errors cannot be solved by repeating the activation phase. For these, proceed as follows:
“Indexes 001 and KEY for table PFO_GO_00IS have identical fields.”"Indexes 3 and E2 for table DFKKRDI have identical fields”"Indexes 2 and E1 for table DFKKRDI have identical fields”"Indexes 4 and E3 for table DFKKRDI have identical fields”Use transaction SE11 to call the relevant table (PFO_GO_00IS or DFKKRDI) in change mode. Important: When you upgrade with SAPup or SAPehpi, you must do so on the unlocked shadow instance.
Choose the menu option “Go to”->”Indexes”. In the dialog box that is then displayed, select the index (KEY or 1,2,3,4) and choose ‘Delete Index’. Do NOT activate the existing index (001 or E1, E2, E3, E4) or the table, but continue with the import.”Table” “OIUX4_BALANCE” could not be activated”Table” “OIUX4_BALANCE_H” could not be activated”Indexes “I01″ and “0″ for table “OIUX4_BALANCE” have identical fields”"Indexes “I01″ and “0″ for table “OIUX4_BALANCE_H” have identical fields”Use transaction SE11 to call the relevant tables (OIUX4_BALANCE and OIUX4_BALANCE_H) in change mode. Important: When you upgrade with SAPup or SAPehpi, you must do so on the unlocked shadow instance.Choose the menu option “Go to”->”Indexes”. In the dialog box that is then displayed, select index I01 and choose “Delete Index”. Then continue with the import.”Srch Help” “H_5ITCN” could not be activated”Srch Help” “H_5ITTT” could not be activatedThe search helps H_5ITCN and H_5ITTT cannot be activated. If Support Package 35 for SAP_HR 600 is already contained in the source release (target release SAP_HR 604 Support Package 01), repeat the activation phase. If a lower Support Package level is contained in the source release SAP_HR 600, ignore the error and see Note 1243014.Error during main import:The following error occurs during the main import of ECC-DIMP 603 into non-Unicode systems: ‘duplicate key error during insert into table SALRTCATCT occured’
Solution: see Note 1083533, unit 5. -> Errors during the installationErrors in the method executionWhen you upgrade from Enhancement Package 1, the method FDT_AFTER_IMPORT terminates with return code 0012.
Solution: Implement Note 1053777 and then continue the installation.Generation errorsINSURANCE 604:
Program SAPLVKKN, include LVKKNU27: Syntax error in line 000034 INCLUDE report ‘ISCDGEN_ACC_OP’ not found.
Solution: After you install INSURANCE 604, execute the report SAPRGEN_CD to generate the includes ISCDGEN_ACC_OP, ISCDGEN_ACC_OPK and ISCDGEN_COPA.IS-H 604:
Screen SAPLNCOOPA003 0100: You can ignore the error (see release note ISH_461_US_KLASSEN).LONGPOST.LOG (switch upgrade)The message: “A1PESEEF_BADI 103 BAdI implementation FMFG_HELD_PO_NO_UPD must still be migrated” can be ignored since the implementation is obsolete. See Note 1246090.You can ignore the following messages:
‘3PETG447 Table and runtime object “/SAPAPO/RESDIM” exist without DDIC reference (”Transp. table”)’
‘3PETG447 Table and runtime object “/SAPAPO/RES_HEAD” exist without DDIC reference (”Transp. table”)’
‘3PETG447 Table and runtime object “/SAPAPO/RES_TXT” exist without DDIC reference (”Transp. table”)’
The tables are deliberately kept on the database when you upgrade (For more information, see Note 827490).

6. After the installation
Activating new business functions.Before you activate the business function “HCM, SAP E-Recruiting 2″ (HCM_ERC_CI_2), see Note 1241014.SAP_APPL 604:
Symptom:
Program SAPLMCEX, include LMCEXU02: Syntax error in line 000219 The data object ‘MC03BF0_TAB’ does not have a component called ‘PERIV’.
Solution: You must import Support Package 01 from SAP_APPL 604 (SAPKH60401) and, in transaction SFW5, repeat the activation of the business function ‘<_Business_Function_xxx>’ (in the menu under “System Settings” -> “Activate Restart”).If the activation job terminates with the error message B! 039 (”Names EA-*, PI-*,IS-PS and JVA are reserved for structure packages”), implement Note 1073405 and repeat the activation. Call transaction SFW5 and choose ‘System Settings’ -> ‘Activate Restart’.If the activation of the industry “Catch Weight Management” terminates with errors in the reports WZRE_RMCSBWXP_COM and /CBAD/SD_RMCSBWXP_COM (”Error while changing structure MC03BF1″), you must implement Note 1112089. You can then start the activation again.Importing languages after the installationIf you intend to install additional languages, we recommend that you do this before importing further Support Packages. Refer to the ‘Language support’ section.Delivery CustomizingDelivery Customizing is imported only into client 000. If you want to copy Customizing into existing clients, read Note 337623.
7. Language support
Enhancement Package 4 supports all the languages of ECC 600. The languages are part of the installation packages, and you do not need to import any additional language packages.For information about subsequently installing further languages in your system, see Note 195442.
8. Passwords
When you use SAPehpi to install or when you include Enhancement Package 4 in an upgrade, the system requests a keyword. This password is:1607077Passwords when using transaction SAINT for the installation: As of Enhancement Package 3, we recommend that you use the SAP Enhancement Package installer (SAPehpi) to install SAP ERP Enhancement Packages. If, in exceptional circumstances, you cannot us the SAPehpi, Note 1256600 contains the passwords for installing Enhancement Package 4.