Milestone billing is possible eventhough billing status is blocked.

Hi,
The scenario is like: I create a sales order for a configurable material which requires to create sales order BOM. Now when I save the sales order, delivery block status and billing block status are shown as 'blocked'. Its obvious as I haven't yet created sales order BOM and run the costing for the same.
But still I am able to do the milestone billing after removing billing block from the billing plan.
Is it the standard SAP functionality or defect in the system?

Hi
it is standard SAP functionality, based on the sales document type it will happen.
cheers

Similar Messages

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

Billing plan and billing status

Hello Friends,
I would like to clarify if my understanding is correct before I configure a billing plan:
1. Billing status is not seen in billing doc but in preceding doc like a DO.
2. For a Billing Plan, there can be 1 billing plan at item level for a set of settlement dates.
If the plan is defined at header level, only 1 billing plan is for all items.
3. Contract is a sales doc type and contract data is only at header level.
Is this considered an Order-related billing when invoice is printed at each billing date?
Is the contract considered as the reference doc for the billing doc sent to customer? I believe so. please confirm.
4. There is no such thing as master billing plan that item level billing plans need to be linked to.
5. date category : this is at billing date level and cannot be changed?
regards
Pascal

Hello,
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.
Thanks,
venkataswamy.y
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
Comments
the article was great it explained about billng milestone very well

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.

Is it possible to change 'billing status' after making credit memo request?

Hi. This is Kwangkyun Choi from Samsung SDS in Korea as a SD system operator.
Our system can make billing documents from contract without making sales order and outbound delevey.
And the contract can use milstone billing.
When we make billing document using contract,
one of the milestone billing item's 'billing status' has been changed from A (Not yet processed) to C (Completely processed).
And also when we cancel the billing, the status has been changed from C to A.
BUT,
When I make CREDIT MEMO request referenced the billing document,
at that time the 'billing status' doesn't changed.
It was still 'C (Completely processed)'.
I want to change that value 'A'.
Is there any methods to solve this problem?
I couln't find any solution using customising IMG setting.
PLZ help to solve this problem.
Best Regards.
Edited by: Kwang-Kyun Choi on Oct 13, 2009 10:45 AM

Hello,
Let me clear my thought on this issue related to Billing Status of the Billing Docoument. You want to change the billing status of billing document to not yet processed after you have created a credit memo request. If this is the case then my explanation would be as :
when billing document is generated and then Accounting document is also generated, the billing status is fully completed. Nothing is rejected here nor nothing is left over. When you are creating a credit memo request, which is of course created with reference to Billing document then the billing status under no circumstances can change to "not yet processed" as the billing process is completed. Morever you are creating the credit memo request to adjust payment for the cusotmer.
Hope this helps to understand !!
Regards,
Sarthak

WBS assigment for Milestone Billing

Hi,
I am assigning milestones to the activities in my project.
I need a particular WBS to be assigned to only one Sales Order. The system is allowing me to assign the same WBS to another Sales Order also. Therefore copies all the milestones to the new sales order and allows me to do the milestone billing for same WBS again. [Twice]
Is there any way to restrict the same WBS being assigned to several Sales Orders and avoid billing for the same WBS again and again.
Please suggest.
Thanks & Regards,
Kabir

U check with SD consultant as suggested by Mrinal.....It is also possible to restrict the assignment using user status...but this has to be done manually...once the user assign the WBS to sales order, he can select an user status manually which restricts the business transaction "Create Sales document"...this will not allow you to assign WBS to new sales order...but this is manual process.

Milestone Billing in projects--Final Invoice

Hi all,
We are using Milestone billing in the project. Milestone confirmation in projects trigger the downpayment requests, partial invoice and final invoice in SD.
Everything works fine for down payment and partial invoice, but when the milestone for final invoice is confirmed in PS, the billing rule in the sales document item does'nt get removed. Consequently billing cannot take place.
Kindly thow some light on this. Is FNBL status on WBS , a must to carryout final billing ?
Warm regards,
Srinivas Potluri

Hi Srinivas,
Please check the Date Category of Milestone usage, the one u have selected for the final invioce. It should be 'Closing Invoice".
Please let me know if that resolve the issue.
Thanks,
Venkat

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

Milestone billing for non project case

Hi,
I have a building/room that is going to be rented. I need to adopt Down Payment (%) with open date, which means the customer is have flexibility to choose when he/she wants to finish the payment. e.g: for a wedding, today the customer pay DP, let say 30% of total, and he/she will use the building next year and pay the remaining.
I try to explore the proper / suitable solution for this case in SD. I try to use milestone billing plan. I copy as SO doc type OR, copy as item category TOA, copy as billing doc type FAZ and FAS , and use milestone billing plan in item level while creating the SO doc.
My question is, before I continue to use it, I want to know if It is okay to use milestone biiling plan for non project case? and what is the possible effects?
thank you,
Regards,
Harris

