Hierarchy
⤷ SLL-LEG (Application Component) Global Trade Services
⤷ /SAPSLL/LEGAL_CON_REX (Package) Legal Services: Legal Control: Re-Export
Basic Data
Data Element | /SAPSLL/VALTY_CMP_SV |
Short Description | Price Type for Components Without Proportional Value |
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 | 15 | Price Type |
Long | 25 | Price Type w/o Prop.Value |
Heading | 25 | Price Type w/o Prop.Value |
Documentation
Definition
Price type for components without proportional values.
Use
During the re-export calculation for a bill of materials, the proportional 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 relevant proportional value for each component can be stored as re-export data in the product master.
Depending on the settings on how the calculation should react to missing re-export data for a component, the system can apply the price data for the component from the plant segment in the feeder system as the proportional value for the calculation. In this case, you specify a price type for the components so that the price data under this price type is applied as the proportional value for a component in the calculation if no re-export data is available for the component.
If a component already has re-export data, the system uses the proportional 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.
Dependencies
Each component can have different price data, which is distinguished by price types, in the product master record.
If the specified price type has no price data, the calculation routine can either flag the finished product as always relevant for checking or it can ignore the component with the missing price data.
On the other hand, if the leading part is used as a component by a higher-level bill of materials, the calculation 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 |