cancel
Showing results for 
Search instead for 
Did you mean: 

Dump while adding a shopping cart in work area in Carryout Sourcing

Former Member
0 Kudos

Hi Experts,

We are getting dump while adding a shopping cart to the work area in Carryout Sourcing.

We want to replicate the Purchase Requisition from R/3 to SRM. And SC contains the limit item with free text service.

The dump details are as follows :

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

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:

Buffer 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_PD_ABORT"

"SAPLBBP_PDH" or "LBBP_PDHU08"

"BBP_PD_ABORT"

Information on where terminated

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

The main program was "SAPLBBP_SOCO_UI_ITS ".

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

of the (Include) program "LBBP_PDHU08".

READ TABLE lt_callstack INTO ls_callstack2 INDEX 4.

CONCATENATE '/' ls_callstack2-eventtype

ls_callstack2-eventname ls_callstack2-progname

INTO lv_msgarg3 SEPARATED BY space.

CALL FUNCTION 'BBP_ALERT_INTERNAL_OT'

EXPORTING

msgid = gc_msgid_bbp_pd

msgno = 047

msgarg1 = lv_msgarg1

msgarg2 = lv_msgarg2

msgarg3 = lv_msgarg3.

MESSAGE ID gc_msgid_bbp_pd TYPE c_msgty_i NUMBER iv_msg_no

WITH ls_callstack1-eventtype

ls_callstack1-eventname

ls_callstack1-progname.

rollback work.

  • get the messages from the application log

TRY.

CALL FUNCTION 'BBP_PD_LOG_GET_MESSAGES'

TABLES

e_messages = lt_messages.

CATCH cx_bbp_pd_abort.

REFRESH lt_messages.

ENDTRY.

RAISE EXCEPTION TYPE cx_bbp_pd_abort EXPORTING

worked_on_document = lv_guid

t100_msgid = gc_msgid_bbp_pd

t100_msgno = iv_msg_no

t_appl_log_messages = lt_messages.

ENDFUNCTION.

Could you please help me on this, how to rectify the dump ?

Thank you very much in advance.

Accepted Solutions (0)

Answers (2)

Answers (2)

ricardo_cavedini
Employee
Employee
0 Kudos

Hello,

I have seen this dump many times because the ERP version defined in table BBP_BACKEND_DEST was not correct.

Please, check the following note related to this configuration:

1230789 - Dump: BBPSOCO01 at include LBBP_PDH_TEOF0B

Kind regards,

Ricardo

former_member183819
Active Contributor
0 Kudos

what about item category of PR ? and give more data on this PR.

see 16 limitations from SAP

Note 505030 - Restrictions for the integration of external requirements

i try when i get time .

Muthu

Former Member
0 Kudos

Hi

Also check notes:

899646 - Restriction in External Requirements Integration - Services

864343 - Enter an expected value error during 'no limit' PR transfer

Regards

Virender Singh