Info record for material group

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


(3) 评论    (26) 引用   

basic procedure for physical inventory

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.


(2) 评论    (188) 引用   

Maintain Plant

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


(4) 评论    (3) 引用   

Split valuation

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

(1) 评论    (295) 引用   

Supplementary Condition以及purchase pricing FAQ

如果有一些价格条件是依附于特定物料的,则我们可以使用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)?


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

    1. 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.

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

    1. 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.

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

    1. 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).

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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).

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

    1. 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.

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

    1. 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".
--------------------------

    1. 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.

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

    1. Question:

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

Answer:

See Note 393367.

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. Question:

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

Answer:

See Note 508009.

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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).

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

    1. 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".

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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.

    --------------------------
    1. 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)

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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.

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

    1. 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


(2) 评论    (84) 引用   

[收藏]预留 Reservation

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


(1) 评论    (84) 引用   

SAP采购审批策略 purchase release strategy

我这里简单的介绍了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,我们最多可以定义8release code。定义审批策略包括定义定义release group, release code, release indicator等步骤

l Release Group

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

我们为审批组分配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)


(2) 评论    (270) 引用   

Tolerance Limits for Price Variance

在我们创建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时进行条件检查的目的。

 查看全文

(1) 评论    (178) 引用   

Material主数据之ABC Anyalisys

在物料主数据中有一个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


(0) 评论    (186) 引用   

Vendor主数据之schema group

在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


(1) 评论    (15) 引用   

Rounding Profile简介

具体图片参考附件Rounding Profile.rar

Rounding Profile

  • Overview


Rounding profile是用来调整order的数量的。在物料主数据的sales和MRP视图中都可以维护。后台通过Materials Management->Consumption-Based Planning->Planning->Lot-Size Calculation->Maintain Rounding Profile来创建rounding profile
主要有三种类型:static rounding profile; Dynamic rounding profile; Rounding profile with quantity to be added/subtracted

  • static rounding profile


静态的定义阈值和阈值范围内, round off到的数量。
我们设定如下,当达到2阈值时,入到3
将这个rounding profile配置如物料主数据,设定MRP type等,使得产生2个需求。通过MD03进行MRP RUN,然后MD04看最后的结果如下,由于rounding profile的存在,产生了3个的PR

我们将rounding profile去掉,再跑MRP会发现,产生的是需求为2的PR

  • Dynamic rounding profile


如图,动态的有两个主要参数需要维护,先看第一个rounding off method

如果选了0,则不进行四舍五入,可以通过simulation来确认。
那么选1 Round off to multiple of order/sales unit of measure,则会四舍五入到物料的销售或者采购单位与基本单位关系的倍数 比如,采购单位1 BOX = 5 PC 那么我们如果采购2PC会自动四舍五如到10 PC
那么我们首先在物料主数据中维护这个1 BOX = 5 PC的采购单位与基本单位的关系
Simulate一下,看到结果如下,2PC会四舍五如到1BOX = 5 PC

之后我们选择2 Round off to order/sales Un and to log. Units 此时系统会要求输入rounding rule 可以通过Logistics – General-> Quantity Optimizing and Allowed Logistics Units of Measure-> Unit of Measure Rounding Rules来定义
如图,Alt. unit of measure定义的单位相当于采购或者销售单位,需要在物料主数据里进行维护。% rounding up维护的是阈值,也就是达到多少百分比进行round up,比如1BOX = 100 PC ,设置80%,则79 PC就不会round up, 100%表示永远不会round up 我们设置为80%来simulate一下,可以发现,79PC时不会四舍五入,而80PC时,四舍五入就发生了


%Round down 则相反,比如输入10%,那么110PC以下就会被舍为1BOX 100PC,110PC以上则不会产生影响。
Check vendor checkbox表示,在做四舍五入时,只有vendor允许的数量单位,才会进行四舍五入。这个通过measure group定义,Logistics – General-> Quantity Optimizing and Allowed Logistics Units of Measure-> Unit of Measure Groups
在vendor主数据的采购视图data中,维护unit of measure group,如图

Check recipient类似,检查的是接收方,通过客户主数据的销售data中维护,如图

  • Rounding profile with quantity to be added/subtracted


比如销售100件衣服,但是由于损耗等,可能需要多于100个随衣服一起销售的袋子,那么,我们可以为袋子创建这种rounding profile,比如多出10%,也就是说,当销售100个衣服时,系统会建议附加110个袋子。
则如图所示配置


(1) 评论    (102) 引用   

货源决定详解 source determination in detail

具体图片请见附件Source determination in detail.rar

补充了Kanter的关于source list和配额协议的讲解

Source determination in detail


前面对contract介绍时,简单的提到过source determination。这由两部分组成:Source list(源清单)和Quota Arrangement(配额协议) 我们将分别介绍

  • Source List Overview


我们提到过,供货来源有供货商(SAP中表现为信息记录和框架协议)和内部工厂(用于stock transfer)两种。我们这里讲的source list主要是采购中,供货商的表现形式。在创建PR的时候,如果将source determination选项勾选(如图),则系统会搜索所有货源,如果没有预先设定的首选项,则可以将列出清单。可以通过价格模拟和供应商评估来决定供货商。

另外,可以在用户参数中配置EFB来禁止用户手动指定供货商。

Source determination将发生在如下业务:
1. MRP运行 MD01/MD02/MD03
2. 创建PR ME51N
3. PR分配 ME56
4. PR分配和处理 ME57
5. 创建PO,vendor未知 ME25
6. 计划订单转化为PR MD14/MD15

  • Source List的功能


1. 定义一个vendor为固定的供货商(除了MRP运行) 同类型的(信息记录或框架协议)固定vendor只能有一个,如果不同类型的都有一个固定vendor,则框架协议的具有的优先级较高
2. 定义从某个内部工厂采购。只有PR的明细类型为U(stock transfer 库存转储)时起作用
3. Block某个vendor 如图,如果没有设置vendor而只是输入有效期间和block,则表示这段时期内,此物料在相关工厂不能外购


4. MRP相关 如果设置为1,则MRP运行时考虑此项作为货源,如果此项为SA,设置为2,可产生SA的schedule line
前面提到过,如果一个物料没有维护源清单则禁止采购,可以如图在物料主数据中设置和后台配置(Purchasing->Source List)某个工厂的物料采购都需要源清单


我们可以通过ME06(Purchasing->Master Data->Source List->Follow-On Functions)来分析某个工厂下哪些物料还没有源清单

  • Source List的创建


1. 手动
2. 通过大纲协议创建 如图

3. 通过信息记录创建 如图

4. 自动创建 ME05(Purchasing->Master Data->Source List->Follow-On Functions)

  • Include和Exclude功能的源清单


因为合同的明细类型有W和M两种特殊形式,并不会指定具体的物料号。比如W(material group),我们要采购的物料都属于001这个物料组,但是唯独001中的100-100这个物料不行,则可以创建一个exclude类型的源清单。操作过程如图


采购一个不在这个清单中的物料Z-ROH-DV01 系统是允许的 如果采购100-100系统就会报出错误的消息Source of supply blocked (according to source list)

但如果按如下设置,Exclusion删除掉,则除了100-100以外的物料都是不允许的,只有100-100可以采购。

  • Quota Arrangement(配额协议) overview


配额协议是source determination中的另外一个可以影响结果的选项。如果一个物料存在配额协议,则在source determination过程中,它有最高的优先级。
当一个需要采购的物料有多个供货源,而采购的数量需要在这多个供货源中分配时用到配额协议。
注意,即使一个物料拥有了配额协议,也不证明在手动创建PR时会自动分配采购的数量给多个供货商,货源只会分配给一个。只在MRP运行时可以分配数量。

  • 配额安排(Quota Arrangement Usage)


在一个物料要使用配额协议之前首先要确定配额要使用的业务范围,这个可以在物料主数据的MPR2视图的配额安排中设定,如图

而这个配额安排的配置在后台Purchasing->Quota Arrangement->Define Quota Arrangement Usage

  • 配额协议的创建


TCODE MEQ1维护配额协议,如图所示。先维护header,一个有效期间和配额协议生效的最小数量。然后维护明细,设置采购类型(外购/内销)特殊采购类型(自制/寄售/库存转移等)指定供货商或者工厂,指定配额以及其他细节。这些其他参数细节我们将稍后讨论。

  • 配额协议的运行方式


在使用系统自动指定供货源的时候,系统会根据配额协议计算供货商。这个计算涉及到配额率的概念。Quota rating = (quota-allocated quantity + quota base quantity) / quota
 Quota-allocated qty:配额安排指定的业务范围中,所有跟这个vendor有关的已分配的数量。这个是系统自动更新的
 Quota base quantity维护配额协议的画面可以找到这个配额基本数量的维护字段。用来人工控制配额协议
 Quota 配额,也在配额协议维护画面找到这个字段,决定需求如何分配
在决定货源的过程中,具有较低配额率的供货商会被优先考虑。

因为配额率中的配额基本数量比较晦涩,其他两个因素都很容易理解。我们详细探讨一下。
配额基本数量,可以在已有的配额协议引入了新的货源或者用来补救已分配配额数量和配额之间的不平衡分配。
Scenario:假设系统原来的配额协议有两个vendor,分别分配50%,这时引入了新的vendor。因为系统已经运行了很长时间,所以两个旧vendor拥有很高Quota-allocated qty,依据公式,新的vendor将具有很高的quota rating,所以,在做货源决定时,将会一直指定给这个新的vendor。这时我们需要手动维护或者由系统来决定。
系统计算是通过配额协议维护画面菜单进入的,如图
其中有单独处理和批量处理两种方式。

  • 配额协议与MRP


与在source determination中的配额协议使用相比,在MRP运行中,可以将一个需求分给多个货源。这个在SAP中叫做splitting(分割)
这个是否做分割,是由物料主数据中MRP1视图的批量大小来控制的,在后台可以配置批量大小计算过程是否分割配额。另外,在配额协议的header中指定分割的最小数量,如图



我们设置最小分割数量为10,而MD03运行MRP,因为需求是5个,所以并没有产生分割。
我们将最小分割数量删除,再次运行MRP。如图,我们看到,MRP的运行结果是5个需求,分割成了3个和2个,给两个货源

我们还可以在配额协议中指定最大和最小批量数量。但是这个只会在MRP自动生成order时起作用。如果物料主数据中也指定了,则配额协议的会覆盖物料主数据中的设定。
如图,物料主数据中设定最小 最大批量数量为2和4,需要再采购1个物料(这里为了方便,使用了静态的reorder point)

如图,运行MRP可以发现,实际产生了采购2个数量的PR

我们在配额协议中配置为1

如图,运行MRP可以发现,时间产生了1个数量的PR

我们再更改一下数据,使得系统目前需要5个数量的物料,运行MRP,可以发现,产生了一个4个数量的PR,又产生了一个2个数量的PR,这是物料主数据限制造成的
同理,如果将配额协议中最大为5,则可一次产生5个数量的PR了
注意,在配额协议中有一个check box,是only-once指示。当我们指定了最大批量数量,而这个vendor具有很低的quota rating时,产生的后果是产生很多个order,每一个都是最大数量,而是这一个vendor。为了避免这种情况,可以勾选Only-once,则这个供货商的采购,只会达到最大数量的一个order,其他的根据配额分配。
如图,我们产生5个数量的需求,设定1000 vendor的最大LOT数量为4,则剩下的1个会分配个1010.


除了最大批量数量,还可以在配额协议中设定最大数量。当一个vendor的已分配配额数量等于或者大于这个值时,这个vendor将不再被视为货源之一。无论手动创建PR还是MRP自动运行都会考虑这个设定。

  • MRP中Source determination过程


SAP在MRP运行时,按照如下顺序绝对货源
1. 配额协议
配额协议存在的话拥有最高的优先级。因为框架协议没办法增加到配额协议中,所以在原清单中,框架协议如果与MRP运行的货源相关,则要将最后MRP-relevant设置为1或者2.
2. 源清单
配额协议不存在的话,系统检查源清单,MRP-Relevant被设置为1或者2的话,系统会作为供货源考虑。如果有多个项目设置与MRP相关,则第一个项目作为供货源。
对于不是MRP运行的source determination,系统也有一个检查顺序。
1. 配额协议
2. 源清单
源清单中被标识为fixed vendor被优先考虑,如果信息记录和框架协议在源清单中都被标识为fixed vendor,框架协议被优先考虑。如果没有fixed vendor,有多个货源,则系统会列出一个List供选择。
3. 框架协议
4. 信息记录

  • Regular vendor(常规供应商)


