SAP ABAP Data Element KNPR2 (2nd pricing type)
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 | KNPR2 |
| Short Description | 2nd pricing type |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | KNPRS | |
| 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 | PriceType2 |
| Medium | 15 | 2nd pricing typ |
| Long | 20 | 2nd pricing type |
| Heading | 4 | PrTy |
Documentation
Definition
In the invoice correction request, two items are automatically created for each item in the invoice to be copied:
- first item: credit memo item
- second item: debit memo item
A particular pricing type is needed for the second item.
- You have to use pricing type 'E' for the credit memo item to guarantee that the item will not be changed.
- You should give a new pricing type to the debit memo item. The system creates a credit or debit memo depending on whether a postive or negative difference is generated.
History
| Last changed by/on | SAP | 19970812 |
| SAP Release Created in |
