SAP ABAP Data Element BS_INOB_REPORTER_TYPE (Reporter of a Scene in Incident Observation)
Hierarchy
☛
SAP_BS_FND (Software Component) SAP Business Suite Foundation
⤷
CA-MDG-APP-BP (Application Component) MDG Business Partner (Central Part)
⤷
BS_COMMON_OBJECTS (Package) Common Tools and Interfaces
⤷
⤷
Basic Data
| Data Element | BS_INOB_REPORTER_TYPE |
| Short Description | Reporter of a Scene in Incident Observation |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | SEOCLSNAME | |
| Data Type | CHAR | Character String |
| Length | 30 | |
| Decimal Places | 0 | |
| Output Length | 30 | |
| Value Table |
Further Characteristics
| Search Help: Name | SEOCLSNAMEF4 | |
| Search Help: Parameters | CLSNAME | |
| 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 | Reporter |
| Medium | 15 | Reporter |
| Long | 20 | Reporter |
| Heading | 30 | Reporter |
Documentation
Definition
A reporter in Incident Observation (IO) is any kind of ABAP OO reference. To allow only apposite references each IO-scene defines so called reporter admittances by listing only those kind of references it accepts reports from. A reporter here is always defined by the name of an ABAP OO interface or class. Whenever an ABAP Object instance tries to establish itself as a reporter for a scene the observation center declines this attempt if the object does not meet any of the given reporter admittances.
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 731 |