facing dump issue in QM1 system..

[Former Member]

Hi Experts,

i am getting data in development system but didnot get the data from QM1

Please Let me know if you have any idea about Below issue..

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"

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

   Restrict the time interval to 10 minutes before and five minutes

after the short dump. Then choose "System->List->Save->Local File

(Unconverted)".

3. If the problem occurs in a problem of your own or a modified SAP

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 error occurred or which

actions and input led to the error.

Best Regards,

sowjanyak.

[Former Member]

please suggest me...

[Former Member]

Hi

Sowjanya

when you are getting this dump?, ex when searching for a contract/po

Regards,

Kiran

[Former Member]

hi kiran,

i got the data from DEV system but i am not getting the data from QM1 system..

Actually i am getting records but not more,when i am increasing the packet size its going to dump...

[konstantin_anikeev]

Please provide a complete dump

[Former Member]

Hi Anikeev,

Here i am providing complete dump issue..

can you check it please and give me any suggestion if you got any idea about issue...

Category               ABAP Programming Error

Runtime Errors         UNCAUGHT_EXCEPTION

Except.                CX_BBP_PD_ABORT

ABAP Program           SAPLBBP_PDH

Application Component  SRM-EBP

Date and Time          04.06.2014 07:02:36

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.

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

Missing Handling of Application Exception

    Program                                 RSFHGEN2

Trigger Location of Exception

    Program                                 SAPLBBP_PDH

    Include                                 LBBP_PDHU08

    Row                                     81

    Module type                             (FUNCTION)

    Module Name                             BBP_PD_ABORT

Source Code Extract

Line  SourceCde

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.

   75   IF iv_msgid IS SUPPLIED.

   76     lv_msgid = iv_msgid.

   77   ELSE.

   78     lv_msgid = gc_msgid_bbp_pd.

   79   ENDIF.

   80

>>>>>     RAISE EXCEPTION TYPE cx_bbp_pd_abort EXPORTING

   82         worked_on_document = lv_guid

   83         t100_msgid = lv_msgid

   84       t100_msgno = iv_msg_no

   85       t_appl_log_messages = lt_messages.

   86

   87 ENDFUNCTION.

[laurent_burtaire]

Hello,

most of the time, such error is due to ABAP code in BAdI.

For example, check KBA 1697675 - Use of SRM Function Modules in BAdI implementation causes "Buffer Table not up to date" er...

Look for other OSS notes with search terms "Buffer table not up-to-date": many deal with this problem.

Regards.

Laurent.