on 05-22-2009 3:48 AM
Hi Expert,
I'm facing this issue Buffering table not up to date when I click on the shop link.
In ST22, the error is caused at bbp_om_struc_read_up_int.
I have run HRALXSYNC and found no issue to the user account.
Any ideal where is the root cause and how to solve it?
Thanks.
Regards,
Henry
Hello,
Please check this user structure authorization has given using
transaction OOSB and OOSP.
When you are using organizational authorization using OOSB and OOSP,
(1) Structural authorization is not allowed being maintained
for the standard SRM user roles, it's released for system
administrators only.
(2) The structural authorization profile that is used for the
system administrator should contain all purchasing groups
organisations in case that the system admin needs to execute
SRM applications. This can e.g. be achieved through a suitable
function module in tx OOSP.
Please check your structural authorization profile and configure
as per your requirement.
please lock the delimited user in transaction SU01 and implement the
last version of note 1120595 which was updated today.
Kind regards,
Gaurav
PLEASE GIVE FULL POINTS FOR USEFUL REPLIES
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Are you geting this error for all the users? or only one user ?
SAP Note 1089331 - PPOMA_BBP:- Employee assigned with more
than one postion
br
muthu
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi henry,
yes user might be perferct. ruled out - user assigment might be good. no issues. it all depends on relationship..
user-cp-org ok.
are you geting this problem for only one cart or every cart ? be specific.
paste the dump here.
bbp_check_consistency for that user for sc- run - any red?
regards
muthu
Hi,
I have run bbp_check_consistency, no error for the user.
Here is the dump from ST22.
Runtime Errors UNCAUGHT_EXCEPTION
Exception CX_BBP_ES_INTERNAL_ERROR
Date and Time 22.05.2009 10:00:47
-
Short text
An exception occurred that was not caught.
What happened?
The exception 'CX_BBP_ES_INTERNAL_ERROR' was raised, but it was not caught
anywhere along
the call hierarchy.
Since exceptions represent error situations and this error was not
adequately responded to, the running ABAP program
'CL_BBP_ES_EMPLOYEE_MYS========CP' has to be
terminated.
What can you do?
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
An exception occurred that is explained in detail below.
The exception, which is assigned to class 'CX_BBP_ES_INTERNAL_ERROR', was not
caught in
procedure "USER_DETAIL_GET" "(FORM)", nor was it propagated by a RAISING
clause.
Since the caller of the procedure could not have anticipated that the
exception would occur, the current program is terminated.
The reason for the exception is:
Buffering table not up to date
How to correct the error
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"UNCAUGHT_EXCEPTION" "CX_BBP_ES_INTERNAL_ERROR"
"CL_BBP_ES_EMPLOYEE_MYS========CP" or "CL_BBP_ES_EMPLOYEE_MYS========CM002"
"GET_STRUCTURE_PATHS_UP"
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.
The exception must either be prevented, caught within proedure
"USER_DETAIL_GET" "(FORM)", or its possible occurrence must be declared in the
RAISING clause of the procedure.
To prevent the exception, note the following:
User and Transaction
Client.............. 100
User................ 3432
Language Key........ "E"
Transaction......... "BBPSC02 "
Program............. "CL_BBP_ES_EMPLOYEE_MYS========CP"
Screen.............. "SAPLBBP_SC_UI_ITS 2000"
Screen Line......... 4
Information on Caller ofr "HTTP" Connection:
Plug-in Type.......... "HTTP"
Caller IP............. "10.64.84.230"
Caller Port........... 80
Universal Resource Id. "/sap/bc/gui/sap/its/BBPSC02"
Information on where terminated
Termination occurred in the ABAP program "CL_BBP_ES_EMPLOYEE_MYS========CP" -
in "GET_STRUCTURE_PATHS_UP".
The main program was "SAPLBBP_SC_UI_ITS ".
In the source code you have the termination point in line 27
of the (Include) program "CL_BBP_ES_EMPLOYEE_MYS========CM002".
The termination is caused because exception "CX_BBP_ES_INTERNAL_ERROR" occurred
in
procedure "USER_DETAIL_GET" "(FORM)", but it was neither handled locally nor
declared
in the RAISING clause of its signature.
The procedure is in program "SAPLBBP_SC_APP "; its source code begins in line
6 of the (Include program "LBBP_SC_APPF35 ".
Source Code Extract
Line SourceCde
1 METHOD GET_STRUCTURE_PATHS_UP .
2
3 DATA lt_start_object TYPE hrtb_object.
4 DATA ls_start_object TYPE hrrootob.
5 DATA lt_return_otype TYPE hrtb_otype.
6
7
8 ls_start_object-otype = is_start_object-otype.
9 ls_start_object-objid = is_start_object-objid.
10 APPEND ls_start_object TO lt_start_object.
11
12 APPEND iv_return_otype TO lt_return_otype.
13
14 CALL FUNCTION 'BBP_OM_STRUC_READ_UP_INT'
15 EXPORTING
16 roots = lt_start_object
17 return_otypes = lt_return_otype
18 IMPORTING
19 struc = rt_structure_up
20 EXCEPTIONS
21 path_not_found = 1
22 error_reading_structure = 2
23 no_roots = 3
24 invalid_roots = 4
25 OTHERS = 5.
26 IF sy-subrc <> 0.
>>>>> RAISE EXCEPTION TYPE cx_bbp_es_internal_error.
28 ENDIF.
29
30 ENDMETHOD.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.