hi ,
Just do the following.
General Preparations: Handling of the seven(7)DB-Export CDs
============================================================
As mentioned above the DB-Export CDs of the 4.6C IDES Installation have to be handled absolutely different to the CDs of the standard installation.
Due to different restrictions the DB-export-files will not be read from CD but from one big virtual CD on disk. And here you can find the instructions how to build it up. This step is independent of operating system and database software.
Building up a virtual DB-Export-CD on disk
DB-Export-CDs - used during an installation - always have the following structure:
DATA CD-subdirectory 1
DB CD-subdirectory 2
LABEL.ASC flat file with the CD-identification
Only the first DB-Export-CD (1/7) has this structure (all others contain only the DATA-subdirectory). Build up this structure on a disk with at least 4,5 GB free space. It is up to you, where you define the directory in your filesystem (for example IDES_CD in /usr/sap or with NT like D:\IDES_CD ; with AS/400 the name has to be /EXPORT ). You have to enter this name (with the path) later when the installation tool R3SETUP asks for the location of the DB-Export-CD. Here the structure of the virtual CD (NT-example):
Example (NT):
D:\IDES_CD
D:\IDES_CD\DATA
D:\IDES_CD\DB
D:\IDES_CD\LABEL.ASC
Now copy the files from the seven DB-Export-CDs to this disk-CD. Use the ‘copy‘-command or the mouse (copy/paste). The order has no meaning. Pay attention of the DB directory. It has to be copied with all files and sub-directories (ADA,...,ORA) to the directory on disk. With AS/400 the IDES subdirectory too.
1) Copy the CD-identification-file to the virtual CD on disk:
CD(1/7): LABEL.ASC to IDES_CD 1 File
2) Copy sub-directory DB with all files and all subdirectories
CD(1/7): /DB/* to IDES_CD/DB 23 Files, 3 Sub-Folder
3) Copy DATA files
CD(1/7): /DATA/* to IDES_CD/DATA 40 Files
CD(2/7): /DATA/* to IDES_CD/DATA 1 File
CD(3/7): /DATA/* to IDES_CD/DATA 2 File
CD(4/7): /DATA/* to IDES_CD/DATA 1 File
CD(5/7): /DATA/* to IDES_CD/DATA 2 File
CD(6/7): /DATA/* to IDES_CD/DATA 1 Files
CD(7/7): /DATA/* to IDES_CD/DATA 3 Files 50 DATA-Files
IDES-Installation with Windows NT
=====================================
The following section describes all the installation steps for the IDES System which are different from the 4.6C SR2 standard installation. For all other steps you should consult the standard installation guidelines.
Preparations
Here you will find the manual steps which have to be done before starting the instal-lation. The steps are common for all NT-platforms. The idea is to use an IDES-template from the DB-Export-CD (1/7) (instead of the standard-templates from the Kernel-CD) to build and load the database. This prepared IDES-template is available:
CENTRDB.R3S
It can be used to install central and database instance on one machine. (see example).
Example: Central Instance and database on the same host. Template: CENTRDB.R3S
1) insert 4.6C-Kernel-CD
<CD_Drive>:\NT\COMMON\R3setup.bat
This step creates the install-directory <install-dir> \users\<SID>adm\install and copies the installation-tools and different installation templates into it. Template CENTRDB.R3S should not be used because it requests the standard DB-Export-CDs.
2) Build up a virtual CD on disk with the content of the seven (7) DB-EXPORT-CDs. Follow the instructions in ‘General Preparations’ just above.
3) Install central and database instance using the prepared template CENTRDB.R3S
insert DB-Export-CD 1 (1/7)
cd <install-dir>
delete CENTRDB.R3S
copy <CD_Drive>:\IDES\NT\<DB>\CENTRDB.R3S <install-dir>\CENTRDB.R3S
(This CENTRDB.R3S template requests one virtual IDES CD on disk! <DB> stands for ORA, MSS. Attention: CENTRDB.R3S needs to have read/write-permissions!!!)
4) Start the installation as described in the standard installation guide using the IDES-template you have copied under the name CENTRDB.R3S to your installation directory .
Just is very simple.
After You do the complete installation You have to follow the SAP Note 312767.
SAP NOTE 312767( The Below Document is non formatted)
===============
SAP Note Number: 312767
IDES 4.6C: Latest information on the installation
Version: 30, Note Language: EN, Released on: 17.07.2002
Symptom
IDES 4.6C: Information regarding the installation
Additional key words
IDES, release planning
Cause and preconditions
Shipment of 4.6C IDES
Solution
This note is updated regularly !
The following versions are available:
*********************************************************************
* Version 1: Shipped since CW 36, 2000
* Version 2: Shipped since CW 25, 2001 for several platforms
* Version 3: Shipped in the frame of IDES mySAP.com (Note:414305)
* Version 4: Shipped since CW 4, 2002 for several platforms
* Please do note the following text (****)
*--------------------------------------------------------------------
Shipment of IDES mySAP.com components: Notes 174107/414305
Contents: R/3 4.6C, CRM/EBP 2.0C, Workplace 2.11, BW 2.1C, APO 3.0A,
plus the required Web Middleware (ITS, IPC, Requisite, ...)
Shipment of IDES-CRM 3.0: see Note 459356
Contents: CRM 3.0-SP04, R/3-SP22, Web-Middleware (ITS,IPC,IN-Q-MY,TREX,.)
-----------------------------------------------------------------------
Differences between the versions:
- more Support Packages (see Transaction SPAM)
- further languages (see Transaction SMLT)
- updated add-ons
- updated plug-ins
- more corrections/repairs
----------------------------------------------------------------------
Version 4: (****)
Shipment on DVD with DB export and installation documentation.
Support Package 22
Platforms available for the 4.6C IDES Version 4:
UNIX,Linux,NT,Win2000 - Oracle....: DB: 35 GB
NT,Win2000 - MSSQL 8...: DB: 26 GB
UNIX,LINUX,NT,Win2000 - SAPDB.....: DB: 32 GB
Important:
In the shipment, the currency entry in Table T000 for client 800 is incorrect. Please use Transaction SM30 to change it from UNI to EUR!!
Wrong kernel CD:
In the first shipments of version 4, the 4.6C SR2 kernel CD was delivered instead of the 4.6D SR1 kernel. The installation abends because the correct kernel CD is not found. Solution: The 'correct' kernel CD, or the text of the kernel CD in file LABEL.ASC must be adjusted to the text in the installation template CENTRDB.R3S.
Alternative 1:
The kernel CD was completely copied to the hard disk. In this case, edit file LABEL.ASC and change it from / to
ORACLE: ORACLE:R/3:4.6C SR 2:KERNEL:SAP KERNEL:CD51014002
ORACLE:BASIS+WP+KW:46D SR 1:KERNEL:
MS-SQL: MSSQL:R/3:46C SR 2:KERNEL:SAP Kernel:CD51014012
MSSQL:BASIS+WP+KW:46D SR 1:KERNEL
Alternative 2:
Edit the installation template CENTRDB.R3S and adjust it to the text
in file LABEL.ASC (from/to).
Oracle: 1_LABEL=ORACLE:BASIS+WP+KW:46D SR 1:KERNEL
1_LABEL=ORACLE:R/3:4.6C SR 2:KERNEL:SAP KERNEL:CD51014002
MSSQL: 1_LABEL=MSSQL:BASIS+WP+KW:46D SR 1:KERNEL
1_LABEL=MSSQL:R/3:46C SR 2:KERNEL:SAP Kernel:CD51014012
The installation terminates due to incorrect codepage settings.
The installation terminates shortly before the end, or after the installation, a logon to the system is impossible, or errors occur due to unsuitable codepage settings. The behavior differs on the different OS/DB platforms, or might not occur at all.
Recommendation: In the phase shortly before the end of the installation, when R3setup stops and asks whether the MNLS settings are to be adjusted, delete the entries from Tables TCPDB and TCP0D using operating system commands: e.g. truncate table TCPDB; and truncate table TCP0D;
You should also do this after a successful installation before making the correct settings using Report RSCP0004.
If you changed the user from Administrator to <sid>adm for making the DB operations before the end of the installation, you can also finish the installation with this user. Under NT, however, the shares created are not found.
PLUG-INs, ADD-ONs
- Error messages of Transaction SAINT
Internal error: SAINT_UI_NEXT_STEP, SPAM_PATCH_LOGIC:
EMERGENY_STOP in step ADDON_CONFLICTS_?
Or:
Internal error: OCS_GET_OBJECTLIST: SAPKB46C01
empty object list in step ADDON_CONFLICTS_?
If these termination messages are displayed when importing to IDES systems, transport BOMs are missing in the system. In this case, use Transaction SE38 to run Report ZTH_CHK (for version 2, the report still needs to be imported - see below). If the list shows 136 or 137 missing objects, data file 46C_object_lists.sep is contained in sapservx (X=3,4,..) directory /general/R3server/abap/note.0312767. This file is also contained as download file on the SAP Service Marketplace
mit Alias IDES --> 'IDES Public Information'-->'General Information'-->'Installation GuidesIDES'. Copy it to your machine, and import it as user <sid>adm using command R3trans -i 46C_object_lists.sep .
ABAP load generation (for version 4 on DVD)
To avoid compiling messages, the ABAP load can be generated using a report. To do this, call Transaction SE38 and start Report ZIDES_LOAD_GENERATOR. Run the report without parameter change in the background. Runtime: Several hours. Please make sure that sufficient free database space is available (Oracle tablespace, or on the hard disk for MS-SQL (with automatic database growth)).
Period closing program (version-independent)
The period closing program (Report RMMMPERI) is scheduled to run in the background at every beginning of a month. If the system is installed only weeks or months after the export, the program no longer works, and adjustment to the current month must be made manually. With the above program, this can be done month by month, but is not practical in case of large backlog. In sapserv3,..4,..5, ... directory /general/R3server/abap/note.0312767, you can find the R3trans e port file R900009.YT7 . Import it into your system as <sid>adm using command R3trans -i R900009.YT7. In this process, Report ZMMPER1A is imported. Afterwards, start this report in your system. The parameters are already preset for an update and all company codes. The report also adjust the period across the fiscal year change.
************************************************************************
************************************************************************
-----------------------------------------------------------------------
Version 2:
Platforms available for the 4.6C IDES version 2:
UNIX, Linux, NT, Win2000 - Oracle....: DB: 32 GB
Linux - SAPDB.....: DB: 26 GB
NT, Win2000 - MSSQL 8...: DB: 22 GB
OS390, AIX, NT - DB2/OS390 (details see below)
For the other platforms, version 1 is still delivered.
Support Packages: SP22
During the import of Support Package 22 (SAPKH46C22), activation errors occur in the three tables RCJ_EVDEGREE, RCJ_EVQUANT, and RCJ_EVVALUE (due to duplicate field names in structure and append). To resolve this conflict, delete the appends affected.
Table: RCJ_EVDEGREE - Append: ZARCJ_EVDEGREE - Dev.Cl.: CN
RCJ_EVQUANT - ZARCJ_EVQUANT - CN
RCJ_EVVALUE - ZARCJ_EVVALUE - ZHR250
However, the two appends ZARCJ_EVDEGREE and ZARCJ_EVQUANT can only be deleted, if you change the development class (Dev.Cl) from CN to a customer development class (Z*, for example ZIDE). You can do this by using Transaction SE03 - Object directory - Change object directory - enter: R3TR TABL ZARCJ_EVDEGREE. The change should be made in client 000 with any user except for DDIC. This user should be registered as developer. You may use user IDADMIN, password IDES or your own user with the same profile.
Now you can delete the three appends using Transaction SE11 - Data type: ZARCJ.......
Then restart SPAM (import of Support Package 22).
ABAP load generation:
This was changed in version 2 as compared to version 1. No more REPLIST is needed. Any data required is read from system tables. Use Transaction SE38 to start report ZTH_LOAD_GENERATOR. On the screen that appears, two parameters are displayed which should not be changed. Schedule the execution in the background. The runtime is several hours. The Oracle tablespace PSAPEL46CD becomes almost 4 GB in size. The MS SQL DB will increase to almost 24 GB.
The table display (SE16/SE17) for table ZTH_LOAD_TAB shows the current generation status.
Period closing program (see version 4)
***********************************************************************
Version 1:
Platforms available for the 4.6C IDES version 1:
AIX, DEC, HPUX, RELIANT, SOLARIS, Linux, NT - Oracle....: DB: 25 GB
AIX, DEC, HPUX, RELIANT, SOLARIS, Linux - INFORMIX..: DB: 38 GB
AIX, DEC, HPUX, RELIANT, SOLARIS, Linux, NT - ADABAS....: DB: 24 GB
AIX, Solaris NT - DB2-UDB...: DB: 23 GB
NT - MSSQL.....: DB: 19 GB
AS/400....: DB: 30 GB
On request only: NT - Informix
Planned in Q4/2001 AIX, NT - DB2/OS390
IDES installation templates (*.R3S)
When you copy the desired template from the DB export CD (1/6) into the install directory, you have to make sure that the file has write/read authorization on the disk (because it is modified by R3setup during the installation).
Setting up the Transport Management System (TMS):
Start Transaction STMS and save the default values. Choose the "Transport routes" icon. On the next screen, switch to the change mode (icon "Display <-> Change"
. Actually, no changes are required. Finally, choose "Save" and "Distribute and activate".
Language:
The IDES DB contains the languages DE, EN, ES, FR, PT, and JA. If the translation is not complete in some of the modules, you can "supplement" it. See Transaction SMLT, language "EN" is recommended. To be able to log on to this system in a different language, you have to set "installed_languages = DESFPJ" in the instance profile. For the language "Japanese" (JA), you additionally have to install the corresponding codepage.
ABAP load generation:
To avoid "compiling" messages during the first execution of transactions in the R/3 System, the load can be generated as follows in the customer system.
1. Increase the DB areas in which the ABAP load is stored, depending on the database system used (for Oracle - tablespace PSAPEL46BD, Informix - Dbspace PSAPEL46B, ..., for MSS, AS/400 there must be sufficient space for the database). The space requirement is approximately 2 GB (that is, Oracle tablespace PSAPEL46BD has to be increased to a total size of approximately 2 GB; valid for DB2 for the corresponding storage areas).
2. Copy the file "REPLIST" on the DB export CD (1/6)
from the directory: /IDES/COMMON
into the directory: /usr/sap/<SID>/DVEBMGSnn/work
1. Start report ZTHQLDGEN in the R/3 System.
Parameters, Input: File.....: REPLIST (list of report names)
Output: ERRFILE..: ERRLIST (faulty reports)
Output: OKFILE...: OKLIST (generated reports)
Only change the default values for the output if required.
Afterwards, start the report in the background (runtime: 6-10 hours).
Support Packages:
Support Packages (previously Hot Packages) are now divided into Basis Support Packages and R/3 Support Packages (as regards the applications). The 4.6B IDES already contains Basis Support Package 03, R/3 Support Package 03 (see Transaction SPAM), and LCP 03 (HR).
You can import further Support Packages. If the SPAU comparison shows a vaste number of objects you can ignore them all.
Problems with Support Package 22 (SAPKH46C22): see above under "Version 2".
PLUG-INs, ADD-ONs
- Error message by Transaction SAINT
Internal error: SAINT_UI_NEXT_STEP, SPAM_PATCH_LOGIC:
EMERGENY_STOP in step ADDON_CONFLICTS_?
If such termination messages are issued during import to your IDES System, then transport object lists are missing in the system. In this case, import an ABAP report that determines the missing object lists from sapservx (x = 3, 4, ...), directory /general/R3server/abap/note.0312767. Follow the instructions in file SAINT.TXT. The report will produce a list with missing objects. Send this list to thomas.habersack@sap.com and you will get the exported object lists. Send also an email if you cannot load this report from sapserv.
- Error message MESSAGE_ADD_TO_PROTOCOL
During import of an ADD-ON, error "MESSAGE_ADD_TO_PROTOCOL" may be issued. In this case, check the existence of the following directories and create them if they do not exist yet: "/usr/sap/tmp", "/usr/sap/trans/tmp", and "/usr/sap/put/tmp". After that, restart the import. The import tools try to create file "AMODPROT.<sid>". If the restart fails again check if the file "AMODPROT.<sid>" was created in subdirectory "/usr/sap/tmp". If so, copy the file to subdirectory "/usr/sap/put/tmp". Now a restart should be successfull.
Period closing program (see the remarks on version 4)
************************************************************************
************************************************************************
Database-dependent information:
AS/400:
After installing, you have to import a transport from sapserv3. You can find the data files and instructions on sapservX (X = 3, 4, ...) in directory "/general/R3server/abap/note.0312767".
OS/390:
For the installation under DB2/OS390, download file IDES_OS390_INST.SAR from sapserv3, sapserv4, sapserv5, ... directory /general/R3server/abap/note.0312767/OS390 to the target server. Unpacking with tool: sapcar -xvf IDES_OS390_INST.SAP results in subdirectories DB, DB/DB2, and IDES_R3S.
Write an e-mail to thomas.habersack@sap.com, if you cannot download the file from sapserv.
In parallel, as described in the IDES guide, create a single virtual CD on disk from the existing 7 DB export CDs. Then copy the files unpacked above into the corresponding subdirectories of the virtual CD: DB files to DB, and DB/DB2 files to DB/DB2.
For installing, use the installation templates stored in subdirectory IDES_R3S - according to the environment (NT, AiX, OS390). Copy the corresponding template DATABASE.R3S.* to the install directory, rename it DATABASE.R3S, and start the installation as described in the standard guide.
Source code corrections
Release Status Released for Customer
Released on 17.07.2002
Priority Recommendations/additional info
Category Installation information
Primary Component XX-IDES IDES
Transaction codes DB2
Transaction codes EMAIL
Transaction codes FILE
Transaction codes ICON
Transaction codes SAINT
Transaction codes SE03
Transaction codes SE11
Transaction codes SE38
Transaction codes SM30
Transaction codes SMLT
Transaction codes SPAM
Transaction codes STMS
Transaction codes TRANSAKTIONEN
Gültige Releases 1 R0000070000000376
Soft. Component Release Track From Release To Release And Successors
SAP_APPL 46C 46C 46C
No correction instruction available
No Support Packages available
Number Short Text
0000413321 POC/progress value in planning table not for current period
0000434463 IDES 4.6C Japanese: List of problems (in Japanese)
0000434461 IDES 4.6C Japanese installation & additional information
0000337578 AS/400: Correction for V5R1
Keine Attachments vorhanden