如果在整个client范围内,某个物料只从一个vendor处采购,则可以在信息记录中,将这个vendor设置为 regular vendor,如图

如果我们要再指定一个常规供应商,会得到警告消息Up to now, vendor 1000 has been regular
与工厂级别的fixed vendor设定相比,regular vendor是client级别的。
当然,我们要在后台激活常规供应商功能(Purchasing-> Source Determination-> Define Regular Vendor),才会在货源确定中使用常规供应商

  • 关于货源决定的其他补充


在创建PR时,如果想为没有物料主数据的采购执行货源决定也是可以的,只要指定了material group,并且有相关material group的框架协议或者信息记录存在。框架协议的优先级高。
在创建PO时,自动货源决定按照配额协议,源清单,框架协议,信息记录的顺序检索可用的供货源。
如果出于某些原因,禁止再从某个供货商采购物料,则可以BLOCK此供货商,这样在创建配额协议,源清单等的时候将禁止操作。Logistics->Materials Management->Purchasing->Master Data->Vendor->Purchasing->MK05 – Block
我们也可以通过在源清单中设定block来禁止从特定供货商采购。这种block有一些小的区别:
1. 阻止的是一个大纲协议的item的货源:则禁止从这个大纲协议创建release order或者schedule line。但是不参考大纲协议创建的采购是可以继续进行的。在创建PR或PO进行指定货源时,大纲协议被阻止明细将不会被作为货源之一出现在列表中。
2. 阻止的不是大纲协议的item(信息记录或者工厂): 则意味着不能从这个vendor进行任何采购相关的活动。在创建PR时,将不会出现在备选货源清单中。如果直接创建PO,会报错误消息:Source of supply blocked (according to source list)


(0) 评论    (286) 引用   

scheduling agreement 计划协议详解

详细图片请见附件 Scheduling_Agreement.rar

  • Overview


计划协议(scheduling agreement)是与供货商签订的一项长期合作协议。会预先定义有效时间和采购数量。
使用计划协议的好处有:
1.可以省去很多PO和合同的release order(直接对SA进行GR操作),SA的delivery schedule line本身就是SA的一部分,因此可以减少文档的数量。
2.MRP运行时,可以自动产生delivery schedule line
可以参考以有的PR RFQ Contract SA来创建新的SA。因为SA永远是与工厂相关的,所以M W类型的item是不允许的(见contract item category的讲解)。SA的条件是可以在后台配置是否是时间相关的,如果指定为与时间相关,则可以指定不同期间的价格。

SA也可以创建对没有物料号的物料的采购。但是与contract不同的是,不能使用U(unknown)的account assignment
我们还可以通过后台,对doc type的配置,来指定是否需要release doc.关于release doc稍后会说明

  • 自动产生delivery schedule line


MRP的运行可以自动产生SA的schedule line,但是有如下几个前提:
1. SA必须明确的在source list中定义为source of supply,并且MRP相关列设置为2(Record relevant to MRP. Sched. lines generated automatically)
2. 物料的MRP2的视图中,Procurement type必须设为F
3. 自动产生schedule line是被允许的(在SA中设置)

  • SA的release document


如果不需要release doc. 那么SA中保存一条schedule line的时候,就可以认为是被客户承认了,可以马上传达给客户。在这种情况下,消息控制功能应该被配置为,SA的任何修改被保存时,马上就产生消息。

如果需要release doc.,在显示的SA release之前,schedule line产生之后不会马上发送给客户,而是保存在系统内部作为参考(LPA SA类型)。这可以是一个FRC(forecast)或者JIT(just-in-time)的交付计划。
可是使用两种SA的release:
1. FRC(forecast) delivery schedules
可以给客户展示中长期的物料需求概览
2. JIT(just-in-time) delivery schedules
可以给客户展示短期内的物料需求

  • SA的release


如图,可以通过在SA的item中设置JIT与release无关。这个flag的值是从物料组数据的MRP2视图中带入。如果MRP2中没有设置,是没办法在SA中修改的。


SA的release可以手动或者自动进行,也可以通过选择条件选择SA的所有item或者SA中被新创建或者更改的item可以被release。
通过TCODE ME84(Logistics-> Materials Management-> Purchasing-> Outline Agreement-> Scheduling Agreement-> ME84 - Create SA Release)来创建SA的release
也可以通过TCODE ME38(Delivery Schedule line maintain)的edit菜单生成FRC或者JIT的SA release

  • Release creation profile


Release creation profile的官方帮助
http://help.sap.com/saphelp_47x200/helpdata/en/3b/665971da7b11d1b6330000e8a738dc/content.htm
我们可以通过release creation profile来定义:
哪种事件可以触发SA schedule line的release,比如schedule line被修改;
Delivery时间如何表示(是否汇总);
是否积压和及时需求也被触发并显示在SA release中;
是否有容差组触发执行创建新的SA release;
如果在vendor主数据中指定了(与工厂相关的数据),则可以带入SA明细项中,否则需要在SA中指定。在vendor中指定工厂相关数据的过程为:Select Purchasing data screen from Vendor maintain, find the submenu Extras--> add. Purchase data -->select data retent. at plant level allowed, then select Alternative data and then choose Yes to create it, enter plant 1000, select Purchasing data and select Continue 如图



Release creation profile(批准创建参数文件)是一种工具用来控制对SA进行release(审批)的频度以及数量汇总的方式。
频度:比如每天或者每星期,对SA进行审批并传送给客户。可以为FRC和JIT分别创建不同的频度。
数量汇总(aggregation):决定哪个期间内的schedule line的数量会被合并。可以分别为FRC和JIT创建不同的数量汇总
我们 简单的来看一下参数文件中的配置(Materials Management->Purchasing->Scheduling Agreement->Maint. Rel. Creation Profile for Sched. Agmt. w. Rel. Docu.)

如图,以JIT为例,release doc创建的策略,分别将计划行修改或者达到下一个交付日作为条件组合。我们首先创建一个计划行(日期在未来)如果选择了第一项,因为是或者的关系,也就是虽然没有达到这个交付日但是新修改的计划行,所以依然可以创建。
ME84 test run的结果如下

注意,创建的原因是change creation
如果我们将创建策略改为只有达到了下一个交付日才创建,再次运行,结果如下

没有创建,原因为No creation (next date not yet reached)
Aggregation Horizons是用来控制,在哪个区间范围之内,交货数量是如何累积的。如图

以FRC为例,创建以后的0~10天内都是数量每天累积的,发给供货商。可以看到我暂时配置的0~10天是每日汇总。SA的计划行和ME84运行后,查看结果如下


可以看到是按照每日的总数量汇总的。
我们再改一下配置,改为0~10天,没有汇总,也就是说每个计划行的数量都会和详细信息发给供货商。
ME84运行后结果如下,可以看到,没有对每天的数量进行汇总,每个计划行都是一条单独的记录

如果想周期性的创建SA release可以使用create periodicity功能。
容差参数文件,可以控制,在schedule line的数量被更改了多大的百分比时,需要创建新的SA release doc给客户。具体操作可以自己试验。

  • Firm Zone(确定的域) and Trade-off Zone(平衡的域)


Firm Zone:定义了从当前日期开始到哪一点为止的时间段,是货物的生产进行时期。落在这个时间段内的schedule line可被认为是确定的订单(firm order).这个时间需要与供货商商讨确定,他包含了客户需要生产计划数量货物的时间。如果在这个区间内的schedule line被取消了,供货商有权利要求支付生产成本和为了生产购置零件的成本
Trade-off Zone:定义了货物进行时期。这个时间一般基于运输时间和供货商采购生产所需物料的组件的时间。如果在这个区间内的schedule line被取消了,供货商只有权力要求支付为了生产购置零件的成本。
落在这两个区间之外的schedule line属于计划区间。
可以通过设置,落在哪个区间的schedule line是可以被MRP运行所修改的。如图:

  • Message


系统可以为每一个SA的release生成message,也可以为整个SA生成一个message。
在后台Materials Management->Purchasing->Messages->Output Control ->Message Determination Schemas->Define Message Schema for Scheduling Agreement Release/Expediter中的Assign Schema: SA Release/Expediter进行配置
将如图所示的选项勾选之后,系统将会为每一个SA的release都生成一个message,否则将在header级别生成message.

我们还需要为每种SA release类型定义也只能定义一个main message type。Main message type如果被输出了,会更新相应的依赖于输出的数据,比如release doc的状态变为被处理状态。配置路径为Materials Management->Purchasing->Messages->Output Control->Message Types->Define Message Types for Scheduling Agreement Release/Expediter中的Fine-Tuned Control: Forecast Delivery Schedule/Expediter
如图

A类型为JIT的release doc,系统默认为LPJ1,我们将其改为LPJ2,之后再生成JIT的release doc,查看输出message, 可以发现默认的消息成为了LPJ2

可以通过菜单(Logistics->Materials Management->Purchasing->Master Data-Messages)来配置message type的条件记录,然后通过TCODE ME9E(Logistics->Materials Management->Purchasing Outline Agreement-> Scheduling Agreement-> Delivery Schedule)输出消息(print out, FAX, EDI等)

此刻,我们输出LPJ1,如图所示,然后查看一下SA release doc的状态,可以发现,还是处于黄灯的未处理状态。


如图,我们再将LPJ2输出,会发现,release doc的状态就成为了已处理的绿灯状态。

处理过后,SA Release doc.状态变为绿灯

如果系统定义的消息在release doc level而不是header level(前面提到的配置)则可以通过查看release doc时,message per release来查看,如图

用系统默认的打印类型,如下

  • Determining the Agreed Cumulative Quantity(允许的累计数量)


在供货商交付货物出现过剩或者短缺的情况时,供货商声称交付的货物数量和我们实际通过GR得到的数量就会产生差异。此刻,我们可以通过联系供货商达成共识,然后将商讨后的结果数量录入SA。
另外,此功能还用于其他用途:SA经常会跨越很多年有效,而在一个财政年结束的时候,累计收到数量(cumulative received)和计划数量(scheduled quantities)通常会重设。累收到数量通常会清零。
可以通过手动输入允许的累计数量和自动产生两种方式。
手动输入操作方法如下,ME32L修改item的additional data.
在修改之前,累计收到数量如下

输入达成协议的数量

保存之后累计收到数量如下

我们刚才的操作,不维护对账日期(Reconciliation Date)但维护允许的累计数量。则累计数量的计算为 起始值=累计收货量+允许的累计数量 所以我们这里是1+5 = 5 这一般应用于与供货商签订了新的SA协议但是又想从原来的累计数量为起始的情况。
这次我们输入对账日期

保存之后累计收到数量如下

在维护了对账日期后,累计收到数量的值 = 累计收货数量-允许的累计数量 我们这里为 4-3 = 1 这一般应用于会计年度更改的情况,我们可以将累计收货数量清零。
我们还可以通过Materials Management-> Purchasing-> Outline Agreement-> Scheduling Agreement-> Administer ->ME88 - Set Agreed Cumulative Quantity来得到系统预先确定了允许累计数量的列表。

  • SA管理


当一个SA有过多的schedule line或者采购历史的时候,可以汇合schedule line 汇合订单历史或者重新分配schedule line的号码。
这些都可以在Materials Management-> Purchasing-> Outline Agreement-> Scheduling Agreement-> Administer下进行操作


(1) 评论    (74) 引用   

国际贸易术语 incoterms

(0) 评论    (236) 引用   

采购合同contract补充

具体图片请见附件 Contract.rar

之前提起过合同,此处补充一些SCM520中涉及的知识

  • Contract types

之前我们曾经提到过,source of supply有3种形式:信息记录;框架协议(合同和计划协议);工厂(用于stock transfer posting)

创建框架协议时并不会包括具体的交付时间和交付数量的数据。根据框架协议的类别有两种途径稍后将这个信息传递给vendor: contract release order 和 scheduling agreement’s delivery schedule


合同与计划协议的区别:

文档数量

在使用合同时,通常会针对合同创建release order;在使用计划协议时,会在新的物料数量和时间确定时,用TCODE ME38维护一条新的delivery schedule line

