Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BTX-BF-IF (Application Component) R/3 Interface for Business Transactions⤷
VZ (Package) Application development R/3 RV central functions
Basic Data
| Data Element | UVPRS |
| Short Description | Incomplete with respect to pricing |
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 | Pricing |
| Medium | 15 | Pricing |
| Long | 20 | Pricing |
| Heading | 5 | Price |
Documentation
Definition
Indicates whether the system records a status message about pricing information in the header and item status screens of a sales document.
Use
If you mark this status for a particular status group, the system determines the status of pricing information by checking the status of fields that are assigned to the status group in the relevant incompletion procedure. If some or all of the fields are missing information, the status message says that the pricing information is, respectively, partially incomplete or incomplete.
Example
You can specify, for example, that an item in a credit or debit memo request is incomplete if pricing has not been carried out. If you try to process the credit or debit memo request without pricing information, the system records an appropriate status message.
History
| Last changed by/on | SAP | 19920519 |
| SAP Release Created in |
