Mrp pricing standard procedure

hi gurus,
we r using mrp pricing for retail invoice.how to configure it.is there any sap standard pric. procedure for mrp pricing..is there any need to create routines or standards r available.
can any body help regarding this
regards
reddy

thanks
I want to create MRP based pricing.
In MRP based pricing all calculations are done by backward.For that i have to develop one formula which contains Multiplication & division, so for that i have to develop routine, how we define routine?
Is there any std. routine is available for MRP based pricing?
I explain the detail senario as follows:
My invoice value is 1000 which contains all the inclusive price containing Freight,P& F,Sales tax(CST or VAT),& Excise Duty which is calculated on based of MRP (67% of MRP Value-Assessable Value)
When i want to calculate 5% P&F which is already included in pricing for that i have to develop one formula for that like (A=Inv. Value * (100/100 + P&F=5))=A=952.38 . Inv Value = 1000
After this calculation I got the correct value for P&F like
Invoice Value- A (Which is calculated)=1000-952.38=47.62
same formulla i want to use for CST,VAT & Freight.
so i can calculate exact sales revenue value.
So plz send me detailed information about the same.
Also sed me how to develop the routine?
Thanks & Regards,
reddy

Similar Messages

I followed the same procedure of reverse calculation from MRP pricing calcu

hi,
sap gurus,
i followed the same procedure of mrp calculation but
MRP Pricing Procedure:
Go through the following:
I will brief your requirement in short
MRP = 1012.5/-
VAT = (1012.5/1.125) = 900/-
so price before discount will be = 900/-
discount given at the rate of 10% = 100/-
Initial Price = 1000/-.
1. Create condition types as below:
ZR00 for price
Condition class = B
Calculation type = C
Plus/minus = A
ZSET for settlement (to knock off the effect of ZR00)
Condition class = A
Calculation type = C
Plus/minus = X
ZWST for tax
Condition class = A
Calculation type = H
Condition category = D
Plus/minus = X
Z007 for discount
Condition class = A
Calculation type = H
Plus/minus = A
ZDUM for net price
Condition class = A
Calculation type = A
Plus/minus = A
YWST for tax (to knock of the previous effect - to be used for posting to G/L)
Condition class = A
Calculation type = A
Plus/minus = X
YOO7 for discount (to knock of the previous effect - to be used for posting to G/L)
Condition class = A
Calculation type = A
Plus/minus = X
2. The following will be the pricing procedure configuration:
Step......No........Cond Type........... From.........to..........Man.........Req........Sta................Acc Key
10........0..............ZR00..................--..........--..........-...........-........---.................ZDU
20........0..............ZWST..................10............19...........----.............X............X...................
30........0.............text.......................10...........29...........---...........----.........X
40........0.............Z007.....................30...........39...........-----.............X............X
50........0..............text.....................30............49...........---...........-----.........X
60........0............ZSET.....................10...........19...........----............X............--.................ZDU
70........0............ZDUM....................50...........59...........----............X............---...............ERL
80........0............Y007.....................40...........49...........----.............X...........---...............ERS
90.......0..............YWST..................20...........29...........-----............X...........---................ZWS
ZDU - dummy account key for posting extra not required items.
ERL - account key for price
ERS - account key for discount
ZWS - account key for tax.
3. Condition records in VK11
Condition type----
Condition record.......
ZR00........................................1012.5.....................INR will be positive (1012.50 +)
ZSET.......................................100%...............................will be negative (100 -)
ZWST.......................................10%................................will be negative (10% -)
Z007.........................................12.5%.............................will be positive (12.50 +)
ZDUM.......................................100%..............................will be positive (100% +)
Y007.........................................100%.............................will be negative (100% -)
YWST.......................................100%.............................will be negative (100% -)
Condition records for Z007 & ZWST will be decided as per the conversion required. You will first have to manually calculate the amount for the condition type.
4. I create a sales order for single quantity for an item & the pricing will be as under:
ZR00 = 1012.5 (dummy account) - positive
ZSET = 1012.5- (dummy account) - negative will knock off effect of ZR00
ZWST = 112.5- (negative & no posting)
Z007 = 100 (positive & no posting)
ZDUM = 1012.5 (positive & posting)
Y007 = 100-(negative & posting)
YWST = 112.5 (positive & posting)
but its not throwing any condition records for ZWST and YWST
can any body help me
plz
regrds,
balaji.t

HI,
Plz try Routin for Vat formula.
i am worked on MRP pricing but in our case formula is different.
eg.: If i want to calculate VAT for B=1000 Rs. it is like
A=1000 * ((100/100 + (12.5- VAT 5)))
= 889
VAT (Value) = B - A = 1000-889 = 111 which is passed to GL account.
For that we developed one Routine with the help of ABAP and assign to Pricing Procedure.
Regards,
PM

