SAP ABAP Data Element OUTPOOL (IS-HCM: FORM Routine Pool for Outbound Msg. Formatting)
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

⤷

⤷

⤷

Basic Data
Data Element | OUTPOOL |
Short Description | IS-HCM: FORM Routine Pool for Outbound Msg. Formatting |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | PROGNAME | |
Data Type | CHAR | Character String |
Length | 40 | |
Decimal Places | 0 | |
Output Length | 40 | |
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 | Out. Pool |
Medium | 15 | Outbound Pool |
Long | 20 | Outbound Pool |
Heading | 40 | Outbound Pool |
Documentation
Definition
With customer-specific message segments, you can include in the normal HCM processing a special FORM routine (user exit) for retrieving, editing or updating segment-related data.
For outgoing messages, this routine runs after data has been transferred from the original SAP structure. Data retrieval from the database is based on this. Data which does not exist in the original SAP structure must be filled within the customer FORM routine selecting the data from the database.
The name of the FORM routine and the FORM routine pool which contains the routine must also be specified for the segment attributes. Afterwards, you have to regenerate the customer structures.
History
Last changed by/on | SAP | 20050224 |
SAP Release Created in |