MRP运行

在MRP运行时,合同可以作为一个source of supply产生采购请求,而后采购请求转化为PO(contract release order)。而在使用计划协议的情况下,可以直接产生delivery schedule line,因此可以省去采购部门的工作。

合同有三种类型:

Quantity contract: 规定某一时期采购一定数量的物料

Value contract:规定某一时期采购一定价值的物料

Distributed contract:这是一种centrally-agreed contract,也就是说创建了以后,其他的SAP系统创建release order也要参照这个合同来创建。数据的交换是通过SAP ALE技术实现。

  • Centrally-agreed Contract

在创建合同时,可以选择指定工厂或者只指定采购组织。如果只是指定了采购组织,则这是一种centrally-agreed contract,在创建release order的时候才会指定相应的工厂。

  • Contract Item category

M(Material Unknown)和W(Material Group)类型的item category可以对应一组物料的需求。选择了这两个类型的合同item不需要指定物料号

M 类型

用于相似物料拥有相同价格的情况。比如各种各样的纸张,虽然样式不同,但是价格近似。M类型需要输入描述和物料组。Release order中也必须输入物料描述。当然,我们也可以选择在release order中采购单位与物料组都与合同相同的物料,如图:

产生了2个release order,不过采购过程各不相同。一个是只输入了short text,另一个指定了具体的物料。都可以作为这个合同的release order。

W 类型

W类型用于拥有同一个物料组,但是价格各不相同的情况。比如同时办公用品,但是笔和本等价格各不相同。所以在创建时,并不需要输入价格。具体的条件和价格只有在创建release order时才会指定。这种item category只能用于value contract.如图

如M类型一样,在PO时,也可以通过输入short text或者精确的物料号两种方式来采购。


(1) 评论    (114) 引用   

Planned Delivery Time Calculation

SAP提供了一个程序,可以优化计划交货时间的设定。

通过菜单Logistics->Materials Management ->Purchasing ->Master Data ->WPDTC - Planned Delivery Time Calculation

可以列出系统在主数据中设定的计划交货时间和实际交货平均时间(PO与GR之间的日期长度) 这样可以对相差较多,不合理的进行更改


(0) 评论    (72) 引用   

自动化采购 procurement automatic

详细图片请见附件procurement_auto.rar


Overview让我们假象一个这样的场景:需求计划的运行自动产生PR,PR自动生成PO。货物交付的结算都是自动完成的。我们只需要手动做GR而已。

自动产生采购申请
首先相关物料的MRP数据要被维护,这样在运行物料需求计划的时候才能产生订单。
另外要有相关的货源数据被维护,比如信息记录或者框架协议(合同和计划协议)。另外,此刻还必须维护源清单(source list TCODE ME01)并标识相关的vendor是与MRP相关的。不过我们一般都选择一个vendor是与MRP相关的,否则系统会将在源清单中排在第一位的作为供货商。如图:


如果我们改变一下5210和1000两个vendor在源清单中的位置,再次MD03运行一下MRP,就会发现1000成了Fixed vendor
自动产生采购订单
可以将指定了供货源的PR自动转化为PO(TCODE ME59N)。因为MRP生成PR的程序和PR生成PO的程序都可以作为后台程序运行,所以如果将这两个程序按顺序安排成JOB,则PO的生成过程就完全自动化了。
但是PR自动生成PO之前,需要有一些配置满足要求才行(如图):
-在物料主数据的采购视图中,自动PO必须被设置
-在vendor主数据中,自动PO必须被设置
-PR必须被制定了供货源


而如我们目前的配置,系统就会报出如下错误:No suitable purchase requisitions found
在我们更改了配置以后再次运行,就会看到如下的成功画面了

评估收货结算ERS(evaluated receipt settlement)用ERS,说明和供货商达成了一致,不必输入发票,而在GR时,SAP自动产生,也就是记货产生发票.

如果想使用ERS,则必须满足以下条件(详细如图):
1.Vendor主数据中必须维护ERS, GR-based选项
2.在PO的header中必须有payment Terms。在vendor主数据中可以定义默认值。
3.PO的item中必须勾选ERS(在vendor主数据中带入);GR-based要被勾选(从vendor主数据或者信息记录带入);必须有税码(可以从信息记录或者合同项中带入);价格不可以是estimated;
4.GR时必须参考PO创建
5.在信息记录中,不能勾选no ERS

在ECC6.0版本中,可以结算delivery cost,通过菜单Materials Management->Logistics Invoice Verification->Evaluated Receipt Settlement (ERS)-> Specify Automatic Settlement of Planned Delivery Costs来激活。
通过TCODE MRRL来执行ERS
在选择屏幕指定一些条件,来对选择条件中的数据进行ERS。如图,我们可以勾选TEST RUN来看一下测试运行的结果已确认是否可以进行ERS

实际运行之后,可以看到FI Doc.一列有FI凭证号产生


(1) 评论    (39) 引用   

contract and source determination

详细图片请见附件contract_src_determin.rar

  • 采购中自动决定供货源

在采购过程中,有很多自动化的步骤可以减低使用部门的工作负担,比如MRP可以自动创建PR,PR可以自动生成PO。而在PR自动生成PO的过程中,有一个关键的步骤,那就是要确定从哪个供货商采购。

在PR中,系统会列出供货商列表并可以建议我们选择哪家供货商,我们可以手动指定供货源。如下图

但这个过程也可以自动化,也就是说MRP产生需求生成PR之时,系统也自动帮我们指定了供货源。为了检查这个自动化指定过程的正确性,可以使用审批策略。关于审批策略,SCM520会有详细探讨,到时会研究讲解审批策略,因为目前网上我找到的审批策略的文档十分简略。

  • 供货源与供货源指定

关于货源有外部供货商和内部工厂两种。外部供货商的表现形式为信息记录和框架协议。框架协议包括合同和计划协议。具体的交货数量和交货时间,是在合同的release order和计划协议的计划交货行项目中指定的。

  • 合同 Contract

合同可以参考PR,报价或已有的合同创建。

合同的类型有两种,数量合同和价值合同

参考相关的合同所创建的PO叫做contract release order,在合同的明细项里能看到生成了的release order.

通过如图菜单或者屏幕上按钮可以看到release order

  • 源清单Source List

源清单在采购与需求计划自动决定供货源时会产生作用。可以设置fix和blk,使得某一特定时期固定从某个货源采购或者某个时期禁止从某个货源采购。

在MRP运行自动产生的PR中,源清单中,设置了MRP-relevant标志的,会被考虑在内。

如果在物料主数据的采购视图中,维护了源清单这个字段,则在做采购时,供货商必须在源清单中维护,否则如图,系统会产生错误信息。

我们也可以在后台维护(Purchasing->Source List->Define Source List Requirement at Plant Level),工厂级别的源清单是否必须维护选项,之后,整个工厂的采购都必须在源清单的控制之下,如图


(1) 评论    (200) 引用   

MM采购中的MRP简介

详细图片请见附件MRP_MM_inBrief.rar

l Overview

运行物料需求计划可能产生如下几种获取元素:Planned Order; PR; Scheduling agreement schedule line

内产情况下:系统生成计划订单,并可将计划订单转化为生产订单

外购情况下:系统生成计划订单或者采购申请。这两种都是SAP的内部订单形式,如果产生的是计划订单,只有当MRP控制者将其转化为采购申请才可进行采购。如果有物料相关的计划协议存在并且设置为与MRP的source list相关,则也可以生成计划协议的计划行。


MRP发生在工厂级别或者MAR范围级别。

要想运行需求计划,必须在相关工厂激活MRP(Materials Management->Consumption-Based Planning-> Planning->Activate Material Requirements Planning)并维护了相关的参数(Materials Management->Consumption-Based Planning-> Plant Parameters-> Carry Out Overall Maintenance of Plant Parameters),最后当然还要确保物料主数据中MRP相关的数据被维护。

MRP的运行可以进行单项的也可以进行总计划。

总计划指的是对一个工厂后者计划范围运行需求计划,包括了此工厂所有的MRP相关的物料以及具有BOM的相关物料。(Logistics->Materials Management ->Material Requirements Planning(MRP) ->MRP Planning ->Total Planning)

单项计划指的是对某个特定的物料运行需求计划。单项计划有单层和多层之分。单层只会在所选定的物料所在BOM级别运行,而多层会在选定物料和它之下的BOM级别运行。单层单项Logistics ->Materials Management ->Material Requirements Planning(MRP) ->MRP ->Planning ->Single-Item,Single-Level

l MRP过程和批量大小(Lot-Size)

在物料主数据中通过维护MRP Type和Lot-Size来定义不同的MRP过程。

原则上,MRP过程主要有基于消费(consumption-based)和基于MRP(MRP-based)两大类。

1. Consumption-based

Consumption-based主要是面向过去已经消费的物料来做计划,比如销售订单,独立的需求计划。

在面向消费的计划中有如下几种过程:

n Reorder point planning

n Forecast-based planning

n Time-phased material requirements planning

Reorder Point

再订货点(Reorder Point)在物料主数据中维护,一旦库存低于这个数量,就会将此物料加到物料需求计划中。

再订货点分为手动和自动两种方式。手动方式是由MRP控制者输入的。自动方式是由系统预测自动计算出来的。

当MRP类型是PD时,我们更改了再订货点,运行MPR(MD03),用MD04可以看到也没有任何order产生,因为再订货点只和reorder point planning和time-phased planning的MRP相关。

之后MRP类型改为VB,也就是手动再订单点计划,再运行MRP。MD04可以看到,有Planned Order产生

当定义再订货点时,必须考虑一下几个值:安全库存;当前的物料消费或者未来的需求;补货提前时间(RLT).其中,安全库存要覆盖掉计划外的物料消费和物料交付的延迟。

Reorder point planning是将可用仓库库存(仓库实际库存+已订货库存:采购订单;确定的计划订单;确定的采购申请)与再计划订货点比较,来决定MRP的运行结果。

Forecast-based planning

未来的需求是基于消费物料数量计算出来的。预测计算是每隔相同一段时间段后运行。

Time-phased planning

l 静态批量大小(Static lot-size)

MRP运行后,需要获得的物料数量是由批量大小(定义在物料主数据中)程式决定的。在批量大小计算过程中有三组:Static lot-sizing procedure(静态分批处理);Period lot-sizing procedure(期间批量大小);Optimum lot-sizing procedure(最优批量程式),每种批量大小具体属于哪个组,在配置(TCODE OMI4)中指定。

这里我们介绍静态分批处理程式。

静态分批分批处理程式并不考虑未来的物料短缺,所以一旦出现了物料短缺,系统会创建order提案来满足当前的,一个静态值的短缺。

如果批量大小指定的是精确的批量大小类型(比如直接按批订货量Lot-for-lot order quantity)则系统会使用精确的短缺值来订货。如果一天之内有很多GI,系统会只产生一个订单来满足短缺。

如果指定的是固定批量大小,系统会使用固定的数量来尝试满足物料短缺。如果一次无法满足,系统会在同一天生成多个订单,直到短缺被满足。

我们可以看到再订货点虽然是5,但是运行了MRP之后,看到的是产生了数量10的订单。

当然,也可以指定Replenishment up to maximum stock level(lot-size: HB) 一般这是由容器的容量限制所致。每次补货都补充到仓库的最大容量值。

具体请参考SAP help

http://help.sap.com/saphelp_45b/helpdata/en/f4/7d281f44af11d182b40000e829fbfe/frameset.htm

l 日期的计算

当计算出了货物需求和数量以后,就要计算货物采购,交付等的具体时间了,以满足生产需求。因为我们是在讲MM的采购,所以以外购为例,见下图

如图,物料的可用日期包括采购处理时间,计划交付时间和收货处理时间。而采购处理时间实在后台配置的Materials Management ->Consumption-Based Planning ->Plant Parameters->Carry Out Overall Maintenance of Plant Parameters

计划交付时间从发出PO到收到货物过程所用的时间。这个时间可以在物料主数据,信息记录和合同中维护,此时间是日历天数。

收货处理时间从收到货物到货物可用过程所用的时间。可以在物料主数据或者合同中维护,为工厂工作日。


(1) 评论    (32) 引用   

MM自动过账 automatic posting

