SAP Financials Blog.

Multicash format for Bank Statement processing

2013-04-29T14:31:00.002-05:00

Multicash is an electronic bank statement format, especially prevalen in Germany and rest of Europe. Multicash is a product of a German company Omikron. The format is widely recognized by various banking systems for communication with customers' ERP systems. SAP supports multicash format as a standard functionality. The format consists of two files in format AUSZUG.TXT and UMSATZ.TXT. AUSZUG.TXT format contains the header information for the bank account statements, while UMSATZ.TXT contains transaction level information.

Format Details

AUSZUG.TXT

Semicolon Delimited

Field#	Field type	Minimum	Maximum	optional	Description

1	Alphanumeric	0	12		bank key
2	Alphanumeric	0	24		bank account number
3	Numeric (Integer)	1	4		statement number
4	DD.MM.YYYY	8	8		statement date
5	Alphanumeric	3	3		currency key
6	Amount	1	18.2		opening balance amount
7	Amount	1	18.2		debit total
8	Amount	1	18.2		credit total
9	Amount	1	18.2		closing balance amount
10	Alphanumeric	0	35		Bank account holder
11	Alphanumeric	0	35	X	special account name
12	DD.MM.YYYY	8	8	X	life start
13	DD.MM.YYYY	8	8	X	life end
14		0	0		Not Used
15		0	0		Not Used
16		0	0		Not Used
17		0	0		Not Used
18	Numeric	1	5		number of records in statement

UMSATZ.TXT

Semicolon Delimited

Field#	Field type	Minimum	Maximum	optional	Description

1	Alphanumeric	0	12		Bank key
2	Alphanumeric	0	24		Bank account number
3	Numeric	1	4		Statement number
4	DD.MM.YYYY	8	8		Value date
5	Numeric	1	10	X	Primary note number
6	Alphanumeric	0	27	X	Note to payee 1
7	Alphanumeric	0	27	X	Bank posting text
8		0	0		Not used
9	Alphanumeric	0	4	X	Text key
10	Alphanumeric	0	16	X	Check number
11	Amount	1	18.2		Amount
12		0	0		Not used
13		0	0		Not used
14	DD.MM.YYYY	8	8		Posting Date
15		0	0		Not used
16		0	0		Not used
17	Alphanumeric	0	27	X	Note to payee 2
18	Alphanumeric	0	27	X	Note to payee 3
19	Alphanumeric	0	27	X	Note to payee 4
20	Alphanumeric	0	27	X	Note to payee 5
21	Alphanumeric	0	27	X	Note to payee 6
22	Alphanumeric	0	27	X	Note to payee 7
23	Alphanumeric	0	27	X	Note to payee 8
24	Alphanumeric	0	27	X	Note to payee 9
25	Alphanumeric	0	27	X	Note to payee 10
26	Alphanumeric	0	27	X	Note to payee 11
27	Alphanumeric	0	27	X	Note to payee 12
28	Alphanumeric	0	27	X	Note to payee 13
29	Alphanumeric	0	27	X	Note to payee 14
30	Alphanumeric	0	27	X	Business partner
31	Alphanumeric	0	27	X	Business partner
32	Alphanumeric	0	12	X	Bank key of the partner's bank
33	Alphanumeric	0	24	X	Bank account number of the partner
34	Alphanumeric	0	3	X	Business transaction code
35		0	0		Not Used

SAP Transaction for processing Multicash files:

FEBC - Convert various formats to multicash format

FF_5 - Import Bank Statement with multicash format

RFEBKATX (program) - Test Tool for to create open items and bank statement files.

Issue/Solution: Errors with IDOC message type PEXR002/REMADV

2013-04-24T13:25:00.001-05:00

Message type PEXR2002/REMADV, can used to create remittance advice for customer using EDI 820 or other common formats. The following errors are common to appear in basic type PEXR2002 and message type REMADV as the mapping of IDOC fields to customer or company code is not very intuitive.

