SAP ABAP Data Element CL (Service Level)
Hierarchy
☛ ECC-DIMP (Software Component) DIMP
   ⤷ IS-AD (Application Component) Aerospace & Defence Industry Solution
     ⤷ AD_ROT_CALC (Package) Stock Calculation: Rotables & Expendables
Basic Data
Data Element CL
Short Description Service Level  
Data Type
Category of Dictionary Type D   Domain
Type of Object Referenced     No Information
Domain / Name of Reference Type ORFCALC1    
Data Type DEC   Counter or amount field with comma and sign 
Length 16    
Decimal Places 6    
Output Length 20    
Value Table      
Further Characteristics
Search Help: Name    
Search Help: Parameters    
Parameter ID   
Default Component name    
Change document    
No Input History    
Basic direction is set to LTR    
No BIDI Filtering    
Field Label
  Length  Field Label  
Short 10 SL 
Medium 18 SL 
Long 30 Service Level 
Heading 30 Service Level 
Documentation

Definition

Probability that a spare part is available on stock in the condition 'serviceable'.

Use

Dependencies

Supplementary Documentation - CLARIFACC_BRO0001

Note

Field is not relevant to the commission system.

Supplementary Documentation - CLARIFACC_BRO0002

Use

Procedure

Enter the account number for the contract account.

Examples

Dependencies

Supplementary Documentation - CLARIFACC_BRO0003

Use

Restriction of the items to be processed: All open items that correspond to the selction criteria specified are selected.

Procedure

If you want to make a more detailed selection, choose Extras -> Custom Selectoins.

Supplementary Documentation - CLARIFACC_BRO1000

Use

The desired logs are only created for the specified contract accounts.

Procedure

Examples

Dependencies

Supplementary Documentation - CLARIFACC_BRO1001

Use

Contract account to which the security deposit is assigned.

Procedure

Examples

Dependencies

Supplementary Documentation - CLARIFACC_BRO1002

Use

Procedure

If you have selected the Person field, you must specify a contract account, to which outstanding receivables can be posted if necessary.

Examples

Dependencies

Supplementary Documentation - CLARIFACC_BRO2000

Use

Restriction on items to be processed.

Procedure

Examples

Dependencies

You can include multiple open items in an installment plan. However, these items must all have been posted to the same contract account; this means that you cannot set up an installment plan on a cross-contract account basis.

Supplementary Documentation - CLARIFACC_BRO2100

Use

The line item will be, or has been, posted to the contract account entered here. More information is received about the contract account posted to during further processing for the line item, as long as this information has not been received already. This information includes: Payment method, dunning procedure, tolerances.

Procedure

Examples

Dependencies

Supplementary Documentation - CLARIFACC_BRO2200

Use

Selection specification: If you only specify one contract account and no business partner, all items are selected for the contract accounts for all business partners that participate in the contract account.

Procedure

Examples

Dependencies

If you also specify a business partner, only the items for the business partner for the specified contract account are selected. You can use the Also Select Postings for Other Partners flag to extend the selection.

Supplementary Documentation - CLARIFACC_BRO2300

Use

Restriction on items to be processed: All open items that were posted to the specified business partner and the specified contract account, and which correspond to the other selection criteria, are selected.

Procedure

Examples

Dependencies

Supplementary Documentation - CLARIFACC_BRO2302

Use

Restriction of the items to be processed: All open items that correspond to the selction criteria specified are selected.

Procedure

If you want to make a more detailed selection, choose Extras -> Custom Selectoins.

Supplementary Documentation - CLASSDE 0001

Use

You can maintain the assignment of data elements to Dictionary authorizations.

This means that authorization for Dictionary maintenance of individual data elements can be restricted to a specified group of users/developers.

Procedure

  1. Mark with a cross, select object from the menu or press PF2.
  2. Generic entry of the object name and/or authorization group.
  3. Select PF key maintenance.
  4. Enter the authorization group in the relevant field.
  5. Save and press PF3 Back.
  6. Check authorization by carrying out a maintenance test.

