Profit center as COPA characteristic

Dear Guru ,
All my sites are profit center and i want to capture information at site level in copa and for the same i need to create a copa characteristic.
My confusion is what should be my characteristic : Profit center or Site......
Regards
Nitisha

Hi Nitisha,
If there is one to onr releationship between Profit Centre and Site there is no need to create additional characteristic "Site".
Profit Centre is so called "fixed" characteristic and is created automatically for every Operating Cncern.
Regards,
Szymon

Similar Messages

Derive Profit Center in COPA as a characteristic

Hi
I have defined an Internal Order with Business Area = 1 and Profit Center =1. There after I have defined a characteristic derivation as "
Source Field: Controlling Area =1000, Business Area = 2
Target Field: Profit Center =2
Condition
Sales Area =
What I want to do is that while creating a settlement rule, i want to settle the costs to a Business Area and profit center, which is different from the one maintained in Internal Order.
However, the characteristic is not getting derived as the step 8 for deriving profit center from CO Order master takes a preference over my derivation rule.
How can I have the profit center 2 derived in this case.
Regards
Sanil Bhandari

Hi Sanil
this note says that fields like Sales Org, GSBER, PRCTR are not available for derivation... They are greyed out and hence no derivation works on them... So, using this modification, you should open these fields for derivation...
In 4.x releases, there was an option to manually enter the desired PRCTR in settlement rule.. See if that works in your system
Regards
Ajay M

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

COPA, how to derive Profit Segment as a characteristic

In COPA I created a characteristic u201CSegmentu201D to report on the Profit Center Segment. I am trying to use Define Characteristic Derivation, T-code KEDR to derive and populate the Profit Center Segment characteristic.
I did the following: use u201CTable Lookupu201D and link it to table CEPC.
1) In the source field the following 3 fields appear and I mapped them to COPA fields:
     CEPC-PRCTR Profit Center
     CEPC-DATBI Valid To Date
     CEPC-KOKRS Controlling Area
2) In the "Assignment of table fields to target fields" section I mapped the CEPC-Segment field to the COPA "Segment" characteristic .
The problem is it does not derive the Segment!
Am I doing something wrong?
Is this the best way to determine the Profit Segment?
Have you seen this before?
Any help will be highly appreciated!!

Ajay, thanks for your reply.
The setup is exactly as you suggested, playing more with it I also added some fixed conditions and it is still not working. I did the analysis before and did it again upon your recomendation but unfortunately no sucess. The profit center=segment entries are in CEPC (checked with se16)......
Here is the log from the analysis.
    0067 Table lookup         Determine Profit Center Segment
