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

Accounting Document saved without a Billing Document

Former Member
0 Likes
1,684

Hello Experts,

Our client creates credit memo's through a custom program for certain schemes. While executing the report, it saves some credit memo's displaying a success message. But few credit memo's are not updated in the system. While the accounting documents are saved for the same.

We checked the timestamp of accounting document to track for any abap dump. Below is the abap dump for the same. Please help analyse the same.

Thanks in advance,

Aniket

ABAP Dump Analysis

______________________________________________________________

Category               ABAP Programming Error

Runtime Errors         MESSAGE_TYPE_X

ABAP Program           SAPLRWCL

Application Component  FI

Date and Time          07.09.2016 09:55:34

______________________________________________________________

Short Text

     The current application has triggered a termination with a short dump.

______________________________________________________________

What happened?

     The current application program has detected a situation that should

     not occur. A termination with short dump has therefore been triggered

     by the key word MESSAGE (type X).

______________________________________________________________

Error analysis

    Short text of the error message:

    Document 9031707050 1000 is locked by another user

    Long text of the error message:

    Technical information about the message:

    Message class....... F5

    Number.............. 302

    Variable 1.......... 9031707050

    Variable 2.......... 1000

    Variable 3..........

    Variable 4.......... " "

______________________________________________________________

How to correct the error

    Probably the only way to eliminate the error is to correct the program.

    -

    If the error occurs in a non-modfied SAP program, you might be able to

    find a solution in the SAP Notes system. If you have access to the SAP

    Notes system, check there first using the following keywords:

    "MESSAGE_TYPE_X"

    "SAPLRWCL" bzw. LRWCLF01

    "DOCUMENT_POST"

    If you cannot solve the problem yourself, please send the following

    information to SAP:

______________________________________________________________

User and Transaction

    Client................. 500

    User..................

    Language key.......... E

    Transaction......... VF01

    Transaction ID...... 57CB76E07F6822E1E1000000C0A800AA

    EPP whole context ID...... 569B59B139FE1EE69D964726DF229700

    EPP connection ID........ 00000000000000000000000000000000

    EPP call counter......... 0

    Program.............. SAPLRWCL

    Screen.............. SAPMV60A                                0103

    Screen line.......... 37

    Active debugger..... "none"

______________________________________________________________

Line  SourceCde

______________________________________________________________

  673   ld_gjahr = sy-datum(04).

  674

  675   CALL FUNCTION 'RWIN_CHECK_SUBSET'

  676     EXPORTING

  677       i_event     = r_event

  678       i_gjahr     = ld_gjahr

  679       i_process   = r_process

  680       i_subset    = gd_subset

  681       i_comp_only = r_comp

  682     TABLES

  683       t_trwpr     = lt_trwpr.

  684

  685   LOOP AT lt_trwpr.

  686

  687     CALL FUNCTION lt_trwpr-function

  688       EXPORTING

  689         i_awtyp       = r_awtyp

  690         i_awref       = r_awref

  691         i_aworg       = r_aworg

  692         i_awsys       = r_awsys

  693       EXCEPTIONS

  694         error_message = 01

  695         OTHERS        = 02.

  696

  697     IF NOT sy-subrc IS INITIAL.

698       ld_msgty = sy-msgty.

699       IF NOT ld_msgty = 'A'.

700 *       switch message type to 'X' => no commit and short dump

701         ld_msgty = 'X'.

702       ENDIF.

>>>>       MESSAGE ID     sy-msgid

704               TYPE   ld_msgty

705               NUMBER sy-msgno

706               WITH   sy-msgv1

707                      sy-msgv2

708                      sy-msgv3

709                      sy-msgv4.

710     ENDIF.

711   ENDLOOP.

712

713   PERFORM check_components             " post

714           TABLES lt_trwpr

715           USING  'C'.

716

717 ENDFORM.                    "DOCUMENT_POST

718 *

719 *---------------------------------------------------------------------*

720 *       FORM RWIN1_READ                                               *

721 *---------------------------------------------------------------------*

722 *       Aufruf des RW-Interfaces                                      *

______________________________________________________________

SY-SUBRC 1

SY-INDEX 0

SY-TABIX 2

SY-DBCNT 0

SY-FDPOS 0

SY-LSIND 0

SY-PAGNO 0

SY-LINNO 1

SY-COLNO 1

SY-PFKEY KM

SY-UCOMM SICH

SY-TITLE Billing Document Create: Billing Document Overview

SY-MSGTY X

SY-MSGID F5

SY-MSGNO 302

SY-MSGV1 9031707050

SY-MSGV2 1000

SY-MSGV3

SY-MSGV4

SY-MODNO 0

SY-DATUM 20160907

SY-UZEIT 095534

SY-XPROG SAPLBPFC

SY-XFORM CONVERSION_EXIT

______________________________________________________________

Hello Experts,

Our client creates credit memo's through a custom program for certain schemes. While executing the report, it saves some credit memo's displaying a success message. But few credit memo's are not updated in the system. While the accounting documents are saved for the same.

We checked the timestamp of accounting document to track for any abap dump. Below is the abap dump for the same. Please help analyse the same.

Thanks in advance,

Aniket