在网上突然发现这个资料,与大家共享。早知道有人写过,我还费劲写什么valuation class啊,多亏我没继续写,否则做了无用功。

见附件吧~~详解自动过账.rar


(1) 评论    (81) 引用   

服务采购简介

具体图片请参考附件 Procurement of External Service.rar

Procurement of External Service

关于服务的采购,SAP有专门的一个培训LO540(新版本叫SCM540),此处只先做简略介绍。待专门研究SCM540时再详细将各个部分分解。

l Basic Process

l Service master record and Condition

TCODE: AC03

如下图,服务主数据包括:号码,类别,描述,基本单位;物料组和评估类别等,它可以被用于PS PM CS MM等模块。

可以像普通物料采购那样创建条件,以便在PO时决定价格

条件也有一些层次级别:在服务层别;在服务,供货商,采购组织层别;在服务,供货商,采购组织和工厂层别。

可以在Materials Management->Service Master->Service->Service Conditions下找到相关定义菜单。

l PO for Service

Item类别用D(Service)account assignment可以用U

对于服务的采购有一定的特殊性,可以设定一个维护价值上限,来保证这种非计划服务采购的成本控制。

因为采购一项服务可能包含很多步骤,比如关闭机器,移除旧零件,更换新零件,检查,测试等等,所以需要维护service specification

采购服务时是必须指定account assignment category的。

对服务建PO的时候不可以指定物料,只填写简略描述,在SSservice specifications)中指定各项服务的数量,价格等。

如下图所示为服务采购创建一个PO

l Service Entry and Invoice Verification

与实体物料的采购不同,服务的采购不用GR的过程,取而代之的的Service Entry Sheet,而且通常此操作由两步组成:create entry sheet, accept entry sheet,不过也可由一步直接完成,在输入时就做了承认。只有在做服务承认的时候,才会产生相关的会计凭证。

具体操作如下,TCODE ML81N

如果release策略允许的话,我们可以直接在输入service sheet时就accept

service sheet没有被accept之前是不能做IR的。

在整个流程做完之后,PO history中列出了相关的物料凭证,发票和服务条目表


(2) 评论    (98) 引用   

Blanket Pruchase Order简介

具体图片请查看附件 Blanket Purchase Order.rar

Blanket Purchase Order

当我们要长期从某个供货商采购一批消费品时,为了节省采购成本(指的是在系统中处理的人力成本),可以不按照传统采购的PR-PO-GR-IR这样的过程。比如对office采购1年所用的水性笔,每次订货都进行这样一个过程太繁琐了。这时可以使用Blanket PO。整个PO只是一个总价值的采购,不需要做GR,只在收货时做IR就可以了。而且也不必麻烦的应用contract release order或者scheduling agreement

Order Type: FO (Framework Order)

必须输入有效期间

Item Category: B (Limit)

限制:必须输入account assignment category;不能输入物料号;GR等栏位不可输入

整个Blanket PO只是规定了在某一个期间一共要买多少价钱的物品,没有具体的物品数量,取而代之的是固定的1 AU(Activity Unit)。也不会输入物料的单价,而需要输入一个期待购买的总价值。

关于item category如何限制的,可以参考后台配置Purchasing ->Define External

Representation of Item Categories 不过只能查看,无法修改

  • SAP预定义的item category

Standard: 向外采购物料标准选项,限制较少

Limit: 以限定的总价值采购消费品或者服务

Consignment: 客户在我方寄售的物料,无价值。需要做non-valued GR,不可以指定account assignment 不能做IR

Stock Transport Order:物料在工厂间传送

Third-party Order:供货商直接将货物发给第三方,比如我方的客户。但是供货商会给我们出具发票。

  • IR

对一个blanket PO做IR需要如下输入

当我们做了两次IR之后,ME23N查看这张PO, limits tab中的实际值已经变成了1000。而history中可以看到这两张invoice


(0) 评论    (60) 引用   

consumable material采购小结

详细图片请见附件Consumable Material.rar

Consumable Material种类1. 没有物料主数据
2. 有物料主数据,但是没有库存管理
3. 有物料主数据,也有库存管理,但是只管理数量,不管理价值
Stock Material 和Consumable Material区别
多个Account Assignment items
如果有多个account assignment项,做partial invoice,可以有两种方式:
对各个项按照数量或者比例进行分配;按照item的顺序一个一个做
如图:

此选项可以从account assignment category集成而来。在后台中配置如下

PR-Tracking Status可以通过status tab来追踪此PR的后续状态,比如是否相关PO被创建,是否相关明细被转成大纲协议等。

PR-Valuation Price
如果物料主数据存在price,则会带入Valuation Price;否则需要手动输入
从一个PR创建PO,如果采购的物料具有主数据,PO首先会判断是否有info record存在,并将相关的价格带入PO;如果没有info record存在则需要手动输入,PR中的价格并不会带入PO
如果采购的物料没有主数据,PR中的价格会带入PO
Valued GR, non-valued GR, no GR如果有多个account assignment 明细,则PO中Non-valued GR选项会被自动勾选。


(0) 评论    (127) 引用   

创建Purchase Order画面中的一些选项

具体图片请见附件Purchase Order option.rar

Purchase Order中的一些选项

  • Goods Receipt


如果goods receipt没有勾选,则此PO不需要做GR

  • GR non-valued

如果GR non-valued勾选,则在做GR时,不会对物料做valuation,直到IR时才会进行


我们看到GR后没有FI的凭证产生以记录到相关科目


IR时则有相关FI凭证产生,来记录到consumable raw material里

  • Invoice Receipt

如果没有勾选此项,则PO不会做IR。也就是说这批货物是免费的。


当作IR时会看到如下提示:没有需要做IR的item

  • GR-based Invoice

做Invoice必须基于收货,也就是每做一笔GR,才可以做相应这笔GR的IR。如果不勾选此项,则不做GR就可以做IR。并且如果有partial delivery的情况,只做了一部分的GR就可以做全部货物的IR。


创建了PO以后马上用TCODE MIRO做IR看到是可以过得,并且因为没有GR,所以总价钱和数量都是可手动输入的。


如果将这个FLAG勾选再,不过GR就做IR,可以看到屏幕提示没有合适的item可以做IR。


(0) 评论    (274) 引用   

采购之Planned delivery cost & Unplanned delivery cost

详细图片请见附件Delivery Cost.rar

  • Planned Delivery Cost

在创建PO的时候就会将运费计算进去(比如在item condition中加入FRB1 condition type)。在做GR的时候会将运费计入Freight clearing acct. 并在做IR的时候,进行清帐,将运费计算到stock科目中。


在做IR时注意如图所示的位置选择3 就是货物和运费一起输入发票,否则只会把货物的价值或者发票的价值单独带出来。


在GR IR时实际产生的会计凭证如下

  • Unplanned Delivery Cost

只在IR的时候才发现供货商有额外的运费发生,输入在发票里,则GR中只会按照正常的计入GR/IR Clearing acct.,在IR时将额外的运费直接计入stock account中。

如图,做IR时在details tab中输入运费

GR IR时产生的会计凭证如下

P.S. 可以通过系统配置,来指定unplanned delivery cost在IR时,是自动分配到各个明细项中还是计入一个特定科目。此处我们自动分配到明细项中。OBYC的UPF transaction配置这个指定科目。请参考SAP的automatic postings

IMG->Materials Management -> logistics invoice verification->incoming invoice->Configure how unplanned delivery cost are posted

如果是SPACE则会将运费分配到各明细项,如果是2,则会计入指定的G/L科目


(2) 评论    (18) 引用   

物料主数据之Standard Price&Moving Average Price

具体图片请见附件MMPrice_SA.rar

l Posting to Standard Price

在创建新的PO,收货之前,库存和物料主数据中的状态如下。

后台OBYC中,BSX的业务配置inventory posting的账户,在系统里,valuation class 3000对应的科目为300000(Z-ROH-DV01物料的v class配置的3000,关于valuation class请参考我的相关Blog)

业务WRX配置的已收货/以收发票清算科目 配置为191100

业务PRD配置的成本价格差额科目 281500

我们创建一个收货的流程,PO->GR,采购100个,价格为2.4块。这样的话,库存应该变为200个,而因为采用S价格,所以库存价值为2 x 200 = 400 而已收货/以收发票清算科目却要按照实际的2.4 x 100 = 240元,差额为40元,这就需要用成本价格差额科目来使借贷达到平衡。

也就是说借记200元库存科目。

借记40元成本价格差额科目

贷记240GR/IR clearing acc.(已收货/以收发票清算科目)

那么我们去系统里实际查看一下。

GR/IR Clearing acc.则如下

成本价格差异科目如下

由于科目300000设置了不显示行项目,所以我们来查看实际产生的凭证

我们这时再看这个物料的moving price 已经变成了2.2 440/200 = 2.2

之后假设我们收到客户的发票,发票的每个物料单价为2.2元,则总价为220元,与GR时相差了20元。做这步之前,请TCODE OMR6确认测试的公司代码下,发票冻结相关的容差组容许有20元的发票容差。发票校验是SAP MM培训单独的一门课程,容差组也有很多选项,以后再讨论。操作截图如下:

那么相应的科目是如何记账的呢?

首先,GR/IR Clearing acc.是一个中间过渡科目,是需要清帐的。所以首先要借记这个191100科目240元。因为客户发票中物品的价格为220元,差额20元,需要贷记Expenditure/income from price differences科目20元。最后相关供货商的AP账户(这里是1000)贷记255.2(含税,并会进入相关的统驭科目)以及相关进项税科目。

产生的会计凭证如下

需要说明一下,由于我使用的系统配置为发票与库存价值差额进入了281500这个科目,一般可设置为另一个科目,叫做Expenditure from price differences

这时再查看一下物料的moving average price2.1元。 因为库存价值降低,有440元变为420元。420/200 = 2.1元。

l Posting to Moving Average Price

首先查看一下在做采购之前物料Z-ROH-DV03的状态和库存状态(初始库存可以用MB1C 移动类型561来做taking)

而用平均移动价格做posting的科目设置与之前相同。

接下来采购100个物料,PO->GR,这批物料的单价为2.4元。则在收获过后库存增加了240元,总价为440元,所以平均移动价格为440/200 = 2.2元。而GR/IR Clearing acc.240元。

由于库存增加价值与实际GR的价值没有差异,所以不需要像使用标准价格那样有一个账户记录差额。

通过生成的会计凭证可以看到这个差异

GR过后物料主数据中价格和库存状态如下

库存总价值440 平均移动价格为 440/200 = 2.2

之后收到客户发票,物料单价为2.2元,则物料总价值为220元,与之前的库存价值价额20元。与前面一样,GR/IR Clearing科目是一定要被清帐的。而物料的差额20元则贷记库存科目。其他科目与之前相同。

产生的会计凭证如下

物料的平均移动价格如图所示为 420 /200 = 2.1


(0) 评论    (193) 引用   

创建Info Record的几种方法

详细图片请参考附件。SAP info.Record.rar

创建SAP采购中重要的主数据之一info record有如下3种方式:手动(ME11);通过Quotation自动创建;通过PO或者outline agreement自动创建;

看一下后两种方式:

首先ME13确认,并不存在一个我们想创建的info record

之后创建相关物料的RFQ并作Quotation

注意Quotation中的这个字段InfoUpdate 其中有如下选项:

No update

A Update with or without plant

B Update with plant (if no plant ban)

C Update without plant (if no plant requirement)

我们首先选默认的No update 然后对报价进行保存,ME13可以看到依然没有Info Record被创建,因为是No update

如果选择A,相应的condition都会被这个报价中的price所更新。

但是更新规则如下,如果有plant level的话,相应的plant level会被更新,如果没有的话,更新general level

我们来确认一下。

但是我们会发现一个现象,那就是再次查看这个报价,会发现InfoUpdate自动变成了C,也就是without plant,而且info record中也会提示没有plant specific的数据。这是因为我们之前没有维护过任何和plant相关的数据,根据A的规则,创建通用数据的condition。而因为没有plant数据,所以这个flag也变成了C,也就是说维护与plant无关的condition

如果之前我们先创建一个与工厂相关的Info record,然后再选择flagA的报价,看看condition是如何更新的。

可以看到,如果这样做的话,与工厂相关的info rec.就被更新了,而general级别的却还是没有condition。而报价中的flag也自然而然的自动变成了B,也就是说如果没有工厂,则不做更新。