Derivation was not carried out. Reason: Source field contains no value.
   Check condition for step
   Origin     Field Name     Description                Content                  Op. Constant                 Result
   GLOBAL     USERTEMP1      Temporary field 1 (user-de                          <   12/31/9999               Fulfilled
   CO-PA        KOKRS              Controlling Area           GLOB                     =   GLOB                     Fulfilled
   CO-PA        PRCTR               Profit Center              0000010111               =   0000010111               Fulfilled
   Source fields
   Origin     Field Name     Description                Content                  Comments
   CO-PA      PRCTR          Profit Center              0000010111
   GLOBAL     USERTEMP1      Temporary field 1 (user-de                          Source field contains no value

Third party sales revenue getting posted to Profit Center valuation in COPA

Hi,
We have activate profit center valuation for our operating concern.
During normal OTC cycle (third party sales), all the data is flowing correctly in legal view for the COPA document
In profit center valuation, only revenue is flowing and no other values like discounts, standard costs are flowing to Profit center valuation view
My question why only revenue is flowing and not any other values. Is this way system should behave
Thanks.

If you have created new GL Accounts to map the Third party scenario, the pre-requesite is that you might need to create cost elemenet with category 11 or 12.
Further only assignments are condition types assigned to value fields.
Check if the billing type is reset under TCode KE4W.

COPA Planning to Profit Center Accounting

Hi,
We are using ECC 6.0.
When we do COPA planning and transfer the values of COPA to Profit Center, no data has been transfered to profit center plan items.
We have not activated Planning version of Classic Profit Center Accounting. Is it required for ECC 6.0 also to activate Classic Profit Center Accoutning?
We have Mapped requisit Value fields of COPA to GL Accounts.
Can any one guide us in this regard.
Thanks in Advance
Sudhakar

Hi,
In COPA the planning has been done to the value field of PRCTR which represents Profit center. Through report forms the actual and plan data for the value fields can be derived in COPA itself. I dont think that the planned values can be transferred to profit center accouting. On the other hand the actuals of profit center with the same value fields can be derived in COPA.
Assign points if its useful
Regards
Kaarthik.D

COPA & Profit Center Accounting

Hi,
Pls send COPA and Profit Center Accounting Configuration material.
regards
ramesh
The thread is locked due to violation of forum's rules.

Hi,
Pls send COPA and Profit Center Accounting Configuration material.
regards
ramesh
The thread is locked due to violation of forum's rules.

Fix Characteristic and Breakdown by PrCtr Group/Profit Center

Hi Experts,
When I am trying to change as "Fix Characteristic and Breakdown by PrCtr Group/Profit Center"
In my monitor I can see only Status Details and not Profit Center
In Data basis, we maintain role consolidation unit for Company and Consolidation Profit Center and currency bearing unit is Company.
How I can overcome from this
Regards
Madhu

Hi Dan,
Thanks for your reply.
I already checked in Sway characteristics, there I can see Status details and Cons Group/Cons Unit
I need information that:
Any configuration required for this
Regards
Madhu

COPA assessment-reciever profit center

Hi there,
If in receiver of copa assessment cycle profit center being one of the receiver, will profit center get a debit and i will be able to see the cost in profit center/ or the segment consisting of profit center and other receiver will get a debit?
Thanks
Deepshikha

Hi,
Here i will explain you clearly.
e.g Cost center 1000 and assgined to profit center 1000
and your assessing to profit center 2000
you booked actual cost $9000 to cost center 1000 and profit center 1000
when you assess the posting like this
Cr:$9000 to CC 1000 and PC1000
Dr:$9000 to PSG and PC2000
postings are going to be in PCA also.
Hope this helps you.
Thanks,
Rau

Avoiding DUMMY value for profit center while posting COPA document

Hi All,
I have a requirement where I post a document using BAPI_COPAACTUALS_POSTCOSTDATA using a Z Program.
Everything works fine , but if we do not mention the profit center explicitly, it takes the value as "DUMMY". Same happens with KE21N.
I want to find a user exit where I can change this dummy value to blank again. I do not want posts with DUMMY profit center values.
Can you please suggest where can add my custom code. I think this should happen just before the document is posted.
Kindly suggest where should I add my code.
Regards,
Barkha

Hi Gangadhar,
Thanks for the input.
But for now our requirement is still the same.
So what can be the other way round for this?
Anyone, any more inputs pls.

COPA derivation - dummy profit center

Hey All
While creating a sales order the system is deriving the dummy profit center for materials assigned to only couple of Profit centers. The material master has right profit center with active status and correct validity dates. I checked the derivation rule in ke4st where a function call line is yellow. this line is realted to checking if profit center accounting is active. Can anyone suggest me why is this happening with only for two of these profit centers

SAP provided multiple derivation rules for profit center, the first one is to 'Check whether Profit Center Accounting is active' and if so DUMMY profit center is filled. You should also see follwoing derivation rules to check profit center.
Table lookup            Profit center from product/plant
Table lookup            Profit center from CO order number
Table lookup            Profit center from WBS element
Please check the derivation rule 'Profit center from product/plant' and check the Target fields section and see if derivation failed.
Regards,
Ganesh

ECCS - Adding Profit Center to Company Code Consolidation

Hello Gurus,
We use ECCS for our consolidation. We do only Legal consolidation and we also use Functional Area as a sub-item category for all the IS accounts. We are now trying to add Profit Center as one of the attributes. Initially, we planned to use the sub-item category, however, we can have only one and it's already taken by Functional Area. Is there a way I can
1. Add PC as an attribute
2. Enhance ECMCT to allow additional Sub-item?
Appreciate your advice and guidance.
Regards,
Venkat

The documentation at the menu path: t-code SPRO > Enterprise Controlling > Consolidation > Add Characteristics states:
Add Characteristics
The SAP standard consolidation database includes various preset characteristics, such as the consolidation unit, the financial statement (FS) item, the subitem, etc. If the information requirements of your group demand additional fields, you can define your own socalled custom characteristics.
This step shows you two ways to add characteristics to the consolidation database:
You can add up to five subassignments to the FS item.
You can add navigation attributes to the characteristic consolidation unit. The system then automatically assigns the same attribute to the characteristics partner unit and investee unit as well.
After adding a characteristic, the system generates the associated ABAP Dictionary objects and maintenance views.
To the consolidation database, you can also add characteristics based on structures that already exist in the SAP system (e.g. Region). However, you can also add characteristics, the structures of which still need to be generated.
Recommendation
Since custom characteristics extend the consolidation database, you should carefully examine which characteristics are to be added. SAP recommends, in particular, that you first finish creating the new characteristics, and that you make sure that want to use this set of data, before you activate the new characteristics and start the generation. This way you can avoid time-consuming deletions if a characteristic must be removed. Also, keep in mind that you can no longer delete a characteristic once you have posted data with the characteristic.
Example
Examples of subassignments for FS items are the Product Group and the Geographic Region.
An example of an attribute for consolidation units is the Company Type.
Standard settings
The standard SAP system already includes the following subassignments for FS items:
Partner unit
Subitem category and subitem
Transaction currency
Acquisition year
Acquisition period
Unit of measure
The standard SAP system already includes the following attributes for the consolidation unit:
Country
Company
Consolidation business area
Profit center
Controlling area
The attributes company, cons business area, profit center and controlling area are particularly useful when you use the integrated collection of reported financial data from your consolidation units.
Activities
1. Reorganize the field catalog. When this is done, the system copies the system field catalog into the customer field catalog. Choose Extras -> Field catalog -> Reorganize.
If you use integrated collection of reported data, during the reorganization you should include SAP's standard attributes in the selection. Note that, initially, these attributes are not included in the Reorganization selection screen.
2. If desired, create one or more new characteristics.
Enter the technical name (field name) of the new characteristic. The technical name must begin with the letters "ZZ".
Also set the appropriate indicator to define how the structure of the characteristic is to be built.
Technical Background Information:
Description, type, and length are properties of characteristics that you can enter directly or define by assigning a data element or domain. Data elements and domains are ABAP Dictionary objects that act as a central store of table field properties:
A data element defines the meaning of a field in business terms with texts and a reference to a domain.
A domain describes the technical properties of the field and defines permissible values for the characteristic if either of the following conditions is met:
- There is a list defining fixed values
- There is a reference to a check table
Normally data element and domain assignments are used to refer to check tables. You can, however, create a characteristic without any validation or texts by assigning a standard domain (for example CHAR07, NUM12).
Ways to create a characteristic:
a) Assigning a data element
Activate this indicator and assign a data element. The domain assignment is made by assigning the data element.
Note: If you run the elimination of IU profit/loss in transferred inventory and the system reads the required additional financial data from the totals database, you need to create the characteristic "product group" and assign it to data element FC_PRGRP.
b) Assigning a domain
Activate this indicator, then specify the meaning and assign a domain. By assigning a domain you define the type and length of the characteristic, and possibly you refer to fixed values or a check table.
c) Referencing a characteristic
Activate this indicator, then specify the description and set a reference to another characteristic. This has the effect of assigning the domain of the referenced characteristic.
d) Creating a characteristic with a new data element and check table
Activate this indicator, the specify the description, type (character or numeric), and length (1-32). The system generates a new check table for the characteristic.
e) Creating a characteristic without a check table (using a standard domain)
Activate this indicator and specify the description, type (character or numeric), and length (1-32). The system does not generate a check table.
Caution: Assigning data elements or domains does not itself ensure that validation, reading characteristic value texts, and Possible Entries Help will work as expected. The following conditions must be given:
The domain must have a check table or fixed values.
There must be either a text table with references to the check table, or the texts must be in the check table itself.
These conditions are always fulfilled by fields in the standard field catalog.
3. If needed, define compound relationships between characteristics in the detail screen of Characteristic Maintenance.
Some characteristics are dependent on other characteristics; that is, the values of dependent characteristics are meaningless in theabsence of values for independent characteristics. Such a relationship is called a characteristic compound. Technically, a check table then contains a key that consists of two parts.
Example: The Region, a dependent characteristic (check table T005S), forms a compound characteristic with the Country, an independent characteristic, because a region can be maintained or interpreted only if a country is specified.
Note the following restrictions when defining compounds:
Compounds can only be defined for characteristics that have a check table.
When a data element/domain is assigned, a compound is predefined by the existing check table.
Compounds can only be defined while creating a dependent characteristic. You do this by specifying the independent characteristic in the detail screen.
Only single compounds are permitted. Multiple compounds cannot be made.
The compound must be defined while creating a new characteristic, and before the new characteristic is saved. This is because the save process generates the check table for the characteristic.
Note: You do not use characteristic compounds to create regular assignments between two fields (such as, consolidation unit A having the local currency USD). Rather, a compound characteristic describes the structural dependency of one field on another (as in FS item 1111 in cons chart of accounts 01 being a different item than FS item 1111 in cons chart of accounts 02).
4. Specify further properties of the characteristic:
Define the display options and the sequence number of the characteristic for reports and so forth.
Activate the Subassignment indicator for all characteristics used as subassignments for FS items.
Activate the Fixed value in breakdown category indicator for all subassignments whose value is determined by the breakdown category (e.g., as with the characteristic subitem category).
Activate the Default value indicator if applicable. Then the characteristic appears in the implementation step Define Default Values. A default value is not necessary and cannot be set if you activate the Fixed value in breakdown category indicator
5. Enhance the checking specifications if needed:
For characteristics without a standard check table, you can enter a text table, a text field, and a long text field. The text fields must use the field type character. You can also specify a view name, usually a view of the check table and text table.
If the system fails to automatically determine the transaction codes for displaying and changing the master data, you can specify them manually.
6. To the characteristic consolidation unit assign any newly created characteristics as an attribute. Only independent characteristics can be assigned as attributes to consolidation units.
These attributes are used for sorting your consolidation units.
Note: Prerequisite for assigning attributes is the reorganization of the field catalog, that is, you need to have copied the field catalog into the customer field catalog. To do this, choose Extras -> Field catalog -> Reorganize.
7. Save and activate the new characteristic.
The Save process stores the new data and, if applicable, creates new tables and views in the ABAP Dictionary.
The Activation process sets the status of the tables, views, data elements, etc. to "active". It also generates the objects that are necessary to enable the consolidation functions to process the new characteristics.
You can activate several characteristics in one step by choosing characteristic maintenance of all characteristics in the initial screen, selecting and activating the inactive characteristics.
8. After activating the characteristic, you are asked whether to generate the view modules. Confirm the generation.
If you exit Characteristic Maintenance and want to ensure that all view modules were generated correctly, choose Environment -> View maintenance modules -> Reorganize.
9. Assign the new characteristics to field groups, if applicable.
Field groups are groupings of characteristics. These let you structure the fields in the field catalog. Individual fields may belong to multiple field groups.
Further notes
Choose Extras -> Log display to display the logs for the activities Save, Activate and Delete.
Edited by: Dan Sullivan on Oct 6, 2011 9:38 AM

