STO PRICING INTERCOMPANY MANUAL PRICING IN STO also

Hi ,
I know there is lot of info available reg STO on this forums .But i am looking for detailed step by step configuration involved for Pricing in intercompany STO process.If its posted on this forum please provide the link.I will be thankful and full points will be awarded
Please guide me in doing Pricing configuration for intercompany STO process in detail steps. full points will be awarded.
One more thing is I also need detail steps for manual pricing in STO Intercompay process.Please guide me how to proceed
Thanks

Hello,
Is ZPRO is copy of PI01.If yes, make sure Ref cond tab should be blank (V/06).
Check Sequence in your pricing procedure(V/08).Zpro & Zk04 Should be before net value calculation.
If Pi01 is not required then you can determine new pricing procedure in intercompany billing.
Revert if not resolved.
Regards
Amit

Similar Messages

Recommendation for maintaining pricing in CRM when R/3 is also in landscape

Hi,
in out context we have already SAP R/3 in the landscape, all the pricing in done in R/3. lot of custom pricing routines are also written in r/3.
now we in the process of implementing CRM and plan to do Quotations in CRM and replicate in SAP R/3 . what is the recommendation for such a scenario.
do we replicate all pricing conditions/procedures in CRM? do we need to re-do all procedures in IPC?
can we re-determine pricing in R/3 so that we can avoid such work in CRM? we are using configurable products in R/3.
please share your thoughts/best practices and any document will be of help.
thanks
RH

Hi Swaroop,
The Assignment of Buisness Partner classification from CRM to R3 is purely based on Classification
so your initial Entry
I chose B as classification & Z001 as an account group which is a copy of 0001. System takes it.
was taken by the system
now when you tried to make another Entry by the same Classification
chose B again & this time Z002 acc gp (copy of 0002), and system does not allow?
it checks for the Existing Classification and so does not allow the same
Delete the Previous Entry and then Try Entering the New Entry
The System shall Take it
Hope it Answered your Queries...
Revert Back for any Doubts..
Also Chk the Link for details:http://help.sap.com/saphelp_crm50/helpdata/en/04/4d9ac77b2b11d3b52f006094b9114a/content.htm
Thanks and Regards,
RK.

CVD not capturing in GRN(101 mvt type) with reference to STO

Hi Experts,
This regarding the CVD not capturing at the time of 101 movement against STO.
My scenerio is as follows.
I am importing some materials. Import PO will be based on a pricing schema where no CVD or customs duties are maintained. Against that Import PO GRN (101mvt type) will takes place at Port plant(Maintained Port as a plant). Now STO will be done from the manufacturing plant setting port plant as the supplying plant.This STO also based on the pricing schema where the Customs duties as well as the CVD s are maintained. Miro for the BCD & CVD will be done based on this STO and then MB1B with 351 mvt type will be done .Then by analysing financial documents having the CVD and BCD entries will be generated at the time 351 mvt type. Then GRN (101)at the Manufacturing plant against STO will be done. But in the Excise duty field the CVD values are not capturing.
Why CVD values are not capturing? Is it a std SAP functionality? If so please explain the logic.
If not please guide me why it is not capturing.
If Only at the time of 351 these excise invoice will be generated. How can I track the Invoice because during mb1b I am not supposed to put any vendor excise invoice number.
Please analyse this scenerio and guide me with your experience in this Ocean.
It will be helpful for me to tackle this issue raised by a client if you put some significant threads on this.
Thanks & Regards
Prabhul

Dear
It is not possible in standard SAP. use the MB_DOCUMENT_BADI.
To get the order components use the COXT_BAPI_GET_DETAIL.
Now while doing goods issue using transaction code MB1A and MIGO system has to do the check:
If Quantity of issue in goods issue screen + Quantity withdrawn <= Requirement quantity then allow the transaction else throw an error u201CGoods Issue not possible for Requirement quantityu201D

Stock transport order pricing