用报价来创建和更新info record就是这个道理。

如果在PO中呢?PO中并不会更新condition。而只是影响info record中的last PO number一个字段而已。如果创建

备注:

我们以上的实验前提都是在condition可以存在于Plant level的前提下。条件永远都与采购组织相关联,但是也可以设定为与plant相关。默认情况下,我们一般都会允许工厂级别的条件存在,配置更加灵活,除非需求真的是将所有工厂都统一用一个价格。这个在后台的配置中

Purchasing -Conditions-Define Condition Control at Plant Level

可以指定是否只允许工厂级别的条件存在;是否不允许工厂级别的条件存在

如果我们不允许工厂级别的条件存在,则ME11指定工厂时会得到错误消息。


(1) 评论    (277) 引用   

[收藏]sap采购价格条件技术 Purchase pricing using SAP condition tech

本来想自己写一篇关于condition的,可是发现网上有了一篇比较完善的文档。

直接参考这个就会比较清楚SAP的条件技术如何应用于定价了。sap采购价格条件技术.rar

那么价格主要存在于info record这个主数据中,关于info record我也有blog描述。

我想补充的是PO中价格的决定这一个小方面。

SAP在创建PO时,首先会搜索info record,如果维护了价格,则会应用它。如果没有维护价格,则会从Info record中搜索last PO这个字段,找到应用了此info rec.的最后一个PO,然后将这个PO中的价格应用于当前PO。

不过我们也可以通过后台设置来做一些改动。

具体通过TCODE OMFI,定义一个组,然后在price adoption选项中,有always copy; Not if price entered manually; Do not copy三个选项来定义从上一张PO中copy价格的选项。然后在SU01客户的parameter中,通过EVO这个parameter ID来配置。


(0) 评论    (292) 引用   

SAP收货时自动创建采购订单

http://www.itpub.net/viewthread.php?tid=1072763

在实际业务中,常常出现到货物料没有订单或订单未批准的现象,按照SAP的标准流程,应该拒绝收货。但在实际业务中,这些物料可能是紧急采购的急件,如不及时处理,将会影响生产计划的安排。对于这种特殊情况,其实SAP有很灵活的处理方式,即由收货自动创建订单。需要说明的是,这种操作方式并不是SAP推荐的,不应在实际业务中大量采用。
  具体流程如下:
   1.移动类型101已在后台设置为自动创建定单。具体方法是:进入IMG后台,物料管理->总量控制->收货->自动创建采购订单,双击进入后,将101 GR收货的第三项“自动产生的采购订单”勾上。
  2.准备采用自动创建订单的工厂已指派给一个标准的采购组织。正常使用的SAP系统这项应该是已配置的,如未配置请到IMG后台,企业结构->分配->物料管理->给工厂分配标准采购组织。
   3.供应商主数据在采购组织下已设置成允许自动创建采购订单。例如,在事务XK03的“采购数据”视图的“控制数据”栏,将“自动产生的采购订单”勾上。
   4.要采用自动创建订单的工厂在后台货源清单的工厂层应激活。具体方法是,进入IMG后,物料管理->采购->货源清单->定义工厂层的货源清单需求,双击进入后,将需启用的工厂第三栏“货源清单”勾上。
   5.物料在工厂的货源清单已建立。经实际试验,其实只要能保证物料的货源清单被建立,第4项实际上可以省略。
   6.物料主数据中已设置为允许自动创建采购订单。例如,在事务MM02的“采购”视图,将“自动采购单”勾上。
   7.物料的相应信息记录已创建,价格条件正确。
  完成了以上设置,在MB01做101收货时,当未输入采购订单时,系统将为你自动创建采购订单。以上在SAP/R3 4.5B上测试通过。

(1) 评论    (29) 引用   

物料主数据之shelf life data

如果想在GR时进行shelf life检查先要在系统中进行配置

The shelf life expiration date of a material can only be checked if

  • the minimum remaining shelf life is maintained in the material master record
    The minimum remaining shelf life is the time the material must still be usable, so that the goods receipt is accepted by the system.
    You can define the time unit the system uses in the storage data of the material master record in the Period ind. field.
  • the shelf life expiration date check is active in the plant
  • the shelf life expiration date check is active for the movement type

配置路径为IMG->Materials Management->Inventory Management and Physical Inventory->Goods Receipt->Set Expiration Date Check

在对PO进行goods receipt的时候会有如下基本的几个check:

  • 是否是正确的物料
  • 是否是正确的数量,或者有没有交付多了
  • 易腐败食物是否在其保质期内

那么我们看这个质保期的check是如何实现的。
首先,要在后台配置哪些收货的过程与质保期check相关。


其次,质保期首先要在物料主数据的plant data/stor.1 view里进行维护。
这里面有两个字段比较重要:Min. Rem. Shelf Life和Total shelf life

SAP Help的解释如下

Minimum Remaining Shelf Life

Minimum amount of time for which the material must keep upon goods receipt for the goods receipt to be accepted by the system.

Total shelf life

Period for which the material will keep in total, that is, from the date of production to the shelf life expiration date.

Use

  • Value entered in the material master record
    The system assumes that the date entered upon goods receipt is the material's date of production. It then calculates a shelf life expiration date from the date of production plus the total shelf life.
  • No value entered in the material master record
    The system assumes that the date entered upon goods receipt is the material's shelf life expiration date.

In both cases, the system updates the shelf life expiration date in the batch master record and in the material document if the goods receipt is accepted.

我们用具体的实例看看这两个字段是如何影响收获的质保期CHECK的。

首先,只配置Min. Rem. Shelf Life。如果只配置了这个字段,则必须在GR FOR PO时输入过期时间。如果过期时间与入库时间的期间段少于配置的Min. Rem. Shelf Life,则系统会报错。

在此示例中,因为从入库到过期这段时间短于物料主数据中配置的Min. Rem. Shelf Life

下面我们在物料主数据中维护Total Shelf Life 设置为5天。

如果这个字段被维护了,则在GR时必须输入物料的生产日期,否则系统会报错。

那么从生产日期到收货日期,不能超过物料的total shelf life,否则系统会报错。这证明还没有收货,货物就过期了。

而如果自己此时手动在GR过程中输入了过期时间,这个时间如果与物料主数据维护的数据所计算的结果不同,系统会产生消息,提醒被改为系统计算的时间。至于会报E还是W型,取决于系统配置。


(1) 评论    (10) 引用   

vendor主数据之vendor subrange

Vendor Sub-Ranges(VSRs)在SAP中的解释为

A subdivision of the full range of products offered by a vendor (e.g. the Henkel company has the subranges "adhesives" and "washing powder").

Individual conditions apply for each individual subrange. If a vendor has subranges, each item offered by the vendor must be assigned to the appropriate subrange to enable the system to correctly determine the conditions for the subrange.

举个简单的例子,我创建了一个叫做DELL的供货商,会向其采购台式机和笔记本,但是台式机和笔记本这两种物料在采购过程中有很多不同,比如生产的工厂不同,比如付款的条件不同,等等,但是理论上这都属于DELL这个vendor,那么为了在采购中有所区别,可以为vendor主数据建立sub-range 每一个sub-range可以维护不同的purchasing和partner数据。

首先,我们新建一个account group,其中配置这个acct grp中的vendor是与sub-range相关的

之后配置这个account group所允许的partner role。此处配置与sub-range无关,但是是acct grp配置的必须步骤。以后会介绍partner决定相关的配置。

之后我们创建一个演示用的vendor,对其建立sub-range

之后在purchasing相关数据编辑中,有一个sub-range的按钮,点击以后可以创建sub-range

这里我们创建两个sub-range

之后点击alternative data会提示我们并没有数据被创建,我们选择Yes创建sub-range的数据

其中在popup中会有checkbox让我们选择,哪些数据需要被创建。这里我们把purchasing data和partner都创建。

我们对不同的sub-range设置不同的Order address

之后,假设有两个物料,分别属于此vendor的两个sub-range。则为他们创建Info. record时,可以指定sub-range。这样在创建PO的时候,就会自动带入,purchasing data以及partner等都会不同。这样sub-range便完成了对vendor的分隔。如果对order address方有confirm letter等发出,则系统会自动分辨。另外,condition价格配置方面,也可应用sub-range


(0) 评论    (9) 引用   

物料主数据之Configurable Materials

我们采购一个物料的时候,有可能这个物料有很多可变的参数。比如SAP为汽车制造业提供的解决方案就充分的利用了LO Variant Configuration 比如汽车的颜色。如果参数很多,为每一个可能都建立一个物料主数据是十分麻烦的,所以SAP提供了物料配置的功能。使得我们在采购和销售物料时,可以指定参数。

那么在SAP关于采购的help中提供了一个最简单的示例,就是配置公司采购的信封,信封有尺寸和是否具有logo等可配置属性。

具体操作步骤可以参考 http://help.sap.com/saphelp_47x200/helpdata/en/9f/fb79385feddf6ae10000009b38f8cf/content.htm

最终配置的效果如下


(0) 评论    (290) 引用   

物料主数据之Variable Units of Measure

在物料主数据的purchasing view中,有Variable Units of Measure这么一个字段。

SAP Help的解释是

Variable Units of Measure

In the material master record, you can specify that the material can be procured in a unit of measure that differs from the order unit.

If the material can be ordered in more than one unit of measure, enter

1

in the Variable order unit field.

让我们来做下实验。

如果此字段为空,采购单位为BAG,则在建立PO时,如果将单位改为PC,则系统会自动改回BAG并提示无法改为PC。

如果此字段设为1,建立PO时,将单位改为PC,则可以通过。


(0) 评论    (11) 引用   

配置consumable material采购时,G/L科目的自动确定

我们知道PO的采购有三种,第一种 stock material 第二种 consumble material 第三种 external service

那么stock material我们可以在新建物料主数据的时候,建立accouting view,然后在acct view 1中,指定valuation class来达到account determination的目的,这个我之前的BLOG也有简单的介绍。

可是在consumable material采购的时候,我们知道是可以不输入物料号,直接输入short text 然后输入account assignment category来直接进行采购,因为此种物料没有库存,直接POST到FI的会计科目中。那么比如我们acct assignment cat.选择K(cost center) 如何让G/L account自动带出来呢? 这个可以通过对material group的配置来达到

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

通过这个路径,对不同的material grp配置不同的valuation class.这里我们对007 group分配了3200,其他的保持空白default值

之后就像stock material一样,我们配置valuation class 我们将用COST CENTER做测试,所以transaction选择GBB 其中general modification选择VBR 我们看到valuation class是空白的 G/L acct 400000以及3200的G/L Acct 417000

之后我们ME21N建立一个PO 采购消费物料,material group选择001,由于001没有设置valuation class 所以在控制中默认是空白,我们看到G/L Acct被正确设置了

我们再来测试一下007这个group,看到 G/L Acct也被正确设置了。整个配置就是这个过程


(2) 评论    (237) 引用   

SAP Note 496082 - FAQ: Account assignment in purch

This note provides answers to frequently asked questions concerning account assignment in purchasing documents.

List of questions

