SAP ABAP Data Element B_PRDAT_NEW (Date of Pricing (Limitation New Structure))
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷
MM-PUR-PO (Application Component) Purchase Orders
⤷
WIND (Package) Document index processing
SAP_APPL (Software Component) Logistics and Accounting⤷
MM-PUR-PO (Application Component) Purchase Orders⤷
WIND (Package) Document index processing
Basic Data
| Data Element | B_PRDAT_NEW |
| Short Description | Date of Pricing (Limitation New Structure) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DATUM | |
| Data Type | DATS | Date field (YYYYMMDD) stored as char(8) |
| Length | 8 | |
| Decimal Places | 0 | |
| Output Length | 10 | |
| 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 | Price date |
| Medium | 15 | Price date |
| Long | 20 | Price date |
| Heading | 10 | Price date |
Documentation
Definition
Date on which the system last determined the net price.
Use
This date is used to limit the number of entries for purchase orders/ delivery schedules when the document index is being restructured.
For technical programming reasons - the price determination date is not stored on the database - you have to let the report run for a huge quantity of purchase orders/delivery schedules.
The limit prevents entries that are not required being written into the database. This shortens the report runtime and reduces the volume of data.
Example
If your volume-rebate arrangements (subsequent settlement) is valid for the calendar year 2001, then you only need to make entries with price determination dates from 01.01.2001 to 31.12.2001.
History
| Last changed by/on | SAP | 20010607 |
| SAP Release Created in | 470 |
