David's Untitled Life

Info record for material group

Sat, 15 Aug 2009 02:19:37 +0100

Info record can be created not only for material but also for material group.

This is used for consumed material or non-stock material purchasing.

Just input vendor/purchasing organization and leave the material field blan, then enter, SAP will require you to key in material group

https://forums.sdn.sap.com/message.jspa?messageID=7364347

basic procedure for physical inventory

Thu, 30 Jul 2009 22:18:56 +0100

MI01 Creating of Physical Inventory Document
MI21 Print of Physical Inventory Document
MI04 Entering the count
MI11 Recount if necessary
MI20 Difference List
MI07 is posting the difference.

Maintain Plant

Sat, 13 Jun 2009 02:14:54 +0100

http://www.sap-img.com/materials/sap-mm-configuration-tips.htm

Maintain Plant

Plant 0001 is the SAP default.

OX14 - Define Valuation Area (Tick one only- Once your system go live, no more changes)
Most company take the SAP recommended choice - Value Material Stock at Plant level
Value Material Stock at Plant or Company Level

- If you valuate material stocks at plant level, the plant is the valuation area.
- If you valuate material stocks at company code level, the company code is the valuation area.
- The decision you make applies to the whole client.

OX10 - Create / Change / View Plants

OVXB - Create / Change / View Division

OX18 - Assign Plant to company code
e.g. 0001 - 0001 - All Plants
Px1 - Plant Px1
Px2 - Plant Px2
OX19 - Assignment of company code to the Controlling Area

OB38 - Assign company code to Credit Control Area

OMJ7 - Assign business area to Plant/Valuation area and division
e.g. Plant Px1 - Business Area Bx1
Bx2
Assign Valuation area to the Business Area
.e.g. Valuation area Vx1 - Business Area Bx1
Business Area Bx2

OMS0 - Assign Factory Calendar to the Plant and Business Area

The plant plays an important role in the following areas:

Material Valuation - If the valuation level is the plant, the material stocks are valuated at plant level. Each plant can have its own material prices and account determination.
Inventory Management - The material stocks are managed within a plant.
MRP - Material requirements are planned for each plant. Each plant has its own MRP data. Analyses for materials planning can be made across plants.
Production - Each plant having they own production/planning.
Costing - In costing, valuation prices are defined only within a plant.
Plant Maintenance - If a plant performs plant maintenance planning tasks, it is defined as a maintenance planning plant. A maintenance planning plant can also carry out planning tasks for other plants (maintenance plants).

If you want to use the application PP (production planning) or product costing and job-order costing, you must set valuation at plant level.

The valuation level that you choose affects

the maintenance of material master records
the G/L accounts in which material stocks are managed
the G/L accounts to which transactions are posted in Materials Management

Effect on the maintenance of material master records:

Depending on the valuation level chosen,

you maintain accounting data in the material master record for each plant or for each company code
you define a valuation price for the material in each plant or in each company code

Effect on G/L accounts:

If material stocks are valuated at company code level, all plant stocks of a material are managed in a joint stock account for each company code.
If material stocks are valuated at plant level, you can manage the material stocks for each plant in different accounts. For each plant, you can define a separate determination.
If several plants are to use account determination, you can group these plants in "Valuation and Account Assignment" Customizing.

Material Master - Introduction

The material master is the starting point for the rest of the modules.

What Material Types are there?

The material types that you use are configured in Customizing for the Material Master under

Logistics Master Data : Material Master -> Material -> Control data -> Define material type attributes.

The following list shows you the material types contained, for example, in the standard SAP R/3 System, and what their different roles are:

DIEN (services)
Services are procured externally and cannot be stored. A material master record of this material type can always contain purchasing data.

FERT (finished products)
Finished products are produced by the company itself. Since they cannot be ordered by Purchasing, a material master record of this material type does not contain purchasing data.

FHMI (production resources/tools)
Production resources/tools are procured externally and used in the manufacture of products. A material master record of this material type can contain purchasing data, but no sales data. It is managed on a quantity basis. Examples of production resources/tools are apparatus, equipment, and measuring and testing devices.

HALB (semifinished products)
Semifinished products can be procured externally (sub-contracting) as well as manufactured in-house. They are then processed by the company. A material master record of this material type can contain both purchasing and work scheduling data.

HAWA (trading goods)
Trading goods are always procured externally and then sold. A material master record of this material type can contain purchasing and sales data.

HIBE (operating supplies)
Operating supplies are procured externally and required for the manufacture of other products. A material master record of this material type can contain purchasing data but no sales data.

NLAG (non-stock material)
Non-stock material is material that is not held in stock because it is consumed immediately. (Office supplies such as stationary. You need to create purchase order and accounting document for payment but the stock balance is always zero as it is issued out immediately to the various department.)

