Вы находитесь на странице: 1из 36

SAP Media

PDF download from SAP Help Portal:


http://help.sap.com/saphelp_media472/helpdata/en/45/E98C371E558216E10000009B38F889/frameset.htm
Created on October 10, 2014
The documentation may have changed since you downloaded the PDF. You can always find the latest information on SAP Help Portal.
Note
This PDF document contains the selected topic and its subtopics (max. 150) in the selected structure. Subtopics from other structures are not included.
2014 SAP SE or an SAP affiliate company. 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 SE. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE
and its distributors contain proprietary software components of other software vendors. National product specifications may vary. These materials are provided by
SAP SE and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be
liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express
warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty. SAP and other
SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE in Germany and other
countries. Please see www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.
Table of content
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 1 of 36
Table of content
1 SAP Media
1.1 Master Data
1.1.1 Distribution
1.1.2 SAP Business Partner (SAP BP)
1.1.3 Product
1.1.4 Sales Support
1.1.5 Shipping
1.2 Media Sales and Distribution
1.2.1 Periodical Sales and Distribution
1.2.2 Media Product Sales and Distribution
1.2.3 Series Sales and Distribution
1.2.4 Contract Accounts Receivable and Payable
1.3 Advertising Management
1.3.1 Order
1.3.2 Contract
1.3.3 Billing and Settlement
1.3.4 Legacy Data Transfer in Advertising Management
1.3.5 SAP Media Document Management
1.3.6 Integration of Technical Systems
1.3.6.1 Ad Sales With an Integrated Technical System
1.3.6.1.1 Ad Sales With a Technical System as the Back End
1.3.6.1.2 Ad Sales With a Technical System as the Front End
1.3.6.2 Integration of Technical Systems (English)
1.3.6.3 Integration of Technical Systems (German)
1.4 Classified Advertising Order Management
1.4.1 Classified Advertising Management (IS-M/AMC)
1.5 Customer Interaction Center (CIC)
1.5.1 Customer Interaction Center (CIC)
1.6 Title Lifecycle Management
1.6.1 Product Development in the Media Industry
1.6.2 Intellectual Property Management (IPM) Integration
1.6.3 By Title Financial Processing and Reporting
1.7 Web Applications
1.7.1 M/SD Internet Applications
1.7.2 M/AM Internet Applications
1.7.3 MiniApps
1.8 Data Archiving
1.8.1 Data Archiving in SAP Media
1.9 Roles
1.9.1 Single Roles for SAP Media
1.9.2 Single Roles in Media Sales and Distribution
1.9.3 Single Roles in Advertising Management
1.10 Campaign Management for the Media Industry
1.10.1 Campaign Management for the Media Sector
1.11 Release Notes SAP Media 4.72
1.11.1 Release Notes SAP Media 4.72 (English)
1.11.2 Release Notes SAP Media 4.72 (German)
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 2 of 36
!--a11y-->
1 SAP Media

Online documentation for SAP Media release 4.72 (based on standard 6.30)
Feedback



!--a11y-->
1.1 Master Data
!--a11y-->
1.1.1 Distribution
Purpose
The component distribution master data contains functions for recording and maintaining the following data:
Master data
on transportation of media products. This includes the following data:
Unloading points
Truck routes
used to supply customers
Unloading point sequences
for truck routes
Assignment of editions to truck routes
The component contains the functions required for automatic generation of truck route master records for specific dates.
Constraints
under which media products can be supplied. These are reproduced in the system as follows:
Delivery viability sets
The delivery viability set defines the admissibility of delivery of a product (publication, edition) for a combination of criteria, such as the delivery
type, sales area, plant, carrier route, delivery round etc.
Unloading viability sets
The unloading viability set links the data on the delivery viability set with the concrete unloading point in the carrier route.
Unloading rules
If more than one unloading point is to be supplied in the carrier route or an unloading point is supplied by more than one truck route, the system lists
unloading rules so that you can maintain them. You define the desired quantity distribution in the unloading rule.
Home delivery rounds
You define the assignment between the carrier (or field collector) and the delivery round in a home delivery round.
Shipping schedules
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 3 of 36
You define the unloading points for postal shipping in the shipping schedule.
Distribution master data in Media Sales and Distribution and Advertising Management
In Media Sales and Distribution, the distribution master data screen contains functions for geographical structuring and change management in addition to the
actual distribution master data . (See Geographical Structures ).
In Advertising Management, the distribution master data screen only contains functions for geographical structuring and change management . However, you
can access distribution master data in Media Sales and Distribution directly from the distribution master data in Advertising Management.
Implementation Considerations
The Implementation Guide for the industry-specific components for media contains Customizing settings for this component under Master Data
Distribution.
Integration
The distribution master data is based on the geographical structures you create in the system using the functions for geographical structuring . As in the case of
geographical structures, maintenance of distribution master data takes place in Change Management .
Features
The component distribution master data has the following features:
Function Use
Maintain unloading points Creating and changing various types of unloading points, e.g. general carrier
route unloading point, business partner unloading point, plant loading point
Edit truck route master data and assignments to truck routes
Creating and changing truck route master records
Creating and changing the following assignments:
Unloading points per truck route (unloading point sequence)
Allowed editions per truck route
Truck route hierarchies (assigning split and subsequent truck routes to higher
level routes)
Generating truck route master records for specific dates (daily truck routes)
Creating and changing truck route contracts
Edit delivery viability sets
Creating and changing delivery viability sets
Mass generation of delivery viability sets
Creating and changing the assignment of researchers to delivery viability
sets
Edit unloading viability sets Creating and changing unloading viability sets manually (assigning unloading
point to carrier route)
You can have the system generate unloading viability sets automatically based
on the delivery viability sets if you have made the appropriate presettings.
Edit unloading rules (quantity distribution, exceptions)
Editing unloading rules for several unloading points in a carrier route
Editing unloading rules for several truck routes for an unloading point
Edit home delivery rounds in carrier route
Creating and changing the assignment of carriers and field collectors to
delivery sets (if delivery viability sets are defined for them)
Recording substitutions of carriers or field collectors in delivery rounds (in
the case of illness, leave etc.)
Edit shipping schedules for postal dispatch Creating and changing shipping schedule variants (grouping of editions with the
same postal delivery type) and shipping schedules (assignment of shipping
schedule variants to postal code areas, countries or country groupings).
Evaluations of distribution master data Creating overviews such as:
Truck routes, unloading points or viable editions for the carrier route
Daily truck routes for shipping date
Unloading point sequences for key date


!--a11y-->
SAP Business Partner (SAP BP)
Purpose
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 4 of 36
The component SAP Business Partner enables you to create and manage business partners centrally. SAP Business Partner is designed to utilize technical
benefits such as data integrity and freedom from data redundancy, and to place greater emphasis on aspects relating to customer maintenance and acquisition of
new customers.
If you want to use the SAP business partner in the industry-specific components for media , IS-M business partners must first be migrated to SAP business
partners.
If IS-M business partner master data does not yet exist in your system, you must still perform migration. This ensures that Customizing and the required
assignments are set up correctly, and you can only activate the SAP Business Partner for SAP Media using the migration tool.
Integration
Advertising Management
Periodical Sales and Distribution (sales and distribution of newspaper and magazine subscriptions)
Media Product Sales and Distribution (sales and distribution of newspapers and magazines to retailers)
Series Sales and Distribution (sales and distribution of book series, journals, and loose-leaf publications)
Media Product Development
Features
You can create a business partner in different business partner roles. During the course of the business relationship, the business partner can assume other
business partner roles. No new data has to be created each time, meaning that redundant data creation and retention is avoided, and there can be no
inconsistencies.
By using SAP Business Partner, it is possible to merge the partner data already held by a company in more than one system in such a way that the potential for
new contracts within the same customer contact can be identified.
When you enter data, the data related to SAP Business Partner, and the application-specific data are integrated seamlessly on the processing screen.
Seamless integration of customer-specific data is possible without modification, ensuring full future maintenance, because defined interfaces exist for this
purpose.
Customizing Settings
You can make the Customizing settings for the SAP business partner under Cross-Application Components SAP Business Partner in the Implementation
Guide.
IS-M-specific Customizing settings for the SAP Business Partner can be made in the Implementation Guide under SAP Media Master Data SAP
Business Partner for Media Companies .

!--a11y-->
1.1.3 Product
!--a11y-->
1.1.4 Sales Support
Purpose
The component sales support master data contains functions that enable you to do the following:
Record marketing-related master data on activities, materials and requirements that affect order processing
Record contacts with customers and performance of sales support activities such as mailing activities
Integration
The master data you create in sales support is used to control processing of sales orders. For example, the sales source defined in Customizing controls for
each order item whether research is generated when an order is entered, whether the sales agent must be a reader and whether the sales agent or sales source
has to be specified in the order.
Features
The component sales support contains the following functions:
Maintenance
of the following objects
Sales source (Customizing)
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 5 of 36
Sales promotion
Promotional material
Advertising medium
Campaign framework
Sales activity
Output
of the following
Standard letters
Labels for gifts
Evaluations
of subscriptions:
Analysis of live subscriptions
Comparison of live subscriptions normal free
Comparison of all live subscriptions
Analysis of transactions affecting live subscriptions
Comparison of transactions affecting live subscriptions
Lifetime analysis
Comparison
of sales promotions
Overviews
Orders for gift (with access to order)
Sales promotions for geographical unit
Sales activities for business partner (with access to sales activity data)


!--a11y-->
1.1.5 Shipping
Purpose
The component shipping master data contains functions that can be used to record basic data for use in shipping functions.
Integration
Shipping of ad inserts and direct-distribution advertising based on orders in Advertising Management is processed using the shipping functions in Media Sales
and Distribution.
Features
The component contains the following functions:
Function Use
Edit technical order deadline limit To avoid errors when setting the order deadline (checking function)
Edit packaging rules for bundling, postal packing and container packing To control the shipping functions bundling and container packing
Edit production master data for shipping
(Production sequence for editions with different insert mixes)
To control creation of production data in shipping as the basis for creating production-
oriented shipping documents
Edit shipping document type usage for general and production-oriented shipping
documents
To control shipping document creation
Edit destination determination for shipping document types
(exception rule for alternate destination)
To control shipping document creation


!--a11y-->
1.2 Media Sales and Distribution


!--a11y-->
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 6 of 36
1.2.1 Periodical Sales and Distribution
Purpose
This component of Media Sales and Distribution contains functions for processing subscription sales and distribution for publications that appear at regular
intervals (newspapers and magazines). It contains subscription-specific functions for the following areas:
Master data (business partner, product, geographical structuring, distribution, etc.)
Sales (order processing for different forms of subscription)
Shipping (for example, home delivery)
Billing
Settlement (home delivery and commission settlement)
Integration
The following components are also available for use in sales and distribution of media products:
Media Product Sales and Distribution for processing single copy sales of media products (newspapers and magazines) to retailers
Series Sales and Distribution for processing sales of series products (such as journals and looseleaf publications) to sales customers

