Hierarchy
IS-M (Software Component) SAP MEDIA⤷
IS-M (Application Component) SAP Media⤷
JSDI (Package) IS-M/SD SD Integration
Basic Data
| Data Element | ISMSPLIT_STATUS |
| Short Description | IS-M/SD: Mix Status |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR80 | |
| Data Type | CHAR | Character String |
| Length | 80 | |
| Decimal Places | 0 | |
| Output Length | 80 | |
| 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 | Status |
| Medium | 15 | Status |
| Long | 20 | Status |
| Heading | 40 | Mix Status |
Documentation
Definition
The traffic light icon indicating the status of the mixes of a media issue (main component of the product kit) has the following meaning:
Yellow: Mixes have not yet been created for the main component of the product kit.
Green: The media issue mix has been created and the alternative BOM corresponds to the current structure of the product kit.
Red: The mixes have been created for the media issue but the alternative BOM does not correspond to the current structure of the product kit. The product kit has been changed since the media issue mixes were created. The mixes for the media issue will have to be created again.
Background
From a technical point of view, the product kit is managed together with the media issue mix as an alternative BOM. The alternative BOM is created by the function Create Issue Mixes. For this reason, it is important to know whether the issue mixes have already been created and whether the product kit structure corresponds to the alternative BOM when maintaining product kits.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in | 463 |