ROH (raw materials)
Raw materials are always procured externally and then processed. Since raw materials cannot be sold, a material master record of this material type contains no sales data.

UNBW (non-valuated materials)
Non-valuated materials are managed on a quantity basis, but not by value.

VERP (packaging materials)
Packaging materials are used to transport goods and come with the goods free of charge. A material master record of this material type is managed both on a quantity basis and by value.

WETT (competitive products)
Competitive products have their own material master records created from the Basic Data view. The competitor's number, which is stored in the material master record, assigns the material to a particular competitor.

Maintain the Material Type

OMS2 - Material Type Maintenance - Create/Change/Display

Steps:-

transaction OMS2
click Change
key in the Material Type you want to change e.g. FERT then hit enter

The Views belows allows you to choose the Views for each Material Type.
(Press the Page up/Page Down keys to scroll the views)

If you tried to change from FERT to HAWA in 4.6x, you will receive an error message :-
The material type cannot be changed. This is not allowed if only external procurement is defined for the new material type, or if the new material type has a different account category reference than the old material type.

To overcome it, goto OMS2 and change the HAWA material type.
In the Internal/external purchase orders sections:
Original Changes
Ext. purchase orders 2 1
Int. purchase orders 0 1

Screens in Material Master

MM01 - Create, MM02 - Change, MM03 - Display and MM06 - Flag for deletion.
MM04 - Display the changes done to the material master.
MMAM - Change the Material Type. for e.g. from FERT to HALB

Configure the Material Master Screen MM01 / MM02 / MM03

OMSR - Assign the field to the field group
OMS9 - Maintain the data screen field

Unit of Measure

In the material master, there is a Units of measure button for users to store in the different conversion rate. This sample program (ZUNT) extract the data from the unit of measure conversion table.

In the Material Master the moving average price are affected by:-

Goods Receipt for Purchase Orders
Transfer from Plant to Plant
Invoice Receipt
Settlement
Price Change

Common configuration changes-

define new material group (OMSF)
define new valuation class (OMSK) and automatic posting (OBYC)
define new material account assignment group (transaction OVK5) and
Customer/Material/Account keys (transaction VKOA)

Block materials from inventory posting

After blocking, when the user do a inventory posting, they will get this error message :-

E: Material xxxxx has status Blocked for procmnt/whse

To activate the blocking :-

Goto transaction MM02 - Purchasing View

Type in 01 at the MM/PP status field and save it

Create Delivery Log - Material xxx is blocked

During the Create Delivery (VL01), SAP prompt you a log that Material xxx is blocked.

During the Sales Order Create/Change for that material, there might be some update termination that causes the locked of the material (Windows hanged or power failure).

You can check using transaction SM12 - type an "*" at the User name field.

Check whether the material is in the locked list.

If it is in the locked list, asked the user to log out before you delete it from the locked list.

Maintain Storage Location

MMSC - Collective entry of Storage Location for a material.

Insert new or delete un-used Storage Location.

Maintain whether the storage location was included or excluded from MRP run.

Block Storage Location from further posting

1. You can block the storage location of a material without affecting the rest of the location using the same material.
Create a Physical Inventory document for the storage location with transaction MI01

Select the Posting Block checkbox.
This would prevent transactions from occuring until you either post or delete the physical inventory document.
(There are no impact, unless you do a post difference for the physical inventory document.)

2. Another method is to rename the storage location name.

Go to transaction OX09
Edit -> Copy as (copy the original storage location to a new name, replacing the first character e.g. ZXXX)
Edit -> Delete (delete the original storage location)

Do the reverse if you want back the original storage location.

Accounting document number range for MM

Transaction OMW9

Document Type - Double click on desire transaction code to check the document type for number range.
(e.g. MR21 Document type - PR)

Financial accounting document type - Assign the document type to a number range and account type.
(e.g. PR - Account type allowed for posting will be MS)

Double click on the document type PR.
Assign an unique starting number range that was not used. e.g. 88
Choose the Account type for Material and G/L account (MS)
The rest of the fields are optional (you can leave it as blank)

SAP definitions for account type -

A - Assets
D - Customers
K - Vendors
M - Material
S - G/L accounts

Number ranges for financial accounting document type - Assign the number range to the running number range.

No. Year (till) From number To number Current number Ext (no tick internal or tick external)
88 9999 8800000000 8899999999 Track by SAP Blank

Accounting document will be generated if there are stocks during price change, if you don't have any stocks, no accounting document will be generated as there are no inventory to revaluate for price differences.

Valuation Class for Material Group

In 4.6x and 4.5b, you can assign valuation class to Material Group.

It is useful in the sense that user do not have to manually do an Account Assignments.

For stock items, valuation class cannot be changed whenever the stock on hand is not zero.

