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 in SAPLOPTB program - COMMIT_IN_POSTING

Former Member
0 Likes
1,154

Hi All,

We are getting a dump when creating parked invoices from scanned documents. Can you please help with this.

*

The dump is occuring at this statement. - COMMIT WORK

32

call method cl_alink_connection=>insert

33

exporting

34

link = l_link

35

barcode = barcode

36

exceptions

37

others = 1.

38

if SY-SUBRC = 0.

>>>>>

commit work.

40

else.

41

MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO

42

WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4

43

raising error_connectiontable.

| 44| endif.

*

thanks

guru.

Edited by: GuruCharan on Oct 10, 2011 7:40 AM

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
946

Hi

I suppose the dump is in fm ARCHIV_CONNECTION_INSERT

This fm is called in a posting process working in update task: here the commit doesn't allow.

In my system the code of fm above is:

data:
    l_link type toav0.

  l_link-mandt         = mandant.
  l_link-sap_object    = sap_object.
  l_link-object_id     = object_id.
  l_link-archiv_id     = archiv_id.
  l_link-arc_doc_id    = arc_doc_id.
  l_link-ar_object     = ar_object.
  l_link-ar_date       = ar_date.
  l_link-del_date      = del_date.
  l_link-reserve       = doc_type.

  call method cl_alink_connection=>insert
    exporting
      link                  = l_link
      barcode               = barcode
    exceptions
      others                = 1.
  if sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
            raising error_connectiontable.
  endif.

As you can see the commit is missing, that mean there's a SAP note corrects that dump: look at Oss Note

Max

6 REPLIES 6
Read only

Former Member
0 Likes
947

Hi

I suppose the dump is in fm ARCHIV_CONNECTION_INSERT

This fm is called in a posting process working in update task: here the commit doesn't allow.

In my system the code of fm above is:

data:
    l_link type toav0.

  l_link-mandt         = mandant.
  l_link-sap_object    = sap_object.
  l_link-object_id     = object_id.
  l_link-archiv_id     = archiv_id.
  l_link-arc_doc_id    = arc_doc_id.
  l_link-ar_object     = ar_object.
  l_link-ar_date       = ar_date.
  l_link-del_date      = del_date.
  l_link-reserve       = doc_type.

  call method cl_alink_connection=>insert
    exporting
      link                  = l_link
      barcode               = barcode
    exceptions
      others                = 1.
  if sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
            raising error_connectiontable.
  endif.

As you can see the commit is missing, that mean there's a SAP note corrects that dump: look at Oss Note

Max

Read only

koolspy_ultimate
Active Contributor
0 Likes
946

Hi,

the problem is that you are missing commit work in the fm ARCHIV_CONNECTION_INSERT.

Apply note 1539662

Release 700

correction instruction 1290720

i.e


  call method cl_alink_connection=>insert
    exporting
      link                  = l_link
      barcode               = barcode
    exceptions
      others                = 1.
  if SY-SUBRC = 0.
     commit work. " this must be added
  else.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
            raising error_connectiontable.
  endif.

Regards,

koolspy.

Edited by: koolspy on Oct 10, 2011 9:53 AM

Read only

0 Likes
946

Hi koolspy

The note 1539662 is right, but the correction is to delete the COMMIT WORK statament, not to add it, because the dumb is just raised by the COMMIT

Max

Read only

0 Likes
946

Hi ,

Sorry for my wrong post earlier


  call method cl_alink_connection=>insert
    exporting
      link                  = l_link
      barcode               = barcode
    exceptions
      others                = 1.
  if SY-SUBRC = 0.
     commit work. " error comes here
  else.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
            WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4
            raising error_connectiontable.
  endif.

Hi Max thanks for your reply and sorry for my wrong post (actually i mistyped it)

Guru apply the note which i mentioned earlier 1539662.

It will be solved.

Regards,

koolspy.

Read only

koolspy_ultimate
Active Contributor
0 Likes
946

Hi,

apply OSS note 1539662

and this solves your purpose.

let me know, If you get any doubts,

Regards,

koolspy.

Read only

Former Member
0 Likes
946

Solved.