EXP_0021
14 pág.

EXP_0021


DisciplinaConsultoria921 materiais3.304 seguidores
Pré-visualização2 páginas
\ufffd
\ufffd
Conditions are stipulations agreed with vendors regarding prices, discounts and surcharges and suchlike. The system determines the effective net purchase price in POs on the basis of these pricing elements.
Conditions can be maintained when you enter or create quotations, info records, outline purchase agreements, and purchase orders.
MM Purchasing differentiates between the following prices:
Gross price: Price excluding any possible discounts or surcharges
Net price: Price taking discounts, surcharges, and possibly taxes into account
Effective price: Net price less or plus delivery (incidental procurement) costs, cash discount, and miscellaneous provisions for accrued costs or rebates.
Discounts or surcharges may be percentage-based, quantity-dependent, or absolute in nature.
You can also enter conditions that do not take effect immediately, at the time of individual transactions, but subsequently thereto, and which require settlement at the end of a predefined period.
In MM Purchasing, a distinction is made between conditions that are valid for a certain period (time-dependent conditions) and conditions for which no special validity period can be defined (time-independent conditions).
Prior to Release 4.0A, the term Master conditions was used in place of the term "time-dependent conditions", and the term Document conditions was used for "time-independent conditions".
\ufffd
Conditions in info records and contracts are always time-dependent. You can specify in Customizing (via the document type) whether time-dependent or time-independent conditions can be maintained in quotations and scheduling agreements. As of Release 4.0A, the standard settings are time-dependent conditions for both scheduling agreements and quotations.
Conditions in purchase orders are always time-independent conditions.
Time-dependent conditions can be stored on either a plant-specific or a cross-plant basis (in the latter case, for all plants belonging to a purchasing organization). You can also use conditions negotiated by another purchasing organization (reference purchasing organization).
In addition to time-dependent conditions that apply to individual info records, or quotation or outline agreement items, you can also define time-dependent conditions reflecting more general pricing arrangements (general conditions).
Time-dependent conditions can be limited to a certain validity period.
If a vendor's pricing varies according to the quantity purchased, you can enter it in the form of a price/quantity scale.
You can specify upper and lower limits for time-dependent conditions in order to prevent agreed maximum or minimum figures from being exceeded in the event that condition values are changed manually in the purchase order.
Valid time-dependent conditions from info records or outline purchase agreements are adopted as default values in purchase orders.
\ufffd
Item conditions are conditions relating to a single item of a document.
Header conditions are entered in the header of a document and relate to all the items of that document.
Some standard condition types can be used only as item conditions, some only as header conditions and others as both header and item conditions. Usage options are determined by the Header condition/Item condition switch in Customizing for the condition type.
No automatic price determination process is carried out for header conditions. For this reason, you cannot assign an access sequence to a header condition (except if it is also defined as an item condition) or create condition records for such a condition.
A condition type can be defined as a group condition in Customizing. A group condition is a condition relating to several items of a document. In the case of a group condition, the condition values (price, order quantities, weight or volume) of the relevant items are added and the total used as the condition basis. This allows more favorable values to be taken as a basis for the scale computation than would be the case if individual items were considered. The grouping of items is carried out using the key of the condition record for the group condition or by means of a group condition routine assigned to the condition type in Customizing.
\ufffd
The individual conditions are described by means of condition types. There are condition types for the gross price, various discounts and surcharges, freight charges, fixed costs and so on.
Condition types are defined together with their control parameters in Customizing.
Condition types are differentiated broadly using the condition class and more finely using the condition category.
The calculation type (or rule) stipulates how the R/3 System calculates the condition value. For example, a discount or surcharge can be a percentage of the gross price, a fixed amount or a quantity-dependent amount.
The plus/minus sign determines whether a condition is treated as a negative or positive amount. Negative amounts are discounts (deductions), positive amounts are surcharges (additions).
The scale basis (or reference magnitude) for scales also depends on the condition type. A scale can be based on quantity or dollar value, for example.
An access sequence may be assigned to a condition type. The access sequence is a search strategy that enables you to specify the order in which condition tables are to be searched for relevant entries for a condition type. In the standard R/3 System, no access sequences are assigned to the condition types for discounts and surcharges (RA00, RA01 and so on.) because they do not have separate validity periods. They are always maintained at the same time as the gross price (PB00) and their validity period is always the same as the validity period of the gross price.
You can define your own condition types.
\ufffd
Conditions are stored in the system as condition records.
Condition tables reference condition records. Condition tables enable you to vary the key structure of condition records.
There are condition tables with the following key fields
Vendor, material, purchasing organization, info record category
Vendor, material, purchasing organization, plant, info record category
Vendor, material, purchasing organization, info record category, order unit
Purchasing document, item, plant
Entries in condition tables consist of a key part and a data part. The data part contains the number of a condition record.
Condition records are stored in the following transparent tables
KONP (time-dependent conditions)
KONH (header conditions)
KONM (quantity scales)
KONW (value scales)
\ufffd
The access sequence is a search strategy defining the order in which condition tables are searched for relevant entries for a condition type. The order of accesses is determined by the order of the condition tables in the access sequence.
A vendor\u2019s gross price for a material can depend on a variety of factors. There are different condition tables with different combinations of key fields for the various price-influencing factors, for example:
Table A068 \u2013 for gross prices in plant-specific outline agreement items
Table A016 \u2013 for gross prices in the items of centrally agreed contracts
Table A067 \u2013 for order-unit-dependent gross prices in plant-specific material info records
Table A017 \u2013 for gross prices in plant-specific material info records
Table A018 \u2013 for gross prices in material info records
Table A025 \u2013 for gross prices in plant-specific non-stock-material info records (info records without a material number).
You can differentiate between gross prices, discounts and surcharges for different variants of a configurable material.
Requirement routines are used to determine the prerequisites by which the system searches certain condition tables for relevant entries. Some condition tables are accessed only if the document item fulfills certain criteria.
\ufffd
In MM, the framework