When we create info & Maintain Quotation, by quota we are determining the source. Also in Vendor Evaluation, we are evaluationg vendor. When we are creating PO, from where the vendor will come from? Is it from Quota or Vendor Evaluation?
You define source list requirements at plant level. If a source list requirement exists, you must maintain the source list for each material before you can order it.
The source list serves:
To define a source of supply as "fixed". Such sources count as preferred sources over a certain period of time. For example, the fixed vendor XXXX for material 100XX is ASA Company for the first quarter and BSB Co. for the second quarter of the year.
Select the plants for which you wish to specify a source list requirement
You use the source list to determine the valid source of supply at a certain point in time.
The source list contains all the sources of supply defined for a material and the periods during which procurement from these sources is possible
Following T/Code activities in Material Management module.
Maintain source list - ME01
Display source list - ME03
Display changes to source list - ME04
Analyze source list - ME06
Reorganize source list - ME07
Generate source list - ME05
Display source list for material- ME0M
you make the system settings that are necessary for purchasing operations carried out using source lists.
Source list requirement for materials, It may be necessary to include possible vendors of a material in the source list before the material can be ordered.
The Source list requirement field in the purchasing data of the material master record indicates whether a source list requirement exists for a material.
You can define the Source list requirement at plant level in IMG. Logistics -->Materials management --> Purchasing --> Source list.
Here you can see the plants for which a source list requirement exists.
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.
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.
I have release strategy for PR and PO, suppose there is 3 levels of Release, at second level I want to set an alternative Release code, if either of the employee releases then it should go to third release.
How to configure for PO (with classifications) and PR (without classifications).
Sharief
To my knowledge you cannot assign two release code for a release level. But you can achieve your requirement that either of the employee releaseas and it goes to third level.
1. In OMGS, under workflow, hope you have assigned S for object and position ID in Agent ID, if not let me
know your assignments
2. In PPOMA, you can assign both employees under the same position.
3. Both employees have authorization to release at this release code.
4. Workflow automatically completes the release and moves to next level if either of the employee releases it.
TC Venkatesan
Workflow is not implemented in our organization. Is there any alternative?
Sharief
In this case, I am assuming employees use ME28 or so directly to release.
As long as any employee has authorization to that release code, they can release using the release code in ME28 or so, right?
Can you explain more about the procedure they try to release?
TC Venkatesan
We are using ME28 to release the POs. But I am trying to minimise the release codes, if there is any possibility let me know.
Sharief
I will set out an example below:-
If the release group is G1 and release code is 03 for the level you wish to add alternative releases to then simply get the user who is in control of authorisations in your organisation to add G1 and 03 to user 1 and the same to user 2.
This will alow any one of them to release, without workflow. If you want this can also be set for a validity period in authorisations. Sometimes if a user is away from work and he is the only one to release, then an alternative user may be assigned these codes for a validity period (during the absence of the other user). The system will automatically invalidate him when it reaches the set date.
What is the procedure to adopt in case of the following situations when they arise? (FOR SAP 4.6C version)
First situation
1)
a) PO LINE ITEM NET PRICE = US$100
b) The item is goods receipted with a price of US$110. Assume the difference of US$10 is because of tax caluculated by the system (for example)
c) Vendors sends an Invoice for this item at the price of US$85 (US$80 PO line item price + US$5 tax).
So in this case, the Invoice price is lower than the PO net price which is US$100.
So for this type of situation what is the procedure to adopt to post the invoice in the system.
Is it that the first the goods receipt needs to be reversed and then change or update the PO line item net price with US$80(for example) and then do the goods receipts and then do the invoice receipt?
If this procedure is correct and what happens if vendors invoice price is lower than the origianl PO line item net price (as described in this case), whether the system blocks the invoice in this case or not?
Or is it that the goods receipt need not be reversed and just post the invoice with the new price and change the PO price with the new vendor invocied price?
When is that the price in the info record needs to be changed?
Second situation
2) What is the procedure to adopt when the vendor's invoice price is greater than PO line item price?
Basically, I am just looking for the correct procedures to adopt in both of these cases like in what sequences,(like what is the first step and what is the second step) with what steps to follow.
What to do procedurally - how to post an invoice with differing value than PO and/or GR and what to do if an invoice blocks, etc in both the cases like when the vendor invoice price is less than the PO price (line item net price plus tax) and one more, I need to know is in this case will the invoice gets blocked upon invoice posting when the vendor price is low.
Similarly in the second case what to do procedurally when the invoice price is more than the PO price (Line item net price +tax)?
Whatever tolerances you have set for over or under invoice will determine if any blocks occur (this covers both your first and second examples). (Transaction code: OMR6)
When the clerk enters the invoice the system will note that the invoice is going to block but will not stop it from being posted. (Transaction: MIRO)
Procedurally, the buyer checks blocked invoices and resolves the block be either:
1. Changing the PO price to match the invoice and then the invoice should unblock (either automatically if you have it set up that way, or the buyer can release the block) or
2. Buyer can dump the block without changing the PO price (info record price history is not updated in this case because PO price wasn't changed).
In either case, if you have your materials being valuated at GR and then at IR, the invoice will revalue the material so there is not really a need to reverse the GR to change the PO price and then reenter the GR.
The transaction code for viewing blocked invoices (and releasing them) is MRBR.
Can anyone please help me on the Pricing Procedures?
I have read it many times but fail to understand.
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
Anand
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.
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.
Can someone please explain on how the account assignment is done for service items which are "texts" unlike materials?
The concept of account assignment remains same whether for materials with Mat. No. Or only text.
If you are purchasing a particular service for a cost center. then you can assign the PO item to Cost Center & so on.....
Use the following Customizing Path:
Material Management
-> Purchasing
-> Material Master
-> Entry Aids For Items Without a Material Master.
Create the Material Groups and the Valuation Classes you are going to assign to the 'text services'. In the moment of a Purchase order, put the text services and assign them the material groups which you created for them. In that moment, the account assignment that you customized will appear into the purchase order.
You can define whether and in which purchasing documents a field is relevant to printouts of changes or which texts are included in change notices.
The text output can be controlled via a text number (direct assignment) or a routine (indirect assignment).
This is done in transaction SM30 - T166C
Text number define in transaction OMF6
If you wish to define further fields as relevant to change notices, you must carry out the following activities:
1. Enter the table and field names
2. Select the document categories for which the field is to be relevant to change notices.
3. Assign a text number or routine
If you have specified your own routine, you can evaluate it in the user exit
EXIT_SAPLMEDRUCK_001.
-----Original Message-----
Subject: No output on PO changes
From: Norman Chan
Hi,
Anyone can advise how to make no output after changing PO. On SAP standard, whenever we change the PO, the change output will be created. However, we don't need that changes output, and we cannot find out how to customize it in IMG. Any suggestion? Thanks.
Thanks.
-----Reply Message-----
Subject: Re: No output on PO changes - Reply
From: Norman Chan
Yes, but the consequent problem is the system will give you the warning message that there is message come out ' No message record could be found for output of message.' The condition table is 'order type/purchasing org.'.
Thanks.
Norman
-----Reply Message-----
Subject: No output on PO changes - Reply
From: Ron Greenfield
Transaction OMQN, "Fine-Tuned Message Control, Purchasing". Delete the entry for operation "2" (Change) for your purchase order condition type.
rsg
What is an Amendment in PO and how it is done?
What type of changes generally comes after release of a PO?
Once a purchase order is released, the vendor is required to execute the order as per terms of order as defined in it.
However at times it is seen that there could be changes which might have taken place after the PO was released. This could be both from from Vendor side as well as the buyer side. Some typical changes could be :
Buyer side :
1. The qty ordered need to be increased.
2. The buyer need the material earlier than the delivery date specified.
3. The payment term need changes as buyer is not able to provide certain documents.
4. Buyer would like to add some more conditions.
5. The description need some additional information etc.
Vendor side :
1. The price no more valid as the order was released after the quotation validity expired.
2. The vendor is facing shortage of raw material and he wants the delivery schedule to be changed.
3. Vendor is offering some alternate materials or different make.
4. The payment term is no more acceptable as the prices have been revised. etc, etc...
In all such cases fresh communications are exchanged between the two parties and changes are made as per mutually agreed terms. In SAP the changes like qty, price, delivery date, payment term, pricing conditions etc can be tracked as changes in the document.
SAP does not have PO amendment but some companies are developing different layout for their orders based on above changes.
There are two ways to force close a PO:
1. You can set Delivery Completed Indicator in Purchase Order or at time of doing goods receipt. That simply means you cannot do further GR for that item. You can still process Open Invoices .
2. You can block material at purchase order level which means, you will not be able to do any GR , Invoice against that specific item in PO.
The recommended is the first option though.
Second option is used in case of : -
1. to cancel an item
2. An item is closed and can be archived
