RE: In COPA define value fields

Hi All,
My requirement is to create Value field for COPA
- how to create value fields and where to create and where to assign them
- i have to assign one (sale conditon type) for this what i have to do
i am trying to create in t code kea6 assigning in ke4i it is giving error message.
please let me know.
points will be assigned.

Hi,
First of all you have to create Operating Concern
2. Create Characterastics in KEA5
3.Create Value fields in KEA6
4. set your operating concern
5.assign SD condition type to Value field in KE4I.
6.check whether sd condition type created in V/08 for Pricing procedure.
Regards,
Sany.

Similar Messages

To change User defined Value field from Amount to Quantity in COPA

I have created a created a User defined Characteristics VV930 - Number of labor hours. While creating, i wrongly assigned the chategory Amount instead of Quantity.
Now when i am trying to change it is giving me errors.
Also it is not allowing to delete and recreate the new VV930 with category as Quatity.
No data is posted in COPA.

Hi Rupesh
1. Remove it from your COPA data structure in KEA0... Shift it from Left to right in data structure screen... Then try to delete it
2. Else, reserve this Value Field for future use and change the name as of now to XXXXXX...Create a new Qty Field for your use now.
Regards
Ajay M

COPA - New value field defined as "Last Value"

Hi experts:
We have defined a new value field that it is integrated as a 'LAST VALUE' instead of 'SUM'. However, when posting different entries the amount continue to sum instead of showing the last value. The new value field has the same behaviour as a sum value field. In KE30 all entries are summarized and in table CE3XXXX I can see all entries summarized.
Now, I have to entries (100 + 125) for the same characteristics and the value field show the total amount 225 instead of the last value 125.
Thanks in advance for your help
Best regards
   Jose

Hi,
      The 'last value' is typically used for no of employees or some similar value where the last number is really important. In such cases it does not make sense to use this field in KE30 reports and take the sum of these values.
    In such cases only the last entry posted is important from reporting purpose. Also this type of value fields are important in planning.
regards
Waman

COPA new value field transport

Hi
Is there any way to trnsport only the single value field in COPA to other instance?
Regards
HK

Hi,
If Value field is assigned to Data structure then you need to regenerate operating concern in KEAO. you cannot transport single value fields in COPA. All value fields which are assigned to Data structure are picked during transport.
Regards,
Sreekanth

Transport COPA new value field

Hello SAP Experts,
I have created a new COPA value field. Now i would like to transport the same to Test (Acceptance or Quality) server, can you kindly let me know how can i proceed with this.
Your inputs are highly appreciable in this regard.
Many thanks in advance.
Regards,
Pavan Kumar P

Hi,
Please read note 131664 regarding the use transaction KE3I to transport operating concern structures.
In principle you can transport a new value field with a transport of an operating concern - part 'Structures: ABAP Repository objects' in transaction KE3I.
You need to perform the following steps:
1. Value field added in source system thro tcode KEA6
2. Regenerate the environment of operating concern in source system (tcode KEA0)
3. Transport using KE3I (select: ABAP repository objects)
4. Regenerate the environment of operating concern in target system.
Via transaction code KE3I you have the option to transport specific object classes. If you select 'Structures: ABAP Repository objects' the following settings are transported:
Cross-client objects in the SAP Repositiory
- Tables and structures of the operating concern (CE1xxxx - CE8xxxx)
- Domains and data elements for CO-PA characteristics
- Master data tables for CO-PA characteristics (without data)
Cross-client control tables
- CO-PA field catalog
- View directory
Normally we advise customer to add a new value field/characteristic to
DEV then transport to QAS and then transport to PRD. This ensures that
the operating concerns in the 3 systems are in sync.
regards
Waman

Assign direct material cost to value field in copa while issue to Prod orde

Dear All,
My requirement is like this:
There are some 16 material groups from A to P each containing some materials(finished goods).
I want to allocate overhead to different material groups(Charecteristic in copa) in COPA using the periodic assesment cycles. I am able to allocate overhead(admin & sales cost) to different value fields in copa from different cost centers.
I want to analyse the product cost and also the profitability of each material group in COPA using Report painter. Iam able to pull all the costs which i assign to value fields using assessment. But, i am NOT able to get the direct material cost which is issued to production orders using BOM.
My question is whether we can assign the direct material cost to any user defined value field(material cost value field) while the material is being issued to production orders. Is there any automated way where we can directly assign the direct material cost to value field in copa while issuing the material to Production orders.
Pls explain me whether we can do it. if yes how?
Thank you very much in advance.
Regards,
Vishnu
VST-IT.

