2. info records
3. outline agreements (contracts & scheduling agreements)
4. purchase orders
2. conditions in a purchasing info record (apply to all PO items that contain material and vendor in PIR)
3. general conditions (display price agreements that don’t apply to individual quotations, outline agreements, PO’s, and info records)
ex of a condition type: ZA01, PB00, etc
3. quantity dependent
can be assigned to condition type
-provides framework for price determination by defining the sequence in which condition types are taken into account
-can define diff calculation schemas, like for individual purch orgs and vendors
2. extent to which manual processing of price determination is possible
3. basis (reference level) on which the system calculates surcharges/discounts in percentages
4. prereqs that must be fulfilled so that a particular condition type is taken into consideration
2. Vendors send quotations or rejections. The vendor’s price and and deliv date specs are entered directly into original RFQ in a transaction for quotation maintenance. Makes RFQ–>quotation
3. determine the most favorable items or quotation using a quotation comparison. can also save the conditions for the shortlisted quotations in a PIR.
-cannot save vendor specific data in the master record for one time vendors
-use a one time account group
-have to enter other info like address for PO or bank info for invoice manually
-entered info is saved only in the relevant docs and not in the one time vendor master record
-save quotation data for a material in a PIR; can do this automatically by setting the Info update checkbox during quotation maintenance on Item Details screen
item data and any existing header data is copied. can change most of it in the PO if necessary.
2. Purch Reqs
-display additional fields from column set or hide them
-arrange the fields
-create cross-user and user-specific layouts
-define one of your layouts as a default setting using the manage layout function
2. delivery data (planned deliv time and over deliv/under deliv tolerances)
3. vendor data (such as contact person) and vendor specific data about the material
4. number of last PO
internal comment that the system transfers to PO item. never printed on PO– just a note for the purchaser.
2. PO text
system uses this text to describe the PO item. system transfers it to PO item and prints it. can be in addition to or instead of text in material master.
general- vendor data, original data, PO unit, info record memo, admin data
purch org- control, prices, stats, PO text
2. purchasing org specific and plant specific data
purch org & plant- control, prices, stats, PO text
when you create a PO, system searches for an info record for the vendor or material combo at purch org and plant level. if none, system searches at PO level. if no data again, must enter price manually.
*in the PO, valuation price from material master is not proposed as PO price*
-if PIR doesn’t have conditions, or they’re all invalid, the system reads the number of the last purch doc in info record and proposes the price from that. buyer can change when making the PO.
*can define how system handles conditions from last PO in the default values for buyers (customizing)
-conditions are not copied if the price is entered manually
-conditions are never copied
-can also create and update PIR automatically by setting the InfoUpdate checkbox when maintaining a quotation, PO, or outline agreement
conditions are transferred to the info record
a contract release order or scheduling agreement, the document and item number is updated as the last doc
it’s important to know whether an info record already exists for the vendor material combo. when you create or change a contract, the system creates a PIR with the conditions from the contract if there are no existing PIRs for that combo of vendor/material/org level. if one already exists then it is not updated.
2. if an info record exists with purch org data or purch org and plant data, the plant specific data is updated
3. if no info record exists and the plant condition req has been specified in customizing, the system creates an info record with a plant. otherwise, the system creates an info record without a plant
-shows connection btw mm and fi because material valuation accesses and updates G/L accounts
so, stock value changes when stock q or val price change
2. material master record
2. Which types of goods movements are relevant for valuation? (movement type + material determine this)
3. Which accounts are posted to during a transaction? (settings for auto account determination establish this)
at cc level, valuation data of a material is created separately for each cc. price ctrl and valuation price of a material are valid for each cc, so the material is valuated consistently in all plants within the cc.
2. valuation area = plant (recommended)
at plant level, valuation data of a material is created per plant, and the price ctrl and valuation price of a material are valid for each plant. so, same material could be valuated differently in each plant.
when entering acct data, must answer:
2. Is the stock of a material valuated at a constant price, or should the price be adjusted to match the fluctuations of the cost price?
2. valuation class combines materials for assigning g/l accounts so you don’t have to manage a separate stock account per material. seen in FI view of material master.
3. valuation classes for material depend on material type (configured in customizing). can also assign a valuation class to multiple material types.
-standard price OR moving average price
-variances to the standard price are posted to the price difference accounts
-if there is sufficient stock coverage, differences btw the PO price and invoice are posted directly to the relevant stock account, changing the moving average price of the material
will have to debit or credit a price diff account sometimes with standard price
when incoming invoice is posted, GR/IR is cleared at order price and vendor account is updated at invoice price, then difference between order and invoice prices gets posted to a price differences account (if standard pricing); stock account or price diff acct if it’s a loss (if moving avg)
can display stock overview for batches or valuation type and special stocks (like consignment) and also the stock overview for org units.
2. quality inspection stock (available from MRP perspective but no withdrawals for consumption possible)
3. blocked stock (not avail for MRP and no withdrawals– damaged or unsellable)
can withdraw from one sample, scrap a quantity, or post an inventory difference
-material doc generated
-no acct doc for stock to stock
-acct doc if movement is relevant to valuation
2. material doc
3. update stock and consumption accounts
5. transfer req for WH mgmt (if active)
6. update PO and PO history
7. output (GR slip; optional)
8. notification of the orderer (optional)
costs have separate condition types in PO, and when you post the GR, the system makes postings to separate clearing accounts for those expenses
advantage: system includes them in the valuation of the material at the time of GR
if needed, system will correct material valuations that happened at time of GR and balances out differences when invoice is received