Pricing Simulation based in a Manual Condition

Hello Dear Gurus,
I'm facing the following problem:
I need to simulate the net value of an Sales Order using ABAP code. But the net value is based in 2 manual conditions: FREIGHT and MANUAL PRICE.
I tried the FM BAPI_SALESORDER_SIMULATE. But in this case I'm not able to specify the manual conditions.
So I tried the FM PRICING_GET_CONDITIONS but it didn't return all the conditions.
Thank you in advance.
Fabio Purcino

Hi,
how did you solve your problem?
I also need pricing with manual conditions. If I call SD_SALESDOCUMENT_CREATE with all the parameters I used to call BAPI_SALESORDER_SIMULATE I don't get a netprice / netvalue in the items return table.
header: doc_type, sales_org, distr_chan, division
logic_switch-pricing: 'B' or 'C'
partners: sold to and ship to party
item: itm_number, material, target_qty, target_qu, sales_unit
The only difference using the BAPI is that I hafe to fill different quantity fields.
What could be missing?
thanks,
Christian

Similar Messages

Manual Condition type in Sales Order

Hi,
i need to enter a manual condition type in sales order which should come in % and the value should not come or it should come as zero, Is there any way to make that manual condition value as Zero in sales order.
Ragu

Raghu,
Pls check the OSS notes 392668, that will solve your problem.
The same pasted here for your reference. However, I advise you to download it and then read due to inconsistent formatting here.
Reward if this helps.
When you create documents in which the standard pricing is used to determine condition records as well as to calculate a pricing result, the display and entry of manual entries is not clear in the relevant condition screen (screen 6201 in the SAPLV69A or SAPMV61A programs for releases prior to 4.6A).
This note explains the interaction of manual entries with the attributes maintained in the pricing procedure and in Customizing of the condition type.
Other terms
KAUTO, V/06, V/08, KAEND fields, KOZGF, PRICING_CHECK, LV61AU08, XKOMV_ERGAENZEN_MANUELLE, LV61AA53, manual entries, MANU
Reason and Prerequisites
In the pricing Customizing, the following fields affect the manual entry of complete condition lines or individual condition rates:
Description        Technical name              Maintenance transaction in SD
Access sequence    KOZGF                  V/06 and V/07
'Manu'            KAUTO                  V/08
Depending on the characteristic of the mentioned fields, the pricing condition screen appears as follows:
KAUTO   | KOZGF    | Condition record existing on DB? | Result
Initial | Initial   | -                                | (1)
Initial | Existing | No                              | (2)
Initial | Existing | Yes                              | (3)
Set     | Initial   | -                                | (2)
Set     | Existing | No                              | (2)
Set     | Existing | Yes                              | (4)
Result (1)
A condition line is set for the relevant condition type [KSCHL]. The 'Condition rate' field [KBETR] does not contain a value, but is ready for input. The displayed line serves as an input help or a template for the manual entry.
Result (2)
No relevant condition line is set on the pricing condition screen, in other words, the condition type is missing.
If you enter the condition type manually without entering a condition rate in the same processing step, you get a 'template line' as described in (1).
Result (3)
A suitable condition record that exists on the database is set with amount (= normal, automatic determination).
Both the 'Condition origin' indicator [KHERK] and the 'Condition control' indicator [KSTEU] are set to 'A'.
If you create another line with this condition type and enter a condition rate not equal to zero, a line is set with this condition rate.
The 'Condition origin' indicator [KHERK] as well as the 'Condition control' indicator [KSTEU] has characteristic 'C'.
If, on the other hand, you create another line and enter a condition rate of zero (or do not enter any condition rate) and the condition record that exists on the database has a scale, the system sets the condition rate according to the achieved scale level. If zero is to be set as the condition rate even if scales exist, then use modification Note 179354. If no scale is maintained, then the system always sets zero as the condition rate.
In these cases, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] characteristic 'A'.
Result (4)
No relevant condition line is set on the condition screen, even though a condition record suitable for the access sequence exists on the database. The pricing analysis displays the message "Manual condition (Condition record exists)". If you enter the condition type manually without entering a condition rate in the same processing step, the record that exists on the database is set. If a condition record has a scale, the system sets the condition rate of the first scale level independently of the achieved scale level.
In this case, the 'Condition origin' indicator [KHERK] has characteristic 'C', the 'Condition control' indicator [KSTEU] has characteristic 'A'.
Thus, the setting variant leading to result (4) serves to suppress the setting of automatically found condition records into a pricing result. However, you can add the maintained record to the already determined pricing result by entering the relevant condition key.

