Error in CO-PA extractor with operating concern

Hello,
I have a problem when trying to load data from R/3 to BW using a CO-PA datasource.
When I try to load it into BW Server and even using simulation transaction RSA3, I get the error:
"Inconsistency in the control tables of the operating concern"
"Error condition when reading data"
I have created the datasource, using SBIW transaction, and then navigating in the menu:
Settings for Application-Specific datasources -> Profitability analysis -> Create Transaction datasource. 
Can anybody help me? any idea?
Thanks in advance, Inma

Hi,
Check whether the operating concern is  defined/created properly using KEA0 tcode.
If the opearationg conern is correctly defined then you can go ahead creating the CO-PA data source using KEB0 and donot forget to mention your operating concern name.
Hope this helps
Assign points if useful
Regards,
venkat

Similar Messages

  • Error when create Operating Concern

    Hi Experts;
         At the time of creating a new operating concern after i have defined Characteristics and Value Fields, and checking the status I received the following error:
    Error generating table KOMPAKE
    Message no. KE434
    Diagnosis
    An error occurred while Table KOMPAKE was being generated.
    Procedure
    Analyze the error using Transaction SE11. Use the function 'Check'.
    Then I wen to SE11 to check giving the table name as mentioned above, I found the following and could not fix the error;
    Then after opening the Long Text it gave the following message:
    Enhancement category for table missing
    Message no. DT192
    Procedure
    Maintain the enhancement category in the table or structure maintenance in the ABAP Dictionary.
    Then by opening the ((enhancement category)) link i received the following message then STOPPED where I could not do anything more!!!
    Enhancement Category Selection
    Definition
    Structures and tables that were defined by SAP in the ABAP Dictionary can be enhanced subsequently by customers using Customizing includes or append structures. The enhancements do not only refer to structures/ tables themselves, but also to dependent structures that adopt the enhancement as an include or referenced structure. Append structures that only take effect at the end of the original structure can also cause shifts - in the case of dependent structures - even within these structures.
    You must select an enhancement category for the following reason: In programs where there is no active Unicode check, enhancements to tables and structures can cause syntax and runtime errors during type checks and particularly in combination with deep structures.
    In programs where there is an active Unicode check, statements, operand checks, and accesses with an offset and length are problematic - for example, if numeric or deep components are inserted into a purely character-type structure and the structure thus loses its character- type nature.
    Depending on the structure definition, the radio buttons allowed in the dialog box are ready for input. Choose one of the possible enhancement categories:
    Cannot be enhanced
    The structure must not be enhanced.
    Can be enhanced or character type
    All structure components and their enhancements must be character-type (C, N, D, or T). The original structure and all enhancements through Customizing includes or through append structures are subject to this limitation.
    Can be enhanced or character-type or numeric
    The structure and its enhancement must not contain any deep data types (tables, references, strings).
    Can be enhanced in any way
    The structure and its enhancement may contain components whose data type can be of any type.
    Not classified
    This category can be chosen, for example, for a transition status; however, it must not be chosen for creating structures.
    The rules for defining the enhancement category result implicitly from the structure setup and the classification of the types used. These rules are as follows:
    If the object contains at least one numeric type or a substructure or component (field has a structure/table/view as its type) that can be enhanced numerically, the object can no longer be enhanced character-type, but is itself, at most, enhanceable character-type or numeric.
    If the object contains a deep component (string, reference, or table type), or it contains a substructure or component that is marked as enhanceable in any way, then the object itself is enhanceable in any way.
    If the object does not contain any substructure or component that is marked as enhanceable, you can select cannot be enhanced. If the structure has not yet been enhanced, you can choose the category cannot be enhanced in any case.
    If you are creating new tables and structures in the ABAP Dictionary, the system proposes the category can be enhanced in any way as standard value for the classification of the enhancement options. If the developer chooses a more restrictive classification than can be enhanced in any way for a particular structure, then only the classification levels that adhere to the rules above are allowed. It is not possible to choose an enhancement option of a structure that is more restrictive than the classification resulting immplicitly from the structure setup and from the classification of the types used. Therefore, only the allowed categories are proposed for selection in the maintenance user interface.
    If a structure depends on one or several other structures, the smallest category is chosen as implicit classification (in the order cannot be enhanced < can be enhanced and character-type < can be enhanced and character-type or numeric < can be enhanced in any way). This classification is greater than or less than the category in the other structures and also greater than or the same as the category that results from the actual setup in the original structure itself.
    For more information, refer to the online documentation (pushbutton "i").
    Thanks in advance;
    Best regards;
    Ahmad Mahmud;

    Hi Mahmud,
    You may need to refer this issue to ABAPer..
    Regards
    Mohit

  • New operating concern - order settlemement - runtime error KE499

    Hello all,
    we created a new operating concern 8000 and changed to the operating concern in KEBC.
    Now when we try to do an order settlement in KO88, it is working for new orders created after the operating concern change, but for old orders, we do get a runtime error KE499:
    Profitability segment number 0000183221 does not exist in operating concern 8000!
    Appearently this is caused by the operating concern change, because the old orders are still "connected" to our old operating conern 2000.
    Now I was wondering, is there a transaction to fix this, something that would transfer the values for the order from the old operating concern to the new one?
    Thanks
    Anne

    Hi,
    I am also getting the exact same error while running CO88 for settlement of production orders, The note recommended above deals with inconsistencies in the sales data. We had changed the assignment of the operating concerna and now we are facing the error where we are not available to pass even one settlemsnt of the production order. I cannot go and individually delete the orders and have to run settlement as a mass transaction.
    Please advise innwhat to do.
    Ariel

  • Operating concern for two company code with different currency

    Hi,
    We are merging two company code into one SAP server.
    We decide to use on chart of account, and to use one operating concern.
    For company code A: the currency is CNY, for company code B: the currency is TWD.  The operating concern currency is:CNY.
    So i need to in KEA0(maintain operating concern) active company code currency, right?
    So every posting in company code B will be posted in TWD and CNY to COPA same item, right?
    In KE30 report, where to add characters: Currency type that i can show company code B report in TWD?
    Thanks.

    Dear David,
    Yes. If you have different compancy codes within one controlling area, you have to maintain currency type with 10-Company code currecny and while maintaining the operating concern also you have to choose the company code currency only.  Then only you will get the reports with respect of your company code currecny level. This will be basing on your company code-sales organisation, plants and other charcters assignment basis in your configuration.
    All the best,
    Dharma Rao. Yekula.

  • My iCal won't go online and returns the error message: The server responded with "500" to operation CalDAVAccountRefreshQueueableOperation.

    My iCal won't go online and returns the error message: "The server responded with “500” to operation CalDAVAccountRefreshQueueableOperation."

    OK Now I can answer my own question.  The incomprehensible (inexcusably geeky) error message is actually Apple language for saying simply: "The iCloud servers are down again.  Please wait until we've fixed them."  I found this out by talking to Apple support.  It took about 12 hours for the iCloud server synching calendars to come back online.  When they did, my calendar reloaded, and everything was fine.

  • Reports for two costing Area With one operating concern

    Hi,
    What are the reports I can get if I am having two different costing area for my comapnies with same operating concern
    Thanks in advance for your input
    CHEERS

    Thanks Sreekanth ,
    I want to what are the reports that will be generated. And what cannot be done if we have two controlling area instead of one.
    CHEERS

  • Error when running application - something to do with Opera?

    When I run a RIA that I made based off a tutorial (I am a Flex beginner,) I get an error message stating : CreateProcess: "C:\Program Files\Opera\opera.exe" "C:\Users\Daniel\Desktop\computer stuff\FB3\FlickrRIA\bin-debug\FlickrRIA.html" error=2.  Why is there something with Opera?  I don't use Opera anymore, I uninstalled it, and only use Firefox now.

    Somebody still thinks opera is the handler for html or SWF files.  If you are using FlexBuilder you may need to update which browser it uses.
    Alex Harui
    Flex SDK Developer
    Adobe Systems Inc.
    Blog: http://blogs.adobe.com/aharui

  • While networking with labview 8.5 it gives error"not enough memory for this operation" ??

    hi
    i m working with the labview networking for the first time, when i ran my code it worked well 4 sometime . but after some days, it started giving error " not enoug memory for this operation" when the data reaches at 'typecast' tool (refer my code). my OS is winXP and RAM is 496MB. how to solve this problem?please reply soon .

    Hi JAhmed,
    Looking at your code, there may be a memory issue with the way you are type casting the string output from your TCP Reads. Since you are type casting a string to a number or array, you are not giving an indication of how much memory to allocate for this data, and I would suggest instead using an Unflatten From String VI. Use this VI the same way as your Type Casts, but for the input that reads "data includes array or string size?" create a false constant value because your data does not include this information.
    Regards,
    Stephen S.
    National Instruments
    Applications Engineering

  • An error was encountered performing the requested operation:  Listener refused the connection with the following error: ORA-12505, TNS:listener does not currently know of SID given in connect descriptor    Vendor code 12505

    From sql developer I am trying to connect to database in my local machine. It shows the following below error. Any suggestions?
    An error was encountered performing the requested operation:
    Listener refused the connection with the following error:
    ORA-12505, TNS:listener does not currently know of SID given in connect descriptor
    Vendor code 12505

    lsnrctl results are as shown below
    C:\Users\ndodd_000>lsnrctl status
    LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 18-AUG-2013 17:40
    :25
    Copyright (c) 1991, 2010, Oracle.  All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
    STATUS of the LISTENER
    Alias                     LISTENER
    Version                   TNSLSNR for 64-bit Windows: Version 11.2.0.1.0 - Produ
    ction
    Start Date                18-AUG-2013 15:29:41
    Uptime                    0 days 2 hr. 10 min. 50 sec
    Trace Level               off
    Security                  ON: Local OS Authentication
    SNMP                      OFF
    Listener Parameter File   C:\app\ndodd_000\product\11.2.0\dbhome_1\network\admin
    \listener.ora
    Listener Log File         c:\app\ndodd_000\diag\tnslsnr\Vamsi\listener\alert\log
    .xml
    Listening Endpoints Summary...
      (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\EXTPROC1521ipc)))
      (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=127.0.0.1)(PORT=1521)))
    Services Summary...
    Service "CLRExtProc" has 1 instance(s).
      Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
    Service "sysdba" has 1 instance(s).
      Instance "sysdba", status READY, has 1 handler(s) for this service...
    Service "sysdbaXDB" has 1 instance(s).
      Instance "sysdba", status READY, has 1 handler(s) for this service...
    The command completed successfully
    lsnrctl service results
    LSNRCTL for 64-bit Windows: Version 11.2.0.1.0 - Production on 18-AUG-2013 17:
    :20
    Copyright (c) 1991, 2010, Oracle.  All rights reserved.
    Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=EXTPROC1521)))
    Services Summary...
    Service "CLRExtProc" has 1 instance(s).
      Instance "CLRExtProc", status UNKNOWN, has 1 handler(s) for this service...
        Handler(s):
          "DEDICATED" established:0 refused:0
             LOCAL SERVER
    Service "sysdba" has 1 instance(s).
      Instance "sysdba", status READY, has 1 handler(s) for this service...
        Handler(s):
          "DEDICATED" established:186 refused:0 state:ready
             LOCAL SERVER
    Service "sysdbaXDB" has 1 instance(s).
      Instance "sysdba", status READY, has 1 handler(s) for this service...
        Handler(s):
          "D000" established:0 refused:0 current:0 max:1022 state:ready
             DISPATCHER <machine: VAMSI, pid: 904>
             (ADDRESS=(PROTOCOL=tcp)(HOST=Vamsi)(PORT=49237))
    The command completed successfully

  • Cross company sales with multiple operating concern

    Hi all,
    I'm going to implement cross company sales in a system that is already live.
    I think that it really fit to the new requirement of the client , that want to allow the possibility of creating a sales order from sales organization A1 of company A, for the plant of company B (related to sales organization B1).
    however the company A and B are also assigned to different controlling area and different operating concern.
    It would be possible to have the cross company sales order in both operating concern? Or in which one I will have the sales order?
    Many thanks.
    Paolo

    Hi
    Inter Co sale will happen whether or not your comp code is assigned to separate Op concern or same
    The sales order must be created by the selling entity
    I would personally prefer Inter Co STO process if the material codes are same across the 2 companies involved here.. This STO can be raised by the Co who is receiving Sales order from the End Customer
    br, Ajay M

  • Error in schedulinq parallel sequences with flow production operations

    We have a routing with a standard sequence with operations in wich we have set "Continuous flow prod"
    and "Min. Send-Ahead Qty=1".
    We have a parallel sequence as well with operations set in the same way "Continuous flow prod"
    and "Min. Send-Ahead Qty=1".
    When you run the transaction "MD11" to create a planned order for the item the scheduling of the operations is correct
    as regard the standard sequence,the system, correctly,  schedules the operations overlapping
    them according to lead time set in the operation details.
    But the last operation of the parallel sequence is scheduled to finish the whole lot before the operation
    following the "return operation" . The system doesn't overlap this operation. In this way the
    last item of the last operation (in the parallel sequence) isn't finished at the same time
    with the last item of the "return operation" (in the standard sequence) as we like it would be.
    We have set "Backwards scheduling" type on customizing and we use the "Alignment key= 2 "
    for standard sequence and in the parallel as well. We have also tryed to set "Alignment key= 1"
    in the parallel sequence but the results are howewer not correct.
    In conclusion the schedulation of  continuous flow production operations
    doesn't work properly between operations belonging to parallel sequences.
    Could you suggest me what to do?
    Thank you.

    Hi,
      I tried with 5 ops 10, 20, 30 ,40,50 ( same work center  wc1)
      Set up time 1, Process time 1min for 1 pc
      set the continuous flow prodn i at op 20 with min send ahead qty 1
      Also a parallel seq was created with 3 ops op20 ,30 , 40 .
      set up time was 2 min for all work centers( same work center wc2) and proc time
      time is 1 min for  1 pc
      In that set the  continuous flow prodn at op 20 with min send ahead qty 1
      sceduling type was forward
    .Alignment key was 2 for both std seq and parallel seq .
      After scheduling found that op 20 in std seq starts at 6.14am and op 40 ends
      at 6.47 am where as in parallel seq op 20 starts at 6.11 am and op 40 ends at
      at 6.47 am which is correct.( branch op is 20 and return op is  40)
      The three minutes late start in op 20 of std seq  is due to 3 minutes extra time
      defined for three  work centers setup time.
      I also tried with alignment key 1in both std seq and parellel seq.
    Kindly check that you have maintained the continous flow prodn radio button
    in the same operation in both std seq and parallel seq.
    Regards,
    S.Nandhakumar

  • Problem in generating operating concern - COPA

    Hi COPA gurus,
    When activating operating concern BPUS through T-Code KEA0, following are the error details we found :
    The system is not allowing to activate the operating concern and saving it with following error "Error saving data structure CE1BPUS", Message no. KX655
    The error details with Data Structure are
    "Reference field CE0BPUS-REC_WAERS for CE0BPUS-VVR10 has incorrect type"
    Table CE0BPUS was activated with warnings
    As we analyzed the above error in Structure CE0BPUS, the field REC_WAERS and VVR10 is referring to each other, but the data type is different. For REC_WAERS data type is CUKY and the No. of Character is 5, where for VVR10 the data type is blank and the No. of Character is 15.
    Same error we are getting for Table CE1BPUS which is updated after updating the structure CE0BPUS.
    Please help.

    Hi Sangram,
    There looks to be some issue with the value field VVR10. Please remove the field from operating concern and try again. There must be some changes to the value feld which created this inconsistancy.
    Best Regards,
    Abhisek

  • 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

  • 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

  • Controlling area & operating concern must have same fiscal year variant

    Dear Experts,
    Whether i can assign two controlling area with different fiscal year variant to one operating concern.
    Getting error 'Controlling area & operating concern must have same fiscal year variant'
    Fiscal year variant must be same or Number of posting period must be same.
    regards
    RR
    Moderator: Please, search before posting

    Hi ajay,
    I did the testing also,
    System is showing error msg' Controlling area & operating concern must have same fiscal year variant'
    But someone told me. number of Posting period must be same not fiscal year variant.That why i am confused.
    I assigned all company code same posting period variant in different controlling area.Still facing same error.
    That why i have posted in SDN.
    regards
    RR

Maybe you are looking for