Grouping of Payment Items in Automatic Payment Program (F110)

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

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

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

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

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

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

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

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

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))

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))