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

Similar Messages

  • COPA-Offset Derivation Rules

    Hi
    Pls let me know how to create offset derivation rules in COPA
    Thanks

    Hi Deepthi ,
    The best way to find out is to check the characteristics in both the release orders seperately ..
    Go to Transaction KE21S   ( Select Record Type F , Point of Valuation 1) and simulate the characteristics derivation for both the orders seperately ..
    . For simulation .. enetr parameters like order no , company code , plant .. etc and click on derivation .. System will derive the sales mode .. for both the orders . You will be able to find out the differences in characteristics .. which is causing the issue ..
    Instead of KE21S .. you can also use transaction KEDR . In KEDR screen , enter (F8) or click on test icon and simulate the characteristics derivation..
    Hope this will solve your issue .. Please revert back for any further clarifications..
    Regards
    Sarada

  • 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

    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.

  • Account Based Vs Cost Based COPA - Char Derivation

    We're trying to implement both Cost based and Account based COPA at a client here.
    I have some derivation rules maintained in KEDR.
    When I'm trying to post a document in FI, the cost based COPA document is being created with the Characteristics populated correctly according to the derivation rules. However, in Account based COPA the characteristics are NOT getting derived.
    Can some tell me if there could be something I've missed?
    Thanks

    Hi
    Have you deactivated any of the characteristics used in Account based COPA
    Check KEQ3 and you may have activated only for Costing based COPA
    S Jayaram
    Edited by: S Jayram on Dec 18, 2007 3:24 PM

  • 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

  • COPA: Characterstic Derivation

    Hi All,
    Can someone give some example of characteristics that are derived and how they were derived ( real time examples )
    This will help me for my interview.
    All answers will be rewarded.
    Regards,
    Reddy

    Hi,
    Check this:
    Country ship to: Derive the ship to country using the following table lookup:
    Origin         Field name                     Origin     Field name     Description
    KNA1          KUNNR     =     CO-PA     KUNWE                     Ship to party
    Move to target ship to country
    Origin           Field name                     Origin     Field name     Description
    KNA1            LAND1     =     CO-PA     VV300                     Ship to country
    You can check this also.
    4.2.1.1     Define Characteristic Derivation
    Use
    The purpose of this activity is to define the characteristic derivation for the characteristics Item Category Dummy, Ship-to party, Country Ship-to, Region Ship-to and Intercompany Indicator.
    Prerequisites
    All characteristics values have been entered and operating concern has been generated successfully.
    Procedure
    1.      Access the activity using one of the following navigation options:
    Transaction Code     KEDR
    IMG Menu     Controlling  Profitability Analysis  Master Data  Define Characteristic Derivation
    2.     In Operating concern, enter BPDE and choose Enter.
    3.     In the Characteristic Derivation: Display Strategy screen, choose the Change button.
    4.     Choose Create.
    5.     In the Create Step dialog box, choose Move and choose Enter.
    6.     In the Characteristic Derivation: Change Assignment screen, in Step Description, enter Item Category --> Item Category Dummy.
    7.     In Source field enter PSTYV and choose Enter, in Target field enter  WWICD and choose Enter.
    8.     Choose the Save button to save the entries, and choose Back.
    9.     Choose Create.
    10.     In the Create Step dialog box, choose Move and choose Enter.
    11.     In the Characteristic Derivation: Change Assignment screen, in Step Description, enter Ship-to party.
    12.     In Source field enter KNDNR and choose Enter, in Target field enter  KUNWE and choose Enter.
    13.     On the tab Condition enter Name KUNWE and Operator =.
    14.     Choose the Save button to save the entries, and choose Back.
    15.     Choose Create.
    16.     In the Create Step dialog box, choose Table lookup and choose Enter.
    17.     In table name, enter KNA1 and choose Enter.
    18.     In the Characteristic Derivation: Change Table Lookup screen, in Step Description, enter Ship-to party --> Country Ship-to.
    19.     Retain the default values in the Source Fields for Table Lookup section.
    20.     In the Assignment of Table Fields to Target Fields section:
    In Field name (in column 2), enter LAND1.
    In Field name (in column 5), enter WWCST.
    21.     Choose the Save button to save the entries, and choose Back.
    22.     Choose Create.
    23.     In the Create Step dialog box, choose Derivation Rule and choose Enter.
    24.     In the Characteristic Derivation: Change Structure of Rule Definition screen, in Step Description, enter Country Ship-to --> Region Ship-to.
    25.     In Source fields enter WWCST and choose Enter, in Target fields enter  WWRST and choose Enter.
    26.     Choose the Maintain Rule Values button and enter the following data:
    Country Ship-to      Region Ship-to
    DE      001
    FR      001
    US      002
    27.     Choose the Save button to save the entries, and choose Back.
    28.     Choose Create.
    29.     In the Create Step dialog box, choose Derivation Rule and choose Enter.
    30.     In the Characteristic Derivation: Change Structure of Rule Definition screen, in Step Description, enter Customer --> Intercompany Indicator.
    31.     In Source fields enter KNDNR and choose Enter, in Target fields enter  WWICI and choose Enter.
    32.     Choose the Maintain Rule Values button and enter the following data:
    Customer     Intercompany Ind.
    101      E
    102      E
    103      E
    104      E
    105      E
    106      E
    107      E
    108      E
    109      E
    110      E
    111      E
    BP0001      A
    BP0002      A
    BP000X      A
    C6000      E
    C6100      E
    C6110      E
    C6111      E
    C6112      E
    C6113      E
    C6120      E
    C6130      E
    CPD100      E
    DUMMY      E
    VERBUND100      E
    33.     Choose the Save button to save the entries, and choose Back.
    Thanks,
    Rau

  • COPA-Characteristic Derivation

    hi
    i created a character to capture vessel name which is stored in billing under Customer PO number.  For the i created Table Look Up like Origin Table is VBKD and field is BSTKD and Target filed is WWVSL which i created.  But while releasing the billing document, i am getting error as mentioned below:
    Error occurred during table access. See long text
    Message no. K/112
    CO-PA Characteristic Derivation
    Diagnosis
    Step 0027 Table lookup for vessel name
    While executing this table lookup, the system could not find an entry for the specified source values in table VBKD.
    This derivation step is defined so that an error message is displayed when this occurs.
    Table VBKD lacks entries for the following source values:
    Sales Order Number/Item Number in Sales Order
    214/10
    Procedure
    Make an entry in table VBKD for the specified source values.
    If you do not want derivation to be performed in every instance, change the derivation step so that no error message is displayed if no entry exists.
    Maintain derivation strategy
    If any one know how to solve this error, pls let me know.
    i will assign good points.
    thanks

    Hi There
    Go to KEDR and double click on that derivation step .
    You will see three tabs there ( Definition , Condition Attribute )
    Go to attributes and uncheck the issue error message box.
    Thanks,
    Reddy

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

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

  • Derivation rule to determine customer tax classification in COPA

    Hi Experts,
    Please guide me to complete this assignment.
    The requirement is to fetch the material tax classification and customer tax classificaion into COPA through derivation rule.
    we can fetch material tax classification through table VBRP.
    Please help me to derive customer tax classification( KNVI-TAXKD) through derivation.
    Customer tax classification data is available in table KNVI.
    But when you consider KNVI table through table lookup it is asking customer, country key and tax category. To define this derivation rule we need tax category values in COPA.
    We can get customer and country key but not tax category.
    How to bring tax category (KNVI-TATYP)
    into COPA to define derivation rule to fetch customer tax classification( KNVI-TAXKD).
    Please suggest me if any alternative solution to bring customer tax classification data into COPA.
    Points will be assigned to usefull answer.
    Thanks in advance.
    Regards,
    Amar.

    HI,
    The Tax related thing are balance sheet items . which can not be considered at CO-PA.
    only revenue item will be considered at Co-pa.
    Hope this is clear
    With regards
    krishna

Maybe you are looking for