SAP ABAP Data Element VFPPR (Availability check for sales)
Hierarchy
☛
BBPCRM (Software Component) BBPCRM
⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions
⤷
VA (Package) Application development R/3 Sales
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VA (Package) Application development R/3 Sales
Basic Data
| Data Element | VFPPR |
| Short Description | Availability check for sales |
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 | AvailCheck |
| Medium | 15 | Availability |
| Long | 20 | Availability check |
| Heading | 3 | AvC |
Documentation
Definition
You must carry out an availability check for the following transaction.
The indicator is determined as a proposal in conjunction with the respective requirements type. It can be changed in individual shipping transactions. However, only one restriction is effective.
Example
You do not set an indicator for maintaining the requirements type. In this case, no availability check is carried out. This is independent of the selection in the respective transaction.
You set an indicator for maintaining the requirements type. In this case you can decide whether or not you require an availability check for the relevant transaction.
History
| Last changed by/on | SAP | 19950403 |
| SAP Release Created in | 470 |
