Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

DUMP with Commit work and wait

Former Member
0 Likes
1,300

Hi all!! I need your help again!!

I have this:



  WAIT UP TO 1 SECONDS.

                      UPDATE zpsc_ofertes
                      SET status = 'ENTRA'
                          status_v = 'CO/AA'
                      WHERE oferta = zpsc_ofertes-oferta
 AND versio = var_vers_destino.


CALL FUNCTION 'STATUS_UPDATE_ON_COMMIT'.
          .

    COMMIT WORK AND WAIT.

CALL FUNCTION 'BUFFER_REFRESH_ALL'
          .

That code creates a dump... Why could be this problem??

Thanks!!

5 REPLIES 5
Read only

Former Member
0 Likes
888

Hi

What error you are getting? at which place.,,,,

Could you please tell me ?

Regards

karthik.,,

Edited by: karthikeyan palaniayya on Mar 18, 2008 2:29 PM

Read only

0 Likes
888

Let's see.

The current application triggered a termination with a short dump.

¿Qué ha sucedido?

The current application program detected a situation which really

should not occur. Therefore, a termination with a short dump was

triggered on purpose by the key word MESSAGE (type X).

¿Qué puede hacer?

Print out the error message (using the "Print" function)

and make a note of the actions and input that caused the

error.

To resolve the problem, contact your SAP system administrator.

You can use transaction ST22 (ABAP Dump Analysis) to view and administer

termination messages, especially those beyond their normal deletion

date.

The code...

000010 *

000020 ***INCLUDE LPS_BAPIF01 .

000030 *

000040 *&

000050 *& Form CHK_PRECOMMIT

000060 *&

000070 * check precommit

000080 *

000090 FORM chk_precommit.

000100

000110 DATA: chk_precommit_ok TYPE c,

000120 chk_error type c.

000130

000140 CALL FUNCTION 'PS_FLAG_GET_GLOBAL_FLAGS'

000150 IMPORTING

000160 e_precommit_ok = chk_precommit_ok

000170 e_error = chk_error.

000180

000190 IF chk_precommit_ok = space.

000200 * Precommit wurde noch nicht aufgerufen.

> MESSAGE x030(cnif_pi).

000220 ELSEIF chk_precommit_ok <> 'Y'.

000230 * Precommit wurde nicht erfolgreich durchlaufen.

000240 MESSAGE x033(cnif_pi).

000250 elseif not chk_error is initial.

000260 * At least one single BAPI failed

000270 MESSAGE x056(cnif_pi).

000280 ENDIF.

000290

000300 * commit work was called successfully after the precommit

000310 PERFORM ps_bapi_init_global_variables.

000320

000330 ENDFORM. " CHK_PRECOMMIT

000340

Read only

0 Likes
888

Please remove the exit message from your code and try.

Exit Message

Message of message type X. Exit messages terminate the running program and create a short dump

a®

Read only

0 Likes
888

Hi

I believe you're calling those functions module in a wrong way, try to call the fm PS_FLAG_SET_GLOBAL_FLAGS in order to set the flag for the PRECOMMIT.

The system is raising an error message because that flag is not setted.

Max

Edited by: max bianchi on Mar 18, 2008 2:56 PM

Read only

0 Likes
888

Sorry, I dont understand you...

The bapi calls to the PS_FLAG_SET_GLOBAL_FLAGS...