Dear All,
this thread I am posting in continuation of my doubts on STO. i have already posted a thread yesterdays and got the best answers on it and found the way to proceed.
now for understanding of pricing for STO pl guide:
my scenario was like this:
i have to transfer raw material from plant 8000 to plant 9000 on which freight of 1000 is paid.
1) when i am making the pricing procedure do i have to enter the only freight condition type in it.
2) is there any need to enter condition type PB00?
3) can i use the pricing procedure what i have defined for the local purchase and use only freight condition from it or i require the new pricing procedure?
this STO is without delivery via SD.
thanks and regards

thanks Sanjay,
i used the regular pricing procedure for STO. the system is not automatically taking the value in PB00 as there is no info record existing.
i entered the value rs 100 in PBXX and added rs 100 in freight condition type.
while doing goods issue from the supplying plant. the following entries are generated:
supplying plant inventory= rs 100 credited
receiving plant inventory = rs 200 debit
freight payable= rs 100 credit
1)is it necessary to have the condition type for basic price in STO?. cannot we live without it?
2) Like in po we can put tax code, can tax code be put in STO also?
i will try to simulate the scenario with your proposal by using condition type P101.
if you donot mind sharing any STO pricing procedure you have configured in your implementation please share with me, it would be of great help to me.
you can send me the screen shots, etc at email address:
[email protected]
with regards
Kavita

Pricing type in item category

Hi,
Can anyone plz tell me how to use the pricing type in item category?
also request for telling me, what the pricing type "K" stands for.
Regards.
amit

Dear Amit,
Pricing type
Specifies how the system treats pricing data when copying documents.
At the time of billing, the following pricing types are possible:
A: Copy pricing elements and update according to scale. The system
does not determine any new condition types
redetermines the scale prices for changed delivery quantities
B: Carry out completely new pricing. The system
carries out a completely new pricing (manually entered pricing elements are not copied from the reference document)
redetermines the taxes
C: Copy manual pricing elements and carry out a new pricing
for the others. The system
carries out a new pricing
copies the manually entered pricing elements
redetermines the taxes
Note: You must ensure that all the condition types which can be changed manually are marked with "C" in the "Manual entries" field in the "Changes which can be made screen section. Otherwise, the conditions (both the automatically and the the manually entered ones) could be duplicated and both be active simultaneously.
D: Copy pricing elements unchanged. The system
copies the pricing elements unchanged with automatically determined or manually entered surcharges and discounts from the reference document (scales are not read again). This means that the value remains unchanged even if the billing quantity is different to the order quantity
does not redetermine the taxes
Copy pricing elements and values unchanged. The system
copies the pricing elements and values and automatically determined or manually entered surcharges and discounts from the reference document without changing them (scales are not read again). This means that the value remains unchanged even if the billing quantity is different to the order quantity.
does not redetermine the taxes
F: Only used within the program
G: Copy pricing elements unchanged and redetermine taxes. The system
redetermines the following condition types:
taxes (condition class D)
Rebate (condition class C)
Intercompany billing conditions (condition category I)
Invoice list conditions (condition category R)
Condition types with condition category L
Cost conditions (condition category G)
Cash discount conditions (condition category E)
all other condition types are treated as for pricing type D
H: Copy pricing elements and redetermine freight. The system
redetermines the following condition types:
Freight conditions (condition categories B, F)
Condition types with condition category L
all other condition types are treated as for pricing type A
Also what is the use of pricing type "K"?
K - Adopt price components and cose. Redetermine taxes.
If you select pricing type as K system will copy the pricing elements(Price ,Discounts And Frieght) and cost from the source document and Taxes will be redetermined i.e taxes will not get copied from the source document.
I hope it will help you,
Regards,
Murali.

Open PIR quantity, unconverted Pld orders and open Prod/ STO orders

Dear all,
How to deal with open PIR quantity, unconverted planned orders and open production/ STO orders in the next MRP run? Do we need to delete/ reduce them manually?
Thanks and Regards,
Raghu

