Dont pick pricing procedure in PO from vendor-schemagroup vendor
PO has created, pricing procedure which had picked from standard, not from schema group vendor of vendor master record. How make to bring schema group vendor pricing procedure
Hi,
Please check if the Info record is already updated,delete the same from PO line item and then try to update new Pricing procedure by using Update Button.
Or Delete the line item in current PO and then add the new line item,it will trigger then new pricing.
Thanks & Regards,
Sandesh Sawant
Similar Messages
-
Can I assign more than one Pricing procedures to the one vendor.
Hi Gurus,
Can I assign more than one Pricing procedures to the one vendor.
If possible, where it can assign &give the procedure.
My client requirement is :
Vendor supply the goods from two different countries. So, pricing procedure is different because taxes are differ in two countries and currency also differs.
If goods are supplying from country u2018Au2019 ,automatically pricing procedure for that country was trigger. How the system know , which pricing schema is required.
Give me solutionHi,
Extend your vendor to new purchase organisation. Assaign new pricing procedure to this Purchase organisation.
Use different Purchase organisation while creating POs for the same vendor procuring from different countries.
Regards,
Satya
Edited by: Penjarla Venkata Satyanarayana on Aug 28, 2008 4:21 PM
Edited by: Penjarla Venkata Satyanarayana on Aug 28, 2008 4:23 PM -
How the systems pick pricing procedure in PO?
Hi Masters
I have deleted the pricing procedure assignment thro schema group in the configuration.But the system picks the pricing procedure RM0000.How?
Regards
MohanHi
Thank you for your replies
I have maintained blank entries of shema group for the purchasing organisation and vendor.And I have also deleted entries for assignment of blank entries to a pricing procedure in the following path
Materials Management->Purchasing->Conditions->Define Price Determination Process->Define Schema Determination->Determine Calculation Schema for Standard Purchase Orders
ie., Schema grpPorg Schema Grp Procedure
Blank Blank XXXXXX -
deleted this entry
01 Blank AAAAA
My question is how the systems picks pricing procedure in PO although the assignment is deleted?
-Mohan -
Hi,
I am a SAP MM learner.
I have done the pricing procedure for CIN (ZAXINN) in IMG - FI part. I have assigned the calculation procedure to the country IN also.
But while creating the PO, the calculation procedure taken is RM00001 from MM. Because of this i am not able to complete the cycle. Pls help me to make the proper setting to get the ZAXINN procedure.
Thanks,
N MuraliHi
1. I have created a pricing procedure ZAXINN in FI Module for CIN (capturing Cenvat amounts like BED, AED, SED, E Cess, etc).
2. I have checked the assignment of the pricing procedure in the below mentioned 4 headings and found to be correct.
-a. IMG > FI > FI GLOBAL SETTINGS > TAX ON SALES / PURCHASE > BASIC SETTING > ASSIGN COUNTRY TO CALCULATION PROCEDURE
b. IMG > LOGISTICS GENERAL > TAX ON GOODS MOVEMENT > INDIA > BASIC SETTING > DETERMINATION OF EXCISE DUTY > SELECT TAX CALCULATION PROCEDURE
c. T Code - OBBG
d. T Code - OY01
3. I have completed all the IMG settings for the CIN.
4. But while creating the PO, system automatically picks the pricing procedure of RM0000 from MM Part.
5. I tried doing the MIGO and found all the Excise amounts are getting captured properly and getting posted to the necessary GL accounts.
6. But I am not able to do the MIRO because the condition type is not picked up during the purchase order creation. I need a help to find out what setting to be done in SAP to pick up the pricing procedure while creating PO which is assigned to the country IN for completing my project.
Thanks,
N Murali -
What is difference between tax procedure and pricing procedure?
Dear Gurus,
Would you please let me know the difference between tax procedure and pricing procedure?
Why it is necessary to maintain them separately?
Thanks in advance,
RanjanHi
Tax procedure settings
OBBG - Assign Country to calculation procedure.
OBCO - Specify structure for Tax Jurisdiction code. For country like U.S.A.
LG -> character length of first level of hierarchy within your tax jurisdiction code structure.
LG -> Second level of hierarchy as above.
LG -> Third level of hierarchy as above.
LG -> Fourth level of hierarchy as above.
TX -> Tick if you want the system to determine taxes on a line by line basis instead of determining them on a cumulative basis
per tax jurisdiction code.
OBCP - Define Tax Jurisdiction code
Dil -> Tick if you do not want tax amounts included in the based amount used for calculating cash discounts.
Txl -> Tick if you want the cash discount amount deducted from the base amount that is used to calculate taxes.
FTXP - Define Taxes on Sales/Purchases Code.
OBCL - Allow Tax codes for non-taxable transactions.
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.
Regards,
Raman -
Hi Friends
Explain how the pricing is determined for an item, starting from the sales order
Discuss the full cycle also make a mention on the Condition type controls, and Maintain pricing procedure controls.
Kindly explain it with an example.
ThanksPricing Procedure is indeed an heart of SD module, reason being if everything else is working fine, but price is not being calculated correctly, the purpose of billing fails.
An Overview of Determination & Configuration of Pricing Procedure is as follows:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG -> Sales & Distribution -> Basic Function -> Pricing Control -> Pricing Procedure --> Determine Pricing Procedure.
Step 5: Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. -
Pricing Procedure (Debit Memo)
I have a pricing procedure at oder level let suppose ABC, I made delivery and billing all is well till that.
Than if delivered quantiy is less than the target quantity client will suppose to create a debit memo sort of penality to the customer, reference to that invoice quantity confirmation source is POD.
My debit memo pricing procedure is different from ABC, mean a PROO and MWST is appear on that not other charges or condition type.
I have assign the procedure at debit memo sales document type but what happen when in VA01 give the reference of invoice and copy the item the whole same (ABC) pricing is came up on the order (Debit Memo Request) which is not required I want the actual procedure will call.
If after this i directly go to the billing document after approval of this document my actual pricing procedure is there, but a different condition type is present in the 2nd pricing procedure that will not come, so I manually press the "Carry out new pricing" so that condition type than will appear..
Hope my gurus understand the problem. I want that actual pricing procedure is available at order if not that all the condition type will appear at the time of billing. I cant set the carry out new pricing setting in the copying control because if i done this the whole condition type of order will aappear at billing as well.
if have any query please feel free to ask.
Regards,Dear W,
I have a pricing procedure ABC having following condition types
1. PR00
2. ZSED
3. ZWEH
4. MWST
sales to order above procedure work and i got the accounting documents and invoice.
My 2nd pricing procedure is XYZ for Debit Memo and assign on document type, have th efollowing steps.
1. PR00
2. MWST
3. ZHE1
4. ZHE2
when i create debit memo with reference to invoice at debit memo (Sales document type) the pricing procedure ABC is come automatically, and when I go to billing the actual pricing procedure is come, plus i have to press maullay carry out new pricing button, other wise the common condition type is came at billing, if in copying control if i by default maintain the carry ou tnew price system duplicate the condition types.
Hope you will now understand my issue and give any value added feedback for the resolution of hte issue.
Regards, -
Pricing procedure execution...
Hi Folks,
How SAP reads the pricing procedure..
Example
Con.Type Requirement Routine
ZSAA 601 901
ZSAB 602 902
Doubt 1: -Is system reads this pricing procedure line by line or coulmn by column?, In the debug we noticed it goes column by colmun? why?
Doubt 2: - I want to know the value found for ZSAA during the execution of 602 requirement. Example scenario is if ZSAA is more than 100$ don't execute ZSAB.Pricing Procedure:
Determination of Pricing Procedure:
In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure through T.Code: OVKK. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
Configuration of Pricing Procedure:
Step 1:
Condition table (T.Code: V/04): If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence (T.Code: V/07): If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type (T.Code: V/06): If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure (T.Code: V/08): It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure (T.Code: VOK0): After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record (T.Code: VK11 / VK12): Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc. Condition Record is maintained in T.Code: VK11 / VK12, which are captured in Sales Order & Billing.
Also check document pricing procedure in Sales Document Type (T.Code: VOV8 - Sales order Type, VOFA: Billing Type (If Required)), customer pricing procedure in Customer Master Data (T.Code: XD02), ... are in place.
Regards,
Rajesh Banka
Reward suitable points. -
Pricing procedure with a reference of a billing document
Hi all,
How to apply new pricing procedure when you use a reference of another billing document?
by VA01, I want to use a billing document as a reference to create another sales document. Tthese 2 has different pricing procedures but when I do this, I want the sales document to use its own procing procedure.
But when I refer a billing document and create a sales document at VA01, it copies the billing document's pricing procedure.
These 2 pricing procedures have different condition types.
I already went to "Maintain Copy Control for Sales Document" - "Copying Controld: Billing Document to Sales Document" and set "B" as its pricing type.
Waiting for a valuable replies from y'all.
Best regards
MisakiHI,
Thank you for your reply,
I already have assigned pricing procedures to the required order types at OVKK, and V/08.
but it still doesn't go right.
When I don't refer any billing document at VA01 and simply create a sales document using required order type, the assigned pricing procedure is used. However, when I use a reference of a billing document to create a new sales document, it copies a pricing procedure from the refered billing document and doesn't use its own pricing procedure.
Wanting to know how to redetermine a pricing procedure to create a sales document when referring a billing document.
Ideally, the new sales document doesn't copy a pricing procedure at all from the reference(billing document), if possible.
I really appreciate for your help.
Misaki -
How to design a Pricing Procedure with both MWST and MWSI in it ?
Hi there.
My business requirement dictates that I can have both Tax inclusive(PR01/MWSI) and Tax Exclusive(PR00/MWST) items within a Single Sales Order.
I know that One pricing procedure can only be assigned to 1 Document Type. So,
Has anyone successfully created a Pricing Procedure that incorporates both the MWST and MWSI tax components ? If so, could you post a sample of the pricing procedure in order for me to understand how I should group the discounts/surcharges and reflect the Subtotals, as well as incorporate the MWST and MWSI all within a single Pricing Procedure ? I will also need to include the PR01 and PR00 conditions into the procedure too, right ?
Really really hope someone with the experience, can aid me on this. I cannot find any relevant materials on this matter, both in OSS Sapnotes and within this forum.
regards
PooIn SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
In SD, the steps to configure Pricing procedure are as under:
Step 1:
Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
Step 2:
Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
Step 3:
Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
Step 4:
a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
It is assumed that document pricing procedure, customer pricing procedure , ... are in place.
Similarly in MM Module we have Pricing Schema.
Regards,
Rajesh Banka
Reward points if helpful. -
Redetermination of pricing procedure and its condition types during credit
Hello ALL,
please provide the solution to redetermination of pricing procedure and its condition types during credit memo request
with referance to invoice
And kindly provide the step by step process of rebates
regards,
ThanksHi,
In standard setting the copy control from billing to sales document uses data transfer routine 052 (FV45C052). Within the standard the pricing procedure is copied from the billing document to the sales document and will not get redetermined. This is standard design.
However, if you would like the sales document (credit memo request) uses its own pricing procedure instead of copy that from the billing, you can implement this by using your own routine. In that case, please see note 14136 for a sample.
Please notice that you would also need to assign a different document pricing procedure for document type of credit memo request in VOV8. Then enter the new entry in OVKK to determine the pricing procedure for the new combination.
Regards,
Alex -
Hi all,
I have problem identifying the link between the schema group and the pricing procedure. Where is that in SPRO?
And also, which transaction do i use to maintain the condition records?
How do i know if the pricing procedure is for PO or for info record? or rather can i actually configure a pricing procedure for info record?
thanksPricing 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 schemasNew 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 groupsvendorNew 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.
hope this will clear ur doubt.Definitely it will help you something.
Reward the points -
Hi,
How system copies pricing procedure from sales document to billing documentas you know pricing procedure is determined by
sales area + doc. pricing pro. + customer pricing procedure
document pricing procedure will come from sales document types and Billing Types.
customer pricing procedure will come from customer master
Between the sales document and billing document the only factor that could change is the document pricing procedure
If they do not differ the same pricing procedure would be used and the control would be as per the configuration given in the copy controls.
If they differ then new pricing procedure determination will be carried out but for that in copy control we need to maintain PRICING TYPE AS B carry out new pricing else it will give you error saying pricing procedure could not be determined -
Hi Gurus
Please help me regarding the Pricing procedure for MM.
How can i go and what are the steps. how they work.
PraneshHi,
Please follow the 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 typeu2026condition types- definition (define for basic price, net price, discount, surcharge, tax etc.)
2. Defining pricing procedure :
/NMEK0- calculation schema-calculation schemasu2014New 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 typeu2026condition types- definition for position for defined conditions (Enter the defined pricing procedure in the each independent conditions u201CPricing Procedureu201D box)
4. Defining Schema group for Vendor :
/NMEK0- calculation schema-schema groupsu2014vendoru2014New 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 u201CPurch. Org. data1u201D and enter condition types and pricing procedure
Activities in Materials Management
Activity Transaction
General overview of conditions MEKA
Create conditions MEK1
Change conditions MEK2
Display conditions MEK3
Thanks & Regards
Anilkumar Dalai -
Changing in pricing procedure for PO
Hi guru,
i want to change in current pricing procedure and want to use this pricing procedure only for some vendors.
so plz tel me how can i do same configuration.
Regards,
AnuHI,
Fits copy your existing pricing procedure and make changes in new pricing procedure and save it .
then in path SPRO-MM-Purchasing -Condition-Define price determination process-copy your existing pricing procedure and save and make changes what you want
then create new vendor schema In same path -under Define schema group
now in same path under schema determination assign your new pricing procedure to your purchasing organization schema ( existing ) new vendor schema group
once complete this then assign new vendor schema in vendor master record for which you want new pricing procedure and create Po and check your new pricing procedure there and new pricing procedure
Regards
Kailas Ugale
Maybe you are looking for
-
How to find rowid of locked rows?
Hello All, I have the "before update trigger" I want to know the rowid of all the locked row before update so that I dont try to update the same row which is locked by some other user. In Ask Tom forum I have seen how to know the rowid of locked row,
-
MBP Retina 13" trouble connecting wirelessly to servers
A couple of months ago i purchase a new Macbook Pro Retina 13" from Apple directly. In my office i used to connect over ethernet. For some reason the wifi continues to drop my connection to the file servers here. I can't figure it out. My internet sl
-
Hi Experts, i'm new to HR reporting, Now My Requirement is to add 16 more fields to existing report . Transaction for that report is S_PH9_46000434. for doing this ,wht is the approch to follow. explaine me in detail please. The program being RHXTEIL
-
Problem in saving long text data from custom
Hi Expert, I am working on a screen exit in QM01. I have created a editor box(like the description box under Description tab in QM01) using class cl_gui_custom_container and cl_gui_textedit. I am able to create and display the text I type in the box
-
Nokia n8-00 screen "slidding" problem
Since yesterday that shows a problem with the screen. This problem "emerged" out of nothing during a video call and now I can´t use the phone properly. This problem appears every time I try to do something with the phone and even when i'm not doing a