PA is a Profitability analysis tool. That means it gets updated when a sale is made, not before. (Except for settlements and assessment of overheads.)
Goods issues for production gets updated in CO-PC, and needs to be analysed there. If you don't, you loose all the inbuilt tools for variance analysis, cost estimate comparisons, Wip Calculation etc. To the best of my knowledge, a Profitability Segment cannot be used as a cost object in Production Planning, because amongst others, you need to be able to capitalise the produced materials to stock at the end of the production run, or to WIP at the end of the Financial period,which is not possible with PS.
Similarly, overheads are recorded in CCA and needs to be analysed there.
If one goes against these big groupings in SAP, you always run into problems.

Transporting of Value field name/description translation in COPA

Hi,
I have a problem with Value field name/description translation in COPA. In English language all user defined value field names are defined properly with name and description.
In my native language their names are blank and its hard to use COPA reports as we don't see the description of particular value fields.
Is it possible to tranport the names of value fields from DEV system to PRD system? I have altready translated value fields on DEV but there is no option to create transport with the translations or changes in the names I made.
If it is possible to transport it to PRD, do I have to refresh and regenerate Operating concern in PRD?
I am not confident with refreshing Operating Concer on PRD client - as it might be generated with errors and stop all sales.
What would you advice?
Kind regards,
Karol

Hi Nakul,
Kindly check if you have reset the value field in KE4W. If this does not help then please provide us more details about the document that you have posted.
Regards,
Abhisek

Value field does not updated in COPA Billing

Hi,
We are facing one issue in COPA.
We are created one Condition type ABC, this condition type we have selected the check box for Accruals in control data 2 ,then we are created one Account key 123 , in pricing procedure we have assigned this one ABC condition type to accrual account key 123.Then Vkoa setting in TAble one customer/mat/ acckey combination we have assign one g/l like transfer cost with (11 cost element) in provision for accrual column.
COPA side setting as been done :
step 1: user defined value field like NMR and this value field is assign in ke4i with respective condition type ABC value filedNMR.
We are generated the billing document.in a/c document is below entry.
Customer a/c dr 10
Trasnfer Cost a/c dr 1
To Cost on sales a/c 11-
Above one 1 rs in coming in condition records in billing document.But In COpa document my revunue is 10 rs with value filed, NMR value filed amount "1" is not updated.
Note :above condition type ABC we are not selecting the statistical check box in Pricing procedure
Please give me suggestion.
Regards
Reddyrrreddr

Hi Reddy
As far as I understand, any GL Account maintained in VKOA under provision column will not flow to COPA, be it B/S 8754 or P/L 4567.
The GL mapped under G/L Account column would essentially flow to COPA. Therefore in your case, values posted to GL 1234 should flow to NMR Value field through SD Condition type ABC.
I dont have access to system so can you check below options:
1) Once you had done KOFK, did you create the cycle from scratch to evaluate the results. If so and if its still not working, can you please share with us the output of the KEAT and / or KE4ST report for the billing document, posted to accounts.
2) Also check in the pricing procedure, if you set an account key under accruals column, then in VKOA, you need not have to mention seperate GL under Provision Column. Just maintain the GL account under "G/L account" column for each Account keys (4 records with KOFI & KOFK)
3) If above also doesnt help, test if removing the check from Accruals in the ABC Condition type configurations really helps, in which case you may need to maintain GL under provision column.
Will explore more options and will revert back hopefully by tuesday.
Hope it helps
Regards

User defined field in SD and its link to Value field in COPA (??)

Dear All,
We have created one "Z" field i.e. user defined field and its in VBRP Table. This is a quantity field. to update the values in this field we have used an exit in sales and distribution module. Now, by defining this exit values are correctly populated in VPRP table on line item basis.
Requirement here is we need to get this field in COPA, for same i have carried out the quantity field assignment to value field (KE4M).
Even after this configuration profitability segment is not updated.
Regards,
Sayujya
Edited by: sayu on Mar 15, 2010 10:13 AM

