cancel
Showing results for 
Search instead for 
Did you mean: 

Payment method - Infotype 9

Former Member
0 Kudos

Hi

For BACS payment method, we currently use the classic payment medium. We are currently considering implementing the payment medium workbench in a new payment method.

As far as the payment methods visible in Infotype 0009, are we able to hide the old payment method, otherwise we will have 2 BACS payment methods.

thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

former_member193210
Active Contributor
0 Kudos

I don't know about BACS payments, but wouldn't you see only the current BACS payment method if you delimit IT0009?

Former Member
0 Kudos

Hi Remi

I mean from the Payment method selection in IT0009. This is how it currently looks like in Dev, but it would be confusing to users. Our intention is that Finance continue to use the old payment method B, and Payroll use the new one (E).

Any thoughts apart from changing the name of the payment method?

former_member193210
Active Contributor
0 Kudos

Hello Farhan,

We also see the other payment methods but have a "Payroll Fund Transfer" and a "Finance Fund Transfer".

Furthermore, we added a little ABAP code to the Infotype during the infotype's validation so that an Error message is generated for any payment method other than "Payroll Fund Transfer".   (Cash or Cheque are also not allowed for Payroll).

Talk your your ABAP resource as it should be possible for you to generate an error message if payment method B is selected (therefore the Infotype can't be saved until a valid payment method is selected).

Former Member
0 Kudos

Thanks for the useful advice.

Former Member
0 Kudos

Hi Farhan

Further to the advice from Remi, from a usability perspective, I assume you would also change the configuration of Feature ZLSCH to default in your new payment method type once you are ready to deploy it? If you really need to tie down use of specific payment types, then additional validation such as suggested by Remi can also be developed. However, a simple configuration change (combined with a very small amount of end-user training/configuration) would be the cheapest/simplest option, especially if your users are back-end/regular users. If you use ESS, you would also need to consider the portal Personal Information application for maintaining Bank Details, if you decide to go down the route of restricting usage via a customer enhancement.

Best regards

Former Member
0 Kudos

Hi Alison

Thanks for your perspective.

We have ZLSCH set for Cheque, and likely will retain this setting.

kind regards