Dummy profit center determined when performing MIGO (after MB21)

Dear experts,
I have the following problem in SAP release 4.7:
Step 1) Perform MB21 (ok, no problem)
Step 2) Perform goods issue (MIGO): Sometimes it determines profit center from the material correctly while sometimes it determines dummy profit center!
The correct one is the profit center of the material master but no dummy. The account has a check in Profit. Segment in OKB9 setting.I have checked that dummy profit center is determined because the characteristic "plant" is not copied to COPA for derivation. Is it a system bug? Can anyone help?
Thanks!

Hi,
Good morning and greetings,
Maintain a substitution rule in the system through GGB1 / OBBH to ensure that the right profit centre is determined during the transaction.
By maintaining the substitution the system will automatically determine.
Please reward points if found useful
Thanking you
With kindest regards
Ramesh Padmanabhan

New GL and Special GL- possible to repost to the correct profit center?

Hi,
The scenario that I have is advance payment to vendor. The mandatory splitting characteristic is Profit Center (PC). The scenario is this:
(1) create down payment    :
      Dr Advance Payment (special GL to vendor account): $12K,
        Cr Bank $12K (PC: 101)
In GL view, both lines will have PC: 101
(2) create vendor open line item :
         Dr Domestic Travel expense (PC: 105): $7K
         Dr Insurance expense (PC: 104): $5K
             Cr Vendor: $12K
