Downpayment Processing as a Document Pricing Condition

Hi There,
Through help.sap.com I was researching new functionality, and found the following documentation on processing Downpayments through pricing conditions.
http://help.sap.com/erp2005_ehp_02/helpdata/en/46/27dcd449fc14dce10000000a155369/content.htm
I can't seem to figure out though where this new functionality comes from. Is this new as part of the enhancement pack, or is this new as part of a support pack?
In particular, it makes note of condition basis formula 48 and condition value formula 49, which are not in our system currently (ECC 6.0, Support Pack 6 - SAPKH60006).
From the documentation:
"Ensure that the condition basis formula 48 and the condition value formula 49 are activated in your system. If not, activate them in transaction VOFM."
Has anyone tried implementing downpayments through pricing conditions yet?
We are already familiar with traditional down payments through Billing Plans on the sales document, but based on new business requirements, we need to look at this other way of processing down payment requests.
Thanks,
Josh

Yes, I am using Calculation type B.
The problem is that the price gets spread/adjusted according to the quantity ordered. For example, if the fixed price is $1.00 and I order 10, then the net price is 10 cents each and that is shown on the item over of the PO.
If I order 100 with a fixed price of $1.00, then the net price is $0.01.
My problem is when the fixed price is $1.00 and I want to order 1000. Then the net price goes to zero and I get an error.

Similar Messages

Pricing Conditions in Invoice

Hello All,
Thank you all for a remarkable support and knowledge you are sharing in this forum. Appreciate you all.
Well here is a situation , when we are processing Invoices - a particular pricing condition we are getting an error. The error is : Pricing condition found but not set". Can any one please suggest what might be the possible problem and how to fix it. This is a Tax condition.
Thanks & Regards
Sai

Hi Sai
This is a very standard error.
THis comes due to the timing difference between the pricing date and the date on which the condition record was maintained.
Consuder the order is created on 10.12.2007 and condition record created on 11.12.2007. Now if u go to the invoice then it will show condition record found but not set. In this case you can do update pricing again. If this doesnt work then you will need the pricing date in invoice or service rendered date in sales order to the date after the condition records maintained and then do repricng.
Hope this helps. Reward accordingly.
Kind Regards
Sandeep

User exit to copy Manual pricing conditions with in sales documents

Hi all,
I have a situation where i have to copy the manual pricing conditions from inquiry to quotation.
Problem: From VA21 when I try to do the same using the tab "create with reference" the document is being copied but the manually set pricing condition in the inquiry is not being copied into quotation. This is because in the copy controls the pricing type is set to 'B' which means "carry out new pricing". I can change it to 'C' or 'D' so that it copies manual pricing but i am not allowed to do so because other sales orgs in the company has a problem if i do so. Only our perticular sales org needs this config. I cannot even create another item catogory specific to this plant because it is against the rules of the company. So I am looking for a user exit in which i can change this pricing type during runtime so that i can plug in some code specific to this sales org to copy manual pricing. I have found one from the SAP note 24832 (MV61AFZA). It doesn't work as i think its obsolte. Can anyone suggest me a better way of solving this issue. Any quick response is appreciated.
Thanks,
Giridhar.

Hi
The following EXITS may help you
Exit Name              Description
SDTRM001            Reschedule schedule lines without a new ATP check
V45A0002            Predefine sold-to party in sales document
V45A0003            Collector for customer function modulpool MV45A
V45A0004            Copy packing proposal
V45E0001            Update the purchase order from the sales order
V45E0002            Data transfer in procurement elements (PRreq., assembly)
V45L0001            SD component supplier processing (customer enhancements)
V45P0001            SD customer function for cross-company code sales
V45S0001            Update sales document from configuration
V45S0003            MRP-relevance for incomplete configuration
V45S0004            Effectivity type in sales order
V45W0001            SD Service Management: Forward Contract Data to Item
V46H0001            SD Customer functions for resource-related billing
V60F0001            SD Billing plan (customer enhancement) diff. to billing plan
V45A0001            Determine alternative materials for product selection
Regards
PRabhu

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

How to control the pricing condition in billing document?