Valuation class are tied to a G/L account.

A change of valuation class means a change of G/L account.

In FI concept, you have to debit and credit to balance the G/L account. That is why your stock must be zero before the system allows you to changed the valuation class. If it is not zero, you have to either transfer it to another material or do a dummy issues. After changing the valuation class, do a reversal entries for the stocks which you have transfer out or you have done a dummy issues.

IMG - Material Management -> Purchasing -> Material Master -> Entry aids for items without a Material Master

G/L Accounts in MM Account Determination

The program RM07C030 check all the G/L account define in your Material Master valuation class.

Search is via Company code and Valuation area.

Compare fields status for movement types against General Ledger

Use SA38 then run RM07CUFA

Split valuation

Mon, 11 May 2009 05:56:04 +0100

http://www.mediafire.com/?nmk0wil3wlr

Supplementary Condition以及purchase pricing FAQ

Fri, 03 Apr 2009 23:15:12 +0100

如果有一些价格条件是依附于特定物料的，则我们可以使用Supplementary condition。一般它都用来计算surcharge和discount. 因为supplementary condition是依附于main condition也就是说与main condition有同样的有效期间，而且condition type都不会分配access sequence. 具体的配置方法是在main condition type编辑画面，分配supplementary pricing procedure schema。比如SAP标准的PB00就分配了RM0002(Condition Supplement Price)，在RM0002中配置这些supplementary condition type。然后当我们维护info record的condition时，可以点击下面的小加号button让SAP提案所有的condition。

但是有一点要注意，所有的supplementary condition如果想在采购价格计算时起作用的话，必须同样将这些conditiont type配置进采购的定价过程，否则系统将忽略。

SAP Note 456691 - FAQ: Price determination in purchasing 有其他采购定价相关的讲解。这篇Note很不错

Summary

Symptom

This note contains questions and answers that are often presented dealing with price determination. Information on conditions are available in Note 456690.

Catalog of questions

1. Problems occur during the price determination in Transaction ME21N/ME22N.

2. What does master conditions (time-dependent conditions) distinguish from document conditions?

3. How does price determination determine the conditions via a 'Last purchase order'?

4. Why does no price determination occur during the creation of a scheduling agreement?

5. Rounding errors occur during a price determination with consideration of conditions in the info record.

6. Why is a condition type not used during the creation of a purchasing document?

7. When you create a scheduling agreement with reference to a contract, why are the conditions from the contract not transferred to the scheduling agreement?

8. Why are no prices found when you post a goods receipt for a scheduling agreement / during the price simulation for a scheduling agreement (scheduling agreement was created with reference to a contract)?

9. How can you maintain conditions for a material group item in the contract?

10. A plant-dependent info record and a cross-plant info record exist.They are both flagged for deletion (EINE-LOEKZ).Why is then the price of the cross-plant info record still used during the creation of a purchase order?

11. Why is the 'Update' (update prices) pushbutton not activated on the header conditions screen in a purchase order?

12. Why are conditions not automatically determined during the maintenance of a quotation (Transaction ME47)?

13. Why is the price not copied from the purchase requisition to the purchase order?

14. ME22N. Why is the price of the purchase order not converted to the new currency when the vendor is changed (other currency)?

15. If the data of a purchase order item is changed, for example the material group, account assignment category and so on, a new price determination is carried out automatically in the new Enjoy Transaction (ME21N/ME22N) whereas this does not occur in the 'old' Transaction ME21/ME22.

16. Why are absolute conditions of a purchasing document are adjusted/calculated proportionally when posting a goods receipt to the GR quantity?

17. How does a new price determination affect the values posted during goods receipt when a goods receipt is cancelled?

18. When are the header conditions updated if a purchase order item is deleted?

19. When displaying/changing a purchasing document (scheduling agreement/contract) a runtime error occurs since the price (net price or effective price) is negative. How can this problem be solved?

20. Why does the system display different/additional conditions when displaying/changing a purchase order that were not displayed during the creation of the document?

Why is the manual gross price (PBXX) suddenly displayed next to the gross price (PB00) (or vice versa)?

21. Why does the price determination not determine any price although in the master conditions (info record, contract, scheduling agreement) valid prices (with scales) exist?

22. In a contract or scheduling agreement (with time-dependent conditions), currently valid conditions have been maintained.Why does the system nevertheless display an obsolete price in the item overview?

23. A purchase order item contains a manual gross price (in standard PBXX). By using Transaction ME21N or ME22N, you can change basic data such as the plant.

What does it depend on whether the price (the conditions) remain or whether these are deleted (the system displays message 06 218 "Net price must be greater than 0")?

24. Why does the system not take into account the better price that results from the scales for a purchase order (several items for the same material, scales are maintained in master conditions)?

