SAP ABAP Data Element NTRABR_VS_NTR (Ind: Sub. Sales Update Vendor Settlement Not Active)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM (Application Component) Customer Relationship Management
⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
⤷ WBON (Package) WWS: Bonus
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
WBON (Package) WWS: Bonus
Basic Data
| Data Element | NTRABR_VS_NTR |
| Short Description | Ind: Sub. Sales Update Vendor Settlement Not Active |
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 | Subs. Upd. |
| Medium | 15 | Subseq. Update |
| Long | 20 | Subsequent Update |
| Heading | 20 | Subsequent Update |
Documentation
Definition
Using this indicator, you can define that you do not work with the function subsequent settlement business volume update as part of subsequent settlement with vendor settlements.
Use
If you set this indicator, then no index data is created on saving of vendor settlement documents. Since program sections are omitted, performance is normally improved.
You can set this indicator if you are working exclusively with condition types that are independent of business volume.
Dependencies
Example
History
| Last changed by/on | SAP | 20100310 |
| SAP Release Created in | 604 |
