Академический Документы
Профессиональный Документы
Культура Документы
In SAP SD a billing plan is a schedule of individual billing dates for a single item in a sales document.
You can define a billing plan at header level, which is then valid for all items assigned to it.Depending
on the kind of business process you are carrying out, the system can automatically propose the billing
plan.
Value of 200 MYR will be distributed among various dates( % or amount ) as per the configuration.
Billing Date Description Billing Value
From the above example value of the sales order will be 200 MYR.
A. Start date :- Date from which billing plan will start .Start date is compared with next billing date(5)
and gives first date of “Settlement To” and “Billing date” in periodic plan. ie. If your start date is the
24rd of a month and you are billing monthly, all billing date will start on the 23rd” (if there are no
further conditions discussed in the later part of the document ).
B. End Date :- Date on which billing plan ends .
Screen shot from rental contract header.
C.Horizon :- This is optional field .If there is no End date entered or Contract end date is far in the
future . Not all billing dates can be accomodated in the billing date screen.The horizon calculates the
last billing date in the
billing plan, based on the current date plus a specified time period.
Example-
If the rental /service contract which is valid from 24.08.2015 until 23.12.2098 .
Before : Rental contract with no Horizon
Screen 1 – End date far in future
Screen 3 – Billing dates created only up to Horizon period.(Only for current quarter ).
Note : – Schedule a back ground job for RVFPLAN01(T-code V.07) to create the future billing date
for the given horizon period.
D. Dates From To : – These date has meaning when item level has certain validity . Billing plan will
be deactivated after validly expired on item level.
Example- Rental contract has two line Items.
Item 10- Header plan- validity from 27.08.2015 Until 26.08.2016 . (Billing dates created up to
26.08.2016)
Item 20 Item level Dates from – 27.08.2015 to Dates Until 26.09.2015 .So Item second has validly
only until 26.09.2015.(Billing dates created up to 26.09.2015)
E. Rule for Origin of Next Billing/Invoice Date :- This is copied from customization , The rule
assigned here is compared with start date and billing dates are proposed in the contract.Please refer
to point number A.
F. Rules for determining deviation in Billing/Invoice date :-
This field determines if there is exception or deviation in billing dates proposed by billing rule .The
customer is to be billed retrospectively for the rental of a photocopier at the end of every month. The
customer, however,wants to be billed two days before the end of each month. You enter a date
determination rule, which subtracts two days from the billing date determined by the system.
Example :- Your client is billing the customer at the end of every month. Client wants to bill the
customer 2 days before end of the month. With deviation rule you can force system to calculate
billing date before or after deviation days .
Before : No data maintained for deviation rule
Example – In the below screen customer was billed for the period of billing Plan dated 01.07.2015
until
31.07.2015 for 100 Euro . But later contract was foreclosed dated 25.07.2015.Credit issued to the
customer for the period of 26.07.2015 to 31.07.2015
2. Define Date Description:-
Date descriptions are defined to describe the various purposes for which billing Plans can be
used.This is only for description only. It has no effect in transaction.
v. Pricing – If you want to carry out new pricing at the time of billing.
vi. Billing Type- This is the default billing type proposed at the time of contract creation in billing Plan.
4. Allocate date category :- Assign the date category to billing plan
5. Assigning Billing Plan Types to Sales Document Type :- This assignment will tie sales
document type with header periodic billing plan.
This is the last section of the documentation for periodic billing plan.Please proceed with T-code
va41 and test on different scenarios .