ABAP Dump Analysis

______________________________________________________________

Category               ABAP Programming Error

Runtime Errors         MESSAGE_TYPE_X

ABAP Program           SAPLRWCL

Application Component  FI

Date and Time          07.09.2016 09:55:34

______________________________________________________________

Short Text

     The current application has triggered a termination with a short dump.

______________________________________________________________

What happened?

     The current application program has detected a situation that should

     not occur. A termination with short dump has therefore been triggered

     by the key word MESSAGE (type X).

______________________________________________________________

Error analysis

    Short text of the error message:

    Document 9031707050 1000 is locked by another user

    Long text of the error message:

    Technical information about the message:

    Message class....... F5

    Number.............. 302

    Variable 1.......... 9031707050

    Variable 2.......... 1000

    Variable 3..........

    Variable 4.......... " "

______________________________________________________________

How to correct the error

    Probably the only way to eliminate the error is to correct the program.

    -

    If the error occurs in a non-modfied SAP program, you might be able to

    find a solution in the SAP Notes system. If you have access to the SAP

    Notes system, check there first using the following keywords:

    "MESSAGE_TYPE_X"

    "SAPLRWCL" bzw. LRWCLF01

    "DOCUMENT_POST"

    If you cannot solve the problem yourself, please send the following

    information to SAP:

______________________________________________________________

User and Transaction

    Client................. 500

    User..................

    Language key.......... E

    Transaction......... VF01

    Transaction ID...... 57CB76E07F6822E1E1000000C0A800AA

    EPP whole context ID...... 569B59B139FE1EE69D964726DF229700

    EPP connection ID........ 00000000000000000000000000000000

    EPP call counter......... 0

    Program.............. SAPLRWCL

    Screen.............. SAPMV60A                                0103

    Screen line.......... 37

    Active debugger..... "none"

______________________________________________________________

Line  SourceCde

______________________________________________________________

  673   ld_gjahr = sy-datum(04).

  674

  675   CALL FUNCTION 'RWIN_CHECK_SUBSET'

  676     EXPORTING

  677       i_event     = r_event

  678       i_gjahr     = ld_gjahr

  679       i_process   = r_process

  680       i_subset    = gd_subset

  681       i_comp_only = r_comp

  682     TABLES

  683       t_trwpr     = lt_trwpr.

  684

  685   LOOP AT lt_trwpr.

  686

  687     CALL FUNCTION lt_trwpr-function

  688       EXPORTING

  689         i_awtyp       = r_awtyp

  690         i_awref       = r_awref

  691         i_aworg       = r_aworg

  692         i_awsys       = r_awsys

  693       EXCEPTIONS

  694         error_message = 01

  695         OTHERS        = 02.

  696

  697     IF NOT sy-subrc IS INITIAL.

698       ld_msgty = sy-msgty.

699       IF NOT ld_msgty = 'A'.

700 *       switch message type to 'X' => no commit and short dump

701         ld_msgty = 'X'.

702       ENDIF.

>>>>       MESSAGE ID     sy-msgid

704               TYPE   ld_msgty

705               NUMBER sy-msgno

706               WITH   sy-msgv1

707                      sy-msgv2

708                      sy-msgv3

709                      sy-msgv4.

710     ENDIF.

711   ENDLOOP.

712

713   PERFORM check_components             " post

714           TABLES lt_trwpr

715           USING  'C'.

716

717 ENDFORM.                    "DOCUMENT_POST

718 *

719 *---------------------------------------------------------------------*

720 *       FORM RWIN1_READ                                               *

721 *---------------------------------------------------------------------*

722 *       Aufruf des RW-Interfaces                                      *

______________________________________________________________

SY-SUBRC 1

SY-INDEX 0

SY-TABIX 2

SY-DBCNT 0

SY-FDPOS 0

SY-LSIND 0

SY-PAGNO 0

SY-LINNO 1

SY-COLNO 1

SY-PFKEY KM

SY-UCOMM SICH

SY-TITLE Billing Document Create: Billing Document Overview

SY-MSGTY X

SY-MSGID F5

SY-MSGNO 302

SY-MSGV1 9031707050

SY-MSGV2 1000

SY-MSGV3

SY-MSGV4

SY-MODNO 0

SY-DATUM 20160907

SY-UZEIT 095534

SY-XPROG SAPLBPFC

SY-XFORM CONVERSION_EXIT

______________________________________________________________

4 REPLIES 4
Read only

Lakshmipathi
Active Contributor
0 Likes
1,165

Moved from SAP ERP Sales and Distribution (SAP SD) to ABAP Development.  Try to post in the right forum.  In the past also, you have been asked to do so.

Read only

0 Likes
1,165

Thanks for the correction, Lakshmipathi. Will keep it in mind next time.

Read only

RaymondGiuseppi
Active Contributor
0 Likes
1,165

Well is the 'Document 9031707050 1000 is locked by another user' not clear enough;add some ENQUEUE Fm in the program to lock the document.

Read only

Former Member
0 Likes
1,165

Dear Aniket,

Please read the below SNOTE :

178545 - F5302: Document & & is locked by another user

I don't know if it is still revelant with your system or not.

Regards,

Yance