3 weeks ago
Hi support,
I would like to open again this issue which we haven't solved with the client.
I have few questions regarding the creation of Payment file structure in the system:
1. Since SG is a pre-localized country, may I know which of the standard Payment Medium format is applicable to Singapore banks?
2. Since we need to create our own Payment File structure, we are confronted with the below scenarios:
2.1. Details requires to select Product Type (3 char) info provided by the bank. How are we able to assign or encode this data manually if we are to pull this data in the Output file, if we have limited options/fields available during payment processing? What are your suggestions/ field to use, if banks will require something like this?
2.2. Details also requires Transaction codes (2 char) info provided by the bank. Same question as 2.1.
2.3 Purpose of Payment (4 char) info provided by the bank. Same issue as 2.1.
Yes we are able to generate the file, however because of the missing data mentioned, bank file is always rejected.
Please advise.
Regards,
Request clarification before answering.
Dear Customer,
Thank you for your follow-up regarding the payment file generation for Singapore.
Please find below our inputs based on standard system capabilities:
1. Standard Payment Medium Format for Singapore
While Singapore is a pre-localized country in SAP Business ByDesign, no standard bank-specific Payment Medium Format (PMF) is currently delivered for SG banks.
2. Data Requirements in Payment File Output
Regarding the additional data fields required by your bank:
2.1. Product Type (3 characters)
2.2. Transaction Code (2 characters)
2.3. Purpose of Payment (4 characters)
These fields are not available in standard payment processing screens or configurations, and there are no dedicated fields in the standard system to capture this information during payment proposal or execution.
As this involves a custom payment file structure and enhancements to standard behavior,
If you need assistance implementing a solution to include these fields, we recommend reaching out to your implementation partner.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
93 | |
15 | |
9 | |
8 | |
5 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.