In GL view, Vendor line will be split with $7K under PC: 105 and $5K under PC: 104
(3) clear down payment     :
     Dr Vendor: $12K
        Cr Advance Payment (special GL to vendor account): $12K
In GL view, Vendor line will be split with $7K under PC: 105 and $5K under PC: 104.
Advance Payment line's PC remains as 101 as per step 1.
My question is at the 3rd step, is it possible to reverse the bank posting in step 1 and repost the bank line to split into PC: 104 and 105 since we now know the advance payment is for PC: 104 and 105? This is so that we can identify outgoing cashflow is for which PC.
Any help is much appreciated. I am open to all ideas, even coding for document splitting rule if it works.
Thank you.

Hi
It would not be possible in std. But you can look at writing your code through BADI AC_DOCUMENT
Regards
Sanil Bhandari

Report Painter Report for Profit Center

Hi All,
I am creating a report for profit center in GRR1.I was using library 8A3,& ledger 8A.which uses for PCA line i tems and table used is GLPCT.which shows profit center totals by period.I ran GLPCT in SE16 and found out No data selected.I see that profit center accounting is not active in my system ECC6.0
and I didn't see any line records for profit center in any of the profit center tables.GLPCA.Now if someone knidly suggets me how to achieve this report, can I still do it profit center wise or not? which library should i use in GRR1.The layout of my report is as under.Thanks
CURRENT MONTH*
Current Yr      Current Yr    Prior Yr
Actual            Budget        Actual          Variance
YEAR TO DATE
Current Yr      Current          Prior Yr        Annual
Actual            Budget        Actual           Budget    Variance
Regards
Shaun