Hi Shiva,
Thanks for your immediate response. I have still some confusion.
Last month, I have material A with Production order quantity of 30000.
'A' has a component 'B' which is an in-house produced material. Three planned orders each of 10000 were generated for B. Of these two planned orders were converted to production orders. One is still in planned order form.
This month I am not going to use this planned order of B. I get new requirement for A. So during MRP run I get the planned orders for B also.
For the last month requirement, as I have not converted one planned order of B to prod order, there will an open quantity of A prod order in this plant and open STO quantity in another plant. Again the PIR will also be not reduced to the same extent. If I reduce the PIR manually or through some reorganization, what about the open quantity of prod order and STO
I think I can TECO the prod order of A. Is there any such thing for STO also?
Thanks and Regards,
Raghu

Sale order- Pricing -Access Sequence

Hi Gurus,
While creating Sale order, the price is picked from the Pricing procedure and Condition records maintained.
In PR00- Material price and Customer-Material special price is maintained in VK11.
So the system picks Customer Material combination price and the same we can see in the Item level conditions-Analysis for pricing and can also see it fetched record from where.
So for this Client wants in the following way: POPUP MESSAGE
At Sale order Warning Message that Price is taken from Which List- Normal Price List or Special Price List for Customer and Material combination
Is there some way to do this?
Thanks in Advance.
Best Regards
Sri

Hi,
U have to take ABAPER HELP No doubt please use this input if tis use full .
User Exits For Price Determination
USEREXIT_PRICING_PREPARE_TKOMK (module pool SAPLV60A, program RV60AFZZ)
This user exit allows you to copy additional fields for pricing in the TKOMK communication structure (header fields), which have not been provided in the standard SAP system. These fields can also be used for pricing in the billing document.
This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_PRICING_PREPARE_TKOMP (module pool SAPLV60A, program RV60AFZZ)
This user exit allows you to copy additional fields for pricing in the TKOMP communication structure (item fields), which have not been provided in the standard SAP system. These fields can also be used for pricing.
This user exit is described in detail in the "New fields in pricing" section.
USEREXIT_FIELD_MODIFICATION (module pool SAPMV61A, program MV61AFZA)
You can use this user exit to adjust the display of individual lines in the condition screen by changing the display attributes of the screen fields. This does not include the display of subtotals.
This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_KZWI (module pool SAPMV61A, program MV61AFZB)
You can change the display of subtotals in the condition screen by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_KOPF (module pool SAPMV61A, program MV61AFZB)
You can adjust the display of subtotals in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_FIELD_MODIFIC_LEER (module pool SAPMV61A, program MV61AFZB)
You can adjust the display of blank lines in the condition screen to your requirements by changing the display attributes of the screen fields.
This user exit is also used in order processing.
USEREXIT_PRICING_CHECK (module pool SAPMV61, program MV61AFZA)
You can install additional checks to the standard checks of condition lines (e.g. maximum/minimum value).
USEREXIT_PRICING_RULE (module pool SAPLV61A, program RV61AFZA)
In the standard SAP system, it is predefined which condition categories and classes can be copied or recalculated per pricing type. You can change the predefined standard procedure for each pricing type.
USEREXIT_CHANGE_PRICING_RULE (module pool SAPMV61A, program MV61AFZA)
You can use this user exit to change the pricing type that has been predefined in the copying control table in billing.
USEREXIT_XKOMV_BEWERTEN_INIT (module pool SAPLV61A, program RV61AFZB)
This field is used in the formulas and therefore initialized before the loop for the pricing procedure starts.
USEREXIT_XKOMV_BEWERTEN_END (module pool SAPLV61A, program RV61AFZB)
Within a loop for the price components during pricing, specific values can be transferred into the communication structures in pricing to be further processed.
USEREXIT_XKOMV_ERGAENZEN (module pool SAPLV61A, program RV61AFZB)
In change mode, you can change the dynamic part of the condition record (KONVD) that is always redetermined (i.e. it is not stored in database table KONV).
USEREXIT_XKOMV_ERGAENZEN_MANU (module pool SAPLV61A, program RV61AFZB)
You can use this user exit to change the ready-for-input fields of the manually entered condition record in add mode in the condition screen.
USEREXIT_XKOMV_FUELLEN (module pool SAPLV61A, program RV61AFZB)
This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record.
USEREXIT_XKOMV_FUELLEN_O_KONP (module pool SAPLV61A, program RV61AFZB)
This user exit is always called up during a redetermination of all or individual price components. You can change the work fields of the condition line. However, this only applies to conditions that have been determined via a condition record. This may include subtotals, manually entered conditions or conditions that have been calculated with a formula.
USEREXIT_PRICING_COPY (module pool SAPLV61A, program RV61AFZA)
You can change the KONV fields for copied price components
With best regards,
venkataswamy.y

