RN IS Media 472 EN

SAP Media
Release Notes
Release 4.72
March 2004
______________________________________________________________
Copyright
Copyright(c) 2004 SAP AG. All rights reserved.

Neither this document nor any part of it may be copied or reproduced in any form or by any
means or translated into another language, without the prior consent of SAP AG. The
information contained in this document is subject to change without notice.
SAP is a registered trademark of SAP AG.
All other products which are mentioned in this documentation are registered or not registered
trademarks of their respective companies.
SAP
System
Table of Content
SAP AG
______________________________________________________________
1
1.1
1.1.1
1.1.1.1
1.1.1.2
1.1.1.3
1.1.1.4
1.1.1.5
1.1.1.6
1.1.1.7
1.1.2
1.1.2.1
1.1.2.1.1
1.1.2.1.2
1.1.2.1.3
1.1.2.1.4
1.1.2.1.5
1.1.2.2
1.1.2.2.1
1.1.2.2.2
1.1.2.2.3
1.1.2.2.4
1.2
1.2.1
1.2.1.1
1.2.1.2
1.3
1.3.1
1.3.2
1.3.3
1.3.4
1.3.5
1.3.6
1.3.7
1.3.8
1.3.9
IS-M SAP Media

IS-M-MD Master Data
IS-M-MD-BP Business Partner
Document Management for SAP Media Business Objects (New)
Business Partner Administration Using SAP Business Partner
(Changed)
Conversion Tool for Customers and Vendors (New)
Restrictions on Changes to Organizational Units (Changed)
Maintaining the Contract Hierarchy As a Relationship in SAP
BP (New)
Alternative Business Partners in User-Defined Roles
(Enhanced)
Processing Order Data from the Internet (Enhanced)
IS-M-MD-PR Product Master Data
IS-M-MD-PR-MP Media Product
13-Digit ISBN (Changed)
Enhancements to the Issue Sequence (New)
Refresh of Quantity Planning Attributes in Issue Sequences
(Changed)
Settings for Media Products in Series Sales (New)
Series Combinations (New)
IS-M-MD-PR-B Booking
BAPIs for the Booking Unit (New)
BAPIs for the Content Component (New)
Internet Publication of a Print Ad (New)
IS-M-BF Basic Functions
IS-M-BF-PR Pricing
Order Pricing with Scale Base Contract (Enhanced)
More Flexible Base for Contract Discount and Bonus (New)
IS-M-CA Contract Accounts Receivable and
Payable
Extraction of Tax-Relevant Data for GDPdU (Changed)
Additional Payments for Renewals (New)
Transfer Postings of Additional Payments and Refunds in
Renewals (New)
Account Balance Display
Archiving for Tax Reporting Argentina (Changed)
Archiving
Authorization Objects
BAPIs in Contract Accounts Receivable and Payable
Boletos
9
9
9
9
13
13
13
14
14
15
15
15
15
16
16
17
18
18
18
19
19
23
24
24
24
24
25
25
26
27
28
28
29
30
30
32
______________________________________________________________
SAP AG
iii
SAP
System
Table of Content
SAP AG
______________________________________________________________
1.3.10
1.3.11
1.3.12
1.3.13
1.3.14
1.3.15
1.3.16
1.3.17
1.3.18
1.3.19
1.3.20
1.3.21
1.3.22
1.3.23
1.3.24
1.3.25
1.3.26
1.3.27
1.3.28
1.3.29
1.3.30
1.3.31
1.3.32
1.3.33
1.3.34
1.3.35
1.3.36
1.3.37
1.3.38
1.3.39
1.3.40
1.3.41
1.3.42
1.3.43
1.3.44
1.3.45
Business Information Warehouse

Payment at Cash Desk
Cash Journal
Closing Operations
Submission of Receivables to Collection Agencies
Collective Bills
Company Codes
Creating Correspondence
Connection of SAP Dispute Management to Contract Accts Rec.
and Pay.
Dunning
Enhanced Message Management
New and Changed Events
Conversion of Finnish Bank Statement to MultiCash (Enhanced)
Foreign Currency Valuation
IDoc Interfaces for Communication with External Billing
Systems
Changed IMG Activities in Contract Account Receivable and
Payable
New IMG Activities in Contract Accounts Receivable and
Payable
Information System
Deferral and Installment Plan
Integration
Interest Calculation
Processing Locks
Mass Runs
Master Data
Evaluating Open Items
Processing of Incoming and Outgoing Payments
Payment Transactions
Collections in the Print Workbench
Postings and Documents
Prenotifications
New Reports
Requests
Processing of Returns
Integration of Schedule Manager in Contract Accounts Rec.
and Pay.
Stop Future Payment (Denmark)
Tax Reporting in Contract Accounting (New)
33
33
34
35
36
36
38
40
40
44
44
45
48
48
49
50
51
53
54
56
57
58
58
59
60
60
61
64
64
69
70
70
71
72
73
74
______________________________________________________________
SAP AG
iv
SAP
System
Table of Content
SAP AG
______________________________________________________________
1.3.46
1.3.47
1.3.48
1.4
1.4.1
1.4.2
1.4.3
1.4.4
1.4.5
1.4.6
1.4.7
1.4.8
1.4.9
1.4.10
1.4.11
1.4.11.1
1.4.11.1.1
1.4.11.1.2
1.4.11.1.2.1
1.4.11.1.2.2
1.4.11.1.2.3
1.4.11.1.2.4
1.4.11.1.2.5
1.4.11.1.2.6
1.4.11.1.2.7
1.4.11.1.2.8
1.4.11.1.2.9
1.4.11.1.2.10
1.4.11.1.2.11
1.4.11.1.2.12
1.4.11.1.2.13
1.4.11.1.2.14
1.4.11.1.3
Write-Offs
Generic Withholding Tax Reporting (Enhanced)
New Entries in Contract Accounts Menu for Media Sales &
Dist. 4.72
IS-M-SD Media Sales and Distribution
CIC - New Functions for Creating Business Partners
(Enhanced/Modified)
CIC - New Functions in the Business Partner Search
(Enhanced)
CIC - Reset to Default Workspace When Contact Ends
(Enhanced)
CIC - Component Layout (Enhanced)
CIC - Additional Data in the Data Environment and HTML
Customer Overview
CIC - Display Variants in the Data Environment (Enhanced)
CIC - Accessing and Executing Workspaces Dynamically (New)
CIC - New Scripting Options for M/SD-Specific Processes
(New)
CIC - Texts for Business Partner (Enhanced)
Campaign Master Data in the Marketing Planner (Changed)
IS-M-SD-PS Periodical Sales and Distribution
IS-M-SD-PS-SL Sales
Transferring Billing Documents to Human Resources (New)
IS-M-SD-PS-SL-O Order
Enhancements to Internet Application Components (New)
Function for Displaying Amortization Log (New)
Terminating Subscriptions with Change Items (New)
Donating Refunds (New)
Proportional Billing for Limited Changes in Renewals
(Changed)
Fixing the Expiration Date for Performance-Related Renewal
Subscriptions
Retroactive Billing for Period Renewal Subscriptions (New)
Automatic Splitting of Subtractive Changes (New)
Skipping a Monitoring Cycle for Credit Memo Surplus (New)
Additional Payments for Renewals (New)
Ending Trial Subscriptions for Period Renewals (Changed)
Bank Control Key Available in Fast Entry (Changed)
Non-Billable Goodwill Deliveries when Payment Is Delayed
(Changed)
Additional Filter for Roles (New)
IS-M-SD-PS-SL-C Complaint
74
74
75
76
76
77
78
78
80
80
81
81
83
84
84
84
84
85
85
86
86
86
87
88
89
89
89
90
91
91
91
92
92
______________________________________________________________
SAP AG
SAP-System
Table of Content
SAP AG
______________________________________________________________
1.4.11.1.3.1
1.4.11.2
1.4.11.2.1
1.4.11.2.2
1.4.11.2.3
1.4.11.2.3.1
1.4.11.2.3.2
1.4.11.3
1.4.11.3.1
1.4.11.3.2
1.4.11.3.3
1.4.11.3.4
1.4.11.3.5
1.4.11.4
1.4.11.4.1
1.4.11.4.1.1
1.4.11.4.2
1.4.11.4.2.1
1.4.12
1.4.12.1
1.4.12.2
1.4.12.3
1.4.12.4
1.4.12.5
1.4.12.6
1.4.12.7
1.4.12.7.1
1.4.12.7.2
1.4.12.7.3
1.4.12.7.4
1.4.12.7.4.1
1.4.12.7.4.2
1.4.12.7.5
1.4.12.7.5.1
1.4.12.7.5.2
Text Field for Complaint in Short Complaint Dialog (New)

IS-M-SD-PS-SH Shipping
Attributes for Delivery Viability Determination in a
Shipping Order
Market Coverage (New)
IS-M-SD-PS-SH-P Circulation Planning
Customer Exit for Home Delivery Quantities in Deliveries
(New)
Planning of Combinations for Backdated Order Items (Changed)
IS-M-SD-PS-BL Billing
Transferring Billing Documents to Human Resources (New)
Update of Intermediate Payment Dataset for Collective
Transfer (Changed)
Document Number Selection for the Check List for Revenue
Accrual
Billing Creation in Parallel with Order Management (Changed)
IS-M-SD-PS-ST Settlement
IS-M-SD-PS-ST-W Home Delivery Settlement
IS-M-SD-PS-ST-C Commission Settlement
IS-M-SD-MS Media Product Sales and Distribution
Direct Store Delivery in Single Copy Sales (New)
Purchasing Planning (New)
Table for Fast Access to Address Data (New)
Enhancements to Logs in Single Copy Sales (New)
Marking Contracts as Media-Specific (New)
Changes to Variant Control (Changed)
IS-M-SD-MS-SL Sales
Improved Ergonomics in Central Access to Single Copy Sales
(New)
Copy Number in Central Access to Single Copy Sales (New)
Shipping Planning (New)
IS-M-SD-MS-SL-C Contract
Index Table for Selecting Contracts in the Quantity Plan
(New)
Subscriptions for Series Sales (New)
IS-M-SD-MS-SL-Q Purchase Quantity Planning
Copying Function for Groups of Media Products (New)
Selection in the Quantity Plan for Each Contract (New)
92
92
92
93
94
94
95
95
96
96
97
97
98
98
98
98
99
99
101
101
101
102
102
102
103
103
103
103
104
104
104
104
105
105
105
______________________________________________________________
SAP AG
vi
SAP
System
Table of Content
SAP AG
___________________________________________________________
1.4.12.7.5.3
1.4.12.7.5.4
1.4.12.7.5.5
1.4.12.7.5.6
1.4.12.7.5.7
1.4.12.7.5.8
1.4.12.7.6
1.4.12.7.6.1
1.4.12.7.6.2
1.4.12.7.7
1.4.12.7.7.1
1.4.12.7.7.2
1.4.12.7.7.3
1.4.12.7.7.4
1.4.12.7.7.5
1.5
1.5.1
1.5.2
1.5.3
1.5.4
1.5.5
1.5.6
1.5.7
1.5.8
1.5.9
1.5.10
1.5.11
1.5.12
1.5.12.1
1.5.12.1.1
1.5.12.1.2
1.5.12.1.3
1.5.12.1.4
1.5.12.1.5
1.5.12.1.6
1.5.12.1.7
1.5.12.1.8
Quantity Forecasts According to Reference Issues (New)

Business Partner Role in Quantity Plan (New)
Business Partner Role in Quantity Planning (New)
Enhancements to the Contract Navigator (New/Enhanced)
Copying Delivery Quantities for Different Media Products
(New)
Event Management in Quantity Planning (New)
IS-M-SD-MS-SL-O Order Creation
Rounding the Order Quantity to Full Bundles (New)
Order Generation for Series Sales (New)
IS-M-SD-MS-SL-R Returns
Determining Media Issues for Collection (New)
Creating New Returns (New)
Parallel Return Release (New)
BAPI for Changing Returns (New)
Restricting Return Release (New/Enhanced)
IS-M-AM Advertising Management
CIC - Contracts in the Data Environment (Enhanced)
CIC - Entry of Ad Items (Enhanced)
Sale of Display Classified Ads (New)
CIC - New Functions for Creating Business Partners
(Enhanced/Modified)
CIC - New Functions in the Business Partner Search
(Enhanced)
CIC - Reset to Default Workspace When Contact Ends
(Enhanced)
CIC - Component Layout (Enhanced)
CIC - Display Variants in the Data Environment (Enhanced)
CIC - Accessing and Executing Workspaces Dynamically (New)
CIC - Texts for Business Partner (Enhanced)
Campaign Master Data in the Marketing Planner (Changed)
IS-M-AM-SL Sales
IS-M-AM-SL-O Order
Filter Objects for Orders in External Systems (Enhanced)
Artwork Assignment (Enhanced)
BAPIs for the Sales Document (Enhanced)
BAPIs for the Ad Spec (New)
Assignment of Voucher Copy and Box Number Recipients
(Modified)
Entry of Payment Cards (Changed)
Customer Enhancements in the Order (New/Enhanced)
Old User Interface Is No Longer Supported (Modified)
106
106
106
107
107
107
108
108
108
109
109
110
110
110
111
111
111
111
113
114
115
116
117
118
118
118
119
120
120
120
120
121
122
122
123
123
123
______________________________________________________________
SAP AG
vii
SAP
System
Table of Content
SAP AG
____________________________________________________________
1.5.12.1.9
1.5.12.2
1.5.12.2.1
1.5.12.2.2
1.5.12.2.3
1.5.13
1.5.13.1
1.5.13.1.1
1.5.13.2
1.5.13.2.1
1.5.14
1.5.14.1
1.5.14.1.1
1.5.15
1.5.15.1
1.5.16
1.5.16.1
1.6
1.6.1
1.7
1.7.1
1.7.1.1
1.7.1.2
1.7.1.3

IS-M-AM-SL-C Contract
Order Pricing with Scale Base Contract (Enhanced)
Discount/Price Adjustment for Scale Base Contracts
(Enhanced)
IS-M-AM-BL Billing Document
IS-M-AM-BL-O Order Billing
Billing Document in Collective Processing: Default Values
for Credit Management
IS-M-AM-BL-S Contract Settlement
Discount/Price Adjustment for Scale Base Contracts
(Enhanced)
IS-M-AM-ST Settlement
IS-M-AM-ST-R Revenue Distribution
Existing Revenue Distribution Procedure No Longer Supported
(Modified)
IS-M-AM-RR Revenue Recognition
FI Document Type for Revenue Recognition Reversal Run (New)
IS-M-AM-MS Connection of Media Technical
Systems
Technical Interface (Enhanced)
IS-M-PLM Product Lifecycle Management
Creating a Media Product Master from a WBS Element
(Enhanced)
IS-M-IS Information System
IS-M-IS-SD Information System for Media Sales
and Distribution
DataSources in the SAP Business Information Warehouse (New)
Enhancements to the Circulation Book (New)
Improved Performance in Circulation Book Update (New)
124
128
128
132
133
133
133
133
133
133
134
134
134
134
134
135
135
137
137
137
138
138
138
139
______________________________________________________________
SAP AG
viii
SAP System
______________________________________________________________
1 IS-M
SAP Media
1.1 IS-M-MD
Master Data
1.1.1 IS-M-MD-BP
Business Partner
1.1.1.1 Document Management for SAP Media Business Objects (New)

Use
As of SAP Media 4.72, document management functions are available for the Business Partner
(BUS1006), Advertising Management sales agent contract (BUSISM018), Advertising Management
Booking Unit (BUSISM024), Advertising Management Content Component (BUSISM025), Advertising
Management Sales Document (BUSISM008), Advertising Management order item (BUSISM009),
Advertising Management Ad Spec (BUSISM028) and Advertising Management Contract (BUSISM012)
business objects. A dialog, in which you can assign folders and documents to the object, has been
integrated in the maintenance transactions for the business objects. A new Documents tab page is
available at header level in the business partner transactions. This type of tab page is also available at
header and item level in the sales document and in the ad spec. The new dialog can be accessed using a
button or menu path in the maintenance transactions for the sales agent contract, booking unit, content
component and contract.
The Knowledge Provider (KPro) is used to manage documents. The KPro is part of the SAP Web
Application Server (SAP Web AS). Additional information is available in the SAP Library under: 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-SRV-KPR).
The connection of document management functions means you can assign diverse file formats to business
object documents. You can for instance record the associated written contract for a sales agent contract,
the written agreement with the customer for a contract or documents for key account planning for a
business partner.
Document management functions have been integrated in response to requirements from the Sale of
Display Classified Ads scenario. Refer to the Sale of Display Classified Ads release note.
Document Management Functions
The new dialog for processing documents consists of two sections as standard. The left hand section of
the screen contains the explorer in which the folder and documents for the object are displayed. The right
hand section of the screen contains the viewer. The content and features of the document selected in the
Explorer are displayed in the viewer.
Functions provided by the Explorer include:
o
Create folder
Create document
Create URL
______________________________________________________________
SAP AG
SAP System
______________________________________________________________
URLS can also be recorded in addition to documents with diverse file formats.
o
Import document from file

You can either create documents directly from the Explorer or you can import an existing document
from the local file system for instance.
Display document
The document is displayed in its full size in the corresponding editor for the respective file format.
Features of the folder or document

The Features dialog box appears. To change these features, switch to the change mode and enter the
corresponding data.
Rename folder or document

To change the description of a folder or document, select the respective object and choose Features.
Delete original
When you delete a document, you can decide whether the document is going to be physically
deleted or whether you are only going to delete the reference to the document. In this situation, the
system only deletes the link between this document and the respective business object. You can use
the where-used list to check the objects to which the document is assigned.
Export
Export the document, for instance to a local directory. Note that you can still change the document
in the Explorer.
Export with block

Documents exported in this manner cannot be changed in the Explorer until a re-import has taken
place.
Import new version

If a document is imported, you can decide whether you want to overwrite or retain the existing
version of the document. The system always displays the most recent version of the document as a
default. To display a list of the various versions of a specific document in the Viewer, choose
Versions.
Cut, copy and paste

Documents can also be dragged between various folders using Drag&Drop. Note that you can copy
both complete folders or individual documents.
Search
You can use attribute values as selection criteria to search for documents. You can use this function
to assign a document to several business objects.
If you also intend to use the search in the document text, you must use Text Retrieval and
Information Extraction in conjunction with a search engine.
You can use the Visibility in the Document Search attribute to control the circumstances in which it
is visible in the search result for each document.
Where-used list
List of all business objects to which a specific document is assigned.
Use as an ad element
List of all ad specs in which the document has been incorporated as an ad element. Information on
graphics used in the artwork assignment, which has been returned by the technical system, is
evaluated here
______________________________________________________________
SAP AG
10
SAP System
______________________________________________________________
Send
You can use the Business Workplace functions to send documents as an e-mail attachment to one or
more recipients.
Functions provided by the Viewer include:

o
Document preview
Display and change documents and their features
Version overview with version display and processing
The new J_DOC_MAN authorization object has been created for document management. You can use
this to give users authorization to create, change or display documents for each business object. If a user
only has display authorization for the business partner business object, they can view documents on
business partners but the editing functions are inactive. If a user does not have display authorization, the
buttons for accessing this dialog are inactive or the corresponding tab pages do not exist.
Copying Orders
When copying orders or items, you can also copy the assigned documents. To do so, you must define the
corresponding copying variants in the IMG under SAP Media -> Advertising Management -> Sales ->
Order -> Client-Specific Settings -> Copying Control. You can define whether documents are to be
copied at header level, item level and ad spec level here.
During copying, the system does not generate copies of documents for the template object, but assigns
references from the original documents to the copied object instead. This ensures that generating a new
version of a document involves both the template object and the object copied.
External Interface for Access to Documents
In addition to the dialog functions, an RFC-enabled interface for read and write access to documents is
available. This interface consists of the following RFC functions:
o
ISM_DM_DOCS_OF_BUS_OBJ_GET: Define documents for a business object
ISM_DM_FOLDERS_OF_BUS_OBJ_GET: Define folder for a business object
ISM_DM_IO_CONTENT_GET: Provide content of a document
ISM_DM_FOLDER_CREATE_FOR_BO: Create folder for a business object
ISM_DM_IO_CREATE_WITH_FILE: Create document using the file system
ISM_DM_IO_CREATE_WITH_TABLE: Create document using a table
ISM_DM_IO_CREATE_WITH_URL: Create document using a URL
ISM_DM_VERS_CREATE_WITH_FILE: Create a new version of a document using the file

system
ISM_DM_VERS_CREATE_WITH_TABLE: Create a new version of a document using a table
ISM_DM_IO_PROPERTIES_CHANGE: Change the document properties
ISM_DM_IOS_DELETE: Delete documents from a business object
ISM_DM_IOS_FOR_AD_CONTENT_GET: Define all documents for all relevant business objects

in an order. The system also takes account of documents that belong to business partners who have
been assigned above the sold-to party or advertiser in the business partner hierarchy, if the BP
______________________________________________________________
SAP AG
11
SAP System
______________________________________________________________
hierarchy type is suitable for this. Settings for the BP hierarchy type are made in the IMG under SAP
Media -> Master Data -> SAP Business Partner for Media Companies -> Control -> Define
Business Partner Hierarchy Types (IS-M/AM).
Infrastructure of Documents in the KPro
The Knowledge Provider is used to manage relationships between documents and not the actual
documents. Document classes, their relationships and their attributes are described in the content model.
Additional information on the content model is available in the SAP Library under: 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-SRV-KPR) -> Document Management Service (BC-SRV-KPR) -> Document Modeling Workbench.
Use the Content Management Service to define the storage medium used to physically store documents.
Various storage types, which have different benefits and should be selected according to the usage of the
document to be stored, are available.
o
HTTP Content Server

You can use the SAP Content Server supplied by SAP or a third party content server.
R/3 database
If you want to store your documents in the R/3 database, you require a content table in which the
usage of the R/3 database as storage for all documents is to be recorded.
Use of an HTTP Content Server is recommended in the live system.

Additional information on physical document storage is available in the SAP Library under: 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-SRV-KPR) -> Content Management Service (BC-SRV-KPR).
SAP Media 4.72 contains a specialist content model which defines the type of documents that can be
assigned to the business objects, the relationships between these documents and the document attributes.
This content model is available in the Document Modeling Workbench in the ISM document area.
Before you can store documents in document management, you must define memory categories and
content repositories. If you use the content repositories ISM_DOC and ISM_URL, which are supplied
with the standard Customizing settings, the documents are stored on the R/3 database. If you want to use
a different storage type, you can define your own content repositories with the desired storage type using
transaction OAC0 and assign them to the content repositories ISM_DOC or ISM_URL using transaction
OACT.
Some instance attributes for document classes in the ISM document area have been provided specifically
for the Sale of Display Classified Ads scenario, such as the type of graphic, release status attributes and
the default sizes for use in ads with one, two or three columns. You can enter values in dialog for these
attributes for each document. These attributes are also available via the external interface. If an attribute
is to be evaluated equally for all documents in a folder, you only need to record values in the folder.
If you require additional attributes that do not exist in the info object classes supplied, you can derive
your own content model from the content model supplied. To do so, you can replicate or copy the info
object classes supplied into a separate document area or the document area supplied to transfer the
existing attributes. You can then assign the attributes required to the new info object classes. You can
also evaluate these attributes in dialog and via the external interface. If you have defined your own info
object classes, you must implement the ISM_DM_CLASS_DETERM BAdI, so that your own classes are
used instead of the classes supplied. The documentation for the BAdI and its methods contains
______________________________________________________________
SAP AG
12
SAP System
______________________________________________________________
information on the way in which you should model your content model. If you want to use your own
document area, you must also record this in the SKWF_APPLS table.
1.1.1.2 Business Partner Administration Using SAP Business Partner

(Changed)
Use
As of SAP Media 4.72, business partner administration only supports the SAP Business Partner. The
alternative master data maintenance functions with the Media Business Partner are now no longer
available. Perform business partner migration to convert your existing media business partners to the
SAP Business Partner.
Effects on Customizing
To execute business partner migration, choose SAP Media -> Tools -> Business Partner Migration to
SAP Business Partner in the Implementation Guide.
1.1.1.3 Conversion Tool for Customers and Vendors (New)

Use
As of SAP Media 4.72, you can create existing customers and vendors as SAP business partners in a
media-specific role.
To perform the conversion, choose SAP Media -> Tools -> Convert Customers and Vendors to SAP
Business Partner -> Convert Customers and Vendors to SAP Business Partner.
Please also refer to the report documentation.
1.1.1.4 Restrictions on Changes to Organizational Units (Changed)

Use
As of SAP Media 4.72, you can change the company code or sales area when editing business partner
data, without having to exit the transaction.
The company code and sales area data is accessible on two different tab pages, which can be accessed
using the Company Code and Sales Area pushbuttons. In release 4.71, it was not possible to change the
organizational unit once it had been entered. To choose a different organizational unit, the user had to exit
the transaction or edit a different business partner.
As of Release 4.72, it is now possible to change the organizational unit. If you make changes to other data
before changing the organizational unit, you must confirm your entries, since otherwise the changes will
be lost.
______________________________________________________________
SAP AG
13
SAP System
______________________________________________________________
See also
Note 700654 describes the technical changes that must be made if customer-specific data dependent on
the company code or sales area exists as an append to a standard table or as a separate table.
1.1.1.5 Maintaining the Contract Hierarchy As a Relationship in SAP BP (New)

Use
As of SAP Media 4.72, you can maintain the business partner hierarchy in the relationships for the SAP
Business Partner (SAP BP). The function is part of a modern maintenance interface. A variety of options
are available for displaying and printing hierarchical relationships. You can display the results as a simple
list, hierarchy, or network with levels that can be expanded in different ways.
The standard relationship category Contract Hierarchy has been designed for this purpose. The
relationships for this category are Parent Company Contract and Subsidiary Contract. You can maintain
the percentage of the parent's share in the subsidiary on the detail screen.
Effects on Existing Data
You can migrate the existing business partner hierarchies to SAP business partner relationships using
report RJJHIERARCHY_MIGRATE.
Before you can maintain the business partner hierarchy as a relationship, you must assign a relationship
category to each business partner hierarchy type. If you set up a new business partner hierarchy type in
the Implementation Guide under SAP Media -> Master Data -> Business Partner -> Control -> Define
Business Partner Hierarchy Types, the system creates a new relationship category in background
processing and assigns it to the business partner hierarchy type.
The migration report RJJHIERARCHY_MIGRATE automatically generates corresponding relationship
categories. The relationship category ISM010 is used as a template for the generated relationship
categories. You must define the descriptions required for the relationship type beforehand in the
Customizing settings for the business partner hierarchy type.
1.1.1.6 Alternative Business Partners in User-Defined Roles (Enhanced)

Use
As of SAP Media 4.72, you can assign alternative business partners in roles that you define to a business
partner in their master data. You could only use the following roles previously:
o
Voucher copy recipient
Box number recipient
Ad spec master recipient
Correction deduction recipient
______________________________________________________________
SAP AG
14
SAP System
______________________________________________________________
Ad spec master sender
General business partner
Competitor
Bill-to party
Payer
Ship-to party
You must record any roles that you define in the SAP Implementation Guide Settings as follows: SAP
Media -> Master Data -> Business Partner -> Control -> Define Business Partner Roles.
You can use alternative business partners in the sales document at item level if you have recorded the role
you have defined in the SAP Implementation Guide under SAP Media -> Basic Functions -> Partner
Determination M/AM -> Define and Assign Partner Determination Procedures. You can only record
alternative voucher copy recipients at header level.
1.1.1.7 Processing Order Data from the Internet (Enhanced)

Use
As of SAP Media 4.72, the following enhancements have been made to the program for processing order
data from the Internet (transaction JKWWWTEMP for Periodical Sales and Distribution or
JHWWWTEMP for Advertising Management):
o
Communication data for duplicates: If a duplicate is identified when processing data from the
Internet, the system displays a duplicate dialog box comparing the data from the Internet with the
potential duplicate in the system. If the business partners are the same, processing continues with
this duplicate or the corresponding business partner number. As of release 4.72, communication data
entered in the Internet that does not yet exist in the system is added automatically. For example, if
the e-mail address or telephone number is entered for the purchase order in the Internet, this data is
added to the duplicate in the system if the corresponding fields were previously empty.
1.1.2 IS-M-MD-PR
1.1.2.1 IS-M-MD-PR-MP
Product Master Data

Media Product
1.1.2.1.1 13-Digit ISBN (Changed)

