Cost center screen layout rules

Question

Hi All,
          In the cost center master data field cost center catagory and person responsible is mandatory i would like to make it optional can anyone advice how to do.
         thanks in advance.
regards,
Pranav

Answer 1

Hello
You can maintain master data for cost centers, cost elements, activity
     types, and business processes with time dependencies. You can make
     changes at any time for any given time interval. Data storage also takes
     place with a time reference. In this way, a master data record can have
     multiple database records storing different information.
     The smallest interval is one day. To ensure data consistency, you cannot
     change each field daily. The timeframes in which you can change a field
     depend on the field functions, which are fixed by the system and cannot
     be changed. Master data maintenance includes an automatic check for each
     field's time-based consistency, resulting in individual time-based
     maintenance for each field.
     The following dependencies are supported:
     o   Not time-based
     o   Day-based
     o   Period-based
     o   (Fiscal) year-based
     This function provides an overview of the time dependencies of
     individual master data fields during master data maintenance, along with
     checks and storage of consistency timeframes. You find this information
     in the "Time dependency" column.
     If you use fields requiring characteristics greater than one day and
     which are changed for the system lifetime of the object, the system
     automatically creates a new database record for this processing
     interval, and changes the time-based validity of existing records. The
     change is logged in the master data record with the time reference.
     However, a great number of changes in multiple timeframes will result in
     a correspondingly great number of data records.
     Fields which you can change freely (indicated in the DAY column) can
     possess different time dependencies only if you mark them additionally
     as historically relevant. This activates the time-based updating for the
     records.
Example
     Object 1000 has one master data record created with a fiscal year of 12
     periods and the cost center name AAAAAAAAAA. During master data
     maintenance, you change the cost center name in period 5 to BBBBBBBBBB.
     The system reacts with one of two options.
     o   "Name" is marked as historically relevant. The existing master data
         record for periods 1 - 12 must now become three records:
         1000   01-04   AAAAAAAAAA
         1000   05      BBBBBBBBBB
         1000   06-12   AAAAAAAAAA
     o   "Name" is not marked as historically relevant. The existing master
         data record remains intact, with the name changed for the entire
         existence of the record:
         1000   01-12   BBBBBBBBBB
Reg
*assign points if useful