SAP ABAP Data Element FEHGR (Incompletion procedure for sales document)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ VBAS (Package) Application development R/3 sales master data
⤷ CRM (Application Component) Customer Relationship Management
⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ VBAS (Package) Application development R/3 sales master data
Basic Data
Data Element | FEHGR |
Short Description | Incompletion procedure for sales document |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | FEHGR | |
Data Type | CHAR | Character String |
Length | 2 | |
Decimal Places | 0 | |
Output Length | 2 | |
Value Table | TVUV |
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 | IncompProc |
Medium | 15 | Incompl.proced. |
Long | 25 | Incompletion procedure |
Heading | 6 | InProc |
Documentation
Definition
The number that uniquely identifies the incompletion procedure. The incompletion procedure defines a number of fields in which the user must enter information.
Use
The system uses the incompletion procedure to determine which fields appear in the incompletion log when the user does not enter information during sales order processing. In SD Customizing, you can specify an incompletion procedure for each type of sales document.
Example
Validity periods and customer purchase order numbers are required entries for both contracts and scheduling agreements. In this case, the system automatically proposes the same incompletion procedure for both types of document.
History
Last changed by/on | SAP | 19991102 |
SAP Release Created in |