Use
As of SAP Media 4.72, a check digit algorithm is available to support the planned conversion to 13-digit
ISBN numbers.
______________________________________________________________
SAP AG
15
SAP System
______________________________________________________________
Existing media product master records are assigned a 10-digit ISBN. You will have created a special ID
code type for this purpose. We recommend that you create a new ID code type for the 13-digit ISBN, so
that you can work with the 13- and 10-digit ISBNs in parallel during the transition phase. This means that
a media product master record can be assigned a 10-digit and a 13-digit ISBN at the same time.
The ID code type 0005 and the check digit algorithm 0003 are delivered as sample Customizing settings
for the 13-digit ISBN.
Copy the check digit algorithm 0003 in the Implementation Guide under SAP Media -> Master Data ->
Product -> Media Product Master -> Settings for Media-Specific Fields -> Define ID Codes -> Define
Check Digit Algorithm for ID Code.
Copy the ID code type 0005 in the Implementation Guide under SAP Media -> Master Data -> Product
-> Media Product Master -> Settings for Media-Specific Fields -> Define ID Codes -> Define ID Code
Types and change the copied ID code type according to your requirements.
1.1.2.1.2 Enhancements to the Issue Sequence (New)

Use
In SAP Media 4.72, the following enhancements have been made to the issue sequence:
o
Shipping planning records for series sales

Shipping planning records for use in sales and distribution of media product series can be created
automatically for media issues that are in an issue sequence. (See also Shipping Planning.)
New attribute for the issue sequence

The new indicator Issue Sequence with Chronological Follow-On Processes allows you to
determine that issues in the issue sequence are always sorted in chronological order. This setting is
relevant for all processes that require a chronological issue sequence.
The indicator is always selected for issue sequences that are synchronized with Periodical Sales and
Distribution (Subscription Sales and Distribution) and cannot be changed.
The indicator can only be changed (so that the issues are no longer sorted in chronological order) if
synchronization does not take place. The publication date can be initial or can be repeated several
times.
1.1.2.1.3 Refresh of Quantity Planning Attributes in Issue Sequences (Changed)

Use
In SAP Media 4.72, improvements have been made to performance in the issue sequence. The attribute
values displayed in the issue sequence are the same as the actual attribute values for all media issues that
have been created physically (green traffic light icon in the issue sequence). There are no longer
exceptions. This applies to the following attribute values:
o
Publication date
______________________________________________________________
SAP AG
16
SAP System
_____________________________________________________________
Copy number
Actual issue variant type
Standard issue variant type (planned)
Number in year
Year number
The function for refreshing the attribute values in the issue sequence has been added to improve
performance. It is no longer necessary to read the above attributes from the media issue when reading the
issue sequence.
Modify any company-specific programs accordingly.
1.1.2.1.4 Settings for Media Products in Series Sales (New)

Use
As of SAP Media 4.72, you can define series characteristics and strategies for use when processing series
sales.
Series Characteristic
The series characteristic is the central Customizing object in the master data for series sales. It determines
certain factors as regards processing of the series; for example, whether or not backdated orders are
possible. You must specify a series characteristic for each media product that is used in series sales. The
series charactieristic groups the shipping characteristic and specifications on the use of the planning
records for media issue deliveries (from contracts) under a unique key.
o
Shipping characteristic
The following three shipping characteristics are possible:
-
Type 1 - Issue must be specified in shipping plan. The issue must not be in an issue sequence.
The next issue can, for example, be determined manually using marketing methods.
Type 2 - Issue is determined from the issue sequence defined. Shipping planning records are
created automatically when an issue is added to the issue sequence. You can only change the
attributes of the shipping planning records.
Type 3 - Issue cannot be specified. The subsequent issue is determined from the customer's
specific history, which means that it can differ for each customer.
Planning records for media issue deliveries

If shipping characteristic type 2 is specified for the series characteristic, you can use planning
records for media issue deliveries (from the contracts). These planning records determine the time
sequence of the planned issues for a series contract.
Backdated issues
Indicates whether or not backdated issues are possible. These are transferred to the planning
function for the media issue deliveries.
______________________________________________________________
SAP AG
17
SAP System
______________________________________________________________
Strategies
The behavior of the order generation function is determined by means of strategies. You define the
strategy for determining the next issue, for determining any additional issues required, and for controlling
further operations, in the media product. For details on strategies, see Order Generation for Series Sales.
Edit the series characteristics and strategies in the Customizing settings for series sales.
1.1.2.1.5 Series Combinations (New)

Use
As of SAP Media 4.72, you can define packages of different media products for series sales. You can do
this using the transaction Series Combination. For example, you could include the issues of media
products B and C in the package for media product A. A customer who purchases the package Media
Product A also receives all the issues of media products B and C.
Structure of 'Series Combination' Transaction
The Series Combination transaction allows you to edit components of mix type definitions. You can
select by media products. All the mix type definitions that contain the specified media products are
displayed in a structure tree. If an issue sequence exists for the media product, this is indicated by a flag.
You can add or delete assignments and display the issue sequence (if there is one) by means of the
context menu.
1.1.2.2 IS-M-MD-PR-B
Booking
1.1.2.2.1 BAPIs for the Booking Unit (New)

Use
The Advertising Management Booking Unit (BUSISM024) BOR object has been created in SAP Media
4.72. The following methods have been created for this BOR object:
o
GetDetail (Read booking unit)
GetList (Select booking unit)
ExistenceCheck (Check existance of booking unit)
Display (Display booking unit)
Create (Create booking unit)
Refer to the Sale of Display Classified Ads release note.

See also
______________________________________________________________
SAP AG
18
SAP System
______________________________________________________________
Additional information on BAPIs is available in the SAP Library under SAP R/3 Enterprise Components
-> Cross-Application Components -> Business Framework Architecture.
1.1.2.2.2 BAPIs for the Content Component (New)

Use
The Advertising Management Content Component (BUSISM025) BOR object has been created in SAP
Media 4.72. The following methods have been created for this BOR object:
o
GetDetail (Read content component)
GetList (Select content component)
ExistenceCheck (Check existance of content component)
Display (Display content component)
Edit (Change content component)
Create (Create content component)

See also
1.1.2.2.3 Document Management for SAP Media Business Objects (New)

Use
______________________________________________________________
SAP AG
19
SAP System
______________________________________________________________
business partner.
o
Create folder
Create document
Create URL

Display document

corresponding data.

Delete original
Export
in the Explorer.
Export with block

place.
Import new version

______________________________________________________________
SAP AG
20
SAP System
______________________________________________________________
Versions.
o
Cut, copy and paste

Search
Where-used list
evaluated here
Send
more recipients.

o
Document preview
Copying Orders
o
______________________________________________________________
SAP AG
21
SAP System
_____________________________________________________________

system


o
HTTP Content Server

R/3 database

______________________________________________________________
SAP AG
22
SAP System
______________________________________________________________
OACT.
1.1.2.2.4 Internet Publication of a Print Ad (New)

Use
As of SAP Media 4.72, you can specify the Internet positioning of a print ad in the master data for an ad
basic booking unit. This information is updated in the order and transferred to a production system.
o
You can use the Web Publication indicator to define the basic booking unit as the booking unit for
the Internet publication in the technical view (screen Technical View for the Basic BU).
You can also specify the start and end date of the period for the Internet publication on the screen
that describes the assignment of content components in technical terms (screen Technical Content
(AD). You specify this period relative to the publication date.
The system uses these settings to determine start and end date of the period for the Internet publication
when it generates the schedule lines.
To ensure that this information can be transferred to a production system, the period for the Internet
publication and the Web Publication indicator have been included in the RJHATPS structure for the
IS-M/ITA technical interface and the structures for the following BAPIs:
o
BUSISM008 business object (Advertising Management sales document)

-
GetDetail (Parameter SCHEDULE_LINE_AD)
CreateFromData (Parameter SCHEDULE_LINE_AD_OUT)
Change (Parameter SCHEDULE_LINE_AD_OUT)
BUSISM008P business object (Advertising Management external sales document)
______________________________________________________________
SAP AG
23
SAP System
______________________________________________________________
Save (Parameter SCHEDULE_LINE_AD)
1.2 IS-M-BF
Basic Functions
1.2.1 IS-M-BF-PR
Pricing
1.2.1.1 Order Pricing with Scale Base Contract (Enhanced)

Use
As of SAP Media 4.72, the assignment of scale conditions in the order can be dependent on specific
attributes in the assigned scale base contract. To do so, the RJHKOMP5 structure must be enhanced using
a customer append. The contract data is used to make entries in the customer-specific fields in the
SCALE_BASE_COMM method in the ISM_AM_CONTRACT BAdI. These fields can be evaluated in
a pricing requirement. Replace requirement 515 that is used in the Customizing settings with an enhanced
requirement in the customer name space.
The COMPRESS_KOLNR method in the ISM_AM_CONTRACT BAdI can be used as of Release 4.72
to perform several accesses in an access sequence, which all use the scale base for the same scale base
contract.
The condition screen in the maintenance dialog for scale base contracts has also been enhanced so that
condition types, which are linked with requirement 515 in the pricing procedure used, can now also be
displayed.
Implement the ISM_AM_CONTRACT BAdI if necessary.
1.2.1.2 More Flexible Base for Contract Discount and Bonus (New)
Use
As of SAP Media 4.72, you can specify reference levels for the discount and bonus contract conditions in
the pricing procedure for the order/billing document. This defines the base for percentage discount or
bonus.
Prior to Release 4.72, condition base formula 572, which is used for contract discount and bonus, always
based the condition base on the net value, so that the base for the bonus had already been reduced by the
value of the discount. You can now enter the level number of the assessment base (condition type
BEMG) as the reference level for the bonus (condition type BOAB), so that the full value is used for the
bonus. Condition base formula then only bases the condition base on the net value if no reference level
has been specified.
The system observes any reference levels you have specified for condition types with condition base
______________________________________________________________
SAP AG
24
SAP System
______________________________________________________________
formula 572. System response is otherwise unchanged.
1.3 IS-M-CA
Contract Accounts Receivable and Payable
1.3.1 Extraction of Tax-Relevant Data for GDPdU (Changed)

Use
As of SAP Media 4.72, you can extract tax-relevant data from Subscription Sales and Distribution to
FI-CA. In addition to FI-CA documents, you can now also extract billing documents and service
settlements.
Extraction of Tax-Relevant Data
On 01.01.2002, the Principles for Data Access and Verifiability of Digital Documentation (GDPdU)
came into force in Germany. These new legal requirements - that exist, for example, in similar form in
France and Switzerland - have been implemented in Contract Accounts Receivable and Payable. This
means that you can now provide the auditors from the tax office with all tax-relevant data as follows:
o
Access 1: Immediately in the online system (Z1)
Access 2: Immediately in the online system or via reports (Z2)
Access 3: To data media that can be evaluated automatically (Z3)
You can restrict the auditors' access to the saved data to a specific period using an extended authorization
concept.
Since the tax-relevant data cannot be saved permanently in the production system for data access due to
the large quantity of data in Contract Accounts Receivable and Payable, you can extract the data before
archiving and transfer it to a separate system which is exclusively for the government tax audit. Based on
the data held in this system, you can carry out analyses and create extracts that you then provide to the
auditor in a data medium that can be evaluated automatically (access 3).
Due to the mass data processed in Contract Accounts Receivable and Payable, the SAP Data Retention
Tool (DART) cannot be used to create data extracts. For all releases in maintenance, Contract Accounts
Receivable and Payable therefore provides own extractors. In the first step, an FI-CA document extractor
is provided, which you can use to extract also industry- and customer-specific fields and carry out field
transformations in events. In the second step, SAP industry solutions that use Contract Accounts
Receivable and Payable can add additional extractors to this Basis function.
See also the release information for the Information System.
Extracting Documents from Subscription Sales and Distribution
The FI-CA documents in the production system are extracted by report RFKK_DOC_EXTR_EXP. You
can now use event 9556 in this report to extract billing documents and service settlements to the file
system.
In the evaluation system, you can use report RFKK_DOC_EXTR_IMP to extract the data from the file
system and transfer it to special database tables. This can be done for billing documents and service
settlements using event 9557. The data is transferred to the following database tables:
______________________________________________________________
SAP AG
25
SAP System
______________________________________________________________
Billing document: FKK_JFRK_SHORT, FKK_JFRP_SHORT, FKK_KONV_SHORT
Commission settlement: FKK_JLRK_SHORT, FKK_JLRPCM_SHORT, FKK_KONV_SHORT
Home delivery settlement: FKK_JLRK_SHORT, FKK_JLRPHD_SHORT, FKK_KONV_SHORT
Event 9558 can be used to delete the data from the database tables.
You can then use report RFKK_DOC_EXTR_EXTR to export the data in the evaluation system. This can
be done using event 9555.
SAP provides a standard implementation ISM_EVENT_955n for all the events.
Caution: Before archiving billing documents and service settlements, you must extract this data together
with the FI-CA documents.
1.3.2 Additional Payments for Renewals (New)

Use
As of SAP Media 4.72, you can record additional payments for renewal subscriptions. The following
types of additional payment are possible:
o
Donation (for example, to charity)
Tip (for carrier)
You can only use the function for processing additional payments if you use Contract Accounting
(IS-M/CA).
The process for additional payments comprises the following steps:
o
Post payment to subscribers contract account

A posting document is characterized by the main transaction 3100 and the special clearing
restriction 4. Depending on the payment method, you can post additional payments in the following
two ways:
-
If payment is made by check, the additional payment is made as it was previously in IS-M/CA,
by means of a separate line item (see also IS-M/CA Integration - Incoming Payment Triggered
by Customer).
New: To make the posting under the reference number from the renewal subscription, you can
set up a special selection category for each additional payment type.
If payment is made using a payment card or by automatic debit, you can enter template data for
the additional payment in the liability account overview for a renewal subscription. When the
renewal offer is accepted, the sum of the offer amount and additional payment amount is
authorized.
The additional payment is recorded in a separate condition record in the billing document.
When the billing document is transferred, two accounting documents are created in IS-M/CA:
the receivable for the offer amount (main transaction 4000) and the additional payment request
(main transaction 4100, statistics key A). Both these documents are cleared by the payment run
and the clearing document gives rise to an actual additional payment (main transaction 3100).
______________________________________________________________
SAP AG
26
SAP System
______________________________________________________________
Execute transfer posting (see Transfer Posting Report) based on the documents created in the first
step
Effects on Data Transfer

You can use report RJKFTRSF with the new record type 12 to transfer template data for the additional
payment together with the renewal subscription from the legacy system.
If you want to use this function, you must make the following settings in Customizing:
o
Define possible additional payment types
Set up pricing (condition types, requirements, check formulas, enhance pricing procedure)
Define account assignment keys
Assign G/L accounts
Define main transactions/subtransactions
Define possible selection categories
See also
Refunds for Renewals
1.3.3 Transfer Postings of Additional Payments and Refunds in Renewals (New)

Use
As of SAP Media 4.72, you can transfer the following documents, which the system posted to the
subscribers' contract accounts in IS-M/CA, to other business partners' contract accounts in renewals
processing:
o
Additional payments (see Additional Payments in Renewals)
Refunds (see Donating Refunds)
You can do this using the report RJK_ADDPAYMENT_REBOOKING_SAMPL.

The recipient (business partner and contract account) is determined according to the additional payment
type or refund type.
If the refund is to be used as a tip for a carrier, the carrier who is active on the posting date is determined
by means of a standard BAdI implementation.
Organizations for donations are also determined by means of a BAdI, but a standard implementation is
not required in this case.
The report supports the following execution options:
o
Test run
Update run
Worklist
______________________________________________________________
SAP AG
27
SAP System
______________________________________________________________
Check list
If you want to use this function, you must define the transfer reasons in Customizing.
1.3.4 Account Balance Display

Use
Restriction of Item Selection
If you select the button Period for Item Selection (F7) on the initial screen of the account balance
display, you can restrict the period that the system uses for selecting the items in the account balance.
Context Menu in the Account Balance
You can call up a context menu by clicking on the right mouse button when the cursor is on an item in the
account balance. In events 1247 and 1248, you can adjust the functions of the context menu to meet your
requirements or add to them.
Define the required function modules for events 1247 and 1248 in the Implementation Guide for Contract
Accounts Receivable and Payable under Program Enhancements -> Define Customer-Specific
Function Modules.
1.3.5 Archiving for Tax Reporting Argentina (Changed)

Use
As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), the following new archive
info structures for archiving objects FKK_GENREP, FKK_GENREV, and FI_MKKGENS are delivered
and must be used for Argentina:
o
SAP_FICA_ARREP1
SAP_FICA_ARREV1
SAP_FICA_ARRES1
You must use these info structures in conjunction with the following function modules:
o
FKK_AR_EVENT_0515
FKK_AR_EVENT_0520
FKK_AR_EVENT_0525
The system calls these function modules to include Argentina-specific fields from the tax reporting tables
in the archive info structures above. Only by using these info structures with these function modules do
you ensure that the system correctly connects the Argentine tax reports to the archive.
______________________________________________________________
SAP AG
28
SAP System
______________________________________________________________
You need to assign the above function modules to each of the relevant tax events: 0515, 0520, and 0525.
You do so in Customizing for Financial Accounting, under Contract Accounts Receivable and
Payable -> Basic Functions - > Tax Reports -> Tax Reporting - Argentina -> Basic Settings ->
Activate Recording of Tax Data.
1.3.6 Archiving
Use
Document Archiving
In future, the program for archiving documents (RFKKAR10)
checks whether the balance of the document is zero (check DOCUMENT-01).
Two new events are available:
o
In event 0501 you can check document headers in blocks.
In event 0505, you can carry out installation-specific checks at document level.
If you need data from other tables for the document check in event 0505, you should read this data in
advance in event 0501 in order to avoid adverse effects on performance. In event 0501, you can select all
of the data required for the documents transferred and save it to the local memory. This means that you
can carry out all additional checks for event 0505 with no individual database access.
The archiving log of the document archiving device has been change over to the Archive Development
Kit (ADK) standard log. You can now no longer display the details of documents that cannot be archived
in the detailed error log. Instead, click on the document number in the detail log to go to the document
display.
The number of archived entries in the individual tables is no longer displayed for the individual
documents. These totals are now only displayed for all archived documents. However, you can display
the archive entered before deletion using the Archive File Browser (transaction AS_AFB) and thus
check the archived structures/content.
Archiving Information about the Foreign Currency Valuation
You can use the new archiving object FI_MKKVAL to archive the data that arises from the foreign
currency valuation. The prerequisites for the archiving are described in the documentation for report
RFKKAR36.
Archiving Clearing Histories
You can archive clearing histories with the new archiving object FI_MKKPCR. The prerequisites for the
archiving are described in the documentation for report RFKKAR41.
Archiving of Doubtful Entries
You can archive data for doubtful receivables with the new archiving object FI_MKKDRVA. The
prerequisites for the archiving are described in the documentation for report RFKKAR44.
Archiving of Transfer Records for Invoicing by Third Parties
______________________________________________________________
SAP AG
29
SAP System
______________________________________________________________
You can use the new archiving object FI_MKKTHI to archive data fo invoicing by third parties (see also
documentation for report RFKKTHPAR01).
1.3.7 Authorization Objects

Use
Maintaining Interval Variants
With authorization object F_KKVARI, you can restrict the authorizations for maintaining interval
variants:
o
In the field OBJECT_KK, define the authorization for individual objects, such as GPART and
VKONT.
In the field ACTVT, you can control the authorizations for the following activities:
Activity
01
02
03
06
07
Description
Create variants
Change variants
Display intervals
Delete variants
Generate variants
New Authorization Object F_FKKCJ for the Cash Journal

The authorization object F_FBCJ, which controls the authorizations for the cash journal, has been
replaced by the authorization object F_FKKCJ.
In the field ACTVT, you can control the authorizations for the following activities:
Activity
01
02
03
10
Description
Add or create
Change
Display
Post
33
B5
Read
Display history
If you cannot change over to the authorization object F_FKKCJ in the cash journal quickly, see SAP note
667984. This note contains a description of how you can continue to use the old authorization object
F_FBCJ in the FI-CA Cash Desk. Note that you should deactivate this temporary solution as soon as
possible. After Release 4.72, SAP will only support the authorization object F_FKKCJ.
______________________________________________________________
SAP AG
30
SAP System
______________________________________________________________
1.3.8 BAPIs in Contract Accounts Receivable and Payable

Use
Requests
You can now use new BAPIs for the business object CA_REQUEST to process requests. The following
methods are supported:
Create
BAPI_REQUEST_CREATE
Create request
Getdetail
BAPI_REQUEST_GETDETAIL
Read request
Change
BAPI_REQUEST_CHANGE
Change request
Delete
BAPI_REQUEST_DELETE
Delete request
EasyCreate
BAPI_REQUEST_EASYCREATE
Create request with template
AddPeriods
BAPI_REQUEST_ADDPERIODS
Add execution periods for request
DeletePeriods
BAPI_REQUEST_DELETEPERIODS
Delete execution periods for a request
AddSpecialDates
BAPI_REQUEST_ADDSPECIALDATES
Add special dates for request
DelSpecialDates
BAPI_REQUEST_DELSPECIALDATES
Delete special dates for a request
AddLineItems
BAPI_REQUEST_ADDLINEITEMS
Add request items
DelLineItems
BAPI_REQUEST_DELLINEITEMS
Delete request items
______________________________________________________________
SAP AG
31
SAP System
______________________________________________________________
Changes to the BAPIs for FI-CA Documents

The parameters ItemRelation and CardData have been added to the BAPI CtrAcDocument.Create,
The parameters DocumentHeader and DocumentHeaderX have been added to the BAPI
CtrAcDocument.Change
New BAPI for Contract Accounts
From Release 4.72, you can use the new BAPI CtrAcContractAccount.GetOpenItems.
Changes to the BAPI for Contract Accounts
The selection field in the parameter ValueSelektions has been extended.
1.3.9 Boletos
Use
Creating Boletos
To improve the performance of the program for creating Boletos, you can use the payment method to
restrict the selection of open items.
If you also consider statistical documents in Boletos, you can delete or integrate the required statistical
documents in event 6303 (see FKK_SAMPLE_6303).
Mass Reversal of Boletos
You can now use a mass reversal transaction (FPO1C) for Boletos created by a mass run (see SAP menu:
Periodic Processing -> For Contract Accounts -> Boleto).
You select the run to be reversed using the run date and the run ID for the creation run. After the reversal,
you can create new Boletos for the open items in the reversed Boletos. The system automatically records
the new run date and run ID for the payments assigned to the banks during the creation of the Boletos.
Creating Boletos Online
In the transaction Create Boleto from Open Items (FBO1S), you can create Boletos online. To do this,
select the required open items manually by business partner, contract account, and document number and
specify the bank and account to which the payment is to be made.
This transaction is particularly useful for installment plans. You can select the individual installment plan
items by business partner, contract account, payment method, and due date and create one Boleto for
these items.
The system assigns the run date and run ID automatically and saves this data in the header of the Boleto.
The payment assigned to the bank is updated in table DFKKBOL_BANKID.
You make the settings for creating Boletos in the Implementation Guide for Contract Accounts
Receivable and Payable under Business Transactions -> Payments -> Creation of Incoming and
Outgoing Payments -> Boleto.
______________________________________________________________
SAP AG
32
SAP System
______________________________________________________________
1.3.10 Business Information Warehouse

Use
Extracting Open Items
During the evaluation of receivables balances in the Business Information Warehouse (BW), you can
now simulate the clearing of credits with the oldest open receivables for a business partner.
The credits are only cleared if the transaction currency of the receivables and the credits to be cleared is
the same.
In event 2506, you can determine which of the following data has to agree for the credits to be cleared:
o
Company code
Business area
General ledger account
If you do not define the event individually, clearing only takes place if the company code and the general
ledger account are the same for the receivable and the credit.
In the simulation, the due date of the credits is fixed to the due date of the receivables cleared. This
means that when the items are totaled and sorted, the status is the status that would be reached if the
credits were cleared with the oldest receivables due. If a credit memo is to be distributed over several
receivables, the extractor simulates several fictitious items.
The restriction by business partner has been added to the extraction of open items. This means that you
can now restrict the extraction of open items to a subset of business partners before the open item
analysis. You can use event 2504 to restrict the quantity of business partners selected. The functions of
event 2505 have also been enhanced to enable you to exclude combinations of business partner, contract
account, and contract (GPART/VKONT/VTREF) that are not required from the extraction quantity. The
system recognizes the runs to be restricted from the naming convention used in the event modules. The
fields LAUFD and LAUFI have been added to the interface of event 2505 for this purpose.
Extracting Installment Plan Data
You can use a new mass activity to extract installment plan data for the evaluation in the Business
Information Warehouse (BW). The data can be extracted either with or without consideration of
previous extractions (delta queue).
As standard, only the most important data for the installment plan headers, installment plan items, and
original items is extracted. However, you can extend the extract structures. You can use events 2525 and
2530 to read additional data and fill additional fields in the extract structures.
1.3.11 Payment at Cash Desk

Use
General Ledger Account Postings In the cash desk (Short Account Assignment)
______________________________________________________________
SAP AG
33
SAP System
______________________________________________________________
The function for transferring incoming and outgoing payments in the Cash Desk has been enhanced and
you can now carry out the transfer postings with a tax on sales and purchases part. The field Tax Code
has been added to the area G/L Account Posting on the tab page Specifications for Payment on the
initial screen of the Cash Desk. The following fields have been added to the Customizing activity Define
Short Account Assignments for Transfer Postings in the Cash Desk:
o
Tax on Sales and Purchases Code

Here you can define a tax code for each short account assignment key, that is, each G/L account
posting.
Authorization Group
With the authorization group you can assign specific authorizations to allow a clerk, for example, to
use only certain short account assignment keys. Maintain the authorization via authorization object
F_KK_KUKON.
Barcode Scanner
With Release 4.72, the connection of barcode scanners has been implemented in the cash journal and the
Cash Desk.
In the Customizing activity Maintain Specifications for Cash Desk/Cash Journal, you can define whether
the barcode entry field is to be displayed or hidden. If the barcode entry field is available, you display or
hide the field dependent on the workplace via the Cash Desk menu Extras -> Barcode Entry ->
Display/Hide. In the menu under Extras -> Hold Settings, you can save the settings user-specific.
The barcode scanned must be interpreted in event FKK_SAMPLE_6050 and the data required for the
entry must be entered on the input screen for the cash desk/cash journal.
You make the system settings in the Implementation Guide for Contract Accounts Receivable and
Payable under Business Transactions -> Payments -> Processing Incoming/Outgoing Payments
-> Cash Desk/Cash Journal.
1.3.12 Cash Journal

Use
Reversing Withdrawals
In the cash journal menu under Edit, you can use the function Reverse Withdrawal to reverse
withdrawal documents. This function does not just reverse the document; it also corrects the cash desk
balance.
Barcode Reader
From Release 4.72, you can connect a barcode reader in the cash journal and the cash desk. In
Customizing, you can define whether the barcode entry field is to be hidden or displayed. If the barcode
entry field is available, you display or hide the field dependent on the workplace via the Cash Desk menu
Extras -> Barcode Entry -> Display/Hide, provided the workplace has a barcode reader. In the menu
under Extras -> Hold Settings, you can save the settings user-specific.
The barcode read is interpreted in event 6060. Enter the data required on the input screen for the cash
______________________________________________________________
SAP AG
34
SAP System
______________________________________________________________
desk or the cash journal. For more information, see the sample function module FKK_SAMPLE_6060.
Posting Areas 0150 and 0160
The field Payment Type has been added to the posting areas 0150 - Cash Journal: Specifications for
Posting Cash Desk Differences - and 0160 - Cash Journal: Bank Clearing, Deposit, and
Withdrawal Accounts. You can define a separate cash desk clearing account per payment type:
CS
CP
CH
PO
CO
Incoming and outgoing cash payment

Credit card payment
Incoming check payment
Postal order payment
Outgoing check payment
The introduction of the new payment type CO for outgoing check payments means that you can now
define separate cash desk clearing accounts for incoming and outgoing check payments. Make sure that
you also enter the cash desk clearing accounts that you enter here in the activity Define Bank Clearing
Accounts for Payment Lots and that they are as follows:
Validity for the Corresponding Lot Types
PymtType PymtLot
CS
X
CP
CH
PO
CO
CheckLot
CardLot
Online Check
X
X
X
X
Maintain Specifications for Cash Desk/Cash Journal

From Release 4.72, you can make the specifications for the cash desk and the cash journal together in the
activity Maintain Specifications for Cash Desk/Cash Journal.
1.3.13 Closing Operations

Use
Summarization Accounts and Summarization Company Codes for Reclassifications
You can now display reclassifications for a group of accounts or company codes - previously, you could
only display the reclassifications in the balance of one receivables or payables account of a business
partner within a company code.
Summarization accounts are required for key date-related open items whose receivables and payables
accounts are displayed in one item in the financial statements (for example, same type of legal transaction
for several utility provider divisions in the case of different receivables accounts per division).
______________________________________________________________
SAP AG
35
SAP System
______________________________________________________________
Summarization company codes are required where company codes are in the legal entity that has to create
the financial statements (for example, consolidated financial statements).
See the release information for Foreign Currency Valuation and Evaluation of Open Items.
Summarization Accounts and Summarization Company Codes for Reclassifications
You make the specifications for reclassification by summarization company codes and accounts in the
Implementation Guide for Contract Accounts Receivable and Payable under Closing Operations ->
Reclassifications.
1.3.14 Submission of Receivables to Collection Agencies

