Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MCS (Package) R/3 application development: Logistics Information Warehouse
Basic Data
| Data Element | STAFO |
| Short Description | Update group for statistics update |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | STAFO | |
| Data Type | CHAR | Character String |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 6 | |
| Value Table | TMCB |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | MCF | |
| Default Component name | UPDATE_GRP | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Update grp |
| Medium | 15 | Update group |
| Long | 20 | Update group (stats) |
| Heading | 6 | UpdGrp |
Documentation
Definition
The update group is a control element in the updating definition, which allows all the different business events in the various applications to have a uniform influence on the statistics update in the Logistics Information System (LIS).
In an application, one update group is allocated to a specific business event or a group of business events. This update group is then used to determine the fields which will be created for the statistics.
The type of allocation and the organizational elements that determine how the allocation takes place vary from application to application.
Use
At present, you can use the update group to define how the application influences the statistics update in the following applications (information systems):
- Sales
- Purchasing
- Plant Maintenance
- Quality Management
- External data
Only one fixed update group each is permitted for all of the other respective information systems in Logistics.
All update groups that begin with numbers or with the letter "S" lie within the SAP name range.
Example
In sales processes, the following elements determine the update group:
- sales organization
- distribution channel
- division
- a group of customers
- a group of materials
- sales document type
- item type
In sales processes, a distinction is made between "normal" sales and so-called returns. These different types of business events are identified by various types of sales documents.
You want to save the order quantities from the various types of business event in different statistics fields in an information structure. This means that only the appropriate statistics fields will be updated when a "normal" sale takes place, and not those statistics fields in which the returns quantities are cumulated, and vice versa.
You can control these different updates by using two different update groups.
For example, assign the update group "000001" to the sales document types that represent the "normal" sales.
Assign the update group "000002" to the sales document types that represent a returns process.
If you define the update rules for the key figures in an information structure, always always make a reference to an update group.
If you define update rules for your information structure with reference to update group "000001", only define the key figures that are to be updated through "normal" sales.
Conversely, only refer the update group "000002" when defining those key figures that are going to be updated by the returns processes.
Key figures that are to be updated by both business transactions should be assigned to both update groups in the definition.
History
| Last changed by/on | SAP | 19981111 |
| SAP Release Created in |
