Message Control and Control Keys in SAP QM

This key determines which conditions are valid for quality management in procurement.

If you activate the indicator for QM in procurement in the material master record at the client level , you must also store a control key at the plant level for quality management in procurement.

Depending on the control indicators in the control key, you may have to maintain additional data.

SAP transaction code to maintain the Control key SM30 - V_TQ08

You can set the Message Control for Lock as :

I - Information
W - Warming
E - Defects

You can also indicate that a Quality Certificate is required or not.

read more...

SAP Quality Management: Introducing QM in Procurement

The QM component is integrated in crucial phases of the procurement process. It supports the procurement activities by means of functions such as:

* Vendor Evaluation
* Vendor block
* Vendor Release for requests for quotation and purchase orders
* Assigning technical delivery terms and Quality(QM) assurance agreements
* Certificate processing
* Status administration of the supply relationships
* Incoming inspections
* Goods(items) receipt inspections


If your company purchases materials from external vendors, you can implement the QM in Procurement (QM-PT-RP-PRC) component to support your procurement processes for Quality(QM) assurance purposes.

If you want to implement the QM in Procurement component, your company must also use the Purchasing (MM-PUR) component. If you require functions for processing goods(items) movements, you must also install the Inventory Management (MM-IM) component.

You can implement the QM in Procurement component as a stand-alone component or together with the Quality(QM) Inspection (QM-IM) component. As a stand-alone component, you can use all procurement functions except those for processing goods(items) receipt inspections. To process such inspections, you need the Quality(QM) Inspection component.

Using the functions of the QM in Procurement component, you can:

* Manage Quality(QM) -related information for materials, vendors, and manufacturers in Quality(QM) info records
* Release or block vendors and manufacturers
* Monitor the QM systems of vendors and manufacturers
* Supply Quality(QM) documents with requests for quotations and purchase orders
* Evaluate vendors on the basis of Quality(QM)
* Certify vendors or manufacturers that have QM systems implemented, to reduce the inspection requirement
* Manage and release supply relationships
* Request that Quality(QM) certificates be submitted with the delivered goods(items) and monitor the receipt of these certificates
* Inspect vendor goods(items) at vendor sites (source inspections)
* Inspect vendor goods(items) upon receipt (goods(items) receipt inspections)
* Manage the posted goods(items) in inspection stock
* Block the payment of invoices until the goods(items) have been inspected and accepted
* Process goods(items) receipt inspections for manufacturer-specific materials
* Inspect goods(items) that have been externally processed when they are returned in a goods(items) receipt.

read more...

Goods Receipts for PO does not contain any items

When you try to post a GR against any PO it says that the PO does not contain any items.
But when you display the PO it shows the items in it.

There have been several reasons which can be attributable to this problem -

1) This PO is subject to release strategy and since the final release was not made, this PO is considered as 'blocked'.

2) You have been using the confirmation control category where in respect of the last confirmation category key, the GR assignment checkbox is flagged. In this particular case, GR is only be posted if the confirmation is not maintained.

3) Early delivery date ie. the GR date is coming earlier than the PO delivery date.

One other nasty thing might have happened (mostly in MIGO):

You have accidently changed your default movement type from 101 to 102 during your last movement.
You will experienced this in some cases before installing hotpackage which shows the movement type on the MIGO screen.

read more...

Steps for MM Pricing Procedures

Pricing Procedure :

In MM module, pricing procedure is used during RFQ and PO creation. Total value of material based on all addition and subtraction like discount, surcharge, tax, freight, etc. In this we are defining pricing procedure and linking to vendor and purchase department through the virtual schemas.

Following steps for pricing procedure as,
1. Define conditions.
2. Define pricing procedure.
3. Define virtual purchase organization and vendor.
4. Info Record.

Customization for Pricing Procedure :
1. Definition of Conditions :
/NMEK0---condition type…condition types--- definition (define for basic price, net price, discount, surcharge, tax etc.)

2. Defining pricing procedure :
/NMEK0--- calculation schema---calculation schemas—New entries (Define procedure and put the conditions like formula so that final price will be net price / total value as per company requirement)

3. Linking pricing procedure to independent condition types.
/NMEK0---condition type…condition types--- definition for position for defined conditions (Enter the defined pricing procedure in the each independent conditions “Pricing Procedure” box)

4. Defining Schema group for Vendor :
/NMEK0--- calculation schema---schema groups—vendor—New Entries.

5. Defining Schema group for Purchase Organization--- New entries.
/NMEK0--- calculation schema--- schema groups---- purchasing organization--- new entries.

6. Linking Virtual Purchase Organization to actual Purchase Organization.
/NMEK0--- calculation schema--- schema groups----- Assign P.Org. (in actual P.Org, enter virtual P.Org)

7. Linking Pricing procedure to virtual P.Org and virtual vendor :
/NMEK0--- calculation schema--- Determine Schema--- -Standard --- New entries (Enter virtual schema and P.Org. along with pricing procedure)

8. Linking virtual vendor to actual vendor-- /NXK02 then enter schema group vendor in Purchasing Data )

9. Info Records (/NME11)---- click on “Purch. Org. data1” and enter condition types and pricing procedure

What are the steps in pricing determination in MM? Condition, Access sequence and schema.

In the SAP MM Pricing is more important. Just yesterday I have completed the Pricing as I am doing the SAPMM now. I can give some light on this Topic, not 100%. After 2 days definitely some more I can share.

The Basic thing is Condition Technique. In which there are
1. Access Sequence 2. Condition Record 3. Condition Type 4. Condition Table.

