We had a similar requirement some time ago. I think the more standardized way would be to get the encryption done by a middleware (e.g. a PI system). If you like to do it directly on the SAP server, SAP is not offering a solution out of the box.
We did it like this:
- We used gpg on the underlying Linux operating system to create and maintain the relevant PGP keys
- We created an "external operating system command" in transaction SM49, which is calling gpg with the respective parameters for encryption a file (e.g. "gpg --trust-model always –recipient recipient@address -v –encrypt")
- We created another "external operating system command" in transaction SM49 to call the "mv" command in order to be able to move files from one folder to another
- We created an enhancement at the end of function module "FI_PAYM_MEDIUM_CLOSE" which is calling the above mentioned system call, passing over the file name as parameter and moving the file to the right outbound folder
With this setup, the file is created as usual on the given output folder, afterwards our custom code is triggering the encryption of the file and moving the file to our expected outbound folder where it is getting picked up by our PI solution and sent to the bank.
We also implemented a custom table to maintain some parameters to be more flexible when calling the system command, but this is optional.
I hope you got an idea how this could be solved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.