Derivation in PCA

We want profit center per Company Code, Plant and Material. In Trans. Code: 3KEH, we have Company Code and Valuation area which is not working in FI entry (plant). Can we add new condition for Derivation in 3KEH ? If yes, how? Is there any other way to get Profit Center for the combination of Company code, Plant and Material.
Please get the Solution.

Hi,
This setting of Plant/Material is already being done when you create the materials itself. Why do you need to derive it again through the PCA derivation rules? There is a profit center assignment done in the Sales-General view when you create the material. Of course you will create the material specific to a plant which means the posting of this combination of Co.code/Plant/Material will go that particular profit center only.
Coming to PCA derivation rules, this is normally created to derive the profit center for certain balance sheet accounts and P&L accounts.
Good Luck!!!! Assign points this input was useful to you!!!!
Thanks and Regards,
Bhuvaneswari.S

Similar Messages

Profit Center Table

Hi Sapiens
I am using an ECC6, NEW GL activated, Can I use Tables like GLPCT, GLPCO, GLPCA, GLPCP for Profit center report painter reports. or should I use tables like FAGLEXT.
What I mean, are the OLD tables like GLP* still getting update in ECC6?
Can we use FAGL* table in report painter reports
Thanks in Advance
KP

The Note pointed by Ravi is an excellent one with complete understanding of the relationship between the classic PCA and the new GL splitting characteristics. Thanks Ravi.
In a nutshell, most of the functionalities related to the classic PCA have been de-activated when the new GL splitting is enabled. You can continue to populate the classic PCA tables only for an <b>interim period</b>. SAP recommends to sign off from classic asap to reduce the volume. Tool is available to migrate the PCA to new GL splitting characteristics. Derivation for PCA needs to be arranged as dummy PCA will no longer work with the new GL.

Load getting failed due to short dump

Hi All,
Process Chain is getting failed due to following short dump Include Report LFZI_CA_PCA_DERIVATIONSU37 not found. Please suggest on rectifying this dump. Its a delta load.
Regards,
Asim

Hi All
As requested please find details short dump below. And datasource name is this GECPC_GLPCP and its extractor is ZPCC_V_GLPCP.
Short text
   Syntax error in program "SAPLZFI_CA_PCA_DERIVATIONS ".
hat happened?
   Error in the ABAP Application Program
   The current ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" had to be terminated
    because it has
   come across a statement that unfortunately cannot be executed.
   The following syntax error occurred in program "SAPLZFI_CA_PCA_DERIVATIONS " in
    include "LZFI_CA_PCA_DERIVATIONSUXX " in
   line 77:
   "INCLUDE report "LZFI_CA_PCA_DERIVATIONSU37" not found"
   The include has been created and last changed by:
   Created by: "SAP* "
   Last changed by: "SAP* "
   Error in the ABAP Application Program
   The current ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" had to be terminated
    because it has
   come across a statement that unfortunately cannot be executed.
What can you do?
    Please eliminate the error by performing a syntax check
    (or an extended program check) on the program "SAPLZFI_CA
    You can also perform the syntax check from the ABAP Edito
    If the problem persists, proceed as follows:
    Note down which actions and inputs caused the error.
    To process the problem further, contact you SAP system
    administrator.
    Using Transaction ST22 for ABAP Dump Analysis, you can lo
    at and manage termination messages, and you can also
   keep them for a long time.
Error analysis
    The following syntax error was
    "INCLUDE report "LZFI_CA_PCA_DE
How to correct the error
    Probably the only way to elimin
    If you cannot solve the problem
    notification to SAP, include th
    1. The description of the curre
       To save the description, cho
    (Unconverted)".
    2. Corresponding system log
Display the system log by callin
Restrict the time interval to 10
ter the short dump. Then choose "
nconverted)".
If the problem occurs in a probl
ogram: The source code of the pro
In the editor, choose "Utilities
ilities->Upload/Download->Downloa
Details about the conditions und
tions and input led to the error.
Information on where terminated
    Termination occurred in the ABAP program "GP9IQHCDEPFH201E24O25IAYXXW" - in
     "START_ROUTINE".
    The main program was "RSBATCH_EXECUTE_PROZESS ".
    In the source code you have the termination point in line 102
    of the (Include) program "ZFICA_DERIVE_PCA_OBJECTS_S".
    The program "GP9IQHCDEPFH201E24O25IAYXXW" was started as a background job.
    Job Name....... "BIDTPR_6726959_1"
    Job Initiator.. "ALEREMOTE"
    Job Number..... 17271800
Line SourceCde
   72 ASSIGN 'L_DERIVE_CHRT_ACCTS-UPD_CHRT_AC
   73 assign (<derive_chrt_accts_field>) to
   74 IF <derive_chrt_accts> IS ASSIGNED.
   75   zzi_attributes_upd-chrt_accts_upd = '
   76 ENDIF.
   77 zzi_attributes_upd-/bic/gactivity_upd
   78 zzi_attributes_upd-/bic/gfactv_upd
   79 zzi_attributes_upd-/bic/gglobacct_upd
   80 zzi_attributes_upd-/bic/ggforacc_upd
   81 zzi_attributes_upd-/bic/ggrracc_upd
   82 zzi_attributes_upd-/bic/ggra_code_upd
   83 zzi_attributes_upd-/bic/gsegmtion_upd
   84 zzi_attributes_upd-/bic/ggaapflg_upd
   85 zzi_attributes_upd-/bic/gsub_item_upd
   86 zzi_attributes_upd-/bic/gsegmnt_upd
   87 zzi_attributes_upd-/bic/gacctgrp_upd
   88 zzi_attributes_upd-comp_code_details_up
   89 zzi_attributes_upd-gbfi0600_upd
   90 zzi_attributes_upd-/bic/zaccsuf_upd
   91 zzi_attributes_upd-/bic/gconunit_upd
   92 zzi_attributes_upd-/bic/gtpunit_upd
   93 *--------------------------------------
   94 * Store a copy of the source fields if
   95 *--------------------------------------
   96 MOVE-CORRESPONDING <source_fields> TO z
   97 CLEAR zze_attributes.
