Billing?

[Former Member]

Hi

plz tell me about milestone&periodic billing and proforma invoice in detail with configuration settings.

[Former Member]

Hi Friend,

Billing Plan for Milestone Billing

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

[Former Member]

Hi Raj,

Mile stone billing is part of PROJECT SYSTEMS MODULE integrated with SD.

Milestone billing is practiced by Infrastructure companies and Power Ind,and construction industry(projects).

Billing Plan for Milestone Billing

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

You can get the detailed information from this link:

http://www.sap-img.com/sd006.htm

Periodic Billing can be used, for example, in rental contracts. The billing dates in a periodic billing plan can be determined from the following sources:

• Control data in the billing plan

• Header data in the rental contract

• Manually entered dates

The following dates are important for billing date determination:

• Start and end dates

• Period (monthly, quarterly, annually)

• Horizon

Start and end dates

Start and end dates define the duration of the billing plan and, whenever possible, are copied from the start and end dates of the corresponding rental contract.

Depending on the configuration of your system, these dates may be indirectly determined by the system. For example, the contract start date may be determined automatically as soon as the installation date is entered.

Period (monthly, quarterly, annually)

The periodicity of the billing dates determines the frequency with which the billing dates are created in the billing plan and, in addition, whether a billing date is processed for billing on the first or last day of the month.

Horizon

In case no end date is entered, or the end date lies so far in the future that not all billing dates can established, then a rule for determining the horizon can be entered. The horizon for periodic billing determines the last date of the billing plan.

The horizon is always determined by a rule that uses the current date as a baseline. If the current date is updated during processing, the system automatically extends the horizon and the schedule of billing dates into the future.

The determination of dates according to the current horizon must be triggered manually via the following menu path.

Sales and Distribution1. Select Logistics Sales.

Subsequent functionsContract 2. Choose Outline agreement Horizontal/periodic billing.

Report RVFPLAN01 which supports this function can be scheduled to run at regular intervals.

Example: Periodic billling is billing the customer for the total amount(here 1000 USD) at regular intervals peridically until the customer agreement is reached. eg: 1000/12 for a 1 year agreement and say billed at the 1st day of every month.

proforma Invoice

After completion of the delivery you can create proforma invoice with reference to the delivery document in the transaction VF01.

You can create Proforma invoice with reference to the Sales order also.

Go to VF01 transaction enter the billing type as F5 if you want create proforma invoice with sales order.

or Enter billing type as F8 it you want to create proforma invoice with delivery.

Before all these things you should have the copy control settings between order to proforma invoice and delivery to proforma invoice

Please Reward If Really Helpful,

Thanks and Regards,

Sateesh.Kandula

[Former Member]

Normal Sales Order Cycle:-

Step 1: Sales Document Type

IMG > Sales and Distribution > Sales > Sales Documents >

Sales Document Header:

1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.

2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.

3. Assign Sales Area To Sales Document Types:

A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.

B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.

Sales Document Item:

1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.

2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category

Schedule Line:

1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.

2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.

Step 2:

IMG > Logistic Execution > Shipping > Deliveries >

1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.

2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.

3. Define Number Ranges for Deliveries: Ensure to maintain number range.

Step 3:

IMG > Sales and Distribution > Billing >

1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.

2. Define Number Range For Billing Documents: Ensure to maintain number range.

3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.

Note: Ensure that Copy Control settings are done

Sales Order to Sales Order (QT --> OR): VTAA

Sales Order to Delivery (OR --> LF): VTLA

Sales Order to Billing (OR --> F1): VTFA

Delivery to Billing(LF --> F2): VTFL

Billing to Sales Order (F2 --> RE): VTAF

The configuration differs from scenario to scenario & requirement of the client.

-

---

This can be configured using Milestone Billing.

1. Create New Sales Order Type, say ZOR (Copy of OR) through T.Code: VOV8

Maintain Delivery Type as LF & Billing Type As 'F1' - Order Related / 'F2' Delivery Related.

IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define Sales Documents Types

2. Assign New Sales Document Type to Sales Area, For Eg:

1000 (S.Org) / 10 (D.Channel) / 10 (Division) / ZOR (S.O Type)

IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Assign Sales Area to Sales Document Type

3. Create New Item Category, say ZTAN - Copy of TAN (For delivery Related) / ZTAD - Copy of TAD (For Order realted) / ZTAS - copy of TAS (For Third Party)

Maintain as under (others remaining same)

Billing Relevance: I

Billing Plan Type: 01

IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Item > Define Item Category

4. Assign Item Category, for ex (assuming Usage & higher level item category as blank):

Sales Document Type | Item Category Group | Default Item Category

ZOR | NORM | ZTAN

ZOR | DEIN | ZTAD

ZOR | BANS | ZTAS

IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Item > Assign Item Category

Note: In the above Billing Type '01' plays the main controller for milestone billing. In Sales order, at item level, we require to maintain the billing plan.

Follow the Sales cycle as normal sales cycle for particular Scenarios

-

---

Periodic Billing.

1. Create New Sales Order Type, say ZOR (Copy of OR) through T.Code: VOV8

Maintain Delivery Type as LF & Billing Type As 'F1' - Order Related / 'F2' Delivery Related.

IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define Sales Documents Types

2. Assign New Sales Document Type to Sales Area, For Eg:

1000 (S.Org) / 10 (D.Channel) / 10 (Division) / ZOR (S.O Type)

IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Assign Sales Area to Sales Document Type

3. Create New Item Category, say ZTAN - Copy of TAN (For delivery Related) / ZTAD - Copy of TAD (For Order realted) / ZTAS - copy of TAS (For Third Party)

Maintain as under (others remaining same)

Billing Relevance: I

Billing Plan Type: 02

IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Item > Define Item Category

4. Assign Item Category, for ex (assuming Usage & higher level item category as blank):

Sales Document Type | Item Category Group | Default Item Category

ZOR | NORM | ZTAN

ZOR | DEIN | ZTAD

ZOR | BANS | ZTAS

IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Item > Assign Item Category

Note: In the above Billing Type '02' plays the main controller for periodic billing. In Sales order, at item level, we require to maintain the billing plan.

Follow the Sales cycle as normal sales cycle for particular Scenarios

-

---

Proforma Invoice

T.Code: VF01

Billing Type F5 - Order Related Proforma Invoice

Billing Type F8 - Delivery Related Billing Type

Regards,

Rajesh Banka