Hi all SAP ers...
I want to continue my first question.
1. Right now I am considering, is it the right concept to use millestone billing plan in my case?
2. If I use Milestone Billing Plan for Down Payment Process, which point of view do we use? Is it I am the project owner and then I bill the vendor OR I am the Vendor who sends the invoice to the customer/project owner?
3. Is it "okay", if I use milestone billing plan ? (If the point of view is I am the Vendor who sends the invoice to the customer)
Regards,
Harris

Milestone Billing Structure

Dear PS Experts,
We have real estate projects (Customer projects), and one typical structure is we have a housing complex project of 100 villas. (We are in process of implementing PS but all other SAP modules like FI/CO, MM, SD, PM, PP, QM etc are existing.)
Now after construction or during construction phase itself, these villas need to be sold through SD sales where following selling scenarios exists.
1. Each villa separately sold to individual customer. 1 S/O per Villa.
2. One S/O with multiple villas (Each villa is line item in S/O)
Here while I structure the project, I considered, two structures as follows,
1. 100 Villa project with project definition ABC/20014/PJ01. One main WBS with 100 WBS under that. Each of this WBS represent one villa and S/O will be assigned with this WBS.
2. 100 Villa project with project definition ABC/20014/PJ01. One main WBS with 4-5 WBS under that (1. Engineering & design 2. Land preperation 3. Construction etc..) and each villa is represented as a network & S/O will be assigned to main WBS and each S/O item will be assigned to these corresponding network of 100.
I would like to hear from you the best possible solutions.
Please share your ideas.
Regards,
VINOD.V

Hi Vinod,
I would suggest you to go with one sales order and One Project for each villa
because sales order is specific to one customer ( one sold to and one ship to)
in the Project you can structure one WBS at Header as Billing element and assign below to it subsequent WBS such as (land acquisition, Engineering, design, construction and miscellaneously) and this individual WBS will in turn have networks and activities based on the phase.
Finally post the actual cost to Each of the WBS and settle to Main WBS
Assign this main WBS to each sales order at line item level to populate actual cost to sales order line using DP91
if you have Milestone billing , you can configure Sales order line item with Billing plan and get 20% as down payment from customer, before you release Project and bill respectively
hope this is useful
thanks
santosh

Milestone Billing

Dear Experts,
I'm interested to know whether DIP profile is mandatory to bill customer projects through milestone billing & sales order?
I never experienced customer projects and in capital projects, customer billing was not there.
So if we can bill without DIP profile, how can we do?
Waiting for your valuable suggestions
Regards,
VINOD.V.

Hi Vinod,
Milestone billing and RRB are two different concepts and RRB need not do anything with MS billing.
In Milestone billing, following are the configurations which need to be done.
You should have a Billing Plan with Milestone billing in SD with relevant date categories, etc and this Billing plan should be assigned to the relevant item category
From PS, you will have basic PS configuration entries followed by Milestones, with the usages etc.
Also some transactional projects, WBS elements or networks with Milestones enabled in either WBS or in Network activities.
These milestones should be Billing relevant milestones (Sales Document Date check box ticked on)
Now the sales order items should have account assignment object as WBS element.
If these set ups are available, then it is possible to have MS billing. When activities are confirmed in Network, billing is activated for the relevant milestones.
Having said these, it is also possible to have a simplified version of Milestone billing without Project System, just by enabling a MS billing plan. But here all the billing plan records need to be manually managed with billing block etc....
This is only a basic tip to explore further. If we shoudl enable the complete MS billing with PS, you will also need help from a PS consultant.
You can do MS billing very well without DIP profile
Hope this helps

Milestone billing without sales Order

Hi Experts,
We have a requirement to use SAP PS to produce a material and be used in the same company or the sister companies.
The project will be only for OPEX cost. They have requested us to do by milestone billing as the fund will be paid at intervals, but there is no sales order.
Is there a possibility to bill the milestone assigned to the WBS element at intervals ?
I have tried to search online, but couldn't get whether this is possible or not.
Appreciate your reply, whether this is possible with our SAP System.
Thanks
Terence

Hello Maria,
Can't you achieve the almost same process using Inter company/Intra company STO (stock transfer Order)? As shown in the link below:
http://wiki.scn.sap.com/wiki/display/profile/Intercompany+Business+Processing?original_fqdn=wiki.sdn.sap.com
Cross-Company Stock Transfer - Managing Special Stocks (MM-IM) - SAP Library
Create STO (ME21N) -> Delivery -> Picking -> Billing.
For Billing with milestones from project with no SD, I am not sure whether it can be done.
Regards
Saurabh

Milestone Billing for partial quantities

