Value Field Analysis

Hello gurus
Actually i am not a consultant but i have query, like the client where i am working with has recently implemented SAP. But the problem is that CO and FI is not Reconciled so they told me to find the differences and their possibilites. Can anyone tell me how i can find the G/L mapping against value field like in specific value field which G/L are mapped. Kindly tell me any T-code or the process for this.
Thanks and Best Regards,
Hassan Ali

Hi..
The system uses the flows of actual values to transfer data from other module to value fields in CO-PA.
You should understand the flows of actual values through the below sap help portal site to find the G/L mapping against value field.
Flows of Actual Values - Profitability Analysis (COPA) - SAP Library
In case of Billing Documents, Values in billing documents are assigned to condition types in SD, accounts in FI and value fields in CO-PA.
You can use t-code KEAT to reconcile the data between FI and CO-PA.
Refer to http://help.sap.com/erp2005_ehp_07/helpdata/en/40/c52df80d1e11d2b5cf0000e82de856/content.htm.
In case of Direct Postings from FI, all assignments of values and quantities to the value fields in costing-based CO-PA are defined using the PA transfer structure "FI“ through the following IMG path: Profitability Analysis->Flows of Actual Values->Direct Posting from FI/MM->Maintain PA Transfer Structure.
Refer to http://help.sap.com/erp2005_ehp_07/helpdata/en/7a/4c3aba4a0111d1894c0000e829fbbd/content.htm?frameset=/en/7a/4c48c64a0111d1894c0000e829fbbd/frameset.htm
In case of Periodic Overhead Allocation, the cost of cost centers is transferred into co-pa using PA Transfer Structure for Assessmentof co-pa cycles.
Refer to http://help.sap.com/erp2005_ehp_07/helpdata/en/7a/4c3ac74a0111d1894c0000e829fbbd/content.htm?frameset=/en/7a/4c48c64a0111d1894c0000e829fbbd/frameset.htm

Similar Messages

Order value fields by field label in the profitability analysis document

Hello,
I am displaying a profitability analysis document and I want to order the value fields by their technical name (VV001, VV002, VV003...) instead of in alphabetical order (the system orders them by the field label).
Is it possible?
Thank you very much
Bea

Hello,
Check in KE4M whether sd condition type FKLMG is mapped corresponding value field in COPA.As you are getting the value for other company codes, this setting should be there.
You can also try checking simulation of billing document transfer through KE4ST. Check the details analysis
thanks
Hari

Characteristic and value field in profitability analysis document

hi,
1 in VF03, when i click the accounting button, i got the profitability analysis document.
when i click on it, it shows display line items with tabs like characteristic and value fields.
may i know where i can see the characteristic and value fields defined where each time when i click on profitability analysis document, i get the list of characteristic and value field.
2 also if open FB03, can see the profit segment. the characteristic and value defined in where?
any tcode or spro that can show how the characteristic and value defined in profit segment.
thanks

Hi
Pleaase go through the below mentioned links. It will give you a better insight on the topic you want information about.
http://help.sap.com/saphelp_erp60_sp/helpdata/en/7a/4c38334a0111d1894c0000e829fbbd/content.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/7a/4c388e4a0111d1894c0000e829fbbd/content.htm
http://help.sap.com/saphelp_erp60_sp/helpdata/en/7a/4c389b4a0111d1894c0000e829fbbd/content.htm
Hope this helps. Let me know if you have any questions.
Karthik

Define value in value field for CO-PA analysis.

Hello everyone,
I am looking to determine the values of a custom value field I created. This new value field is activated and assigned to an operating concern and I am able to use it in my form.
Now I would like to "link" my field value to an GL account in FI. How can I do this?
Thanks.

Hi Elodie,
Just to add to Pavan's reply you need to use tcode KEI2.
In case of SD to COPA transfer you need to map the SD condition to the value field
regards
Waman

Exit EXIT_SAPLKEII_002 in profibility Analysis to change value fields

Hello,
I want to change some of the value fields in the records which are produced in the CO-PA with
the user exit EXIT_SAPLKEII_002.
The problem is that the table interface table T_ACCCR_PA which is for the "FI/CO document: CO-PA segment" is not filled with the generated records.
How can I change the value fields in co-pa in the user-exit than? Do I have to generate these
records myself?
Thanks.
Regards, Lars.

Hi,
Welcome To SDN!!
use enhancement COPA0001 , component EXIT_SAPLKEDRCOPA_001
Regards
Kiran Sure

New Value Field in COPA

Hi
I have created new conditions in SD. These have been assigned to a value field which was never assigned to any conditions. Now this KE4I config is moved to test system and I found that values of these conditions are not appearing under new value field.
Earlier these new conditions were assigned to old value field and those were coming correctly in billing doc. Still these conditions values are appearing under that old value field.
Am I missing any step ? Please help
Raj