Use
The following functions have been added to the submission of receivables to collection agencies:
o
Derivation of collection agency responsible
Deletion of submission logs
Derivation of Collection Agency Responsible

If you want to release receivables to different collection agencies using rules in your organization, from
Release 4.72, you can define these derivation rules in Customizing for Contract Accounts Receivable and
Payable.
The derivation rules defined in Customizing are evaluated by the derivation tool. The derivation tool is
always called in the function module FKK_COLL_AG_SAMPLE_5060 if items are released for
collection individually in transaction FP03E or in the mass release via transaction FP03M. The derivation
tool determines the relevant collection agency in one or more derivation steps from a sequence of source
fields of the enhanceable structure FKKCOLLAG. The number of derivation steps corresponds to the
number of derivation rules that you define in Customizing.
Deletion of Submission Logs
You can now delete logs recorded in table DFKKOPCOLL by the mass run for submitting receivables to
collection agencies (FP03M). You can do this with transaction Delete Submission Logs (FP03DML)
(see SAP menu: Periodic Processing -> Delete Data).
You define the derivation rules for the responsible collection agency in the Implementation Guide for
Contract Accounts Receivable and Payable under Business Transactions -> Submission of
Receivables to Collection Agencies -> Define Derivation Rules for Responsible Collection Agency.
1.3.15 Collective Bills

Use
______________________________________________________________
SAP AG
36
SAP System
______________________________________________________________
From Release 4.72, you can group documents from different contract accounts in a collective bill
document in order to process them together. You can manage and process all of the individual documents
in a collective bill together via a third account the collective bill account. You can create a joint invoice
and make the payment or in the case of payment arrears, dun all of the items in the collective bill
together.
Collective bills are particularly useful, for example, for billing property and house building companies
that process receivables from utilities companies for their tenants, and for companies with branch-head
office relationships.
At master data level, you have to assign the individual contract accounts to a collective bill account. A
collective bill account is a contract account of the contract account category collective bill account. You
have to define this account in the master record of every contract account whose postings you want to
group in a collective bill. There is no change to the assignment of contract accounts that you link via the
collective bill account to your business partners. To link an account with the collective bill account:
1.
In the SAP menu choose Contract Account -> Create or Change.
2.
In the field Collective Bill Account in the area Invoice Creation on the tab page General Data,
enter the required collective bill account.
Once you have assigned the account to a collective bill account, when you enter posting documents in
this account, each business partner item is automatically linked to a statistical posting document
(collective bill document) in the collective bill account.
To use collective bills, you have to carry out the following in the Implementation Guide for Contract
Accounts Receivable and Payable:
o
Under Program Enhancements -> Define Customer-Specific Function Modules, enter

FKK_COLL_BILL_CREATE_0063 for event 0063, provided this module is not already integrated
in the industry-specific module for event 0063.
In the industry components Utilities and Telecommunications, this module is already integrated in
the industry-specific module for event 0063.
Under Basic Functions -> Contract Accounts -> Number Ranges and Contract Account
Categories -> Configure Contract Account Categories and Assign Number Ranges, enter a
contract account category for collective bill accounts.
Set the indicator in the column CB (contract account is collective bill account) and assign a
number range to the contract account category.
Under Basic Functions -> Postings and Documents -> Document -> Maintain Document
Account Assignments -> Document Types -> Maintain Document Types and Assign
Number Ranges, create a document type for collective bill documents and assign a
number range to this document type.
Under Basic Functions -> Postings and Documents -> Document -> Maintain Document Account
Assignments -> Maintain Default for Document Type for Collective Bill, define the document type
that you defined in the previous step as the default for creating collective bill documents.
The main and subtransaction for the collective bill item are determined in event 2222. You can overwrite
industry definitions implemented for this event. This event has already been defined for the industry
______________________________________________________________
SAP AG
37
SAP System
______________________________________________________________
component Utilities.
1.3.16 Company Codes

Use
Replacement of the Responsible Company Code in Contract Accounts Receivable and Payable
Previously, the responsible company code had the following control characteristics in FI-CA:
o
It determined the company codes in which you could post to a contract account
It was the company code in which payment transactions were processed
It was (regardless of Customizing) the company code in which payments on account were posted
The coupling of these functions heavily restricts the options in some areas and leads, for example, to you
having to introduce auxiliary company codes to portray the organizational model.
From Release 4.72, the responsible company code is replaced by the following three new entities:
o
Company code group

The company code group includes all company codes that are permitted for posting to a company
account. One company code group is assigned to each contract account. Company code groups can
overlap. This means, for example, you can have a group G1 that consists of company codes 0001,
0002, and 0003, and group G2 that consists of 0001 and 0003.
Paying company code

Exactly one paying company code is always assigned to each company code group. A paying
company code is responsible for payment transactions. You have to define house banks and
payment methods for paying company codes. Several company code groups can have the same
paying company code. The paying company code does not have to be in the company code group
itself.
Standard company code

One standard company code is assigned to every contract account. You use the standard company
code for all postings for which no company code can be determined by other means (for example,
for payments on account).
Transition from Responsible Company Code to the New Entities

The conversion of the responsible company codes to company code groups and paying company codes
takes place automatically during the first check (contract account or document) where you check the
validity of a company code group or where the company code group is a prerequisite.
For each responsible company code, the system creates a company code group with the same key. The
company codes that were previously assigned to the responsible company code are assigned to this
company code group. The responsible company code is assigned as the paying company code for the
group. This ensures continuity for the existing organizational model.
The name of the responsible company code is taken as the name for the company code group. Since the
new name is language-dependent, it is automatically created in all languages used in the installation. The
languages are determined empirically by analyzing the document type texts.
Changes to the Contract Accounts
______________________________________________________________
SAP AG
38
SAP System
______________________________________________________________
For new contract accounts, the company code group and standard company code are mandatory
requirements. For existing contract accounts, you can use conversion report RFKKSTDBK to add the
standard company code. The standard company code receives the value of the former responsible
company code. You can convert the contract accounts in stages you do not have to convert them all at
once. The system handles accounts that you have not yet converted as if you had converted them.
Changes to Checks in Contract Accounts
The validity of certain fields was previously coupled to the combination with the country of the
responsible company code. The following changes have occurred in these checks:
o
The country from the paying company code of the company code group is used for:
-
Payment methods
Own bank details
The country of the standard company code is used for:

-
Withholding tax codes
Region
County code
Tax exemptions
Restrictions for Company Code Groups

Using the new event 1010, you can check whether a company code group is permitted in a contract
account. This enables you to prevent, for example, that cross-country groups (in certain contract
accounts) are used.
Authorization Check
In the authorization object F_KKVK_BUK, the responsible company code was used for the check in the
master data maintenance. The standard company code is now used instead.
Payment Program
You can also specify the paying company code in a business partner item. In this case, this specification
overrides the paying company code determined via the company code group of the contract account. If a
paying company code specified in the line item is in a different country to the paying company code
determined via the contract account, you also have to specify a payment method in the line item. In this
case you cannot use the payment methods from the contract accounts since they refer to a different
country.
In the parameters for the payment run/debit memo run, you restrict the company codes to be processed.
All relevant company code groups and their paying company codes are determined for the company
codes internally. If these are in different countries, the country of the payment run must be assigned via a
different parameter. In a payment run, you can still only create payments for one country.
You define the company code groups in the Implementation Guide for Contract Accounts Receivable and
Payable under Organizational Units -> Define Company Code Groups.
You assign the company codes to the groups under Organizational Units -> Assign Company Codes
to Company Code Groups.
______________________________________________________________
SAP AG
39
SAP System
______________________________________________________________
1.3.17 Creating Correspondence

Use
Balance Notification
You can use event 9552 to create balance notifications. In this event you decide whether a balance
notification is to be created.
Requests and Standing Requests
To print requests and standing requests, you can use events 0766: Print Request and 0767: Create Request
Printout, and correspondence type 0039 Request (see also the release information for Requests).
You define customer-specific function modules in the Implementation Guide for Contract Accounts
Receivable and Payable under Program Enhancements -> Define Customer-Specific Function
Modules.
1.3.18 Connection of SAP Dispute Management to Contract Accts Rec. and

Pay.
Use
From Release 4.72, you can create and manage complaints (disputes) from your business partners with
regard to incorrect invoices and credits or missing invoices and credits as dispute cases in a dispute
system as part of SAP Dispute Management. These dispute cases contain attributes, such as the reason
for the complaint, the priority, the disputed amount, the clerk responsible for resolution, and contact data
of the business partner. During the processing of the dispute case, you can trigger functions such as the
reversal of an invoice, write-offs, and postings of invoice-related credits. From the dispute case you can
display the follow-on postings for the case. To get an overview, you can display a list with all dispute
cases for a business partner or document.
Definition of terms used
Dispute System
The system in which the dispute cases

are created and managed.
FI-CA System
The system in which

Contract Accounts Receivable and Payable runs.
Dispute Case
The complaint of the business partner as

object to be managed in
SAP Dispute Management. The dispute case
contains attributes such as the amount, data
______________________________________________________________
SAP AG
40
SAP System
______________________________________________________________
about the status of processing and for

categorizing the dispute as well as,
in the record, a list
of related objects to which the
case references (for example, document, invoice
business partner, contract, contract account).
Case Type
The following case types are

differentiated:
- FICA: Incorrect invoice, incorrect credit
- FCA2: Missing payment
The case types are differentiated by
their attributes. A dispute case
of the case type Missing Payment describes, for
example,
the case when a customer complains about a dunning
notice
that was executed despite payment having been made.
The clerk's job is to
find this payment, which may have been incorrectly
assigned,
and potentially reassign it
and then close the case. With
a dispute case of the case type
Incorrect Invoice, the customer has complained
about an incorrect
invoice amount. Here the clerk has
to check the amount
and trigger any adjustment postings,
such as reversals, write-offs, or
credits.
Internal Dispute Type
Internal categorization
of a dispute case that each
dispute case must have.
Since the system behaves differently in
different case types,
and each customer can create
installation-specific case types,
______________________________________________________________
SAP AG
41
SAP System
______________________________________________________________
an internal categorization
(assignment) is necessary. Thus, the
dispute type A001, for example, is an incorrect
invoice, and dispute type B001 is a
missing payment.
Creating Dispute Cases
Dispute cases are created from the dispute system. However, you can also create dispute cases in the
FI-CA system.
In the document display, you can use the function Create Dispute Case to create a dispute case. A
dialog box appears, where you can set the default values defined for event 1250. For a sample form of
event 1250, see sample function module FKK_SAMPLE_1250.
The specification of a business partner is mandatory in each dispute case; the specification of a contract
account and contract is option and determines the level of detail of the dispute case. The system includes
the document displayed as a disputed document in the case. The data and amounts of the document are
used to determine the default values.
Dispute cases are only created at document level, not at line item level. You can create several dispute
cases for one document.
You can create a dispute case from the account balance. This enables you to create dispute cases without
an invoice reference, for example, for cases of the type Missing Payment after Dunning Notice. The same
dialog box appears for creating the case. Enter the amount specified by the customer as paid as the
disputed amount; then assign the case to a business partner.
When you create a dispute case, the system proposes contact data of the contact person, such as name and
e-mail address from the address data of the business partner; you can overwrite this data.
Displaying Dispute Cases
In the document display, you can use the function Display Dispute Case to display invoice-related
dispute cases. However, this function is only active if such a dispute case exists. If, for example, you have
entered various disputed partial amounts for various reasons, you can simultaneously create several
dispute cases for one document. If there are several dispute cases for one document, the system first
displays an overview of all cases, and there you can select the case you want to display. If you create a
new dispute case for a document for which a dispute case already exists, the system notifies you of this
before sending the dialog for creating a case.
In the account balance you can display an icon on which you can double-click to display a dispute case.
To do this, include the field IDISP (placeholder for icon Dispute Case) in a line layout variant for items
whose document number is included in a dispute case. You also have to set the indicator Field-Sensitive
Double-Click in the settings.
With the function Environment -> Account -> Dispute Case -> Display in the menu of the account
balance display, you can display a list of all of the dispute cases for the business partner/contract account.
With report RFKKDM00 you can select dispute cases across all business partners and contract accounts.
This report provides additional selection options to the master data.
Changing Dispute Cases
______________________________________________________________
SAP AG
42
SAP System
______________________________________________________________
When you display a dispute case you can use the function Change to switch the mode and therefore
change a dispute case. However, from the FI-CA system you can only change the disputed amount. With
case type Incorrect Invoice, you can include additional documents in the dispute case.
With the case type Missing Payment, the payments received since the creation of the dispute case are
listed on the lower part of the screen. The system only adds the payment amounts posted in the dispute
case via the payment lot as potential candidates for the missing payment, since you can assume that
payments posted by the payment program cannot be #missing#. From this list of payments you can create
one or more payments, identify them as missed, and assign them to the dispute case. The case can then be
closed in the dispute system.
In the dispute system, an amount field with the total of all potentially suitable payments received since
the creation of the case is managed before the assignment of the payment found. With the assignment of
the payment found, the document number of this payment and the identification of the related payment
lot are included in the case. By double-clicking on these objects in the case you can display the payment
document or the payment lot item.
With the case type Missing Credit, you can list the credits posted since the creation of the dispute case,
identify them and assign them to the case. Only the amounts of the credits that fulfill the following
criteria are added in the dispute case:
o
They are not statistical
They are not down payments
They were not posted by the payment run
They were not posted with the main/subtransaction defined in posting area 0113 for posting
payments on account
Follow-On Postings for Dispute Case

Follow-on postings for dispute cases are reversals, write-offs, credits (invoice adjustments), and the
posting of replacement receivables. In these postings, the corresponding amount fields are updated in the
relevant dispute cases automatically. With the exception of the case type Missing Payment, incoming
payments are not automatically logged follow-on postings. For example, in the case of an underpayment
of an invoice, a dispute case is not created automatically for the residual open amount. Dispute cases are
generally independent of the existence of open items and are not tied to the clearing or partial clearing of
open items.
You can also post invoice-related credits (invoice adjustments) or replacement receivables with
transaction FPE1 - if, for example, you reverse an incorrect invoice and then post the corrected invoice.
To do this, enter the document number to which the adjustment/replacement receivable refers on the
initial screen of the transaction. You can also enter such postings with reference to a dispute case. In this
case you have to enter the case ID (external identification of the case). The input help shows you the
cases for the business partner, and you can select a case.
You can also call up the transactions for reversals and write-offs in the case display of the dispute system.
The dispute system calls up the corresponding transaction in the FI-CA system. You can then complete
the data and post the document. However, the transactions should only be called up in the display of
dispute cases in the dispute system, since the amounts (for example, amount written off) of the case could
be changed during the update. Locked dispute cases cannot therefore be updated and you have to
subsequently post the corresponding IDoc in this situation.
Integration in the Payment Run
______________________________________________________________
SAP AG
43
SAP System
______________________________________________________________
If an open dispute case exists, you can reduce the amount to be collected from a business partner by the
disputed amount. You can make the logic of the reduction dependent on the status, the priority, the
complaint reasons, and whether the dispute case is an invoice-related dispute case or a dispute case
without invoice reference. The reduction therefore makes more sense for the collection of an invoice for
which there is exactly one invoice-related dispute case than for the collection of the first random item to
be collected where the dispute case has no invoice reference. In order to be able to make these decisions
flexibly, you can define your process logic for event 0610. For a commented example, see the sample
module FKK_SAMPLE_0610_DISPUTE.
Activating Dispute Management
You have to activate the integration of SAP Dispute-Management with Contract Accounts Receivable
and Payable (FI-CA) at company code level in the FI-CA system. To do this, set the activity Dispute in
the activity Set Up Company Codes for Contract Accounts Receivable and Payable in the Implementation
Guide for Contract Accounts Receivable and Payable under Organizational Units.
1.3.19 Dunning
Use
In the dunning history, you can display a text for the business partner. As standard, the text appears with
the name and address of the business partner; with a customer-specific function module defined in event
4700, you can adjust this text to meet your requirements.
Register your function module in the Implementation Guide for Contract Accounts Receivable and
Payable under Program Enhancements -> Define Customer-Specific Function Modules for event
4700.
1.3.20 Enhanced Message Management

Use
The Enhanced Message Management Analysis (EMMA) has been enhanced so that you can now analyze
the application logs of any jobs in the R/3 system. The transaction code is no longer required to identify
the job logs. Instead, business process areas and business process codes have been introduced.
The Customizing has been changed so that you now have to activate EMMA for complete business
process areas instead of for individual transaction codes; you can also define the suppression of messages
during log preparation per business process area.
Business process areas consist of similar business processes, such as billing and invoicing. Business
process codes rewrite a specific activity of a business process area regardless of whether this activity
was carried out by a transaction, a report to be started online or in the background, or by a mass activity
(for example, reversal of a document in transaction FP08, or mass reversal of documents with transaction
FP08M).
______________________________________________________________
SAP AG
44
SAP System
______________________________________________________________
Installation-specific transactions are evaluated via the interface IF_EMMA_LOGMSG_PROCESS.

The Customizing for the case category has been revised with regard to user-friendly aspects. For existing
case categories, you have to maintain the assigned business process code, since this has taken over the
role of the clarification case type as decisive selection criterion for case generation.
You can now use clarification types for several business area codes; they are no longer coupled to an SAP
entity and are used as optional specification for the categorization of case categories.
The role resolution has been integrated in Customizing for clarification case processing.
You can now insert business object attributes into the Customizing for clarification case categories
without programming. To do this, connect the objects of the message pool with the new case container
via a data flow definition.
In the Customizing for the clarification case categories, the administrative data of the author and the last
person to make changes is recorded.
With transaction FPEMMACGEN (see SAP menu: Periodic Processing -> Mass Processing
Administration -> Enhanced Message Management Analysis -> Create Clarification Cases), you
can now create clarification cases in a mass run. You can also create clarification cases for individual
intervals of a mass activity or for several.
Make the system settings required for Enhanced Message Management Analysis in the Implementation
Guide for Contract Accounts Receivable and Payable under Basic Functions.
1.3.21 New and Changed Events

Use
New Events
0063: Include Document in Collective Bill
0086: Industry Grouping Key for Rounding
0104: Clearing: Arrears Surcharges
0113: Clearing: Transaction for Payment on Account
0175: Account Assignment Derivation for Tax Items in PS-CD
0211: Payment Lots: Propose Key for New Lot
0222: Payment Lot: Include Screen for Customer Fields
0232: Payment Lot: Additional Data for Item
0254: Payment Reversal of Locked Checks
0367: Dunning: Leading Contract Account and Company Code
0501: Document Archiving: Check Header
0505: Document Archiving: Check Complete Document
______________________________________________________________
SAP AG
45
SAP System
______________________________________________________________
0580: G/L Account Check for Accounting Rules

0652: Payments: Partner Bank Selection
0671: Payments: Round Payment Amount
0766: Correspondence: Print Request
0767: Correspondence: Create Request
0798: Printing: Output Mode of Attached Payment Media
1010: Contract Account: Check Company Code Group
1054: Business Partner: Determine CCARD_ID for Automatic Creation
1091: Change Payment Card Data: Print Correspondence
1092: Change Payment Card Data: Create Correspondence
1247: Account Balance: Determination of Document Category
1248: Account Balance: Supplement Context Menu
1250: Dispute: Default Values for Creation of Dispute Case
1251: Dispute: Distribute Follow-On Postings to Disputes
1252: Dispute: Define Communication Channel
1253: Dispute: Include Screen for Customer Fields
1254: Dispute: Additional Activities for Manual Changes
1311: Checks for Posting Area 1010
1742: Mass Activity: Set Locks
1743: Mass Activity: Set Locks, Move Parameters
1766: Mass Activity: Evaluation of Open items OP04
1767: Mass Activity: Integration FI/COPA
1840: Mass Activity: Credit Liability Update
1841: Mass Activity: Credit Liability Update, Move Parameters
1842: Mass Activity: SAP Credit Management Score Replication
1843: Mass Activity: SAP Credit Management Parameters, Score Replication
1970: 1099 Reporting: Determine Reporting Flag
1971: 1099 Reporting: Items Relevant for 1099 Reporting
2065: Interest: Set Value Date
2404: Posting via IDoc: Processing of Customer Header Segment
2504: BW: Open Items, Restrict Selection
2506: Open Item BW Extraction: Parameters for Credit Clearing
2805: ICWC Account Balance: Create Info Items
______________________________________________________________
SAP AG
46
SAP System
______________________________________________________________
2806: ICWC Account Balance: Create Item Groupings

2807: ICWC Account Balance: Prepare Items
2821: ICWC Documents: Correspondence Category Independent Data
2822: ICWC Documents: Correspondence Category Dependent Data
3031: Installment Plan: Determine Print Type for Payment Forms
3910: Migration: Document Transfer - Convert Document Data
3920: Migration: Document Transfer - Check Document Data
4030: SD/FICA Integration: Enhanced Transaction Determination
4256: Credits: Create Additional Correspondence
4257: Credits: After Creation of Correspondence
4258: Credits: Check Payment Method (Transfer/Check)
4500: SAP Credit Management: Supplement FI Summary
4501: SAP Credit Management: Filter Open Items
4502: SAP Credit Management: Determine Liability Category
4600: XI: Add FI Summary for SAP Credit Management
4601: XI: Asynchronous Outbound Interface for FI Summary
5125: Transfer of Open Items: Payment on Account
6060: Cash Desk: Barcode Interpretation
6302: Boleto: Determination of Default Instruction Key
6303: Boleto: Assignment of Instruction Key
6306: Boleto: Selection of Statistical Documents
6351: Boleto: Adjust Data Parameters for Account Statements
FKK_EMMA_MASS_CREATE_CASES: Creation of Clarification Cases in Enhanced Message
Management Analysis (EMMA)
6507: Requests: Supplement Customer Fields for Approval
9050: Print Collection Letter
9051: Create Collection Letter
9052: Analyze Items from Collection Case
9053: Attributes for Collection Case
9510: BAPI: Create Request (ExtensionIn)
9511: BAPI: Create Request (ExtensionOut)
9512: BAPI: Change Request (ExtensionIn)
9513: BAPI: Change Request (ExtensionOut)
______________________________________________________________
SAP AG
47
SAP System
______________________________________________________________
9514: BAPI: Create Execution Period for Request (ExtensionIn)

9516: BAPI: Read Request (ExtensionOut)
9552: Balance Confirmation: Check Balance
9557: Document Extracts: Additional Data Records for Import
9558: Document Extracts: Additional Data Records for Deletion
9570: Set Mass Locks
Deleted Events
Events 0161, 1706, and 1707 are no longer available.
You define installation-specific function modules in the Implementation Guide for Contract Accounts
Receivable and Payable under Program Enhancements -> Define Customer-Specific Function
Modules.
1.3.22 Conversion of Finnish Bank Statement to MultiCash (Enhanced)

Use
As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), the Bank Statement: Finland
Reference Payments - Convert to MultiCash report (RFEBFI00) has been enhanced to convert the
following types of bank statement files in FI-CA:
o
Reference payments
Direct debits
Direct invoices
You can also specify further processing of the converted file with the FI-CA MultiCash report,
RFKKKA00.
1.3.23 Foreign Currency Valuation

Use
In the foreign currency valuation (transaction FPW1) (see SAP menu: Periodic Processing ->
Closing Preparations), you can now save the valuation difference for each open item. This enables you
to further process the revaluation of an open item in closing preparations, for example, in the key
date-related open item list and during reclassification of customers with credit balances.
By saving the valuation difference, you can make a more flexible assignment of valuation methods to
company codes. This means that the foreign currency valuation is compatible with different GAAPs. This
means that you can valuate open items differently according to the reporting view (valuation area).
______________________________________________________________
SAP AG
48
SAP System
______________________________________________________________
Each foreign currency valuation that requires correction postings is logged. You can use the new
transaction Log for Foreign Currency Valuation (FPW2), you can get an overview of all foreign
currency valuations. You can also reverse individual valuation runs in the display if you have the
authorization to run them again later with more current data.
In the Implementation Guide for Contract Accounts Receivable and Payable under Closing -> Foreign
Currency Valuation, define:
o
Valuation methods
Valuation areas for each reporting view (for example, HGB, IAS, US GAAP)
Valuation variants
For each company code and for each local currency, you can configure the valuation method to be
used for a foreign currency valuation, and for which valuation area the valuation is to be carried out.
The general ledger accounts that the unrealized gains and losses are to be posted to
You can define different accounts dependent on the valuation area.
1.3.24 IDoc Interfaces for Communication with External Billing Systems

Use
Evaluation of Mass Runs by Enhanced Message Management Analysis
The evaluation of Enhanced Message Management Analysis has been activated for the following
programs:
o
Document Data Transfer (transactions FKK_EBS_TOI_COPA and FKK_EBS_TOI_COPA_E)
Linking with Archive Data (transactions FKK_EBS_ARC and FKK_EBS_ARC_E)
Reversal of Documents (transactions FKK_EBS_MRD and FKK_EBS_MRD_E)
Functional Enhancements in the IDOC FKK_EBS_TOI_COPA (Document Data Transfer from

External Billing Systems)
To define and process customer- or project-specific document header data, you can now define a
replacement segment for the segment E1FKK_EBS_TOI_HEADER in Customizing.
You can use event 2404 to process header
segment data. You can also change the standard processing by defining the standard segment
E1FKK_EBS_TOI_HEADER in Customizing. For example, you can change the field BLART or
AWTYP.
In event 2404, you can also create the object relations between documents via the interface
T_FKKOPREL.
By defining a customer- or project-specific segment you can transfer the additional data contained
therein, for example, the classification key, to the document header.
The optional field DOC_TYPE (document type) has been added to the segment
E1FKK_EBS_TOI_HEADER. With this segment you can override the document type defined in the
______________________________________________________________
SAP AG
49
SAP System
______________________________________________________________
interface Customizing at document level.

Maintaining Object Relations at Item Level
The maintenance of object relations (interface T_FKKOPREL) has been added to event 2413. This
means that you can now fill the object relations at document item level from a customer- or
project-specific ITEM additional segment.
In the Implementation Guide for Contract Accounts Receivable and Payable under Data Transfer ->
Communication with External Billing Systems -> Transfer of Accounting Documents, the
following activities have been enhanced:
o
Basic Settings for Document Transfer

You can now define a customer- or project-specific header data segment.
Define Translation of External Tax ID

You can now define (optional) a tax on sales and purchases code as well as the condition key for
each external tax code. If you define a tax on sales and purchases code, this is available in events
2405 and 2406 for comparison.
1.3.25 Changed IMG Activities in Contract Accounts Receivable and Payable

Use
There have been changes to the following system settings with Release 4.72:
Organizational Units
As part of the changeover of the company code concept in Contract Accounts Receivable and Payable,
you now have to make the settings for the company code in the following activities:
- Set Up Company Codes for Contract Accounts Receivable and Payable
- Define Company Code Groups
- Assign Company Codes to Company Code Groups
Basic Functions
o
Contract Accounts
The activity Activate Additional Checks for Changes to the Business Partner Master Record
has been moved from the section Technical Settings to the section Contract Accounts.

In the section Define Account Assignments for Automatic Postings, the activity Define CO
Account Assignments has been renamed to Define CO Account Assignment Keys.
Here you can also define the required specifications for the Nota Fiscal in Brazil. To do this,
Contract Accounts Receivable and Payable uses the Customizing of the standard FI.
Business Transactions
______________________________________________________________
SAP AG
50
SAP System
______________________________________________________________
Payments
The activity Specifications for the Clarification of Incoming Checks under Basic Functions ->
Check Management has been renamed to Define Specifications for the Clarification of
Cashed Checks.
The activities in the sections Cash Desk and Cash Journal under Business Transactions ->
Payments -> Processing of Incoming/Outgoing Payments have been grouped under the section
Cash Desk/Cash Journal.
The activity Maintain Responsibilities for Cash Journal Users has been moved from the IMG to
the menu (see SAP menu Payments -> Cash Journal -> Responsibilities).
In the section Creation of Incoming/Outgoing Payments, the activity Define Specifications for
Responsible Company Code has been replaced by the activity Define Specifications for
Paying Company Code.
In the same section, the activity Specifications for Transferring Open Items to the Responsible
Company Code is no longer available.
Submitting Receivables to Collection Agencies

The activity Define Strategy for Derivation of Collection Agency Responsible has been
renamed to Define Derivation Rules for Collection Agency Responsible and has been
enhanced.
Technical Settings
The activity Activate Dependency Check for Business Partner Master Data Changes is no longer
available.
1.3.26 New IMG Activities in Contract Accounts Receivable and Payable

Use
In the Implementation Guide for Contract Accounts Receivable and Payable, the following new settings
are available:
Basic Functions
o
Contract Partner
This section and the subsection Changes to Payment Transactions, with the activities
Client-Specific Settings, Company Code-Specific Settings, Define Processing Variants, and
Define Rules for Follow-Up Actions are new.
Bank Chains
In this section you can now Define Scenarios, Define Bank Chains, and Configure Bank
Chains as in the component Financial Accounting (FI).