Can pricing requirement be used for manual header condition

I have a manual header condition ZCR1 which will be entered in a sales document with doc type ZAB1. When this sales document is copied into another sales document ZAB2, I want that the manual header condition ZCR1 is not determined. Can I do this via pricing requirement? Or should I use alternation formula for condition base value and make the value of condition ZCR1 to zero when the document is copied into ZAB2.
Both the document types are using the same pricing procedure. In copy control for all item categories from ZAB1 to ZAB2, pricing type G (Copy pricing elements unchanged and re-determine taxes). ZCR1 is a manual condition in the pricing procedure used.
Regards
Javed

Hi javed
If you want the ZCR1 manual header condition should not be determined then you need to change the pricing type in the copy control but if you assign a requirement in the pricing procedure for ZCR1 condition type then you cant enter the ZCR1 condition type manually also as you are not meeting your requirement.
Another option is you have to create a new requirement with the help of Technical consultant ans assign it to the header condition type in the pricing procedure requirement feild . giving inputs to your Technical consultant that The condition type should not be determined
Regards
Srinath

Doubt - Service Contract - Pricing - "Retain Manual conditions" in SAPUI

Hi,
For service contract, at header pricing level, there is a button, "RETAIN MANUAL CONDITION". What is the purpose of this button?
what ever the result it gives after clicking on this button, I should get it through programatically.
Could you please help me out with any FM for this purpose..
Thanks,
Sandeep

Hi,
RETAIN MANUAL CONDITION button reprices the order keeping the manual conditions intact.
regards,
Chait

Doubt - Sales Order- Pricing - "Retain Manual conditions" in SAPUI

Hi,
For sales order, at header pricing level, there is a button, "RETAIN MANUAL CONDITION". What is the purpose of this button?
what ever the result it gives after clicking on this button, I should get it through programatically.
Could you please help me out with any FM for this purpose..
Thanks,
Sandeep

Hi Michael,
Thanks for mentioning the function modules.
My exact requirement goes like this:
I have sales order. Now I am creating the follow-up document to this. while creating the follow-up, the follow-up document should get updated with pricing condition, which we get when we click on "Retain Manual of Changes" of preceding document.
Currently I am using CRM_COPY_BADI, for creating this follow-up. But, I couldn't find any method, which updates the pricing conditions. Is there any other BADI, which can solve my purpose while creating follow-up?
Currently, I am getting the pricing conditions to my follow-up document: what ever I see on on SAPUI screen of Preceding documnet.
If I click on "Retain Manual Changes" of Preceding document and save. And then if I create the follow-up document, then it is getting what ever the conditions, the preceding document have.
But, user wants : Without clicking the button of preceding document also, the follow-up documnet should have the result of "Retain manual Changes".
I hope I am not confusing you. And I I hope you understood my requirement.
Can you please help me?
Thanks.
Sandeep

Addition of 2 manual conditions in pricing procedure.

Dear all,
I have three conditions, ABC1, ABC2 & ATOT. Here ABC1 & ABC2 are manual conditions and my requirement is third condition value should be the sum of these 2 condition values. I have configured as below.
STEP---- CONDITIONFROM-TO-----Ex:
100 -
ABC1--000000----
1000
110 -
ABC2--000000----
500
120 -
ATOT--100110----
500
But system showing value of ATOT as blank and in analysis it is displaying as "condition found without any records".
please add your inputs where I might done wrong.
thanx,
Anup