Runtime Errors         SYNTAX_ERROR
Date and Time          04.08.2014 17:27:39
    98 *----------------------------------------------------------------------*
    99 * Derive all PCA fields for reporting
   100 *----------------------------------------------------------------------*
   101
>>>>> CALL FUNCTION 'ZFI_CA_DERIVE_PCA_ATTRIBUTESII'
   103   EXPORTING
   104     i_zfi_ca_pca_attributes     = zzi_attributes
   105     i_zfi_ca_pca_attributes_upd = zzi_attributes_upd
   106     msgty                       = 'I'
   107     recno                       = <source_fields>-record
   108   IMPORTING
   109     e_zfi_ca_pca_attributes     = zze_attributes
   110   TABLES
   111     monitor_recno               = lt_monitor_recno.
   112
   113 *----------------------------------------------------------------------*
   114 * On the recurrsive load delete entries where the data is the same
   115 *----------------------------------------------------------------------*
   116 IF zzg_realignment_run = 'X'.
   117   IF zzi_attributes = zze_attributes.
   118     DELETE source_package INDEX la_tabix.
   119   ELSE.
   120     MOVE-CORRESPONDING zze_attributes TO <source_fields>.
   121   ENDIF.
SY-SUBRC 0
SY-INDEX 3
SY-TABIX 1
SY-DBCNT 10
SY-FDPOS 0
SY-LSIND 0
SY-PAGNO 0
SY-LINNO 1
SY-COLNO 1
SY-PFKEY
SY-UCOMM
SY-TITLE Execute Batch Proces
SY-MSGTY E
SY-MSGID R7
SY-MSGNO 057
SY-MSGV1 ZBAL_LC
SY-MSGV2 A
SY-MSGV3
SY-MSGV4
SY-MODNO 0
SY-DATUM 20140804
SY-UZEIT 172720
SY-XPROG SAPCNVE
SY-XFORM CONVERSION_EXIT
No.   Ty.          Program                             Include                             Line
      Name
    8 FUNCTION     GP9IQHCDEPFH201E24O25IAYXXW         ZFICA_DERIVE_PCA_OBJECTS_S            102
      START_ROUTINE
    7 METHOD       GP9IQHCDEPFH201E24O25IAYXXW         ZFICA_DERIVE_PCA_OBJECTS_S            102
      LCL_TRANSFORM=>START_ROUTINE
    6 METHOD       GP9IQHCDEPFH201E24O25IAYXXW         GP9IQHCDEPFH201E24O25IAYXXW          1299
      LCL_TRANSFORM=>EXECUTE
    5 METHOD       CL_RSTRAN_TRFN_CMD============CP    CL_RSTRAN_TRFN_CMD============CM005    70
      CL_RSTRAN_TRFN_CMD=>IF_RSBK_CMD_T~TRANSFORM
    4 METHOD       CL_RSBK_PROCESS===============CP    CL_RSBK_PROCESS===============CM00Q    93
      CL_RSBK_PROCESS=>PROCESS_REQUEST
   3 METHOD       CL_RSBK_PROCESS===============CP    CL_RSBK_PROCESS===============CM002    13
      CL_RSBK_PROCESS=>IF_RSBATCH_EXECUTE~EXECUTE
    2 FUNCTION     SAPLRSBATCH                         LRSBATCHU13                           437
      RSBATCH_EXECUTE_PROCESS
    1 EVENT        RSBATCH_EXECUTE_PROZESS             RSBATCH_EXECUTE_PROZESS               374
      START-OF-SELECTION
REQUEST
    DTPR_1FR9TKO2U6M616ATG9C2EYKRH
    455553453544353433345434345454
    4402F16294BF256D61614793259B28
    000000000000000000000000000000
    000000000000000000000000000000
DATAPACKID
    000001
    333333
    000001
    000000
    000000
MONITOR
    Table[initial]
SOURCE_PACKAGE
    3000000001012P2013K4AU0ACD 2013005          00                                               0
    3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
    300000000101202013B415013402013001000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
    300000000101202013B415013402013002000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
    300000000101202013B415013402013003000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
    3333333333333533334345344423333333222222222233222222222222222222222222222222222222222222222223
    300000000101202013B415013402013004000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000