In the section Automatic G/L Account Determination, you can Define Accounts for Surcharges
on Late Payment.
______________________________________________________________
SAP AG
51
SAP System
______________________________________________________________
Requests
For requests you can Make Settings for Approving Requests.
Open Item Management

You can define Short Account Assignments for Transfer Postings in Account Maintenance.
Enhanced Message Management

The settings for maintaining clarification case categories have been changed over as follows:
Specifications for Processing Clarification Cases
- Generate Selection Screen for Clarification List
- Define Reasons for Reversing Clarification Cases
- Specifications for Customer-Defined Business Processes and Messages
- Define Customer Business Process Areas for Message Management
- Define Customer Business Processes for Message Management
- Define Customer Business Processes for Processes from CIC
Business Transactions
o
Processing Incoming and Outgoing Payments

The Customizing for the cash desk/cash journal has been changed over (see release information).
Boleto
In this section you can make all of the settings required for processing Boletos in Brazil.
Write-Offs
For write-offs you can Maintain Alternative Expense and Contract Account.
Transfers
You can now Define Default Values for Transfer Reasons.
Doubtful Entries and Individual Value Adjustments

You can Define an Age Grid for Value Adjustment Variants.
Integration
o
Financial Supply Chain Management

-
Biller Direct
You can make the following settings for the integration of SAP Bille Direct:
- Define Clearing Account for Overpayments
- BAdI: Determination of Bill Details
- BAdI: Assignment of Business Partners to User IDs
- Specifications for the Integration of SAP Dispute Management
Credit Management
______________________________________________________________
SAP AG
52
SAP System
______________________________________________________________
You can make the following new system settings as part of the integration of SAP Credit
Management:
- Activate Credit Management
- Maintain Credit Segments
- Assign Open Items to Credit Segments
- Define Specifications for Credit Management
-
Dispute Management
For the integration of SAP Dispute Management you can Make Basic Settings for
Dispute Management.
Funds Management
The following settings have been provided for the integration of Funds Management in the
FI-CA standard:
- Activate FM Table Fields for Contract Accounts Receivable and Payable
- Define FM Account Assignment Derivation
- Display Activation Status of Fund Accounting
- Define Accounts for Funds Clearing
Closing Operations
o
In the Foreign Currency Valuation you can:

- Define Valuation Areas
- Define Valuation Variants
- Define Valuation Area-Specific Accounts for Exchange Rate Differences
In Reclassifications you can:

- Define Summarization Accounts
- Define Company Codes for Summarization
Technical Settings
You can Activate Parallel Update in Cash Management.
Program Enhancements
As part of the introduction of the classification key you can activate the prepared enhancements.
1.3.27 Information System

Use
Preselections of Master Data (Transaction FPSELP)
When you select by dunning data, you can now consider only open items if required previously all
cleared items were selected automatically.
______________________________________________________________
SAP AG
53
SAP System
______________________________________________________________
Data Extracts (GDPdU)

From Release 4.72, all developments for the realization of the German Principles of Data Access and
Verifiability of Digital Documentation (GDPdU) area available in all releases maintained by SAP. In
Releases 4.64, 4.63, and 4.61 however, only the export programs FPDE_EXP, FPDE_AEXP, and
FPDE_EXTR are available. All export programs support the SAP format AIS, which can be imported
into IDEA. For the Contract Accounts Receivable and Payable objects, the following export, import, and
deletion transactions are available:
o
Document Extracts
-
FPDE_EXP
FPDE_AEXP
FPDE_IMP
FPDE_DEL
You can also select SD documents for the FI-CA documents and export them.
o
Partner Extracts
-
FPDEP_EXP
FPDEP_IMP
FPDEP_DEL
Customizing Extracts
-
FPDEC_EXP
FPDEC_IMP
FPDEC_DEL
You can use the transactions FPDE_EXTR (evaluation system) and FPDE (extract overview) for all
extract objects.
Evaluating Open Items
Transaction FPO4P provides you with a parallel variant for transaction FPO4. For each interval, this
transaction creates a list and a list with the totals records (similar to transaction FPO1P (Open Items for
Key Date Parallel). However, in contrast to transaction FPO4, transaction FPO1P has certain restrictions.
Parallelization is therefore only possible if the layout sorting corresponds to the parallelization object.
The output is not in ALV format and no additional output in the dataset is possible.
For transaction FPO4, the memory has been optimized. If you do not want to display line items, the
report no longer collects all items in the memory if you have selected an object and a variant (technical
settings) (see also the documentation for the report).
You can now group the spool requests for individual intervals for the evaluation with transaction FPO1P
and transaction FPO4P.
Transactions FPO1 and FPO1P can now also calculate the evaluation for different currency types and
therefore consider a currency valuation. Transaction FPRECL has therefore also been changed. You can
now also post adjustments to reclassifications for different currency types.
______________________________________________________________
SAP AG
54
SAP System
______________________________________________________________
1.3.28 Deferral and Installment Plan

Use
Clearing Locks on Installment Plan Items
When you display installment plans, you can now also display the clearing locks as well as the payment,
dunning, and interest locks. When you create and change installment plans, you can create and set
clearing locks.
Improved Display of Processing Locks
Previously, you could only display the different processing locks (payment, dunning, interest, and
clearing locks) in installment plan items via a joint icon (lock), which, when you placed the cursor on it,
displayed the type of locks that existed in a quick info. You could only see details, such as the lock
reason, by double-clicking on the icon. The display of the installment plan items now also has, in addition
to the joint lock icon, a column for each processing lock with the respective lock reason. If there are
several locks of the same type with different lock reasons, a tilde appears (~). Double-click on one of
these fields to display the details for the locks.
Easier Maintenance of Processing Locks
Previously, you could only maintain processing locks (payment, dunning, interest, and clearing locks) for
installment plan items by double-clicking on the field for displaying the lock icon. Then you had to select
the type of lock. Now you can maintain the lock you have selected directly by double-clicking on one of
the new table fields. You can also set an unlimited (time) lock by entering a lock reason directly. If there
is only an unlimited (time) lock for a lock type, you remove this from the table field by deleting the lock
reason.
Selection by Classification Key
You can also select items for which a new installment plan is to be created by classification key.
Standard Company Code instead of Responsible Company Code
If the system cannot derive a unique company code from the original receivables when you are creating
an installment plan, the system posts the installment plan to the standard company code.
New Display Fields in the Installment Plan History
When you display the installment plan history (SAP menu: Account -> More Information ->
Installment Plan History), the contract account, business partner, and address of the business partner are
displayed for each installment plan.
New Fields in the Header Data of the Installment Plan History
The fields Number of Installments and Distributed Interest and Charges are stored in the header data
for the installment plan history.
Determination of Company Code, Contract, Business Area, and Business Place No Longer in
Event 3000
When you create an installment plan, the company code, contract, business area, and business place are
taken from the original item as standard, as long as these fields have the same value in all original items
selected. Previously, this check took place in a standard module processed in event 3000. This check now
takes place in the standard coding before event 3000. The source code of the standard module
______________________________________________________________
SAP AG
55
SAP System
_____________________________________________________________
FKK_SAMPLE_3000 has been deleted.

If you do not want to fill these fields in the installment plan, or want to enter other values, you can do this
by defining event 3000 accordingly.
Printing of Payment Forms for Installment Plans - List of Correspondence Created
When you are printing payment forms for installment plans (SAP menu: Periodic Processing -> For
Contract Accounts -> Correspondence -> Print Installment Plan Payment Forms), you can use the
entry Correspondence in the environment menu to display a list of the correspondence created
(installment plan letters and payment forms).
1.3.29 Integration
Use
Event 4030: Determination of SD/FI-CA Transaction
Before the upgrade from Release 4.6* to Release 4.7*, you have to close all of the reconciliation keys in
the old system and transfer the postings to the General Ledger and Profitability Analysis (CO-PA).
Event 4030 has been introduced to determine the main and subtransaction of an FI-CA document during
the transfer of an SD billing document. In this event you have access to all of the information in an SD
billing document, which means that a more detailed transaction determination is possible here in contrast
to Customizing.
With the new event 4040 you can restrict the selection of contract accounts when you create/change an
SD order.
In the SD document flow, FI-CA documents that have already been archived are also displayed now.
Transfer of Totals Records to the General Ledger (Report RFKKGL00)
Errors in the transfer of FI-CA totals records to the general ledger no longer lead to a program
termination. From Release 4.72, report RFKKGL00 continues the transfer with the next company code
and logs the errors in the spool list. There you can check the completeness of the transfer.
Integration of FI-CA with SAP Credit Management
With SAP Credit Management you can manage liabilities and scores for a business partner. The central
Credit Management server manages information from different systems, such as CRM, Contract
Accounts Receivable and Payable (FI-CA), and Accounts Receivable Accounting (FI-AR), and carries
out operational credit queries. The use of the interface technology of the Exchange Infrastructure means
that you can also connect external systems to SAP Credit Management.
FI-CA now has an interface for transferring credit information from SAP Credit Management.
The FI-CA document interfaces (report RFKKBIB0, BAPI, IDoc interface) support the transfer of the
partner message ID for SAP Credit Management. This transfer guarantees the synchronization of the
liability update over several systems.
In FI-CA there are mass activities for the following activities:
o
Sending the liability for a business partner to SAP Credit Management
Sending an FI summary to SAP Credit Management
______________________________________________________________
SAP AG
56
SAP System
_____________________________________________________________
Replication of the score in SAP Credit Management
FI-CA also supports the liability query for the online credit check in SAP Credit Management.
You can influence the program flow in the following events:
o
4500: Add FI Summary
4501: Filter Open Items for Liability Determination
4502: Determination of Liability Category
For a description of the integration of industry-specific processes, see the release information for the
corresponding industry components.
You configure SAP Credit Management in the Implementation Guide for Contract Accounts
Receivable and Payable under Integration -> Financial Supply Chain Management -> Credit
Management.
o
In order for the internal processes of Contract Accounts Receivable and Payable (for example,
creditworthiness) to derive the data from SAP Credit Management, you have to activate Credit
Management here.
In the activity Define Specifications for Credit Management, you define the default values, such as
the interest rate for the liability subject to interest and the liability category.
The credit segments that you enter in the activity Maintain Credit Segments must agree with those
of SAP Credit Management. There the credit segments are used to split the liability into different
areas (for example, country A and B).
In the activity Assign Open Items to Credit Segments, you use the parameters Posting Area,
Division, Account Determination ID, and Business Area to decide which credit segment an open
item is to be assigned to.
1.3.30 Interest Calculation

Use
Interest Calculation Rule
There are two new calculation methods for defining interest calculation rules:
o
30/30E
You should only use the method 30/30E for exponential interest calculation. The system calculates
exponential interest on a monthly basis.
act/actY
In the method act/actY, the suffix Y stands for Year. It indicates that the calculation is based on the
number of days in a calendar year.
Setting #Interest Calculation To Date

With a function module processed in event 2065 you can change the date for the Interest Calculation
To for clearing items.
______________________________________________________________
SAP AG
57
SAP System
_____________________________________________________________
For amounts cleared in the account maintenance, as standard the due date of the invoice and clearing date
of both items are used to calculate the interest.
In event 2065 you can use the due date of the invoice amount and the value date of the payment amount
to calculate the interest for amounts cleared in the account maintenance.
You define interest calculation rules in the Implementation Guide for Contract Accounts Receivable and
Payable under Business Transactions -> Interest Calculation -> Item Interest Calculation ->
Define Interest Calculation Rule.
1.3.31 Processing Locks

Use
Setting Processing Locks
With the new transaction FKLOCK2 (Set Processing Locks) in the SAP menu under Periodic
Processing -> For Contract Accounts, you can create processing locks. From the selection criteria
Business Partner, Contract Account, Contract, Company Code, you can set mass locks for a
combination of Lock Category, Process, Lock Reason. Locks created in this way contain the data of
the creating run in the fields DFKKLOCKS-LAUFI and DFKKLOCKS-LAUFD in table DFKKLOCKS.
You have to define event 9570 for the following application-specific locks:
Lock Category
Object
21
22
41
51
Insurance policy
Partner locks for insurance policy
Utility contract
Contract object partner account
To delete mass locks, you can use transaction FPLKDEL (Delete Mass Locks Set) in the SAP menu
under Periodic Processing -> For Contract Accounts.
1.3.32 Mass Runs

Use
Repeated Processing of a Job Interval
If an interval cannot be processed in a payment run, interest run, or interest calculation run for cash
security deposits because the data is locked by another processing function, the system can restart the
processing of this interval automatically and as frequently as required.
You have to enter the maximum number of repetitions in the field Maximum Int. Repetitions in the
______________________________________________________________
SAP AG
58
SAP System
______________________________________________________________
specifications for General Control on the tab page Job Control under Technical Settings -> Prepare
Mass Activities in the Implementation Guide for Contract Accounts Receivable and Payable.
1.3.33 Master Data

Use
Changing the Bank Data of a Business Partner
With the new transaction Maintain Payment Data (FPP4) (see SAP menu: Master Data -> Business
Partner), you can:
o
Create new bank details
Change existing bank details
Delete existing bank details
Create new payment cards
Change existing payment card details
Create customer contacts
Print confirmation letters
This makes changing business partner-related bank data much easier. In the transaction Maintain
Payment Data, you can, for example, change the bank details of a customer who changes from being a
cash payer to a direct debit payer simultaneously in the business partner master record and in dependent
objects, such as the contract account.
You can also control follow-up actions, such as reversing dunning notices, by means of flexible rules.
If you set the indicator Create Bank ID in the client-specific settings in Customizing, in event 1053 you
can determine new bank details ID for the business partner concerned.
If you set the indicator Create Credit Card ID in the client-specific settings in Customizing, in event
1054 you can determine a new payment card ID for the business partner concerned.
With a function module processed in event 1083 you can make further changes to the contract account
when you save the data. In this event, you can, for example, change the field Posting Control Group in
the contract account if a customer changes from being a cash payer to a direct debit payer.
You make specifications for changing bank data in the Implementation Guide for Contract Accounts
Receivable and Payable under Basic Functions -> Contract Partner -> Changes to Payment
Transactions in the following activities:
o
Client-Specific Settings
Company Code-Specific Settings
Define Processing Variants
Define Rules for Follow-Up Actions
Specifications for Posting Credits in Follow-Up Actions
______________________________________________________________
SAP AG
59
SAP System
______________________________________________________________
If you want to send confirmation letters, define the required form for correspondence type 0036 under
Basic Functions -> Correspondence -> Define Application Forms for Correspondence.
You define event modules under Program Enhancements -> Define Customer-Specific Function
Modules.
1.3.34 Evaluating Open Items

Use
Currency Type and Currency Valuation
When you enter a currency type on the selection screen for the Key Date-Related Open Item List
(transaction FPO1), the report replaces the first local currency with a currency with this currency type. If
you also enter a valuation variant and a valuation key date, the report does not display the original
amounts of the items; instead, it displays the amounts calculated by the currency valuation for the
valuation key date.
1.3.35 Processing of Incoming and Outgoing Payments

Use
Payment Lot: Archive Connection
From Release 4.72, you can display archived lots and non-archived lots.
When you display documents posted by a payment lot, you can also display the related payment lot items
if the lot has been archived. This display option requires an additional index table that is created during
archiving with effect from Release 4.72. For payment lots archived before 4.72, you can recreate these
index entries using report RFKKPLAR.
Payment Lot: Default Value for New Key
If you want to create a new lot, you can have the system default a suitable key. The prerequisite for this
function is that you have registered a suitable module for event 0211.
Payment Lot: Installation-Specific Fields in Items
If additional fields are included in the payment lot item via the customer include CI_FKKZP, you can
display these on the detail screen and the list screen. To do this you have to provide an include screen.
The program name and the number of the include screen are determined in event 0222. For more
information see the documentation and the coding examples in the related sample function module
FKK_SAMPLE_0222.
Payment Lot: Installation-Specific Additional Function
The detail screen for the payment lot item contains an installation-specific addition function that you can
define to meet your requirements. This function is available under Extras -> XXX, and you can also call
it up via a separate pushbutton (optional). In event 0232, the texts for the processing menu and the
function key (xxx) are determined, along with which function module is to be called when the user
______________________________________________________________
SAP AG
60
SAP System
______________________________________________________________
executes this function. For more information, see the documentation for the function module
FKK_SAMPLE_0232.
Payment Lot: Clarification
o
From Release 4.72, you can have the clarification account determined dependent on the document
type. Posting area 1040 has been extended accordingly.
From Release 4.72, clerks can also create notes during clarification.
If clearing is to be posted online during clarification, the note to payee entered in the payment lot
also appears on the processing screen for the open items (first 80 characters).
In the search with errors function, you can now also search for business partner with just the name
(and optionally the city) in the field Sold-to-Party/Account Holder.
Payment Lot: Changes to Protected Fields

o
In check lots, you can use the special function Correct Check Number to correct the check number
for individual payments in lots that have already been closed or posted. You may need to make a
correction, for example, if, when creating the check deposit list, you discover that check numbers
have been entered incorrectly. To carry out this function you need authorization 014 for
authorization object F_KK_SOND. You make the change in the check lot display. On the first
screen, choose Edit -> Correct Check Numbers. Then call up the detailed display for the check
payment to be corrected and select Edit -> Correct Check Numbers. The check number field is
then ready for input you can overwrite the number and save.
In payment lots created automatically, you can change the bank data of the payer and the note to
payee during clarification. A correction is necessary, for example, if a data reader has incorrectly
interpreted a hand-written note to payee. To carry out this function you need authorization 017 for
authorization object F_KK_SOND. To make the fields on the tab pages Payment Data or Note to
Payee ready for input, select Edit -> Change Bank Data.
Payment Lot: Transfer with Report RFKKZE00

In the transfer structures BFKKZP and BFKKZS (ZFKKZP/ZFKKZS), the field lengths of the fields
SELW1, SELW2, and SELW3 have been extended from 30 characters to 35.
If you do not create the files with these record structures with ABAP programs, you may have to
adjust the data declarations and the coding in the programs.
Payment Lot: Clarification
You define the clarification account in the Implementation Guide for Contract Accounts Receivable and
Payable under Business Transactions -> Payments -> Processing of Incoming/Outgoing
Payments -> Define Clarification Account. If you want to use the document type as selection criterion,
you first have to select the field Document Type as additional key field via Goto -> Key Selection.
1.3.36 Payment Transactions

Use
Payment Program: Restriction to One Payment Card Type
______________________________________________________________
SAP AG
61
SAP System
______________________________________________________________
From Release 4.72, you can restrict the payment run to one payment card type. You can then run separate
payment runs for each payment card type, event though the payment method is always the same card
payment.
For contract accounts with other payment card types, a corresponding message is created in the
application log and a payment exception is created.
Payment Program: Selection of Partner Bank via New Event
In the new event 0652, you can override the automatic selection of partner banks created by the payment
program.
In the standard system, the partner bank is selected as a result of the bank details defined either in the
contract account or the contract (differentiated by incoming payment and outgoing payment). You can
override this by explicitly specifying bank details in the line item. However, it is not possible, for
example, to select a partner bank dependent on the currency of the items paid if these bank details are not
entered in the items to be paid.
Using event 0652, you can now set a different bank details ID dependent on the items to be paid, or
prevent payment.
See the documentation for function module FKK_SAMPLE_0652.
Payment Media Creation: Settings for the Note to Payee
The standard options for defining the note to payee have been enhanced for the creation of payment
media. In the user-defined specifications, you can now specify the number of items to be prepared only
once per payment. This avoids the contents of PAYH and PAYHX being output per item, even though
these are the same for all items.
In the definition of the item content (FQP5 -> Note to Payee: Content), the sequence (item number)
decides whether the content is prepared per payment or per item. If, for example, you have specified 2
information items per payment and 1 information item per item, you have to provide a total of 3 items
with content. The first two apply per payment, which means that here only the fields from the structures
PAYH and PAYHX are useful. The third item is then repeated for each item. The fields from the
structure PAYP are useful here.
Payment Media Creation: Correspondence Banks
If you use the payment media formats EDIFACT, S.W.I.F.T. (MT 100, 101, 103, 104, 200, and 202),
(customer development), from Release 4.72 you can define correspondence banks. This means that you
can specify a bank chain with up to three intermediary banks (correspondence banks) in Customizing for
the transfer from one bank to another. You can define general and recipient-specific bank chains. You
then specify recipient-specific bank chains in the transactions for creating and changing business partner
data (FPP1, FPP2) on the tab page Payment Transactions, in the area Bank Chains.
The function module FI_PAYMENT_BANK_CHAIN_SET determines the bank chains during the
payment media creation and places them in the corresponding structures.
If you want to use the function for the payment media formats stated, you have to add the call of the
function module FI_PAYMENT_BANK_CHAIN_SET to the function modules defined for the events 20
and 30, or, for customer-defined developments, the events 21 and 31. The function module
FI_PAYMENT_BANK_CHAIN_SET contains the data in the corresponding event module as import
parameter.
Check Management: New Status for Processing Check Locks
______________________________________________________________
SAP AG
62
SAP System
______________________________________________________________
A new check status (Locked) has been introduced with Release 4.72. This means that you can lock a
check and report the lock to the bank, without having to reverse the related payment or issue a
replacement check. The check is locked in check management and reported to the bank using transaction
FPCHX. After a specific deadline (usually 24 hours) the bank guarantees that this check can no longer be
cashed. You reverse the related payment document after this deadline by regularly scheduling transaction
FPCHS so that the cleared items are open again. By running the payment run again you can create a new
check if required. If checks are cashed within the deadline, you can define, in the settings for the voiding
reason, whether the checks are to be deemed 'cashed' automatically or whether clarification cases are to
be created.
This procedure is interesting for US customers and is known by the name 'Stop Payment'. It is an
alternative to the previous way of issuing a replacement check. Invalid checks that have not yet left the
company premises should be voided and reissued as previously. A check lock is not necessary in these
cases.
Check Management: Enhanced Maintenance in Change Mode
If you want to correct the data of a check that was created via a payment run, only a few fields are
modifiable. You cannot even change a status set by accident. From Release 4.72, the button
'Administrator has been added in change mode (F6). When you press this button, additional fields are
ready for input. To carry out this function you need authorization 018 for authorization object
F_KK_SOND.
You make the settings for bank chains in the Implementation Guide for Contract Accounts Receivable
and Payable under Basic Functions -> Bank Chains:
o
Define Scenario
Activate Bank Chains
Set Up General Bank Chains
In the activity Define Scenario, you define for each scenario, whether the bank chain is determined via
the general bank chain search and/or via the partner-specific bank chain search. If both fields are set, the
partner-specific bank chain search has priority over the general bank chain search. Using the fields
Sender Bank, Recipient Bank Country, Recipient Bank, and Currency, you can define a ranking for
the bank chain search for each scenario. SAP delivers four standard scenarios; you can also generate your
own scenarios.
The bank chains that you create in the activity Set Up General Bank Chains are independent of the
bank details of a business partner or of the house banks. For a bank chain ID, you can create up to three
intermediary banks. The intermediary banks are linked independently of the recipient and sender banks.
Check Management: Settings for Voiding Reasons
If you want to use the new check status 'Locked, you need a voiding reason or a lock reason, as for
voiding. Whether a reason is permitted as a lock reason depends on the indicator Lock.
You can also define whether the cashing of a locked or voided check is to be posted automatically or
whether a clarification case (for check encashment) is to be created.
In the field Activity, you can enter a 6 digit code to control additional activities (for example, setting
limited clearing locks) in customer modules. You can evaluate this field directly or use it as a key for
______________________________________________________________
SAP AG
63
SAP System
______________________________________________________________
your own customer table.
1.3.37 Collections in the Print Workbench

Use
Using Collections, you can now group application forms to process them together.
A Collection is an application form of the form type Collection.
In a Collection, you can group both application forms from the same form class, and also application
forms from different form classes. You can define your own parameters for the technical components of a
Collection, for example, a specific printer. You can classify the individual application forms so that they
are issued sequentially or bundled. You can process Collections using transaction EFRM (SAP menu:
Print Workbench -> Application Form -> Process), as for application forms.
1.3.38 Postings and Documents

Use
Postings and Documents: Classification Key as New Characteristic in Document
The new attribute Classification Key has been added to the Contract Accounts Receivable and Payable
document and the request. The classification key provides a similar function to the reference number, but
allows keys with a length of up to 35 characters. The classification key is an enhancement supported in
the system. This means that the attribute is not initially active in the system delivered; you have to
activate it explicitly in your installation.
Functions of the Classification Key
The classification key
o
Can be entered in the document header
Is available as input field in the document display, document change, document reversal, and mass
reversal, and you can use this field to identify the required document(s)
Is inherited in the business partner items and can be displayed in the account balance or in the
processing of open items
Can be used as selection criterion in the account balance, in the selection of open items (for
example, in the payment lot or in online posting), and for the write-off or creation of an installment
plan
Is a possible selection criterion in payment advice notes for incoming payments
Activating the Classification Key

You activate the field Classification Key in Customizing using a report that creates the required fields
and database indexes. In test mode, the report shows which enhancements would be made.
______________________________________________________________
SAP AG
64
SAP System
______________________________________________________________
If the classification key is active and you have posted documents with classification keys, the system
administrator must update the database statistics for table DFKKKO. This is the only way to make sure
that the new indexes are also used.
If you use requests, the same applies for table DFKKORDERPOS.
Deactivating the Classification Key
You can deactivate the classification key but only manually. To do this, you have to remove the field
OPORD from the CI includes to which it was added. You then have to convert the database tables; this
can involve a long runtime if there are a lot of data records affected.
SAP therefore recommends that you weigh-up the use of the classification key and then adhere to this
decision.
Postings and Documents: Negative Postings
From Release 4.72 you can create negative postings in Contract Accounts Receivable and Payable. A
negative posting reduces the transaction figures for the account posted to in the general ledger. A debit
posting as negative posting therefore does not lead to an increase of the debit transaction figures; it leads
to a reduction of the credit transaction figures. This enables you to show transaction figures for accounts
after an incorrect posting and subsequent correction (for example, invoice posting and reversal) as if
neither the incorrect posting nor the correction had taken place.
Negative postings have been supported in the general ledger (FI-GL) for a long time. You decide whether
to permit negative postings at company code level. The corresponding setting in the company code table
is also effective for Contract Accounts Payable and Receivable.
In addition, in Contract Accounts Receivable and Payable, the document type decides whether a posting
is to be posted negatively. You can designate a document type such that negative postings are always
created, or such that negative postings are only created for corrections in the same fiscal year. For more
information about the setting for the document type, see the Customizing for the document types and the
field documentation for the field Negative Posting.
A description of negative postings for the most important business transaction follows:
Reversal
For a reversal, the document type used decides:
o
Whether a negative posting is never permitted
Whether a negative posting is always permitted
That a negative posting is created if the posting and reversal are in the same fiscal year
A special feature is that the items in the reversal document for which the account to be posted to has been
swapped in comparison to the original document are not posted negatively This can be the case for
aperiodic reversals (swap of P&L accounts) or for posting incoming payments where the reversal is used
to post back to the clarification account.
Resetting Clearing
After resetting clearing, all accounts should appear as if the clearing had not taken place. This means that
______________________________________________________________
SAP AG
65
SAP System
______________________________________________________________
the inverse posting of cash discount, small differences, exchange rate differences, and taxes that were
posted due to the clearing are to be posted negatively. The display in the receivables accounts is retained.
Example
You reset clearing for a payment received. After the clearing reset, the payment with clearing of open
items becomes a type of payment on account again, which means that the credit from the payment is an
open item in the receivables account. From the view of the account balance in the receivables account, it
is irrelevant whether there was a payment on account or whether items were cleared.
Returns
Returns should be treated like reversals. The first item in a returns clearing account is, however, never
posted negatively; the same applies to returns charges.
Individual Identification of Individual Posting Items
If you want to post a document for which negative postings are required for all items manually, all you
have to do is select an appropriate document type. However, if you only want to post individual items
negatively, you have to enter the entire transaction in two documents.
Example
Transfer posting from an incorrect G/L account to the correct G/L account. The reset in the incorrect G/L
account should be posted negatively, the posting to the correct account not. First enter a negative posting:
Clearing account to incorrect G/L account. Then a 'normal posting: Correct G/L account to clearing
account.
Payments on Account
If, on receipt of payment, you first post on account instead of clearing immediately and then carry out
clearing later, (for example, via account maintenance or during processing of a subsequent payment), the
debit and credit side of the receivables account increases by the amount of the payment on account. If you
want to avoid this effect, make sure that every clearing of a posting on account is posted negatively. To
do this, you have to indicate in Customizing for the main and subtransaction used for payments on
account that each clearing of this item is to be posted negatively.
Postings and Documents: Parallel Open Item Processing for Partners
If a business partner has several contract accounts, before Release 4.72, it was not possible for two clerks
to process open items in different contract accounts for this business partner simultaneously (for example,
during account maintenance). Parallel processing in different accounts of a business partner is possible
from Release 4.72.
Postings and Documents: Hold Status of Open Item Processing
During manual processing of clearing transactions, you can save the status of open item processing and
reload it later. For this purpose, the new functions Hold Processing Status and Retrieve Processing
Status are available on the processing screen for open items. When you hold the status, you have to
specify an identification. You can hold several processing statuses in parallel for the same object (for
example, same business partner, same collective bill).
A processing status is held in the system for 30 days. This period starts from the last time the status is
saved.
______________________________________________________________
SAP AG
66
SAP System
______________________________________________________________
For each processing status, the system also saves the object being processed in addition to the
identification. This is either the business partner to whom the open items belong, or for assignment at
detail level, the collective bill, the installment plan or the bundle for which assignment of clearing
amounts is to take place at the level of the related original item.
If the business partner is not unique, the partner with the most active items is set.
When you retrieve a held status, in the detail assignment for collective bills, installment plans, and
bundles, only identifications that belong to the object named are permitted. The possible entries help (F4)
offers a correspondingly restricted selection.
When you retrieve a held status during the processing of open items for one or more business partners,
the identifications permitted are those where the business partner held is correct for at least one of the
currently selected items. The possible entries help (F4) also offers a correspondingly restricted selection
here.
In general, the held status is mixed with the current selected items. These can be different to the items
that were selected when the processing status was held. Possible causes are:
o
Other selection criteria
Clearing or partial clearing that has taken place in the meantime
Different amounts for clearing in a different currency

Here the amounts are translated for open item processing and the translation result may have
changed due to changes in the exchange rate.
If a clearing amount was recorded in a held status, and this clearing amount is higher than the total
amount of the open items when the status is retrieved, the maximum possible clearing amount is set. If a
cash discount amount was specified, this is reduced accordingly so that the cash discount percentage rate
is retained.
Whenever the held status cannot be used again completely, the user sees a message with details of the
variance in the long text.
Postings and Documents: Transfer Postings in Account Maintenance
In the account maintenance, you can transfer difference amounts to a G/L account defined in
Customizing. You have to specify the amount to be posted and similar to the payment lot a short
account assignment that the system can use to determine the company code, account, business area, and
CO account assignments.
The fields for the transfer posting are only active if the user has been assigned to a tolerance group for
which a maximum amount and maximum percentage rate for the transfer posting have been specified in
Customizing.
You cannot transfer to tax-relevant accounts.
Postings and Documents: Arrears Surcharges
If open items are cleared by payments or clearing of payments, you can define arrears surcharges. These
surcharges have the opposite effect to cash discount. For example, if you set a surcharge of 2.00 for an
invoice for 100.00, a payment of 100.00 leads to postings for partial clearing in the amount of 98.04 and
revenue from payment surcharges of 1.96.
Since the calculation of surcharges is dependent on the value date of the payment, clearing transactions
with surcharges can only consider additional credit items (for example, from payments on account) if
______________________________________________________________
SAP AG
67
SAP System
______________________________________________________________
they have the same due date. All other credit items are locked for the current clearing transaction.
If clearing processing takes place online, you can deactivate or reduce the surcharges calculated
manually.
The following transactions enable the calculation and posting or surcharges:
o
Payment Lot
Cash Desk and Cash Journal
General posting online
Account Maintenance
Automatic Clearing
In order to enable the calculation of surcharges you have to define an installation-specific function
module for event 0104.
Postings and Documents: Mass Postings and Cash Management
For mass postings that run in parallel processes, waiting time may occur due to competing accesses
during the update of data for Cash Management. Contract Accounts Receivable and Payable therefore
offers a parallel update mode that you can activate for specific categories of mass runs. Cash
Management is then updated at the end of each process. If the process is terminated before the Cash
Management update, the update takes place when you close the relevant reconciliation key. If the
update also fails here, you can transfer the data recorded separately individually. To do this, in the menu
for Contract Accounts Receivable and Payable choose Periodic Processing -> Execution -> Cash
Management Transfer.
Document Transfer
During the document transfer, you can also transfer the identification of the partner message from SAP
Credit Management (field PRTID) with the header structure.
You can also transfer the identification of the subapplication in Contract Accounts Receivable and
Payable (field SUBAP) with the item structure (BFKKOP).
During the document transfer, you can transfer the company code for the automatic payment transactions
(field PYBUK) with the item
structure (BFKKOP).
You can also transfer the following new structures:
o
BFKKOPREL: Relation between objects
BFKKOPC: Card supplement for open items
Classification Keys
To activate the classification key, in the Implementation Guide for Contract Accounts Receivable and
Payable choose Program Enhancements -> Prepared Enhancements -> Classification Key.
Postings and Documents: Negative Postings
You make the setting for the company code (negative postings possible) in the Implementation Guide for
Financial Accounting under Financial Accounting Global Settings -> Company Code -> Check
______________________________________________________________
SAP AG
68
SAP System
______________________________________________________________
and Supplement Global Parameters.

You make the setting for the document type in the Implementation Guide for Contract Accounts
Receivable and Payable under Basic Functions -> Postings and Documents -> Document ->
Maintain Document Account Assignments -> Document Types -> Maintain Document Types
and Assign Number Ranges.
The main and subtransactions that you want to define for a negative clearing (example: Payments on
Account) are in the Implementation Guide for Contract Accounts Receivable and Payable under Basic
Functions -> Postings and Documents -> Document -> Maintain Document Account
Assignments -> Maintain Subtransactions.
Transfer Postings in Account Maintenance
You define the short account assignments in the Implementation Guide for Contract Accounts Receivable
and Payable under Basic Functions -> Open Item Management -> Short Account Assignments for
Transfer Postings in Account Maintenance.
You maintain the tolerance groups under Basic Functions -> Postings and Documents -> Document
-> Tolerance Groups for Amount Limits and then the entries Define Tolerance Groups and
Assignment of Tolerance Groups to Users.
Arrears Surcharges
To create the installation-specific function module for event 0104 and to register, in the Implementation
Guide for Contract Accounts Receivable and Payable choose Program Enhancements -> Define
Customer-Specific Function Modules.
To define the accounts to be posted to in the case of arrears surcharges, choose Basic Functions ->
Postings and Documents -> Document -> Define Account Assignments for Automatic Postings
-> Automatic G/L Account Determination -> Define Accounts for Arrears Surcharges.
Mass Postings and Cash Management
You activate the parallel update of Cash Management for selected processes via: Technical Settings
-> Activate Parallel Update of Cash Management.
1.3.39 Prenotifications
Use
As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), the following prenotification
functions have been added:
o
The Create Prenotification File program has been enhanced to cover requirements for Denmark.
SAP delivers a new payment medium format, PBS_PRENOTE, required for sending prenotification
files to the Danish clearing house PBS.
The Process Return File program has been enhanced to handle incoming files in formats DK603 for
Denmark, AUTH for Finland, and ACH for the United States. It additionally creates a PBS605 file
to send back to the Danish clearing house, PBS, if required; and it processes bank statement data
contained in the return file sent by the US clearing house, ACH.
______________________________________________________________
SAP AG
69
SAP System
______________________________________________________________
A Business Add-In is available for Denmark that enables you to delete business partner CPR and CVR
numbers after you have processed the return file from PBS. You can create an implementation in
Customizing for Financial Accounting, under Contract Accounts Receivable and Payable ->
Business Transations -> Payments -> Incoming/Outgoing Payment Processing -> Add-In:
Deletion of CPR/CVR Numbers (Denmark).
1.3.40 New Reports

