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 | INPOOL |
| Short Description | IS-HCM: FORM Routine Pool for Inbound Message 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 | In. Pool |
| Medium | 15 | Inbound Pool |
| Long | 20 | Inbound Pool |
| Heading | 40 | Inbound 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 incoming messages, this routine is run prior to the data being transferred into the original SAP structures. The writing of the incoming data to the IS-H database is also based on this routine. As long as no additional fields need to be processed, all actions can be performed with this user exit (compare with the ADDFIELDS exit below).
The name of the FORM routine and that of the FORM routine pool in which the routine can be found must also be specified for the segment attributes. Afterwards, you must regenerate the customer structures.
Note that if only the ADDFIELDS FORM exists, you need only specify the incoming pool. If both exits are to be used, they must both be implemented in the same program.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