kindly explain, why you need to maintain condition type ATOT, you can have subtotal for this
You condition type ATOT is might be having the access seq assgined to it and may be that is searching for condition record
Kindly let us know is there any requirment type is assgined to ATOT condition type in pricing procedure???
also if you don't miantain the ATOT in PP and still needs to calclate sum of ABC1 and ABC2 then you can do as below
STEP---- CONDITION -- description   FROM-TO-----Ex:
100 -
ABC1                                   000000----
1000
110 -
ABC2                                   000000----
500
120 -
                          XYZA--100110----
500
maintain subtotal as 2 step 120
i think this will work

How to find pricing procedure based on condition type

Hi,
Please tell me any one " how to find the pricing procedure based on condition type " is there any tables.
Thanks

check table - T683S, where you get all prciing procedures for which has same condition type.
go to se16
give table - T683S
in condition type feild, menation your condition type and execute, you get all procedures with condition type.

Diff betwn Manual field in Pricing Proc(V/08) and in Condition type Screen

Hi,
Can anyone please help me in knowing what is the difference between "Manual" field maintained in Pricing Procedure(V/08) and "Manual" field maintained in V/06.
Thanks in advance.
Regards,
Rianka.

Hi,
Let me explain with some cases.
Case 1: I need a pricing condition type to get the value from condition records and at the same time user can be able to modify it
Keep manual indicator in V/06. There is no need to keep manual indicator at V/08.
Case 2: I'm having a manual header condition type for which user will enter the value at document
Keep it as manual in both the places.
Case 3: I'm getting a value from EDI such as customer expected price which should not be edited inside the conditions.
Keep it as manual in V/08 and restrict manual entry through V/06.
You dont need to keep access sequence for condition types which are marked as manual in V/08. It should get value either using routines in Altcalc type or manual entry inside the document by user. And all the header conditions are set as manual in V/08. Hope now it clarifies.
Regards,
P Gomatheeswaran.

Pricing - Manual Condition Type with value = 0

Hi gurus,
I need to insert a manual condition type with value = 0 into the billing data set.
I realize that if its valiue is 0 it is not active.
Anyone knows how to make it active despite its value = 0?
Thank you.

Dear Customer,
if you have customized the condition as price then the condition will be inactive if the condition is set to zero.
This is calling in:
LV61AA55
inactivate prices with rate / condition value zero
      if xkomv-koaid eq 'B' and xkomv-kbetr eq 0 and komp-kposn ne 0 and
         xkomv-kgrpe eq ' ' and xkomv-kinak ca ' Y' and xkomv-kwert eq 0
         and xkomv-kntyp ne 'e' and komp-fareg na '45'.
        xkomv-kinak = 'X'.
      endif.
If you need an active condition with value zero, then the condition class should not be 'B' (price)
I hope that the information are helpful.
regards
Claudia

Manual Condition Type should be visible in Sales order by default

Hi
How to maintain manual condition types in Sales orders by default. They will be maintaining the value based on the discussion they had with the customer(Negotiated price). The condition type should be visible in the procedure and they will only enter the value.(The method of keying condition type manually is not accepted by the client).
Thanks in advance.
Regards
Vamsi Javaji.

Hi,
In the PRICING PROCEDURE V/08 maintain the CONDITION TYPE as Mandatory
In the CONDITION TYPE V/06 maintain the field MANUAL ENTRIES as C which is Manual entry has a priority.
And check the box VALUE
Now maintain the condition records for the condition type in VK11 with 0 value
Now while processing the sales order the CONDITION TYPE will trigger from the CONDITION RECORDS with 0 value and this can be in EDITABLE mode ( and maintain the value)because of the check box VALUE you flagged in V/06.
Please try this and revert back if you need further details
thanks,
santosh

How to configuration of pricing procedure based on the Region

Hi,
please help me how to configuration of pricing procedure based on the Region in the roll out project.
Thanks
mustafa