Dependencies

You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.

You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.

Examples

Supplementary Documentation - CLASSDOM 0001

Use

You can maintain the assignment of domains to Dictionary authorization groups.

This allows you to restrict authorization for Dictionary maintenance of individual domains to a specific group of users/developers.

Procedure

  1. Mark with a cross, select object from the menu or press PF2.
  2. Generic entry of the object name and/or authorization group.
  3. Select PF key maintenance.
  4. Enter the authorization group in the relevant field.
  5. Save and press PF3 Back.
  6. Check authorization by carrying out a maintenance test.

Dependencies

You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.

You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.

Examples

Supplementary Documentation - CLASSMCO 0001

Use

You can maintain the assignment of matchcode objects to Dictionary authorization groups.

This allows you to restrict authorization for Dictionary maintenance of individual matchcode objects to a specific group of users/developers.

Procedure

  1. Mark with a cross, select object from the menu or press PF2.
  2. Generic entry of the object name and/or authorization group.
  3. Select PF key maintenance.
  4. Enter the authorization group in the relevant field.
  5. Save and press PF3 Back.
  6. Check authorization by carrying out a maintenance test.

Dependencies

You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.

You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.

Examples

Supplementary Documentation - CLASSPC 0001

Use

You can maintain the assignment of pools/clusters to Dictionary authorization groups.

This allows you to restrict authorization for Dictionary maintenance of individual pools/clusters to a specific group of users/developers.

Procedure

  1. Mark with a cross, select object from the menu or press PF2.
  2. Generic entry of the object name and/or authorization group.
  3. Select PF key maintenance.
  4. Enter the authorization group in the relevant field.
  5. Save and press PF3 Back.
  6. Check authorization by carrying out a maintenance test.

Dependencies

You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.

You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.

Examples

Supplementary Documentation - CLASSPC 0002

Use

A table should be placed in a pool

  • if external access to the table is not required
  • if the table is accessed using the primary key
  • if the table is very small

A table should not be placed in a pool

  • if the table is to be processed from outside the SAP System
  • if the table is to be accessed using non-key fields
  • if additional indexes are required
  • if a database join to other tables is required
  • if it is a large table

A table should be placed in a cluster

  • if it forms an object together with other tables and this object is generally processed as a complete unit

    Example:

    The "Order header", "Order item" and "Operations" tables form an object.

  • if several records of a table form an object which is generally processed as a complete unit

    Example:

    Applies to tables containing documentation or text.

  • if the table is intended for SAP internal use only, i.e. it is not accessed externally

A table should not be placed in a cluster

  • if it is to be processed from outside the SAP System
  • if it is to be selected using non-key fields
  • if additional indexes are required
  • if a database join to other tables is required
  • if a table is to be processed separately from other tables in a cluster

Procedure

Examples

Dependencies

Supplementary Documentation - CLASSSPO 0001

Use

You can maintain the assignment of lock objects to Dictionary authorization groups.

This allows you to restrict authorization for Dictionary maintenance of individual lock objects to a specific group of users/developers.

Procedure

  1. Mark with a cross, select object from the menu or press PF2.
  2. Generic entry of the object name and/or authorization group.
  3. Select PF key maintenance.
  4. Enter the authorization group in the relevant field.
  5. Save and press PF3 Back.
  6. Check authorization by carrying out a maintenance test.

Dependencies

You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.

You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.

Examples

Supplementary Documentation - CLASSTAB 0001

Use

You can maintain the assignment of tables to Dictionary authorization groups.

This allows you to restrict authorization for Dictionary maintenance of individual tables to a specific group of users/developers.

Procedure

  1. Mark with a cross, select object from the menu or press PF2.
  2. Generic entry of the object name and/or authorization group.
  3. Select PF key maintenance.
  4. Enter the authorization group in the relevant field.
  5. Save and press PF3 Back.
  6. Check authorization by carrying out a maintenance test.

Dependencies

You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.

You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.

Examples

Supplementary Documentation - CLASSTABU 0001

