Statistical and value field

hi,
i would like to seek advice on below.
1) when say post statistically, like "A profit center is always posted to statistically", it means no FI accounting document generated?
so statistical means no fi accounting document generated?
2) profit segment is value field or combination of characteristic value?
    combinations of characteristic values example: product X sales to customer A in the eastern region
    value field like revenues, costs.
3) what is the difference for characteristic and characteristic value?
thanks

1) For postings in external accounting that use a cost element as the account you need to use a special account assignment logic. This enables the SAP system to ensure that data is reconcilable with all the relevant application components. so if there is no posting in fi how do you reconcile the external posting to fi.
2) Profit segment is a combination of characteristic
     Eg: Characteristics : Sales organization, region, product, customer group
     Value fields: Revenue, sales deductions, costs and quantities
3) Segments of your organization for which you want to analyze your data in CO-PA. Eg: Plant/Division/Material/Customer/Product.
In the above example as mentioned by you product, customer, region would become characteristics. In other words  you are analyzing data on this segments so they become characteristics.
Value fields: what things you would take in consideration to get the data for the characteristics would become value fields.
Eg: In the above example you are trying to find how the product x sales is to a particular customer A . So in other to find values you would take what are actual sales for that product , any deductions etc so these would become value fields.

Similar Messages

  • 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

  • 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.

  • Settle Production Variances to COPA- Cost elements and Value fields

    Dear All,
    I know this question has been discussed in the past, but I have one specific doubt regarding this topic.:
    When assigning cost elements to variance categories in t-code KEI1, how do we figure out what combination of cost elements (in the top half of the screen) constitute Input Price Variance, Scrap variance etc (in the bottom half of the screen)? I know the net of the postings on those cost elements tells us what variances we are looking it, but how do we get the cost elements (group) for let's say, 'Input/Output Quanity Varinace or 'Lot size Variance' ?
    Or is this a futile exercise? May be I should just create three types of variances: Labor, Machine and Overhead. And I know what cost elements (net of the postings) would, in total, make up the $ variance in each of those categories. I can then use them in my report painter reports.
    Please help clear the fog for me.
    Ajay?
    Thanks a lot,
    Deepak

    Hi Deepak,
    Welcome to SDN!!
    There are 2 ways of updating variances in COPA... I Prefer the 2nd option always...
    1. Category wise variances (Input Prc, Usage var, etc) - Here, create a Cost ele group, where in you include all the Cost elements that can be posted to the Prod orders
    For the sake of simplicity, you can include Cost elements 1 to 99999999 in the Cost element group...
    2. Cost Comp Structure wise variances -
    a. Create as many assignment lines in PA Trf Structure as in your Cost Comp Str...
    Eg: If your Cost Comp Str in OKTZ has Raw Mat, Labor, Overhead - Create 3 Assignments in PA Trf Structure..
    b. Assign the same cost elements in the SOURCE as in the Cost Comp Str
    c. Choose the radio button "Costs/Revenues" in your assignment line, instead of " Variance on Production orders"
    d. Assign each Assignment line to a separate Value Field
    br, Ajay M

  • Adding new characteristics and value fields in COPA

    I have recently added several new characteristics and one new value field to the operating concern in the development system.
    I am not exactly sure how to create the transport.  This is the first time I have done a transport in COPA so I was hoping someone out there would have some tips on how this is done.
    Also any helpful tips with transporting this type of change is much appreciated.
    Thanks,
    Laurie Hensiek

    Refer to the documentation at http://help.sap.com/saphelp_46c/helpdata/en/c6/f22c7dd435d1118b3f0060b03ca329/frameset.htm
    This is under the node Tools>production startup>transport.

  • Create characteristic and value field in kea0

    Hi there,
    I am writing a doc about above mentioned subject and wondering if somebody can inform me, if there are certain standard points I have to considerate like,  for e.g. regenerate the system?
    Thanks,
    K.

    Hi Kristina,
    Creation of COPA data structure must be defined very carefully. Please note that adding value fields and CHARs are very easy in COPA but removing them is just near to impossible. Also you must remember that there is a limit of Max 120 value fields and 50 Characteristics in standard SAP. You can check note 160892 in case you want to increase the limit. The other thing you should take into account is it should be possible to regenerate the operating concern in KEA0 before and after the changes to the data structure. COPA will not generate any transport request for these changes automatically so you need to transport them viw transaction KE3I. In case you have added a new Characteristics and you want to update the historical data as well you should take help of reallignment (KEND). For value fields you need to repost the documents through KE4S, KE4ST, KE4SFI and KE4SMM.
    I have tried to give some details if you need more information please let me know.
    Regards,
    Abhisek

  • Q54: Cumulative quantity and value fields

    Hi All,
    Thanks for all previous help in getting me up and running but now I have a new challenge...........
    Which table(s) can I find the fields for Cumulative Qty and Cumulative Value as reported in the Stock Audit Report?
    Regards,
    Robin

    Hi Robin,
    There is no fields in any tables hold those cumulative quantity and values. Those values are calculated on the fly by program. You can reproduce them easily through an excel formula to verify.
    Thanks,
    Gordon

  • New Value Field

    Dear Friends,
    We are planning to add new value field in current copa structure, for this I need know :
    1. As soon as we add new value field current operation conern gets deactivated ?
    2. If there is only one server for development and production then as soon as we create value filed in development, what would be the impcat in production client ?
    3. If server is same than transport of value field is required ?
    4. If required then opernation concern shuld be re-generate after transport ?
    5. If server is same then operating concern has to be regenerated in every client ? i.e. dev, testing, preprod, prod.
    and what ever impact would be in this case and also if we have different server for dev nad product. Kindly let me know about you expert comment.
    If there is any risk while regenerate operating concern, also please let me know.
    Thanks
    Ravi

    Hi,
    Activation of Operating concern has two aspects- Cross client and client specific...  for your questions.. if you have operating concern in the same server it is enough if you activate only client specific one..
    On each change of u r datastructure i.e changes to characteristics and value fields u need to generate.. till then it will be in Inactive mode..
    In terms of different systems generally u can transfer the active operating concern on addition of new value field.  However sometimes it may be required to activate specifically..
    Regards
    Sudhakar Reddy

  • New Value Fields in COPA

    hi
    All COPA configuration with characteristics and value fields is already transported to QAS.
    I have created three new Value fileds in DEV and want to transport in QAS?

    Use Tcode KE3I
    Select operating Concern
    Execute
    create bot customising and Wrokbench requests for that
    Select the operating concern Execute
    Select ABAP repository objects and Enter
    release the transports and Import them in QAs and you are done
    Thanks
    Naveen

  • 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

  • Custom report #value.FIELD# issue

    I've created a report using the custom report layout option. This type of report has field tags #column_name.LABEL# in the heading section and #value.FIELD# in the Body section.
    The layout of my report requires that some of the values, #value.FIELD# , be in the heading HOWEVER when I place them there they are returned literally. Values are only substitued when I place them in the Body section.
    AND
    If I place #column_name.LABEL#'s in the BODY section they are repeated for every row returned. How can I get the #value.FIELD# to return values in the HEADER section?

    Dear All,
    I have checked that for the company code which has COPA value field as zero there is no settlement posted in c088.
    For other company codes there are postings on date 30.11.2010 but for this company code there is no poating on date 31.12.2010.
    When I am executing co88 in test run its says:
    Invalid posting period (please check your entry)
    Message no. CK122
    Diagnosis
    You are attempting to update in a period that is locked against posting. This error can occur when you attempt to post to a period that is in the past.
    Procedure
    You can allow posting to the prior period in Materials Management. Choose Logistics -> Materials management -> Material master -> Other -> Post to previous period and activate this function for your company code.
    If the posting is to be neither in the current period nor in the previous period, then you cannot change any stock data (such as goods movements, purchasing postings, invoice entries, or settlement to materials) because stock data can only be updated in two periods. Possible entries:
    the current period in the material master record
    the previous period
    the last period of the previous fiscal year
    Please suggest on the reason ofl error in order settlement how can I rectify
    Regards
    Raju

  • 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?

  • 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

  • How to get the table of value field? and can we expand the technical limits

    Dear
    I have created value field in COPA with KEA6. And now, I need the table which the value fields are saved. Yet, I have tried a lot to find it and get failure? Can any guy help me? Please tell me how to get the table of a value field.
    And another question is that, can we extend the technical limits for the number of value field for ECC6.0?
    We have a note for R.4.x Please see below:
    OSS note 160892
    You can display the length of a data record using Transaction KEA0 ('Maintain Operating Concern'). After you have navigated to the 'Characteristics Screen' or to the 'Value field Screen' choose menu path 'Extras -> Technical Limits'.
    The maximum displayed here under 'Length in bytes on the DB' is the maximum length permitted by the Dictionary. The reserve required for the release upgrade must be subtracted from this value.
    To increase the allowed number of the value fields, increase the value that is assigned to field ikcge-bas_max_cnt (FORM init_ikcge_ke USING fm_subrc, approx. line 165) in Include FKCGNF20. It specifies the number of the possible value fields. The corresponding part of the source code is attached to the note as a correction.
    David Sun
    Regards!

    how to extend the limit of value numbers? please see the original question.

Maybe you are looking for