DME payment file to be exported automatically
We currently generate a payment medium in the form of a text file in different formats according to the payment method. This file is created when the last step of the payment run is carried out, and then the relevant person goes to DME administration FDTA and exports the file to a folder in the network. This file is afterwards imported into the bank system.
The problem we have is from the point of view of security and auditing since the file can be edited once exported and before being imported into the bank system.
For that, we are trying to automate the export of the payment medium. I have tried using the "file name" in the output control but although the log tells me that the output was transferred successfully, this is not happenning. However if I go again to FDTA and export the file (the system tells me that this was already exported although I can not find the file in the specified folder), then this is exported correctly (to the same specified location)
Can anyone tell me what we may be doing wrong? Also, does anyone know of a way of making the output file non-editable?
Or any other possible solutions to this issue?
thanks a lot
Kalyan K replied
Diego - Here I have just corrected the spelling mistake in the above posting:
If you use DMEE (payment medium workbench) then in the variant, which you define in OBPM4 and assign it to a specific house bank and account ID, you specify the file name and path.
Here '/usr/sap/interfaces/R3Q/out/common' is the path to the SAP server and CGS_OUT_TAXCH is the file name. The path is case sensitive and typically you use lowe case letters.
When you run print program, the files get created and stored in the SAP server as per the above path. SAP also adds a 4 digit number to the file name and the file will be CGS_OUT_TAXACH0163. The four digit number is incremented every time a new file is created, something similar to our FI document number, to prevent the old file being overwritten by a new file.
After the file is created you can access the file using T-code AL11. In this screen " SAP Directories", you can then drill down to the final destination where the file is stored. So first you will see '/usr/sap/interfaces' (which will be at the bottom of this AL11 scree). Double click on this. Then you will see R3Q (which is the SAP system in this case Quality. In Production it will probably R3P). Like this keep double clicking on each sub directory 'R3Q', then 'Out' and then 'Common' and you will find the file which was created by your print program.
In order to prevent people from changing/editing this file, nobody (except the administrator) gets access to this directory. There will be a batch job (which is event driven and it will be kicked off as soon as this file is saved in this directory) which will pick up this file, encrypt it using PGP encryption program and send this file to the bank using FTP program. So nobody ever handles the file manully.
When the bank receives the file they can decrypt the file (based on the keys or passwords given by you) and then they can read the file and process.
We can also ask the bank to send a confirmation. This confirmation will contain total no. of wires in the file and the amount. Once we get the confirmation we can cross check the total with the number of wires sent by us and the total amount. All this - the process of encryption, FTP to bank, receiving confirmation and checking the confirmation sent by bank within SAP - requires custom program. SAP also has a standard product called Bank Communication which is a
add-on product with a separate licence fee etc.
Hope the process is clear. By this process you can ensure that no user ever handles the fie manually.