Use
Report RFKK_MA_SCHEDULER
The program RFKK_MA_SCHEDULER creates and starts new mass activity runs. Once the run has
started, the program monitors all parallel jobs started.
This program is particularly helpful if you want to schedule and monitor mass activities using the
Schedule Manager or your own report.
1.3.41 Requests
Use
Printing Requests
You can print requests and standing requests as of Release 4.72. All header data on the request and all
request items with additional information on the business partners and contract accounts are available for
the printout of a request. All execution dates and special dates are also available for the printout of
standing requests. Generation and printout occur with events 0766: Print Request and 0767: Generate
Request Printout with correspondence 0039 Request; correspondence type 0039 uses form class
FI_CA_REQUEST. SAP provides sample form FI_CA_REQUEST_SAMPLE_SF.
Entering Notes
You can enter notes for requests and standing requests. If you generate documents from requests, the
notes are copied over into the notes on the documents.
Business Blocks
You can set the clearing block for request items payment/dunning/ interest and clearing blocks that are
copied into the documents when the documents are generated. You can enter a block reason and validity
period for each request item and block.
Entering Documents for each Request Item
If you create requests with lots of lines and in some circumstances several business partners and contract
accounts, this can cause quite a number of documents that can no longer be represented clearly. For this
reason, you can only generate documents from requests and standing requests for each request item. You
define the corresponding specifications for requests for each request category in Customizing.
Multi-Level Control
______________________________________________________________
SAP AG
70
SAP System
______________________________________________________________
You can also enter requests and standing requests with a tax code that contains several tax rates. The
calculated tax amount that is displayed in the request item is determined from the total of amount of the
individual tax rates.
Classification Key in Request Items
You can enter the new field Classification Key in the request items if you have activated the standard
enhancement for the classification key. As the classification key is a header field of the document you can
only enter different classification keys in a request if you generate documents for each request item.
Displaying Requests in Account Balance
By defining corresponding function modules for events 1203, 1209 and 1211 you can display requests
and standing requests in account balance. SAP provides function modules
FKK_EVENT_1203_REQUEST, FKK_EVENT_1209_REQUEST and
FKK_EVENT_12011_REQUEST for this that you can define for the events mentioned or use as
templates for your own function modules .
BAPIs for Processing Requests
In the future you will be able to use BAPIs to process requests and standing requests (see release
information BAPIs).
Approving Requests
Until now you could only approve requests through workflow. As of Release 4.72 you can approve
requests using a worklist. You define which classes and categories of requests should be approved
through a worklist in Customizing.
Event 5510 was enhanced for a customer-specific differentiation between approval by worklist or by
workflow. You can also suppress the entry of an approval reason for event 5510 when starting the
workflow.
To generate documents for each request item, set the indicator Document for each item in the IMG of
Contract Accounts Receivables and Payable, under Basic Functions -> Requests -> Document
Creation -> Define Specifications for Document Creation.
You define which requests should be approved per request class, request category, or document type
through a worklist in the IMG of Contract Accounts Receivable and Payable, under Basic Functions ->
Requests -> Define Settings for Approving Requests .
1.3.42 Processing of Returns

Use
Read Returns Data from Archive
Via transaction FPO9, (SAP menu: Payments -> Returns -> Returns Lot), you can display returns that
have already been archived. Note that when you are archiving, archived returns are no longer available
for the determination of the number of returns an important value for determining the returns activities.
Zero Total Tax Items
______________________________________________________________
SAP AG
71
SAP System
______________________________________________________________
If charges are posted for a return, and the charges have a tax code with a tax rate of 0.0%, the system
creates zero total tax items and displays these in the returns document.
Automatic Creation of Returns Lots
At the time of creation, you can create the manual posting items Type of Posting = 3 directly.
Check for Changed Bank Details
You can check for a return whether the bank details of the partner have changed since the last payment
run. If this is the case, you can either use an alternative returns reason, or you can define your own
activities to be carried out by the return via event 0293.
Version Numbering and New Fields in the Returns History
The new activity fields and the version numbering have been included in the returns history; you can
display both using the display variant.
Selection via Payment Form Number
When you are assigning payments, you can also use the payment form number as selection criterion.
New Returns Category "External Payment Collector"
If a confirmation of a payment receipt forwarded by a payment collector is incorrect, a return occurs. You
have to process such returns in a separate account not the bank clearing account for bank returns. You
can determine the G/L account required in the automatic account determination using the new returns
category 05 (External Payment Collector).
Reversal of Returns with a Clarification Document
From Release 4.72, you can also reverse returns with a clarification document. During the reversal of the
document (SAP menu: Document -> Reverse), a returns lot that has already been closed is reopened
and, if necessary, a new reconciliation key created, and you can then process the clarification case again
in the returns lot. The creditworthiness of the business partner concerned is reset accordingly.
Save Display Variant for Returns Display
In the header of the returns lot you can save a user-dependent line layout variant for data entry.
You make the settings for the new returns category External Payment Collector in the Implementation
Guide for Contract Accounts Receivable and Payable under Business Transactions -> Returns ->
Define Charges Accounts for Returns.
1.3.43 Integration of Schedule Manager in Contract Accounts Rec. and Pay.

Use
From Release 4.72, you can schedule mass activities in Contract Accounts Receivable and Payable with
the program RFKK_MA_SCHEDULER - Schedule Mass Activities using the Schedule Manager (see
SAP menu: Periodic Processing -> Mass Processing Administration).
In addition, the following periodic programs have been changed over so that you can also schedule these
with the Schedule Manager:
______________________________________________________________
SAP AG
72
SAP System
______________________________________________________________
Technical Names
Name
RFKKFIKEYCLOSE
Automatic Closure of
Reconciliation Keys
RFKKABS1
Check Totals Tables
RFKKGL00
Transfer of FI-CA Totals Records to

General Ledger
RFKKCOPA00
Transfer of Account Assignment Data to

Profitability Analysis
RFKKPCDS
Bill Payment Cards
RFKKBIB0
Document Transfer
RFKKZE00
Payment Lot Transfer
RFKKRL00
Returns Lot Transfer
RFKKCM00
Data Transfer for Manually Issued

Checks
RFKKCR00
Transfer of Cashed Checks
RFKKKA00
Transfer of Data from Account Statement to

Payment/Returns Lot
RFKKAV00
Transfer of Payment Advice Notes from

Sequential File
RFKKCOPM
Read Collection Agency File
RFKKRD00
Post Revenue Distribution
1.3.44 Stop Future Payment (Denmark)

Use
As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), you can generate a file to
______________________________________________________________
SAP AG
73
SAP System
______________________________________________________________
send to PBS to cancel a future (within two business days) direct debit payment for a business partner. To
do so, from the SAP Easy Access menu, choose Accounting > Financial Accounting > Contract
Accounts Receivable and Payable > Payments > Payment Run -> Stop Future Payment (DK).
1.3.45 Tax Reporting in Contract Accounting (New)

Use
As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), you can prepare value-added
tax (VAT) reporting with the new program, Tax Reporting in Contract Accounting (RFKKTX00).
A new Business Add-In, FKK_TAX_REP_00, is available that enables you to modify the list layout to
cover country-specific requirements. An implementation is delivered for Mexico,
IMP_MX_TAX_REP_00.
Note, also, that a new function module is delivered for Mexico, FKK_MX_EVENT_0934, which you
must assign to event 934 in Customizing for Financial Accounting, under Contract Accounts
Receivable and Payable -> Program Enhancements -> Define Customer-Specific Function Modules
(assign under Installation-Specific Function Modules). Refer to the function module documentation for
more information.
1.3.46 Write-Offs
Use
In the transaction Write-Off (FPO4), you can enter notes for a write-off document created. To do this, in
the menu choose Extras -> Notes -> Enter Notes.
1.3.47 Generic Withholding Tax Reporting (Enhanced)

Use
As of Release 4.72 for Contract Accounts Receivable and Payable (FI-CA), Generic Withholding Tax
Reporting has been enhanced to enable you to select withholding tax data from FI-CA.
Under the group box Further Selections, you can select which application the system is to retrieve data
from when you run the program, and specify other parameters relevant to FI-CA.
A new Business Add-In, FKK_WTAX_REP00, is available that enables you to enhance the report to
cover country-specific requirements in the output. You can add parameters to the selection screen and
modify business partner and withholding tax data. An implementation is delivered for the United States,
IMPUS_IDWT_1099MISC.
______________________________________________________________
SAP AG
74
SAP System
______________________________________________________________
1.3.48 New Entries in Contract Accounts Menu for Media Sales & Dist. 4.72
Use
The following transactions have been added to the SAP menu in the areas listed below:
o
Contract Accounts Receivable and Payable for Media Sales and Distribution:
-
Account:
-> Other Information -> Dispute Cases for Account Balance (FPDM00)
Payments:
-> Cash Journal -> Cash Journal Evaluation (FPCJR)
-> Payment Run -> Enter Registration ID (DK) (FPDKCPR)
-> External Payment Banks -> Clarification of Transferred Payments (FPCVS)
Standing Request:
-> Approve Request (FKKORDA)
Master Data:
-> Business Partner -> Maintain Bank Data (FPP4)
-> Business Partner -> Enter Registration ID (DK) (FPDKCPR)
Periodic Processing:
-> For Contract Accounts -> Boleto -> Mass Run (FP01)
-> For contract Accounts -> Boleto -> Single Generation (FBO1S)
-> For Contract Accounts -> Boleto -> Mass Reversal (FBO1C)
-> For Contract Accounts -> Reversal of Check Payments (FPCHS)
-> For Contract Accounts -> Dunning Notice -> Forward Telephone List(FPVT)
-> For Contract Accounts -> Set Processing Locks (FKLOCK2)
-> For Contract Accounts -> Delete Processing Locks (FPLKDEL)
-> Forward Postings -> Preparation -> Recreate Totals Records (FPT6) moved and
renamed from Delete Data -> Totals Records (FPT6))
-> Forward Postings -> Execution -> Cash Management Transfer (FPCF)
-> Closing Preparation -> Reverse Foreign Currency Valuation (FPW2)
-> Correction postings:
The sequence of the Correction Posting and Closing Preparation nodes has been changed in
the menu so that the Closing Postings node is displayed first followed by the Correction
Postings node in the menu.
-> Evaluation of Open Items -> Evaluate (Parallel Processing) (FPO4P)
-> Extraction for Business Information Warehouse -> Extract Installment Plans (FPIPBW)
-> Archive Data -> Foreign Currency Valuation (FPAR09)
-> Archive Data -> Clearing History (FPAR10)
-> Archive Data -> Doubtful Entries (FPAR11)
-> Delete Data -> Invoice Creation by Third Party (FPAR12)
-> Delete Data -> Total Records (Following Document Archiving) (FPARS1)
-> Delete Data -> Logs of Submissions for Collection (FP03DML)
-> Delete Data -> Entries in Dunning Telephone List (FPVT1)
Administration of Mass Processing:

-> Schedule Mass Activity (FPSCHEDULER)
______________________________________________________________
SAP AG
75
SAP System
______________________________________________________________
-> Enhanced Message Management -> Display Clarification List (EMMACL)

-> Enhanced Message Management -> Clarification List with Short Cut (EMMACLS)
-> Enhanced Message Management -> Clarification with Automatic Processes
(EMMACAP)
-> Enhanced Message Management -> Creation of Clarification Cases in Mass Run
(FPEMMACGEN)
-
Administration of Customer Portal:

-> Customer Messages Worklist (IQS8)
-> Create Customer Notifications (FPACTEN)
Administration:
-> Create Search Index for Archived Payment Lot (FP05ARC)
1.4 IS-M-SD
Media Sales and Distribution
1.4.1 CIC - New Functions for Creating Business Partners (Enhanced/Modified)

Use
As of SAP Media 4.72, the functions for creating business partners have been revised as follows in the
Customer Interaction Center (CIC):
o
The same address fields as those available during creation or modification of an SAP Business
Partner are now available to you when you enter or create address data.
During creation of a business partner in dialog processing, the master data for the SAP Business
Partner (full screen transaction) is accessed from the Business Partner Search and Processing (short
dialog) dialog box. The system does not copy all data that was entered on the dialog box into the full
screen transaction. Data that is not transferred includes additional street information or bank data.
During creation of a business partner in the background, all data is copied into the full screen
transaction and made available here.
Both functions are available to you in a new dialog box. You can use the new classified order entry
indicator to define whether you want to use the new or existing dialog box to enter the business
partner master data.
The ISM_BP_CREATE Business Add-In can be used to modify the layout and fields on the new
dialog box. You can use the BAdI to modify the title and border text on the dialog box. You can also
define which fields are displayed and which fields shown are mandatory.
Simplified creation of a sales or media customer in an additional sales area using the context menu
in the Data Environment.
Simplified creation of an existing business partner in an additional role using the context menu in
the Data Environment.
During creation of a business partner, you can now define a default sales area according to the
business partner role to be created. If you create a media customer, you can define a default
Advertising Management sales area. If you then create a sales customer, you can define a default
sales area for Media Sales and Distribution.
______________________________________________________________
SAP AG
76
SAP System
______________________________________________________________
During creation of the business partner, the CIC memory, which always contains the last sales area
used for the corresponding SAP Media component, is read first. If no sales area can be determined
from the memory, the system determines this from the Customizing settings. The memory does not
usually contain a sales area during business partner creation, since the memory is deleted after every
contact is terminated.
Default sales areas are recorded for each SAP Media component in Customizing. This setting is
recommended for agents who work with both SAP Media components.
The CreateFast BOR method for the BUSISM007 (ISMBusinessPartner) usiness object still provides
functions for shortened business partner entry.
Settings for the Business Partner Search/Processing component are made as follows in Customizing:
SAP Media -> Customer Interaction Center (CIC) -> Make Settings for the Business Partner
Search/Processing Component
Observe the following possible settings here:
o
Search areas and option of switching the search area
Country as a default setting
Number of items
Sales organization, distribution channel and division for each component as a default setting.
New Classified Order Entry
1.4.2 CIC - New Functions in the Business Partner Search (Enhanced)

Use
In SAP Media 4.72, the following enhancements have been made to the business partner search in the
o
You can specify whether or not it is possible to search by household or business partner and
whether or not it is possible to switch between these two search areas. The system displays search
fields for the search area selected or specified as default.
A Next Contact pushbutton has been added to the other pushbuttons Clear All Fields and End
Contact. The buttons serve the following purpose:
-
Next Contact: The contact is completed. The search fields are reset to the last values entered. If
you press the pushbutton again, the system initializes all the fields. The call is not ended.
For example, the caller wants to make changes for two business partners with the same address
one after the other. The 'Next Contact' function completes the process for the first business
partner (and creates a contact document) and enters the data entered last in the search fields so
that a new search can be executed.
Clear All Fields: The search fields are reset to the values entered last. If you press the
pushbutton again, the system initializes all the fields. This allows you to perform a second
______________________________________________________________
SAP AG
77
SAP System
______________________________________________________________
search if the wrong business partner was identified without having to enter all the search data
again. (The pushbutton does not affect the contact or the call or the data displayed in the
components of the navigation and application area.)
For example, this function can be used to cancel an identification that was made by mistake.
The user can start a new search immediately using the search data entered last.
-
End Contact: The contact is completed. The search fields and all the components of the
navigation and application area are initialized. The call is ended.
To avoid long runtimes when reading and displaying data on a business partner wrongly identified
in the CIC - for example, when processing a major customer with a large dataset - you can specify
that the system is to notify you if the dataset exceeds a certain volume so that you have an
opportunity to correct any errors beforehand.
To prevent the system from displaying a business partner's old addresses, you can specify a time
restriction for displaying the business partner's addresses. You can define the period for address
selection using the user parameters ISM_CIC_BP_FROM and ISM_CIC_BP_TO. You can enter a
number of days for the parameter ISM_CIC_B_FROM to specify a period in the past starting from
the current date. For example, current date 365 = 1 year ago. Similarly, by entering a number of
days for the parameter ISM_CIC_BP_TO, you can specify a period in the future starting with the
current date.
As an alternative to displaying the business partner hit list in a dialog box, as was the case in
previous releases, you can now integrate a new hit list in the navigation or application area. If you
want to use the new hit list, assign the component ISM_HITLIST to the navigation or application
area in Customizing. The advantage of the new hit list is that the search result is displayed until the
contact is ended, so that you can proceed to a different business partner in the list without having to
perform a new search.
You can use the Business Add-In ISM_BP_SEARCH to add customer-specific functions to the hit
list in the business partner search. For example, you could add a function for retrieving details on a
business partner in the hit list, or for identifying duplicates.
The following methods have been added to the Business Add-In ISM_CIC_BP_SEARCH:
-
BP_SEARCH_WITH_DOCNR: Search for business partners if you use your own document
classes
PRELIMINARY_BUSINESS_PRTN_SRCH: Preliminary business partner search (upstream

from the standard search)
HITLIST_PREPARE_FOR_WORKSPACE: Enrich and format hit list (workspace)
You can make the settings for the component Business Partner Search/Processing in Customizing under
SAP Media -> Customer Interaction Center (CIC) -> Make Settings for Business Partner
Search/Processing Component.
Please note the following possible settings:
o
Search areas and the option of changing the search area
Specifying a default country
Number of items
______________________________________________________________
SAP AG
78
SAP System
______________________________________________________________
Specify a default sales organization, distribution channel, and division for each component.
New fast data entry
1.4.3 CIC - Reset to Default Workspace When Contact Ends (Enhanced)

Use
As of SAP Media 4.72, you can specify in the configuration profile of the application and navigation
area that the default workspace is to be displayed automatically after a contact is ended.
Restrictions:
o
If the default workspace was deleted in the meantime, it is not created again automatically.
Workspaces created dynamically during a contact are not deleted. You can make this setting by
selecting the Workspace Lifetime indicator for the action box call.
1.4.4 CIC - Component Layout (Enhanced)

Use
As of SAP Media 4.72, the display options in the Customer Interaction Center (CIC) have been enhanced
as follows:
o
Full screen mode for the navigation and application area

You can change the size of the navigation or application area using a pushbutton.
A button is available for activating or hiding the full screen display of the navigation or application
area if you want to incorporate the invisible component LAYOUTSWITCH in the framework and
include the FRW_LAYOUT_BIG_NAV and FRW_LAYOUT_BIG_APPL function codes in the GUI
status.
Docking control for incorporating an ad editor

Two frameworks, to which the invisible component ISMAM_EDITOR has been assigned, are
supplied. These frameworks are incorporated in the CIC profiles C_STD_C (17 inch screen
resolution) and C_STD_C2 (21 inch screen resolution) supplied. The ISMAM_EDITOR
component provides you with an HTML docking control in which an ad design editor can be
incorporated in the right hand section of the framework. You could only previously display the
editor in a separate dialog box or on a tab page in the navigation area.
The HTML docking control occupies a third of the right hand section of the screen in its default
display format. You can increase or decrease its size using the corresponding button. Docking
control can also be activated in the full screen mode so that you can use the entire screen area to
design the ad. The new framework does not contain a navigation area. The application area has
been increased so it now occupies the entire screen width and therefore provides a user-friendly
environment for editing ad orders in conjunction with docking control.
You can also use a button to switch the application area to full screen display in this framework.
Docking control is minimized dynamically here.
______________________________________________________________
SAP AG
79
SAP System
______________________________________________________________
The settings for the new framework are made in Customizing. Pay particular attention to the following
settings here:
o
Assign Invisible Components to Framework IDs
Make Settings for the Ad Spec Editor Component
Define Toolbars and User-Defined GUI Status
1.4.5 CIC - Additional Data in the Data Environment and HTML Customer Overview
(New)
Use
As of SAP Media 4.72, you can display additional data in the data environment and the HTML customer
overview in the Customer Interaction Center.
The following new nodes have been added:
o
M/SD: Offer
M/SD: Order research for an order item
M/SD: Bank returns research for a billing document
Contract account for business partner

-
SD: Order (can be grouped according to order types)

-
Open items for contract account
Items in SD order
SD: Contract (can be grouped according to contract types)

-
Items in SD contract
SD: Billing document
SD: Invoice list
See also
IS-M/AM release note Contracts in the Data Environment
1.4.6 CIC - Display Variants in the Data Environment (Enhanced)

Use
When the system sets up the data environment in the Customer Interaction Center (CIC), it reads a large
number of objects and dependent data that are not required for simple business transactions but that still
have a serious effect on performance. As of SAP Media 4.72, you can use the Business Add-In
______________________________________________________________
SAP AG
80
SAP System
____________________________________________________________
ISM_CIC_NAVVIEW to define display variants that override the Customizing settings for the data
environment.
Example 1:
You define a profile for the data environment that contains the format for all relevant objects and specify
whether or not these objects are to be displayed in the data environment and if so, how. You can set up
the BAdI methods in such a way that the user is only presented with a limited selection of objects once
the business partner has been identified. If the user discovers in the course of the contact that they need a
wider overview of the customer's data, they can choose a variant defined using the BAdI to display
additional objects.
Example 2:
You use the BAdI to change the time horizon for selecting relevant objects.
1.4.7 CIC - Accessing and Executing Workspaces Dynamically (New)

Use
As of SAP Media 4.72, you can use the business object BUSISMCIC (CIC support object) in the
Customer Interaction Center (CIC). The business object provides methods, which you can use to do the
following:
o
Access an existing workspace from the context menu in the data environment and bring it to the
foreground:
-
EditMAMOrder: Brings M/AM order entry to the foreground
DisplayMAMOrder: Brings the M/AM order list to the foreground
DisplayMSDOrderList: Brings the M/SD order list to the foreground
EventRaise: Can be used to bring customer-specific workplaces to the foreground.
Create a workspace dynamically from the action box or the context menu in the data environment:
-
StartBSPWorkspace: Starts a workspace to access BSP applications
StartWorkspace: Starts a workspace of your choice
1.4.8 CIC - New Scripting Options for M/SD-Specific Processes (New)

