Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-ESI-SIW (Application Component) Service Implementation Workbench⤷
S_SIW_UI (Package) UI of Service Implementation Workbench
Basic Data
| Data Element | SIW_DTE_MAPPING_RDY_STATUS_TXT |
| Short Description | Status of the Mapping Readiness Check |
Data Type
| Category of Dictionary Type | Direct Type Entry | |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ||
| Data Type | CHAR | Character String |
| Length | 60 | |
| Decimal Places | 0 | |
| Output Length | 60 | |
| 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 | Map.Cmpl. |
| Medium | 17 | Mapping complete |
| Long | 20 | Mapping complete |
| Heading | 55 | Mapping complete |
Documentation
Definition
Indicates if the mapping is complete from a formal point of view.
Formal requirements are all checks which can be performed locally as, for example, the consistency of ES Repository type descriptions, completeness and validity of field and types names and such.
The status is only provided for the service creation types API-based.
Use
The following overall statuses exist:
@00@ Undetermined -
No status could be determined since no mapping activity has been done so far.
@5B@ OK -
The mapping is formally correct.
@5D@ Warning -
The current mapping information does not prevent a successful ES Repository generation but should be revised as it does not meet formal requirements like naming conventions.
@5C@Error -
At least one mapping node is erroneous.
Dependencies
The extended ESR mapping check statusperforms the real check against the ES Repository.
Example
History
| Last changed by/on | SAP | 20110908 |
| SAP Release Created in |
