MT940 to FINSTA01 mapping

Dear all,
We want to map standard MT940 file format to FINSTA01 Idoc to post Electronic Bank statement in to Sap.
Does any one know how to map MT940 format to FINSTA01 Idoc ( to which segements and fields of the IDoc ).
If any of you have information regarding this please do share the information.
Thanks & Regards,
Sravan

That's possibly the best answer
Just to add, if you have the Idoc already imported into IR, then create a new message mapping object, then import the Idoc message structure as the target message in the mapping. There you should see a few fields marked in "RED" color. Those are fields you must map as they are mandatory fields (occurance 1:1) and without mapping those target fields, you cannot even activate the message mapping object.
So that way you know which fields you must map on the IDoc side..............for the rest of the fields.....I think Jakub has given you the best suggestion
Regards,
Suddha

Similar Messages

Mapping to FINSTA01

I am new to IDoc and I am trying to map EDI823 data to FINSTA01.
Can someone give/show me mapping for FINST01?
I need to know what fields need to populated with which data.
Thanks for any help you can give.
John

That's possibly the best answer
Just to add, if you have the Idoc already imported into IR, then create a new message mapping object, then import the Idoc message structure as the target message in the mapping. There you should see a few fields marked in "RED" color. Those are fields you must map as they are mandatory fields (occurance 1:1) and without mapping those target fields, you cannot even activate the message mapping object.
So that way you know which fields you must map on the IDoc side..............for the rest of the fields.....I think Jakub has given you the best suggestion
Regards,
Suddha

FINSTA01 IDOC mapping

Hi ,
Are there any standard mappings available for FINSTA file format to FINSTA01 IDOC ?
Regards
Saravana

Hi SaravanaKumar
My Name is Ashokkumar
Currently in Denmark. I am in very urgent need of the mapping for EDIFACT FINSTA to SAP R/3 FINSTA01.
I hope you would have somehow managed to get the mapping file. Shall I request you to send me the mapping file I need it very badly now.
Thanks in Advance
Ashok ([email protected])
+0045 23212447 (mobile)

TR-EBS SwiftMT940 mapping to an IDOC message FINSTA01 - Bank Statements

For Treasury, we are going to move to the PI platform. We are currently using EDI.
We start the process by requesting Citibank(GXS operations team) to put a sample file into the outbound mailbox to let our company pick up. The output of the file will be XML.
We will them map and create an IDOC with the FINSTA message.
However, we are only beginning the IDOC mapping process.
Does anyone have a sample crosswalk which will allow us to see how the SwiftMT940 from Citibank can be mapped to an SAP Idoc?
If so, may we see how you mapped the segments?
Also, how do you test the loading of the IDOC created? with the RFEBKA00 program?
Please advise.