Hello Experts,
Greetings!
We are using two pricing condition.One is PR00 another one is VA00.PR00 is a mandetory condition & prices comes from condition record only.Users are not allowed to enter pr00 manually.
Now we have created one more condition VA00 by which user can increase the price for some particular customers.
Now if the user do enter the condition VA00 in sales order & if it beyound credit limit than system gives informative message & blocks for the delivery.
Now the issue is if they do enter the condition in billing documents instead of sales order system does not check the credit limit at billing level.It allows invoice to be generated even beyond the credit limit.
How can we control this? Is it possible that the condition VA00 can only be used for sales order only.It will not allow to enter at billing time?
Plz suggest how can we resolve this issue in order to control the credit limit.
Any help would be highly appriciated.
Best Rgds
Nitin

Hi,
you can use a surcharge condition type which calculates a percentage over the basic price price that is PR00 in your case.
insert it in the pricing procedure just below the PR00
and remember to maintain FROM & TO step no. of PR00, this condition should be manual entry alllowed
and insert one more condtion type in pricing procedure that will add the values of above 2 condtions .
make above condition type w/o account keys and assign account ker erl to this new condtion type,
STEP NO.     COUNTER     C TYPE     DESCRIPTION     FROM      TO     R     ACCOUNT KEY
8     0     PR00     BASIC PRICE                                           YES
11     0     ZSUR     SURCHARGE     8     8     YES
13     0     ZPR0     Price (Gross)     8     11     YES     ERL
in condition type of ZSUR(surcharge)maintain "c"
REVERT IF HELPFUL
Mohit Singh

Table to link FI document number, line item and pricing condition type

Hi,
I am looking for tables to link the FI document number, line item and PO pricing condition type.
Appreciate any help on this.
Thanks.

For any PO in ME23n in which Goods receipt has happened, you can check in the itemdetails->Po history tab in ME23n.
Here you will find the material document number. Just click on the material document, it will take you to anpther screen here you will find a button for FI document.
Click that button for FI document. In PO history istelf you can see the Condition types.
Hope this helps.

Excise condition types not appearing in the Delivery document pricing

Hi,
This is a scenario of sales from an Exciseable Plant.
The client has pricing requirement at delivery document.
I have configured the pricing at Delivery document, but the Excise condition type (JEXP) does not appear.
We are maintaine ED values at control code level and control code field is not availabe in LIPS, i tried adding the field in LIPS structure but still the ED condition type does not appear as program is not identifying the control code field in delivery.
Can you please let me know the solution for bringing Excise condition type in the Delivery document pricing procedure.
Regards
Venkat

Changed the Condition Category from 'F' to 'L'.

Pricing condition in Billing document (Pricing Date)

Hi Gurus,
I have a sales order which is created on 10.01.2012, the pricing date in the sales order is the same (10.01.2012). The Delivery was created on 22.02.2012 and Actual GI date is also 22.02.2012.
Now when I am creating the billing document, the pricing condition value is showing as '0'. I checked the pricing analysis and found that the validity of the base price condition Z001 was from 10.01.2012 till 14.01.2012 in the sales order.
As the Actual Goods Issue date is taking as the 'Billing date' as well as 'Pricing Date' , the system is not able to find a valid condition type as on 22.02.2012 (GI date). The pricing type in copying control of Delivery to Billing is 'C - Copy manual pricing elements and redetermine the others'.
So I would like to know your opinion on the following.
1) Can I create the billing document using VF01, manually change the pricing date as 10.01.2012 and do the price update using rule C? Will it fetch the price based on the pricing date?
OR
2) Maintain the condition type Z001 for the GI date and do the billing?
Please let me know which is the best way to adopt?
Regards,
SAM

Hello,
If you have necessary authorization to change the Pricing Date in Invoice, please go ahead.
Change the Pricing date in Invoice, go to Conditions tab & update the Pricing. System will fetch Condition Records as on that date.
Hope this helps,
Thanks,
Jignesh Mehta

Function module to get Pricing conditions of billing document

Hi All,
Please help me getting the pricing condition values for a billing document. I got values from KONV table against perticular Condition type. but i need to get the values against step number maintained in Conditions for my billing item. is there any function module to get all condition data maintained in document with totals and discounts aswell.
Please help me. if required i will give tou full details what i required.
Kumar.