00000000000000000000000000000000000
33333333333335333343453444233333332
300000000101202013B4150134020130050
00000000000000000000000000000000000
00000000000000000000000000000000000
Table IT_110723[600000x1144]
{A:114*\TYPE=%_T00003S00000115O0000
Table reference: 3570
TABH+ 0(20) = 90A161080000000060C1
TABH+ 20(20) = F20D000083B00100C027
TABH+ 40(16) = 03730000242D00000400
store        = 0x90A1610800000000
ext1         = 0x60C1190C00000000
shmId        = 0     (0x00000000)
id           = 3570 (0xF20D0000)
label        = 110723 (0x83B00100)
fill         = 600000 (0xC0270900)
leng         = 1144 (0x78040000)
loop         = 128   (0x80000000)
xtyp         = ROL.115.11556
occu         = 4     (0x04000000)
accKind      = 1     (ItAccessStand
idxKind      = 0     (ItIndexNone)
uniKind      = 2     (ItUniNo)
keyKind      = 1     (default)
cmpMode      = 8     (cmpManyEq)
occu0        = 1
stMode       = 0
groupCntl    = 0
rfc          = 0
unShareable = 0
mightBeShared = 1
sharedWithShmTab = 0
isShmLockId = 0
isUsed       = 1
isCtfyAble   = 1
hasScndKeys = 0
hasRowId     = 0
scndKeysOutdated = 0
scndUniKeysOutdated = 0
----- Shareable Table Header Data -----
tabi         = 0xB008190C00000000
pgHook       = 0x404CE73B00000000
idxPtr       = 0x0000000000000000
id           = 61767 (0x47F10000)
shmTabhSet   = 0x0000000000000000
refCount     = 1     (0x01000000)
tstRefCount = 0     (0x00000000)
lineAdmin    = 606204 (0xFC3F0900)
lineAlloc    = 600004 (0xC4270900)
shmVersId    = 0     (0x00000000)
shmRefCount = 2     (0x02000000)
rowId        = 18446744073709551615
scndKeyAdmin = 0x0000000000000000
----- 1st level extension part --------
regHook      = 0xC8C0190C00000000
collHook     = 0x0000000000000000
ext2         = 0x0000000000000000
RI-CLUSTR
   0
   00
   00
ZE_ATTRIBUTES
                     00000
   22222222222222222233333
   00000000000000000000000
   00000000000000000000000
   00000000000000000000000
ZI_ATTRIBUTES
   AU0A    070221000020130
   45342222333333333333333
   15010000070221000020130
   00000000000000000000000
   00000000000000000000000
ZI_ATTRIBUTES_UPD
   XXXXX XXXXXX XX XXXX
   55555255555522552555522
   88888088888800880888800
   00000000000000000000000
   00000000000000000000000
SOURCE_FIELDS>-RECORD
   1
   0000
   1000
T_MONITOR_RECNO
   Table[initial]
ZG_REALIGNMENT_RUN
   2
Regards,
Asim
GECPC_GLPCP

Derivation Rule in PCA

Dear All,
we have an issue in profit center acccounting. Balance sheet account Vat input tax payable is picking dummy profit center instead of correct profit center. Basically we are doing the following steps. 1. Purchase order creation 2. Goods received via migo 3. invoice receipt via miro
At the time of miro posting, system is automatically created accounting document, with dummy profit center is assigned to Vat input tax payable account. For GR/IR clearing account right profit center is picking without any mistake.
Infact, Dummy profit center is assigned to this balance sheet account under tcode 3KEH.
Derivation rule is created for this balance sheet account along with plant condition to post to correct profit center under 3KEI . But system is taking only dummy profit center.
I have checked configuration and the following areas like Material master costing view, tax code areas, and account group but not find any mistake.
Please advice how to get correct profit center to this balance sheet account instead of dummy.

You have to do this with the Month end closing
TC
F.5D - Calculate
F.5E - Post
F.5F - Display Log
F.5G - Special Functions
This is the help from F.5D - Calculate
Short text
Calculate Balance Sheet Adjustment
Description
A balance sheet eadjustment distributes
receivables and payables in customer and vendor reconciliation accounts,
tax postings,
cash discount postings from the net method of posting vendor invoices as well as
valuated exchange rate differences in open items (this is a P&L item, but since receivables or payables increase or decrease depending on the valuation, a readjustment is also made for the exchange rate difference with a reverse +/- sign).
This process ensures the zero balance per business area necessary for creating business area balance sheets.
It consists of the following steps:
When posting a document, the system analyzes it to determine whether a balance sheet readjustment is necessary. If a readjustment is required, the system marks the document for readjustment.
Readjustments are calculated for the marked documents and stored in special tables.
This subfunction is described below.
The calculated readjustments are read and then distributed and posted in total to the appropriate accounts.
Fields Included in Readjustment
Readjustments are made for business areas if the function for business area balance sheets is activated in the company code in question. Readjustments are also made for trading partner business areas if the function for business area consolidation is activated.
If Profit Center Accounting is activated in the controlling area allocated to the company code, readjustments are made for profit centers as well as trading partner profit centers.
Note
The fields included in readjustment are determined when the original document is posted. Thus, the customizing settings for business areas and profit centers must be made prior to posting the first document. If these settings were not made, you can still mark posted documents for balance sheet readjustment by executing the subfunction for setting up the balance sheet readjustment (see below).
Basis for Distribution
The system uses the account assignments of the offsetting entries in the initial document to calculate the distribution. Offsetting entries are all G/L account items apart from tax items and cash discount items.
Readjustment is made only for those account assignments which were not specified during posting (their value is blank). If a value is entered in an account assignment field during posting, it is regarded as a correct entry and not changed by the readjustment.
Carrying Out the Distribution
Readjustments are transfer postings which create one or more account assignments (not blank) for the unspecified account assignments in original documents.
Scheduling the Program Run
You can run this program as often as you like.
Requirements
Account Determination
For each account, you can specify an adjustment account to post the readjustment to. Otherwise, the system posts the readjustment to the original account.
To distinguish readjustment postings from other postings, you should create separate adjustment accounts and have the readjustments posted to them.
Since reconciliation accounts cannot be posted to directly, you have to specify adjustment accounts for them.
Since readjustments are posted without tax, the accounts posted to cannot be relevant to tax.
Adjustment accounts are determined when calculating the distribution.
For more information on automatic postings, see the Implementation Guide.
Output
The log shows how many documents per company code the system calculated distributions for.
Note:
If valuation differences are noted in documents, the system always includes them in the calculation. When updating the allocation tables, it checks for whether or not calculations already exist for these documents.
If account determination is incomplete or maintained incorrectly, the system does not calculate any distributions for the affected documents. It lists both the queried entries and the affected documents.
To view the readjustment calculated for an individual document in Document Display, choose Environment -> B/S readjustment.
Additional Information
See the documentation for the other subfunctions:
Posting the distribution.
Displaying the logs of existing posting runs.
Reversing an incorrect posting run.
Redetermining the adjustment accounts if you changed the account determination or it was incomplete at the time of calculation.
Setting up balance sheet readjustment if you have already been productive with a release prior to 3.0.
Dependent functions
Readjustment must be carried out prior to creating a business area balance sheet.
Profit Center Accounting also requires the results of readjustments.

Profit center not derived in MIGO in traditional PCA

Dear All
I have a few basic questions in PCA
We are using SAP ECC 6.0 but new G/L is NOT activated
So in traditional PCA , i have mainatined all the configurations like Std hierarchy, Profit center hierarchy, basic settings etc.
While creating material, different PC is maintained for different plants.
Initially no settings were maintained in 3keh. At that time no PCA document is cretaed at the time of MIGO. However the PC is getting correctly populated in FI document.
I am confused that in case of balance sheet transactions like MIGo etc, is PC document created under traditional PCA based on material master ? settings for online transfer are active for the financial year.
Thanks in advance
Amit

Hi,
Yes. At the time of MIGO, the system picks up the profit center from the material master. Another way is to maintain default profit center in 3KEH against the inventory account. These are the two ways the system can find the profit center for the inventory account in MIGO.
Trust this helps much!
Cheers!

Derivation of Profit Centers in case of bank and Cash line items

We are in the process of configuring the Profit Center Accounting functionality. We are in ECC 6.0 but have not migrated to New G/L.
We understand that Profit center needs to be derived for each of the items for which it does not flow online in realtime. As regards Bank and Cash Line Items, we are not able to understand how Profit Center Derivation will happen.
We have posted an FI payment document using Tcode F110 and further to which we executed F.5D and 1KEK. Further to this, we have checked the Profit Center Total records report (2KEE). It updates the vendor line items. But it does not reflect the Bank line item. Unless this happens, we understand that our Profit Center wise Trial Balance will not tally.
Kindly let us know how bank and Cash line items will update in PCA. In our view, it should derive the Profit center from the offsetting entry in the vendor invoice. Pl. correct me if I am wrong.
Pl. help.
Venkat Iyer

Hi Venkat,
You may define a derivation rule in 3KEH
Regarda
Sachin

Derivation Of partner profit center in COPA (Direct Posting from FI)

When posting from SD partner profit center is derived and transfered to COPA, so eliminations can take place.
When ever we made posting from SD, Partner profit center is coming from derivation rule which is exclusively for sales and maintained in transaction code 8KER.But whenever we made direct posting in FI, Data is transferred to COPA before profit center is derived as system does not find any data from COPA or in other words there is no any Derivation rule or table lookup or user exists in COPA from where we can derive the Partner profit center.
For testing purpose I made a derivation rule in COPA in KEDR with the same logic used in 8KER, Partner profit center is coming in COPA from this derivation rule. Derivation logic used in 8KER is very simple : source filed is KUNNR from table KNA1 and target Field is Partner Profit Center : PPRCTR from table CEPC.
I mean that i derive the partner profit center from customer number in 8KER transaction which is only for SALES and in EC-PCA only.
Now whenever I do a direct posting from FI, suppose using transaction code F-02
but partner profit center is not coming. I made a another derivation rule in KEDR in COPA and maintained the rule values there and I got the success for deriving the partner profit center.
But my query is that If I am maintaing rule values in 8KER then why I maintain the same duplicate data in KEDR.Can we use the same rule values from 8KER for direct posting of FI.
I have tried with Table lookup, derivation rule in KEDR but not getting any success.
Please tell me that without maintaing rule values in KEDR (as these are already maintain in 8KER)how I can derive the partner profit center from FI posting.Or in other words i can say that how we can get both PCA as well as COPA document with partner profit center in case of FI direct posting.
Thanks in advance.
With best Regards
Sandeep Seth
[email protected]
Thanks in advance

Dear Paolo
we have live system, we also have cost center accounting active.
do u know how to active automatic posting in Profit segment through cost center.
For Example, i post document in FB60, i assign cost center against GL expense account, if i assign profit segment the amount reflects in COPA, but i want when i assign required cost center it automatically active the profit segment ?
hope you under stand my query!!!
Regards
MuR!!!!

Profit center derivation in sales order with New GL

Dear Gurus,
We are using the New GL, so EC-PCA is not activated.
We would like to set-up a substitution rule in order to derive the profit center in the sales order and customer invoice (we don't want the profit center to always be derived from the costing view of the material master data).
I created a substitution rule with transaction 0KEM and assigned it to the controlling area with active status"3" (Other transactions + cross-company (orders + billing doc.)).
Unfortunately, it doesn't seem to be called when I create a sales order.
Can you please confirm gthat 0KEM is the transaction to use even when we use New GL without EC-PCA?
Where should I put a breakpoint in order to trace the call to the substitution rule?
Thanks a lot in advance for your help.
Regards,
Simo

Dear Gurus,
We are using the New GL, so EC-PCA is not activated.
We would like to set-up a substitution rule in order to derive the profit center in the sales order and customer invoice (we don't want the profit center to always be derived from the costing view of the material master data).
I created a substitution rule with transaction 0KEM and assigned it to the controlling area with active status"3" (Other transactions + cross-company (orders + billing doc.)).
Unfortunately, it doesn't seem to be called when I create a sales order.
Can you please confirm gthat 0KEM is the transaction to use even when we use New GL without EC-PCA?
Where should I put a breakpoint in order to trace the call to the substitution rule?
Thanks a lot in advance for your help.
Regards,
Simo

Determining which PCA to use between new-GL and classic EC-PCA

I tried to use 1kek to transfer AR and AP from FI to PCA but failed with message saying "Document Splitting is Activated".
We are considering using PCA to make B/S and P/L of several business unit in a company. We are using SAP 6.0. After looking for the references, I understood that I can use new-GL or EC-PCA(classic PCA) for Profit Center Accounting. I wonder which way is the best and easiest one to achieve my company's object.
As I understood if I activate document splitting, it means I use new-GL for PCA, and I should use table FAGLFLEXA of FI instead of GLPCA of EC-PCA.
I'd like to use new-GL because it's "new" and convenient, hopefully. But I found several problems using new-GL to make financial reports.
The first problem was that I couldn't make allocation with accounts which cannot be manually input like AA accounts(Building, Machine, etc.), AR/AP or materials. When I operate transaction FAGLGA35, no effect occurs on those accounts.
And the second problem is that I couldn't find a way to make a report which has accounts list on its first column and profit center list on its first row. It's surely because I'm a newbie in SAP
I think everybody trying to use new_GL encounter this problem and it's wired because I couldn't find any thread about this.
And If I decide to use EC-PCA and make allocation on GLPCA, I think I should make some CBO to transfer AR/AP to EC-PCA. Is there any other possible solution?
I have a lot of things to ask but I'm not even sure what I know and don't.
Thanks for you guru's great help.

The following notes will help you in understanding the set up of PCA in New GL with Classic PCA (EC-PCA): <b>OSS Norte no 826357</b>
You want to know
For release SAP ERP, the Profit Center Accounting was integrated into the new G/L accounting. The solution is as follows:
SAP delivers the 'Profit Center' and the 'Partner Profit Center' as fixed characteristics that are posted on the original FI postings. The data is not updated in another ledger as in the classic Profit Center Accounting.
As a result of integration of the Profit Center Accounting into the new G/L accounting, new functions such as 'Document Splitting' are available. Using the function 'Document Splitting' (online document split), you can create balance sheets for company codes as well as for other entities such as the profit center. The balance is then set to 0 for each document for the profit center.
Integrating the G/L accounting and the Profit Center Accounting into the one application also removes the time and effort needed to reconcile G/L accounting and PCA.
When implementing the new G/L accounting in Release SAP ERP, we recommend that all new customers map the Profit Center within the new G/L accounting by activating the scenario FIN_PCA (profit center update). It is not advisable to activate the classic Profit Center Accounting in parallel and consequently update parallel data volumes.
Detailed information about setting Profit Center Accounting in the New General Ledger:
Define the update of the characteristics 'Profit Center' and 'Partner Profit Center' in the ledger by selecting the scenario 'Profit center update' (Customizing: Financial Accounting (New) -> Financial Accounting Basic Settings (New) -> Ledgers -> Ledger -> Assign Scenarios and Customer-Defined Fields to Ledgers).
If you want to use the document splitting, you can define the field 'Profit center' as a splitting characteristic in the document splitting (Customizing: Financial Accounting (New) -> General Ledger Accounting (New) -> Business Transactions -> Document Splitting -> Define Document Splitting Characteristics for General Ledger Accounting). Set the 'Zero balance' indicator again for the added field 'Profit Center'. You can now create balance sheets on the profit center. You must also activate the Mandatory Field check to ensure that the profit center is set in all postings. If you want to display balance sheet items at profit center level (for example, receivables and payables) but you do not require complete balance sheets, we recommend that you do not set the indicator 'Zero balance' and 'Mandatory Field check'.
If you already used classic Profit Center Accounting as an SAP R/3 customer but you now want to use Profit Center Accounting in the new general ledger, you can continue to use classic Profit Center Accounting in parallel to the profit center update scenario in the new G/L accounting in the interim. However, we do not recommend you do this on a long-term basis due to the increased data volume and the increased time and effort required.
However, if the classic Profit Center Accounting continues to play a leading role for you, we recommend that you do not activate the document splitting in the new G/L accounting, and not for other entities such as the segment either. This is because the classic Profit Center Accounting uses certain functions of the classic general ledger that are no longer available with active document splitting (for example, transaction F.5D, Calculate Balance Sheet Adjustment).
See the following information for details about the differences between the function of PCA in new G/L accounting and in classic PCA and for details about the effects of new G/L accounting on the posting behavior in classic PCA. Even if mapped into new G/L accounting, PCA always occurs within a controlling area. SAP does not support cross-controlling area PCA. The derivation of profit center and partner profit center with the different business processes when you use the new G/L Accounting is identical to the classic Profit Center Accounting. Details about the differences are available in the following.
1. Set the proposal profit center for additional balance sheet and P&L accounts.
Release SAP ERP 2004:
           Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: If you have to set a profit center on balance sheet and P&L accounts, make entries manually, use FI substitution or implement the BADI AC_DOCUMENT. Note that the system calls the BADI AC_DOCUMENT only for postings using the accounting interface (for example, MM and SD postings), but it is not called for FI postings.
           Profit center scenario in new G/L accounting and classic PCA is active: Transactions 3KEH and 3KEI are available in the classic Profit Center Accounting for maintaining a proposal profit center for balance sheet accounts and P&L accounts. Transactions 3KEH and 3KEI also exist in SAP ERP2004 and function in the same way as in R/3: In other words, you can use the settings in transaction 3KEH to control the update in classic Profit Center Accounting, and the transactions set a proposal profit center where necessary. Keep in mind that the profit center information is therefore affected in new G/L accounting by settings in classic Profit Center Accounting.
Release SAP ERP 2005:
           Transactions 3KEH and 3KEI (from classic Profit Center Accounting) for maintaining proposal profit centers for balance sheet and P&L accounts are no longer used to set the profit center.
           Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: If you have to set a profit center on balance sheet and P&L accounts, make entries manually, use FI substitution or implement the BADI AC_DOCUMENT. Note that the system calls the BADI AC_DOCUMENT only for postings using the accounting interface (for example, MM and SD postings), but it is not called for FI postings. In addition, the new transaction FAGL3KEH and the BAdI FAGL_3KEH_DEFPRCTR are available for maintaining proposal profit centers. You can use these new functions to determine a proposal profit center depending on the company code and the account. Note that this proposal profit center does not appear on the input screen; it is derived only when you post the document. The proposal profit center is used if the line item does not contain a CO account assignment and if the profit center was not already determined elsewhere.
           Profit center scenario in new G/L accounting and classic Profit Center Accounting are active: The entries of transaction 3KEH control ONLY the transfer of line items to classic Profit Center Accounting. Transaction 3KEI is no longer relevant. To set the profit center, use the options which are available in the new G/L accounting (make entries manually, use FI substitution, or implement the BADI AC_DOCUMENT).
2. Derivation of the partner profit center
Release SAP ERP 2004:
           Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: Transactions 8KER/8KES are no longer available. Notes 997925 and 1087350 provide the functions from transaction OCCL. Alternatively, you can use the BAdI AC_DOCUMENT to set the partner profit center.
           Profit center scenario in new G/L accounting and classic PCA is active: Transactions 8KER/8KES and OCCL (reading purchase order/sales order for affiliated companies) are active. However, we recommend that you no longer use transaction 8KER or 8KES. Partner profit centers derived using these transactions are available in both classic Profit Center Accounting and in New General Ledger Accounting only if the line is relevant in classic Profit Center Accounting.
Release SAP ERP 2005:
           Profit center scenario in the new G/L accounting is active, classic Profit Center Accounting is not active: Transactions 8KER/8KES are no longer available. Notes 997925 and 1087350 provide the functions from transaction OCCL. Alternatively, you can use the BAdI AC_DOCUMENT or the new BAdI FAGL_DEFPPRCTR (enhancement spot FAGL_LEDGER_CUST_DEFPRCTR) with the method SET_DEFAULT_PART_PRCTR to set the partner profit center.
           Profit center scenario in new G/L accounting and classic PCA is active: Transactions 8KER/8KES and OCCL are active. However, we recommend that you no longer use transaction 8KER or 8KES because partner profit centers derived using these transactions are available in both classic Profit Center Accounting and in New General Ledger Accounting only if the line is relevant in classic Profit Center Accounting. Instead, if required, you should use the BAdI FAGL_DEFPPRCTR to set the partner profit center. A partner profit center determined in this way is always updated both in new G/L accounting and in classic Profit Center Accounting.
3. Displaying receivables and payables for each profit center
Document splitting is active
           The detailed information from the general ledger view about receivables and payables split online from the document splitting is NOT available for classic Profit Center Accounting. In this case, you CANNOT split receivables/payables nor follow-up costs subsequently (Transaction F.5D - report SAPF180A, Transaction F.50 - report SAPF181, Transaction F.05 - report SAPF100). This means that you CANNOT use transaction 1KEK to transfer receivables and payables to classic Profit Center Accounting. Follow-up costs split according to source can be transferred online to the classic Profit Center Accounting because these are already available in the data entry view.
           Read the documentation of the document splitting carefully. Analyze in which cases you have to set default account assignments because the document splitting is sometimes prevented by default account assignments.
Document splitting is not active
           In this case, you CANNOT display the receivables and payables according to source at profit center level within the new G/L accounting. However, you can use the old split of the receivables and payables within the classic Profit Center Accounting (transaction F.5D) as well as of the follow-up costs (transaction F.50), and you can use the periodic transfer of receivables and payables using transaction 1KEK. However, you can execute the new report for the foreign currency valuation of the open items (report FAGL_FC_VALUATION) with depreciation areas only, which means that the documents are no longer updated (valuation difference not updated in BSEG-BDIFF). As a result, transaction 1KEK copies only the original receivables/payables, independently of transaction 2KEM 'Account Valuation Differences'; in other words, the original data is not corrected by the valuation differences.
           You can use the standard report groups 8A98 and 8A99 to display the open receivables and payables in classic Profit Center Accounting.
4. Periodic transfers of asset portfolios to classic Profit Center Accounting
              As of Release 4. 7, it is possible to map a parallel reporting mapped in FI (for example, parallel accounts) for parallel depreciation areas in Asset Accounting by using particular settings (defining an accounting principle). You must stop the execution of transaction 1KEI because it would result in duplicated data in PCA because of postings to the same accounts. You must also stop transaction 1KEI with a 'different company code' or a 'different depreciation area in the different company code' because the data cannot be transferred correctly. Transaction 1KEI terminates with the error message KM 764. As of Release SAP ERP, if the new general ledger accounting is active, the system issues the message FAGL_LEDGER_CUST 076.
5. Dummy profit center on P&L accounts
              You use transactions 3KEH and 3KEI to firstly try to determine a proposal profit center in classic Profit Center Accounting for document line items with a P&L account (no cost element) and without a profit center account assignment. If the system does not find a proposal profit center, the dummy profit center is set for some activities (primarily from Logistics). If the new G/L accounting is active AND if at least one of the two characteristics 'Profit Center' and 'Segment' is used in the document splitting, the routine for setting the dummy profit center will no longer run (see Note 820121 and 832776). Otherwise the document splitting would not split a document, or not split it correctly. The system must then find the profit center that is valid for the process using the document splitting or another derivation. If this is not the case, the document line item will not be updated in the classic Profit Center (document line items with Profit Center initial are not allowed in the classic Profit Center Accounting).
6. PCA additional rows
              If you map Profit Center Accounting in new General Ledger Accounting in SAP ERP, you can use consulting note 937872 to update PCA additional lines recognized from classic Profit Center Accounting in new General Ledger Accounting.
              If you use the transfer price functions, you do not require Note 937872 because the structure of the PCA additional lines are technically "true" and are automatically posted in new General Ledger Accounting when maintained in transaction 0KEK.
7. Substitution of profit centers in sales orders
              Transactions 0KEL and 0KEM are available both in the classic Profit Center Accounting and in the new G/L accounting (Customizing: Financial Accounting (New) -> General Ledger Accounting (New) -> Tools -> Validation/Substitution)
8. Reporting
Line item reporting within the new G/L accounting
           Release SAP ERP 2004: Even if document splitting is set with the characteristic Profit Center, only one restricted line item reporting to profit centers is available in this release at present. When you use the G/L account line item list of FI, you can limit profit centers for line item settlement G/L accounts that are not relevant for the document splitting. As of Support Package 10, line item reporting to profit centers and segments is available.
           Release SAP ERP 2005: Line item reporting according to profit centers and segments is available.
Ledger reporting within the new G/L accounting
           Release SAP ERP 2004: Even if the document splitting is set with the characteristic profit center or segment, no current account reporting to profit centers and segments is available up to Support Package 10. With Support Package 10, current account reporting according to profit centers and segments is available. Also see the detailed explanations for Release SAP ERP 2005.
           Release SAP ERP 2005: Current account reporting according to profit centers and segments is available. It replaces the standard report groups 8A98/8A99 in earlier releases. However, the difference is that the foreign currency valuation correction is no longer displayed for each item because no update of the valuation in items occurs through the foreign currency valuation in the new general ledger (no BDIFF/BDIFF2 update). It is a key date-related valuation (mostly for the period end).
9. Transfer prices
              The transfer price functions (multiple valuations) are available for new General Ledger Accounting as of SAP ERP 2005. For SAP ERP 2004, see the release restrictions in Note 741821. In SAP ERP 2004, you can use the transfer price functions or multiple valuation functions only if you have activated the classic General Ledger and classic Profit Center Accounting.
10. Creating the profit center standard hierarchy
Release SAP ERP 2004: You must create the highest node of the standard hierarchy in the Customizing of the classic Profit Center Accounting (transaction 0KE5), even if you are not using classic Profit Center Accounting.
Release SAP ERP 2005: To create the highest node of the standard hierarchy, use transaction SM30 with the maintenance view V_FAGL_PC_STHR.
11. Creating the dummy profit center
Classic Profit Center Accounting is active (regardless of whether classic G/L accounting or new G/L accounting is active):
           If the classic Profit Center Accounting is active, you must create a dummy profit center to avoid postings with an initial profit center in the database tables of the classic PCA.
           If the new G/L accounting is also active AND if you are using at least one of the two characteristics 'Profit Center' and 'Segment' in the document splitting, you have to ensure in Release SAP ERP 2004 that Notes 820121 and 832776 are included. In Release SAP ERP 2005, the changed posting logic is included from the beginning. Note that the update of document line items in classic Profit Center Accounting is omitted because of this.
Classic Profit Center Accounting is not active, New G/L Accounting is active and you are using at least one of the two characteristics 'Profit Center' and 'Segment' in the document splitting:
           You do not have to create and use a dummy profit center. Using the dummy profit center can cause situations you want to avoid: For example, the system splits receivables/payables to the dummy profit center because of the document splitting (you cannot transfer them manually), or a document line item with dummy profit center account assignment is not split by the document splitting. To ensure that a profit center is assigned in all rows, set the profit center as mandatory field in the Customizing of the document splitting. However, note that this can also lead to terminations while posting, if a profit center assignment is missing.
12. Compare G/L Accounts in FI with Profit Center Accounting (Transaction KE5T)
              In classic Profit Center Accounting, transaction KE5T is used to compare account balances. In this transaction, the ledgers to be compare are fixed. If you use Profit Center Accounting in new General Ledger Accounting, use the general transaction GCAC. You can enter any base ledger and any comparison ledger.

Material Costs transfer to PCA Planning

Dear SAPguru,
How to transfer the variable cost like material costs to PCA (Profit Center accounting) planning. we have all the materials assigned to Profit center. We also run MRP.
Thanks in Advance.
Regards.,
RK

Dear Santosh,
When we upload the plan for quantity, we are expecting the material costs to be derived automatically from material master price or from MRP requirment.
Thanks
RK

Reflect changes of 3KEH table in PCA

Dear experts,
I've added a new account to 3KEH table and obviously SAP is transferring the values of this GL to PCA for all postings that were posted after the table 3KEH update. But in this way the document posted to that account before the table update are not transferred (and for this reason teh year to date balance in PCA is not correct).
Can you tell me how I can make SAP recalculate the Balance Sheet Adjustment for the documents posted in the past?
Many thanks
Cristina
Edited by: Cristina Pirola on Sep 27, 2011 2:54 PM

Apart from transferring values from cost and revenue element if we want to link balance sheet items like asset accounts to Profit center then we use 3KEH.If no profit center is set for a specific transaction in one of these additional accounts, the system posts to the default profit center for that account interval. If you require greater flexibility in finding the profit center, you can also define derivation rules for this purpose
Assign points if useful

Transfer of Bal from BA to Segment or PCA

Hi All
I would like to know whether it is possible to transfer the balance of the BUSINESS area to New Segment or PCA,once i activate the New G/L .
Procedure that i have to follow for Year end closing in the Migration Period.
Revert
Regards
Praveen

Hi
1) 1KEK - Transferring Payables/Receivables to PCA
The Payables and Receivables are not transferred online to PCA. You have to run this month end program to transfer the balances to PCA.The payables and receivables derive its profit centers from the offsetting entry line of the FI document to which they belong. In a Single invoice there are 2 products belonging to 2 different Profit centers. 2 different profit centers are captured in the sales line item. The customer is not posted with a profit center. After transaction code F.5D (Balance sheet adjustments) has been run the customer will be split according to the sales line item ratio.
2) 2KES - PCA Balance Carry Forward
Balance sheet accounts are carried forward under the same account and divided according to controlling area, profit center and function area.
Once you have activated the function for carrying balances forward in Profit Center Accounting, the system performs it automatically in the actual system for all postings which are transferred from Financial Accounting or entered manually in Profit Center Accounting. You can still Carry forward manually as one of the year-end activities.
Thanks
Rajanikanth

Transfer normal balance sheet accounts to PCA

Hi All,
Following 4 T-codes are available for transfer of balance sheet accounts from FI to PCA
1KEH                  EC-PCA: Transfer Material Stocks
1KEI                   EC-PCA: Transfer Assets
1KEJ                  EC-PCA: Transfer Work in Process
1KEK                 EC-PCA: Transfer Payables/Receivables
How do i transfer any other balance sheet account to PCA [other than through Default Profit Center (3keh)]
Regards,
Shridhar.

Hi Daniela, hi All, because this is my first posting I would like to introduce myself. I'm working with SAP since 1996, I'm certified FI and CO. I used to work as a consultant for six years and now I'm Inhouse SAP with Gerresheimer. http://www.gerresheimer.de/en/home.html
We are supporting our people around the world and also we are putting in new SAP systems in our organisation. Currently we have three different clients world wide, with different organizational levels. We are on SAP ECC 6.0 however not using the new GL yet.
So far so good ;-)..
===========
We are currently in the US trying to switch on balance sheet accounting for PCA due to business unit requirements.
We've got:
- Assets
- Material
- AP and AR
working! All with periodic transfer which we found more stable then online. When created the opening balances did match for AP and assets to FI and AR and material were just a little bit of, that was great.
Now we are running into the problem with all the other balance sheet accounts and still we are reading documentation, OSS Notes and all kind of stuff, but still we have problems. The issues are:
- Do we have to assign every account in 3KEH which is not covered by assets, ap/ar, and material? We tested it with a bank account and it is working, but the table in 3KEH only gives you the option of one PC, plus you can use derivation rule. Ok, there is a user exit but we are not sure about that...
- Why can't we use the profit center which is populated in the balance sheet account? Every BS account has the radio button 'profit center required' for example we have an accrual account in the PC is in there, we can see it, put when we move the FI document over with 1KE8 nothing happens.
- On the other hand we had an account and it was just working the way I described with 1KE8, the document was moved over to PCA.
We are really a little bit confused, since assets, AP/AR and material worked so well, we seem to be blocked on the other accounts and not sure what is the best way to go.
Any response is highly appreciated!
With best regards and all the best,
Thomas
Edited by: Thomas Sablonski on Jul 23, 2008 5:43 PM
Edited by: Thomas Sablonski on Jul 23, 2008 5:46 PM
======================================
We have got it working 100% looks nice...
basically the answer :
'- Do we have to assign every account in 3KEH which is not covered by assets, ap/ar, and material? '
is YES.
Thanks and regards,
Thomas
Edited by: Thomas Sablonski on Jul 24, 2008 11:40 PM

Material transferd to PCA

Hi
through tr code 1KEH it allows transferring material current period and previous period .for e.g. for the month of October it allows only on sept and OCT
for July and aug we are not able to transfer material to PCA so for these period it shows difference in KE5T, i refer note no 858363 still issue is unsolved can any one give assistance to over come this issue ,looking for positive response
Regards
praveen

Dear Santosh,
When we upload the plan for quantity, we are expecting the material costs to be derived automatically from material master price or from MRP requirment.
Thanks
RK

Planning in EC-PCA with material number

We have a requirement to enter Revenue plan data in PCA by using Profit Center & Account number & Material number. However, I do not see 'material' as a characteristic that can be added to the plan layout. The only available field is 'Representative Material', which we do not want to use. Does anybody know how to add the characteristic Material to a PCA Plan Layout? Thank you.

We have a similar requirement & found no way to plan utilising the material field MATNR. As you indicated, representative material is offered. We have elected to set up a 1:1 relationship of material to representative material for those materials we intend to plan and set the derivation rules as such. This seems to be the only way to accomplish this in PCA.

Derivation in PCA

Similar Messages

Maybe you are looking for