Payment information and management of data

[Former Member]

Hi,

When it comes to tables DPAYH and DPAYP, SAP says just delete data older than a certain period of time. The issue we are running into is that these tables store information on the bank account used to make payments and as far as we can tell, SAP does not store this information anywhere else. Here is an issue that comes up:

- Customer X obtains someoneu2019s bank account information and uses that information to pay his/her electric bill

- A few months pass, DPAYP and DPAYH data is deleted

- We are notified by the owner of a bank account that the account has money withdrawn by PSEG and wants to know why because say the person does not have PSEG as its electricity or gas provider

- We begin research to see where was this account used if at all to pay anything

- Because DPAYP and DPAYH data is deleted, analysis cannot complete on the account used to pay any bills

Here is another example:

- Customer X appears to have used fraudulent means to pay his electric/gas bill

- We are asked to review the account of customer X and essentially rebuild it to see how much of the fraudulent activity took place

- By regulation, we need to and can legally go back as far as 6 years to rebuild a customer account.

- We would not be able to validate if any of the payments in the past were made through fraudulent or legal means as payment data is not available (which bank account etc.)

My question is therefore, how can we get the two sides to meet so that on one side data from DPAYH and DPAYP can be deleted, yet on the other there is history available somewhere in the system on the source of the payment, which can be used to address cases such as the ones I have described above?

Mike

[AmlanBanerjee · Accepted solution]

Hi Mike,

I don't think, you will be able to retrieve the DPAYH\DPAYP data once it gets deleted SAP using the SAP program RFKPYD00.

On a pro active basis, you can go for either of the following options-

Option-1

DPAYH/DPAYP contains payment data as well as exception data for the various payment runs.However, the main concern is the payment data, as it is the data that is sent to the bank.

These payment data can be easily segregated from the exception data based on the field (DPAYH-GRPNO).

So you can create two custom tables like DPAYH\DPAYP in IS-U and store only the payment data along with the relevant fields that you want to store for future references.

You can update these custom tables during the processing of the payment medium job (creation of the file that is sent to bank),

Option-2

If your SAP IS-U system is connected to BW\BI, then you can also retrieve the payment relevant data from the DPAYH\DPAYP tables in to BW\BI through a BW\BI extractor and then design a report which will give you the relevant details.

Thanks,

Amlan