Procedure

  1. Mark with a cross, select object from the menu or press PF2.
  2. Generic entry of the object name and/or authorization group.
  3. Select PF key maintenance.
  4. Enter the authorization group in the relevant field.
  5. Save and press PF3 Back.
  6. Check authorization by carrying out a maintenance test.

Dependencies

You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.

You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.

Examples

Supplementary Documentation - CLASSVIEU 0001

Procedure

  1. Mark with a cross, select object from the menu or press PF2.
  2. Generic entry of the object name and/or authorization group.
  3. Select PF key maintenance.
  4. Enter the authorization group in the relevant field.
  5. Save and press PF3 Back.
  6. Check authorization by carrying out a maintenance test.

Dependencies

You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.

You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.

Examples

Supplementary Documentation - CLASSVIEW 0001

Use

You can maintain the assignment of views to view maintenance authorization groups.

This allows you to restrict authorization for table maintenance of individual views to a specific group of users/developers.

Procedure

  1. Mark with a cross, select object from the menu or press PF2.
  2. Generic entry of the object name and/or authorization group.
  3. Select PF key maintenance.
  4. Enter the authorization group in the relevant field.
  5. Save and press PF3 Back.
  6. Check authorization by carrying out a maintenance test.

Dependencies

You require authorization to maintain the associated tables TDDAx. If you do not have this authorization, the system branches automatically to display mode. There is also a lock function that prevents parallel assignment of authorization classes and Dictionary maintenance of the same objects. If this function is in place, only display mode is possible.

You can only enter allowed authorization groups. These are maintained under menu point Permitted_groups.

Examples

Supplementary Documentation - CLASS_52B40001

Use

The form class determines the area in which the form will be used.

Examples

Form    Form class

Remuneration statement    CEDT

Payroll account    CKTO

Payroll journal    CLJN

Time statement    TEDT

Supplementary Documentation - CLCPS 0001

Use

In a field with format CHAR, DATE, or TIME, you can search for a string that occurs in the value of the characteristic.

Procedure

If you want to search for an exact match, select this field.

If you want to search for a string containing figures, you must define the format of the characteristic as format CHAR, DATE, or TIME, and define figures as allowed values.

Examples

Dependencies

Supplementary Documentation - CLEARREAS_SINGLE_BRO1000

Use

This clearing reason is noted in those documents that the payment program creates in the payment run with the payment method.

Examples

Dependencies

Supplementary Documentation - CLEARREAS_SINGLE_BRO2300

Use

Der Schlüssel wird zu Ihrer Information in den ausgeglichenen Belegpositionen gespeichert und kann bei Auswertungen über die Einzelposten (z.B. in der Kontenstandsanzeige) ausgegeben werden.

Procedure

If you clear items with the Post document function, specify a clearing reason here. If you do not enter a clearing reason, the system will ask you for a clearing reason before posting the document.

Procedure

Examples

Dependencies

Supplementary Documentation - CLEARREAS_TOTAL_BRO1000

Use

This clearing reason is noted in those documents that the payment program creates in the payment run with the payment method.

Examples

Dependencies

Supplementary Documentation - CLEARREAS_TOTAL_BRO2300

Use

Der Schlüssel wird zu Ihrer Information in den ausgeglichenen Belegpositionen gespeichert und kann bei Auswertungen über die Einzelposten (z.B. in der Kontenstandsanzeige) ausgegeben werden.

Procedure

If you clear items with the Post document function, specify a clearing reason here. If you do not enter a clearing reason, the system will ask you for a clearing reason before posting the document.

Procedure

Examples

Dependencies

Supplementary Documentation - CLSEL01 0001

Procedure

Select the status to be used for the current assignment.

Supplementary Documentation - CLSEL02 0001

Procedure

Select the characteristic value that you want to assign to the selected characteristic.

Dependencies

If the characteristic only allows one value to be entered, and you select a value from the list, the system automatically removes the values already assigned.

Supplementary Documentation - CLSTATUS 0001

Procedure

If you want to change the status, you can do this by choosing "Change status".