Use
As of SAP Media 4.72, additional events are available for triggering scripting. This means it is possible to
match up scripting texts and (M/SD) business transactions more precisely.
The script texts defined for the CIC are either displayed in the dialog boxes for the short order dialogs or
in an additional display dialog box alongside order maintenance in the full dialog.
The text displayed in the dialog boxes in the short dialogs can be made dependent on the data entered
here.
The following events are available (the texts for events during an action are displayed in the dialog box
______________________________________________________________
SAP AG
81
SAP System
_____________________________________________________________
for the short dialog or alongside the full dialog, and those after an action are displayed in the normal
scripting area upon return from the transaction in question):
Event
MSD_IT_CANCEL_B
MSD_IT_CANCEL_A
MSD_IT_COMPL_B
MSD_IT_COMPL_A
MSD_IT_CREA_B
MSD_IT_CREA_A
MSD_IT_GIFT_B
MSD_IT_GIFT_A
MSD_IT_OBJCH_B
MSD_IT_OBJCH_A
MSD_IT_PAYM_B
MSD_IT_PAYM_A
MSD_IT_RECREA_B
MSD_IT_RECREA_A
MSD_IT_SUSP_B
MSD_IT_SUSP_A
MSD_IT_TRAVEL_B
MSD_IT_TRAVEL_A
MSD_IT_TRSF_B
MSD_IT_TRSF_A
MSD_IT_TRSFTR_B
MSD_IT_TRSFTR_A
MSD_IT_UNLIM_B
MSD_IT_UNLIM_A
MSD_ORD_CHNG_B
MSD_ORD_CHNG_A
MSD_ORD_CREA_B
Meaning
During creation of a termination
After creation of a termination
During creation of a complaint
After creation of a complaint
During creation of an item
After creation of an item
During creation of a gift item
After creation of a gift item
During a change of object
After a change of object
During a change to the payment frequency
After a change to the payment frequency
During restart
After restart
During creation of a suspension
After creation of a suspension
During creation of a redirection
After creation of a redirection
During creation of a transfer item
After creation of a transfer item
During conversion of a FI/TI
After conversion of a FI/TI
During creation of an unlimited change
After creation of an unlimited change
During a change to an order
After a change to an order
During creation of an order
MSD_ORD_CREA_A
MSD_ORD_DISP_B
MSD_ORD_DISP_A
After creation of an order

During display of an order
After displaying an order
The texts are displayed in an HTML browser that is embedded in the relevant GUI window.
To display the texts, which are recorded in CIC Customizing as SAPscript texts, in this way, please note
the following:
o
One way of displaying the texts in the CIC is to integrate the visible component ISM_SCRIPT
directly in an area of the framework.
______________________________________________________________
SAP AG
82
SAP System
______________________________________________________________
If the scripting is to be located on a tab in the navigation or application area, you can do this using
the component (workspace) ISM_SCRIPT.
o
The standard component HIDDEN SCRPT and the IS-M component ISM_HSCRIPT are required as
hidden components.
Further data can be made available in the script text using the enhancement JYCIC001. These are
then available as SAPscript text symbols in the script text.
The SAPscript texts in HTML format contain the usual HTML tags. Since this makes maintenance
in the SAPscript Editor somewhat messy, you may prefer simply to link to the actual HTML text
from the SAPscript text.
1.4.9 CIC - Texts for Business Partner (Enhanced)

Use
As of SAP Media 4.72, you can determine which texts are displayed in the application area of the
Customer Interaction Center (CIC) for the business partner and in Media Sales and Distribution for the
objects order, order item, and complaint.
For example, you can specify in Customizing which types of texts (text objects, text IDs) are to be listed
in what order, whether or not notes from generic object services are to be taken into account, and whether
or not the existence of a text is to be indicated in the tab title.
The following texts are available:
o
Business partner
-
Business partner
Central customer texts
Customer texts for accounting
Customer texts for sales and distribution
Central vendor texts
Vendor texts for company code
Vendor texts for purchasing
M/SD order
-
M/SD order item

-
Order header text
Order item text
M/SD complaint
-
Customer complaint
Subsequent delivery information
Carrier information
______________________________________________________________
SAP AG
83
SAP System
______________________________________________________________
Carrier's statement
1.4.10 Campaign Master Data in the Marketing Planner (Changed)

Use
Campaigns in Campaign Management were previously planned in the Marketing Planner in SAP CRM,
then released and transferred to SAP Media. Media-specific attributes, such as validity period, usage, and
template documents, then had to be added in SAP Media for master data maintenance.
As of SAP CRM 4.0 SP 05, you can create, change, and display campaign master data for SAP Media in
the Marketing Planner in SAP CRM. It is no longer necessary to postedit the campaign master data in
SAP Media and switch between the two application components.
You must define your own set type so that a tab for entering the media-specific attributes is displayed in
the Marketing Planner in SAP CRM. On the tab page, you can implement a BSP application that provides
the functions for editing the media-specific attributes on further tab pages:
o
Campaign tab: The tab page is subdivided into the areas Campaign, Assignment, and Sorting. Each
of these subareas is also displayed as a tab page.
-
Campaign tab: Displays campaign data, such as Description, Validity period, Use.
Assignment tab: Displays template documents assigned to the campaign document and those
that can be assigned to the campaign in a hierarchy tree, split according to Media Sales and
Distribution and Advertising Management.
Sorting tab: Display sequence of template documents, split according to Media Sales and
Template tab: Displays the existing template documents, split according to Media Sales and
Distribution and Advertising Management. You can also create and search for template documents.
M/SD Promotional Data: Displays promotional data, from which you can access the corresponding
processing functions in Media Sales and Distribution.
See also
For further technical data, see note 627927.
1.4.11 IS-M-SD-PS
1.4.11.1 IS-M-SD-PS-SL
Periodical Sales and Distribution

Sales
1.4.11.1.1 Transferring Billing Documents to Human Resources (New)

Use
As of SAP Media 4.72, you can transfer billing documents to Human Resources. You specify the transfer
______________________________________________________________
SAP AG
84
SAP System
______________________________________________________________
destination in the Customizing settings for the sales document types. The following transfer destinations
are possible:
o
Financial Accounting
Human Resources
If you do not specify Human Resources as the transfer destination when defining the sales document type
(order type), the billing documents are transferred to Financial Accounting as before. When an order is
created, the system determines the transfer destination from the order type. If you specify in Customizing
that the data is to be transferred to Human Resources, the system automatically determines the new
transfer type 'H' (transfer to Human Resources).
Notes on data transfer to Human Resources:
o
The payment method in the order is not relevant
Revenue accrual does not take place for billing document transfer
Effects on System Administration

Billing document transfer to Human Resources is performed by the report RJFTRANSFERHR. Create
variants for the background jobs.
Before you can use the function for transferring billing documents to Human Resources, you must make
the following settings in Customizing:
o
Specify transfer destination Human Resources in sales document type definition
Check condition types for pricing in order/billing, if applicable
Define wage types in Human Resources
Assign wage types to condition types
1.4.11.1.2 IS-M-SD-PS-SL-O
Order
1.4.11.1.2.1 Enhancements to Internet Application Components (New)

Use
In SAP Media 4.72, the following enhancements have been added for Internet application components
(IACs):
o
Function Check Data.

This function is optional and can be displayed on the website if you wish. The function performs the
formal data checks and displays a message notifying the user that the data is correct. For example,
the function can be used in the IAC Change Payment Data to check a bank key. When the customer
enters a bank key and then executes this function, the name of the corresponding bank appears
automatically. If they have entered an invalid bank key, an error message appears. This allows the
customer to check their entries more effectively.
Business partner role in order
______________________________________________________________
SAP AG
85
SAP System
_____________________________________________________________
When you define a logon scenario for an IAC, you can now also specify a role for the business
partner in the order. This has the following effect:
-
When a business partner logs on with an order number, the system checks whether they have
the specified role in this order.
When selecting the orders to be changed in the IACs Vacation Service, Change Payment Data,
and Create Complaint, the system only includes orders in which the business partner who has
logged on has the specified role.
This allows you to define the variants of the Internet application components more flexibly
according to the role of the customer. This is particularly relevant when the roles Sold-To Party,
Ship-To Party, Bill-To Party, and/or Sales Agent are occupied by different persons in the same
order. For example, the Ship-To Party in an order might be able to change an address or create a
redirection, but changes to the payment data would have to be made by the Sold-To Party.
o
Backdated subscription orders

You can now also create backdated subscription orders with the IAC Subscription Sales.
Start IAC Subscription Sales with logon screen

You can also have the IAC Subscription Sales display a logon screen when first accessed. This
means the customer can log on in any of the four possible roles. This is controlled by an OK code,
which is specified when the IAC is called. The OK codes for the individual roles are displayed with
the corresponding pushbuttons in the layout of the logon screen.
1.4.11.1.2.2 Function for Displaying Amortization Log (New)

Use
As of SAP Media 4.72, you can display the amortization log in the liability account overview for delivery
and renewal subscriptions.
The amortization log gives an overview of the amortized deliveries in a cycle. Deliveries for which
complaints have been received are highlighted in color.
1.4.11.1.2.3 Terminating Subscriptions with Change Items (New)

Use
As of SAP Media 4.72, you can terminate subscription items even if the termination date is in the validity
period of a subsequent limited or unlimited change. If this is the case, the system automatically limits or
deletes the subsequent item.
This new feature allows you to terminate a trial subscription with automatic transformation to chargeable
when the trial item ends. When you do this, the system automatically deletes the subsequent standard
item.
______________________________________________________________
SAP AG
86
SAP System
______________________________________________________________
1.4.11.1.2.4 Donating Refunds (New)

Use
As of SAP Media 4.72, you can make donations with refunds from terminated subscriptions or
suspensions. Until now, the credit memo was always sent to the subscriber.
You can now choose one of the following options:
o
Tip for carrier
Donation to charity
Donation to another business partner
You determine the way in which the credit memo is to be used by selecting a refund type. If you do not
specify a refund type, the credit memo is returned to the original payer.
If you specify refund to another business partner, the following applies:
o
When a subscription is terminated, you can determine a business partner according to their category
and delivery end reason, using the customer exit EXIT_SAPMJ45A_017.
When a suspension is created, you must enter the business partner in the payer field on the billing
details screen.
You can only use this function if you use Contract Accounting (IS-M/CA). Main transactions and
subtransactions are assigned in FI-CA Customizing according to the refund type.
The donated amounts are gathered in FI-CA (main transaction 4200) and forwarded to the carrier or
charity by means of a transfer posting (report RJK_ADDPAYMENT_REBOOKING_SAMPL).
This function is also suitable for processing donations to NIE projects (Newspapers in Education, USA).
This function replaces the customer exit EXIT_SAPMJ45A_016 in the enhancement J45A0013 that was
required in releases 4.64 and 4.71 to determine the payer as the recipient of NIE donations according to
the suspension reason.
You can copy the refund type from the legacy system for suspensions or terminations.
If you want to use this function, you need to make the following Customizing settings:
o
Define possible refund types
See also
Additional Payments for Renewals
______________________________________________________________
SAP AG
87
SAP System
______________________________________________________________
1.4.11.1.2.5 Proportional Billing for Limited Changes in Renewals (Changed)

Use
As of SAP Media 4.72, you can perform proportional billing for limited changes to renewal subscriptions.
Proportional billing is relevant when creating credit memos for suspensions and debit memos for
redirections. You can perform billing as follows for limited changes relevant to billing that extend
beyond the expiration date:
o
Proportional billing of credit or debit memo amount up to expiration date

(Until this point, it is still uncertain whether the customer will want to extend their subscription or
whether a receivable will be created for the subsequent cycle. For this reason, billing for the
subsequent index is suppressed for the subsequent cycle until an incoming payment is received.)
Billing of remaining amount after incoming payment for subsequent cycle
Proportional billing for limited changes takes place when the following indicators are initial in the order
type-item type assignment (redirection and suspension):
o
Billing in full
Bill to end of billing period
1.4.11.1.2.6 Fixing the Expiration Date for Performance-Related Renewal

Subscriptions (New)
Use
As of SAP Media 4.72, you can prevent automatic adjustment of the expiration date when unlimited
changes are made to renewal subscriptions (for example, quantity increases), allowing you to retain the
current payment frequency.
For this purpose, you can perform a difference calculation (retroactive billing and recalculation) for the
period up to the expiration date, which allows you to clear receivables or credit memos from unlimited
changes with the payment for the next cycle.
This option is particularly suitable for the payment method credit card.
Note: The retroactive billing process results in an open item for invoice payers, which must then be
dunned in Financial Accounting. Monitoring does not take place here because the expiration date remains
the same.
When you enter an unlimited change that is before the expiration date, you can decide whether or not
retroactive billing is to take place (which would mean that the expiration date would remain the same).
You can also define retroactive billing as the default setting in the customer exit EXIT_SAPMJ45A_011.
Retroactive billing in renewal subscriptions is only possible if the Retroactive Billing indicator is selected
in the order type.
______________________________________________________________
SAP AG
88
SAP System
______________________________________________________________
1.4.11.1.2.7 Retroactive Billing for Period Renewal Subscriptions (New)

Use
As of SAP Media 4.72, you can retain the payment frequency when unlimited changes before the
expiration date are made to period renewal subscriptions (for example, quantity increases).
To achieve this, you can perform retroactive billing and recalculation for the remaining period before the
expiration date. The difference amount is cleared with the payment amount for the next cycle.
When you enter an unlimited change that is before the expiration date, you can decide whether or not
retroactive billing is to take place. You can also define retroactive billing as the default setting in the
customer exit EXIT_SAPMJ45A_011.
Note: The retroactive billing process results in an open item for invoice payers, which must then be
dunned in Financial Accounting. Since the expiration date remains the same, monitoring does not take
place.
Retroactive billing in period renewal subscriptions is only possible if the Retroactive Billing indicator is
selected in the order type.
1.4.11.1.2.8 Automatic Splitting of Subtractive Changes (New)

Use
As of SAP Media 4.72, you can make backdated changes to billing arrangements in periods that contain
limited subtractive changes (such as redirections and suspensions).
The system automatically splits changes with overlaps. Where the change is a redirection, the system
adjusts the delivery assignments. If the subtractive change has already been billed, you must reverse
billing first.
If an unlimited change results from the acceptance of a renewal offer, the system executes the split
automatically.
1.4.11.1.2.9 Skipping a Monitoring Cycle for Credit Memo Surplus (New)

Use
As of SAP Media 4.72, you can clear credit memos from suspensions and complaints with the payment
for the subsequent cycle for period renewal subscriptions.
Credit memos can be suppressed in billing and only taken into account when creating an offer. The credit
memos result in a reduction in the offer amount.
To allow you to accept and bill the offer at the full sales price for a customer who pays by invoice, you
______________________________________________________________
SAP AG
89
SAP System
______________________________________________________________
must increase the payment amount by the credit memos in the offer, using customer exit
EXIT_SALPJKC4_002 in enhancement JKC4001.
If the total of the credit memo amounts is greater than the offer amount, the cycle can be accepted
automatically without a payment. This can be done using customer exit Exit
EXIT_SAPLJKREMIND_008 in enhancement JKRENEW0. If you select the indicator
JKREMIND-XAUTO_ACCEPT in the customer exit, the system accepts the offer automatically and
creates a billing index. Billing must be suppressed for this index until the next cycle has been accepted.
You can determine whether billing is to be suppressed using the customer exit EXIT_SAPLJF60_014 in
enhancement JF600008. Please note that credit memos cannot be suppressed for subscriptions that have
been terminated.
1.4.11.1.2.10 Additional Payments for Renewals (New)

Use
As of SAP Media 4.72, you can record additional payments for renewal subscriptions. The following
types of additional payment are possible:
o
Donation (for example, to charity)
Tip (for carrier)
You can only use the function for processing additional payments if you use Contract Accounting
(IS-M/CA).
The process for additional payments comprises the following steps:
o
Post payment to subscribers contract account

A posting document is characterized by the main transaction 3100 and the special clearing
restriction 4. Depending on the payment method, you can post additional payments in the following
two ways:
-
If payment is made by check, the additional payment is made as it was previously in IS-M/CA,
by means of a separate line item (see also IS-M/CA Integration - Incoming Payment Triggered
by Customer).
New: To make the posting under the reference number from the renewal subscription, you can
set up a special selection category for each additional payment type.
If payment is made using a payment card or by automatic debit, you can enter template data for
the additional payment in the liability account overview for a renewal subscription. When the
renewal offer is accepted, the sum of the offer amount and additional payment amount is
authorized.
The additional payment is recorded in a separate condition record in the billing document.
When the billing document is transferred, two accounting documents are created in IS-M/CA:
the receivable for the offer amount (main transaction 4000) and the additional payment request
(main transaction 4100, statistics key A). Both these documents are cleared by the payment run
and the clearing document gives rise to an actual additional payment (main transaction 3100).
Execute transfer posting (see Transfer Posting Report) based on the documents created in the first
step
______________________________________________________________
SAP AG
90
SAP System
______________________________________________________________

You can use report RJKFTRSF with the new record type 12 to transfer template data for the additional
payment together with the renewal subscription from the legacy system.
If you want to use this function, you must make the following settings in Customizing:
o
Define possible additional payment types
Set up pricing (condition types, requirements, check formulas, enhance pricing procedure)
Define account assignment keys
Assign G/L accounts
Define possible selection categories
See also
Refunds for Renewals
1.4.11.1.2.11 Ending Trial Subscriptions for Period Renewals (Changed)

Use
As of SAP Media 4.72, you can specify an end of validity manually for trial or free items in period
renewal subscriptions. This also applies to items with automatic transformation to chargeable.
In previous releases, the end of the validity period was determined from the number of publication dates
specified in the sales promotion.
Pricing must be set up in such a way that a proportional price is determined for items relevant to pricing.
1.4.11.1.2.12 Bank Control Key Available in Fast Entry (Changed)

Use
As of SAP Media 4.72, the bank control key is available in fast subscription entry (transaction JK07). The
bank control key is required in several countries to check bank details.
The bank control key is displayed in a separate line. If field RJKRG-BKONT is not relevant in your
system, you can hide the line using the dynamic screen modification function. This compresses one line
in the data entry mask.
______________________________________________________________
SAP AG
91
SAP System
______________________________________________________________
1.4.11.1.2.13 Non-Billable Goodwill Deliveries when Payment Is Delayed

(Changed)
Use
As of SAP Media 4.72, you can specify the date to which goodwill deliveries are to be billed for renewals
(liability account overview, Payment Action detail screen).
See also Processing Goodwill Deliveries when Payment Is Delayed.
Example:
Goodwill deliveries are usually billed when a delayed incoming payment is received. To offer the
subscriber an incentive to renew their subscription, you can offer not to bill them for a certain number of
goodwill deliveries. In this case, you can respond flexibly and agree with the subscriber on a date from
which the goodwill deliveries are to be free of charge. The write-off amount for the goodwill deliveries is
determined from the amortized non-billable deliveries.
If you want to process all goodwill deliveries in the same way, do not enter a date and instead, specify the
desired action on delayed payment; for example, bill deliveries, or deliveries free of charge.
If the write-off amount for the goodwill deliveries is not to be taken into account in the offer for the
corresponding cycle, select the indicator 'Do Not Adjust Offer'. Normally, the write-off amount is
deducted from the offer amount. If this is the case, you must not select the indicator.
1.4.11.1.2.14 Additional Filter for Roles (New)

Use
As of SAP Media 4.72, you can filter the orders displayed in the M/SD order list in the application area of
the Customer Interaction Center, so that the list only contains orders in which the business partner has a
specific single role and, additionally, a specific composite role (new).
You can define these composite roles in the Customizing settings for the order list.
1.4.11.1.3 IS-M-SD-PS-SL-C
Complaint
1.4.11.1.3.1 Text Field for Complaint in Short Complaint Dialog (New)

Use
As of SAP Media 4.72, you can enter complaints in a continuous text field in the short dialog for creating
a complaint for a sales order.
______________________________________________________________
SAP AG
92
SAP System
______________________________________________________________
1.4.11.2 IS-M-SD-PS-SH
Shipping
1.4.11.2.1 Attributes for Delivery Viability Determination in a Shipping Order

(New)
Use
As of SAP Media 4.72, you can determine the following data in the shipping order for delivery viability
determination for each item:
o
Reference edition
Delivery type
You can do this using the BAdI ISM_SHIPORDPOS_DELIV.

The reference edition determined by the BAdI and the delivery type override any entries for these
attributes in the shipping order header.
1.4.11.2.2 Market Coverage (New)

Use
As of SAP Media 4.72, you can use the market coverage functions to process distribution of free
publications to households in your distribution areas.
Households are non-personalized business partners whose data can be imported to the system from
external files. When this is done, the addresses in the household master records are compared with those
in the customer master records. Only customers can be addressed personally (by name).
Market coverage means that all the households in a defined distribution area, including those that are not
customers, are taken into account for delivery.
For example, a market coverage product might be a free weekly magazine that mainly contains regional
advertising material and is distributed to all households in the region. The market coverage product is
created in the system as a media product (marked with an indicator for market coverage). Market
coverage products are always assigned to a carrying product. A separate combination with the market
coverage product is defined in the data on the carrying product with the new Market Coverage
Combination indicator.
Market coverage can take place in the following forms for a carrier route (home delivery) or geographical
unit (postal or direct delivery):
o
Market saturation
The product is delivered to all households, regardless of whether or not the residents have a
subscription for the carrying product.
Total market coverage

In this case, the product is only delivered to households that do not receive the carrying product.
You can define delivery viability sets for market coverage products, or use reference products to
determine the carrier routes and geographical units. Exception: reference products cannot be used if ad
______________________________________________________________
SAP AG
93
SAP System
______________________________________________________________
inserts from Advertising Management orders are inserted in the market coverage product.
You can exclude households in certain carrier routes or geographical units from market coverage. When
excluding households from market coverage, you can also assign certain delivery types to the households,
which allows you to set a filter according to the delivery type when generating orders for market
coverage.
The following functions are available for market coverage:
o
Order creation
Shipping orders are created for the households that are to be supplied. Since the number of potential
recipients of the product is recorded for each household, you have the following options:
-
If you perform market saturation, the system creates the corresponding number of shipping
order items for the household.
In the case of total market coverage, the system checks the ship-to parties who belong to the
household to determine whether or not they already receive the carrying product. If they do,
the number of recipients in the household is reduced accordingly. (You can use the default
implementation of the Business Add-In ISM_TMCP_SUB_MERGE to check when the
carrying product is delivered to a ship-to party address.) Shipping orders are created by
program RJVTMCP.
Audit report for market coverage products

Circulation auditing is not possible for shipping orders for market coverage. You can set up a
process for determining the audit report category for each household. (The template function
module ISM_IVW_CATEGORY_FIND_SHIPORD is supplied for category determination. The
module interprets the basic default category for shipping orders, which can be defined in
Customizing according to the delivery type. You can replace the template module with one of your
own.) The audit report is updated to the circulation book.
Circulation planning and shipping documents

Circulation planning for shipping orders takes place using program RJVTMCP_PLANNING. The
standard shipping documents for the shipping order are used for market coverage.
1.4.11.2.3 IS-M-SD-PS-SH-P
Circulation Planning
1.4.11.2.3.1 Customer Exit for Home Delivery Quantities in Deliveries (New)

Use
As of SAP Media 4.72, you can influence quantity specifications in deliveries eries for home delivery
settlement. The following quantity fields have been added to the circulation planning customer exit
JVDE0001:
o
Actual quantity of normal items in a delivery for a carrier
Actual quantity of normal items in a delivery for a service company
Actual quantity of promotional copies in a delivery for a carrier
Actual quantity of promotional copies in a delivery for a service company
______________________________________________________________
SAP AG
94
SAP System
______________________________________________________________
For example, if you want to exclude actual quantities in a carrier's deliveries from home delivery
settlement, you set the corresponding quantities to zero.
1.4.11.2.3.2 Planning of Combinations for Backdated Order Items (Changed)

Use
As of SAP Media 4.72, circulation planning for backdated order items creates deliveries for separate
combinations in the period of the backdated order items.
1.4.11.3 IS-M-SD-PS-BL
Billing
1.4.11.3.1 Extraction of Tax-Relevant Data for GDPdU (Changed)

Use
settlements.
o
concept.
______________________________________________________________
SAP AG
95
SAP System
______________________________________________________________

system.
o
1.4.11.3.2 Transferring Billing Documents to Human Resources (New)

Use
As of SAP Media 4.72, you can transfer billing documents to Human Resources. You specify the transfer
destination in the Customizing settings for the sales document types. The following transfer destinations
are possible:
o
Financial Accounting
Human Resources
If you do not specify Human Resources as the transfer destination when defining the sales document type
(order type), the billing documents are transferred to Financial Accounting as before. When an order is
created, the system determines the transfer destination from the order type. If you specify in Customizing
that the data is to be transferred to Human Resources, the system automatically determines the new
transfer type 'H' (transfer to Human Resources).
Notes on data transfer to Human Resources:
o
The payment method in the order is not relevant
Revenue accrual does not take place for billing document transfer
______________________________________________________________
SAP AG
96
SAP System
______________________________________________________________
Billing document transfer to Human Resources is performed by the report RJFTRANSFERHR. Create
variants for the background jobs.
Before you can use the function for transferring billing documents to Human Resources, you must make
the following settings in Customizing:
o
Specify transfer destination Human Resources in sales document type definition
Check condition types for pricing in order/billing, if applicable
Define wage types in Human Resources
Assign wage types to condition types
1.4.11.3.3 Update of Intermediate Payment Dataset for Collective Transfer

(Changed)
Use
As of SAP Media 4.72, you can specify in a user exit that the system is only to create one REGUP record
per billing document in collective transfer, instead of creating a REGUP record per billing document
item. The user exit allows you to specify this for specific billing documents where only one REGUP
record is required.
Activate the user exit EXIT_SAPLJF24_006 from the SAP enhancement JF230002.
1.4.11.3.4 Document Number Selection for the Check List for Revenue Accrual
(Changed)
Use
As of SAP Media 4.72, you can restrict selection of the check list 'Transfer Revenue Accrual' (report
RJFTRANSFERREVACC) to the accounting or contract accounting document number.
If you want to use this change to the function, please adjust the variants for your background jobs
accordingly.
Changes to the interface
You can restrict selection according to the following selection parameters in the execution mode 'Check
List'.
o
Document number (FI-CA)
Document number (FI-AR)
______________________________________________________________
SAP AG
97
SAP System
______________________________________________________________
Fiscal year (FI-AR)
1.4.11.3.5 Billing Creation in Parallel with Order Management (Changed)

Use
As of SAP Media 4.72, you can create collective billing runs (program RJF_FAKT) in parallel with order
management. An optional parameter has been added for this purpose to the selection screen for the
collective billing run.
If this parameter is selected, it is possible to make order changes that affect the billing indexes during
billing creation. These changes include complaints, terminations, and backdated changes to the billing
arrangements.
If you select this option for a collective run, the system does not import the billing indexes until billing is
due for the payer in question. Billing indexes can be changed by other processes during the collective run
until this point.
Since this function imports the billing indexes specifically for each payer, it can affect performance.
If you want to use this change to the function, please adjust the variants for your background jobs
accordingly.
Changes to the interface
The new optional parameter Parallel to Order Management is now available for the execution type
when creating a collective billing run (program RJF_FAKT).
1.4.11.4 IS-M-SD-PS-ST
Settlement
1.4.11.4.1 IS-M-SD-PS-ST-W
Home Delivery Settlement
1.4.11.4.1.1 Extraction of Tax-Relevant Data for GDPdU (Changed)

Use
settlements.
______________________________________________________________
SAP AG
98
SAP System
______________________________________________________________
concept.
system.
o
______________________________________________________________
SAP AG
99
SAP System
______________________________________________________________
1.4.11.4.2 IS-M-SD-PS-ST-C
Commission Settlement
1.4.11.4.2.1 Extraction of Tax-Relevant Data for GDPdU (Changed)

Use
settlements.
o
concept.
system.
o
______________________________________________________________
SAP AG
100
SAP System
______________________________________________________________
1.4.12 IS-M-SD-MS
Media Product Sales and Distribution
1.4.12.1 Direct Store Delivery in Single Copy Sales (New)

Use
As of SAP Media 4.72, you can use the visit planning functions in Direct Store Delivery (DSD) for single
copy sales of newspapers and magazines. You can use the visit planning functions to control
transportation planning.
The customers to be visited and the delivery drivers, and, if applicable, vehicles, are assigned to a visit
plan. A customer can be assigned to several visit plans.
Note: In these scenarios, master data maintenance for the SAP BP also takes place using the maintenance
functions for the Retailer in the SAP BP. If you want to use the functions for the driver and for vehicle
space optimization, you must enter the necessary data for the corresponding vendor. This data is not
integrated with the SAP BP.
In addition to specific business partner data, you must also maintain additional master data so that you
can use DSD. For further information, see the release notes listed below.
See also
For further information, see the following release notes:
Direct Store Delivery Backend Overview
Master Data for Direct Store Delivery Backend
Visit Control in Direct Store Delivery Backend (DSD Backend)
Direct Store Delivery Backend (DSD Backend) Transportation Planning
1.4.12.2 Purchasing Planning (New)