1. Why is the G/L account for a sales order with non-valuated customer sales order stock different from the account with valuated customer sales order stock?
2. Can I create several assets in the new purchasing transactions at the same time?
3. You create a purchase order with account assignment using Transaction ME22. You enter a material group, from which a G/L account is determined via the valuation class. If you go to a material group that does not determine a G/L account via the valuation class, the system deletes the previous G/L account and prompts you to enter a G/L account. If you cancel the account assignment screen and change back the material group on the item detail screen, the previously determined G/L account is not determined again. Why is that?
4. Is there an easy way of entering the same account assignments for different items in the new Enjoy transactions?
5. Why does the repeat account assignment function not work in the new Enjoy transactions when I create new account assignments in the multiple account assignment?
6. Why does the system generate message KI161 'Cost center does not exist on &' when I change the account assignment of an existing purchase order? The same thing happens for other account assignment objects (for example, profit center).
7. Can I create assets from within the single account assignment screen?
8. Why does the system not display an account assignment tab page even though I have entered an account assignment category?
9. Why does the system sometimes derive account assignment objects even though the corresponding field on the account assignment tab page is hidden??
10. You create a purchase order with reference to a subcontracting purchase requisition. This purchase requisition was created with an unknown account assignment, that is, account assignment category 'U'. When you change the account assignment category in the purchase order, the system issues error message ME453 'Changing consump. or spec.
11. Why can I not select a valuated goods receipt together with multiple account assignment in a purchase order/purchase requisition?
12. Funds Management is active. Why are the fields EBAN-FISTL, -GEBER, -KBLNR, -GRANT und -FKBER (as in table EKPO) empty?
13. You want to change a purchase order item with account assignment category 'A' which contains a locked asset. The system displays error message AA 334: 'You cannot post to this asset (Asset & & blocked for acquisitions)'.
14. What is the meaning of the indicator for the account assignment screen that I can set in Customizing for Single account assignment/Multiple account assignment?
15. Is there an unknown account assignment for standard purchase orders?
16. You change data in a purchase order item (for example, purchase order value, delivery date, and so on). The system does not check the account assignment again.
17. If you delete all entered account assignment lines in the account assignment screen, the system exits the account assignment tab title and goes to the material data. In addition, the system displays an error message telling you to enter account assignment data for the item in case of an account assignment.
18. Which account assignment categories should I enter in schedule line categories for third-party order processing (CS) and individual purchase order processing (CB)?
19. You subsequently change the material group in a limit purchase order or in a purchase requisition assigned to an account. Even though the new material group is assigned to another G/L account via the valuation class, the system does not redetermine the account assignment of the item. The old G/L account remains.
20. In Customizing, you can set the account assignment fields as mandatory, optional or display fields or as completely hidden fields, depending on the account assignment category. These settings also determine whether or not the system deletes the values of the account assignment fields when you change the account assignment category in a purchase order item.
21. You create a purchase order item assigned to an account with reference to a purchase requisition. You create a second schedule line for this purchase order item with reference to another purchase requisition. The system ignores the account assignment data of the purchase requisition for the second schedule line.
22. Why can I undelete an item in a purchase requisition if the corresponding account assignment data is no longer valid?
23. You create a purchasing document with reference to a reference document. What account assignment data is transferred?
--------------------------

1. Question:
Why is the G/L account for a sales order with non-valuated customer sales order stock different from the account with valuated customer sales order stock?

Answer:

Refer to Note 458270.
--------------------------

1. Question:
Can I create several assets in the new purchasing transactions at the same time?

Answer:

It is possible to create several assets at the same time. However, you must ensure that there are enough account assignment lines for the number of assets you want to create. You can insert additional lines using the copy function.
--------------------------

1. Question:
You create a purchase order with account assignment using Transaction ME22. You enter a material group, from which a G/L account is determined via the valuation class. If you go to a material group that does not determine a G/L account via the valuation class, the system deletes the previous G/L account and prompts you to enter a G/L account. If you cancel the account assignment screen and change back the material group on the item detail screen, the previously determined G/L account is not determined again. Why is that?

Answer:

Unfortunately, we cannot change this system behavior. First, enter any G/L account so that the item is valid. If you then go to the old material group again, the system determines the correct G/L account.
--------------------------

1. Question:
Is there an easy way of entering the same account assignments for different items in the new Enjoy transactions?

Answer:

Ensure that Note 315676 is implemented in your system and follow the procedure described there.
--------------------------

1. Question:
Why does the repeat account assignment function not work in the new Enjoy transactions when I create new account assignments in the multiple account assignment?

Solution:

Use the copy function in the multiple account assignment to create identical account assignment lines. With the repeat account assignment function you can create similar account assignments for different items with the same account assignment category. To do this, proceed as described in question 4.
--------------------------

1. Question:
Why does the system generate message KI161 'Cost center does not exist on &' when I change the account assignment of an existing purchase order?
The same thing happens for other account assignment objects (for example, profit center).

Solution:

Refer to Note 193371.
--------------------------

1. Question:
Can I create assets from within the single account assignment screen?

Solution:

Assets can only be created from the multiple account assignment screen ('Account assignment' tab page).
You can change between single account assignment and multiple account assignment in the 'Account assignment' tab page by clicking the icon in the upper left corner.
--------------------------

1. Question:
Why does the system not display an account assignment tab page even though I have entered an account assignment category?

Solution:

When you have implemented Note 520149, the system only displays the account assignment tab page when you have entered all required information, for example, the company code.
--------------------------

1. Question:
Why does the system sometimes derive account assignment objects even though the corresponding field on the account assignment tab page is hidden??

Solution:

Refer to Note 619203.
--------------------------

1. Question:
You create a purchase order with reference to a subcontracting purchase requisition. This purchase requisition was created with an unknown account assignment, that is, account assignment category 'U'. When you change the account assignment category in the purchase order, the system issues error message ME453 'Changing consump. or spec.

Solution:

Refer to Note 205597.
--------------------------

1. Question:
Why can I not select a valuated goods receipt together with multiple account assignment in a purchase order/purchase requisition?

Solution:

Refer to Note 204252.
--------------------------

1. Question:
Funds Management is active. Why are the fields EBAN-FISTL, -GEBER, -KBLNR, -GRANT und -FKBER (as in table EKPO) empty?

Solution:

The system only fills these fields if the account assignment category is set to 'blank'. If you maintain an account assignment category in the purchasing document, the system transfers the information in these fields to the EBKN table (as in EKKN).
--------------------------

1. Question:
You want to change a purchase order item with account assignment category 'A' which contains a locked asset. The system displays error message AA 334: 'You cannot post to this asset (Asset & & blocked for acquisitions)'.

Solution:

This is standard system design. To change this purchase order item, you have the following two options:

a) If you no longer require the purchase order item with the blocked asset, delete the purchase order item.
b) Otherwise, activate the asset, make the required changes to the purchase order item and then block the asset again.
--------------------------

1. Question:
What is the meaning of the indicator for the account assignment screen that I can set in Customizing for Single account assignment/Multiple account assignment?

Solution:

The indicator determines the account assignment screen that is generally used for maintaining the account assignment of a purchase order item.
For the EnjoySAP transactions, this value is a proposal that you can change in the purchasing document.
For the old transactions, this value is the only value you can use.
--------------------------

1. Question:
Is there an unknown account assignment for standard purchase orders?

Solution:

In general, this is not allowed, and the system displays message ME 069 'Unknown account assignment not assigned for user here'. Service items that you create with item category D (Service) or B (Limit) are an exception in this respect.
--------------------------

1. Question:
You change data in a purchase order item (for example, purchase order value, delivery date, and so on).
etc.). The system does not check the account assignment again.

Solution:

This is standard system design. If the system has already checked the account assignment without errors when you created the purchase order item, it only checks the account assignment again if you change a field that is relevant for the account assignment (for example, quantity, material number, and so on).
If this system response does not meet your requirements, implement the account assignment check in the ME_PROCESS_PO_CUST BAdI. The system calls the BAdI each time the purchase order is changed.
--------------------------

1. Question:
If you delete all entered account assignment lines in the account assignment screen, the system exits the account assignment tab title and goes to the material data. In addition, the system displays an error message telling you to enter account assignment data for the item in case of an account assignment.

Answer:

If you delete all account assignment lines, the system assumes that you do not want to maintain account assignment data.
This is in conflict with the account assignment category and the system issues error message 06436. You can remove the account assignment indicator.
Procedure:
If you want to delete all entered account assignment data, you can simply remove the account assignment category. The system then automatically deletes all account assignment data.
If you only want to change the account assignment data, make the changes in the corresponding account assignment lines and delete the lines you no longer require.
--------------------------

1. Question:
Which account assignment categories should I enter in schedule line categories for third-party order processing (CS) and individual purchase order processing (CB)?

Solution:

See Note 210997.
--------------------------

1. Question:
You subsequently change the material group in a limit purchase order or in a purchase requisition assigned to an account. Even though the new material group is assigned to another G/L account via the valuation class, the system does not determine the account assignment of the item again. The old G/L account remains.

Solution:

See Note 449216.
--------------------------

1. Question:
In Customizing, you can set the account assignment fields as mandatory, optional or display fields or as completely hidden fields, depending on the account assignment category. These settings also determine whether or not the system deletes the values of the account assignment fields when you change the account assignment category in a purchase order item.

Answer:

In MM Customizing, when you maintain the account assignment categories (IMG: Materials Management-> Purchasing -> Account Assignment-> Maintain Account Assignment Categories), you can control the different account assignment fields as follows:
Required entry: You must make an entry in the field, otherwise the system displays error message ME 083.

Optional entry: You may make an entry in the field.

Display: The field is displayed, but it is not ready for input.

Hidden: The field is hidden.

For example:
Account assignment category K, the cost center field is optional, the cost center field is filled with value 1000;
you change the account assignment category to P.
Depending on the field settings for the cost center with account assignment category P, the system response is as follows:
The cost center is a required entry or an optional entry field: The system transfers the value 1000 for the cost center

Displaying the cost center: first, the value 1000 is deleted for the cost center. If the system can determine a value again after you enter the changed account assignment category, this value is transferred.

The cost center field is hidden: The system deletes the value 1000 for the cost center.

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

1. Question:
You create a purchase order item assigned to an account with reference to a purchase requisition. You create a second schedule line for this purchase order item with reference to another purchase requisition. The system ignores the account assignment data of the purchase requisition for the second schedule line.

Solution:

This is standard system design. The system does not create a multiple account assignment in the purchase order item, even if the two referenced purchase requisitions are assigned to different CO objects.
Also refer to Note 47150 for the old transactions and to Notes 422609 and 771045 for the EnjoySAP transactions.
--------------------------

1. Question:
Why can I undelete an item in a purchase requisition, if
the corresponding account assignment data is no longer valid?

Solution:

When you undelete an item in a purchase requisition, the system does not run a new account assignment check. Therefore, the system does not check the account assignment data again.
Nevertheless, errors occur if you try to create a purchase order with reference to this purchase
requisition.
When you undelete an item in a purchase order, however, the system does run
another account assignment check.
--------------------------

1. Question:
You create a purchasing document with reference to a reference document. What account assignment data is transferred?

Solution:

The account assignment data is derived from the reference document.
If you delete the account assignment category and enter it again, a new automatic general ledger account determination occurs.


(0) 评论    (26) 引用   

[收藏]OBYC中的Transaction key详细解释以及用法

The following list shows the individual transactions with examples of how they are used:

  • Agency business: income (AG1)

This transaction can be used in agency business for income deriving from commission (e.g. del credere commission). The account key is used in the calculation schemas for agency business to determine the associated revenue accounts.

  • Agency business: turnover (AG2)

This transaction can be used in agency business if turnover (business volume) postings are activated in Customizing for the payment types. The account key is specified in Customizing for the billing type.

  • Agency business: expense (AG3)

This transaction can be used in agency business for commission expenses. The account key is used in the calculation schemas for agency business to determine the associated expense accounts.

  • Expense/revenue from consumption of consignment material (AKO)

This transaction is used in Inventory Management in the case of withdrawals from consignment stock or when consignment stock is transferred to own stock if the material is subject to standard price control and the consignment price differs from the standard price.

  • Expenditure/income from transfer posting (AUM)

This transaction is used for transfer postings from one material to another if the complete value of the issuing material cannot be posted to the value of the receiving material. This applies both to materials with standard price control and to materials with moving average price control. Price differences can arise for materials with moving average price if stock levels are negative and the stock value becomes unrealistic as a result of the posting. Transaction AUM can be used irrespective of whether the transfer posting involves a transfer between plants. The expenditure/income is added to the receiving material.

  • Provisions for subsequent (end-of-period rebate) settlement (BO1)

If you use the "subsequent settlement" function with regard to conditions (e.g. for period-end volume-based rebates), provisions for accrued income are set up when goods receipts are recorded against purchase orders if this is defined for the condition type.

  • Income from subsequent settlement (BO2)

The rebate income generated in the course of "subsequent settlement" (end-of-period rebate settlement) is posted via this transaction.

  • Income from subsequent settlement after actual settlement (BO3)

If a goods receipt occurs after settlement accounting has been effected for a rebate arrangement, no further provisions for accrued rebate income can be managed by the "subsequent settlement" facility. No postings should be made to the account normally used for such provisions. As an alternative, you can use this transaction to post provisions for accrued rebate income to a separate account in cases such as the one described.

  • Supplementary entry for stock (BSD)

