Reset a pricing condition type value when generating billing document

Hi experts,
I have a delivery-related billing type. In sales order, there is a pricing condition type Z001, with value = 100, I would like to reset it to zero when generating billing document. Is there any configuration or user exits can do this? Thanks.

Hello,
You can do this in BILLING provided , if the Condition type is Manual condition type
To achieve this you have to do some configuration in the condition types as,
Goto transaction code V/06 and select your condition type and maintain the MNAUAL ENTRIES as C which means you can process it manually and in the V/08 chose your pricing procedure and against your condition type check the Manal entry .
Now you can change the value of the condittion type to 0 in the Billing document.
Hope this is clear,
regards,
santosh

Similar Messages

Pricing : Condition type value need tog get from the lowest of 4 other cond

Hi,
I have one requirement in one pricing procedure.
I need to calculate condition value of one condition type from the lowest value of other 4 condition tyeps. These condition types values are not defined as a subtotal.
So if I decide to write a formula on condition values, is there
any way to select these values and choose the lowest of them?
Please also advice if there is any other way such as condition exclusion
or so?
Thanks and regards,
Anand

Anand,
As you have mentioned you can use condition exclusion for such a requirement.
here is a detailed description of how you can achieve this: use the menu path IMG> Sales & Distribution> Basic Functions> Pricing> Condition Exclusion> Condition exclusion for group of conditions.
When you execute this IMG acitivity you get a window with three options
1.Define Condition Exclusion Groups
2.Assign condition types to the exclusion groups
3.Maintain condition exclusion for pricing procedures
We will use these three options one by one, we start with the first
1. Define an exclusion group, lets say EX01 and give a description
2 Assign the four condition types that you want to compare to this exclusion group under this option
   lets say EX01 ZK01
               EX01 ZK02
               EX01 ZK03
               EX01 Zk04
3. under this third step, select the pricing procedure that you are working on and from the left margin click on 'Exclusion'. click on 'New Entries' and make the following entries (example)
         Sno.   Cpr         ExGr1
          10      A            EX01                leave ExGr2 blank, Save your entries
Check if your purpose has been met or not. Do give your feedback
Regards,
PATHIK

MM Pricing Condition Type values in Condition Tab updation while CHANGE PO.

Hi,
The process of PO creation and PO change is through inbound IDOC posting.
I created a PO with configured MM pricing procedure.
While creating PO, the PO is created as required with different Condition Type value break-ups [PBXX, Discount, Surcharge etc] in the PO as required via Inbound IDOC processing.
While CHANGING the same PO, the Condition Type break-ups [i.e. pricing related values] in the PO are NOT changing in the PO via Inbound IDOC processing.
What needs to be done to update the Condition Type break-ups in the PO while changing PO through IDOC processing process?
This problem is not occured while manual / on-line changing of PO valueS and saving the PO & exists through IDOC processing method ONLY.
Thanks in Adv,
RK

Hi
Try this function module
FM RV_CHECK_CONDITION_VALUE
Regards
Hareesh Menon

Condition type not visible in billing document

Hi
We are currently in the process of making some changes to the pricing procedures.
While processing an IC order, we find the following discrepancies,
In VA03, when we enter the order details, the price shows the expected value and so do the condition details.
However, in the billing document for the same, in VF03, we find that one of the condition types are missing, hence the value in the sales document and the billing document are different.
I have checked the details in the condition types, pricing procedures and the access sequences, everything appears to be configured correctly.
Please advice as to how this can be corrected.
Thanks
sap10

Hi
Check in pricing procedure (tcode V/08) if you have any Reqt.
Other possibility, but I think that it doesn't matter in your case. See SAP Note 105621 - Authorization check for the condition screen, that it is used to hide conditions, but not for delete them.
I hope this helps you
Regards
Eduardo

Scrap Sales-VAT Condition Type Not Copying into Billing Document.

Dear All
I am facing problem while billing a scrap sales order.
1. Even though condition record has been maintained for JIVP, the condition is not picked automatically.
2. I enter it manually and save the document and later do delivery and billing; in billing, if I go to Conditions Tab, I do not see VAT condition copied into the document.
Naturally, when I am doing analysis, only PR00 condition type is showing.
Kindly require your suggestion as to where I might have gone wrong.
Thanks and Regards
Adithya