Mrp pricing procedure

dear all,
we have created new pricing procedure called mrp pricing procedure.which means in procedure we have given mrp price as base price. system would calculate taxes (calculating backwards) on billing value derived after discuont .ex.
mrp              rs.1000.00
disc. @10%       100.00
billing value            900.00
taxes12.5%       100.00 (900 /1.125)
net(billing value-tax)   800
we need net value to be passed to accounts We have introduced new pricing condition type " zdum" which represents net value thereby we could pass values to accounts.
atter this , discount and tax condition types are not passing to accounts .In the analisys we found that discount condition type is in active because of subsequent price
we need to achieve net value, tax discounts should pass to accounting.
kindly give your inputs on this .
thanks and regards,
reddy,
Edited by: YUGANDHAR REDDY on Jul 21, 2008 10:23 AM

Hello,
Go through the following:
I will brief your requirement in short
MRP = 1012.5/-
VAT = (1012.5/1.125) = 900/-
so price before discount will be = 900/-
discount given at the rate of 10% = 100/-
Initial Price = 1000/-.
1. Create condition types as below:
ZR00 for price
Condition class = B
Calculation type = C
Plus/minus = A
ZSET for settlement (to knock off the effect of ZR00)
Condition class = A
Calculation type = C
Plus/minus = X
ZWST for tax
Condition class = A
Calculation type = H
Condition category = D
Plus/minus = X
Z007 for discount
Condition class = A
Calculation type = H
Plus/minus = A
ZDUM for net price
Condition class = A
Calculation type = A
Plus/minus = A
YWST for tax (to knock of the previous effect - to be used for posting to G/L)
Condition class = A
Calculation type = A
Plus/minus = X
YOO7 for discount (to knock of the previous effect - to be used for posting to G/L)
Condition class = A
Calculation type = A
Plus/minus = X
2. The following will be the pricing procedure configuration:
Step......No........Cond Type........... From.........to..........Man.........Req........Sta................Acc Key
10........0..............ZR00..................--..........--..........-...........-........---.................ZDU
20........0..............ZWST..................10............19...........----.............X............X...................
30........0.............text.......................10...........29...........---...........----.........X
40........0.............Z007.....................30...........39...........-----.............X............X
50........0..............text.....................30............49...........---...........-----.........X
60........0............ZSET.....................10...........19...........----............X............--.................ZDU
70........0............ZDUM....................50...........59...........----............X............---...............ERL
80........0............Y007.....................40...........49...........----.............X...........---...............ERS
90.......0..............YWST..................20...........29...........-----............X...........---................ZWS
ZDU - dummy account key for posting extra not required items.
ERL - account key for price
ERS - account key for discount
ZWS - account key for tax.
3. Condition records in VK11
Condition type----
Condition record.......
   ZR00........................................1012.5.....................INR will be positive
   ZSET.......................................100%...............................will be negative
   ZWST.......................................10%................................will be negative
   Z007.........................................12.5%.............................will be positive
   ZDUM.......................................100%..............................will be positive
   Y007.........................................100%.............................will be negative
   YWST.......................................100%.............................will be negative
Condition records for Z007 & ZWST will be decided as per the conversion required. You will first have to manually calculate the amount for the condition type.
4. I create a sales order for single quantity for an item & the pricing will be as under:
ZR00 = 1012.5 (dummy account) - positive
ZSET = 1012.5- (dummy account) - negative will knock off effect of ZR00
ZWST = 112.5- (negative & no posting)
Z007 = 100 (positive & no posting)
ZDUM = 1012.5 (positive & posting)
Y007 = 100-(negative & posting)
YWST = 112.5 (positive & posting)
I hope this gives you a clear idea about the configuration required.
With best regards,
Allabaqsh G. Patil

How to split the Order items using standard procedure

Hi All,
               I am a BW Consultant and currently working for Sales Module. I have one question regarding the Order Item changes in VA02. For example a user creates one SO with Item 10 and the quantity is 1000. Later they want to split this Order into two i.e. they change the first item quantity to 500 and create another item (20) with Quantity 500 .Users are doing this ,because of allocation process.
             Now I would like to ask whether this is a standard procedure to follow.I have no issues with the new item , I am not sure how they are changing the first order item qty in VA02, because Qty is greyed out . My assumption is, they are deleting the item first and then recreating with the new quantity.
            Hence I would like to check is there any other option/process available to change the quantity and also would like to know whether it is a standard procedure? Reason I am asking this question is,extractor is not picking the correct records.Hence I suspect this is not a standard procedure to follow.
