SAP ABAP Data Element KZDELIVER (IS-HCM: Indicator for Express Dispatch)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NBAS (Package) Appl. development Hospital System master data, catalogs
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ NBAS (Package) Appl. development Hospital System master data, catalogs
Basic Data
Data Element | KZDELIVER |
Short Description | IS-HCM: Indicator for Express Dispatch |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
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 | Express |
Medium | 15 | Xpress Dispatch |
Long | 20 | Express Dispatch |
Heading | 1 | E |
Documentation
Definition
This indicator specifies that express dispatch (synchronous transfer of data) is supported
- for a system (TN02S) or
- for an event (TNCD0).
Express dispatch means that the data is transferred synchronously to a subsystem by means of a call to a function module.
The transferring point must however wait until the data arrives in the receiving system. Consequently you should set this indicator in table TN02S only for systems which require the data urgently and cannot wait for it to be transmitted normally via HCM. You should also keep the number of events in table TNCD1 which trigger express dispatch to a minimum.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |