Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-TS (Application Component) Technical Application Support⤷
BK (Package) CO Cross-application Objects
Basic Data
| Data Element | MGEFL |
| Short Description | Indicator for Recording Consumption Quantities |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | YNFLG | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | RECORD_QUANTITY | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Quantity |
| Medium | 15 | Record Quantity |
| Long | 20 | Record Quantity |
| Heading | 5 | Qty |
Documentation
Definition
Indicator defining whether the system issues a message if no quantity or quantity unit is specified for commitment or actual postings.
- The indicator has no effect on planning.
You can also plan consumption quantities at a later date.
- The indicator has no effect on quantity updates or on the identification of quantities in reports.
- You must set the indicator if you want to cost using an overhead that is dependent on the unit of measure posted with this cost element.
- The indicator is an active default setting for the combination of cost center and cost element if in the master data for the cost center and cost element, it is defined that quantities should be managed.
Use
You can specify the recording of quantities in two ways:
- In the master data for the cost center and cost element, you can activate the Record qty indicator.
In the master data, the indicator specifies whether consumption quantities should be recorded for each object (cost center, cost element).
- You can change the indicator in planning.
In planning, the indicator specifies whether consumption quantities are to be recorded for planning values as well as actual values. This is for the object combination to be planned (such as cost center/cost element).
A combination of objects is used for planning or actual postings, which means that the effect this has depends on the indicator setting for each object combination.
The object combination comes from - The first planning entries
- The first actual posting
- If planning does not exist, the system determines whether the indicator is set for the object combination. It does this by using the logical AND link for the field values in the master record of the corresponding single objects.
Caution
If you want to record consumption quantities, you need to specify a quantity and a unit of measure for actual and commitment postings.
Procedure
- For the first posting in a fiscal year to an object using a particular cost element, specify the following for the object and the corresponding cost element:
- Whether quantities are to be recorded in the totals records
- Which unit of measure is to be used for recording the quantities
- Once you have specified this for the relevant fiscal year, you cannot change it.
- Specify a different unit of measure for a later posting.
- If you can convert the unit of measure using that of the first posting (such as kilograms into tons), then
- - The system converts the units of measure accordingly
- - The system displays the posted quantities using the unit of measure that you specified for the first posting.
- If the unit of measure cannot be converted (such as hours into pieces), then
- - The system does not update any quantities after this posting
- - The system does not display any quantities in the information system
- - The system displays the posted quantities in the line items using the corresponding posted unit of measure.
Supplementary Documentation - MGEFL 0001
Note
Field changes
The data in this field can be changed daily.
Time dependency
You can define this field as time-based in the configuration menu of Cost Center Accounting.
- If you activate this indicator, you can maintain separate data for any number of different time intervals.
- If you do not activate this indicator, you can make only one field entry valid for all intervals. If, however, you change a time-based field, you can enter a new value in the non-time-based field that is valid for the interval of the time-based field.
Supplementary Documentation - MGEFL 0002
Note
Field changes
The field can be changed on the fiscal year level (such as for a new fiscal year).
Time dependency
The field is always recorded as time-dependent. You can thus record different field contents for each time interval.
Supplementary Documentation - MGEFL 0003
Note
This is only a default value. It is used by the system when you select the cost center category during the master data maintenance of a cost center. If required, you can change this default value using the "Control" tab.
Supplementary Documentation - MGEFL 0009
Note
Field changes
You can change this field for each fiscal year. For example, you can change the field content for a new fiscal year.
Time dependency
The data in this field is always time-based.
Supplementary Documentation - MGEFL 0099
Note
Field changes
The data in this field can be changed daily.
Time dependency
You can define this field as time-based in the configuration menu of Cost Center Accounting.
- If you activate this indicator, you can maintain separate data for any number of different time intervals.
- If you do not activate this indicator, you can make only one field entry valid for all intervals. If, however, you change a time-based field, you can enter a new value in the non-time-based field that is valid for the interval of the time-based field.
Use
Procedure
Examples
Dependencies
History
| Last changed by/on | SAP | 19990629 |
| SAP Release Created in |
