Profit Center Derivation

in mySAP ERP 2005

SAP AG

08.08.2005

©SAP AG 2005

„ See also SAP Note 826357

© SAP AG 1
 Profit Center Derivation in New General Ledger Accounting
in mySAP ERP 2005

Default profit center for additional balance sheet accounts and P&L accounts
„ The transactions used in classic Profit Center Accounting, 3KEH and 3KEI, are
no longer used.
„ Instead, there is the new transaction FAGL3KEH as well as the BAdI
FAGL_3KEH_DEFPRCTR (company code / account).
„ Where necessary, derivation by manual entry, FI substitution, or
implementation of the BAdI AC_DOCUMENT (for AC interface postings).
„ Profit center scenario in New General Ledger Accounting and classic Profit
Center Accounting active: Entries in transaction 3KEH ONLY control the transfer
of line items to classic Profit Center Accounting. Transaction 3KEI is no longer
relevant.
„Derivation for partner profit centers
„ Entries in transactions 8KER/8KES still active, but now only available in classic
Profit Center Accounting. For this reason, the new BAdI FAGL_DEFPPRCTR
should be used.

© SAP AG 2005

„ => The transactions 3KEH and 3KEI originating from classic Profit Center Accounting for the
maintenance of default profit centers for balance sheet accounts and P&L accounts are no longer used to set
the profit center.
„ Profit center scenario active in New General Ledger Accounting, classic Profit Center Accounting
not active:
Where necessary, set a profit center on balance sheet and P&L accounts using manual entry, FI
substitution, or the implementation of the BAdI AC_DOCUMENT. Note that the BAdI AC_DOCUMENT
is only called for postings via the Accounting interface (such as MM or SD postings), but not for FI
postings. In addition, the new transaction FAGL3KEH as well as the BAdI FAGL_3KEH_DEFPRCTR
can be used to maintain default profit centers. In this way, you can determine a default profit center on the
basis of company code and account. Note that this default profit center does not appear in the entry screen;
it is not derived until the document is posted. The default profit center is applied if the line item does not
contain a CO account assignment and the profit center has not already been determined elsewhere.
„ Profit center scenario in New General Ledger Accounting and classic Profit Center Accounting
active:
Entries in transaction 3KEH ONLY control the transfer of line items to classic Profit Center Accounting.
Transaction 3KEI is no longer relevant. To set the profit center, use the options offered in New General
Ledger Accounting.
„ Derivation of Partner Profit Center (transactions 8KER/8KES):
„ Profit center scenario active in New General Ledger Accounting, classic Profit Center Accounting
not active:

© SAP AG 2
 The transactions 8KER/8KES are no longetr available. Use the BAdI AC_DOCUMENT or the new
BAdI FAGL_DEFPPRCTR to set the partner profit center.
„ Profit center scenario in New General Ledger Accounting and classic Profit Center Accounting
active:
The transactions 8KER/8KES are active. However, SAP recommends no longer using transactions
8KER/8KES because partner profit centers derived in this way only become available in classic Profit
Center Accounting, not in New General Ledger Accounting. If necessary, you should use the BAdI
FAGL_DEFPPRCTR to set the partner profit center. A partner profit center determined in this way is
updated in New General Ledger Accounting as well as in classic Profit Center Accounting.
„ Dummy profit centers on P&L accounts:
„ In classic Profit Center Accounting, an attempt is first made using transactions 3KEH and 3KEI to
determine a default profit center for line items with a P&L account (no cost element) and with any profit
center account assignment. If no default profit center is found, the dummy profit center is set for some
transactions (in particular those from Logistics). If New General Ledger Accounting is active AND at
least one of the two characteristics Profit Center and Segment are used in document splitting, the routine
for setting the dummy profit center is not run (see also SAP Note 820121). The profit center valid for the
process must then be found using document splitting or another derivation.

© SAP AG 3
 Profit Center Derivation New General Ledger Accounting
in mySAP ERP 2005

BAdI BAdI
AC_DOCUMENT AC_DOCUMENT

Derivation PC / PPC
(only AC interface) (only AC interface)

TA FAGL3KEH BAdI
/ BAdI FAGL_DEFPPRCTR
FAGL_3KEH_DEFPRCTR

No longer used if PC scenario is

TA 3KEH / 3KEI TA 8KEH / 8KES
active in New General Ledger
Accounting

Profit Center Partner Profit Center

(PRCTR) (PPRCTR)

© SAP AG 2005

Important note for active document splitting:

„ Classic Profit Center Accounting and New General Ledger Accounting are active:
In New General Ledger Accounting, document splitting is active with the characteristics Profit Center and/or
Segment. The reason for this behavior is the logic in Profit Center Accounting. The following rules in the
Accounting interface apply for the validation module in Profit Center Accounting: If a line with P&L
accounts that are not cost elements does not yet contain a profit center, the transactions 3KEH (and 3KEI)
are first analyzed. If still no profit center is set, the dummy profit center is set for some transactions (see
Include LPCRWF01: FORM dummy_fuellen). The segment is then derived from the new profit center that
was set. For this reason, document splitting in General Ledger Accounting can no longer split this line. With
SAP Note 820121, the dummy profit center is no longer set for lines with P&L accounts. Consequently, no
segment is derived either, and the line can be split.

© SAP AG 4
 New Transaction FAGL3KEH

FAGL3KEH

© SAP AG 2005

© 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