Hi Kumar,
Please check below mentioned Function Module for details:
RV_PRICE_PRINT_GET_BUFFER
RV_PRICE_PRINT_GET_MODE
RV_PRICE_PRINT_HEAD (Header)
RV_PRICE_PRINT_HEAD_BUFFER
RV_PRICE_PRINT_ITEM (Item)
RV_PRICE_PRINT_ITEM_BUFFER
RV_PRICE_PRINT_REFRESH
Regards,
Tutun

Create pricing condition with default value in processing process field

hi all,
when i maintain the pricing conditions with vk11 or vk31, i want the price maintained is set default as blocked (the processing status field-KBSTAT). can it be done? i am using 4.6c.

You should try to use transaction variant
<i>Transaction variants simplify transaction flow by:
Inserting default values in fields
Changing the ready for input status of fields
Hiding various screen elements and menu functions, or even entire screens
Adjusting table control settings
When you create a transaction variant, you run through the transaction in a special mode. In this mode, you decide which elements you no longer need in your transaction and which values should be inserted where. If you choose to hide an entire screen, the system will no longer display that screen in the transaction and will proceed on to the next screen in the series. You can also adjust table control settings and determine the width of columns and the order in which you want them displayed. In tab strips, you can suppress tabs that you no longer need by setting them to invisible.
You may also create as many variants for a transaction as you desire. One of these variants can be defined as a standard variant. This variant is then valid across all clients. You may also assign different variants to specific users.
This is done using Variant Transactions. Variant transactions are then places in those users user menus instead of the standard transaction. </i>
To use this : Tools -> Accelerated SAP -> Personalization (transaction SHD0)
Regards

Billing Document Error - Mandatory pricing Condition Missing

Dear Gurus,
We created a sales order for job work for service material and it asked the pricing condition job work price (ZJOP), so pricing condition maintained, in VF01 error is coming Mandatory pricing condition missing (ZBPR).
Regards,
Vasant

Hi,
First check the sales order is complete.Click on incompletion log.If its complete then try the following
To check the settings for billing type T code is VOFA. Here you can check the document pricing proc only. If its is showing fine
in sales order and not billing then check your copy control T code VTFL. Check what is the pricing type for item category.
Edited by: scm.sd on May 9, 2011 1:45 PM
Edited by: scm.sd on May 9, 2011 1:50 PM

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.

Invoice List: Missing Pricing Condition

Hi,
We are trying to implement invoice list because of the different sold-to party but same payer requirement. we have configured all the requirements listed
Prerequisites
You can only process invoice lists if the following prerequisite data is defined by your system administrator in Customizing for Sales:
    Condition type RL00 (factoring discount) must be maintained and, if required, also the condition type MW15.
    An invoice list type must be assigned to each billing type that you want to process in invoice lists. The standard version of the SAP R/3 System includes two types of invoice lists: LR for invoices and debit memos, LG for credit memos.
    Copying requirements must be defined (for example, the payer, terms of payment and other fields that must be identical in the documents to be included in the invoice list)
In addition, before you process an invoice list, you must maintain the following master data:
    A customer calendar must be defined, specifying the time intervals or dates on which invoice lists are to be processed.
    The customer calendar must be entered in the Billing Sales Area view of the customer master record.
    Pricing condition records for the condition type RL00 and, if necessary, (e.g. in Germany) the condition type MW15 must be maintained.
    Output condition records for condition types LR00 and RD01 must be created.
It successfully creates the invoice list now with net value, but, the pricing condition is missing.
What might have been the problem?
Thanks in advance for your help...

Hi,
Have you maintained the pricing condition record for RL00? Also can you please explain what have you maintained in copy control? If possible, please share the screenshot.
Thanks,
Jaydip

Pricing conditions EK01 and PR00 in pricing procedure

Hi Gurus,
We have a process in which a SD billing request is generated by using DIP profile (DP90). Pricing condition used in the pricing procedure for the sales document is EK01 (which brings the actual cost of the service order that creates the Billing request through DP90) but it happens sometimes that EK01 is not desired but instead PR00 ( another price agreed with a certain client instead of the actual cost in the order).
In order to match this need, best would be to combine both conditions (EK01 and PR00) in the same pricing procedure, and as a general rule, EK01 will apply in the billing request price, but in case PR00 condition exists, then this one will prevail and EK01 will be in the price conditions but will not be taken into account in the price calculation--> how can this be done in the pricing procedure?
Another possibility would be using different pricing procedures so that one has EK01 as pricing condition and the other one has PR00. The pricing procedure will be assigned by using document pricing procedure assigned to a different document type but this is not the desired solution as it makes much more tricky the design: another dynamic item profile would be needed so that proper document type is assigned.
Thanks for your great help in advanced!
VL