Supplementary Documentation - CLSTATUS 0002

Procedure

Enter the status for the assignment in the class search.

Supplementary Documentation - CLSTATUS 0003

Procedure

Enter the status that this object is to have when searching via the superior class.

Supplementary Documentation - CLSTB1_LST0001

Use

You can create the list in various breakdown levels.

Procedure

This parameter allows you to define the breakdown level for the first list. Press F2 to break down the list entries further.

List = 1 Personnel numbers and periods
2 Table names in cluster B1 for the selected persons
3 Table contents
4 Data description of entries in tables which can be broken
down or contents of tables which cannot be broken down.

You can use the scroll function to display the data of various persons or tables.

Examples

Dependencies

Supplementary Documentation - CLSTB2LART0002

Use

You can select one of the radio buttons under 'List format' to determine the level at which the list is displayed.

Procedure

The list can be displayed at two levels:

  • List of personnel numbers and periods:
    • A list of the selected personnel numbers and periods is displayed. You can select a line to see more information on the list entries.
  • Detailed description of all table entries:
    • All table entries for the selected personnel numbers and periods are displayed.

Supplementary Documentation - CLSTB2LART0003

Use

You can select one of the radio buttons under 'List format' to determine the level of detail in the list display.

Procedure

The list can be displayed at two levels:

  • List of group numbers and periods:
    • A list of the selected group numbers and periods is displayed. You can select a line to see the next level of the list.
  • Detailed description of all table entries:
    • All table entries for the selected group numbers and periods are displayed.

Procedure

Examples

Dependencies

Supplementary Documentation - CLSTB2LART1000

Use

Specifies the level of detail in which the list is displayed. For more information, see the report documentation.

Supplementary Documentation - CLSTB2LART2000

Use

The list can be generated at various explosion levels.

Procedure

You can choose the radio button group 'List format' to specify an explosion level for the list.

Level 1: Provides a list of the selected personnel numbers
and periods.

Level 2: Shows all table entries in cluster ZL for the selected
personnel numbers and periods.

Use the line selection function to move from level 1 to level 2 for a selected personnel number and period.

Supplementary Documentation - CLSTB2_LST0001

Use

You can create the list in different breakdown levels.

Procedure

This parameter allows you to define the breakdown level for the first list. Press F2 for a further break down of the list.

List = 1 Personnel numbers and periods
2 Table names in cluster B2 for the selected persons
3 Table contents
4 Data description of entries in tables which can be broken
down or contents of tables which cannot be broken down.

You can use the scroll function to display the data of various persons or tables.

Examples

Dependencies

Supplementary Documentation - CLSTB3_LST0001

Use

You can create the list in various breakdown levels.

Procedure

This parameter allows you to define the breakdown level for the first list. Press F2 for a further break down of the list entries.

Parameter list = 1 General information
2 Table names in cluster B3
3 Table contents
4 Data description of table entries

Examples

Dependencies

Supplementary Documentation - CLSTB4_LST0001

Use

List breakdown level

Procedure

You can create the list in different breakdown levels. This parameter allows you to define the breakdown level for the first list. Press F2 for a further breakdown of the list entries.

Parameter list = 1 General information
2 Table names in cluster B4
3 Table contents
4 Data description of table entries

Examples

Dependencies

Supplementary Documentation - CLSTEXT 0001

Procedure

From the list of jobs, choose the job that you want the system to use for the reduction of requirements for the current day and the current employee.

In the list of jobs, you will only find jobs that are assigned (via a position) to at least one organizational unit from your current selection of organizational units.

Dependencies

This alternative job assignment does not affect the employee's pay. If you made an alternative job assignment in this field, then only positions that are linked to the alternative job appear in the display. If you did not make any alternative job assignment, then all the positions are displayed.

Supplementary Documentation - CLTYP 0001

Use

Procedure

The cluster type is used to distinguish between original and copy records in the cluster. Cluster type 1 is used for original records, copy records have higher numbers.

Examples

Dependencies

History
Last changed by/on SAP  20050301 
SAP Release Created in 46C2