Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Periodicals
IMD320
SAP for Media Periodical Sales and
Distribution
SAP AG2009
SAP AG 2009
SAP AG 2009
Some software products marketed by SAP AG and its distributors contain proprietary software
components of other software vendors.
Microsoft, Windows, Excel, Outlook, and PowerPoint are registered trademarks of Microsoft
Corporation.
IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400,
OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5,
System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli,
Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or
registered trademarks of IBM Corporation.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and/or other countries.
Oracle is a registered trademark of Oracle Corporation.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are
trademarks or registered trademarks of Citrix Systems, Inc.
HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C, World Wide
Web Consortium, Massachusetts Institute of Technology.
Java is a registered trademark of Sun Microsystems, Inc.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology
invented and implemented by Netscape.
MaxDB is a trademark of MySQL AB, Sweden.
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and
services mentioned herein as well as their respective logos are trademarks or registered trademarks
of SAP AG in Germany and in several other countries all over the world. All other product and
service names mentioned are the trademarks of their respective companies. Data contained in this
document serves informational purposes only. National product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior written
permission of SAP AG.
This document is a preliminary version and not subject to your license agreement or any other
agreement with SAP. This document contains only intended strategies, developments, and
functionalities of the SAP product and is not intended to be binding upon SAP to any particular
course of business, product strategy, and/or development. Please note that this document is subject
to change and may be changed by SAP at any time without notice.
SAP assumes no responsibility for errors or omissions in this document. SAP does not warrant the
accuracy or completeness of the information, text, graphics, links, or other items contained within
this material. This document is provided without a warranty of any kind, either express or implied,
including but not limited to the implied warranties of merchantability, fitness for a particular
purpose, or non-infringement.
SAP shall have no liability for damages of any kind including without limitation direct, special,
indirect, or consequential damages that may result from the use of these materials. This limitation
shall not apply in cases of intent or gross negligence.
The statutory liability for personal injury and defective products is not affected. SAP has no control
over the information that you may access through the use of hot links contained in these materials
and does not endorse your use of third-party Web pages nor provide any warranty whatsoever
relating to third-party Web pages.
Course Prerequisites
Course Prerequisites:
z SAP01 mySAP.com Overview
z SAPTECH mySAP Basis Technology
z Industry experience in subscription sales and
distribution
Or similar previous experience
Recommended:
z Knowledge of the mySAP.com solutions for Sales
and Distribution and Logistics
SAP AG 2003
Target Audience
Target audience:
z Members of the project team
z Employees in specialist departments
z Consultants
Duration:
z 5 days
SAP AG 2003
Content:
z Course Goals
z Course Goals
z Course Content
z Course Overview Diagram
z Main Business Scenario
z Functions in Subscription Sales and Distribution
SAP AG 2003
SAP AG 2003
SAP AG 2003
Preface
Internet Application
Organization
Components
Customer Interaction
Summary
Center (CIC)
SAP AG 2003
SAP AG 2003
Master data
Materials Promotions Bus. partners Products Geo. structures Carrier routes Truck routes
Orders Planning
HR Payroll HR
FI Financial Accounting FI
SAP AG 2006
IS-M/SD (Industry Solution Media: Sales & Distribution), the component for newspaper and
magazine sales and distribution, contains functions for end-to-end handling of business processes in
the following areas of a media company:
y Sales (sales support, order processing, and billing)
y Logistics (circulation planning, bundling, and shipping)
y Service settlement (commission and home delivery)
Centralized master data forms the basis for integration with Financials, Human Resources, and
Advertising Management.
Data on orders on hand is central to IS-M/SD; all relevant information on sales and basic
information for logistics is stored together with this data.
You are a member of the Implementation Team and are responsible for
testing functions in the R/3 system. You begin testing by logging onto the
R/3 system, navigating in the system and making your user settings.
1-2 Which menu options are displayed in the work area Logistics/ Media Sales and
Distribution/ Periodical Sales and Distribution?
1-4 Find out the transaction code for the Customer Interaction Center screen in the work
area Logistics / Media Sales and Distribution / Periodical Sales and Distribution / Sales
/ Order.
1-6 Which master data can you maintain in the Logistics application Media Sales and
Distribution/ Periodical Sales and Distribution?
1-8 Define the date format in your user profile. Choose the European or American date
format, depending on the scenario you want to work with.
SAP AG IMD320 1-9
SAP AG IMD320 1-10
Solutions
1-3 You can use the menu to call the application or you can enter the relevant transaction
code in the command field.
1-4 Menu:
Logistics Media Sales and Distribution Periodical Sales and Distribution
Sales Order Customer Interaction Center Front Office Front Office
Menu bar:
Extras Technical details
The transaction code is CIC0.
You are a member of the Implementation Team and are responsible for
testing whether the available R/3 tools function correctly.
2-1 Access the Maintain Business Partner screen and choose the button Create Person.
Position the cursor in the Grouping field and call up the help for this field.
2-2 Now call up the value help for the Grouping field. Which groupings exist in the system?
2-1 Menu:
Logistics Media Sales and Distribution Periodical Sales and Distribution
Master Data Business Partner Business Partner (SAP BP) Edit Business
Partner Button Create Person
Position the cursor on the Grouping field and press the F1 key or click on the question
mark in the standard toolbar.
2-2 Position the cursor in the Grouping field and press the F4 key.
CPD Internal Number Assignment One-Time
Cross Media Customer IDES US
Dont use (CRM)
Entertainment Cust IDES US
External number assignment
Internal number assignment
Content:
z Organizational units in the R/3 System and their
relationship to each other
z Overview of the flexible options for recording enterprise-
specific organizational structures
SAP AG 2003
SAP AG 2003
Internet Application
Organization
Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
SAP AG 2003
Controlling area
Valuation area
SAP AG 2003
Client
3 4 2
SAP AG 2003
All organizational units that belong to one client are controlled as a group in business terms. For this
reason, the word "client" is often used as a synonym for a corporate group. For example, standard
charts of accounts are defined at client level.
A corporate group can be defined by the terms "company code" and "business area" from an
accounting viewpoint.
Each company code is an independent balancing unit. Several company codes can use the same
standard chart of accounts.
A business area is a separate unit for which an internal balance and profit and loss statement can be
created. Business areas are defined across company codes, and you must determine for each
company code whether or not business area processing is necessary. The business area can be
determined automatically in postings from Sales and Distribution.
Sales
organization
USA
Distribution channels
SAP AG 2003
To ensure best possible market penetration, Media Sales and Distribution uses a variety of
distribution channels. Typical examples are wholesale, retail and direct sales.
A customer can be supplied by means of a number of distribution channels within one sales
organization.
The publication master data relevant to sales (such as prices) can be different for each sales
organization and distribution channel.
Sales
organization
USA
Product divisions
Newspapers Magazines
SAP AG 2003
Sales Organization
Sales Sales
organization organization
Distribution Division
Channel USA DE
SAP AG 2003
SAP AG 2003
The physical aspects of the organization of business development and sales are reproduced by means
of sales offices, sales groups and salespersons.
The sales office is used to define the geographical areas in your internal organization. The sales
office could be a plant or a branch office. Each sales office is assigned to one or more sales areas.
The staff employed at a sales office are recorded by means of sales groups. For example, sales
groups can be created for individual product divisions. Each sales group is assigned to a sales office.
Each sales group is assigned salespersons. This assignment is made in the salesperson's user master
record.
Client
Company Company
code 1 code 2
Plant 2
Plant 1
New Media,
New York
Plant 3
SAP AG 2003
The goods flow in publishing distribution begins at the locations where production and shipping take
place. These locations are reproduced in the system by means of plants.
A plant can either be the location at which production or planning take place or simply a group of
one or more locations near each other geographically and grouped for distribution.
Each plant is assigned to a company code.
Client
Company Company
code 1 code 2
Sales Sales Sales
organization organization organization
USA USA USA
SAP AG 2003
The plants relevant for sales and distribution are defined for each sales organization according to the
distribution channel. This means that a sales organization can sell publications from a number of
plants.
A plant can be assigned to more than one sales organization at the same time. All the sales
organizations assigned to a plant can sell products from this plant.
The assignment of the distribution channel allows you to classify the plants in a sales organization
from the point of view of sales and distribution. This means that the direct sales distribution channel
can be allowed for some plants and not allowed for others.
When maintaining delivery viability sets, the system checks the assignment of the plant to the
distribution channel.
Client
Company Company
code 1 code 2
Purchasing Purchasing
organization organization
1 2
Purchasing
Central purchasing department organization
3
SAP AG 2003
A purchasing organization is an organizational unit that is responsible for purchasing materials and
services.
Each purchasing organization is assigned to a company code. The company code represents the legal
entity that is legally responsible for all purchasing activities performed by the purchasing
organization. Home delivery and commission settlement in IS-M/SD are also performed on behalf of
this legal entity.
A purchasing organization can act for different sales areas in IS-M/SD.
IS-M
PS
PM WF
HR IS-M SD
FI
M/SD M/AM
SAP AG 2006
Provides a structured
procedure for system Provides tools for
implementation and system settings
enhancement Customizing
IMG
SAP AG 2003
Company-specific values
Customizing
tables
SAP AG 2003
Activity 1
SAP Reference IMG
Activity n Countries, Countries,
components components
Unit 2
Activity 1
Project Project
IMG 1 IMG n
Update, Attributes
Delta (e.g.
Activity n mandatory,
optional)
Unit n
Activity 1 Release Views of
Activity n
IMG IMG project
SAP AG 2003
The Implementation Guide (IMG) is the central Customizing tool. It performs the work steps
required online.
y For implementation of the R/3 System
y For subsequent changes
y For system upgrades
The SAP Reference IMG (Contains all current Customizing activities) is supplied.
Implementation projects (project IMGs) are generated on the basis of the reference IMG.
A release-specific IMG can be generated from the project IMG for release updated (link to release
notes).
y Delta IMGs contain all activities required to implement new functions.
y Upgrade IMGs contain all activities required to implement modified, enhanced or corrected
functions.
Attributes for individual IMG documents can be used to generate different views of the projct IMG
(such as required field, optional field, critical, non-critical activities).
Roadmap
(Procedure model)
Countries
Application
components USA
Germany
France
...
Project IMG
Financial Accounting
Mandatory Critical
Optional Fiscal year
Not critical
Not required ...
...
SAP AG 2003
Global Settings
Countries
Languages
Currencies
Units of measurement
Calendar
Organizational Structure
Accounting
Logistics
Sales and Distribution
Assignments
Media Company
General settings
Basic functions
Master data
Media Sales and Distribution
Periodical Sales and
Distribution
Advertising Management
Tools
SAP AG 2006
Represent
company
structure
SAP AG 2003
SAP AG 2003
Content:
z Business partner roles in subscription sales &
distribution
z Structure of the business partner master
z Central address management
z Employment relationships between service providers
and service companies
z Business Partner Customizing
SAP AG 2003
SAP AG 2003
Internet Application
Organization
Components
Geographical structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Unit Summary
Center (CIC)
SAP AG 2003
SAP AG 2003
Service
company
Carrier
Commission
recipient
Household
Business
partner roles
Researcher Field
collector
Sales customer
(subscriber) Publisher
SAP AG 2003
The definition of a business partner role is based on a business process. The attributes of the
business partner role are defined according to the requirements derived from this process.
You can create a business partner in a variety of business partner roles and have them take on
other roles in the course of the business relationship. Data entered once is used for each new role.
This saves you having to repeat data entry for each new role and avoids inconsistencies.
Centralized business partner data provides you with a unified view of all business transactions and
relationships in which a business partner is involved.
Central data on the business partner, in particular addresses, can be used for the different business
transactions. Any number of addresses can exist over the course of time for a business partner.
It is also possible to record different data for different roles
Service Carrier
Sales
Employment relationship
customer company
Researcher
Commission
recipient
Field
collector
SAP AG 2003
The business partner roles are structured according to the type of business relationship:
y This structure is based on the role played by the business partner, either that of a customer or of
a service provider (vendor).
y Further classifications can be made for the business partner in every customer or vendor role.
The customer business partner role in subscription sales and distribution is the sales customer. Sales
customers are subscribers or others who purchase periodicals (newspapers or magazines) and whose
payment goes directly to the publisher.
Customer business partners are further classified according to their function as ship-to party, sold-to
party, bill-to party and payer in the order.
The following service provider functions are available in subscription sales and distribution:
y Carrier
y Researcher
y Field collector
y Commission Recipient
y Service Company
Carriers, researchers, field collectors and commission recipients have an employment relationship
with a service company.
SAP AG 2003
Business partners can be classified for special roles using indicators (in the general data on the
business partner).
Examples of the use of classifying business partner roles in the order:
y The internal business partner is an organizational unit of the company.
y Third-party delivery orders can only be created for an external publisher.
y A social facility, such as a hospital, can be sent transfers.
SAP AG 2003
SAP SAP
Banking Utilities
If you use the SAP business partner, you can group business partner data that is distributed among
several systems within a company.
For example, this allows you to identify potential new contracts in a customer relationship.
Business
partner
Business
Data
Toolset
SAP AG 2006
The term "SAP business partner" has the following two meanings:
Administration of central business partner data
Open technical infrastructure
y You can use the Business Data Toolset to adjust master data without modifications
y Customers use the same tool as SAP
As of Release 4.63, you can archive SAP business partners in IS-M. Archiving includes the following
functions:
Archiving of relevant business partner data
Deletion of archived data
It is not possible at present to reload archived data.
As of SAP ECC Media Extension 6.0, you can use the Easy Enhancement Workbench (EEW) to
make enhancements to the SAP Business Partner quickly and easily.
y You can use the EEW to make enhancements to the general business partner data.
y You cannot make enhancements to company code or sales area data using the EEW.
SAP BP (IS-M)
Role- Sales
Central Bank details with Payment
specific area
data additional data cards
data data
FI / SD
Customer Vendor
SAP AG 2003
IS-M-specific fields have been added to the data structure for the SAP business partner. These fields
include role-specific data (for example, on the service company or carrier) and sales area-specific
data.
Fields from the customer master record are integrated in dialog maintenance of the SAP business
partner.
You can preassign entries to the customer and vendor fields
y using a template vendor
y using a function module
You must preassign entries to the fields using a template technique when creating a vendor role.
Cross-application data:
Identifying data (category, type, grouping)
Name and address
Personal or organization data
Bank details and payment cards
SAP AG 2003
SAP AG 2003
General data
Change documents
e.g. "Internal BP"
indicator
Business Additional data on
Role-specific data partner bank details
Service company
Data specific to Collection
authorization data
Carrier
subscription
Intended purpose
Commission recipient
sales
Sales area
assignment (optional)
SAP AG 2003
The master data on the SAP business partner contains the following data specific to subscription
sales and distribution:
General data
y e.g. "Internal BP" indicator
Role-specific data on the following business partner roles:
y Service Company
y Carrier
y Commission Recipient
Additional data on bank details
y Collection authorization data
y Intended purpose
y Sales area assignment (optional)
Change documents
Sales area-specific and accounting-specific data from the customer master in the SAP component
SD.
Attributes:
Purchasing
Relationship Manager
Category: "belongs to
company" Authorized
from: 01.01.2003 Signatory
Relationship
Category: "is married to"
from: 25.09.2001
SAP AG 2003
You can record relationships between two business partners that are relevant for business. The
relationship is defined by the relationship category.
You can assign attributes to a relationship, which allows you to avoid redundant data retention.
Example: Your business partner Mr. Huber is Purchasing Manager with Company A and MRP
Controller with company B. You can record his attributes - for example, department, function,
decision authority - in each of these roles with the relationship to the company in question
(=business partner). If it was not possible to assign attributes to a relationship, you would have to
create the business partner twice in order to assign the appropriate data in the correct role.
You can limit the validity period of a relationship by specifying a start and end date. This gives you
an overview of the periods during which certain business partners were, for example, contact
persons at a company.
Select Adjust
maintenance maintenance
screens dialog
SAP AG 2003
Maintenance dialog with tab pages (selection of maintenance screens when you access maintenance)
Various fields offered for maintenance according to the business partner category
(e.g. name and address, personal and organization data)
Adjustment of maintenance dialog
y You can integrate company-specific fields from SAP tables or from company-specific tables in
data maintenance
y You can enhance existing screens or add new screens to the screen sequence
y You can adjust the maintenance dialog via Drag&Drop using the Visual Configuration Tool
(VCT)
Enhancements and changes are not overwritten by upgrades.
Display and hide fields (the field status is defined for each field group in Customizing, e.g. required,
optional, display, hide)
The field status is defined for various field modification criteria
y The settings for these criteria are combined
y You can add further criteria
You can define default customer, vendor and media-specific business partner data using the
Business Add-In ISM_BP_DEFAULT_VALUES.
Ship-to party
Relocation
Bill-to party
SAP AG 2003
Central address management is used to record the addresses of IS-M business partners (or SAP
business partners) with validity periods.
When you record addresses, the system checks your entries against the postal units (city, street,
postal code).
You can record different address variants in a business partner's address data, for example:
Standard address: postal code, city, street
P.O. box address: P.O. boxes are grouped under one postal code
Company address (major customer postal code): the postal code is reserved for one company
Alternative addresses for an order-related partner role:
For example: the customer Newsstand Chain Broadway, Corp. (retailer) has the ship-to party and
bill-to party address 7 Steward Street. On January 1st, 2001, the company's goods receipt moves to
the new warehouse building at 2503 Broadway. This changes the ship-to party address, while the
bill-to party address, which is maintained independently (for the business partner role bill-to party),
remains unchanged.
As an alternative to the duplicate check (BAdI) in central address management, you can use the IS-
M duplicate check that was available previously.
Employment Employment
relationship relationship
Employment
Service Service relationships for
Company Company external service
companies are
Employee Employee not recorded in
IS-M/SD.
Employee Employee SC SC
Settlement Settlement Settlement Settlement
SAP AG 2003
In IS-M/SD, services are managed using service companies (SC) and their employees. The service
companies created in the system can have the following statuses depending on their membership in
the media company:
y own service company
y co-administered service company
y external service company
Service providers have an employment relationship with a service company that works for the
media company. Employment relationships can be managed for the service provider roles carrier,
researcher, field collector and commission recipient (sales agent). Settlement of services is
performed according to the type of employment relationship:
y Employment relationship with an owned service company: settlement takes place for each service
provider.
y Employment relationship with a co-administered service company: settlement takes place for
each service company or service provider (employee of the co-administered service company)
y No employment relationship since an external service company performs the services and
manages the data on the service providers itself. Settlement takes place for each external service
company.
Implementation
SAP Business
Partner
SAP AG 2003
The migration tool (see next slide) is not solely used to convert existing business partner data to the
SAP business partner.
During the implementation of mySAP Media, it is also used to set up the tables required for the SAP
business partner.
Create central
data and roles
System exists
("Old" business
partner data) Migration tool
Migration
Fixed sequence
New system of migration
steps
SAP AG 2003
Existing business partners must be migrated before you start using the SAP business partner.
The system creates the central data for the SAP business partner and the corresponding roles
during migration.
Business partner migration is supported by a migration tool.
Migration cannot take place until the IS-M business partner Customizing settings are complete.
The migration tool covers all migration steps and saves the process flow in the correct order.
Migration is not performed during a release upgrade.
Once successful migration has taken place, you can only perform business partner maintenance
using the SAP BP transactions.
SAP AG 2003
1-5 Create an employment relationship for your commission recipient JCR-## with JSC-
##:
1-5-1 Create the employment period: the researcher is a permanent employee with
an unlimited contract as of today.
All the exercises in this unit begin with the following menu path:
Logistics Media Sales and Distribution Periodical Sales and
Distribution Master Data Business Partner
Content:
z Product structure in Subscription Sales and Distribution
z Product synchronization
z Data structure of the media product master
z Subscription-specific data objects (variant type, mix offer,
service type, mix type combination)
z Issue sequence for media product
z Media Product Master Browser
z Mass maintenance of media product master data
z System settings for media product master
SAP AG 2003
SAP AG 2003
Internet
Organization
Application Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Conclusion
Center (CIC)
SAP AG 2003
SAP AG 2003
Media product
Content-related,
geographical or layout-
New Berlin New City Newport Norwood
based variant
Media issue
Actual issue on
publication date New City
New City
New City
IAL
IAL EC
Issue mix EC SP FER
SP FER OF
OF
- Title inserts
- Ad inserts
(e.g. ad pre-prints, CDs)
New City
SAP AG 2003
The media product master contains media-specific fields and screen sequences in addition to the
material master on which it is based. The product data can usually be recorded using the following
objects, which form the following hierarchy in the case of newspapers and magazines:
y Media product family
Organizational data that applies to all the media products that belong to the family.
Example: Organizational data that applies to all the regional issues of a newspaper or all the
forms of publication of a book
y Media product
Business data on all physical units of sale (media issues).
Example: Business data that applies to all copies of a magazine title
y Media issue
Physical unit of sale of the media product that is actually published.
Example: Print edition of a magazine on March 24th, 2003
The issue mix for a media issue includes the title inserts (for example, TV guide) and ad inserts (ad
pre-prints, CDs, product samples) from orders in Advertising Management.
+ =
Issue mix 1
IAL
EC
IAL SP FER
EC O F
SP FER
F
+ O
=
Issue mix 2
SAP AG 2003
Media issue mixes are created by the corresponding function based on existing orders. They contain
the following data:
y Title inserts (based on subscription orders)
y Ad inserts (based on ad insert orders from Advertising Management, for example, ad pre-prints,
CDs, product samples)
Actual Standard
variant type: variant type:
Saturday edition Saturday edition
SAP AG 2003
The issue variant type classifies media issues according to the columns they contain, for example:
Issue variant type Mo Sports
Issue variant type Fr Real Estate
Issue variant type Sa Employment
The Customizing settings for product master data determine which actual issue variant types can be
delivered instead of the standard issue variant types on or around public holidays.
Example: Since Saturday is a public holiday, the Saturday edition is delivered on Friday as the
actual issue variant type instead of the standard issue variant type (Friday edition).
Mix offers
Product mix
SAP AG 2003
The product mix contains data on the hierarchy levels media product (edition) and media product
family (publication) that are relevant to Subscription Sales and Distribution but are not contained in
the media product master.
The data on the product mix complements the master data objects as follows:
y Media product family (publication):
Data referring to subscription orders (shipping for backdated orders, use of copy numbers in the
order), product procedure for monitoring renewal subscriptions, data referring to CO order
account assignment, controls for media issue administration
y Media product (edition):
- Mix type
- Mix type definition
IAL IAL
EC EC
SP FER SP FER
OF OF
SAP AG 2003
Ad insert Insertion
IAL
EC
SP FER
OF
o
es/n
Norwood Y Norwood
Substitution Combination
Daily Paper
Norwood
Mon, +
Wed, Fri
SAP AG 2003
The mix type determines which media issue is combined with a carrying media issue in
Subscription Sales and Distribution.
The concrete definition of individual mix types for a media product is specified in the mix type
definition.
The minimum specification required for a mix type is the statement of whether or not the media
product is to be combined with ad inserts (for example, ad pre-prints). This data must be recorded in
the system before a mix offer can be created.
In addition, you can specify the combination type used to combine further media products in the mix
type definition.
The following combination types are possible:
y Insertion of ad inserts and titles
y Substitution with different media products on dates on which publication does not take place
y Combination with media products that are delivered separately
ue
ss
i ngi
rr y
Ca Media product:
Daily Paper Norwood
Mo Tu We Th Fr Sa
Norwood
Insertion
sert
I n Media product:
TV Magazine
Weekly
magazine
SAP AG 2003
Further media products can be inserted in a media product to which readers subscribe.
Insertion can be limited to certain issue variant types of the media product in question (for example,
always insert in the Friday edition).
You must also specify in the mix type definition whether the inserted media product is a third-party
insert or a publisher's insert, as classified for settlement of postal charges.
ue
i ss
g
rr yin
Ca
Media product:
Daily Paper
Mo Tu We Th Sa
Combination
Norwood
d t
bine oduc Media product:
m r
Co dia p Daily Paper Entertainment & Art
m e
Fr
SAP AG 2003
Further media products can be inserted in a media product to which readers subscribe.
Insertion can be limited to certain issue variant types of the media product in question (for example,
always insert in the Friday edition).
You must also specify in the mix type definition whether the inserted media product is a third-party
insert or a publisher's insert, as classified for settlement of postal charges.
on
l editi Media product:
ca Daily Paper Norwood
Lo
Tu Th Sa
Substitution
Substitution
Substitution
Norwood
n
editio Media product:
c al Daily Paper New City
Lo
Mo We Fr
New City
SAP AG 2003
You can replace a media product with another media product belonging to the same media product
families on days on which the former is not published.
For example, this would mean that a subscriber receives a national edition instead of the local
edition to which they subscribe.
Variant type
Monday
Tuesday
Wednesday
Friday
Saturday
Sunday
SAP AG 2003
You can use the service type to specify which media issues of a media product can be sold
individually or as a subscription (partial or full subscription).
The service type is combined with the mix type to form the mix offer. The mix type defines which
other media product(s) can be purchased together with a media product. Example: ad pre-prints, title
inserts in daily newspapers, etc.
You specify the issue variant types to which the service type applies in the mix type definition.
Mix Offer
Media product Sales document
Media product Norwood Order
270000
Norwood
SAP AG 2003
The mix offer contains the data on the media product that is required in order to create an order
item. The mix offer defines the purchase frequency and delivery type with which a media product
can be sold in a certain mix type.
y The mix type defines which other media product(s) can be purchased together with a media
product.
Example: ad pre-prints, title inserts in daily newspapers, etc.
y The purchase frequency allows you to specify which media issues of a media product can be
sold individually or as a subscription (partial or full subscription).
Example: full subscription for all daily editions or only for the Saturday edition.
You can also exclude certain mix offers for certain order types.
Create entries
Flag
SAP AG 2006
The issue sequence is used to define the order in which issues of a media product are delivered to
customers. Media product master data is synchronized with the product master in Periodical Sales
and Distribution (publication, edition, issue) on the basis of the issue sequence. Issues created
manually must be entered in the issue sequence so that they are included in synchronization. Issues
that are not included in the issue sequence are not synchronized.
You can have the system create entries in an issue sequence automatically for the selection period
specified on the initial screen, using a simple rule. This is done based on data taken from the
frequency rule and the factory calendar from the media product.
You can also select publication dates using the calendar. This is particularly recommended when
dealing with products published at irregular intervals or products for which it is difficult to create a
publication rule.
Once the issue sequence has been created automatically, you can edit the entries, for example,
changing issue variant types, or adding and deleting entries.
Status of the media issues in the issue sequence:
y Planned (red traffic light symbol): The new entries in the issue sequence created using a rule
contain planned media issues. Although the entries contain media issue keys (material numbers)
that have been generated automatically, master records do not yet exist.
y Flagged (yellow traffic light symbol): To create media issue master records for the planned
entries in the issue sequence, you must first flag the entries in question. The system then creates
the desired master records automatically when you save the issue sequence.
y Active (green traffic light symbol)
Master records are created (in the material master) for active media issues.
MIssue 1
Change Media Product
MIssue 2 Basic Media Data 1 Basic Media Data 2
MIssue 3 Material MProduct
SAP AG 2003
You can use the media product master browser to display and maintain the media product master
hierarchies. The data is displayed as a hierarchical structure.
You can access editing functions for master data on the objects displayed in the media product
master hierarchy.
You can also create further objects on the initial hierarchy level and on the lower levels. For
example, if you accessed the list by specifying a media product, you can only create media products
and media issues from the list but no media product families.
Select Change
records field values
Changed
values
MARA (General material data)
MARC (Plant data on material)
MVKE (Sales data on material)
Log
SAP AG 2003
The mass maintenance tool in the SAP System allows you to change master data fields for selected
media product master data easily and quickly.
The following data is relevant for the mass maintenance function for the media product master:
y Object type BUS1001
y Tables
- MARA (General material data)
- MARC (Plant data on material)
- MVKE (Sales data on material)
y Selection criteria
- Material (object in media product master)
- Plant
- Sales organization, distribution channel
You need the authorization B_MASSMAIN experience with mass data maintenance in order to be
able to use the function.
You can create variants for use when you execute the function.
Synchronization
Mix alternatives
Media
Media Media
product Media issue
product issue
family
Insert 1
Media product master Issue
(enhanced material master) sequence Insert 2
Insert 3
SAP AG 2003
As an alternative to the product master in periodical sales and distribution, the media product master
contains maintenance functions for media product master data that are integrated with the material
master in the MM (Materials Management) component and that can be used to record master data on
a variety of media products, such as newspapers, magazines, CDs and books.
The media product master contains media-specific fields and screen sequences in addition to the
material master on which it is based. The product data can usually be recorded using the following
objects, which form the following hierarchy like the periodical product master in the case of
newspapers and magazines:
Media product family (corresponds to the publication)
Media product (corresponds to the edition)
Media issue (corresponds to the issue)
You can synchronize the objects in the media product master with those in the periodical product
master. To do this, you must activate product synchronization in Customizing. In product
synchronization, product master data is created and changed using the maintenance functions for
media product master data and the system maintains the corresponding objects in the periodical
product master automatically in parallel.
Mo Tu We Th Fr Sa Su
1 2 3 4
5 6 7 8 9 10 11
12 13 14 16 17 18 19
20 21 22 23 24 25 26
27 28 29 29 30 31
SAP AG 2003
The function Move media issue changes the publication date of a media issue that is synchronized
with the periodical product master.
When you move the publication date of a media issue, the system also moves production units
(M/AM), M/SD orders, and M/AM orders.
You can define how the system is to respond to changes to production units and M/SD and M/AM
orders in Customizing.
Grid Mo Tu We Th Fr Sa Su
Indiv. period 1 2 3 4 5 6 7
Period date 01/01 01/02 01/03 01/04 01/05 01/06 01/07
SAP AG 2003
The frequency rule defines a period after which the publication frequency of an edition is repeated.
This period is termed a repetition period.
This repetition period is subdivided into one or more time intervals of the same length, termed grids.
These grids represent the smallest unit in which an edition can be published.
Example:
y Daily paper Week / day
y Monthly magazine Year / month
y Monthly magazine 1/1 Monthly publication
y Monthly magazine 2/1 Publication every two months
y Monthly magazine 1/2 Publication twice a month
You can make a grid larger or smaller by specifying a fraction (numerator = grid factor,
denominator = grid divider).
Implementation
of IS-M
Media Product
SAP AG 2003
You must make the following settings to implement the media product master in mySAP Media:
y Settings for the media product master
- Configuration of the material master (screen sequences, field selection)
- Basic settings (for example, output format of material number, company codes)
- Settings for central and Media-specific fields
- Allowed business partner roles
- Settings specific to Sales and Distribution: Code types, BOM item categories for each
material type, control parameters for the issue sequence
y Settings for the periodical product master
- Product determination procedures for renewals
- Content categories
- Frequencies
- Service types and service type compositions
- Issue variant types
- Delivery address alternation
Issue
Publication Edition Issue
mix
Synchronization
Mix alternatives
Media
Media Media
product Media issue
product issue
family
Insert 1
Media product master Delivery
(enhanced material master) sequence Insert 2
Insert 3
SAP AG 2003
As of Release 4.62, you can use the media product master (MM material master) as an alternative to
the periodical product master. A migration tool is available with Release 4.63 for customers who
would like to use the media product master.
Migration of M/SD products to the media product involves several steps for each publication.
The publication and editions are migrated manually. This means you need to create the media
product family (for the publication) and the media products (for the editions) using corresponding
media product transactions.
Issues are migrated automatically. A central migration program deletes the issues from the migration
date onward and creates (planned) issue sequences for all the media products, copying the attributes
from the issues.
The media issue numbers and template issues must then be added to these issue sequences.
Once maintenance of the issue sequence is complete, media issue generation is started manually
from issue sequence maintenance.
SAP AG 2003
Wireless World News New York adds a local daily newspaper to its range.
The daily newspaper has a regional edition. It is your job to create the
new media product.
1-2 Create a local edition New Hampton (JM##) for the media product family JMH*.
1-2-1 Use the distribution channel Direct Sales for your media product.
1-2-2 Use the short text JM##. Assign the local edition to your media product
family (JMH*). Please note that your media product is relevant for circulation
auditing.
1-2-3 JM## is also created in the base unit of measure Copies and with the division
J8. The media product is subject to half the tax rate in Germany and is tax-
free in the USA.
1-2-4 Its publication frequency is daily, according to the IDES US factory calendar.
1-2-5 Local edition JM## is available as mix type 01 with ad pre-prints and as mix
type 10 without ad pre-prints. Create these mix types for your media product.
1-3 Generate media issues for media product JM## of the daily newspaper JMH*.
1-3-1 Create a template media issue (JM##_TEMP) of media product JM## for
plant ME02, sales organization M02, and distribution channel J6.
1-3-2 Assign your template to media product JM##. The template media issue is a
local daily newspaper whose publication date is the first day of the previous
year. This is both the first issue of the year and the first copy number.
1-3-3 The physical data on the newspaper is as follows:
Format 53.3x33, extent 20 pages, thickness 0.025 inches, paper weight 0.046
Oz/Ft
1-3-4 Use the current weekday for the standard issue variant type and the actual
issue variant type.
1-3-5 The company newspaper (division J8) is managed in the base unit of measure
Copies and belongs to material group 019 for Media.
1-3-6 The template is eligible for cash discounts and returns are allowed. The
return period begins today and is unlimited. The product is subject to half the
tax rate in Germany and is tax-free in the USA.
1-3-7 An availability check is performed according to the day's requirements. Your
template is to be loaded manually and transported loose on a truck.
1-3-8 Create an issue sequence for your media product JM## for the current
calendar year and the following year.
1-3-9 Create a rule for creating default values (button Assign Defaults). Maintain the
rule for Monday through Sunday so that the standard issue variant type
corresponds to the weekday in question. Issues should also be published on
public holidays. Use media issue JM##_TEMP, which you created in 1-3-1, as
a template issue. Check the rule and generate the default values for the issue
sequence.
1-3-10 Check the issue sequence generated. You can now make changes to its name or
delete media issues. Select all the entries and have the system check them, so
that they can be created later if need be. Save the issue sequence.
Information for instructor:
1. Once the exercises for the media product master have been completed, please
create the billing frequencies for the new publications in Customizing:
Periodical Sales and Distribution (Subscriptions) Billing General
Settings Maintain Billing Procedures for Subscriptions
SOrg. DChl Publicn BF DF PF
ME02 J6 JMH* 04 4W
ME02 J6 JMH* 26 4W
ME02 J6 JMH* 52 X 4W
SAP AG IMD320 4-26
2. Please also maintain the address alternation offer for the new publications so
that you will be able to do the exercise on delivery address alternation in the
Sales unit.
Master Data Product Publication (Periodical Product) Edition
Purchase Define Address Alternation Groups Address Alternation Offer
(in the dialog structure)
Choose New Entries.
SDTy. Serv. Type Publicn AddAltGrp Bill.Level
ABO FD JMH* 2 Main Item
SUBE FD JMH* 2 Main Item
1-6 What are the names of the function modules used to define the copy and material
numbers when media issues are generated from the delivery sequence?
1.____________________________________________________
2.____________________________________________________
All the exercises in this unit for maintaining master data begin with the
following menu path:
Logistics Media Sales and Distribution Periodical Sales and
Distribution Master Data
All the exercises for checking system settings begin with the following
menu path:
Tools AcceleratedSAP IMG Project Administration SAP
Reference IMG SAP Media
1-3 Generate media issues for media product family JMH* and media product JM##
1-3-1 Media Product Master Media Issue Individual Maintenance Create
Field name or data type Values
Material JM##_TEMP
Industry Sector Media
Material Type Media Issue News/Mag
Select View(s): Basic media data 1
Physical Characteristics
Media Issue Sales and Distrib.
Basic Material Data
Media Issue Sales and Distrib. 1
Sales: General/Plant Data
Organizational Levels
Field name or data type Values
Plant ME20
Sales Organization ME02
Distribution Channel J6
1-6 Master Data Product Media Product Master Media Issue Generation
Define Control Parameters for Issue Sequence
Function Module for Copy Number: Z_ISM_DELIV_SEQUENCE_COPYNR_SE
Function Module for Material Number: Z_ISM_DELIV_SEQUENCE_MATNR_SET
Content:
z Geographical structures
Master data on postal units, geographical units and
carrier routes
Recording geographical structures in Media Sales and
Distribution
z Change Management
General information on Change Management
Change number
Change status of change numbers
Postal change service
SAP AG 2003
SAP AG 2003
Internet
Organization
Application Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Conclusion
Center (CIC)
SAP AG 2003
SAP AG 2003
SAP AG 2006
The geographical structure of the distribution area affects the following areas in Media Sales and
Distribution:
y Sales (controls order entry)
y Shipping (controls shipping functions)
y Settlement (controls service settlement)
Level 0 CRte 04
New Berlin South
Carrier route
New Berlin
Level 1 GU-04 South
New Berlin South
A carrier route represents a distribution area in which media products (titles and ad inserts such as
ad pre-prints) are delivered by carriers. From a technical perspective, a carrier route is made up of
geographical units or lower level carrier routes.
The diagram illustrates how a carrier route can be made up of a hierarchy of geographical units
(GU-04 is made up of GU-04B and GU-04A). Each (lower level) geographical unit is made up of
postal units, such as streets or street sections.
The geographical structure of carrier routes is not determined by the assignment of the streets to
postal codes but rather by the actual physical structure of the carrier route.
When a carrier route structure is recorded in the system, each assignment is given a validity period.
Carrier route
New Berlin South A
Weekend
Carrier 1
Carrier 1
SAP AG 2003
As a result of weekend subscriptions and the increased size of individual weekend editions, the
home delivery quantity at the weekend is much greater than on working days during the week. This
means the number of carriers and the carrier route structure must be defined differently for
weekends than for working days.
You can use weekday-specific carrier route assignments to map different carrier route structures for
individual weekdays or parts of weeks.
Weekday-specific distinctions between carrier route structures are only possible for delivery types
for home delivery.
Carrier route
Address
Residential area
1 12 29
State Highway 8
Town center
53 78
Red Mill Rd
Martin Rd
20
Norton Rd
461 357
Martin Rd
SAP AG 2003
Geographical structures of actual geographical distribution areas are mapped in the system using
the following structuring elements:
Carrier routes
Geographical units
Postal units (streets, street sections, postal codes etc.)
Postal units are grouped together to form geographical units.
Carrier routes are made up of geographical units. Carrier routes define geographical areas in which
media products (newspapers, magazines, ad inserts) are delivered.
The system can use the postal units to assign each address uniquely to a geographical unit or carrier
route.
New Berlin
GU-04B
1 12 29
State Highway 8
GU-04A
53 78
Red Mill Rd
20
Norton Rd
Martin Rd
461 357
Martin Rd
SAP AG 2003
A geographical unit maps an area based on postal units, and is used as the basis for geographical
structuring.
Geographical units can also be made up of other, smaller geographical units.
Carrier routes are set up using geographical units.
The geographical unit GU-04B covers the area containing the following street:
y State Highway 8
The geographical unit GU-04A covers the area containing the following streets and street sections:
y Red Mill Rd
y 301-399 Martin Rd
y 401-499 Martin Rd
y Norton Rd
SAP AG 2003
Structure of geographical unit GU-04A (see previous slide) from postal units.
SAP AG 2003
Geographical units (such as city districts) can also be subordinated to other geographical units (such
as cities).
SAP AG 2003
A city is assigned to a country. A city can comprise a number of city districts. City districts serve as
input help when recording addresses. If a street name exists more than once in one city, the city
district can be used to identify the street.
A delivery-related postal code is assigned all the cities to which it applies. P.O. box, major customer
and major customer group postal codes are assigned to one city only.
Each street is assigned to one postal code, one city and one city district.
The house number range identifier indicates which house number ranges belong to this street:
y all house numbers = blank
y odd house numbers =1
y even house numbers = 2
The street can be restricted to a certain house number interval.
St St St St St St
SAP AG 2003
New Berlin
4032667 4032668
SAP AG 2003
Postal Geo.
units structures
Delivery
Change Truck route-
viability sets edition
Management assgmt
Truck route-
Unloading unl. point
viability sets
assgmt
SAP AG 2003
Changes that are linked (for example, creation of a new carrier route, creation of the corresponding
delivery viability set, creation of unloading viability sets and truck routes) are edited under one
change number.
The validity period of a change number limits the validity of structural changes.
You can define which objects are to be edited with a change number in the planning data for the
change number.
You can use the search function to determine which change numbers exist in the system and which
changes are related to the change numbers.
- Addresses affected
- Delivery viability sets affected
SAP AG 2003
A change number is a key used to group changes to geographical structures and master data
(distribution, organizational structure) logically, to ensure consistency.
When you change geographical structures and distribution master data, you must specify a change
number in the system. The system assigns change numbers sequentially from the internal number
range defined for this purpose in Customizing.
The validity period of the change number applies to all changes made and all objects added using
this number. The valid-from date must be later than the current date. Default setting: tomorrow's
date (can be moved into the future). If you leave the valid-to date blank, the system enters
12/31/9999.
The change status (in process, checked, or released) is displayed in the master data on the change
number. If the change number is used to make changes to postal units, the status is also displayed in
the postal change service (postal data processed, structures updated, addresses updated).
Specific to user: The change number and changes can only be processed by the user who created the
change number.
Optimize delivery viability: When the change number is released, the system executes delivery
viability optimization according to predefined rules.
Release scheduled: The change number can be checked and released in background processing by
report RJSFREI2.
You can restrict the order lock for change number release to orders with addresses or delivery
viability sets that are affected by the changed.
Step in Status of
Change Management change number
Process In process
Check Checked
Release Released
SAP AG 2003
Changes made in Change Management are not activated for processing immediately (planning
status).
All changes made need to be checked first. If this check run encounters errors, you must access
processing again to correct them. When no more errors are found, the changes can be released for
operative processing.
A change number can have the following statuses:
y In process
y Checked
y Released
Carrier Carrier
route 1 route 1
Geo 1 Geo 1
Release change
number
Validity period
11/24/2001 12/31/9999
SAP AG 2003
The change number determines the validity period of the change. This means changes can be
planned in advance.
The system checks the consistency of the structure that has been changed before it is released.
Geographical unit 13 is assigned to geographical unit 1 at a lower level for the key date 11/24/2001.
Order 4711
Orders
Orders on hand
Release
change number
SAP AG 2003
If geographical structures or delivery viability sets are edited using a change number, the changes
can affect the delivery viability of orders. The following cases may apply:
y Delivery is still viable for orders
- Example: A subscriber's delivery address moves from one carrier route to another. The system
makes this change automatically.
y Delivery is no longer viable for orders
- Example: A subscriber's address is no longer on the carrier route and the order can no longer
be supplied by home delivery. This change cannot be made automatically. A clerk must
choose the delivery type that is to be used in the future, for example post (which would mean
that the delivery type needs to be changed to postal shipping). The orders to be edited
manually are forwarded to the clerks responsible by means of an SAP workflow.
Postal
change
service
SAP AG 2003
The postal change service is based on the postal data for the country in question, which is imported
to the system by a program designed for this purpose.
The postal change service involves a sequence of steps aimed at ensuring the consistency of the
structures and addresses when changes are made to postal units.
The postal change service is fully connected to Change Management. The following rules apply:
y Every change number that you use to maintain postal units in the postal client belongs to the
postal change service.
y The Change Management functions (analyze, delete, move date, check, release) are available for
change numbers that belong to the postal change service.
y A fixed sequence of steps is defined for updating data in the postal change service.
SAP AG 2003
The steps in the postal change service can only be processed in a fixed sequence.
Each step changes the status of the change number (in the postal change service). The status can
only move up one step at a time.
Structures updated
Change number
checked and released
Structures updated Structures updated
SAP AG 2003
Postal data can only be maintained from a client specified beforehand (postal client or master
client; defined in Customizing).
If several clients exist, you must also execute the postal change service in the dependent clients
(slave clients).
Procedure:
1. Edit postal data in master client
2. Update structure data in master client
3. Check and release change number in master client
4. Update addresses in master client (optional)
5. Update structures in the slave clients (the change number is created automatically during a live
run, using the change number from the master client as a template).
6. Update addresses in slave clients
y Once the change service has been executed in the master and in all slave clients, you can delete
the entry in status management. The change records are retained until the valid-from date for
the (master) change number is reached.
SAP AG 2003
Status management in the postal change service provides information on activities that have already
been performed, as well as on necessary follow-on activities.
You can trigger all the functions in the postal change service from status management (in the
relevant client - see also Multi-Client Capability).
Implementation
of IS-M Structures
and Change
Management
SAP AG 2003
SAP AG 2003
1-2 Create the following geographical units for the city of New Hampton (New York):
1-2-1 GU1-##, name: Milo Rd Group ##, type: Street
1-2-2 GU2-##, name: Bailey Rd Group ##, type: Street
1-2-3 GU3-##, name: Lynch Ave Group ##, type: Street
1-3 Assign the streets to the geographical units GU1-##, GU2-##, and GU3-##.
Note down your change number:___________________
Select the higher level object and choose Assign at Lower Level.
Call the <F4> help for the Street Number field and enter the city and street name,
country key US and region NY as search criteria. Hit <Enter> to display the hitlist.
Street numbers for Milo Rd: 3038231 and 3038232
Copy the assignment.
When you save the assignment, the system displays the following message:
Assignments to object GU1-## modified
You can use the change number you have created when creating further
assignments for geographical units.
Content:
z Truck routes and links between them and other truck
routes, editions, unloading points etc.
z Unloading points
z Delivery viability sets
z Unloading viability sets
z Shipping schedules for postal shipping
SAP AG 2003
SAP AG 2003
Internet
Organization
Application Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Conclusion
Center (CIC)
SAP AG 2003
SAP AG 2003
Address : 1 Ashley St
13668 Norwood
Location: In front of garage
SAP AG 2006
Carrier route 1
Ed.2
Ed.1
Unloading point 1
Truck route 1
(Morning round)
Truck route
contract
July
Mo TuWe Th Fr Sa Su
1 2 3 4
5 6 7 8 9 10 11
Ed.1 12 13 14 16 17 18 19
20 21 22 23 24 25 26
27 28 29 29 30 31
SAP AG 2003
Truck routes are scheduled for transporting products to distribution areas (see the unit Geographical
Structures). The following data is recorded in the system so that you can use a truck route:
y Master data on truck route (departure time, factory calendar etc.)
y Vehicle type (truck route contract)
y Sequence of unloading points served by the truck route
y Assignment of the editions transported by the truck route
y Generation rule and generation trigger for generating daily truck routes
The truck route data is recorded for each specific shipping date. For this purpose, generation rules
are used to create daily truck routes. The daily truck route is used to record all actual data for a
specific date and changes with regard to planning data.
Each truck route is assigned to a delivery round (e.g. morning round, night round). This determines
the time of day at which the truck route is run.
Unloading point 1
Truck route 1
Ed.2 Ed.2
Ed.1 Ed.1 Ed.1 Ed.1
Truck Truck
Ed.2 route 2 route 3
Ed.1
Ed.1
SAP AG 2003
You can set up assignments between truck routes in truck route hierarchy processing. The following
assignments are possible:
y Trunk route assignment(s)
You assign lower level truck routes (trunk routes) to a (main) truck route. The main truck route
serves the trunk routes.
y Split route assignments (not included in the above diagram)
You assign split routes to a higher level truck route. This means you can make the best possible
use of the loading capacity of the truck routes (or rather, of the vehicles assigned) when the
delivery quantities vary.
y Example: Normally, only one split route is run, but on days with an unusually heavy load, the
delivery quantity is split between two split routes.
To ensure that the data in the system is consistent, route hierarchy definition takes place in Change
Management.
Frequency rule
Mo Tu We Th Fr Sa Su
1 2 3 4
Availability time 21:00 5 6 7 8 9 10 11
12 13 14 16 17 18 19
Departure time 23:30 20 21 22 23 24 25 26
27 28 29 29 30 31
SAP AG 2003
Planned times are copied into daily truck routes. The times can then be changed there for specific
dates.
You can use the truck route type to group truck routes for exceptional situations.
For example:
Truck route type Public holiday. On the day before a public holiday, truck routes other than the
regular ones are run. These are marked as truck route type Public holiday.
The frequency rule defines whether a route is to run daily, weekly or monthly.
Loading weight
SAP AG 2003
A truck route is only run on a shipping date if a daily route has been created for it for the shipping
date.
Planned times are copied into daily routes. The times can then be changed there for specific dates.
In addition, actual times are maintained for the daily route.
The loading weight allowed for a route is determined from the vehicle type. The vehicle type is
assigned to the truck route in the route contract.
March 1 March 7
Gen.
trigger
Generation rule:
all weekdays except Sunday
Truck route
March Generation
Mo Tu We Th Fr Sa Su
1 2 3 4
5 6 7 8 9 10 11
12 13 14 16
20 21 22 23
27 28 29 29
17
24
30
18
25
31
19
26 Daily routes
TH FR SA SU MO TU
March 1 March 2 March 3 March 4 March 5 March 6
SAP AG 2003
Ind.
Period GTrRte BefPH OnPH 1AftPH 2AftPH
1 - Mo
2 - Tu X X X X
3 - We X X X X
4 - Th X X X X
5 - Fr X X X X
6 - Sa
7 - Su X X X X
Mo Tu We Th Fr Sa Su
Daily
01/02 01/03 01/04 01/05 01/07
routes
SAP AG 2006
01/01 01/07
t
2001
MoTuWeTh Fr Sa Su
1 2 3 4
Generation
5 6 7 8 9 10 11
12 13 14 16 17 18 19
trigger
20 21 22 23 24 25 26
27 28 29 29 30 31
SAP AG 2003
In the generation trigger, you specify a period in which daily routes are to be created for a truck
route.
The status of the generation trigger controls whether or not generation is taking place for the first
time and whether daily routes are to be deleted.
If you want to create daily routes manually within a generation trigger period, you must set the
generation status to Manual maintenance.
If you set a lock date, generation does not take place until after this date.
You must also specify how existing daily routes are to be processed for each generation trigger:
y Copy existing daily routes
y Replace existing daily routes with new ones
y Delete existing daily routes
SAP AG 2003
You can use the truck route type to group truck routes according to various characteristics.
For example:
On the day before a public holiday, special public holiday routes are run instead of the truck routes
that apply to normal working days. Each of these truck routes has its own unloading point sequence
and truck route-edition assignment. The truck routes are grouped in a Public holiday truck route
type. You create daily routes manually for 12/24/2001. You want to run exactly the same truck
routes a year later, on 12/24/2002. You can generate the daily routes for 12/24/2002 manually, with
reference to the truck route type Public holiday route.
Unloading point 1
Unloading point 2
Loading point - plant
Unloading point 3
The unloading point sequence lists the unloading points in the order in which they are served by
the truck route.
Unloading point sequences are maintained in Change Management.
Maintenance functions for unloading point sequences:
y Insert, assign at lower level
y Terminate a truck route-unloading point assignment. The unloading point is then no longer
served by the truck route.
y Suspend a truck route-unloading point assignment. The unloading point is then not served by the
truck route for a certain period.
y Reassign an unloading point from one truck route to another or within a truck route.
y Change the sequence in which an unloading point is served by a truck route by reassigning the
unloading point within a truck route.
SAP AG 2003
The truck route-edition assignment determines which edition is transported by a truck route.
It is maintained in change management and thus for a certain period, which is determined by the
change number.
You must specify the publication and the edition for publications of the type title. You can enter
either the publication type or the publication and edition for publications of the type ad pre-print.
Carrier
Media product (edition)
route 1
Home delivery
GEO 1
Postal delivery,
Sales
direct delivery
organization Night round
1
Morning round
Plant (printing works)
SAP AG 2006
The delivery viability set defines the following for a sales area (sales organization, distribution
channel, division):
y Edition to be delivered
y Area to be supplied (geographical unit or carrier route)
y Delivery type
y Delivery round (time of day at which delivery begins according to the Customizing settings, for
example, morning round, evening round)
y Plant as point of departure for the delivery
Delivery viability sets are edited in change management (which gives them a restricted validity
period).
Delivery to a delivery address is only viable if a delivery viability set has been created for it in the
system.
y Delivery viability sets for home delivery must be created in the system for the corresponding
carrier routes.
y Delivery viability sets for postal shipping and direct delivery must be created for the
corresponding geographical units.
Note: You cannot create a delivery viability set for the delivery type pickup. Pickup is possible with
any delivery type marked for pickup.
Transaction type
e.g. order processing,
releasing a change number
Order or orders
on hand affected
Determination or application
of delivery viability
parameters
Edition
Delivery viability optimization Mix type
Delivery type
according to optimization rules
SAP AG 2003
Delivery viability optimization is a function for flexibly determining and applying the delivery
viability parameters edition, mix type, and delivery type in order items.
Besides efficient order processing, the aim of delivery viability optimization is to automatically
optimize the delivery viability parameters for existing orders in a flexible way. This has the
following advantages:
y Cost reduction
y Best possible delivery time
You can define specific optimization rules for different transaction types - for example, for order
processing and change number release.
Create/change order
Change of address
Change number release
Explicit optimization run Optimization
rule
SAP AG 2003
010 * * 01
The system determines
020 * * 02 the delivery viability set
030 * * 03 with the highest priority
parameters of all those
040 * * * found.
...
Status
SAP AG 2003
The system automatically determines the delivery viability parameters using the optimization rule
during order processing.
Priority Edition Mix Type Del.Type Edition Mix Type Del.TypeRecal Outpt Active
.
010 01 01 =
* 10 03
020 * * 03 = = 04
SAP AG 2003
The delivery viability parameters are converted from their initial status to a new status for the
following operation types.
You can enter the following special characters for generic entries:
y "*" for any values
y "=" for values that are to remain unchanged
You can choose the following options for each entry:
y Recalculation may take place as a result of the change to the delivery viability set.
y The output control functions can be used to create a message, for example, a confirmation or
notification of the change to the delivery viability set.
y The entry is active. Only active entries are included in delivery viability optimization.
m ple
a
Ex Operation 01 Create/Change
Type Order
Order Type ABO Order Type ABO Order Type ABO
Publication Daily Paper Publication Daily Paper Publication Daily Paper
SAP AG 2003
Delivery viability optimization determines the best possible delivery viability parameters for the
operation type Create/Change Order.
Orders affected
Order item
Last time slice
Original del. viability set
Delivery viability optimization
Unlimited change
Optimized del. viability set
SAP AG 2003
Prerequisite:
The indicator Optimize del. viab. must be selected in the master data on the change number.
When you release a change number, the system searches for the "best" delivery viability set using
the optimization rules for all the orders affected by the change.
When changing delivery viability parameters, the system creates an unlimited change for the last
time slice in the order item.
Delivery rounds
SAP AG 2003
The delivery time is determined by the delivery round. The possible delivery rounds are defined in
Customizing (e.g. delivery round 1 is the morning round, delivery round 2 is the evening round).
The time at which delivery is initiated or actually takes place is controlled by the assignment of the
delivery round to the following data objects:
y Home delivery round
Assignment of carrier or field collector to delivery round. Several editions are delivered together
in a delivery round. The assignment of the editions to a home delivery round takes place using
the delivery viability sets.
y Delivery viability set (delivery viability sets for carrier routes or geographical units are always
restricted to one delivery round)
y Truck route (the delivery round assigned determines the time of day at which the truck route is
run, for example, in the morning)
Carrier route 1
Home delivery
Unloading point 1
Ed.1 Ed.2 Ed.2
Morning round
SAP AG 2006
The unloading point is defined for each edition in a carrier route. This means it is possible to use a
different unloading point for daily newspapers than that used, for example, for ad pre-print
distribution.
A carrier route can have several unloading points. The corresponding unloading viability sets must
also be created.
When you create delivery viability sets for a carrier route, the corresponding unloading viability
sets are created automatically. When this is done, the unloading point is copied from the default
values in the carrier route master data.
The unloading viability sets are edited in Change Management. The checks in Change
Management ensure that there is an unloading viability set for each delivery viability set (for home
delivery). The system also checks that each unloading point in an unloading viability set also has at
least one truck route that serves it and that carries the edition that is to be unloaded there.
Unloading point 2
Carrier route 1
Unloading point 1
SAP AG 2006
If a second unloading viability set is defined for a carrier route, the system automatically generates
an unloading rule. The unloading rule determines how the units delivered in this carrier route are to
be split.
When you save the unloading viability set, the system displays a message informing you of the
unloading rules that have been generated.
The units can either be split according to percentages (%), full bundles (FB), or pieces (PC). (If they
are split by percentage or by pieces, the bundle divider is also taken into account.)
The order in which the unloading points are served is defined implicitly in the unloading rule, but
you can change this sequence.
The first unloading point is always interpreted as the unloading point for the odd bundle, which
means that the shipping documents for the odd bundle are created for this first unloading point.
Note: The sequence of unloading points in the unloading rule is defined from the carrier's point of
view, not from the perspective of the carrier route.
Unloading
point
Newsstand 1
SAP AG 2006
If an unloading point (business partner or general unloading point) is served several times by
different truck routes on one shipping date, you must specify how the quantities are to be split.
Example: You might decide to deliver 50% of the total delivery quantity with Truck Route 1 and
50% with Truck Route 2.
The delivery round specified in the master record of the truck route determines the time at which
delivery takes place (for example, with the morning round or the evening round).
A corresponding rule is generated based on the current orders sent to an unloading point by direct
delivery.
Daily
Daily Paper
Paper West
West 30%
30%
Daily
Daily Paper
Paper West
West SA*
SA* 50%
50%
Unloading point 2
Carrier route V1
Unloading point 1
SAP AG 2006
Since certain issue variant types may require you to split quantities differently for some editions,
you can create exceptions to the usual unloading rules.
An exception always overrides the normal rule. This means that the exception rule is always used
when the actual issue variant type for the issue corresponds to the one specified in the rule on a
certain shipping date.
Delivery
round in
carrier route
Period
Mo Tu We Th Fr Sa Su Weekday
Carrier/SC
+ Substitution
type
Settlement?
SAP AG 2003
The assignment of a carrier (or field collector) to a delivery round in a carrier route is defined in the
home delivery round. You can maintain the following attributes:
y Validity period in which the carrier works the delivery round.
y Service company and carrier (depending on the membership status of the service company).
The system checks that an employment relationship (relevant for employee settlement) and
settlement data on the service company (relevant for SC settlement) exist.
y Weekdays on which the carrier is deployed (in the validity period of the home delivery round).
y Settlement relevance
y Substitution type (Carriers and service companies can be replaced by other carriers and service
companies in the period of the home delivery round.)
Airport Mo-We Fr
11:00 pm GB
I
Airport Mo E
1:00 am We P
Fr
SAP AG 2003
The shipping schedule determines which unloading point is used for shipping to a certain postal
code area (country).
You can use a different shipping schedule for each edition.
SAP AG 2003
The shipping schedule determines which unloading point and network are used for shipping to a
certain postal code area (country).
You can also group countries together to form a country group.
You can process postal shipping for a geographical area using various shipping networks.
The container type and latest goods arrival time control postal packing and container packing.
Shipping schedule
Shipping schedule
SAP AG 2003
The validity period of a shipping schedule variant defines the dates on which a certain edition is
shipped using the shipping schedule that is assigned to this variant.
Example
The daily newspaper is normally shipped using the variant shipping of daily newspaper and the
shipping schedule assigned. However, a modified shipping schedule is used for the shipping date
12/24. This is assigned to the variant shipping for public holiday. This variant can also be used on
other public holidays on which shipping is performed in the same way.
Implementation
of IS-M
Distribution
SAP AG 2003
SAP AG 2003
1-2 Assign unloading point ULP-## as the main unloading point to your carrier route
CAR-##. The main publication for this carrier route is JMH* and the main edition is
JM##.
1-3 The unloading points ULP-## and PST-## are to be served by truck route TRT-##.
1-3-1 Create a basic truck route TRT-## with loading point PUB-## at the plant
New Media (ME20). Trucks are the vehicles used on this truck route. Choose
calendar Z2 for use in generating the daily route. The truck route is served by
the MORNING delivery round.
1-3-2 The unloading points are to be served in the following order: ULP-##, PST-##.
1-3-3 Assign edition JM## to your truck route TRT-##.
1-6 The edition is also to be available from tomorrow in North America via domestic post
without ad inserts and abroad via international post, also without ad inserts. Create the
corresponding delivery viability sets.
1-6-1 Use the geographical unit GU-NAM, delivery type 04, mix type 10, and the
MORNING delivery round for the delivery viability set in North America.
1-6-2 Use the geographical unit GU-WORLD, delivery type 04, mix type 10, and the
MORNING delivery round for the delivery viability set that is valid
worldwide.
1-7 Master data maintenance, which affects change management, is now completed. Release
your change number.
1-7-1 To obtain an overview of the changes made, analyze your change number.
1-7-2 Run a check on your change number.
1-7-3 Release your change number.
1-8 Create the delivery optimization rule for your publication JMH* with the following
data:
1-8-1 Your delivery optimization rule is to be valid for your publication JMH* when
you create and change order items for a subscription.
1-8-2 The optimization rule is to give home delivery priority over domestic and
international postal shipping.
All the exercises in this unit begin with the following menu path:
Logistics Media Sales and Distribution Periodical Sales and
Distribution Master Data Distribution
Content:
z Sales promotion
z Campaign framework
z Allowed gifts, advertising media and commission recipients
z Sales activity
z Marketing campaign
SAP AG 2003
SAP AG 2003
Internet Application
Organization
Components
Geographical structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Unit Summary
Center (CIC)
SAP AG 2003
SAP AG 2003
Order 1
Order 2
Order 3
Sales
promotion
Plan Actual
800 850
900 920
...
SAP AG 2003
Sales source
Sales
promotion Publication
Order
Campaign
framework
Sales agent
role
Sales area Event
Sales Initial introduction
organization Renewal
1 Gift
Change pyt meth.
...
SAP AG 2003
The campaign framework defines the basic information for obtaining orders for a sales area. It has
the following characteristics:
y Validity period
y Refers to a sales source
y Refers to a sales promotion
You specify information such as the following in the campaign framework:
y Minimum length for the subscription obtained
y Maximum suspension period
y Commitment period for a subscriber
y Liability period for a commission recipient
Advertising
Gifts media
SAP AG 2003
Sales source
Campaign
framework
SAP AG 2003
If gifts are specified in the sales source for obtaining orders, you can enter the specific gifts allowed
in the campaign framework.
You can then select one of the allowed gifts when editing the order.
Sales source
Campaign
framework
SAP AG 2003
You can assign a campaign framework advertising media that support the sales promotion.
You can then select one of the advertising media assigned in order processing.
You can evaluate the orders according to the advertising media. The evaluation allows you to
identify which advertising media are valuable for use as marketing instruments.
Sales source
Campaign
framework
SAP AG 2003
If commission is allowed in the sales source for obtaining orders, you can enter the allowed
commission recipients in the campaign framework (only for the sales source Commission).
You can specify the following in the campaign framework for each commission recipient:
y Commission clawback type
y One-time commission or renewal commission
y Additional promotion rebate
y Commission recipient is also failure researcher
It is also possible to assign a service company (SC) to the campaign framework. In this case, all
commission recipients who have an employment relationship with this service company are allowed
in the campaign framework.
In order processing, you can only select one commission recipient who is specified in the campaign
framework for obtaining orders.
SAP AG 2006
Business partner-
independent campaigns
Template offers
Application area
Navigation area
SAP AG 2006
SAP AG 2003
1-2 Create a campaign framework for the sales promotion and sales source RR (reader
recommendation).
1-2-1 Use the same validity period as you used for the sales promotion.
1-2-2 Create gifts for the campaign framework that can be awarded for full
subscriptions (FD):
Coffee machine (for 2 subscriptions), radio (1 subscription + an additional
payment of 5 USD).
1-2-3 Assign the event initial introduction to the campaign framework.
Content:
z Structure of the CIC
z Functions of the CIC
z Integration
SAP AG 2003
SAP AG 2003
Internet Application
Organization
Components
Geographical structures
Settlement
and Change Management
Distribution Pricing
SAP AG 2003
PBX Telephony
Dials service
IVR / ACD / Gateway
number CTI
ll
c Ca
i DNIS
at n
t om
utio ANI
Au ib
str
Di
R/3
Front End
Data Application
Link
SAP AG 2006
R/3 System
SAPphone
SAPphone SAPphone
Server RFC Interf.
Telephony TAPI
Gateway
CTI
Dialer ACD
Call Center
IVR VRU
1002 1001 1000
PBX Public
telephone
network
SAP AG 2003
Telephony functions
BP search
Call status
Action Box
Navigation area
SAP AG 2003
You can access details on the selected entry (order, complaint, suspension, ...) by double clicking or
using the context menu in the business partner environment.
SAP AG 2003
You can define the position of the tab pages in the application area as you wish.
You can only use SAPGUI for HTML in connection with an ITS (Internet Transaction Server).
Valid From
Relocation
Name Sawyer from date
First Name Tom
Street/No. Cottage Street 2
PCd/City Country Correction
Tel.no.
Suspension
Order 165 / 10 / SI
Period 13.03.2000 31.12.9999 Publication Role Suspension
Validity 15.08.1998 - 31.12.9999
Publication Monthly Monthly
Complaint
Mag Mag (reduced
Order SDTy. ItNo. PA Valid From Valid To Publication Edition dialog)
1356 ABO 10 ChangeSIData13.03.2000 31.12.9999 DPAPER LOCAL
Period 20.12.2001 - 31.12.2001
1356 Save
ABO 10 S 01.05.2000 15.05.2000 DPAPER LOCAL
Susp.reason 001
Date Catg. Curr. date
Full
dialog
SAP AG 2003
The change functions in the CIC are executed using shortened CIC dialogs. You can access the full
dialog from these dialogs.
SAP AG 2003
A BSP application for campaign-supported order entry is available as of Release 4.71 in Media
Sales and Distribution.
The ISM_BSP component can be used to incorporate Business Server Pages (BSP) in the application
area of the Customer Interaction Center and navigate to a SAPGUI-based detail maintenance screen
from this BSP application.
The settings for this component are made in Customizing under SAP Media -> Customer Interaction
Center (CIC) -> Make Settings for Accessing BSP Applications.
If you want to use this component in the application area, you have assigned it to a tab page in the
application area under SAP Media -> Customer Interaction Center (CIC) -> Maintain Navigation
and Application Area.
The ISM_BSP component can also be incorporated in the application area in the SAP CRM
Interaction Center.
SAP AG 2003
Content:
z Sales document structure and sales document types in
Subscription Sales and Distribution
z Subscription order types and processing functions
z Complaints
z Internal orders
z Delivery address alternation
SAP AG 2003
SAP AG 2003
Internet
Organization
Application Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Conclusion
Center (CIC)
SAP AG 2003
SAP AG 2003
Internal
order
Subscription:
Subscription Unlimited subscription
offer Delivery subscription
Renewal subscription
Period renewal subscription
Sales
document
type
SAP AG 2006
The most important sales document types are predefined in the standard system, for example:
y Subscription offer
y Subscription
y External delivery order
y Credit memo request
y Internal order
SAP AG 2003
New
billing period
Time
Customer
account
Year's Year's
subscription subscription
D C
$ 60
IS-M/SD FI
SAP AG 2003
Billing is performed periodically in advance for an unlimited subscription. The subscription can be
suspended by limited changes and is valid only until terminated.
For example: year's subscription, month's subscription, Saturday subscription.
Unlimited subscriptions are common in Germany and Austria, for example.
Time
Time
Customer
account
Year's Year's
6 deliveries 6 deliveries
subscription subscription
Liability acct 001 Liability acct 002 D C
mySAP Media
IS-M/SD
Subscription Sales & Distribution FI
SAP AG 2003
Subscriptions with a delivery-related liability account are specially suited to magazines that are
published at irregular intervals.
The delivery-related liability account for the order contains the number of issues for which billing
has been performed for each billing cycle and the number of issues currently delivered. Once an
issue has been shipped, the amortization procedure updates the delivery-related liability account.
When the first issue is amortized, the system generates:
y the liability account
y amortization installments (required for revenue deferral)
y billing index
When the last issue is amortized, the system generates the transfer index for the liability account
transfer. When the liability account transfer takes place, any differences are cleared in the clearing
and revenue accounts.
In the case of subscriptions with a delivery-related liability account, the price frequency is defined
for the unit of measure "Number of deliveries". If you use this kind of subscription, you must define
a new price and billing frequency. You must also extend the billing arrangements for subscriptions.
Subscriptions with a delivery-related liability account are specially suited to magazines that are
published at irregular intervals.
The delivery-related liability account for the order contains the number of issues for which billing
has been performed for each billing cycle and the number of issues currently delivered. Once an
issue has been shipped, the amortization procedure updates the delivery-related liability account.
Steps Time
Customer
Monitoring 3 tolerance
account
period periods
Renewal Suspension
offer Termination D C
Reminders Restart
Billing $ 100 $ 100
Liability acct Liability acct
Payment Amort. Payment Amort.
Billing Payment
Period covered by Period covered by new
payment amount payment amount
IS-M/SD FI
SAP AG 2003
Renewal subscriptions are assigned an expiration date. When the expiration date approaches, the
subscription moves into a monitoring phase.
In the first monitoring step, the monitoring control procedure (which consists of a number of steps)
sends the subscriber a renewal offer, encouraging him to continue his subscription.
In further monitoring steps, the subscriber is sent reminder letters requesting payment. If no
incoming payments are received, delivery of the subscription continues after the expiration date for
an initial tolerance period (in expectation of an incoming payment). Once the first tolerance period
is over, the monitoring control functions suspend the subscription for an unlimited period. If the
second tolerance period also passes without any incoming payments, the subscription is
terminated. Once the third tolerance period is past, the closing step clears the clearing accounts
and performs a liability account transfer if applicable.
Activities for delayed payment can be set up in Customizing. For example, you can determine
whether or not billing is to take place for goodwill deliveries.
If the payment is reversed within a predefined period, the incoming payment is recalculated in the
renewal subscription. The expiration date is canceled and the subscription returns to the monitoring
phase. Revenue already accrued for the reversed payment amount is canceled.
Check procedures
for inc. payments
Incoming payment
Order
No order
exists
SM58
Job OPEN_FI_PERFORM_...
Accept offer Workflow control
Renew order event
Log payment
OK Error
Subs. Workflow
renewed event
IS-M/SD tRFC FI
SAP AG 2003
Closure
No payment Termination
Unlimited suspension;
stop delivery
You specify which functions are triggered by each monitoring step in the Customizing settings for
monitoring control (order Customizing for Media Sales and Distribution). For example, a
monitoring step can trigger the following functions:
y Create renewal offer
y No action (output control creates reminder letter if applicable)
y Create unlimited suspension
y Terminate order item
y Terminate subscription
You specify times for executing the functions for each step when you define the monitoring
procedure. The system interprets the time remaining for the subscription until the expiration date for
each step in a monitoring procedure. The time remaining until the expiration date is specified for
dailies in a number of offset days. You can also specify the interval for non-dailies in a number of
copies still to be delivered. You cannot combine a number of offset days and a number of copies still
to be delivered in the same monitoring procedure.
In addition to the number of offset days or copies to be delivered, you can also determine user-
specific criteria in a function module.
60 $ 100 $ 100 $
Amortization
plan
Amortization Incoming
payment
Deliveries
IS-M/SD FI
SAP AG 2006
Amortization is executed by a program located downstream from shipping. The system determines
the revenue recognized, the amortization installment, from each delivery of an issue. The payment
amount (from FI Accounts Receivable Accounting) and the amortization amount (total of the
amortization installments for each renewal cycle) are posted to the monetary liability account for the
renewal subscription.
You can display the liability account on the relevant tab for the item. Liability account display lists
all the renewal cycles for the item together with information on the renewal status and the payment
and amortization amounts. If an open renewal offer is identified, the items in the renewal offer are
listed. If a payment amount cannot automatically be assigned to an item (for example, because the
amounts are different), an administrator can accept the offer manually so that the item in the renewal
subscription is extended.
The system generates an amortization plan for each cycle, containing the issue variant types and the
corresponding amortization installments. You can access the amortization plan and the payment and
revenue log from the liability account screen.
If changes such as price increases are made that affect the amortization plans for renewal
subscriptions, you can update the amortization plan for a selection of order items.
Payment Customer
1
D C
120 $ 120 $
Liability acct .
bs
4 4711 / 005 Su cle
cy
Amort. Payt
amount amount
120 $
IS-M/SD FI
SAP AG 2003
The function for transferring remaining amounts from monetary liability accounts is required if
a monetary liability account contains a remaining amount for which revenue recognition is no longer
possible. Remaining amounts can arise in the following cases:
y As a result of redirections or price changes that lead to a change in the amortization installment,
the amount on the liability account is not used up.
y The subscription is terminated before the end of its validity period.
Any remaining amount on the liability account is transferred once the account is closed
(reconciliation of clearing accounts). The following transfer types are possible:
y 0 No transfer, simply reconciliation of clearing accounts
y 1 Transfer to payer's customer account
y 2 Transfer to extraordinary revenue (G/L account)
y 3 Transfer to other item
y 4 Transfer to subsequent cycle
y Transfer types 1 through 3 can be specified by the administrator when a subscription is
terminated. Transfer to the subsequent cycle takes place automatically when a new liability
account is opened.
D C
Incoming payments for
renewal subscriptions 300 $ 300 $
D C
Assignment number Post 80 $
from renewal offer
D C
120 $
SAP AG 2003
As of Release 4.62, incoming payments can be entered easily and efficiently for renewal
subscriptions with the payment method Invoice.
The incoming payment is entered for each payer and posted to the payer's customer account.
You must enter the assignment number and check amount for checks. The offer amount and the
name of the payer are displayed for the assignment number to allow you to check the data.
Each renewal offer displays an assignment number determined by the system from the order number
and the external item number. The system uses this assignment number to assign the payment to the
order item, so that subscription renewal is possible. The assignment number is displayed on the item
data screen for the order.
If the payer's business partner number is specified on the selection screen, the system automatically
determines all the payer's orders for which payment is due and displays the corresponding
assignment numbers on the data entry screen.
You must define the document type and the posting keys for debit and credit postings in
Customizing, so that the amount can be posted to the customer account.
Time
IS-M/SD FI
SAP AG 2003
Renewal subscriptions are assigned an expiration date. When the expiration date approaches, the
subscription moves into a monitoring phase.
In the first monitoring step, the monitoring control procedure (which consists of a number of steps)
sends the subscriber a renewal offer, encouraging him to continue his subscription.
In further monitoring steps, the subscriber is sent reminder letters requesting payment. If no
incoming payments are received, delivery of the subscription continues after the expiration date for
an initial tolerance period (in expectation of an incoming payment). Once the first tolerance period
is over, the monitoring control functions suspend the subscription for an unlimited period. If the
second tolerance period also passes without any incoming payments, the subscription is
terminated.
If the payment is reversed within a predefined period, the incoming payment is recalculated in the
renewal subscription. The expiration date is canceled and the subscription returns to the monitoring
phase. Revenue already accrued for the reversed payment amount is canceled.
Note:
Revenue deferral for period renewal subscriptions is performed periodically and does not relate to
performance, so that amortization is not required. Liability account transfer also does not take place.
Subscription
order
Delivery
SAP AG 2003
Carrier Planning
route reserves
reserves
Delivery Delivery
to to Branch
carrier internal
route BPs
Random Employee
distribution
SAP AG 2003
The publisher places internal orders itself for the following reasons:
y Planning reserves for subsequent deliveries
y Planning promotional copies for random distribution
y Supply internal organization (e.g. departments) with free copies
Billing is not performed for internal orders.
The following types of internal order exist:
y Internal orders from business partners
y Carrier route-related orders
The sales document types for the different types of internal orders are provided in the standard
system.
Sold-to party
Bill-to party Sales customer
Payer and SC
Commission recipient
WBZ company
nt
ns
Su
me
ti o
bs
ttle
Su
uc
cri
rod
se
bs
g
pti
illin
cri
ion
int
on
pti
yb
iss
on
bil
on
r
lin
pti
mm
or
liv
g
cri
WBZ
de
co
De
bs
r
subscription Ship-to
SC
Su
processing party
Media company
Delivery Customer
WBZ subscription order (subscriber)
SAP AG 2003
WBZ (Werbender Buch- und Zeitschriftenhandel subscription book and magazine trade) is a form
of sales and distribution specific to Germany. WBZ companies advertise and sell subscriptions for
other media companies in their own name and receive commission for this service in the form of
promotion rebates.
To be able to record WBZ orders in your system, you must make special Customizing settings in
pricing (WBZ unit price, WBZ promotion rebate), sales support (sales source for WBZ
commission), and the order (order type for WBZ subscriptions).
WBZ orders are usually created automatically (for each WBZ subscriber and therefore for each ship-
to party) when the files of WBZ companies are imported. The WBZ company operates as sold-to
party, bill-to party, payer, and commission recipient in the WBZ subscription order. Billing for
delivery to WBZ customers takes place based on deliveries.
Commission settlement for WBZ companies takes place in service company settlement. For this
purpose, WBZ companies must be created as external service companies with corresponding
settlement data.
Item 1 Edition
Delivery type
Business partner WE,RE,RG,VM
Promotional data
Validity period
SAP AG 2003
In Media Sales and Distribution, each sales document is structured according to the hierarchy
header - item - schedule line.
Any number of items can exist for a header in a sales document.
The only differences are in the number of possible schedule lines per item.
The abbreviations have the following meanings:
WE = ship-to party
RE = bill-to party
RG = payer
VM = sales agent
Sold-to party
Payer
General
Bill-to party business partner
SAP AG 2003
The business partner must be created as a Sales Customer (subscriber) in the system in order to
occupy the following order-specific roles:
y Sold-To Party
Order-related data: customer pricing procedure, customer group, price group, price list type, tax
data
y Payer
Order-related data: Bank details, tax data, billing schedule, terms of payment
y Ship-To Party
Tax data
Since only the address is relevant for the Bill-To Party role, the Bill-To Party must at least be
created as a general business partner in the system.
Note:
Free items do not have payers or bill-to parties. This means that in this case you need only create the
ship-to party as a general business partner in the system.
SAP AG 2003
On the initial screen of the subscription order (Create), you can call up a separate maintenance
screen for each item type. You can create the following item types:
y Standard item when creating a regular subscription item.
y Free item when creating a free subscription item that is not relevant for billing.
y Free item with transformation to chargeable when creating a free item that is automatically
converted to a standard item when the sales promotion is over (e.g. two months at a special rate).
y Trial item when creating an item in connection with a sales promotion (for a limited period). The
sales promotion is aimed at converting the trial item into a standard subscription item.
y Trial item with transformation to chargeable when creating a trial item that is automatically
converted to a standard item (e.g. two months at a special rate).
Basic Data Billing Doc. Sales Support Shipping Addit. Data Schedule Line Text
Billing Document
Sales Support
Additional Data
Schedule Line
SAP AG 2003
The principal element in the user interface of the maintenance functions for sales document is a tab
index. Each tab page has a title that is visible at all times. You can click on the tab page title to bring
the page to the foreground and edit it.
You can control period specifications by specifying the date category.
Delivery address
determination
User Delivery viability
parameters determination
Determination of soonest
Customizing of possible start of delivery
default values
Data entry Audit report category
determination
Default values
in master data Pricing
Partner Determination of sales
determination support data
Researcher
determination
SAP AG 2003
When you create a new order item, the system automatically enters default values in certain fields.
These default values are derived from:
y Master data
y Customizing
y User parameters
Data entry is supported by the following functions:
y Input checks
y Determination functions that add the missing data on the order item
Order types
Validity period Order type
Mix offer
Delivery viability set
Delivery address Publication
Order types
Viable
Mix offer
Publication editions Edition
SAP AG 2003
Order processing
Determine or apply
Delivery viability optimization delivery viability parameters
according to optimization rule z Edition
z Mix type
z Delivery type
SAP AG 2003
Delivery viability optimization is a function for flexibly determining and applying the delivery
viability parameters edition, mix type, and delivery type in order items.
Besides efficient order processing, the aim of delivery viability optimization is to automatically
optimize the delivery viability parameters for existing orders in a flexible way. This has the
following advantages:
y Cost reduction
y Best possible delivery time
You can define specific optimization rules for different operation types - for example, for order
processing and change number release.
SAP AG 2003
Delivery viability optimization determines the best possible delivery viability parameters for the
operation type Create/Change Order.
STOP
Indicator "No delivery Manual entry of
viability optimization" delivery viability parameters
SAP AG 2003
The indicator No delivery viability optimization in the basic data (shipping data) for the order item
prevents the delivery viability parameters from being changed by the automatic delivery viability
optimization process.
This allows you to include customer requests regarding delivery - for example, that delivery is
always to be by post.
Note: Values entered manually for the edition, mix type, and delivery type are not overridden in
delivery viability optimization.
Transaction types
z Create or change orders
Transaction type z Change address
Explicit optimization run z Release change number
z Explicit optimization run
SAP AG 2003
Explicit optimization of delivery viability parameters takes place for a defined quantity of issues (for
example, worklist).
You can create or maintain the worklist in advance.
When changing delivery viability parameters, the system creates an unlimited change for the last
time slice in the order item.
Caution: Changes on a larger scale can lead to major changes in the shipping processes.
Once a new delivery viability set has been introduced (for example, with a new delivery type) for a
geographical unit, you should process the orders affected in several separate optimization runs.
Monday: 5:00 PM
Order deadline
for shipping on Wednesday
11 12 1
10 2
9
8 4
3
Processing
7 6 5 Monday to 5:00 PM
Outbound delivery
for Wednesday
Monday from 5:00 PM
SAP AG 2003
If the order deadline has been set for a publication in shipping, no more orders can be accepted for
the shipping date.
Sales source
Header
Sales area
Sales Publication
promotion
Campaign
framework
SAP AG 2003
The Customizing settings for the sales source determine whether or not the sales support data is
recorded in the order item. Sales support data includes data on the campaign framework, on how
the order was obtained, on advertising media and on commission.
The campaign framework defines the framework conditions for the sales support data. The system
requires the following data for use in determining the campaign framework for the order item:
y Sales area
y Sales source
y Sales promotion
The campaign framework assigned to the order item controls recording of sales support data as
follows:
y If a new subscriber is introduced by an existing one, you can choose a gift for the reader and if
the new subscription is sourced by a professional agency, you can assign the commission
recipient.
y You can also record data on commission for professional agents, such as the liability period and
commission due date.
y You can record the advertising medium or business partner sales activity by means of which the
promotional information reached the customer in the sales support data.
SAP AG 2003
As of Release 4.02, you can create as many sales support entries as you wish for each subscription
order item. For example, additional entries are required in the following cases:
y The subscriber is to receive a gift if they change their payment method or request a gift transfer.
y The subscriber is to receive a gift when an incoming payment is received for their renewal
subscription.
Each campaign framework is assigned certain events for which sales support data is required. You
can select events for which you want to enter new sales support data in the overview list for sales
support. The system automatically determines the event "Initial introduction" when a new order item
is entered.
A main sales agent must be specified in the sales support entry for initial introduction.
You can assign several gifts or commission records to each sales agent.
All existing sales support entries are displayed as an overview. You can edit, delete, or create entries
from this overview screen.
Order type
Delivery type
Audit report Audit
category report
Customer group
default category
Customer price group
SAP AG 2003
The audit report category is determined using the audit report category default (Customizing).
Audit report categories are defined for the following combination of data:
y Order type
y Item type
y Customer price group
y Customer group
If the system does not determine a unique audit report category, it lists the possible categories on a
selection screen.
If the start of the billing period is delayed for certain order items, you must specify a second audit
report category for the non-billing period. This category is also determined using the category
default.
Change
Unlimited change publication
Termination Cancellation
SAP AG 2003
Relocation
Standard item
STOP
Standard item
SAP AG 2003
An unlimited change is required when critical item attributes change as of a certain date, affecting
y Delivery
y Billing doc.
Critical changes to an order item include the following:
y Different delivery type or edition (change to delivery viability set)
y Different delivery address
y Different billing data
Note:
You can change the business partner's bank details in the standard item. You do not need to make an
unlimited change in this case.
SAP AG 2003
When a suspension is made, deliveries do not take place during the suspension period. Circulation
planning is not carried out for the standard item during the suspension period. The subscriber can be
given a credit memo in compensation. (The separate function partial suspension allows you to
suspend a subset.)
A redirection involves delivery to an alternate delivery address for a certain period. Circulation
planning does not take place for the standard item during a redirection period. You can change the
delivery type and the edition in the standard item (provided the corresponding delivery viability set
is defined). A redirection may involve additional shipping costs.
A gift transfer involves delivery to a different business partner for a certain period at the
subscriber's expense. The sold-to party does not receive the deliveries himself during this period.
Circulation planning is not carried out for the standard item during the change period. You can
change the delivery type and the edition in the standard item (provided the corresponding delivery
viability set is defined).
A charitable transfer involves delivery to a social facility for a certain period. Circulation planning
is not carried out for the standard item during the change period. The social facility is not specified
as the ship-to party in the charitable transfer. All charitable transfers valid on a particular date are
divided anonymously among the social facilities specified in the system (distribution function
charitable transfers).
Delivery
quantity
10 7 2 5 10
Additive change
Credit memo
SAP AG 2003
A partial suspension is only possible if the schedule line quantity is greater than 1. You can use a
partial suspension to suspend part of the schedule line quantity from the standard item.
As can be seen in the graphic, partial suspensions can overlap.
Advantage:
Each partial suspension requested by a customer that is a company (for example, a corporate group
or government agency) can be recorded individually in the system. If several change requests are
received, you no longer need to calculate absolute quantities.
Standard item
Redirection
Add. copy
redirection
Divert address
Quantity
Change to delivery
type and edition
Costs
SAP AG 2003
In an additional copy redirection, an additional delivery is made to a divert address for a certain
period.
Circulation planning continues for the standard item for the period of the additional copy redirection.
You can change the following data on the standard item for the additional copy redirection (provided
the corresponding delivery viability set is defined):
y Delivery type
y Edition
Since this is an additional delivery, the redirection involves purchase costs and possibly shipping
costs.
Standard item
Redirection
Suspension
SAP AG 2003
Only one subtractive change item is allowed at any one time for a standard item.
Time overlaps are not allowed for the following subtractive change items:
y Suspension
y Redirection (without additional copy)
y Gift transfer
y Charitable transfer
Exception:
An additional copy redirection can overlap with any subtractive change item.
Standard item
Redirection
SAP AG 2003
Time overlaps between subtractive changes and unlimited changes are also not allowed.
Reason (example):
For example, a redirection only involves invoicing for additional shipping costs, whereas an
unlimited change can lead to completely new prices as a result of changed attributes.
Standard item
Suspension
SAP AG 2003
You can also enter an unlimited change if the period for the unlimited change already contains a
limited change (for example, a suspension, redirection, or gift). The existing limited change is
automatically assigned a new predecessor reference to the new unlimited change.
If the period for the existing limited change covers both the unlimited change and the previous item,
you must split the limited change first.
Standard item
Limited change
Split
SAP AG 2003
You can split the period for a limited change item (such as a suspension, redirection, gift, or
transfer) using the corresponding change function.
You need to split a limited change item if you have to enter an unlimited change to the standard item
during the period of the limited change.
Old
publication
New
publication
Termination
SAP AG 2003
You can change the publication for an order item. When you do this, the previous item is terminated
and a new one is created.
The delivery and invoice addresses are copied from the item to be terminated. If commission
recalculation is to take place, the sales support data is copied to the new item.
Charge
off
Tip or
donation
Condition record
$ 10.--
SAP AG 2004
As of SAP Media 4.72, you can make donations of refunds from subscription terminations or
suspensions. Until now, the resulting credit memos were always sent to the subscribers themselves.
You can now choose between the following possible uses for the credit memo:
y Tip for carrier
y Donation to charity
y Gift to another business partner
You define the use of the credit memo by selecting a refund type. If a refund type is not specified,
the credit memo is sent to the original payer.
This function can only be used if you work with Contract Accounts Receivable and Payable (IS-
M/CA).
The amounts donated are collected in FI-CA and forwarded to the carrier or to the charity by means
of a transfer posting.
SAP AG 2003
Original item
SAP AG 2003
Main
item
SAP AG 2006
t
STOP
t
STOP
t
STOP
SAP AG 2003
t
STOP
SAP AG 2003
t
Unlimited change because of
new billing frequency
SAP AG 2003
t
Unlimited change because of
new delivery address
SAP AG 2003
Main item
Complaint at sub-
item level for each
delivery address
Sub-item Sub-item
for alternating for alternating
address address
element element
MO-FR SA-SU
SAP AG 2003
Reversal
Standard item
STOP
Actual end of
delivery
SAP AG 2003
You can only reverse an order item if billing or commission settlement have not yet been performed
for it.
You need the reversal function, for example, if a customer cancels their order.
The reversed item remains in the system but is not subject to
y circulation planning
y delivery
y billing
To reverse a billed order item, you must first reverse billing. To reverse an order item for which
commission settlement has been performed, you must first reverse commission settlement.
When you reverse an order item, you must specify a reversal reason.
The soonest possible end of delivery is derived from the order deadline for order processing.
Termination
Standard item
STOP
SAP AG 2003
When a standard item is terminated, the system determines the soonest possible end of delivery or
termination date based on the following data:
y Minimum length of subscription specified for subscriber
y Commitment period for sales agent
To terminate a subscription immediately (without performing failure research), you enter an actual
end of delivery.
When you save the order, the item is closed and billing and commission are recalculated, if
applicable.
Termination can be canceled if the following prerequisites apply:
y Recalculation has not yet taken place
y The order deadline for shipping is not yet past for the delivery end date
It should be possible to continue delivery without any gaps after termination has been canceled.
SAP AG 2003
1-2 The customer JSU-## also wants to receive an additional copy of the newspaper at their
place of work.
1-2-1 Create an additional item for 1 copy of JMH*.
1-2-2 Create an additional delivery address for the business partner: Hamptons
Hotel, ## Evergreen Ln, New Hampton, NY.
1-4 Your customer is not happy with the current publication and wants to change
publication as of next week.
1-4-1 First, create a subscription for your subscriber JSU-##. The subscriber wants to
subscribe to the daily newspaper New Hampton News JMH*. The customer
wants to receive 1 copy of this. The customer purchase reason is own
initiative, they want a full subscription, and they want to receive an annual
invoice for this.
1-4-2 Enter a change of publication from JMH* to the daily newspaper JMDP. The
customer states that the delivery end reason is insufficient quality.
Then display the order overview.
All the exercises in this unit begin with the following menu path:
Logistics Media Sales and Distribution Periodical Sales and
Distribution Sales Order Customer Interaction Center Front
Office Front Office
1-1 Dialog box Choose Organization: Position: CIC Agent MSD (tel) Copy
Dialog box Settings not yet Maintained Do you want to make the settings now?
Yes
Dialog box Maintain Own Telephone Number Extension 123## Copy
Dialog box Queue Selection Choose queues 801 and 802 Choose Continue.
1-1-1 Business Partner area
Field name or data type Values
BP JSU-##
Choose Manual Identification (system searches for business partner data and
order data)
Choose the Subscription Orders tab in the application area.
Application toolbar Subscription Orders: Create Order Subscription
Field name or data type Values
Sold-To Party JSU-##
Order Type ABO
Sales Organization ME02
Distribution Channel J8
Division J6
1-2 Application area: Select the row containing the new order.
Function bar M/SD Orders: Create Item
1-2-1 Choose Create standard item (SI)
Field name or data type Values
Publication JMH*
Sales Source SI
Sales Promotion SP-##
Purchase Reason 003
Service Type FD
Quantity 1
1-2-2 The buttons Delivery Address and Create Address allow you to record
additional delivery addresses for the business partner.
Field name or data type Values
Add. Name Field Hamptons Hotel
House Number ##
Street Name Evergreen Ln
City New Hampton
Region NY
Country US
Choose Copy to confirm or choose this additional address.
When you save the subscription, the system displays the following message:
Subscription xxx has been saved.
Choose Refresh in the navigation and application areas.
2-2 Customer JSU-## also wants an additional copy of the newspaper delivered to his place
of work.
2-2-1 Create an additional delivery address for the business partner: Hamptons
Hotel, ## Evergreen Ln, New Hampton, NY.
2-2-2 Create an additional item for 1 copy of JMH* for your order with the new
ship-to party address.
2-4 Your customer is not happy with the current publication and wants to change
publication from next week.
2-4-1 First, create a subscription for your subscriber JSU-##. The subscriber wants to
purchase the daily newspaper New Hampton News JMH*. The customer wants
1 copy. The customer approached you themselves, meaning that the purchase
reason is own initiative, and they request a full subscription with an annual
invoice.
2-4-2 Enter a change of publication from JMH* to another groups daily
newspaper. The customer gives insufficient quality as the delivery end reason.
Then display the order overview.
2-5 Subscriber JSU-## calls you because he now wants the main item of his subscription
delivered only to his home on weekends. From Monday through Friday, it is to be
delivered to his partners office.
2-5-1 Initialize your CIC view by means of the button Clear all fields in the business
partner search (trash can). Simulate a call with the telephone number 0719-
456##. Switch to Inwait mode.
Set the call status to 2 ringing. Enter the desired incoming telephone number in
the ANI field. The simulated call is from an external number and the caller
dialed extension 800.
2-5-2 Answer the call and display the orders for the business partner.
2-5-3 Choose the main item in the order created previously and access the function
Delivery Address Alternation (caution: in the case of existing subscriptions, you
will have to create an unlimited change to do this). Enter an alternate delivery
address for the sub-item for delivery on weekdays. The company address is:
Bright Lights Agency, ## Red Mill Rd, New Berlin.
2-5-4 Save the order and display the order overview.
2-6 Check the validity of the optimization rule by creating a new subscription without
delivery viability optimization for your sales customer JSU-##.
2-6-1 Then remove the indicator to deactivate delivery viability optimization.
2-6-2 How can you find out which delivery viability sets exist in the system?
All the exercises in this unit begin with the following menu path:
Logistics Media Sales and Distribution Periodical Sales and
Distribution Sales Order Customer Interaction Center Front
Office Front Office
2-1 Dialog box Choose Organization: Position: CIC Agent MSD (tel) Copy
Dialog box Settings not yet Maintained Do you want to make the settings now?
Yes
Dialog box Maintain Own Telephone Number Extension 123## Copy
Dialog box Queue Selection Choose queues 801 and 802 Choose Continue.
Business Partner area
Field name or data type Values
BP JSU-##
Choose Manual Identification (system searches for business partner data
and order data)
Application area Subscription Orders: Button: Create Order Subscription
Field name or data type Values
Sold-To Party JSU-##
Order Type SUBE
Sales Organization ME02
Distribution Channel J6
Division J8
Choose Create standard item (SI)
Field name or data type Values
Publication JMH*
Sales Source SI
Sales promotion SP-##
Purchase Reason 003
Service Type FD
2-2 Application area: Select the line containing the new order and double click to access the
item data.
Choose Edit Create Item Standard Item in the menu to create a further item for
your order.
The buttons Delivery Address and Create Address allow you to record additional
delivery addresses for the business partner. Choose Copy to confirm or choose this
additional address.
2-3 Application area: Select the row containing order item 10.
2-3-1 Redirection
Choose Redirection to create the redirection. Create a divert address on the
selection screen for the delivery address.
When you save, the system displays the following message:
Subscription xxx has been saved.
2-3-2 Suspension
Choose Suspension to create the suspension. Enter Vacation as the suspension
reason.
When you save, the system displays the following message:
Subscription xxx has been saved.
2-3-3 Refresh
Choose Refresh to see the changes in the order overview.
Content:
z Functionality of Internet services
z IAC technology
z Editing subscriptions in the Internet
z Postediting order data from the Internet
z Overview of Business Server Pages
SAP AG 2003
SAP AG 2003
Internet Application
Organization
Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Conclusion
Center (CIC)
SAP AG 2003
SAP AG 2003
Customer
Employee Business
Server Pages
Order entry
SAP AG 2003
WWW
SAP AG 2006
Website
Customizing
Store
Postediting
The data entered is enriched by means of Customizing tables that allow you to offer complex
subscription variants. The HTML link contains a reference to a full set of required data.
Type of Customizing data
y Control data
y Fixed data: cannot be modified on the Web page (for example, order type, sales area, ...)
y Variable data: can be modified by the Internet user if displayed for them on the HTML page
y Type of identification for change procedures
Temporary storage: Depending on the settings, all data or only data on procedures that contain errors
are stored here. You can postedit these records manually later on (report
RJKWWWTEMP_MONITOR).
Logging: Changes to and creation of orders is logged
Temporary storage
Selection Create
of order data from orders and business
temporary table partners
Edit
data in
temporary
storage
Delete
SAP AG 2003
If the data entered via the Internet cannot or is not to be used to create a subscription directly, this
data is stored temporarily. Possible reasons for this are:
y An error occurred that cannot be corrected in a user dialog.
y Some of the business partner data entered is duplicated.
y The Customizing settings for the Internet Application Component Subscription Sales specify
that all data is to be stored temporarily first.
You can easily postedit the data from temporary storage. The postediting procedure is as follows:
y Select order data to be edited
y Individual or Collective Processing -> Create Orders
y Check orders if applicable
y Delete entries from temporary storage
Errors are corrected during order creation as follows:
y If an error occurs, processing stops and a message is displayed -> in this case, the administrator
needs to correct the error
y If a duplicate is identified, the address data entered is compared with the existing data
-> the administrator must decide whether or not the business partners are the same.
Business
BSP
Web
Applications
SAP AG 2003
Like the SAP GUI, IACs (Internet Application Components) are screen-based (different screen
templates). An Internet Transaction Server is still required for existing IACs.
New Web applications use BSPs (Business Server Pages) and do not require an ITS. The
corresponding functions are transferred directly to the Web Application Server, which is a
component of the R/3 Application Server.
Implementation
of IS-M
IACs and BSPs
SAP AG 2003
SAP AG 2003
Wireless World News, New York also sells its products in the Internet.
The system is set up so that trial subscriptions and subscriptions
containing errors are stored temporarily in the system. You are
responsible for postediting these orders stored temporarily and correcting
errors so that they are created correctly in the system.
1-2 Check the temporary table for editing orders from the Internet.
1-2-1 Switch to the mySAP Media System.
1-2-2 Display the order you created in the Customer Interaction Center.
1-2-3 Call the Internet postediting transaction in a new session.
1-2-4 Choose the order you created.
(House number = group number)
1-2-5 Check the order data and create the order.
1-2-6 Now check the order in the Customer Interaction Center.
1-2-3 Logistics Media Sales and Distribution Periodical Sales and Distribution
Sales Environment Internet Connection Access to Internet
Postediting
Start postediting without changing the entries on the screen.
To display the incoming orders, double click on the line Orders.
1-2-4 Start postediting by double clicking on your order. Choose Change so that you
can postedit the order.
1-2-5 Check the data and create the order using the Create function.
The system displays the following message: Order xxx created and the
overview of orders for postediting will be refreshed
1-2-6 Switch to the Customer Interaction Center and display the data on your new
business partner.
Content:
z General shipping procedure
z Circulation planning
z Bundling and container packing
z Shipping document creation
z Shipping order
SAP AG 2003
SAP AG 2003
Internet
Organization
Application Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Conclusion
Center (CIC)
SAP AG 2003
SAP AG 2003
SAP AG 2003
Planning
Orders Circulation trigger
planning
Order
Deliveries
Order
Order
Drop-offs
Control data
Shipping document
creation
Delivery note Carrier list
SAP AG 2003
Functions in shipping:
y Circulation planning: Circulation planning for orders takes place for a specific period in the
future. Planning results in deliveries. These contain the delivery quantities for a carrier route (or
a geographical unit).
y Bundling: Delivery quantities for a carrier route or a geographical unit are packed in bundles. At
the same time, the system determines the unloading point at which bundles are to be unloaded
and which truck route serves this unloading point. The drop-off contains this data.
y Generation of shipping documents: Once bundling has been performed, shipping documents
can be created and printed.
Printing works
Sales area
Geographical unit
Sales orders Product
Carrier route
Edition
(subscription, retail, etc.) structures
Delivery type - Substitution
Customer group Order - Combination
Period
Delivery Order
viability set Daily
Paper 7/3
4
Circulation planning
Deliveries
SAP AG 2003
March
MoTuWeTh Fr Sa Su
1 2 3 4
5 6 7 8 9 10 11
12 13 14 16 17 18 19
20 21 22 23 24 25 26
27 28 29 29 30 31
Regen. planning
at any time Basic planning
for any period (regen. planning) Orders on hand
for all relevant orders
Order change 1
Netchange Netchange
order-related
for a period for which planning Order change 2
already performed
Netchange
Conclusion: Order change n
Planning takes place once
and is constantly updated. Netchange
SAP AG 2003
There are two basic procedures regarding the time and scope of planning:
Regenerative planning: You can use the planning trigger to perform circulation planning at any
time for any period in the future. The function processes all relevant orders. Order processing is
locked during this time. Any order changes made during planning using Internet Application
Components are saved to the temporary table for the IACs.
Netchange: If changes are made to order data affecting a period for which planning was already
performed, this procedure updates the planning values. This means the planning results are always
up to date.
SAP AG 2003
In the planning trigger, you specify a period in which circulation planning is to take place for the
orders for an edition. This can be any period in the future.
The status of the planning trigger controls whether or not deliveries are being generated for the
first time, and whether the deliveries in the specified period are to be deleted.
You can set a lock date to determine that regenerative planning does not plan the trigger until after
this date.
MoTuWeTh Fr Sa Su
1 2 3 4
5 6 7 8 9 10 11
12 13 14 16 17 18 19
20 21 22 23 24 25 26
27 28 29 29 30 31
Regen.
Edition
Planning period planning Delivery type
Deliveries
TH FR SA SU MO TU
03/01 03/02 03/03 03/04 03/05 03/05
SAP AG 2003
Once all the data required for circulation planning has been maintained, you can start planning in
SAP background processing.
Planning always takes place for a certain period for a trigger.
The publication structure (calendar, mix type definition) of the edition determines the days in the
time interval for the planning trigger on which deliveries are created.
ORDER CHANGES
10:00 15:00
t
Netchange Netchange
Deliveries
SAP AG 2003
Circulation
Shipping
planning
Logistical delivery type:
Airmail
SAP AG 2003
A distinction is made between order delivery types and logistical delivery types.
A delivery type can be defined as:
y An order and logistical delivery type
y An order delivery type
y A logistical delivery type
An order delivery type is specified at order acceptance. The delivery viability set for a geographical
area is defined by the order delivery type.
An example of an order delivery type is Postal Shipping. However, from a logistics perspective, the
order delivery type Postal Shipping can be processed using a variety of postal shipment types.
Corresponding logistical delivery types are created for these postal shipment types.
The logistical delivery type is determined for each order during circulation planning. You can use
customer-specific function modules (customer exits) to define rules for converting an order delivery
type to logistical delivery types.
Issue:
Technical Friday
order deadline
limit
SAP AG 2003
Order acceptance ends for a specific shipping date when the order deadline is set. The shipping
runs can start after this. The order deadline must be set for each shipping date.
The maximum number of days the order deadline can be entered in advance is defined by the
assignment of the "technical order deadline limit".
This is defined primarily to prevent errors when setting the order deadline.
You can deactivate the technical order deadline (latest date limit for the shipping date) in
Customizing. This means the order deadline is not checked against the technical limit when you
enter it. Deactivating the technical order deadline has the following effect:
y You do not need to define a technical order deadline limit.
y If a technical order deadline limit is defined, it is ignored by the system.
Deliveries
Unloading
Unloading rules
viability set
Bundling
Bundling
Bundle rules
Drop-offs
drop-offs
Truck
routes
Container
Container packing packing
rules
Container
drop-offs
SAP AG 2003
In bundling, delivery quantities for a carrier route (geographical unit) are assigned to full bundles
and odd bundles according to the bundling rule.
The unloading point for a carrier route is determined from the unloading viability sets.
The bundling procedure then determines which daily truck routes serve these drop-off points. This is
determined from the unloading point sequence, the truck route-edition assignment and the existing
daily truck routes.
In postal shipping, packs are created according to the bundling rules. Packs can then be packed in
containers. The unloading point is determined from the shipping schedule.
Bundling results can also be deleted.
Containers can be packed for logistical delivery types that refer to a postal shipping type postal
distribution items. Postal packs containing different issues can be packed together in a container.
Container packing takes place according to the postal pack and container packing rules. Container
packing is only possible when all postal packs have been packed for this shipping date.
Container
packing
SAP AG 2003
Containers can be packed for logistical delivery types that refer to a postal shipping type postal
distribution items.
Postal packs containing different issues can be packed together in a container.
Container packing takes place according to the postal pack and container packing rules.
Container packing is only possible when all postal packs have been packed for this shipping date.
SAP AG 2006
Postal packing rules refer to the ZEBU file provided by Deutsche Post AG, the German postal
service.
The ZEBU file is imported into IS-M/SD during system configuration.
The following manual maintenance functions are possible:
y Add new postal codes
y Delete postal codes
y Change IDs
The ZEBU data can also be updated using external files. When this is done, the system creates a log
of the changes to the ZEBU database.
The configuration settings for the system specify that postal packs have to contain a minimum of 10
issues before they can be packed on a packing level. Containers can be put together on a packing
level if they contain a minimum of 10 bundles or have a total weight of over 10 kg.
A checking program allows you to determine whether a postal packing rule exists on the ZEBU
database for each of a ship-to party's address postal codes.
Bundling
Drop-offs Container packing
Postal packs
Containers
1 Destinations
Shipping doc.
creation Control data
for shipping
doc. creation
Seq. file SAP spool
2
Shipping doc. printing
SAP AG 2003
Shipping document creation based on the bundling results (drop-offs) takes place daily in two
phases:
y Shipping document creation: If the bundling results (drop-offs) are available, the corresponding
shipping documents can be created. The shipping documents are output first to the SAP spool
files.
y Shipping document printing: The shipping documents created can be printed out individually
or as a group from the SAP spool to different output devices.
The program for shipping document creation requires a number of control elements. This increases
the flexibility of shipping document printing.
y Shipping documents can be created at any time and sorted.
y The printer can be determined according to various influencing factors. Shipping documents can
be sorted by means of field assignments and distributed to various output devices (printer, fax,
...). This enables decentralized shipping document creation in the same way as central creation at
the computer center.
y The user can determine which shipping documents are to be printed.
Truck route
loading instructions
Carrier
Truck route list delivery note
Shipping Container
Truck route
schedule document label
types
Customer Pack
pickup list label
Address
labels
SAP AG 2003
The shipping document type is set up in the configuration settings for the system. You can change
the form and content of a shipping document type.
In addition, defaults for printer control are stored in the shipping document type.
.............................. Plant
..............................
..............................
..............................
..............................
..............................
..............................
Delivery type
. . . . ..............................
....
. . . . ..............................
....
.... . . ... . . . ....
.... ...
.
.
... ....
Network
.... ... .
. ... ....
. ... .... Publication,
edition
Shipping Period
document type
SAP AG 2003
If a shipping document type is defined in the system, this does not mean that this shipping document
type is printed every day for each plant and publication.
The shipping document type that is actually to be printed on a shipping date is specified in the
shipping document type usage.
You define the supplying plant and delivery type (network) for which the shipping documents are to
be created for each corresponding shipping document type.
You can also create a shipping document type at a certain plant and for a delivery type for one
specific publication.
Example
Bundle labels for full bundles are only to be printed for the main edition of a publication Daily
Paper. In this case, you must define in the shipping document type usage that the bundle labels are
to be created at the supplying printing works for the delivery type home delivery and for the
publication Daily Paper.
1
r oute s 1
ck ork
Tru ting w
Prin
Printer Ramp 1
Tru
c
Truck route list Prin k rout
ting e 2
wor
ks 1
Printer Ramp 2
SAP AG 2003
Each shipping document type is assigned a logical destination, to which the corresponding shipping
documents are output.
A logical destination can represent a specific output device or a sequential dataset (for example, for
transferring shipping data to shipping systems).
You can create shipping documents for different logical destinations according to a variety of
criteria.
The logical output device is determined according to the shipping document type, the plant, and (if
you wish) the truck route, edition, and shipping outsorting type.
The combination of criteria and the order in which they are used to determine a destination is
specified in the shipping document destination search sequence.
Example:
The route list for Truck Route 1 is printed out from the printer located at Ramp 1. Truck Route 1
also departs from this ramp. The route list for Truck Route 2 is printed out from the printer located
at Ramp 2.
SAP AG 2003
SAP spool
Spool file 2
...
Spool file n
SAP AG 2003
Postal circulation
Small quantities
Small quantities
Small quantities
Direct delivery
Direct delivery
Direct delivery
Surcharge
Surcharge
Surcharge
t
No inserts 1 ad pre-print 2 ad pre-prints
insert
"Region" edition "Local" edition
SAP AG 2003
Production-related shipping documents (bundle labels, production plan) are sorted according to the
production sequence when they are created.
....................
....................
.................... Category (for truck route,
.... ....
.... ....
.... ....
edition, level)
Form
Shipping Function module for
document data retrieval
(ABAP/4)
type
Shipping document
type group
SAP AG 2003
The shipping document type is used to classify shipping documents that have the same appearance
and content every day.
The shipping document type is set up in the configuration settings for the system. You can change
the form and content of a shipping document type. From a technical point of view, a shipping
document type is assigned a function module for data retrieval and a form that defines the
appearance of the shipping document.
The form determines the layout of the shipping document, the position of the output fields, and the
font (size).
Specifications for output control (printer, fax, or file) are also recorded in the shipping document
type.
You define in the shipping document type whether the shipping document is truck route-related,
issue-related, or general and plant-related (shipping document type category).
The shipping document type level defines the following:
y Size of the interface for the data retrieval function module
y Dataset for which documents are created
A shipping document type can be assigned to a group of shipping documents. Shipping documents
that belong to a group can be sorted together for creation.
Sort criterion
1
Sort criterion
2
SAP AG 2003
You must define a sequence for creating shipping documents that are to be created together.
You must define this sequence for all truck route-related, issue-related, and general shipping
documents. Sorting control can also be defined on a more detailed level for a shipping document
type group.
Sorting is primarily controlled by the following criteria:
y Truck route date, truck route departure time, truck route number
y Sequence number of unloading point
y Edition number
y Logistical delivery type
y Shipping document type
y Vehicle departure date (time)
y Issue availability date (time)
The sort criteria depend on the shipping document type category.
Two
bundles Newspaper
missing missing
Complaint
Shipping problem message
Carrier route: Center
Missing qty: 2 bundles
Subs.delivery: by 12:00
Mail: Create
Message
to Shipping
SAP AG 2003
IS-M/SD provides the function shipping problem message to allow you to record and process
problems relating to delivery logistics. The function enables you to do the following:
y Record problems that occur when the delivery is on its way from the plant to the customer and
that are reported by a carrier or by the driver of a truck route.
y Trigger subsequent deliveries or special processing functions. When this is done, messages are
sent or displayed in the system.
y Display data on shipping problem messages received previously when recording complaints in
sales.
Example
The carrier reports that too few bundles were delivered in his carrier route. This problem is recorded
in the system as a shipping problem message and the necessary follow-up activities are triggered on
the basis of the information stored. The SAP R/3 output control functions allow you to send
messages to the administrators responsible.
Delivery and service problems reported by customers are recorded as customer complaints in sales.
If a shipping problem message already exists for the corresponding area, the system displays the
data on the problem message and the customer can be informed of any action taken. If subsequent
delivery is scheduled, no further subsequent deliveries can be recorded as a result of the customer
complaint.
SD orders
Shipping order
Addresses Addresses
Items Import
SAP AG 2003
The planning function generates deliveries for shipping orders from the specified shipping date. You
can specify the planning horizon number of days planning is to be performed in advance on the
screen for the shipping order.
There is no netchange procedure for deliveries for the shipping order. The deliveries are updated
immediately when shipping orders are changed. You should schedule planning for shipping orders
periodically (report RJVSO_PLANNING). You can also execute planning in dialog processing.
Items Import
Order deadline
SAP AG 2006
Deliveries
Shipping orders are included with the deliveries created in the normal shipping functions for
subscription sales and distribution.
A number of functions support the creation of shipping documents (for example, truck route lists,
address labels, carrier change notifications).
Home delivery settlement is also supported.
House number
and (optional)
house number affix
SAP Media
and (optional)
apartment/building z New BP role Household
Addresses z Autom. BP assignment
Transfer household z Manual BP assignment
addresses with preferences z Exclusion of BP
Allowed delivery type assignment to
Excluded delivery type household addresses
Business partner
(subscriber)
Address 1
1 household only per
BP address
Address 2
SAP AG 2004
As of release 4.71, you can enter SAP business partners in the new role Household.
Entering addresses as households allows you to personify delivery addresses for total market
coverage.
You can assign each household you create in the system to an existing customer. Customers are
assigned to households in their address data. To determine a customer address for a household, the
system searches by street, house number, and house number affix. You can assign customers to
households as follows:
In dialog processing: Once you have entered the address for the business partner Household, the
corresponding customer address in the system is assigned automatically in background processing. If
the system finds several customer addresses for one household address, it lists the possible addresses
for selection in a dialog box. You can assign one customer only to a household.
In batch input: If households are created in batch input, the system assigns the one appropriate
customer address to each household. If there are several possible customer addresses for one
household address, it is not possible for the system to assign the addresses in background processing.
In such cases, you must postedit the data manually.
You can prevent a customer from being assigned to a household by selecting the indicator Exclude
household assignment in the corresponding customer master record.
4 Shipping orders
Create shipping orders
for all households to
Shipping order per household
be supplied
SAP AG 2004
As of release 4.72, you can distribute free publications to the households in your distribution areas
using market coverage functions.
Market coverage allows you to include all the households in a distribution area for delivery, even
those that are not currently customers of your publishing company.
An example of a market coverage product would be a free weekly magazine containing primarily
local advertising that is distributed to all households in a region. The market coverage product is
created in the system as a media product (with an indicator for market coverage). Market coverage
products are always assigned to a carrying product. The new indicator Market coverage combination
is selected for the market coverage product in the data on the carrying product, specifying that
separate combination is possible.
The following market coverage options are possible for a carrier route (home delivery) or
geographical unit (postal or direct delivery):
Market saturation:
y Deliveries are made to all households irrespective of whether they receive the carrying product.
Total market coverage:
y Deliveries are only made to households that do not receive the carrying product.
You can define delivery viability sets for market coverage products or use reference products to
determine carrier routes and geographical units. Exception: If the market coverage product contains
ad inserts from Advertising Management orders, you cannot use reference products.
You can exclude households on certain carrier routes or in certain geographical units from market
coverage. To exclude households from market coverage, you can also assign them certain delivery
types, which you can later use to filter them when generating the orders for market coverage.
+ home delivery
and settlement
of SD materials
Carrier route
New Berlin
Home delivery planning involves the following
steps:
9 Include material in home delivery planning
9 Include order items for this material in
planning
9 Generate home delivery data for these
planning records
SAP AG 2006
Implementation
of IS-M
Shipping
SAP AG 2003
SAP AG 2003
Unit: Shipping
Topic: Shipping
1-1 Enter an order deadline for your publication JMH* of 1 day before the shipping date and
an order deadline of 2 days before the shipping date for the two delivery types labeled
periodical post and reduced charge shipment.
1-2 Check the bundling rule for your publication JMH* and correct it accordingly.
1-2-1 The full bundle of newspapers contains 20 copies and the odd bundle a
minimum of 6 copies. The bundling rule is valid from the current date + 1.
1-3 Enter the following shipping document types in the shipping document type usage for
your publication JMH*:
SDoc.Type Text Plant Delivery Type Postal Shipping
Network
1000 1-col.add.label ME20 PA, PD 01
1006 LPP label ME20 PA 01
3003 Route load. list ME20 01, PA, PD
3005 Rt. loadg. instr. ME20 01, PA, PD
3006 Route plan ME20 01, PA, PD
Please note the postal shipping network.
SAP AG IMD320 11-37
Validity: Current date to last day in the year 9999
Destination A000; number of printouts 1
1-4 Carry out quantity planning for your publication for the next 2 months.
Users can block each other during this procedure. We recommend that the groups
take turns with this exercise.
1-4-1 Maintain the planning trigger for your publication.
1-4-2 Execute regenerative planning.
Unit: Shipping
Topic: Shipping
The exercises in this unit all begin with the following menu path:
Logistics Media Sales and Distribution Periodical Sales and
Distribution Master Data Shipping
Content:
z Functions in billing
z Control options in order billing
z Creating billing documents
z Transferring billing documents to Financial Accounting
z Integration of IS-M/SD with Contract Accounts Receivable and
Payable, IS-M/CA
z Revenue accrual
SAP AG 2003
SAP AG 2003
Internet Application
Organization
Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Conclusion
Center (CIC)
SAP AG 2003
SAP AG 2003
Order Invoice
100.--
100.--
.
Credit memo Cred.memo
request 10.--
! + 10.--
! - 10.--
Invoice Reversal
Invoice 100.--
100.--
SAP AG 2003
Billing doc.
Business data
overview Business data
Partners
Items in indiv.
billing doc. Partners
Output
FI accounting
Texts document Texts
SAP AG 2003
Subscription
Subscription
order billing doc.
in advance
t
Subscription
Subscription billing doc.
change in retrospect
SAP AG 2003
The billing method defines whether an order is billed in advance or periodically in retrospect.
You can define the billing method in Customizing for each combination of order type and item type.
The billing frequency is transferred to the billing data on the order item when the subscription is
created.
The following default settings are provided with the standard delivery for subscription orders:
y Standard subscription item: in advance
y Limited subscription changes: in retrospect
Publication
(media product
family)
Billing
calendar
SAP AG 2003
Billing arrangements can either be maintained globally or specifically for individual publications
(media product families).
y Billing frequency:
- (Without billing calendar) period for rolling billing
- Criterion for advance payment discount
y Billing calendar: determines billing schedule for the next billing documents
y Price frequency:
- Price frequencies for which prices are maintained
- Price frequency used for the billing frequency
t
January September
Invoice B
10 PC
10 x 10.50
Discount 2%
Order 10 PC Invoice C
Delivery
10 PC
10 x 9.50 10 x 10.50
Ed.1 10 PC Discount 2%
Manual discount Delivery
Manual discount
Invoice D/G
10 PC
10 x 9.50
Manual discount
SAP AG 2003
The pricing type determines which condition elements are copied unchanged from the reference
document (order or billing document) and which are redetermined using the condition technique.
The pricing type is set up for specific orders and billing types in the Customizing settings for the
document flow. The following pricing types are possible for billing:
y A
The prices are copied from the order and updated according to the billing quantity. This pricing
type only applies to SD. It is not used in IS-M/SD.
y B
Pricing is repeated.
y C
Pricing is repeated. Manual price components are copied. This pricing type is specified as the
default value in Customizing for all order types for billing.
y D
The price components are copied unchanged from the reference document. This pricing type is
specified as the default setting in Customizing for reversal billing documents.
y D
The price components are copied unchanged from the order. The tax conditions are redetermined.
If price fixing is specified in the order, this pricing type overrides the standard setting. This is
repeated until the price fixing limit is past.
1
Create Reverse 100.--
billing index
2 Billing
item 80.--
SAP AG 2003
The system copies the data from the reference document to the reversal document and transfers an
offsetting entry to Financial Accounting if the billing document in question has already been
transferred. If an invoice has not been forwarded to Financial Accounting, the reversal document
cannot be forwarded either.
Billing can be repeated for the orders in the reversed invoice. This is done by creating a new billing
index for the billing period for all the relevant orders.
This mechanism also reverses credit and debit memos.
Credit and debit memo requests are processed like order items in billing. You create a billing item
preceded by a plus or minus sign, which is then inverted when reversal takes place.
Selection criteria
Payer: C1
by May 15
Subs. Subscription
order billing doc.
Date Payer Doc.
Order 1
May 12 C1 1
Subs.
order
May 12 C1 2
May 14 C2 3 Order 2 Subscription
May 15 C1 4 Subs.
billing doc.
order
May 17 C1 5
Order 3
Log
SAP AG 2003
SAP AG 2003
The function Simulate billing is basically the same as the function Create billing document, but only
has the function keys and authorizations for the function Display billing document.
The function can be accessed at the following points in the system:
y From the initial Billing screen
y From the screen Create Billing Document - Central Access
Billing Billing
calendar frequency
Subs.
order
by May 15
Subs.
Order 1 Billing order
Document by
Subscription
Subs.
billing doc.
order
Order 1 May 15 Order 1
Subs.
Order 2 order
Coll. processing
Subs.
Order 2 May 15
order
Order 2
SAP AG 2003
Due dates for billing, in other words the dates on which invoicing takes place, are defined in the
business transaction in question.
For example, you can define the following billing due dates in the order item:
y Billing on fixed calendar dates
y Rolling billing, in other words, billing performed in a certain frequency from the start of the
billing period
Specifications on billing due dates can be found in the billing data on the order item.
In Subscription Sales and Distribution, you can define default values for the order item in
Customizing.
Subs.
order
2 Invoice split Subs.
billing doc.
Subs.
order Subs.
billing doc.
SAP AG 2003
Order items can be included with other order items in collective invoices or in several individual
invoices according to criteria specified in billing.
You can control billing by specifying custom criteria (in Customizing for document flow) for
specific transactions. These criteria are used to control invoice splitting (invoice criteria). The
following invoice criteria always apply:
y Payer number
y Bill-to party number
y Sales organization
y Billing date (from calendar or frequency)
y Terms of payment
y Payment method and bank details
y Indicator for separate invoice
Delivery subscription
Delivery-related liability account
Billing frequency: 3 deliveries
Billing
Billing Billing Suspension Billing
t
Delivery 1 ... Delivery 4
Cycle
Liability acct
Amortization Bill. Amort.
3 del. 1 del.
SAP AG 2003
As of Release 4.02, you can create billing documents for a fixed number of deliveries (copies). After
shipping has taken place for the first delivery, a new cycle is created in the order for the liability
account and the billing document is then created. After shipping, revenue accrual takes place based
on amortization installments. In the case of a suspension, the next billing date is moved.
After shipping has taken place for the last delivery in the cycle, all the amortization postings are
reconciled with the postings from billing document transfer. Any differences that arise are
reconciled in Financial Accounting. Reconciliation takes place in a liability account transfer.
Prerequisites:
y There must be a delivery-related liability account for the order.
y A cycle is run for the liability account for each billing document. This requires a special order
type in which the type of liability account is specified.
y The billing frequency is defined as a number of deliveries. This also applies to the price
frequency if period prices are used instead of unit prices. (Alternatively, you can define the
billing frequency using a time unit. If this is the case, the number of billed deliveries is
determined using the publication calendar.)
y You must define amortization installments for amortization. Revenue account determination
takes place for the amortization installment based on the amortization procedure. This is
necessary for performance-related revenue accrual.
Set
billing due date
Customer
exit
SAP AG 2003
As of Release 4.02, you can use a customer exit (customer enhancement) to influence the billing
date in the billing index determined from the settings in the order item, the billing due date.
The customer exit is accessed in the following cases:
y When a billing index is created in order processing
y When the next billing index is created in billing for order items that are to be billed at regular
intervals
y When a billing index is created on reversal of a billing document
t
Suspension Minimum amount
undershot
Suppress Suppress
billing doc. creation billing doc. creation
Customer Customer
exit exit
SAP AG 2003
As of Release 4.02, you can use a customer exit (customer enhancement) to suppress billing
document creation and postpone it to a later date.
You can make use of this option in cases such as the following:
y Order suspension (for example, the bill-to party is away on vacation)
y Minimum amount for billing not reached
1. Check Customer
Billing FI documents
documents 2. Update 8300001 Debit Credit
3000011
8300002 107 .-
3000027
8300003
3000030 Revenue
8300004
3000031
Debit Credit
Transfer
100 .-
107.00
107.00
VAT
Debit Credit
7 .-
FI/CO
IS-M/SD FI CO
interface
SAP AG 2003
You can specify in Customizing that billing documents are to be transferred to Financial Accounting
by means of the FI/CO interface. This technique posts the data directly to Financials when the billing
documents are transferred.
Advantages:
y Changes to the document architecture, in particular to dialog, do not have any effect.
y Batch input sessions are no longer required.
y Internal document number assignment in Financial Accounting.
y Distribution to the external FI system takes place using ALE.
Processing using the FI/CO interface is divided into the following parts:
y Consistency check on data. (For example, a zero balance check is performed for the FI
document.)
y Update data to the database. (The data is only updated if all checks have been run and no errors
identified.)
The data must be transferred via the FI/CO interface before revenue accrual can be processed.
Instead of data transfer via the FI/CO interface, you can transfer the billing document to the general
ledger by means of the contract account.
IS-M/SD
Billing
documents
Intermediate
payment dataset
SAP AG 2006
The following transfer types can be used to transfer billing documents to Accounts Receivable
Accounting, depending on the payment method:
Single transfer
Open items are created in the customer accounts in Accounts Receivable Accounting. (The
customer account can be created automatically if necessary.) A posting is made to the customer
account as an offsetting entry. If a VAT registration number exists for the customer, a single
transfer takes place.
Collective transfer
No open items are generated. A posting is made to the clearing account for the house bank to
offset the postings to the G/L account. The system creates a payment dataset for each collective
transfer. The payment program in Financial Accounting generates the payment documents and
the data for the payment media on the basis of the payment dataset.
Payment card transfer
A special kind of single transfer. A posting is made to the receivables account for payment cards
to offset the postings to the G/L account. An additional posting is made to the customer account
(which is cleared automatically) if this is specified in Customizing.
Collection transfer (not included in the diagram)
Several billing documents can be grouped in an accounting document. A posting is made to the
account for the service company to offset the postings to the G/L account.
SAP AG 2003
z Business partner
Contains central data such as names, addresses,
communication data, and bank details
Represents a natural person or a legal entity with
whom a company has a business relationship
z Contract account
Contains control data such as payment methods,
payment terms, and dunning procedures
Object for which open item accounting takes place in
Contract Accounts Receivable and Payable
BP IS-M/CA
Usually represents a group of
subscription orders Account Account
SAP AG 2006
SAP AG 2003
Order Billing
item item Transfer Document FI-GL
+ doc. type
+ transaction Origin: Transfer FI-GL
Account Media Sales
+ receivables and Distribution
Contract assgmt account
account data
SAP AG 2003
Contract Accounts Receivable and Payable is based on the document, which contains:
Document header
Contains the data that applies to all the document line items, such as the document date, posting
date, and reconciliation key.
Business partner items (receivables or reconciliation posting lines)
These items contain all the data relevant for payment transactions and dunning and the
receivables (reconciliation) account to which debit or credit postings were made.
The document types
differentiate between the business transactions
control document storage by means of the number ranges assigned. The document number is
determined from the number ranges when a document is posted.
apply throughout the client
Examples of document types include: general document, charges, billing
The transaction
represents a business transaction
is divided into a main transaction and a subtransaction: for example, main transaction billing,
subtransaction receivables, credit
The receivables account
The reconciliation account in the customer master record is used as the receivables account when
transferring billing documents to Contract Accounts Receivable and Payable.
FI/CO
IS-M/SD FI CO
interf.
SAP AG 2003
During billing document transfer, revenue is distributed evenly among the periods affected.
The periods in the accrual interval are determined according to the financial calendar.
Proportional revenue distribution can be influenced using a customer enhancement.
Recurring entry documents are not created, but the revenue is transferred at regular intervals when
due.
FI/CO
IS-M/SD FI CO
interf.
SAP AG 2003
Customer
FI/CO
IS-M/SD FI CO
interf.
SAP AG 2003
When the billing document is transferred, the revenue is distributed evenly between all the issues in
the billing period.
Revenue posting takes place after shipping for the issue.
When revenue is posted, CO account assignment can be performed for the issue.
The CO order is not determined until the revenue from the issue is transferred.
SAP AG 2006
You can execute the following activities in dialog processing in the Revenue Accrual Cockpit for
each type of revenue accrual (period-related, per issue, performance-related with liability account,
liability account closure):
y Create check list (FI documents generated when transferring revenue accruals)
y Display worklist (for revenue accrual transfer)
y Reverse FI documents from the check list
The function for transferring revenue accrual can also be used to create check lists or worklists in
SAP background processing, depending on the type of revenue accrual in question.
SAP AG 2003
Wireless World News, New York creates the advance billing documents
regularly required for its subscriptions each day. Credit and debit memos
originating from order processing are taken into account.
The billing documents and accrued revenue are transferred to Financial
Accounting.
You are responsible for processing billing in the system.
1-5 Analyze your billing documents from the overview in the navigation area in the
Customer Interaction Center.
1-5 Sales Order Customer Interaction Center Front Office Front Office
Choose organization: CIC Agent MSD (tel)
Queue selection: Select both and choose Continue.
Wireless World News, New York creates billing documents for its
subscriptions each day.
The billing documents and accrued revenue are transferred to Financial
Accounting.
You are responsible for processing billing in the system.
2-1 Before billing can take place for a renewal subscription, you must first simulate an
incoming payment. This incoming payment represents the acceptance of the offer that
preceded it and triggers the creation of a billing index.
2-1-1 Create a renewal subscription and note down the following values:
BP number
Assignment number
Subscription price
Order number
2-1-2 Create the payment lot ##. Enter the currency US Dollars for the posting
document. The bank clearing account for the company code ME02 is with the
Mellon Bank. Use the current date as the value date.
2-1-3 Create a new item for your payment lot ##, containing the payment amount, the
assignment number, and the business partner number.
2-1-4 Close and post the payment lot. Then check the expiration date in the order.
Content:
z Functions in service settlement
z Home delivery settlement
z Commission settlement
SAP AG 2003
SAP AG 2003
Internet
Organization
Application Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Conclusion
Center (CIC)
SAP AG 2003
SAP AG 2003
Service Sales
Carrier agent
company
Service settlement
Carrier Home delivery Commission sion
settlement Commis ent
settlement for settlement for m
settle
serv. company serv. comp.
SAP AG 2003
The settlement type defines the services for which settlement is performed for which business
partner. The following service types are defined in the system:
Carrier settlement: Settlement is performed by the service company and includes all home delivery
services performed by the carrier for the service company. Settlement can always be performed for
the employees of the service company if it is the media company itself, or if it is a linked company
that is co-administered in the same system.
Home delivery settlement for service company: Settlement is performed by the media company
and includes all home delivery services performed by the service company for the media company.
Commission settlement: Settlement is performed by the service company and includes all services
performed by the sales agent for the service company with a view to obtaining orders, if the media
company itself is the service company, or if it is a linked company that is co-administered in the
system.
Commission settlement for service company: Settlement is performed by the media company and
includes all services performed by the service company for the media company with a view to
obtaining orders.
Service company
1 Accounting
Settlement
100.--
100.--
Normal carrier
2
Settlement Human Resources
Home
WType xy:400.--
delivery
WType xz:100.--
Substitute carrier
3
Settlement Human Resources
WType xy:400.--
WType xz:100.--
SAP AG 2003
Settlement for carriers or service companies that perform home delivery services is performed based
on daily shipping data (deliveries or home deliveries).
If a substitute carrier performs home delivery, the carrier substitution type determines whether or not
the service is relevant to settlement for the normal carrier who was replaced. This enables you to
perform settlement according to the "as if" principle for carriers who are replaced.
The process can be regarded from the following two perspectives:
Services performed by service company (1)
Services performed by individual carrier: in this case, the normal carrier (2) and the substitute
carrier (3).
Service
company
Accounting
1 Settlement
100.--
Order 100.--
Order
Order
Order
.. .
Order
Order
..
Order
Order
.. 2 Human Resources
Settlement
.. Commission
WType xy:400.--
. recipient
WType xz:100.--
SAP AG 2003
Settlement for commission recipients takes placed on the orders on hand that they have obtained.
Terminations and reversals are taken into account and retroactive accounting is performed if
necessary.
The process can be regarded from the following two perspectives:
Services performed by service company (1)
Services performed by individual commission recipient (2)
Business data
Settlement Business data
overview
Partners
Partners
Output Settlement
items
Texts Texts
SAP AG 2003
Selection criteria
Service company: S1
Home delivery
by May 15
Settlement
Date SC EE
May 12 S1 C2 Settlement
May 14 S2 C3
May 15 S1 C1
Home delivery
May 17 S1 C1
Log
SAP AG 2003
Employee "Vendor"
settlement settlement
HR FI FI
Payroll data
(i.e. gross wage)
G/L accounts Vendors
SAP AG 2006
Delivery round in
carrier route
Period
Mo Tu We Th Fr Sa Su Weekday
Carrier 1 Carrier 1 k
Sic Carrier/SC
Carrier 2 Carrier 2
Substitution
type
$ $ $ $ Settlement?
SAP AG 2003
The assignment of a carrier (or field collector) to a delivery round in a carrier route is defined in the
home delivery round. You can maintain the following attributes:
Validity period in which the carrier works the delivery round.
Service company and carrier (depending on the membership status of the service company).
The system checks that an employment relationship (relevant for employee settlement) and
settlement data on the service company (relevant for SC settlement) exist.
Weekdays on which the carrier is deployed (in the validity period of the home delivery round).
Settlement relevance
Substitution type (Carriers and service companies can be replaced by other carriers and service
companies in the period of the home delivery round.)
Calendar Settlement
FI HR
t
SAP AG 2003
Settlement data is maintained in different locations depending on the type of settlement in question:
For employee settlement, the settlement data is stored in the employment relationship.
For service company settlement, the settlement data is stored in the purchasing organization
segment.
Attributes of settlement data:
Expense account assignment group
Terms of payment
Transfer type: determines whether settlement is to be transferred to Financial Accounting or
Human Resources
Personnel number: for use if settlement is transferred to Human Resources (employee number)
$/PC $/PC
SAP AG 2003
The contract arrangements define the compensation to be settled for carriers and service companies.
Settlement can take place based on one of the following basic remuneration types:
Carrier route flat rate
Daily edition average (for example, measured over a month)
Period edition average (remuneration for the average quantity per weekday)
Daily rate for edition
April
Path Path comp. 20.00 Run
Run comp. 12.00
compensation Key comp. 30.00 compensation
62.00
Key
compensation
Key compensation
Path length category category Path category
SAP AG 2003
The contract arrangements contain three different flat rate bonuses that can be credited to the
carrier/service company in settlement for each delivery round:
Path compensation
Run compensation
Key compensation
The flat rate bonuses are listed in the settlement item Carrier route flat rates. Remuneration is also
influenced by the individual bonus categories defined for the carrier route.
SAP AG 2003
The daily bonuses can be paid on different days (working day, public holiday with delivery, public
holiday without delivery).
The following daily bonuses can be used in remuneration:
Daily path compensation: Remuneration is influenced by the path length category in the carrier
route
Insert bonus: Calculated according to the number of inserts in the issue
Weight bonus: The weight is calculated from the number of pages, the page format, and the
weight of paper. The weight calculated automatically can be changed in the issue. The weight
bonus can be calculated according to the net weight (weight of issue) or the gross weight (net
weight + weight of inserts).
Sunday bonus, night bonus, public holiday bonus: You can maintain a category for each bonus
and remuneration day.
Sales source
Sales
promotion Publication
Campaign
framework Order1 Order2
Order3
SAP AG 2003
Commission settlement is performed based on the orders obtained by a commission recipient. IS-
M/SD supports the following commission settlement types:
Commission settlement for commission recipients who work for an owned or co-administered
service company
Commission settlement for external (or co-administered) service companies
Besides the general influencing factors of the employment relationship and purchasing data for the
service company, commission settlement is influenced by the following special criteria:
Campaign framework
The campaign framework is used to define settings for sales support activities that depend on the
sales source and sales promotion that lead to the creation of orders. You can specify in the sales
source that commission is granted for obtaining orders. Each campaign framework is assigned
the allowed commission recipients. You can define commission data (one-time commission or
renewal commission, promotion rebate) for each commission recipient. Only one commission
recipient can be specified in the sales document based on the campaign framework.
Conditions
The commission amount to be paid is defined in the commission master data.
nt
Su
on
me
bs
cti
ttle
Su
cri
du
se
bs
g
pti
ro
illin
cr
ion
on
int
ip
b
iss
bil
tio
ery
ion
lin
mm
no
liv
ipt
g
WBZ
co
De
rd
cr
subscription Ship-to
er
Ship-to
SC
bs
Su
processing party
party
SAP AG 2003
WBZ (Werbender Buch- und Zeitschriftenhandel = subscription book and magazine trade) is a form
of sales and distribution specific to Germany. WBZ companies advertise and sell subscriptions for
other media companies in their own name and receive commission for this service in the form of
promotion rebates.
Commission settlement for WBZ companies takes place in service company settlement. For this
purpose, WBZ companies must be created as external service companies.
The relevant Customizing settings for commission settlement for WBZ introduction services include
the following:
y Sales source for WBZ commission
y Condition type for WBZ promotion rebate
y Pricing procedure for WBZ promotion rebate
SAP AG 2003
Unit: Settlement
Topic: Settlement
Wireless World News, New York employs carriers and sales agents to
supply its customers and win new ones.
You are responsible for preparing periodical settlement of these internal
and external service providers services.
1-3 Maintain the data required for commission settlement. Use the employment relationship
you created for the commission recipient JCR-## and service company JSC-##.
1-3-1 Maintain the settlement data for your service company JSC-## with the
following data:
Currency USD, exchange rate type M, tax code I0, procedure STDPV1 (SC
commission settlement), calendar JM, valuation type 1 (quantity x price),
transfer type 1.
Unit: Settlement
Topic: Settlement
The exercises in this unit all begin with the following menu path:
Logistics Media Sales and Distribution Periodical Sales and
Distribution
Content:
z Basic functions of the condition technique
z Condition elements for pricing and output determination
z Condition master data
SAP AG 2003
SAP AG 2003
Internet
Organization
Application Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Conclusion
Center (CIC)
SAP AG 2003
SAP AG 2003
Application
Application Application
Application 11
Procedure
Procedure 11
Procedure
Procedure 22
Pricing procedure Procedure
Procedure ...
...
Cond.
Cond. type
type 11
Cond.
Cond. type
type 22
Condition control
Access
Access seq.
seq. 11
Access sequence Access
Access seq.
seq. 22
Access
Access seq.
seq. ...
...
SAP AG 2003
The pricing and output determination functions are based on the SAP condition technique. The
condition technique transfers application data to condition control, where they are used to determine
conditions. Conditions are specified both for prices and for output.
Condition elements
Application: Each application that uses the condition technique is assigned an application ID.
Pricing procedure: A procedure is a pool of condition types. An application determines a procedure
from the current document type and transfers it to condition control. This means the procedure is a
collection of condition types grouped according to application characteristics.
Condition type: A condition type groups conditions that have the same meaning. It contains
parameters that apply to all the conditions assigned to it.
Access sequence: An access sequence is a strategy used by the system in condition determination to
find valid values for the condition proposal. It determines the order in which the condition tables are
processed. The system searches for conditions in the condition tables. You can specify that the
system is to stop processing the condition tables in the access sequence as soon as the search
identifies a condition (exclusive indicator).
Condition access: When the system accesses a condition table, it enters values from application
fields in the key fields in the table. The condition table is then read using the key defined in this
way.
Condition table: A proposal is created in the condition technique when a condition type is
determined successfully.
Document
Document
Item
Item 10
10 11 COP
COP
Order
Order Type
Type ABO
ABO
Sales Org.
Sales Org. ME02
ME02
Dist.
Dist. Channel
Channel J6
J6
Division
Division J8
J8
Doc.
Doc. Pric.
Pric. Proc.
Proc. A
A
SAP AG 2003
A subscription order is created with one copy. The system is to determine the price automatically.
Pricing
Pricing Procedure
Procedure ZS_SUB
ZS_SUB Document
Document
1.
1. Net
Net Purchase
Purchase Price
Price ZRPR
ZRPR Item
Item 10
10 11 COP
COP
2.
2. Item
Item Discount
Discount ZRCA
ZRCA Order
Order Type
Type ABO
ABO
3.
3. Adv.
Adv. Payment
Payment Disct
Disct ZAPD
ZAPD Sales Org.
Sales Org. ME02
ME02
4.
4. Special Offer
Special Offer Disct
Disct ZSPD
ZSPD Dist.
Dist. Channel
Channel J6
J6
5.
5. Customer
Customer Discount
Discount ZCDS
ZCDS Division
Division J8
J8
6.
6. Shipping Costs
Shipping Costs ZSHC
ZSHC Doc.
Doc. Pric.
Pric. Proc.
Proc. A
A
SAP AG 2003
The pricing procedure is determined from the Customizing settings according to the order type, sales
organization, distribution channel, division, and document pricing procedure.
Pricing
Pricing Procedure
Procedure ZS_SUB
ZS_SUB Document
Document
1.
1. Net
Net Purchase
Purchase Price
Price ZRPR
ZRPR Item
Item 10
10 11 COP
COP
2.
2. Item
Item Discount
Discount ZRCA
ZRCA Order
Order Type
Type ABO
ABO
3.
3. Adv.
Adv. Payment
Payment Disct
Disct ZAPD
ZAPD Sales Org.
Sales Org. ME02
ME02
4.
4. Special Offer
Special Offer Disct
Disct ZSPD
ZSPD Dist.
Dist. Channel
Channel J6
J6
5.
5. Customer
Customer Discount
Discount ZCDS
ZCDS Division
Division J8
J8
6.
6. Shipping Costs
Shipping Costs ZSHC
ZSHC Doc.
Doc. Pric.
Pric. Proc.
Proc. A
A
Condition
Condition Type
Type ZSHC
ZSHC
Access
Access Sequence
Sequence ZSHC
ZSHC
SAP AG 2003
The access sequence is determined from the condition type on the first level.
Pricing
Pricing Procedure
Procedure ZS_SUB
ZS_SUB Document
Document
1.
1. Net
Net Purchase
Purchase Price
Price ZRPR
ZRPR Item
Item 10
10 11 COP
COP
2.
2. Item
Item Discount
Discount ZRCA
ZRCA Order
Order Type
Type ABO
ABO
3.
3. Adv.
Adv. Payment
Payment Disct
Disct ZAPD
ZAPD Sales Org.
Sales Org. ME02
ME02
4.
4. Special Offer
Special Offer Disct
Disct ZSPD
ZSPD Dist.
Dist. Channel
Channel J6
J6
5.
5. Customer
Customer Discount
Discount ZCDS
ZCDS Division
Division J8
J8
6.
6. Shipping Costs
Shipping Costs ZSHC
ZSHC Doc.
Doc. Pric.
Pric. Proc.
Proc. A
A
Condition
Condition Type
Type ZSHC
ZSHC
Access
Access Sequence
Sequence ZSHC
ZSHC
Access
Access Sequence
Sequence ZSHC
ZSHC
Condition
Condition Tables:
Tables:
1.
1. DelTy/ServTy/CtryGrp
DelTy/ServTy/CtryGrp 705
705
2.
2. DelType/ServType
DelType/ServType 706
706
SAP AG 2003
The system reads the access sequence. The order in which the condition tables are specified in the
access sequence defines how the corresponding condition record is determined.
The condition records are accessed with the specified key for each condition table.
Pricing
Pricing Procedure
Procedure ZS_SUB
ZS_SUB Document
Document
1.
1. Net
Net Purchase
Purchase Price
Price ZRPR
ZRPR Item
Item 10
10 11 COP
COP
2.
2. Item
Item Discount
Discount ZRCA
ZRCA Order
Order Type
Type ABO
ABO
3.
3. Adv.
Adv. Payment
Payment Disct
Disct ZAPD
ZAPD Sales Org.
Sales Org. ME02
ME02
4.
4. Special Offer
Special Offer Disct
Disct ZSPD
ZSPD Dist.
Dist. Channel
Channel J6
J6
5.
5. Customer
Customer Discount
Discount ZCDS
ZCDS Division
Division J8
J8
6.
6. Shipping Costs
Shipping Costs ZSHC
ZSHC Doc.
Doc. Pric.
Pric. Proc.
Proc. A
A
Condition
Condition Type
Type ZSHC
ZSHC
Access
Access Sequence
Sequence ZSHC
ZSHC
Access
Access Sequence
Sequence ZSHC
ZSHC
Condition
Condition Tables:
Tables:
1.
1. DelTy/ServTy/CtryGrp
DelTy/ServTy/CtryGrp 705
705
2.
2. DelType/ServType
DelType/ServType 706
706
Records
Records in
in Table
Table 705
705
No
No valid
valid records
records
Records
Records inin Table
Table 706
706
Valid
Valid record
record found
found
SAP AG 2003
The system searches for valid condition records for the condition tables.
If the system does not find a valid condition record the first time it accesses the data, it continues
searching by accessing the data a second time.
Pricing
Pricing Procedure
Procedure ZS_SUB
ZS_SUB Document
Document
1.
1. Net
Net Purchase
Purchase Price
Price ZRPR
ZRPR Item
Item 10
10 11 COP
COP
2.
2. Item
Item Discount
Discount ZRCA
ZRCA Order
Order Type
Type ABO
ABO
3.
3. Adv.
Adv. Payment
Payment Disct
Disct ZAPD
ZAPD Sales Org.
Sales Org. ME02
ME02
4.
4. Special Offer
Special Offer Disct
Disct ZSPD
ZSPD Dist.
Dist. Channel
Channel J6
J6
5.
5. Customer
Customer Discount
Discount ZCDS
ZCDS Division
Division J8
J8
6.
6. Shipping Costs
Shipping Costs ZSHC
ZSHC Doc.
Doc. Pric.
Pric. Proc.
Proc. A
A
Condition Net
Net Purchase Price
Purchase Price 12.00 USD
12.00 USD
Condition Type
Type ZSHC
ZSHC
Shipping
Shipping Costs
Costs 24.00
24.00 USD
USD
Access
Access Sequence
Sequence ZSHC
ZSHC Subscription
Subscription Price
Price 36.00
36.00 USD
USD
Access
Access Sequence
Sequence ZSHC
ZSHC
Condition
Condition Tables:
Tables:
1.
1. DelTy/ServTy/CtryGrp
DelTy/ServTy/CtryGrp 705
705
2. Records
Records in
in Table
Table 706
706
2. DelType/ServType
DelType/ServType 706
706
Records Sales
Sales Org.
Org. ME02
ME02
Records in
in Table
Table 705
705
Division
Division J8
J8
No
No valid
valid records
records Publication
Publication JMDP
JMDP
Delivery
Delivery Type
Type 04
04
Records
Records inin Table
Table 706
706 Service
Service Type
Type MO-SA
MO-SA
Valid
Valid record
record found
found Amount
Amount 24.00
24.00 USD
USD
SAP AG 2003
When a valid condition record is found for access, the system reads the record and copies the value
to the sales document.
These steps are repeated for each condition type until the entire pricing procedure has been
processed. In this way, the net retail price is determined.
Home delivery
Commission Order/billing
Postal
Postal charges
charges
SAP AG 2006
The applications order/billing, and carrier, commission, and postal charge settlement all access
pricing and provide the data required for condition determination.
Postal charge settlement is only supported for Germany.
Pricing
Pricing conditions
conditions
Validity
Validity period
period e.g.
e.g. 03/01-05/31
03/01-05/31
Prices
Prices Surcharges
Surcharges and and discounts
discounts
-- Purchase
Purchase price
price of
of publication
publication -- Shipping costs
Shipping costs
-- Purchase
Purchase price of edition
price of edition group
group -- Advance
Advance payment
payment discount
discount
-- Subscription
Subscription price of
price of publication
publication -- Special
Special offer discount
offer discount
-- Subscription
Subscription price
price of
of edition
edition group
group -- Customer
Customer discount
discount
-- Unit
Unit price
price -- Customer
Customer group
group discount
discount
-- Customer
Customer unit
unit price
price
-- Unit
Unit price
price of
of special
special edition
edition
SAP AG 2003
Sales
Sales order
order
Address
Address change
change
Billing
Billing
Shipping
Shipping
problem
problem
message
message
Settlement
Settlement
Bank
Bank returns
returns
research
research
Complaint
Complaint
Subscription
Subscription
monitoring
monitoring
System
System
resubmission
resubmission
Order/carrier
Order/carrier
route
route research
research
Settlement
Settlement
SAP AG 2003
The applications order, billing, settlement, complaints, system resubmission, settlement, address
changes, shipping problem message, bank returns research, subscription monitoring, and
order/carrier route research all access output determination and provide the data required for
condition determination.
Output
Output determination
determination conditions
conditions
Processing
Processing Form
Form Partner
Partner roles
roles Shipping
Shipping time
time
program
program
Shipping
Shipping medium
medium
SAP AG 2003
SAP AG 2003
Wireless World News, New York used its standard price for daily
newspapers for the new daily paper until now. This is now about to
change with the introduction of publication-specific prices.
You are responsible for recording the flexible retail prices in your system.
Wireless World News, New York copes with the large volume of order
changes from its subscribers using automatic correspondence.
You are responsible for output determination in the system.
1-2 What is the sales price of the subscription and how is it composed?
___________________ ____________ USD
___________________ ____________ USD
___________________ ____________ USD
1-2-1 What is the condition type for the purchase price?
_______________________
What is the condition type for the shipping costs?
_______________________
1-4 Create a new order with the same publication for your customer from 1-1.
1-4-1 What is the sales price of the subscription now and how is it composed?
___________________ ____________ USD
___________________ ____________ USD
___________________ ____________ USD
Compare the result with that in 1-1, using the condition determination analysis.
1-2 Choose the Conditions tab in the view Subscription Order: Item Data.
Purchase price________ 195.00______ USD
Sales price______ 195.00______ USD
1-2-1 Choose Analysis to display the pricing analysis for the pricing procedure.
Condition type for purchase price: ZRPR
Condition type for shipping costs: ZSHC
1-4 Sales Order Customer Interaction Center Front Office Front Office
Choose the Conditions tab in the view Subscription Order: Item Data.
Purchase price________ 208.00______ USD
Shipping costs______ 312.00______ USD
Sales price______ 520.00______ USD
1-4-1 Choose Analysis to display the pricing analysis for the pricing procedure.
Content:
z Circulation auditing
IVW (Germany)
ABC (USA)
SAP AG 2003
SAP AG 2003
Internet
Organization
Application Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Conclusion
Center (CIC)
SAP AG 2003
SAP AG 2003
Deliveries
Orders
} Update
Daily IVW statistics
(JITSTAT)
IVW hierarchy/ies
Evaluations and
auditing programs
SAP AG 2003
JVTLFNG-XIVWFORTS = 'X'
Deliveries
(various data)
Delivery update
Assignment Daily IVW statistics
RJIIVW00 (JITSTAT)
Sales orders
(basic IVW category)
Return update
Return during posting
orders
SAP AG 2003
A distinction is made between the following two areas when updating daily IVW statistics:
y Update of delivery quantities
y Update of return quantities
Deliveries that have been updated are marked with a flag. This prevents the update from being
repeated for the same deliveries. This also means the program can be restarted (for example, if
processing is canceled).
Sel. criterion
Orders
Evaluations and
IVW hierarchies auditing programs
Basic reference category .....
SAP AG 2003
IVW hierarchy/ies
Evaluations and
auditing programs
SAP AG 2003
When executed as a live run, the auditing program sets a flag in the IVW statistics (JITSTAT-
XIVWMELD). Once this flag is set, returns can no longer be entered for the month in question
(return date).
The following applies to the IVW evaluations that interpret the hierarchy:
y The total is not calculated as a sum but instead is derived from the Draw field for the relevant
issues.
y The difference between the grand total and the total of all basic categories is displayed in the
basic category "calculated remainder" (which must be included in every hierarchy).
y Background: The actual draw (which is also audited) is a value defined by the printing works. It
should not be confused with the total number of copies delivered.
SAP AG 2003
Assignment;
Assignment; Control
Control
determination
determination Control
Control data:
data: data,
data,
program
program programs,
programs, relevant
relevant programs
programs
Audit report characteristics
characteristics
category Various
tools
}
Orders
Update
Circulation book
(JITCIRCBOOK)
Deliveries Influence
Influence
Audit Evaluations
reports
SAP AG 2003
The audit report type controls the way in which the circulation figures for an edition are managed
and the procedure for reporting these figures, if applicable. The audit report type has the following
characteristics:
y Audit report categories assigned to the report type
y Control settings for determining and assigning the valid audit report category for an order (item
level) (default setting for ABC: new determination table, logic priority-controlled, table TJI15)
y Assignment of update programs for the circulation book; outsorts relevant characteristics
y Control settings for various tools for managing the circulation book
Default settings, programs, and function modules are supplied for the audit report type ABC. These
can be customized as follows:
y By changing the settings for the audit report type ABC (replacing standard function modules or
changing the relevancy of characteristics)
y By creating a customer-specific report type with changed settings
Note: In Release 4.62, the audit report type IVW (for Germany) is also available with the circulation
book. Past IVW updates are transferred to the circulation book by means of a migration report.
JVTLFNG-XIVWFORTS
JVTLFNG-XIVWFORTS == 'X'
'X'
Deliveries
Sales
orders
Assignment
} Periodical
update
of delivery
quantities
Posting of
Circulation
book
backdated
order changes
Audit
reports
Return
Return update
orders during
posting
SAP AG 2003
A distinction should be made between the following areas for the circulation book update:
y Update of delivery quantities for publication dates (periodical job)
Default setting for audit report type ABC: Report RJIABC00 (schedule as background job)
y Immediate order update for:
- Backdated order changes (pricing criteria, audit report category in order)
- Returns
y Various (customizable) function modules are responsible for the order update.
Deliveries that have been updated are marked with a flag. This prevents update from being repeated
for the same deliveries and allows you to restart the program if, for example, processing terminates.
Reported periods are created and cancelled as audit reports by means of a service program. These
reported periods influence posting of backdated changes (changes to reported periods are not
allowed) and entry of returns for reported periods.
This means reported periods are protected and cannot be changed.
SAP AG 2003
Internet
Organization
Application Components
Geographical Structures
Settlement
and Change Management
Distribution Pricing
Customer Interaction
Conclusion
Center (CIC)
SAP AG 2003
SAP AG 2003
SAP AG 2003
SAP AG 2003