How to triger RDDIMPDP at operational level

[Former Member]

Hi Basis experts,

We are importing support package, and get stucked at the IMPORT_PROPER stage. The RDDIMPDP is not running at the background, and we cannot use the SE38 to run RDDNEWPP. So, anyone can tell me how can I run the RDDIMPDP from UNIX level? Thanks alot in advance.

Amy

[Former Member]

Hi Amy, the only way you have is to operate at low-level using R3trans (option -i) to reimport the last support package from the beginning, and after restart the queue.

Be careful because there could be some problems with the overall queue you are importing.

If the problem affects a productive landscape i suggest you to open an OSS problem.

Bye Riccardo

[Former Member]

>Hello Amy,

Why cannot you use SE38 to run RDDNEWPP?

Regards.

Ruchit.

[Former Member]

It gives me error message like:

Runtime Errors SYNTAX_ERROR

Date and Time 02.08.2007 16:16:20

Short text

Syntax error in program "SAPLSEWORKINGAREA ".

What happened?

Error in the ABAP Application Program

The current ABAP program "SAPLWBABAP" had to be terminated because it has

come across a statement that unfortunately cannot be executed.

The following syntax error occurred in program "SAPLSEWORKINGAREA " in include

"LSEWORKINGAREAU01 " in line 54:

"The data object "WORK_ITEMS" does not have a component called "JUST_FO"

"R_CHECKING"."

" "

" "

The include has been created and last changed by:

Created by: "SAP "

Last changed by: "SAP "

What can you do?

Please eliminate the error by performing a syntax check

(or an extended program check) on the program "SAPLSEWORKINGAREA ".

You can also perform the syntax check from the ABAP Editor.

If the problem persists, proceed as follows:

Note down which actions and inputs caused the error.

To process the problem further, contact you SAP system administrator.

Using Transaction ST22 for ABAP Dump Analysis, you can look

at and manage termination messages, and you can also keep them for a long time.

Error analysis

The following syntax error was found in the program SAPLSEWORKINGAREA :

"The data object "WORK_ITEMS" does not have a component called "JUST_FO"

"R_CHECKING"."

" "

" "

How to correct the error

Probably the only way to eliminate the error is to correct the program.

-

If you cannot solve the problem yourself and want to send an error

notification to SAP, include the following information:

1. The description of the current problem (short dump)

To save the description, choose "System->List->Save->Local File (Unconverted)".

2. Corresponding system log

Display the system log by calling transaction SM21.

Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

program: The source code of the program

In the editor, choose "Utilities->More

Utilities->Upload/Download->Download".

4. Details about the conditions under which the error occurred or which

actions and input led to the error.

System environment

SAP-Release 700

Application server... "btrcmap6"

Network address...... "172.17.2.211"

Operating system..... "AIX"

Release.............. "5.3"

Hardware type........ "000C4658D600"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "btrcmap6"

Database type..... "ORACLE"

Database name..... "AP7"

Database user ID.. "SAPSR3"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Apr 2 2006 20:44:50"

create on........ "AIX 2 5 005DD9CD4C00"

Database version. "OCI_101 "

Patch level. 52

Patch text.. " "

Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."

SAP database version. 700

Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"

Memory consumption

Roll.... 16192

EM...... 8379696

Heap.... 0

Page.... 40960

MM Used. 1830352

MM Free. 2356896

User and Transaction

Client.............. 000

User................ "DDIC"

Language key........ "E"

Transaction......... "SE38 "

Transactions ID..... " "

Program............. "SAPLWBABAP"

Screen.............. "SAPLWBABAP 0100"

Screen line......... 5

Information on where terminated

Termination occurred in the ABAP program "SAPLWBABAP" - in "SET_STATUS".

The main program was "RSABAPPROGRAM ".

In the source code you have the termination point in line 23

of the (Include) program "LWBABAPO00".

Source Code Extract

Line SourceCde

1 *----

---

*

2 * INCLUDE LWBABAPO00 *

3 *----

---

*

4

5 *----

-

---

6 * MODULE SET_STATUS

7 *----

-

---

8 * Status und Titlebar

9 *----

-

---

10 MODULE SET_STATUS OUTPUT.

11

12 * Programmnamen setzen

13 if rs38m-programm is initial

14 or xcode = copy

15 or xcode = renm.

16 GET PARAMETER ID 'RID' FIELD RS38M-PROGRAMM.

17 endif.

18

19 * Änderungen in Einstellungen?

20 perform settings_check using settings.

21

22 REFRESH EXCLTAB.

>>>>> CALL FUNCTION 'RS_WORKING_AREA_ACTIVE_CHECK' "Aktive/Inaktive Sourcen

24 EXCEPTIONS

25 NOK = 1

26 OTHERS = 2.

27 IF SY-SUBRC NE 0.

28 HANDLE_ACTIVE_SOURCES = NO.

29 EXCLTAB-FUNCTION = AKTI.

30 APPEND EXCLTAB.

31 EXCLTAB-FUNCTION = INAC.

32 ELSE.

33 HANDLE_ACTIVE_SOURCES = YES.

34 ENDIF.

35

36 call 'C_SAPGPARAM' id 'NAME' field 'transport/systemtype'

37 id 'VALUE' field system_id.

38 if system_id ne 'SAP'.

39 EXCLTAB-FUNCTION = SYCR.

40 APPEND EXCLTAB.

41 endif.

42

Cannot use SM37, SE38, SM50 etc to watch the process, or do anything. I am thinking to manually run the RDDIMPDP or RDDNEWPP from unix level. Need help!!

Thanks.

Amy