SAP Note 26370 - Last minute info - industry sector texts convers.

Symptom:

Problems, questions when converting industry texts (WWS)

Cause and prerequisites

There are various causes.

Solution

1. Problems when importing industry tools

a) The job SAP_BRANCHE_TOOL_IMPORT cannot import the industry tools using tp.
Error message: RDDIMPDP cannot be started.
=> In this case, only 1 background process is defined in the system; however, at least 2 background processes are needed.

b) The job SAP_BRANCHE_TOOL_IMPORT terminates (see Transaction SM37) and the error message is: "Ext. program: &cp: /usr/sap/trans/data/RB30B11.SAP: Permission denied=> Delete file RB30B11.SAP in the data directory using any suitable means (for example in UNIX rm /usr/sap/trans/data/RB30B11.SAP)Then start the tool import again.

2. Problems importing industry texts

• The job SAP_BRANCHE_IMPORT cannot be called by tp.

=> Error correction is similar to 1.a)

• As of Release 3.0F with 3.1H kernel: termination of the import job to delfrombuffer.
  

Cause: tp-change for Release 3.1H

Solution: Carry out the steps described in Chapter 2 of the "R/3 Conversion of Industry Texts" guide (Release 1.2B2) for the text files for the language you require (the names of these text files are listed in Appendix A: SAPKB30F12, SAPKB30F13, and so on instead of SAPKB30F11), in each case before you execute the last line (delfrombuffer), execute the second last line (that is addtobuffer again).

Then you can activate the texts.

*End of corrected entry March 5th, 1998 / WM.

3. Problems converting industry texts

a) The conversion in table TQ37T can terminate.

There can be two causes for this.

• Table TQ37T is inactive.

Activating the table in the ABAP/4 Dictionary helps here.

• Table TQ37T does not exist in the database.

In this case, you need to add table TQ37T to the table NOTRA. A "T" must be entered as the exclusion reason.

You can maintain table NOTRA using SM30.

4. Messages in the conversion log
(the conversion log is standardly stored as /usr/sap/trans/log/BRA.).You can display the error log with report RSPUTPRT.

Just enter the file name (for example /usr/sap/trans/log/BRA00001.CIR) in the field "Full file name (with directory)".

• The error message 'Error in the structure determination for table TCNTX' is issued.
  This message can be ignored because the underlying conversion table for table TCNTX contains too many entries.
  

5. Error in the activation

In Release 4.0A termination of the activation due to error BU019:
See also the separate Note 97414.

Under ADABAS and INFORMIX, a data base error (for example SQL-271) occurs because an ORDER BY condition can only handle fields up to a length of 254 bytes.
Proceed as follows:
a) Create a local copy of program RSBRAN03.
b) In this copy, find the first line containing ORDER BY.
c) Change this line from ORDER BY sprsl branche tabname keyinh.
to
ORDER BY sprsl branche tabname.d) Save the copy.
e) Start this copy in the background with the following parameters:
BRANCHE --> Industry indicator (for example ISR for Retail)
LANG --> Language indicator (for example E for English)
RESET --> Reset indicator ( ' ' for activation
'X' for deactivation)
LDIR --> complete directory name for log file (z.B. /usr/sap/trans/log)
f) When you have finished activating the log, create and execute the following ABAP/4 program using SE38:
REPORT YBRANCHE.
TABLES BRACNTL.
PARAMETERS LANGU LIKE SY-LANGU DEFAULT SY-LANGU.
BRACNTL-SPRSL = LANGU.
BRACNTL-BRANCHE = 'ISR'.
BRACNTL-STATUS = 'ACT'.
BRACNTL-AKTREL = SY-SAPRL.
BRACNTL-ADATE = SY-DATUM.
BRACNTL-ATIME = SY-UZEIT.
MODIFY BRACNTL.
WRITE SY-SUBRC.

Enter the language indicator for the imported language (for example 'D', 'E') as the value for the parameter LANGU. If you import two languages, start the program twice.

Start of new entry, December 12th, 1997 (Uwe Gerlach) Empty texts after conversion for French in Retail 1.2B2. Refer to Note 89680. End of new entry December 8th, 1997.

6. Problems under NT due to unknown directory names
Under NT, the error message "Directory does not exist" can be issued even though the directory exists.

In this case, proceed as follows:

a) Use tp to import the tools as described in the guide for industry short texts ("R/3 Conversion of Industry Texts, Chapter 1, Starting the Tool Import).

b) Also use tp to import the industry texts as described in step 1 (the names of the respective CD files are listed in the supplement to the guide).

c) Instead of activating the industry texts via SE62, start program RSBRAN03 in the background as described in point 5.5
(with Informix and ADABAS, start with 5.1).

d) As for point 5.6

7. Problems under AS/400 with R/3 Retail 1.2B or 1.2B1
Under AS/400 and 1.2B or 1.2B1, there are the following problems:

a) Starting the tool import:
In the "R/3 Conversion of Industry Texts" guide, chapter 1, Starting the Tool Import, there is no section on importing the data required under AS/400. For importing the required conversion tools, execute the following commands (as OFR):
CPY OBJ('/QOPT//IS/RB30F11.SAP) TODIR
('/usr/sap/trans/data')
CPY OBJ('/QOPT//IS/KB30F11.SAP) TODIR
('/usr/sap/trans/cofiles')
CD DIR('/usr/sap/trans/bin')
TP PARMLIST('addtobuffer SAPKB30F11 ')
TP PARMLIST('import SAPKB30F11 U146')

b) Starting the industry texts import:
Importing industry texts with transaction SE62 does not yet work under 1.2B and 1.2B1. Thus, import the industry texts with tp as described above (the names of the corresponding CD files are listen in the appendix of the guide: RB30F12.SAP and KB30F12.SAP or RB30F13.SAP and KB30F13.SAP, respectively).

c) Activating the industry texts:
Activating the industry text with transaction SE62 does not yet work under 1.2B(1). Thus, for activating the industry texts, start program RSBRAN03 in the background as described under 5.5 (with Informix and ADABAS, start with 5.1).

d) As for point 5.6

8. Problems under AS/400 with R/3 Retail 1.2B2
Note the following under AS/400 and 1.2B2:
Before you import the industry texts, import the 3.1G kernel
and the existing 3.1G kernel patches.
In addition, execute the following AS/400 commands from OFR:
- CRTDUPOBJ OBJ(CPYSTMF) FROMLIB(R3UP) OBJTYPE(*ALL)
TOLIB(R331GOPT)
- MRGMSGF FROMMSGF(R331GOPT/R3MSGF) TOMSGF(R3UP/R3MSGF)

9. Industry import hangs
In this case, check the CPIC user as follows:

a) Does the CPIC user exist? See note 3310.
Always reset the password (ADMIN).
Is the CPIC user really created as a CPIC user (and not for example as a dialog user).

b) Does the CPIC user have the correct profiles according to note 43180? If not, enter these profiles.
Afterwards, delete the hanging job and the second scheduled job for the industry import from the job queue (use SM37, select with all options).