Value Contract-Milestone Billing

Hi Friends,
I want to know about the value contracts with milestone billing.
How we use milestone billing in value contracts.
with regards
Azeez.Mohd

Hi Azeez,
Please go thru following thread.
[Milestone billing|https://forums.sdn.sap.com/click.jspa?searchID=21566193&messageID=4014303]
regards,
Abhee.

Similar Messages

  • Billing value in milestone billing exceeds net value.

    Dear all Sap Gurus,
                            I have a situation where in my Sales Order i booked 10 quantities for an item with item category Tao,with each having value of Rs 1000. So net value for the item is Rs 10000. Now in billing plan my client bills on value basis. an bills for 5 times.1st time billed for 3000,next time 4000,then 2000,then 3000,then 5000. Now the billing value for the item is 17000.My net value is Rs10000 and my billing value is 17000.this should not happen the billing value should not exceed net value.i am stuck with this concern.i require this on priority basis as reports will show this entry.looking forward to your help.

    Hi,
    I think, in milestone billing, value of TAO item is immaterial(as long as it is non-zero). Whatever value you have in the billing plan would get billed. So I dont see any issue in your case.
    Regards,
    Sridhar

  • Milestone Billing, Billing date value exceeds Net Value

    Hi all,
    I have a issue related to Milestone Billing. Here billing dates are entered manually. Say for eg for Rs.1000, 4 billing dates will be entered for 25% based on completion of a project.
    Now the problem here is , The net value will be 1000 [contract amount] but system is allowing to enter more than Rs.1000 in milestone billing dates. means i can enter more than 100%. how to restrict this. Do we need to use any user exit.? I have tried all standard ways.
    Thanks & Regards
    Praveen

    Dear Praveen,
    You can put a logic to compare the Total Value and also the individual milestone amount and trigger a error message while saving the sales order.
    This seems the only way.
    However lets wait for the experts to comment on this requirement.
    Thanks & Regards,
    Hegal K Charles

  • Reg Milestome Billing in Value contracts

    hi,
    I have created a Value contract and had used milestone billing plan and assortment module.
    Problem
    i have create a release value contract (release order)  with ref to the Value contract and done billing and also cleared the accounting.
    But in the Value contract, status for the each milestone in the billing plan is always in A (Not yet processed) even after clearing of accounting.
    Regards
    Sivaraman

    The only option i can think of is you have to check copy control settings for your contract order type and billing type and see if update document flow button is checked.
    Or you have to detailed analysis in configuration to point out the problem.
    Basically everything is working but only status is not getting updated. Something is wrong as document flow is not getting updated.

  • Hi  When i create the downpayment process in the invoice i get amount as value but my requirement is in percentage even after i select the percentage basis milestone billing please help what can be done

    Hi  When i create the downpayment process in the invoice i get amount as value but my requirement is in percentage even after i select the percentage basis milestone billing please help what can be done

    downpayment percentage , so if i want 50 percent of order value to be paid  and when i go to faz type the invoice is created for 0 value that 50 percent of the amount is not getting calculated , where as when i enter in order same as 50 percent in amount it gets calculated in invoice, any help ?

  • Billing Request in Value Contract Document Type

    Dear Friends
    In Value Contract Document Type WK1 in [VOV8] Billing Request is IRC:- Debit Memo Request for Contract
    What is the use of it how i will see it is effect in standard business process
    Regards
    Arun

    The billing request is your call off sales document for the value contract e.g. USD 2,000 contract for which initially only USD 500 is billed, thus the debit memo request. The process applies to a situtaion where there is/are partial or staggered releases of contracted goods or services.

  • Error while creating Credit Memo Request for Milestone billing invoice

    Hi All,
    I have a scenario where i have Milestone billing(% based) at header level in Contracts. I create Invoice for that and then try to create Credit Memo Request with reference to the Invoice.
    Problem comes when we try to change the qty in the credit memo request. we are able to change the qty but the value is not changing. It remains the same constant value of that milestone.
    In my copy control from Invoice to Credit memo request for the item category i have maintained the pricing type as "C" because i want to copy and manual conditions.
    So kindly let me know which config setting should be done so that whenever i change the qty the value should also be changed.
    Please Note : This is happening only when my billing plan is at header level. For Billing plan at Item level its working fine.....
    Thanks.....

    Hiiii.....
    Can anyone please advise on the below issue of mine.....
    Thanks alot for the help.......in advance

  • Milestone Billing  for third party order process

    hai Gurus
                 Pls help me in understanding of milestone billing with example.
                 Is it possible to link the milestone billing for Thirdparty order process?
                 pls send me documents to my Id [email protected]
    I will reward points for the helpfull answers
    Regards
    SaravananS
    Message was edited by:
            Saravanan Sevuga perumal

    Hello Saravanan,
    Milestone billing means distributing the total amount to be billed over multiple billing
    dates in the billing plan.
    As each milestone is successfully reached, the customer is billed either a percentage of
    the entire project cost or simply a pre-defined amount.
    During sales order processing, the system determines from the item category whether a
    billing plan is required and, if so, which type of plan
    The type of billing plan that is determined at this point is set up in Customizing and
    cannot be changed in the sales document.
    Billing plans for periodic billing and milestone billing plans for project-related milestone
    billing have different overview screens so that you can enter data relevant to your
    processing.
    For example, for milestone billing, you must be able to enter data to identify the
    individual milestones.
    IMG configuration requires :-
    1.  Maintain billing plan types for milestone billing in OVBO.
    2.  Define date description in SM30 - V_TVTB.
    3.  Maintain Date Category for Billing Plan Type IN OVBJ.
    4.  Allocate date category in SM30 - V_TFPLA_TY.
    5.  Maintain date proposal for Billing Plan Type in OVBM.
    6.  Assign Billing Plan Type to Sales Documents Type in OVBP.
    7.  Assign Billing Plan Type to Item Categories in OVBR.
    8.  Define rules for determining the date in OVBS.
    Milestone billing is typically used for billing projects, such as plant engineering and
    construction projects. Such projects often include a series of milestones that mark the
    completion of different stages of the work. In the SAP R/3 System, milestones are defined
    in a network along with planned and actual dates for the completion of work. The milestones
    are also assigned to the billing dates in the billing plan.
    Each milestone-related billing date is blocked for processing until the Project System
    confirms that the milestone is completed.
    Delivery-relevant order items for which a milestone billing plan applies are billed on the
    basis of the requested delivery quantity and not on the total of the confirmed quantities.
    The connection between the project and the sales document item is made in the individual
    schedule lines of the item. Each schedule item can be assigned to a network in a project.
    To display the project-related data for a schedule line, proceed as follows:
    In one of the overview screens of the sales document, select
    1.  Item -> Schedule lines.
    2.  Mark the schedule line and select Procurement details.
    The following figure shows an example of milestone billing where only the Contract have
    been billed :
    Order  Item  Turbine    100,000
    Billing Plan
    Billing date Description    %  Value  Billing Block   Milestone   Billing Status
    01-10-94     Contract      10  10,000      -             x           x 
    01-03-95     Assembly      30  30,000      x             x          
    01-04-95     Maintenance   30  30,000      x             x
    01-05-95     Acceptance    30  30,000      x             x
    01-06-95     Final invoice ..    ..        x
    Network/Activities
    Milestone    Estimate      Actual
    Assembly     01-03-95      01-03-95
    Maintenance  01-04-95     
    Acceptance   01-05-95
    For each billing date in a milestone billing plan, you can specify whether the billing
    date is:
    1.  fixed
    2.  always updated with the actual date of the milestone
    3.  updated with the actual date of the milestone, if the date is earlier than the
        planned billing date for the date
    <b>**REWARD IF THIS HELPS**</b>
    Regards
    AK

  • Milestone Billing Plan issue

    Hi all,
    I have a scenario of project sales. The billing will be order based - 50% after order confirmation, 40% after delivery & 10% after installation & testing.
    I am using milestone billing plan for my project sales. I am not using the project system. I have created the billing plan in the following way:
    1. Define billing plan types. I have copied from standard billing plan 01 & saved as Z type.
    2. Define date descriptions. I have created 3 different date descriptions - a) Order confirmed, b) Delivery done, c) Installation & testing done.
    3. Define & assign date categories. I created 3 different entries. First for the down payment at the time of order confirmation........i used the date description as down payment. The billing rule selected was "Down payment in milestone billing on percentage basis". The fixed date selected was "Fixed date, date not copied from milestone". The billing block selected was "calculation missing". The billing type selected was "FAZ".
    For the second part (40% after delivery) I used the date description as delivery done. The billing rule selected was "Milestone billing on a percentage basis". The fixed date selected was "Fixed date, date not copied from milestone". The billing block selected was "calculation missing". The billing type selected was "FV".
    For the third part (10% after installation) I used the date description as installation done. The billing rule selected was "Closing invoice in milestone billing". The fixed date selected was "Fixed date, date not copied from milestone". The billing block selected was "calculation missing". The billing type selected was "FV".
    4. Maintain date proposals. I maintain 3 different dates with an interval of 5 days. For first step i selected the date description as "order confirmation"......billing % as 50%........selected the block......billing relevance as down payment on % basis.........payment term..........billing type as FAZ.
    For second step i sselected the date description as "delivery done".......billing % as 40%........selected the block........billing relevance as "Milestone billing on a percentage basis".......payment term........billing type as FV.
    For third step i selected the date description as "installation done"......billing % as 10%.......selected the block..........billing relevance as "Closing invoice in milestone billing".......payment term......billing type as FV.
    5. Assign billing plan types to sales document types....I assigned the billing plan to the sales doucment for project sales.
    6. Assign billing plan types to item categories.....I assigned the billing plan to the item category of the project item....with billing relevance as "I-Order-relevant billing - billing plan".....billing plan as the milestone billing plan.
    Copy controls: I maintained the copy control settings in VTFA.......sales order to billing document type FAZ & FV as well. In the transaction code VOV8 for the sales order document type I maintained the order related billing type as FV.
    Now I created a project sales order.......the system displayed the billing plan tab......the milestones were shown but the data regarding the billing percentage.......payment terms.........billing relevance.....was not shown. I entered all the details......with the document types as
    FAZ
    FV
    FV.
    I removed the block from the first milestone......down payment.
    Now i created an invoice in VF01......selected the order number for reference......the system created 2 invoices.......1 for the down payment request & the other contract invoice. The down payment request had the correct amount but the contract invoice did not display any value.......
    How should i correct the settings so the system will only create the relevant invoice......
    With best regards,
    Niyaz.

    Hi,
    You have done a good job.
    Enter different dates in sales order for each Milestone and assign billing block save the sales order.
    Goto change sales order, remove the block for one billing date.
    In billing screen, enter sales order no. don't press enter
    Click on Selection date (Shift+F7) enter the date range and press enter. you will get only first billing that is 50%.
    Actually we are using PS, milestones and billing dates will be copied from there.
    Regards,
    Chandra

  • Problem with milestone billing.

    Hello Experts,
    I need your precious help on milestone billing.
    When we create the contract system automatically determine Billing plan in sales order
    When I check the order and I found that at header level system does not show Billing value but at item level system shows Billing value while creation of sales order and this is creating the problem we have other Billing Plan type but we don't face such issues.
    User wants system should show billing value at item level and header level as well automatically.
    When this issue came I provide the temporary solution and ask user to set the check box Header Billing Plan check box at item level and once we set this check box than system shows the net value at header level as well shown in below screen shots.
    Once I set the check box Header Billing Plan exist at item level in Billing plan tab then system shows the Billing value/ net value in at Header level as well. as below.
    I have provided  temporary solution but I don't have permanent solution user does not wants to set  check box Header Billing Plan  every time manually.
    User wants, check box Header Billing Plan should be set by default so user no need to do any manual interruption in SO.
    Kindly provide me your valuable inputs.
    Thanks.

    Hello Experts,
    My issue is still pending for solution. Anybody can help me out.
    I want to know the functionality of check box Header Billing Plan which is exist at item level Billing Plan tab (as shown in above pictures).
    One I set this check box then only I can get the Billing value at header level (Billing Plan tab) as shown above.
    Please help me out.
    Thanks,

  • Reg:  User Manual for Value contract

    Hi ALL
    Can anybody send
    usr manual for Material related value contract with milestone billing
    Regards
    Rams

    Hi,
    just mark your question as 'Answered' and give some comments.
    Thanks.

  • Periodic billing and Milestone billing

    Dear SD gurus,
    Can anybody explain what is Periodic billing and Milestone billing?
    If you have the configuration guide for the above, please send the same to my email id : [email protected]
    Thanks in advance
    Regards
    Manivannan R

    Hi,
    Milestone billing means distributing the total amount to be billed over multiple billing
    dates in the billing plan.
    As each milestone is successfully reached, the customer is billed either a percentage of
    the entire project cost or simply a pre-defined amount.
    During sales order processing, the system determines from the item category whether a
    billing plan is required and, if so, which type of plan
    The type of billing plan that is determined at this point is set up in Customizing and
    cannot be changed in the sales document.
    Billing plans for periodic billing and milestone billing plans for project-related milestone
    billing have different overview screens so that you can enter data relevant to your
    processing.
    For example, for milestone billing, you must be able to enter data to identify the
    individual milestones.
    IMG configuration requires :-
    1. Maintain billing plan types for milestone billing in OVBO.
    2. Define date description in SM30 - V_TVTB.
    3. Maintain Date Category for Billing Plan Type IN OVBJ.
    4. Allocate date category in SM30 - V_TFPLA_TY.
    5. Maintain date proposal for Billing Plan Type in OVBM.
    6. Assign Billing Plan Type to Sales Documents Type in OVBP.
    7. Assign Billing Plan Type to Item Categories in OVBR.
    8. Define rules for determining the date in OVBS.
    Milestone billing is typically used for billing projects, such as plant engineering and
    construction projects. Such projects often include a series of milestones that mark the
    completion of different stages of the work. In the SAP R/3 System, milestones are defined
    in a network along with planned and actual dates for the completion of work. The milestones
    are also assigned to the billing dates in the billing plan.
    Each milestone-related billing date is blocked for processing until the Project System
    confirms that the milestone is completed.
    Delivery-relevant order items for which a milestone billing plan applies are billed on the
    basis of the requested delivery quantity and not on the total of the confirmed quantities.
    The connection between the project and the sales document item is made in the individual
    schedule lines of the item. Each schedule item can be assigned to a network in a project.
    To display the project-related data for a schedule line, proceed as follows:
    In one of the overview screens of the sales document, select
    1. Item -> Schedule lines.
    2. Mark the schedule line and select Procurement details.
    The following figure shows an example of milestone billing where only the Contract have
    been billed :
    Order Item Turbine 100,000
    Billing Plan
    Billing date Description % Value Billing Block Milestone Billing Status
    01-10-94 Contract 10 10,000 - x x
    01-03-95 Assembly 30 30,000 x x
    01-04-95 Maintenance 30 30,000 x x
    01-05-95 Acceptance 30 30,000 x x
    01-06-95 Final invoice .. .. x
    Network/Activities
    Milestone Estimate Actual
    Assembly 01-03-95 01-03-95
    Maintenance 01-04-95
    Acceptance 01-05-95
    For each billing date in a milestone billing plan, you can specify whether the billing
    date is:
    1. fixed
    2. always updated with the actual date of the milestone
    3. updated with the actual date of the milestone, if the date is earlier than the
    planned billing date for the date
    reward points if it helps
    Regards
    Govind.

  • Release orders for value contract

    Hi Folks,
    I have question on value contract.
    Customer contract is fullfilled by issuing orders against the contract. When a release order is created for the contract, the system automatically updates the released values in the contract. The release order value is calculated from the total of the open order and delivery values, plus the value that has already been billed to the value contract. System checks this value with "Outline agreement target value" in value contract and issues warning or error message depends on configuration settings in value contract item catagory.
    We have business scenario where system has to check net value of value contract rather than checking "Outline agrrement target value" in value contract. Because we offer some discounts to customer in value contract thus net value of the contract differs from agreement value. So that system will issue error message when release order value exceeds net value of value contract.
    Is there any customizing settings available to meet the requirement?
    Awaiting for your inputs.
    Regards,
    Prabhaharan

    Hi,
    In transcation VTAA at item level have your own cory requirment code which will calcullate net value of the doc, hope this works out
    regards
    sriky

  • Down Payment Processing in Milestone billing

    I have created sales order that does milestone billing. The down payment is 10 % of amount - Billing type FAZ and condition type AZWR is included in Pricing Procedure and ERL is asigned.
    I also have done all the required settings from the help file at:
    http://help.sap.com/saphelp_47x200/helpdata/en/4a/ac853478616434e10000009b38f83b/frameset.htm.
    But the sales order still says G/L account not found and not saving. Is the G/L account need to found at sales order itself ? If so, where in sales oredr type I have to assigne account determination like KOFI00 etc ? Can any explain this ?
    Does the down payment in sales order do the account determination to find G/L account as in case of regeualr billing docs ?

    The following Customizing settings have to be made for down payment processing:
    Settings for the billing plan - To activate the billing plan function, maintain the materials, for which you wish to process down payments, with item category group 0005 (milestone billing). This gives the item type TAO via item type determination. The item type TAO calls up the billing plan function.
    You need to implement the following activities in the billing plan for down payments:
    Maintain deadline category - This determines the billing rule (percentage or value down payment) for the down payment request. The system assigns billing type FAZ (payment request) defined in the standard system with billing category P. (For the billing type FAZ there is the cancellation billing document type FAS in the standard system).
    Maintain the deadline proposal - Use the down payments that are due for the proposed deadlines.
    Maintaining a Pricing Procedure with the Condition Type AZWR:
    In the standard system the condition type AZWR is delivered for the down payment value already provided but which has not yet been calculated. You must include this condition type in the relevant pricing procedure before output tax.
    Enter condition 2 (item with pricing) and the calculation formula 48 (down payment clearing value must not be bigger than the item value) for the condition type AZWR.
    Before the condition AZWR you can create a subtotal with the base value calculation formula 2 (net value). If the condition AZWR is changed manually, you can get information on the original system proposal from the subtotal.
    Maintain the printing indicator - The pricing procedure can not be marked as a transaction-specific pricing procedure (field Spec.proc.) The condition type AZWR has the calculation type B (fixed amount) and the condition category E (down payment request / clearing).
    Maintaining the Billing Document - In the standard system there is the billing type FAZ (down payment request) and the billing type FAS for canceling . The down payment is controlled using the billing category P of the billing type. A billing type becomes a down payment request when the billing category P is assigned. You have to maintain blocking reason 02 (complete confirmation missing) for the billing documents and assign it to billing type FAZ.
    Copying control - Copying requirement 20 must be entered in copying control at item level for the down payment request. In the standard system the order type TA for copying control is set up according to the billing type FAZ for the item category TAO.
    Copying requirement 23 must be entered in copying control at item level for down payment clearing. In the standard system the order type TA for copying control is set up according to the billing type F2 for the item category TAO.
    Financial Accounting settings - A prerequisite for down payment processing is that the account is assigned to the underlying sales document. To do this, change the field status settings in Customizing as follows:
    Set reconciliation accounts (transaction OBXR) - For the `received down payments' and `down payment requests' from
    the G/L accounts you have selected, you should assign the field status definition G031.
    Maintain accounting configuration (transaction OBXB) - For the down payments (posting key ANZ in the standard system) and the output tax clearing (posting key MVA in the standard system), you must maintain the posting key.
    You must also carry out a G/L account number assignment for the tax account.
    Maintain the posting key (transaction OB41) - For posting key 19, set the sales order as an optional field !!!
    Maintain the field status definition (transaction OB14) - For field status variant 0001, field status group G031, set the
    sales order as an optional field !!!
    Assign the company code to the field status variants (transaction OBC5)
    By useing tcode---> VKOA assing the G/L accounts for account deteramination

  • Down Payment processing for Sales orders using Milestone Billing Plan

    Hi,
    The business scenario is as follows.
    The delivery for the sales orders are to be created only after the pre payment( a percentage of the total sales order value) is made by the customer.
    Hence the sales orders while creation are blocked for delivery creation using credit block by means of a userexit.
    The credit manager checks the blocked sales orders using VKM1 transaction and verify if there are any payments made by the customer to cover this pre payment to be made.
    If it is enough to cover then he releases the sales order manually for delivery creation.This is a complex process since there are too many sales orders and the payments made by the customer may not match the amount to be paid(it can be greater or lesser).The customer just pays a huge amount which is to be distributed among the sales orders for pre payments.
    Later, when the invoice is created, the customer account is cleared manually using F-32 transaction for the oldest open invoices.
    Here again there is a huge manual effort involved since he need to distribute the amount against the invoices using oldest open item principle.
    As a solution we are planning to implement "Down Payment processing for Sales orders using Milestone Billing Plan".
    Is this the right solution?
    Can you please give the steps in detail to implement this functionality for above scenario?
    We are using SAP 4.7 version without Project Systems.
    Thanks in advance.
    Regards,
    Ragesh

    Hi Ragesh
    Check the links where you will get the entire down-payment configuration
    [https://forums.sdn.sap.com/post!replydownpayments ]
    Regards
    Srinath

Maybe you are looking for

  • Drop down box question

    Is there a way to allow multiple options to be chosen from a drop down box?  I have the Designer version ES 8.2 that came w/ Acrobat Pro Extended 9.  Thanks.

  • Marketing

    Hi, is it possible to implement sap crm marketing satnd alone...may i know the archetecture of sap crm marketing stand alone and with integration of r/3 thanks

  • More than  2 thousands objects to the contract

    Hi, Is it possible to incluce more than  2 thousands objects to the contract? Does the system handle? Rgds, Stenwa

  • MDIS - Structural Exception

    We are using SAP MDM 5.5. SP6 We are having some issues with our development repository. This repository is not used every day but when we have some testing this is used. While using MDIS and loading the files, some files will to go exception -> Stru

  • How exit for a script having set of pl/sql blocks and sql queries

    HI, I have set of blocks and sql queries in a script. In some cases I want to stop the excution of next statements and blocks. As in pl/sql block We can use return , in case of loop we can use exit, so what is to be use in case if sql script which co