This account is posted when closing entries are made for a cumulation run. This account is a supplementary account to the stock account; that is, the stock account is added to it to determine the stock value that was calculated via the cumulation. In the process, the various valuation areas (for example, commercial, tax), that are used in the balance sheet are taxed separately.

  • Change in stock (BSV)

Changes in stocks are posted in Inventory Management at the time goods receipts are recorded or subsequent adjustments made with regard to subcontract orders.

If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.

  • Stock posting (BSX)

This transaction is used for all postings to stock accounts. Such postings are effected, for example:

  • In inventory management in the case of goods receipts to own stock and goods issues from own stock
  • In invoice verification, if price differences occur in connection with incoming invoices for materials valuated at moving average price and there is adequate stock coverage
  • In order settlement, if the order is assigned to a material with moving average price and the actual costs at the time of settlement vary from the actual costs at the time of goods receipt

Because this transaction is dependent on the valuation class, it is possible to manage materials with different valuation classes in separate stock accounts.

Caution

Take care to ensure that:

  • A stock account is not used for any transaction other than BSX
  • Postings are not made to the account manually
  • The account is not changed in the productive system before all stock has been booked out of it

Otherwise differences would arise between the total stock value of the material master records and the balance on the stock account.

  • Revaluation of "other" consumptions (COC)

This transaction/event key is only relevant to Brazil. It is used if a revaluation report is used for company codes in Brazil.

The revaluation report uses the actual prices determined by the material ledger/actual costing t

  • Revaluate costs on the basis of actual prices
  • Post the price differences arising from "other" consumptions (e.g. consumption to cost center) to a collective account

This transaction/event key is needed to post the price differences. The account specified here is posted with the price differences for "other" consumptions.

  • Del credere (DEL)

Transaction/event key for the payment/invoice list documents in Purchasing. The account key is needed in the calculation schema for payment/settlement processing to determine the associated revenue accounts.

  • Small differences, Materials Management (DIF)

This transaction is used in Invoice Verification if you define a tolerance for minor differences and the balance of an invoice does not exceed the tolerance.

  • Purchase account(EIN), purchase offsetting account (EKG), freight purchase account (FRE)

These transactions are used only ifPurchase Account Managementis active in the company code.

Note

Due to special legal requirements, this function was developed specially for certain countries (Belgium, Spain, Portugal, France, Italy, and Finland).

Before you use this function, check whether you need to use it in your country.

  • Freight clearing (FR1), provision for freight charges (FR2), customs duty clearing (FR3), provision for customs duty (FR4)

These transactions are used to post delivery costs (incidental procurement costs) in the case of goods receipts against purchase orders and incoming invoices. Which transaction is used for which delivery costs depends on the condition types defined in the purchase order.

You can also enter your own transactions for delivery costs in condition types.

  • External service (FRL)

The transaction is used for goods and invoice receipts in connection with subcontract orders.

If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.

  • External service, delivery costs (FRN)

This transaction is used for delivery costs (incidental costs of procurement) in connection with subcontract orders.

If the account assigned here is defined as a cost element, you must specify a preliminary account assignment for the account in the table of automatic account assignment specification (Customizing for Controlling) in order to be able to post goods receipts against subcontract orders. In the standard system, cost center SC-1 is defined for this purpose.

  • Offsetting entry for stock posting (GBB)

Offsetting entries for stock postings are used in Inventory Management. They are dependent on the account grouping to which each movement type is assigned. The following account groupings are defined in the standard system:

  • AUA: for order settlement
  • AUF: for goods receipts for orders (without account assignment)
    and for order settlement if AUA is not maintained
  • AUI: Subsequent adjustment of actual price from cost center directly
    to material (with account assignment)
  • BSA: for initial entry of stock balances
  • INV: for expenditure/income from inventory differences
  • VAX: for goods issues for sales orders without
    account assignment object (the account is not a cost element)
  • VAY: for goods issues for sales orders with
    account assignment object (account is a cost element)
  • VB for consumption from stock of material provided to vendor
  • VBR: for internal goods issues (for example, for cost center)
  • VKA: for sales order account assignment
    (for example, for individual purchase order)
  • VKP: for project account assignment (for example, for individual PO)
  • VNG: for scrapping/destruction
  • VQP: for sample withdrawals without account assignment
  • VQY: for sample withdrawals with account assignment
  • ZOB: for goods receipts without purchase orders (mvt type 501)
  • ZOF: for goods receipts without production orders
    (mvt types 521 and 531)

You can also define your own account groupings. If you intend to post goods issues for cost centers (mvt type 201) and goods issues for orders (mvt type 261) to separate consumption accounts, you can assign the account grouping ZZZ to movement type 201 and account grouping YYY to movement type 261.

Caution

If you use goods receipts without a purchase order in your system (movement type 501), you have to check to which accounts the account groupings are assignedZOB

If you expect invoices for the goods receipts, and these invoices can only be posted in Accounting, you can enter a clearing account (similar to a GR/IR clearing account though without open item management), which is cleared in Accounting when you post the vendor invoice.

Note that the goods movement is valuated with the valuation price of the material if no external amount has been entered.

As no account assignment has been entered in the standard system, the assigned account is not defined as a cost element. If you assign a cost element, you have to enter an account assignment via the field selection or maintain an automatic account assignment for the cost element.

  • Purchase order with account assignment (KBS)

You cannot assign this transaction/event key to an account. It means that the account assignment is adopted from the purchase order and is used for the purpose of determining the posting keys for the goods receipt.

  • Exchange rate differences in the case of open items (KDM)

Exchange rate differences in the case of open items arise when an invoice relating to a purchase order is posted with a different exchange rate to that of the goods receipt and the material cannot be debited or credited due to standard price control or stock undercoverage/shortage.

  • Differences due to exchange rate rounding, Materials Management (KDR)

An exchange rate rounding difference can arise in the case of an invoice made out in a foreign currency. If a difference arises when the posting lines are translated into local currency (as a result of rounding), the system automatically generates a posting line for this rounding difference.

  • Exchange rate differences from lower levels (KDV)

In multi-level periodic settlement in the material ledger, some of the exchange rate differences that have been posted during the period in respect of the raw materials and semi-finished products used in the manufacture of a semi-finished or finished product are debited or credited to that semi-finished or finished product.

  • Consignment liabilities (KON)

Consignment liabilities arise in the case of withdrawals from consignment stock or from a pipeline or when consignment stock is transferred to own stock.

Depending on the settings for the posting rules for the transaction/event key KON, it is possible to work with or without account modification. If you work with account modification, the following modifications are available in the standard system:

  • None for consignment liabilities
  • PIP for pipeline liabilities
  • Offsetting entry for price differences in cost object hierarchies (KTR)

The contra entry for price difference postings (transaction PRK) arising through settlement via material account determination is carried out with transaction KTR.

  • Accruals and deferrals account (material ledger) (LKW)

If the process of material price determination in the material ledger is not accompanied by revaluation of closing stock, the price and exchange rate differences that should actually be applied to the stock value are contra-posted to accounts with the transaction/event key LKW.

If, on the other hand, price determination in the material ledger is accompanied by revaluation of the closing stock, the price and exchange rate differences are posted to the stock account (i.e. the stock is revalued).

  • Price differences (PRD)

Price differences arise for materials valuated at standard price in the case of all movements and invoices with a value that differs from the standard price. Examples: goods receipts against purchase orders (if the PO price differs from the standard pricedardpreis), goods issues in respect of which an external amount is entered, invoices (if the invoice price differs from the PO price and the standard price).

Price differences can also arise in the case of materials with moving average price if there is not enough stock to cover the invoiced quantity. In the case of goods movements in the negative range, the moving average price is not changed. Instead, any price differences arising are posted to a price difference account.

Depending on the settings for the posting rules for transaction/event key PRD, it is possible to work with or without account modification. If you use account modification, the following modifications are available in the standard system:

  • None for goods and invoice receipts against purchase orders
  • PRF for goods receipts against production orders and
    order settlement
  • PRA for goods issues and other movements
  • PRU for transfer postings (price differences in the case
    of external amounts)
  • Price differences in cost object hierarchies (PRK)

In cost object hierarchies, price differences occur both for the assigned materials with standard price and for the accounts of the cost object hierarchy. In the course of settlement for cost object hierarchies after settlement via material account determination, the price differences are posted via the transaction PRK.

  • Price differences, product cost collector (PRP)

During settlement accounting with regard to a product cost collector in repetitive manufacturing, price differences are posted with the transaction PRP in the case of the valuated sales order stock.

This transaction is currently used in the following instances only:

- Production cost collector in Release 4.0

- Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)

  • Offsetting entry: price differences, product cost collector (PRQ)

The offsetting (contra) entry to price difference postings (transaction PRP) in the course of settlement accounting with respect to a product cost collector in repetitive manufacturing in the case of the valuated sales order stock is carried out via transaction PRQ.

This transaction is currently used in the following instances only:

- Production cost collector in Release 4.0

- Product cost collector in IS Automotive Release 2.0 (product cost collector in connection with APO)

  • Price differences from lower levels (PRV)

In multi-level periodic settlement in the material ledger, some of the price differences posted during the period in respect of the raw materials and semi-finished products used in a semi-finished or finished product are debited or credited to that semi-finished or finished product.

  • Price differences for material ledger (PRY)

In the course of settlement in the material ledger, price differences from the material ledger are posted with the transaction PRY.

  • Expense and revenue from revaluation (retroactive pricing, RAP)

This transaction/event key is used in Invoice Verification within the framework of the revaluation of goods and services supplied for which settlement has already taken place. Any difference amounts determined are posted to the accounts assigned to the transaction/event key RAP (retroactive pricing) as expense or revenue.

At the time of the revaluation, the amounts determined or portions thereof) are posted neither to material stock accounts nor to price difference accounts. The full amount is always posted to the "Expense from Revaluation" or "Revenue from Revaluation" account. The offsetting (contra) entry is made to the relevant vendor account.

  • Invoice reductions in Logistics Invoice Verification (RKA)

This transaction/event key is used in Logistics Invoice Verification for the interim posting of price differences in the case of invoice reductions.

If a vendor invoice is reduced, two accounting documents are automatically created for the invoice document. With the first accounting document, the amount invoiced is posted in the vendor line. An additional line is generated on the invoice reduction account to partially offset this amount. With the second accounting document, the invoice reduction is posted in the form. of a credit memo from the vendor. The offsetting entry to the vendor line is the invoice reduction account. Hence the invoice reduction account is always balanced off by two accounting documents within one transaction.

  • Provision for delivery costs (RUE)

Provisions are created for accrued delivery costs if a condition type for provisions is entered in the purchase order. They must be cleared manually at the time of invoice verification.

  • Taxes in case of transfer posting GI/GR (TXO)

This transaction/event key is only relevant to Brazil (nota fiscal).

  • Revenue/expense from revaluation (UMB)

This transaction/event key is used both in Inventory Management and in Invoice Verification if the standard price of a material has been changed and a movement or an invoice is posted to the previous period (at the previous price).

  • Expenditure/income from revaluation (UMD)

This account is the offsetting account for the BSD account. It is posted during the closing entries for the cumulation run of the material ledger and has to be defined for the same valuation areas.

  • Unplanned delivery costs (UPF)

Unplanned delivery costs are delivery costs (incidental procurement costs) that were not planned in a purchase order (e.g. freight, customs duty). In the SAP posting transaction in Logistics Invoice Verification, instead of distributing these unplanned delivery costs among all invoice items as hitherto, you have the option of posting them to a special account. A separate tax code can be used for this account.

  • Input tax, Purchasing (VST)

Transaction/event key for tax account determination within the "subsequent settlement" facility for debit-side settlement types. The key is needed in the settlement schema for tax conditions.

  • Inflation posting (WGB)

Transaction key, which posts inflation postings to a different account within the handling of inflation for the period-end closing.

  • Goods issue, revaluation (inflation) (WGI)

This transaction/event key is used if already-posted goods issues have to be revaluated following the determination of a new market price within the framework of inflation handling.

  • Goods receipt, revaluation (inflation) (WGR)

This transaction/event key is used if already-effected transfer postings have to be revaluated following the determination of a new market price within the framework of inflation handling. This transaction is used for the receiving plant, whereas transaction WGI (goods receipt, revaluation (inflation)) is used for the plant at which the goods are issued.

  • GR/IR clearing (WRX)