Hello,
I am really not sure how you map to IDOC.
But, the following information may be useful to you.
Hello, You can configure the electronic bank statement at the following path: IMG => Financial Accounting => Bank Accounting => Business Transactions => Payment Transactions => Electronic Bank Statement => Make Global Settings for Electronic Bank Statement. All the settings will be done at this path only. 1. Create Account Symbols 2. Assign Accounts to Account Symbols 3. Create keys for posting rules 4. Define posting rules 5. Create transaction type Assign external transaction types to posting rules 6. Assign bank accounts to transaction types. There are different programs to upload electronic bank statement. FF.5 or FF_5. I think your case Multicash format you are using. You need have three files in FF.5 and two files in FF_5 You can prepare a Z program in order to truncate the electronic bank statement into two or three part files and save them on the application server. 1. Take all the external codes list from bank. 2. Take any available documentation from the Bank describing the relevance of the external codes. 3. Make sure that your Chart of Accounts (Bank Accounts) last digits logic is appropriate to meet the requirements. 4. Based on this decide the Account Symbols that are required to be created. 5. Make sure that the masking rules are configured properly. 6. Decide the posting rules that needs to be created. 7. Link up your external symbols provided by the bank with Posting rules and give proper algorithms for posting and clearing logic. 6. Concentrate on the posting areas to be posted while uploading the bank statement. Further explanation would help you to understand the functionality when uploaded the electronic bank statement. Main purpose of uploading the bank statement into SAP is to make your Bank Main Account and physical bank statement balance in sync. You do not have any traditional Bank Reconciliation Statement (BRS) report in SAP. SAP is normally you maintain bank main account and bank sub account. Whenever you make a payment through F-53 or F-58 or F110, the entry would be: Vendor Account Dr To Bank Sub Account The ending digits of the sub-account would be important in configuring the masking rule. Based on this masking rule when you upload the bank statement the entry the system would pass is: Bank Sub Account Dr To Bank Main Account It depends on the configuration, either the sub account will be cleared by the system automatically or you need to run F.13 to clear the sub accounts. At the time of receipts, you have different accounting entries unlike payments. It needs to post to two posting areas. 1. GL Accounting 2. Sub-Ledger Accounting The entries would system itself pass is: Bank Main Account Dr To Bank Sub Account Bank Sub Account Dr To Cutomer account. Clearing logic mentioned for your posting rules and the alogrithm used for your external bank symbols will also play pivotal role in clearing the accounts. Ideally you will use FF67 / FF.5 / FF_5 for uploading manual or electronic bank statement FEBA / FEBA_BANK_STATEMENT is used for furthe rprocessing. GO THROUGH SAP NOTE 48854 Please go through SAP Note. 48854. You will get an idea regarding the functionality of the algorithms. Though this note is in relevant to GB specific, you will find this very useful. description follows below regarding the normal procedure for maintaining table T028G. Due to the different bank codes and posting rules, pre-Customizing is not possible at this point. The following processing types are available - unless stated otherwise, you should use the interpretation algorithm: '000 - No interpretation' in each case. 1. '00': There is no processing. The entry line is ignored. 2. '01': A validation is made whether an entry exists for the transferred check number in the check table (PAYR). The check number and payment document number are transferred for further processing. Interpretation algorithm: outgoing check processing '011'-'013'; the update in the check file is via the interpretation algorithm. 3. '02': Transfer of the ending balance to the electronic bank statement 4. '03': Transfer of the opening balance to the electronic bank statement 5. '04': Clearing via the allocation number which is delivered with the bank statement. No interpretation algorithm. 6. '05': Clearing of BACS payments or BACS bank collection. The reference text field is first read to ascertain whether it involves payments initiated by users or bank collection via BACS. Providing it does involve a cash transaction initiated by the user, the payment document numbers concerned are determined via the reference number and transferred as a reference to further processing. Interpretation algorithm: '000 - No interpretation' or '019 - Reference number DME'. Note To differentiate between the two procedures in table T028G, you have to maintain two separate entries. Example: the bank uses bank code '62' for cash receipts and for BACS bank collection. Ext. Transaction +/- sign Posting rule Int. Algorithm Processing type 62 + GB62 001 5 62 SAPBACS + GB63 000 5 7. '06': Bank costs or interest revenues Recommended interpretation algorithm: '000 - No interpretation' 8. '07': Total amount of cash disbursements 9. '08': Total amount of cash receipts 10. '09': Items not paid Recommended interpretation algorithm: '000 - No interpretation' Regards, Ravi

MT940 statement BACS DME auto clearing

Hi Friends,
Needed some help on automatic clearing of bank open items when processing electronic bank statement (MT940 format). When automatic payment is done through F110 , a DME file is created. In the bank statement config , the external transaction (NDDT) of HSBC bank is mapped to internal posting rule with clearing algorithm 019 - DME refrence number.
Bank in the MT940 statement must have BACS reference number.Usaually a 10 digit number if we use SAP delivered DME for BACS (GB_BACS). But this number does not appear in the file created. This can be seen in the details tab of the file. In the file created , there is another refrence which starts with SAPBACS00000xxxxx.(Note: a search string has been defined to pull the 10 digit numeric from this string). Earlier when i used to put this reference ..SAPBACS.... or the 10 digit number , open items used to be automatically cleared. Now it is not happening.
Does anyone have some more input on BACS items auto clearing during Electr Bank rec.
Regards
Ajit

Hi Ajit... I am also facing the same issue. Has your problem solved..
It would be of great help if u can give me u=your valuable inputs
cheers
sanjeev

Issue with MT940 ACK/NACK FILE

Hi Guys,
BANK->SWIFTNETGATEWAY(ACK/NACK Files)->SAP PI---->SAP ECC
The issue is regarding the ACKNOWLEDGEMENT/NACK files sent from back with respect to MT 101 files.
I am using FILE-PROXY scenario for this ( FILE SENDER ADAPTER---RECEIVER XI ADAPTER)
To read the sample ACK file i have used the module localejbs/swift/FINConversionFromSWIFTModule in sender file adapter. The sample file has multiple fields structure which is similar to SWIFT_FIN structure. But if you read the file using this module it will populate the data only for the 6 fields based on datatype SwiftMessage whose structure is different from SWIFT_FIN .Due to this data will not be populated in the mapping, so blank data is going to SAP ECC and its throwing error.
I have tried out all possible ways to use the modules provided in the configuration file but the file is read only with SwiftMessage structure and the standard mapping for ACK/NACK is provided with SWIFT_FIN structure as source and collectivePaymentOrderNotification as receiver structure.
I have explored and tried all the possible ways and got struck at this point of picking the file based on SWIFT_FIN structure, I request to let me know if there is any additional module available in the SWIFT integration package which will read the file based on SWIFT_FIN structure. Kindly suggest me with the valuable inputs.
Thanks,
Vishnu