FD 16 - Company code could not be determined for intermediate document
FD 17 - Customer/vendor could not be determined for intermediate document

To resolve the errors above, it's very important to understand how standard SAP function module to process Remittance Advice determines the relevant Customer or Company Code records.

Customer Determination
The Customer to whom remittance advice is to be posted is determined using segment with the following alternatives

1. Based on Partner Profile, as configured in WE19 if the partner is of type "KU" - customer
2. If partner type is not "KU", Segment E1EDKA1 is checked the following order of precedence where the partner function E1EDKA1-PARVW = "AG"

Based on field LIFNR (Vendor) if Partner Function (PARVW) = "AG" (Sold to Party) against KNA1-KUNNR (Customer Account Number)

Yes: Field LIFNR in the IDOC is validated against KUNNR in table KNA1

Based on Our Number at Vendor/Customer (Name1) if the Partner Function (PARVW) = "AG" (Sold to Party) againt KNBK-KOINT , where KNBK-KOINT is Customer's Bank Account Holder Name as maintained in customer master Payment Transaction tab

Company Code Determination

1. Based on configuration in OBCA

Company Code Name assigned to the partner type and partner number is checked against the fields PARTN and NAME1 in segement E1EDKA1, where Partner Function (PARVW) = "BE"

2. Based on Details of the bank account in segment E1IDB02 where Partner function(PARVW)= "BB"

Some more details may be found in SAP Note 63485
https://service.sap.com/sap/support/notes/63485

Program to execute external operating system commands on SAP

2012-10-19T17:43:00.000-05:00

SAP program RSBDCOS0 can be used to execute external operating system command, such as Unix/Linux Shell commands, from within SAP GUI.

For example, commands like change directory (cd), copy (cp), move (mv) can be executed from withing SAP GUI, to copy or move files on the SAP application server

T-codes CG3Y and CG3Z can also be used in to download files from SAP application server to desktop environment or to upload from desktop to SAP application server. However, these transactions may not work with upload of large files.

Mismatch in GL balance between FAGLB03 and FAGLL03

2012-06-12T20:57:00.000-05:00

Issue:

General Ledger account balance displayed in transaction FAGLB03, may not match with balance for the same period shown on double clicking any cell in FAGLB03. or with transaction FAGLL03.

Causes:

There could be various reasons for mismatch between FAGLB03 and FAGLL03, Below are some of the common reasons

Reason One: Transaction Figures not updated

Some documents were posted in entry view, but did not update the ledger totals

Solution:

To identify and correct such documents, follow the steps below

Execute t-code FAGLF03 ( Program: TFC_COMPARE_VZ) to compare document and transaction figures in order to identify the documents in error
If FAGLF03 identifies documents which are not posted to one or more ledgers, Execute t-code GLGCU1 (Program: RGURECGLFLEX) to update the transaction totals for the documents in error in the corresponding ledgers

Reason Two: Incorrect negative postings

Due to a program error, some debit line items may be displayed as credit line items in transaction FAGLL03 or some credit line items may be displayed as debit line items as shown in the screenshot below.This is usually for negative postings made due for reversals

Solution:
There could be various causes for this error,
Check the following SAP notes for resolution according to your system conditions

Note 1113114 - FAGLL03: Incorrect plus/minus signs for negative postings
Note 1163346 - FAGLL03: Incorrect plus/minus signs for negative postings(2)
Note 1170400 - Document splitting: Incorrect posting key in new G/L

Reason Three: Database Inconsistencies

Inconsistencies in the database at various levels may cause the transaction totals and balance to differ.

Solution:

Several reports are provided by SAP to analyze database inconsistencies for relevant tables.

Note 1155429 - Analysis:Posting keys/debit/credit indicators in FI-GL (new)

The not above provides reports to detect and analyze database inconsistencies in new GL line items.

Electronic Bank Statement Processing in SAP

2012-06-08T16:54:00.000-05:00

The following pages from SAP Help site, provide excellent details on the Electronic Bank Statement Processing methodology in SAP.It also provided detail explanation of the terms used to setup the electronic bank reconciliation process using SAP

