Hierarchy

⤷

⤷

Basic Data
Data Element | /SAPSLL/VALTY_CMP_OR |
Short Description | Price Type for Components With Preferential Origin |
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 | Prc.Type-Pos.Comp. |
Long | 25 | Price Type-Pos.Component |
Heading | 20 | Price Type-Pos.Comp. |
Documentation
Definition
Price type for components with preferential origin.
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). Each component can have different price data, which is distinguished by price types, in the product master record.
Specific price data is applied in the preference determination, depending on the trade agreement.
Specify a price type for components with preferential origin. When you do this, the determination routine applies the price data of the price type for a component if the component has a preferential origin.
If a component has no preferential origin, the system uses the non-originating value for this component for the calculation of the finished product. In this case, the price data under this price type is ignored for the component.
If a component has its own assembly and therefore has the preferential status "Price-Influenced" along with a threshold value as a criterion, the system then checks whether the price data under the given price type of the component meets that criterion. If the criterion is met, the system applies the price data under the price type as the originating value in the calculation of the finished product. If the criterion is not met, the system applies the originating and non-originating values for this component for the calculation of the finished product. In the latter case, the price data under this price type is ignored for the component.
Dependencies
The result of the determination is saved for the leading part of the assembly.
On the other hand, if the leading part is used as a component by a higher-level bill of materials, the determination for the higher-level bill of materials proceeds using the same logic.
Example
The price type for material prices.
History
Last changed by/on | SAP | 20141106 |
SAP Release Created in | 901 |