Integration of FI-CA with

New General Ledger

Accounting in mySAP ERP
2005

SAP AG

08/09/2005

©SAP AG 2005

© SAP AG 1
 Enhancements in FI–CA for New GL Accounting

„ Reporting by segments
If a balance per segment is required, this takes place in the accounting interface using
document splitting.
„ Extensibility of New General Ledger Accounting
The same restrictions and requirements apply as for the Special Purpose Ledger.
„ General Ledger Transfer: Enhancement of Document Types
The document type for the general ledger transfer can now be specified individually for
each document in Contract Accounts Receivable and Payable. You do this via a module
that you define for event 0061. A segment must also be defined here for the carryforward
account.
IMG: Integration -> General Ledger Accounting -> Define Posting Specifications for
General Ledger Transfer

Not supported:
„ Portrayal of different accounting principles in parallel ledgers
-> Value adjustment (OI)
-> Foreign currency valuation
These functions are still performed in the account approach in FI. However, an enhancement is
planned for the next release.
„ Balanced ledgers in all dimensions:
By segment, but not by profit center because this relates exclusively to CO account assignments
(only revenue items and no business partner items)
„ No migration for introduction in productive operations:
No migration scenario exists. Documents already located in the system are not supplemented
with account assignments. In this way, follow-on documents also cannot be supplement with
account assignments. For this reason, you should expect a transition period of approximately
one year.

© SAP AG 2005

© SAP AG 2
 Account Assignment and Derivation of the Segment

1. Derivation from Object (Contract or Contract Type) Used as Characteristic

Account assignment in business partner item inherited by revenue item.
2. Derivation from Profit Center
Provided the first strategy was not found. The system derives the segment from the revenue items and inherits
it to the business partner items. In this case, the derivation is performed using the profit center. You must
therefore assign a profit center in the revenue item and assign a segment to this profit center in the master
record.
3. Account Determination and Default Values for New Posting Area 0301
Provided neither of the above derivation strategies are applied, the system can derive the segment from other
details for the business partner item. For this, posting area 0301 was created. The system derives the
segment from the following details of the business partner item(s):
‹ Company code, business area, division, receivables account, account determination ID, main
transaction, subtransaction
The segment determined is then inherited to the offsetting items (revenue items).
4. Account Determination and Default Values for New Posting Area 0300
Derivation via Customizing without a profit center is only possible if the segment can be determined from the
combination company code/general ledger account (new posting area 0300 with key CoCode, General Ledger
Account)
5. Installation-specific value using a new event (0081)
Here, individual logic can be used to determine a segment for every item for which the person creating the
document has not assigned a segment. However, segments are ignored in bank items and tax items and are
subsequently replaced by the valued define in Customizing.

Note:
Certain statistical items, such as statistical charges receivables, down payment receivables, and budget billing receivables also require the
specification of a segment. This segment is inherited to the non-statistical follow-on postings on later payment. If for statistical postings the
segment is not directly specified externally on creation of the item, it is also derived from the Customizing for the business partner item.

© SAP AG 2005

For documents that are not a follow-on posting to previous documents (typical example: New receivable), the
account assignment Segment can be specified on manual entry and for transfer using one of the available
interfaces. This specification has priority over the derivation options described below.
Case 1:
Note that the segment is usually determined from the leading characteristic (such as contract), depending on the
corresponding industry. The derivations described below are only applied if no segment can be determined.
Otherwise, the account assignment is inherited from the business partner item to the revenue item. If no
segment is assigned, one is derived as follows:
Case 2:
The system derives the segment from the revenue items and inherits it to the business partner items. In this case,
the derivation is performed using the profit center. You must therefore assign a profit center in the revenue
item and assign a segment to this profit center in the master record.
Case 3:
The system derives the segment from other details of the business partner item(s). (-> posting area 0301 with key
company code, business area, division, G/L account, account determination characteristic, main transaction,
subtransaction). The segment determined is then inherited to the offsetting items (revenue items).
Segment in statistical items: Certain statistical items, such as statistical charges receivables, down payment
receivables, and budget billing receivables, also require the specification of a segment. This segment is
inherited to the non-statistical follow-on postings on later payment. If the segment is not directly specified
externally on creation of the item, it is derived from the Customizing for the business partner item.

