short dump when executing tcode xk03

[Former Member]

Hi All,

I have developed BAPI for Vendor Master creation. When I execute it, the Vendor is getting created. But when I try to open that vendor in display mode using XK03 transaction, it is directing to short dump(program terminated).

The error analysis is saying -

The system attempted to use dynpro 0000 in program "SAPLSZA1".

This dynpro does not exist.

In ST22 transaction, I got the error details as in the file attached. Please kindly find the attachment.

Please look into this <removed by moderator>.

Thanks & Regards,

Murali.

Message was edited by: Thomas Zloch

[ThomasZloch]

It would be more interesting to know the code line, include name and the surrounding code where the dump occurs.

It looks like you have created some inconsistency involving the link to the vendor address data, how is your BAPI inserting the vendor data, are you directly updating SAP standard tables?

Thomas

[Former Member]

Hi Thomas,

Thanks for your reply. Please find the code as below:

  LV_OBJKEY = I_LFA1-LIFNR.

*Call function to update

  CALL FUNCTION 'BAPI_ADDRESSORG_CHANGE'

    EXPORTING

      OBJ_TYPE       = 'LFA1'

      OBJ_ID         = LV_OBJKEY

    IMPORTING

      ADDRESS_NUMBER = LV_ADDRESS_NUMBER

    TABLES

      BAPIAD1VL      = LT_BAPIAD1VL[]

      BAPIAD1VL_X    = LT_BAPIAD1VLX[]

      RETURN         = LT_RETURN[].

*if we get address no. of vendor, then no errors

  IF NOT LV_ADDRESS_NUMBER IS INITIAL.

*Do commit

    CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

  ENDIF.

Please suggest.

Thanks,

Murali

[former_member585060]

Hi,

     May be the address is not getting updated correctly or the above BAPI might not be updating the vendor address, add the BAPI_TRANSACTION_ROLLBACK when the LV_ADDRESS_NUMBER is initial.

IF NOT lv_address_number IS INITIAL.

   CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

ELSE.

   CALL FUNCTION 'BAPI_TRANSACTION_ROLLBACK'.

ENDIF.

Thanks & Regards

Bala Krishna

[Former Member]

Hi murali,

Use the commit work function module's.

or

further reference and how to use the commit work function modules like that info is available in below

link:

http://wiki.sdn.sap.com/wiki/display/ABAP/Function+Module+Test+Sequence

see the below link.

http://help.sap.com/abapdocu_70/en/ABAPCOMMIT.htm

I hope the first link more useful and if you have any q's let me know.

Regards

Mahesh.

[former_member282968]

Hi,

Once you get the short dump screen click on debugger button available at the application toolbar.This will take to the place of source code or screen where the error is occured from which you will be able to easily identify.

Since its a Dynpro error, it is related to screen and could be because of some conversion not working or something similar to that.

With regards,