Is there a procedure to auto populate shipping instructions on Kanban STOs?

Hello,
The scenario is this:
- intra-company STO (does not cross borders, no billing), type UB, created via Kanban when the bin is emptied
- for this organization, type UB STOs also originate from other sources (ie, conversion from Purchase Reqs), not just originating from Kanban; although for a single material within a plant, Kanban is the method and UB STO is the replenishment strategy
- Shipping instructions (on the Delivery Line Item tab) are a required field when UB STO is created directly, but via Kanban background process the STO is saved successfully without shipping instructions (I find this interesting). This is not a text for shipping instructions, it's the element EVERS, field name EVERS in structure MEP01313.
The problem is this:
- the user (in this case the planner) must go in to manually add the shipping instructions on the Delivery Line Item tab prior to SAP allowing delivery document creation & shipment activities. this manual intervention by the user is unacceptable to the business.
The desired solution from the business is this:
- the business has specified a default shipping instruction that they want (it is configured and ready to go)
Steps we've taken to resolve:
-I first thought of using a purchasing info record. But we cannot use a purchasing info record to default the shipping instructions because this STO is using SUPPLYING PLANT and not vendor as the relationship.
-Then, I thought about maintaining shipping instructions on the purchasing view material master record, but the requirement is to only default these shipping instructions when they originate from Kanban and when the STO type = UB. So I thought it was too broad because it could impact other purchasing functions for the same material, plus the info record doesn't work for supplying plant.
-Now I am thinking about a procedure of some sort to configure to find the correct shipping instructions when material master + STO data meet certain characteristics. Is there such a thing?
-Another option would be a user exit available in the STO to do a check for Kanban indicator and STO type and then to choose the desired shipping condition, but this doesn't seem as elegant as other potential options, and seems restrictive (ie, hard-coding the key for the desired shipping instructions or building a ztable with combinations of STO attributes and desired shipping condition, which requires maintenance).
-Finally, it seems odd that the background creation of the STO via Kanban doesn't trigger a hard error when it checks the document for completeness, rather than saving and getting a document # even though the document is missing a required field. This seems to point to STO user exit as a way to fix this problem.
Your thoughts on the assumptions we've made and the potential resolutions are greatly appreciated.
Rebecca
Edited by: Rebecca Slomski on Oct 8, 2008 7:37 PM

Answered my own question. This may help someone, so here is the answer for version 4.6.
The way to automatically default shipping instructions when the STO uses "SUPPLYING PLANT" instead of vendor is to first configure a purchasing value key that contains the shipping instructions. The path is: IMG>Materials Management>Purchasing>Material Master>Define Purchasing Value Keys.
Then, the material master record must be updated on the Purchasing View with the new purchasing value key.
Cautions to this approach:
1. Even though this is on the Purchasing View, purchasing value key is on the MARA table, so it is not a plant-specific material master setting. One purchasing value key per material master record.
2. The purchasing value key contains settings for reminders and over/under-delivery tolerance percentages. This is interconnected with the choice of shipping instructions. Be sure that the purchasing value key is configured to meet the wide variety of planning needs that could exist at multiple locations where the material is used.
3. Some of the above considerations are mediated by the fact that the material master purchasing value key is over-ridden by specific information contained on a purchasing info record or a contract.

CRM 5.0 pricing...custom fields