© SAP AG 3
„ Case 4:
„ Derivation via Customizing without a profit center is only possible if the segment can be determined from
the combination company code/general ledger account. (-> posting area 0300 with the key company code,
general ledger account)
„ Case 5:
„ The derivation of the segment is installation-specific using the new event 0081. Here you can use
individual logic to determine a segment for each item for which the creator of the document has not
assigned a segment. However, segments are ignored in bank items and tax items and are subsequently
replaced by the valued define in Customizing.
„ You can mix the procedure; that is, you can assign some of the segments explicitly, add some using event
0081, and determine the rest using the Customizing settings.
„ For line items that arise as follow-on posting to other line items (for example, clearing, reversal, returns,
interest calculation, write-off), if possible, the segment of the triggering item is inherited to the follow-on
items. This means that the segment of an open item is not only inherited to the clearing posting on
clearing, it is also inherited to cash discount, payment surcharges, exchange rate differences, and interest
on arrears that arise from the clearing of this item.

© SAP AG 4
 Account Assignment and Derivation of the Segment

Special Features:
„ Payments on Account without Clearing
The segment cannot be derived from offsetting postings. A segment account assignment
(default) should be defined in Customizing for the combination of main
transaction/subtransaction used for a payment on account.
=> posting area 0301
„ Tax and Bank Accounts
These neutral segments for tax and money accounts have no immediate reference to the
segment or segments that are affected by the underlying business transaction. Neutral
segments (default) are used for both of these types of account. Customizing via
=> posting area 0300
„ Cash discount, payment/exchange rate differences, dunning charges, returns charges
With the rule applied by default, the highest item involved is inherited.
For line items that arise as follow-on posting to other line items (for example, clearing,
reversal, returns, interest calculation, write-off), if possible, the segment of the triggering item
is inherited to the follow-on items.
This means that the segment of an open item is not only inherited to the clearing posting on
clearing, it is also inherited to cash discount, payment surcharges, exchange rate differences,
and interest on arrears that arise from the clearing of this item.

© SAP AG 2005

Payment on account:
For payments on account, the segment cannot be derived from offsetting postings. As far as payments on account take
place in combination with the clearing of other items, you can select the segment that has the highest amount proportion
in the clearing. However, since payments on account also take place with no clearing of further open items, this rule
cannot be applied generally. You should therefore define a segment account assignment in Customizing for at least the
combination of main transaction/subtransaction used for a payment on account.
Segments for Tax and Money Accounts:
For all balance sheet accounts that are not managed on an open item basis, the problem arises that there are no fixed
dependencies between postings on the debit side and the credit side. Therefore, where different segments are used, a
balance sheet account may no longer show a balance, but, in the ledgers, there are positive and negative balances for
different segments that then provide no useful information. Money (bank, cash desk) and tax accounts are particularly
affected by this problem. For these account categories, Contract Accounts Receivable and Payable always uses neutral
segments that you assign in Customizing. No customer-specific definitions (event) are possible here.
These neutral segments for tax and money accounts have no immediate reference to the segment or segments that are
affected by the underlying business transaction.
The system considers a general ledger item a tax item if a tax base amount is specified in the line item. The systems
considers a general ledger item a money item if either the value date is set or the attribute Financial Transaction -
Relevant is set in the master record of the general ledger account.
Cash discount, payment/exchange rate differences, dunning charges, returns charges:
For line items that arise as follow-on posting to other line items (for example, clearing, reversal, returns, interest
calculation, write-off), if possible, the segment of the triggering item is inherited to the follow-on items. This means that
the segment of an open item is not only inherited to the clearing posting on clearing, it is also inherited to cash discount,
payment surcharges, exchange rate differences, and interest on arrears that arise from the clearing of this item.
Customer-specific definition also possible using event 0081.

© SAP AG 5
 Copyright 2005 SAP AG. All Rights Reserved
„ No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information
contained herein may be changed without prior notice.
„ Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.
„ Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.
„ IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP,
Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other
countries.
„ Oracle is a registered trademark of Oracle Corporation.
„ UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
„ Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.
„ HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.
„ Java is a registered trademark of Sun Microsystems, Inc.
„ JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.
„ MaxDB is a trademark of MySQL AB, Sweden.
„ SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are
trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned
are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications
may vary.

„ The information in this document is proprietary to SAP. No part of this document may be reproduced, copied, or transmitted in any form or for any purpose
without the express prior written permission of SAP AG.
„ This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. This document contains only intended
strategies, developments, and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business, product
strategy, and/or development. Please note that this document is subject to change and may be changed by SAP at any time without notice.
„ SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the accuracy or completeness of the information, text, graphics,
links, or other items contained within this material. This document is provided without a warranty of any kind, either express or implied, including but not limited
to the implied warranties of merchantability, fitness for a particular purpose, or non-infringement.
„ SAP shall have no liability for damages of any kind including without limitation direct, special, indirect, or consequential damages that may result from the use
of these materials. This limitation shall not apply in cases of intent or gross negligence.
„ The statutory liability for personal injury and defective products is not affected. SAP has no control over the information that you may access through the use
of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party
Web pages.

© SAP AG 2005

© SAP AG 6