Hi All,
Pls find Overview of SWIFT message structure.
The high-level structure of a SWIFT message is as follows:
Sample MT940 text File structure will be
I want to read this data and convert into XML file via SAP PI
Give me possible ways, how we need to convert the text file into xml file..
Regards,
Vishnu

EDI 823 to iDoc FINSTA01

I am trying to map EDI 823 file to iDoc FINSTA01.
I mapped as much as I know, but I am getting following errors when I test it:
- External transaction is missing for determining the posting rule
- Bank statement date is incorrect: 00000000
Anyone seem these errors?
Anyone know what I need to fix to get rid of these errors?
Any help can be really appreciated.
Thank you,
John

Hi,
Can you give the procedure to configure EDI 823 and the bare minimim segments with fields that are required to be filled if you have solved the issue you got earlier.
Thanks & regards,
raj

SAP Lockbox Processing (EDI 823) via FINSTA01 IDoc

I am trying to implement lockbox processing in SAP using the FINSTA01 IDoc. I have not found any documentation regarding the data mapping. Does anybody have experience with this? If so, I could really use a sample data mapping document.
Any help would be appreciated.

Hi,
Sorry,
Three times the same URL has copied,
Click to the URL and check :
http://help.sap.com/saphelp_erp2005/helpdata/en/57/f1fc3768b56d00e10000009b38f842/frameset.htm
1) Importing Lockbox Data
2) Postprocess Lockbox Data
This might help you,
http://ifr.sap.com/catalog/query.asp?namespace=urn:sap-com:ifr:FI:470&type=idoc&name=FINSTA01
Regards
Agasthuri Doss

EBS MT940 Ext Transaction Problem

Dear Gurus,
I have completed all config for MT940 upload and small sample statement worked fine but today testing with real EBS from bank found a typical issue.
For the EBS SAP is reading Ext transaction from the :86: line.
For Example:
:20:20081110
:25:126367007
:28:89
:60F:C081008THB137,14
:61:0810141014CB10,NCMZNONREF//0000300382
:86:/PT/DE/EI//BRC/0140014
:62F:C081008THB147,14
:86: item SAP gives msg as /PT ext transaction not defined in table.................
Ext tran are taken from :61:line why its taking from 86 I am confused::
But surprising is that in case of small test statement with little line items it was not happening.Is there anything to do do with the file (notepad)properties ?Please suugest.
Regards
Raju

Hi,
:61: contains only the transaction details and not the external transaction. The external transaction also called the Business Code is always taken from the first three characters of the :86: line. The :61: only contains the following:
mandatory:
<CR><LF>:61:                      Transaction line
Value-date                             exactly 6 characters numeric in the format YYMMDD
optional:
Booking date                         exactly 4 characters numeric
mandatory:
Debit/credit mark                  1 to 2 characters
                                            C         =   Credit
                                            RC      =   Reversal credit
                                            D         =   Debit
                                            RD      =   Reversal debit
optional:
Currency type                        1 Characters alphanumeric
mandatory:
Amount                                 1 to 15 characters numeric
                                               amount with , (comma) as decimal point
Booking code .                      exactly 4 characters alphanumeric
                                            codes according to Swift, 1. character always N
Reference                              1 to 16 Characters alphanum.
Customer reference; if not present, replaced by NONREF
//                                              Delimiter; only if field "Bank reference" present
Cont. :61:
You need to map the external transaction in the node Make Global Settings for Electronic Bank Statement in the Bank Accounting IMG.
In there, you have an option to assign external transaction types to your posting rules. This decides how an external transaction, identified by this mapping, is to be posted, whether to the bank account or subledger account etc etc. So you need to assign /PT here to a posting rule.
Cheers.

EDI 823 (Inbound) - Field Mapping

Hello,
I need to configure Incoming IDOC EDI 823 for Lockbox.
Basic type: FINSTA01
Message Type: FINSTA
Processing code: FINS
Function Module: IDOC_INPUT_FINSTA
By giving the Basic type u2013 FINSTA01 and executed in the test tool, I am getting the list of all the segments related to this Idoc type.
I request please let me know how I can map the field segments by taking minimum segments and what qualifiers should I input to process the idoc.
Thanks for your co-operation.

No Response.

Mapping for FINSTA

Hi All,
We are trying to upload bank statements through FINSTA01 IDOC types, If anyone has implemented the same message type earlier, could you please forward me the mapping.
Thanks a lot in advance.
Prashanth

What kind of structure your bank messages does have? TXT or XLS...?
If it is an TXT file, you can use the value conversion in File Adapter.
cheers,
André

EDI 821 and EDI 823 field mapping file and basic IDOC type and message type