Postings to the GR/IR clearing account occur in the case of goods and invoice receipts against purchase orders. For more on the GR/IR clearing account, refer to the SAP Library (documentationMM Material Valuation).

Caution

You must set theBalances in local currency onlyindicator for the GR/IR clearing account to enable the open items to be cleared. For more on this topic, see the field documentation.

  • GR/IR clearing for material ledger (WRY)

This transaction/event key is not used from Release 4.0 onwards.

Prior to 4.0, it was used for postings to the GR/IR clearing account if the material ledger was active. As of Release 4.0, the transaction is no longer necessary, since postings to the GR/IR account in parallel currencies are possible.

Customers who used the transaction WRY prior to Release 4.0 must make a transfer posting from the WRY account to the WRX account in order to ensure that the final balance on the WRY account is zero.


(0) 评论    (226) 引用   

[收藏]SAP系統BUG - info recorde的價格與Condition的不統一

http://ssgang.itpub.net/post/10314/397943

Info Record中價格欄位: EINE-NETPR與Condition的欄位:KONP-KBETR有時會出現不統一的現象, 特別是在批量上傳Info Record時, 系統沒有同時更新兩個欄位, 造成不匹配. 系統有提供一個修正此BUG的程式: RM06INP0


處理建議:

1.Old Price和New Price均顯示"Not found"的 =>不要處理.

2.Old Price有,New Pirce "not found"的 =>無最新Infor.Record,給相關采購處理

3.Old Price和new price均有,且不一至的 =>去掉"Test Run",讓程式來更新價格.

最好給足條件,一個一個跑,且及時到內表中查看結果.不要一大批地跑,一旦發現錯誤,可以及時回復


祥見SAP Notes:

Symptom

After the change of the info record currency, the conversion factors between the order unit and the purchase order price unit are no longer correct on the purchasing view.The conversion factors between the base unit of measure and the order unit on the general view are, however, possibly correct.

However it is also possible that there are incorrect values in database table EINE.

A similar behavior can also occur for contracts.

Other terms

MEKPE, MEKP, EURO, WEWU, BME, BPRME, EINE, EINA, EINA-MEINS, EINA-LMEIN, KONP, KUMZA, KUMNE, LMEIN, MEKL, MEKLE, scheduling agreement, outline agreement, MEKRE, MEKR, EINE-NETPR

Solution

Implement the program correction.

Note:

Bear in mind that this note only has a preventive effect and cannot correct already existing data inconsistencies.

Proposed solution:

To eliminate possible data inconsistencies, we recommend that you carry out the currency conversion again.

Alternative:

Provided that, in the conditions of the affected purchasing documents, the conversion factors between the order unit and the purchase order price unit and also the prices in the conditions are correct, it is possible to carry out a correction using the following reports:

For info records: RM06INP0; also refer to Note 392988

For contracts: RM06ENP0

The 'No date check' indicator should be set for both reports.

After using the reports, it is not necessary to carry out a further currency conversion


(0) 评论    (25) 引用   

[收藏]SAP系統BUG - info recorde的價格與Condition的不統一

http://ssgang.itpub.net/post/10314/397943

Info Record中價格欄位: EINE-NETPR與Condition的欄位:KONP-KBETR有時會出現不統一的現象, 特別是在批量上傳Info Record時, 系統沒有同時更新兩個欄位, 造成不匹配. 系統有提供一個修正此BUG的程式: RM06INP0


處理建議:

1.Old Price和New Price均顯示"Not found"的 =>不要處理.

2.Old Price有,New Pirce "not found"的 =>無最新Infor.Record,給相關采購處理

3.Old Price和new price均有,且不一至的 =>去掉"Test Run",讓程式來更新價格.

最好給足條件,一個一個跑,且及時到內表中查看結果.不要一大批地跑,一旦發現錯誤,可以及時回復


祥見SAP Notes:

Symptom

After the change of the info record currency, the conversion factors between the order unit and the purchase order price unit are no longer correct on the purchasing view.The conversion factors between the base unit of measure and the order unit on the general view are, however, possibly correct.

However it is also possible that there are incorrect values in database table EINE.

A similar behavior can also occur for contracts.

Other terms

MEKPE, MEKP, EURO, WEWU, BME, BPRME, EINE, EINA, EINA-MEINS, EINA-LMEIN, KONP, KUMZA, KUMNE, LMEIN, MEKL, MEKLE, scheduling agreement, outline agreement, MEKRE, MEKR, EINE-NETPR

Solution

Implement the program correction.

Note:

Bear in mind that this note only has a preventive effect and cannot correct already existing data inconsistencies.

Proposed solution:

To eliminate possible data inconsistencies, we recommend that you carry out the currency conversion again.

Alternative:

Provided that, in the conditions of the affected purchasing documents, the conversion factors between the order unit and the purchase order price unit and also the prices in the conditions are correct, it is possible to carry out a correction using the following reports:

For info records: RM06INP0; also refer to Note 392988

For contracts: RM06ENP0

The 'No date check' indicator should be set for both reports.

After using the reports, it is not necessary to carry out a further currency conversion


(2) 评论    (52) 引用   

material master物料主数据field selection的配置

在使用物料主数据相关TCODE进入相关屏幕时(以MM01为例),我们会发现在不同的项目里,有些屏幕字段是必输项,有些不是,有些干脆被隐藏。这个是通过一个叫做field selection的进行配置来起作用的。

field selection与transaction code(MM01 MM02 MM03屏幕字段表现各不相同) material type; procurement type;industry section;plant;SAP delivery相关。

Field selection在后台的相关配置路径如图所示

所有的field不是单独被控制的,而是被组成了group,对整个group进行必输 可输 隐藏等设定

首先我们运行Assign Fields to Field Selection Groups 可以看到MARA-MEINS在group 1里面

点击后面绿色的按钮,可以进入到相应的GROUP的设定。走菜单的Maintain Field Selection for Data Screens也可以进入的配置屏幕。

我们进入到material type的配置屏幕,可以看到ROH原材料的field reference配置的是ROH

那么我们回到field selection group的配置画面,找到field ref.为ROH的一行,将其改为隐藏,看看是否可以有效果

我们看到,这个basic unit字段被隐藏了

其他关于Industry Sector的配置可以简单的看一下配置画面,也十分简单。

其他,关于procurement type是内制还是外购,是固定的,field ref是E和F

关于TCODE呢,可以在field ref. MM01 MM02等找到相应的配置。

而和plant有关的配置,只在有Plant有关的view里才会工作


(0) 评论    (22) 引用   

关于material master物料主数据的valuation class

在物料主数据的会计1视图中,有一个重要的屏幕字段valuation class 这个选项将会决定此物料的财务记账的科目。

那么这是如何起作用,如何配置的呢?为什么search help会自动带出几个相关的valuation class?

这其中有一个起到桥梁作用的,叫做account category reference

也就是说,一个物料类型,会配置一个account category reference,而一个account category referenceH会对应多个valuation class。那么定义一个物料,相关的物料类型就决定了可以选择的valuation class了。

下面我们看一下实际操作

在后台的配置路径如下

第一个Define Valuation Control 会让我们选择是否激活valuation group code 因为SAP的配置十分灵活,我们可能很多工厂的记账方式和科目都是一样的,这样避免重复配置,可以将他们group在一起,然后将这个group进行配置。我们还是重点讲解valuation class

执行Define Valuation Classes

我们可以看到三个push button 那么第一个就是可以定义account category ref.

第二个定义valuation class 并assign一个act category ref.

第三个将每个物料类型assign一个act category ref. 这样便形成了最开始我们讲解的那个结构

当然,从物料类型的配置画面,也可以指定

之后我们来运行Configure Automatic Postings 进行自动记账的配置

进入这个画面以后,我们看到有三个按钮

acct assignment就是我们要进行G/L ledger与valuation class进行关联配置的功能

而simulation是个十分重要和好用的功能,它可以让我们模拟某个物料在某个工厂下,进行各种业务操作时,各种自动记账账户的一个概览

而最后一个按钮可以让我们看到,某个公司代码下的某个value area下,有哪些G/L科目在被使用

我们首先看第一个功能,我们要讲解的功能

可以看到SAP将各种业务操作进行了分类,我们随便选取一个没有被配置过的BSD

进入后,系统会首先提示我们配置rule 也就是科目决定过程的一个规则

因为我们要根据valuation class进行不同科目的POST 所以将最后一个checkbox勾选

再点击accounts就可以看到 有一个两列的table 第一列便是valuation class 后面是相对应的账户

我们还可以在rules里面勾选debit/credit选项,则同一个valuation class,可以设置在作为借方和贷方是不同的账户

最后我们show一下前面提过的simulation功能 可以看到,一个物料的自动记账账户,一目了然


(1) 评论    (271) 引用   

采购组织的典型配置形式

Plant-Specific Purchasing Organization
每一个采购组织只为一个工厂采购,将采购组织分配给固定工厂

Cross-Plant Purchasing Organization
采购组织为多个工厂采购,可能多个工厂出产相同的产品,需要一样的原材料等。将采购组织分配给company code即可,此company下的所有工厂都可以由此采购组织负责

Cross-Company Code Purchasing Organization
采购组织可以为多个公司的不同工厂采购,配置的关键是,不要将采购组织分配company code,在新建PO的时候,系统会提示,将要为哪个company code采购


(0) 评论    (191) 引用   

[收藏]移动类型

(0) 评论    (124) 引用   

GR error, message: Posting Only Possible Between...

precondition
T-CODE
MMPV is used to close the current period and to open a new period. Enter the company code (range or single), enter the new period, normally the next month and year (month and year) or date (but not both) and save.

MMRV is used to allow posting in a previous period (per your company
requirement), tick or untick and save.

Refer http://sap.ittoolbox.com/groups/technical-functional/sap-log-sd/sap-sd-mb1c-1586723

While doing goods receipt for order, the following error occurs, it says POSTING ONLY POSSIBLE BETWEEN 08/2007 AND 09/2007

Movement type.101
Order: 4500016867
Plant:1000
Storage Location:0001

I am trying to do GR after creating PO. It is showing an error messg "posting only possible during 08/2007 and 09/2007". I went into open and close posting peiords in FI (IMG) and tried opening new periods but it is still not allowing me to proceed further and is showing the same messg.

Go to T.Code MMPV :
1. Enter your company code.
2. Fiscal year of the current period (in your case 2007).
3. Put the period as 10.
4. Check the radio button for check and close period.
5. Execute.
6. The system does say it is not current calender year. (do not worry about this).
7. Hit Esc and
8. Now change the Fiscal year to 2007 and
9. Period to 11
10. Execute
Continue these steps until you reach your period and fiscal year.

I am facing a problem with fiscal year. When I am trying to close the periods with MMPV, it is saying that 'specify a present calender'. It is not allowing me to receipt GR and post the invoice. And also when I am trying to change the next period through navigation (SPRO/Logostics general/Material master/Maintain company codes for matl management) it is saying that this company code can no longer be initiated. Our SAP was installed recently.

To maintain fiscal year

SPRO - Logistics General - Mat Master - Basic Settings - Maintain Company Codes for Material Management - Execute - Select Company Code and Define the Fiscal Year

Year = 2006
P(month) = current month
F/yr = 2006
M = Previous Month

ABP = Allow Back Posting , DBP = Disallow back posting


(0) 评论    (260) 引用   

ME22N执行BDC出错 ME22N BDC error

ME22N这种新的TCODE因为有新的控件在屏幕上,所以执行BDC会出错。
解决办法就是用BAPI或者ME22老TCODE来做。
具体请见http://sapfans.com/forums/viewtopic.php?t=272362&view=next&sid=3fe9a01071e5e08614ed42b46beaca50

Hi All,

I am using a report to update confirmation control in ME22N through BDC.
If i run the report in foreground it works fine and the conf contrl has been updated. But while running the report in Background mode(Program->Execute in Background) record has not been updated and spool is created with the below error Msg.

Unable to initialise ABAP Control
Control Framework: Fatal error -
Runtime error RAISE_EXCEPTION has occured


Please can you help to overcome this and thanks in advance.

ME22N being enjoy transaction, is not suitable for BDC. Also, it uses some frontend controls, which are not available in background mode.
Use BAPI_PO_CHANGE, which works nice.
In case you must use BDC, use transaction ME22.


(1) 评论    (13) 引用