COPA - characteristics

Hello,
I was wondering, is there a way to "derive" only part of a characteristic to another characteristic in COPA. Let's say we have a product hierarchy PP123AB in one characteristic and we want to split it into 3 different characteristics:
characteristic1: PP
characteristic2: 123
characteristic3: AB
Thanks,
Anne

Table lookups let you read individual records of any table to determine characteristic values. Here the source fields must make up the key of a specific table, from which the system can copy certain contents to the target fields.
Create a custom table which shall host the product hierarchy as the key field. Have additional fields that parse the key field with selected digits to populate the remaining required fields. What I mean is like this
ZTABLE
Product Hierarchy|    Category|  BRAND| Division
PP12345ALPHA   |     PP          |  12345  | ALPHA
Developers can help you build this table. You may need to set up a business process to update this table as and when required.

Similar Messages

  • COPA Characteristics Derivation

    Hi All,
    Good day!
    I would like to seek help regarding my concern in COPA.
    We are trying to derive certain COPA characteristics but this derivation rule will only be triggered whenever we post Freight for Sales. My question is how can I technically know that the line item is from Freight for Sales? I check for the nature of a sample GL account for Freight on Sales, transaction is GBB with account modification VAX. My first idea is to set memory ID on VI01 and VI04 where in we store those transaction codes, whenever we met this tcodes, then the rule will trigger but the problem is, in the nature of the said GL account, posting will not only be in VI01 and VI04. We can also manually post it in ML81N by copying the entry sheet automatically created. Please help.
    Thanks.

    Our freight on Sales is just the standard frieght posted in VI01 or VI04, but when we discovered that amount posted is not correct, we changed it manually in ML81N via copying the original SES created upon posting in VI01 or VI04. Now what management requires is that in the profitability segments of the GL for Freight on Sales, COPA characteristics for customer should be equal to COPA Characteristics of the Trading Partner. Hope this clarifies the data you need. Thanks.
    Would like to add, yes my problem now is how will I know if postings are for Freight on Sales given the nature of the P&L account. I think I need a user exit that identify the account assignment. With that, hopefully I can make some adjustment to pass it to COPA.
    Edited by: baguado on May 11, 2011 12:52 PM

  • Need Help with populating COPA characteristics

    SAP Gurus,
    Here is the scenario,
    We have a requirement where we need to populate Reference (XBLNR) and Assignment fields (ZUONR) from Billing Document (VBRK) into COPA Characteristics.
    We have CO-PA activated to update sales order data @ time of SO creation. The current KEDR rules have been set up to get the information into CO-PA from Sales Orders (VBAK). Is it possible to do?

    Hi Mayank
    In the standard system, chars are not derived from Billing Doc, because the Biling doc no is not yet generated when COPA doc is created
    You need to make settings in Table TKEZU using the structure KOMK or KOMP (Busn Trans  = KEDR, Table KOMP-XBLNR and map it to a WWXXX Char).. However, note that TKEZU will be effective only if you redetermine PSG during Billing
    Another option is use exit COPA0001 or COPA0005 and populate the chars
    Br. Ajay M

  • COPA CHARACTERISTICS  ORT01 FROM KNA1

    Hi,
    We are using both costing based and account based copa.I have
    selected and activated the field KNA1-ORT01 from pre-defined
    characteristics .The particular characteristics is not appearing
    when i try to transfer to ORT01 to operating concern in KEA0
    Regards,
    Guru

    hi
    pls check that particular characteristic has been assigned to operating concern or not?
    Thanks & Regards
    Phaneendra

  • Delete COPA characteristics which not used in any operating concern

    Hello SAP experts,
    Please advise me on how to delete PA characteristic "WW001" created by mistake that we are hoping to delete if possible. However, when attempting to delete in KEA5, the error log appear as
    Data element RKEG_WW001 is used in these table/view
    CACS_S_COND_MA
    JVKOMP
    KOMG
    KOMGF
    KOMGFNEW
    KOMGFOLD
    KOMP
    KOMPAKE
    STR_KOMG
    TRCON_IT_KOMP
    WB2_EKOMP
    And does not allow the deletion
    WW001 have already been delete from the operating concerns.
    Please shed some light on how to do this?
    Thanks in advance for your help
    Yang

    Hi,
    In order to delete a characteristic 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.                                                                               
    It is not possible to transport information about 'deleting of             
    characteristics (value fields)' with transaction KE3I. Only                          
    characteristics and value fields included in operating concern (to be                
    transported) are transported with KE3I. Deleted characteristics and                  
    value fields are ignored. You have to delete these characteristics and               
    value fields manually in each system.    
    Best regards,
    Maria Luisa

  • Park FI Documents Using COPA Characteristics

    We have a journal entry upload program that is parking FI documents (FV50) that needs to be modified to enter COPA characteristic values.  Is there a standard function module or BAPI available for this?  We are currently using FM PRELIMINARY_POSTING_FB01.

    HI Bharat,
    The posting key of FI document is decided on the account tye (K) or (S) and also debit creadit indicator (CR/DR).
    So based  on the GL ACCOUNT number/ account type and DR/CR indicator you need to decide the posting key for the same.

  • COPA Extraction-Characteristics value not appearing in RSA3

    Hi All,
    We have developed Costing based COPA DataSource in KEB0 based on our operating concern. Included all standard fields(Characteristics from the segment  level,  Characteristics from the segment table, Characteristics from the line items, Value fields) in data source.
      When we do extract data in RSA3, All the key figure value fields are appearing correctly but I cannot see any Characteristics values. all the characteristic value  appearing blank value.
    I have checked everything is active and all (CE1 **** ,CE2 and CE4) tables have data with characteristics and value fields .
    My questions are:
      1)why COPA characteristics value are not coming in RSA3?
      2)what do I need to get this work?
       I hope it helps. let me know if you need  more further details
    Thanks,
    L.Prathap

    Hi,
    Worked on CO-PA but never got such an issue..........
    Do you have any of the chars selected from the line items section other than rec_waers?
    Also check if you have any summarization levels...transaction KEDV. If no other char from the line items are selected, data could be read from the summarization levels.
    There would be 2 tables for a summarization level...key table and the totals table. Check what chars are selected in the key table.
    http://help.sap.com/saphelp_470/helpdata/en/7a/4c40794a0111d1894c0000e829fbbd/content.htm
    Edited by: Murali Krishna K on Mar 8, 2011 3:32 PM

  • How to transfer the classification characteristics of MM to COPA?

    I have been trying to bring the classification characteristics of MM to COPA.I don't have a match for those in COPA and I am unable to get those values thru table look up from KSML, KLAH or AUSP into COPA.Could anyone please help me out.
    Thanks,
    Swapna

    Hi
    I am understanding that you want to derive COPA characteristics based on some Classification values. But what you need to understand is that the values flows to COPA from SD when you either post a Sales order or Billing Document.
    So you need to explore what classification data is available in Sales order or Billing Document for the material,  check those tables of SD only those values can be used in Derivations to derive the characteristics.
    I hope it helps.
    Regards,
    Suraj

  • COPA structure cross 50  char-How to add more char fields in the sturcture

    Hi SAP CO Guru's,
    I am facing one problem in COPA characteristics, I have created the characteristics however in the KEA0 structure where we have already exhaused max limit of 50 char, hence system is not allowing to add these new fields in the structure.
    I need help for getting addition 2 fields into structure.
    I have one more option where few Char fields are not usable, can be remove from the structure if we can not increase the limit of 50 Char in the structure but system is not allowing me th remove the already selected Char fields.
    Thanks in Advance.
    Uday Suryawanshi
    SAP FICO consultant, Pune

    Hi Uday
    There is a way you can increase the limit.. refer the note given above
    However, SAP wont take the responsibility of any thing that happens later on.. It is completely your headache....
    So, better rename the Chars and use them....
    If you are still in DEV Client, delete COPA docs posted till now.. refer Note 21207... This helps you to delete a char if posted data exists
    I personally would prefer to rename and reuse.. After all, recycling is encouraged these days
    Br, Ajay M

  • COPA - Product Hierarchy

    Dear all experts,
    My client has split the product hierarchy in COPA into 3 levels.
    For example, ProdHier01-1, ProdHier01-2 & ProdHier01-3.
    Then they use these values in COPA to further derive the detailed product characteristics.
    By looking at the questions posted in SCN, I realized that the naming convention (ProdHier01-1, etc) and setting (create characteristic with reference to MARA-PAPH1/2/3) are the same.
    So I assume this is the standard SAP way to create the prod. hierarchy in COPA.
    Now my question is,
    1) Is it necessary (or standard way) to create 3 COPA characteristics to derive each level from PAPH1/2/3?
    2) What is the purpose to create no. of COPA characteristics according to no. of product hierarchy level?
    3) Can I just create 1 COPA characteristic and map it to the full length of product hierarchy value?
    I can still derive the detailed product characteristics from this 1 COPA characteristic.
    Thanks.
    Sincerely,
    Sebastian

    Hello Madhu,
    Thanks for your reply.
    That is my main question, why do we need to update Prod.Hier1/2/3 in COPA?
    Is it the standard SAP way that's why my client just follows?
    When I check in the derivation rule, this Prod.Hier1/2/3 is later being used to derive detailed product characteristics where I am able to get it if i map 1 COPA characteristic to full length product hierarchy value.
    What is the purpose of splitting them into 3 levels if there is no other functionality of this piece of info in COPA?
    Thank you.
    Regards,
    Sebastian

  • Characterstic Derivation in COPA

    Dear Experts,
    could you please give me example and purpose of derivation rule (meaning) in COPA ie., why do we define derivation..
    your replies are highly appreciable..
    With Best Regards,
    satish

    Hi ,
    In COPA , you pull reports based on various dimensions , like product , plant , company code , region , division , product group etc... . We define these dimensions as Characteristics in COPA ..
    Now , if we have to pull data in these dimensions.. we have to make sure that all these characteristics are populated in a COPA Document ..All the characteristics are not always are available during creation of billing document ..hence we need to have a COPA Characteristics derivation strategy ..
    Strategy may be :
    Derivation of Fixed Characteristics
    Derivation from derivation rules
    Derivation from table lookups
      Derivation from customer hierarchy
    Derivation of Product Hierarchy
    Derivation of Region
    Derivation with move and clear functions
    Derivation within enhancement steps
      Derivation of quantity units
    Regards
    Sarada

  • COPA Derivation rule not running in background

    Hi all
    We are encountering a strange problem during derviation in document posting & creation of assets.
    We have added a characteristic value Material group to the profitability segment and have added a derivation rule in KEDR based on order.
    The rule is if the value of order number is filled then the material group is assigned a value.
    Order number          Assigned         Material Group
    Z0000000001              =                        001210
    The problem is that we have to manually go into the PA segment and click the derivation button OR just press enter to get the derivation working.
    If we do not access the PA segment area then the derivation is not carried out in the background.
    I have tried searching for notes and for some relevancy on the forums.
    I have also taken screen-shots and uploaded them, please view in order.
    Derivation Rule
    http://i116.photobucket.com/albums/o23/zkage/Deriv1.jpg
    Document Posting(Deriv rule not picked even order is placed)
    http://i116.photobucket.com/albums/o23/zkage/deriv2.jpg
    The PA segment before pressing enter or the button derivation
    http://i116.photobucket.com/albums/o23/zkage/deriv4.jpg
    The PA segment after pressing the button
    http://i116.photobucket.com/albums/o23/zkage/deriv3.jpg
    We require that the derivation runs in the background after we enter the line item details. The system is not picking the derivation if we directly post the document without checking the PA segment.
    If there is some BADI or user exit we could use to manually replace the COPA characteristics explicitly at document posting, please let me know
    Thank You

    Hi,
    You have to use the rule,
    Moves it let you copy a constant or the content of the source field to target field.
    With regards
    krishna

  • How do we transfer payment terms discount to cost based COPA

    Hi All
    If customer pays in 30 days we will offer 2 % discount. This will be captured in SKTO condition type. How do we transfer this discount to cost based COPA?

    Venkat
    You can assign the Discount GL Account in OKB9 for the company code and tick PrfSeg.
    Then create a PA Transfer Structure with Cost Element Discount as Source and suitable Value field.
    At the time of your Finance Entry where discount is calculated, based on your FI Settings, relevant COPA characteristics would be captured and transferred to COPA.

  • Sales Employee wise Profitability in COPA

    Experts,
    Below mentioned are COPA characteristics in current structure. Mentioned in RED are characteristics based on Derivation Logic.
    Company Code
    Plant
    Sales Org.
    Distr. Channel
    Division
    Customer
    Product
    Sales employee
    Supervisor
    Manager
    Segment
    I am able to run COPA Assessment cycle for all other segmental level characteristics maintained in KEQ3, But for Sales Employee my logic failed i Have searched for some SAP notes in which SAP mentioned that Sales employee as a receiver characteristic  we can not run assessment cycle.
    SAP Note : 74399
    But in this case my derivation logic is failed as
    Supervisor
    Manager
    Segment
    Are based on Sales Employee based derivation logic.
    In this case how to run KEU5 with Sales employee as a receiver characteristic or else any work around is available for the same.
    Thanks
    Sagar C'kar

    Sir,
    Near to Resolve....
    Need your Approval & expert comments... :-)
    I have maintained 4 Custom Characteristic
    WW010 Sales employee
    WW011 Supervisor
    WW012 Manager
    WW013 Segment
    KEDR with Move Concept from(Std characteristic) KMVTNR to WW010 (Custom Characteristic)
    KEDR Maintained for Supervisor and manager based on Sales Employee (WW010) to flow Revenue & Cogs
    similarly KEDR maintained for Segment on different combination like customer grouping
    Now system has revenue posted with 
    WW011 Supervisor
    WW012 Manager
    WW013 Segment
    and the same can be used in Assessment cycle for OH allocation.
    But if i keep (Std characteristic) KMVTNR for assessment i am unable to allocate OH to this due to system constraints.
    So i am having WW010 (Custom Characteristic) with flow Revenue & Cogs and i am planning to allocate OH to this through COPA Assessment cycle..... And display only this characteristic in the COPA reports.
    Is it fine.... May i proceed with this which will resolve my issue for Sales Employee based profitability...
    Thanks
    Sagar C'kar

  • Runtime Error COPA Report KE30  - Assign_Length_0

    Dear users,
    As ABAP is unknown terrain for me, I stumbled upon an error which I can't seem to bypass.  I do not know wheter this is the right forum to ask the question, so if I'm wrong, please do correct me.
    Current situation
    1. I've added a user def COPA Characteristic to the operating concern X.
    2. I've made a realignment run to fill table CE40001 (prof segments)
    3. Ive created a report (with form) where the report uses the field (point 1) as a drill down object.
    When running this report, I immediatly get the error 'Assign length 0' - in program "SAPMKCBE", module "SEIG_POSITIONIEREN"
    When looking at the error it stumbles at understanding code.  It seems that
    1. looking for value in table  'field_tab', which is CE10001
    2. field "Reffl"
    But as I've checked the table, this field does not exist.  So this is where I'm stuck;
    Allready thanks for any help that you can provide!
    Ben
    74           IF SY-SUBRC EQ 0.
    75             IF L_S_LCOL_CHAR-DIMPR EQ DIMPR_L  OR
    76                L_S_LCOL_CHAR-DIMPR EQ DIMPR_KL OR
    77                L_S_LCOL_CHAR-DIMPR EQ DIMPR_LK.
    78               IF FIELD_TAB-FIENM NE SEIG-FNAM.
    79                 READ TABLE FIELD_TAB WITH KEY
    80                                      FIENM = SEIG-FNAM BINARY SEARCH.
    81               ENDIF.
    82               I = FIELD_TAB-REFLL.
    83               ASSIGN FELD1(I) TO <TEXT>.                   "#EC *
    84             ELSE.
    85               ASSIGN FELD1(20) TO <TEXT>.
    86             ENDIF.

    I found the issue regarding this problem. In customizing for the COPA characteristics, you have to define the default display for this characteristic in the COPA Report. This option can be set to "Long Text".
    As it seems, this field is (in my case) not activated, and it can't be activated.  Nor can it be maintained.
    As a result the report searches for 'long text - REFLL' which doesn't exist.
    solution:
    Change default view for the characteristic AND completly rebuild your report.  Since SAP doesn't read this value (default dispay) dinamicly, but only once while creating the report.
    regards and thanks for no help
    hope I could be of assistance to anybody else

Maybe you are looking for