topic Re: BAPI_TRANSACTION_COMMIT gives short dump in Application Development and Automation Discussions

BAPI_TRANSACTION_COMMIT gives short dump

Former Member — Thu, 15 May 2008 08:45:58 GMT

in my report i make something like this


CALL FUNCTION 'BAPI_BUPR_RELATIONSHIP_CREATE'
      EXPORTING
        businesspartner1     = lv_destination_partner
        businesspartner2     = lv_source_parnter
        relationshipcategory = lv_rel_category
        validfromdate        = sy-datum
        validuntildate       = '99990101'
      TABLES
        return               = gt_ret_table.

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
    IMPORTING
      return = gs_ret_elem.

After performing first function table gt_ret_table returns no errors (messages type I and S) and after BAPI_TRANSACTION_COMMIT i have short dump (MESSAGE TRANSACTION X):

Program CL_CRM_CHM_PDM_COMHUB=========CP

INCLUDE CL_CRM_CHM_PDM_COMHUB=========CM001

Line 10

Module type (METHOD)

Module name CONSTRUCTOR


*=======================================================================
METHOD constructor .
*=======================================================================

*  DATA:
*    lt_return TYPE bapiret2_t.

* precondition check
  IF iv_partner_guid IS INITIAL.
   MESSAGE x000(crm_chm_bp_cch)
      WITH 'PROGRAM ERROR: Precondition Failed'.            "#EC *
  ENDIF.

*  CALL FUNCTION 'BUPA_NUMBERS_GET'
*    EXPORTING
*      iv_partner_guid = iv_partner_guid
*    TABLES
*      et_return       = lt_return.
*  IF NOT lt_return IS INITIAL.
*    MESSAGE x000(crm_chm_bp_cch)
*      WITH 'PROGRAM ERROR: Precondition Failed'.            "#EC *
*  ENDIF.

  mv_partner_guid = iv_partner_guid.
  mv_xsave        = iv_xsave.

ENDMETHOD.

What can be wrong?

Any sugestions?

reg.

Wojciech

Edited by: Wojciech Moroz on May 15, 2008 10:48 AM

Edited by: Wojciech Moroz on May 15, 2008 10:50 AM

Re: BAPI_TRANSACTION_COMMIT gives short dump

Former Member — Thu, 15 May 2008 08:54:04 GMT

Hi, have you done the check after using the BAPI_ function module?

Like this...

CALL FUNCTION 'BAPI_BUPR_RELATIONSHIP_CREATE'

EXPORTING

businesspartner1 = lv_destination_partner

businesspartner2 = lv_source_parnter

relationshipcategory = lv_rel_category

validfromdate = sy-datum

validuntildate = '99990101'

TABLES

return = gt_ret_table.

if sy-subrc = 0.

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

IMPORTING

return = gs_ret_elem.

endif.

I Think in your 'BAPI_BUPR_RELATIONSHIP_CREATE'

function module having some problem. PLease check the return table from this FM.

And then proceed.

Hope it will help you.

Regards,

Madan.

Re: BAPI_TRANSACTION_COMMIT gives short dump

former_member156446 — Thu, 15 May 2008 08:56:53 GMT

Check this :

CALL FUNCTION 'BAPI_BUPR_RELATIONSHIP_CREATE'
      EXPORTING
        businesspartner1     = lv_destination_partner
        businesspartner2     = lv_source_parnter
        relationshipcategory = lv_rel_category
        validfromdate        = sy-datum
        validuntildate       = '99990101'
      TABLES
        return               = gt_ret_table.
 
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'.

Re: BAPI_TRANSACTION_COMMIT gives short dump

Former Member — Thu, 15 May 2008 08:59:06 GMT

before calling the fm bapi_transaction_commit

read table gt_ret_table with key type = 'S'.

if sy-subrc eq 0.

then call bapi transaction commit

Re: BAPI_TRANSACTION_COMMIT gives short dump

Former Member — Thu, 15 May 2008 09:11:36 GMT

Thanks for tips but my problem is still unsolved. I did check sy-subrc = 0 after frist FM and tried BAPI_TRANSACTION_COMMIT without return and still i get the same crash

any further ideas?

Re: BAPI_TRANSACTION_COMMIT gives short dump

Former Member — Thu, 15 May 2008 09:39:45 GMT

Hi Wojciech,

Try by sending export parameter 'WAIT' also like

CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'

EXPORTING

WAIT = 'X'

IMPORTING

.....

Regards,

Suresh

Re: BAPI_TRANSACTION_COMMIT gives short dump

Former Member — Thu, 15 May 2008 09:46:30 GMT

I tried this before - still nothing

regards

Wojciech

Re: BAPI_TRANSACTION_COMMIT gives short dump

Sm1tje — Thu, 15 May 2008 09:50:55 GMT

Like already mentioned before, the problem probably is not the BAPI_TRANSACTION_COMMIT but rather the first BAPI you are calling. One thing you can and should do is set a break point at point where short dump occurs and via the call stack try to determine, why the BP guid is not available. My guess it that one of your BP's has no BP guid created (yet).

Re: BAPI_TRANSACTION_COMMIT gives short dump

Former Member — Thu, 15 May 2008 13:09:22 GMT

Hi,

maybe just try with commit work.

And you should read about fm. 'BUS_BAPI_CLEARBUFFER'.

best regards, Robert

Re: BAPI_TRANSACTION_COMMIT gives short dump

Former Member — Thu, 15 May 2008 13:17:10 GMT

tried with commit_work, with fm BUPR_RELATIONSHIP_CREATE. I Also tried to create a new partner with filling all data. Still nothing.

Maybe it's some kind of bug i CRM 5.0 ?

Re: BAPI_TRANSACTION_COMMIT gives short dump

Former Member — Thu, 15 May 2008 13:36:25 GMT

As I can see in fm parameters VALIDFROMDATE and VALIDUNTILDATE has the default value ()

So you may just do not use them at all ?

Re: BAPI_TRANSACTION_COMMIT gives short dump

Former Member — Thu, 15 May 2008 13:41:17 GMT

already tried. Without success

regards

Wojciech

Re: BAPI_TRANSACTION_COMMIT gives short dump

Former Member — Fri, 03 Sep 2010 14:32:50 GMT

Hi, Have u managed to sloved the problem? I'm having same problem. can you please share you solution for this issue?

Kind regards,

Anil