SAP ABAP Data Element UMM_Y_ADMIN_BUFFER_MODE (Mode for Manual Data Buffering)

Hierarchy

☛ SEM-BW (Software Component) SEM-BW: Strategic Enterprise Management
   ⤷ FIN-SEM-CPM-MC (Application Component) Management Cockpit
     ⤷ UMM (Package) SEM-CPM: Management Cockpit

Basic Data

Data Element	UMM_Y_ADMIN_BUFFER_MODE
Short Description	Mode for Manual Data Buffering

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	UMM_D_ADMIN_BUFFER_MODE
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
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Mode
Medium	15	Mode
Long	20	Data Buffering Mode
Heading	35	Mode for Manual Data Buffering

Documentation

Definition

Manner in which the data should be buffered.

Use

You have two settings to choose from:

• Read Values for Time Series Completely.
  When this setting is selected, the time series are buffered completely.
  Example: A frame is defined as a time series as follows: From-period = First period of current year; To-period = Current period. When you choose this mode, the values of all periods (that is, the values of the first period of the current year up to the current period) are written to the buffer. Thus the cockpit data that is required in the presentation for the selection of an earlier period than the current period is also buffered.
  This mode is preferable if the buffer is still empty, and is filled for the first time.
• Read Only Values for Current Period in Time Series
  When you select this option, only the data belonging to the current period is buffered for time series (when using an interval variable, it is replaced with the current period). In this case, you can buffer the data of specific periods (this is helpful, for example, for period-end closing).
  This mode is preferable if the buffer of a cockpit is already partly filled, and only the data of specific periods should be buffered.

Dependencies

With both buffering types, it is not possible to know exactly at what time the data was buffered for the cockpit (as it is displayed to the end user).

If you always use the second buffering type, you cannot be sure whether all (and not only part of) the necessary data has been buffered for a cockpit, as a cockpit generally presents data from more than one period.

Example

History

Last changed by/on	SAP	20041006
SAP Release Created in	3.1A