BRS report

Hi!
Can anybody help me out with a sample Bank Reconciliation report (BRS) ABAP code.
thankx in advance
Amit
Please do not ask the forum to do your work for you
Edited by: Rob Burbank on Feb 18, 2009 10:35 AM

Hi,
just go through this link..
[Bank Reconciliation|http://209.85.175.132/search?q=cache:tcrUKfYjsaAJ:help.sap.com/bp_bblibrary/500/Documentation/J03_BankStmt_EN_US.docexampleonBankReconciliationprogram%2B+abap&hl=en&ct=clnk&cd=5&gl=in]
Regards
Kiran

Similar Messages

  • BRS Report for un cleared items

    Hi Developers,
    I have a requirement in FI Module. I want a BRS Report. Can any one help me on that because I have no idea what a BRS Report is. Any one having sample code please post.
    Regards,
    Bibhu

    BRS - Bad Report Specification?  Seriously, go back to your FI/CO wizard and ask what he/she means by "BRS".

  • Report for Un-Reconcile items

    Hi All,
    Hope you all must be doing great,I have one problem related with FI.
    we are implementing Manual bank Reconciliation statement at our client place. I am facing a practical problem here. The problem is ;
    There are some line items those are present in Bank statement( bank charges, LC payment) but the same financial entry is not there in the SAP system(sap ledger). The user feeds all the data that is in the bank statement and run the BRS. The system is taking the matched data and for un-matched data system is throwing Errors while running the BRS . All thematched & Un matched data stored in a Table FEBEP.
    The system is not maintaining any status for those line items which are present in the bank statement but not present in the SAP 
    I have to develop a report  in co-ordination with ABAP for those line items which are present in bank statement but not present in the SAP  i.e. for Un-Reconcile items
    Kindly look into this case please let me know How this situation is to be handeled?
    If possible please let me know the Table & fields involved.
    With Regards
    Manoj Singh

    Hello,
    It all depends on how you have configured. If you want to clear the items, the system looks for the algorithm you have given. If you want to make postings then the system itself will pass the entries for the unmatched entries. (Bank Charges, LC Payments). You need not bothered about this. The system credits your main account and debits the sub account. Manually you can pass the contra entry if you do not configure for example credit bank sub account and debit bank charges account (in case if you do not configure).
    Please let me know if you need any further help.
    Regards,
    Ravi
    ==============================================================
    The following notes may useful to you. Please search some of my notes on Bank Statements in other threads.
    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

  • Un reconciled transaction report

    Hi all,
    When we run BRS report we will get reconciled transaction and Unreconciled transactions report
    Under Unreconciled transaction we will get a headings and values as follows
    Open in Book after dates       xxxxxx                                      Open in bank after date     xxxxxx
    Bank's Closing Balance             xxxxxx                       Book's Closing Balance             xxxxxx                                                                 
    Transaction in bank after date  xxxxxx                       Transaction in book after date  xxxxxx                                                             
    Total in book for checking         xxxxxx                       Total in bank for checking         xxxxxx                                                            
    If some one can explain, it will be a grate help
    SBO version 2005 B
    Kind regards
    Rashid

    Hi,
    Thanks for your reply , in the following scenario i need some clarification
    VALUE DATE : 31.03.09          
                                                                      Unreconciled Transactions                                                       
    Total credits in Books   :  Rs. 123,335.94                                    Total Debit in Bank :  Rs. 174,048.00          
    Total open in Books      :  Rs. -123,335.94                                   Total Credit in Bank:  Rs. 357,395.00                                                                               
    Total Open in Bank:   Rs. 184,347.00          
    Open in books after date :    (4,364,249.01)                                 Open in Bank After date  : 7,506,301.09          
    Bank`s closing Balance            :  5,266,069.84                  Book`s closing balance          :  (2,326,264.66)          
    Transactions in Bank after date :  2,402,915.24                  Transaction in books after date :  (2,181,982.30)          
    Total in books for checking       :  3,181,400.13                    Total in bank for checking        :   3,181,400.13          
    Balance as per Bank  :   5,266,069.84
    Balance as per SAP   :  -2,326,982.30
    Differences                    7,593,052.14
    How can i get the list of unreconciled transactions in bank book and bank ledger matching with the above difference.
    TIA
    Kind regards
    Rashid
    Edited by: Muhammed Rashid on Sep 10, 2009 10:09 AM

  • Uncleared items in BRS to be captured

    Dear All,
    As per my client requirement have developed a BRS report with separate annexure and summary report, report shows the items which are reconcilled and updated in tables as per the logic which i applied thru ABAP, now the issue is whenever bank statement does not matches with SAP data system will thrown the error as "No open items found" in SM35 & remaining matched items will be cleared.The issue is client wants to show these uncleared amounts in BRS report.Have checked in all atbles but no where found uncleared items with reference to BRS since there is no reference in system except the amount.
    Kindly let me know is there any possibility of getting this data in the report and in which table..Ur help will be greatly appreciated.
    Regards,
    Balaji.c

    Hi Balaji,
    Please refer attached documents. You can can read up pages 1-23 onwards to 1-25. This gives proceedure for Postprocessing of Bank Statements, including when you process as a batch input session.
    Link: https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/a97fa590-0201-0010-04ba-beed13d6cc7e
    Maybe this would explian why you do not see the data in the tables.
    If you want to capture the results of BRS posting in an ABAP report, maybe you should try running the Bank Reconciliation transaction in background mode and not as a batch input session.
    Hope this helps.
    Thanks and Regards,
    Uma

  • BRS Printing

    Hi guys....
    Is there any way in SAP b1 2007B to print the BRS report.
    As the  financial year ends we  have to submit the Report to our audit team and
    we are  unable to find the brs in b1.
    But They need the BRS Report..
    Pls guys its critical any body pls give me some solutiion to print Bank Reconciliation Statement inb B1.
    Thanks in Advance,,....

    Hi,
    You may check this: Re: Bank Reconciliation Reports
    Thanks,
    Gordon

  • Bank Recollection Report

    Hi Developers,
    I need a BRS  Report ( Bank Recollection Report  )  which will show un cleared items. any one having any sample report please help me.
    Regards,
    Bibhu

    Hello Emeka,
    I landed on this thread when I tried searching for a similar requirement. I'm curious to know if something came out of this discussion.
    Have you been able to pull something out of the system using any workaround, or creating a new report,...?
    Thanks,
    Mohan

  • Clearing customer open items

    Hello!
    Can anybody help to find a way how to clear customer open items when there is no reference number in use for customer. In electronic bank statemen there is only billing document number in TXT field. How to configure "Make Global Settings for Electronic Bank Statement" and "Define Search String for Electronic Bank Statement" for that purpose.
    With all the best,
    Merlin

    Hello,
    IMG => Financial Accounting => Bank Accounting => Business Transactions => Payment Transactions => Electronic Bank Statement => Make Global Settings for Electronic Bank Statement
    Give your chart of Accounts
    1. Create your account symbols
    Create freely definable account symbols. Make sure that you are able to identify them when you are configuring in future steps.
    2. Assigning Accounts to Account Symbols
    Here you need to assign the account symbols to GL Accounts or you need to use masking logic. You must have designed your accounts in such a way that the end digits will work for posting the entries to FI. Account Modifier you use as + and use your local currency, if you do not have any foreign currency postings.
    3. Create Posting Rules
    Create freely definable posting rules.
    4. Define Posting Rules (This is the most important configuration for your FI Postings / Clearings)
    a) For all the payments you need to create the entries for posting area 1
    b) For all the receipt you need to create the entries for posting area 1 and 2
    c) Use the document type DZ in case if you want to clear the items. Use Posting type 8. If the invoice number is there in the reference field of bank statement, automatically the same will be selected by the system and cleared.
    d) If you want just only entries to be posted use posting type 1.
    e) If you want to clear the check, then use the posting type 4.
    f) Configure according to the entries to be posted.
    g) If you are going for clearing something the offsetting debit / offsetting credit (as the case may be) need not be given.
    5. Create Transaction Type
    Create freely definable Transaction Type
    Select the transaction type and assign the external transactions to your posting rules.
    For outgoing check use 13 as Interpretation Algorithm and 1 as the processing type.
    Remaining all case use 1 (Standard algorithm) and 5 as the processing type.
    Please also go through the below mentioned note in case if you are required to use further available interpretation algorithms or processing types.
    6. Assign Bank Accounts to Transaction Types:
    You need enter the Bank Key / Bank Account / Transaction type here.
    You can get the the bank key and bank account details from table T012K (Go to SE16)
    Further supplementary notes may be useful to you:
    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

  • EBS statement Assign to Automatic payment programme?

    Hello,
    The requirment of customer when i run automatic payment progrmme customer want electronic bank statement. in statement detail information bank account of company. how to assign electronic bank statement to automatic payment programme.if any configuration  please give me detail .
    Regards.
    Shailesh.

    Hello,
    Both are different. Automatic Payment program is outgoing and electronic bank statement is incoming.
    There is no direct linkage. For electronic bank statement, you are not the initiator. Your bank is the initiator. Unless, you have the inputs from Bank, you cannot upload the electronic bank statement.
    Anyway, the following information may be useful for your electronic bank statement configuration.
    Hello,
    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

  • 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

  • Bank Manual Statement - FF.5

    Hi CFM experts,
    while doing FF.5, I am getting error, INR:STATEMENT 200900106 is not in the bank data storage.
    actually BDC, session is not created. Kindly provide some solution.
    Regards
    J. Stephen Thangiah

    When you upload the first statement you will get this warning message. Just ignore this.
    Hello, 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

  • Electronic bank mt940 step by step configuration document

    hi all,
    can any body send me a step by step electronic bank mt940 configuration document.
    Its little bit important we are implementing mt940 format.
    regards,
    sudhakar

    Hello, Hope the following information is helpful. 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

  • Material Movements issue in BEX report

    Hi Friends
    We have one report which shows the report on the production date, batch number, number of expired
    products and non expired products etc. recently in R/3, people have changed the production date
    for few batches and now the BW report is displaying 2 production dates for the batches whose production date changed. the report is based on 0IC_C03. I need to display the production date of a batch when they first entered into the system and any changes to the production date to any batch should be ignored and should  not be pulled into the report. Hope to get quick help on this.
    Thanks,
    Prasasd

    Hi,
    Could you please tell me how do you know which production date is entered first for batch. I think this job is difficult or even it can do this will make impact the performance because system has to check again and again when you view report . I suggest that to make sure one batch only have one production date you should put production date as the attribute of batch and use it as navigation attribute in cube.
    Hope this helps.
    BRs
    TRUC
    Edited by: Hieu Truc Nguyen on Dec 4, 2008 8:43 AM

  • How to clear Documents using XBLNR(Reference field) through Manual BRS-FF67

    I want to clear GL line items in clearing account using Manual BRS(FF67) with reference to "XBLNR" field(Reference). IS there any standard Algorithm which SAP provided for reference field or if we want to develop ne algorithm then how to create.
    Thank in advance.
    Best Regards
    Raj

    Hello Raj,
    It is not possible to clear an open item on a g/l account via the
    reference document number. The automatic clearing with interpretation
    algorithm 021/001 only takes place, if the item, which should be cleared
    is on a customer/vendor account. So it could never find open G/L items.
    The reason is that the reference number is usually not unique
    so it could lead to wrong clearings.
    A workaround therefore would be to use:
    a) another interpretation algorithm depending on the note to payee
       data are available.
    b) the user exit 1 (described in note 494777, point 1) if there are
       no other information available as the reference number.
    c) the report SAPF124/E to clear these items afterwards. Then the bank
       statement should only post FB01 without clearing. The requirements
       are criteria to assign and clear the suitable items.
    Regards,
    Renan

  • Manual bank statement -  report

    Hi SAP Gurus,
    Is there any standard report in SAP which can pull out the entries maintained through manual bank statement, the business transactions used for a year??
    Regards,
    SATVIR SINGH

    Hi:
              I guess your requirement can be met through FBL3N. As you know FF67 credits Bank Incoming clearing a/c and debit Main Bank account as BRS is posted and vice versa for Outgoing. This posting is done using document types as defined in SPRO...Financial Accounting....Banks...Business Transactions...Payment Transactions....Manual Bank Statement..Define posting key and posting rules....Define posting rules...There you will see doc type against various transaction types you use for postings BRS.
    All posting done through FF67 can be tracked by executing Main Bank Accounts GLs in FBL3N and filtering the document type.
    Hope it will help you.
    Regards

Maybe you are looking for