Follow the link below for details:

SAP Help : Electronic Bank Statement Processing

Tool to compare SAP financial statement versions, Configuration and Table

2012-06-06T16:47:00.000-05:00

Recently I needed to compare Financial Statement Versions, Configurations and Table data between two SAP systems or clients in order to ensure synchronization across multiple landscape

While SAP offers great tools to compare ABAP programs and many configurations within the system and across multiple systems, comparing financial statement versions, table data could be tricky. Comparison in Excel may work well for comparing table data, but it becomes a time consuming activity if you need to compare each and every cell

I stumbled upon a beautiful tool to compare two text files. SAP allows any Financial Statement Version (FSV), Configuration or Table to be downloaded to a ASCII text (.txt) file using menu option System > List > Save > Local File > Unconverted in case of FSVs or Configuration screens

On screens where the Save Local option is not available a Print option may also be used to download data to an unconverted .txt file. Only precaution required is, files from both the SAP systems or clients you need to compare should be downloaded with exact same procedure.

After downloading the data into two files to be compared, just enter the location of the two data files in the Exam Diff tool and it would provide you with usual analysis of entries which are common in both the files, records which exist in one file but do not exist in other file or records which exist in both the files but are different in some way

ExamDiff is a freeware visual file comparison tool which can be downloaded from PrestoSoft's website at the following location: ExamDiff Download Page It's also available for download on CNET.

Conditions Copied from Last Purchase Order

2012-05-07T19:52:00.000-05:00

While creating a Purchase Order, If Net Price of the order is found to be zero with the calculation schema, System checks data in the last purchase orders and copies values from the last PO.

The following conditions must be met before system copies price from the previous purchase order

An Info record exists for the Vendor, Material Combination at the purchase org/ plant.
The last document is not a request for quotation.
The calculation schema of the last document is the same as the schema for the Purchase Order being created
Net Price of the purchase order is zero based on the calculation schema

A copy function is executed to copy values from the last document. No checks are made for requirements for the calculation schema.

As a exception to the above, system does not copy the condition records of the subsequent settlement (condition class "C"); instead, they are always determined again to ensure that the condition records are consistent with the field contents

The copy control can be disabled at user level by maintained EVO parameter as described in SAP Note# 675523

Exchange Rate Based On Document Date for LIV Invoices

2011-07-29T22:22:00.004-05:00

For LIV Invoices posted using MIRO transaction the exchange rate defaults based on the posting date, As there is no provision to change the translation date on the MIRO screen, it cannot be substituted with document date.

In order to post all invoices based on exchange rate at the document date instead of the exchange rate at the invoice date, the BADI FI_TRANS_DATE_DERIVE needs to be implemented according to the SAP Note #574583

Detailed steps to implement this BADI are :

Go to transaction SE18, enter implementation name as "FI_TRANS_DATE_DERIVE" and click "Display"
Click Menu option, "Implementation" > "Create"
Enter an implementation name, for example "Z_BADI_FI_TRANS_DATE_DERIVE"
Add country codes where document date is required as translation date in "Attributes" tab
Go to "Interface" tab
Double click on "DERIVE_WWERT"
Activate the code
Go back to the previous screen and activate the implementation

The SAP note#574583 shows relevance only upto ECC 6.0, but it can be implemented with ECC 6.04 also.

Grouping of Payment Items in Automatic Payment Program (F110)

2010-03-26T14:44:00.000-05:00

When executing an Automatic Payment program (F110), Various open items can be grouped together to be paid with a single payment document.
The grouping of open items for payment is carried out based on the fields in structure ZHLG1. Items are grouped only if all the fields in this structure are identical

for more details on open item grouping, refer to the following SAP Note
Note 164835 - F110: Clearing credit memos and invoices

RFTBFF00: Import Market Data

2010-03-26T14:25:00.001-05:00

RFTBFF00 allows to transfer external market data into the SAP system in file form

