Field catalog in Profitability Analysis

Hi,
In profitability analysis, if we want to use a particular characteristic or value field, then they should be maintained in field catalog.
Could anyone please explain me where we will define this field catalog.
Thanks
Chandra

You need to create the Characteristics and/or Value Fields using transaciton KEA5 / KEA6
Once this is done, assign these to the Operating Concern using transaction KEA0
In this transaction, enter the Operating Concern you need to modify, and then enter the Data Structure in the Data Structure tab. Assign the Characteristics / VFs in this screen (click on the respective tab to access the assignment). Once done, remember to generate the Operating Concern.
If you exit the maintenance screen on saving, the system normally prompts you to Generate the Op Co. Once this is generated, you can use these in your config./ analysis.
Cheers.

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

  • Problem filling Arch infostructure for COPA2_S001 - field catalog?

    I'm not sure I'm posting this ti the correct forum, but I'll give it a try.
    Archivingobject COPA2_S001 is used to archive Copa data (account based CoPa). As the profitability analysis archiving objects depend on the operating concern (generated by the customer), and must also be generated, no appropriate information structures or field catalogs can be delivered as standard with the Archive Information System (SAP AS). You must create these yourself.
    This was set up by somenone in the pst, but the Infostructue (the table cretaed for it) stays empty.
    The Infostructure is activated, the archiving process shows no errors and even the status info from the AIS shows only green lights!
    My guess that the field catalog which was set up is not correct.
    Can anyone give my some info how to be sure what the cause, how to solve it and how to fill the AIS without starting a new archiving run.
    Thanks in advance!
    Ger

    Sorry misread the message.
    Kind regards,
    Robert Loeffen
    Message was edited by:
            M. van Lieshout

  • Runtime error in Field catalog creation

    when i try to create the field catalog using the following code.
    am getting *'Field Symbol Is not assigned' Runtime error.*
    Please give me idea how to resolve this issue.
    data: wa_field type slis_fieldcat_alv,
            t_field type slis_t_fieldcat_alv.
    LOOP AT t_role INTO wa_role.
        wa_field-col_pos = count1.
        wa_field-fieldname = wa_role-agr_name.
        wa_field-datatype = 'CHAR'.
        wa_field-ref_fieldname = 'AGR_NAME'.
        wa_field-ref_tabname = 'AGR_1251'.
        APPEND wa_field TO t_field.
        count1 = count1 + 1.
      ENDLOOP.
    Suitable  Answers rewarded with maximum points....
    it's Urgent...
    Give me Quick Reply.

    Error is having following short text.
    Field symbol has not yet been assigned.
    Error analysis                                                            
        You attempted to access an unassigned field symbol                    
        (data segment 92).                                                                               
    This error may occur for any of the following reasons:                
        - You address a typed field symbol before it is set using ASSIGN      
        - You address a field symbol that points to a line in an internal table
          that has been deleted                                               
        - You address a field symbol that had previously been reset using     
          UNASSIGN, or that pointed to a local field that no longer exists    
        - You address a global function interface parameter, even             
          though the relevant function module is not active,                  
          that is it is not in the list of active calls. You can get the list 
          of active calls from the this short dump.                           
    Please tell me how to correct this error.
    It is very Urgent..

  • Profitability Analysis not generated in Contract billing Document

    I have created the Billing document against the contract order but the Profitability Analysis is not getting generated.  But any sale order related billing document is created; system automatically creates the Profitability Analysis.
    Can you tell me where the problem is or have I missed any steps?
    Regards,
    Devendra

    1) For a service material (DIEN), We are creating an Sales Order (VA01) and doing a order based billing (VF01). In the Sales Order we are giving the plant (no shipping point and storage location as it is a DIEN material).
    Once we do the billing we are able to see the Profitability Analysis document.
    2) Now we are using the same material we are creating a Contract (VA41) for a period of one year and doing a monthly billing. In this case we are using VF04 for doing the bills that are due.
    We are getting two results in this:
    a) If we give a Plant in the contract, the Profitability Analysis document is not getting generated at the time of billing.
    b) If we do not give any plant, the Profitability Analysis document is getting generated at the time of billing.
    Please note that we are using the same material, same pricing procedure in both the above cases 1) and 2). Only difference is that the source documents are different i.e., one is Sales Order and the other one is Contract.
    In our copa valuation we have assigned the conditions to value field, no derivation rule assigned.
    Regards
    Devendra
    Edited by: Devendrap on Apr 14, 2009 10:38 AM

  • COPA Values in the Profitability analysis for a credit memo request

    Hi All,
    When I am trying to create an Invoice document for a Credit Memo request having a Configurable material , in the accounting document profitable analysis Profit Center view fields are not getting updated.
    If we do the same thing for a reference material profit center view fields are getting updated properly.
    What is the problem with the Configurable  material.
    Thanks in advance,
    RajaMahi

    I would start fresh with a new sales order.  When you create with reference both the return delivery and credit memo are created with reference to the return sales order.  Here is an example document flow to clarify:
    Document                                      Date               Qty/value   UoM/Cur   Overall proc. status
                                                                                    Return 60000077 / 10                          08/25/05               10.000  EA      Completed                                 
    . Returns Delivery 500000016 / 10             08/25/05               10.000  EA      Completed                                 
    .. GD returns QI 4900030060 / 1               08/25/05               10.000  EA      complete                                  
    .. Credit for Returns1 10000017 / 10          08/25/05               10.000  EA      Completed                                 
    ... Accounting document 10000017              08/25/05               10.000  EA      Cleared

  • Price condition creation & fields catalog update

    Hello all SAP experts,
    I am trying to create a pricing condition that will be applied in stock transport order based on shipping conditions. Depending on the shipping conditions used in the STO, the amount of this condition will change.
    The thing is, I cannot get it to work.
    <b>What I did:</b>
      - created a new condition type
      - included this condition in the current calculation schema
      - added the shipping condition field (VSBED) in the field catalog for condition tables (it was not in standard field list)
      - created a condition table with the shipping condition field embedded
      - created an access sequence with reference to the above condition table
      - linked the access sequence to the condition
      - created a few condition records for the new condition type
    <b>Result:</b>
    When creating a STO, the system tries to populate but it is not working. When I look at the price deter;ination analysis, the system that the value of the shipping condition was not found, though it is defined in the STO.
    <b>One step further</b>
    I tried to change several things, but it isn't working. Looking at the access sequence, I noticed that the field for shipping conditions (VSBED) was stored in an internal document structure valid for document header (so-called 'KOMK' in the document structure column). I am a bit surprised because the system should look for the information at item level, not at header level. I tried to change the value to 'KOMP' (item level), but I don't know how to do it.
    I realize my post is a bit lon and might get a bit confusing, but would you have any hint / idea on how to retrive the shipping conditions infomation properly?
    Any info highly appreciated!
    Thanks in advance,
    Morgan

    Please go through the steps below
    - created a new condition type
    This is file
    - included this condition in the current calculation schema
    this is fine
    - added the shipping condition field (VSBED) in the field catalog for condition tables (it was not in standard field list)
    This is fine
    - created a condition table with the shipping condition field embedded
    make sure the table is created properly
    - created an access sequence with reference to the above condition table
    Make sure the access sequence is created based on the way you want to defualt the condition in PO
    like if you access seq should contian
    e.g. your criteria is suppose STO type ST and vendor X and shipping condition is 01 then insert that condition in the PO
    - linked the access sequence to the condition
    check the access sequence in the condition record bu hitting Record for Access and here you should able see the value as per the criteria
    - created a few condition records for the new condition type
    This is fine
    Now check you calculation schema that this condition should not checked as Manual determination in schema.
    Hope this will help you to resolve ur problems

  • VF03 Profitability Analysis - Cost not capture in profitability

    HI SAPFans,
    I'm facing difficulty on profitability analysis on VF03.
    The problem is, my cost of sales is not capture on Value fields tab (refer attachment).
    [vf03|[IMG]http://i303.photobucket.com/albums/nn133/kerisnagasostro/vf03.jpg[/IMG]]
    is there any maintenance that i need to check ? in order to flow cost amount into cost field on value fields tab ?

    Dear
           GOTO CONTROLLING Profitibility Analysis ---Flow of Acual Value --Transfer of Billing document --Assign value field --Maintain assignment of SD Condition to COPA -- OPERATING CONCERN(TYPE OF PROFITB ANALYSIS--SELECT COSTING BASED) AND CLICK. issue may arise to do this activity as that is FI Consultant job so u might not having require Authorization so need to take help of ur FI Consultant or asked ur Basis Consultant to give authoriztion.
    Regards
    AJIT K SINGH

  • Account Based Profitability Analysis

    Hi,
    I am mapping characteristic fields of account based profitability analysis. I have been given fields such as KMLAND to map into BI fields.My question is how do i map the key figures. What fields in account based profitability analysis are key figures, are they value fields? Do i need a list field names of value fields to map it into BI.Some one mentioned something about cost elements.
    Thanks
    TJ

    Hello Tee Jay,
    Cost Element is a key field in ECC. That means its char. in BW. What are the infoobjects that you have in your DSO or cube n BI.
    Do you have 0COSTELMNT or 0GL_ACCOUNT? If so, then you map Cost element field from SAP to one of the above char. in BW.
    By Revenue, do you mean a value field in R/3? If so, it will have to be mapped to key figure in BI.
    Hope that helps.

  • Characteristic Derivation in Profitability Analysis

    Dear Experts,
    I am finding it bit difficult to understand the concept fully when it comes to the Characteristic Derivation in Profitability Analysis.
    I had gone through the various SAP explanations of MOVE, LOOK UP, ENHANCEMENT, DERIVATION RULEu2026. And now I am having rough understanding of all of it. But I am finding it difficult to understand on how these various steps or rule impact the COPA output. In other words if someone can explain the usage of all the MOVE, LOOK UP, ENHANCEMENT, DERIVATION RULE steps with an example?
    Thanks in advance
    Paul

    Hello Paul,
    Its purely clients decision/requirements  which determine whether derivation is required or not.  But in all COPA implemenation you need at least couple of derivations.
    I will explain a simple scenario for Table Look up. Suppose you are settling production orders linked to a sales order ( Make to order scenario).
    When the production order settles variances to COPA, system will not transfer Customer ( sold to party) characteristics.
    But you can tweak the system through a small derivation rule to bring the customer from sales order and pass it to COPA when production order is settled.
    For table look up first you have to identify the table, here our reference is sales order (VBAP-VBELN) and the required field is sold to party (VBAP-KUNNR), both are in VBAK
    In the source field for table look up
    VBAP- VBELN =  CO-PA- KAUFN ( means if sales order number from VBAP table is same as the COPA sales order number)
    VBAK-KUNNR= CO-PA-KDNR  ( then pull the customer number associated with that sales order and populate the COPA customer field)
    Please carefully go through SAP help for derivation, it is clearly explained with simple examples
    http://help.sap.com/saphelp_46c/helpdata/en/7a/4c37ef4a0111d1894c0000e829fbbd/frameset.htm
    thanks
    SAP FREAK

  • Customizing Monitor in Profitability Analysis

    Hello SAP-team!
    What functions are provided by the Customizing Monitor in Profitability Analysis?
    ps: thanks to SAP-community!
    Eugene

    Hi,
    Customizing monitor in Profitability analysis as follows..
    General topics:
    35288 Technical Documentation CO-PA
    69384 Account-based Profitability Analysis
    199467 New act assignment table as of Release 4.5
    2. Master data:
    a) Characteristics and value fields:
    13377 Naming conflicts in characteristics and value fields
    21207 Deleting a charctrstc/value field from an op.concern
    40336 Maintaining foreign keys for characteristics
    76493 Changing texts of characteristics or value fields
    b) Characteristics derivation and submission of characteristics values
    32719 Customer hierarchy in CO-PA
    33968 SD/CO-PA: Characteristics from sales document tables
    36557 SD/CO-PA: Transfer partner functions to CO-PA
    62690 Product hierarchy in CO-PA
    93652 Info: Variant configuration in CO-PA
    134889 Info on derv. of char:Why not all flds avail.?
    148609 Char.deriv.:deriv. rule vals miss.aft.upgrade&trnsp.
    172740 Techn.docum.charct. derivtn as of Release 4.0
    c) Valuation
    40408 Valuation for record types 'B' and 'C'
    62536 Valuation using conditions in Profitability Analysis
    67240 Info: Valuation with material cost estimate
    111232 INFO: Valuation for materials valuated separately
    144337 INFO rounding differences: Valuation with costing
    142628 Behaviour of user exit in periodic valuation
    3. Actual data transfer:
    20254 Values from SD are not transferred to CO-PA
    37114 Incorrect setup/reversal of provisions
    33178 +/- sign logic in CO-PA (SD/FI interface)
    52849 Transfer of conditions with +/- signs
    39635 Profitability segment by substitution exits
    64768 FI/CO-PA: Problems with exchange rate differences
    87704 Cost-of-goods-sold Reconciliation: FI to Co-PA
    83702 Acct assignmt logic sales order proc. - REM
    111309 Transfer of quantities into CO-PA
    185826 Enhancement COPA0005
    a) Correction of data inconsistencies
    69370 Clearing data inconsistencies in CO-PA
    70718 Correctn of data inconsistency for order recpt
    140457 Correcting data inconsstncs in incoming orders
    126937 Correction of billing data inconsistency
    93051 Restructure of the segment level from line items
    4. Planning:
    67191 Useful tips on the CO Planning Processor
    72110 KE11: Long runtimes/timeout
    77476 Information: Top-down planning
    124598 CO-PA Planning: FAQs
    5. Information system:
    21773 Performance in reporting (summarization data)
    83204 Usage strategy for summarization levels
    136216 Fast rollup for summ. levels for costing-based CO-PA
    6. Tools:
    134430 Euro conversion and CO-PA
    19015 Termination during external data transfer
    19410 Characteristic validation during external data transfer
    44658 Error with batch input for KE21
    40994 Transport Profitability Analysis (CO-PA) to 3.0
    52636 CO-PA Customizing transport
    128862 Transport Customizing CO-PA in 4.0A/B
    131664 Transport of operating concern structures 4.0
    144015 Client copy and CO-PA/EC-EIS
    65999 Information: Supported ALE scenarios in CO-PA
    94458 CO-PA Realignments: documentation
    113050 Segment table repair after realignments
    127334 Missing archiving of profitability segments
    199959 Change assignmt for operating concern
    67839 Generating parts of an operating concern environment
    69829 Delete operating concern in Release 3.0
    106314 Delete operating concern in Release 3.1
    562043 - Transfer actual costs to Profitability Analysis
    544241 - INFO:Customizing Monitor new fnc 'Report Overview'.
    429517 - INFO: Currency translation Billing document -> CO-PA
    428563 - Material cost estimate valuatn: Translaton for posting date
    400237 - CO-PA INFORMATION: Line item in company code currency
    199959 - Information: change assignmt for operating concern
    199467 - Info: New act assignment table as of Release 4.5
    185826 - Information: Enhancement COPA0005
    172740 - Info.:Techn.docum.charct.derivtn as of Release 4.0
    148609 - Char.deriv.:deriv.rule vals miss.aft.upgrade&trnsp.
    144337 - INFO rounding differences: valuation with costing
    144015 - CC-INFO: client copy and CO-PA/EC-EIS
    142628 - Behaviour of user exit in periodic valuation
    140457 - Info:Correcting data inconsstncs in incoming orders
    136216 - Fast rollup for summ.levels for costing-based CO-PA
    134889 - CO-PA Info on derv.of char:Why not all flds avail.?
    134430 - Information: Euro conversion and CO-PA
    131664 - INFO: Transport of operating concern structures 4.0
    128862 - INFO: Transport Customizing CO-PA in 4.0A/B
    127334 - Missing archiving of profitability segments
    126937 - INFO: Correction of billing data inconsistency
    124598 - Info: CO-PA planning: frequently asked questions
    113050 - Segment table repair after realignments
    111309 - INFO: Transfer of quantities into CO-PA
    111232 - INFO: Valuation for materials valuated separately
    106314 - Delete operating concern in Release 3.1
    94458 - CO-PA Realignments: documentation
    93652 - Info: Variant configuration in CO-PA
    93051 - Restructuring the segment level from line items
    83702 - INFO: Acct assignmt logic sales order proc. - REM
    83204 - Usage strategy for summarization levels
    77476 - Information: top-down planning
    76493 - Changing texts of characteristics or value fields
    75334 - INFO:Downloading CO-PA correctn package fm SAPSERV
    72110 - KE11: Long processing times / timeout
    70718 - INFO:Correctn of data inconsistency for order recpt
    69829 - Delete operating concern in Release 3.0
    69384 - Information: Account-based Profitability Analysis
    69370 - INFO: Clearing data inconsistencies in CO-PA
    67839 - Generating parts of an operating concern environment
    67240 - Info: valuation with material cost estimate
    67191 - Info: Useful tips on the CO Planning Processor
    65999 - Information: Supported ALE scenarios in CO-PA
    64768 - FI/CO-PA: Problems with exchange rate differences
    62690 - Info: product hierarchy in CO-PA
    62536 - Info: Conditions in Profitability Analysis
    52849 - INFO: Transfer of conditions with +/- signs
    52636 - INFO: CO-PA Customizing transport
    44658 - Error with batch input for KE21
    40994 - INFO:Transprt Profitability Analysis (CO-PA) to 3.0
    40408 - Info: Valuation for record types "B" and "C"
    40336 - Info: maintaining foreign keys for characteristics
    39635 - Info: finding the profitability segment using a substitution
    37114 - Incorrect setup/reversal of provisions
    36557 - Info SD/CO-PA:transfer partner functions to CO-PA
    35288 - Profitability Analysis: Technical Documentation
    33968 - SD/CO-PA: Characteristics from sales doc tables
    33178 - INFO: +/- sign logic in CO-PA (SD/FI interface)
    32719 - INFO: Customer hierarchy in CO-PA
    21773 - Performance in Reporting (Summarization data)
    21207 - Deleting a charctrstc/value field from an op.concern
    20254 - INFO: Values from SD not transferred to CO-PA
    19410 - INFO: Char.validity check f.external data transfer
    19015 - Termination during external data transfer
    13377 - INFO: Naming conflicts in charactrst. & value flds.
    Thanks
    Prasada

  • Costs of the product calculation lack in the profitability analysis

    Hello there,
    A group of students and I are currently working on a SAP project which is about to implement a full cost accounting in the SAP system (ERP). At first we used a case study reading (Friedl,Hilz,Pedell), some important components for calculating the products like u201Ccosting sheetu201D, u201Ccost component structureu201D and u201Ccosting variantu201D do exist already.
    For our project we had to insert an additional primary cost center. For that reason we also added new components (the above given ones). After that the costs for our products could be calculated in the right way. We also booked supplies and stated the quantity of sales. Our problem is that the Profitability Analysis (CO-PA) does not show any costs of our cost centers (material input, manufacturing costs, overhead costs) only the earnings. We did not add any u201Cattributesu201D, u201Cderivation rulesu201D or u201Cvalue fieldsu201D but fulfilled all requirements in the Customizing menu (u201CAssign costing key to productu201D, u201CAssign costing key to productu201D, u201CAssign value fields for cost component structureu201D).
    The first time when we used the case study reading and therefore another company code everything worked fine. We think that the problem might be that the costing key is not attached to the products.
    Thank you for any help and suggestions,
    Kind regards!

    In the same area as where you assign the costing key to the product, there is also an entry where you need to define the costing key. You don'tr mention that you have done that.
    In the user menu for Profitability Analysis, there are also a lot of tcodes that will help you investigate the flows of values and derivation of characteristics. They are very helpful in most cases.

  • How to Calculate Profitability Analysis ?

    Hi
    kishore
    This is basically a part of Sales and Distribution Module . can u just revert me back with the Answer .
    Regards
    kishore

    Dear kishore
    Profitability Analysis (CO-PA) enables you to evaluate market segments, which can be classified according to products, customers, orders or any combination of these, or strategic business units, such as sales organizations or business areas, with respect to your company's profit or contribution margin.
    The aim of the system is to provide your sales, marketing, product management and corporate planning departments with information to support internal accounting and decision-making.
    Two forms of Profitability Analysis are supported: costing-based and account-based.
    Costing-based Profitability Analysis is the form of profitability analysis that groups costs and revenues according to value fields and costing-based valuation approaches, both of which you can define yourself. It guarantees you access at all times to a complete, short-term profitability report.
    Account-based Profitability Analysis is a form of profitability analysis organized in accounts and using an account-based valuation approach. The distinguishing characteristic of this form is its use of cost and revenue elements. It provides you with a profitability report that is permanently reconciled with financial accounting.
    Thanks
    G. Lakshmipathi

  • 50 Fixed CO-PA Profitability Analysis Elements

    We are in the blueprint stage of a new SAP implementation using the Life Sciences express solution.  Our consultants advised us that there are 50 SAP fixed characteristics in CO-PA for Profitablity Analysis and we have the ability to add up to 50 non-fixed characteristics.  The list of the 50 fixed characteristics that our consulting team provided to us appeared very strange.  Many of them appear to related to the airline industry.  For example:
    KMATYP - Aircraft type
    KMDEST - Desitnation
    KMFLTN - Flight number
    KMFLTY - Flight type
    KMIATA - IATA season
    KMOPDY - Day of operation
    KMORIG - Departure location
    KMLEGS - Route segment
    After questioning the provided list, we have been assured that we have been provided is the correct list of 50 fixed characteristics for all SAP implementations.  We are looking for validation that these value are indeed part of the correct list.  If not, we would greatly appreciate receiving the correct full list.
    Thank you,
    Carrie

    Hi Carrie,
    I vaguely remember that CO-PA (Profitability Analysis) module was initially developed/used for Airline industry to analyze the contribution margins. I'm not 100% sure on this, think i read it somewhere. SAP has provided these characteristics and derivation rules (logic to derive the characteristic for a transaction) by default. In my experience, i have always seen clients using at least 10-20 custom fields in CO-PA, since these are client specific we need to create additional derivation rules (either table lookup/Move/Derivation rules/Enhancements). Fields from Material master and customer master tables are commonly used for analysis in CO-PA.
    Best Regards,
    Venkata Ganesh Perumalla

Maybe you are looking for

  • Report Designer : Data Provider & Report Section .

    Hi Experts , Is it a mandatory compulsion to insert data provider to create a formatted report in Report designer . can we not create it through report section. thanks & regards , M.S

  • Query on OBYC  Transaction key

    Dear Experts , I have a few queries regarding automatic postings : 1.What process triggers the transaction key AUM ? what type of account should be assigned here ? 2.What process triggers the transaction key BSV? what type of account should be assign

  • Do not use tpc 2106T for custom animation Purpose

    I was trying to use TPC2106T for developing a MMI for an application.To my surprise the Labview in built functions for creating custom animations (eg ring control)  does not work for TPC2106T .I had been told this is to do with Windows CE OS (which i

  • Adding author bio and image to blog posts

    I can see tags {tag_blogpostauthorpicture}{tag_blogpostauthorbiography} but no where to add this information to the system.  I have tried adding the author (who is an admin) to the CRM and adding the information there. But I am just getting a place h

  • Database Cleanup

    Hello Team: I maintain and manage a 5 regional databases which are by design a look alike. In reality it is not the case. I am assigned this project to make sure that these databases are in sync. Each database has atleast 8 application schemas that n