!--a11y-->
Media Product Sales and Distribution
Purpose
SAP Media 1.2.2 Media Product Sales and Distribution is a solution for sales and logistics for publishers and wholesalers. It supports the processes for
single copy sales of media products, such as newspapers, magazines, and books, to retailers (for example, this term includes wholesalers, station
bookstores, newsstands, and gas stations).
Integration
The solution for Media Product Sales and Distribution is based on the standard functions for sales and distribution and logistics in the mySAP CRM and
mySAP SCM solutions.
Media-specific planning functions allow you to obtain the data for logistics processing. Planning includes the following activities:
Planning for the business partner (for example, factory calendar, vacation plans for point of sale)
Product planning (media issues to be delivered for each media product, splitting the media product to form a product kit if applicable, assignment of media
products to geographical areas)
Planning of customer-product assignment in contracts
Quantity planning for each media issue and customer
Insert planning for each media issue and customer
Media-specific planning ends with the generation of sales orders based on the planning data. Each sales order contains all the required information for shipping
the planned quantity of the media issue (for example, the newspaper on a particular publication date) to the customer in question.
You can evaluate the master and transaction data in mySAP BI (Business Intelligence) and use it to control logistics processing.
The following diagram illustrates the connection between the media-specific functions and the standard functions in mySAP CRM and mySAP SCM within the
Media Product Sales and Distribution solution.
To use the functions of the Media Product Sales and Distribution solution, select the Media Product Sales and Distribution flag under General IS-M Control
Parameters in the SAP Media Customizing settings.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 7 of 36
Features
The following functions are available for processing the business transactions involved in Media Product Sales and Distribution:
Function Use
Business partner administration and planning You record customers retailers and their ship-to parties to whom you sell media
products as SAP business partners.
All the customer data required to process single copy sales is recorded in the business
partner role Retailer . You can enter the valid planning calendar, as well as suspensions
to opening times during which delivery is not to take place, in the business partner
master record.
Product planning You create the products that are to be delivered to retailers in the media product master
using the hierarchical product structure media product family , media product and
media issue .
You plan the media issues for delivery in the issue sequence of the media product. You
can generate the master records of the scheduled media issues from the issue sequence.
You can split media issues into their components for staggered shipping and group
different issues to be shipped together by creating product kits.
You can ensure that customers can only be assigned media products for which delivery
is viable by assigning media products to distribution areas (geographical media product
determination).
Assignment of media products to customers (contract processing) You map the assignments between your media products and your customers in
contracts. A contract (media contract) includes all the media products that a sold-to party
purchases from you.
Each contract item assigns a media product to the sold-to party. The ship-to party in a
contract item can differ from the sold-to party.
You can use mass processing functions to create new contract items for media
products or to reject existing contract items.
Insert planning Insert planning is used to assign inserts (ad inserts and other materials) to media
issues and their ship-to parties. You can execute insert planning as follows:
Manual insert planning
You can use the dialog function for insert planning to assign ad inserts and other
inserts manually to the contracts for each media issue. You can group the customers
(contracts) as you wish in these assignments.
Automatic insert planning (from AI orders)
If you use the Advertising Management component, you can use a function to assign ad
inserts from AI orders to the contracts automatically. The system does this using the
geographical assignment of the ad inserts in the AI orders and the customers
geographical assignments.
The results of insert planning are used by a batch function to generate issue mixes. An
issue mix covers a unique combination of inserts, and, if applicable, product kit
components, that are to be delivered together with a media issue. The batch function also
assigns the issue mixes to the contracts.
Quantity planning You can use the following options to plan quantities of media issues that are to be
delivered to customers according to their contracts:
Quantity planning for each contract item
You select the media issues in a time period and plan the corresponding delivery
quantities in the quantity plan for a contract item (customer and media product).
Quantity planning for each media issue
You can also edit the quantity plan for a selection of contracts for the same media issue.
If you carry out quantity planning externally, for example, using the planning tool SAP
APO (SAP Advanced Planner and Optimizer), you can import the planned delivery
quantities into the quantity plans in Media Product Sales and Distribution.
You can also copy subscription quantities for delivery to distribution centers from the
corresponding subscription deliveries into the quantity plans for the distribution centers.
Order generation You can use the planning data (contracts, quantity plans, insert mixes) to generate orders
using a mass processing function.
The order data is created as orders in the standard SAP Sales and Distribution solution.
The system creates an order item for each media issue, insert, or product kit component.
Functions are available for changing order quantities and deleting order items.
You can also allow your customers to place orders in the system via the Internet or
using a WAP mobile phone.
Phase delivery You can use the phase delivery functions to plan staggered delivery of media products
in different geographical regions.
You define assignments of regions, media issues and delivery dates in phase models.
You plan the delivery quantities for each phase model and media issue and create the
orders using the planning data.
Shipping and transportation You can choose between the following scenarios when processing shipping based on
orders in Media Product Sales and Distribution:
Use the standard shipping functions in the Logistics Execution System (LES):
outbound delivery, shipment etc.
Use the subscription-related shipping functions in Periodical Sales and Distribution
To do this, you copy the order data from Media Product Sales and Distribution into
shipping order items in Periodical Sales and Distribution .
Returns and subsequent deliveries You can take different operations (such as full-copy or certificated returns) into account
when entering returns and subsequent deliveries in the Service Cockpit.
Returns
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 8 of 36
You can enter advance returns or corrections (for example, quantities not created or not
delivered) as a basis for planning.
Your customers can enter returns data online using the Internet. Internet access to your
system also allows the customer to query returns recorded previously. This includes
displaying open or completed returns and displaying all returns in a past period, for
example a week ago or two weeks ago.
Subsequent deliveries
When recording subsequent deliveries, you can use different sales document types to
control whether or not the subsequent delivery is subject to charge. The data is recorded
in much the same way as data for returns processing.
Goods transfers You can use the transfer functions to enter transfer deliveries of media products that
take place directly between customers. The system creates a return delivery and a new
outbound delivery for each of these. Recording of goods transfers means that you can
check return quantities.
Billing You can use the billing functions from the standard SAP Sales and Distribution solution
to bill retailers for orders.
Special mass recording functions are available for credit memos.
Circulation auditing You can update circulation and create circulation statistics based on the quantities sold.
Programming interfaces You can use the standard programming interfaces (BAPIs) to control the following
functions:
Quantity planning for contracts (data exchange for collaborative planning)
Record return requests (with workflow link)
Recording of transfer requests
Recording of subsequent delivery requests
Edit delivery sequence (sequence of media issues to be delivered)
Shipping (export of packaging rules)


!--a11y-->
Series Sales and Distribution
Purpose
SAP Media Series Sales and Distribution is the solution for sales and distribution of series products, such as journals and looseleaf publications, from the
publisher.
Features
The following functions are available for processing business transactions in series sales and distribution of media products:
Function Use
Business partner processing You create the business partners for 1.2.3 Series Sales and Distribution in the role of
sales customer using the functions of the SAP Business Partner.
Product processing You create the products for Series Sales and Distribution (series products) in the media
product master. You define the products that can be sold as media products and the
products that can be delivered as media issues. Planning and generation of media issues
takes place in the issue sequence of the media product.
You can assign other series products to each series product in the series product
hierarchy.
You can also define series products as groupings of components, product kits.
Contract processing You map the contract data for delivering series products such as journals and looseleaf
publications to your customers in series contracts.
Shipping planning You use shipping planning to plan the sequence in which the issues are to be
delivered.
When you do this, the series characteristic assigned to each series product determines
how the subsequent issues are determined.
Insert planning Insert planning is used to assign inserts to media issues and to their ship-to parties.
You can carry out insert planning as follows:
1. Manual insert planning
You can use the dialog function for insert planning to make manual assignments of
inserts to the contracts for each media issue.
2. Automatic insert planning (from AI orders if the Advertising Management component
is active in your media company)
The results of insert planning are included in the issue mixes. See Issue Mix Creation.
Order processing You can create the corresponding orders based on the contract data and the media-specific
shipping planning data. Issue determination takes place using function and check
modules.
Shipping You use the standard shipping functions in the Logistics Execution System (LES)
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 9 of 36
(outbound delivery, transportation, etc.) to process shipping based on orders in Series
Sales and Distribution.
Billing To bill retailers for orders, you use the billing functions available in the standard SAP
Sales and Distribution solution (SD).


!--a11y-->
Contract Accounts Receivable and Payable
Purpose
The Contract Accounts Receivable and Payable component is a subledger developed for industries with a large customer base and a correspondingly high
volume of documents to post. This includes insurance companies, utilities, telecommunication, and public service companies.
Features
This component provides standard accounts receivable and accounts payable functions including posting, payments, and dunning. This component currently
consists of:
Basic Functions
Business Transactions
Integration
Closing Preparations
Information System
Job Control
European Monetary Union and Contract Accounts Receivable and Payable
Archiving
Interfaces
The Event Concept
Data Processing in Mass Runs
Enhanced Message Management


!--a11y-->
1.3 Advertising Management
!--a11y-->
1.3.1 Order
Purpose
This component is used replicate sales transactions using sales documents in the system.
You can enter inquiries, offers, orders, complaints and cancellations in a sales document.
Integration
The Master Data, Basic Functions, Contract and Settlement components are closely associated with the Order component .
Order creation requires a business partner who has been created in the media customer role in the business partner master data. The system performs address
determination automatically during sales document creation. The system ensures that the business partner address is valid for the business transaction and that
an invoice can be sent to the sold-to party once the ad or commercial has been published or aired when it determines the address data.
You have created content components and booking units in the product master data to describe and plan the advertising service. The system checks whether the
magazine or column can be published on the date specified or whether the correct numbers of ad inserts can be inserted in the newspaper on the date specified
when it creates the sales document.
Prices for advertising services in media companies are usually dependent on booking units and content components. If you have replicated prices in your
company using condition records in the Pricing component, the system determines these prices automatically for any sales documents you create or modify.
It can also assign contracts and sales agents to a sales document automatically.
The system determines whether a contract can be created for the sold-to party or advertiser in the sales document during contract determination. If a suitable
contract is found, the media customer is granted the agreed discounts or fixed quantity prices automatically.
During sales agent determination, the system identifies whether a requirement can be created in a sales agent contract for the sold-to party or booking unit
specified and assigned to the sales document. If a suitable sales agent contract is found, this sales agent can be granted the agreed commission figure
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 10 of 36
during the next settlement run.
Billing and settlement documents are created on the basis of sales documents.
Business transactions described in the Contract and Order components are distinguished as follows:
Component Use
Order Replicate business transactions in which media customers sell an undefined
number of advertising services on a spontaneous non-regular basis.
Business transactions are replicated in sales documents.
Contract Replicate business transactions in which media customers sell a defined
number of advertising services within a particular period. By defining the
amount of advertising to be sold, you can grant media customers discount
conditions that are not admissible for individual sales. Since you can control the
use of your advertising media, you can grant media customers discount
conditions in advance.
Business transactions are replicated in contracts.
Features
Any number of document items can be created in a sales document. An ad that is published on three days during the week in various local editions of a daily
newspaper with various ad specs is entered in an ad item. The associated order for creating the films is entered in a service item.
Document items in a sales document can describe the following advertising services:
Ads
Ad inserts
Distributions
Commercials
Online advertising
Services
A sales document contains all production and settlement data at various levels in the sales document that has been entered by the user or determined and
displayed by the system.
The following functions can be used to edit sales documents:
Function Use
Create sales documents Standard access, classified order entry and central access can be used to
create, change or display sales documents. The type of business transaction to
be replicated determines which access you choose.
Use standard access to create a sales document without reference to
existing sales documents for a sold-to party where the business partner
identification key is known. You can create a service order for a regular
customer in standard access.
Use classified order entry to create an ad order such as a classified
ad for an occasional customer that is accepted by telephone where the
business partner identification key is unknown.
Use central access to create a sales document with reference to
existing sales documents for a sold-to party where the business partner
identification key is unknown. You can create the ad order for a major
customer in central access by copying an existing sales document or
you can determine the order for which a customer has made a complaint.
You can then create a complaint with the associated credit memo item.
You can determine whether a sold-to party has been created as a media
customer in the master data and enter an advertising order for this business
partner. You can create the sold-to party master data or update an address that
is no longer valid.
Copy sales documents To reduce the amount of data you need to enter when you create sales
documents, you can define copying variants that are used to copy sales
documents and document items. When defining copying variants, you
determine which data in the original document is copied and whether data in the
original document is copied into a subsequent document or item in the same
sales document.
You create copying variants for orders, free items, partial and full credit memos
and those for converting offers to orders. You can specify that all data with the
exception of the publication date or ad spec is copied in copying variants used
to create orders. This accelerates the process of entering orders for ad
campaigns, public announcements or classified ads in popular columns in a
magazine.
Create complaints and cancellations You can create complaints and cancellations at the document header,
document item, schedule line and billing dataset levels in a sales document.
Sales document levels allows you to replicate complaints and cancellations
according to the business transactions in the system. If a customer makes a
complaint about an ad with a single publication date, you enter the complaint at
item level. If a customer makes a complaint about one of several publication
dates for an ad, you enter the complaint at schedule line level. If a complaint is
made for one of several publication dates, you do not need to enter a complaint
for the entire ad item.
When creating complaints and cancellations, you enter a complaint (complaint
reason, complaint date) in the first step. In the second step, you use copying
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 11 of 36
variants to create a correction item (full or partial credit memo or item or
schedule line copy).
Document flow is used to trace the development of a business transaction:
(Example: Offer Order Complaint Partial credit memo Billing
Settlement ).
Enter business partners You can assign business partners to a sales document in roles that you define.
Business partner roles defined in the Advertising Management System
include the sold-to party, advertiser, bill-to party, payer, box number recipient
and voucher copy recipient.
A business partner can only be assigned to a sales document if they have
been created in the media customer or general business partner role in the
master data. You require address data for a business partner to send letters,
invoices, ad spec masters, responses or voucher copies. You do not however
require the sales and billing data. Business partners who perform the bill-to
party or voucher copy recipient roles can be created in the general business
partner role. You require address, sales and billing data for the sold-to party,
advertiser or payer. Business partners who perform these roles must be
created in the media customer role.
The sold-to party usually performs the advertiser, payer and bill-to party roles.
The system defines these roles from the sold-to party master data when you
create a sales document item. If a different business partner performs the payer
or bill-to party roles, you should assign business partners to the sales
document item manually. If you have assigned a business partner who
performs the payer or bill-to party roles to a media customer in the master data,
the system offers you this business partner for selection automatically.
An agency performs the sold-to party, bill-to party and payer roles in an agency
order. You can change the way in which these roles are defined and assign one
or more business partners to the agency order in the advertiser role.
Create ad specs An ad spec describes the area of an ad or the airtime in a commercial to be
designed.
You can enter ad spec data at the document item, sub-item and schedule line
levels in a sales document. Sales document levels allow you to enter ad orders
in which a different ad spec is published in each local edition of a local daily
newspaper.
Assigning sub ad specs to an ad spec creates multi-page, satellite or
panorama ads. Sub ad spec linking defines the sub ad spec sequence. You
can enter different data in each sub ad spec. By doing so you can replicate a
multi-page ad in a sales document in which the ad spec on the first page is four
color and all additional ad pages are black and white.
Format proposal hierarchies that you have defined are available to you as
possible entries when entering multi-page ads. If format proposal hierarchies
are used, the system creates the sub ad specs automatically.
An ad spec that is assigned to a document item can be copied within the same
sales document or for all sales documents.
Since ad spec data can influence price, you can perform settlement for ad
specs and sub ad specs separately.
Ad spec data in ad orders is transferred to a technical system for production if
you have connected the Advertising Management System to an ad production
system.