It can be used to import the following

Category 01: Exchange rates

Category 02: Security price information (stocks quotes, bonds)

Category 03: Reference interest rates (e.g. LIBOR, FIBOR)

Category 04: Indexes

More information on how to use this program and transfer structures is available at the following SAP help link:
http://help.sap.com/saphelp_45b/helpdata/en/35/a7b5629af50d14e10000009b38f9b9/content.htm

With program RFIMPNBS it is possible to automatically import new exchange rates from European Central Bank into the system using an XML file. The following configurations need to be completed before RFIMPNBS can be use:
Standard quotation for exchange rates,
Exchange rate type,
Translation ratios for currency translation

More details for using this program are available in SAP Note:
Note 1286897 - Import of Exchange Rates from ECB

Issue/Solution: Offsetting Account in FBL3N/FAGLL03

2010-03-23T16:07:00.004-05:00

Issue:
You need Customer / Vendor Number (KUNNR/LIFNR) to be displayed for the offsetting GL accounts in the GL account line item reports FBL3N or FAGLL03

Soultion
There is no standard configuration to achieve this.
Using Sort key in the GL account will not populate data from the offsetting account
This can be achieved by using a BTE or BADI as described in the following SAP Notes
Note 112312 - Line item: Display of offsetting a/c information
Note 1034354 - FAGLL03: Display of offsetting account information

Further, if Vendor Name or Customer Name are also needed
Refer to the BTE solution provided by Burak in the following SDN thread..
http://forums.sdn.sap.com/thread.jspa?messageID=7848056&tstart=0#7848056

Information: RFBIBL00 - Batch document processing program

2010-03-17T15:44:00.001-05:00

RFBIBL00 is a program which can be used to post documents or clear open items based on an input UNIX file. The programs supports the following transactions

FB01 Post document

FBB1 Foreign currency valuation

FBS1 Enter accrual/deferral document

FBV1 Park document

FB05 Posting with clearing

One of the basic advantages of using this program over a posting with BAPI is that it can also process profitability segment characteristic selection, which is not supported with BAPI for document posting.It also supports fields for one-time data and the data for the coding block fields.

The Unix file structure details and more information required to implement this program can be found at the following link from SAP help portal:
http://help.sap.com/saphelp_45b/helpdata/en/35/a47e63763e0392e10000009b38f9b7/content.htm

Information: Difference between Business Area and Profit Centers

2010-03-03T09:51:00.000-06:00

With the onset of New General Ledger, which provides seamless integration between general ledger and profit center accounting, Business Area seems to have lost the importance it enjoyed with the classical general ledger.

Often we encounter a dilemma on whether to use a Business Area or Profit Center (or Segment) to obtain financial information on an important logical business division or geographical business location.

The following note from SAP clearly classifies the distinction between the functionality available with Business Area and Profit Center to help make the appropriate choice.

Note 321190 - Difference between business area and profit center

Information:Tables for CO-PA Transaction Data

2010-02-25T16:21:00.001-06:00

The following link explains the concept of CO-PA data tables, which the system creates when an Operating Concern is generated.

Database Tables for CO-PA Transaction Data (SAP Library - Profitability Analysis (COPA))

Costing Based COPA

CE4XXXX - Profiability Segment Definition Table
(Assigns segment number to each characteristic combination)
CE3XXXX - Segment Level Totals table
(Provides Period Based Segment level Totals)
CE2XXXX - Plan Line Items
CE1XXXX - Actual Line Items

Account Based COPA

CE4XXXX - Profiability Segment Definition Table
(Assigns segment number to each characteristic combination)
COSS/COSP - Segment level Totals
COEP - Plan Line Items
COEJ - Actual Line Items

Information: Report to compare GL transactions and totals

2010-02-19T11:08:00.000-06:00

The report program transaction FAGLF03 (Program:TFC_COMPARE_VZ) can be used to compare and reconcile the transaction amounts in documents to the GL totals.