Please advice .Thanks for your time.
Thanks.

hi raja,
go to shedule line data of position 10
here you want to have 1000 pcs for the 18.12.2009
change her into
500 pcs for the 18.12.2009   and
500 pcs for the 21.12.2009
at 18.12.2009 you will get adelivery of 500
at 21.12.2009 you will get the rest.
in total, the Position has 1000 pcs.
hans

VAT/Excise calculation - map pricing & tax procedures

Dear,
Pls tell me how to map my blw senerio;
In pricing procedure, i have
A- Gross price
B- Handlying charges
C- Excise on A+B,
here i need to calculate my exise on A+B values and it flows (C) frm tax procedure (taxinn). until here i'm ok.
D - A BC
E - Insurance (defined in pricing proce) on D value,
here i'm unbale to map my price, since the sytem taking A+ B price only, its not taking my D values... I need to map pricing & tax procedures, since Gross price, Han. charges and insurance flows frm pricing proce and Excise frm tax procedure.
Anyone has right solution, pls guide me...

Hello sapjj
Here in your issue, u have to maintain a dummy condition type for excise calculation in your pricing procedure. The excise on A+B will be calculated in pricing procedure itself and not it flows from tax procedure.You have to make a condition type in pricing procedure and mark it as statistical in the procedure so that it doesn't get added to material value.
you are ok till gross price and handling charges, right?
Then you include your dummy condition type for excise amount calculation.Then in the next step calculate a subtotal without giving any condition type and maintaining 'S' in the subtotal field in the pricing procedure.
In the next step include the insurance condition type and calculate it on the subtotal.
This will help
Regards
Gregory Mathews

Standard procedure to transfer Inventory Items from one Warehouse to other

Dear All,
Please let me know what is the standard procedure to be followed while transferring Inventory Items from one warehouse to other warehouse through SDK. Right now I am using sql statements to deduct and add the items to and from warehouse. Its not working properly. Please let me if any business object is provided by SAP to achieve this functionality.
Regards,
Noor Hussain

Hello Noor,
You can use stocktransfer object:
Private Sub PostStockTransfer()
        Dim oDoc As SAPbobsCOM.StockTransfer = oCompany.GetBusinessObject(BoObjectTypes.oStockTransfer)
        oDoc.DocDate = Date.Today()
        oDoc.FromWarehouse = "01"
        oDoc.Lines.ItemCode = "A0001"
        oDoc.Lines.WarehouseCode = "02"
        oDoc.Lines.Quantity = 10
        If oDoc.Add = 0 Then
            sbo_application.MessageBox("Stock transfer Issued")
        Else
            sbo_application.MessageBox(oCompany.GetLastErrorDescription)
        End If
    End Sub
Regards
János

What is the Standard Procedure to Modify SAP Delivered BSP Application ?

Dear Experts what is the standard procedure to modify SAP delivered standard BSP application.
i need to enhance the cFolder application delivered by SAP, adding new fields to Notification Template. The task essentially boils down to add new field in database table and changing few HTML page content.
Greetings
John

Hi Vivek,
thanks for the answer. My requirement is to enhance few of the BSP Views with custom fields, i have figured out the ABAP table that stores the value of input fields displyed. what i am NOT understanding is when i make ZCopy of the views using BSP_CUSTOMIZE & change its UI to include my custom fields..how will the Standard BSP application PICK my zChanged views??
is there someway i can say to standard SAP BSP to PICK these Modified Z View ???
hope i made query clear ??
Greetings
John

Standard procedure to do repartitioning !

Hi I have an infocube and I want to repartition it. Now what standard procedure I should follow considering I want to make a back up of the Infocube. To make the backup infocube I cant use the cubes data as it is aggregated. Should I use the DSO to make a copy , well that would mean creating all the DTPs and transformation and doesnt make sense. What should be done in this case ?

No need to take a back of the info cube data.
The repartitioning function allows you to reorganize the InfoProvider by adding, merging, or completely repartitioning the dataset without the need to create a new InfoProvider or dropping and reloading the data.
Note:
Prior to taking advantage of this new functionality, you should back up the system/database. Although you can execute these partition options easily within SAP NetWeaver BI 7.0, SAP recommends that your system administrators back up your system and database prior to executing any of the repartitions options. This en¬¬sures that youu2019ll be able to restore the status of your data and system if an error occurs during or after you execute repartitioning.

Standard procedure pre and post BW SPS?