In the past I did something similar and had to use function module EXIT_SAPLKEAB_001 in enhancement COPA0002 to populate the field. To use this exit you'll first need to add a user exit id to your valuation strategy (transaction KE4U). The help on the function module is pretty good, but if you run into a problem let me know.
thanks,

Impact of Addition of New Value Fields in the existing Op. Concern-COPA

Hi All,
Want to know the steps of adding new value fields in the existing operating concern in COPA?
What is the overall impact of addition of New Value fields in the running Operating Concern?
How do we test the addition of new value fields?
Is the addition of New Value fields to the running Operating Concern advisable?
Your support and advice is highly anticipated and appreciated.
Thanks & Regards
9819528669
Ohter details are as follows...
VALUE FIELDS : Defines the Structure of your Costs & Revenues. (Op. Concern 120 Value Fields)
1)     The client requires three new value fields to be created. Value fields for :
-     Other Airport Charges - International
-     Cargo Commission Cost
-     Personal Cost (Direct)
2)     What are the Steps involved in creation of new value fields? The steps are :
1)     Before creating new value field we need to check whether we can use already existing UNUSED value fields (There are 62 value fields created for the op concern 1000, in production the value fields TBUL1-L7 i.e. to be used (I assume) screen shot1 provided. My predecessor has used value field VV291, VV292, VV380 original description being TBUL3, TBUL4, and TBUL1. I believe he has changed the description in development client and created a transport request ref screen shot 2)
2)     You can create new value field thru T-Code KEA6 (4-5 characters beginning with VV) u2013 My predecessor has reused the value fields originally created he has not created new one I believe. please provide give your comments)
3)     Specify whether this field is for Currency or Quantity (currency defined in attribute of op concern and quantity defined by its own field u2013 unit of measure) u2013 My predecessor has configured the three value fields as Currency.
4)     Describe how the values in this field are aggregated over characteristics. (SUM, LAS, AVG) u2013 My predecessor has aggregated all the three value fields as SUM and they are in Active status.
5)     After the value field is created you have to add the value field (active status only) to the operating concern by Editing the Data Structure. (I guess this is done in the next step)
6)     Assign newly created Value fields to the Operating Concern u2013 T-Code KEA0 (In development client the value fields are assigned to the op concern 1000 refer screen shot 3. In the production client also those three value fields exist (does it mean they are assigned? your comments please.) As they have the original description TBUL3, TBUL4, and TBUL1 refer screen shot 4.
7)     After the Data Structure is defined you need to activate them. (creates plan vs actual database) u2013 Go to the data structure tab and Choose Activate. The status in dev client is Active with correct description but in the production client it is Active with the OLD description. After addition of the value field you need to regenerate the operating concern. T-Code KEA0 u2013 right?
8)     Condition Types are assigned to Value Fields? Donu2019t know u2013 T-Code KE45 (I think this is NOT required in our case u2013 Please give your comments)
9)     Define and Assign Valuation Strategy u2013 Cost assigned to Value fields u2013 T-Code KE4U (I think this is also NOT required in our case)
10)     Define PA Transfer Structure for Settlement u2013 T-Code KEI1 (This step is crucial u2013 I think I have to to include newly created value fields, but am not aware how to do it and what is the connectivity or what happens after this is done)
Note: My predecessor has created a Transport Request No# KEDK902167 for the value fields created by him.
3)     Whether my predecessor has performed all the steps for value field creation? How to test it and check that?
4)     If yes then, Do I need to perform additional configuration or can I proceed to transport it to Production?
5)     What is COPA Allocation Structure & PA Transfer Structure? Where and Why It is used?
6)     What are the different methods of cost and revenue allocations in SAP?
7)     I have checked the status of the value fields across clients, It is as followsu2026
     Value Field     Value Field For     Description     Development      Quality     Production
1     VV291     Other Airport Charges International     TBUL3     Exists      DNE     DNE
2     VV292     Cargo Commission Cost     TBUL4     Exists      DNE     DNE
3     VV380     Personal Cost u2013 Direct     TBUL1     Exists      DNE     DNE
#DNE : Does Not Exist (assumed since the description given to value field is not the same as in development client.)

HI sree,
ofter creation value field and saving that time reqwest number appeare copy the reqwest number and go through the se01 select that reqwest number select and transport click the truck symbole, and draft a mail to basis guyw.
Thank You!
Best Regards,
pradheep.

CO-PA : How to define separate value fields for Revenue & Incoming SO