!--a11y-->
1.3.2 Contract
Purpose
This component is used to represent sales-relevant business transactions using outline agreements in the system. Outline agreements are referred to as
contracts in the system.
Sales of the following advertising services can be managed using contracts:
Ads
Ad inserts
Distributions
Commercials
Online advertising
Services
Integration
The Master Data , Basic Functions , Order and Billing components have close associations with the Contract component .
You require a business partner who is a media customer to create a contract. You require content components and booking units to describe the advertising
services that are found in these contracts.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 12 of 36
Prices for advertising services in media organizations are usually dependent on content components and booking units. If you have represented prices and
discounts in your organization using condition records in the Pricing component, the system determines these prices and discounts automatically when it creates
sales documents, contracts, billing and settlement documents.
The system can assign orders to contracts automatically during contract determination, if billing datasets for these orders are suitable for the contracts. When
creating the final settlement, the system determines the discount conditions to be granted on the basis of the advertising services sold and calculates the
respective credit and debit memo amounts.
The following differences exist between business transactions described in the Contract component and those in the Order component:
Component Use
Order Represent business transactions in the system, in which media customers sell an
undefined number of advertising services on a spontaneous, non-regular basis.
You use sales documents to represent these business transactions.
Contract Represent business transactions in the system in which media customers sell a
predefined number of advertising services within a particular period. If you define the
amount of advertising to be sold, you can grant media customers discount conditions that
are not available for individual advertising sales. Since advertising sales are planned in
advance, you can grant media customers advance discount conditions.
You use outline agreements to represent these business transactions.
Features
The following functions for creating, changing and monitoring contracts are available to you in the Contract component:
Function Use
Create requirements The validity of advertising services in contracts is to be defined for all sales areas to
ensure that they are used consistently. Requirements are recorded as master records in
the system.
The following requirement types exist in the system:
Contract requirement
Barter deal requirement
System contract requirement
Contract requirement
Rate requirement
You create requirements to represent some of the general terms and conditions of
business in the system. These are used to define discount conditions (discount, bonus,
fixed quantity price) in contracts. Contract customers are to be granted discount conditions
on all ads that are placed in the national edition of a daily newspaper.
See also: Requirement
Create contracts Media customers who regularly sell advertising services are to be granted discount
conditions that are guaranteed in the general terms and conditions of business. Number
contracts are used to reward major customer loyalty and quantity contracts are used for
smaller customers. The following types of contract are available to you here:
Discount/bonus contracts: Discounts and bonuses are granted on a
standard price. Price is usually dependent on a price scale where discount
conditions increase proportionally to the target number to be sold. Discount
can be granted as a frequency, quantity, sales volume, or combination
discount or a discount with best conditions. Bonus can be granted as a
sales volume bonus.
Fixed quantity price contracts: A fixed quantity price is a lower price
than the standard price that is negotiated for each unit of measure. These
prices are usually dependent on a price scale where prices increase
proportionally to the target number to be sold.
The following variants and special types of standard contracts are also available to you:
Customer bonus contracts: Special contract in which discounts and
bonuses are granted in addition to discount conditions that have already
been granted from other contracts.
Media-mix contracts: Contract that links several contracts for a contract
holder using a fulfillment rule. Various discount conditions can be granted
on services that are described in the contract requirements. You can
ensure that a media customer is only granted these discount conditions if
the contract requirements are fulfilled according to the fulfillment rule.
Discount conditions in media-mix contracts can be granted to media
customers additionally or alternatively to those in other contracts (standard
or customer bonus).
Scale base contracts: Contract in which ads placed in various booking
units receive different discount but contribute to fulfillment of the target
quantity collectively. The scale base contract is a contract category that
can contain several discount scales. The condition technique in order
pricing can be used to find different discount scales, whose scale bases
contribute to achieving the contract target collectively, for different booking
units that are defined in a contract agreement. One target quantity applies
to scale base contracts. Any number of these discounts can appear in an
order pricing procedure.
Group contracts: Variant of the standard contract. Used to manage the
sale of advertising services in groups. Subsidiaries without an individual
contract are to be granted discount conditions from contracts that are held
by organizations at a higher level in the group hierarchy. Discount
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 13 of 36
conditions are to be inherited in group hierarchies and advertising services
sold by subsidiaries are to count towards contract fulfillment for
organizations at higher levels in these hierarchies.
Barter deal contracts: Variant of the standard contract. Used to manage
the mutual exchange of goods and services between organizations. Barter
deals can be managed with and without financial transactions and barter
deal contracts are used to monitor these mutual agreements.
System contracts: Variant of the standard contract. Created automatically
by the system if an advertising service sold fulfills a system contract
requirement and the media customer is a contract customer. Contract
customers are to be granted discount conditions on advertising services
sold even if no suitable contract exists for them.
See also: Contract
Define contract-relevant business partner roles You can assign business partners to a contract in the roles that have been defined in the
partner determination procedure for contracts. These usually include the following
business partner roles:
Contract holder
Agency
Beneficiary
Agency responsible
Media sales agent
Use a partner access sequence to define the business partners for which contract
assignments can be created during contract determination.
See also: Partner Access Sequence
Grant discount conditions Contract customers are to be granted discount conditions automatically when the agreed
advertising services are sold. The system determines discount conditions automatically
when you perform the following functions:
Create and change contracts
Contract determination
Create and change sales documents
Bill sales documents
Create interim and final settlements
You use condition records to record the discount conditions that all media customers
receive for an agreed minimum number of sales. You can enter scales for a condition
record.
If you specify the target number to be sold when you create a contract, the system
determines the discount conditions that are to apply. If a contract is over-fulfilled, you can
adjust these discount conditions using the scales recorded in the system. You cannot
adjust discount conditions if they have been negotiated on an individual basis.
If a contract is over-fulfilled, the media customer is granted discount conditions that apply
to larger numbers of advertising sales. The point at which the media customer is granted
more favorable discount conditions depends on the definition of discount/price
adjustment in their contract. You can grant a media customer more favorable discount
conditions during order creation or creation of an interim or final settlement.
If a standard, customer bonus and/or a media-mix contract has been created for a media
customer, they are granted discount conditions from the media-mix contract or the other
contracts during alternate discount assignment. The media customer is granted discount
conditions from the media-mix contract and other contracts during multiple discount
assignment.
See also:
Determination of Discount Conditions in Contracts
Determination of Discount Conditions in Media-Mix Contracts
Monitor contracts A series of functions are available in contract monitoring that can be used to monitor and
post-edit contracts. Contract monitoring functions include the following:
Display contract standing: You display the current standing of a contract
to check whether a media customer has sold the agreed number of
advertising services within the defined period.
Display contract assignments: You can display contract assignments
that have been created during contract determination, You can display the
billing datasets and rate indicators that have been assigned to the contract
and the advertisers who placed the orders.
Determine billing datasets: You identify the billing datasets that could not
be assigned to a contract in order to create these contract assignments
manually.
See also:
Contract Monitoring
Display Contract Standing
Display Contract Assignments
Determination of Billing Datasets
Assign contract-relevant documents You can use SAP Media Document Management to manage documents, such as
texts, graphics and multi-media objects, and to structure these hierarchically.
See also:
SAP Media Document Management


!--a11y-->
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 14 of 36
1.3.3 Billing and Settlement
Purpose
This component is used to create invoices and credit memos for debit-side business transactions and settlements for credit-side transactions. Billing and
settlement functions are available to you for the following IS-M/AM business processes:
Order processing
Contract management
Sales agent settlement
Revenue distribution integration
This component concludes the debit and credit-side business processes within IS-M/AM and creates the interface to the Accounting and Human Resources
functions.
Features
Function Use
Order billing
Combine and transfer data from the order in a billing document
Invoice printing
Cancel order billing documents
Combine and transfer billing data to Accounting
Contract settlement
Adjust discount conditions that have been granted in the order to a point in
time within the validity period as an interim settlement or to the end of the
validity period as a final settlement.
Calculate discount conditions that are granted once the validity period is
over.
Contract billing
Combine and transfer data from the contract settlement in a billing
document
Print credit or debit memo
Cancel contract billing documents
Combine and transfer billing data to Accounting
Sales agent settlement
Summary and transfer of data generated by a sales agent from the
contract data and the order in a settlement document.
Determine payments for sales agent services
Invoice printing
Cancel sales agent settlements
Summarize and transfer sales agent settlement data to accounting for
external sales agents and Human Resources for sales agents who are
internal employees.
Revenue distribution
Determine revenues for defined revenue objects
Partner publisher settlement if the revenue objects belong to a
cooperating company.
Post revenues to your own revenue objects
Posting by periods


