Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
MG (Package) Application development R/3 material master prior to 3.0
Basic Data
| Data Element | VJSTP |
| Short Description | Standard price in previous year |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WERT11V | |
| Data Type | CURR | Currency field, stored as DEC |
| Length | 11 | |
| Decimal Places | 2 | |
| Output Length | 15 | |
| Value Table |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | STD_PR_PY | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Std price |
| Medium | 15 | Std price PY |
| Long | 20 | Standard price |
| Heading | 15 | Standard price |
Documentation
Definition
Standard price valid at the last balance sheet key date.
Dependencies
The following fields serve as a basis for postings to previous periods or for balance sheet valuations:
- Price control indicator for the previous year
- Standard price in the previous year
- Moving average price in the previous year
Technical Information
As of Release 4.5, stock fields and valuation fields relating to the previous period or to an earlier period are stored in history tables (for example, MBEWH, MARDH, MCHBH), and no longer in those tables in which the current stock data is stored (for example, MBEW, MARD, MCHB).
These history tables can contain one entry for each period. An entry is created in the history table only if the stock-relevant data or valuation-relevant data changes. The value of the entry relates to the end of the period. The history tables do not contain any entries for the current period.
Example
Scenario
At the start of period 02, there are 10 pieces of material 4711 in stock.
Goods receipt
5 pieces are received in period 02.
System response
The system records a stock of 10 pieces in the history table for period 01. At the same time, the system increases the current stock to 15 pieces.
Goods receipt
2 more pieces are received in period 02.
System response
The history table is unaffected by this event because an entry already exists for period 01. The system increases the current stock to 17 pieces.
Goods issue
4 pieces are withdrawn from stock in period 04.
System response
The system records a stock of 17 pieces in the history table for period 03. At the same time, the system reduces the current stock to 13 pieces. (The history table does not contain an entry for period 02 because there were no goods movements in period 03.)
Rules
- If the history table does not contain an entry for the previous period, the values for the previous period are the same as those for the current period.
- If the history table does not contain an entry for a period n that precedes the previous period, the values for period n are the same as those for period n+1.
Since the second rule can be applied recursively, it is possible to determine (in accordance with both rules) the values for any periods as of the period in which Release 4.5 or a subsequent release was implemented.
History
| Last changed by/on | SAP | 19971006 |
| SAP Release Created in |