Prasanna,
It is fine to press Release to Accounting button, but the issue has not yet been identified to fix and then Release to Accounting.
When I go to document flow and check the accounting documents in Goods Issue Document, Accounting document has not been created only, only Profit Centre and Controlling Documents are created. Am looking on the same y it has happened like this.
Thanks and Regards
Adithya

Exit/BADI for condition type value

Hi friends,
    I have a BADI BADI_SD_BILLING_ITEM. I want to enhance method 'ITEM_PRICING_COM' present in this BADI.
    My purpose of using this BADI is that I want to get the values of condition type before saving a billing document.For that purpose I want to enhance this BADI.
But I don't know how to proceed.
   Please help me out.
Regards,
Rajesh

Enhancement
V61A0001                                Customer enhancement: Pricing
V60P0001                                Data provision for additional fields for display in lists
SDVFX011                                Userexit for the komkcv- and kompcv-structures     "This may be usefull

Condition type field when Define Pricing Procedure Determination

Hello Gurus,
there is a condition type field when Define Pricing Procedure Determination. what does it mean ?
Many thanks,
Frank Zhang

Here is are the details of various fields while configuring pricing procedure.
A. STEP
This indicates the number of step-in the procedure.
B. COUNTER
This is used to show a second ministep
C. CONDITION TYPE
This is the most important component in the pricing procedure. The rates are picked up from this element, on the basis of the properties described.
D. DESCRIPTION
This forms the description of the condition type.
E. FROM
This is used to define the progression of the calculation and range of subtotals
F. TO
This is used to define the progression of the calculation and range of subtotals
G. MANUAL
This function enables to allow the condition type to be entered manually also apart from automatic pickup.
H. MANDATORY
This function identifies the conditions that are mandatory in the pricing procedure. The sales price is a mandatory condition type.
I. STATISTICS
This can be used to represent the cost price of the material sold, generally used for study statistical impacts of price
J. PRINT
The activation of this function will enable the printing of the values and conditions to the document.
K. SUBTOTAL
A key is assigned from the drop down menu; this can be used by the system in other area like Sis for reporting purpose also
L. REQUIRMENT KEY
This function is used to assign a requirement to the condition type. This requirement can be used to exclude the system from accessing the condition type and trying to determine the value. This can be used to specify that the condition type should only be accessed if the customer has a low risk credit.
M. ALTERNATE CALCULATION TYPE
This function allows you use a formula as an alternative in finding the value of the condition type, instead of standard condition technique. this can be used to calculate complex tax structures.
N. ALTERNATE CONDITION BASE VALUE.
The 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.
O. ACCOUNTS KEY
The account keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts.
PR00- ERL
K007/KA00- ERS.
KF00- ERFu2026u2026u2026u2026.& so On.
P. ACCRUAL KEY.
The accrual keys form part of account determination. These keys are used here to define the posting of the revenue generated to respective account heads& to subsequent assignment to GL accounts and payment to respective parties.
Kalpesh

Condition type value can not be changed in PO pricing

I have created PO which is having pricing procedure consisting different condition type. When i create any subsequent document (MIGO or MIRO) and realized that condition value in the pricing need to be changed so I have reversed all subsequent document so that can carry out "update pricing".
when i press Update pricing button on the condition tab, its showing message that new pricing can not be carried out. I observed that some condition types of pricing are grayed out.
Kindly help to solve this problem. Kindly help me how to 1) update pricing or 2) can change value of condition type.
answers will be rewarded

Hi shiwanshu
Actually i tried the same and could change after I have reversed all subsequent documents
Since your system does't allow you change and since you have reversed all the subsequent docs why dont you delete the PO item and add a new one with right pricing..
i guess it will solve your problem..
Hope helps
Best Regards
Reward please if found useful

Function module to change the value for pricing condition type