Use
As of SAP Media 4.72, purchasing planning is possible for wholesalers in Single Copy Sales (Media
Product Sales and Distribution).
______________________________________________________________
SAP AG
101
SAP System
______________________________________________________________
The following applications are available for executing purchasing planning:

o
Generate purchase order quantity records

for generating the initial purchase order quantity records
Purchase order quantity planning

for processing purchase order quantities
Purchase order generation

for creating purchase orders
1.4.12.3 Table for Fast Access to Address Data (New)

Use
As of SAP Media 4.72, the new BAdI ISM_ADDR_SYNC is available in SAP business partner
processing. You can use it to store addresses and address changes in a database table so that you have fast
access to the address data.
According to the default setting, the BAdI executes the following functions in the database table:
o
Create new addresses
Adjust changed addresses
1.4.12.4 Enhancements to Logs in Single Copy Sales (New)

Use
In SAP Media 4.72, the following enhancements have been made to log creation for functions in Single
Copy Sales:
o
User name
The name (and title(s)) of the user is displayed on the log. Previously, the SAP user name was
displayed. This change simplifies identification of the person who executed the program and, in so
doing, created the log. This enhancement only affects new logs.
Filter for message types

When logs are read from the database, you can now set a filter to suppress success, information, or
warning messages so that they are not displayed.
Error messages are not suppressed. You can also search for specific error messages by filtering out
other message types.
1.4.12.5 Marking Contracts as Media-Specific (New)

Use
As of SAP Media 4.72, all contracts used in Single Copy Sales (Media Product Sales) are marked as
______________________________________________________________
SAP AG
102
SAP System
______________________________________________________________
media-specific.
Caution:
If you used contracts from Media Product Sales in a previous release, you must mark all the Media
Product Sales contracts you have been using as media-specific in the maintenance view V_JTVAK01
after the release upgrade. Otherwise, certain functions will no longer be available for the contracts.
1.4.12.6 Changes to Variant Control (Changed)

Use
In SAP Media 4.72, the following enhancements have been made to the variant control (for managing
selection variants), which is used in a number of transactions in Single Copy Sales (Media Product
Sales):
o
Sort criteria allowing structured sorting of variants and simpler identification of variants have been
added to the variant control. You can assign variants to a sort criterion by means of drag and drop.
The variants are sorted alphabetically within a sort criterion. You can change the text description of
a sort criterion by accessing it through the context menu.
All users can display variants once they have been released. Each user can make their own
assignments of released variants to sort criteria. New variants are displayed for other users under the
sort criterion under which they are created.
The authorization object J_VARIANT controls whether or not a user is allowed to delete and
rename other users' variants once they have been released.
1.4.12.7 IS-M-SD-MS-SL
Sales
1.4.12.7.1 Improved Ergonomics in Central Access to Single Copy Sales (New)

Use
In release 4.72, improvements have been made to the interface in central access to the solution for single
copy sales of newspapers and magazines.
The selection criteria and the results list are displayed on separate tab pages to improve accessibility.
1.4.12.7.2 Copy Number in Central Access to Single Copy Sales (New)

Use
As of SAP Media 4.72, a new entry option for use in newspaper retail has been added to central access to
single copy sales (Media Product Sales and Distribution):
You can now also specify a media issue as a combination of a copy number and a media product.
______________________________________________________________
SAP AG
103
SAP System
______________________________________________________________
1.4.12.7.3 Shipping Planning (New)

Use
As of SAP Media 4.72, you can carry out shipping planning for series sales. In shipping planning, you
define the operative data for order generation and subsequent delivery (for example, billing date, delivery
date).
Shipping planning data for media products with a type 02 shipping characteristic (issue is determined
from the issue sequence) is created automatically when an issue is added to the issue sequence. In this
case, you can change the shipping planning data that is created automatically.
You can create shipping planning records for media products with shipping characteristic type 01 (issue
must be specified in shipping planning) and 03 (issue cannot be specified).
Meaning of Status
Shipping planning records are assigned a status. The statuses have the following meanings:
o
Status 00 (Planned)
Not included in order generation
Status 01 (Create orders)

Orders are created for shipping planning records once the starting date and time for order creation
are reached
Status 03 (Order creation completed)

This status is set by report RJKSESETSTATEFINISHED for all media issues that are not to be
delivered subsequently and that have a delivery date that is in the past.
You can set status 03 manually in shipping planning for issues that are to be delivered subsequently.
Status 04 (Delete orders)

You can delete generated orders using report rjkseordercancel. After deletion, you can create the
orders again using the order generation function.
1.4.12.7.4 IS-M-SD-MS-SL-C
Contract
1.4.12.7.4.1 Index Table for Selecting Contracts in the Quantity Plan (New)
Use
As of SAP Media 4.72, the index table VAPMA is read to select contracts in quantity planning for each
contract (transaction JKSD03) in order to improve performance. The index table must be supplied with
data for contract creation.
Important: set up the system in such a way that the index table VAPMA is created. You can define the
structure of the index table using table TVIND.
______________________________________________________________
SAP AG
104
SAP System
______________________________________________________________
1.4.12.7.4.2 Subscriptions for Series Sales (New)

Use
As of SAP Media 4.72, subscriptions for series sales are mapped using quantity contracts.
Suspensions
You can suspend a contract item by specifying a suspension period on the Media tab in the item data on
the contract. You can then specify whether the issues in the suspension period are to be delivered on a
subsequent delivery date.
Suspensions are not taken into account in billing plans.
History of Issues Delivered
You can list the orders already generated for the contract item on the Media tab in the contract item data.
Planned Deliveries
Planned issues of media products with shipping characteristic type 02 are listed together with the
corresponding shipping dates. You can change the delivery quantity and date for specific issues. You can
also set a delivery block on the level of the planned deliveries. The block is then copied to the order
during order generation.
1.4.12.7.5 IS-M-SD-MS-SL-Q
Purchase Quantity Planning
1.4.12.7.5.1 Copying Function for Groups of Media Products (New)

Use
As of release 4.72, you can copy planned delivery quantities for a selection of contracts (media products)
using a new copying function (transaction JKSD17, report RJKSDDEMANDCOPY2).
See also the documentation on report RJKSDDEMANDCOPY2.
1.4.12.7.5.2 Selection in the Quantity Plan for Each Contract (New)

Use
In release 4.72, the following enhancements have been made to the quantity planning functions for each
contract item (transaction JKSD03):
o
You can create sort criteria for grouping selection variants and assign them to selection variants
using a drag and drop function.
You can use the BAdI ISM_CONTRACT_NAVI to define the structure of the selection variants
according to company-specific criteria.
You can access the Customizing settings for specifying a default date interval from the menu on the
______________________________________________________________
SAP AG
105
SAP System
______________________________________________________________
processing screen. To do this, choose the menu path Goto -> Settings -> Set Date Interval.
You can specify a number of days before and after the current date to calculate the date interval.
1.4.12.7.5.3 Quantity Forecasts According to Reference Issues (New)

Use
As of SAP Media 4.72, you can create forecast quantities for quantity planning in Single Copy Sales and
copy these quantities into the quantity plans. The forecast quantity for a media issue is calculated
according to past delivery quantities of reference media issues in the same contract.
You can use the following functions for quantity planning with quantity forecasts:
o
Calculate the forecast quantity for a media issue

You can use this transaction (jksdforecast02) to assign reference issues to the media issues and
weight the sales figures for the reference issues.
Calculate forecast quantities and copy them to quantity plan

The report RJKSDDEMANDFORECASTPLAN calculates the forecast quantity for a media issue
from the weighted sales figures and copies it as a planned delivery quantity to the corresponding
quantity plan for the contract.
Create a log
The function for creating and copying the forecast quantities creates a log, which you can display
using the transaction JKSDFORECASTPROTOCOL.
1.4.12.7.5.4 Business Partner Role in Quantity Plan (New)

Use
As of SAP Media 4.72, you can use the BAdI ISM_DEMAND_SET_ROLE in quantity planning
(transaction JKSD03) to specify the business partner role for which quantity plan records are to be
displayed.
The default setting is the role Ship-To Party.
Define Role for Display in Transaction JKSD03
1.4.12.7.5.5 Business Partner Role in Quantity Planning (New)

Use
As of SAP Media 4.72, you can specify a default role in which a business partner is to be displayed in
quantity planning (per contract) in Single Copy Sales.
The default values is assigned using the customer determination procedure. You can use the BAdI
______________________________________________________________
SAP AG
106
SAP System
______________________________________________________________
ISM_DEMAND_SET_ROLE to assign a default business partner role.

If you want to use this function, you must make the following Customizing settings:
o
Maintain Business Partner Role for Display

In this step, you define the role in which the business partner is displayed.
Implementation of BAdI ISM_DEMAND_SET_ROLE
1.4.12.7.5.6 Enhancements to the Contract Navigator (New/Enhanced)

Use
In SAP Media 4.72, the following enhancements have been made to the Contract Navigator:
o
The enhanced variant control function is now used
You can use the method CUSTOMER_SELECTION to make further customer-specific selections to
determine the hit list of contracts in the Contract Navigator. You can use the parameter
CONTRACT_TAB to influence (increase or reduce) the number of contracts displayed. Please note
that customer-specific selection parameters must begin with Z.
You can change the way the data is displayed in the Contract Navigator using the method
SHOW_SELECTION_ON_SCREEN. For example, you can add fields to the Contract Navigator,
change the sort sequence, or add a further level to the structure. To do this, you will need to write
your own display methods. The display method used is specified in the parameter METHOD. Please
note that customer-specific display methods must begin with Z.
1.4.12.7.5.7 Copying Delivery Quantities for Different Media Products (New)

Use
As of SAP Media 4.72, you can copy the delivery quantities from one media product to another. This
function is available in report RJKSDDEMANDCOPY2. For further information, please see the
documentation on report RJKSDDEMANDCOPY2.
1.4.12.7.5.8 Event Management in Quantity Planning (New)

Use
As of SAP Media 4.72, you can manage events and take them into account in quantity planning.
This function allows you to perform event-controlled quantity planning. Sales figures of a media product
can be influenced by various events. You can use this dependency to plan sales quantities with greater
precision in Media Product Sales.
______________________________________________________________
SAP AG
107
SAP System
______________________________________________________________
You can use the transaction JKSDQEVENT - Events for Quantity Planning to create these events and
link them with certain contracts (media products). For example, you can use this transaction to adjust
(increase/reduce) the sales figures and to update existing quantity planning records that were maintained
using transactions JKSD03 and JKSD07.
You can assign an event attributes and characteristics to classify and describe its properties.
For a detailed description of this function, see the documentation on report RJKSDQEVENTMNG.
Activities
Before you can assign attributes and characteristics to an event, you must maintain them in Customizing:
o
Maintain Attributes
Maintain Attribute Characteristics
1.4.12.7.6 IS-M-SD-MS-SL-O
Order Creation
1.4.12.7.6.1 Rounding the Order Quantity to Full Bundles (New)

Use
As of SAP Media 4.72, you can specify whether or not the system is to perform rounding to full bundles
during order generation for each contract item in a contract.
You can make this setting using the field VABAP-ISMROUNDALLOWED, which has been added to the
transactions VA41, VA42, and VA43.
If rounding to full bundles is activated for a contract item, the order quantity is rounded to the defined full
bundle quantity in accordance with the packaging rule. The minimum bundle quantity is taken into
account.
You can program settings to influence rounding to full bundles. You can do this using the BAdI
ISM_ORDER with the following methods:
o
ROUND_FULL_BUNDLE_CREATE_ORDER
This method is accessed during order generation.
ROUND_FULL_BUNDLE_CHANGE_ORDER
This method is accessed by program RJKSDORDERCHANGE when an order is being changed.
1.4.12.7.6.2 Order Generation for Series Sales (New)

Use
As of SAP Media 4.72, the order generation program RJKSEORDERGEN is available for processing
sales of series.
The program creates orders in R/3 based on shipping planning and on contracts from series sales.
Subsequent delivery or initial shipping orders are created depending on the status of a media issue in
______________________________________________________________
SAP AG
108
SAP System
______________________________________________________________
shipping planning.
The function for determining the issue(s) for which orders are to be created in order generation can be
modified according to your specific requirements using an open interface. SAP provides a framework in
which the order generation function can access customer coding at specific points.
The framework comprises the following basic parts:
1.
Search strategy for determining the next issue for delivery
2.
Search strategy for determining additional issues (for example, a club journal)
3.
Strategy for executing processes of your choice in the system (for example, create a follow-up offer
for a new series once the last issue in a series is reached)
Definition of Determination Module

A determination module is a function module that has an interface defined by SAP and that is used to
determine the issue the customer is to receive.
Definition of Check Module
A check module is a function module with an interface defined by SAP that can be used to check whether
or not a customer is allowed to receive the corresponding issue. For example, a customer is not to receive
the standard issue if they purchased it from a retailer during the past 12 months. Check modules are
optional.
Definition of Number Module
A number module is a function module with an interface defined by SAP that is used to determine the
maximum number of additional issues allowed for a customer.
Structure of a Search Strategy
Each search strategy comprises a maximum of five determination modules and five check modules. The
search strategy for determining the additional issues also contains a number module. All the check
modules specified in a search strategy are always processed for each determination module.
Once a determination routine has found an issue, the system runs the check modules specified in the
search strategy in order to check whether the issue found meets the requirements.
You specify the determination modules, check modules, number modules, and strategies in Customizing.
SAP provides sample function modules for the determination and check modules. The standard SAP
modules for determining the next issue are in the function group JKSEORDER10. Determination
modules for the additional issue can be found in function group JKSEORDER13. The check modules are
in the function group JKSEORDER12.
Deleting Generated Orders
You can use program RJKSEORDERCANCEL to delete the orders generated. To do this, you must set
the status of the media issue for which you want to delete orders to 04 (delete orders) in shipping
planning.
______________________________________________________________
SAP AG
109
SAP System
______________________________________________________________
1.4.12.7.7 IS-M-SD-MS-SL-R
Returns
1.4.12.7.7.1 Determining Media Issues for Collection (New)

Use
As of SAP Media 4.72, you can determine the media issues for collection in Single Copy Sales according
to return notifications.
The media issues to be collected are determined according to the follow following data:
o
Sales area
Collection date
Retailer
1.4.12.7.7.2 Creating New Returns (New)

Use
As of SAP Media 4.72, you can create returns for media issues using a Web browser.
You can select the media issues for which you want to create the returns by entering the following data:
o
Customer number
Date interval that covers the collection date for the media issue(s)
The system displays all the media issues in the selection period that were delivered to the customer
number. The delivery quantity and the return quantity already entered are displayed for each media issue.
You can increase or reduce the return quantity by entering a new return (to reduce it, enter the return with
a minus sign). When you save, the system checks the entire return quantity for the media issue against the
delivery quantity. You can also execute a check on your entries before saving. If the return quantity is too
high, you can still save the return in the system.
1.4.12.7.7.3 Parallel Return Release (New)

Use
As of SAP Media 4.72, you can release several returns in parallel.
Parallel processing has been implemented internally and cannot be influenced by the user.
The change has resulted in a major improvement in performance during return release.
______________________________________________________________
SAP AG
110
SAP System
______________________________________________________________
1.4.12.7.7.4 BAPI for Changing Returns (New)

Use
As of SAP Media 4.72, you can use BAPI BAPI_ISMRETURNREQUEST_CHANGE to make the
following changes to returns:
o
Change return attributes (until they are released to SD)
Add items to a return
Delete items from a return
Delete returns
1.4.12.7.7.5 Restricting Return Release (New/Enhanced)

Use
In SAP Media 4.72, the selection parameter "To Notification Date" has been converted to a selection
option parameter "Notification Date". This allows you to specify more precise selection criteria for
returns that are to be released (report RJKSDCREDIT).
1.5 IS-M-AM
Advertising Management
1.5.1 CIC - Contracts in the Data Environment (Enhanced)

Use
As of SAP Media 4.72, you can display contracts for a business partner as follows in the Data
Environment in the Customer Interaction Center (CIC):
o
Contracts that have been assigned the business partner as a result of a role other than that of the
Contract Holder are displayed in an additional node. Example: Business partner is a contract
beneficiary.
Contracts, which have been assigned the business partner as a result of the contract hierarchy, are
also displayed in an additional node.
All contract nodes for a business partner are combined in an additional node.
Settings for the Data Environment are made in Customizing as follows: SAP Media -> Customer
Interaction Center -> Define Data Environments for the Navigation Area
______________________________________________________________
SAP AG
111
SAP System
______________________________________________________________
1.5.2 CIC - Entry of Ad Items (Enhanced)

Use
The component for entering ad items (classified order entry) has been enhanced as follows in the
Customer Interaction Center (CIC) as of SAP Media 4.72:
o
Edit ad item
You can now display and edit ad items in addition to creating ad items in Classified Order Entry.
Display and editing takes place on the screen that was previously only used to enter ad items. The
following options are available for accessing ad items in Classified Order Entry:
-
Access the order by entering the order number in Classified Order Entry
Access the order from the Data Environment using the context menu (right mouse click) or by
double clicking. The EditMAMOrder or DisplayMAMOrder BOR methods for the
BUSISMCIC (CIC Support Object) business object are available here. These methods can be
used to access the order in the display or editing mode.
Access the order from the Order Overview by selecting the corresponding menu functions
You can toggle between the display and editing mode in Classified Order Entry using a button.
o
Working with a dummy business partner

You can enter a classified ad order without business partner master data for the customer in the first
instance. Since the sold-to party in classified order entry can be defined as a default using a dummy
business partner, you can enter the order data without having to first search for, identify and even
create a business partner. However, the order cannot be updated until you have exchanged the
dummy business partner for an actual business partner. You cannot perform an update using a
dummy business partner.
You can specify the number of the dummy business partner to be entered as a default in
Customizing under Make Settings for the Ad Item Entry Component. The dummy business partner
must be created in the Media Customer role.
Enter payment cards and bank data

Two buttons for creating and changing payment cards and bank details are now available to you in
Classified Order Entry.
Refresh pricing
A button for refreshing pricing is now available to you in Classified Order Entry. If you have
integrated an editor for ad design in the CIC framework, you can use this button to perform pricing
using the modified ad spec data during ad content design without leaving the editor. If you have not
integrated an editor in the CIC framework or are not using this editor, pricing is first performed
when the ad order is saved if pricing data has been modified.
Access document management

A button for accessing document management is now available to you in Classified Order Entry.
Documents are displayed for the current order item here.
______________________________________________________________
SAP AG
112
SAP System
______________________________________________________________

Settings for classified order entry are made in Customizing as follows: SAP Media -> Customer
Interaction Center -> Make Settings for the Ad Item Entry Component.
1.5.3 Sale of Display Classified Ads (New)

Use
SAP Media provides you with a comprehensive solution for sales of display classified ads, which enables
your call center employees (agents) and your customers to enter commercial data on an ad order in the
Customer Interaction Center (CIC) or in the Internet, and to design the ad content in an integrated editor.
Agents and customers have the following two options for designing ad content:
o
Design using a WYSIWYG editor
Template-supported design using ad content attributes

The system displays a range of ad content attributes (for example, brand, model, engine size, and
number of doors) depending on the booking unit and content component the agent selects (in this
case, Auto Mart). They can then enter values for these attributes. The values entered are transferred
to a template, which the system then uses to create the ad content.
This scenario has been implemented in Advertising Management in SAP Media 4.72 with functions for
process-oriented entry of commercial order data in the Customer Interaction Center (CIC), integration of
an editor for designing ad content, and storage, administration and reuse of the graphics relevant for the
ad content.
SAP Media contains an editor for use in designing ad content, which is delivered with the component
Advertising Management for Classified Ad Design (IS-M/AMC).
Features
In classified ad sales, graphics files are often used to design the ad content. These files might include a
photo of a house for sale, a realtor's logo, or an icon for a cross in an obituary.
You can now store these graphics files in Document Management and assign them to the relevant
business objects, for example, business partners, content components, or orders. For further information,
see the release note Document Management for SAP Media Business Objects.
When designing ad content, the technical system can use an RFC interface to access the graphics for the
business objects involved in the order to include them in the ad content. The technical interface IS-M/ITA
and the artwork assignment have been enhanced so that the technical system is able to return pricing
information to Advertising Management about the graphics used in the ad. For further information, see
the release notes Artwork Assignment and Technical Interface.
BAPIs have been created or enhanced so that production-relevant data in Advertising Management can be
passed on to the editor. See the release notes BAPIs for the Sales Document, BAPIs for the Booking Unit,
BAPIs for the Content Component, and BAPIs for the Ad Spec.
The CIC framework has been enhanced so that the SAP editor or an editor from a non-SAP system can be
______________________________________________________________
SAP AG
113
SAP System
______________________________________________________________
integrated on the right hand side of the screen. Until now, you could only display the editor in a separate
dialog box or on a tab page in the navigation area. It is also now possible to switch the navigation and
application areas to fullscreen mode using a pushbutton. Please see the release note Component Layout.
In addition to creating ad items, agents can now also display and edit them in Ad Item Entry. Since the
sold-to party in Ad Item Entry can be defined as a default using a dummy business partner, agents can
enter the order data without having to first search for, identify, and even, in some cases, create a business
partner. See the release note Entry of Ad Items.
1.5.4 CIC - New Functions for Creating Business Partners (Enhanced/Modified)

Use
As of SAP Media 4.72, the functions for creating business partners have been revised as follows in the
o
The same address fields as those available during creation or modification of an SAP Business
Partner are now available to you when you enter or create address data.
During creation of a business partner in dialog processing, the master data for the SAP Business
Partner (full screen transaction) is accessed from the Business Partner Search and Processing (short
dialog) dialog box. The system does not copy all data that was entered on the dialog box into the full
screen transaction. Data that is not transferred includes additional street information or bank data.
During creation of a business partner in the background, all data is copied into the full screen
transaction and made available here.
Both functions are available to you in a new dialog box. You can use the new classified order entry
indicator to define whether you want to use the new or existing dialog box to enter the business
partner master data.
The ISM_BP_CREATE Business Add-In can be used to modify the layout and fields on the new
dialog box. You can use the BAdI to modify the title and border text on the dialog box. You can also
define which fields are displayed and which fields shown are mandatory.
Simplified creation of a sales or media customer in an additional sales area using the context menu
in the Data Environment.
Simplified creation of an existing business partner in an additional role using the context menu in
the Data Environment.
During creation of a business partner, you can now define a default sales area according to the
business partner role to be created. If you create a media customer, you can define a default
Advertising Management sales area. If you then create a sales customer, you can define a default
sales area for Media Sales and Distribution.
During creation of the business partner, the CIC memory, which always contains the last sales area
used for the corresponding SAP Media component, is read first. If no sales area can be determined
from the memory, the system determines this from the Customizing settings. The memory does not
usually contain a sales area during business partner creation, since the memory is deleted after every
contact is terminated.
Default sales areas are recorded for each SAP Media component in Customizing. This setting is
recommended for agents who work with both SAP Media components.
______________________________________________________________
SAP AG
114
SAP System
______________________________________________________________
The CreateFast BOR method for the BUSISM007 (ISMBusinessPartner) usiness object still provides
functions for shortened business partner entry.
Settings for the Business Partner Search/Processing component are made as follows in Customizing:
SAP Media -> Customer Interaction Center (CIC) -> Make Settings for the Business Partner
Search/Processing Component
Observe the following possible settings here:
o
Search areas and option of switching the search area
Country as a default setting
Number of items
Sales organization, distribution channel and division for each component as a default setting.
New Classified Order Entry
1.5.5 CIC - New Functions in the Business Partner Search (Enhanced)

Use
In SAP Media 4.72, the following enhancements have been made to the business partner search in the
o
You can specify whether or not it is possible to search by household or business partner and
whether or not it is possible to switch between these two search areas. The system displays search
fields for the search area selected or specified as default.
A Next Contact pushbutton has been added to the other pushbuttons Clear All Fields and End
Contact. The buttons serve the following purpose:
Next Contact: The contact is completed. The search fields are reset to the last values entered. If
you press the pushbutton again, the system initializes all the fields. The call is not ended.
For example, the caller wants to make changes for two business partners with the same address
one after the other. The 'Next Contact' function completes the process for the first business
partner (and creates a contact document) and enters the data entered last in the search fields so
that a new search can be executed.
Clear All Fields: The search fields are reset to the values entered last. If you press the
pushbutton again, the system initializes all the fields. This allows you to perform a second
search if the wrong business partner was identified without having to enter all the search data
again. (The pushbutton does not affect the contact or the call or the data displayed in the
components of the navigation and application area.)
For example, this function can be used to cancel an identification that was made by mistake.
The user can start a new search immediately using the search data entered last.
End Contact: The contact is completed. The search fields and all the components of the
navigation and application area are initialized. The call is ended.
To avoid long runtimes when reading and displaying data on a business partner wrongly identified
______________________________________________________________
SAP AG
115
SAP System
______________________________________________________________
in the CIC - for example, when processing a major customer with a large dataset - you can specify
that the system is to notify you if the dataset exceeds a certain volume so that you have an
opportunity to correct any errors beforehand.
o
To prevent the system from displaying a business partner's old addresses, you can specify a time
restriction for displaying the business partner's addresses. You can define the period for address
selection using the user parameters ISM_CIC_BP_FROM and ISM_CIC_BP_TO. You can enter a
number of days for the parameter ISM_CIC_B_FROM to specify a period in the past starting from
the current date. For example, current date 365 = 1 year ago. Similarly, by entering a number of
days for the parameter ISM_CIC_BP_TO, you can specify a period in the future starting with the
current date.
As an alternative to displaying the business partner hit list in a dialog box, as was the case in
previous releases, you can now integrate a new hit list in the navigation or application area. If you
want to use the new hit list, assign the component ISM_HITLIST to the navigation or application
area in Customizing. The advantage of the new hit list is that the search result is displayed until the
contact is ended, so that you can proceed to a different business partner in the list without having to
perform a new search.
You can use the Business Add-In ISM_BP_SEARCH to add customer-specific functions to the hit
list in the business partner search. For example, you could add a function for retrieving details on a
business partner in the hit list, or for identifying duplicates.
The following methods have been added to the Business Add-In ISM_CIC_BP_SEARCH:
-
BP_SEARCH_WITH_DOCNR: Search for business partners if you use your own document
classes
PRELIMINARY_BUSINESS_PRTN_SRCH: Preliminary business partner search (upstream

from the standard search)
HITLIST_PREPARE_FOR_WORKSPACE: Enrich and format hit list (workspace)
You can make the settings for the component Business Partner Search/Processing in Customizing under
SAP Media -> Customer Interaction Center (CIC) -> Make Settings for Business Partner
Search/Processing Component.
Please note the following possible settings:
o
Search areas and the option of changing the search area
Specifying a default country
Number of items
Specify a default sales organization, distribution channel, and division for each component.
New fast data entry
1.5.6 CIC - Reset to Default Workspace When Contact Ends (Enhanced)

Use
______________________________________________________________
SAP AG
116
SAP System
______________________________________________________________
As of SAP Media 4.72, you can specify in the configuration profile of the application and navigation
area that the default workspace is to be displayed automatically after a contact is ended.
Restrictions:
o
If the default workspace was deleted in the meantime, it is not created again automatically.
Workspaces created dynamically during a contact are not deleted. You can make this setting by
selecting the Workspace Lifetime indicator for the action box call.
1.5.7 CIC - Component Layout (Enhanced)

Use
As of SAP Media 4.72, the display options in the Customer Interaction Center (CIC) have been enhanced
as follows:
o
Full screen mode for the navigation and application area

You can change the size of the navigation or application area using a pushbutton.
A button is available for activating or hiding the full screen display of the navigation or application
area if you want to incorporate the invisible component LAYOUTSWITCH in the framework and
include the FRW_LAYOUT_BIG_NAV and FRW_LAYOUT_BIG_APPL function codes in the GUI
status.
Docking control for incorporating an ad editor

Two frameworks, to which the invisible component ISMAM_EDITOR has been assigned, are
supplied. These frameworks are incorporated in the CIC profiles C_STD_C (17 inch screen
resolution) and C_STD_C2 (21 inch screen resolution) supplied. The ISMAM_EDITOR
component provides you with an HTML docking control in which an ad design editor can be
incorporated in the right hand section of the framework. You could only previously display the
editor in a separate dialog box or on a tab page in the navigation area.
The HTML docking control occupies a third of the right hand section of the screen in its default
display format. You can increase or decrease its size using the corresponding button. Docking
control can also be activated in the full screen mode so that you can use the entire screen area to
design the ad. The new framework does not contain a navigation area. The application area has
been increased so it now occupies the entire screen width and therefore provides a user-friendly
environment for editing ad orders in conjunction with docking control.
You can also use a button to switch the application area to full screen display in this framework.
Docking control is minimized dynamically here.

