cancel
Showing results for 
Search instead for 
Did you mean: 

runtime error creating SC or PO, 'CX_BBP_PD_ABORT' in support pack 9??

0 Kudos

we are using support pack 9, we found few notes regarding Support pack 5, we need for support pack 9.

we are getting the error (dump) The exception, which is assigned to class 'CX_BBP_PD_ABORT', was not caught and

therefore caused a runtime error. while creating SC using describe steps or PO.

As per dump analysis i had look in SAP Note, that are all support only support pack 5 and below.

Could you please provide me any solution to above error for Support pack 9..

Regards

Ahmed

Accepted Solutions (0)

Answers (5)

Answers (5)

0 Kudos

Hi,

We checked status of IPC using the program bbp_cnd_customizing_check and there it is showing IPC is active and restated the O/S as well.

Still we are getting the same dump.

Could you please help us to resolve this problem?

Regards

Ahmed

Former Member
0 Kudos

Hi

Please go through this ->

Note 876152 - SRM 5.0: Corrections in report BBP_CND_CUSTOMIZING_CHECK

When you create/change purchase documents, a dump short is triggered.

Solution ->

1. Refer to Note 533877 to make sure that you have imported the correct Support Package (e.g. IPC40SPXY) and the current patch (e.g. IPC40SPXYP) for the IPC. Note 653277 described how to stabilize the IPC in case of sporadic terminations.

2. Execute report BBP_CND_CUSTOMIZING_CHECK in Transaction SE38. This report should not display any error messages or warning messages. You must maintain missing Customizing accordingly, for example: condition tables, time zone (TIMEZONE_MASTER_DATA_DB) and others.

If you cannot execute the report in Transaction SE38, you have the following alternative:

Transaction: SPRO -> 'Supplier Relationship Management -> SRM Server -> Cross-Application Basic Settings -> Pricing --> Check Technical and Customizing Settings for Conditions'.

If you use the IPC (Internet Pricing and Configuratior), it must be active. Bear in mind that pricing with the IPC is client-specific. The correct client must be set accordingly in the IPC administrator.

The IPC is required for all SRM scenarios. Only in the classic scenario you can replace the IPC by the simplified pricing!

If you have made changes to Customizing or the IPC administrator, restart the IPC. In this way you make sure that the system uses the new settings.

3. Check whether the BAdIs relevant for the pricing are activated correctly and filled with the correct coding.

Transaction: SPRO -> 'Supplier Relationship Management -> SRM Server -> Business Add-Ins for SRM Server (BAdIs) -> Pricing --> Switch On Simplified Pricing (Classic Scenario)'

or:

-> 'Product Master Maintenance: Switch Off Buffer Refresh in IPC'

Also read the corresponding documentation.

4. Short dump when searching for/displaying/changing contracts

Note: 661712, 667685

5. Deleting/undeleting items in change version

Note: 658916

6. Creating/editing purchase orders and contracts (also from the SoCo)

Note: 651994, 671481, 706493, 724316, 718489

7. Publishing bids/bid invitations in SoCo

Note: 706493, 834918

Please also check whether the user who wants to publish the bid/bid invitation has a valid e-mail address. This address must be maintained using Transaction BBPUSERMAINT.

It must be possible to send the bid/bid invitation technically. Please check whether the basic settings (e.g. SAPConnect) have been configured correctly.

8. Goods confirmation or service confirmation (Transaction: BBPCF02)

Note: 662972, 709716, 686173

9. Dump in Transaction SARA

Note: 710241

10. Deleting attachments or account assigment lines in Sourcing

Note: 688437, 684795

11. Creating purchase orders and contracts in the Bidding Engine

Note: 718489

12. Creating, saving and monitoring Shopping Carts or deleting items in SC

Note: 668771, 724118, 751002, 789571

13. Problems with cFolders

Notes: 743886, 739177, 667317

14. Price disappears when you authorize purchase orders

Note: 697144

15. Error in the IPC Log file: "Dimension POINTS is not available"

Note: 743025

16. Termination in function module: B40B_READ_TABLE

Note: 831467

17. Deleting index table using report BBP_GETLIST_INDEX_FILL

Note: 725976

18. Error when you copy template without ship-to address

Note: 847427

Note 781669 - Correction of BBP_CND_CUSTOMIZING_CHECK

Note 673372 - Short dumps UNCAUGHT_EXCEPTION in SRM 3.0, 4.0, and 5.0

Hope this will help.

Regards

- Atul

0 Kudos

Hi,

Could you please have look in this issue?

i am expecting instant reply.

Regards

Ahmed

Former Member
0 Kudos

Hi,

Reboot means OS server reboot.

BR,

Disha.

Pls reward points for useful answers.

0 Kudos