25. You create a purchase order with reference to a quotation with document conditions.The quotation contains next to the gross price (in the standard PBXX) further conditions such as discounts or surcharges.

If you carry out a price determination of type 'C' ("Copy manual pricing elements and redetermine the others") for the purchase order item (manually or arranged by the system, for example when changing the account assignment category's), the system doubles conditions. Why?

26. You post a goods receipt for a purchase order item with pricing date category '5' (new price determination during the goods receipt). Why are conditions determined twice during pricing?

27. You post a goods receipt for a purchase order item with pricing date category '5' (new price determination during the goods receipt). Error message ME573 "The transaction cannot be posted because of an error in the price determination" is generated.

28. What does it depend on whether the net price on the item overview of a purchase order is ready for entry?

29. What does it depend on whether the condition value for the condition of a returns item becomes negative?

30. How is pricing carried out in the info record or contract, if fixed conditions are taken into account for the net price (calculation rule 'B', fixed amount)?

31. You are using the user exit EXIT_SAPLMEKO_002 and find differences in pricing between Transaction ME21N and Transactions ME21/ME59.

32. You copy a purchase order item (ME21/ME22 or ME21N/ME22N), the reference item contains taxes. Why is the corresponding condition copied but the condition amount/value is not?

33. When posting goods receipt for a scheduling agreement of price date type '5' (new pricing at goods receipt), how can a price with value '0' be determined which is reflected in the purchasing history (and in the GR/IR clearing account)?

34. Can conditions be changed after a goods/invoice receipt or is a new price determination still possible then?

35. The net price in the contract is to be updated using Report RM06ENP0. The document contains valid conditions. Why does the report not determine any net price?

36. In a scheduling agreement with time-dependent conditions, you maintain a condition with scales. Is it deliberate that always the first scale level is used for calculating the net price?

37. You add supplementary conditions to a quotation, for example, discounts (condition type RA10). Why does the system ignore these conditions during the quotation comparison (Transaction ME49)?

--------------------------

Question:

Problems occur during the price determination in Transaction ME21N/ME22N.

Answer:

It is highly recommended to implement Note 381391 and the related notes contained in that note, provided that - according to the R/3 Support Package Release - this has not occurred yet.

--------------------------

Question:

What does master conditions (time-dependent conditions) distinguish from document conditions?

Answer:

Conditions in the info record and contract are master conditions.The difference between quotations and scheduling agreements is made by the document type (indicator 'time-dependent conditions').Master conditions are limited to a certain validity period, have master data status and are rather valid on a long-term basis.
Master conditions, which refer to more general price agreements such as vendor, material type, ... (general conditions, Transactions MEK*), can also be represented.
Generally conditions in purchase orders are document conditions.They are only valid for this document.Document conditions are also available for quotations and scheduling agreements if this is set in Customizing.

--------------------------

Question:

How does price determination determine the conditions via a 'Last purchase order'?

Answer:

No valid conditions are in the info record, one, however, exists for the info record 'last document', then all become (!)Conditions copied from this document if following requirements are fulfilled:

After the system has carried out the price determination, the net price must be equal to zero (EKPO-NETPR = 0.00).

However, if you maintained master conditions on the vendor or material group level, that affect the net price calculation, the net price is not equal to zero after the system has carried out the price determination and the conditions from the last purchase order are not copied.

The last document must not be a request for quotation.

The info record must not be deleted.

Vendor and material from info record and last document must be identical.

The calculation schema of the last document must correspond to the currently determined schema.

During the transfer of the conditions from the last document a pure copy function is carried out. In that case the conditions of the calculation schema are not checked.
Condition records of the subsequent billing (condition category has condition class C) are not copied, but rather thoroughly redetermined in order to ensure the consistency of the condition records for the field contents (also see Note 486757).
If copying conditions from the last purchase order is generally not required, you have the option of deactivating this procedure via user parameter EVO (see also Note 675523).

--------------------------

Question:

Why does no price determination occur during the creation of a scheduling agreement?

Answer:

Check the Customizing for the document type of the scheduling agreement (Transaction OMED).A price determination only occurs during the creation of the scheduling agreement if the 'time-dependent conditions' indicator is not set.

--------------------------

Question:

Rounding errors occur during a price determination with consideration of conditions in the info record.

Answer:

Check the standard quantity and price unit in the info record (considering Notes 30658 and 39963).
On the condition screen, go to the condition analysis.('Analysis' pushbutton).There you will see all the conditions of the calculation schema. By double-clicking on the condition type (or on the access) the system will open the detail display to the right. If you go to the technical view ('View' pushbutton) there, you will receive information on the field contents that were used for the access to the condition table or the fields which were not filled for the access.You can avoid rounding errors by choosing a standard quantity that is at least as large as the price unit.

--------------------------

Question:

Why is a condition type not used during the creation of a purchasing document?

Answer:

On the condition screen, go to the condition analysis. ('Analysis' pushbutton).There you will see all the conditions of the calculation schema. By double-clicking on the condition type (or on the access) the system will open the detail display to the right. If you go to the technical view ('View' pushbutton) there, you will receive information on the field contents that were used for the access to the condition table or the fields which were not filled for the access.

--------------------------

Question:

When you create a scheduling agreement with reference to a contract, why are the conditions from the contract not transferred to the scheduling agreement?

Answer:

See Note 160630.

--------------------------

Question:

Why are no prices found when you post a goods receipt for a scheduling agreement / during the price simulation for a scheduling agreement (scheduling agreement was created with reference to a contract)?

Answer:

See Note 431460.

--------------------------

Question:

How can you maintain conditions for a material group item in the contract?

Answer:

Conditions for material group items are not allowed in the contract. (See notes 62729 and 105899).

--------------------------

Question:

A plant-dependent info record and a cross-plant info record exist.They are both flagged for deletion (EINE-LOEKZ).Why is then the price of the cross-plant info record still used during the creation of a purchase order?

Answer:

Since the corresponding condition tables are read by an external SD module, the information on the deletion indicator of the info record is not available there.
You can only set that the conditions of the cross-plant info record are to be read, if the plant-dependent info record is deleted, by means of a corresponding transfer parameter (komp-no017, set in module ME_FILL_KOMP_PO).
For the case that both info records are deleted you have the option of changing the validity period of the conditions to a past date or archiving the info record.

--------------------------

Question:

Why is the 'Update' (update prices) pushbutton not activated on the header conditions screen in a purchase order?

Answer:

The pushbutton does not have any function on header level.It is not meant to trigger a new pricing for all items of one document.This can only occur by item. Thus the pushbutton is not active on header level (in the standard system).
You can use Transaction MEI2 to perform the mass adjustment of documents according to condition changes. However, consider the functional restrictions in the online documentation or in Note 457511 "FAQ: Purchase order change and goods receipt in purchasing".
--------------------------

Question:

Why are conditions not automatically determined during the maintenance of a quotation (Transaction ME47)?

Answer:

During quotation maintenance, no pricing occurs.The conditions must be maintained manually.

--------------------------

Question:

Why is the price not copied from the purchase requisition to the purchase order?

Answer:

See Note 393367.

--------------------------

Question:

ME22N. Why is the price of the purchase order not converted to the new currency when the vendor is changed (other currency)?

Answer:

See Note 445509.

--------------------------

Question:

If the data of a purchase order item is changed, for example the material group, account assignment category and so on, a new price determination is carried out automatically in the new Enjoy Transaction (ME21N/ME22N) whereas this does not occur in the 'old' Transaction ME21/ME22.

Answer:

This is not an error.The new Enjoy Transaction was intentionally designed in such a way and is much more extensive with regard to the price determination.

--------------------------

Question:

Why are absolute conditions of a purchasing document are adjusted/calculated proportionally when posting a goods receipt to the GR quantity?

Answer:

See Note 304178.

--------------------------

Question:

How does a new price determination affect the values posted during goods receipt when a goods receipt is cancelled?

Answer:

See Note 508009.

--------------------------

Question:

When are the header conditions updated if a purchase order item is deleted?

Answer:

If a purchase order item is deleted, the item is marked as 'statistical' (field EKPO-STAPO = X) and the change is reflected in the header conditions.
However, if for the item the final invoice indicator (EKPO-EREKZ) or the inward delivery completed indicator (EKPO-ELIKZ) is set, the item is not marked as 'statistical' (EKPO-STAPO is not set) and thus the header conditions are not updated.

--------------------------

Question:

When displaying/changing a purchasing document (scheduling agreement/contract) a runtime error occurs since the price (net price or effective price) is negative. How can this problem be solved?

Answer:

Proceed as follows to determine the condition that results in the negative price:
Scheduling agreement:Display the document using Transaction ME3N. Select the item and navigate via Edit to the price simulation.
Contract:Display the conditions for the contract via Transaction MEKA. These can be changed directly from here.

--------------------------

Question:

Why does the system display different/additional conditions when displaying/changing a purchase order that were not displayed during the creation of the document?
Why is the manual gross price (PBXX) suddenly displayed next to the gross price (PB00) (or vice versa)?

Answer:

These problems indicate that, after the creation of the purchase order, the calculation schema has been changed.This must absolutely be avoided.

--------------------------

Question:

Why does the price determination not determine any price although in the master conditions (info record, contract, scheduling agreement) valid prices (with scales) exist?

Answer:

Check whether a scale exists for the quantity on which the price determination is based.It is recommended to set the quantity of the first scale to zero in order to avoid such problems.

--------------------------

Question:

In a contract or scheduling agreement (with time-dependent conditions), currently valid conditions have been maintained.Why does the system nevertheless display an obsolete price in the item overview?

Answer:

During the maintenance of condition validity periods, the system uses the price of the currently valid period for the item (field EKPO-NETPR). However, if a condition validity period expires, the net price of the item is not updated automatically.This can be made up with report RM06ENP0 (for contracts) or report RM06ENP1 (for scheduling agreements).
The obsolete price does not affect the creation of a purchase order with reference to such a document because basically the system uses the current price from the conditions without taking into account the price of the item (EKPO-NETPR).

--------------------------

Question:

A purchase order item contains a manual gross price (in standard PBXX).By using Transaction ME21N or ME22N, you can change basic data such as the plant.
What does it depend on whether the price (the conditions) remain or whether these are deleted (the system displays message 06 218 "Net price must be greater than 0")?

Answer:

In case of the change of basic data, a new price determination is triggered.Here, if no price is found, the system checks whether the price existing before was a 'manual price'.
(A price is considered as being 'manual' if the net price is equal to the gross price (PBXX), that is, no further conditions have been included in the net price.This can be seen by the fact that field 'net price' is ready for input in the item overview).
If this is the case, the system transfers the price existing before.As a result, the user gets the impression as if the price had not been changed through the change at the item.
Otherwise (net price not equal to gross price -> field 'net price' in the item overview is not ready for input) the price existing before (the conditions) cannot be transferred.The price must be maintained again, the system displays error message 06 218 "Net price must be greater than 0".

--------------------------

Question:

Why does the system not take into account the better price that results from the scales for a purchase order (several items for the same material, scales are maintained in master conditions)?

Answer:

The purchase order quantities of the items are only grouped together for the consideration of scales if the document is saved or checked.

--------------------------

Question:

You create a purchase order with reference to a quotation with document conditions.The quotation contains next to the gross price (in the standard PBXX) further conditions such as discounts or surcharges.
If you carry out a price determination of type 'C' ("Copy manual pricing elements and redetermine the others") for the purchase order item (manually or arranged by the system, for example when changing the account assignment category's), the system doubles conditions. Why?

Answer:

In case of a reference to the quotation the conditions are copied from the quotation.If you carry out a price determination of type 'C' afterwards, the manually maintained conditions (from the quotation, as PBXX) will remain, in addition the gross price from the master condition is set(for example info record). this can be seen on the detail screen for the condition.

For more information you can also refer to Notes 76774 and 548900.

----------------------------------------------------------------------

Question:

You post a goods receipt for a purchase order item with pricing date category '5' (new price determination during the goods receipt). Why are conditions determined twice during pricing?

Answer:

You changed/maintained this condition manually in the purchase order. In addition, the condition has been maintained in the master conditions (e.g. info record).
During goods receipt, pricing of type 'C' is carried out. This means that the condition changed/maintained manually from the document is kept and is determined from the master conditions in addition.
This problem can be solved by choosing the following customizing setting (Transaction m/06) for the condition:
Manual entries: C 'The manual setting takes priority'
If during goods receipt, the pricing of type 'C' determines an already existing condition from the master conditions, that condition is set to inactive since the manual condition from the document takes priority (to be seen on the condition details screen).
Please also refer to Note 548900.

--------------------------

Question:

You post a goods receipt for a purchase order item with pricing date category '5' (new price determination during the goods receipt). Error message ME573 "The transaction cannot be posted because of an error in the price determination" is generated.

Answer:

It is possible that, during the price determination, condition records are used that do not yet exist at the time of the creation of the document item. As, for example, an additional discount on the vendor level, ... These additionally determined conditions can, for example, result in the net price being negative or 0.
In order to find out from where the conditions are coming that lead to an incorrect price, it can help in some cases to create a purchase order item with identical data. Branch to the condition screen in the 'analysis'. Here, you can find out which condition record results in the undesired result.

--------------------------

Question:

What does it depend on whether the net price on the item overview of a purchase order is ready for entry?

Answer:

The net price is not ready for entry (price can be changed on the condition screen only), if

the document currency is not the same as the condition currency of the price,

apart from the basic price PB00, other conditions are used to calculate the gross amount (e.g. variants),

if the net amount is not the same as the gross amount.

--------------------------

Question:

What does it depend on whether the condition value for the condition of a returns item becomes negative?

Answer:

The condition value for the condition of a returns item receives a negative sign, if in the customizing of the condition type
- condition type 'B' (delivery costs) is not set,
- the provision indicator is not set,
- in the calculation schema for the condition the statistical indicator
is not set.

The condition value for a condition of type 'B' (delivery costs) only receives a negative sign, if calculation rule 'A' (percentage) is set for the condition.
(see LV61AA43, FORM xkomv_kwert_ermitteln)

--------------------------

Question:

How is pricing carried out in the info record or contract, if fixed conditions are taken into account for the net price (calculation rule 'B', fixed amount)?

Answer:

See Note 586856.

--------------------------

Question:

You are using the user exit EXIT_SAPLMEKO_002 and find differences in pricing between Transaction ME21N and Transactions ME21/ME59.

Answer:

A frequent cause for the fact why pricing is different for Transaction ME21/ME59 when using user exit EXIT_SAPLMEKO_002 is the use of fields EKPO-BANFN / EKPO-BNFPO in the user exit. These two fields are filled only when Transaction ME21N is used. In Transactions ME21/ME59, these fields have their initial values, but the document and item numbers of the purchase requisition are available in Table EKET.
This difference results from the enhanced functional range of the Enjoy purchasing transaction and cannot be interpreted as an error in the R/3 standard program.
To achieve identical behavior of the mentioned transactions, you can enhance the interface of user exit EXIT_SAPLMEKO_002 and function module ME_FILL_KOMP_PO accordingly.

--------------------------

Question:

You copy a purchase order item (ME21/ME22 or ME21N/ME22N), the reference order item contains taxes. Why is the corresponding condition copied but the condition amount/value is not?

Answer:

Amount and value are not copied to the new purchase order item. Amount and value are determined as soon as a PRICING_COMPLETE is carried out. This is the case when checking or posting the document and when going to the header conditions.

--------------------------

Question:

When posting goods receipt for a scheduling agreement of price date type '5' (new pricing at goods receipt), how can a price with value '0' be determined which is reflected in the purchasing history (and in the GR/IR clearing account)?

Answer:

See Note 683646.

--------------------------

Question:

Can conditions be changed after a goods/invoice receipt or is a new price determination still possible then?

Answer:

Changing the delivery costs is impossible after the goods receipt has been posted.
After applying Note 549408, changing conditions of type 'B' (delivery costs) is no longer possible after the invoice has been posted or parked.
If data are changed in the purchase order which normally trigger a new price determination of type 'B' or 'C', that automatic price determination is not carried out, if goods receipt or invoice receipt has already been posted.
See also Note 457511, Question 3.

--------------------------

Question:

The net price in the contract is to be updated using Report RM06ENP0. The document contains valid conditions. Why does the report not determine any net price?

Answer:

The net price is determined based on the release quantity. If the release quantity is lower than the price unit, it may happen that the net price is rounded off to zero if the gross price is low.
The release quantity should always be higher than or equal to the price unit.

--------------------------

Question:

In a scheduling agreement with time-dependent conditions, you maintain condition with scales. Is it deliberate that always the first scale level is used for calculating the net price?

Answer:

Price determination in the scheduling agreement cannot be compared to the one in purchase orders, if the scheduling agreement is a document with time-dependent conditions (master conditions). To display the price in the scheduling agreement, always the first scale level is taken into account.
On the topic "Goods receipt in scheduling agreements with scales", please read Note 401941.

--------------------------

Question:

You add supplementary conditions to a quotation, for example, discounts (condition type RA01). Why does the system ignore these conditions during the quotation comparison (Transaction ME49)?

Answer:

The problem occurs if you use a supplementary calculation schema (RM0002 in the standard system) that included conditions that are not contained in the calculation schema of the document (RM0000 in the standard system). All condition types used in a supplementary calculation schema must be defined in the calculation schema of the document.

--------------------------

Other terms

FAQ, PRICING, NETPR, EFFPR, NETWR, NETPR, KSCHL, EBAN-BPUEB,
BEKPO-NETZU

[收藏]预留 Reservation

Thu, 02 Apr 2009 21:41:38 +0100

http://www.mediafire.com/?zjmjikttymi
http://www.mediafire.com/?wyqwjnh4jyi

预留是可用性检查要考虑的一个重要方面。但即使你使用了预留，预留所占用的数量也未必不可以使用，这要根据你对预留的设置而定。比如：你如果将预留设置为“物料一旦预留出来就不允许移动”，那么就会出现楼上所说的情况。但你也可以将预留设置为：“在预留的物料被计划使用日的30天前可以被使用”，那么这些预留的物料在计划使用日的30天前还是可以使用的，即可以移动的。
http://help.sap.com/saphelp_erp60_sp/helpdata/en/a5/63361c43a211d189410000e829fbbd/frameset.htm

SAP采购审批策略 purchase release strategy

Wed, 04 Mar 2009 18:39:46 +0000

我这里简单的介绍了PO的审批流程，在附件中包含了图片，以及网络上的关于PR的审批详解，以及SAP Notes 207490对PO审批配置的介绍。Release Strategy.rar

Purchase Release Strategy

如果想需要PR或者其他采购文档(PO, contract, scheduling agreement, request for quotation (RFQ)等)在一定条件下被审批，就需要用到SAP的审批策略。

对于PR的审批可以在item级别也可以再total级别，并且有带classification和不带classification两种，不过不带classification的只能在total级别审批。我们接下来都以PO为例讲解。

l Release Condition(Characteristics class)

一个PO必须满足审批条件，才会进入审批流程，比如采购总价值超过1万元，或者采购组001采购的物料等。SAP采用classification系统进行审批条件的配置。

首先通过CT04定义审批条件的要素，比如采购组或者总价值，我们可以在表CEKKO中找到所有可以被利用的字段，如果不能满足需求，就需要enhancement M06E0004

之后CL02定义class，也就是将各个审批要素组合在一起，组成一个完整的审批条件。比如采购组001采购金额大于5K 采购组002采购金额大于10K

l Release Strategy overview

审批策略是一个总的审批流程，可以在一个审批策略下定义release code，我们最多可以定义8个release code。定义审批策略包括定义定义release group, release code, release indicator等步骤

l Release Group

同一个release group具有相同的审批level，比如我提到的001采购组大于5K的金额需要审批，而002采购组大于10K的金额需要审批，这就需要连个不同的审批组，而如果有一个第三个部门，但是依然用采购组001和大于5K的policy，那么它可以与第一组共享审批组。

我们为审批组分配Class

l Release Code

Release Code我们可以理解为现实中与整个审批流程相关的人，每个审批者都会审批相应的release code。如果配置了workflow，可以将他们与workflow结合起来用，审批自动到达他们的task中。

l Release Indicator

这一步骤实际是定义审批中的各种状态和在此状态时系统的反应。

比如我们这里有2个状态，在审批流程中都会是状态1，也就是没有release，可以更改PO并且不会触发新的审批流程，或者是在触发新的审批流程的值状态时进行新的审批等。后面的%value change字段限制了字段更改的最大范围，超过了一定百分比系统会产生错误信息。

l Release Strategy

最后一步定义审批流程。Release codes我们看到最多输入8个，我们按照审批顺序输入。

Release prerequisites定义的是每个审批流程需要的前提，很简单，一般的审批都是一步一步进行的。都会勾成下面的样子，也就是02需要01最为条件。

Release status定义每一步被审批后，PO的状态，我们定义只有01 02都被通过了，才会进入最终的2状态

Classification相当于定义这个审批策略被触发的条件。

l Authorization

整个审批的授权可以通过分配authorization object M_EINK_FRG给相应用户进行限制

l Test

我们为采购组001创建一个总价80块的订单，没有触发审批流程。

当我们改为总价8000块时，就产生了审批流程

我们通过TCODE ME28进行审批，如果直接审批02 code会发现系统提示没有合适的PO，审批后PO的状态改变

审批02 CODE以后，PO状态改变

如果尝试更改PO会得到以下错误消息

Purchasing document has release indicator 2 (changes not possible)

Tolerance Limits for Price Variance

Tue, 03 Mar 2009 22:45:50 +0000

在我们创建PO的时候，可以检查当前PO中物料输入的价格以及产生的现金折扣，如果与我们期望的相差过多，可以产生warning或者error的消息。
这个功能是通过Set Tolerance Limits for Price Variance来实现的 IMG->Materials Management->Purchasing->Purchase Order->Set Tolerance Limits for Price Variance
SAP预置了两个容差KEY PE和SE PE是用来检查物料的价格与物料主数据价格的差异 SE是用来价差现金折扣为每个company code通过设置上下限最终达到在创建PO时进行条件检查的目的。

Tolerance Limits for Price Variance

Material主数据之ABC Anyalisys

Fri, 27 Feb 2009 00:57:26 +0000

在物料主数据中有一个ABC indicator可供选择，是高消耗量中等消耗量还是低消耗量。分别对应ABC

这是为了应用ABC分析的字段。

具体请看下面几个文章

http://space.itpub.net/90437/viewspace-526518

http://www.examda.com/wuliu/shanji/20060815/11202018.html

http://new.boyar.cn/boyar_code/uploadfiles/news/200571415549708.doc

useful TCODE in SAP MIBC

Vendor主数据之schema group

Thu, 26 Feb 2009 23:17:53 +0000

在vendor主数据的采购view中，有一个选项为schema group，这个选项会影响PO时候的采购价格。
PO的价格的决定可以受schema group的影响。而我们可以为采购组织指定schema group也可以为vendor指定schema group
在Purchasing->Conditions->Define Price Determination Process->Define Schema Determination中我们可以看到价格计算schema的决定过程
而在同级菜单下，我们可以为采购组织定义并分配schema group