Hi All,
We are facing some issues regarding EDI 821 and EDI 823 file mappings.
We are mapping EDI 821 and EDI 823 transactions into SAP using IDOCs. Currently we are using the below entries
EDI 823 - Lock Box
Basic IDOC type - FINSTA01
Message type - FINSTA
Process Code - FINS
The problem is we are able to get the IDOC into SAP with status red and the various errors were due to not able to create the lockbox entry in SAP and once we got yellow status also but the lock box entry was not created and the errors are like No Conversions,no header etc.
EDI 821 -
Basic IDOC type - PEXR2002
Message type - PAYEXT OR REMADV
Process Code - PEXC OR REMA
We are facing the same problem here also and the internal payment order is not creating in SAP and IDOC was generated with yellow status and red status.
We are trying different combinations but nothing is working so far.
I need the following things to proceed furthur.
1)Are the IDOC , Message and process codes are correct that I am using now for both EDI 821 and EDI 823
2)If those are not correct, can you please let me know the correct entries
3) Please provide me the field mapping if any one of you have worked earlier for both the above IDOC and message type or new ones and we have one field mapping now but if you can send it to me then I can re check it.
4) Do we have to create any configuraion or customizing in SAP to create the IDOC in green status and if so please let me know the customizing steps and procedures for both EDI 821 and EDI 823.
thanks in advance for all your help.
Please let me know if my question is not clear.
Thanks,
Ramesh.

Hi Ramesh,
I believe you are using those interfaces with the business partner type as Bank, Whatever idoc type, message type and process code you have used are perfectly correct.
First of all did you enable your bank for EDI, the house bank has to be EDI enabled first then only your idoc's can be processed, talk to your fi functional consultant and he might help you.
Are you can give me the exact error and i can help you as well.
Thanks,
Mahesh.

IDOC FINSTA01 information

HI All,
Could anybody provide some information on the mapping of data from BAI2 format to idoc FINSTA01. I checked the program FF_5 which accepts a text file (comma separated) as input to update data in SAP (direct insert into FEBKO), but we need to map this data to idoc FINSTA01's segements. I checked the documentation in WE60 but was not much of help.
Thanks and Regards,
Sachin

Hi,
Check this link
[IDOC Statistics|http://www.sapmaterial.com/IDOC_statistics_we07.html]
[Handle Acknowledgement of IDOC|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f6d2d790-0201-0010-9382-b50b499b3fbe]
Name of the table is EDIDC ---> Control record.
Regards
Narin Nandivada

FINSTA01 idoc in EDI

Hi All,
Presently im working on edi, Are there any mappings available for <b>EDI 823 file</b> format to <b>FINSTA01 IDOC ?</b> in EDI
I hope you would have somehow managed to get the mapping file. if u have any related stuff ie: edi823 file to incoming edi ( finsta01 idoc in SAP ). Please send me to
Email [email protected]
Thanks in Advance,
Nirupama reddy

Nirupama,
Are you able to get the mappings for X12 to FINSTA01. If u did, can you help me with that. my email: [email protected]
Manohar,
The link you gave does not work.
Thanks,
Gopi

Remote System and Remote Key Mapping at a glance

Hi,
I want to discuss the concept of Remote System and Remote Key Mapping.
Remote System is a logical system which is defined in MDM Console for a MDM Repository.
We can define key mapping enabled at each table level.
The key mapping is used to distinguish records at Data Manager after running the Data Import.
Now 1 record can have 1 remote system with two different keys but two different records cannot have same remote system with same remote key. So, Remote key is an unique identifier for record for any remote system for each individual records.
Now whenever we import data from a Remote System, the remote system and remote key are mapped for each individual records. Usually all records have different remote keys.
Now, when syndicating back the record with default remote key is updated in the remote system that is sent by xml file format.
If same record is updated two times from a same remote system, the remote key will be different and the record which is latest contains highest remote key.
Now, I have to look at Data Syndication and Remote key.
I have not done Data Syndication but my concept tell if there is duplicate record with same remote system but different remote keys both will be syndicated back. But if same record have two remote keys for same remote system then only the default remote key is syndicated back.
Regards
Kaushik Banerjee

You are right Kaushik,
I have not done Data Syndication but my concept tell if there is duplicate record with same remote system but different remote keys both will be syndicated back.
Yes, but if they are duplicate, they needs to be merged.
But if same record have two remote keys for same remote system then only the default remote key is syndicated back.
This is after merging. So whichever remote key has tick mark in key mapping option(default) , it will be syndicated back.
Pls refer to these links for better understanding.
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/80eb6ea5-2a2f-2b10-f68e-bf735a45705f
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/7051c376-f939-2b10-7da1-c4f8f9eecc8c%0c
Hope this helps,
+ An

MT940 to FINSTA01 mapping

Similar Messages

Maybe you are looking for