topic Re: DUMP in SAPLOPTB program - COMMIT_IN_POSTING in Application Development and Automation Discussions

DUMP in SAPLOPTB program - COMMIT_IN_POSTING

Former Member — Mon, 10 Oct 2011 01:54:23 GMT

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

Re: DUMP in SAPLOPTB program - COMMIT_IN_POSTING

Former Member — Mon, 10 Oct 2011 03:03:23 GMT

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

Re: DUMP in SAPLOPTB program - COMMIT_IN_POSTING

koolspy_ultimate — Mon, 10 Oct 2011 04:18:18 GMT

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

Re: DUMP in SAPLOPTB program - COMMIT_IN_POSTING

koolspy_ultimate — Mon, 10 Oct 2011 09:41:44 GMT

Hi,

apply OSS note 1539662

and this solves your purpose.

let me know, If you get any doubts,

Regards,

koolspy.

Re: DUMP in SAPLOPTB program - COMMIT_IN_POSTING

Former Member — Mon, 10 Oct 2011 12:53:00 GMT

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

Re: DUMP in SAPLOPTB program - COMMIT_IN_POSTING

koolspy_ultimate — Tue, 11 Oct 2011 03:24:46 GMT

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.

Re: DUMP in SAPLOPTB program - COMMIT_IN_POSTING

Former Member — Tue, 11 Oct 2011 11:08:38 GMT

Solved.