Hierarchy
BI_CONT (Software Component) Business Intelligence Content⤷
BW-BCT-PLA-RAP (Application Component) Retail Assortment Planning⤷
UPARM (Package) Retail MAP Master Data Maintenance
Basic Data
| Data Element | UPARM_Y_IOBJ_GROUP |
| Short Description | Grouping InfoObject for an Assignment View |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | UPC_IOBJNM | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| 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 | Group IO |
| Medium | 17 | Group InfoObject |
| Long | 20 | Group InfoObject |
| Heading | 30 | Group InfoObject |
Documentation
Definition
This is the grouping info object in an Assignment view scenario or in a Browse and Collect view scenario. It defines the range of valid values for the reference info object. For this relationship to work, the grouping info object must be defined as a compound key or an attribute of the reference info object.
Only an existing info object defined as an attribute of a reference info object is accepted.
- In Assignment view scenario, the grouping controls the number of assignment columns that will be displayed.
- In Browse and Collect view scenario, the grouping changes the number of available choices in the dropdown list of assignment.
Use
Dependencies
Example
For example, the grouping info object 0RT_CHARRNG groups several values of reference info object 0RT_COLOR. This relationship works because 0RT_CHARRNG is an attribute of 0RT_COLOR.
You can also refer to the following views as examples:
- 0RAP_RANGE_PLAN to see how the grouping is used in a Browse and Collect scenario
- 0RMP_V3_STYCO_A to see how the grouping is used in an Assignment scenario
History
| Last changed by/on | SAP | 20141031 |
| SAP Release Created in | 703 |