Hello folks,
I'm currently working on pricing configure in CRM 5.0
I have 3 new custom fields on the Service Order (item level) for which I need to set pricing along with fields - Sales Org and Product.
As the 3 "new" fields were not present in the Field Catalog, I added them on the catalog.
I created new condition tables/ new access seq./ new conditions types / new pricing procedure. Also the pricing determination is set.
Questions:
0) Have I missed any steps?
1) How do I maintain the condition records for the "Z" condition type? Is MasterData-->Prices and Conditions --> /SAP CND/GCM - MC the right place to set the condition records?
2) What communication structure needs to be updated for these 3 new custom field on the item level? CRMT_CUSTOMER_I_INT? Is this automatic or manual?
3) Can anyone provide me some pricing cookbook?
my email id is [email protected]
Please help !!
I'll generously reward the points.
Regards,
Amey

Hi jai
i've benn using this object to download pricing configuration in QAS and PROD environment even if, as matter of fact, it's not the best practice.
I suggest to create a Z adapter object with filters on relevant tables and then to run it also in QAS and PROD env.
The client, of course, should be open to customizing and workbench modification otherwise you're not able at all to download all the objects.
Regards
Carmine

Inter-company pricing

Hi all,
I have a cross company sales process and I am setting up 1 pricing procedure to be used for both
1. Sale to the end customer-Customer who orders goods from the ordering company code.
2. Bill the ordering company code- This is Inter-company billing document generated from the supplying company code to the ordering company code.
So my question is when I create the step 1. my intercompnay price IV01 is a statistical conditon, but when I create the step 2. thye IV01 doesnt remain statistical condition.
could anyone explain how does it happen or what influeces this. Thanks to all for ur help!!

