on 09-13-2007 10:15 AM
Hi,
I have uploaded the patches, basis , abap 12 and other,
since then in SU01 when i save the user after creating it , it throws dump.
any ideas..
Regards,
SM
it's hard t help you with so little information
supply these info:
1. SAP version
2. OS version
3. DB version
4. first 50 lines of that short dump
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
ECC6.0
HPUX
Oracle 10.2
===========================================================
===========================================================
Runtime Errors SYNTAX_ERROR
Date and Time 15.09.2007 11:15:15
-
-
Short text |
Syntax error in program "SAPLBUPA_INTERFACE_OUTBOUND ". |
-
-
What happened? |
Error in the ABAP Application Program |
The current ABAP program "CL_IM_CRM_BUPA_ADDR_CAM=======CP" had to be |
terminated because it has |
come across a statement that unfortunately cannot be executed. |
The following syntax error occurred in program "SAPLBUPA_INTERFACE_OUTBOUND " |
in include "LBUPA_INTERFACE_OUTBOUNDF88 " in |
line 73: |
"The data object "CS_BANKDETAIL" does not have a component called "BK_I" |
"BAN_ONLY"." |
" " |
" " |
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 "SAPLBUPA_INTERFACE_OUTBOUND ". |
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 SAPLBUPA_INTERFACE_OUTBOUND |
: |
"The data object "CS_BANKDETAIL" does not have a component called "BK_I" |
"BAN_ONLY"." |
" " |
" " |
-
-
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... "SAPHRS" |
Network address...... "172.16.16.32" |
Operating system..... "HP-UX" |
Release.............. "B.11.23" |
Hardware type........ "ia64" |
Character length.... 16 Bits |
Pointer length....... 64 Bits |
Work process number.. 0 |
Shortdump setting.... "full" |
Database server... "SAPHRP" |
Database type..... "ORACLE" |
Database name..... "HRP" |
Database user ID.. "SAPSR3" |
Char.set.... "C" |
SAP kernel....... 700 |
created (date)... "Mar 19 2007 20:44:04" |
create on........ "HP-UX B.11.23 U ia64" |
Database version. "OCI_102 (10.2.0.1.0) " |
Patch level. 102 |
Patch text.. " " |
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.." |
SAP database version. 700 |
Operating system..... "HP-UX B.11" |
Memory consumption |
Roll.... 16192 |
EM...... 20949200 |
Heap.... 0 |
Page.... 57344 |
MM Used. 3637856 |
MM Free. 549360 |
-
-
User and Transaction |
Client.............. 000 |
User................ "SAP*" |
Language key........ "E" |
Transaction......... "SU01 " |
Transactions ID..... " " |
Program............. "CL_IM_CRM_BUPA_ADDR_CAM=======CP" |
Screen.............. "SAPMSSY0 1000" |
Screen line......... 6 |
-
-
Information on where terminated |
Termination occurred in the ABAP program "CL_IM_CRM_BUPA_ADDR_CAM=======CP" - |
in "IF_EX_ADDRESS_UPDATE~ADDRESS2_SAVED". |
The main program was "SAPMSUU0 ". |
In the source code you have the termination point in line 17 |
of the (Include) program "CL_IM_CRM_BUPA_ADDR_CAM=======CM003". |
-
-
Source Code Extract |
-
Line | SourceCde |
-
1 | METHOD if_ex_address_update~address2_saved. |
2 | |
3 | DATA : lv_oubound_active TYPE c, |
4 | lv_shadow type c. |
5 | |
6 |
|
7 | CALL FUNCTION 'UPGRUNT_CHECK_SHADOW_SYSTEM' |
8 | IMPORTING |
9 | EV_SHADOW = lv_shadow |
10 | . |
11 | |
12 | if lv_shadow = 'X'. |
13 | exit. |
14 | endif. |
15 | |
16 |
|
>>>>> | CALL FUNCTION 'BUPA_OUTBOUND_CHECK_ACTIVE' |
18 | IMPORTING |
19 | ev_active = lv_oubound_active. |
20 | |
21 | CHECK NOT lv_oubound_active IS INITIAL. |
22 | |
23 | IF im_person_group <> 'BP'. |
24 | EXIT. |
25 | ENDIF. |
26 | |
27 | CALL FUNCTION 'BUPA_OUTBOUND_ADDR2_SAVE' |
28 | EXPORTING |
29 | im_address_number = im_address_number |
30 | im_person_number = im_person_number |
31 | im_t_object_types = im_t_object_types |
32 | im_t_xadrp = im_t_xadrp |
33 | im_t_yadrp = im_t_yadrp |
34 | im_t_xadrc = im_t_xadrc |
35 | im_t_yadrc = im_t_yadrc |
36 | im_t_xadr2 = im_t_xadr2 |
-
=======================================================================
Regards,
SM.
Are you on Oracle 10.2.0.1? or did you install already 10.2.0.2?
10.2.0.1 is NOT supported, this may have been the error, why SPAM was failing.
Check
Note 871096 - Oracle Database 10g: Patch sets/patches for 10.2.0
and install the 10.2 patchset and all single patches (30+). Also check, that you use the Oracle client 10.2.0.2
--
Markus
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.