Request you to throw some light on my query.
Below is the file for Bank Charges, I am able to post through Fiori by using the same external transaction type(808) through Manage bank statements app( by creating statement in it direclty). But when i try to upload through Incoming bank payment file app the error is throwing is as below. Same file if i change External Transaction type to NTRF i am able to upload and post.
Please let me know if i am supposed fill any seperator between amount and external transaction type here.
Request your early revert.
From what I can see, your bank provides the bank statement as an unstructured MT940. Besides, from what I can see, this file does not meet SAP's requirements with regards to the layout of the field :61:.
First of all, I'd advise you to check out the recommendations for MT940 format as they were formulated by SAP. You can find detailed guide in OSS-note 2471036 - FF_5 : Note to payee information is not copied completely from tag 61. Below is a short excerpt. As you can see, SAP expects to find the alphanumerical transaction code which has 4 characters & starts from N, S or F. Otherwise, SAP is not able to parse the values during the upload.
Therefore, I can suggest you two things:
1) Please get in touch with your bank and clarify if they are able to fix it on they own. Banks often have the option to customize the layout of certain fields in MT940. Sometimes, you can choose between unstructured & structured MT940 etc. But if you do not ask, you'll never know.
2) If your bank will categorically deny any change requests, you can consider the enhancement spot EXIT_RFEKA400_001. This spot is triggered during the file upload. It is possible to process raw text file and do the replacement. In your case, you need to identify the lines beginning with :61: and replace " 808" by NTRF or any other code. In this case, you're free to choose. You can define your own code e.g. NFEE. But make sure that you do the appropriate mapping in OT83.
If you interested about the enhancement option, you can check out my blog post on this topic.