Hello experts,
I want to change the value for pricing condition type for an item in the transaction CRMD_ORDER.
I used many function modules but none are working.
Please kindly suggest a function module that will change the value for a condition type .
I have used the following function module but its not working, please correct the coding if anything needs to be changed or added. Please help me .
Thank you.
CLEAR PRCD_COND.
     SELECT SINGLE * FROM PRCD_COND WHERE KPOSN = WA_ORDERADM_I-GUID AND
                                          KSCHL = COND_TY.
IF SY-SUBRC = 0.
*    MOVE-CORRESPONDING PRCD_COND TO L_COND_CHG.
*    CLEAR L_COND_CHG-KBETR.
    L_COND_CHG-STUNR = PRCD_COND-STUNR.
    L_COND_CHG-KBETR = COND_PRC.
*    L_COND_CHG-KSCHL = COND_TY.
    INSERT L_COND_CHG INTO TABLE T_COND_CHG.
L_HEAD_GUID = CRMD_ORDERADM_H-GUID.
L_ITEM_GUID = WA_ORDERADM_I-GUID.
INSERT L_HEAD_GUID INTO TABLE HEAD_GUID.
INSERT L_ITEM_GUID INTO TABLE ITEM_GUID.
    CALL FUNCTION 'CRM_ORDER_READ'
     EXPORTING
       IT_HEADER_GUID                    = HEAD_GUID
       IT_ITEM_GUID                      = ITEM_GUID
     IMPORTING
       ET_ORDERADM_H                     = LT_ORDERADM_H
       ET_ORDERADM_I                     = LT_ORDERADM_I
       ET_PRIDOC                         = IT_PRIDOC_RD
       ET_DOC_FLOW                       = T_DOC_FLOW
*     CHANGING
*       CV_LOG_HANDLE                     =
*     EXCEPTIONS
*       DOCUMENT_NOT_FOUND                = 1
*       ERROR_OCCURRED                    = 2
*       DOCUMENT_LOCKED                   = 3
*       NO_CHANGE_AUTHORITY               = 4
*       NO_DISPLAY_AUTHORITY              = 5
*       NO_CHANGE_ALLOWED                 = 6
*       OTHERS                            = 7
    IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRI_COND.
INSERT L_PRI_COND INTO TABLE PRI_COND.
LOOP AT IT_PRIDOC_RD INTO LS_PRIDOC_RD.
MOVE-CORRESPONDING LS_PRIDOC_RD TO L_PRIDOC_CHG.
L_PRIDOC_CHG-PRIC_COND = PRI_COND.
L_PRIDOC_CHG-REF_GUID = LS_PRIDOC_RD-GUID.
L_PRIDOC_CHG-COND_CHANGE = T_COND_CHG.
INSERT L_PRIDOC_CHG INTO TABLE PRIDOC_CHG.
ENDLOOP.
LOOP AT LT_ORDERADM_H INTO LS_ORDERADM_H .
MOVE-CORRESPONDING LS_ORDERADM_H TO L_HEADER.
INSERT L_HEADER INTO TABLE HEADER.
ENDLOOP.
LOOP AT LT_ORDERADM_I INTO LS_ORDERADM_I.
MOVE-CORRESPONDING LS_ORDERADM_I TO L_ITEM.
INSERT L_ITEM INTO TABLE ITEM.
ENDLOOP.
L_FIELD-FIELDNAME = 'STUNR'.
INSERT L_FIELD INTO TABLE FIELD.
L_FIELD-FIELDNAME = 'KBETR'.
L_FIELD-CHANGEABLE = 'X'.
INSERT L_FIELD INTO TABLE FIELD.
L_INPUT-FIELD_NAMES = FIELD.
L_INPUT-REF_KIND = 'E'.
L_INPUT-REF_GUID = LS_PRIDOC_RD-GUID.
L_INPUT-OBJECTNAME = 'PRIDOC'.
INSERT L_INPUT INTO TABLE INPUT.
    CALL FUNCTION 'CRM_ORDER_MAINTAIN'
     EXPORTING
       IT_PRIDOC                     = PRIDOC_CHG
     IMPORTING
       ET_EXCEPTION                  = EXCEPT
     CHANGING
       CT_INPUT_FIELDS               = INPUT.
    IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
REFRESH EXCEPT.
CALL FUNCTION 'CRM_ORDER_SAVE'
EXPORTING
    IT_OBJECTS_TO_SAVE         = HEAD_GUID