!--a11y-->
1.3.4 Legacy Data Transfer in Advertising Management
Purpose
Data transfer functions are used to transfer data from your legacy systems to the Advertising Management System.
Features
The Advertising Management System makes a distinction between data transfer for new orders and legacy orders.
New orders
Orders that have yet to be published (service date in the future)
The system only copies those sections of open orders with a service performance date in the future. Ads that are placed till forbid are transferred
from the next feasible publication date.
Orders that have been published but not settled (service date in the past)
Orders that are technically complete but not settled are transferred completely.
Legacy orders
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 15 of 36
Orders that have already been billed in the legacy system are not transferred to the Advertising Management System. Billed orders that are required for
contract settlement are transferred as legacy orders to the Advertising Management System.
Order billing document cancellations are transferred from the legacy system with credit and debit memos without reference to the preceding document.
The following functions are available to you for data transfer to the Advertising Management System:
Function Menu path Report
Transfer new orders of the ad , ad insert and
online item types using direct input or batch input
Logistics Advertising Management Sales
Environment Data Transfer Order Data Transfer
New Orders New Ad/Ad Insert/Online Orders
RJHADU01
Transfer new orders of the commercial and
distribution item types using batch input
Logistics Advertising Management Sales
Environment Data Transfer Order Data Transfer
New Orders New Commercial/Distribution
Orders
RJHADU04
Transfer legacy orders of all item types using direct
input
Logistics Advertising Management Sales
Environment Data Transfer Order Data Transfer
Legacy Orders
RJHADU03
Orders of the service item type cannot be transferred from legacy systems.
In addition to the functions described above, the following functions can also be used during data transfer:
Function Menu path Report
Display content of sequential input file Logistics Advertising Management Sales
Environment Data Transfer Order Data Transfer
Tools Display Content of Input File
RJHADU_SHOWDATA
Check accuracy of sequential input file Logistics Advertising Management Sales
Environment Data Transfer Order Data Transfer
Tools Check Content of Input File
RJHADU_CHECKDATA
Create test input file for transferring new orders Logistics Advertising Management Sales
Environment Data Transfer Order Data Transfer
Tools Generate Test Data for New Order
RJHADU01_GENERDATA
Create test input file for transferring legacy orders Logistics Advertising Management Sales
Environment Data Transfer Order Data Transfer
Tools Generate Test Data for Legacy Order
RJHADU03_GENERDATA
More detailed information on these functions is available in the corresponding report documentation in the system.
You must create a separate sequential file for each item type.
Export structure descriptions
Data definitions in the transfer file or individual structures can be exported in the C, Cobol, PL/1, and P_RPG programming languages. Choose: Tools ABAP
Workbench Development Dictionary Utilities Table Description Generator
OSS notes
Refer to the following notes on legacy data transfer in Advertising Management :
Note Name
99261 Transfer contract credit memos from legacy system
126917 Missing data for legacy orders transferred
88507 Legacy data transfer for IS-M/AM orders (legacy orders)
164504 Collective note for hints and information on legacy data migration
326689 Order migration support tools
134875 Order migration performance: RJHADU01 / RJHADU03
Data transfer workbench
The data transfer workbench is provided to simplify administration of data transfer programs and to improve organization of data transfer from a legacy system to
the SAP System.
The following data transfer functions are available in the data transfer workbench:
Administration and organization of data transfer projects
Tools for analyzing the SAP structures required
Integration of standard data transfer programs
Registration and integration of your own data transfer and auxiliary programs
Support for various technologies used to load data into SAP Systems
The data transfer workbench is accessed in the SAP menu under Tools Data Transfer Workbench
See also
: Data Transfer Workbench
Data to be transferred is read in SAP format from a transfer file and loaded into your SAP System using one of the following techniques:
BAPI as an interface
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 16 of 36
Batch input
Direct input
See also:
Data Transfer Techniques
The following programs have been registered for the Advertising Management AdMgmtSalesOrder (order) and AdMgmtCOA (contract) business objects in the
data transfer workbench:
Program Function
RJHADU01 Create new orders of the ad , ad insert and online item types
RJHADU04 Create new orders of the commercial and distribution item types
RJHADU03 Create legacy orders of any item type
CreateFromData
BAPI for the AdMgmtSalesOrder business object
Create new and legacy orders of the ad , ad insert and online item types
RJHADU02 Create contracts
Programs that have been registered for data transfer can be displayed for each business object in the data transfer workbench under: Goto Register
Programs .
If you register the data transfer programs, the following programs for creating the corresponding test input files are also available to you in the data workbench
automatically:
Program Function
RJHADU01_GENERDATA Create test input file for transferring new orders
RJHADU03_GENERDATA Create test input file for transferring legacy orders
RJHBUSISM008_BAPI_CREATE_TEST Create test input file for transferring new and legacy orders
RJHADU02_GENERDATA Create test input file for transferring contracts
Programs for creating test input files can be executed or displayed in the system under Goto Analyze Files and Data Structures .


!--a11y-->
SAP Media Document Management
Purpose
A powerful document management system is a central component in a media system. 1.3.5 SAP Media Document Management can be used to assign
documents such as texts, graphics and multi-media objects to the Business Partner , Content Component , Booking Unit , Order , Contract and Sales Agent
Contract business objects.
This completes your comprehensive view of customers, and also offers you fast, direct access to photos, logos and icons, if you are using Classified
Advertising Management (IS-M/AMC).
Connecting document management functions enables you to assign diverse file formats to the business object documents. Users in the ads department can
record graphics files for relevant business objects, such as the order or business partner when ads are accepted. Document management functions can also be
used by employees at the publisher who are responsible for technical ad design processes and newspaper production, for instance to save a file that has been
revised for technical reasons in the document system.
Prerequisites
You have used transaction SICF to create an external alias '/default_host/sap/bc/contentserver', which contains anonymous logon data.
The service '/default_host/sap/bc/contentserver' is active.
Integration
Pre-defined interfaces provide the option of an external system accessing graphics that have been recorded for a business object. More detailed information is
available in the documentation for function modules in the ISM_DM_EXTERNAL_INTERFACE function module group.
Features
When processing business objects, the system accesses the respective document management functions.
The processing dialog consists of two parts: The Explorer is found in the left hand section of the screen in which the folder and documents for the object are
displayed. The Viewer is found on the right hand section of the screen. The content and properties of the document selected in the Explorer are displayed in the
Viewer.
The following diagram illustrates the way in which the screen is divided:

PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 17 of 36

Functions of the Explorer:
Integration with Internet documents by entering the appropriate URLs.
Import and export of documents.
Import and export of documents with blocking function.
Where-used list: You can display a list of all business objects to which a specific document is assigned.
Content search: You can search for all the documents in Document Management . This includes documents that belong to other business objects.
Entry of personal notes, and those that are generally visible at document level

Functions of the Viewer:
Document preview.
Display and change documents and their properties.
Version overview with version display and processing.

Authorization Concept
The J_DOC_MAN authorization object is used for document management. You can therefore grant users authorization to create , change and display
documents for each business object type. If a user only has display authorization for the Business Partner business object, they can view documents for the
business partner, but the processing functions are inactive. If a user does not have display authorization, the buttons used to access the dialog are also inactive or
the corresponding tab pages are not available.

Constraints
During business partner replication between SAP Media and SAP CRM , the documents assigned to the business partner are not exchanged.
External access to documents recorded in Document Management is possible using an interface provided by SAP.
Additional Information
The Knowledge Provider (KPro) is used to manage documents. This is part of the SAP Web Application Server (SAP Web AS).
Technical information on document management is available in the SAP Library under SAP R/3 and R/3 Enterprise SAP R/3 Enterprise Release 4.70
SAP R/3 Enterprise Release 47x200 SAP NetWeaver Components SAP Web Application Server Basis Services/Communication Interface (BC-
SRV) Knowledge Provider (BC-SVR-KPR).

!--a11y-->
1.3.6 Integration of Technical Systems

Purpose
The following options are available to you in Advertising Management for integrating a technical system for the production of ad or online advertising:
Integration using the technical interface IS-M/ITA
Detailed documentation on this interface is available in the Technical Interface IS-M/ITA: Integration of Technical Systems PDF document.
Integration of Technical Systems (English)
Integration of Technical Systems (German)
Integration using Business Application Programming Interfaces (BAPIs)
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 18 of 36
Media-specific BAPIs cannot be used to integrate a technical system. They can however be used to integrate a commercial system.
While IS-M/ITA is designed to communicate with a technical system, meaning that only production-relevant order data is transferred to the technical system,
BAPIs can be used to modify billing datasets for example.
The way in which a technical system can be integrated using BAPIs is described in the following scenarios using the example of ad sales.
Ad Sales With a Technical System as the Back End
Ad Sales With a Technical System as the Front End
BAPIs and IS-MITA functions can be used simultaneously in a scenario involving the sale of advertising services.
If you establish that certain tasks cannot be performed using the functions for changing an order in IS-M/ITA , you can use the AdMgmtSalesOrder.Change
BAPI whilst continuing to use the ISP_AD_DESIGN_CALL function module.
BAPIS are standardized programming interfaces and are therefore easier to implement. The structure of a BAPI (GetDetail, Change, Create, ...), parameter
documentation, description of parameters and fields in the structures have all been standardized . In contrast to IS-M/ITA , BAPIs do not have dialog functions,
such as those required to access an editor or pagination system.
Additional information on BAPIs is available in the Business Object Repository (BOR) .
If you want to design classified ads during order entry, you can integrate an ad spec editor with the Customer Interaction Center . You can incorporate the editor
from an external system or the Classified Advertising Management (IS-M/AMC) supplied by SAP.
See also: Ad Spec Editor
See also: Classified Advertising Management (IS-M/AMC)