We checked status of IPC using the program bbp_cnd_customizing_check and there it is showing IPC is active. Please get back to us what exactly is the "Server Reboot" means? (Restarting the IPC Service or Physical OS Server Reboot?

Thanks and Regards

Ahmed

Former Member
0 Kudos

Hi

Please try my suggestions as well... Do let me know.

Btw, Server Reboot" means restarting the Physical OS Server Reboot..

Regards

- Atul

Former Member
0 Kudos

The reason for the exception is:

>Übernehmen

You have a problem with your IPC, ask your basis team to restart the IPC, in 9 out of 10 cases this solves your problem.

You can run report BBP_CND_CUSTOMIZING_CHECK to check whether the IPC is running correctly or not.

Regards,

Robin

Former Member
0 Kudos

Hi

Please give some more details in next reply..

What steps i need to do replicate the same in my system ?

Meanwhile, look for following SAP OSS Notes ->

Note 833442 Data inconsistency due to termination when you save

Note 831594 Purchase order: Termination when you write a new version

Note 828356 Duplicate items when changing ordered purchase orders

Note 526831 EBP: Missing currency in the limit results in termination

Note 724316 Purchase order: Short dump in case of vendor deletion

Note 671481 Exception: CX_BBP_PD_ABORT in pricing

Please paste complete ST22 dump details in next reply. Also create a new Customer OSS message with SAP on this for faster resolution of the query.

Do let me know.

Regards

- Atul

0 Kudos

Hi Atul,

i had look in SAP Notes. i am looking for support pack 9.

please help me how to creat a new Customer OSS message with SAP for faster resolution of the query.

The short dump details are as below.

Runtime Errors UNCAUGHT_EXCEPTION

Exception CX_BBP_PD_ABORT

Date and Time 03.01.2008 07:58:33

Short text

An exception occurred that was not caught.

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.

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 which is explained in detail below.

The exception, which is assigned to class 'CX_BBP_PD_ABORT', was no

therefore caused a runtime error.

The reason for the exception is:

Übernehmen

How to correct the error

If the error occures in a non-modified SAP program, you may be able

find an interim solution in an SAP Note.

If you have access to SAP Notes, carry out a search with the follow

keywords:

"UNCAUGHT_EXCEPTION" "CX_BBP_PD_ABORT"

"SAPLBBP_PDH" or "LBBP_PDHU08"

"BBP_PD_ABORT"

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 S

Restrict the time interval to 10 minutes before

after the short dump. Then choose "System->List->S

(Unconverted)".

3. If the problem occurs in a problem of your own

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 er

actions and input led to the error.

System environment

SAP-Release 700

Application server... "bp1xeuaa202"

Network address...... "149.184.194.116"

Operating system..... "Windows NT"

Release.............. "5.2"

Hardware type........ "4x AMD64 Level"

Character length.... 16 Bits

Pointer length....... 64 Bits

Work process number.. 0

Shortdump setting.... "full"

Database server... "BP1XEUAA217"

Database type..... "ORACLE"

Database name..... "RFV"

Database user ID.. "SAPSR3"

Char.set.... "C"

SAP kernel....... 700

created (date)... "Sep 1 2006 00:19:17"

create on........ "NT 5.2 3790 Service Pack 1 x86 MS VC++ 14.00"

Database version. "OCI_10201_SHARE "

Patch level. 75

Patch text.. " "

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

SAP database version. 700

Operating system..... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2"

Memory consumption

Roll.... 16192

EM...... 16759360

Heap.... 0

Page.... 401408

MM Used. 14941856

MM Free. 1814208

User and Transaction

Client.............. 100

User................ "BUYER99"

Language Key........ "E"

Transaction......... "BBPSC01 "

Transactions ID..... " "

Program............. "SAPLBBP_PDH"

Screen.............. "SAPLBBP_SC_UI_ITS 1000"

Screen Line......... 48

Information on caller of Remote Function Call (RFC):

System.............. "########"

Database Release.... 700

Kernel Release...... 700

Connection Type..... "E" (2=R/2, 3=ABAP System, E=Ext., R=Reg. Ext.)

Call Type........... "synchron and non-transactional (emode 0, imode 0)"

Inbound TID.........." "

Inbound Queue Name..." "

Outbound TID........." "

Outbound Queue Name.." "

Client.............. "###"

User................ "############"

Transaction......... " "

Call Program........." "

Function Module..... "EXTRACT_DATA"

Call Destination.... " EXCP 05 C00F LBBP_PDHU08 73

609 FUNE 00 0000 LBBP_PDHU08 79

610 -

-


00 0000 LBBP_PDHU08 79

611 STCK 02 C000 LBBP_PDHU08 1

612 STCK 02 C003 LBBP_PDHU08 1

613 CPOP 00 0000 LBBP_PDHU08 1

614 -

-


00 0000 LBBP_PDHU08 1

615 FUNP 31 0000 0041 8000 0000 8000 0000 0000 LBBP_PDHU09 1

Former Member
0 Kudos

Hi,

Please run program bbp_cnd_customizing check in se38

Select expert mode

If you are using classic scenario, IPC should be deactivated through relative badi

Else (standalone and extended scenario), IPC have to be activated.

If not, please ask your basis people to install/configure it.

Also sometimes reboot of Server helps.

BR,

Disha.

Pls reward points for useful answers.

Former Member
0 Kudos

Hi

To create a new Customer OSS message with SAP for faster resolution of the query, you need a S-User ID (OSS ID) and go through the SAP Official website

service.sap.com

Meanwhile, please go through the pointers below ->

OSS Note 673372 Short dumps UNCAUGHT_EXCEPTION in SRM 3.0, 4.0, and 5.0

Regards

- Atul