*   IV_UPDATE_TASK_LOCAL       = FALSE
*   IV_SAVE_FRAME_LOG          = FALSE
*   IV_NO_BDOC_SEND            = FALSE
*   IT_ACTIVE_SWITCH           =
IMPORTING
   ET_SAVED_OBJECTS           = SAVED
   ET_EXCEPTION               = EXCEPT
   ET_OBJECTS_NOT_SAVED       = UNSAVED
* CHANGING
*   CV_LOG_HANDLE              =
* EXCEPTIONS
*   DOCUMENT_NOT_SAVED         = 1
*   OTHERS                     = 2
IF SY-SUBRC <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
COMMIT WORK AND WAIT.

Hi,,
To be able to call a function module in an update work process, you must flag it in the Function Builder. When you create the function module, set the Process Type attribute to Update with immediate start
Alternatively u can use this function module.
CRM_STATUS_DATA_SAVE_DB
BAPI_CUSTOMERCRM_CHANGE (If u wish to use a bapi for this).
Also , Let me know what error you got when implementing other function module.Does the function module didnt return any error but still the value is not changed for pricing condition type?

In Stock trasfer order how to pick pricing condition types

Dear Experts,
I am new to SAP MM my question is In Stock transfer order (plant to plant through purchasing) it is picking PI01 pricing condition types? how it is picking? what are the Accounting doc are updating?

Hi,
Goto the following node SPRO > IMG > Materials management > Purchasing > Conditions > Define Price determination process > Define shcema determiantion
Define schema for transport orders under which you will be able to see RM2000, when you try to open the RM2000 through M/08 transaction code.
You will be able to see the PI01 as the basic price condition type.
Accounting entries
During Goods Issue.
The stock account in the supplying plant gets Credited with the MAP value.
The stock account in the receivving plant gets debited with the MAP value.
If there exists any diffeence then the key AUF will get hitted.
During Goods Receipt.
No accounting doucment gets generated.
Regards,
DilliB

How to change exchange rate type for specific pricing condition type

Hello every one,
I have a requirement for billing ie VF01.
currently all the exchange rate are being calculated with exchange rate type 'M' by default.
but now client want it should calculate exchange rate with type 'E' for two pricing condition type for all others it should calculate with type 'M'
Please any body can help me with the exit and code which i can use.
I have checked exits SDVFX008.
but how to change exchange rate with type 'E' only for two conditions.
as changing exchange rate at document header will change exchange rate for all condition type.

You need to assign KOMK-KURST = 'E', for those two condition types. If it had been item number specific, you could have used USEREXIT_PRICING_PREPARE_TKOMK(RV60AFZZ).
Do one thing, put a breakpoint on FM 'PRICING' and then do selective runtime analysis.
Check whether any user exit/BADI/ explicit enhancement are available when condition types are processed in a loop. If nothing is available, try implicit enhancement.
Link to refer for selective runtime analysis - Runtime Analysis for VOFM
Also try with VOFM requirements ( not sure whether changing KOMK-KURST is permissable in requirement as normally we only set sy-subrc values to suppress/allow condition types ). Don't forget to assign requirements against condition types in pricing procedure.

Pricing Condition Type PR00.

Hi experts,
I have a scenario where condition type PR00 shoul be mandatory in sales order and document should not proceed further unless the basic price is put while creating sales order. Also, system should not allow double entry of PR00.
I have already marked condition type PR00 as manadatory (still document is precceding in absence of any value ) and incompletion procedure log is applied.
Pl guide on same at the earliest.
Regards,
Pallavi

Hi
Check following points :
1. Check for the properties of condition type. It should has BASE PRICE as the property. And Access sequence should have to be there.
2. Mark check for Mandaotory in the Pricing procedure.
3. Check for your calculation. Your Net value should come as zero- if the PR00 is missing.
So when you will process any sales order it will, give you a incompletion log error as net value is zero- or pricing is missing for the item. And also Mandatory condition type PR00 is missing.
Thanks
Rishi

Pricing Condition type triggering based on other condition type