A Access Sequence access a Condition Record of a Condition Type in a Condition Table is a Condition Technique.This is a simple logic

Here the Condition Type is very important like PB00, PBXX,RA01 etc.

In the background every Condition Type has its own defition means the purpose of the Condition Type like, is it for Pricing or Percentage, Quntity base, Accrual Feilds etc is to be defined to work this functions.

Normally we use the existing ones without any risk. But some cases, we have to Create a New Condition Types as per the organisation requirement.

The Pricing Schema is useful to minimise condition types while mention prices for Vendor on the basis of Pricing Schema which we defined according to organisation requirement.

The Pricing Schema means the calculations procedure of Condition Type.

Ex. RA01 - Discoount % is caclulated on PB00 - Gross Price means
RA01 is based on PB00 like that we have to define in the Pricing Schema
which makes easy to use in realtime.
Here PB00 has the Access Sequence - 0002.
But RA01 does not have the Access Sequence.Why because it is a dependent on PB00. But both are Condition Types.

In the system, by default some standard Scheme will be there at Vendor Schema Group in the Vendor Master Screen means the standard one is assigned which is very lengthy which may fullfil our requirement. But some cases which may not fullfil our requirement, in such we have to define.

For the configuration, I may not able to explain properly through here but will give some Idea.

Configuration: SPRO-IMG-Material Management- Purchasing- Conditions-Define Price Deternmination Process
1. Define Access Sequence
2. Define Condition Type
3. Defince Calculation Schema:- Here you have to define the Schema
Define Schema group
1. Define Schema Group vendor
2. Define Pricing Schema group
3. Schema group for Purchase Organisation
4. Assign Schema group to Purchase Organisation

Define Schema determination
1.define calculation schema for Standard purchase organisation

After completion of the Schema Group, we have to assign it to Vendors.
Then whenever we use any transaction with this Vendor, the concerned Schema will work as configured by us.

I think this will help you. Actually the Pricing is a vast. Becuase each Condition have its own importance and each Access Sequence have its own importance. So you need not bother about this. First you learn how to define the Calculation Schema through the above.

Here we can create many Calculation Schemas which can assign one schema to Local vendors
another schema to out side vendor one more schema to foreign vendors like that we can classify.

Definitely it will help you something. Because I have to do R & D on this Topic. Due to lack of time I am not able to do the Practice Properly as I am doing non-related SAPMM job.

read more...

Language Error when creating Purchase Order

This happens when the language in Material Master (MM02 - Purchase Order
Text) and Vendor Master (XD02 - Address - Communication - Language) does not matched.

In the Purchase Order, you can see the language in PO Header - Communications data - Language.

If the Purchase Order have been saved before you change the Vendor Master Language, the PO need to be closed as the language in the PO Header cannot be changed.

This is the SAP Language Error that will appear when creating PO with language mis-matched:

No short text maintained in language CS (please re-maintain material ABCDEFGHIJK)
Message no. ME 095

Diagnosis
No material short text (short description) has been maintained in language CS.

System Response
No short text can be adopted from the material master record.

Procedure
If a material is to be procured from a vendor in a different language, the material short text must first be maintained in this language.

Maintain the short texts in the material master record in those languages in which procurement is normally carried out. In this case, you should at least maintain the short text in language CS.

read more...

Procedure to Define Both Currency USD and EURO

We are purchasing export item, export item currency is USD. Some time same vendor send item with different currency like EURO. I'm facing problem when we pay to vendor.
In Vendor Master Currency is defined as USD. I can pay in USD.
If I want to pay in EURO, again I have to go vendor master and change USD to Euro vice versa.
Everytime I am changing.
Is there any procedure to define both currency USD and EURO.
According to situation I can select currency.
My local currency is different i.e SAR (Saudi Riyal).

This is a common problem in almost all factories in our group. To simply the matters let me explain the method we use with some numbers.

1) Lets say we raise a PO as follows:
2 items @ $10 = $ 20

2) GRN is raised as per PO

3) Invoice comes from the vendor as
2 items @ Euro 0.80 = Euro 1.60

4) What we do is that we check with our purchasing people whether the Euro to $ convertion from the supplier is beneficial to us, if not it is within our tolerance levels.
Then we process the payment for $ but mention the correct EURO amount in narration. Bank instructions goes for EURO and there will be a Exchange diff entry to the bank rec at the month end.

5) As far as I know you can't maintain multi currency in the vendor master.

6) Another effective method we are adopting is to have two vendor accounts for different currencies.

read more...

What are the Types of Inforecords?

You can create purchasing info records for different procurement types as follows:

Standard, Subcontracting, Pipeline, Consignment You use this component if you wish to store information on a vendor and a material as master data at purchasing organization or plant level.

Standard

A standard info record contains information for standard purchase orders.
The info records can be created for materials and services with and without master records.

Subcontracting

A subcontractor info record contains ordering information for subcontract orders.
For example, if you subcontract the assembly of a component, the subcontractor info record would include the vendor's
(subcontractor's) price for assembling the component.

Pipeline

A pipeline info record contains information on a vendor's commodity that is supplied through a pipeline or pipes
(oil or water) or by similar means (electricity through the mains).
The info record contains the vendor's price for the consumption of such commodities by the buyer
("pipeline withdrawals"). You can store withdrawal/usage prices for different validity periods.

Consignment

A consignment info record contains information on a material that vendors keep available at their own cost on the orderer's premises.
The info record contains the vendor's price for withdrawals by the orderer from consignment stock.
As in the case of the pipeline info record, you can store prices for different validity periods.

read more...