HI,
Billing document value flow is as per KE4I mapping to value fields.
There are some value flow analysis tools under CO-PA to check your settings with respect to value flows. Use transaction KE4ST (Simulate billing document transfer -> Value flow (<Ctrl +F7>) to check where things went wrong.
Hope this helps.

COPA Value Field +/- Error while releasing Billing Document for Return orde

Hi,
We have done Sale Order - PGI - Delivery and Billing for Quantity 10 and the customer returned 10 Qty due to some problem.
When i am doing the return process billing, I am getting the below error...
9000000892 000000 Check value field assignment for condition SGL1*
When condition "OR01" (application "V") was transferred to the value field "ERLOS" in operating concern "OR01" in
Profitability Analysis, the following became apparent:
o   The condition can take both positive and negative
    values
o   The flag "Transfer values with +/- signs" has not be
    set in Customizing for value field assignment.
Inconsistencies in the data could occur as a consequence.
Can any body help me on this issue
Is there any consequences if i activate +/- sign in KE4I for the above value field Please suggest me
Thanks
KC

Hi Kischow
You shud tick the +/- indicator only if
1. any One condition type repeats in the pricing procedure and can have +ve and -ve values
2. Two cond types in pricing procedures are assigned to same Value Field and the cond types can have +ve and -ve values
In COPA, all values are transferred as absolute values without + or - sign, with some exceptions ofcourse....
So, if you dont check + / - indicator in the cases mentioned above, say, +100 and -80 will be transferred as 100and 80 and the result will be 180 instead of 20
Regards
Ajay M

Value Field in PA Document

Hi,
We are seeing a difference while doing an automatic posting and manual posting of an GL transaction.
After posting a document, going to T.code:FB03 giving the document number and looking into the document and from there going to Environment>Document environment>Accounting document-->Selecting (Profitability analysis document)
Here when the CO-PA document opens in tab 2- Value fields on the bottom we have Foreign currency/operating currency/local currency.
What is exactly happening here is when we post documents manually in foreign currency it is still showing as Local currency. But something interesting is when the documents are automatically posted it is showing foreign currency.
I hope there is something maintained in derivation rule. Please help me to solve this query...
Thanks in advance

any suggestions please...

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.

Only on value field in COPA gets values from SD

Hi,
I created two value fields for COPA. I assigned one of them to the condition VPRS (a cost) which works properly. The other condition, assigned, VKP0 doesnt appear in the COPA-document. We are using record type F.
But when I ran an flow analysis I can see that the value from VKP0 has flown to COPA in record type A?
I will assign point directly to a working solution.
Best regards
Carl-Johan

HI,
Billing document value flow is as per KE4I mapping to value fields.
There are some value flow analysis tools under CO-PA to check your settings with respect to value flows. Use transaction KE4ST (Simulate billing document transfer -> Value flow (<Ctrl +F7>) to check where things went wrong.
Hope this helps.

Value Fields assignment. urgent!!!!!

< MODERATOR: Message locked. Please read the [Rules of Engagement|https://www.sdn.sap.com/irj/sdn/wiki?path=/display/home/rulesofEngagement] before posting next time. >
hi gurus,
we use costing based COPA. i have created a new value field and assign it to a SD condition. but when billing, there is error, i check the system and found this value field has been actived but can not displayed in my operating concern. i want to transfer the value field to operating data structure with T-code KEA0. but failed. because it is actived in the column "Copy from". it is in our production system. very urgent. the following is the error message.
Operating concern 6000 does not contain value field VV150
Message no. KE891
Diagnosis
Value field VV150 is not found in operating concern 6000. This value field is nevertheless assigned to condition type ZD69.
System Response
The billing document cannot be posted to Profitability Analysis.
Procedure
Delete the assignment to condition type ZD69 for operating concern 6000. You do this in Customizing for Profitability Analysis underFlows of Actual Values -> Transfer of Billing Documents -> Assign Value Fields.
your valuable point will be assigned.
thanks in advance.
Ivan

You have to declare the l_lotno and l_batno as global variables.
here they are local variables and their scope is withing the block in which they are defined.
Declare them outside the blocks(Performs etc)
Regards,
Ravi

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

Remove Value Field from Operating Concern

Hi all,
I created a new value field in DEV and assigned it to the corresponding Operating Concern.
Now, after some discussions, it is not necessary this value field.
I want to "un-assign" from the Operating Concern they use.
No data is being posted to this value field and nothing has been transported to QA yet.
Is this possible? Any ideas?
Thanks and Regards,
Flower.

I guess you can delete the value field as it was not transported to QA and PRD.
Here is some information given by SAP.
Deleting characteristics/value fields from an operating concern
You can delete characteristics and value fields retrospectively from an operating concern that you have already activated. However, you should only use this deletion function for operating concerns that have not yet been used productively. You should also note that some database systems require the operating concern tables to be converted (database conversion) after the deletion has taken place if data had already been posted to the operating concern. Depending on the data volumes involved, the database conversion can take a matter of seconds or indeed several hours. Moreover, you cannot post data or run reports during the conversion. Due to integration, other applications are also affected when data is postedwith an assignment to profitability segments (such as settlement and direct assignment from FI/MM). If the operating concern has been transported to another system (such as the productive system), then the database conversion must also occur in that target system.
Depending on the fields that were deleted, the following tables need to be converted (where xxxx = operating concern):
Characteristics: CE1xxxx, CE2xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Amount fields: CE1xxxx, CE2xxxx and CE3xxxx
Quantity fields: CE1xxxx, CE2xxxx, CE3xxxx, CE4xxxx, CE4xxxx_ACCT, CE4xxxx_ACCT, CE4xxxx_FLAG, and CE4xxxx_KENC
Before deleting fields from an operating concern with a large data volume (more that 10 000 records in a table), you should refer to the section "The Database Utility" in the ABAP dictionary documentation. This section describes the database conversion process.
For database systems that do not require conversion (such as DB2 for AS/400, Informix, MSSQL), it can still take a considerable amount of time for the operating concern to be activated.
To delete characteristics or value fields, 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. 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.
If you want to transport the operating concern into a different system, see the section "Notes on transport"
Note
Hope this helps
Thanks,
Reddy
Edited by: reddy sap on Sep 11, 2009 6:58 PM
Edited by: reddy sap on Sep 11, 2009 7:00 PM

KE30 - UOM Value Field required

Hi,
We have some FG Materials which are sold in PAC and EA. and PAC is Base Unit of Measure while EA is Alternative Unit of Measure.
In PA Report - KE30, system is accurately showing Sales Quantity but business wants to see UOM of Sales Quantity as well, means they want to see how much of same material is sold in EA and PAC. I have created customized Value Field (VVXXX) for UOM but my issue is how can i derive Base Unit of Measure and Alternative Unit of Measure to this Value Field as i need to see this in PA Report. I have checked T-Code : KEDR but i am not able to map value field there.
Kindly guide steps to solve this problem !!!
Thanks in Advance
Regards,
Sapna

I assume you have defined (at least) 3 quantity value fields in the operating concern. (The value fields shown below can be named as per your convention and may differ from these.)
VVIQT - Invoiced Quantity (in sales unit of measure) --> PAC or EA
VVPAC - PAC Quantity (base unit of measure = stock keeping unit)
VVEAQ - EA Quantity
The first two fields above are easily mapped in customizing transaction KE4MI via path:
SPRO > Controlling > Profitability Analysis > Flow of Actual Values > Transfer of Billing Documents > Assign Quantity Fields
Assign the following:
SD Qty Field     Name                       CO-PA Qty Field        Name
FKIMG              Billed Quantity          VVIQT                       Invoiced Quantity
FKLMG             Billing Qty in SKU     VVPAC                     PAC Quantity
To derive the third field try using customizing transaction KE4MS via path:
SPRO > Controlling > Profitability Analysis > Flow of Actual Values > Initial Steps > Store Quantities in CO-PA Standard Units of Measure
Assign the following:
Source Quantity      Description          Quantity     Description      Unit
VVPAC                    PAC Quantity      VVEAQ      EA Quantity     EA
The above option is to derive standard units of measure, such as KG. I'm not 100% certain it will work in your requirement to access the alternative units of measure conversion rates for a material (table MARM). If this configuration does not derive the EA quantity and units as expected, then the user exit mentioned previously can be used to fill the fields with the converted amount and unit.
Best regards,
Jeffrey Holdeman
SAP Labs, LLC

Condition types and value fields

hi Gurus,
Can anybody please explain me what is condidion type and value field and the purpose of these two in costing??
Regards,
S.Sumana

Dear Sumana,
Condition types and Value field conjuction is used in Profitability Analysis.
Condition type is an element in pricing procedure. For e.g price of the product consist of several things like base price, discount, tax, etc. so each compenent is called condition type.
Value fields are grouping of cost elements for e.g. you have created a cost element Sales revenue then all revenue cost elements which consist of revenue.
Condtion type Base Price is revenue which is mapped to value field Sales revenue. So as soon as the billing document is created value field is updated.
For more information on Profitability analysis please read the documentation provide in www.help.sap.com
Regards,
Chintan Joshi.

Value Field Analysis

Similar Messages

Maybe you are looking for