Hello friends,
In CO-PA reports, how can I see separate value fields for Revenue (ERLOS) and "Incoming Sales Order" ? I created a value field for incoming sales order value.
But when I goto customizing for CO-PA, Transfer of Incoming Sales Orders and Transfer of Billing Documents refer to the same tcode KE4I. So its not possible for me to define a condition type to 2 separate value fields.....how can I see both incoming sales order value and revenue (from invoices) together ?
Any advice you can give me would be greatly appreciated.
Cheers
Ken

Hi
In COPA value flow from a condition type thru a value feild.
One condition type can be assinged to only one value feild ratio
Condition    :        Value feild
     1                         1
But where as ratio between
Value feild              :         Condition
      1                                     N
Apart from above check the operating concern check for the values & characteristics and activate.
Thanks
Colin Thomas

Delete COPA value fields in a productive system

Does anyone have practical experience with deleting COPA value fields in a productive system?
The issue is that old, no longer used value fields should be deleted from a productive system to allow creating new ones, as the maximun number of value fields is reached.
An alternative would be to delete the prior transaction data captured on these no longer to be used value fields and rename them for their new use (to avoid that different kind of old and new data is reported on the same value field).
I am refering to the documentation on transaction KEA0 (or OSS note 160892 up to release 4.5), where it is mentioned that deleting value fields should only be done for operating concerns that have not yet been used productively. Did anyone do this already in a productive system?
Cheers, Peter

To delete characteristics or value fields, you should perform the following
activities:
1. Delete the corresponding characteristics and value fields from
Customizing in all clients (this includes forms, reports, planning
layouts, and so forth). To locate characteristics and value fields, use
the appropriate where-used list in the Customizing Monitor. You can
access it by choosing Tools -> Analysis -> Check Customizing Settings
(TA KECM).
You can jump directly from the where-used list to the relevant
Customizing transaction and then delete the appropriate field there.
2. Switch to the screen for maintaining the data structure of an
operating concern (Maintain operating concern).
3. If you need to effect other changes to the datastucture for the
operating concern before making any deletions, effect those changes and
save the data structure.
4. In order to be able to select the fields of the data structure,
choose Extras -> Characteristics (or Value fields) -> Unlock.
5. Select the characteristics and value fields to be deleted and remove
them from the data structure with the "Reset fields" function.
6. Reactivate the operating concern. The system starts by checking
whether the operating concern contains any data and whether the fields
to be deleted are still being used in any Customizing settings.
7. If none of the fields are still in use, the system then starts the
re-activation. If the operating concern does not contain any data or
does not require the database system to be converted, the tables are
activated. You are then able to activate the environment for the
operating concern. In this case, the following activities no longer
apply.
If the operating concern already contains data, a system message tells
you that the database needs to be converted. If you proceed, an
activation log appears (at the top of the list).
8. Analyze the activation log. If it only contains error messages
telling you to convert the tables, proceed with the next activity.
You must otherwise remove the cause of the errors before the tables can
be converted. In this case, you should answer "No" to the next prompt,
which asks whether the conversion transaction should start.
9. If you still only receive error messages telling you to convert the
tables, choose "Back" and start the conversion.
10. Plan a job for the conversion. A list of the tables to be converted
is shown for this. If the tables only contain a small amount of data
(less than 10 000 records), then all the tables can be converted in one
job. In that case, you can select all the tables.
For larger tables, conversion should take place in several jobs.
However, you should ensure that table CE4xxxx (where xxxx = operating
concern) is the last table to be converted.
Warning. No other changes can be made to the operating concern during
the conversion.
A copy of the table is generated during the conversion. The database
system should have sufficient memory available for this copy.
To schedule conversion as a job, use the "Schedule selections" function.
You can display the current status of the conversion by selecting the
"Refresh" icon. Tables disappear from the list once they have been
converted sucessfully. If a conversion is taking a while, it is also
possible to leave the transaction. You can then continue the conversion
using DB requests -> Mass processing in one of the following ways:
With the job overview. You access this by choosing System -> Services ->
Jobs.
Using the database utility transaction. You access this by choosing
Utilities -> Database Utility in the ABAP Dictionary menu.
You can use the status function to call up the status of the operating
concern during operating concern maintenance. You need to activate all
tables after conversion.
11. To analyze errors that have occurred during the conversion, you can
use the database utility transaction by choosing Extras -> Logs. The log
has the same name as the conversion job: TBATG-date. You can also
restart the conversion with this transaction.
For more information on the database utility, choose Help -> Application
help while still in the above transaction.
12. Once you have activated all the tables in the operating concern,
generate the operating concern environment from within operating concern
maintenance.
You can then use the operating concern again.
Please, refer to the IMG documentation under Controlling ->
Profitability Analysis -> Structures -> Define operating concern
-> Maintain operating concern, for further details.
Hope it helps