What I proposed to do was,
a. Create routes like 0 day route, 1 Day route, 2 day route etc.
b. Route determination is based on the Shipping condition of the customer. Put in the shipping condition for the customer as 00 - immediate delivery. 01 - By Truck, 02 - By Rail, 03 - Ship etc
c. Now, put in your route determination in such a way that routes change in the sales order with shipping condition (SC). Like, if the shipping condition is set to 00, then 0 day route comes up. Meaning immediate delivery, if SC is 01, then your normal route by truck picks up. etc.
When the sales order is manually created, you know the time of creation. As route is one of the criteria, the material confirmation happens based on number of days you put in the route to reach the destination. Now that you have the material available for today's delivery, the delivery program can be run to create it, or it can be manually created.
Now, when you configure the route you have to specify 'Transit duration in calendar days'.
When you have the sales order created electronically (say thru EDI), then, you may have to ask them to send in shipping condition. Else, you have to modify the function module Idoc_input_orders in such a way that if the sales order creation time is < 12 PM, then put shipping condition as 00, else copy what ever is there in the customer.
If you do not want to check the time manually when the user creates the sales order, then you may have to use the user exit MV45AFZZ (and I think you can use Save_order_prepare) to check the time and change the shipping condition. By this you will avoid extra coding in Idoc_input_orders and also need not bother if the user changed the route or not.
Hope my explanation helps.
Regards,
Mukund S

Net Value in Sales order is not picking up for manual conditions.

Dear Gurus,
I created a new pricing procedure for a sales document, where 2 manual conditions will given in sales order.
But after giving manual conditions, the system is only taking one condition value as net value.
I given Base value description and the step numbers of two manual conditions for Addition.
Please help me I want total of two manual conditions into Net value.

Hi Mahendar ,
Could you please share the solution if your issue has been resolved . Even we are facing the same issue . It would be of a great help
thanks and regards
Kish

To Restrict Duplicate & Without Value Manual Condition Type in ME21N

Hi Friends,
While making a stock transfer (purchase order) by ME21N from supplying plant (Factory) to other plant (depot), if user make mistake & donu2019t put value for Manual condition type ZMRP, system accept & save the order.
Afterwards when he realizes the same or immediately come to know about not putting value & put again, system take that second line entry also & create double entry.
When invoice come then it pick the value from first line & show in negative.
How it is possible to restrict it at order level only to not to allow 0 value & repeat entry for the same condition type?
I have triedu2026.
1. At pricing procedure, there ZMRP is required entry.
2. Condition Type - ZMRP, there is _ No Limitations
We can not put D Not possible to process manually or fix this condition type as then we have to maintain condition record & prices are varies depot to depot & day by day.
3. Since this is a Header Condition, so canu2019t restrict at Access Sequence level.
This is only has to put manually by user according to the instruction of sales department.
Got Suggestion to change at user exit level to put check at delivery to not to allow printing or invoicing by putting 0 value/without any value.
Please suggest at configuration level only as itu2019s difficult to create User Exit for all requirement.
Srivastav
+91-9694096833

Hi,
You must update the forum how did you solved the issue as it will help others also in future.
This is good practice.
Regards
Sanjay

Manual condition types need to be reapplied after material change

HI Team,
For some of order items user enters manually condition type through VA02 for availing discount for the order item,
I am having a custom program for updation of sales orders, Through which we can change the order materials.
Order 123 having item material ABC. For which he entered manual condition type ZXYX.
now using custome program he wants to change the mateial ABC to XYZ. Thorugh custom progam material is updated. Price has been recalculted.
But customer wants condition type ZXYX also need to apply for the XYZ material.
Please guide me how to proced.
Regards.

Hi,
Ask your ABAP consultant to check program MV45AFZZ.
Here in item pricing update i.e
FORM USEREXIT_PRICING_PREPARE_TKOMP *
write PERFORM preisfindung_gesamt(sapmv45a) USING charc.
where charc is 'C' (copy manual pricing elements & redetermine others) or you may also use 'G'(Copy pricing elements unchanged and redetermine taxes.)
This surely works.
Regards,
Amit

Adding manual condition types to a service contract

Hi,
I need to add a manual condition type and price value at billplan line item level in a service contract. Could anyone please let me know any way of adding it after the service contract has already been created?

Hi,
You need to first create the Condition type which can take manual entries or the manual entries are prefered.
Then add the Condition type to the pricing procedure being determined in service contract.
Once done when you go to edit mode in conditions tab you shoudl be able to add the above condition types.
Regards,
Tanu

Pricing Simulation based in a Manual Condition

Similar Messages

Maybe you are looking for