This document describes billing plans in SAP. It discusses the different types of billing plans including periodic billing which is used for rental contracts, and milestone billing which is used to distribute amounts over billing dates based on project milestones. It describes how billing plans are controlled through billing plan types, date categories, and assigning billing plan types to items. Key functions of billing plans are also summarized such as automatic creation of dates, pricing, billing blocks, and document flow.
S4 HANA sattlement management_Ganesh Tarlana Ganesh Tarlana
Settlement Management functionality supports all types of settlement processes, including core business processes that need to be fully integrated in the order-to-cash cycle or within in a procure-to-pay scenario, such as condition contract settlement (rebate settlement), as well as standalone processes, whereby you provide special financial settlement services for your business partners
When good receipt (GR) and invoice receipt (IR) is performed, an accounting document gets generated. Movement of material leads to the automatic generation of accounting document and this is referred as MM FI integration.
This SAP SD Study Material & Configuration Guide is extracted from my training material which I provide to my students.
This material is enough for you to get a SAP SD JOB, I even provide 1000+ Interview questions along with SAP SD Study Material.
I will update this document frequently ,so please check for new versions of my SAP SD Training study material.
SAP Asset accounting book Sample PDF by LearnSAPLearnSAP LLC
http://www.learnsap.com/sap-study-material.php
SAP Asset accounting step by step study sample material - visit our website http://www.learnsap.com/sap-study-material.php for complete access of printed hardcopy.
These SAP step by step study guides are carefully written by experienced and certified instructors based in the USA
Call +1-832-419-7371 for more details
S4 HANA sattlement management_Ganesh Tarlana Ganesh Tarlana
Settlement Management functionality supports all types of settlement processes, including core business processes that need to be fully integrated in the order-to-cash cycle or within in a procure-to-pay scenario, such as condition contract settlement (rebate settlement), as well as standalone processes, whereby you provide special financial settlement services for your business partners
When good receipt (GR) and invoice receipt (IR) is performed, an accounting document gets generated. Movement of material leads to the automatic generation of accounting document and this is referred as MM FI integration.
This SAP SD Study Material & Configuration Guide is extracted from my training material which I provide to my students.
This material is enough for you to get a SAP SD JOB, I even provide 1000+ Interview questions along with SAP SD Study Material.
I will update this document frequently ,so please check for new versions of my SAP SD Training study material.
SAP Asset accounting book Sample PDF by LearnSAPLearnSAP LLC
http://www.learnsap.com/sap-study-material.php
SAP Asset accounting step by step study sample material - visit our website http://www.learnsap.com/sap-study-material.php for complete access of printed hardcopy.
These SAP step by step study guides are carefully written by experienced and certified instructors based in the USA
Call +1-832-419-7371 for more details
SAP Profit center accounting provides the information of an organization’s profit and loss. The method which can be utilized for profit center accounting is period accounting. Profit centers can be set-up to identify product lines, divisions, geographical regions, offices, production sites or by functions. Profit centers are used for internal control purposes enabling management the ability to review areas of responsibility within their organization. The difference between a cost center and profit center is that the cost center represents individual costs incurred during a given period.
What's New in SAP Business One 10.0
For more information, please contact at
Sundae Solutions Co., Ltd.
Tel. +66 26348899
Email: sales@sundae.co.th
URL: http://www.sundae.co.th
Understanding GL determinations in SAP Business OneMTC Systems
Overview of GL Determinations
Determinations by Module
GL Determinations & Fiscal Periods
Using a Template Chart of Accounts
GL Default Account Hierarchy
System Level Defaults to Master Records
Business Partners
Warehouse
Item Groups
Items
Do Not Use or Dummy Accounts
GL Determinations and Master Data Conversion
Additional GL Accounts Setup
Tax Jurisdictions
House Banks
Credit Cards
New GL Determination Guide
Oracle Sales Planning Cloud is a new addition in Oracle Enterprise PBCS solution stack keeping same EPBCS frameworks. Oracle Sales Planning focuses on a) Planning, directing, evaluating sales b) Sales quotation planning at territory or resource level c) Benchmark for evaluating sales effectiveness d) Sales commission planning.
SAP FICO Interview Questions By Garudatrainingspiyushchawala
SAP FICO is a core SAP module that covers the financial and reporting segments of a business.
It consists of the interrelated component modules-FI (Financials) and CO (Controlling) with an
extensive set of sub-modules that cover every aspect of the financial and managerial accounting
for both external and internal reporting. Skilled FICO Technical and Functional Consultants are in
very high demand as enterprises world over have been moving to SAP as a single solution for their
business needs. As financial management forms the very basis for any business, SAP FICO has seen
a consistent increase in its implementation with a very high demand for FICO professionals. Garuda
Trainings has come out with a comprehensive online training course in SAP FICO to give our students
the much needed advantage in this highly competitive and sought after segment of the ERP industry.
Online SAP FICO Course Contents: FICO is an integration of two modules FI and CO and the below
curriculum has been segmented accordingly.
Contents:
1) An Introduction to SAP
2) The FI module and its architecture
3) General Ledger Accounting
4) Fixed Assets sub-module
5) The Account Receivables sub-module
6) The Accounts Payable sub-module
7) Integration with other SAP modules and business implementation and deployment
8) The CO module and its architecture, interaction with the FI and other SAP modules
9) Cost centres and profit centres accounting
10) Internal orders and profitability
11) Product costing and activity based costing
For More Info: http://garudatrainings.com/sap-fico-online-training/
Why Choose Us: Our online course in SAP FICO gives you a perfect flexibility of pursing the
course within your existing schedule as you can opt from weekend or weekday batches as per
your convenience. The training resources are prepared by experts with rich experience in SAP
implementations. All modules are led by trainers and are interactive with a recording ability for
future use and access. We offer a 24/7 access to training resources and technical support and give
you a perfect quality training course with an extra emphasis on practical exposure to real-time
implementation scenarios and live projects.
The Complete Advantage: We endeavour to give you a perfect career as a SAP FICO consultant and
our online training course also includes the advantage of placement assistance through our industry
network. To help our users easily clear the interview evaluation, we offer an extensive collection of
in-depth interview questionnaires along with tips of effectively writing resumes. Choose us to get
the perfect advantage in your career as an SAP FICO consultant.
Register For Free Demo:
www.Garudatrainings.com
Email Us:garudatrainings@gmail.com
Ph No:+1-508-841-6144
Transcript: Selling digital books in 2024: Insights from industry leaders - T...BookNet Canada
The publishing industry has been selling digital audiobooks and ebooks for over a decade and has found its groove. What’s changed? What has stayed the same? Where do we go from here? Join a group of leading sales peers from across the industry for a conversation about the lessons learned since the popularization of digital books, best practices, digital book supply chain management, and more.
Link to video recording: https://bnctechforum.ca/sessions/selling-digital-books-in-2024-insights-from-industry-leaders/
Presented by BookNet Canada on May 28, 2024, with support from the Department of Canadian Heritage.
Elevating Tactical DDD Patterns Through Object CalisthenicsDorra BARTAGUIZ
After immersing yourself in the blue book and its red counterpart, attending DDD-focused conferences, and applying tactical patterns, you're left with a crucial question: How do I ensure my design is effective? Tactical patterns within Domain-Driven Design (DDD) serve as guiding principles for creating clear and manageable domain models. However, achieving success with these patterns requires additional guidance. Interestingly, we've observed that a set of constraints initially designed for training purposes remarkably aligns with effective pattern implementation, offering a more ‘mechanical’ approach. Let's explore together how Object Calisthenics can elevate the design of your tactical DDD patterns, offering concrete help for those venturing into DDD for the first time!
State of ICS and IoT Cyber Threat Landscape Report 2024 previewPrayukth K V
The IoT and OT threat landscape report has been prepared by the Threat Research Team at Sectrio using data from Sectrio, cyber threat intelligence farming facilities spread across over 85 cities around the world. In addition, Sectrio also runs AI-based advanced threat and payload engagement facilities that serve as sinks to attract and engage sophisticated threat actors, and newer malware including new variants and latent threats that are at an earlier stage of development.
The latest edition of the OT/ICS and IoT security Threat Landscape Report 2024 also covers:
State of global ICS asset and network exposure
Sectoral targets and attacks as well as the cost of ransom
Global APT activity, AI usage, actor and tactic profiles, and implications
Rise in volumes of AI-powered cyberattacks
Major cyber events in 2024
Malware and malicious payload trends
Cyberattack types and targets
Vulnerability exploit attempts on CVEs
Attacks on counties – USA
Expansion of bot farms – how, where, and why
In-depth analysis of the cyber threat landscape across North America, South America, Europe, APAC, and the Middle East
Why are attacks on smart factories rising?
Cyber risk predictions
Axis of attacks – Europe
Systemic attacks in the Middle East
Download the full report from here:
https://sectrio.com/resources/ot-threat-landscape-reports/sectrio-releases-ot-ics-and-iot-security-threat-landscape-report-2024/
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
JMeter webinar - integration with InfluxDB and GrafanaRTTS
Watch this recorded webinar about real-time monitoring of application performance. See how to integrate Apache JMeter, the open-source leader in performance testing, with InfluxDB, the open-source time-series database, and Grafana, the open-source analytics and visualization application.
In this webinar, we will review the benefits of leveraging InfluxDB and Grafana when executing load tests and demonstrate how these tools are used to visualize performance metrics.
Length: 30 minutes
Session Overview
-------------------------------------------
During this webinar, we will cover the following topics while demonstrating the integrations of JMeter, InfluxDB and Grafana:
- What out-of-the-box solutions are available for real-time monitoring JMeter tests?
- What are the benefits of integrating InfluxDB and Grafana into the load testing stack?
- Which features are provided by Grafana?
- Demonstration of InfluxDB and Grafana using a practice web application
To view the webinar recording, go to:
https://www.rttsweb.com/jmeter-integration-webinar
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
Key Trends Shaping the Future of Infrastructure.pdfCheryl Hung
Keynote at DIGIT West Expo, Glasgow on 29 May 2024.
Cheryl Hung, ochery.com
Sr Director, Infrastructure Ecosystem, Arm.
The key trends across hardware, cloud and open-source; exploring how these areas are likely to mature and develop over the short and long-term, and then considering how organisations can position themselves to adapt and thrive.
3. SAP AG Billing Plan (SD-BIL-IV)
April 2001 3
Icons
Icon Meaning
Caution
Example
Note
Recommendation
Syntax
Tip
4. Billing Plan (SD-BIL-IV) SAP AG
4 April 2001
Contents
Billing Plan (SD-BIL-IV) ................................................................................................. 5
Billing Plan....................................................................................................................................................6
Billing Plan Functions..................................................................................................................................8
How Billing Plans are Controlled..............................................................................................................11
Periodic Billing ...........................................................................................................................................13
Credit Memo Date in the Billing Plan ......................................................................................................15
Milestone Billing.........................................................................................................................................17
Billing Plans at Header Level ....................................................................................................................19
Functions in Header Billing Plans ............................................................................................................20
Displays.......................................................................................................................................................21
Header Billing Plans in Milestone Billing.................................................................................................22
Header Billing Plans in Periodic Billing...................................................................................................23
5. SAP AG Billing Plan (SD-BIL-IV)
Billing Plan (SD-BIL-IV)
April 2001 5
Billing Plan (SD-BIL-IV)
6. Billing Plan (SD-BIL-IV) SAP AG
Billing Plan
6 April 2001
Billing Plan
Purpose
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 one of two different types of billing plan: periodic billing or milestone billing.
Billing types
Milestone billing
Periodic billing
% of net item value
fixed amounts
final calculation
Lease/contract
fixed period
always 100 %
· Periodic billing means billing a total amount for each individual billing date in the plan. For
example, if you are creating a rental contract, the system can propose a schedule of monthly
rental payments, according to the length and conditions of the contract.
· Milestone billing means distributing the total amount to be billed over multiple billing dates in
the billing plan. For example, you can use a billing plan for billing a make-to-order item that is
assigned to a project in the SAP Project System. When you enter the project-related make-
to-order item in the sales order (or assembly order), the system proposes a billing plan based
on milestones defined for networks in the project. 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. For each billing
plan you create, you can enter a freely-definable search term in the details screen of the billing
plan in the sales document. When you save the document, the system automatically assigns a
number that later uniquely identifies the individual plan. You can use the search term later to
locate specific billing plans.
Billing plans for rental contracts and 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.
For more information about project milestones, see the Production Planning
documentation about the Project System.
7. SAP AG Billing Plan (SD-BIL-IV)
Billing Plan
April 2001 7
8. Billing Plan (SD-BIL-IV) SAP AG
Billing Plan Functions
8 April 2001
Billing Plan Functions
Billing plan processing includes the following functions:
· Automatic creation of billing plan dates
· Pricing
· Billing block
· Billing index
· Billing status
· Billing rule for milestone billing
· Fixed dates in milestone billing
· Document flow
· Creating with reference
· Exchange rate determination
Automatic Creation of Billing Plan Dates
In Customizing for Sales, you control how the system automatically creates the schedule of dates
in a billing plan. The system determines the schedule of individual dates based on general date
information, such as the start and end dates. This general date information is copied either from
contract header data or from proposals in the billing plan type.
Pricing
Sales document items are billed as each billing date in the plan becomes due. The system
determines the amount to be billed either from the condition records that are applicable to the
item or from the values that are explicitly entered in the billing plan for a particular billing date. In
milestone billing, for example, you can specify a percentage to be billed or an actual amount.
Billing block
A billing block can be set for each date in a billing plan. The block prevents processing for a
particular billing date but does not necessarily affect any of the other dates in the plan. In
milestone billing, the system automatically sets a billing block for each billing date. This block
remains in effect until the project system reports back that the milestone in the corresponding
network has been successfully completed. At this point the system removes the block.Billing
index
For every billing date in a plan, the system creates and updates a billing index. If a billing date is
blocked for billing, the system copies this information into the index.
Billing status
The system assigns a billing status to each billing date in the plan. The status indicates to what
extent the billing has been processed for that particular date. After billing has been carried out
successfully, the billing status is automatically set to ‘C’. This prevents a billed date from being
billed again.
9. SAP AG Billing Plan (SD-BIL-IV)
Billing Plan Functions
April 2001 9
Billing Rule for Milestone Billing
For every date in the milestone billing plan, you can specify a billing rule. The rule determines
how the billing amount for the particular date is calculated. For example, you can specify whether
the billing amount is a percentage of the total amount or whether it is a fixed amount. The
following figure shows an example of how a billing value can be determined.
Item 1: Turbine
PR00
KA00
FR00
100.000
10.000
500+
10 %
Net value * (%) of billing plan =
Net value 90.500
+ 10 kg
-
In addition, you can specify that the amount to be billed is a final settlement that takes into
account billing that has not yet been processed. For example, price changes may take place after
billing dates in the plan have already been processed. The price differences can be taken into
account during final settlement.
Final settlement is not automatically proposed in the billing plan by the system; you
must enter it manually during processing.
Fixed dates in milestone billing
You can control for each date in a billing plan, whether the date is fixed or whether the system
copies the date from the planned or actual milestone dates in a project.
Document flow
After a particular date in a billing plan is processed for billing, the system updates the document
flow for the corresponding sales document item. The following figure shows an example of
document flow for a billing plan.
Sales order 4711
120.000
100.000
20.000
Billing plan data
10.06.95
.
.
10.000
.
.
Bill. Doc.
Item 1 10.000
10.06.95
10.000
Item 1
Item 2
Billing index B. bl.
10.06.95
.
.
10.000
.
.
4711
Posting status
The document flow for the sales document displays the following data:
· Creation date
10. Billing Plan (SD-BIL-IV) SAP AG
Billing Plan Functions
10 April 2001
· Billing date
· Billed value
Creating with reference
When you define a billing plan type in Customizing for Sales, you can enter the number of an
existing billing plan to serve as a reference during subsequent billing plan creation. During sales
order processing for items that require billing plans, the system automatically proposes the
reference plan and, if necessary, re-determines the billing dates (based on the current date rules)
for inclusion in the new billing plan.
Exchange rate determination
In the billing plan with partial billing, you can store a certain exchange rate for each date. The
amount billed is the amount determined after using this exchange rate to convert from the local
currency into the document currency.
An exchange rate can also be stored at item level for the sales document (field: Exchange rate
for FI on the Billing tab page. This fixed rate is valid for all dates in the item billing plan for which
no rate is specified in the billing plan. If an exchange rate is entered both for the date in the billing
plan and at item level in the exchange rate field, then the system uses the rate specified for the
date during billing.
If no exchange rate is entered for the the date or at item level, then the system uses the
exchange rate used for invoice creation and it is forwarded to FI.
When using a header billing plan, all billing plans linked to this header billing plan are
automatically updated. If, for example, you enter an exchange rate manually for the first date in
the header billing plan, this is automatically copied to the corresponding dates for the item billing
plans.
11. SAP AG Billing Plan (SD-BIL-IV)
How Billing Plans are Controlled
April 2001 11
How Billing Plans are Controlled
Billing plans are controlled in Customizing for Sales by the following elements:
· Billing Plan Type
· Date Description
· Date Category
· Proposed Date Category
· Proposed Date
· Assigning billing plan types to sales document items
Billing Plan Type
The billing plan type defines the basic control data for the billing plan. For example, the billing
plan contains rules for date determination. These rules determine, for example, the beginning
and end dates for the schedule of billing dates. The billing plan type also contains a date rule for
determining the horizon for the billing plan. The horizon calculates the last billing date in the
billing plan, based on the current date plus a specified time period (for example: today’s date plus
one year). The standard version of the SAP R/3 System includes the following billing plan types:
· Milestone billing (for example, billing dates determined by the percentage of project
completion)
· Periodic billing (for example, monthly fees for a rental contract)
The billing plan type is displayed in the sales document but cannot be changed.
Date Description
Date descriptions are defined to describe the various purposes for which billing plans can be
used. Depending on the date category you use, the system proposes a date description for the
billing dates in the billing plan. The descriptions are for information purposes only and do not
affect processing.
Date Category
The date category defines data for each billing date that appears in the billing plan. For example,
the date category determines the following data:
· Billing rule (determines whether the billing date is based on, for example, the percentage
of project completion or a monthly periodic payment for a service contract, and so on)
· Date description (specifies, for example, whether the billing date is for a rental contract,
maintenance contract, and so on)
· Billing block (the billing date may be blocked, for example, if a project milestone has not
been confirmed)
· Whether the date is fixed or not (in milestone, you may want the system to use the actual
date of the milestone, for example)
· Billing type (proposes the type of billing document to be used during billing: invoice, pro
forma, and so on)
12. Billing Plan (SD-BIL-IV) SAP AG
How Billing Plans are Controlled
12 April 2001
Proposed Date Category
For every billing plan type, you can assign a date category. During sales order processing, the
system then automatically proposes the date category and its corresponding data for each billing
date in the plan.
The date category “Final settlement” is not proposed as part of the standard version
of the SAP R/3 System and must be entered manually during processing.
Proposed Date
The date proposal function is used only for milestone billing. This function enables you to create
a standard billing plan as a reference. This reference can be used during order processing. The
dates can be used as the basis for an actual billing plan and changed if required.
Assigning Billing Plan Types to Sales Document Items
Billing plans are controlled by item category. In Customizing for Sales, you can specify that
individual item categories are relevant for order-related billing by means of a billing plan. You can
also specify a billing plan type for each item category.
13. SAP AG Billing Plan (SD-BIL-IV)
Periodic Billing
April 2001 13
Periodic Billing
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 figure shows an example of periodic billing:
Order 007
Dates
Periodic addition of data to horizon
08.02.96 100,00
Billing plan 100
Item 10 Rent 100,00
Contract data
Installation data
Contract endStart
Finish
Period
Horizon
Billing date
Billing date
31.10.95
30.11.95
31.12.95
31.01.96
100,00
100,00
100,00
100,00
Rent x
Billing statusDescription Value
31.10.95
monthly
4 periods
Last month
:
:
:
:
:
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.
14. Billing Plan (SD-BIL-IV) SAP AG
Periodic Billing
14 April 2001
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.
1. Select Logistics ® Sales and Distribution ® Sales.
2. Choose Outline agreement ® Contract ® Subsequent functions ® Horizontal/periodic
billing.
Report RVFPLAN01 which supports this function can be scheduled to run at regular intervals.
15. SAP AG Billing Plan (SD-BIL-IV)
Credit Memo Date in the Billing Plan
April 2001 15
Credit Memo Date in the Billing Plan
Use
After cancellation of a contract, depending upon your agreement with the customer, settlement
periods that have already been billed can be recredited automatically.
The most important criterion is that if the end date or ‘to- date’ is changed, it comes before the
last billed data. It is unimportant whether the end date changed because of a rule (e.g. contract
end date) or whether it was entered manually.
Correction dates are created automatically if the field Corr is activated in the document billing
plan data. Activation of this field can be carried out manually or automatically via Customizing.
Deactivating the field removes the correction dates again.
Example:
The contract had a duration of 4 months and all dates were billed. After further
negotiations with the customer, the contract was canceled on April 15 1998 and it
was agreed that the amount for the remaining period would be credited to the
customer.
As soon as the end date is changed, a corresponding correction date is set.
Billingplan
Start 01/01/98 First of eachmonth
End 04/30/98
Settlement period Sts
-----------------------------------------------------------------
01/01/98–01/31/98 01/01/98 USD 100.00C
02/01/98–02/28/98 02/01/98 USD 100.00C
03/01/98–03/31/98 03/01/98 USD 100.00C
04/01/98–04/30/98 04/01/98 USD 100.00C
Billingplan
Start 01/01/98 First of eachmonth
End 04/15/98
Settlement period Sts
-----------------------------------------------------------------
01/01/98–01/31/98 01/01/98 USD 100.00C
02/01/98–02/28/98 02/01/98 USD 100.00C
03/01/98–03/31/98 03/01/98 USD 100.00C
04/01/98–04/30/98 04/01/98 USD 100.00C
04/16/98–04/30/98 04/01/98 USD -50.00 A
Correction
dateà
à
The value of a correction date cannot be changed. If you only want to reimburse a
certain amount to the customer, then you can only do this by fixing the end date.
16. Billing Plan (SD-BIL-IV) SAP AG
Credit Memo Date in the Billing Plan
16 April 2001
Correction dates which have already been billed can no longer be changed.
The billing dates to which the correction dates refer cannot be canceled.
Prerequisites
You need to make the following settings in Customizing for billing plans:
· Billing plan type for periodic billing:
In the ‘Aut.cor.date’ field, you activate the automatic creation of credit memo dates in
the billing plan.
· Date category maintenance:
In the billing type field, you maintain the proposal billing type for the credit memo date in
the billing plan.
In the billing block field you maintain a block indicator for credit memo in the billing plan.
All fields represent a proposal for the billing plan and can be overwritten in the billing plan.
You can configure authorizations for changing the billing block in the document
(activating and deactivating) using authorization object V_VBAK_AAT.
17. SAP AG Billing Plan (SD-BIL-IV)
Milestone Billing
April 2001 17
Milestone Billing
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 following figure shows an example of milestone billing:
Billing
date
Description % Value Billing
block
Billing
status
Mile
stone
10.000
30.000
30.000
30.000
- -
-
x
x
x
x
x
x
x
x
x10
30
30
30
- -
01.10.94
01.03.95
01.04.95
01.05.95
01.06.95
Contract
Assembly
Maintenance
Acceptance
Final invoice
Billing plan
Project Network/activities
Order
Item: Turbine 100.000,00
Milestone Est. Actual
Assembly
Maintenance
Acceptance
01.03.95
01.04.95
01.05.95
01.03.95
For each billing date in a milestone billing plan, you can specify whether the billing date is:
· fixed
· always updated with the actual date of the milestone
· updated with the actual date of the milestone, if the date is earlier than the planned billing
date for the date
18. Billing Plan (SD-BIL-IV) SAP AG
Milestone Billing
18 April 2001
· updated with the actual date of the milestone, if the date is earlier than the planned billing
date for the date
As of Release 3.0C it is also possible to assign milestones to the dates of the billing
plan during milestone billing if no network plan has been opened.
In order to do this you must assign the milestone manually in billing plan
maintenance. For you to be able to make this assignment, the Fixed date field of the
proposed date category of the billing plan type must not be blank. The additional
fixed value (as of Release 3.0C) of Fixed date ‘ ‘ means that you cannot assign it to a
milestone. Milestone assignment is possible for all other values. You make these
settings in the Implementation Guide.
Integration Between Sales and the Project System
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:
1. In one of the overview screens of the sales document, select Item ® Schedule lines.
2. Mark the schedule line and select Procurement details.
19. SAP AG Billing Plan (SD-BIL-IV)
Billing Plans at Header Level
April 2001 19
Billing Plans at Header Level
Up to and including Release 3.0D, billing plans for milestone and periodic billing were created
and maintained exclusively at item level. When making changes to documents across all items,
however, a large amount of manual work was required. Due to the large number of manual
changes, there was also a high risk of error.
As of Release 3.0E, you can define a billing plan at header level which is valid for all items
assigned to it. The header billing plan is maintained at header level. Data copied to the assigned
items cannot be changed in the items.
20. Billing Plan (SD-BIL-IV) SAP AG
Functions in Header Billing Plans
20 April 2001
Functions in Header Billing Plans
· Automatically attaching item billing plans to the header billing plan
All items with the same billing plan type (controlled by the item category) refer to the
header billing plan. By marking the header billing plan field on the item billing plan
screen, you can display the relevant item/header billing plan assignment. If you want to
define billing plans for specific items, you can remove the assignment and maintain the
item billing plan separately.
You can remove or set an item assignment with the assignment indicator. Once an
item has been partially billed, it can be removed from the header but no longer
attached to it.
· Copying the header billing plan to item billing plans
You can copy global changes made at header level to item billing plans assigned to that
header. Dates which have already been billed can no longer be changed. In periodic
billing, the system carries out pricing, determines billing document value and determines
document status at item level, independent of the header.
· Dynamically determining totals and status at header level
Information displayed in the header billing plan is valid for all items which refer to that
header. In milestone billing, billing document value and status at header level are
determined dynamically from all assigned items. The document value at header level is
the sum of all assigned items.
21. SAP AG Billing Plan (SD-BIL-IV)
Displays
April 2001 21
Displays
· In the sales order, you can branch to the header billing plan with Header ® Contract
® Billing plan.
· The header billing document field in the item billing plan (Item ® Contract ® Billing plan)
indicates whether it has been assigned to a header billing plan.
· There are two new fields in the Billing overview screen (Overview ® Billing):
The Billing relevance field indicates for each item whether the sales order isrelevant
for an order-related billing document and whether a billing plan exists(billing
relevance ‘I’)
The Header billing plan field indicates whether the item billing plan refers to the
header billing plan (Header Bill Plan “X”)
22. Billing Plan (SD-BIL-IV) SAP AG
Header Billing Plans in Milestone Billing
22 April 2001
Header Billing Plans in Milestone Billing
The system copies the basis for the header billing plan from Customizing. In milestone billing, the
following functions are carried out at item level:
· Determining billing document value on a percentage basis
· Dates at header level are copied from all item billing plans assigned to that header.
When you make changes at header level (e.g. new billing dates or changes to
percentage rates), the related items are automatically changed accordingly. The system
does not allow you to make changes at item level.
Handling milestones
Dates generated in the header billing plan and milestones set in the header billing
plan (Edit ® Generate dates ® Manual milestones) are copied to the item billing
plans assigned to that header.
If you want to schedule milestones in an item separately from the header, you must
first remove the item from the header billing plan before milestones can be assigned
to it.
All manually set milestones will be deleted when you reassign this item to the header
billing plan. Header data will once again be valid for the item.
23. SAP AG Billing Plan (SD-BIL-IV)
Header Billing Plans in Periodic Billing
April 2001 23
Header Billing Plans in Periodic Billing
In periodic billing, the following functions are carried out exclusively at item level:
· Pricing
· Determining status
· Determining date-from and date-to
For this reason, no billing document value or status appear in the header billing plan.
Changes to validity period
Start and end dates establish the billing validity period and can be determined
automatically using a rule or entered manually. These dates are copied to the item
billing plans. If you change the rule or the manual validity period at header level, the
resulting dates will be copied to the item level.
To maintain different dates at item level, proceed as follows:
If you specify a validity period manually in the Date-from and Date-to fields in the
item billing plan, the system deletes the rule and uses the manual dates from these
two fields to determine the relevant billing dates. The dates which the system
determines at item level remain valid even if you make changes to the header billing
dates. If the manual dates from the Date-from and Date-to fields are deleted, the
system will again use the rule in the billing header to determine billing dates.