When New General Ledger is not activated, the report compares data in table BSEG with totals in table GLT0
While, when New GL is activated, the report compares data between New GL Totals table FAGLFLEXT with transactions table FAGLFLEXA

Program: TFC_ADJUST_VZ can be used to rectify some of the error identified with the above report.

Information: Workflow settings to release Parked documents

2010-02-03T14:53:00.003-06:00

The following document provides details on various standard workflows which can be used for release of Parked documents.

The document also provides details on standard sub-workflow models which can be used for amount based release or account assignment based approval and release process

http://help.sap.com/printdocu/core/print46b/en/data/en/pdf/FIBP/FI-AP-AP-PRK.pdf

Here are some key excerpts from the document...

Workflow Model for Completing Documents

"There is a workflow model in the system (WS00400004) for completing parked documents. In
order to use this in your active clients, you must copy it there using the tools in the workflow
workbench."

Standard Task for Completing a Document

"Users who want to complete parked documents must be allocated the task “Complete parked
document” (TS00407848). To do this, create the organizational object in Personnel Planning and
Development using the workflow workbench. You then allocate the relevant users and the abovementioned standard task to this object."

Workflow Models for Document Parking and Release

"Several Workflow models are provided in the system for document parking; a Workflow
framework (WS10000051) and five sub-workflows. In the Financial Accounting Configuration
menu, you can set which sub-workflow model should be used by the workflow framework at the
time of the program run. You can also define your own sub-workflows while in this menu,
providing that they send and receive the same data from the workflow framework as the subworkflow
models do.
If you want to use the standard sub-workflow models for multi-level amount release
(WS10000052, WS10000053, WS10000054), you can define between one and three levels for
amount release in your system. Should you want more than three release levels, copy the
workflow models for amount release and then expand them. If are not working with amount
release, you can use a dummy sub-workflow model (WS20000006). The fourth standard subworkflow (WS10000055) can be used for account assignment approval."

(c) SAP AG

Issue/Solution: Asset XXXXXXXXX-0000 in CoCd XX00: Error in fiscal year change

2010-01-07T15:32:00.004-06:00

Issue:
When the user try to execute Asset Fiscal Year Change transaction AJRW, they get the following error

Message No.: AA707

Short Text
Asset &-& in CoCd &: Error in fiscal year change

Diagnosis
The fiscal year change in one asset has produced an error.

System Response
No fiscal year change will be performed for this asset, processing will be continued with the following asset.

Procedure
Determine the error message using the function 'fiscal year change' when displaying the asset values.

Also When they open Asset Explorer for the asset in error using transaction AW01N, they get the following error message

Message No.: AA634

Short Text
Correction to ordinary dep. greater than acc. dep. in area &

Asset affected:
Diagnosis
The line item cannot be posted, since the correction to ordinary depreciation in area exceeds the cumulative ordinary depreciation.

The error can occur during a transfer, a write-up, or post-capitalization.

Procedure
Correct your entry.

Solution:
1. Check all the planned deprication runs are posted in the fiscal year to be closed.
2. Check for incomplete asset master data with transaction code AVUA and correct any master data problems
3. Execute transaction ASKB - Periodic Asset postings, even if you do not have any depreciation areas which post periodically.

Database Tables for CO-PA Transaction Data (SAP Library - Profitability Analysis (COPA))

2010-01-04T15:34:00.001-06:00

The following link provides a detailed relationship between COPA tables created for each operating concern.

Database Tables for CO-PA Transaction Data (SAP Library - Profitability Analysis (COPA))

ASAP Methodology

2009-12-21T16:08:00.001-06:00

A small and precise presentation on ASAP Methodology.

ASAP Methodology

View more presentations from arun_bala1.

Information: How to implement a BTE (Business Transaction Event) ?

2009-11-11T15:27:00.003-06:00

Here's a quick guide on how to implement a Business Transaction Event (BTE)

http://sapient.wordpress.com/2007/12/09/business-transaction-events-bte/

And here is another step by step guide to implement a BTE

Click Here for the SDN link.