!--a11y-->
Ad Sales With an Integrated Technical System
Purpose
This scenario uses the example of ad sales to illustrate the integration between SAP Media and a technical system. Integration of SAP Media with a technical or
additional commercial system is also possible for the sale of ad inserts, distributions, online advertising, commercials and services.
These scenarios use media-specific BAPIs and functions from the IS-M/ITA technical interface to describe integration. These technical interface functions are not
BAPI interfaces.
Documentation on this interface is available in the Technical Interface IS-M/ITA, Integration of Technical Systems document.
Prerequisites
You are already using a technical system and want to use SAP Media as a front end or back end system for the sale of advertising services. During the sale of
ads, one example of distribution between these systems is as follows:
Scenario Example Distribution
Ad Sales With a Technical System as the Back End Sale of display classified ads Ad spec design and production of orders in the technical
system, business partner, contract maintenance, order
maintenance and billing in SAP Media.
Ad Sales With a Technical System as the Front End Sale of classified ads Business partner maintenance, order maintenance and
production of orders in the technical system, check
business partner data, contract maintenance and billing in
SAP Media.
System Requirements
Technical system
SAP Media, as of Release 4.64
SAP Financials, as of Release 4.6C
The Advertising Management component is part of SAP Media and the Accounting component is part of SAP Financials .
General Technical Requirements
SAP has created the Business Framework to facilitate technical integration and commercial exchange of data both internally between SAP components and
externally between SAP and non-SAP components.
The Application Link Enabling (ALE) integration service and the Business Application Programming Interfaces (BAPIs) are central elements in the Business
Framework.
ALE means that business processes can be distributed between several systems and data consistency and availability for systems involved in these
business processes can be guaranteed. ALE provides the infrastructure used to link the systems.
Close linkage using synchronous RFC calls (BAPIs)
Loose linkage using asynchronous message exchange (IDocs)
See also: ALE Introduction and Administration
See also: ALE Programming Guide
A BAPI is an interface that is defined as a method for a business object and used to access processes and data in a business application system. A BAPI is
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 19 of 36
not dependent on access technology. Access is for instance possible using RFC, IDoc, XML, CORBA, DCOM or JAVA. Each BAPI can be accessed
independently of other BAPIs. Repeated BAPI calls do not have any negative implications.
See also: General Introduction to BAPIs (CA-BFA)
See also: BAPI User Guide (CA-BFA)
See also: BAPI Programming Guide (CA-BFA)
See also: Enhancements, Modifications ...(CA-BFA)
See also: Library of ALE Business Processes
The IDoc message type can be generated from a BAPI. An IDoc is a data container that is used for asynchronous message transfer. BAPIs and IDocs can
therefore be used to call a system synchronously or asynchronously using the same interface.
See also: IDoc Interface / Electronic Data Interchange (BC-SRV-EDI)
The range of functions for BAPIs is documented in the Business Object Repository (BOR) in the BAPI Exp l orer and the Interface Repository.
The Business Object Repository (BOR) is accessed using transaction SW03 and the Business Object Builder button. Choose the All Object Types
selection button on the dialog box that appears.
The BAPI Explorer is accessed in the SAP menu under: Tools Business Framework BAPI Explorer ( BAPI transaction .
The Interface Repository is accessed in the Internet using the following address: http://ifr.sap.com/.
Media-Specific Prerequisites
BAPIs have been developed for the following business objects in SAP Media to provide integration with a technical system .
Business partner in media organization (BUSISM007)
External business partner in media organization (BUSISM007P)
Sales document in Advertising Management (BUSISM008)
External sales document in Advertising Management (BUSISM008P)
Contract in Advertising Management (BUSISM012)
External contract in Advertising Management (BUSISM012P)
Note that you can only use BAPIs for the business partner if you are using the SAP business partner.
If SAP Media is to be accessed using the CreateFromData or Change BOR methods, you must indicate whether BAPIs or IDocs are to be used when you
implement the calling program. The following BAPIs and IDocs have been developed for the CreateFromData and Change BOR methods in SAP Media:
Business Object BAPI IDoc
Business partner (BUSISM007) ISMBusinessPartner.CreateFromData ISMBP_CREATE
ISMBusinessPartner.Change ISMBP_CHANGE
Sales document (BUSISM008) AdMgmtSalesOrder.CreateFromData ADMGMTSO_CREATE
AdMgmtSalesOrder.Change ADMGMTSO_CHANGE
If the Save BOR method is to be used to transfer data to the technical system during creation or modification of business partners, orders or contracts, SAP
Media sends IDocs. The following BAPIs and IDocs have been developed for the Save BOR method in SAP Media:
Business Object BAPI IDoc
External business partner (BUSISM007P) ISMBusinessPartnerExt.Save ISMBPEX_SAVE
External sales document (BUSISM008P) AdMgmtSalesOrderExt.Save ADMGMTSOEXT_SAVE
External contract (BUSISM012P) AdMgmtCOAExt.Save ADMGMTCODEXT_SAVE
The Save method is an outbound proxy.
An outbound proxy is used to define an interface that the SAP System can use to call another system. This method is not implemented in the SAP System. The
functions provided by the outbound proxy must be implemented in the recipient system. Data is transferred to the recipient system in the structure defined in the
outbound proxy. The recipient system must ensure that the function is executed. This can involve checking that the data transferred is entered in the
corresponding database tables. This can be achieved by implementing the interface defined in the outbound proxy.
The Save method that SAP Media uses to transfer business objects to the technical system is integrated in the update for the business object involved. You
have defined the way in which SAP Media can be called by the technical system when you implemented the calling program for the BAPI. You have also
defined situations in which a system is to be called. You do not for instance normally need to check the credit status when creating a new customer. This means
that SAP Media does not need to access the credit check function here. This is defined when you implement the calling program for the BAPI.

!--a11y-->
Ad Sales With a Technical System as the Back End
Purpose
This scenario describes integration between SAP Media and a technical system during the sale of ads, where SAP Media is used as the front end system and
the technical system is used as the back end.
Prerequisites
During the sale of display ads, orders and contracts are to be created, modified, billed and settled in SAP Media, and orders are to be produced in the technical
system.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 20 of 36
See also: Ad Sales With an Integrated Technical System
Process Flow
One example of the sale of display ads where SAP Media is integrated with a technical system as a back end is as follows:
1. A customer contacts the office where ads are accepted by telephone and places an order for a display ad.
2. The agent enters or modifies the business partner data for the customer in the Advertising Management System.
During the sale of display ads, the agent can use the Central Access and Customer Interaction Center (CIC) from the Advertising Management System to
determine, create and change the business partner data.
See also: Central Access
See also: Customer Interaction Center (CIC)
If the agent creates an order for a new customer, they must create a business partner in the media customer role. The sold-to party, advertiser and
payer roles can only be performed by a media customer. Data for the general business partner role is sufficient for sending documents such as invoices
and voucher copies.
See also: SAP Business Partner (SAP BP)
If the agent creates an order for an existing customer, they can display the business partner data for this customer to check that the address data is correct
and make any changes required.
Business partner data can be transferred to the technical system using the ISMBPEXT_SAVE IDoc. Data that is exported to the technical system can be
used to create or change a business partner in this system who corresponds to the business partner in the Advertising Management System.
See also:Documentation for the ISMBusinessPartnerExt.Save BAPI
If the business partner data has been modified, all business partner data and not just the modified data is transferred to the technical system.
Note that all business partner data is transferred to the technical system for business partner creation and modification regardless of role.
3. If the media customer is a contract customer, the agent creates a new contract or modifies an existing contract in the Advertising Management System.
Contract data can be transferred to the technical system using the ADMGMTCOAEXT_SAVE IDoc.
See also:Documentation for the AdMgmtCOAExt.Save BAPI
4. The agent enters or changes the customer order in the Advertising Management System.
Order data can be transferred to the technical system using the ADMGMTSOEXT_SAVE IDoc.
See also:Documentation for the AdMgmtSalesOrderExt.Save BAPI
Data that is exported to the technical system can be used to create or change an order in this system that corresponds to the order in the Advertising
Management System. A production order for a display ad can be created in the technical system from an Advertising Management order.
See also: Order
The documentation for the AdMgmtSalesOrderExt.Save BAPI explains which data is transferred during order creation. If the order data has been modified, all
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 21 of 36
order data and not just the modified data is transferred to the technical system.
See also:Documentation for the AdMgmtSalesOrderExt.Save BAPI
Each ad, online or commercial order in the Advertising Management System contains an ad spec.
An ad spec is a unit that describes advertising areas or times. This can include the size, length, color scheme or shape of an ad, banner or reminder.
See also: Ad Spec
The technical system can be called using the ISP_AD_DESIGN function module to design the ad spec. The function module makes all ad spec data that is
relevant to production available to the technical system. The agent returns to order entry in the Advertising Management System when they terminate
processing in the technical system. All price data must be transferred to the Advertising Management System for pricing.
Ad spec data must be transferred from the Advertising Management System to the technical system for ad spec design in this system. It cannot be created
in the technical system. However, the technical system returns any ad spec data and ad spec assignments that are modified during production due to
technical restrictions to the Advertising Management System.
See also:Documentation for the ISP_AD_DESIGN function module
Note that the technical system can only be accessed to design an ad spec during creation of an ad order.
5. The order is produced in the technical system and billed in the Advertising Management System.
The order is not usually billed in the Advertising System until it has been produced. An accounting document is created and transferred to accounting during
billing.
See also: Billing and Settlement
If price data such as the ad size, color scheme or position (booking unit, content component, page, positioning instruction) is modified during production or a
production completion confirmation is created when the order is produced, this information must be transferred to the Advertising Management System using
the AdMgmtSalesOrder.Change BAPI or the ADMGMTSO_CHANGE IDoc. This means that the order data can be updated in the Advertising
Management System and the order can be billed.
Relevant information is transferred to the technical system using the ADMGMTSOEXT_SAVE IDoc when the order is billed. You must ensure
that the order can no longer be modified in the technical system from this point.
Result
An agent has created or modified a business partner, order and contract in the Advertising Management System and designed an ad spec in the technical
system. The business partner and order data have been replicated in the technical system.
Once the order has been produced in the technical system, the actual price data can be returned to the Advertising Management System where the order can
be billed.

!--a11y-->
Ad Sales With a Technical System as the Front End
Purpose
This scenario describes integration between SAP Media and a technical system during the sale of ads, where the technical system is used as the front end
system and SAP Media is used as the back end.
Prerequisites
During the sale of classified ads, you want orders to be created, modified and produced in the technical system. Billing and settlement is to be performed in SAP
Media .
See also: Ad Sales With an Integrated Technical System
Process Flow
One example of the sale of classified ads where SAP Media is integrated with a technical system as a front end is as follows:
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 22 of 36
1. A customer visits a sales office or contacts the office where ads are accepted by telephone and places an order for a classified ad.
2. The agent enters or modifies the business partner data for the customer in the technical system.
If the agent creates an order for a new customer, they must create a business partner in the technical system. This business partner is used to create a
business partner in the media customer role in the Advertising Management System.
A business partner can be created in the general business partner , media customer or media sales agent roles in the Advertising Management
System. The media sales agent role is a credit-side role. Data for the general business partner role is sufficient for sending documents such as invoices
and voucher copies. However, a business partner in the media customer role is required to create ad orders. The sold-to party, advertiser and payer roles
can only be performed by a media customer.
See also: SAP Business Partner (SAP BP)
If the agent creates an order for an existing customer, they can display the business partner data in the technical system and change existing data such as
the address as required.
An agent can display information on existing customers that is not available in the technical system in the Customer Interaction Center in Advertising
Management. The ISM_CIC_BP_SEARCH BAdI is available for communication with the Customer Interaction Center.
a. The credit status of the payer can be checked during order entry in the Advertising Management System. Credit data that has been created for the
customer in the Accounting component is accessed during this check.
See also: Credit Management
The DebtorCreditAccount.GetStatus BAPI is used to access Accounting and check the business partner credit status. Any open items or the
business partner dunning level are checked here. Various export parameters can be used to return the credit status to the technical system as an A/R
summary. You have defined the way in which A/R summaries can be displayed and how the agent can respond to them when you implemented the
calling program for the BAPI.
The GetStatus B API is used to perform the credit check in this scenario. However, any other BAPIs that have been created in the
DebtorCreditAccount) business object for the credit check, such as the GetDetail BAPI can also be used. You decide which BAPI is to be used for
the credit check in the project. You must choose between improved performance or more current data when choosing between the GetStatus and
GetDetail BAPI.
See also: Documentation for the DebtorCreditAccount.GetStatus and DebtorCreditAccount.GetDetail BAPIs.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 23 of 36
b. If the credit status is admissible, the ISM_BAPI_007_ADDRESS_CHECK function module can be used to check the business partner address in the
Advertising Management System. During this address check, the system adds any data that the agent has entered. This can include adding the postal
code to the city entered. The system also checks whether the business partner address matches the postal structures. It uses the main business
partner address to be checked and a date from which the address is valid.
The Advertising Management System returns a list of error messages such as P.O.box does not match postal code to the technical system in the
Return parameter. You have defined the way in which error messages can be displayed and how the agent can respond to them when you
implemented the calling program for the function module. You can for instance stipulate that error messages are to be displayed in a dialog box.
See also:Documentation for the ISM_BAPI_007_ADDRESS_CHECK function module
c. Following the address check, the ISMBusinessPartner.GetDuplicates BAPI can be used to access the Advertising Management System and perform
a duplicate check for the business partner master record created.
Business partner master records where the addresses or telephone numbers do not match are defined as duplicates. The duplicate check uses the
main business partner address that is valid on the day that the check is performed.
The Advertising Management System returns a list of any duplicates identified to the technical system in the PartnerList parameter. You have defined
the way in which business partner duplicates can be displayed and how the agent can respond to them when you implemented the calling program for
the BAPI.
See also:Documentation for the ISMBusinessPartner.GetDuplicates BAPI
d. If the address matches the postal structures and no duplicates exist, the ISMBusinessPartner.CreateFromData BAPI or the ISMBP_CREATE IDoc
can be used to create a business partner or the I SMBusinessPartner.Change BAPI or the ISMBP_CHANGE IDoc can be used to change a business
partner in the Advertising Management System.
See also:Documentation for the ISMBusinessPartner.CreateFromData and ISMBusinessPartner.Change BAPIs
Most business partner data from the Advertising Management System is not usually known to the technical system. It is therefore possible to create a
business partner using a reference business partner ( Partnertemplate parameter) in the Advertising Management System. All data that is required to
create a business partner in the Advertising Management System but cannot be transferred in the ISMBusinessPartner.CreateFromData BAPI or the
ISMBP_CREATE IDoc, is transferred from the reference business partner This can include sales data that is not required to create a business partner
in the technical system. X-structures can be used in Advertising Management to define which data is determined by the caller and which data is
copied from the reference business partner.
Use the ISMBusinessPartner.CreateFromData BAPI or the ISMBP_CREATE IDoc if the business partner is to be created in an additional role
and/or in an additional sales area.
Since the business partner must exist in both systems, the business partner number must be unique in both systems. Two options are available
for assigning a unique business partner number:
If you intend to use identical business partner numbers, create two number ranges in Advertising Management : An external number range for
the business partner who was created in the technical system and an internal number range for the business partner created in the Advertising
Management System. Advantage of using identical business partner numbers: Your agents are working with a single business partner number
in both systems. You should note however, that identical business partner numbers can cause problems if various business partners with
identical numbers are created in both systems.
If you are using different business partner numbers, you can create a reference between the two business partners in Advertising Management.
Use the External partner number and Data origin fields that are found on the Control tab page in the business partner master record for the
SAP business partner.
3. The contract for the media customer can be transferred to the technical system using the ADMGMTCOAEXT_SAVE IDoc.
See also:Documentation for the AdMgmtCOAExt.Save BAPI
A contract in Advertising Management has a limited validity period and is used to grant advance discount on advertising services that are sold on a regular
basis. . It is negotiated between a sales area in your organization and a media customer.
See also: Contract
Since contracts are created and changed in the Advertising Management System, all contract information must be transferred to the technical system.
Contracts can be used for contract determination and discount conditions from contracts can be used for pricing in the technical system.
See also: Contract Determination
If a discount condition from an Advertising Management contract is used in an order in the technical system, the technical system must return the contract
number to the Advertising Management System as a contract assignment for the order.
Contracts are not usually relevant during the sale of classified ads. This step has been included in the scenario to show that contracts can be
maintained in Advertising Management to assign discount to advertising services.
Contracts are usually processed as orders by other agents. During the sale of advertising services, contract maintenance should not be performed
at the time selected in this scenario. Since the ADMGMTCOAEXT _SAVE IDoc is always called if a contract is created or changed in
Advertising Management , contract maintenance can also take place at a much earlier stage, independently of order entry.
4. Order data can be transferred to the Advertising Management system using the AdMgmtSalesOrder.CreateFromData BAPI or the
ADMGMTSO_CREATE IDoc when the agent creates an order. The BAPI documentation explains which data is to be transferred to the Advertising
Management System.
See also:Documentation for the AdMgmtSalesOrder.CreateFromData BAPI
Modified order data can be transferred to Advertising Management using the AdMgmtSalesOrder.Change BAPI or the ADMGMTSO_CHANGE IDoc
when the agent changes an order.
See also:Documentation for the AdMgmtSalesOrder.Change BAPI
Orders for classified ads can also be modified in the Advertising Management System. We recommend only making changes in one system to
ensure that the data is consistent. Orders for classified ads should for instance only be modified in the technical system.
The order origin indicator that can contain the from technical system , not modifiable values is available to you in Advertising Management to
ensure that the data is consistent. If the technical system transfers the indicator with the corresponding value, you can ensure that the order is not
modified during dialog processing in the Advertising Management System.
During order processing, each process step that changes the status of the order, such as canceling an order or creating a production completion confirmation,
must always be returned to the other system. If an order status is reached in Advertising Management that does not permit any further order changes in the
technical system, you must ensure that the order can no longer be modified in the technical system from this point. This is for instance the case if the order
has been billed in Advertising Management.
5. The order is produced in the technical system.
The order is not usually billed in the Advertising System until it has been produced. An accounting document is created and transferred to accounting during
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 24 of 36
billing.
See also: Billing and Settlement
If price data such as the ad size, color scheme or position (booking unit, content component, page, positioning instruction) is modified during production or a
production completion confirmation is created when the order is produced, this information must be transferred to the Advertising Management System using
the AdMgmtSalesOrder.Change BAPI or the ADMGMTSO_CHANGE IDoc. This means that the order data can be updated in the Advertising
Management System and the order can be billed.
Relevant information is transferred to the technical system using the ADMGMTSOEXT_SAVE IDoc when the order is billed. You must ensure
that the order can no longer be modified in the technical system from this point.
Result
An agent in your organization has created or modified a business partner and an order in the technical system. The business partner and order data have been
replicated in Advertising Management once the system has checked the credit status, address consistency and duplicates for the business partner.
The contract is processed and the order is billed and settled in Advertising Management.

PDF Content
This page content is in PDF format.
Download
PDF Content
This page content is in PDF format.
Download
!--a11y-->
Classified Advertising Management

!--a11y-->
Classified Advertising Management (IS-M/AMC)
Purpose
You use this component to design ad content.
Ad content involves ad text that is entered, formatted and designed in IS-M/AMC UI according to the type of classified ad, for instance by inserting borders and
graphics.
Implementation Considerations
The functions in this component are based on the requirements of classified advertising order entry. This involves fast entry and design of classified ads that are
accepted by telephone, and not complex design of large format product or image ads.
Integration
IS-M/AMC includes IS-M/AMC User Interface (UI) and IS-M/AMC Server. IS-M/AMC UI and IS-M/AMC Server communicate using Remote Function Calls
(RFC).
You cannot enter ad content independently of an ad order.
You require Advertising Management (IS-M/AM) for order entry. You can incorporate IS-M/AMC UI in the Customer Interaction Center (CIC) framework in IS-
M/AM . This integration means you can access IS-M/AMC UI from IS-M/AM , and design the ad content during order entry.
See also: Customer Interaction Center (CIC)
When you access and exit IS-M/AMC UI , the system transfers production and price-relevant data to IS-M/AMC UI or IS-M/AM via the Interface for Integration
of Technical Systems (IS-M/ITA) .
See also: Integration of Technical Systems
SAP R/3 Document Management is integrated in IS-M/AM and IS-M/AMC UI.
You can assign graphics to various business object types in IS-M/AM . During insertion of graphics in ad content in IS-M/AMC UI , you are offered graphics for
selection, which have been released in SAP Media Document Management, and have been assigned to the booking unit, content component, business
partner, sales document header, sales document item , or ad spec business object types.
See also: SAP Media Document Management
When the ad order is saved, the system saves the ad order in IS-M/AM, and the ad content designed in IS-M/AMC Server with the graphics inserted. The ad
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 25 of 36
production system can retrieve the ad content from here.
Additional information on the integration of IS-M/AMC with other application components is available in the Master Guide for SAP for Media.
Features
IS-M/AMC UI is an editor, which provides you with two options for entering ad content:
You enter and design the ad text directly in the editor in the editor mode. You can format characters, paragraphs and text blocks here, and insert borders and
graphics in the ad text. The style that you use defines which options are available to you to design the ad text. The style also defines the structure of the ad
content, such as the number of columns and position of the header or graphics, in addition to controlling these design options.
See also: Working in the Editor Mode
You can instruct IS-M/AMC UI to generate the ad content using a template in the template mode. A template is pre-defined ad content, with ad text that
contains placeholders. Enter ad content attributes on a panel to generate the ad content. Ad content attributes are characteristics that describe the semantic
aspects of the classified ad content. You can for example enter the brand , model and color ad content attributes for a car ad. The system inserts the ad
content attributes in the relevant gaps in the template when it generates the ad content. You can post-edit the pre-defined classified ad in the editor mode.
See also: Working in the Template Mode
You make Customizing settings for IS-M/AMC UI in IS-M/AMC Server . This includes creating panel groups, templates and styles.
When you exit IS-M/AMC UI , IS-M/AMC Server checks that the ad content conforms to company-specific content and design requirements, and can be
produced. It checks the ad content validation rules to do so.
See also: Validate Ad Content
When the ad order is saved, the system saves the ad order in IS-M/AM, and the ad content in IS-M/AMC Server . The entry context, ad content attributes,
print and preview formats, ad content versions, and violations against ad content validation rules are saved with the ad content.
See also: Save Ad Content
When you save the ad order, IS-M/AMC UI generates the native editor format, and the EPS print format and the TIFF, JPG and PNG preview formats from
the native editor format.
See also: Generate Print and Preview Formats
If you modify ad content that has been saved, the system saves a new version of the ad content in IS-M/AMC Server when you save the ad order. This version
is the active version.
See also: Modify Ad Content

!--a11y-->
Customer Interaction Center (CIC)


!--a11y-->
1.5.1 Customer Interaction Center (CIC)
Purpose
The Customer Interaction Center (CIC) is a working interface for call center agents who have direct contact with customers.
Components that are provided by SAP can be added to this interface meaning that it can be adjusted to meet the requirements of a company and the individual
business areas and employees within this company.
The CIC can be connected to external telephone systems and used as a call center. Callers can be identified by their telephone number (Automatic Number
Identification). Corresponding call center functions, such as logging on to and off from queues, accepting, forwarding, and terminating contacts can be made
available to call center agents using application toolbars or function keys (quick keys). The call status of a customer can also be displayed with the number that
the customer has dialed (Dialed Number Identification Service). Comprehensive call logging is also supported.
Various information views for a customer can be displayed simultaneously in the CIC . This information can be used as the basis for entering advertising and
subscription orders in the CIC , and creating and changing business partner master data, contacts and complaints.
Access to the Internet, marketplaces and B2B scenarios is possible in addition to the facility to receive emails and fax documents.
Implementation Considerations
The CIC in SAP Media is the CIC from SAP R/3 Customer Service , to which media-specific components have been added. You should therefore make
Customizing settings for the CIC in two locations in the Implementation Guide.
Customer Service Customer Interaction Center (CIC) [...]
SAP Media Customer Interaction Center (CIC) [...]
A description of the media-specific components is available in this documentation. The description of the CIC in SAP R/3 Customer Service is available in the
SAP Library under SAP R/3 Enterprise Application Components Logistics Customer Service Customer Interaction Customer Interaction
CenterYou must create number range intervals for the following objects if you want to use the CIC :
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 26 of 36
Object Range
CCMCALLBCK (Call Management: Call-Back-ID) 01
CCMIOCNR (Logging: Information object instance) 01
CCMIOCNR (Logging: Detailed information) 01
CCMSESSION (Logging: Logging session) 01
Integration
The CIC can be used with and without telephony integration.
See also: Telephony Integration
The ad spec editor from an external system or the Classified Advertising Order Management editor provided by SAP can be incorporated in the CIC for the
sale of display classified ads.
See also: Ad Spec Editor
See also: Classified Advertising Management (IS-M/AMC)
The reference clients in SAP Media contain the FW_STD_03 (17 inches) , FW_STD_04 (21 inches) FW_STD_AMC (17 inches with
docking control for editor) framework IDs for a CIC with telephony integration and the FW_STD_05 (17 inches) , FW_STD_06 (21 inches) and
FW_STD_AMC21 (17 inches with docking control for editor) framework IDs for a CIC without telephony integration.
Features
The structure of the CIC is similar to a building block system, whose central elements include a framework, components, component profiles and CIC profiles.
See also: Framework
See also: Component
See also: CIC Profile
The functionality of the CIC is defined by the components that are assigned to the framework.


!--a11y-->
1.6 Title Lifecycle Management
The overall life cycle of a media title comprises a sequence of highly integrated processes. This means that integrated title management requires that all the data
be accessible without gaps in the system. Title Lifecycle Management integrates the mySAP business suite with a range of media-specific enhancements to
meet these requirements in a powerful end-to-end tool.


!--a11y-->
Product Development in the Media Industry
Definition
mySAP Media Product Lifecycle Management (PLM) is a business solution for planning and cost monitoring of product developments in the media and
entertainments industries. mySAP Media PLM supports processes for planning and developing new titles, including task and deadline planning and control, and
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 27 of 36
entertainments industries. mySAP Media PLM supports processes for planning and developing new titles, including task and deadline planning and control, and
profitability planning and analysis.
Integration
This means the mySAP Media PLM application is designed for project teams and project managers in editorial offices. However, it is also the core process in the
integrated Title Management solution, which covers all the processes required in a media company by uniting mySAP ERP, mySAP Customer Relationship
Management (marketing, product sales, and customer interaction), mySAP Media Product Sales (Sales and Distribution), mySAP Supply Chain Management
(production and warehouse management), and mySAP Media Intellectual Property Management (rights and royalties).
mySAP Media PLM maps the business process of product development using a selection of functions from the mySAP business suite. Industry-specific
functional enhancements have been developed in various components for mySAP Media PLM. Industry-specific enhancements in the components SAP CO,
SAP IM, SAP PS, and SAP MM are delivered with the SAP Media releases.
The following application description is based on the process flow as supported by the SAP R/3 Enterprise components with the SAP Media add-on. Additional
components are recommended for certain processes in media product development; for example, SAP CRM-IPM for rights acquisition and contract management
or the cProject Suite for interdepartmental collaboration and project management in media product development. The functions in these additional components are
not described in this documentation.
Process Overview
The life cycle of a media production can be subdivided into a number of phases.
The process model in mySAP Media PLM begins with a production proposal in a development phase. Production proposals are managed in the system with
corresponding master data and the characteristics of what is to become the product. At this stage, it is irrelevant whether the proposal is implemented later as a
customer development (investment) or with reference to an actual order from a sold-to party.
A production proposal is developed from the production proposal in the early planning phase. You can plan several alternative scenarios for a production
proposal. A set of production characteristics is defined and basic dates are planned for each scenario.
A parameter-controlled preliminary costing based on the production characteristics and basic dates is used to perform a feasibility analysis and a preinvestment
analysis for one or more alternative scenarios. When doing this, all the phases in the life cycle must be taken into account; for example, this cost estimate is used
to perform a full cost and revenue estimate for the entire life cycle for an investment proposal. Various departments in a company collaborate on this valuation of
the production proposal.
The plan values of the production proposal are available for higher level planning methods from a defined status. Basic data for annual budget planning, cash flow
planning and so on can then be determined dynamically from the plan values for the individual production proposals that are valid on the planning date.
Implementation of production proposals can be influenced by releasing budgets and budget availability dates.
Once a decision on implementation can be made for a scenario, the scenario is registered for a documented and standardized approval procedure. System
workflows can be used to coordinate the involvement of several release points, so that the user can obtain a clear picture of the current status and the next steps
at any point.
Rejected scenarios are retained in the system for evaluation or for use as templates for later proposals. Approved scenarios are transferred with all the planning
data to projects and thus enter the implementation phase, which involves detailed production planning and monitoring of actual costs. When implementation
takes place, the overall view of the life cycle in the proposal phase can result in a number of projects involving several products, divided according to
organizational and time-related criteria.
Structuring requirements for a project can differ greatly, so that we recommend that you use an appropriately widely scaled range of methods.
If project management focuses principally on cost controlling without any further requirements from resource and flow planning, purchasing processes and internal
service requests can be triggered directly based on the initial standard cost estimate. The standard cost estimate can be modified to take account of planning
findings updated and refined as often as required during the course of the project.
Planned-planned and planned-actual comparisons allow you to check deviations at all times. In the case of planned-planned comparisons, you can conserve
planning statuses for certain milestones in the progress of the project at precisely the level of detail you require. If the planning values at WBS element level are
sufficient, you can do this by copying the planning values to another plan version. However, if you want to conserve all the planning data with the maximum
amount of detail possible for the standard cost estimate, in other words, the entire profit and loss projection, you can transfer this data to a simulation version of the
project at the appropriate time.
If emphasis is placed on project management for complex processes, you use methods that streamline the process flow and resource load, to determine the
progress of the project and to identify deviations from the original plan at an early stage.
The current status of planned, actual and commitment values for production is also available for higher level planning methods during the implementation phase.
Integration with the actual procurement processes (mySAP SCM Supply Chain Management) is supported by a function allowing you to create materials (media
product masters and their BOM components) with reference to the production proposal or project. When you do this, you can copy the production characteristics
defined in the standard cost estimate into the material classification. You can also transfer documents assigned to the production proposal or project (for example,
production templates, template layouts) and business partner assignments (author, editor) to the media product master. This means this planning data is also
available in the procurement process.
Specifications for procurement processes themselves are made according to the individual procurement strategies.
Production in the media and entertainment industry is followed (often with an overlap) by a long-term exploitation phase or revenue phase, which often lasts
several years. Sales of various products, rights and licenses for the productions takes place during this phase. Subsequent productions of varying extents still
take place.
The master data on the products is recorded during this phase in the media product master, a media-specific enhancement of the SAP MM material master,
which supports product hierarchies and additional media-specific attributes. This master data can also be copied into sales documents.
The long exploitation phases make high demands of profitability evaluation and require a special concept for life cycle controlling.
Specific requirements for managing rights, licenses and royalty entitlements are particularly important during the exploitation phase and special sales and
distribution and settlement problems must be taken into account. These issues are addressed by other SAP Media solutions and are not part of the solution
mySAP Media PLM.
Phase 1: Product Idea, Production Proposal
The first phase in the life cycle of a media production is normally termed the idea, planning or development phase. This phase is represented in mySAP Media
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 28 of 36
PLM by the appropriation request.
During this phase, the initial product idea is developed into a description of a production proposal, which covers the entire planned life cycle of the production and
its economic exploitation and is used as an informative basis for decision-making when approving the production proposal.
Master Data
The master data relevant to this phase is recorded for the appropriation request. You can extend the standard master data. A set of user-defined master data
fields is provided with the standard delivery as an initial simple extension option.
You should make a very precise distinction between master data on the production proposal and the specifications for actual production or on the
product itself. For example, the organizational assignment of a production can change during its life cycle but the production remains the same.
For this reason, the organizational assignment is recorded in the master data of the objects that characterize the phases (appropriation request,
WBS element, media product master). On the other hand, the product specification is managed in the cross-application SAP classification
system and is therefore available to other applications; for example, you can copy the provisional product specification to the material
classification later when creating the media product master.
Partner Assignment
You can assign the production proposal business partners in the relevant roles.
A partner determination procedure is defined in the Customizing settings for the appropriation request type; the determination procedure contains all the partner
functions that are allowed for the appropriation request type.
The SAP Business Partner allows you to use the same partner master record in a wide variety of roles in the various applications. The roles
relevant for production proposals are defined in Customizing. The standard delivery contains one master role. Partners you assign in the production
proposal in SAP Business Partner roles can later be copied automatically to the partner assignments set up when creating the media product
master and the production project.
It is not possible to create new business partners directly from the appropriation request, but only business partner assignments. The business
partner must have been created before hand in the role in question.
Besides the business partner, you also assign the internal participants to the production proposal, in particular persons or offices involved in the approval
workflow.
Variants: alternative planning scenarios
You can plan each production proposal in several alternate scenarios. Examples of alternative scenarios include make or buy scenarios, alternative marketing
strategies, alternative product design or alternative basic dates. An appropriation request variant is created for each scenario; you can perform a preinvestment
prognosis for each of these scenarios.
You can assign plan versions to the variants. This means the (costed) plan values in the alternative scenarios are also available for higher level planning
methods in the plan version in question.
Preinvestment Valuation
Estimated Plan Values
In an initial rough estimate, you can enter the scale of the expected costs and revenue manually.
Costed Plan Values
Once sufficient details are available on the specifications for the production, the plan values are determined more precisely by a cost estimate (Easy Cost
Planning). Once a cost estimate has been created, the values calculated for costs and revenue are copied to the plan values, where they can no longer be
overwritten manually. The plan values are updated each time the cost estimate changes.
You can only create one cost estimate for each variant. There cannot be more than one cost estimate variant per variant. However, a variant can
be copied with its cost estimate to a new variant and can be planned there using a changed version of the cost estimate.
Easy Cost Planning
Easy Cost Planning is a method of creating cost estimates that have a hierarchical structure. The costing structure already has the basic features of the later
structure of the production in the subsequent phases.
You can use Easy Cost Planning in the SAP Media System to calculate costs and revenue and update them in the plan according to cost elements. This means
you can use Easy Cost Planning to carry out a preinvestment prognosis along the lines of a profit and loss statement. A user exit allows you to define company-
specific preinvestment indicators (Key Performance Indicators) and the methods for calculating them. You can then determine and list these indicators in the cost
estimate.
The SAP Media System contains various methods for time distribution of individual cost items. For example, you can record complex distribution keys and edit
them manually. This allows you to plan characteristic sales time curves or royalty payments for exact periods.
When determining costs for internal or external services and material usage, Easy Cost Planning determines the rates and prices from the master data on cost
center planning, purchasing and materials management recorded in the system. Time distribution is taken into account for exact periods.
Easy Cost Planning can take place with or without planning forms.
Profit and Loss Projection with Easy Cost Planning
In the SAP Media System, you can read the values of items at lower levels within a costing structure, group them and use them in formulas. This is done using
the aggregated item. This allows you to display evaluations and summarizations of lower levels in higher levels of a standard cost estimate. For example, you can
display profit and loss projections for the individual contribution margin levels. Changes to costing characteristics, such as production characteristics, royalty
conditions and other parameters, take effect immediately in the profit and loss projection and enable iterative cost planning based on certain key business figures.
You can further simplify this process by calculating limit values for certain parameters based on the costs and revenue already estimated in Easy Cost Planning;
these values must not be undershot or exceeded if specified target values are to be reached for business key figures Typical examples in publishing are supply
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 29 of 36
circulation, minimum prices and maximum royalty rates.
Easy Cost Planning with a Planning Form
Easy Cost Planning with planning forms allows you to perform costing controlled by parameters with the user answering a number of questions or entering
production characteristics, which are then evaluated by a costing model and translated to a cost estimate. The system calculates the required quantities of
materials and services from the data entered by the user and determines the prices and rates that apply on the valuation date from the corresponding master data.
The user does not need detailed knowledge of prices, services and process flows in order to perform costing for the production. The costing result is displayed as
a tree in accordance with the costing structure.
The data entry screen for recording characteristics is generated as a freely designable HTML page, which you can enhance by adding any utilities you wish to
include for the user. The screen is intuitive and can, for example, be used in the Web portal to allow external partners to enter specifications on production
proposals or licensing offers, which are then valuated by the system using the costing models defined.
The characteristics (production characteristics) entered here can be copied automatically to the material classification when generating a media
product master from an appropriation request later on.
A planning form (costing model) comprises a collection of questions or characteristics that must be specified for costing, a customer-specific data entry screen
that can contain additional utilities for use in answering the questions or specifying the characteristics, and the costing template, in which the derivation rules and
calculation formulas for costing are stored. Costing templates represent production standards and ensure that preliminary costing is complete and repeatable.
You can use as many costing models as you wish. You do not need programming experience to maintain costing models and templates.
See also:
Using Easy Cost Planning
Example of Multilevel Easy Cost Planning
Easy Cost Planning without a Planning Form
Users who have the appropriate authorization can also perform costing without a costing model or manually enhance a cost estimate created using a costing
model. To do this, the cost estimate is opened in the individual item view.
You can only assign complex distribution keys and edit time distribution in the individual item view and not via the costing structure.
Approval: Status Administration and Workflow
The degree of development and valuation status of an appropriation request and its variants are described by means of a status concept. Status events are
important stages in the life cycle of a production proposal. Triggering status events is subject to authorization. Status events for a production proposal serve as
prerequisites to important functions, for example whether or not an appropriation request can be replaced by a measure, whether plan values can be used in
higher level planning methods or whether or not planning can be changed for the appropriation request.
In the standard delivery, a status event triggers a sample workflow, which organizes the agreement of certain authorities or persons for the implementation of a
measure variant and informs other persons or authorities of the status of the measure. The result (acceptance, rejection, postponement) of this workflow also
triggers a corresponding status event.
You can design the status concept and the workflow in Customizing for each appropriation request type according to your requirements.
You can copy the standard workflow as a template for similar processes in other status events and modify the copy.
Higher Level Planning Methods
An appropriation request is assigned to an item in an investment program. If an appropriate status event occurs for the appropriation request, the plan values
for the next dynamic selection are used to determine the planning basis for the investment program.
The overall plan can now be approved for the period in question on the level of the investment program and budget strategies can be used to influence
planning and implementation of the individual productions.
Transfer to the Implementation Phase
If an appropriate status event occurs, the production proposal can be transferred to the implementation phase. In the model process in mySAP Media PLM, this
step is reached by creating one or more projects in SAP PS.
During the transfer, the system transfers certain master data, partner assignments and the plan values or cost estimate to the top WBS for the projects created.
Basic features of the project are determined from the Customizing settings for the appropriation request type.
In the SAP Media System, you can access existing work breakdown structures from standard projects or operative projects as a template for transfer.
While the entire life cycle was the object of planning for the appropriation request, the implementation phase can be distributed among several projects that all
develop from the same original appropriation request. Since the costing structure for the appropriation request variant mirrored this structure in the subsequent
phases, the appropriate costing substructure can be passed on for each project during transfer.
Phase 2: Implementation in the Project
The SAP Project System provides a scaleable instrument for the implementation phase that can be modified to meet a wide range of requirements. The best
possible structure must be determined and the most suitable methods chosen for each category of productions (see Project System (PS))
Experience has shown that the huge number of methods available with the SAP Project System leads to users creating process models in the
business blueprint that are overloaded with methods in comparison to the actual requirements of the project. Please try to streamline your
processes and make use of the scaling options in the system.
Cost Controlling
Cost controlling must be the smallest common denominator of all project management requirements in the media and entertainment industry. The SAP Project
System provides a wide range of planning methods for this purpose.
According to the SAP Media process model, overall costing (Easy Cost Planning) in the form of a profit and loss statement is performed during the development
phase before implementation begins. During the transfer to the implementation measure project, this overall costing or only part of the costing structure is
transferred to the top WBS element of the project.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 30 of 36
If emphasis in project management is placed on cost controlling, the subsequent detailed planning phase with Easy Cost Planning in the project distributes the
costing structures transferred from the top WBS element among the corresponding lower level WBS elements and refines them there if applicable. The costing
structure also records the project structure but you can subdivide it further without having to add more detail to the project structure.
Sales Pricing
If you execute your projects in the order or as co-productions, you can transfer cost planning directly from Easy Cost Planning to sales pricing as the sales
price basis, for example to create a customer quotation costing or to bill your sold-to party or production partner for your services according to performance.
Execution Services
Execution Services allow you to trigger the following costed processes directly from the costing structure in Easy Cost Planning:
Purchase request
Purchase orders
Material reservation
Goods issue
Internal activity allocation
The costed quantities and prices are used as default values but you can overwrite them. This saves you entering data again in continued processing.
Scheduling: Networks:
If you need to perform scheduling and resource planning for more complex projects, implement networks at the most detailed planning stage. Automatic parallel
network costing then represents the most up to date planning status of the corresponding processes and replaces costing in Easy Cost Planning. The values
determined in Easy Cost Planning for the project structure can be retained in a different plan version or in a project simulation for variance analyses. However,
the two planning forms in the work breakdown structure can not only be used alternatively (in phases) but also additively, for example you can use Easy Cost
Planning and Execution Services for certain part tasks and then use the network technique for critical processes. This allows you to streamline planning and
administrative work for your projects according to detailed criteria.
Scheduling
The network technique provides you with efficient scheduling functions for your processes. A variety of date types and scheduling strategies allow you to
perform scheduling exactly to match your requirements.
Capacity Requirements Planning
Capacity planning allows you to identify resource requirements at an early stage for processes planned and scheduled in the network, to schedule or change
the available capacities and to respond flexibly to changed conditions at all times. Capacity planning is based on work centers with defined capacity categories
and available capacity.
Confirmation
Actual data is recorded to document the exact processing status of activities and activity elements in the network and allow you to perform progress analyses
and forecasts of further cost development. A variety of options for recording confirmations with or without direct access to the SAP System covers a wide
range of requirements. You can use cross-application time sheets to record confirmations for several SAP components.
Progress Analysis
You can use the progress analysis to compare planned and actual progress of the project with the actual performance (confirmed), so as to determine date and
cost variances in good time. The milestone trend analysis provides you with an overview of the dates in a project.
Claim Management
You can use Claim Management to document variances from planned costs and dates, their causes, those responsible etc. You can list the costs incurred by
the variance in a special cost estimate for the claim. Integrated status management and workflow functions support performance of unplanned tasks necessitated
by the claim.
Budget Management
Budget management, budget release strategies and the availability control represent further methods of monitoring and influencing the actual costs of the
project.
Project Information System
The Project Information System provides you with a number of evaluations for structures, dates, planned and actual costs, commitments and capacities. All
persons involved in the project are provided with exactly the information they require and are authorized to receive. You can use project versions to record the state
of a project at a certain point in time and include it in the evaluations.
Results Analysis/Project Settlement
The results analysis performs periodical evaluations for determining provisions, cost of sales and the amount of work in process for Financial Accounting and
Profitability Analysis. Project settlement transfers costs or revenue to Financial Accounting, Asset Accounting, Profitability Analysis and Controlling.
Collaborative Engineering & Project Management
The purpose of CEP is to facilitate the exchange of information and knowledge between the person responsible for a project in your company, referred to as the
owner, and external partners, referred to as participants, who are all involved in a common project, for instance developing ad booking details in a publishing
company. CEP allows you to send folders of documents of all kinds that are relevant for this task to chosen participants for further processing using the Internet.
The changed documents and comments are returned to you for evaluation and if desired, transfer back to the SAP System.
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 31 of 36
Phase 3: Exploitation
When production is finished, the process of media product development is complete. The subsequent processes for content exploitation and product sales are
supported by other SAP Media solutions. The SAP Media media product master is a material master specially enhanced for the media industry and forms the link
between mySAP Media PLM, Sales and Distribution, and planning of products in Materials Management.
Life Cycle Controlling
You should not collect actual sales figures in Project System for product cycles involving product sales phases of several years and high volumes of sales
transactions, such as are typical for the media industry. We recommend instead that you settle the projects after production is finished and then gather the actual
sales figures in CO PA, from where they can be retrieved for further evaluations. The SAP Business Information Warehouse is ideal for grouping all planned and
actual data over a life cycle of several years. The Business Information Warehouse is an independent application environment that draws information from both
internal and external sources in order to run speedy and informative reports and evaluations.
SAP Business Information Warehouse allows you to record, combine, summarize and select data from the Controlling components (CO PA, actual sales figures)
for projects (planned costs, planned revenue, actual costs) in Asset Accounting and Investment Management, over long periods of time if required, and to make
the results available and easily accessible at all times in the form of queries, evaluations and analyses.


!--a11y-->
Intellectual Property Management (IPM) Integration

!--a11y-->
By Title Financial Processing and Reporting
By Title Financial Processing and Reporting gives you an up-to-date picture of the profitability of your individual media titles at all times, categorizing them by
business areas and other combinations of characteristics, such as territory, market, and language. In addition to periodic analysis, the function focuses primarily
on a view of the entire life cycle of a media product. You can use this data for planning and profitability analyses of existing and new titles and product strategies,
and you can also consolidate it to preview your companys overall success. In some scenarios, you need the results of these profitability analyses to precisely
determine payables and activate investment portions.
Purpose
mySAP Media PLM provides you with a framework for deriving and saving financial data and other controlling characteristics on a title, which are then used in
Accounting transactions (for example, posting of CRM billing documents, posting of G/L documents, posting of expenditure and costs to internal orders or
projects). These characteristics can be derived from the process data by derivation rules defined using a generic mapping tool. This allows you to identify
attributes that are recorded as transaction data and specify how these attributes are used to derive the characteristics for by title financial processing and
reporting. For example, the attribute Delivery Location from Product Sales in an SD application is mapped to the characteristic Territory . A special
enhancement can also be used to assign titles for partial payments at billing item level for incoming payments in Accounts Receivable Accounting.
For further information on the generic mapping tool, see the IMG documentation under SAP Media Title Lifecycle Management Intellectual Property
Management (IPM) Integration Define Attribute Mapping.
Integration
By title financial processing and reporting can take place using special purpose ledgers and/or a profitability analysis.
If you want to use the special purpose ledgers, the most important step you must perform is to define the account assignment objects to be used by the ledger.
This determines the level at which profitability analysis is to take place.
You can only use account assignment objects that belong to the structure ACCIT. Title-specific account assignment objects (such as title or territory) do not exist
there. Add these fields to the customer include for the account assignment block (CI_COBL). The system contains data elements for the most common title-
specific account assignment objects (title level 1, title level 2, title level 3, market, territory, and language) and you should use these.
In order to use the profitability analysis function, you must set up an operating concern and define the data structure. This determines the level on which the data is
aggregated for profitability analysis. The template contains characteristics for the most common title-specific characteristics (title level 2, title level 2, title level 3,
territory, and language).





!--a11y-->
1.7 Web Applications
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 32 of 36
!--a11y-->
1.7.1 M/SD Internet Applications
Purpose
The Internet applications in Periodical Sales and Distribution can be used for subscription sales (creating subscription orders) and customer service for
subscriptions (address changes, vacation service, changes to payment data, etc.) in the Internet.
Integration
For basic information on how Internet Application Components are programmed and how they work, please see the following documentation:
SAP@Web Studio
Web Transaction Tutorial
IAC Implementation
This documentation also describes the tools and functions you can use to modify the Internet application components in Subscription Sales and Distribution
according to your requirements.
Features
The following Internet application components are available for Subscription Sales and Distribution:
Internet application component Use
Subscription Sales Used to record subscription sales in the Internet in a variety of variants.
The user can create orders and business partners directly as well as store data
initially in a temporary table.
Vacation Service Enables the customer to suspend one or more of their subscriptions for a certain period
or create redirections.
Change Address The sold-to party of a subscription can use this Internet application component to change
their address in the Internet.
Change Payment Data Can be used by the customer to change the payment data for one or more orders.
Create Complaints Allows your customers to create complaints regarding a media product or delivery via
the Internet.
Create Internet Users Allows your customers to create their own Internet users. The customer can use this
Internet user to log on to the Internet applications.
The Internet user is required if customers are to log on with a password.
Change Access Data for Internet User Allows your customers to change data on their Internet user (password, user name, e-
mail address) themselves. You can design the scenario to allow the customer to obtain a
new password for their Internet user if they forget the old one.


!--a11y-->
1.7.2 M/AM Internet Applications
Purpose
Internet applications allow you to use R/3 transactions in the IS-M/AM System on the Internet.
Integration
Basic programming principles and the functions of an Internet application component can be found in the following documentation:
SAP@Web Studio
Web Transaction Tutorial
IAC Programming
This documentation also includes a description of the tools and functions that you can use to adjust the Internet application components provided with IS-M/AM to
meet your requirements.
Features
The following Internet application components are available in IS-M/AM:
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 33 of 36
Internet application component Use
Enter classified ads The Internet application component is a simplified version of the Create ad
items R/3 function.
You can use this Internet application component to create classified and
designed ads.
A technical system can be integrated here, as is the case for the R/3 function.
Manage classified ads The Internet application component is a simplified version of the Central
access R/3 function.
This Internet application component is used to perform business and content
checks for ads created via the Internet. A technical system can also be
integrated here, as is the case for the R/3 function.
Check fixed space availability The Internet application component is a simplified version of the Fixed spaces
planning R/3 transaction.
Your customers or sales employees can use this Internet application
component to check the availability of fixed spaces.
Display contract The Internet application component is a simplified version of the Display
contract R/3 transaction.
Customers can use this Internet application component to display certain
contract data on the Internet.
Change addresses The Change address Internet application component is used to change the
business partner address via the Internet.


!--a11y-->
1.7.3 MiniApps
!--a11y-->
1.8 Data Archiving


!--a11y-->
1.8.1 Data Archiving in SAP Media



!--a11y-->
1.9 Roles


!--a11y-->
1.9.1 Single Roles for SAP Media
!--a11y-->
1.9.2 Single Roles in Media Sales and Distribution
!--a11y-->
1.9.3 Single Roles in Advertising Management
!--a11y-->
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 34 of 36
Campaign Management for the Media Industry


!--a11y-->
Campaign Management for the Media Sector
Purpose
This business scenario enables you to use the marketing functions in SAP CRM for media-specific campaign management. Media-specific campaign
management covers campaigns for advertising services and subscriptions.
TheCampaign Management for the Media Sector business scenario covers the entire process chain from market and customer analysis, marketing planning,
campaign execution and monitoring through to analysis of success.
Various communication channels are available to you for campaign execution. You can perform campaigns for advertising services and subscriptions by e-mail,
telephone, fax or letter and using Mobile Sales and the Internet. You can also use the campaign automation and optimization functions to simulate execution of a
campaign, improve the general campaign conditions, and have the system perform campaigns automatically.
Orders for a campaign can be entered in the Customer Interaction Center (CIC) in SAP Media, the Interaction Center WinClient (IC) in SAP CRM , the
Internet and by using Mobile Sales.
Target costs for a campaign can be transferred to the SAP R/3 Project System independently from campaign execution, to ensure that the actual costs can be
assigned to the corresponding WBS element. This means that you can check the campaign costs during campaign execution.
Information on campaigns, orders and costs is also transferred to SAP BW so that you can determine the response to campaigns after campaign execution and
in doing so check the success of the campaign.
A description of this business scenario is available in the SAP Library under mySAP Customer Relationship Management CRM Enterprise
Marketing.
Media-specific functions that are part of this business scenario are also described here.
Implementation Considerations
The 1.10.1 Campaign Management for the Media Sector scenario requires comprehensive Customizing settings to be made, such as configuration of
middleware, business partner replication or definition of specialist functions in the Customer Interaction Center . A description of these Customizing settings is
available in the Solution Manager .
Integration
The following components are part of this scenario:
SAP CRM (as of Release 4.0 with SP01)
SAP BW (as of Release 3.10) with SEM Add-On (as of Release 3.2)
SAP Media (as of Release 4.71 with SP 01)
SAP R/3 Plug-In PI 2003.1 with SP01
SAP R/3 Enterprise 4.70 x 1.10
Mobile Client 4.0 with Middleware integration
Features
Marketing and campaign planning takes place in the SAP CRM Marketing Planner . The description, target groups, dates and key figures are defined here.
If the campaign is business partner-independent, select the target groups in SAP CRM using SAP BW. You should then assign the target groups selected to
the campaign in the Marketing Planner . This step is not required if the campaign is business partner-dependent.
All objects in the Marketing Planner (marketing plans, campaigns, campaign elements) are exported to the SAP R/3 Project System. They are created as
WBS elements here. Costs and revenues can be posted to WBS elements.
During order entry, the agent can identify which campaigns were assigned to the customer. Order entry can be accelerated by assigning template documents to
the campaign in the campaign master data. The system transfers data in the template documents and the campaign ID to the order items created.
The campaign ID is transferred to follow-up documents for the order item during billing and settlement.
A marketing element is available as a characteristic in SAP R/3 profitability analysis for SAP R/3 Cost Accounting . Actual costs for the WBS element can be
assigned to the corresponding profitability segment directly. Revenues are assigned to the profitability segment during billing.

!--a11y-->
Release Notes SAP Media 4.72
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 35 of 36


PDF Content
This page content is in PDF format.
Download
PDF Content
This page content is in PDF format.
Download
PUBLIC
2014 SAP SE or an SAP affiliate company. All rights reserved.
Page 36 of 36

Вам также может понравиться