SAP ABAP Data Element SRMAISCNID (Integration Scenario)
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-RM (Application Component) SAP Records Management
⤷
SRM_INTEGRATION_BROKER (Package) Records Management - Application Integration Broker
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-SRV-RM (Application Component) SAP Records Management⤷
SRM_INTEGRATION_BROKER (Package) Records Management - Application Integration Broker
Basic Data
| Data Element | SRMAISCNID |
| Short Description | Integration Scenario |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | CHAR20 | |
| Data Type | CHAR | Character String |
| Length | 20 | |
| Decimal Places | 0 | |
| Output Length | 20 | |
| 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 | Scenario |
| Medium | 20 | RM Scenario |
| Long | 35 | RM Integration Scenario |
| Heading | 20 | RM Scenario |
Documentation
Definition
The purpose of the integration scenario field is to distinguish between different scenarios in which you want to integrate Records Management with applications.
Use
Each integration scenario has an RMS ID and the logical system in which Records Management is running assigned to it. This makes it possible, for example, to find the RFC destination and the RMS ID assigned to the logical system when creating a record from an application.
Example
An integration scenario could have the name personnel records/> and the scenario ID, Z_HR.
History
| Last changed by/on | SAP | 20041216 |
| SAP Release Created in | 700 |