Hello sir,
There are some pricing condition types in our system.
Based on condition records you can trigger one condition type based on other    condition type.
For eg: PR00 condition type is there and amount is suppose 1000rs and other condition type is JBED and we made a condition record and put it some percentage so as soon as we some value in PR00 ,JBED condition type is automatically manipulating the value on the base condition record.
Now i want other than condition record can we trigger one condition type based on other condition type through defining user routine under requirement.
Suppose we have condition type ABC and some amount i have given and other condition type DEF , i want that amount of DEF condition type should automatically come from the Condition type and it should manipulate according to my routine .
eg Condition type    Amount
       ABC                  1000
       DEF                    40
The value 40 should come as 4% of 1000.
I am not maintaing any condition record and i want that this should trigger through some requirement created by me.
i created my routine no 905 and i putted the code inside it.
if komtl-kschl = 'DEF'.
komv-kbetr =   ( komv-kbetr * 4) / 100.
endif.
Now problem is that this code is getting trigger when i m giving value in DEF condition type then it is showing 4 % of it.
But i want as soon as i give value for the condition type ABC and some value 1000
then after pressing enter , one condition type DEF should automatically come with value 40 that too in display mode ,not in change mode.
Please suggestions and solutions regarding this matter , I will be grateful to you.
Manish

hi
In V/06 in the calculation type you can see the entries for "D-gross weight" & "E-net weight"
For the required condition type select the calculation type as gross weight or net weight. Save it.
In MM01 - create material master, here in BASIC DATA 1 SCREEN you have fields for gross weight & net weight.
Maintain the condition record in VK11 for the required condition type.
You can also maintain the scales as required like u said
1 to 10 kgs - 100 rupees,
11 to 25 kgs - 1000 rupees.
Another way could be
The BEST practice to do it is, use of VOFM routine for price calculation (VOFM-->Formulae).
Take help from ABAPer and write a routine such that
if weight = 1 - 10
price = 100.
else if weight > 8.
price = 1000.
else
price = 100.
end if
but the maintainnance of routine is big problem as u might be having many records
Hope this will help you
Vishal

Relation B/W tax and pricing condition types

HI friends
I want to know relation b/w tax and pricing condition types.
Here, i think we are giving relation in pricing procedure, how we are giving that relation, what is that mean.
How sys will carry the values from tax condition types to pricing condition types.
plz give me the details early.
with regards
lakky

Hi...
Actually in priciing procedure it is only sequential arrnagment of COnt type could be price, dicount or tax ... so that system calculates as process given by client.
now when u see tax condition types .. they are also created in FI and also in Sd with same controls and linked via the account key...
Account key MWS, MW3 are created in Fi and only used in Sd but azccount keys like ERL, ERF, ERS are created in Sd and used for account det in VKOA ...
also MWS, MW3 used in VkOA but are used in TAx procedure also and are assigned G/L in Tax code ...
now when u c the pricicng in a Sd doc .. sales order then all totals calculated and net price given and below that a Tax total given ... how system calculates tax totals is that in the tax conditio type in condition category .. we give Taxes as D so that all cond types with this cond catefory gets added and totalled to this tax total figure ..
Reward if helpful
Krishna

Use of conditino category in pricing condition type

Hi,
Can anybody please guide about the exact use of condition category in the pricing condition type. In text it is mentioned that it is used for grouping of similar condition types but what exactly is the requriement for this? Does it have any control function like the feild condition class has( like for example grouping in this is used in redeterminations etc) ?
Please guide about the use of this feild and if maintained or not maintained then how will it matter?

Hi,
It serves some purposes.
1. It is used for the classification of condition types. During implementations, consultants classify the condition types into condition categories (Prices, Discounts, Taxes) and later use these categories to print the value of condition types in the forms. Coding based on condition categories reduces the effort instead of hardcoding on the condition type.
2. They also have some inbuilt property for some of the condition types like VPRS, SKTO etc where the categories are important for the behaviour the condition type, the way they are expected to behave.
3. Some of the condition categories will be applicable only for some specific processes and not for all the processes. for example e during downpayment.
But the complete function of this field can be only learned over a period of time when we implement new functionalities for the business.

Reset a pricing condition type value when generating billing document

Similar Messages

Maybe you are looking for