Dear Guru,
I have looked around but not able to find a good answer on a standard procedure/common practice as one implement BW support pack. After we implemented SPS21 in our production system this past weekend, we had endless data load issues but didn't happen in our test or QA system. I think I need a better list of what to do pre and post SPS.
Please share your experience on implementing BI support pack. What do you do pre and post SPS?
Many thanks in advance.
Chimei Shea

I re-read the note again, It says, If task manager content notes(1707321) are not applied, we will not see reports for stopping RDA Daemons and Process chains i...e report RS_SYSTEM_SHUTDOWN. However we are on NW 731 SP7 so we already have this report. This means we can go ahead with implementing the Z report from 1734333 and forget about the other note. Have I comprehended it correctly
Regards
Kalyan

Standard procedure of sales return

Can any one tell me the standard procedure of a sales return, with relevant T codes? Also, what if the customer want a replacement for the return?
A freshman. just eager to learn sth.
Thanks!

Hi Jerry,
Its Return order (Va01)-- return delivery(Vl01n)-- credit memo(Vf01).
You can create the return order w.r.t the billing doc.
If the customer wants a replacement instead of a credit note then you can give by using subsequent free of charge Delivery.
hope thiis helps.
Also just a friendly advice all such topics are discussed many a times in the forum you just need to search. This way you will save your time only as you will not have to wait for someone to respond.
Regards
Suchait

Standard procedure of component Rejection in production Order

Dear All,
I want to know what is the exactly standard procedure for posting rejection of component in production order?
Some points to be noted !
1).Rejection quantity is not constant. For example, material A can be rejected with 5 EA quantity or 20 EA quantity. so not a static quantity in BOM should be referred.
2) For example, If m going to post rejection of semi finish material abc which exist in finished material BOM. Semi finish material abc contains another semi finish material in its bom. Then how rejection process should be catered in this scenario.
Waiting for your kind responce
Regards
Ahmed

Hi,
You can reject/scrap the semi finish material while it's operational confirmation e.g. by CO11N.
You can put the rejected quantity in scrap or if require to rework then put it into Rework field. See the fields in below screen snap of CO11N,
If your semi finish BOM include another semi finish then at any operational confirmation if is consumed then cost of it considered and ultimately the same is also rejected.
Regards,
Narresh

Please explain me about pricing determination procedure in SAP SD ?

Could you please explain me about the pricing determination procedure in SAP SD ?
Edited by: Piruthiviraja on Aug 18, 2009 8:00 AM

Hello,
Please go through the following
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 u2013> Sales & Distribution u2013> Basic Function u2013> Pricing Control u2013> 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 u2013> Sales & Distribution u2013> Basic Function u2013> Pricing Control u2013> 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 u2013> Sales & Distribution u2013> Basic Function u2013> Pricing Control u2013> 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 u2013> Basic Function u2013> Pricing Control u2013> 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 u2013> Basic Function u2013> Pricing Control u2013> 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.
SANTOSH

Pricing condition/procedure set up for mark up price

Hi All,
I am struggling with a requirement related to MM pricing procedure. Below is the requirement:
When a PO is created of a material, it will have something called as markup price included in the price of that material. Example- If a material price is 100, it will be made up of basic price 90 + mark up price 10 (two different condition types -PB00 and say ZPB0).
Now when GR is posted, inventory a/c should be debited with 100, GRIR clearing a/c should be credited with 90 and GRIR clearing a/c for markup (new a/c) should be credited with 10. In short mark up price should be speared out in a different clearing account just like freight clearing account.
At the time of IR, there should be only one line item showing balance of 100. Note there should not be two line items, one with 90 and other with 10 (just like in case of planned delivery cost).
So, this scenario is very similar to planned delivery cost scenario except client doesn't want to have two line items in IR.
Is there any standard way to achieve this?
Regards,
Pat.

If you dont want the mark up to come in invoice separately, why do you want it to hit a GR / IR account? ( in short why use del cost condition )
If hitting gr / ir is not a requirement and you just need to acrue it, try the following
PB00 to take 100
create 2 conditions one positve and one negative ( accrual, without condition category ) to take the value 10
the + and - will cancel in the inventory account; you can accrue to different accrual accounts

MRP Pricing

Dear SD Gurus,
I have scenario where the client has the MRP price requirement, it is a reverse calculation the MRP price and dealer price is declared in the price list based on these two components you we have to arrive at the base price, has any one work on the this type of scenario kindly provide me with config steps.
Regards
Parvez