Hi Victor,
You can put both of the conditions in the same pricing procedure and use the exclusion group to compare the conditions and choose the favourable as per you requirement.
I hope this will certainly help you in solving your problwm.
Regards,
VB

Pricing Conditions Rounding Issue

Currently, our system has two pricing condition types. ZP,ZD. The ZP conditions represent a base price and the ZD represent a differential(- discount or + surcharge). Both are based on the same hierarchy. ZP00,ZP01,ZP02.ZP03,ZP04. A ZP01 overrides a ZP00 and ZP03 overrides ZP00, ZP01,ZP02 and so on and so forth. All transactions are settled in USD. However, most of the time the ZP, ZDs are based on prices that extend out more than two decimal places. I am experiencing and issue because SAP calculates the ZP and ZD separately and is rounding each. For example the ZP or base price in this case is $2.245. This times quantity of 3,999Gal = $8,977.755. SAP rounds this to $8,977.76. SAP then calcs. the differential ZD $.0235X3,999Gal = $93.9765. SAP rounds to $93.98. This is a total price of $8,977.76+$93.98 =$9,071.74. However the unit price is ZP $2.245 + ZD $0.0235 = $2.2685. If you take this price multiplied by the quantity $2.2685 X 3,999Gal = $9,071.7315. So the actual total price is off by 1ct because SAP treats the ZP and ZD as two separate calculations. I have seen various ideas on how to fix, from creating another pricing condition, to user exits. I was wondering if there was a preferred method? Or if there is a simpler solution?

Good Evening,
1. Please review OSS NOTE 80183 regarding Rounding.
   Values calculated in pricing are always rounded to the amount of
   decimal places which the used document currency owns. As subsequent
   processing steps setup on this rounded value rounding differences can
   occur in the calculation of the price per unit or in subtotal line.
   To bypass such effects note 80183 describes possible solutions to
   reduce / bypass this effect.
   A few problems in rounding after applying note 80183, variant 2 have
   been recorded where it was recommended to use the formulas 919 and
   920 on all discounts and surcharges that appear before NETP and the
   problem was solved.
2. In transaction V/06 there is a field under header 'Control data1'
   which can effect how the system rounds off condition values during
   pricing:
   ->> Rounding rule
       The rule that determines how the system rounds off condition
       values during pricing. The last digit will be rounded.
Example
o In the standard rounding rule '_', values are rounded off according
   to business standards:
   10.454 -> 10.45 DEM
   10.455 -> 10.46 DEM
o In rounding rule 'A', values are always rounded up:
   10.459 -> 10.46 DEM
   10.451 -> 10.46 DEM
o In rounding rule 'B', values are always rounded down:
   1045.9 -> 1045 LIT
   1045.1 -> 1045 LIT
   In this example, the currency of the condition rate is Italian Lira.
   The Italian Lira does not have any places after the point.
3. Also check if the condition type is set as item condition as well
   as group condition in transaction V/06. What this means is that
   the system will calculate the value of the condition on header level
   and compares it with the sum of item values in the document.
   Any rounding difference (KONV-KDIFF) detected, will be populated
   in the line item with greatest value or in first line item if all are
   of equal value.
   In other cases where there is no adjustment because there is no
   rounding difference when comparing the header value and the sum of
   item values.
   ->> Solution to this scenario -
       If you remove the 'group condition' setting, the system will then
       calculate amount for the items directly and you will not get the
       rounding. You must decide which setting is more suited for your
       business. This is not a bug, but works as per designed.
       EXAMPLE: MWST - tax condition (a group condition)
                Item 10     16%   of 100.90 = 16.14
                Item 20     16%   of 100.90 = 16.14
                                       Total = 32.28
I hope this helps you!
Kind Regards,
Martina McElwain
SD Forum Moderator

Downpayment Processing as a Document Pricing Condition

Similar Messages

Maybe you are looking for