cancel
Showing results for 
Search instead for 
Did you mean: 

SRM 5 Patching Price Check Uncaught Exception Error

Former Member
0 Kudos

Hi Gurus

We are in the process of applying patches to our SRM 550 system. We are going from SP 13 to 15.

Extended classic scenario linked to backend ERP

We have a particular issue with the system producing short dumps.

1. We create a SC using describe requirements. Add two lines to the cart, one for goods e.g. furniture with a price, and one for delivery with a zero price.

2. The SC is sent by WF to our operational purchasers. We do not use SOCO.

3. An Operational Purchaser opens the cart for change and adds a valid supplier to the zero priced line. Press Check button, hit return key, or refresh button.

4. The system produces a short dump because of an uncaught exception and fails.

ST22 error log shows us the following:-

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:

Incorrect status in pricing

Information on where terminated

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

The main program was "SAPLBBP_SC_UI_ITS ".

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

of the (Include) program "LBBP_PDHU08".

I can provide further ST22 log entries if this would help, but I wanted to keep my initial posting short.

This only happens when a Describe requirements cart has a zero priced line, catalog items with zero price work OK.

Zero priced lines are essential to our business process as goods may be supplied to us either with a zero price, or the price may not be determined at the time the order is raised e.g. Delivery charges.

The issue has already been logged as high priority with OSS but we have no answer yet.

We have no bespoke in this area.

Our ABAP team have already debugged and determined that there is an error being returned by the SAP code.

Has anyone else come across this issue or know of any SAP note that will fix this uncaught exception?

We are now getting desperate as our go-live for this system is next week.

Any suggestions would be much appreciated and suitable points will be awarded.

Allen Brooks

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Issue resloved

The pricing engine needed to be patched applied SAP note 880749