FI to COPA Value fields Currency translation

Hello All,
We are having the following situation.
1) The company code currency is RUB
2) Operating concern currency is EUR.
3) Second local currency as EUR.
we are using a customised program to run the settlement. This program calls the KE21 transaction and creates the settlement line items.
The program passes the amount in the document currency to Ke21 transaction and the transaction inturn does the currency conversion to operating concern currency EUR.
The issue is that because of this there are some differences in the Amount in FI and Amount in CO-PA in EUR currency because the RUB exchange rate is volatile.
The userexit COPA0004 will give control only to the exchange rate type that can be defined.
Please let us know whether there is any user exit or any other way to have a control on the date of the currency conversion.
We tried sending the Second local currency,in this case the amount in EUR(Operating concern) is correct but the amount in the company code currency-RUB in COPA (Ke23)is not matching with the FI amount.
Hence our assumption is that if we can have a control on the date of the conversion then the FI and COPA amounts will match.
Please let us know incase the above requirement can be achived in any other way.
Thanks in Advance.
Regards
Pavan M

You should be able to achieve this by implementing the COPA valuation enhancement. Enhancement COPA0002, EXIT_SAPLKEAB_001 can be used to populate value fields. To use the exit you first must assign an exit number to your valuation strategy (t-code KE4U), which you then use in the exit. You can find documentation for the enhancement there as well.
thanks,

COPA value field not getting complete SD condition value

Hi Gurus,
I find a strange issue when a billing document is transferred to COPA (well basically, after a billing document is released to accounting, all the controlling docs and COPA docs are generated). The issue is, I have a SD pricing condition which has been assigned to COPA value field. I also have the transfer +/- sign checked on this value field. Now consider the following 2 scenarios:
Scenario 1: In VKOA, two different G/l accounts have been assigned to the corresponding pricing condition account key. These 2 G/L accounts have been defined as cost elements with category '12' (its related to sales deduct). and fall under the same cost element group. When a billing doc is posted to accounting and hence to COPA, I see that there is no value in the value field and the corresponding condition type. Then I ran a simulation using KE4ST and found that I have two lines with the same pricing condition type and value field but one carries a positive value and the other one carries a negative value. Then I came to a conclusion that may be these two lines are netting out and hence there is no value being posted on the value field.
Scenario 2: In VKOA, I have assigned two different G/L accounts which fall under different cost element group and one is defined as category 12 and the other as category 1. This time I see that only 1 line of value field is brought into COPA corresponding to the pricing condition and hence I see a value in COPA value field. But business doesn't want to go with scenario 2 as they don't want to use two cost elements in different cost element group. Also one is sales deduct and the other is primary cost/ cost reducing revenue. So there is a balance getting accumulated in the primary cost/cost reducing revenue element.
How do I resolve this issue to post a value to the COPA value field using scenario 1? I have also tried to uncheck the transfer +/- sign but I am unable to even release a billing doc to accounting as it is giving me a error message,: "correct the value field assignment for the condition type".
Please help me !!
Regards,
Sony

Version of SAP?

Cost Elements and COPA Value Fields

Hi All,
Should all the cost elements created in CO be assigned to value fields in Costing Based COPA?
I am a bit confused . . .
Regards,
Ravi Kumar

Hi ravi,
Basically fist you understood, how the values are flowing into the CO-PA. ie When ever billing document generated co-pa document generates automatically. based on your condition type and account keys.
While defining pricing procedure, they mapped the conditon type against releavant account key.
Based on the releavant account key they assigned releavant cost element under VKOA.
Against these condtion types they assgined value filed under KE4I in co-pa.
This is the way system will capture cost elemetns under copa. KIndly revert in case any issue.
Regards
Maruthi.

RE: In COPA define value fields

Similar Messages

Maybe you are looking for