Control extended classic mode BADI

[Former Member]

Hi,

I am trying to setup the system to work in the extended classic scenario.

I have activated the extended classic switch and i am using the BADI control extended classic badi.

For product categories that i want to use in extended classic mode, the logic inside the BADI returns a "X"

For Eg: I have a product cat "Boards" for whcih the BADI returns "X"

When i add this pruduct category to my shopping cart, there is a dump in ITS.

However, I remove the product cat "Board" from the BADI, I am able to add this product cat to the shopping cart without a dump.

Please let me know why this is happening.

Dump:

Runtime Errors UNCAUGHT_EXCEPTION

Except. CX_BBP_PD_ABORT

Date and Time 04/21/2010 06:07:37

Short dump has not been completely stored (too big)

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.

Please help

Thnaks,

Vignesh

[ricardo_cavedini]

Hello,

Have you maintained such product category in "Define backend systems for product category"?

I have this badi active in my test system and extended classic product categories are pointing to backend system in both entries "Source" and "Target".

Also, if you are using the badi to set the extended classic scenario flag, why to change it in SPRO as well?

As per my understanding, once the badi is controlling this switch, you do not need to set the ECS in SPRO. Off course, this is my understanding. Not sure if I am correct.

Kind regards,

Ricardo

[Former Member]

Hi, Vignesh

It's really difficult to find out the rootcause based on these limisted information.

Not sure it caused by the call of the function module BBP_PD_SC_GETDETAIL

from the BADI BBP_EXTLOCALPO_BADI.

If this BADI is called during the update of the shopping cart(BBP_PD_SC_UPDATE)

when it is in the process of updating the PD layer buffers. When a

BBP_PD_SC_GETDETAIL is called during that state, the buffer tables are

of inconsistent state. When the system is in the process of updating the 2nd item to the

PD layer buffers, a call of GETDETAIL is made wherein the system looks

for the 2nd item in the database and dumps on not finding it.

Regards

Lauren

[Former Member]

Hi Laurent,

I am getting the foloowing error. Can you identify what is going on ?

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

Source Code Extract

Line SourceCde

43

44 READ TABLE lt_callstack INTO ls_callstack2 INDEX 4.

45 CONCATENATE '/' ls_callstack2-eventtype

46 ls_callstack2-eventname ls_callstack2-progname

47 INTO lv_msgarg3 SEPARATED BY space.

48

49 CALL FUNCTION 'BBP_ALERT_INTERNAL_OT'

50 EXPORTING

51 msgid = gc_msgid_bbp_pd

52 msgno = 047

53 msgarg1 = lv_msgarg1

54 msgarg2 = lv_msgarg2

55 msgarg3 = lv_msgarg3.

56

57 MESSAGE ID gc_msgid_bbp_pd TYPE c_msgty_i NUMBER iv_msg_no

58 WITH ls_callstack1-eventtype

59 ls_callstack1-eventname

60 ls_callstack1-progname.

61

62 rollback work.

63

64 * get the messages from the application log

65 TRY.

66 CALL FUNCTION 'BBP_PD_LOG_GET_MESSAGES'

67 TABLES

68 e_messages = lt_messages.

69 CATCH cx_bbp_pd_abort.

70 REFRESH lt_messages.

71 ENDTRY.

72

>>>>> RAISE EXCEPTION TYPE cx_bbp_pd_abort EXPORTING

74 worked_on_document = lv_guid

75 t100_msgid = gc_msgid_bbp_pd

76 t100_msgno = iv_msg_no

77 t_appl_log_messages = lt_messages.

78

79 ENDFUNCTION.

Pls help

[Former Member]

The systems does not dump when i use the classical scenario..

Could this be any config that i am missing so that the system dumps in extended classic mode??