Information: Document Splitting in Expert Mode

2009-11-11T13:25:00.003-06:00

During FI document posting in any transaction the menu option "simulate general ledger" allows user to view the document splitting line item in details using the expert mode. where the business transaction,transaction variant and splitting method are displayed along with splitting details of each item

T Code: FAGL_MIG_SIM_SPL (Program: FAGL_SHOW_SPLIT) can be used to display document spltting details of document which have already been posted.
However, the transaction shows splitting details with regards to the existing customization for document splitting,
Hence if the document splitting configuration has been changes after the document was posted, some inconsistencies may be observed.

Thanks to Bernard for this information.

Information: How to find tables for a customizing object?

2009-09-20T15:34:00.002-05:00

Information: How to find tables for a Customizing object/Configuration Node

1. Select the configuration node in SPRO
2. Go to menu option edit >display IMG activity
3. Select tab Maint. Object
4. In the assigned objects table you would find a view or cluster name
5. If it's a view (type V)
- Use SE11 to open the view and check the "table/join conditions" tab
to find the tables
7. If it's a cluster (type C)
8. Go to se54 - click "Edit Cluster", Enter the cluster name and display
9. Go to "object structure" node to find the related views
10. Open the views in SE11 to find the tables.

Information:Foreign Currency Valuation with Multiple Ledgers

2009-09-17T14:52:00.005-05:00

Information: Foreign Currency Valuation with Multiple Ledger

The new Foreign currency valuation program. FAGL_FC_VALUATION uses the ledger group assigned to the valuation area to determine the ledger(s) from which balance is to be read for valuation. If the ledger group assigned to the valuation area contains only a single ledger, this ledger is used for the selection of the balances. If more than one ledger is contained in the ledger group assigned to the valuation area, each ledger is valuated individually

However, The postings for the valuation of balances are made using the ledger group that has the same name as the ledger being valuated. For example, if ledger group Z1 is assigned to the valuation area, which contains ledgers 0L and ledger L1, the balances of ledger 0L are valuated and the valuation program makes the postings using ledger group 0L and balances of ledger L1 are also valuated and the program makes postings with ledger group L1

In the above scenario, if ledger group L1 contain ledgers L1 and Z1, foreign currency valuation postings would be made to both the ledgers L1 and Z1 based on the balances in ledger L1

More details availble in the following SAP Note
983847 - Foreign Currency Valuation: Balances in NEW G/L

Information: Convert tcode FSE2 (Financial Statement Maintenance) to Current Settings

2009-08-14T11:25:00.004-05:00

Requirement: Transaction Code FSE2- Maintain Financial Statements Versions is a configuration item by default and you need to convert it to current settings or a user transaction.

Solution:
The procedure to convert FSE2 from an IMG activity to a user transaction/current setting is outlined in SAP Note#200674- Fin.Statement Vrsn: Maintenance in production clients. This note cannot be applied using transaction SNOTE and the following manual activities need to be performed.

1. Change the SPRO settings for view V_T011 using SOBJ as outlined in SAP Note#135028 - Transfer IMG activity to Current Settings.
2. Further, Message FE-146, also needs to converted to an Information or Warning message, using OBA5 as outlined in SAP Note#109577 - Changing FS version although client not changeable.
The above activities may differ depending upon the SAP release.

Issue/Solution: Issuer details for paying company code XX01 are missing

2009-07-09T13:54:00.003-05:00

Issue:
While generating a payment medium using the payment medium workbench (with t-code F110 or FBPM) the user get the following error message: "Issuer details for paying company code XX01 are missing"

Solution:
The issuer details need to be maintained through transaction FBZP in the node "Payment Method in Company Code".
Select the relevant company code and payment method combination and add text to the tab "Drawer on the form" in the Form Data.
The details to be filled varies depending upon the payment medium format in use
for example : White using MT103 SWIFT format the following details would be required
Field 1 - Name 1
Field 2 - Name 2
Field 3 - Address 1
Field 4 - Address 2