Professional Documents
Culture Documents
Invoicing Plan in Sap MM
Invoicing Plan in Sap MM
So, In invoicing plan you don’t wait for invoices from vendor’s ,the system will generates invoices
automatically for scheduled dates.
In Po, system will creates the desired dates for the invoices with amount based on Valid from
and Valid To and invoicing plan type. For these Po’s there is NO GR. So, we also called
as special type of planned procurement for non- stock materials because the materials are non
stock materials. System will generates the invoices for Po scheduled dates automatically and
Once release the invoices payment will be done. It is also possible to enter the invoice for an
invoicing plan manually.
Based On PO data system will creates invoices automatically. Invoicing plan is help ful to users,
do not wait each time for the vendor to submit an invoice for goods or services performed.
Invoicing plan is helpful for the regularly repeated Procurement transactions like Rental, leasing
and also for invoicing of highly invested material or projects involving the procurement of
external services that are to be subject to stage payments such as construction projects and
building projects.
Simple explanation, For Periodic invoicing plan – Payment of total amount effected at regular
intervals. Ex : Vehicle leasing ( payments monthly) , Ground lease
Pre Requisites :
4) Both GR indicator and GR Non valuated Indicator should be set or not set
6) SAP recommends the Frame work order type (FO document type) in PO.
Path : Material Management —-> LIV —-> automatic settlement —-> MRIS -invoicing plan
settlement.
SPRO –> Material Management –> Logistics Invoice Verification –> Incoming Invoice –> Number
Assignment –> Maintain Number Assignment for Logistics Documents –> Transaction – Assign
Number Range
3)Once the Invoice is posted, the settlement documents are sent to vendor automatically in print,
email or fax form. The below mentioned Message Determination configuration is required for this
action.
SPRO –> Material Management –> Logistics – Invoice Verification –> Message Determination –
> Maintain Message Types
Out put type INS, you should configure for this output type.
Important points :
1) The account assignment category cannot be changed once you have created the item. Only
the detailed data dependent on the account assignment category, such as the specification of the
cost center in the case of account assignment category K, can be changed at any time.
2) The invoicing plan settlement run can be carried out either online or in the back ground.
3) Further information on Problem with invoicing plans can be found in Note 499523.
Invoicing Plan
Skip to end of metadata
Created by Arminda Jack, last modified by Diana Dai on Dec 07, 2015
Go to start of metadata
Content
"List of dates on which invoices for purchase order items covering materials or services are to be maintained and paid.
The invoicing plan permits extensive automation of the process of creating and paying invoices for both recurring
procurement transactions (such as rental or leasing payments) and transactions involving settlement in stages (such as
payment regarding the individual phases of a building project as they are completed)."
How it works
The invoicing plan is a time schedule that belongs to a PO item. According to this time schedule the system
automatically can create invoices when the planned invoicing date is reached.
(There are also customers who don't use the automatical posting of invoices, but use the invoicing plan as a sort of
memory aid for themselves where they can look up when to create an invoice.)
Invoicing plans contain informations and rules that belong to the whole invoicing plan, like:
invoicing value
invoicing date
billing block (if filled -> no invoice will be created at the invoicing date of this line. The billing can not be filled or deleted
by the system! If you want to use it, the billing block has to be filled / deleted manually.)
billing status (for invoicing plans the billing status can have two different values: 'A' = not processed, 'C' = partially
processed or fully processed, status 'B' does not exist for invoicing plans, but only for SD factury plan!)
The invoicing dates in periodic invoicing plans are created automatically by the system.
This is how the corresponding partial invoicing plan can look like:
The invoicing dates in partial invoicing plans can either be created manually (like in the above example) or
automatically.
To create the dates automatically an appropriate reference invoicing plan has to be used. This has been done in the
following example:
reference invoicing plan 1838 has been used.
The invoice dates have been created automatically, using the relation between start date and invoice dates of the
reference invoice plan and using the percentages of the reference invoice plan.
You can maintain a reference invoicing plan for an invoicing plan type in customizing, in 'Maintain Date Proposal for
Partial Invoicing Plans'. This is explained later in chapter 'Customizing'.
(Partial invoicing plans can contain down payments too. Down payments can't be posted automatically! They have to be
created manually. The down payment date in an invoicing plan is only a memory aid for the user.
The whole amount of the PO item has to be in the invoices of the invoicing plan. The amount of the down payments
must not be subtracted from the amount of the invoices.
The payment program in the end knows about the down payments and only pays the difference between the invoice
and the down payment.)
If you want the system to automatically create invoices for this PO item, you must flag ERS (Evaluated Receipt
Settlement, EKPO-XERSY) on the item detail screen.
(To make this ERS field appear on the screen, it must be chosen in the customizing of the vendor where it is part of
'control data')
In a partial invoicing plan you can either create the dates manually or use a reference invoicing plan (see above,
chapter 'How it works, Partial invoicing plan').
In a periodic invoicing plan, you can not create or delete dates manually (if you do so, these changes will be undone by
the system when the invoicing plan is worked with either directly or via transaction MLRP)
To create or delete invoicing dates, use the rules defined in the invoicing plan like "start date" and "end date" - maybe
additionally "dates from" and "dates until" - "horizon", rules like "monthly", "in advance", ... (see above, chapter 'How it
works, Periodic invoicing plan').
You can define your own invoicing plan types here. To do so, please copy an existing invoicing plan type and change it.
Here you can maintain data that are suggested in an invoicing plan, such as start date etc.
The field "Dialog pur. Order" has to be maintained here too. It is important for the automatic creation of invoicing dates.
This rules means that there will be a new invoicing date one ("time period") month ("time unit") after the last invoicing
date ("baseline date"). The invoicing dates will be at the first of month.
(The calendar ID can be used if you want the invoicing dates to be at different dates: you could define a calendar that
has only one working day each month. In this case leave the field "last of month" blank and fill the field "calendar ID".
The invoicing dates will then be at the only working day of each month.)
Often customers think that there is a link between the invoicing date in the invoicing plan and the invoice.
There is no such connection! All invoices belong to the PO item. All the information is in the PO item (such as
accounting information for example or the value).
The invoicing plan is only a scheme to remind the system (or the user) of when to post an invoice. It is nothing else!
A connection between invoicing dates in the invoicing plan and invoices will not be realised either (from time to time
there are customers asking for this). Such a connection is not part of the concept of invoicing plans. The invoices are
connected only to the PO item.
(The design of the whole functionality is not to realise such a connection. If someone would want to redesign the
invoicing plan and realise this connection, the whole functionality would have to be designed and programmed newly.)
Sometimes customers want to use the status of an invoicing date ('A' or 'C') for some report of their own. This status
has to be calculated newly whenever it is needed.
The status that is stored in table FPLT is irrelevant!
The design is to calculate the status newly whenever the invoicing plan is touched. The system does this by taking the
sum of all invoices that belong to this item. This sum is then being distributed on the invoicing dates in chronological
order (leaving out the invoicing dates with billing block).
All invoicing dates that get at a part of the sum, get status 'C' ("partially processed / fully processed").
The invoicing dates that get nothing of the sum of all invoices, get status 'A' ("not processed").
-> when the status is needed for a new report, it must not (!!) be taken from the database but must be calculated!
Tables:
There are two database tables that store the informations of invoicing plans:
FPLA: contains informations and rules that belong to the whole invoicing plan, like:
- invoicing plan type
- start date
- end date (only for periodic invoicing plans)
- dates from (only for periodic invoicing plans)
- dates until (only for periodic invoicing plans)
- Rule for determining the next billing/invoice date (only for periodic invoicing plans)
- in advance (only for periodic invoicing plans)
- calender ID (only for periodic invoicing plans)
- horizon (only for periodic invoicing plans)
- reference (only for partial invoicing plans)
Each invoicing plan has a number. In table EKPO this invoicing plan number is stored in field EKPO-FPLNR. Via this
FPLNR invoicing plan and PO item are tied together.
Function modules:
Forms:
SAPMM06E / SAPLMEPO
Forms:
Forms:
ME_PREPARE_STATISTICS
RKO_EKBE
Forms:
Function group V60F (does not belong to us but to SD. It is billing plan code. Invoicing plan uses much of their code,
but there are some special parts of the code that are processed only for invoicing plans!)
Forms:
RECHNUNG_VERTEILEN distributes sum of all posted invoices to the invoicing dates -> decides if an invoicing date gets
status 'A' or 'C'.
When we are in SD billing plan code, invoicing plan and billing plan can be distinguished by field XFPLA-FPTYP:
For Invoicing plans, XFPLA-FPTYP = 'B'
Important notes
685262 Down payments in the invoicing plan
663759 Connection of invoice and invoicing plan date
621072 Invoice quantity in purchase order with invoicing plan
562298 Statistics: REWRT and REMNG w/ invoicing plan
552039 Composite SAP note for problems in LIS with invoicing plan
537779 Date generation for Periodic Invoicing Plans
535461 MCER: Invoice quantity in purchase order with invoicing plan
525108 Parked invoices with invoicing plan
499799 Total value of purchase orders with periodic invoicing plan
499688 FAQ: Ending an invoicing plan / restricting date period
499523 FAQ: Invoicing plan in MM
484608 Price change in invoicing plan
456398 Invoicing plan: Status 'C' for not settled date
442610 Block for dates in the invoicing plan
433597 Commitment update for services or invoicing plan
350549 RE-PLAN: Invoicing plans and account assignment change
339264 IR plan:commts reductn for invoicing plan (net doc)
321164 Invoice entered manually for invoicing plan
303610 Invoicing plan: commitments only reduced for period