topic Re: Problem with BAPI_FTR_PAYDET_DELETE in Application Development and Automation Discussions

Problem with BAPI_FTR_PAYDET_DELETE

Former Member — Wed, 25 Jun 2014 11:21:38 GMT

Hello,

I want to change the payment-details within security-transactions concerning "House Bank". I plan to do this using

BAPI_FTR_PAYDET_DELETE and BAPI_FTR_PAYDET_CREATE.

To start I created an ABAP to call "BAPI_FTR_PAYDET_DELETE". I provided this FM with the details of the payment-detail to be

erased. Within debugger I saw that the correct deal-data and payment-data were selected and the correct entry within VTBZV was selected for deletion.

At the end the SAVE-Method was called and the BAPI returned with SY-SUBRC = 0 and also the table for all kinds of messages contained no entry.

So I supposed that the BAPI was executed successfully.

But the real result was absolutely nothing: within the security-deal all payment-deals still were present. There were also no messages within system-log.

Something must have gone wrong but I got no information from the BAPI.

Does anyone know more about BAPI_FTR_PAYDET_DELETE?

Thanx a lot!

Dietrich Kunze

Re: Problem with BAPI_FTR_PAYDET_DELETE

VenkatRamesh_V — Wed, 25 Jun 2014 11:44:56 GMT

Hi, Dietrich,

Pass Fields with the correct Format.

Use this Function module for Conversion 'CONVERSION_EXIT_ALPHA_INPUT'

Regards,

Venkat.

Re: Problem with BAPI_FTR_PAYDET_DELETE

Former Member — Thu, 26 Jun 2014 06:53:54 GMT

Hi Venkat,

thanx for your reply.

What is your intention using this FM? Do you suggest to apply it on the input-parameters?

Regards

Dietrich

Re: Problem with BAPI_FTR_PAYDET_DELETE

VenkatRamesh_V — Thu, 26 Jun 2014 07:12:56 GMT

Hi,

In bapi some fields never consider,if you never delcared with the domain size.

Eg: table entry contains 000123, in excel contains entry without zero means it will never consider.

Use that FM and try.

Regards,

Venkat.

Re: Problem with BAPI_FTR_PAYDET_DELETE

Former Member — Thu, 26 Jun 2014 10:02:07 GMT

Hi Venkat,

I took a very close look at the BAPI within debugger and finally found the reason: at the end this BAPI calls an FM IN UPDATE TASK and this requires mandatory a COMMIT WORK within the calling program.

I completely forgot that. Sorry bothering you!

Regards & thanx for your patience

Dietrich