The settings for the new framework are made in Customizing. Pay particular attention to the following
settings here:
o
Assign Invisible Components to Framework IDs
Make Settings for the Ad Spec Editor Component
Define Toolbars and User-Defined GUI Status
______________________________________________________________
SAP AG
117
SAP System
______________________________________________________________
1.5.8 CIC - Display Variants in the Data Environment (Enhanced)

Use
When the system sets up the data environment in the Customer Interaction Center (CIC), it reads a large
number of objects and dependent data that are not required for simple business transactions but that still
have a serious effect on performance. As of SAP Media 4.72, you can use the Business Add-In
ISM_CIC_NAVVIEW to define display variants that override the Customizing settings for the data
environment.
Example 1:
You define a profile for the data environment that contains the format for all relevant objects and specify
whether or not these objects are to be displayed in the data environment and if so, how. You can set up
the BAdI methods in such a way that the user is only presented with a limited selection of objects once
the business partner has been identified. If the user discovers in the course of the contact that they need a
wider overview of the customer's data, they can choose a variant defined using the BAdI to display
additional objects.
Example 2:
You use the BAdI to change the time horizon for selecting relevant objects.
1.5.9 CIC - Accessing and Executing Workspaces Dynamically (New)

Use
As of SAP Media 4.72, you can use the business object BUSISMCIC (CIC support object) in the
Customer Interaction Center (CIC). The business object provides methods, which you can use to do the
following:
o
Access an existing workspace from the context menu in the data environment and bring it to the
foreground:
-
EditMAMOrder: Brings M/AM order entry to the foreground
DisplayMAMOrder: Brings the M/AM order list to the foreground
DisplayMSDOrderList: Brings the M/SD order list to the foreground
EventRaise: Can be used to bring customer-specific workplaces to the foreground.
Create a workspace dynamically from the action box or the context menu in the data environment:
-
StartBSPWorkspace: Starts a workspace to access BSP applications
StartWorkspace: Starts a workspace of your choice
1.5.10 CIC - Texts for Business Partner (Enhanced)

Use
______________________________________________________________
SAP AG
118
SAP System
______________________________________________________________
As of SAP Media 4.72, you can determine which texts are displayed in the application area of the
Customer Interaction Center (CIC) for the business partner and in Media Sales and Distribution for the
objects order, order item, and complaint.
For example, you can specify in Customizing which types of texts (text objects, text IDs) are to be listed
in what order, whether or not notes from generic object services are to be taken into account, and whether
or not the existence of a text is to be indicated in the tab title.
The following texts are available:
o
Business partner
-
Business partner
Central customer texts
Customer texts for accounting
Customer texts for sales and distribution
Central vendor texts
Vendor texts for company code
Vendor texts for purchasing
M/SD order
-
M/SD order item

-
Order header text
Order item text
M/SD complaint
-
Customer complaint
Subsequent delivery information
Carrier information
Carrier's statement
1.5.11 Campaign Master Data in the Marketing Planner (Changed)

Use
Campaigns in Campaign Management were previously planned in the Marketing Planner in SAP CRM,
then released and transferred to SAP Media. Media-specific attributes, such as validity period, usage, and
template documents, then had to be added in SAP Media for master data maintenance.
As of SAP CRM 4.0 SP 05, you can create, change, and display campaign master data for SAP Media in
the Marketing Planner in SAP CRM. It is no longer necessary to postedit the campaign master data in
SAP Media and switch between the two application components.
You must define your own set type so that a tab for entering the media-specific attributes is displayed in
the Marketing Planner in SAP CRM. On the tab page, you can implement a BSP application that provides
______________________________________________________________
SAP AG
119
SAP System
______________________________________________________________
the functions for editing the media-specific attributes on further tab pages:
o
Campaign tab: The tab page is subdivided into the areas Campaign, Assignment, and Sorting. Each
of these subareas is also displayed as a tab page.
-
Campaign tab: Displays campaign data, such as Description, Validity period, Use.
Assignment tab: Displays template documents assigned to the campaign document and those
that can be assigned to the campaign in a hierarchy tree, split according to Media Sales and
Sorting tab: Display sequence of template documents, split according to Media Sales and
Template tab: Displays the existing template documents, split according to Media Sales and
Distribution and Advertising Management. You can also create and search for template documents.
M/SD Promotional Data: Displays promotional data, from which you can access the corresponding
processing functions in Media Sales and Distribution.
See also
For further technical data, see note 627927.
1.5.12 IS-M-AM-SL
1.5.12.1 IS-M-AM-SL-O
Sales
Order
1.5.12.1.1 Filter Objects for Orders in External Systems (Enhanced)

Use
As of SAP Media 4.72, it is possible to use the front-end ID of a computer as a filter object when
creating, changing and displaying orders in an external system using the CreateExternal, EditExternal
and DisplayExternal BOR methods for the BUSISM008P (Advertising Management External Sales
Document) business object.
If you want to use the front-end ID as a filter object, make the settings described in note 640023
(transaction SALE).
1.5.12.1.2 Artwork Assignment (Enhanced)

Use
As of SAP Media 4.72, the following fields have been included in the artwork assignment for the ad spec:
o
Type of artwork
Size
______________________________________________________________
SAP AG
120
SAP System
______________________________________________________________
Color scheme
Artwork incomplete indicator
Physical document from document management
These fields manage artwork information that is used to design the ad content with all price information
in the artwork assignment.
If you change the artwork assignment, the system generates the associated billing dataset again and
repeats pricing.
The artwork assignment has been included as an additional parameter in the EXIT_SAPLJHGA_001 user
exit for making entries in the pricing interface. The procedure for performing pricing in accordance with
customer fields is described in note 111887.
You define the artwork type as follows in Customizing: SAP Media -> Advertising Management -> Sales
-> Order -> Sales Documents -> Sales Document Item -> Ad Item Type -> Ad Spec/Technical Settings
-> Define Artwork Type.
See also
The fields described above have also been included in the BAPIs for the sales document and the interface
used to integrate technical systems (IS-M/ITA):
o
Release note BAPIs for the Sales Document in Advertising Management
Release note Technical Interface
1.5.12.1.3 BAPIs for the Sales Document (Enhanced)

Use
As of SAP Media 4.72, the BAPIs for the Advertising Management Sales Document (BUSISM008) have
been enhanced as follows:
o
Commercial item type:

The CreateFromData and Change BAPIs have been enhanced so that you can now create and
modify commercial items.
Internet publication of a print ad

The Booking unit for Internet publication indicator, Start and End date of the Internet publication
fields have been added to the ad schedule line in Release 4.72 (refer to the Internet Publication of a
Print Ad release note. These fields have been included in the BAPIBUSISM008_SL_AD_OUTBAPI
structure.
Artwork assignment:
Additional fields have been included in the artwork assignment to the ad spec in SAP Media 4.72
(refer to the following release note Artwork Assignment). These fields have been included in the
BAPIBUSISM008_ARTWORK_ASS and BAPIBUSISM008_ARTWORK_ASSX BAPI structures so
______________________________________________________________
SAP AG
121
SAP System
______________________________________________________________
that they can be read and modified using the BAPIs for the Advertising Management Sales
Document. The ARTWORK_ASS_TEXT parameter has also been included in the GetDetail BAPI, so
that short texts can be read for the artwork assignment.
o
Ad spec
The Style and Template fields have been added to the ad spec in SAP Media 4.72. These fields have
been included in the BAPIBUSISM008_AD_SPEC_AD and BAPIBUSISM008_AD_SPEC_AD_OUT
structures so that they can be read and modified using the BAPIs for the Advertising Management
Sales Document.
Advertiser assignment
Card verification fields have been included in the BAPIBUSISM008_ADVERTISER_ASS BAPI
structure in SAP Media 4.72 so that they can be read and changed using BAPIs for the Advertising
Management Sales Document.

See also
1.5.12.1.4 BAPIs for the Ad Spec (New)

Use
The Advertising Management Ad Spec (BUSISM028) BOR object has been created in SAP Media 4.72.
The following methods have been created for this BOR object:
o
GetDetail (Read Ad Spec)
ExistenceCheck (Check existance of ad spec)

See also
1.5.12.1.5 Assignment of Voucher Copy and Box Number Recipients (Modified)

Use
As of SAP Media 4.72, the Copy Selection function is available to you on the Select Box Number
Recipient and Select Voucher Copy Recipient dialog boxes that are displayed during order entry. This
simplifies assignment of the box number and voucher copy recipient to an order item.
To make a selection on one of these dialog boxes, it was previously necessary to proceed as follows:
o
Select business partners who were not required (individually)
______________________________________________________________
SAP AG
122
SAP System
______________________________________________________________
Delete selected business partners
Transfer the remaining business partners
The number of dialog steps has been reduced in the new function:
o
Select business partners required.
Transfer selected business partners.
This simplifies the assignment of voucher copy and box number recipients, particularly in those cases
where several business partners are available for selection but only one can be transferred. This is for
instance the case for box number recipients with several alternative box number addresses.
1.5.12.1.6 Entry of Payment Cards (Changed)

Use
As of SAP Media 4.72, the Payment Card Category field is no longer a required field when entering
payment cards in the sales document. Instead, the system checks whether the payment card category you
enter matches the one determined in FI according to the rules you defined in Customizing. If this is not
the case, the system displays a warning message indicating that the categories do not match.
1.5.12.1.7 Customer Enhancements in the Order (New/Enhanced)

Use
As of SAP Media 4.72, the following customer enhancements are available in the order environment:
o
Business Add-In ISM_AM_JHA6_SELECT (new):

The ORDER_ITEM_SELECT BOR method was created. This BOR method can be used for
customer-specific selection of order items in Central Access.
Business Add-In ISM_AM_ITA (new):

The AFTER_AD_DESIGN BOR method was created. Once you have accessed the Text Entry/Ad
Design (ISP_AD_DESIGN) function from the IS-M/ITA technical interface, you can use this BOR
method to make changes to the Advertising Management sales document.
Enhancement JHGA0001 (enhanced):

The Artwork Assignment parameter (RJHABILOZ_ITAB) has been included in the Modify Interface
(EXIT_SAPLJHGA_001) customer exit.
Business Add-In ISM_AM_ORDER_BAPI:

The BOR method BAPI_MAP2I_ALL has been created. This means it is possible to map
customer-specific contents from BAPI structures to internal structures.
______________________________________________________________
SAP AG
123
SAP System
______________________________________________________________
1.5.12.1.8 Old User Interface Is No Longer Supported (Modified)

Use
A new user interface that is based on tab pages has been available to you for sales document entry since
SAP Media 4.62 (transactions JHA1N, JHA2N, JHA3N). This interface offers you the following benefits:
o
More straightforward handling as a result of navigation between the various processing screens.
Reduction of the number of screen changes required during processing.
Transparent data display
As of SAP Media 4.72, the existing user interface (transactions JHA1, JHA2, JHA3) is no longer
supported during dialog processing. This does not affect orders that are imported using batch input
(programs RJHADU01 and RJHADU04), which has been implemented using the existing interface. This
function has been retained in its existing format.
If all users at your company are already using the new interface, this only affects you during order entry
using classified order entry. Accesses using menu functions and buttons from classified order entry
always used the existing interface in the past. As of SAP Media 4.72, these accesses use the new
interface. This provides you with the benefits of the new interface and navigation has been standardized,
regardless of whether you are starting order processing from Classified Order Entry, Standard Access,
Central Access or the Customer Interaction Center. The menu in Classified Order Entry has been
replaced by the Standard Access menu at item level.
The JHA1, JHA2, HA3 transactions have not been deleted and are still available. If you access these
transactions directly, you are informed that you should use the JHA1N, JHA2N, JHA3N transactions
instead. Note that the existing transactions are no longer maintained. The only exception here is
maintenance, which affects importing orders using the RJHADU01 and RJHADU04 programs.
You were previously able to define whether the new interface or the existing interface was to be used for
sales document processing for each user group in Customizing. You could also override this setting using
the JHN user parameter. As of SAP Media 4.72, these Customizing settings and the user parameter will
no longer be interpreted. The Customizing indicator can no longer be selected.
See also
Release note New User Interface for Sales Documents in SAP Media 4.61.

Use
______________________________________________________________
SAP AG
124
SAP System
______________________________________________________________
business partner.
o
Create folder
Create document
Create URL

Display document

corresponding data.

Delete original
Export
______________________________________________________________
SAP AG
125
SAP System
______________________________________________________________
in the Explorer.
o
Export with block

place.
Import new version

Versions.
Cut, copy and paste

Search
Where-used list
evaluated here
Send
more recipients.

o
Document preview
Copying Orders
______________________________________________________________
SAP AG
126
SAP System
______________________________________________________________

o

system


o
HTTP Content Server

R/3 database
______________________________________________________________
SAP AG
127
SAP System
______________________________________________________________

OACT.
1.5.12.2 IS-M-AM-SL-C
Contract

Use
______________________________________________________________
SAP AG
128
SAP System
______________________________________________________________
business partner.
o
Create folder
Create document
Create URL

Display document

corresponding data.

Delete original
Export
in the Explorer.
______________________________________________________________
SAP AG
129
SAP System
______________________________________________________________
Export with block

place.
Import new version

Versions.
Cut, copy and paste

Search
Where-used list
evaluated here
Send
more recipients.

o
Document preview
Copying Orders
______________________________________________________________
SAP AG
130
SAP System
______________________________________________________________
o

system


o
HTTP Content Server

R/3 database
______________________________________________________________
SAP AG
131
SAP System
______________________________________________________________
OACT.
1.5.12.2.2 Order Pricing with Scale Base Contract (Enhanced)

Use
As of SAP Media 4.72, the assignment of scale conditions in the order can be dependent on specific
attributes in the assigned scale base contract. To do so, the RJHKOMP5 structure must be enhanced using
a customer append. The contract data is used to make entries in the customer-specific fields in the
SCALE_BASE_COMM method in the ISM_AM_CONTRACT BAdI. These fields can be evaluated in
a pricing requirement. Replace requirement 515 that is used in the Customizing settings with an enhanced
requirement in the customer name space.
The COMPRESS_KOLNR method in the ISM_AM_CONTRACT BAdI can be used as of Release 4.72
to perform several accesses in an access sequence, which all use the scale base for the same scale base
contract.
The condition screen in the maintenance dialog for scale base contracts has also been enhanced so that
condition types, which are linked with requirement 515 in the pricing procedure used, can now also be
displayed.
______________________________________________________________
SAP AG
132
SAP System
______________________________________________________________
Implement the ISM_AM_CONTRACT BAdI if necessary.
1.5.12.2.3 Discount/Price Adjustment for Scale Base Contracts (Enhanced)

Use
As of SAP Media 4.72, the system also evaluates information on discount/price adjustments for scale
base contracts. The following options are available here:
o
Adjustment in the order was previously already available and means that the higher value is used as
the scale base for every order for which the target agreement of the scale base contract has already
been exceeded.
Adjustment for interim settlement means that the target agreement for the scale base contract is
increased to the values obtained during interim settlement after each interim settlement.
Prohibit over-fulfillment means that no assignment, which would exceed the target agreement for
the scale base contract, will be created.
As of SAP Media 4.72, the quantity or sales volume entered manually is used as the scale base for
calculation during settlement of scale base contracts.
1.5.13 IS-M-AM-BL
1.5.13.1 IS-M-AM-BL-O
Billing Document
Order Billing
1.5.13.1.1 Billing Document in Collective Processing: Default Values for Credit

Management (Modified)
Use
As of SAP Media 4.72, modified default values for credit management are available on the selection
screen for order billing in collective processing (report RJHFAK, transaction JHF7 and report
RJHFAKDI). All billing datasets with one of the credit limit statuses listed below are now excluded from
the selection as a default setting:
-
Credit check performed, transaction not OK
Credit check performed, transaction not OK, partial release
______________________________________________________________
SAP AG
133
SAP System
______________________________________________________________
1.5.13.2 IS-M-AM-BL-S
Contract Settlement
1.5.13.2.1 Discount/Price Adjustment for Scale Base Contracts (Enhanced)

Use
As of SAP Media 4.72, the system also evaluates information on discount/price adjustments for scale
base contracts. The following options are available here:
o
Adjustment in the order was previously already available and means that the higher value is used as
the scale base for every order for which the target agreement of the scale base contract has already
been exceeded.
Adjustment for interim settlement means that the target agreement for the scale base contract is
increased to the values obtained during interim settlement after each interim settlement.
Prohibit over-fulfillment means that no assignment, which would exceed the target agreement for
the scale base contract, will be created.
As of SAP Media 4.72, the quantity or sales volume entered manually is used as the scale base for
calculation during settlement of scale base contracts.
1.5.14 IS-M-AM-ST
1.5.14.1 IS-M-AM-ST-R
Settlement
Revenue Distribution
1.5.14.1.1 Existing Revenue Distribution Procedure No Longer Supported

(Modified)
Use
The new revenue distribution procedure including revenue recognition and partner settlement has been
available since SAP Media 4.62. As announced previously, the existing revenue distribution procedure
will only be supported for a limited period.
Information on the implementation of the new procedure is available in the online documentation and the
Implementation Guide.
1.5.15 IS-M-AM-RR
Revenue Recognition
1.5.15.1 FI Document Type for Revenue Recognition Reversal Run (New)

Use
______________________________________________________________
SAP AG
134
SAP System
______________________________________________________________
As of SAP Media 4.72, you can specify an FI document type, which is used for documents that are
generated during a reversal run for revenue recognition (Transaction VF46), in Customizing.
If you do not specify this type of FI reversal document type, the system uses the same FI document type
as that used during revenue recognition during the revenue recognition reversal run (as was previously
the case).
These settings are available in the SAP Customizing Implementation Guide under the following path:
SAP Media -> Advertising Management -> Settlement -> Revenue Distribution and Partner Settlement
-> Revenue Recognition -> Assign Revenue Recognition Category to FI Document Types. Enter the FI
reversal document type in addition to the FI document type here.
1.5.16 IS-M-AM-MS
Connection of Media Technical Systems
1.5.16.1 Technical Interface (Enhanced)

Use
As of SAP Media 4.72, the interface used to integrate technical systems (IS-M/ITA) has been enhanced as
follows:
o
Artwork assignment
-
Additional fields have been included in the artwork assignment in SAP Media 4.72 (refer to
the following release note Artwork Assignment). These fields have also been included in the
RJHATBLZ structure.
You can now use the Text entry/ad design (ISP_AD_DESIGN) function to modify existing
artwork assignments or create new assignments.
Texts
-
The FORMAT_COL field has been included in the RJHATTXT and RJHATTXTO structures so
that SAPscript texts can be transferred. The formatting of SAPscript texts is also exported here.
The ad spec (text type MOAZ) is now exported in addition to the raw text (text type ROHT) in
the Text Entry/Ad Design function (ISP_AD_DESIGN). The XMOTIVTEXT field has been
included in the RJHATMO structure that is transferred with the ad spec to show that an ad spec
text exists.
The Text Entry/Ad Design function (ISP_AD_DESIGN) can now be used in the technical
system to create or modify the raw text and the ad spec text. Up until and including SAP Media
4.71, the technical system could be used to create but not modify a raw text.
Order transfer system

-
You can now define several order transfer systems for each sales area. The key field
Assignment Number in Order Transfer System has been included in the Customizing table
______________________________________________________________
SAP AG
135
SAP System
______________________________________________________________
Determine Technical System for Order Transfer. This means you can transfer an order to one
or more technical systems for production during the update.
-
When defining technical systems, you can select the System is IS-M/AMC indicator.
Editor in the CIC

The value 3 (CIC Workspace: Import Data. Editor remains active) can now be added to the
PAR_AD_DESIGN_CALL_TYPE parameter in the Text Entry/Ad Design function. This value is
used to fetch changes to the ad content whilst continuing to design the ad content. The ISP
_AD_DESIGN function is accessed with this value if the editor is active and the Refresh Pricing
function is accessed on the tab page for entry of ad orders. If the value 2 is entered (CIC Workspace:
Import Data. Editor is terminated), design of ad content is terminated once the data has been
imported.
Define front end ID

During synchronous access of the IS-M/ITA funcions, the RFC destination is now determined
according to the front end ID. The system reads the front end ID from the environment variables in
the operating system. This is not possible if SAP GUI for HTML is used.
If it is not possible to determine a front-end ID from the environment variables, the
JHFRONTENDID SET/GET parameter is now evaluated. You can also determine various
user-related RFC destinations in the SAP GUI for HTML.
Page/column format
The technical system could only previously identify the
page/column format in the ad spec during access of the Text Entry/Ad Design (ISP_AD_DESIGN)
function, if no page/column format had been defined in Advertising Management. The technical
system can now modify the page/column format. If the technical system does modify the
page/column format and the Check Page/Column Format indicator in the order change type is
selected, the system checks whether the ad spec page/column format is suitable for the page/column
format of the associated schedule lines.
New fields in the ad header (Structure RJHATPAK))

The following fields have also been included in the RJHATPAK structure:
Current User
Client
New fields in the ad spec (Structure RJHATMO)

The following fields have been included in the RJHATMO structure:
-
Style
Template
Content Component 1. Technical Level
Rule Group for Ad Content Validation
New fields in the ad schedule line (Structure RJHATPS)

The following fields have also been included in the RJHATPS structure:
-
Content Component 1. Technical Level
Booking Unit for Internet Publication Indicator
Internet Publication Start Date
______________________________________________________________
SAP AG
136
SAP System
______________________________________________________________
Internet Publication End Date
The new Rule Group for Ad Content Validation field can be evaluated in the RJHALI01 and
RJHSTAT3 reports from Advertising Management.
New parameters in the Text Entry/Ad Design function

The following optional import parameters have been added to the Text Entry/Ad Design
(ISP_AD_DESIGN) function:
-
Order header (Structure RJHATPAK)
Item (Structure RJHATPAP)
Schedule lines (Structure RJHATPS)
Additional order transfer systems can be assigned in Customizing as follows: SAP Media -> Advertising
Management -> Connection of Media Technical Systems -> Assign Order Transfer Systems.
The System is IS-M/AMC indicator is selected in Customizing as follows: SAP Media -> Advertising
Management -> Connection of Media Technical Systems -> Define Technical Systems.
See also
Additional information on the technical interface is available as the Technical Interface IS-M/ITA:
Integration of Technical Systems PDF document in the SAP Library in the Advertising Management
documentation.
1.6 IS-M-PLM
Product Lifecycle Management
1.6.1 Creating a Media Product Master from a WBS Element (Enhanced)

Use
As of SAP R/3 Enterprise PLM Extension 2.00 (EA_APPL 200), you can carry out several alternative
planning runs for a project in Easy Cost Planning.
As of SAP Media 4.72, you can select the CO plan version from which the costing data is to be copied
when creating a media product master from a WBS element.
This means you can use several different costing versions for a WBS element and use one of them to
create the media product master.
This function is only available if you have activated the SAP R/3 Enterprise PLM Extension and have
activated the Easy Cost Planning function in several CO versions for the controlling area in the WBS
element.
______________________________________________________________
SAP AG
137
SAP System
______________________________________________________________
1.7 IS-M-IS
Information System
1.7.1 IS-M-IS-SD
Information System for Media Sales and Distribution
1.7.1.1 DataSources in the SAP Business Information Warehouse (New)

Use
The following DataSources hierarchies have been created in Release 4.72:
0ME_MED_ISS_BP_HIER Assign business partner to media issue
The hierarchy is based on the media issue InfoObject. Media issues are read from the material master.
(Field ISMHIERARCHLEVL = '3'). Table JPTBUPAASSIGN is used to read the business partners that
have been assigned to the material number. The result is transferred to BW in a hierarchical format.
0ME_MED_ISS_HIER Relationship between media product family, media product and media issue
The hierarchy is based on the media issue InfoObject. The hierarchical relationship between the media
product family, media product and media issue is displayed. A dummy node is inserted for media issues
that do not have a media product.
1.7.1.2 Enhancements to the Circulation Book (New)

Use
As of SAP Media 4.72, additional characteristics can be updated to the circulation book. These
characteristics are as follows: region, county code, city number, Newspaper Designated Market Zone for
ABC, CTZ, RTZ, OTZ zones for ABC, service type, weekday, and sales promotion. Two additional fields
are also available for customer-specific data.
If you change the selection of characteristics to be updated for the audit report type in Customizing, you
should delete and recompile the circulation book for the relevant period (since the last audit report). If
you do not recompile the circulation book, update may be terminated, particularly when processing
backdated order changes in Periodical Sales and Distribution.
Please note that the degree of granularity increases when additional characteristics are updated. This may
mean there is a significant increase in the number of entries in the circulation book. Performance of the
update and evaluation programs may be affected.
You can select the characteristics that are to be updated in the Customizing activity Maintain Audit
Report Types.
______________________________________________________________
SAP AG
138
SAP System
______________________________________________________________
1.7.1.3 Improved Performance in Circulation Book Update (New)

Use
As of release 4.72, the new update program RJIIVW01_SUBSCRIPTION is available for updating
circulation figures in the circulation book.
You can use the new program instead of the update programs RJIIVW01 and RJIABC00.
The new program achieves the same result as the existing two but performance is better, provided at least
one of the following two conditions applies:
o
None of the fields in the table of business data (JKKD) are updated to the circulation book. You
specify which data is updated to the circulation book in the Customizing step Maintain Audit Report
Types. The following business data can be updated: billing frequency, customer price group, rate
code, and customer group.
None of the fields in the table of schedule line data (JKEP) are updated to the circulation book. This
applies to the fields Price Frequency, Service Type, Purchase Price, Purchase Price Condition Type,
and Tax Code.
If this condition applies, the possible improvement in performance also depends on the number of
schedule lines in the system with a quantity greater than one. The fewer there are, the better.
______________________________________________________________
SAP AG
139

RN IS Media 472 EN

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

RN IS Media 472 EN

Încărcat de

Drepturi de autor:

Formate disponibile

SAP Media

Copyright(c) 2004 SAP AG. All rights reserved.

IS-M SAP Media

Business Information Warehouse

Text Field for Complaint in Short Complaint Dialog (New)

Quantity Forecasts According to Reference Issues (New)

Document Management for SAP Media Business Objects (New)

1.1.1.1 Document Management for SAP Media Business Objects (New)

Import document from file

Features of the folder or document

Rename folder or document

Export with block

Import new version

Cut, copy and paste

Functions provided by the Viewer include:

Display and change documents and their features

Version overview with version display and processing

ISM_DM_DOCS_OF_BUS_OBJ_GET: Define documents for a business object

ISM_DM_FOLDERS_OF_BUS_OBJ_GET: Define folder for a business object

ISM_DM_IO_CONTENT_GET: Provide content of a document

ISM_DM_FOLDER_CREATE_FOR_BO: Create folder for a business object

ISM_DM_IO_CREATE_WITH_FILE: Create document using the file system

ISM_DM_IO_CREATE_WITH_TABLE: Create document using a table

ISM_DM_IO_CREATE_WITH_URL: Create document using a URL

ISM_DM_VERS_CREATE_WITH_FILE: Create a new version of a document using the file

ISM_DM_VERS_CREATE_WITH_TABLE: Create a new version of a document using a table

ISM_DM_IO_PROPERTIES_CHANGE: Change the document properties

ISM_DM_IOS_DELETE: Delete documents from a business object

ISM_DM_IOS_FOR_AD_CONTENT_GET: Define all documents for all relevant business objects

HTTP Content Server

Use of an HTTP Content Server is recommended in the live system.

1.1.1.2 Business Partner Administration Using SAP Business Partner

1.1.1.3 Conversion Tool for Customers and Vendors (New)

1.1.1.4 Restrictions on Changes to Organizational Units (Changed)

1.1.1.5 Maintaining the Contract Hierarchy As a Relationship in SAP BP (New)

1.1.1.6 Alternative Business Partners in User-Defined Roles (Enhanced)

Voucher copy recipient

Box number recipient

Ad spec master recipient

Correction deduction recipient

Ad spec master sender

General business partner

1.1.1.7 Processing Order Data from the Internet (Enhanced)

Product Master Data

1.1.2.1.1 13-Digit ISBN (Changed)

1.1.2.1.2 Enhancements to the Issue Sequence (New)

Shipping planning records for series sales

New attribute for the issue sequence

1.1.2.1.3 Refresh of Quantity Planning Attributes in Issue Sequences (Changed)

Actual issue variant type

Standard issue variant type (planned)

1.1.2.1.4 Settings for Media Products in Series Sales (New)

Planning records for media issue deliveries

1.1.2.1.5 Series Combinations (New)

1.1.2.2.1 BAPIs for the Booking Unit (New)

GetDetail (Read booking unit)

GetList (Select booking unit)

ExistenceCheck (Check existance of booking unit)

Display (Display booking unit)

Create (Create booking unit)

Refer to the Sale of Display Classified Ads release note.

1.1.2.2.2 BAPIs for the Content Component (New)

GetDetail (Read content component)