Hi,
My client is having Milestone billing schedule where in they bill their customers as per the billing schedule maintianed in the billing plan tab in sales order.
Billing plan is activated at Item level as the various items in a sales order can have different schedules.
But the issue is that they bill their customer on pro-rata basis which means the the billing document created for different milestones in the billing plan for each item can happen for partial quantities of the item under consideration.
Standard SAP Functionality doesnot allow this. In Copy Control, I tried out using the Invoice Split in Data Transfer Routine in Copy Control which doesnot give me the desired fucntionality.Copy Requirements Formula used is 023 (Item ord.ref. w/o AZ) as i need to create invoices for each milestones at item level which is working fine. But just that i cannot do milestone billing (for individial milestones at Item Level) for rpartial quantities. It can only happen for the entire order quantity.
In short the condition BIlling Quantity = Order Quantity - Invoiced Quantity is not working. Always Billing Quantity = Order quantity.
Delivery Related billing will not serve their purpose either...
Can any one throw some light on the above issue? Can I achieve the desired rersult using some custom routines?
Regards,
Nithin

Hi Navaneetha,
Thanks for your reply.
I do completely agree with you and informed the same to the client.
I have activated Billing plan at item level and each item is been assigned with different WBS Element and everything is working Fine except the fact that partial billing is not possible for the quantities.
Let me explain the business implications of the same.
My client might have a billing schedule with 4 milestones for an Item A of 100 Quantities in a Sales order
Milestone 1 : Upon the confirmation of Order Acceptance , they bill the customer for 10 %
Milestone 2 : Upon the completion of designing part, they bill the customer for another 20 %
Milestone 3 : Upon the dispatch of materials to the customer. they bill the customer for another 60 %
Milestone 4 : Upon the submission of the documents and completion the legal aspects, the final invoice for the 10 % which completes 100 % Milestone billing
Now here in the third milestone when the items are dispatched, they also need to create the excise invoice. here what they do is that they bill the customer for 60% of the net item value as explained above, but the taxes would be calculated for 100% net item value( VAT/CST & Excise Duties).and based on this commercial invoice, the excise document is created. I managed to map that. No problems
But their concern is with third milestone. Milestone 1, 2 & 4 will happen for the full 100 quantities. But for third milestone, let us say that they dispatched 90 quantities of the item and for some reasons they could not dispatch 10 nos of items. They are entitled to bill their customers for the 90 nos of the Item and the rest 10 Nos they will bill it as a different invoice. Now SAP Doesn't allow this.
One solution is to ask them to prepare Proforma/Commercial Invoice against the delivery Document and Excise Invoice against the invoice so created. But then it further complicates the process and already billing against billing plan is so complicated that they are complaining that their life was so easy before the implementation of SAP
They want some solution for this problem of theirs as when they mean one quantity of Item A, they mean some thing around 10-50 Crore Rupees.
There is one note released by SAP but that is restricted to versions below 4. 7 and become obsolete for higher versions.
Can any body help me out with this? How about possibility of a custom Routine in Copy Control or Data Transfer?
The problem is that the moment i activate an item category with billing plan, it deactivate the copy control setting for partial order billing.
Thanks & Regards,
Nithin Mohanan

Billing plan: milestone billing problem.

I have the following scenerio:
Billing plan:
(Net value: 1000 euros)
- Milestone nº1 20% (percentage of value to be invoice). That is: -->200 euros
- Milestone nº2 30% --> 300 euros
- Milestone nº3 50% -->500 euros
I create first invoice for milestone 1 (that is: 200 euros).
Then, this sales order is modified, so net value is now 1100 euros.
If I don't do anything, the system changes my billing plan:
- Milestone nº2 30% --> 330 euros
- Milestone nº3 50% -->550 euros
but I have 20 euros left that has not been invoiced. I know I could change manually the billing rule and choose billing rule 3 "Closing invoice in milestone billing", but i would like the system to do it automatically. In explanation, the system should propose:
- Milestone nº2 --> 330 euros + 20 euros
-_Milestone nº3_--> 550 euros.
Is it possible? How should I proceed?

Hello Luis,
it is not possible to assign automatically the difference in the second billing plan line.
But you can make the system automatcially assigns to the last one.
Please set the last milestone billing plan line as closing invoice:
- Date description 0008
- Billing rule 3
Best regards,
Ivano.

Sales order with milestone billing

Hi,
We are migrating sales orders with milestone billing to ECC 6.0 system. There are line items in the sales orders in the billing plan which have been completely billed. For line items which have not been billed, there is billing block which flows from the WBS element attached to the line item.
We want to transfer the sales orders to the new system with same status of billing completed for the line items for billing dates which have been billed. This will ensure that billing is not done again in the new system for these billing dates.
Kindly guide as to how we can achieve this.
Regards,
T Saravanan

Hi,
We are moving the orders from ECC 6.0 system to ECC 6.0 system only.
The challenge is to that customer wants the orders with milestones completely billied as it is in the system.
When we bring the orders to the new system, how to ensure this status for milestones which have already been billed.
Regards,
T Saravanan

Milestone billing is possible eventhough billing status is blocked.

Similar Messages

Maybe you are looking for