![]() The problem with above approach is the KPEIN is only a 5 digit integer, limiting the Quantity on the item to a maximum 99,999 units. = ZNSV Condition Value (without rounding issue) = ( ZNSV Condition Value * Quantity ) / Quantity = ( Condition Rate (KBETR) * Condition Base (Quantity = KAWRT) ) / Condition rate unit (KPEIN) To overcome the limitation, we are assigning ZNSV Condition value (XKOMV-KWERT) directly to Condition rate XKOMV-KBETR and assigning the Quantity value to Condition rate unit (XKOMV-KPEIN). This causes the parent price in ZNSV not to match the Billing child price ZCPY, because of loss during rounding of Condtion rate XKOMV-KBETR. This will of course cause rounding issues, as the condition rate field XKOMV-KBETR has only two decimal places. So what was done earlier, is to divide the parent ZNSV value by Quantity on the item and assign it to Condition rate (XKOMV-KBETR). However, we can only set Condition rate (XKMOV-KBETR) and Condition base (XKWERT = XKOMV-KAWRT) in Condition Base Value formula. So the only way left to copy the value from parent condition ZNSV to child condition ZCPY is to use Condition Base Value formula. This is of course incorrect as we want the Billing plan row value to be equal to be ZCPY monthly value, if the Billing plan type is set to Monthly, multiplied by 3 times ZCPY monthly value if the Billing plan type is set to Quarterly etc. The problem is that, if we use Condition Value formula to copy the value from parent condition ZNSV to ZCPY, then SAP will interpret the ZCPY value as absolute value, rather than monthly value, and the same value will apply on Billing Plan rows irrespective of the duration between Settlement From and Settlement To dates being a month, a quarter or a year. So we can't use a Condition type with Calculation type 'C' - Percentage, with 100% rate, which perfectly copies any value. Since ZCPY is used to represent monthly price of the service item, its calculation type is set to 'M' (as doing this only can guarantee that all months irrespective of being 28, 29, 30 or 31) can get the same monthly price irrespective of number of days in them. There is a condition type on the child item, say ZCPY, that copies the condition type value from the parent, say ZNSV (Net Service Value), that represents item final price. On Maintenance Contracts (VA41) in our company we have a design of a parent item (that has pricing on it) and a child item that has the billing plan on it.The Pricing Procedures are designed in such a way, that all pricing conditions on the parent are set to statistical so it doesn't contribute to Net value on the parent item. I already try to use customer service module, and conclude that it is not effective to use it for this business scenario, so i am trying to use the sales order. we only create sales order from contract, if there is a request from the customer to send the spare parts or services to them. The customer pay the contract on monthly basis. The reason that we need to create billing plan from the contract is the customer make a quantity contract for the spare part and services that they required. If we don't create invoice from the sales order, then wouldn't the sales order will be always outstanding? If we create invoice from the sales order, then the customer will be invoiced double? invoice from the contract and invoice from the sales order, Let's say in the contract, I use periodic billing plan in contract, whereas we generate the invoice based on the billing plan in contract.Īlong the journey, we will generate sales order based on the contract.ĭo we need to create invoice from this sales order? I have a problem about billing plan in contract, Currently right now i am stuck at this problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |