IMD320 - SAP For Media - Periodical Sales and Distribution EN

IMD320 SAP for Media Sales and Distribution of
Periodicals
IMD320
SAP for Media Periodical Sales and
Distribution
THE BEST-RUN BUSINESSES RUN SAP
SAP AG2009
SAP AG 2009
SAP for Industries

SAP for Media
Version 92
Material number: 5009 6753
Copyright
Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in
any form or for any purpose without the express permission of
SAP AG. The information contained herein may be changed
without prior notice.
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
Notes for use

These training materials are not intended for use as teach-yourself programs. They will only give
you a full picture in combination with the course instructor's explanations. You should have plenty
space in your course materials to note down this additional information.
In some cases, you may not have time during the course to complete all the exercises. The exercises
provide you with additional examples, which are explained during the course. Participants can also
use these examples to consolidate their knowledge after the course.
Course Overview
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 IMD320 1-1

Course Goals
This course will prepare you to:

z understand the functions and standard processes
in subscription sales and distribution in IS-M and
the way in which they are linked
SAP AG 2003
SAP AG IMD320 1-2

Course Goals
At the conclusion of this course, you will be able to:
z Describe and use the basic functions in

subscription sales and distribution
SAP AG 2003
SAP AG IMD320 1-3

Course Content
Preface
Unit 1 Course Overview Unit 9 Sales

Unit 2 Organization Unit10 Internet Application
Components
Unit 3 Business Partner
Unit 11 Shipping
Unit 4 Media Product Master
Unit 12 Pricing and Output
Unit 5 Change Management and Determination
Geographical Structures
Unit 13 Billing
Unit 6 Distribution Master Data
Unit 14 Settlement
Unit 7 Sales Support
Unit 15 Reporting
Unit 8 Customer Interaction Center
Unit 16 Summary
Exercises and Solutions

SAP AG 2003
SAP AG IMD320 1-4

Course Overview: Overview Diagram
Course Overview Sales
Internet Application
Organization
Components
Business Partner Shipping
Media Product Billing
Geographical Structures and

Settlement
Change Management
Distribution Master Data Pricing
Sales Support Circulation Auditing
Customer Interaction
Summary
Center (CIC)
SAP AG 2003
SAP AG IMD320 1-5

Overall Business Scenario
z Wireless World News, New York sells four regional

issues of the daily newspaper Daily Paper, with the
weekly insert TV Magazine and the Weekly Paper
weekly newspaper. The magazine Monthly
Magazine is published internationally. All the
regional editions can contain ads and ad inserts
(such as ad pre-prints and CDs).
SAP AG 2003
SAP AG IMD320 1-6

Features of Subscription Sales and Distribution
Master data
Materials Promotions Bus. partners Products Geo. structures Carrier routes Truck routes
Business Information Warehouse

Web applications CIC
Order management
Statistics / reporting
Sales Subscription orders AI orders Bundling

support Shipping
Orders Planning
Commission Billing Home delivery

settlement Single invoice Collective invoice Collection settlement
HR Payroll HR
FI Financial Accounting FI
Customers Vendors G/L accounts
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.
SAP AG IMD320 1-7

SAP AG IMD320 1-8
Exercises
Unit: Getting Started with SAP R/3

Topic: SAP R/3
At the conclusion of these exercises, you will be able to:

log on to the R/3 system
navigate in the R/3 system
create several sessions
explain the meaning of the symbols
change user profiles
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-1 Log on to the R/3 System.
1-2 Which menu options are displayed in the work area Logistics/ Media Sales and
Distribution/ Periodical Sales and Distribution?
1-3 Describe two different ways of accessing an application.
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-5 Create a second and third session in two different ways.
1-6 Which master data can you maintain in the Logistics application Media Sales and
Distribution/ Periodical Sales and Distribution?
1-7 Enter an address in your user profile.
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
Unit: SAP R/3 Introduction

Topic: SAP R/3
1-2 Menu path:

Logistics Media Sales and Distribution Periodical Sales and Distribution
Master Data
Sales Support
Sales
Shipping
Billing
Settlement
Circulation Auditing
MDIS/Sales and Distribution
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:
Sales Order Customer Interaction Center Front Office Front Office
Menu bar:
Extras Technical details
The transaction code is CIC0.
1-5 Menu bar:

System Create session
or standard toolbar:
Choose the "Creates New Session" pushbutton.
SAP AG IMD320 1-11

1-6 Menu path:
Media Sales and Distribution Periodical Sales and Distribution Master Data
Business Partner
Product Master (Periodicals)
Media Product Master
Distribution
Shipping
Organizational Structure
Marketing
Output
Conditions
1-7 Menu bar:

System User profile Own data Address
1-8 Menu bar:

System User Profile Own Data Defaults Date Format
European Date: DD.MM.YYYY
American Date: MM/DD/YYYY
SAP AG IMD320 1-12

Exercises
Unit: Getting Started with the Tools

Topic: Tools

use the field help and the value help
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?
SAP AG IMD320 1-13

SAP AG IMD320 1-14
Solutions
Unit: Getting Started with the Tools

Topic: Tools
2-1 Menu:
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
SAP AG IMD320 1-15

SAP AG IMD320 1-16
Organization
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 IMD320 2-1

Organization: Unit Objectives
At the conclusion of this unit, you will be able to:

z understand the organizational elements that can
be used to reproduce an enterprise structure in
the R/3 System
SAP AG 2003
SAP AG IMD320 2-2

Organization: Course Overview Diagram
Organization
Components
Settlement
and Change Management
Distribution Pricing
Customer Interaction Center

Unit Summary
(CIC)
SAP AG 2003
SAP AG IMD320 2-3

Organization: Business Scenario
z Wireless World News, New York sells print media

using the USA sales organization.
z Sales and distribution takes place using the direct
sales distribution channel.
z Products are assigned to the newspaper/magazine
division.
z The combination of sales organization, distribution
channel and division produces the sales area.
z The Berlin and New York sales offices are
responsible for the sales area.
z New Media in New York is the sending plant.
SAP AG 2003
SAP AG IMD320 2-4

Organizational Structures in the SAP System
Views Organizational units
Cost accounting Company
Controlling area
External logistics Sales org. Purchasing org.
Accounting Company code
Valuation area
Internal logistics Plant

(planning/production)
SAP AG 2003
Aims of the organizational structure in R/3:

y Increased flexibility in mapping complex company structures
y Providing a means to take account of changes to the company structure
y Separation of logistics (purchasing, sales and distribution) from internal accounting and financial
accounting
y Processing no longer restricted to company codes
SAP AG IMD320 2-5

Accounting Organization
Client
Company Company Company

code 1 code 2 code 3
business business
area area business
area business
1 2 1 area
business business business 1
area area area
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.
SAP AG IMD320 2-6

Sales Organization: Distribution Channels
Sales
organization
USA
Distribution channels
Direct sales Direct

Wholesale
Subscription retail
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.
SAP AG IMD320 2-7

Sales Organization: Product Divisions
Sales
organization
USA
Product divisions
Newspapers Magazines
SAP AG 2003
Product divisions allow you to make groupings in your range of products.

Typical product divisions could be newspapers and magazines.
You can organize sales and distribution purely in product divisions.
You can set up individual customer specifications (regarding pricing or terms of payment, for
example) for each division.
You can also carry out statistical evaluations or set up a separate marketing department within one
division.
SAP AG IMD320 2-8

Sales Organization: Sales Areas
Sales Organization
Sales Sales
organization organization
Distribution Division
Channel USA DE
Wholesale Newspapers Magazines Magazines
Retail Newspapers Magazines
Subscription sales Magazines
SAP AG 2003
A sales area is defined as a combination of

y Sales organization
y Distribution channel
y Division
The sales area can be used to specify which publications can be sold using one distribution channel.
You can define all sales-related data for each individual sales area. This means, for example, that
price agreements with specific customers can be defined for each sales area.
You can perform evaluations within one sales area (for example, organize the sales volume for each
sales area).
SAP AG IMD320 2-9

Internal Organization in Business Development
and Sales
Sales office 1 Sales office 2
Sales area Sales area

Sales Sales
USA USA
Sales area Sales area

Sales Sales
USA USA
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.
SAP AG IMD320 2-10

Plants
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.
SAP AG IMD320 2-11

Assignment of Sales Organization and Plant
Client
Company Company
code 1 code 2
Sales Sales Sales
organization organization organization
USA USA USA
Plant 1 Plant 1 Plant 2
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.
SAP AG IMD320 2-12

Purchasing Organization
Client
Company Company
code 1 code 2
Purchasing Purchasing
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.
SAP AG IMD320 2-13

Purpose of Customizing
SAP AG Wireless World News
Standard mySAP system

( Specific organization
Standard mySAP system ( Specific requirements
SD FI
MM CO Customizing
AM
IS-M
PS
PM WF
HR IS-M SD
FI
M/SD M/AM
SAP AG 2006
SAP AG IMD320 2-14

Features of Customizing
Provides a structured
procedure for system Provides tools for
implementation and system settings
enhancement Customizing
IMG
Provides control tools

for management,
performance and Makes
evaluation of recommendations
Customizing projects on system settings
(default values)
Provides
documentation on
individual system settings
SAP AG 2003
Customizing has the following features:

y Provides a structured procedure for implementation and enhancement of the SAP System.
y Provides tools for system settings and their documentation
y Provides control tools for management, performance and evaluation of implementation and
enhancement projects
y Makes recommendations for system settings
y Supports transfer of system settings from the test system to the production system
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
SAP AG IMD320 2-15

System Settings
System settings are used to modify the SAP System to

company-specific process flows.
Customizing tables are maintained here.
Company-specific values
Customizing
tables
SAP AG 2003
SAP AG IMD320 2-16

Implementation Guide (IMG)
IMG Features of the IMG

Unit 1
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).
SAP AG IMD320 2-17

Attributes of an IMG Activity
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
Each IMG activity is structured as follows:

y Assignment to application components
y Assignment to procedure model (such as represent basic data, set up number ranges, define
functions and processes).
y Classification of an activity as required, optional or not required).
y Classification of an activity as critical or non-critical).
To reduce the number of implementation steps required, you can use attributes to create views for
each implementation project, such as required activities, all critical activities, all activities for a work
package in the procedure model (such as activities that represent the basic data).
The system uses the application components to make the selection during generation of the company
IMG. All IMG activities, which are assigned to the selected application components, are included in
the company IMG.
SAP AG IMD320 2-18

System Settings for mySAP Media
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
System settings are divided as follows:

y General cross-application settings
y Settings for organizational units
y Settings for specific applications
(such as Financial Accounting, Customer Service, Media Sales and Distribution, Advertising
Management)
Global settings and settings for the organizational structure are found in the standard IMG. The IMG
structure for IS-M contains a simplified version of the standard settings for the organizational
structure, tailored to meet publishers' requirements.
Publisher-specific settings can be found in the application-specific section of the IMG structure.
SAP AG IMD320 2-19

System Settings for Organization
Represent
company
structure
Definition: Assignment: Consistency check:

Plant - company code
Company Code Purch.org. comp.code Company structure
Sales and distribution
Business area Sales org: company
Assign purchasing org.
Plant code
To sales area
Division Dist. channel - sales org.
Sales organization.... Sales area...
SAP AG 2003
SAP AG IMD320 2-20

Organization: Unit Summary
You are now able to:

z understand the organizational elements that can
be used to reproduce an enterprise structure in
the R/3 System
SAP AG 2003
SAP AG IMD320 2-21

SAP AG IMD320 2-22
Business Partner
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 IMD320 3-1

Business Partner: Unit Objectives

z name the business partner roles in Subscription
Sales and Distribution and their purpose
z describe the IS-M-specific data structure of the SAP
business partner master record
z create a business partner in different roles and
change their master data
z change a business partner's address in central
address management
z record employment relationships
z maintain system settings for business partner
SAP AG 2003
SAP AG IMD320 3-2

Business Partner: Course Overview Diagram
Organization
Components
Geographical structures
Settlement
Unit Summary
Center (CIC)
SAP AG 2003
SAP AG IMD320 3-3

Business Partner: Business Scenario
z Wireless World News, New York delivers its

newspapers and magazines to subscribers using
home delivery or by post.
z Some of the service providers (carriers, agents,
researchers) are employees of the company's own
service company and others are employees of an
external contractor.
z Wireless World News, New York is constantly
expanding its clientele. It also hires new service
providers (carriers, agents, researchers etc.)
z Changes are recorded for existing business
relationships.
SAP AG 2003
SAP AG IMD320 3-4

Business Partner Roles in Subscription Sales &
Distribution
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
SAP AG IMD320 3-5

Customers and Service Providers in Subscription
Sales & Distribution
Roles depending on business relationship
Service Carrier
Sales
Employment relationship
customer company
Researcher
Commission
recipient
Field
collector
Customer Service provider

(vendor)
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 IMD320 3-6

Classification of Business Partners
Classifying roles in subscription sales
Association Social facility Internal department
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 IMD320 3-7

Order-Related Customer Roles
Customer roles in the order
Sold-to party Ship-to party
Bill-to party Payer
SAP AG 2003
A customer can have the following order-specific roles in order processing:

y Sold-To Party
y Ship-To Party
y Bill-to party
y Payer
SAP AG IMD320 3-8

SAP Business Partner
Sales customer Commission recipient Researcher Service company
SAP SAP
Banking Utilities
General data Vendor General data

Company code Customer supplier Company code
data data
Sales area data Purchasing org.
data
FI FI
SD MM
SAP AG 2003
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.
SAP AG IMD320 3-9

Advantages of the SAP Business Partner
Business
partner
Business
Data
Toolset
Administration of Adjustment of business

central business partner master without
partner data modifications
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 AG IMD320 3-10

Data Structure of the SAP Business Partner
SAP BP (IS-M)
Role- Sales
Central Bank details with Payment
specific area
data additional data cards
data data
FI / SD
Customer Vendor
Company Sales Company

Central Central
code area code
data data
data data data
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.
SAP AG IMD320 3-11

Central Data
Customer-specific data Business Partner Application-specific data

can be integrated
without e.g. IS-M-specific
modification Central or role-specific data
data
Cross-application data:
Identifying data (category, type, grouping)
Name and address
Personal or organization data
Bank details and payment cards
SAP AG 2003
Cross-application administration of central business partner data

y Identifying data (category, type, grouping)
y Name and address
y Personal or organization data
y Bank details and payment cards
Further data
y Application-specific data (e.g. IS-M-specific or role-specific data)
y Customer-specific data can be integrated without modification
SAP AG IMD320 3-12

Identifying Data
Grouping Business partner type

same as the account Defined in
group in the previous Customizing
business partner
Used to distinguish
master Business between business
determines the number partner partners
range used
Identifying
Identifying data
data Fields can be shown
For example: or hidden according
internal to the business
external partner type
Business partner cat.

Natural person
Organization
Group
SAP AG 2003
Business partner category

y Natural person
y Organization
y Group
Grouping
y same as the account group in the previous business partner master
y determines the number range used
Business partner type
y freely definable grouping of business partners defined in Customizing
y fields can be shown or hidden according to the business partner type
SAP AG IMD320 3-13

Subscription Sales and Distribution-Specific Data
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)
Sales area-specific data Accounting-specific data

(SD customer master (Company code data SD
record) customer master record)
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.
SAP AG IMD320 3-14

Relationships Between Business Partners
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.
SAP AG IMD320 3-15

Data Maintenance
Select Adjust
maintenance maintenance
screens dialog
Data according Lisa Miller Field status

to business partner according to field
category (e.g. natural modification criterion
person, organization) and field group
Required
Optional
Hidden
Display
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.
SAP AG IMD320 3-16

Central Address Management
Family Miller, New Berlin
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.
SAP AG IMD320 3-17

Employment Relationship and SC Membership
Own SC Co-administered SC External SC
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.
SAP AG IMD320 3-18

System Settings for Business Partner
Implementation
SAP Business
Partner
Account Customer: Vendor: SAP BP Assign SAP

groups Billing Settlement tables BP groupings
Roles calendar calendar Set up using to FI account
Number range Blocking Carrier type migration tool groupings
etc. reasons for Sales agent
order billing type
document, Employment
customer types
procedures etc.
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.
SAP AG IMD320 3-19

Set Up SAP Business Partner (Migration)
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 IMD320 3-20

Business Partner: Unit Summary

z name the business partner roles in Subscription Sales
and Distribution and their purpose
z describe the IS-M-specific data structure of the SAP
business partner master record
z create a business partner in different roles and
change their master data
z change a business partner's address in central
address management
z record employment relationships
z Maintain system settings for business partner
SAP AG 2003
SAP AG IMD320 3-21

SAP AG IMD320 3-22
Exercises
Unit: Business partner

Topic: Business Partner Master Data

name the business partner roles in Subscription Sales and Distribution
and their purpose
describe the IS-M-specific data structure of the SAP business partner
master record
create subscribers, carriers, researchers, commission recipients and
service companies and change their master data
record employment relationships
Wireless World News, New York is constantly expanding its clientele.

You are an employee of the US sales organization (ME02) and are
responsible for maintaining business partner master data.
Make the following assignment, wherever this is requested:

Company code ME02, sales organization ME02, distribution channel J6,
division J8, and grouping External number assignment.
1-1 Create a subscription customer JSU-## with the following data:

1-1-1 Your subscriber, Ms. Miller, resides at ## Bailey Rd, New Hampton, New
York, US, and is single. Enter general business partner data. Do not forget to
enter her telephone number: 0718-456##.
1-1-2 Ms. Miller pays with the following terms of payment: 14 days - 3% cash
discount, 30 days - 2% cash discount, 45 days net. Her payment currency is
USD, the exchange rate type for your house currency is M. She is subject to
tax (tax classification: liable for tax (reconciliation account: 140050).
1-2 Create a carrier JCA-## with the following data:

1-2-1 Mr. Nadler lives at ## Milo Rd, New Hampton, and is married. He is an
employee of your company and his personnel number is ##.
1-2-2 Mr. Nadler is an individual carrier and delivers titles. Accounting is performed
for his services by standard translation at the average rate.
SAP AG IMD320 3-23

1-3 Create a commission recipient JCR-## with the following data:
1-3-1 Mr. Banfield lives at 2## Echo Lake Rd, New Hampton, New York. He is an
employee of your company with the personnel number 1## and is a full-time
sales agent.
1-4 Create a service company JSC-## with the following data:

1-4-1 Service Company Inc. has its headquarters at ## Training Center Ln, New
Hampton, New York. Its purchasing organization is ME02 (New Media).
1-4-2 Your company owns the service company (membership status: own). It is
managed in company code ME02 and is responsible for home delivery,
research, and introductions (sales agent activities). The service company
belongs to company code ME02.
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.
SAP AG IMD320 3-24

Solutions
Unit: Business partner

Topic: Business Partner Master Data
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
1-1 Edit Business Partner

Button Create Person
Field name or data type Values
Business Partner JSU-##
Grouping External number range BP
Create in Role Sales Customer/Contr Part
Change to Another Role in Create Mode: The system queries whether you want to create
the business partner in the role of Sales Customer or save them in the role of General BP
first and change the data afterwards.
Choose Create.
1-1-1 General Data
Address tab
Title Ms.
First Name Jane
Last Name Miller
Correspondence Language EN
House Number ##
Street Bailey Rd
City New Hampton
Region NY
Country US
Telephone 0718-456##
SAP AG IMD320 3-25

Identification tab
Gender Female
Marital Status Single
1-1-2 Company Code button

Company Code ME02
Account Management tab
Reconciliation Account 140050
Payment Transactions tab
Payment Terms 0002
Sales Area Data button
Sales Organization ME02
Distribution Channel J6
Division J8
Orders tab
Currency USD
Exchange Rate Type M
Billing Document tab
Tax Classification (country US) 1
When you save the business partner, the system displays the following message:
Business partner JSU-## created

Business Partner JCA-##
Create in Role Carrier/Contr Part
SAP AG IMD320 3-26

the business partner in the role of Carrier or save them in the role of General BP first and
change the data afterwards.
Choose Create.
1-2-1 General Data
Address tab
Title Mr.
First Name John
Last Name Nadler
House Number ##
Street Milo Rd
City New Hampton
Region NY
Country US
Identification tab
Gender Male
Marital Status Married
Employee X (select)
Personnel Number ##
1-2-2 Carrier tab
Carrier Type 1
Title Carrier X (select)
Business partner JCA-## created

Business Partner JCR-##
Create in Role Commission Recipient/CP
SAP AG IMD320 3-27

the business partner in the role of Commission Recipient or save them in the role of
General BP first and change the data afterwards.
Choose Create.
1-3-1 General Data
Address tab
Title Mr.
First Name Martin
Last Name Banfield
House Number 2##
Street Echo Lake Rd
City New Hampton
Region NY
Country US
Identification tab
Gender Male
Employee X (select)
Employee Number 1##
Commission Recipient tab
Sales Agent Type 1
Business partner JCR-## created

Button Create Organization
Business Partner JSC-##
Create in Role Service Company/Contr
Par
the business partner in the role of Service Company or save them in the role of General
BP first and change the data afterwards.
Choose Create.
SAP AG IMD320 3-28
1-4-1 General Data
Address tab
Title Company
Name Service Company Inc.
House Number ##
Street Training Center Ln
City New Hampton
Region NY
Country US
Language English
Media Control Data tab
Purchasing Organization ME02
1-4-2 Service Company tab
Membership Status 1
Company Code ME02
Home Delivery X (select)
Research X (select)
Sales Agent Role X (select)
Company Code button
Company Code ME02
Account Management tab
Reconciliation Account 160000 (proposed entry)
Planning Group A1
Business partner JSC-## created
SAP AG IMD320 3-29

1-5 Connections Employment Relationship Edit
Service Company JSC-##
Employee JCR-##
Commission Recipient (role) (select)
1-5-1 Service Company Employment Relationship: Create

Currency USD
Procedure STDPM1
Settlement Calendar JM
Valuation Type 1
Tax Code I1
Transfer Type None
To create the employment period, choose the Insert Line button and enter the
following data:
Valid From Current date
Valid To Last day in the year 9999
Employment Type 02
Choose Copy.
Employment relationship JSC-##/ JCR-## created
SAP AG IMD320 3-30

Media Product
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 IMD320 4-1

Media Product: Unit Objectives

z Explain the product structure in Subscription
Sales and Distribution
z Describe the data structure of the media product
master and product synchronization
z Describe the data objects that define a media
product for Subscription Sales and Distribution
(for example, mix offer)
z Create and change media product hierarchies
z Describe the system settings for the media
product master
SAP AG 2003
SAP AG IMD320 4-2

Media Product: Course Overview Diagram
Internet
Organization
Application Components
Settlement
Conclusion
Center (CIC)
SAP AG 2003
SAP AG IMD320 4-3

Media Product: Business Scenario
z Wireless World News, New York sells the following

regional products:
Daily newspaper Daily Paper with four local editions
(New Berlin, New City, Newport, and Norwood) and the
weekly insert TV Magazine
Weekly newspaper Weekly Paper (delivered to the
distribution area on Thursdays)
z The magazine Monthly Magazine is published
internationally on the first of each month
z As an employee of the publishing house, you are
responsible for maintaining the product master data
SAP AG 2003
SAP AG IMD320 4-4

Product Structure in Subscription Sales and
Distribution
Newspapers Magazines
Media product family TV

Daily
Title Paper Magazine
(newspapers, magazines)
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.
SAP AG IMD320 4-5

Issue Mix
Media issue Inserts Issue mix
Title inserts Ad inserts

IAL
EC
SP FER
O F
IAL
EC
SP FER
O F
+ =
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)
SAP AG IMD320 4-6

Issue Variant Types
Monday Friday Saturday

Daily Paper Daily Paper Daily Paper
7/34 7/34 7/34
Sports Real Estate Employment
Customizing Public holiday

Standard
variant type:
Friday edition
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).
SAP AG IMD320 4-7

Product Mix
Media product family Media product
Control data Mix types
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
SAP AG IMD320 4-8

Mix Types
Mix type 01 Mix type 02
IAL IAL
EC EC
SP FER SP FER
OF OF
With ad inserts Without ad inserts

(ad pre-prints, CDs, etc.) Without combination
Combination with media With insertion
products delivered separately
With insertion
SAP AG 2003
A media product can be sold in various mix types.

The mix type determines which other media products (TV guide, regular inserts) are supplied in
combination with it.
SAP AG IMD320 4-9

Mix Type Definition for Subscription Sales and
Distribution
Ad insert Insertion
IAL
EC
SP FER
OF
o
es/n
Norwood Y Norwood
Substitution Combination
Daily Paper
Norwood
Mon, +
Wed, Fri
Norwood New City
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
SAP AG IMD320 4-10

Mix Type Definition - Insertion
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.
SAP AG IMD320 4-11

Mix Type Definition - Combination
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.
SAP AG IMD320 4-12

Mix Type Definition - Substitution
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.
SAP AG IMD320 4-13

Service Type
Service type (full Order

subscription) 270000
Variant type
Monday
Tuesday
Wednesday
Thursday Media issue

Friday
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.
SAP AG IMD320 4-14

Mix Offer
Mix Offer
Media product Sales document
Media product Norwood Order
270000
Mix type No ad pre-prints
Purch.freq. Full subscription
Delivery type Home delivery
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.
SAP AG IMD320 4-15

Issue Sequence
Assign defaults Copy Calendar

Weekday Template media product MoTuWeThFrSaSu
1 2 34
Choose
5 6 7 8 91011
Variant type Relevant weekdays 12131416171819 publication
20212223242526
Template media issue Template media issue 272829293031
dates
Create entries
Issue sequence Generate media

Media issue issues
Status
Publication date
Variant types
Template issue, etc.
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.
SAP AG IMD320 4-16

Media Product Master Browser
Media Product Master Hierarchy
Family Create Edit

Selection
MPM Hierarchy Data
Media product MP Family
master
MProduct
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.
SAP AG IMD320 4-17

Mass Maintenance of Media Product Master Data
Mass maintenance in the SAP System
Object type BUS1001

General Change
change single value
Tables
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.
SAP AG IMD320 4-18

Product Synchronization
Product master (periodicals)

Sales Issue
Publication Edition
issue mix
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.
SAP AG IMD320 4-19

Moving a Media Issue
Media product Media issue

master
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
Change category (Customizing)
Periodical product master

Issue Production Order (M/SD) Order (M/AM)
unit
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.
SAP AG IMD320 4-20

Publication Period
Period: Week Dailies
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
Period: Year Non-dailies
Grid Jan Feb Mar Nov Dec

Indiv. period 1 2 3 11 12
Period date 01/01 02/01 03/01 11/01 12/01
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).
SAP AG IMD320 4-21

System Settings for Media Product Master
Implementation
of IS-M
Media Product
Configuration: Basic settings: Settings for: Settings for Sales Publication:

- Data screens - Format of - Central fields and Distribution: - Types
- Screen material no. - Media-specific - Control - Product
sequences - Material types fields parameters procedures
- User settings - Product - Allowed BP - Issue change - Edition content
- Field selection synchronization roles types categories
- Control - Frequencies
parameters - Service types
- System - Delivery add.
messages alternation
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
SAP AG IMD320 4-22

Media Product - Migration
Product master (periodicals)
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 IMD320 4-23

Media Product: Unit Summary

z Explain the product structure in Subscription Sales
and Distribution
z describe the data structure of the media product
master
z Describe the data objects that define a media product
for Subscription Sales and Distribution (for example,
mix offer)
z Create and change media products
z Describe and carry out the system settings for the
media product master
SAP AG 2003
SAP AG IMD320 4-24

Exercises
Unit: Media Product Master

Topic: Media Product Master Data

explain the product structure in Subscription Sales and Distribution
describe the data structure of the media product master
describe the data objects that define a media product for Subscription
Sales and Distribution (for example, mix offer)
create media products in the media product hierarchy (media product
family - media product - media issue)
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-1 Create the daily newspaper JMH*.

1-1-1 JMH* is a media product family that is assigned to the plant New Media
(ME20), sales organization Wireless World News (ME02) and distribution
channel Direct Sales (J6).
The media product family has the short text JMH* and is maintained using the
base unit of measure Copies (COP) in the division Newspapers/Magazines
(J8). JMH* is a US daily paper owned by the publisher and is not taxable (the
tax rate for Germany is half tax).
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.
SAP AG IMD320 4-25

1-2-6 Mix offers for full subscriptions are available in the combination full by home
delivery, without ad pre-prints by domestic mail, and without ad pre-prints
by international mail. Maintain the mix offers.
1-2-7 The product procedure for monitoring is Daily newspaper (01) and CO order
account assignment takes place for each issue during billing transfer.
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-4 Check the general IS-M control parameters in Customizing.

Which areas are affected by these settings?
1.__________________ 2._____________________
3.__________________ 4._____________________
5.__________________ 6._____________________
1-5 Which media types are defined?

1.__________________ 2._____________________
3.__________________ 4._____________________
5.__________________ 6._____________________
7.__________________ 8._____________________
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.____________________________________________________
SAP AG IMD320 4-27

SAP AG IMD320 4-28
Solutions
Unit: Media Product Master

Topic: Media Product Master Data
All the exercises in this unit for maintaining master data begin with the
following menu path:
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-1 Media Product Master Media Product Family Create

1-1-1 Daily newspaper with the distribution channel direct sales (J6)
Create Media Product Family (Initial Screen)
Material JMH*
Industry Sector Media
Material Type Media ProdFamily News/Mag
Group 00: * =A Group 01: * =B Group 02: * =C Group 03: * =D

Group 04: * =E Group 05: * =F Group 06: * =G Group 07: * =H
Group 08: * =I Group 09: * =J Group 10: * =K Group 11: * =L
Group 12: *=M Group 13: * =N Group 14: * =O Group 15: * =P
Group 16: * =Q Group 17: * =R Group 18: * =S Group 99: * =T
Select View(s): Media Product Family

Organizational Levels
Plant ME20
SAP AG IMD320 4-29

Detailed maintenance of media product family
Material Daily Paper JMH*
Short Text JMH*
Title Title of your choice
Base Unit of Measure COP (Copies)
Division J8
Tax Classification (country DE) 2
When you save the media product family, the system displays the following
message:
Material JMH* created
1-2 Media Product Master Media Product Create

1-2-1 Media product JM## with the distribution channel direct sales (J6)
Material JM##
Material Type Media Product News/Mag
Select View(s): Media Product
Sales 1 Media Product
Sales 2 Media Product
Plant ME20
SAP AG IMD320 4-30

1-2-2 Detailed maintenance of media product
Material New Hampton Group ##
Short Text JM##
Title Title of your choice
Media Product Family JMH*
Content Category Local edition
Publication Type Newspaper
Publication Frequency Daily
Audit Report Type 3 (ABC)
1-2-3 Detailed maintenance Sales 1 Media Product

Base Unit of Measure COP
Division J8
1-2-4 Detailed maintenance Sales 2 Media Product

Frequency Daily
Base Year (Year Number) Current year
Factory Calendar Z2
When you save the media product, the system displays the following message:
Material JM## created
1-2-5 Product Master (Periodicals) Product Mix Edit
Publication: JMH* Edition: JM##
Create Mix Type
Mix Type 01
Text Full with ad pre-print
With Ad Pre-Print X

Mix Type 10
Text No ad pre-prints
SAP AG IMD320 4-31

When you save, the system displays the following message:
Data saved
1-2-6 Mix Offer
Serv. Type Mix Type Del. Type MO Subs. Den. Sub.
Weightin Wting
g
Full Full with ad Home delivery 1 1
subscription pre-print
Full No ad pre- Mail - 1 1
subscription prints domestic
Full No ad pre- Mail - 1 1
subscription prints international
Data saved
1-2-7 Publication Settings
Copy Numbers in Order Do Not Display
Monitoring ProdProc. 01 (Daily newspaper)
CO Order Account Assignment X (Issue account assignment)
Data saved
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
Material JM##_TEMP
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
Plant ME20
SAP AG IMD320 4-32

1-3-2 Basic media data 1
Material JM## Template
Media Product JM##
Content Category Local edition
Publication Type Newspaper
Media Type Publication
Publication Date First day of previous year
Issue Number (in Year) 0001
Copy Number 0001 / Number of previous year
Publication Period D / First day of previous year
Year Number 0001
When you switch to the next tab, the system displays the message:
Publication date is in the past (please check your entry)
1-3-3 Physical Characteristics
Standard Format 5.3x33
Extent 20 PP
Thickness 0.635 mm
Weight of Paper 0.046 Oz/Ft
Please make sure you use periods instead of commas as decimal points.
1-3-4 Media Issue Sales and Distrib.
Issue Number (in Year) 1
Year Number 1
Copy Number 0001
Initial Shipping Date First day of previous year
Publication Period D / First day of previous year
Standard Issue Variant Type Current weekday
Issue Variant Type Current weekday
Publication Date First day of previous year
SAP AG IMD320 4-33

1-3-5 Basic Material Data
Material Group 019 Media
Division J8
1-3-6 Media Issue Sales and Distrib. 1

Division J8
Material Group 019
Cash Discount X
Returns Allowed X
Return Period From First day of previous year
Return Period To Unlimited (12/31/9999)
Tax Classification (country DE) 2
1-3-7 Sales: General/Plant Data

Availability Check 01
Transportation Group 0005
Loading Group 0003
Material JM##_TEMP created
1-3-8 Media Product Master Media Issue Issue Sequence Edit
Media Product JM##
From Publication Date First day of current year
To Publication Date Last day of next year
SAP AG IMD320 4-34

1-3-9 Edit Issue Sequence
To maintain the rule, choose the button Assign Defaults.
Weekday Mo, Tu, We, Th, Fr, Sa, Su
Standard Issue Variant Type Mo, Tu, We, Th, Fr, Sa, Su
Public Holiday Publication X
Template Issue JM##_TEMP
Choose the Check Rule button to have the system check the rule and then choose
Assign Default Issue Sequence.
Date First day in current year to last day of
next year
The entries in the issue sequence generated using a rule contain only planned
media issues (red traffic light symbol).
To create master records for the planned entries, choose Select All to mark the
relevant entries and then choose Create Selected Media Issues.
Save the entries with the status flagged (yellow traffic light symbol).
1-3-10 When you save, the system displays the following message:
Max. XXX media issues can be created in dialog => batch job
Create Media Issues in Batch => Schedule Job
Immediate Start X
The system then displays the following message:
Data saved
1-4 General Settings Maintain General IS-M Control Parameters

The general control parameters are grouped as follows:
1. Active Applications
2. General Settings
3. Postal Data
4. Structure Maintenance
5. Business Partner
6. Address Management
7. Central Access
SAP AG IMD320 4-35

1-5 Master Data Product Media Product Master Settings for Media-Specific
Fields Define Media Types
1. Audio CD 2. Audio MC
3. DVD 4. CD ROM
5. Online download 6. Publication
7. Book 8. Copy
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
SAP AG IMD320 4-36

Geographical Structures and Change Management
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 IMD320 5-1

Geographical Structures and Change Management:
Unit Objectives

z Describe the master data used for geographical
structuring of distribution areas
z Describe and use the basic functions for geographical
structuring
z List the functions in Change Management
z Describe how change numbers are used
z Explain the functions in the postal change service
SAP AG 2003
SAP AG IMD320 5-2

Course Overview Diagram
Internet
Organization
Settlement
Conclusion
Center (CIC)
SAP AG 2003
SAP AG IMD320 5-3

Business Scenario
z Wireless World News, New York has to respond

flexibly to the changing geography of its distribution
area and map changes to delivery options.
z The regional edition Daily Paper New Berlin is
published in New Berlin. The city is supplied by means
of home delivery and is mapped by a number of carrier
routes. To enable the carrier routes to be redefined
flexibly if required, they are comprised of geographical
units, which are structured based on street sections,
where possible.
z Changes to geographical and logistics data must be
made in such a way as to ensure that the data in the
system is consistent at all times.
SAP AG 2003
SAP AG IMD320 5-4

Structure of the Distribution Area
Shipping New Berlin North

worldwide by
foreign post
New Berlin New Berlin
West East
Shipping in North
America and
Canada by
domestic post New Berlin South
Shipping in parts Newport

of the State of
Norwood New City
New York by
home delivery
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)
SAP AG IMD320 5-5

Structure of a Carrier Route
Level 0 CRte 04
New Berlin South
Carrier route
New Berlin
Level 1 GU-04 South
New Berlin South
Level 2 GU-04B GU-04A

New Berlin South B New Berlin South A
Street 1 Street 2 Street 3 Street 4 Street 5

Level 3 State Highway 8 Martin Rd
401-499
Martin Rd
301-399
Norton Rd Red Mill Rd
Each assignment has a validity period

SAP AG 2003
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.
SAP AG IMD320 5-6

Weekday-Specific Carrier Routes
Carrier route Carrier route Carrier 2

New Berlin South New Berlin South B
Weekday Weekend
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.
SAP AG IMD320 5-7

Geographical Structuring
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.
SAP AG IMD320 5-8

Geographical Units
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 IMD320 5-9

Structure of a Geographical Unit
Geographical unit GU-04A
Street 2 Street 3 Street 4 Street 5

Martin Rd Martin Rd Norton Rd Red Mill Rd
401-499 301-399
SAP AG 2003
Structure of geographical unit GU-04A (see previous slide) from postal units.
SAP AG IMD320 5-10

Higher Level Geographical Units
Geographical unit Geo 100

(city)
Geo 11 Geo 12 Geo 13

(city district) (city district) (city district)
SAP AG 2003
Geographical units (such as city districts) can also be subordinated to other geographical units (such
as cities).
SAP AG IMD320 5-11

Postal Units
Country z Delivery-related postal code (= 1 city)

z P.O. box postal code (1-n cities)
z Major customer postal code (1-n cities)
Postal code
z Major customer group postal code (1-n
cities)
City
City district z House number range

all
even
odd
Street
z House number interval
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.
SAP AG IMD320 5-12

Postal Unit Hierarchy
City Postal code
PCode PCode PCode City City City
St St St St St St
SAP AG 2003
Relationships between cities and postal codes:

y A city can be assigned several postal codes.
y Several cities can belong to one postal code.
SAP AG IMD320 5-13

Street Sections
New Berlin
Street number 4032663 4032664
100 198 200 298

Martin Rd
101 199 201 299
4032667 4032668
SAP AG 2003
A street can be subdivided into several postal units.

Example
Martin Rd in New Berlin is subdivided into four street sections. Two of these street sections are
assigned the house number range identifier 1 (odd) and the other two are assigned the identifier 2
(even).
SAP AG IMD320 5-14

Maintenance Objects in Change Management
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.
SAP AG IMD320 5-15

Change Number
Modify Change Number
Description Change to Postal Data
Validity Period 11/24/2001 - 12/31/9999

Change Status Checked
Postal Change Service Structures updated
Specific to User
Optimize Del. Viab.
Rel. Scheduled
Limited Order Block
Determine Orders By Addresses affected
- 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.
SAP AG IMD320 5-16

Status of Change Number
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
SAP AG IMD320 5-17

Validity Period According to Change Number
Carrier Carrier
route 1 route 1
Geo 1 Geo 1
Geo 11 Geo 12 Geo 13 Geo 11 Geo 12
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.
SAP AG IMD320 5-18

Effect of Release on Orders on Hand
Order 4711
Orders
Orders on hand
Release
change number
SAP Workflow Log

of orders
affected
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.
SAP AG IMD320 5-19

Postal Change Service - Overview
Modification of postal units All the functions in

for a specific time: Change Management:
- Move date
- Cities - Analyze
- Streets
- Postal codes
30 - Delete
- Check
- Release
Postal
change
service
Status management Multi-client capability
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 IMD320 5-20

Steps in the Postal Change Service
Step in postal change service Old status New status
1. Edit postal units ( ) Postal unit processed (01)
2. Update structures (01) Structures updated (02)
3. Check change number (01) or (02) -No status change-
4. Release change number (02) -No status change-

5. Update addresses (02) Addresses updated (03)
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.
SAP AG IMD320 5-21

Multi-Client Capability
Master client Slave client 1 Slave client n
Postal data processed
Structures updated
Change number
checked and released
Structures updated Structures updated
Change number Change number

checked and released checked and released
Addresses updated Addresses updated Addresses 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 IMD320 5-22

Status Management
Status of Postal Change Service

Role Client ChNo. ChNo. Status Post St Add. Status of Change Serv.
M 000 1130 Released X X X Change service completed

S 771 22 Released X X Changes still to be updated
M 000 1144 Released X X X Change service completed

S 771 34 Checked X X Change number still to be released
M 000 1153 In process X Structures still to be updated

S 771 No activities until master change no. released
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).
SAP AG IMD320 5-23

System Settings for Structures and Change
Management
Implementation
of IS-M Structures
and Change
Management
- Number ranges Postal structures: Geographical units: Carrier route

- Geographical - Assign district - Types structures:
hierarchy municipality keys - Number ranges - Carrier route
categories to regions categories
- Exceptional postal - Number ranges
code lengths
- City number range
SAP AG 2003
SAP AG IMD320 5-24

Unit Summary

z Describe the master data used for geographical
structuring of distribution areas
z Describe and use the basic functions for geographical
structuring
z Explain the role of Change Management in
maintaining geographical structures
SAP AG 2003
SAP AG IMD320 5-25

SAP AG IMD320 5-26
Exercises
Unit: Geographical Structures and Change

Management
Topic: Postal and geographical units, carrier routes and
delivery viability sets
obtain data on postal units
create master data for geographical structuring of distribution areas
(geographical units and carrier routes and their assignments)
describe and use the basic functions for geographical structuring
explain the role of change management in maintenance of
geographical structures
You need postal data when checking or completing business partner

addresses. You are in charge of administration for the new region New
Hampton for Wireless World News New York and are responsible for
creating the geographical units and carrier routes for use in delivery.
1-1 Determine postal units:

1-1-1 Find out the home delivery postal code for New Hampton (New York).
Postal code: ___________
1-1-2 Find out the city number of New Hampton (New York):
____________________
1-1-3 List all the streets in New Hampton (New York).
First street: ______________________________________________
Last street: ______________________________________________
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:___________________
SAP AG IMD320 5-27

1-4 Create a higher level geographical unit.
1-4-1 GUNH-##, name: New Hampton ##, type: City district
1-4-2 Assign geographical units GU1-## to GU3-## to geographical unit GUNH-##.
1-5 Create a carrier route CAR-##.

1-5-1 Create the carrier route CAR-##. Since the carrier has to climb a large number
of steps on this route, this is noted for home delivery settlement in the carrier
route category.
1-5-2 Assign geographical unit GUNH-## to carrier route CAR-##.
1-6 Which types of geographical units exist in the system?

__________________ _____________________ _____________________
__________________ _____________________ _____________________
__________________ _____________________ _____________________
__________________ _____________________ _____________________
__________________
SAP AG IMD320 5-28

Solutions
Unit: Geographical Structures and Change

Management
Topic: Postal and geographical units, carrier routes and
delivery viability sets
All the exercises on postal units begin with the following menu path:
Distribution Master Data Distribution
1-1 Determine postal units:

1-1-1 Geography Postal Unit Postal Codes Display
Country Key US
Position the cursor on the Postal Code field and call the input help. Select the
tab Home Delivery Postal Code.
City New Hampton
Region New York (NY)
Postal code: 10958
1-1-2 Geography Postal Unit Cities Display
Country Key US
Position the cursor on the City Number field and call the input help. Choose the
tab Cities by City Name with Region.
City New Hampton
Region New York (NY)
New Hampton: V14938
SAP AG IMD320 5-29

1-1-3 Geography Postal Unit Streets Display
The procedure is the same as in exercise 1-1-2
Caution: The city district and a number of other search terms are case-sensitive.
Please capitalize initial letters.
First street: Airport Rd Last street: Wildwood Ln
1-2 Geography Geographical Unit Create

1-2-1
Geographical Unit GU1-##
Short Text Milo Rd
Geo. Unit Type Street
When you save the geographical unit, the system displays the following
message:
Geographical unit GU1-## was created
1-2-2
Short Text Bailey Rd
message:
1-2-3
Short Text Lynch Ave
message:
SAP AG IMD320 5-30

1-3 Geography Geographical Unit - Postal Unit Edit
No assignments exist yet for your new geographical units.

Press <Enter> to confirm this message. The system now asks you to enter
the change number. Create a change number for your group.
Description: Change number for group ##
Select the indicators: Specific to User
Optimize Del. Viab.
Limited Order Block
Determine orders by: Delivery viability sets affected
Save and note down your change number.
You can now edit the geographical structures.
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.
Street numbers for Bailey Rd: 3038165 and 3038166

Street numbers for Lynch Ave: 3038227 and 3038228
1-4 Create higher level geographical unit.

1-4-1 Geography Geographical Unit Create
Geographical Unit GUNH-##
Short Text New Hampton ##
Geo. Unit Type City district
message:
Geographical unit GUNH-## was created
SAP AG IMD320 5-31

1-4-2 Geography Geographical Unit-Geographical Unit Edit
Assign geographical units GU1-##, GU2-##, and GU3-## to geographical unit
GUNH-##. Use your change number to do this.
The procedure is the same as in exercise 1-3.
Choose the assignment type
Geo. Hierarchy X (select)
message:
Assignments to object GUNH-## modified
1-5 Create carrier route

1-5-1 Geography Carrier Route Create
Carrier Route CAR-##
Short Text CAR-##
Choose Settlement
Topography Many steps
When you save the unloading point, the system displays the following message:
Carrier route CAR-## created
1-5-2 Geography Carrier Route-Geo. Unit Edit
You can also use your change number here.
Select the higher level object and choose Assign at Lower Level.
Geographical Unit GUNH-##
Assignments to object CAR-## modified
1-6 Which types of geographical units exist in the system?

Country Federal state Administrative district County
City City district Street Street section
Apartment house House number Region Local district
Nielsen district Postal code World Europe
US
SAP AG IMD320 5-32

Distribution
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 IMD320 6-1

Distribution: Unit Objectives

z Create master data on unloading points and truck
routes
z Link truck routes with the relevant editions and
unloading points
z Generate daily routes
z Create delivery viability sets and optimization
rules
z Describe unloading viability sets
z Describe the structure of a shipping schedule for
postal shipping
SAP AG 2003
SAP AG IMD320 6-2

Distribution: Course Overview Diagram
Internet
Organization
Settlement
Conclusion
Center (CIC)
SAP AG 2003
SAP AG IMD320 6-3

Distribution: Business Scenario
z Wireless World News, New York sells its

newspapers and magazines in New York State.
Delivery is performed principally by home delivery
on carrier routes.
z Separate local editions are published for the
individual carrier routes (city districts).
z Truck routes are planned for transportation of the
products to be supplied. A route consists of a
number of unloading points that are served in a
certain sequence. The routes are run on fixed dates
and at fixed times by shipping companies.
z Shipping schedules are designed for postal
dispatch.
SAP AG 2003
SAP AG IMD320 6-4

Unloading Points
General unloading point
Address : 1 Ashley St
13668 Norwood
Location: In front of garage
Loading point - plant
IDES Media Inc. US

Address : 10036 New York
Location: Ramp 1
SAP AG 2006
Unloading points are created for

y Carrier routes (general unloading point)
y Loading points at a plant
General unloading points are created for postal dispatch points.
An unloading point is characterized by its address and a description of the exact location (for
example First door on the left).
The address of a loading point is determined from the address of the corresponding plant.
Customer-related unloading points are not used in IS-M/SD because they cannot be assigned to a
carrier route.
SAP AG IMD320 6-5

Truck Routes
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
Ed.1 Ed.2 Unloading point 2

Newsstand
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.
SAP AG IMD320 6-6

Trunk Routes
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
Unloading point 2 Unloading point 3

Carrier route Newsstand
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.
SAP AG IMD320 6-7

Daily Routes

Daily route generation
Frequency rule
Truck route type
Planned times March
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.
SAP AG IMD320 6-8

Daily Route Data
Split route Vehicle type

Actual and
planned value
Loading weight
Planned times Actual times
Availability time 21:00 Availability time 21:12

Departure time 23:30 Departure time 23:23
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.
SAP AG IMD320 6-9

Generating Daily Routes
March 1 March 7
Gen.
trigger
Generation rule:
all weekdays except Sunday
Truck route
March Generation
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
Automatic generation of daily routes

The following data must be maintained in the truck route master record in order to generate daily
routes automatically:
y Frequency rule and factory calendar in truck route
y Generation rule for truck route
y Generation trigger for truck route
If the data required for automatic generation has been maintained fully, the process can be started in
dialog using a special menu option, or automatically in background processing.
Automatic generation always takes place for the period of the generation trigger.
The system determines the dates in the trigger period on which daily routes are actually run from the
generation rule.
SAP AG IMD320 6-10

Generation Rule for Daily Routes
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
Truck route runs daily Generation

except on public holidays
Daily
01/02 01/03 01/04 01/05 01/07
routes
SAP AG 2006
Generation rule for truck routes run daily.

The generation rule refers to a frequency a week in length with a daily grid structure.
The individual periods 1-7 represent the weekdays Monday through Sunday.
On the slide, there are no truck routes scheduled on Mondays and Saturdays.
If a weekday is a public holiday or is directly before or after a public holiday, you can decide in each
case whether the truck route is to run.
In this example, truck routes never run on a public holiday but can run on the day before (BefPH)
and on the two days after (1AftPH and 2AftPH).
SAP AG IMD320 6-11

Generation Triggers for Truck Routes
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
Truck route Downtown Route

Validity period 01/01-01/07
Status Initial generation
Lock date 12/25
Response to existing daily routes
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 IMD320 6-12

Truck Route Types
Truck Route Schedule 12/24 Truck Route Schedule 12/24
Truck route TRte type Truck route TRte type
TRte-West Public hol. R1 Weekday

TRte-East Public hol. R2 Weekday
TRte-Post Public hol. R3 Weekday
TRte-Newsstand Public hol.
Truck Route Schedule 12/24

Template date : 12/24
Prev. year
Truck route TRte type
Truck route type : Public
holiday
TRte-West Public hol.
Shipping date : 12/24
TRte-East Public hol.
TRte-Post Public hol.
TRte-Newsstand Public hol.
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.
SAP AG IMD320 6-13

Unloading Point Sequence
Unloading point 1
Unloading point 2
Unloading point 3
Level Type Object Valid from Valid to

0 TRt Tr.route - East End
1 UPt Unloading point 1 01/01 12/31
SAP AG 2003
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 IMD320 6-14

Truck Route-Edition Assignment
Ed.1 Ed.2 Ed.2
Ed.1 Ed.1 Ed.2 Ed.2
Publicn Edition Truck route Valid from Valid to

DailyP Ed.1 Tr.route - East End 01/01 12/31
DailyP Ed.2 Tr.route - East End 01/01 12/31
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.
SAP AG IMD320 6-15

Delivery Viability Set
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.
SAP AG IMD320 6-16

Delivery Viability Optimization
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
Orders with optimized

delivery viability parameters
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.
SAP AG IMD320 6-17

Optimization Rules for Delivery Viability Sets
Operation type Order type Publication
Create/change order
Change of address
Change number release
Explicit optimization run Optimization
rule
Determine Apply delivery

del. viability viability
parameters parameters
SAP AG 2003
Optimization rules control delivery viability optimization.

An optimization rule is defined for each operation type, order type, and publication.
y The following operation types are defined in the system:
- Order maintenance (creation, change)
- Change of address (planned)
- Change number release
- Explicit optimization run
SAP AG IMD320 6-18

Optimization Rule for Order Processing
Edit Delivery Viability Optimization
Oper. Type 01 Create/Change Order Item

Order Type ABO Subscription
Publication Daily Paper Daily Paper
Priority Edition Mix Type Del.Type Active
010 * * 01
The system determines
020 * * 02 the delivery viability set
030 * * 03 with the highest priority
parameters of all those
040 * * * found.
...
Status
Priority of parameter record

for delivery viability
determination
SAP AG 2003
The system automatically determines the delivery viability parameters using the optimization rule
during order processing.
SAP AG IMD320 6-19

Change Rule for Change Number Release
Edit Delivery Viability Optimization
Oper. Type 03 Release change number

Order Type ABO Subscription
Options for converting
Publication Daily Paper Daily Paper delivery viability parameters
Priority Edition Mix Type Del.Type Edition Mix Type Del.TypeRecal Outpt Active
.
010 01 01 =
* 10 03
020 * * 03 = = 04
Initial status New status
Priority of entry for * Any value

converting delivery = Value remains unchanged
viability parameters
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.
SAP AG IMD320 6-20

Delivery Viability Optimization in the Order (1)
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
Order Item Optimization Rule Order Item

(initial status) (optimized)
Priority Edit. Mix Type Del.Type
Edition Local Edition Local
010 * * 01 (Home delivery)
Mix Type Mix Type 03
020 * * 02 (Mail - domestic)
Del.Type Mail - Dom. Del. Type 01 Home
030 * * 03 (Direct delivery) delivery
040 * * *
Existing delivery viability sets

Edition Mix Type Delivery Type
Regional 01 01 (Home delivery)

Local 03 01 (Home delivery)
Local 01 02 (Mail - domestic)
SAP AG 2003
Delivery viability optimization determines the best possible delivery viability parameters for the
operation type Create/Change Order.
SAP AG IMD320 6-21

Optimization for Change Number Release
Release change number

Master data on change number
Description District changes
Validity Period 01/03/2001
Optimize Del. Viab.
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.
SAP AG IMD320 6-22

Delivery Round
Delivery rounds
Morning round Evening round
Carrier A Truck route 1 Carrier B Truck route 2

Delivery Delivery
viability set viability set
Home delivery Home delivery
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)
SAP AG IMD320 6-23

Unloading Viability Set
Carrier route 1
Home delivery
Unloading point 1
Ed.1 Ed.2 Ed.2
Ed.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.
SAP AG IMD320 6-24

Unloading Rule for Carrier Routes
Unloading point 2
Ed.1 Ed.2 Ed.2
Ed.1 Ed.1 Ed.2 Ed.2
Carrier route 1
Unloading point 1
Ed.1 Ed.2 Ed.2
Ed.1 Ed.1 Ed.2 Ed.2
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.
SAP AG IMD320 6-25

Unloading Rule for Repeated Direct Delivery
Ed.1 Ed.2 Ed.2
Ed.1 Ed.1 Ed.2 Ed.2
Unloading
point
Newsstand 1
Ed.1 Ed.2 Ed.2
Ed.1 Ed.1 Ed.2 Ed.2
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.
SAP AG IMD320 6-26

Exceptions
Daily
Daily Paper
Paper West
West 30%
30%
Daily
Daily Paper
Paper West
West SA*
SA* 50%
50%
Unloading point 2
Ed.1 Ed.2 Ed.2
Ed.1 Ed.1 Ed.2 Ed.2
Carrier route V1
Unloading point 1
Ed.1 Ed.2 Ed.2
Ed.1 Ed.1 Ed.2 Ed.2
*SA = Actual issue variant type for Daily

Daily Paper
Paper West
West 70%
70%
Saturday edition Daily
Daily Paper
Paper West
West SA*
SA* 50%
50%
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.
SAP AG IMD320 6-27

Home Delivery Round
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.)
SAP AG IMD320 6-28

Shipping Schedule
Unloading point Weekdays Country

Goods arr. time
Airport Mo-We Fr
11:00 pm GB
I
Airport Mo E
1:00 am We P
Fr
Daily Paper Magazine
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 IMD320 6-29

Shipping Schedule II
Unloading point Central Station Description Intercity 23421

Network Rule net
Container type Bag 25kg Latest arrival time 11:00 PM
Postal code area assigned Valid

Weekdays
10000 - 14999 US Mo-We

17000 - 19999 US Sa-Sa
21000 - 21999 US
CA
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.
SAP AG IMD320 6-30

Shipping Schedule Variants
Shipping schedule variant for

public holiday
Shipping schedule
12/01 12/24 12/27 12/31

MoTuWe 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
Shipping schedule variant for daily

newspaper
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.
SAP AG IMD320 6-31

System Settings for Distribution
Implementation
of IS-M
Distribution
Truck route: Delivery: Postal dispatch:

- Truck route types - Delivery types - Country groupings for
- Frequencies - Weekday-specific shipping schedule
- Vehicles carrier routes - Number ranges
- Geographical conditions - Delivery rounds
- Number ranges - Number ranges
SAP AG 2003
SAP AG IMD320 6-32

Distribution: Unit Summary

z Create master data on unloading points and truck
routes
z Link truck routes with the relevant editions and
unloading points
z Generate daily routes
z Create delivery viability sets and optimization rules
z Edit unloading viability sets
z Edit unloading rules
z Edit shipping schedules for postal shipping
SAP AG 2003
SAP AG IMD320 6-33

SAP AG IMD320 6-34
Exercises
Unit: Distribution Master Data

Topic: Unloading points, truck routes, shipping schedules

create master data on unloading points and truck routes
link truck routes with the relevant editions and unloading points
maintain delivery viability sets
1.
You must create a truck route with loading and unloading points for the
carrier route in order to make home delivery possible for the new daily
paper. You must also maintain delivery viability sets to create a
relationship between the delivery type and the geographical structure.
1-1 Create unloading points.

1-1-1 Create an unloading point ULP-## for Mr. Nadler at ## Milo Rd in New
Hampton. Specify that the bundles are to be dropped off in front of the garage.
1-1-2 Create a postal unloading point PST-##. Enter ## Fisher Ln, New Hampton
(New York) as the address.
1-1-3 Create a loading point PUB-## for printing works (plant) ME20.
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-4 Generate the daily routes for truck route TRT-##.

1-4-1 Maintain the generation rules. Daily routes are to be generated for every day
including public holidays.
SAP AG IMD320 6-35

1-4-2 Maintain the generation trigger so that the daily routes are generated for the next
2 months.
1-4-3 Have the system generate daily routes, first as a test run and then as an update
run.
1-5 Create the delivery viability set for publication JMH*.

1-5-1 Home delivery is to be viable for the edition JM## in carrier route CAR-##
from tomorrow (see change number for geographical units).
1-5-2 Make the assignment to the sales organization ME02 with distribution
channel J6 and the plant New Media (ME20). The mix type is full with
inserts (01), delivery type 01 and delivery round MORNING.
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.
1-9 Maintain the shipping schedule.

1-9-1 Create the shipping schedule variant VI## for plant ME20 and your
publication JMH* for international mail shipping. The postal service performs
international delivery with the delivery type PD. Valid from todays date.
1-9-2 Create a shipping schedule with unloading point PST-##, network type 01,
container type 01 and country group WO (World) for your shipping schedule
variant VI##.
SAP AG IMD320 6-36

1-9-3 Create the shipping schedule variant VD## for plant ME20 and your
publication JMH* for domestic postal shipping. The postal service performs
domestic delivery and delivery to Canada with the delivery type PA. Valid from
todays date.
1-9-4 Create a shipping schedule with the countries US and CA, unloading point
PST-##, network type 01, and container type 01 for your shipping schedule
variant VD##.
SAP AG IMD320 6-37

SAP AG IMD320 6-38
Solutions
Unit: Distribution Master Data

Topic: Unloading points, truck routes, shipping schedules
Distribution Master Data Distribution
1-1 Create unloading points

1-1-1 Unloading Point Create
Unloading Point ULP-##
Caution: Do not specify a business partner at this point: if you do, the system
will create it as a business partner unloading point. A main unloading point must
be defined as a general unloading point.

Name1 Nadler
Street Name Milo Rd
House Number ##
City New Hampton
Country US
Region NY
Choose Copy
Location In front of garage
Object ULP-## created
SAP AG IMD320 6-39

Unloading Point PST-##
Name1 Post Group ##
Street Name Fisher Ln
House Number ##
City New Hampton
Country US
Region NY
Choose Copy
Object PST-## created
Caution: Enter the plant now, since otherwise the system will create the
unloading point as a general unloading point.
Unloading Point PUB-##
Plant ME20
Object PUB-## created
1-2 Geography Carrier Route Change

Main Unloading Point ULP-##
Main Publication JMH*
Main Edition JM##
Carrier route CAR-## saved
SAP AG IMD320 6-40

1-3 Truck Route Create
1-3-1 Basic Data
Truck Route TRT-##
Short Text TRT-##
Truck Route Category Basic route
Truck Route Type 7 day route
Loading Point PUB-##
Vehicle Truck 7.5 t
Start Time 00:00 same day
Generation
Factory Calendar Z2
Frequency Rule Daily
Delivery Rounds
Delivery Round MORNING
When you save the truck route, the system displays the following message:
Object TRT-## created
1-3-2 Truck Route Unloading Point Sequence Edit
The unloading points are not yet assigned to truck route TRT-##. You can also
use your change number here.
Select the higher level object and choose Assign at lower level.
Unloading Point ULP-##
Assignments to object TRT-## modified
SAP AG IMD320 6-41

1-3-3 Truck Route Truck Route-Edition Edit
You can also use your change number here.
Publication JMH*
Edition JM##
Truck route-edition assignment was edited
1-4 Generate daily truck routes

1-4-1 Truck Route Daily Truck Route Generation Rule Create
Truck Route TRT-##
Ind.Period GTrRte BefPH OnPH 1AftPH 2AftPH

1 X X
2 X X
3 X X
4 X X
5 X X
6 X X
7 X X
Generation rule TRT-## created
1-4-2 Truck Route Daily Truck Route Generation Trigger Edit
Truck Route TRT-##
Generation Period From Tomorrow's date
Generation Period To Tomorrow's date +2 months
GenStat. 01 (Initial generation)
1-4-3 Truck Route Daily Truck Route Generation Execute Automatically

Truck Route TRT-##
Execute generation as a test run first and then as an update run.
SAP AG IMD320 6-42

1-5 Delivery Delivery Viability Set Edit
1-5-1 Home delivery
Delivery Type 01
Plant ME20
Publication JMH*
Enter your change number and hit <Enter> to confirm.
Press <Enter> to confirm the message 'No delivery viability sets found that
correspond to selection criteria'. Choose Insert Row to continue.
1-5-2
Publication JMH*
Edition JM##
Mix Type 01
When you save the delivery viability set, the system displays the following
message:
Delivery viability changed, 1 unloading viability set(s) edited
1-6 Delivery Delivery Viability Set Edit

1-6-1 North America
Delivery Type 03
Plant ME20
Publication JMH*
Edition JM##
Mix Type 10
Geographical Unit GU-NAM
SAP AG IMD320 6-43

message:
1-6-2 Worldwide
Delivery Type 04
Plant ME20
Publication JMH*
Edition JM##
Mix Type 10
Geographical Unit GU-WORLD
message:
1-7 Release change number

1-7-1 Change Number Analysis Changes on Change Number
1-7-2 Change Number Check
1-7-3 Change Number Release
1-8 Delivery optimization rule

1-8-1 Delivery Delivery Viability Set Optimization Rules
Operation Type 01
Sales Doc. Type ABO (SUBE) announced by
course instructor
Publication JMH*
SAP AG IMD320 6-44

1-8-2 Choose Create.
Priority 8 9 10
Edition * * *
Mix Type 01 10 10
Delivery Type 01 03 04
Active
When you save the optimization rule, the system displays the following
message:
Data saved
1-9 Shipping schedule

1-9-1 Delivery Postal Shipping Shipping Schedule Variant Edit
Enter plant ME20 and choose Create Variant. Enter your shipping schedule
variant VI## in the corresponding field in the Create Variant Number dialog
box and choose Create.
Short Text Mail international ##
Publication JMH*
Edition JM##
Logistical Delivery Type PD
Valid-From Date Current date
Valid-To Date Last day in the year 9999
Shipping schedule variant VI## was modified
1-9-2 Delivery Postal Shipping Shipping Schedule Edit
Choose Insert Shipping Schedule.
Text 1 Mail international ##
Network 01
Container Type 01
Country Grouping WO (World w/o USA)
Valid for Weekdays 1 through 7
Shipping schedule under variant VI## was modified
1-9-3 The procedure is the same as that described in 1-9-1 and 1-9-2.
SAP AG IMD320 6-45

SAP AG IMD320 6-46
Sales Support
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 IMD320 7-1

Sales Support: Unit Objectives

z name the basic terms in sales support (e.g. sales
promotion, advertising material)
z describe the effect of the sales support data on order
acceptance
SAP AG 2003
SAP AG IMD320 7-2

Sales Support: Course Overview Diagram
Organization
Components
Settlement
Unit Summary
Center (CIC)
SAP AG 2003
SAP AG IMD320 7-3

Sales Support: Business Scenario
z Wireless World News, New York is constantly

performing sales promotions to increase sales of
the daily newspaper Daily Paper.
z The sales promotions are planned in such a way
that it is possible to respond to different events,
such as initial introduction, transfer and change of
payment method, with the appropriate gift or
commission.
z Contacts between sales agents and important
customers are recorded in the system so that their
progress can be monitored.
SAP AG 2003
SAP AG IMD320 7-4

Sales Promotion
Order 1
Order 2
Order 3
Sales
promotion
Plan Actual
800 850
900 920
...
SAP AG 2003
Sales promotions support sales.

A sales promotion has the following characteristics:
y Validity period
y Refers to a specific publication
y Optional: Restriction to a geographical area (geographical unit)
The order can be assigned to a sales promotion during order entry.
The success of a sales promotion can be measured by comparing the planned and actual data on
the orders obtained.
SAP AG IMD320 7-5

Campaign Framework
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
SAP AG IMD320 7-6

Promotional Material
Advertising
Gifts media
SAP AG 2003
You use promotional material for the following purposes:

y As gifts in return for obtaining subscriptions
y As advertising material
You can record data such as the following in the master data on the promotional material:
y Delivery Type
y Information on the purchase price of the material
y Unavailable indicator if the promotional material is not available
SAP AG IMD320 7-7

Allowed Gifts
Sales source
Sales promotion Publication
Campaign
framework
Sales area Event Order 1 Order 2 Order 3

Sales Initial introduction
organization Renewal
1 Gift
Change pyt meth.
...
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.
SAP AG IMD320 7-8

Allowed Advertising Media
Sales source
Campaign
framework
Sales area Event Order 1 Order 2 Order 3

Sales Initial Introduction
Organization Renewal
1
1 Gift
Change pyt meth.
...
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.
SAP AG IMD320 7-9

Allowed Commission Recipients
Sales source
Campaign
framework
Sales area Event Order 1 Order 2

Sales Initial Introduction Order 3
Organization Renewal
1 Gift
Change pyt meth.
...
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 IMD320 7-10

Marketing Campaign
SAP Media CRM SAP Media R/3
Campaign Campaign with reference to CRM

Campaign without reference
to CRM
Appl. in R/3 Template offers for campaign

For simplified order entry
CRM IC R/3 CIC
Order entry Order entry
SAP AG 2006
This is a campaign conducted by your company's Marketing department.

If your system is connected to a CRM system, the marketing campaign is planned and created in this
system.
The campaign is exported to the R/3 system for execution, where media-specific attributes (such as
validity, description) can be added.
A template offer is entered for the marketing campaign to simplify order entry.
To evaluate revenues, all orders that result from the campaign must be assigned to it.
A marketing campaign can also be created without reference to CRM.
In this case, the campaign is used to group the template offers that have been assigned.
SAP AG IMD320 7-11

Marketing Campaign II
Business partner-
independent campaigns
Template offers
Application area
Navigation area
SAP AG 2006
Campaigns can be displayed as follows, depending on your Customizing settings:

y Business partner-dependent campaigns
Display all campaigns that exist in SAP CRM for a business partner or all media-specific
campaigns. You define which campaigns are displayed using the Campaign Exists in IS-M
indicator when you set up the data environment.
y Business partner-independent campaigns
Display all media-specific campaigns that can be used independently of a business partner. This
applies to all campaigns for which the BP-Independent indicator is selected in the campaign
master data.
The campaign-supported order entry function allows the call center agent to identify which
campaigns are executed in a company and which are assigned to a customer. The agent can select
the campaign to which the customer is responding. When he enters the order, he can base his entries
on the template offers assigned to the selected campaign. The order data is entered automatically
from the template offers.
If a marketing campaign is created without reference to CRM, it is used to group the assigned
template offers.
SAP AG IMD320 7-12

Sales Support: Unit Summary

z name the basic terms in sales support (e.g. sales
promotion, advertising material)
z describe the effect of the sales support data on
order acceptance
SAP AG 2003
SAP AG IMD320 7-13

SAP AG IMD320 7-14
Exercises
Unit: Sales Support

Topic: Sales Promotion

name the basic terms in sales support
describe the effect of the sales support data on order acceptance
create a sales promotion
create a campaign framework
Before the new daily newspaper is introduced with active advertising,

campaign frameworks and sales promotions must be created in the
system.
1-1 Create a sales promotion SP-##.

1-1-1 The sales promotion contains reader promotion SP-## for the media product
family (publication) JMH* with a validity period of 2 months from the
current date.
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.
SAP AG IMD320 7-15

SAP AG IMD320 7-16
Solutions
Unit: Sales Support

Topic: Sales Promotion

Distribution Sales Support
1-1 Sales Promotion Create

1-1-1 General data
Sales Promotion SP-##
Short Text SP-##
Valid To Current date + 2 months
Campaign Profitability
Planned Sales Activities 10000
Planned Trial Items 100
Number of Free Subscriptions 10
Number of Standard 10
Subscriptions
Publication
Publication JMH*
When you save the sales promotion, the system displays the following message:
Sales promotion SP-## was created
SAP AG IMD320 7-17

1-2 Campaign Framework Create
1-2-1 Sales Support: Create Campaign Framework
Division J8
Sales Source RR
1-2-2 Gifts tab

Service Type FD
Gift Coffee machine Radio
Subscriptions Obtained 2 1
Additional Payment 5
Currency USD
1-2-3 Events tab

Event Initial Introduction
When you save the campaign framework, the system displays the following
message:
Campaign framework created
SAP AG IMD320 7-18

Customer Interaction Center (CIC)
Content:
z Structure of the CIC
z Functions of the CIC
z Integration
SAP AG 2003
SAP AG IMD320 8-1

Customer Interaction Center (CIC): Unit Objectives

z Name the basic terms in the CIC
z Describe the structure of the components
z Search for a business partner and the associated
orders in the CIC
SAP AG 2003
SAP AG IMD320 8-2

Customer Interaction Center (CIC): Course
Overview Diagram
Organization
Components
Settlement

Unit Summary
(CIC)
SAP AG 2003
SAP AG IMD320 8-3

Customer Interaction Center (CIC): Business
Scenario
z Wireless World News, New York uses the Customer

Interaction Center for order acceptance and
processing.
z You are responsible for order processing at the
publisher and receive customer inquiries.
SAP AG 2003
SAP AG IMD320 8-4

CIC: Overview
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
PBX Private Branch Exchange

CTI Computer Telephone Integration (software to control the switch)
y ACD Automatic Call Distribution (forward to agent using specific rules)
y IVR Interactive Voice Response (interaction with caller)
DNIS/ ANI Communication partner's telephone number
SAP AG IMD320 8-5

CIC: System Architecture
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
PBX Private Branch Exchange

CTI Computer Telephone Integration (Software for controlling the switch)
y ACD Automatic Call Distribution (Forward to agent using specific rules)
y IVR Interactive Voice Response (Interaction with caller)
y VRU Voice Response Unit (like IVR, but without interaction)
y Dialer Make mass calls (outgoing)
Telephony Gateway R/3 connection ? Switch or CTI
y SAPphone Server Section of SAPphone that is not found in R/3
y TAPI Telephony API
SAP AG IMD320 8-6

mySAP Media-Specific Functions in CIC
z mySAP Media components

Business partner search
Order overview
Forwarding note
Queue load indicator (if supported by CTI; with integrated
forwarding function)
Extended scripting: dependent on BP and DNIS
z Modified ("short-cut") dialog functions

Business partner (create, change, display, relocation)
Order
(create, change, display, suspension, redirection, termination)
Complaints
Change payment method
SAP AG 2006
SAP AG IMD320 8-7

CIC: Layout
Telephony functions
BP search
Call status
Action Box
Navigation area Application area

SAP AG 2003
The screen for the CIC contains the following areas:

y Business partner search with data on the caller or the current business partner
y Call status indicating the business partner calling and the number dialed
y Action box containing pushbuttons with dropdown menus
y Navigation area containing an overview of the data on the business partner and their orders,
billing documents, complaints etc. as well as the tab page displaying the scripting (reminder
scripting for the agent)
y Application area containing an order overview and the most important functions (such as
suspension, redirection, termination). You can integrate HTML-based applications from the same
R/3 system, from an external R/3 system, and from the Intranet and Internet in this area.
SAP AG IMD320 8-8

CIC: Navigation Area
Business partner environment

Sales area
Bank details
M/SD order
M/SD order items
M/SD limited order items
M/SD complaints
M/SD billing documents
M/AM ...
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 IMD320 8-9

CIC: Application Area
Tab pages containing

M/SD order overview
Customer overview (HTML)
Customer contacts
Contact history for agent
Workflow inbox
SAPGUI for HTML:
Application area IS-M and R/3 transactions
HTML pages of your choice
e.g. Intranet
M/AM contents
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).
SAP AG IMD320 8-10

CIC: Change Functions
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 IMD320 8-11

CIC: Business Server Pages
Campaign: Advertising campaign
Offer: Weekly Paper, weekly,...
Payment method Invoice, automatic debit, ...
Present: Coffee cup
Variable data: Delivery start, delivery quantity

+ Campaigns for BP
+ Summer offer Sales agent, billing and mix
+ Special offer frequencies
+ General campaigns
+ Advertising campaigns
+ TV advertising
+ Image campaigns Save Check Full dialog Reverse
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 IMD320 8-12

Customer Interaction Center (CIC): Unit Summary

z Use basic terms in the CIC
z Describe the structure of the components
z Perform a business partner search in the CIC
SAP AG 2003
SAP AG IMD320 8-13

SAP AG IMD320 8-14
Sales
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 IMD320 9-1

Sales: Unit Objectives

z Describe the special features of the subscription
order types and the necessary system settings
z Create and change subscription orders and
complaints
z Explain and use the function for delivery address
alternation
SAP AG 2003
SAP AG IMD320 9-2

Sales: Course Overview Diagram
Internet
Organization
Settlement
Conclusion
Center (CIC)
SAP AG 2003
SAP AG IMD320 9-3

Sales: Business Scenario
z Wireless World News, New York sells subscriptions

to the daily newspaper Daily Paper, which are
supplied to the distribution area by means of home
delivery. All other areas are supplied by mail.
z Delivery can be changed at the subscriber's
request, for example, a subscription can be
redirected to a temporary address during vacation.
SAP AG 2003
SAP AG IMD320 9-4

Sales Document Types (Excerpt)
Internal
order
Subscription:
Subscription Unlimited subscription
offer Delivery subscription
Renewal subscription
Period renewal subscription
Sales
document
type
Credit memo External

request delivery order
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 IMD320 9-5

Types of Subscription
Unlimited subscription Delivery subscription
No liability account Delivery-related liability account

Valid until terminated Valid until terminated
Periodical advance billing Periodical advance billing
based on order based on last delivery in
(e.g. year's subscription) cycle (e.g. 6 copies)
Liability account amortized
based on each delivery
Renewal subscription Period renewal subscription

Monetary liability account Monetary non-performance-related
Expiration date (purchase period) liability account
according to payment amount Expiration date (purchase period)
Liability account amortized according to billing frequency
based on each delivery No amortization
Monitoring control (renewal offer, Monitoring control (renewal
reminders) offer, reminders)
Tolerance periods Tolerance periods
SAP AG 2003
SAP AG IMD320 9-6

Unlimited Subscription
New
billing period
Time
Customer
account
Year's Year's
subscription subscription
D C
$ 60
Billing Billing Billing

index index
Year's sub.
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.
SAP AG IMD320 9-7

Delivery Subscription
First cycle First delivery

New
billing
in new period
cycle
Time
Time
Customer
account
Year's Year's
6 deliveries 6 deliveries
subscription subscription
Liability acct 001 Liability acct 002 D C
Bill. Amort. Bill. Amort. $ 60

6 del. 6 del. 6 del. 6 del.
Billing Billing Billing
index index
6 del.
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.
SAP AG IMD320 9-8

Renewal Subscription
Order First New

expiration date expiration date
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.
SAP AG IMD320 9-9

Renewal Subscription - Incoming Payment Process
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
An incoming payment is received for an open renewal offer in Financial Accounting.

The assignment number and the payer's business partner number must be printed on the renewal
offer or reminder letter so that these can be identified in the incoming payment.
When an incoming payment is entered in FI with the correct assignment number, the corresponding
process is triggered in IS-M/SD by OPEN FI. This means a transactional RFC (tRFC) is accessed at
an interface specified in the Business Transaction Event.
The tRFC enables the system to process function modules called remotely even if the execution time
for the relevant remote partners is currently not accessible.
Error processing: If the tRFC call is triggered in the partner system but errors occur during
processing in the server system, this is reported to the client system. You can use transaction SM58
to analyze and process the source of the error.
If the payment amount is incorrect or other problems arise in determining and extending the renewal
subscription, the administrator responsible receives a work item in their inbox requesting manual
postediting.
SAP AG IMD320 9-10

Renewal Subscription - Incoming Payment
Administration
Incoming Expiration Incoming New expiration date

payment date payment for incoming payment
Monitoring 1st 2nd 3rd Time

Order period tolerance tolerance tolerance STOP
period period period
Closure
No payment Termination
Unlimited suspension;
stop delivery
Activity Incoming payment received
Before expiration date Renewal at offer price, determine expiration date

Renewal at offer price, determine expiration date, postamortize
In 1st tolerance period issues from 1st tolerance period if applicable
Renewal at current price, determine expiration date,
In 2nd tolerance period
postamortize if necessary, limit suspension
Stop delivery at end of 1st tolerance period,
After 2nd tolerance period delete unlimited suspension
In 3rd tolerance period Restart at current prices, determine expiration date, no

postamortization
Restart of order item no longer possible.
After 3rd tolerance period You must create a new order item.
SAP AG 2006
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.
SAP AG IMD320 9-11

Renewal Subscription - Amortization
Order Liability acct Customer

account
item Amort. Payment
amount amount Debit Credit
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.
SAP AG IMD320 9-12

Liability Account Transfer
Payment Customer
1
D C
120 $ 120 $
Write-off Extraordinary revenue

Liability account
2
D C
4711 / 004
Transfer
Amort. Payt
amount amount Liability acct r
3 4712 / 001 he
Ot der
117 $ 120 $ or
Amort. Payt
amount amount
42 $ 75 $
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.
SAP AG IMD320 9-13

Bulk Recording of Incoming Payments
Check dep. acct
D C
Incoming payments for
renewal subscriptions 300 $ 300 $
Check deposit account 130000 Customer

accounts
Assgmt Amount Payer
Check 4711101 100 $ Tom Lang D C
100 $ 4712105 80 $ Sam Smith
4713103 120 $ Jane Jones 100 $
4711101
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.
SAP AG IMD320 9-14

Period Renewal Subscription
Order First New

expiration date expiration date
Time
Monitoring 3 tolerance Customer

period periods Account
Renewal Suspension
offer Termination
Reminder Restart D C
Monetary liab. acct Monetary liab. acct $ 100 $ 100
non-perf.-related non-perf.-related
Payment for 4 weeks Payment for 4 weeks
Payment
Billing frequency Billing frequency
4 weeks 4 weeks
Billing index Billing index Billing
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.
SAP AG IMD320 9-15

External Delivery Order
External delivery order
Sales Other publisher

organization
1
Subscription
order
Delivery
Other publisher's customers
SAP AG 2003
An external delivery order is a contract between the following parties:

y Publisher (represented by a sales organization)
y Other publisher
The external delivery order contains an agreement that the sales organization is in charge of
logistics, in particular delivery of subscriptions, for the other publisher.
The sales organization invoices the other publisher for the services performed.
SAP AG IMD320 9-16

Internal Orders
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.
SAP AG IMD320 9-17

WBZ Subscriptions (Germany Only)
Sold-to party
Bill-to party Sales customer
Payer and SC
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.
SAP AG IMD320 9-18

Structure of the Subscription Sales Document
Header Sold-to party

Purchase order data
Item 1 Edition
Delivery type
Business partner WE,RE,RG,VM
Promotional data
Validity period
Schedule line 1 Service type

Delivery quantity
Purchase price
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
SAP AG IMD320 9-19

Subscription Order - Business Partner Roles
Order-related roles Business partner roles
Sold-to party
Ship-to party Sales customer
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 IMD320 9-20

Creating Subscription Items
Create standard Standard item

item
Create free item Free item
Create free item

with transformation Free item + Standard item
to chargeable
Create trial item Trial item
Create trial item

with transformation
to chargeable
Trial item + Standard item
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).
SAP AG IMD320 9-21

Order Processing - Item Data
Order 4711 Order Type ABO Matric. Date 12/31/2000

Item Number 10 Item Type ST Date Catg. Copy
Sold-To Party 4712 Jason Delight, Addison 60101, 102 Winthrop Ave 1
Basic Data Billing Doc. Sales Support Shipping Addit. Data Schedule Line Text
Shipping Ship-To Party Tab pages
Date From / To 15/2000 14/2001
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.
SAP AG IMD320 9-22

Default Item Data
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
SAP AG IMD320 9-23

Delivery Viability Determination
Order types
Validity period Order type
Mix offer
Delivery viability set
Delivery address Publication
Order types
Viable
Mix offer
Publication editions Edition
Edition Mix type
Mix type Service type
Delivery type Delivery type
SAP AG 2003
Prerequisites for delivery viability determination:

y There must be a corresponding mix offer in the system
y The Customizing settings for the order should exclude the mix offers that are not allowed for
particular order types
If the above prerequisites apply, you do not need to make the following entries when recording an
order item, since the system enters the appropriate values automatically:
y Key of edition
y Key of mix type
y Key of delivery type
If a number of viable editions exist for one publication, the system lists them so that you can select
one. The main edition in the ship-to party's carrier route is highlighted in color. When you choose
the edition, the system also enters the mix type and delivery type automatically.
SAP AG IMD320 9-24

Delivery Viability Optimization
Optimization rule Operation types

for each operation type (address z Create or change orders
change), order type, and publication z Change address
z Release change number
z Explicit optimization run
Order processing
Determine or apply
Delivery viability optimization delivery viability parameters
according to optimization rule z Edition
z Mix type
z Delivery type
Orders with optimized delivery

viability parameters e.g. home delivery
instead of postal shipping
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 IMD320 9-25

Delivery Viability Optimization in the Order
ple Oper. Type 01 Create/Change

xam Order
E
Order Type ABO Order Type ABO Order Type ABO
Publication Daily Paper Publication Daily Paper Publication Daily Paper
Order Item Optimization Rule Order Item

(initial status) (optimized)
Priority Edit. Mix Type Del.Type
Edition Local Edition Local
010 * * 01 (Home delivery)
Mix Type Mix Type 03
020 * * 02 (Mail - domestic)
Del. Type Mail - Dom. Del. Type 01 Home
030 * * 03 (Direct delivery) delivery
040 * * *
Existing delivery viability sets

Edition Mix Type Delivery Type
Regional 01 01 (Home delivery)

Local 03 01 (Home delivery)
Local 01 02 (Mail - domestic)
SAP AG 2003
Delivery viability optimization determines the best possible delivery viability parameters for the
operation type Create/Change Order.
SAP AG IMD320 9-26

Locking Delivery Viability Optimization
No delivery viability optimization
STOP
Indicator "No delivery Manual entry of
viability optimization" delivery viability parameters
Item Data Item Data
Publication Paper Morning Paper Publication Paper Morning Paper
Edition Local Morning Paper Edition Local Morning Paper
Mix Type 03 No Ad Pre-Prints Mix Type 03 No Ad Pre-Prints
Delivery Type 02 Direct Delivery Delivery Type 02 Direct Delivery
Date From / To 06/30/2002 Date From / To 06/30/2002

DVParInc. NoDViaOpt. DVParInc. NoDViaOpt.
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.
SAP AG IMD320 9-27

Explicit Optimization Run
Transaction types
z Create or change orders
Transaction type z Change address
Explicit optimization run z Release change number
z Explicit optimization run
Maintain worklist for an interval

Order processing or of order or change numbers:
worklist z Display
z Compile (optional: only n
orders not delivered)
z Delete
Delivery viability optimization z Explicit optimization run
according to optimization rule
Caution:
Optimization of a large order
Orders with optimized delivery dataset can have a serious effect
on the shipping processes.
viability parameters
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.
SAP AG IMD320 9-28

Order Deadline
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.
SAP AG IMD320 9-29

Determining Sales Support Data
Sales source
Header
Sales area
Sales Publication
promotion
Campaign
framework
Sales area Event

Sales
organization Initial introduction
1 Renewal
Gift
Change pyt meth.
...
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 IMD320 9-30

Sales Support Data in the Order
Sales Support Overview

001 RR SProm99 12 MON
CD PLAYER
20000111 A. Miller, New Berlin
STICKER
20000112 P. Smith, New Berlin
002 SI SI99
CLUB CARD
20000112 P. Smith, New Berlin
Sales Source RR Min. Subs. 12 MON

Sales Promotion SProm99 Max. Del. Susp. 3 MON
Valid From 01/01/2002 Initial Introd. X
Advertising medium INTERNET BP Sales Act.
Sales Agt MA Gift Ship. Date Add. Pyt SBlock Comm.From

20000111 X CD_PLAYER 07/01/2002 80 USD X 07/01/2002
01.07.1999
20000112 STICKER 07/01/2002
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.
SAP AG IMD320 9-31

Audit Report Category Determination
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.
SAP AG IMD320 9-32

Change Functions in the Subscription Order
Change
Unlimited change publication
Suspension Partial suspension
Redirection Order Gift transfer

item
Additional copy Charitable transfer

redirection
Termination Cancellation
SAP AG 2003
Order items are valid for certain periods.

There are different change functions according to the purpose of the change. All change functions
refer to the validity period, i.e. they generate scheduled change items.
The following types of scheduled changes can be made according to the change function:
a) Limited changes
- Suspension
- Redirection
- Gift transfer
- Charitable transfer
b) Unlimited changes (special case: change of publication)
- Special cases: termination, cancellation
Limited changes must not overlap.
If an unlimited change is made to the standard item during the period of a limited change, the limited
change must be split using the corresponding function.
SAP AG IMD320 9-33

Unlimited Change
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 IMD320 9-34

Limited (Subtractive) Changes
Standard item Limited change
Suspension Gift Charitable

Redirection
transfer transfer
Rule: Limited change items must not overlap
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).
SAP AG IMD320 9-35

Partial Suspension
Standard item, 10 pieces
1st partial suspension, -3 units
2nd partial suspension, -5 units
Delivery
quantity
10 7 2 5 10
Additive change
Suspended partial quantity (negative)
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.
SAP AG IMD320 9-36

Additional Copy Redirection
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.
SAP AG IMD320 9-37

Time Overlaps in Changes (1)
Standard item
Redirection
Suspension
Goal: Create a suspension

Problem: Redirection already exists in suspension period
Solution: Suspension only allowed after end of redirection, or
redirection only allowed until start of 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.
SAP AG IMD320 9-38

Time Overlaps in Changes (2)
Standard item
Unlimited change (new

standard item)
Redirection
Goal: Create a redirection

Problem: An unlimited change begins in the period for the redirection
Solution: Create two redirections (for the standard item and the
unlimited change) or create one redirection after the end of
the unlimited change.
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.
SAP AG IMD320 9-39

Unlimited Change if Limited Change Exists
Standard item
Suspension

standard item)
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.
SAP AG IMD320 9-40

Splitting a Limited Change
Standard item
Limited change
Split

standard item)
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.
SAP AG IMD320 9-41

Change of Publication
Delivery end reason 001

Actual end of delivery 07/24/2002
Commission clawback X
New publication Weekly Mag
Delivery from 08/01/2002
Sales source COMM
Sales promotion
Old
publication
New
publication
Termination
New standard item
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.
SAP AG IMD320 9-42

Donating Refunds
Last Next Subscriber's liability

expiration expiration account
date date
Subscription
t Tip or
donation
$ 10.--
Charge
off
Tip or
donation
Condition record
$ 10.--
Subscription Sales Contract Accts Rec. & Payable
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 IMD320 9-43

Delivery Address Alternation: Unit Objectives
z Support of alternating delivery addresses according to

weekdays
z Shared billing and settlement
z Shared monitoring
z Shared liability account
z Redirections / suspensions for each delivery address
z Unlimited change for each delivery address or for all delivery
addresses
SAP AG 2003
SAP AG IMD320 9-44

Delivery Address Alternation: Item Levels
Original item
- Payer, bill-to party

- Payment method
Main Main item
item (unlim.
change)
Copy
- Payer, bill-to party

- Payment method
- Audit report
Sub-item Sub-item - Circ. planning, audit report cat.

for alternating for alternating - Delivery viability check
address address - Billing, amortization
element element - Ship-to party, delivery address
MO-FR SA-SU
SAP AG 2003
SAP AG IMD320 9-45

Delivery Address Alternation: Billing Level
Main
item
Level of billing relevancy:

Main item or
Subitem
Subitem Subitem
for alternating for alternating
address address
element element
MO-FR SA-SU
SAP AG 2006
Billing relevancy at subitem level is not supported in the USA.
SAP AG IMD320 9-46

Delivery Address Alternation: Suspensions for
Main Items
Main item, full subscription
t
STOP
Sub-item for alternating address element MO-FR
t
STOP
Sub-item for alternating address element SA-SU
t
STOP
SAP AG 2003
SAP AG IMD320 9-47

Delivery Address Alternation: Suspensions for
Sub-Items
t
STOP
SAP AG 2003
SAP AG IMD320 9-48

Delivery Address Alternation: Unlimited Changes
to Main Items
t
Unlimited change because of
new billing frequency
SAP AG 2003
SAP AG IMD320 9-49

Delivery Address Alternation: Unlimited Changes
to Sub-Items
t
Unlimited change because of
new delivery address
SAP AG 2003
SAP AG IMD320 9-50

Delivery Address Alternation: Complaint
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
SAP AG IMD320 9-51

Reversal
Reversal
Standard item
STOP
Actual end of
delivery
z Determine soonest possible end of delivery

z Enter reversal reason
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.
SAP AG IMD320 9-52

Termination
Termination
Standard item
STOP
Actual end of delivery
z Determine soonest possible end of delivery

z Create failure research
z Recalculate billing amount
z Recalculate commission
z Liability account transfer
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 IMD320 9-53

Sales: Unit Summary

z Describe the special features of the subscription
order types and the necessary system settings
z Create and change subscription orders
z Create complaints
z Explain and use the function for delivery address
alternation
SAP AG 2003
SAP AG IMD320 9-54

Exercises
Unit: Sales Unlimited Subscription

Topic: Creating and Editing Subscriptions
After completing these exercises, you will be able to:

use the CIC for order processing
describe the subscription order types
create subscription orders and use their change functions
create additional items for an order
create alternate delivery addresses for an order
You are responsible for subscription administration for the daily

newspaper New Hampton News. You have received the first subscriptions
resulting from a sales promotion and are now responsible for entering
these orders in the system. At the same time, you also manage
subscriptions to the daily newspaper Daily Paper in your system.
Use the Customer Interaction Center to access order creation or
processing.
Sales organization ME20, distribution channel J6, and division J8.
1-1 Create a subscription for your subscriber JSU-##.

1-1-1 Access the business partner in the CIC. The subscriber wants to purchase the
daily newspaper New Hampton News JMH*. Based on the customer delivery
address, the system proposes the delivery type with which the customer can
receive the newspaper. The customer wants 1 copy.
The customer purchase reason is own initiative, they want a full subscription,
and they want to receive an annual invoice for this.
Save the order and note down the order number: ____________________.
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.
SAP AG IMD320 9-55

1-3 The customer JSU-## is going on vacation next week for one month. The customer
wants to suspend the subscription to their place of work for the duration of their
vacation and to redirect the paper that is delivered to their home address.
1-3-1 Create a redirection for the standard item in your order that contains the
customers home address. Select the order and use a vacation address of your
choice.
1-3-2 Create a suspension for the additional item.
1-3-3 Display the current changes in the order overview. To do this, choose Refresh.
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.
1-5 Check the delivery viability optimization settings.

1-5-1 Check the validity of the optimization rule by creating a new subscription
without delivery viability optimization for your sales customer JSU-##. Then
remove the indicator that deactivates delivery viability optimization.
1-6* Optional exercise:

The subscriber JSU-## calls you because they now want the main item of their
subscription delivered to their home only on weekends. From Monday to Friday, it is
to be delivered to their partner's office.
1-6-1 Choose End Contact and simulate a call with telephone number 0718-456##.
To to this, first switch to Inwait mode.
Set the call status to 2 ringing. Enter the required incoming telephone number
in the field ANI. The simulated call is from an external number and the caller
dialed extension 802.
1-6-2 Answer the call and display the orders for the business partner.
1-6-3 Select the main item of the order that was created previously and enter an
alternate delivery address. The company address is: Bright Lights Agency,
Red Mill Rd ##, New Berlin. Branch to the Alternating Delivery Addresses
function and assign the home address to the subitem for delivery on the
weekdays Saturday and Sunday.
1-6-4 Save the order and display the order overview.
SAP AG IMD320 9-56

Solutions
Unit: Sales Unlimited Subscription

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
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
Sold-To Party JSU-##
Order Type ABO
Division J6
SAP AG IMD320 9-57

Choose Create standard item (SI)
Publication JMH*
Sales Source SI
Sales promotion SP-##
Purchase Reason 003
Service Type FD
Quantity 1
When you save the subscription, the system displays the following message:
Subscription xxx has been saved.
Refresh button in navigation area: The new order is now displayed in the order
overview.
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)
Publication JMH*
Sales Source SI
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.
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.
Choose Refresh in the navigation and application areas.
SAP AG IMD320 9-58

1-3 Order change
1-3-1 Redirection
Application area: Select the order item with the home address (item 10). Choose
Redirection to create the redirection.
Period Monday of next week + 1 month
Create a divert address on the selection screen for the delivery address.
1-3-2 Suspension
Application area: Select the order item with the office address (item 20). Choose
Suspension to create the suspension.
Period Monday of next week + 1 month
Susp.Reason 001
1-3-3 Refresh
Choose Refresh to see the changes in the order overview.
1-4 Change of publication

1-4-1 Application toolbar Subscription Orders: Create Order Subscription
Sold-to Party JSU-##
Order Type ABO
Division J6
Publication JMH*
Sales Source SI
Purchase Reason 003
Service Type FD
Quantity 1
SAP AG IMD320 9-59

A dialog box appears listing all the business partners delivery addresses for
selection. Select the main address and choose Copy.
Refresh button in navigation area: The new order is now displayed in the order
overview.
1-4-2 Change of publication
Application area: Select the order and Change Object.
Delivery End Reason 005
Actual End of Delivery Last publication date in
current week
Publication JMDP
Start of Delivery First publication date in the
next week
Purchase Reason 001
Sales Source SI
Choose Continue. Choose a relevant edition and save the order.
1-5 Delivery viability optimization

1-5-1 When you create the subscription, enter your publication JMH* in the Shipping
block and select No del. via. optimization. The system displays a selection of all
the possible delivery types for the customers address. Delete the indicator and
choose <Enter> to confirm. The system displays the optimized delivery viability
set.
1-6* Optional exercise:

Simulate a call.
1-6-1 Initialize the CIC view by means of the button Initialize all fields in the
business partner search.
Choose Inwait in the application toolbar at the top.
New Call X
Call Status Ringing
ANI 0718-456##
Intern./Extern. External
DNIS 802
Choose Continue.
SAP AG IMD320 9-60

1-6-2 Choose Answer.
The call status changes to connected.
Confirm the address data proposed in the business partner search using the
button Manual Identification.
1-6-3 Alternating delivery addresses
Select the relevant order in the order overview and switch to change mode.
Choose Delivery Addresses in the ship-to party area. Choose Create Address
on the screen Choose Delivery Address.
Add. Name Field Bright Lights Agency
Street Name Red Mill Rd
House Number ##
City New Berlin
Region NY
Country US
Press <Enter>. The system now determines the missing data. Choose Copy.
Now choose Delivery Address Alternation and double click on the entry
Weekend to select it in the dialog box that appears. Choose SAT-SUN in the
additional order processing window and choose Delivery Address to assign the
home address. Choose No in the dialog box that appears, so that the system
searches for the corresponding delivery viability set.
1-6-4 Save the order. The system displays the following message:
Application area: Choose Refresh. All the order and change items are now listed
for the business partner.
SAP AG IMD320 9-61

SAP AG IMD320 9-62
Exercises
Unit: Sales Renewal Subscriptions


use the CIC for order processing
describe the subscription order types
create subscription orders and use their change functions
create additional items for an order
create alternating delivery addresses for an order
You are in charge of subscription administration for the daily newspaper

New Hampton News. You have received the first subscriptions resulting
from a sales promotion and are now responsible for entering these orders
in the system. Furthermore, you also manage subscriptions to the daily
newspaper Daily Paper in your system.
Please use the Customer Interaction Center to access order creation or
processing.
Sales organization ME02, distribution channel J6 and division J8.
2-1 Create a subscription for your subscriber JSU-##.

2-1-1 The subscriber wants to purchase the daily newspaper New Hampton News
JMH* with the sales document type SUBE. Have the system propose the
delivery type with which the newspaper is available, based on their delivery
address. The customer wants 1 copy and wants to pay by credit card. Use the
Diners credit card number 4444 5555 6666 77## with the expiration date
08/31/2006.
2-1-2 The purchase reason is self initiative and the customer wants a full subscription
for 52 weeks.
2-1-3 Save the order and note down the order number: ________.
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.
SAP AG IMD320 9-63

2-3 Customer JSU-## is leaving on vacation next week for one month. He wants to suspend
the subscription to his place of work for the duration of his vacation and have the paper
that is delivered to his home address redirected.
2-3-1 Create a redirection for the standard item in your order. Select the order and use
a vacation address of your choice.
2-3-2 Create a suspension for the additional item.
2-3-3 Have the system display the current changes in the order overview. Use the
Refresh button to do this.
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?
SAP AG IMD320 9-64

Solutions
Unit: Sales Renewal Subscriptions

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
BP JSU-##
Choose Manual Identification (system searches for business partner data
and order data)
Application area Subscription Orders: Button: Create Order Subscription
Sold-To Party JSU-##
Order Type SUBE
Division J8
Publication JMH*
Sales Source SI
Sales promotion SP-##
Purchase Reason 003
Service Type FD
SAP AG IMD320 9-65

Choose Refresh. The new order is now displayed in the order overview.
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.
2-3-2 Suspension
Choose Suspension to create the suspension. Enter Vacation as the suspension
reason.
2-3-3 Refresh
Choose Refresh to see the changes in the order overview.
2-4 Check the delivery viability optimization settings.

2-4-1 Check the validity of the optimization rule by creating a new subscription
without delivery viability optimization for your sales customer JSU-##. Then
remove the indicator to deactivate delivery viability optimization.
SAP AG IMD320 9-66

2-5 Optional exercise:
Simulate a call.
2-5-1 Initialize the CIC view by means of the button Initialize all fields in the
business partner search.
Choose Inwait in the top row of buttons.
New Call X
Call Status Ringing
ANI 0718-456##
Intern./Extern. External
DNIS 802
Choose Continue.
2-5-2 Choose Answer.
The call status changes to connected.
Confirm the address data proposed in the business partner search using the
button Manual Identification.
2-5-3 Alternating delivery addresses
Select the relevant order in the order overview and choose Delivery Address in
the Sold-to Party area to change the delivery address. Choose Create Address
on the screen Choose Delivery Address.
Supp. Name Bright Lights Agency
Street Name Red Mill Rd
House number ##
City New Berlin
Now choose Delivery Address Alternation and double click on the entry
Weekend to select it in the dialog box that appears. Choose the entry SAT-SUN
in the additional window for order processing. Change the delivery address to
the customers home address for this item.
Answer No when the system queries whether or not delivery address
alternation is to be cancelled.
2-5-4 Save the order. The system displays the following message:
Application area: Choose Refresh. All the order and change items are now listed
for the business partner.
SAP AG IMD320 9-67

SAP AG IMD320 9-68
Internet Application Components
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 IMD320 10-1

Internet Application Components: Unit Objectives

z Describe the functionality of IACs and Business
Server Pages
z Create and change subscriptions
z Check logs
SAP AG 2003
SAP AG IMD320 10-2

Internet Application Components: Course
Overview Diagram
Organization
Components
Settlement
Conclusion
Center (CIC)
SAP AG 2003
SAP AG IMD320 10-3

Internet Application Components: Business
Scenario
z Wireless World News, New York also sells its

products in the Internet.
z As an employee, you are responsible for checking
the incoming orders and changes from the Internet.
z To do this, you have to check the temporary tables
of orders for postediting at regular intervals, and
process any required activities.
SAP AG 2003
SAP AG IMD320 10-4

Browser-Based Order Processing
Customer
Order mySAP Media

entry Internet
Application
Components
Employee Business
Server Pages
Order entry
SAP AG 2003
Browser-based order processing is possible in the following two ways:

y Internet Application Components (IACs) allow customers to edit their subscriptions in the
Internet. They can be integrated flexibly in the publisher's homepage.
y Business Server Pages (BSPs) can be run in the browser or in an HTML Control. The BSP
application for creating an order with reference to an offer is primarily designed for use with the
Customer Interaction Center (CIC) in CRM or R/3. This means it is possible to enter subscription
orders in the CIC without having to switch to a full dialog in R/3.
SAP AG IMD320 10-5

IAC Subscription Services in the Internet
Customer Publisher's Website

Customer mySAP Media
WWW
z IAC Subscription Sales z IAC Address Change

z IAC Vacation Service z IAC Change Payment Data
Redirection z IAC Complaint
Delivery suspension z IAC Internet User
Charitable transfer Create Internet user
Gift transfer Change data for Internet user
SAP AG 2006
IAC Internet Application Components

IAC Subscription Sales
y Maps subscription sales in the Internet in several different variants
y Orders and business partners can either be created directly in the system or stored in a temporary
table
IAC Vacation Service
y The customer can suspend one or more of his subscriptions for a certain period or create a
redirection
IAC Address Change
y Change a sold-to party's address in the Internet
IAC Change Payment Data
y Change payment data for one or more of a sold-to party's orders
IAC Complaint
y Create complaints
IAC Internet User
y Create an Internet user so that the customer can log on to the Internet Application Components
y Change access data for Internet user (password)
SAP AG IMD320 10-6

IACs - Process Flow Schema
Website
Log Enriching and checking
Customizing
Store
Postediting
Temporary table Operative system

SAP AG 2003
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
SAP AG IMD320 10-7

IACs - Postedit Order Data
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.
SAP AG IMD320 10-8

Technical Components
z Internet Application Components (IACs)

Platform: Internet Transaction Server (ITS)
z Business Server Pages (BSPs)
Platform: Web Application Server integrated with SAP R/3
Enterprise
SAP GUI R/3 Application R/3

Server Database
Server
GUI
Business
Web Browser Web Server ITS Applications
IAC
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.
SAP AG IMD320 10-9

System Settings
Implementation
of IS-M
IACs and BSPs
Business partner: Order: Internet Transaction Order maintenance

- Identify and check - IAC Subscription Server: using BSPs:
business partners Sales (fixed and - Publish and edit - Assign payment
- IAC Change variable order standard templates method type
Address values) - Control settings for
- Settings for Internet - IAC Change application
user Payment Data
- IAC Vacation
Service
- IAC Create
Complaint
SAP AG 2003
SAP AG IMD320 10-10

Internet Application Components: Unit Summary

z Describe the functionality of IACs and Business
Server Pages
z Create and change subscriptions
z Check logs
SAP AG 2003
SAP AG IMD320 10-11

SAP AG IMD320 10-12
Exercises
Unit: Internet Application Components

Topic: IAC

manage and postedit orders created in the Internet
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-1 Create a trial subscription in the Internet.

1-1-1 Choose the entry Publishers Homepage in your favorites.
1-1-2 Under SUBSCRIBE, choose the product DAILY PAPER. If you worked with
the order type SUBE up to now, choose the option Renewal Subscription. If
you worked with the order type ABO up to now, choose the option Periodical
Subscription.
1-1-3 Now choose 20 Days Trial and create an order for the customer George
Bornham, 1## Bell Rd, New Berlin in New York State.
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.
SAP AG IMD320 10-13

SAP AG IMD320 10-14
Solutions
Unit: Internet Application Components

Topic: IAC
1-1 Create a trial subscription in the Internet.

1-1-1 Favorites Publisher's Homepage
1-1-2 Daily Paper Renewal Subscription 20 Days Trial or
Daily Paper Periodical Subscription 20 Days Trial
1-1-3
Form of Address Mr.
First Name George
Name Bornham
House Number/Street 1## Bell Rd
City / Postal Code New Berlin
Federal State New York
Choose Order Now to save the order.
1-2 Display the order in the Customer Interaction Center.

1-2-2 Logistics Media Sales and Distribution Periodical Sales and Distribution
Sales Order Customer Interaction Center Front Office Front
Office
Business partner search area
Name Bornham, George
House Number/Street 1## Bell Rd
City / Postal Code New Berlin
Country US
SAP AG IMD320 10-15

You will not be able to find the business partner because the system
settings specify that all trial orders are saved to a temporary table for
postediting.
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.
SAP AG IMD320 10-16

Shipping
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 IMD320 11-1

Shipping: Unit Objectives
z Describe the shipping process in detail

z Understand the general sequence of functions
performed preparatory to shipping and on a
particular shipping date
z Describe the role of the shipping order in
subscription shipping
SAP AG 2003
SAP AG IMD320 11-2

Shipping: Course Overview Diagram
Internet
Organization
Settlement
Conclusion
Center (CIC)
SAP AG 2003
SAP AG IMD320 11-3

Shipping: Business Scenario
z Wireless World News, New York ships its daily

newspaper Daily Paper on a daily basis according
to the existing subscriptions.
z Circulation planning for the deliveries takes place
two weeks before the shipping date and is
continually updated until shipping takes place.
This means packing is always performed based on
the current orders on hand. The shipping
documents required are created after packing.
z The shipping functions prepare the products for
transportation to the unloading points.
SAP AG 2003
SAP AG IMD320 11-4

Shipping Procedure - Overview
1 Generate basic set of deliveries (regenerative planning)
2 Update deliveries continuously

Execute Execute Execute ...
netchange netchange netchange
Generate issue Adjust issue mixes in
...
mixes deliveries
3 Execute shipping function for shipping date
Set order deadline
Execute netchange explicitly
Adjust issue mixes in deliveries
Execute bundling and container packing
Create and print shipping documents
SAP AG 2003
A basic set of deliveries is usually generated in shipping (regenerative planning).

The deliveries are updated continuously based on the orders on hand up to the actual shipping date.
The shipping process for a particular shipping date does not begin until the order deadline is set.
SAP AG IMD320 11-5

Shipping Functions
Planning
Orders Circulation trigger
planning
Order
Deliveries
Order
Order
Packaging Truck route

rules Bundling data
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.
SAP AG IMD320 11-6

Sources for Circulation Planning
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
Publication Planning trigger

calendar
Circulation planning
Deliveries
SAP AG 2003
The following data is processed in circulation planning and shipping preparation:

y Planning trigger: controls when planning is performed for which period
y Delivery viability set: determines which edition can be purchased with which delivery type and
from which printing works.
y Subscription or retail orders with all changes
y Publication calendar for editions
y Product structures (substitution hierarchy, combination, mix type definition)
Planning results are recorded in the planning database for each individual shipping date. Planning
results in deliveries. These contain the delivery quantities for a carrier route (or a geographical unit).
Deliveries are classified according to further criteria: customer group, combination type, order type
group.
SAP AG IMD320 11-7

Planning Procedure
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 IMD320 11-8

Planning Trigger
March 03/01 03/07

MoTuWeTh Fr Sa Su
1 2 3 4
5 6 7 8 9 10 11
t
12 13 14 16 17 18 19
20 21 22 23 24 25 26
27 28 29 29 30 31
Edition: Daily Paper

Delivery type: Home delivery
Validity period: 03/01 - 03/07
Status: Initial planning
Lock date: 02/24
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.
SAP AG IMD320 11-9

Regenerative Planning - Generating Deliveries
Generation 03/01 03/07

trigger
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.
SAP AG IMD320 11-10

Scheduling Netchange
ORDER CHANGES
10:00 15:00
t
Netchange Netchange
Deliveries
SAP AG 2003
You can start the netchange procedure at any time.

Netchange is normally executed at regular intervals in SAP background processing. It is advisable to
execute the netchange procedure several times a day.
The netchange procedure can run in parallel with order processing.
SAP AG IMD320 11-11

Logistical Delivery Type
Order delivery type: Logistical delivery type:

Postal shipping Postal distrib. item
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.
SAP AG IMD320 11-12

Order Deadline
Issue:
Technical Friday
order deadline
limit
Check Order acceptance

to Thursday,
5:00 PM 11 12 1
Set order deadline 10 2
9 3
for shipping day 8 4
7 6 5
Friday
Execute function
on Thursday, 5:00 PM
From Thursday, 5:00 PM
Create shipping documents for
shipping day, Friday
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.
SAP AG IMD320 11-13

Bundling and Container Packing
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.
SAP AG IMD320 11-14

Container Packing
Daily Paper TV Magazine
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 IMD320 11-15

Postal Packing Rules ZEBU (Germany Only)
PCode PL1 PL2 PL3 PL4 PL5
73726 73728 73700 73000

73728 73728 73728 73700 73000
73732 73732 73728 73700 73000
73733 73733 73728 73700 73000
73734 73734 73728 73700 73000
73744 73760 73700 73700 73000
Log
73745 73760 73700 73700 73000
Data transfer ZEBU

DATABASE
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.
SAP AG IMD320 11-16

Phases in Shipping Document Creation
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
Ramp 1 Packaging Shipping

line X channel Y
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.
SAP AG IMD320 11-17

Shipping Document Types
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.
SAP AG IMD320 11-18

Usage
.............................. 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.
SAP AG IMD320 11-19

Destination Determination
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 IMD320 11-20

Shipping Document Creation
Shipping doc. creation

TRte list Route 1
Carrier documents
Truck route freight list
Shipping
doc. creation
TRte list Route 2

Carrier documents
Truck route freight list
15:00 16:00 18:00 22:00
Add. labels Ed. 1

Postal pack label Ed. 1
Shipping doc. creation
SAP AG 2003
Shipping documents are generated by a creation program.

Shipping documents are stored in the SAP spool file. They can be printed from there at various
times and using various programs:
y Immediately upon transfer to the spool file
y Immediately after transfer and deletion of the corresponding spool file
y Print individual shipping documents or an entire spool file. The user can make this choice in
dialog processing.
You can access the shipping document creation program in dialog processing or using the SAP batch
system. The SAP batch system allows you to start the creation program at a certain time and to set it
up in such a way that shipping document creation is executed daily at a certain time with fixed start
values.
You can also create different shipping documents at the same time. This means you can create all
the shipping documents for one shipping date or simply for selected shipping document types or
type groups.
SAP AG IMD320 11-21

Shipping Document Printing
SAP spool
Postal pack add. label

Spool file 1 Container add. label
Goods arrival list
Spool file 2
...
Spool file n
SAP AG 2003
Shipping documents are placed in individual spool files.

A spool file is created for each logical output device (printer, fax).
Depending on the configuration settings for shipping document creation, a spool file can contain
several shipping document types.
SAP AG IMD320 11-22

Production-Related Shipping Documents
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.
SAP AG IMD320 11-23

Configuring Shipping Document Types
....................
....................
.................... 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.
SAP AG IMD320 11-24

Sorting Control for Shipping Documents
Truck Carrier Carrier Truck Carrier

route list notif. notif. route list notif.
Truck Unloading Unloading Truck Unloading
route 1 point1 point2 route 2 point3
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.
SAP AG IMD320 11-25

Shipping Problem Message
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.
SAP AG IMD320 11-26

Shipping Order
Sold-to party Partner publisher

Media Product
Sales &
Distribution
SD orders
One-time Shipping Simplified

service interface external
delivery order
Shipping order
Addresses Addresses
Postal shipping Direct delivery Home delivery

SAP AG 2003
The shipping order contains the following functions:

Service: Shipping of publications to addresses
The actual order management functions are performed in the sold-to party's system. The sold-to
party simply passes on the required data to Shipping. The data is loaded into the system using the
import assistant, and by processing the import jobs in parallel if necessary.
The following two forms of shipping order are possible, depending on the type of service:
y One-time shipping for a sold-to party
- One shipping date
- Large address dataset: full import of address data
- Postal shipping
y Repeated shipping for a partner publisher (simplified third-party delivery order)
- Full and delta imports
- Home delivery or postal delivery
- Change notifications
- Home delivery settlement
You can also create complaints for shipping orders and forward them to the sold-to party by means
of an interface.
Shipping of orders from Media Product Sales and Distribution (SD orders) transferred to
shipping orders via the shipping interface. This means you can used the detailed logistics functions
in subscription shipping for SD orders.
SAP AG IMD320 11-27
Shipping Order - Planning
Shipping Order 123 Add.-based ship. Comp. Z

Sold-To Party Publisher Z
Publication/Edition Paper National
Date From / To 03/01/2004 03/30/2004
Delivery Type 01 Planning To

No Del. Via. Optimization Planning Horizon Create
Order Type ABO
Reference Edition
Items Import
Deliveries are created independently of regenerative planning and

netchange
No planning triggers; instead, planning horizon in shipping order header
Periodical execution of planning
Changes relevant to planning are taken into account immediately
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.
SAP AG IMD320 11-28

Shipping Order - Structure
Item in shipping order:

Shipping Order 123 Add.-based ship. Comp. Z = line in address list
Sold-To Party Publisher Z (Periodical Sales & Distribution)
Publication/Edition Paper National = item in SD order
Date From / To 03/01/2004 03/30/2004 (Media Product Sales &
Distribution)
Delivery Type 01 Planning To
No Del. Via. Optimization Plan Horizon Create
Order Type ABO
Reference Edition
Items Import
Item Valid From Valid To Delivery Qty Address Doc.No. ItNo.

1 03/01/2000 03/30/2000 1 A. Miller, 2 Red Mill Rd, 13411 New Ber 1325 10
2 03/01/2000 03/30/2000 1 B. Miller, 6 Red Mill Rd, 13411 New Ber 1325 20
Address encryption
3 03/01/2000 03/30/2000 1 C. Miller, 7 Red Mill Rd, 13411 New Ber 1325 30 Change Management
4 03/01/2000 03/30/2000 1 D. Miller, 1 Red Mill Rd, 13411 New Ber 1325 40 Postal change service
5 03/01/2000 03/30/2000 1 E. Miller, 9 Red Mill Rd, 13411 New Ber 1325 50 Delivery viability
6 03/01/2000 03/30/2000 1 F. Miller, 6 Red Mill Rd, 13411 New Ber 1325 60 determination or
7 03/01/2000 03/30/2000 1 G. Miller, 4 Red Mill Rd, 13411 New Ber 1325 70 optimization
Order deadline
SAP AG 2006
Shipping order header

The sold-to party, publication/edition, validity period and delivery type are specified here. You can
also use the delivery viability optimization function to determine the delivery type.
Prerequisites: The publication and edition and distribution master data (for example, delivery
viability sets) must be maintained.
Import of address lists
Once you have created the shipping order header, you can import address lists
y Full import for initial or one-time data transfer
y Delta import for continuous update with new subscriptions and terminations
Items in the shipping order
y Each line in the address list corresponds to an item in the shipping order for a sold-to party.
y The shipping order item contains the quantity, the validity period and the address data.
y The order deadline is taken into account.
y Items cannot be changed. If a change has to be made, the item is closed and created again with
the changed data.
y Address encryption and delivery viability determination take place when items are created and
changed.
y Change Management and the postal change service are available for shipping orders.
y Shipping is only possible if a delivery viability set exists.
y Delivery viability optimization is possible.
y Order deadline in shipping orders
y As of SAP ECC Industry Extension Media 6.0, a new Order Deadline per Item/Delivery
indicator has been added to the Customizing settings for the shipping order. If this indicator is
selected, the order deadline for each individual shipping order item is taken into account during
delivery viability determination and circulation planning.
SAP AG IMD320 11-29

Shipping Order - Shipping
Subscription AI orders Shipping orders

orders
Reg. planning Creation of
Create
Netchange AI deliveries
Deliveries
Home del. Shipping

settlement
documents, e.g.
truck route lists,
address labels,
carrier change
notifications
SAP AG 2003
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.
SAP AG IMD320 11-30

Market Coverage - Households
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.
SAP AG IMD320 11-31

Market Coverage - Process
1 Delivery viability set

Carrier route
All households that can be
from delivery supplied with a market
X viability set coverage product
X
X X 2 Mkt cov. combination
Daily Paper
X X Minus subs with mkt
coverage combination
X
Demograph. filter
X 3 (BAdI implementation)
X Minus hhds excluded
acc. to demographic criteria
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.
SAP AG IMD320 11-32

The following functions are available for executing market coverage:
Order creation:
y Shipping documents are generated for the households to be supplied. Since the number of
potential recipients of the market coverage product is recorded for each household, the following
options are possible:
y In the case of market saturation, the system generates the appropriate number of shipping order
items for the household.
y If you are performing total market coverage, the system checks the ship-to parties in the
household to determine whether or not they receive the carrying product. If they do, the system
reduces the number of recipients in the household accordingly. The shipping orders are generated
by program RJVTMCP.
Circulation auditing for market coverage products:
y Shipping orders for market coverage are connected to the circulation auditing functions. You can
set up audit report category determination for each household. The audit report is updated to the
circulation book.
Circulation planning and shipping documents:
y Circulation planning for shipping orders is performed using program RJVTMCP_PLANNING.
The shipping documents for market coverage are the standard shipping documents for the
shipping order.
SAP AG IMD320 11-33

Integration of Shipping for SD Orders with Home
Delivery
+ 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
Shipping of orders from Sales and Distribution (SD)

y If delivery is to take place in a carrier route that is already supplied with an edition and for which
carrier settlement takes place, all SD materials can be delivered and settled in Media Sales and
Distribution (M/SD).
y Home delivery settlement takes place in a separate step for the home delivery data:
- Update external interface for home delivery settlement for SD orders based on home delivery
data
- Home delivery settlement for employee or service company
SAP AG IMD320 11-34

System Settings
Implementation
of IS-M
Shipping
Master data: Planning/postal Shipping documents: Problem messages:

- Deactivate order shipping: - Spool control - Number ranges
deadline - Number ranges - Shipping document - Problem message
- Define delivery - Function modules types types
types for bundling - Sorting control - Problem message
- Bundling types - Minimum number - Forms reasons
- Postal package for postal packing - Function modules - Problem message
types/variants and container for forms origins
- Postal networks packing
- Container types
- Number ranges
SAP AG 2003
SAP AG IMD320 11-35

Shipping: Unit Summary

z Describe the shipping process in detail
z Describe the shipping functions in detail and use
them
z Describe the role of the shipping order in
subscription shipping
SAP AG 2003
SAP AG IMD320 11-36

Exercises
Unit: Shipping
Topic: Shipping

assign shipping document types
create bundling rules
schedule shipping and execute it online
check changes and execute netchange
Wireless World News New York supplies the publications for its existing
subscriptions on a daily basis.
Circulation planning for the deliveries takes place two weeks before the
shipping date and is continually updated until shipping takes place. This
means bundling and container packing is always performed based on the
current orders on hand. The necessary shipping documents are created
afterwards.
You are responsible for shipping of the products for delivery.
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.
1-5 Execute shipping online for your publication JMH*.

Please restrict processing to your publication only.
1-5-1 Set order deadline (report: RJVANSET)
1-5-2 Execute netchange for each order (report: RJVNCNOT)
1-5-3 Check shipping date (report: RJVPRUF1)
1-5-4 Execute bundling (report: RJDPAKET)
1-5-5 Create shipping documents (report: RJVSP001)
1-5-6 Display the shipping documents.
1-5-7 Obtain an overview of the possible shipping checks.
SAP AG IMD320 11-38

Solutions
Unit: Shipping
Topic: Shipping
The exercises in this unit all begin with the following menu path:
Distribution Master Data Shipping
1-1 Control Order Deadline Limit Edit

Plant ME20
Publication JMH*
Choose New Entries.
Publn Publicn Log. Valid Valid M T W T Fri Sat Sun
Type delTy From To o u e h day urd day
n e d u ay
d s n rs
a d es d
y a d a
y a y
y
ME20 1 JMH* 01 Current Last 1 1 1 1 1 1 1
date day in
the
year
9999
ME20 1 JMH* PA Current Last 2 2 2 2 2 2 2
date day in
the
year
9999
ME20 1 JMH* PD Current Last 2 2 2 2 2 2 2
date day in
the
year
9999
SAP AG IMD320 11-39

1-2 Packaging Bundles Bundling Rule Edit
1-2-1 Enter plant ME20 and your publication JMH* and choose Enter to confirm.
Choose Add.
Valid From Date Current date + 1
Valid To Date Last day in the year 9999
Bundle Divider 20
Min. in Odd Bundle 6
Choose Copy, then save.
1-3 Shipping Documents Shipping Document Type Usage General Documents

Edit
Choose New Entries. You can now maintain the shipping document type usages.
SDocTy. Plant Log Network Publicn Valid From Valid To Dest. Prt.
1000 ME20 PA 01 JMH* Current End of A000 1
date 9999
1000 ME20 PD 01 JMH* Current End of A000 1
date 9999
date 9999
3003 ME20 01 JMH* Current End of A000 1
date 9999
date 9999
date 9999
date 9999
date 9999
date 9999
date 9999
date 9999
date 9999
When you save, the system displays the following message: Data saved
SAP AG IMD320 11-40

1-4 Quantity planning
1-4-1 Shipping Deliveries Planning Trigger Edit
Plant ME20
Publication JMH*
Choose New Entries.
Plant Publicn Edition Delivery Planning Planning Block dt. PlStatus
Type From To
ME20 JMH* JM## 01, 03, Tomorrow's Tomorrows Yesterdays 01
04 date date + 2 date
months
Changes to planning trigger were saved
1-4-2 Shipping Deliveries Circulation Planning Execute Regenerative
Planning
Execute regenerative planning for your publication JMH*, first as a test run and
then as an update run.
1-5 Shipping online

1-5-1 Logistics Media Sales and Distribution Periodical Sales and
Distribution Shipping Shipping Creation Order Deadline Set
(Report: RJVANSET)
Plant ME20
Shipping date Tomorrows date
Publication JMH*
Distribution Shipping Deliveries Circulation Planning Execute
Netchange Netchange per Order
(Report: RJVNCNOT) first as a test run and then as an update run.
Printer A000
SAP AG IMD320 11-41

Distribution Shipping Environment Shipping Checks Check
Shipping Date
Plant ME20
Publication JMH*
Shipping (<> Post) x
Shipping (Post) x
Planning Trigger Status x
Bundling Rule x
Sev. Truck Routes per Unl. x
Point
Postal Packing x
Distribution Shipping Shipping Creation Bundling Execute
(Report: RJDPAKET)
Plant ME20
Publication JMH*
Start as Test Run X
Execute bundling as a test run first and then as an update run.
Check bundling.
Distribution Shipping Shipping Creation Bundling Check Result
1-5-5 Shipping Shipping Creation Shipping Documents Create Shipping
Document
(Report: RJVSP001)
Execute shipping document creation separately for the different shipping
documents (truck route-related, edition-related, and general shipping documents
can be created and printed separately).
SAP AG IMD320 11-42

Delivering plant ME20
Shipping document type 1000, 1006, 3003, 3005, 3006
Print truck route-related SDoc. X
... for truck route TRT-##
Print edition-related SDoc. X
... for publication JMH*
Print general shipping doc. X
1-5-6 Shipping documents
Choose System Own Spool Requests to open a new session displaying your
spool requests. Click on the icon for the text Shipping Documents: to
choose your shipping documents.
1-5-7 Evaluations
Shipping Environment Shipping Checks Check Shipping Date
Shipping Environment Evaluate Deliveries ...
Shipping Environment Evaluate Drop-Offs ...
SAP AG IMD320 11-43

SAP AG IMD320 11-44
Billing
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 IMD320 12-1

Billing: Unit Objectives

z Describe the billing functions and control options in
detail
z Describe and use the options for creating billing
documents
z Transfer billing documents to Financial Accounting
z Describe the integration of IS-M/SD with Contract
Accounts Receivable And Payable, IS-M/CA
z Explain the options for revenue accrual
SAP AG 2003
SAP AG IMD320 12-2

Billing: Course Overview Diagram
Organization
Components
Settlement
Conclusion
Center (CIC)
SAP AG 2003
SAP AG IMD320 12-3

Billing: Business Scenario
z Wireless World News, New York creates the

advance billing documents regularly required for
subscriptions to the Daily Paper on a daily basis.
z Credit and debit memos originating from order
processing are taken into account.
z The billing documents and accrued revenue are
transferred to Financial Accounting.
SAP AG 2003
SAP AG IMD320 12-4

Billing Functions in Subscription Sales &
Distribution
Order Invoice
100.--
100.--
.
Credit memo Cred.memo
request 10.--
! + 10.--
Debit memo Deb.memo

request 10.--
! - 10.--
Invoice Reversal
Invoice 100.--
100.--
SAP AG 2003
Billing supports the following functions:

y Generating billing documents (invoices) based on orders
y Creating credit and debit memos based on requests (suspensions, redirections, terminations, and
complaints)
y Canceling transactions
y Transferring billing documents to Financial Accounting. Due to the quantity and complexity of
the data, the transfer is staggered and takes place in collective runs.
SAP AG IMD320 12-5

Screens in Billing
Header Overviews Item

Transactions for
billing
Conditions Conditions
Billing doc.
Business data
overview Business data
Partners
Items in indiv.
billing doc. Partners
Output
FI accounting
Texts document Texts
SAP AG 2003
To access the detail screens, choose the corresponding function.

Detail screens with custom text are planned but are not available at present.
You can display the corresponding accounting document if the following criteria apply:
y If Financial Accounting is processed in the FI module of the same SAP system
y If the current billing document corresponds to one accounting document; in other words, if it was
transferred individually. You can display a collective document for subscription billing
documents that are usually transferred to Financial Accounting by means of a collective transfer.
SAP AG IMD320 12-6

Billing Method
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
SAP AG IMD320 12-7

Billing Arrangements
Subscription billing arrangements
Publication
(media product
family)
Billing
calendar
Billing Billing Price

frequency calendar frequency
Billing takes place Billing schedule for Price for annual,

annually annual billing, monthly billing
quarterly monthly billing etc.
monthly
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
SAP AG IMD320 12-8

Pricing in the Billing Document
Price: Price: Discount

From 1 PC 10.00 From 1 PC 11.00 From
10 PC 9.50 10 PC 10.50 50.00 1 % -
20 PC 9.00 20 PC 10.00 100.00 2 % -
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.
SAP AG IMD320 12-9

Reversal
Order item Billing 100.--

Credit/debit item
memo req.
Incorrect
prices
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.
SAP AG IMD320 12-10

Billing in Collective Processing
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
You can create billing documents in collective processing.

Creation takes place in background processing using a report with the following selection criteria:
y Billing date to: the program selects all business transactions due up to this date that have not yet
been billed. The billing date is determined from the billing frequency or billing calendar.
y Billing type
y Payer
y Payer's name
y Payment method
You can use all the reporting functions, such as variants and jobs, to schedule collective processing
periodically.
SAP AG IMD320 12-11

Simulating Billing
Simulate Billing - Central Access
Area Code Tel. No.

Mayer BPartner
Name
SINo.
First Name
x
Simulate
Street Sold-To Party
New York
x
Ship-To Party
=
City
Postal Code Ctry US
Bill-To Party Create
Payer
Search Term Sales Agent
Sales Organization 0001 Distribution Channel 01 Division 01
Order Number Item Number

Order Type Authorization:
Publication Edition Display
Sales Office
Bank Key Bank Acct Bank Ctry
Card Number
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
SAP AG IMD320 12-12

Invoicing for Specific Dates
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
Order 3 Order 3 May 31

Subs.
order
Order 4 May 31
Order 4
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.
SAP AG IMD320 12-13

Forms of Invoicing
1 Separate invoice per order item 3 Collective invoice

Subs.
billing doc.
Subs.
order Subs.
billing doc. Subs.
order
Subs.
billing doc.
Subs.
order
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 Billing date (from calendar or frequency)
y Terms of payment
y Payment method and bank details
y Indicator for separate invoice
SAP AG IMD320 12-14

Billing for a Fixed Number of Deliveries
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.
SAP AG IMD320 12-15

Billing Due Date with Customer Exit
Billing due date Billing due date set

according to billing by customer exit
frequency or billing
calendar
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
SAP AG IMD320 12-16

Moving Billing by Customer Exit
Billing due Billing doc. Billing due Billing doc.

date creation date creation
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
SAP AG IMD320 12-17

Billing Document Transfer (FI/CO Interface)
Customizing Transfer via FI/CO interface
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.
SAP AG IMD320 12-18

Data Transfer to Financial Accounting (FI-AR)
IS-M/SD
Billing
documents
Collective transfer Single transfer

Payment card
FI transfer
Intermediate
payment dataset
Payment House bank Customer

account
G/L Rec. acct
Payment Payment list
media Log accounts Payment
cards
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 IMD320 12-19

Goals of IS-M/CA
Subledger accounting for applications with the

following features:
Mass contract invoicing, open item accounting
Many business partner master records
Several accounts possible per business partner
Business volume controlled by account master records rather
than by business partner master record
Possibility of changing or enhancing standard process flows in
standard processes (such as posting and payment)
Designed for customer processing
IS-M/CA is not a full subledger accounting system but is always

part of an industry or project solution.
SAP AG 2003
SAP AG IMD320 12-20

Central Objects in IS-M/CA
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
z Subscription order Subs. Subs. Subs.

order order order
z Document items IS-M
SAP AG 2006
SAP AG IMD320 12-21

Parallel Process Flows
Problem: mass processing requires an extremely long

runtime
z Split processes into packages (intervals) of similar sizes

according to
Business partner
Contract account
z Form interval variants
Number of intervals
Size of intervals
z Split up the intervals in different jobs run on different
computers
SAP AG 2003
SAP AG IMD320 12-22

Integration of IS-M/SD with IS-M/CA: Overview
Media Sales and Contract Accts General

Distribution Receivable and ledger
Payable
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.
SAP AG IMD320 12-23

Periodical Revenue Accrual
Billing doc. Revenue Revenue

Period 1: 10.-
Billing doc.
Period 2: 10.- Revenue Debit Credit
Billing doc. Period 3: 10.- accrual for
Period 4: 10.- 10 .-
each posting
Billing doc. Period 5: 10.-
Period 6: 10.-
period
Net amount: Revenue
Period 7: 10.-
120 .- Period 8: 10.- accrual
Period 9: 10.-
Billing Debit Credit
Period 10: 10.-
period: Period 11: 10 .- 10 .- 120 .-
Period 12: 10 .-
01/01 12/31
Customer
Transfer Debit Credit
billing document 120 .-
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.
SAP AG IMD320 12-24

Performance-Related Revenue Accrual with
Liability Account
Billing doc. Amortization Revenue

Plan
Billing doc.
Debit Credit
Billing doc. Billing cycle: Amortization
0001 for each issue 10 .-
Billing doc.
Net amount: Liability acct: Revenue
120 .- 4711 accrual
Billing cycle: Net value: 10 .-
0001 Debit Credit
Liability acct: 10 .- 120 .-

4711
Customer
FI/CO
IS-M/SD FI CO
interf.
SAP AG 2003
Only possible if the order has a monetary or delivery-related liability account.

Performance-related revenue accrual with a liability account is determined by the legal requirements
of the country in question.
There are two types of revenue recognition:
y Revenue is recognized independently of billing in activity output (Anglo-American accounting
method).
y Revenue is dependent on activity output and can only be recognized once the billing document
has been transferred to Financial Accounting (German accounting method).
When revenue is posted, CO account assignment can be performed for the issue.
SAP AG IMD320 12-25

Performance-Related Revenue Accrual Without
Liability Account
Billing doc. Revenue Revenue

Iss. no. 1: 10.-
Billing doc.
Iss. no. 2: 10.-
Iss. no. 3: 10.-
Revenue Debit Credit
Billing doc. accrual
Iss. no. 4: 10.- 10 .-
Billing doc. Iss. no. 5: 10.- for each issue
Iss. no. 6: 10.-
Net amount: Iss. no. 7: 10.- Revenue
120 .- Iss. no. 8: 10.- accrual
Billing period: Iss. no. 9: 10.-
Debit Credit
12 issues Iss. no. 10: 10.-
Iss. no. 11: 10 .- 10 .- 120 .-
Iss. no. 12: 10 .-
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 IMD320 12-26

Revenue Accrual Cockpit
Activities that can be executed in dialog:

Types of revenue Generate check list
accrual: Display worklist
Reverse FI documents from the check list
Period-related
Per issue
Performance-related
with liability account
Liability account
closure
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 IMD320 12-27

Billing: Unit Summary

z Describe the billing functions and control options
in detail
z Describe and use the options for creating billing
documents
z Transfer billing documents to Financial
Accounting
z Describe the integration of IS-M/SD with Contract
Accounts Receivable And Payable, IS-M/CA
z Explain the options for revenue accrual
SAP AG 2003
SAP AG IMD320 12-28

Exercises
Unit: Billing Unlimited Subscriptions

Topic: Billing/Transfer

describe the billing functions and control options in detail
describe and use the options for creating billing documents
bill subscriptions, suspensions, and redirections
create collective processing runs
create transfer data for Financials and perform individual transfers
transfer data online to Financials
analyze billing documents from the order overview
check and monitor billing documents
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-1 Bill a subscription

1-1-1 Create a new subscription with the order type ABO.
Order Number
1-1-2 Create the billing document for your subscription.
Billing Document
1-1-3 Check your billing document. Determine the collective run or the collective run
number and the billing date and billing period.
Collective
Processing
Billing Date
Billing From
Billing To
1-1-4 Check pricing in your billing document.
SAP AG IMD320 12-29

1-1-5 Exit the CIC and check your billing result using the collective processing log.
1-2 Bill a subscription with a suspension and a redirection.

1-2-1 Create a redirection and then a suspension for the subscription for your
business partner JSU-##.
1-2-2 Check the billing data for the item in the subscription for your business partner
JSU-##. The indicators Billing Completed and End of Billing Period are not
displayed in the standard item.
SI S R
Billing Method
Price Basis
Next Billing Date
Billing Complete Indicator
End of Billing Period Indicator
1-2-3 Bill your subscription with the suspension and redirection.
The standard item, the suspension, and the redirection are listed as individual
items for billing.
1-2-5 Check the billing result using the collective processing log.
1-3 Create a collective processing run.

1-3-1 Create additional orders for your business partner JSU-##.
1-3-2 Perform billing in background processing using the collective processing run.
Select by payer JSU-## to avoid billing other groups orders.
Execute this program in background processing only!
Note down your collective processing number.
1-3-3 Check whether your billing run was completed successfully using the job
overview.
1-4 Create an individual transfer.

1-4-1 Transfer your collective run to Financial Accounting in dialog processing.
Note: Please transfer your own runs only.
Note down the transfer number:__________________
1-4-2 Use the log to check whether the transfer run was completed successfully.
1-5 Analyze your billing documents from the overview in the navigation area in the
Customer Interaction Center.
SAP AG IMD320 12-30

1-6 Create a transfer for a subscription with the payment method credit card.
1-6-1 Create a further order for your business partner JSU-## with the payment
method credit card (AMEX 1112223334445##).
1-6-2 Bill this order.
Note down your billing document or collective processing number.
1-6-3 Execute payment card authorization for your collective run.
1-6-4 Transfer your collective run using an individual transfer.
Note: If FI-CA is active, the transfer always takes place as an individual
transfer.
Please transfer your own runs only.
1-6-5 Use the log to check whether the transfer run was completed successfully.
SAP AG IMD320 12-31

SAP AG IMD320 12-32
Solutions
Unit: Billing Unlimited Subscriptions

Menu path for the exercises in the CIC:

Distribution
Menu path for the other exercises:
Periodical Sales and Distribution Billing
1-1 Billing for a subscription

1-1-1 Create a new subscription with the sales document type ABO for your
publication JMH*.
Note down the order number of the subscription.
1-1-2 Sales Order Customer Interaction Center Front Office Front
Office
Action Box in CIC: BillDoc -> M/SD: Create OrdBDoc
Select the order you just created in the list of billing indexes. Choose Create
Billing Document and then save in the billing item overview.
1-1-3 Choose Refresh in the business partner environment.
Choose your billed order in the business partner environment and expand the
structure so that the billing document is displayed for the order item.
Select the billing icon with the right mouse key and choose Display Billing
Document from the context menu.
Note down the billing document number.
You can determine the billing date in the overview of billing items.
Choose Details to determine the billing period.
Choose Header Details to determine the collective processing run created for
your billing document.
1-1-4 Choose Conditions in the overview of billing items. You can check the
conditions using the Details, Analyze and Condition Record buttons.
1-1-5 Periodical Sales and Distribution Billing Billing Document
Collective Processing Log
Enter your user name or the number of your collective run and choose Execute.
SAP AG IMD320 12-33

1-2 Billing for suspensions and redirections
1-2-1 Create a redirection and a suspension for the subscription for your business
partner JSU-##.
1-2-2 You access the various items for the order in the application area by double
clicking on them.
You can display the relevant billing data on the Billing tab in the standard,
suspension, and redirection item.
SI S R
Billing Method in advance retro. retro.
Price Basis Per.price Per.price Per.price
Next Billing Date xx.yy.200z xx.yy.200z xx.yy.200z
Billing Complete Indicator
End of Billing Period Indicator
1-2-3 The procedure is the same as in exercise 1-1-2.
1-2-4 see 1-1-4
1-2-5 see 1-1-5
1-3 Collective billing processing

1-3-1 Create additional orders for the subscriber JSU-##.
1-3-2 Billing Create Collective Processing
Enter ME02 as the sales organization and your payer JSU-##, and tomorrows
date in the field Billing Date To, and then choose Program Execute in
Background.
Remove the Test Run indicator.
1-3-3 System Services Jobs Job Overview Enter
1-3-4 see 1-1-5
1-4 Individual transfer

1-4-1 Transfer Individual Transfer
Enter the company code ME02, the number of your collective run, and
tomorrows date in the Billing Date To field.
Start transfer as an update run.
1-4-2 Transfer Logs Transfer Run
1-5 Sales Order Customer Interaction Center Front Office Front Office
Choose organization: CIC Agent MSD (tel)
Queue selection: Select both and choose Continue.
SAP AG IMD320 12-34

Enter your business partner JSU-## in the area for the business partner search and
choose Manual Identification.
The Environment tab in the navigation area displays an overview of all billing
documents. Double click to access the detail view.
1-6 Transfer a subscription with the payment method credit card

1-6-1 Create additional orders for the subscriber JSU-## with the payment method
credit card.
To do this, access the item data for the order on the Billing tab and change the
payment method to credit card using the button Payment Method Different from
Contract Account.
Card Type AMEX
Card Number 1112223334445##
Valid To 12/2006
Do not select an order on the screen now displayed, because only the new order
is to be paid with the credit card.
Save the order.
1-6-2 Proceed as described in 1-1 (CIC -> Action Box)
1-6-3 Transfer Payment Card Authorization
Enter the number of your own collective run and your payer. Select
Preauthorization.
Choose Execute to start authorization.
Select your billing document and choose Authorization.
The system displays the following message: Authorization completed
successfully
1-6-4 Transfer Individual Transfer
Enter the company code ME02, the number of your collective run, and
tomorrows date in the Billing Date To field.
Start transfer as an update run.
1-6-5 Transfer Logs Transfer Run
SAP AG IMD320 12-35

SAP AG IMD320 12-36
Exercises
Unit: Billing Renewal Subscriptions


post an incoming payment
describe and use the options for creating billing documents
create collective processing runs
create transfer data for Financials and perform individual transfers
transfer data online to Financials
analyze billing documents from the order overview
check and monitor billing documents
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.
SAP AG IMD320 12-37

2-2 Perform billing for the subscription your created.
2-2-1 Create the billing document for your subscription.
Billing Document
2-2-2 Check your billing document. Determine the collective run or the collective run
number and the billing date and billing period.
Collective
Processing
Billing Date
Billing From
Billing To
2-3 Perform transfer to Financial Accounting.

2-3-1 Transfer your collective run to Financial Accounting by means of an individual
transfer.
2-3-2 Check the transfer run using the log.
SAP AG IMD320 12-38

Solutions
Unit: Billing Renewal Subscriptions

Menu path for the exercises in the CIC:

Distribution
Menu path for the other exercises:
Periodical Sales and Distribution Billing
2-1 Simulate incoming payment

2-1-1 Create a sales order with the sales document type SUBE.
See Sales exercises 1-1, Unit 9.
2-1-2 Create payment lot
Office Action box in CIC: Order -> Inc. Pyt for Renewal
Lot
Please note down the number of the payment lot.
Choose Create.
Search Term Payment lot
number
Document Type ZA
Posting Date Current date
Document Date Current date
Reconciliation Key ##
Currency USD
Bank Clearing Account 113100
Value Date Current date
Company Code ME02
Clearing Reason 01
Selection Categories S G
Line Layout SAP
SAP AG IMD320 12-39

2-1-3 Create new item
Choose New Items
Payment Amount Subscription price
1. Selection Category S
Selection Value 1 Assignment
number
2. Selection Category G
Selection Value 2 BP number
Choose Save.
2-1-4 Close payment lot
Lot
Choose Close.
Answer yes to the system query as to whether all payments have been entered in
full.
Post payment lot
Lot
Choose Post.
Start Directly x
Choose OK.
Choose Continue to confirm the information that the posting run is completed
and you should check its status.
Refresh the order overview using the button provided for this purpose and check
the expiration date in the order, which has been moved back.
2-2 Billing the subscription

2-2-1 Create billing document
Office Action box in CIC: BillDoc -> M/SD: Create OrdBDoc.
Order Number
Choose Execute.
Select all the items listed and choose Create Billing Document. Select the billing
items listed and save the billing document.
2-2-2 Check billing document
Office Action box in CIC: Environment tab
SAP AG IMD320 12-40
In the environment, access the order created in 2-1-1. The billing document you
just created is displayed here. Double click to access an overview of the billing
items.
You can determine the billing date in the overview of billing items.
Choose Details to determine the billing period.
Choose Header Details to determine the collective processing run created for
your billing document.
Note down the billing document number and the number of the collective run.
2-2-3 Check pricing in the billing document
Choose Conditions in the overview of billing items. You can check the
conditions using the Details, Analyze and Condition Record buttons.
2-2-4 Check the collective processing result
Periodical Sales and Distribution Billing Billing Document
Collective Processing Log
Enter your user name or the number of your collective run and choose Execute.
2-3 Data transfer to Financial Accounting

2-3-1 Single transfer
Periodical Sales and Distribution Billing Transfer Individual
Transfer
Company Code ME02
Collective Processing
Billing Date To 1st of next month
Choose Execute.
2-3-2 Log of transfer run
Periodical Sales and Distribution Billing Transfer Logs Transfer
Run
Enter your transfer number and choose Execute. In the overview then displayed,
you can double click to display details on all the billing documents transferred
during this run.
SAP AG IMD320 12-41

SAP AG IMD320 12-42
Settlement
Content:
z Functions in service settlement
z Home delivery settlement
z Commission settlement
SAP AG 2003
SAP AG IMD320 13-1

Settlement: Unit Objectives

z Describe the most important functions for home
delivery and commission settlement in
z Create and process settlements
SAP AG 2003
SAP AG IMD320 13-2

Settlement: Course Overview Diagram
Internet
Organization
Settlement
Conclusion
Center (CIC)
SAP AG 2003
SAP AG IMD320 13-3

Settlement: Business Scenario
z The publishing house Wireless World News, New

York employs carriers and sales agents to supply its
customers and win new ones.
z The services performed by these service agents are
settled at regular intervals.
SAP AG 2003
SAP AG IMD320 13-4

Service Settlement: Settlement Types
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.
Quantitative service settlement
Valuated service settlement
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.
SAP AG IMD320 13-5

Functions in Home Delivery Settlement
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).
SAP AG IMD320 13-6

Functions in Commission Settlement
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)
SAP AG IMD320 13-7

Screens in Settlement
Header Overviews Item
Conditions Transactions for Conditions

settlement
Business data
Settlement Business data
overview
Partners
Partners
Output Settlement
items
Texts Texts
SAP AG 2003
To access the detail screens, choose the corresponding function.
SAP AG IMD320 13-8

Settlement in Collective Processing
Selection criteria
Service company: S1
Home delivery
by May 15
Settlement
Date SC EE
May 12 S1 C1 Home delivery
May 12 S1 C2 Settlement
May 14 S2 C3
May 15 S1 C1
Home delivery
May 17 S1 C1
Log
SAP AG 2003
You can perform settlement in collective processing.

Settlement takes place in background processing using a report with the following selection criteria:
Service company
Employee
Settlement date to: the program selects all business transactions due up to this date that have not
yet been settled. The settlement date is determined using the settlement calendar (from the
employment relationship or the purchasing organization for the service company).
You can use all the reporting functions, such as variants and jobs, to schedule collective processing
periodically.
SAP AG IMD320 13-9

Service Settlement: Data Transfer
Valuated service settlement
Employee "Vendor"
settlement settlement
HR FI FI
Payroll data
(i.e. gross wage)
G/L accounts Vendors
SAP AG 2006
When transferring service settlements to downstream application areas, IS-M/SD makes a

distinction between:
Settlements for employees of owned or affiliated companies: In this case, gross wage elements
are transferred to Human Resources.
Settlements for freelancers or service companies: Here, the settlement results are transferred to
Financials for payment.
Data can be transferred both to Financial Accounting and to Human Resources.
SAP AG IMD320 13-10

Home Delivery Round
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.)
SAP AG IMD320 13-11

Settlement Data for Service Company / Carrier
Calendar Settlement
200 x 0.10 20.00

200 x 0.12 12.00
300 x 0.10 30.00
Procedure
62.00
Tax code 15 % VAT 9.30
Valuation type 71.30 Currency /
exchange rate
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)
SAP AG IMD320 13-12

Contract Arrangements
Basic remuneration types

Carrier rte flat rate Daily rate for edit.
For all editions For each separate Ed.1 Ed.2
For totals edition 04/01 Sa 300 PC 700 PC
-> fixed amount -> edition unit price 04/02 Su 400 PC 710 PC
-> carrier route flat rate for quantity actually 04/03 Mo 200 PC 720 PC
category delivered 04/04 Tu 210 PC 600 PC
04/05 We 250 PC 710 PC
04/06 Th 200 PC 700 PC
Edition period Daily edition 04/07 Fr 250 PC 600 PC
average average/PC 04/08 Sa 340 PC 740 PC
Ed.1 Ed.2 04/09 Su 390 PC 600 PC
Ed.1 1933 PC ->$/PC 04/10 Mo 220 PC 700 PC
Ed.2 4707 PC ->$/PC Sa 283 PC 717 PC
Su 395 PC 04/11 Tu 270 PC 700 PC
655 PC 04/12 We 210 PC 600 PC
Mo 210 PC 710 PC
Tu 240 PC 04/13 Th 300 PC 690 PC
650 PC 04/14 Fr 400 PC 650 PC
We 230 PC 655 PC
Th 250 PC 04/15 Sa 210 PC 710 PC
695 PC
Fr 325 PC 625 PC
$/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
SAP AG IMD320 13-13

Contract Arrangements for Flat Rate Bonuses
Per period and

home delivery round
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
Carrier route 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 IMD320 13-14

Contract Arrangements for Daily Bonuses
Public hol. Public hol.

Working with
day without
delivery delivery
Path length category in carrier
Path comp. route
Inserts Number of inserts in issue
Weight Weight of issue
Category Category Category

Sunday Arrangemt Arrangemt Arrangemt
Category Category Category

Night Arrangemt Arrangemt Arrangemt
Public -- Category Category

holiday Arrangemt Arrangemt
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.
SAP AG IMD320 13-15

Commission Settlement
Sales source
Sales
promotion Publication
Campaign
framework Order1 Order2
Order3
Sales area Event . .

Sales
organization
Initial introduction
Renewal
.
1 Gift
Change pyt meth. Commission Commission
... settlement
Commission settlement
settlement
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.
SAP AG IMD320 13-16

WBZ Commission Settlement
Sold-to party Sales customer

Bill-to party
and SC
Payer
WBZ company
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
Media company Customer

Delivery (subscriber)
WBZ subscription order
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 IMD320 13-17

Settlement: Unit Summary

z Describe the most important functions for service
settlement in Media Sales and Distribution
z Create and process settlements
SAP AG 2003
SAP AG IMD320 13-18

Exercises
Unit: Settlement
Topic: Settlement

describe the most important functions for service settlement in
create data for home delivery and commission settlement
create home delivery and commission settlements
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-1 Maintain the data required for home delivery settlement.

1-1-1 Maintain the settlement data for the service company you created previously,
JSC-##, entering the following:
Currency USD, exchange rate type M, tax code I0, procedure STDZV1
(settlement), calendar JM, valuation type 1 (quantity x price), transfer type 1.
1-1-2 Define the contract arrangements for JSC-##.
Delivery type 01, carrier route CAR-##, delivery round MORNING, contract
arrangement VM01.
1-1-3 Create an employment relationship between your carrier JCA-## and your
service company JSC-## with the following data:
Currency USD, exchange rate type M, tax code I0, procedure ZSTDUS
(settlement), calendar JM, valuation type 1 (quantity x price), transfer type
none.
Period: January 1st of current year to 12/31/9999 (unlimited).
1-1-4 Define contract determination as follows:
Delivery type 01 and contract arrangement VM01.
1-1-5 Create a home delivery round for your carrier route CAR-## and the delivery
round MORNING for your service company JSC-## and carrier JCA-##.
Validity period: January 1st of current year to 12/31/9999.
SAP AG IMD320 13-19

1-2 Execute carrier settlement.
1-2-1 Create employee daily unit remuneration conditions for home delivery
settlement.
1-2-2 Create a carrier settlement in dialog and check the conditions in the settlement
procedure.
Please do not save the settlement.
1-2-3 Check the carrier route/business partner assignment.
1-2-4 Determine the settlement quantity for a particular day.
1-2-5 Execute carrier settlement for this settlement period. Please note that settlement
is performed for the carrier according to a settlement calendar.
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.
1-4 Maintain promotion data for your publication JMH*.

1-4-1 Create a sales promotion SP-1## for a period of 3 months. Enter JMH* as the
publication in the sales promotion.
1-4-2 Create a campaign framework for your sales promotion SP-1## with the sales
source CO (commission) for a validity period of 3 months.
You do not need to assign it to the advertising medium. The minimum length
for a subscription is 12 months.
Your commission recipient JCR-## is assigned to this campaign framework and
receives one-time commission without commission clawback. The campaign
framework references the event Initial Introduction.
1-4-3 Create a new subscription for the sales promotion SP-1## with the sales source
CO.
1-5 Execute commission settlement.

1-5-1 Create employee one-time commission conditions for settlement for your
commission recipient JCR-##.
1-5-2 Execute commission settlement.
SAP AG IMD320 13-20

Solutions
Unit: Settlement
Topic: Settlement
The exercises in this unit all begin with the following menu path:
Distribution
1-1 Data for home delivery settlement

1-1-1 Settlement Home Delivery Master Data Service Company SC
Settlement Data
Service Type 0001
Choose Continue.
Choose New Entries on the screen now displayed.
SC Expense Account 01
Assignment Group
Payment Terms 0001
Currency USD
Country US
Tax Code I0
Procedure STDZV1
Valuation Type 1
Transfer Type 1
SAP AG IMD320 13-21

1-1-2 Master Data Business Partner Connections Contract Determination
Service Company Assignment Purchasing Organization ME02 (Enter)
New Entries
Delivery Type 01
Valid From 01/01 of current year
Contract Arrangement VM01
1-1-3 Master Data Business Partner Connections Employment
Relationship Edit
Employee JCA-##
Role - Carrier
Currency USD
Tax Code I0
Procedure ZSTDUS
Valuation Type 1
Transfer Type None
Choose Insert Row and create the employment relationship for your carrier
JCA-## on the SC Employment Relationship Details: Edit screen.
Valid From 01/01 of current year
Valid To 12/31/9999
Employment Type 02
Title Carrier
When you save, the system displays the following message: Employment
relationship JSC-##/ JCA-## created
SAP AG IMD320 13-22

1-1-4 Master Data Business Partner Connections Contract Determination
Carrier Assignment Service Company JSC-## Enter New Entries
Delivery Type 01
Valid From First day of current year
Contract Arrangement VM01
1-1-5 Master Data Distribution Delivery Home Delivery Home Delivery
Round Edit
Carrier
Carrier
Choose Copy.
1-2 Carrier settlement

1-2-1 Settlement Home Delivery Conditions Master Data Employee
Daily Unit Remuneration Carrier Route Create
Order Delivery Type 01
Publication JMH*
Amount 0.05
Unit USD
per 1
Unit of Measure COP
Valid From 1st of current month
To 12/31/9999
SAP AG IMD320 13-23

1-2-2 Settlement Home Delivery EE Home Del. Settlement Create
Dialog
Settlement Period 1st of next month
Choose Execute.
Select an item on the screen Employee Home Delivery Settlement Create:
Settlement Item Overview. Then choose Conditions.
Please do not save the settlement.
1-2-3 Choose Partner on the screen Employee Home Delivery Settlement Create:
Settlement Item Overview.
1-2-4 Choose Details on the screen Employee Home Delivery Settlement Create:
Settlement Item Overview.
1-2-5 Save the carrier settlement.
Document xxxxxxx saved (no accounting document generated)
1-3 Data for commission settlement

1-3-1 Settlement Commission Master Data Service Company SC
Settlement Data
Service Type 0002
Choose Continue.
SAP AG IMD320 13-24

Choose New Entries on the screen now displayed.
SC Expense Account 01
Assignment Group
Payment Terms 0001
Currency USD
Country US
Tax Code I0
Procedure STDPV1
Valuation Type 1
Transfer Type 1
1-4 Promotional data

1-4-1 Sales Support Sales Promotion Create
Sales Promotion SP-1##
Short Text Sales Promotion 1##
Valid To + 3 months
Publication JMH*
SAP AG IMD320 13-25

1-4-2 Sales Support Campaign Framework Create
Division J8
Sales Source CO
Include Advertising
Medium
Sales Promotion SP-1##
Minimum Length of 12 months
Subscription
Commission Recipient JCR-##
Commission Clawback 0
Type
Event Initial Introduction
1-4-3 A new subscription is required for the sales source CO and your sales promotion
SP-1##.
1-5 Commission settlement

1-5-1 Settlement Commission Conditions Master Data Employee One-
Time Commission Title Create
Publication JMH*
Minimum Length of 12
Subscription
Time Unit MON
Service Type FD
Amount 5
Unit USD
per 1
Unit of Measure COP
Valid From 1st of current month
To 12/31/9999
SAP AG IMD320 13-26

1-5-2 Settlement Commission EE Commission Settlement Create Dialog
Settlement Period 1st of next month
Choose Execute and save the commission settlement.
SAP AG IMD320 13-27

SAP AG IMD320 13-28
Pricing
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 IMD320 14-1

Pricing: Unit Objectives

z Explain and demonstrate the basics of the condition
technique
z Describe the condition elements used in pricing and
output determination and set them up in
Customizing
z Maintain condition master data
SAP AG 2003
SAP AG IMD320 14-2

Pricing: Course Overview Diagram
Internet
Organization
Settlement
Conclusion
Center (CIC)
SAP AG 2003
SAP AG IMD320 14-3

Pricing: Business Scenario
z Wireless World News, New York sells the daily

newspaper Daily Paper on a regional basis.
Besides private individuals, its subscribers include
a number of companies. This means the publisher
needs to tailor its retail prices flexibly to meet the
requirements of the customer group in question
and sometimes to meet one customer's needs.
z The dense population of the distribution area and
its constant fluctuation result in a large volume of
changes to orders, which mean that automatic
correspondence (for example, order and change
confirmations, subsequent deliveries, invoices,
and service settlements) is a must.
SAP AG 2003
SAP AG IMD320 14-4

Condition Technique - Overview
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
Condition type Cond.

Cond. type
type ...
...
Access
Access seq.
seq. 11
Access sequence Access
Access seq.
seq. 22
Access
Access seq.
seq. ...
...
Access condition Access

Access 11
Access
Access 22
table Access
Access ...
...
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.
SAP AG IMD320 14-5

Condition Technique: Process Flow (1)
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.
SAP AG IMD320 14-6

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.
SAP AG IMD320 14-7

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.
SAP AG IMD320 14-8

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.
SAP AG IMD320 14-9

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.
705
2.
2. DelType/ServType
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.
SAP AG IMD320 14-10

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.
705
2. Records
Records in
in Table
Table 706
706
2. DelType/ServType
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.
SAP AG IMD320 14-11

Uses of Pricing
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.
SAP AG IMD320 14-12

Special Features of Pricing Conditions
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
SAP AG IMD320 14-13

Applications for Output Determination
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.
SAP AG IMD320 14-14

Special Features of Output Determination
Conditions
Output
Output determination
determination conditions
conditions
Processing
Processing Form
Form Partner
Partner roles
roles Shipping
Shipping time
time
program
program
Shipping
Shipping medium
medium
Printout Fax Workflow Mail EDI
SAP AG 2003
You can specify the following for output:

y When the output is sent (transmission time)
y How the output is sent (transmission medium)
y Organizational criteria according to which printers are assigned if the output is to be printed out
(transmission medium 1: printout)
y Program used to select the data (processing program)
y Form used for output
You assign a printer for output that is to be printed out (transmission medium 1).
You enter a mail text and define mail parameters for output that is to be sent by mail (transmission
medium 4).
SAP AG IMD320 14-15

Pricing: Unit Summary

z Explain and demonstrate the basics of the
condition technique
z Describe the condition elements used in pricing
and output determination and set them up in
Customizing
z Maintain condition master data
SAP AG 2003
SAP AG IMD320 14-16

Exercises
Unit: Pricing and Output Determination

Topic: Conditions

explain and demonstrate the basics of the condition technique
check the assignment of the pricing procedure and pricing/output
determination
create conditions
check pricing and output determination
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-1 Check the pricing procedure in order creation.

1-1-1 Create a business partner JSU-##1 with a delivery address outside of North
America and a subscription, in the CIC. (For example, Blumenstr. 5, 01307
Dresden, DE.) Check which pricing procedure is assigned.
Pricing procedure:________________________
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?
_______________________
SAP AG IMD320 14-17

1-3 Maintain the purchase price and the shipping costs for your publication.
1-3-1 Maintain a purchase price of 16 USD for a full subscription to your publication
JMH* with a price frequency of 4 weeks.
1-3-2 Maintain shipping costs of 24 USD for subscriptions to your publication JMH*
with the delivery type 04.
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-5 Create order confirmations and changes for your subscription.

1-5-1 Create a new subscription with the sales document type ABO.
1-5-2 Check your order to find out whether output was determined.
1-5-3 Save your order.
1-5-4 Check the result of your output in the spool request.
1-5-5 Make an unlimited change to your order and check output determination.
1-5-6 Save your change.
SAP AG IMD320 14-18

Solutions
Unit: Pricing and Output Determination

Topic: Conditions
The first two exercises in this unit begin with the following menu path:
Distribution
The remaining exercises begin with the following menu path:
Tools AcceleratedSAP IMG Edit Project SAP Reference
IMG SAP Media Basic Functions Pricing Pricing in Media
Sales and Distribution Pricing in Order Processing/Billing
1-1 Check assignment to pricing procedure.

Sales Order Customer Interaction Center Front Office Front Office
1-1-1 Choose Header Data to access your order. The subscription for your new
business partner JSU-##1 is assigned to the following pricing procedure.
Order Type Pricing Procedure Text
SUBE ZS_RNW Standard renewals IDES USA
ABO ZS_SUB Standard subscription
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-3 Master Data Conditions Application Objects Order/Billing Doc.

1-3-1 Sales Order Prices Including Taxes ZRPR Basic Price Key
Combination: Sales org./dist. channel/publication/price freq./billing freq.
SAP AG IMD320 14-19

Publication JMH*
Price Frequency 4W
Service Type FD
Amount 16
Unit USD
per 1
Unit of Measure COP
Choose <Enter> and the system enters values in all the other fields.
Condition records saved
1-3-2 Sales Order Prices Including Taxes ZSCH Shipping Costs Key
Combination: Shipping Costs (Service Type)
Publication JMH*
Delivery Type 04
Service Type FD
Amount 24
Unit USD
per 1
Unit of Measure COP
Choose <Enter> and the system enters values in all the other fields.
Condition records saved
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.
SAP AG IMD320 14-20

1-5 Order confirmation
Caution: The order confirmation is only created for the order type ABO.
1-5-1 Create a new order.
1-5-2 Choose the menu path Extras -> Output to navigate to the output on the screen
Create Subscription Order: Basic Item Data. Output type KDP2 is proposed.
1-5-3 Choose Save.
1-5-4 System Own Spool Requests
The system displays a corresponding spool entry. Click on the icon to display a
print preview.
1-5-5 Change the existing order.
Choose Extras Output to determine the output type that is proposed.
1-5-6 Choose Save.
SAP AG IMD320 14-21

SAP AG IMD320 14-22
Circulation Auditing
Content:
z Circulation auditing
IVW (Germany)
ABC (USA)
SAP AG 2003
SAP AG IMD320 15-1

Circulation Auditing: Unit Objectives

z Explain the characteristics of circulation auditing
SAP AG 2003
SAP AG IMD320 15-2

Circulation Auditing: Course Overview Diagram
Internet
Organization
Settlement
Conclusion
Center (CIC)
SAP AG 2003
SAP AG IMD320 15-3

Circulation Auditing: Business Scenario
z Wireless World News, New York makes significant

profits from the advertisements placed in its
newspapers and magazines.
z Since circulation figures directly influence pricing in
the advertising business, it is important that the
publisher monitor its circulation and have the
figures certified by central institutions (ABC).
z Audit reports are created regularly for this purpose.
SAP AG 2003
SAP AG IMD320 15-4

IVW (Overview)
Deliveries
Orders
} Update
Daily IVW statistics
(JITSTAT)
IVW hierarchy/ies
Evaluations and
auditing programs
SAP AG 2003
SAP AG IMD320 15-5

IVW Update
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).
SAP AG IMD320 15-6

IVW Hierarchy
Sel. criterion
Orders
Evaluations and
IVW hierarchies auditing programs
Basic reference category .....
SAP AG 2003
You can define as many IVW hierarchies as you wish.

The end nodes in the hierarchies are basic categories; these are referenced in order items.
To perform an evaluation, you must specify a hierarchy, which is used to control further
summarization (in group categories).
SAP AG IMD320 15-7

IVW Audit Reports and Evaluations
z Evaluation of daily IVW

statistics
z Summarization of data Daily IVW statistics
JITSTAT-XIVWMELD = 'X'
according to selected (JITSTAT)
IVW hierarchy
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 IMD320 15-8

IVW Revenue Accrual
IVW revenue accrual
Comparison of IVW audited quantities, billed quantities, and billing

amounts
Monthly revenue accrual
Accrual of billing amounts and quantities to periods (months) according

to transfer logic
Revenue accrual by copy
Accrual of billing amounts and quantities to individual issues (copies)

Use of ALV (general list viewer) functions according to entries on
selection screen
SAP AG 2003
SAP AG IMD320 15-9

ABC (Overview)
Edition Audit report type (TJD57)
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.
SAP AG IMD320 15-10

ABC - Updating the Circulation Book
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 IMD320 15-11

Circulation Auditing: Unit Summary

z Explain the characteristics of circulation auditing
SAP AG 2003
SAP AG IMD320 15-12

Conclusion
Internet
Organization
Settlement
Conclusion
Center (CIC)
SAP AG 2003
SAP AG IMD320 16-1

Course Goals
You are now able to
z Make the basic system settings for implementing

z Work with the functions in Subscription Sales and
Distribution
SAP AG 2003
SAP AG IMD320 16-2

Recommended Follow-Up Courses
z IMD500 Single Copy Sales of Newspapers and Magazines

z LO840 Customer Interaction Center
z BW3xx Business Information Warehouse (BW)
z IUT240 Contract Accounts Receivable and Payable
z SAPCRM CRM Overview
z CR100 CRM Basics
z SCM620 Pricing in SD
SAP AG 2003
SAP AG IMD320 16-3

Recommended Follow-Up Activities
z Go through the exercises using IDES data or your own data

z Read the online documentation
z Read the IMG documentation
z Read the Release notes
SAP AG 2003
SAP AG IMD320 16-4

IMD320 - SAP For Media - Periodical Sales and Distribution EN

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

IMD320 - SAP For Media - Periodical Sales and Distribution EN

Uploaded by

Copyright:

Available Formats

IMD320 SAP for Media Sales and Distribution of

THE BEST-RUN BUSINESSES RUN SAP

SAP for Industries

Copyright 2009 SAP AG. All rights reserved.

Notes for use

SAP AG IMD320 1-1

This course will prepare you to:

SAP AG IMD320 1-2

At the conclusion of this course, you will be able to:

z Describe and use the basic functions in

SAP AG IMD320 1-3

Unit 1 Course Overview Unit 9 Sales

Exercises and Solutions

SAP AG IMD320 1-4

Course Overview Sales

Business Partner Shipping

Media Product Billing

Geographical Structures and

Distribution Master Data Pricing

Sales Support Circulation Auditing

SAP AG IMD320 1-5

z Wireless World News, New York sells four regional

SAP AG IMD320 1-6

Business Information Warehouse

Sales Subscription orders AI orders Bundling

Commission Billing Home delivery

Customers Vendors G/L accounts

SAP AG IMD320 1-7

Unit: Getting Started with SAP R/3

At the conclusion of these exercises, you will be able to:

1-1 Log on to the R/3 System.

1-3 Describe two different ways of accessing an application.

1-5 Create a second and third session in two different ways.

1-7 Enter an address in your user profile.

Unit: SAP R/3 Introduction

1-2 Menu path:

1-5 Menu bar:

SAP AG IMD320 1-11

1-7 Menu bar:

1-8 Menu bar:

SAP AG IMD320 1-12

Unit: Getting Started with the Tools

At the conclusion of these exercises, you will be able to:

SAP AG IMD320 1-13

Unit: Getting Started with the Tools

SAP AG IMD320 1-15

SAP AG IMD320 2-1

At the conclusion of this unit, you will be able to:

SAP AG IMD320 2-2

Course Overview Sales

Business Partner Shipping

Media Product Billing

Sales Support Circulation Auditing

Customer Interaction Center

SAP AG IMD320 2-3

z Wireless World News, New York sells print media

SAP AG IMD320 2-4

Views Organizational units

Cost accounting Company

External logistics Sales org. Purchasing org.

Accounting Company code

Internal logistics Plant

Aims of the organizational structure in R/3: