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 | NADDFIELDS |
| Short Description | IS-HCM: Indicator for Additional Fields in Customer Segment |
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 | 8 | Add. F. |
| Medium | 15 | Addit. Fields |
| Long | 20 | Additional Fields |
| Heading | 3 | AdF |
Documentation
Definition
By selecting this indicator you specify that in addition to the original SY fields, new customer-specific fields were inserted when the customer-specific message segment was created.
Only if these extra fields have to be updated in addition to the original batch input should this indicator be selected.
If this indicator is set, it is indispensable that an inbound pool has been specified for this segment. Within this inbound pool there has to be a FORM routine called kknnnVvv_ADDFIELDS (where kk is the owner code, nnn the message segment number, and vv the version. For version 1.3, for example, vv corresponds to "13").
Here, it is necessary to assign the additional segments (and these only - the other segments have already been assigned) to the corresponding (additional) batch input fields.
Dependencies
This indicator controls that a standardized user exit is called when inbound messages are being processed.
If the batch input functionality has been extended (additional RNBInnnn fields, where nnnn is the transaction code), a standardized user exit is an essential requirement for the system to support additional fields
For a detailed description of how to create such user exits, please refer to the Implementation Guide and the documentation of the SAP template program RNCZIN00.
History
| Last changed by/on | SAP | 20050224 |
| SAP Release Created in |
