SAP ABAP Data Element ISH_RUNNR (_)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NNL1 (Package) Application development Hospital System Netherlands
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
NNL1 (Package) Application development Hospital System Netherlands
Basic Data
| Data Element | ISH_RUNNR |
| Short Description | _ |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | ISH_RUNNR | |
| Data Type | NUMC | Character string with only digits |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | _ |
| Medium | 15 | _ |
| Long | 20 | _ |
| Heading | 2 | _ |
Documentation
Definition
Especially for the 'Specialist' billing parties a distinction between the 'first' specialist and the 'second' specialist (=anaesthesist) is necessary. This distinction is made by using the running number, running number 1 is related to the main or actual specialist and running number 2 is related to the anaesthesist or second specialist.
With the help of this running number it is possible to create a unique billing component for each billing party involved.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
