Buffering Table not up to date

[Former Member]

Hi SRM Gurus,

Many of our users are getting "Buffering table not up to date" error when they are trying to create/access shopping carts.

I searched for OSS Notes and did not find any.

Could someone please help me in analysing and resolving this error.

This has been a serious issue for now as there are many carts which are waiting for approval.

Thanks in advance for your help.

Thanks & Regards,

Venkat

[Former Member]

Hi Venkat,

did you manage to solve the problem? We are facing the same issues?

Thanks and best regards for your reply.

Achim

[Former Member]

Hi,

I tried refreshing buffer in SWU_OBUF, still didn't work.

Here is the dump analysis.

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"
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:

-

---

-

---

System environment

SAP-Release 700

Application server... "srmhau"

Network address...... "10.10.61.13"

Operating system..... "AIX"

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

Hardware type........ "00C9FECD4C00"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 1

Shortdump setting.... "full"

-

---

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 ".

-

---

Thanks in advance for your help.

Thanks & Regards,

Venkat

[Former Member]

Hi

<u>Please go through the following SAP OSS Notes -></u>

Note 920185 SRM 5.0: No CP<->BP consistence check in BBP_BP_OM_INTEGRATE

Note 946381 - Unloading point is not filled from room number

Note 939052 Termination when you create/change a surrogate bid

Note 927307 SRM 5.0: Termination in the shopping cart monitor

Do let me know.

Regards

- Atul

[Former Member]

Hi Venkat,

sometimes the system gets confused with the documents.

Try to reset the buffer using trx SWU_OBUF.

Hope it helps,

Cheers,

Claudia

[dennis_bruder]

Hi,

if you would tell us more about your dump we could give you a hint. You only told us that the dump comes from BBP_PD_ABORT. Could you check the involved ABAP programs in ST22 and tell us in which form routine BBP_PD_ABORT is called.

BBP_PD_ABORT can be called everywhere in the system where an exception occurs which is not handeled.

[Former Member]

Hi,

Yes, there is a dump generated for this error and the dump analysis says the following.

What happened?

The exception 'CX_BBP_PD_ABORT' 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 'SAPLBBP_PDH' has to be terminated.

Error analysis

An exception occurred which is explained in detail below.
The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and
therefore caused a runtime error.
The reason for the exception is:
Übernehmen

Information on where terminated

Termination occurred in the ABAP program "SAPLBBP_PDH" - in "BBP_PD_ABORT".

The main program was "BBP_BACKGROUND_APPROVAL ".

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

of the (Include) program "LBBP_PDHU08".

I am not sure why this dump has occured.

Thanks & Regards,

Venkat

[Former Member]

This sometimes also occurs when you dont give in the correct PROCESS type.

I it also can be due to the mismatch between the Purchasing Org and Purchaisng Group which has been defined.

So please look at the Process Type conflict.

There can be some Authorization issues with the way workflow has been configured for the Shoping carts/PO.

OR there may be user authorization issues.

Please consult your worklfow expert and tell him to run the Shopping cart/PO workflow independently and let him debug the same and trace the place where exactly it terminates - then it shud solve your problem.

Please look at both these issues.

Hope this helps you out

Thanks

Venugopal

[Former Member]

Hi

Please elaborate the problem in detail. Which SRM version are you using ?

<b>At what step are you getting this Dump ?</b>

<u>Meanwhile, try the following SAP OSS Notes / links -></u>

Note 751022 - Monitor Shopping Cart: Item deletion causes termination

Note 617187 - Update termination due to deletion of several items

Do let me know.

Regards

- Atul

[dennis_bruder]

Hi,

go to ST22 and check if there is a corresponding dump. Check the call structure and see where the ABORT statement is raised.

Sometimes this error occurs when a purchasing group no longer belongs to a purchasing org.

Regards

Dennis