HI
Go through the following:
I will brief your requirement in short
MRP = 1012.5/-
VAT = (1012.5/1.125) = 900/-
so price before discount will be = 900/-
discount given at the rate of 10% = 100/-
Initial Price = 1000/-.
1. Create condition types as below:
ZR00 for price
Condition class = B
Calculation type = C
Plus/minus = A
ZSET for settlement (to knock off the effect of ZR00)
Condition class = A
Calculation type = C
Plus/minus = X
ZWST for tax
Condition class = A
Calculation type = H
Condition category = D
Plus/minus = X
Z007 for discount
Condition class = A
Calculation type = H
Plus/minus = A
ZDUM for net price
Condition class = A
Calculation type = A
Plus/minus = A
YWST for tax (to knock of the previous effect - to be used for posting to G/L)
Condition class = A
Calculation type = A
Plus/minus = X
YOO7 for discount (to knock of the previous effect - to be used for posting to G/L)
Condition class = A
Calculation type = A
Plus/minus = X
2. The following will be the pricing procedure configuration:
Step......No........Cond Type........... From.........to..........Man.........Req........Sta................Acc Key
10........0..............ZR00..................--..........--..........-...........-........---.................ZDU
20........0..............ZWST..................10............19...........----.............X............X...................
30........0.............text.......................10...........29...........---...........----.........X
40........0.............Z007.....................30...........39...........-----.............X............X
50........0..............text.....................30............49...........---...........-----.........X
60........0............ZSET.....................10...........19...........----............X............--.................ZDU
70........0............ZDUM....................50...........59...........----............X............---...............ERL
80........0............Y007.....................40...........49...........----.............X...........---...............ERS
90.......0..............YWST..................20...........29...........-----............X...........---................ZWS
ZDU - dummy account key for posting extra not required items.
ERL - account key for price
ERS - account key for discount
ZWS - account key for tax.
3. Condition records in VK11
Condition type----
Condition record.......
ZR00........................................1012.5.....................INR will be positive
ZSET.......................................100%...............................will be negative
ZWST.......................................10%................................will be negative
Z007.........................................12.5%.............................will be positive
ZDUM.......................................100%..............................will be positive
Y007.........................................100%.............................will be negative
YWST.......................................100%.............................will be negative
Condition records for Z007 & ZWST will be decided as per the conversion required. You will first have to manually calculate the amount for the condition type.
4. I create a sales order for single quantity for an item & the pricing will be as under:
ZR00 = 1012.5 (dummy account) - positive
ZSET = 1012.5- (dummy account) - negative will knock off effect of ZR00
ZWST = 112.5- (negative & no posting)
Z007 = 100 (positive & no posting)
ZDUM = 1012.5 (positive & posting)
Y007 = 100-(negative & posting)
YWST = 112.5 (positive & posting)
HOPE THIS SETTINGS WILL HELP YOU
Regards
Raja

MRP Lot-Sizing Procedures PK

Hi experts,
When we use lot-sizing procedures PK, I have a problem about it.
Can you please kindly help me.
The problem is.
When we run MRP and get the release date as past date in purchase requisition.
I would not like system to propose release date as past date.
Do we need more configuration for using lot-sizing procedures PK ?
The settings are mentioned as below.
* material master
- Lot size in MRP1 view : PK
- MRP Type in MRP1 view : PD
- Procurement type in MRP2 view : F
* MRP parameters
- Processing key : NETCH
- Create purchase req. : 1 (Purchase requisitions)
- Delivery schedules : 3 (Schedule lines)
- Create MRP list : 1 (MRP list)
- Planning mode : 1 (Adapt planning data (normal mode))
- Scheduling : 2 (Lead Time Scheduling and Capacity Planning)

please read below for the detail explanation of the release date.
please check the example part of below.
wish it help.
tks.
Purchase Requisition Release Date
Specifies the date on which the purchase order
should be initiated on the basis of the purchase
requisition.
The release date is based on:
The
     purchasing department processing time defined for the plant
The
     planned delivery time from the material
     master record or purchasing
     info record
The
     delivery date
The
     goods receipt processing time from the material master record
Note
The planned delivery time from the
purchasing info record and the GR processing time are only taken into account
if the purchase requisition was generated via materials
planning.
Example
Processing time Planned del. GR processing
Purchasing time time
|----------|---------------------|--------|
Release PO Delivery Date
date date date required
Date required: 01.10.2007
GR processing time: 2 days (working days)
Planned delivery time: 10 days (calendar days)
Purchasing dept processing time: 2 days (working days)
For the material to be available on the
date it is needed, the purchase requisition must be released on 13.09.2007
(requirement date less GR processing time, planned delivery time, and
purchasing department processing time).

Mrp pricing standard procedure

Similar Messages

Maybe you are looking for