Check the pricing procedure.
This condition type might be assigned with routine 22 (inter-company), so this works only for intercompany scenario, where in the code checks t001-bukrs ne t001k-bukrs condition is satisfied.
The condition type is checked as statistical condition type, but if you check the sub-total field in the pricing procedure, the value is assigned to value B- cost field KOMP-WAVWR. Hence the value is considered during pricing.
If you dont want this to be calculated, then the sub-total field should be assigned to value C-Carry over value to KOMP-GKWRT (statistical value). In this case, it will not be used in pricing calculations.
Also check the link where SAP documents informs the same (but not in detail) [Working with Intercompany Condition Types|http://help.sap.com/saphelp_47x200/helpdata/en/dd/5614e7545a11d1a7020000e829fd11/frameset.htm]
Hope this clarifies.
Regards

Authorisation for pricing conditions in sales order

Hi,
This could be a tipical requirement. he requirement is a sfollows:
Some users should not be allowed to enter / change some of the pricing conditions (manual) in the create / change mode of sales order (VA01/VA02). But they should be allowed to enter/change couple of other condtion types (manually).
The other requirement is to disable the functionality of adding new condtions type through dropdown in the item pricing condition screen in VA01/VA02. The pricing update button also should be in a disabled mode for some users.
Please advice me whether this can be achieved through some user exits or Basis authorisation?
Regards,
Sam

Hi,
Yes this can be done. If you are on EP4 you cna use the Badi PRICING_AUTHORITY_CHECK_UI to disallow users to use certain conditions.
If you are not on EP4 you can still use the exit userexit_field_modification in program LV69AFZZ to check against authorisation.
Choose the one that best suits your needs.
Regards,
Naveen

Delete pricing conditions line using BAPI_SALESORDER_CHANGE

Hi experts.
I've read the forum and OSS about this topic and don't have clear if it's possible to delete a price condition position (using BAPI). Using tx. VA02 I can delete pricing conditions, that's why I think should be possible.
We have a sales order created, and depending on the sold-to-party we have some discounts: RA00 (% discount) or RB00 (absolute discounts).
In some cases we need to insert/update or delete these pricing conditions. For insert/update, we don't have any problem using
BAPI_SALESORDER_CHANGE and setting the appropiate updateflag.
But... what would be the procedure to delete a discount, for example, RA00 fixed on a sales order? Has the logic_switch be informed specially?
        wa_cond-itm_number = lt_cond-itm_number.
        wa_cond-cond_type = lt_cond-cond_type.
        APPEND wa_cond TO i_cond.
        wa_condx-itm_number = lt_cond-itm_number.
        wa_condx-cond_type = lt_cond-cond_type.
        wa_condx-updateflag = 'D'.
        APPEND wa_condx TO i_condx.
Lots of thanks.
Javier

I am not positive on being able to delete a pricing condition through program.
Online when you try to change the pricing, SAP suggests us to redetermines the Pricing rather than just changing the values. And also the pricing condition config also plays a role... I think there was a setting which says Pricing condition to be manual which means you can add or delete the conditoin.

Butter stuff on Pricing Procedure Understanding

Hi Gurus
Please help me on Pricing Procedure Understating , Detail functionality of fileds , like   From , To, SubTo, Reqt, Altcty etc.
Regards\Adnan

Hello Adnan,
Pricing
     Menu path IMG sales & distribution basic functions pricing pricing control define & assign pricing procedures maintain pricing procedures (V/08).
     A pricing procedure consists of a list of condition types in a defined order, such as price, less discount, plus tax. Some controls exist in the pricing procedure. For example you can specify that a condition type is mandatory; it must have an entry defined either automatically or entered manually.
     The pricing procedure is also used in account determination. This determines the general ledge (GL) accounts to which the prices, discounts and taxes must be posted. The condition types in the pricing procedure are linked to an account key. This key in turn is linked to the GL Accounts. This shows the integration between the pricing in the invoice and the financial accounting module.
     It is suggested to use to the SAP standard pricing procedure RVAA01 to copy and make necessary changes according to the requirement while configuring a pricing procedure. The following is the control data of the pricing procedure in detail
1.     Step this indicates the number of steps in the procedure. The first condition type should be step 10; the second condition type should be step 20 and so on. It is possible to number the steps in the intervals of 1, but it is not suggestible as it may cause inconvenience when changing the procedure in future.
2.     Condition counter this is used to show a second mini-step within an actual step. For example, you may have assigned all you freight surcharges to step 100. However there may be three condition types, each representing a different freight surcharge. Thus you can assign a freight condition type to step 100, counter 1; another to step 100, counter 2; another to step 100, counter 3 and so on.
3.     Condition type this is the backbone of the pricing procedure. The condition type is the link from the access sequence all the way to the actual condition record. When you enter a condition type, the description field is automatically filled in with the description from the condition type.
     Note: A description without a condition type can be entered for sub-total or total or net price in between the condition types in the control data.
4.     From & To columns these are used in two circumstances
a)     To define the range for a sub-total for example, if you want to add up all the condition types from step 10 to step 50; you would enter 10 and 50 in the From and To columns respectively.
b)     To define the basis for a calculation for example, if a discount is defined as a percentage, you need to indicate which step must be used as the basis for the calculation. If the calculation must be performed from step 100, you would enter 100 in the From field.
5.     Conditions determined manually indicates if the condition type it is assigned to is allowed to be processed automatically or only manually. Conditions, that are given this indicator in the pricing procedure, are only included in determination (price determination, output determination, and batch determination) either if they are entered manually, for example, on the condition overview screen in Pricing or if they are transferred from an external process, such as costing.
6.     (Note: when assigning the pricing procedure to the sales documents, a condition type is also assigned to it; reason being that the condition type assigned to the sales document here is displayed in the sales document item level which can be manually changed - provided it is indicated while configuring the control data - conditions determined manually). This feature is more often used in case of costing and output determination.
7.     Condition is Mandatory the mandatory column identifies those condition types that are mandatory in the pricing procedure. Mandatory condition types are the sales price or the cost price. If the mandatory condition is missing in the pricing procedure, the system has an error in pricing and the respective sales order cannot be processed.
8.     Condition is used for statistics - This indicator causes a surcharge or discount to be set in the document statistically (that is, without altering the value). This can be used to represent the cost price of the material sold.
9.     Print determines which descriptions and associated values assigned to a step are printed on a document, such as order confirmation.
10.     Condition Subtotal - Controls whether and in which fields condition amounts or subtotals (for example, a customer discount or the cost of a material) are stored. If the same fields are used to store different condition amounts, the system totals the individual amounts. These condition amounts or subtotals are used as a starting point for further calculations. You may, for example, want a subtotal of all the discounts included in the pricing of a sales order. These subtotals are used in other areas of the system such as in logistics information system. It is recommended that you assign the subtotal field 4 to the total value in the pricing procedure for Freight.
11.     Requirement this column is used to assign a requirement to the condition type. This requirement can then be used to exclude the system from accessing the condition type and trying to determine a value. This can be used to specify that the condition type, a discount, should only be accessed if the customer has a low risk credit group.
12.     Alternative calculation type - specifies that the system is to use the formula represented in this column as an alternative in finding the value of the condition type, rather than by using the standard condition technique. This can be used to calculate complex tax scenarios. This field is used in obtaining values such as Net Price, Profit Margin where there wouldnt be any access sequence to get the required value. Instead the system calculates net value using the existing amounts and the alternative calculation types. (formula: profit margin = net value cost price)
13.     Alternative condition base value is a formula assigned to a condition type in order to promote an alternative base value for the calculation of a value. For example, one can specify a formula that uses a subtotal, such as 4, from the subtotal field; modify it slightly, such as dividing it by 2, and then using the resultant value as a base value for the condition type.
14.     Account key - Key that identifies different types of G/L accounts. The account key enables the system to post amounts to certain types of revenue account. For example, the system can post freight charges (generated by the freight pricing condition) to the relevant freight revenue account.
15.     Account key accruals/provisions - Key which identifies various types of G/L accounts for accruals or provisions. With the aid of the account key, the system can post amounts to certain types of accruals accounts. For example, rebate accruals which are calculated from pricing conditions can be posted to the corresponding account for rebate accruals.
REWARD POINTS IF HELPFUL
Regards
Sai

