Hierarchy

⤷

⤷

Basic Data
Data Element | /SAPSLL/VALTY_PRD_CP |
Short Description | Price Type for Preferential Statement of Finished Part |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | /SAPSLL/VAL_TYPE | |
Data Type | CHAR | Character String |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table | /SAPSLL/TCOVAL |
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 Type |
Medium | 18 | Price Type/Statem. |
Long | 25 | Price Type for Statement |
Heading | 20 | Price Type/Statement |
Documentation
Definition
Price type for preference statement of finished product.
Use
During the preference determination for a bill of materials, the originating and non-originating values of individual components in the bill of materials are determined and updated for the finished product (also called the leading part of an assembly). The system can assign one of the following preference statuses as the result of the finished product:
- Eligible for Preference
- Not Eligible for Preference
- Price-Influenced
The preference status Price-Influenced features a threshold value as a criterion.
Certain trade agreements require that the preference status of the finished product be set to Eligible for Preference or Not Eligible for Preference. Before you can set the status Price-Influenced, one more step is necessary:
You specify a price type for the preference statement of the finished product. When you do this, the price data under this price type for the finished product is applied for the status Price-Influenced. If the price under this price type meets the criterion for the given finished product, the system assigns the status Eligible for Preference to the finished product. Otherwise, the system assigns the status Not Eligible for Preference.
If a trade agreement does not have such a requirement, do not specify a price type for the finished product.
Dependencies
Price data, which is distinguished by price types, must exist for the finished product in the product master record.
However, if the leading part reflects a component in a higher-level bill of materials, the system continues the determination for the higher-level bill of materials using the same logic, as described above.
Example
NAFTA (North American Free Trade Agreement) using the "Net Cost Method" for comparisons.
History
Last changed by/on | SAP | 20141106 |
SAP Release Created in | 901 |