Thanks Abhijit , I can now see my report group at the bottom of the list .I assigned you full points.I posted another question regarding report painter .If you could also give me some guidance on that.When I was creating rows and updating cost elements with account numbers.I set up 3 revenue accounts and then ran the report to see if I get any data for profit centers.I did get data but when I double clicked on one of the account,it displays this messsage.I read the msg. but could not make any sense with it.for example in definning row I put account number from/to 400000- 400000    Explode. and thats a characteristic.
No valid master data for characteristic 'Account Number'
Report MEG1 does not contain any data pages.
No valid master data for characteristic 'Account Number'
Message no. GR633
Diagnosis
No valid master data within the specified interval was found for the characteristic 'Account Number'.
Explanation:
For each characteristic that is processed in a report, the Report Writer optimizes the interval limits which are relevant for selecting data from the database.
Example:
A report contains the characteristic 'account', for which an account interval from 100000 to 200000 has been entered. However, if the master data validation shows that the lowest/highest account in this interval is 110000/190000, the selection will be limited to accounts 110000 to 190000 only.
The system returns this error message if no master data exists for the interval.
This error is typically caused by an invalid version. In FI-SL Special Purpose Ledger, for example, versions are assigned to the ledger and are defined in configuration. The report definition can then contain a non-defined version. A similar situation applies to controlling (cost center accounting): here, versions are assigned to the controlling area and fiscal year and can be defined in planning.
Another cause of this error is a ledger that is not assigned to the table for which the report was created.
Technical information:
The field name for 'Account Number' is 'RACCT'.
System Response
The system cancels processing.
Procedure
Check the report definition, or the specified master data, or the intervals.
Regards
Shaun

Profit center as COPA characteristic

Similar Messages

Maybe you are looking for