GATP in APO and Free Goods Pricing Records in R/3

We have set up Free Goods in SAP R/3. These free goods are granted based upon a series of access sequences in pricing.
We also have our Order Entry system using GATP on our APO box. In that APO instance, we have set up a large number of product substitutions to occur at order time.
When an item is ordered that is NOT subbed to different item by APO and that item has Free Goods associated with it, the Free Goods are granted by R/3 and placed onto the sales order.
When an item is ordered that IS subbed to different item by APO and that item has Free Goods associated with it, the Free Goods are NOT granted by R/3.
Why are the Free Goods being ignored after the substitution? We have Free Goods records in pricing for BOTH items, and neither one is granting the Free Goods.
Is this a bug, a feature, or an oversight ?
Any help in this area will be GREATLY appreciated!!!

Hi John,
GATP in APO does not supports Free Goods.
Rohit
Edited by: rohit kumar on Feb 20, 2009 1:33 AM

Pricing: New condition type not getting listed in options in product master

Hi,
I have created a new pricing procedure and also created a new condition type for it. I am trying to create a condition record in the product master for this condition type but the condition is not there in the list of conditions. How can I inlcude it in the condition list?
Even the new condition type I have created by copying 0PR0 is not getting listed in the options, whereas 0PR0 is getting listed.
Regards,
Meenakshi
Edited by: Meenakshi Sawhney on Sep 9, 2010 8:27 AM
Edited by: Meenakshi Sawhney on Sep 9, 2010 8:29 AM

Hi Meenakshi,
you need to enhance the condition maintenance group in the customizing, which is assigned to the product master. Please check: IMG: Customer Relationship Management -> Master Data -> Products -> Special Settings for Sales Operations -> Assign Condition Group to Application CRM and IMG: Customer Relationship Management -> Master Data -> Conditions and Condition Technique -> Condition Technique: Basics -> Create Maintenance Group.
Best Regards,
Michael

STO PRICING INTERCOMPANY MANUAL PRICING IN STO also

Similar Messages

Maybe you are looking for