SAP R/3 Enterprise
Release 4.70
Release Notes
© Copyright 2002 SAP AG. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission
of SAP AG. The information contained herein may be changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary software components of other software
vendors.
Microsoft®, WINDOWS®, NT®, EXCEL®, Word®, PowerPoint® and SQL Server® are registered trademarks of
Microsoft Corporation.
IBM®, DB2®, OS/2®, DB2/6000®, Parallel Sysplex®, MVS/ESA®, RS/6000®, AIX®, S/390®, AS/400®, OS/390®, and
OS/400® are registered trademarks of IBM Corporation.
ORACLE® is a registered trademark of ORACLE Corporation.
INFORMIX®-OnLine for SAP and Informix® Dynamic Server
Incorporated.
TM
are registered trademarks of Informix Software
UNIX®, X/Open®, OSF/1®, and Motif® are registered trademarks of the Open Group.
Citrix®, the Citrix logo, ICA®, Program Neighborhood®, MetaFrame®, WinFrame®, VideoFrame®, MultiWin® and other
Citrix product names referenced herein are trademarks of Citrix Systems, Inc.
HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology.
JAVA® is a registered trademark of Sun Microsystems, Inc.
JAVASCRIPT® is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape.
SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP EarlyWatch, BAPI,
SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com are trademarks or registered trademarks of SAP AG
in Germany and in several other countries all over the world. All other products mentioned are trademarks or registered
trademarks of their respective companies.
Design: SAP Communications Media
SAP
System
Table of Contents
SAP AG
______________________________________________________________
1
2
3
4
4.1
4.1.1
4.1.2
4.2
4.2.1
4.2.2
4.2.3
4.2.3.1
4.2.3.2
4.3
4.3.1
4.3.1.1
4.4
4.4.1
4.4.2
4.5
4.5.1
4.5.2
4.5.3
SAP Reference IMG structure changes in
Release 4.70
Activation Switch for the SAP R/3
Enterprise Extension Set
Accessibility
CA
Cross-Application Components
CA-ESS Employee
self-service
HRESSWWW Enhancement Replaced
Customizing for the Leave Request ESS
Application (Enhanced)
CA-DMS Document
Management
Structure Changes in Document Management
Document processing in the Web interface
CA-DMS-EDT Document
Processing
Structural Changes in PLM-LDM
CAD desktop
CA-CL Classification
CA-CL-CHR Characteristics
Where-Used List for Characteristics and
Characteristic Values
CA-CAD CAD Integration
Structural Changes in PLM-LDM
CAD desktop
CA-BP SAP Business
Partner
Changes in the IMG Structure of the SAP
Business Partner
Properties of BP Roles and BP
Relationships
Changes to the Locator and to the
Business Partner Interface
2
3
5
5
5
6
7
9
10
10
11
12
______________________________________________________________
SAP AG
iii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
4.5.4
4.5.5
4.5.6
4.5.7
4.5.7.1
4.5.7.2
4.5.7.3
4.5.8
4.5.8.1
4.6
4.6.1
4.6.2
4.6.2.1
4.6.2.1.1
4.6.3
4.6.3.1
4.7
4.7.1
4.8
4.8.1
4.8.2
4.8.3
4.8.4
4.8.5
4.8.6
International Address Versions
Changes in the IMG structure for Release
6.20
Various New Features and Changes in
Business Partner
CA-BP-BP Business
Partners
Changes to Data Cleansing
Deletion of Business Partners without an
Archiving Procedure
International Bank Account Number (IBAN)
CA-BP-RS Business Partner
Relationship
Changes to the Business Partner
Relationships
CA-GTF General
Application Functions
Terminology for Country Version Brazil
(Changed)
CA-GTF-TS Technical
Application Support
CA-GTF-TS-CE Conversion Exits
Data Elements of Reference Document
Numbers (changed)
CA-GTF-SCM Schedule Manager
Schedule Manager (extended)
CA-NO Messages
New Developments in Notifications:
Several Customer Subscreens Possibl
CA-TS Time Sheet
Cross-Application Time Sheet
Enhancements (General)
CATS notebook: Recording Working Times
Offline (New)
User Interfaces for the Time Sheet
(Enhanced)
Personal Templates in the
Cross-Application Time Sheet (New)
Display and Approve Working Times and
Tasks (New)
Enhancements in CATS for service
13
13
16
17
18
18
20
20
20
20
22
22
23
24
25
26
______________________________________________________________
iv
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
4.8.7
4.8.8
4.8.9
4.9
4.9.1
4.9.2
30
4.9.3
4.9.4
4.10
4.10.1
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
5.9
5.10
5.11
5.12
providers
Business Add-Ins (BAdIs) for the
Cross-Application Time Sheet (New)
Account Assignment Dimensions for Fund
Accounting (New)
Returns for Service Entry Sheets from
Time-Sheets (New)
CA-JVA Joint Venture
Accounting
Replacement of actual posting
transactions
Switch for activating Joint Venture
Accounting in a system
Production Sharing Accounting (Enhanced)
CA-DSG Digital
Signature
Digital Signature (extended)
FI Financial
Accounting
Structure Changes for Country Version
Brazil
Country Version India in Standard R/3
System
Accessible: Financial Accounting
(Modified)
Condition-Based Tax Calculation (New)
Terminology for Country Version Brazil
(Changed)
Data Medium Exchange Engine (Changed)
Structure Changes in the FI
Implementation Guide (IMG)
Release Notes from Country Version India
Add-On (FI)
Payments with the Orbian payment system
(enhanced)
Plants Abroad (Enhanced)
Changes to Structures for Country
Version India
FI-GL General Ledger
26
27
28
29
29
29
38
40
40
41
42
45
47
48
49
50
______________________________________________________________
SAP AG
v
SAP
System
Table of Contents
SAP AG
______________________________________________________________
5.12.1
5.12.2
5.12.3
5.12.4
5.12.5
5.12.5.1
5.12.5.2
5.12.5.3
5.12.5.4
5.12.5.5
5.12.5.6
5.12.5.7
5.12.5.8
5.12.5.9
5.12.5.10
5.12.5.10.1
5.12.5.11
5.12.5.11.1
5.12.5.12
5.12.5.12.1
5.12.5.12.2
5.12.5.12.3
5.12.5.12.4
5.12.5.12.5
5.12.5.12.6
Accounting
Valuation Posting (Enhanced)
Manual Accruals (New)
Parallel Valuation Methods (Changed)
Provisions for Awards (New)
FI-GL-GL Basic Functions
Document Overview in the ALV List for
Document Entry/Parking (New)
Displaying Parked Documents (New)
Entering Long Texts in the FI Enjoy
Transactions (New)
Personalized Tree (Changed)
Generic Object Services for FI Document
Display Transactions (Extended
ALE remote comparison for distributed
FIDCC1/2 - FI-GL (enhanced)
Tax Invoices and VAT Reporting (Changed)
Advance Return for Tax on Sales and
Purchases (New)
Condition-Based Excise Determination in
MM (New)
FI-GL-GL-MD Master Data
Chart of Accounts and Financial
Statement Version (New)
FI-GL-GL-AP G/L Account
Posting
Changing Last Adjustment Dates in Line
Items (New)
FI-GL-GL-CL Closing
Operations
Chart of Accounts and Financial
Statement Version (New)
Changing Last Adjustment Dates in Line
Items (New)
Accumulated Balance Audit Trail
(Modified)
Closng/Opening Postings (New)
COS: Extension of Functional Area Field
(modified)
Foreign Currency Valuation of SL
Balances (Modified)
51
53
54
55
55
57
57
59
59
59
60
60
60
61
62
62
______________________________________________________________
vi
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
5.12.5.12.7
5.12.6
5.12.6.1
5.13
5.13.1
5.13.1.1
5.13.1.2
5.13.1.3
5.13.1.4
5.13.1.5
5.13.1.6
5.13.1.7
5.13.1.8
5.13.1.9
5.13.1.10
5.13.1.11
5.13.1.12
5.13.1.13
5.13.1.14
5.13.1.14.1
5.13.1.14.2
5.13.1.15
5.13.1.15.1
5.13.1.16
5.13.1.16.1
5.13.1.16.2
5.13.1.16.3
5.13.1.16.4
5.13.1.16.5
Structure Changes in Inflation
Accounting
FI-GL-IS Information
System
DRB (Enhanced)
FI-AP Accounts Payable
FI-AP-AP Basic Functions
Returns for Section 16 of the Taxes and
Management Act (New)
Annual Returns Under Section 194 A (New)
Annual Returns Under Section 194 C
(Changed)
Canceled TDS Certificates (Changed)
TDS Programs (Changed)
Annual Returns for Classic TDS (Deleted)
Classic TDS Program (Changed)
Withholding Tax Reporting (Changed)
Withholding Tax Reports (Changed)
Entering Long Texts in the FI Enjoy
Transactions (New)
Document Types for Journal Vouchers and
Provisions (Changed)
Extended Withholding Tax and ALE
Distribution for Master Data and
Withholding Tax Analysis Report for
Extended Withholding Tax (New)
FI-AP-AP-MD Master Data
Customer-Specific Fields in Business
Partner Master Data (New)
Extended Withholding Tax and ALE
Distribution for Master Data and
FI-AP-AP-IC Invoices and
Credit Memos
Amount Split in the FI Enjoy Document
Parking Transaction (New)
FI-AP-AP-PT Payment
Transactions
Payment Cards
Domestic Payments by PAYMUL (New)
Payments in Finland (Changed)
Payments by BACS (Changed)
Payments with Bank of Ireland and Allied
63
64
65
67
71
72
72
73
73
74
75
75
75
______________________________________________________________
SAP AG
vii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
5.13.1.16.6
5.13.1.16.7
5.13.1.16.8
5.13.1.17
5.13.1.17.1
5.13.1.18
5.13.1.18.1
5.13.1.18.2
5.14
5.14.1
5.14.1.1
5.14.1.2
5.14.1.3
5.14.1.4
5.14.1.5
5.14.1.5.1
5.14.1.5.2
5.14.1.6
5.14.1.6.1
5.14.1.7
5.14.1.7.1
5.14.1.7.1.1
5.14.1.7.1.2
5.14.1.8
5.14.1.8.1
5.14.1.8.2
5.14.1.8.3
Irish Banks (Changed)
Payments in Sweden (Changed)
Automatic Scheduling of the Payment
Program (New)
Payment Program SAPF110S (Enhanced)
FI-AP-AP-CR Correspondence
Balance Confirmation (Enhanced)
FI-AP-AP-CL Closing
Operations
Returns for Section 16 of the Taxes and
Management Act (New)
Structure Changes in Inflation
Accounting
FI-AR Accounts
Receivable
FI-AR-AR Basic Functions
Withholding Tax Reports (Changed)
Document Display: Invoice Status
(Enhanced)
Entering Long Texts in the FI Enjoy
Transactions (New)
Withholding Tax Analysis Report for
Extended Withholding Tax (New)
FI-AR-AR-MD Master Data
Customer-Specific Fields in Business
Partner Master Data (New)
Extended Withholding Tax and ALE
Distribution for Master Data and
FI-AR-AR-IC Invoices and
Credit Memos
Amount Split in the FI Enjoy Document
Parking Transaction (New)
FI-AR-AR-MP Manual Payments
FI-AR-AR-MP-BF Basic Functions
Fast Entry Payment Receipts (Changed)
Open Item Clearing (Enhanced)
FI-AR-AR-PT Payment
Transactions
Domestic Payments by PAYMUL (New)
Payments in Finland (Changed)
Payments by BACS (Changed)
77
79
80
80
81
82
84
84
85
85
86
87
87
90
______________________________________________________________
viii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
5.14.1.8.4
5.14.1.8.5
5.14.1.8.6
5.14.1.9
5.14.1.9.1
5.14.1.10
5.14.1.10.1
5.14.1.11
5.14.1.11.1
5.14.1.12
5.14.1.12.1
5.15
5.15.1
5.15.2
5.15.3
5.15.3.1
5.15.3.1.1
5.15.4
5.15.4.1
5.15.4.1.1
5.15.4.2
5.15.4.2.1
5.15.4.2.2
5.15.5
5.15.5.1
5.15.5.2
5.15.5.3
5.15.5.4
Payments with Bank of Ireland and Allied
Irish Banks (Changed)
Payments in Sweden (Changed)
Payment Program SAPF110S (Enhanced)
FI-AR-AR-DU Dunning
Performance Dunning Program
FI-AR-AR-OI Open Item
Management
Residual Items in Invoice Currency (New)
FI-AR-AR-CR Correspondence
Balance Confirmation (Enhanced)
FI-AR-AR-CL Closing
Operations
Structure Changes in Inflation
Accounting
FI-BL Bank Accounting
FI Cash Journal (Extended)
Repetitive Codes (Modified)
FI-BL-MD Master Data
FI-BL-MD-BK Bank Master Data
IBAN (International Bank Account Number)
(new)
FI-BL-BM Cash Balance
Management
FI-BL-BM-CM Check Management
Integration of check management in PMW
and IDoc
FI-BL-BM-BE Bill of Exchange
Management
Printouts of Bill of Exchange
Transaction Records (Changed)
Bill of Exchange Transactions Program
(Changed)
FI-BL-PT Payment
Transactions
Cross-country bank account transfers
(new)
Transaction for entering online payments
(enhanced)
Check Printing Program RFFOUS_C
(Enhanced)
Cross-Payment Run Payment Medium
92
94
96
96
98
99
99
100
100
100
100
100
101
102
______________________________________________________________
SAP AG
ix
SAP System
Table of Contents
SAP AG
______________________________________________________________
5.15.5.5
5.15.5.5.1
5.15.5.5.1.1
5.15.5.5.1.2
5.15.5.5.1.3
5.15.5.5.1.4
5.15.5.5.1.5
5.16
5.16.1
5.16.2
5.16.3
5.16.4
5.16.4.1
5.16.4.1.1
5.16.4.1.2
5.16.4.2
5.16.4.2.1
5.16.4.2.2
5.16.4.3
5.16.4.3.1
5.16.4.3.2
5.16.4.3.3
5.16.4.3.4
5.16.4.3.4.1
5.16.4.3.5
5.16.4.3.5.1
Creation (new)
FI-BL-PT-BS Bank Statement
FI-BL-PT-BS-EL Electronic Bank
Statement
DRB (Enhanced)
Conversion of Incoming Electronic Bank
Statments in LUM2 Format (New)
Electronic Bank Statement (extended)
Postprocessing the electronic bank
statement (new)
Processing of returns in the electronic
bank statement (new)
FI-AA Asset Accounting
New Account Assignment Objects in the
Asset Master Record
Customizing: Resetting Asset
Transactions (New)
Parallel Valuation in Asset Accounting
FI-AA-AA Basic Functions
FI-AA-AA-MA Asset
Maintenance
Investment Support Areas Modifiable
Using BAPIs for Asset Master Recor
Creating Subnumbers in Purchase Orders
and Purchase Requisitions (New)
FI-AA-AA-DE Depreciation
Enhancement of User Exits in
Depreciation Calculation
Change to Rounding with Base Method
Immediate Depreciation
FI-AA-AA-TR Transactions
New BAdI for Changing the Asset Document
Changes to Posting
Settlement of Investment Support for
Assets Under Construction
FI-AA-AA-TR-AC Acquisitions
New Transaction Type for
Post-Capitalization
FI-AA-AA-TR-ST Budget
Monitoring by Statistical Order / WBS Elem
Change to Budget Monitoring with
102
103
104
105
106
106
107
108
108
108
109
110
111
111
111
______________________________________________________________
x
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
5.16.4.3.6
5.16.4.3.6.1
5.16.4.3.6.2
5.16.5
5.16.5.1
5.16.5.2
5.16.5.2.1
5.16.5.2.2
5.16.5.2.3
5.16.5.3
5.16.5.3.1
5.16.6
5.16.6.1
5.16.7
5.16.7.1
5.16.7.2
5.16.7.2.1
5.16.7.2.2
5.17
5.17.1
5.17.2
5.17.3
Orders/WBS Elements
FI-AA-AA-TR-PG Posting
Depreciation to the General Ledger
New Report for Periodic Posting of APC
Values: RAPERB2000
New Report for Depreciation Posting:
RAPOST2000
FI-AA-SVA Special
valuation
Depreciation Using Half-Year and Annual
Rates in Japan (New)
FI-AA-SVA-HI Handling of
Inflation
Reverse Multiple Asset Revaluation
Documents (New)
Revaluation After End of Useful Life
(New)
Structure Changes in Inflation
Accounting
FI-AA-SVA-IS Investment
Support
New Report for Posting the Maximum
Investment Support Amount
FI-AA-LM Leasing
Processing
Asset Accounting Engine, and Additive
Interface
FI-AA-IS Information
System
Changes in the Asset Explorer
FI-AA-IS-ST Standard Reports
Year-End Income Tax Depreciation Report
(New)
Changed Assignment in Mid-Quarter
Convention Acquisitions Report
FI-SL Special Purpose
Ledger
Using Pooled Tables (Deleted)
Archive Connection for Line Item Reports
and Summary Reports (Changed)
FI-SL-IS Information
System
112
112
112
113
113
113
114
114
114
115
116
116
116
116
116
117
118
118
119
119
______________________________________________________________
SAP AG
xi
SAP
System
Table of Contents
SAP AG
______________________________________________________________
5.17.3.1
5.17.3.2
5.18
5.18.1
5.19
5.19.1
5.19.2
5.19.3
5.19.3.1
5.19.3.2
5.19.3.3
5.19.3.4
5.19.3.5
5.19.3.6
5.19.3.7
5.19.3.8
5.19.3.9
5.19.3.10
5.19.3.11
5.19.3.12
5.19.4
5.19.4.1
5.19.4.2
5.19.4.3
5.19.4.4
5.19.4.5
5.19.4.6
DRB (Enhanced)
Transport Report Writer, Sets and Groups
(Changed)
FI-RL Retail Ledger
Retail Ledger
FI-TV Travel
Management
BOR und Workflows in Travel Management
Standardization of Travel Manager (TRIP)
and Planning Manager (TP01)
FI-TV-PL Travel Planning
Mobile Travel Planning for PDAs
SABRE Interface for SAP R/3 Travel
Planning
Flight Bookings
Hotel Bookings
Car Rental Bookings
Enhanced Functions for Booking German
Rail (Deutsche Bahn) Services
Enterprise-Specifc Information in PNR Improved Communication with
Reason codes
Synchronization of Traveler Profiles
Between AMADEUS and SAP
Upload Current Table Contents for IATA
Locations and Providers
Structure Changes in the Implementation
Guide for R/3 Travel Planning
Further New Functions in Travel Planning
FI-TV-COS Travel Expenses
Public Sector Germany: German Federal
Travel Expenses Legislation
Public Sector Germany: Border Crossing
Rules
Public Sector Germany: Comparison
Calculation for Meals Per Diems
Public Sector Germany: Comparison
Calculation for Accommodation
Public Sector Germany: Several Domestic
Business Trips on One Day.
Clearing Additional Amounts and
120
123
126
127
130
130
132
132
133
134
136
136
137
137
______________________________________________________________
xii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
5.19.4.7
5.19.4.8
5.19.4.9
5.19.4.10
5.19.4.11
5.19.4.12
5.19.4.13
5.19.4.14
5.19.4.15
5.19.4.16
5.19.4.17
5.19.4.18
5.19.4.19
5.19.4.20
5.19.4.21
5.19.4.22
5.19.4.23
5.19.4.24
5.19.4.25
5.19.4.26
5.19.4.27
5.19.4.28
Income-Related Expenses
Federal State Travel Expense Laws for
Rhineland Palatine: Trip Segment
Kilometer Accounting: Enhancement of
Cumulation According to Period
Public Sector France: Travel Expense
Accounting for Domestic,
Public Sector France: Processing
Deductions
Public Sector France: Processing
Advances
Public Sector France: Standard Form for
Travel Expenses
Three Month Rule: First Level
Enhancement to BAPI Interface for Travel
Management
New Functions for Credit Card Clearing
in Travel Management
Avoidance of Cross-Company Code Postings
in Travel Management
Travel Management for Finnland
Creating and Posting Receipts and
Advances in Foreign Currencies
Structure Changes in the Implementation
Guide for R/3 Travel Expenses
Offline Travel Expenses: Enter Travel
and Entertainment Expenses
Alternative Processing of Paid Receipts
Enhancement of Posting Interface for
Travel Management
Receipt Wizard: Enter and Process
Complex Receipts
Separation Allowances: Public Sector
Germany
Payment of Separation Allowances using
Different Payment Methods
Travel Expenses: France and German
Federal Travel Expense Laws
Comparison Calculation for Travel
Expenses: Public Sector
Separation of Travel Requests and
Requests for Travel Expense
138
138
139
139
140
141
141
143
144
144
146
146
148
150
150
153
153
153
154
155
______________________________________________________________
SAP AG
xiii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
6
6.1
6.2
6.2.1
6.2.2
6.2.2.1
TR Treasury
Various enhancements in cash management
TR-CM Cash Management
Various enhancements in cash management
TR-CM-CM Basic Functions
Various enhancements in cash management
7
7.1
CO Controlling
CO Document Header: Reference
Transaction Filled for Internal Document
CO-OM Overhead Cost
Controlling
Transfer of Actual Data into Controlling
(New)
BAPIs for Actual Postings in Controlling
(Extended)
Valuation of activity allocations
BAdI For The Valuation of Activity
Allocations (New)
Overhead Rates: Calculation Base Cost
Center/Activity Type (Extended)
Transactions for The Manual Actual
Postings in Controlling (Changed)
Deletion Program for Archiving Object
CO_CCTR_ID (Extended)
WBS Element Groups (New)
CO-OM-CEL Cost Element
Accounting
CO-OM-CEL-RE Reconciliation
Financial Accounting / Controlling
Partner Functional Area for
Reconciliation Between CO and FI
CO-OM-CCA Cost Center
Accounting
CO-OM-CCA-PL Cost Center
Planning
Read BAPIs for Overhead Cost Planning
(New)
7.2
7.2.1
7.2.2
7.2.3
7.2.4
7.2.5
7.2.6
7.2.7
7.2.8
7.2.9
7.2.9.1
7.2.9.1.1
7.2.10
7.2.10.1
7.2.10.1.1
161
161
161
162
163
164
164
164
165
165
166
166
166
166
______________________________________________________________
xiv
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
7.2.10.2
7.2.10.2.1
7.2.11
7.2.11.1
7.2.11.2
7.2.11.3
7.2.11.4
7.2.11.4.1
7.2.11.5
7.2.11.5.1
7.2.11.6
7.2.11.6.1
7.2.11.6.2
7.2.11.7
7.2.11.7.1
7.2.11.7.2
7.2.11.7.2.1
7.2.12
7.2.12.1
7.2.12.2
7.3
7.3.1
7.3.1.1
CO-OM-CCA-CM Commitments and
Funds Commitments
Comitment Update for Invoice Receipt
Without Goods Receipt
CO-OM-OPA Overhead Cost
Orders
Resource-Related Billing for Internal
Orders With Revenues (new)
Deletion Program for Archiving Object
CO_ORDER (enhanced)
Static Processing of Resource-Related
Billing (Deleted)
CO-OM-OPA-PL Order Planning
Planning and Budgeting in Any Currency
(new)
CO-OM-OPA-BU Order Budgeting
Availability Control in Object Currency
(new)
CO-OM-OPA-CM Commitments and
Funds Commitments
Field Control for Funds Commitments
(new)
Comitment Update for Invoice Receipt
Without Goods Receipt
CO-OM-OPA-CL Periodic Order
Closing
Settlement of Investment Support for
Assets Under Construction
CO-OM-OPA-CL-IC Interest
Calculation
Interest Calculation for Special Periods
(Changed)
CO-OM-IS Information
System, iViews
DRB (Enhanced)
Display of Archived Line Items in The
Line Item Report (Extended)
CO-PC Product Cost
Controlling
CO-PC-PCP Product Cost
Planning
External Cost Estimate Interface Through
167
167
167
167
168
168
169
171
172
172
172
173
173
174
174
174
175
175
175
______________________________________________________________
SAP AG
xv
SAP
System
Table of Contents
SAP AG
______________________________________________________________
7.3.1.2
7.3.1.3
7.3.2
7.3.2.1
7.3.2.2
7.3.3
7.3.3.1
7.3.3.2
7.3.3.2.1
7.3.3.2.2
7.4
7.4.1
7.4.2
7.4.2.1
7.4.2.2
7.4.2.2.1
7.4.3
7.4.3.1
7.4.3.1.1
7.4.3.2
7.4.3.2.1
7.4.4
7.4.4.1
BAPIs
Flexible Material Selection for Costing
Runs
Mass Costing of Sales Orders
CO-PC-OBJ Cost Object
Controlling
Mass Costing of Sales Orders
Results Analysis Using Dynamic Items
(Enhanced)
CO-PC-ACT Actual
Costing/Material Ledger
Distribution of Usage Differences
CO-PC-ACT-MAC Multilevel
Actual Costing
Alternative Valuation Run
Revaluation of Consumption
CO-PA Profitability
Analysis
Changes to the IMG Structure in
Profitability Analysis
CO-PA-SPP Sales and Profit
Planning
New features in CO-PA Planning
CO-PA-SPP-IP Integrated
Planning
Transfer of Cost Component Split for
Activity Allocations (New)
CO-PA-ACT Flows of Actual
Values
CO-PA-ACT-OH Transfer of
Overhead
Transfer of Cost Component Split for
Activity Allocations (New)
CO-PA-ACT-PA Periodic
Adjustments
New features for periodic valuation and
top-down distribution
CO-PA-IS Information
System
DRB (Enhanced)
175
177
177
178
178
179
180
180
180
180
181
181
181
181
181
181
182
______________________________________________________________
xvi
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
8
8.1
8.1.1
8.1.2
8.1.2.1
8.1.2.2
8.1.2.3
8.1.2.3.1
8.1.3
8.1.3.1
8.1.4
8.1.4.1
8.1.4.2
8.1.4.2.1
8.1.5
8.1.5.1
8.1.5.1.1
8.1.6
8.1.6.1
9
9.1
IM Investment
Management
IM-FA Capital
Investments
Planning and Budgeting in Any Currency
(new)
IM-FA-IA Appropriation
Requests
Transfer of Appropriation Requests to
Measures (Extended)
Enhancement of Field Transfer From A
Request in WBS Element (new)
IM-FA-IA-MD Master Data
BAdI: Checking Appropriation Requests
(neu)
IM-FA-IP Investment
Programs
Reorganization of Investment Programs
(New)
IM-FA-IE Investment
Orders
Settlement of Investment Support for
Assets Under Construction
IM-FA-IE-BU Order Budgeting
Change to Budget Monitoring with
Orders/WBS Elements
IM-FA-PR Projects as
Investment Measures
IM-FA-PR-BU Project
Budgeting
Change to Budget Monitoring with
Orders/WBS Elements
IM-FA-IS Information
System
Depreciation Forecast and Primary Cost
Planning (Extended)
EC Enterprise
Controlling
EC-PCA Profit Center
Accounting
183
183
183
185
185
185
186
186
186
187
187
188
188
188
188
189
189
190
190
______________________________________________________________
SAP AG
xvii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
9.1.1
9.1.2
9.1.3
9.1.3.1
10
10.1
10.1.1
10.1.1.1
10.2
10.2.1
10.2.2
10.2.3
10.3
10.3.1
10.3.2
11
11.1
11.2
11.3
11.4
11.5
11.5.1
11.5.2
Archive Connection for Line Item Reports
(New)
Displaying Linked Documents for Line
Items (New)
EC-PCA-IS Information
System
DRB (Enhanced)
RE Real Estate
Management
RE-RT Rental
RE-RT-RA Rental
Accounting
Performance Dunning Program
RE-PR Real Estate
General Contract
Accrual/deferral for general contracts
Index adjustment for Real Estate general
contracts
Returned debit memos - Statistics
RE-FX Flexible Real
Estate Management
New in Flexibe Real Estate Management
Accessibility: Flexible Real Estate
Management
LO Logistics General
Country Version India in Standard R/3
System
Changes to Structures for Country
Version India
Exports Under Excise Regulations (New)
New functions in the High Performance
Retailing (HPR) project
LO-MD Logistics Basic
Data
Structural Changes in PLM-LDM
CAD desktop
190
190
191
193
193
193
193
194
195
196
196
197
198
199
______________________________________________________________
xviii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
11.5.3
11.5.4
11.5.4.1
11.5.4.2
11.5.5
11.5.5.1
11.5.5.2
11.5.5.3
11.5.5.4
11.5.5.5
11.5.5.6
11.5.5.7
11.5.6
11.5.6.1
11.5.6.1.1
11.5.6.1.2
11.5.6.2
11.5.6.2.1
11.5.6.2.2
11.5.6.2.3
11.5.7
11.5.7.1
11.5.7.2
11.5.7.2.1
11.5.7.3
11.5.7.3.1
11.5.7.3.2
11.5.8
11.5.8.1
11.5.8.2
LO-MD-PL Plant Master
Multiple Assignment of Assortments to
Sites/New Store Openings
Mass Maintenance of Master Data
LO-MD-MM Material Master
Customer, Vendor, and Material Master
Data (Changed)
Material Variant Distribution (New)
Prepack Allocation Planning
Variant Handling by Characteristics
Mass Maintenance of Master Data
Calculating Planned Delivery Time
LO-MD-RA Assortment
LO-MD-RA-MT Assortment
Maintenance
Layout Workbench
Multiple Assignment of Assortments to
Sites/New Store Openings
LO-MD-RA-ASL Assortment List
POS Outbound Reports for Assortment
Lists
Assortment List
New Change Pointers for Condition
Records (WIND)
LO-MD-BP Business
Partners
Customer-Specific Fields in Business
Partner Master Data (New)
LO-MD-BP-CM Customer Master
Customer, Vendor, and Material Master
Data (Changed)
LO-MD-BP-VM Vendor Master
Customer, Vendor, and Material Master
Data (Changed)
Calculating Planned Delivery Time
LO-MD-SN Serial Numbers
Registration and archival of configured
serial numbers (new)
Synchronization of construction type and
material number (new)
200
203
210
210
212
214
216
216
217
217
219
219
______________________________________________________________
SAP AG
xix
SAP
System
Table of Contents
SAP AG
______________________________________________________________
11.5.8.3
11.5.8.4
11.5.9
11.5.9.1
11.5.9.2
11.5.9.3
11.5.10
11.5.10.1
11.5.10.2
11.5.10.2.1
11.5.11
11.5.11.1
11.5.11.2
11.5.12
11.5.12.1
11.5.12.2
11.6
11.6.1
11.6.2
11.6.3
11.6.3.1
11.6.4
11.6.4.1
11.6.5
11.6.5.1
11.6.6
11.6.6.1
11.7
11.7.1
Synchronization of equipment number and
serial number (new)
Functions in the serial number history
(enhanced)
LO-MD-RPC Retail Pricing
Business Add-Ins in Retail Pricing
General Parameters for Retail Pricing
New Change Pointers for Condition
Records (WIND)
LO-MD-SE Season
Markdown Planning
LO-MD-SE-MDF Markdown
Planning
Markdown Planning
LO-MD-PR Promotion
Promotion Discounts
Promotion: Minor Enhancements
LO-MD-QO Quantity
optimizing
Parallel Processing
New Change Pointers for Condition
Records (WIND)
LO-BM Batches
Original Batches (New)
Structure Changes in Batch Management
LO-BM-BC Batch
Specification
Batch Class Conversion
LO-BM-WUL Batch Where-Used
List
Batch Where-Used List in Repetitive
Manufacturing
LO-BM-BIC Batch
Information Cockpit
Further Development of the Batch
Information Cockpit
LO-BM-DRV Derivation
Batch Derivation
LO-VC Variant
Configuration
LO-VC-CHR Characteristic
220
220
223
225
229
230
232
233
233
233
233
235
______________________________________________________________
xx
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
11.7.1.1
11.8
11.8.1
11.9
11.9.1
11.9.1.1
11.9.1.2
11.9.2
11.9.2.1
11.9.3
11.9.3.1
11.9.3.2
11.10
11.10.1
11.10.2
11.10.3
11.10.4
11.10.5
11.10.6
11.10.7
11.10.8
11.10.9
11.11
11.11.1
11.11.2
11.11.3
11.11.4
11.11.5
11.11.6
Value Assignment / Interface Design
Distribution of Interface Designs (New)
LO-ECH Engineering
Change Management
21 CFR Part 11 Enhancement on Electronic
Records (New)
LO-MDS Merchandise
Distribution
LO-MDS-AL Allocation
Allocation Tables for Customers
New Allocation Strategies Based on SAP
BW
LO-MDS-CPO Collective
Purchase Order
Collective Purchase Order: Improved
Throughput and Parallel Processing
LO-MDS-DPR Distribution
Processing
Distribution monitor: Restriction to
adjustment-relevant items
Automatic Delivery Generation After
Manual Adjustment
LO-SRS SAP Retail Store
Cash Control
Expense Invoice
Physical Inventory in SAP Retail Store
Sales Order in SAP Retail Store
Mass Maintenance of Master Data
PDC Link in SAP Retail Store
Store Groups/New Store Openings
SAP Retail Store
LO-MAP Merchandise and
Assortment Planning
MAP: Methods for Linking Planning Steps
- Aggregation and
MAP: Assortment Planning
MAP: Attributes
MAP: Data targets for the BW Interface
MAP: Calculation Sequence in Formula
Groups
MAP: New authorization object W_WXP_HIER
235
236
236
237
238
239
239
241
241
241
251
251
253
______________________________________________________________
SAP AG
xxi
SAP
System
Table of Contents
SAP AG
______________________________________________________________
11.11.7
11.11.8
11.11.9
11.11.10
11.11.11
11.12
11.12.1
11.12.2
11.12.3
11.12.4
11.12.5
11.12.6
11.12.7
11.12.7.1
11.13
11.13.1
11.13.1.1
11.13.1.2
11.13.1.3
11.13.2
11.13.2.1
11.13.2.2
11.13.3
11.13.3.1
11.13.4
11.13.4.1
11.13.4.2
11.13.4.3
11.14
11.14.1
MAP: New Authorization Object W_WXP_LAY
MAP: Blocking Data Cells and Changing
Row Totals in Manual Planning
MAP: Generic read module
MAP: Material Planning and
Characteristics Planning
MAP: Simplification of the Transport of
Planning Scenarios and Layouts
LO-AB Agency Business
(Global Trade)
Updating of Business Volume in Customer
Settlements
Customer Settlement
Expense Settlement
Interface to SAP Business Information
Warehouse
Item Category in Agency Documents
LO-AB-RS Remuneration
settlement
Remuneration List Enhancement
LO-GT Global Trade
LO-GT-TC Trading Contract
Open order/Open delivery
Profit Simulation
Trading Contract (TC)
LO-GT-TE Expenses
New Screen for Trading Expenses
Trading Expenses
LO-GT-TEW Trading
Execution Workbench
Trading Execution Workbench (TEW)
LO-GT-PM Position
Management
Association Management
Portfolio Management
Position Management
LO-HU Handling Unit
Management
Business Add-Ins for Handling Unit
Management (New)
254
255
256
256
256
259
259
264
265
267
267
______________________________________________________________
xxii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
12
12.1
12.2
12.3
12.4
12.5
12.6
12.6.1
12.6.1.1
12.6.1.2
12.7
12.7.1
12.7.1.1
12.7.2
12.7.2.1
12.8
12.8.1
12.8.2
12.8.2.1
12.8.2.2
12.9
12.9.1
12.9.1.1
12.9.1.1.1
12.9.1.1.2
12.9.1.1.3
SD Sales and
Distribution
Country Version India in Standard R/3
System
Condition-Based Tax Calculation (New)
Changes to Structures for Country
Version India
Exports Under Excise Regulations (New)
Release Notes from Country Version India
Add-On (SD)
SD-MD Master Data
SD-MD-CM Conditions
Deleting Bonus Buys
New Change Pointers for Condition
Records (WIND)
SD-BF Basic Functions
SD-BF-PR Pricing and
Conditions
Condition-Based Excise Determination in
SD (New)
SD-BF-TX Taxes
Condition-Based Excise Determination in
SD (New)
SD-SLS Sales
Evaluation of open sales documents
according to US-GAAP guideline SFAS
SD-SLS-SO Sales Orders
Purchase Requisitions Generated from
Sales Orders Update FM (Changed)
SD Order Update in Funds Management (FM)
(Changed)
SD-BIL Billing
SD-BIL-IV Processing
Billing Documents
SD-BIL-IV-SM Expense-Related
Billing
Resource-Related Billing for Internal
Orders With Revenues (new)
Archiving CO Line Items (Enhanced)
Document Flow Evaluations of
269
269
271
272
274
276
276
277
277
278
278
279
279
279
______________________________________________________________
SAP AG
xxiii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
12.9.1.1.4
12.9.1.1.5
12.9.1.1.6
12.9.1.1.7
12.10
12.10.1
12.10.2
12.11
12.11.1
12.11.1.1
12.11.1.2
13
13.1
13.2
13.3
13.4
13.5
13.6
13.6.1
13.6.1.1
13.6.1.2
13.7
13.7.1
Resource-Related Billing (New)
DI Processor (Enhanced)
Billing Requests for Sales Order Items
(Enhanced)
Collective Processing for
Resource-Related Billing (Enhanced)
Static Processing of Resource-Related
Billing (Deleted)
SD-EDI Electronic Data
Interchange
BAdIs in the Price Catalog
Support for Scales in the Price Catalog
SD-POS POS Interface
SD-POS-OUT POS Interface Outbound
New Change Pointers for Condition
Records (WIND)
New Functions in POS Interface Outbound
MM Materials
Management
Country Version India in Standard R/3
System
Condition-Based Tax Calculation (New)
Changes to Structures for Country
Version India
Release Notes from Country Version India
Add-On (MM)
MM: Overview of Changes to SAP R/3
Enterprise Core 4.70
MM-CBP
Consumption-Based Planning (See Also PP-MR
MM-CBP-CBP
Consumption-Based Planning (See Also PP-MR
Alternative Historical Data/Post
Distribution Forecasting
Multi-Step Replenishment
MM-PUR Purchasing
Accessibility Barriers Removed:
Purchasing Lists Converted to ALV Grid
280
281
281
282
282
286
286
289
289
291
291
293
294
294
294
297
______________________________________________________________
xxiv
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
13.7.2
13.7.3
13.7.4
13.7.5
13.7.6
13.7.7
13.7.7.1
13.7.7.2
13.7.7.3
13.7.7.4
13.7.7.5
13.7.7.6
13.7.7.6.1
13.7.7.7
13.7.7.7.1
13.7.7.7.2
13.7.7.8
13.7.7.8.1
13.7.8
13.7.8.1
13.7.8.2
13.7.8.2.1
13.7.8.2.2
13.7.8.2.3
13.7.8.3
Business Add-Ins in Purchasing (New)
Matchcodes Superseded by Search Helps in
Purchasing
Continuation of Conventional Purchase
Order and Requisition
Reports for Inclusion of Derivative
Financial Instruments in Balance
Perishables Processing
MM-PUR-GF Basic Functions
New Change Documents in Purchasing (New)
Version Management in Purchasing (New)
Changeability of Configuration
Controllable in Purchasing
Display of Commitments in External
Purchasing Documents and Purchase
Commitment in Stock Transfer Documents
(New)
MM-PUR-GF-TAX Taxes
Condition-Based Excise Determination in
MM (New)
MM-PUR-GF-REL Release
(Approval)
Release Transactions in New Interactive
Design
New Workflows for Refusal to Release
(Rejection) (New)
MM-PUR-GF-OC Message
Determination
Reminder Level as Selection Criterion
for Reminders and Expediters
MM-PUR-VM Vendor-Material
Relationships and Conditions
Calculating Planned Delivery Time
MM-PUR-VM-SET Subsequent
Settlement
Updating of Business Volume in Customer
Settlements
Discontinued Functions in Subsequent
Settlement
Reorganization of Information Structures
for Business Volume and Incom
MM-PUR-VM-CON Conditions
299
300
301
303
304
304
305
306
306
307
307
307
307
308
308
309
310
______________________________________________________________
SAP AG
xxv
SAP
System
Table of Contents
SAP AG
______________________________________________________________
13.7.8.3.1
13.7.9
13.7.9.1
13.7.9.1.1
13.7.10
13.7.10.1
13.7.10.2
13.7.10.3
13.7.10.4
13.7.10.5
13.7.10.6
13.7.11
13.7.11.1
13.7.11.2
13.7.11.3
13.7.11.4
13.7.11.5
13.7.11.6
13.7.11.7
13.7.11.8
13.7.11.9
Copying Rules for Conditions in
Purchasing (New)
MM-PUR-OA Vendor Outline
Agreements
MM-PUR-OA-SCH Scheduling
Agreement
New Change Pointers for Condition
Records (WIND)
MM-PUR-REQ Purchase
Requisitions
PBET: Version Posting Date Derivation
(Changed)
Purchase Requisitions Generated from
Sales Orders Update FM (Changed)
Stock Transfer Orders Can Update Funds
Management Commitment
Continuation of Conventional Purchase
Order and Requisition
Enjoy Purchase Requisition - Assign and
Process (Changed)
Automatic Generation of Purchase Orders
from Requisitions in New
MM-PUR-PO Purchase Orders
PBET: Version Posting Date Derivation
(Changed)
Stock Transfer Orders Can Update Funds
Management Commitment
Release of Enjoy BAPIs: BAPI_PO_CREATE1
and BAPI_PO_CHANGE (New)
Consignment Also Possible on
Cross-Company-Code Basis (New)
Different Delivery Types in a Single
Stock Transfer Document (New)
Continuation of Conventional Purchase
Order and Requisition
Automatic Generation of Purchase Orders
from Requisitions in New
Supplementation of Personal Settings in
Enjoy Purchase Order
Underdelivery Tolerance in the Case of
Stock Transport Orders (New)
310
311
311
311
312
312
313
313
314
314
315
315
316
316
317
317
318
318
319
319
______________________________________________________________
xxvi
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
13.7.11.10
13.7.11.11
13.7.11.12
13.7.11.13
13.7.11.14
13.8
13.8.1
13.8.1.1
13.9
13.9.1
13.9.2
13.9.3
13.9.3.1
13.9.3.2
13.9.4
13.9.4.1
13.9.4.2
13.9.4.3
13.9.4.4
13.9.4.5
13.9.5
13.9.5.1
13.9.5.2
13.9.5.3
Create a Subcontract Order with Batch
Number (New)
Improved Performance with Investment
Buying
Calculating Planned Delivery Time
Order Cancelation
Progress Tracking (New)
MM-SRV External
Services
MM-SRV-SR Service Entry
Returns for Service Entry Sheets from
Time-Sheets (New)
MM-IM Inventory
Management
Goods Movements and Excise Documents
Combined (New)
MM-IM: Overview of Release Infos for SAP
R/3 Enterprise Core 470
MM-IM-GF Basic Functions
Business Add-Ins in Inventory Management
(new)
Output Determination: Program for
Creating Condition Records (New)
MM-IM-GR Goods Receipt
Functional Supplement for BAPI
CreateFromData (Changed)
Create a Subcontract Order with Batch
Number (New)
Functional Enhancements in MIGO
(Changed)
Replacing the MB* Transactions with
Transaction MIGO (New)
SAP Smart Forms in Inventory Management
(new)
MM-IM-GI Goods Issue and
Return Delivery
Functional Supplement for BAPI
CreateFromData (Changed)
Functional Enhancements in MIGO
(Changed)
Replacing the MB* Transactions with
Transaction MIGO (New)
320
321
324
324
324
324
325
326
326
327
327
328
329
329
330
330
331
332
______________________________________________________________
SAP AG
xxvii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
13.9.6
13.9.6.1
13.9.6.2
13.9.6.3
13.9.6.4
13.9.6.5
13.9.6.6
13.9.6.7
13.9.6.8
13.9.6.9
13.9.7
13.9.7.1
13.9.7.2
13.10
13.10.1
13.10.1.1
13.10.2
13.10.2.1
13.10.2.2
13.10.2.3
13.10.2.3.1
13.10.2.3.2
MM-IM-ST Stock
Transfer/Transfer Posting
Stock Transfer Orders Can Update Funds
Management Commitment
Consignment Also Possible on
Cross-Company-Code Basis (New)
Different Delivery Types in a Single
Stock Transfer Document (New)
Commitment in Stock Transfer Documents
(New)
Underdelivery Tolerance in the Case of
Stock Transport Orders (New)
Functional Supplement for BAPI
CreateFromData (Changed)
Create a Subcontract Order with Batch
Number (New)
Functional Enhancements in MIGO
(Changed)
Replacing the MB* Transactions with
Transaction MIGO (New)
MM-IM-VP Balance Sheet
Valuation Procedures
Structure Changes in Inflation
Accounting
Enhancements in Balance Sheet Valuation
MM-IV Invoice
Verification
MM-IV-GF General
Functions
CENVAT Credit on Capital Goods after
Budget 2000 (Changed)
MM-IV-LIV Logistics
Invoice Verification
Overview of Developments in Logistics
Invoice Verification
All Functions in Logistics Invoice
Verification
MM-IV-LIV-CRE Entry
Automatic Quantity and Amount
Distribution for Multiple Account
Enhancements to BAPIs in Logistics
332
332
333
333
334
334
335
335
336
337
338
338
340
340
340
340
340
342
342
______________________________________________________________
xxviii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
13.10.2.3.3
13.10.2.3.4
13.10.2.4
13.10.2.4.1
13.10.2.4.2
13.10.3
13.10.3.1
13.11
13.11.1
13.11.1.1
14
14.1
14.1.1
14.2
14.2.1
14.2.1.1
14.2.1.2
14.2.2
14.2.2.1
14.2.2.2
14.3
14.3.1
14.3.2
Invoice Verification
Displaying MM and FI Document Numbers
Clearing the GR/IR Clearing Account for
External Service Purchase
MM-IV-LIV-IVB Invoice
Verification in Background
Enhancements to the Invoice Overview
Verifying Freight Invoices in the
Background
MM-IV-INT Interfaces
Business Add-Ins in Logistics Invoice
Verification
MM-EDI Electronic Data
Interchange
MM-EDI-IV Invoice
Verification
EDI: Posting to Material and G/L
Accounts Using Customer Exit
LE Logistics
Execution
LE-MOB Mobile Data
Entry
Business Add-Ins for Logistics
Execution (new)
LE-IDW Decentralized
WMS Integration
LE-IDW-CEN Central
Processing
Subsequent Changes to the Delivery (New)
Delayed Distribution of Inbound and
Outbound Deliveries to the
LE-IDW-DEC Local Operations
Several ERP systems to one decentralized
WMS
Subsequent Changes to the Delivery (New)
LE-WM Warehouse
Management
Business Add-Ins for Logistics
Execution (new)
Structure changes in the Logistics
343
344
345
346
346
347
347
347
348
348
348
349
349
351
352
356
356
______________________________________________________________
SAP AG
xxix
SAP
System
Table of Contents
SAP AG
______________________________________________________________
14.3.3
14.3.4
14.3.4.1
14.3.4.2
14.3.4.3
14.3.5
14.3.5.1
14.3.6
14.3.6.1
14.3.7
14.3.7.1
14.3.7.2
14.3.8
14.3.8.1
14.4
14.4.1
14.5
14.5.1
14.5.2
14.5.2.1
14.5.2.2
14.5.2.3
14.5.3
14.5.3.1
Execution IMG
Delayed update of outbound delivery
(new)
LE-WM-TFM Stock Movements
Business Add-Ins for Logistics
Execution (new)
Transfer order for multiple outbound
deliveries (new)
Delayed update of outbound delivery
(new)
LE-WM-BIN Inventory at the
Storage Bin Level
Business Add-Ins for Logistics
Execution (new)
LE-WM-STU Storage Unit
Management
Stock overview for SU-managed bulk
storage (changed)
LE-WM-IFC Interfaces
Links between IDoc and business object
(new)
Task and Resource Management (LE-TRM)
LE-WM-GF Other Functions
Delayed update of outbound delivery
(new)
LE-TRM Task & Resource
Management
Task and Resource Management (LE-TRM)
LE-SHP Shipping
Structure changes in the Logistics
Execution IMG
LE-SHP-DL Delivery
Processing
Business Add-Ins for Logistics
Execution (new)
Conversion of Matchcode Objects in
Delivery Processing
Partial Goods Receipt for Inbound
Delivery (New)
LE-SHP-GI Goods Issue
Business Add-Ins for Logistics
357
357
358
359
360
361
361
362
362
362
365
365
367
367
367
369
370
______________________________________________________________
XXX
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
14.6
14.6.1
14.6.1.1
14.6.1.2
15
15.1
15.2
15.2.1
15.2.1.1
15.2.1.2
15.2.2
15.2.2.1
15.2.2.2
15.2.2.3
15.2.2.4
16
16.1
16.2
16.3
16.4
16.4.1
16.4.2
16.4.2.1
Execution (new)
LE-TRA Transportation
LE-TRA-FC Freight
Processing
Business Add-Ins for Logistics
Execution (new)
Direct Navigation from the Shipment Cost
Document to the Reference
PLM Product
Lifecycle Management
Accessibility
PLM-PPM Product and
Process Modeling
PLM-PPM-PDN Product Designer
Product Designer
Accessibility: Web User Interface of the
Product Designer
PLM-PPM-RPL Product Data
Replication
Structural Changes in PLM-LDM
Business
Add-Ins (BAdIs) in PLM PDR
Product Data Replication (Changed)
Product Data Distribution
QM Quality
Management
New Developments for SAP R/3 Enterprise
PLM Extension 1.10 (EA_APPL
New Business Add-Ins
New Developments for SAP R/3
Enterprise Core 4.70 (SAP_APPL 470
QM-IM Quality
Inspection
Flexible Inspection Specifications
QM-IM-RR Results
Recording
QM-IM-RR-CHR Characteristic
Results
370
372
372
373
374
374
375
375
376
377
377
379
379
382
382
______________________________________________________________
SAP AG
XXXi
SAP
System
Table of Contents
SAP AG
______________________________________________________________
16.4.2.1.1
16.5
16.5.1
16.5.1.1
16.6
16.6.1
17
17.1
17.2
17.3
17.4
17.5
17.6
17.7
17.7.1
17.7.2
17.7.3
17.7.4
17.7.5
17.7.6
17.7.7
17.7.8
17.7.9
17.7.9.1
17.7.9.2
Input Processing
QM-QN Quality
Notifications
QM-QN-NT Creating Quality
Notifications
New Developments in Notifications:
Several Customer Subscreens Possibl
QM-ST Stability
Studies
Stability Study
PM Plant
Maintenance
Structure changes in Plant Maintenance
and Customer Service (changed)
Structure changes in Plant Maintenance
and Customer Service (changed)
Connection of partner to central address
management (new)
Business Package for Assets (new)
Project-oriented maintenance (new)
Mobile scenarios for Plant Maintenance
and Customer Service (new)
PM-EQM Technical
Objects
Displaying lower-level objects as
symbols (changed)
BAPIs for technical objects (new)
Display of indirectly assigned BOMs
(changed)
Material search using classes (new)
Material where-used-list (new)
Multiplying out quantities in structural
displays (new)
Search for technical objects (new)
New archival objects (new)
PM-EQM-EQ Equipment
Installation and removal with
simultaneous goods movement
Consupmtion control for vehicles (new)
383
383
383
384
388
388
388
389
390
390
390
391
392
393
______________________________________________________________
XXXii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
17.7.9.3
17.7.9.4
17.7.9.5
17.7.9.6
17.7.10
17.7.10.1
17.7.11
17.7.11.1
17.7.11.1.1
17.7.11.1.2
17.7.11.1.3
17.7.11.1.4
17.8
17.8.1
17.8.2
17.8.2.1
17.8.2.2
17.8.2.3
17.8.2.4
17.8.2.5
17.9
17.9.1
17.9.2
17.9.3
Registration and archival of configured
serial numbers (new)
Search for replacement
equipment/-components (new)
Synchronization of construction type and
material number (new)
Synchronization of equipment number and
serial number (new)
PM-EQM-BM Bills of
Material (Plant Maintenance)
Display of indirectly assigned BOMs
(changed)
PM-EQM-SF Additional
Functions
PM-EQM-SF-MPC Measuring Points
and Counters
Consupmtion control for vehicles (new)
Measurement value graphic (changed)
Generation of interval documents (new)
Update of vehicles' consumption data
(new)
PM-PRM Preventive
Maintenance
Worklist for notifications (enhanced)
PM-PRM-MP Maintenance
Plans
Generation of interval documents (new)
Separate completion of maintenance call
dates (new)
Change document for preventive
maintenance (new)
Change status of task lists and
scheduling (changed)
Scheduling log for maintenance plans
(changed)
PM-WOC Maintenance
Processing
Worklist for notifications (enhanced)
Change header notification in order
(new)
Copy notification long text into order
(new)
394
395
395
395
396
396
396
396
398
398
400
400
401
401
402
403
404
404
______________________________________________________________
SAP AG
XXXiii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
17.9.4
17.9.5
17.9.6
17.9.7
17.9.8
17.9.8.1
17.9.8.2
17.9.8.3
17.9.9
17.9.9.1
17.9.9.2
17.9.9.3
17.9.9.4
17.9.9.5
17.9.9.6
17.9.10
17.9.10.1
17.10
17.10.1
17.10.2
17.10.3
17.10.4
17.11
Separate completion of maintenance call
dates (new)
Document flow (changed)
Assigning a task list to a notification
(enhanced)
Assigning and displaying operations in
the object list (new)
PM-WOC-MN Maintenance
Notifications
BAPIs for maintenance- and service
notifications (new)
Search for replacement
equipment/-components (new)
New Developments in Notifications:
Several Customer Subscreens Possibl
PM-WOC-MO Maintenance
Orders
BAPIs for maintenance- and service
orders (new)
Material where-used-list (new)
Search for replacement
equipment/-components (new)
Sales order or project stock in
maintenance- and service orders (new)
Purchase Order Handling Using an
External Procurement System (New)
OCI Interface (New)
PM-WOC-JC Completion
Confirmations
BAPIs for confirmations (new)
PM-WCM Work Clearance
Management
Valuation of applications (new)
Optimization for construction of a
library of work clearance documents
Integration with graphic WCM planning
(new)
Improved support of revision planning
(new)
PM-IS Information
System
404
406
406
406
406
408
408
409
409
410
410
411
411
412
413
413
414
414
______________________________________________________________
XXXiv
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
17.11.1
18
18.1
18.2
18.3
18.4
18.5
18.6
18.6.1
18.6.2
18.6.3
18.6.4
18.6.5
18.6.6
18.6.7
18.7
18.7.1
18.7.2
18.7.3
18.7.3.1
18.7.3.2
18.7.3.3
18.8
18.8.1
18.8.2
18.8.2.1
Update of vehicles' consumption data
(new)
CS Customer Service
Structure changes in Plant Maintenance
and Customer Service (changed)
Structure changes in Plant Maintenance
and Customer Service (changed)
Connection of partner to central address
management (new)
Business Package for Assets (new)
Mobile scenarios for Plant Maintenance
and Customer Service (new)
CS-BD Basic Data
Displaying lower-level objects as
symbols (changed)
Display of indirectly assigned BOMs
(changed)
Material search using classes (new)
Material where-used-list (new)
Multiplying out quantities in structural
displays (new)
Search for technical objects (new)
Search for replacement
equipment/-components (new)
CS-IB Installed Base
Management
Consupmtion control for vehicles (new)
New archival objects (new)
CS-IB-MC Measuring Points
and Counters
Measurement value graphic (changed)
Generation of interval documents (new)
Update of vehicles' consumption data
(new)
CS-AG Service
Agreements
Change document for preventive
maintenance (new)
CS-AG-QU Quotations
DI Processor (Enhanced)
414
415
415
416
416
417
417
418
419
419
420
421
422
422
______________________________________________________________
SAP AG
XXXv
SAP
System
Table of Contents
SAP AG
______________________________________________________________
18.8.3
18.8.3.1
18.8.3.2
18.8.3.3
18.8.3.4
18.8.3.5
18.9
18.9.1
18.9.1.1
18.10
18.10.1
18.10.2
18.10.3
18.10.4
18.10.5
18.10.6
18.10.7
18.10.8
18.10.9
18.10.10
18.10.11
18.10.12
18.10.13
18.10.14
CS-AG-SC Service
Contracts
Generation of interval documents (new)
Worklist for notifications (enhanced)
Separate completion of maintenance call
dates (new)
Change status of task lists and
scheduling (changed)
Scheduling log for maintenance plans
(changed)
CS-CM Call Management
CS-CM-SN Service
Notifications
BAPIs for maintenance- and service
notifications (new)
CS-SE Service
Processing
BAPIs for maintenance- and service
orders (new)
Conversion for accounting indicator
(changed)
Material where-used-list (new)
Search for replacement
equipment/-components (new)
Worklist for notifications (enhanced)
Change header notification in order
(new)
Copy notification long text into order
(new)
Separate completion of maintenance call
dates (new)
Document flow (changed)
Assigning a task list to a notification
(enhanced)
Assigning and displaying operations in
the object list (new)
Sales order or project stock in
maintenance- and service orders (new)
Purchase Order Handling Using an
External Procurement System (New)
OCI Interface (New)
423
425
426
427
427
427
429
429
429
430
431
432
432
433
433
434
434
______________________________________________________________
XXXvi
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
18.10.15
18.10.15.1
18.10.16
18.10.16.1
18.11
18.11.1
18.11.1.1
18.11.1.2
18.11.1.3
18.11.1.4
18.11.1.5
18.11.1.6
18.11.2
18.11.2.1
18.12
18.12.1
19
19.1
19.1.1
19.1.2
19.2
19.2.1
19.2.2
19.2.3
19.2.4
CS-SE-SD Scheduling and
Planning
OCI Interface (New)
CS-SE-CON Confirmations
BAPIs for confirmations (new)
CS-BS Billing and
Settlement
CS-BS-BI Billing
Archiving CO Line Items (Enhanced)
Document Flow Evaluations of
Resource-Related Billing (New)
DI Processor (Enhanced)
Billing Requests for Sales Order Items
(Enhanced)
Collective Processing for
Resource-Related Billing (Enhanced)
Static Processing of Resource-Related
Billing (Deleted)
CS-BS-RR Deferred Revenue
Results Analysis Using Dynamic Items
(Enhanced)
CS-IS Information
System
Update of vehicles' consumption data
(new)
PP Production
Planning and Control
PP-MRP Material
Requirements Planning
Business Add-Ins in MRP
Usability improvements in MRP
PP-SFC Production
Orders
Business Add-Ins for Production Orders
and Process Orders
Preconfigure Batch Split for Production
Order (new)
Changes to Production and Process Orders
Confirmation: Termination if Incorrect
Actual Costs/Goods Movements
435
436
437
438
438
438
439
439
439
441
441
444
444
445
447
______________________________________________________________
SAP AG
XXXvii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
19.2.5
19.2.5.1
19.3
19.3.1
19.3.2
19.4
19.4.1
19.4.2
19.4.2.1
19.4.3
19.4.3.1
19.4.3.2
19.4.3.3
19.4.4
19.4.4.1
19.4.4.2
19.4.4.3
19.4.4.4
19.4.4.5
19.4.4.6
19.4.4.7
19.4.4.7.1
19.4.4.7.2
19.4.4.8
19.4.4.8.1
PP-SFC-IS Information
System
DRB (Enhanced)
PP-REM Repetitive
Manufacturing
Business Add-Ins in Repetitive
Manufacturing (REM)
Usability Improvements in Repetitive
Manufacturing (REM)
PP-PI Production
Planning for Process Industries
Changes to the IMG Structure for
Production Planning - Process
PP-PI-MD Basic Data
Linking DMS Documents to Production
Versions (New)
PP-PI-POR Process Order
Business Add-Ins for Production Orders
and Process Orders
Changes to Production and Process Orders
Confirmation: Termination if Incorrect
Actual Costs/Goods Movements
PP-PI-PMA Process
Management
Introduction to Decentralized Process
Management
Data Exchange Between Applications in
the SAP R/3 System (New)
- Service MDA
- Services PSH and PMC
- Services ODA and OAE
- Service SYS
PP-PI-PMA-MSG Process Message
New Message Destination for Sending
Alerts
New Transaction for Automatic Process
Message Creation (New)
PP-PI-PMA-PMC Browser-Based PI
Sheet / Cockpit
User Change in PI Sheets and Cockpits
(New)
447
448
448
449
450
450
452
452
454
455
455
457
470
471
472
472
______________________________________________________________
XXXviii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
19.4.4.8.2
19.4.4.8.3
19.4.4.8.4
19.4.4.8.5
19.4.4.8.6
19.4.4.8.7
19.4.4.8.8
19.4.4.9
19.4.4.9.1
20
20.1
20.2
20.3
20.3.1
20.3.2
20.3.2.1
20.3.2.2
20.3.2.3
20.3.2.3.1
20.3.2.4
20.3.2.4.1
20.3.3
20.3.3.1
20.3.3.2
Asynchronous Signature Process for
Process Steps in the PI Sheet
New Functions in the PI Sheet Context
Menu (Enhanced)
Automatic Execution of Functions in PI
Sheets and Manufacturing
Using Global Variables in PI Sheets and
Manufacturing Cockpits
Automatic Execution of Calculations and
Dynamic Function Calls (New)
Determining Control Recipe Numbers (New)
Intergrating DMS Documents to the PI
Sheet (New)
PP-PI-PMA-OPC OPC Interface
Introduction of SAP OPC Data Access (SAP
ODA) (New)
PS Project System
Structure Changes in the Project System
IMG (EA-APPL 110)
Structure Changes in the Project System
IMG (SAP_APPL 470)
PS-ST Structures
WBS Element Groups (New)
PS-ST-OPR Operative
Structures
User Status in the SAP Project System
(New)
Creating Projects with Templates (New)
PS-ST-OPR-WBS Work Breakdown
Structure
BAdI for Field Transfer From WBS Element
to Asset (New)
PS-ST-OPR-NET Network and
Activity
Network Activity Authorization Checks
(Changed)
PS-ST-INT Interface to
External Project Software
BAPIs in the Project System (Enhanced)
BAPIs in the Project System (New)
473
474
476
481
484
487
488
491
491
493
493
495
495
495
495
495
______________________________________________________________
SAP AG
XXXix
SAP
System
Table of Contents
SAP AG
______________________________________________________________
20.4
20.4.1
20.4.2
20.5
20.5.1
20.5.1.1
20.5.1.1.1
20.5.1.2
20.5.1.2.1
20.5.2
20.5.2.1
20.5.3
20.5.3.1
20.5.3.1.1
20.5.3.2
20.5.3.2.1
20.6
20.6.1
20.6.2
20.6.3
20.6.3.1
20.6.4
20.6.4.1
20.6.4.2
20.6.4.3
20.6.4.4
20.6.5
20.6.5.1
PS-CLM Claim Management
Cost Integration for Claims (New)
New Developments in Notifications:
Several Customer Subscreens Possibl
PS-COS Costs
PS-COS-PLN Planned Costs
PS-COS-PLN-PLN Planning
Planning and Budgeting in Any Currency
(new)
PS-COS-PLN-CAL Costing
Integrated Planning for Networks (New)
PS-COS-BUD Budget
Availability Control in Object Currency
(new)
PS-COS-PER Automatic and
Periodic Allocations
PS-COS-PER-IC Interest
Interest Calculation for Special Periods
(Changed)
PS-COS-PER-SE Settlement
BAdI for Generating Settlement Rules
(New)
PS-REV Revenues and
Earnings
DI Processor (Enhanced)
Copying the Status of Order Items (New)
PS-REV-PLN Planned Revenues
Creating a Quotation from the Project
Builder (New)
PS-REV-ACT Actual Revenues
and Forecast
Archiving CO Line Items (Enhanced)
Document Flow Evaluations of
Resource-Related Billing (New)
Collective Processing for
Resource-Related Billing (Enhanced)
Static Processing of Resource-Related
Billing (Deleted)
PS-REV-RA Results Analysis
Results Analysis Using Dynamic Items
(Enhanced)
498
498
502
502
503
503
504
505
505
506
506
507
507
______________________________________________________________
xl
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
20.7
20.7.1
20.7.2
20.7.3
20.7.3.1
20.7.4
20.7.4.1
20.7.5
20.7.5.1
20.8
20.8.1
20.8.1.1
20.9
20.9.1
20.9.1.1
20.9.2
20.9.2.1
20.9.2.1.1
21
21.1
21.2
21.3
21.4
21.4.1
21.4.2
21.4.2.1
PS-MAT Material
Purchase Order Handling Using an
External Procurement System (New)
OCI Interface (New)
PS-MAT-INT Bill of Material
Transfer
Requirements Dates in Bill of Material
Transfer (Enhanced)
PS-MAT-PRC Procurement
OCI Interface (New)
PS-MAT-PRO Project-Oriented
Procurement
ProMan - Project-Oriented Procurement
(New)
PS-PRG Progress
PS-PRG-TRC Progress
Tracking
Progress Tracking (New)
PS-IS Information
System
PS-IS-REP Project Reports
Project Information System (Changed)
PS-IS-CON Responsibility
Accounting
PS-IS-CON-SUM Project
Summarization
Dynamic Selection for Summarization
Characteristics (Enhanced)
EHS Environment,
Health and Safety
Basic Data and Hazardous Substance
Management (New)
EH&S Native Language Support (Enhanced)
Integration in PLM Extension 1.10 (New)
EHS-SAF Product Safety
IMG Structure Changes in Product Safety
(Changed)
EHS-SAF-SPE Specification
Management
Specification Management (Enhanced)
507
508
508
509
509
510
511
512
512
512
514
514
516
516
______________________________________________________________
SAP AG
xli
SAP
System
Table of Contents
SAP AG
______________________________________________________________
21.4.2.2
21.4.3
21.4.3.1
21.4.3.2
21.4.3.3
21.4.4
21.4.4.1
21.4.4.2
21.4.4.3
21.4.4.4
21.4.4.5
21.5
21.5.1
21.5.2
21.5.2.1
21.6
21.6.1
21.6.2
21.6.2.1
21.6.2.2
21.7
21.7.1
21.7.2
21.7.3
21.7.3.1
21.7.4
21.7.4.1
21.7.4.2
Assignment of Specifications and
Materials (Enhanced)
EHS-SAF-RGE Report
Generation
Report Generation (Enhanced)
WWI Installation (Enhanced)
WWI Functions (New)
EHS-SAF-INT Interfaces
Interface to SAP Unicode Systems
(Changed)
ALE for EH&S Reports (Enhanced)
Bill of Material Transfer (Enhanced)
Import of Vendor MSDS (New)
Data Import (Enhanced)
EHS-DGP Dangerous Goods
Management
IMG Structure Changes in Dangerous Goods
Management (Changed)
EHS-DGP-TP Template and
One-Time Material Processing
Template and One-Time Material
Processing (New)
EHS-HEA Occupational
Health
Case History (Enhanced)
EHS-HEA-IIL Injury/Illness
Log
Integration of Incident/Accident Log and
Health Center Services (New)
Setting the Time Zone (New)
EHS-IHS Industrial
Hygiene and Safety
Setting the Time Zone (New)
IMG Structure Changes in Industrial
Hygiene and Safety (Changed)
EHS-IHS-WA Work Area
Management
Work Area Hierarchy (Enhanced)
EHS-IHS-RSK Risk Assessment
Risk Assessment (Enhanced)
Analysis Method Summated Rating (New)
517
517
521
523
523
524
524
524
524
524
525
526
527
______________________________________________________________
xlii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
21.7.4.3
21.7.5
21.7.5.1
21.7.5.2
21.7.5.3
21.7.5.4
21.7.5.5
22
22.1
22.2
22.3
22.4
22.5
22.6
22.7
22.8
22.8.1
22.8.2
22.9
22.9.1
22.9.2
22.9.3
22.9.4
Customer-Specific Analysis Methods
(Enhanced)
EHS-IHS-IA
Incident/Accident Management
Incident/Accident Management (Enhanced)
Sending Accident Messages (New)
Menu Exits for Incident/Accident
Management (New)
Integration of Incident/Accident Log and
Health Center Services (New)
User-Defined Texts and Documents for
Incident/Accident Log Entries
PA Personnel
Management
Structure changes in SAP Reference IMG
HR: Structural changes in the SAP
Reference IMG for SAP R/3 Enterprise
HR: Structure changes in the SAP
Reference Implementation Guide (IMG)
Changes to the SAP Reference IMG in
Release 4.0A
HR: Changes to the SAP Reference IMG for
Release 4.0B
HR: Changes to the SAP Reference IMG in
Release 4.5A
HRDSYS table conversion for
documentation maintenance
PA-RC Recruitment
Web Application Employment
Opportunities: Changing Application Data
Storage of Applicant Documents Using
Generic Object Services (Changed)
PA-PA Personnel
Administration
Pay Scale Reclassification (Changed)
Context Authorization Check for HR
Master Data
Number of Wage Types in the Basic Pay
Infotype (0008) (changed)
PA-PA-AU Australia
528
529
530
530
531
533
533
538
539
544
545
549
550
551
551
552
553
______________________________________________________________
SAP AG
xliii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
22.9.4.1
22.9.4.1.1
22.9.5
22.9.5.1
22.9.5.1.1
22.9.6
22.9.6.1
22.9.6.1.1
22.9.7
22.9.7.1
22.9.7.1.1
22.9.8
22.9.8.1
22.9.9
22.9.9.1
22.9.9.1.1
22.9.9.2
22.9.9.2.1
22.10
22.10.1
22.10.2
22.10.3
22.10.3.1
22.10.3.1.1
22.10.4
22.10.4.1
22.10.4.2
22.10.4.2.1
22.11
22.11.1
PA-PA-AU-PY Payroll Data
Stand-alone Salary Packaging Structure
Removed
PA-PA-FR France
PA-PA-FR-PD Personal Data
Finding out the work contract type
PA-PA-GB Great Britain
PA-PA-GB-PY Payroll Data
Company Car - Change of Taxation Base to
CO2 Emissions
PA-PA-SG Singapore
PA-PA-SG-PD Personal Data
Changes in Employee Residence Status and
Work Permit
PA-PA-US USA
Recruitment Integration U.S.
PA-PA-ZA South Africa
PA-PA-ZA-PY Payroll Data
Medical Aid Conversion Program - Upgrade
from 4.0B /4.5A (RPU46AW0)
PA-PA-ZA-SP Salary Modelling
Stand-alone Salary Packaging Structure
Removed
PA-BN Benefits
Eligibility for Dependents and
Beneficiaries (Enhanced)
Domestic Partners as Dependents and
Beneficiaries (New)
PA-BN-PL Plans
PA-BN-PL-HL Health Plan
Dependent Coverage Options for Health
Plans (Enhanced)
PA-BN-CO COBRA
COBRA Administration (Enhanced)
PA-BN-CO-IN Initial
Notification
Dependent Coverage Options for Health
Plans (Enhanced)
PA-PF Pension Schemes
PA-PF-CH Pension fund:
Switzerland
554
556
558
560
561
561
563
564
566
566
567
______________________________________________________________
xliv
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
22.11.1.1
22.11.1.2
22.11.2
22.11.2.1
22.11.3
22.11.3.1
22.12
22.12.1
22.12.2
22.13
22.13.1
22.13.1.1
22.14
22.14.1
22.14.2
22.14.2.1
22.15
22.15.1
22.15.2
22.15.2.1
22.15.2.1.1
22.15.2.1.2
22.16
22.16.1
22.17
Changes to PF Model Funds
Functional Changes to the SAP HR Pension
Fund (SAP_HR 470)
PA-PF-NL Pension fund
Netherlands
Functional Changes to the SAP HR Pension
Fund (SAP_HR 470)
PA-PF-XX Pension fund:
Switzerland
Functional Changes to the SAP HR Pension
Fund (SAP_HR 470)
PA-IS HR Information
Systems
New logical database in HR: PNPCE (HR
Master Data/incl. CE)
New Query Generator for HR
PA-PD Personnel
Development
PA-PD-PM Objective
Setting and Appraisals
Objective Setting and Appraisals (New)
PA-OS Organizational
Structure
BAdI: Return Validity Period of Persons
to Organizational Management
PA-OS-BS Bases
Context Authorization Check for HR
Master Data
PA-CM Compensation
Management
Pay Scale Reclassification (Changed)
PA-CM-AD Administration
PA-CM-AD-CS Long-Term
Incentives
Management of Awards (Enhanced)
Deleting Records of Infotype 0382
(Changed)
PA-CP Personnel Cost
Planning and Simulation
Personnel Cost Planning and Simulation
(New)
PA-GE Management of
568
569
569
569
570
570
571
573
573
575
575
576
576
578
581
581
581
______________________________________________________________
SAP AG
xlv
SAP
System
Table of Contents
SAP AG
______________________________________________________________
22.17.1
22.18
22.18.1
22.18.2
22.19
22.19.1
22.20
22.20.1
23
23.1
23.2
23.3
23.4
23.5
23.6
23.7
23.8
23.9
23.10
23.10.1
23.10.2
23.10.3
Global Employees
Management of Global Employees
PA-CE Concurrent
Employment
Concurrent Employment (new)
PA-ES Employee
Self-Service
Customizing for the Leave Request ESS
Application (Enhanced)
PA-XF Expert Finder
Expert Finder (New)
PT Personnel Time
Management
Structure changes in SAP Reference IMG
HR: Structural changes in the SAP
Reference IMG for SAP R/3 Enterprise
PT: Structural Changes to the SAP
Reference IMG in SAP R/3 Enterprise
HR: Structure changes in the SAP
Reference Implementation Guide (IMG)
Changes to the SAP Reference IMG in
Release 4.0A
HR: Changes to the SAP Reference IMG for
Release 4.0B
HR: Changes to the SAP Reference IMG in
Release 4.5A
PT: Structure Changes in Reference IMG
for SAP R/3 Enterprise HR Ext.
HRDSYS table conversion for
documentation maintenance
PT-RC Time Data
Recording and Administration
Time Manager's Workplace Now in HR
Extension (Changed)
BAdIs for Time Data Recording and
Administration (New)
Calendar Views in the Time Manager's
Workplace (New)
583
584
585
585
587
587
592
592
594
599
600
604
605
605
605
606
606
______________________________________________________________
xlvi
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
23.10.4
23.10.5
23.10.6
23.10.7
23.10.8
23.10.8.1
23.10.8.2
23.10.8.3
23.10.8.4
23.10.9
23.10.9.1
23.10.10
23.10.10.1
23.11
23.11.1
24
24.1
24.2
24.3
24.4
24.5
24.6
24.7
Enhancements in the Time Manager's
Workplace Navigation Calendar (New)
Enhancements to the Time Manager's
Workplace (New)
Additional Fields for Account Assignment
Information in the TMW (New)
Conversion of Technical Tables for the
TMW (Changed)
PT-RC-AA
Attendances/Absences
RPTENT00: Time Recording for Multiple
Persons and Infotypes (Obsolete)
Conversion to Hide Unused Columns
(Changed)
Customizing for the Leave Request ESS
Application (Enhanced)
US: Management of Family and Medical
Leave
PT-RC-IW Time Tickets
Conversion to Hide Unused Columns
(Changed)
PT-RC-QT Quotas
Enhancements to Absence Quotas (New)
PT-IN Integration with
Other Applications
Account Assignment Dimensions for Fund
Accounting (New)
PY Payroll
Structure changes in SAP Reference IMG
HR: Structural changes in the SAP
Reference IMG for SAP R/3 Enterprise
HR: Structure changes in the SAP
Reference Implementation Guide (IMG)
Changes to the SAP Reference IMG in
Release 4.0A
HR: Changes to the SAP Reference IMG for
Release 4.0B
Transfer External Wage Component to
Payroll (new)
HRDSYS table conversion for
607
608
609
610
611
611
611
611
612
613
614
614
617
622
623
628
629
______________________________________________________________
SAP AG
xlvii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.8
24.9
24.10
24.11
24.11.1
24.11.2
24.11.3
24.11.4
24.11.4.1
24.11.4.1.1
24.11.4.1.2
24.11.4.1.3
24.11.4.1.4
24.11.4.1.5
24.11.4.1.6
24.12
24.12.1
24.12.2
24.12.3
24.12.4
24.12.5
24.12.5.1
documentation maintenance
Variables in the payroll programs
(changed)
Function XEDT (deleted)
Operation MESSG deleted and replaced
with operation XMES (new)
PY-AR Argentina
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-AR-FP Subsequent
Activities
PY-AR-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-AT Austria
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-AT-FP Subsequent
Activities
PY-AT-FP-DT Data Transfer to
Other Applications
630
630
632
632
636
638
639
639
639
639
640
641
642
644
644
648
650
650
650
______________________________________________________________
xlviii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.12.5.1.1
24.12.5.1.2
24.12.5.1.3
24.12.5.1.4
24.12.5.1.5
24.12.5.1.6
24.13
24.13.1
24.13.2
24.13.3
24.13.4
24.13.4.1
24.13.4.1.1
24.13.4.1.2
24.13.4.2
24.13.4.2.1
24.13.4.2.2
24.13.4.2.3
24.13.4.2.4
24.13.4.2.5
24.13.4.2.6
24.14
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-AU Australia
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-AU-FP Subsequent
Activities
PY-AU-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-AU-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-BE Belgium
651
651
652
653
653
656
656
660
662
662
662
662
663
663
663
664
665
666
666
668
______________________________________________________________
SAP AG
xlix
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.14.1
24.14.2
24.14.3
24.14.4
24.14.4.1
24.14.4.1.1
24.14.5
24.14.5.1
24.14.5.1.1
24.14.5.1.2
24.14.5.2
24.14.5.2.1
24.14.5.2.2
24.14.5.2.3
24.14.5.2.4
24.14.5.2.5
24.14.5.2.6
24.15
24.15.1
24.15.2
24.15.3
24.15.4
24.15.4.1
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-BE-NT Net
PY-BE-NT-NI Social Insurance
Multiple corrective declaration (new)
PY-BE-FP Subsequent
Activities
PY-BE-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-BE-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-BR Brazil
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-BR-FP Subsequent
Activities
PY-BR-FP-DT Data Transfer to
669
673
674
676
676
676
676
677
677
678
679
679
680
682
682
686
688
689
______________________________________________________________
l
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.15.4.1.1
24.15.4.1.2
24.15.4.1.3
24.15.4.1.4
24.15.4.1.5
24.15.4.1.6
24.16
24.16.1
24.16.2
24.16.3
24.16.4
24.16.5
24.16.5.1
24.16.5.1.1
24.16.5.1.2
24.16.5.1.3
24.16.5.1.4
24.16.6
24.16.6.1
24.16.6.1.1
24.16.6.1.2
24.16.6.1.3
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-CA Canada
HR: Changes to the SAP Reference IMG in
Release 4.5A
Deleted and Discontinued Reports for
Payroll Canada in R/3 Enterprise
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-CA-NT Net
PY-CA-NT-TX Tax
Revised Canadian Business Number
Configuration in R/3 Enterprise
Mandatory Payroll Canada Conversion
Reports for R/3 Enterprise Upgrade
Deleted, Discontinued and New Functions
for Payroll Canada in R/3
Revised Canadian Tax Infotype Framework
in R/3 Enterprise
PY-CA-FP Subsequent
Activities
PY-CA-FP-DM Data Medium
Exchange
Preliminary DME Program for Separate
Payment Run (Canada)
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
689
689
689
690
691
692
694
694
698
699
700
701
703
705
706
708
708
708
709
709
______________________________________________________________
SAP AG
li
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.16.6.2
24.16.6.2.1
24.16.6.2.2
24.16.6.3
24.16.6.3.1
24.16.6.3.2
24.16.6.3.3
24.16.6.3.4
24.16.6.3.5
24.16.7
24.16.7.1
24.16.7.2
24.17
24.17.1
24.17.2
24.17.3
24.17.4
24.17.4.1
24.17.4.1.1
24.17.5
24.17.5.1
24.17.5.1.1
24.17.5.1.2
PY-CA-FP-RS Remuneration
Statement
Supply remuneration statement only via
Internet
Supply Remuneration Statement in
Internet as PDF
PY-CA-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
PY-CA-RP Reporting
Revised Assignment of BPS Data to
Business Numbers in R/3 Enterprise
Revised Assignment of Reduced EI Rates
to Business Numbers in R/3
PY-CH Switzerland
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-CH-NT Net
PY-CH-NT-TX Tax
Enhancements to Withholding Tax
Calculations
PY-CH-FP Subsequent
Activities
PY-CH-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
710
710
711
711
711
712
713
714
714
716
717
719
723
724
725
726
726
726
______________________________________________________________
lii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.17.5.2
24.17.5.2.1
24.17.5.2.2
24.17.5.2.3
24.17.5.2.4
24.17.5.2.5
24.17.5.2.6
24.18
24.18.1
24.18.1.1
24.18.1.2
24.18.1.3
24.18.1.4
24.18.1.5
24.18.1.6
24.19
24.19.1
24.19.2
24.19.3
24.19.4
24.19.5
24.19.5.1
24.19.5.1.1
for Remuneration Payments
PY-CH-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-CN China
PY-CN-FP Final Payroll
Processing
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-DE Germany
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-DE-NT Net
PY-DE-NT-BS Bases
Payroll for Awards in Compensation
Management (new)
726
727
727
727
728
729
729
731
732
732
733
734
734
735
737
737
741
743
744
______________________________________________________________
SAP AG
liii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.19.5.2
24.19.5.2.1
24.19.5.3
24.19.5.3.1
24.19.5.3.2
24.19.5.4
24.19.5.4.1
24.19.6
24.19.6.1
24.19.6.1.1
24.19.6.1.2
24.19.6.2
24.19.6.2.1
24.19.6.2.2
24.19.6.3
24.19.6.3.1
24.19.6.3.2
24.19.6.3.3
24.19.6.3.4
24.19.6.3.5
24.19.6.3.6
24.19.7
24.19.7.1
24.19.7.1.1
PY-DE-NT-SI SI - Additional
Insurance
745
PY-DE-NT-CI Company
Insurance /Retirement Pension Plan
745
PY-DE-NT-GR
Garnishment/Cession
745
PY-DE-FP Subsequent
Activities
PY-DE-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-DE-FP-RS Remuneration
Statement
Supply remuneration statement only via
Internet
Supply Remuneration Statement in
Internet as PDF
PY-DE-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-DE-RP Reporting
PY-DE-RP-ST Statements
745
745
745
745
746
746
747
747
748
748
749
750
750
752
______________________________________________________________
liv
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.19.8
24.19.8.1
24.19.8.2
24.19.9
24.19.9.1
24.20
24.20.1
24.20.2
24.20.2.1
24.20.2.1.1
24.20.2.1.2
24.20.2.1.3
24.20.2.1.4
24.20.2.1.5
24.20.2.1.6
24.21
24.21.1
24.21.2
24.21.2.1
24.21.2.1.1
24.21.2.1.2
24.21.2.2
24.21.2.2.1
24.21.2.2.2
PY-DE-PS Public Sector
PY-DE-BA Business to
Administration
PY-DK Denmark
HR: Changes to the SAP Reference IMG in
Release 4.5A
PY-DK-FP Subsequent
Activities
PY-DK-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-ES Spain
HR: Changes to the SAP Reference IMG in
Release 4.5A
PY-ES-FP Subsequent
Activities
PY-ES-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-ES-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
753
753
757
757
757
758
759
760
760
762
763
767
767
767
767
768
768
768
______________________________________________________________
SAP AG
lv
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.21.2.2.3
24.21.2.2.4
24.21.2.2.5
24.21.2.2.6
24.22
24.22.1
24.22.2
24.22.2.1
24.22.2.1.1
24.22.2.1.2
24.22.2.2
24.22.2.2.1
24.22.2.2.2
24.22.2.2.3
24.22.2.2.4
24.22.2.2.5
24.22.2.2.6
24.22.3
24.22.3.1
24.23
24.23.1
24.23.2
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-FR France
HR: Changes to the SAP Reference IMG in
Release 4.5A
PY-FR-FP Subsequent
Activities
PY-FR-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-FR-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-FR-IE Interface to
External Payroll Systems
Enhancements on ADP/SAP Payroll
Interface : Version 2.1
PY-GB United Kingdom
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Connecting a
770
770
771
773
773
777
777
777
778
778
778
779
780
781
781
783
784
784
789
______________________________________________________________
lvi
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.23.3
24.23.3.1
24.23.3.1.1
24.23.3.1.2
24.23.3.2
24.23.3.2.1
24.23.3.2.2
24.23.3.3
24.23.3.3.1
24.23.3.3.2
24.23.3.3.3
24.23.3.3.4
24.23.3.3.5
24.23.3.3.6
24.23.4
24.23.4.1
24.23.4.1.1
24.24
24.24.1
24.24.2
24.24.3
24.24.3.1
Server Group to a Process Step
PY-GB-FP Subsequent
Activities
PY-GB-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-GB-FP-RS Remuneration
Statement
Supply remuneration statement only via
Internet
Supply Remuneration Statement in
Internet as PDF
PY-GB-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-GB-RP Reporting
PY-GB-RP-SR Statutory
Reporting
New End-of-Year Processing
PY-HK Hong Kong
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-HK-FP Subsequent
Activities
PY-HK-FP-DM Data Medium
Exchange
793
794
794
794
794
795
795
796
796
796
797
798
799
799
801
802
803
807
807
807
______________________________________________________________
SAP AG
lvii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.24.3.1.1
24.24.3.1.2
24.24.3.2
24.24.3.2.1
24.24.3.2.2
24.24.3.2.3
24.24.3.2.4
24.24.3.2.5
24.24.3.2.6
24.25
24.25.1
24.25.2
24.25.3
24.25.4
24.25.4.1
24.25.4.1.1
24.25.4.1.2
24.25.4.1.3
24.25.4.1.4
24.25.4.1.5
24.26
24.26.1
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-HK-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-ID Indonesia
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-ID-FP Subsequent
Activities
PY-ID-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
PY-IE Ireland
HR: Changes to the SAP Reference IMG in
807
808
808
808
809
810
811
811
813
814
818
819
820
820
820
821
822
822
823
______________________________________________________________
lviii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.26.2
24.26.3
24.26.3.1
24.26.3.1.1
24.26.3.2
24.26.3.2.1
24.26.3.2.2
24.26.3.3
24.26.3.3.1
24.26.3.3.2
24.26.3.3.3
24.26.3.3.4
24.26.3.3.5
24.26.3.3.6
24.27
24.27.1
24.27.2
24.27.3
24.27.4
24.27.4.1
24.27.4.1.1
Release 4.5A
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-IE-FP Subsequent
Activities
PY-IE-FP-DM Data Medium
Exchange
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-IE-FP-RS Remuneration
Statement
Supply remuneration statement only via
Internet
Supply Remuneration Statement in
Internet as PDF
PY-IE-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-IN India
Summary of Rel. Notes originally from
WSD (Add HR SP 2 - 17)
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-IN-FP Subsequent
Activities
PY-IN-FP-DT Data Tranfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
825
829
830
830
830
830
830
832
832
832
833
834
834
835
837
837
862
863
864
864
864
______________________________________________________________
SAP AG
lix
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.27.4.1.2
24.27.4.1.3
24.27.4.1.4
24.27.4.1.5
24.27.4.1.6
24.28
24.28.1
24.28.2
24.28.2.1
24.28.2.1.1
24.28.2.1.2
24.28.2.2
24.28.2.2.1
24.28.2.2.2
24.28.2.2.3
24.28.2.2.4
24.28.2.2.5
24.28.2.2.6
24.29
24.29.1
24.29.2
24.29.3
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-IT Italy
HR: Changes to the SAP Reference IMG in
Release 4.5A
PY-IT-FP Subsequent
Activities
PY-IT-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-IT-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-JP Japan
HR: Changes to the SAP Reference IMG in
Release 4.5A
Misc. Enhancements in the Enterprise
Release for Payroll Japan
HR Process Workbench: Connecting a
865
866
866
867
869
870
874
874
874
874
875
875
875
876
877
877
880
880
884
______________________________________________________________
lx
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.29.4
24.29.4.1
24.29.4.1.1
24.29.5
24.29.5.1
24.29.5.1.1
24.29.5.1.1.1
24.29.6
24.29.6.1
24.29.6.2
24.29.6.2.1
24.29.6.3
24.29.6.3.1
24.29.6.3.2
24.29.6.3.3
24.29.6.3.4
24.29.6.3.5
24.29.6.3.6
24.29.6.3.7
24.29.7
24.29.7.1
24.29.7.1.1
24.29.7.1.1.1
24.30
Server Group to a Process Step
PY-JP-GR Gross
PY-JP-GR-LR
Leaving/Retirement
Retirement Allowance Enhancements in the
Enterprise Release for Payrol
PY-JP-NT Net
PY-JP-NT-MP Monthly Payroll
PY-JP-NT-MP-NI Social Insurance
Social Insurance Enhancements in the
Enterprise Release for Payroll
PY-JP-FP Subsequent
Activities
Supply Remuneration Statement in
Internet as PDF
PY-JP-FP-RS Remuneration
Statement
Supply remuneration statement only via
Internet
PY-JP-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-JP-RP Reporting
PY-JP-RP-ST Statements
PY-JP-RP-ST-SI Social Insurance
Statements
Social Insurance Enhancements in the
Enterprise Release for Payroll
PY-KR South Korea
885
886
886
887
888
888
889
889
890
890
891
892
892
893
893
895
896
896
______________________________________________________________
SAP AG
lxi
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.30.1
24.30.1.1
24.30.1.2
24.30.1.3
24.30.1.4
24.30.1.5
24.30.1.6
24.30.1.7
24.31
24.31.1
24.31.2
24.31.3
24.31.4
24.31.4.1
24.31.4.1.1
24.31.4.1.2
24.31.4.2
24.31.4.2.1
24.31.4.2.2
24.31.4.2.3
24.31.4.2.4
PY-KR-FP Final Payroll
Processing
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-MX Mexico
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-MX-FP Subsequent
Activities
PY-MX-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-MX-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
897
897
898
899
899
900
900
902
903
907
908
909
909
909
909
910
910
911
912
912
______________________________________________________________
lxii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.31.4.2.5
24.31.4.2.6
24.31.4.2.7
24.32
24.32.1
24.32.2
24.32.3
24.32.4
24.32.4.1
24.32.4.1.1
24.32.5
24.32.5.1
24.32.5.1.1
24.32.5.1.2
24.32.5.1.3
24.32.5.1.4
24.32.5.1.5
24.32.5.1.6
24.33
24.33.1
24.33.2
24.33.3
24.33.4
24.33.4.1
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-MY Malaysia
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-MY-NT Net
PY-MY-NT-TX Tax
Normal Payments through Offcycle Run
PY-MY-FP Subsequent
Activities
PY-MY-FP-DT Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
PY-NL The Netherlands
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-NL-FP Subsequent
Activities
PY-NL-FP-DM Data Medium
913
913
915
916
920
921
923
923
923
923
924
925
925
926
928
932
934
934
______________________________________________________________
SAP AG
lxiii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.33.4.1.1
24.33.4.1.2
24.33.4.2
24.33.4.2.1
24.33.4.2.2
24.33.4.2.3
24.33.4.2.4
24.33.4.2.5
24.33.4.2.6
24.33.4.2.7
24.34
24.34.1
24.34.2
24.34.3
24.34.4
24.34.4.1
24.34.4.1.1
24.34.4.1.2
24.34.4.1.3
24.34.4.1.4
24.34.4.1.5
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-NL-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-NO Norway
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-NO-FP Subsequent
Activities
PY-NO-FP-DT Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
934
934
935
935
935
936
937
938
938
939
941
941
945
947
947
947
947
948
949
950
______________________________________________________________
lxiv
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.34.4.1.6
24.34.4.1.7
24.35
24.35.1
24.35.2
24.35.3
24.35.4
24.35.4.1
24.35.4.1.1
24.35.4.1.2
24.35.4.2
24.35.4.2.1
24.35.4.2.2
24.35.4.2.3
24.35.4.2.4
24.35.4.2.5
24.35.4.2.6
24.35.4.2.7
24.36
24.36.1
24.36.2
24.36.3
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-NZ New Zealand
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-NZ-FP Subsequent
Activities
PY-NZ-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-NZ-FP-DT Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-PH Philippines
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
950
951
953
953
957
959
959
959
959
960
960
960
961
962
963
963
964
966
966
970
______________________________________________________________
SAP AG
lxv
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.36.4
24.36.4.1
24.36.4.1.1
24.36.4.1.2
24.36.4.1.3
24.36.4.1.4
24.36.4.1.5
24.36.4.1.6
24.36.4.1.7
24.37
24.37.1
24.37.2
24.37.2.1
24.37.2.1.1
24.37.2.1.2
24.37.2.2
24.37.2.2.1
24.37.2.2.2
24.37.2.2.3
24.37.2.2.4
24.37.2.2.5
Server Group to a Process Step
PY-PH-FP Subsequent
Activities
PY-PH-FP-DE Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-PT Portugal
HR: Changes to the SAP Reference IMG in
Release 4.5A
PY-PT-FP Subsequent
Activities
PY-PT-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-PT-FP-DE Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
972
972
972
972
973
974
975
975
976
978
978
982
982
982
983
983
983
984
985
985
______________________________________________________________
lxvi
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.37.2.2.6
24.37.2.2.7
24.38
24.38.1
24.38.2
24.38.2.1
24.38.2.1.1
24.38.2.1.2
24.38.2.2
24.38.2.2.1
24.38.2.2.2
24.38.2.2.3
24.38.2.2.4
24.38.2.2.5
24.38.2.2.6
24.38.2.2.7
24.39
24.39.1
24.39.2
24.39.3
24.39.4
24.39.4.1
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-SE Sweden
HR: Changes to the SAP Reference IMG in
Release 4.5A
PY-SE-FP Subsequent
Activities
PY-SE-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-SE-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-SG Singapore
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-SG-GR Gross
PY-SG-GR-WV Wage Type
Valuation
986
986
988
989
993
993
993
993
994
994
995
996
996
997
997
999
1000
1004
1005
1006
______________________________________________________________
SAP AG
lxvii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.39.4.1.1
24.39.4.1.1.1
24.39.5
24.39.5.1
24.39.5.1.1
24.39.5.1.2
24.39.5.1.3
24.39.5.1.4
24.39.5.1.5
24.39.5.1.6
24.39.5.1.7
24.40
24.40.1
24.40.2
24.40.3
24.40.3.1
24.40.3.1.1
24.40.3.1.2
24.40.3.1.3
24.40.3.1.4
24.40.3.1.5
24.40.3.1.6
PY-SG-GR-WV-AB Absences
Third Child Maternity Leave
PY-SG-FP Subsequent
Activities
PY-SG-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-TW Taiwan
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-TW-FP Subsequent
Activities
PY-TW-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
1007
1007
1008
1008
1009
1010
1010
1011
1013
1013
1017
1018
1018
1018
1019
1020
1020
1021
1021
______________________________________________________________
lxviii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.40.3.1.7
24.41
24.41.1
24.41.2
24.41.3
24.41.4
24.41.4.1
24.41.4.1.1
24.41.4.1.2
24.41.4.1.3
24.41.4.1.4
24.41.4.1.5
24.41.4.1.6
24.42
24.42.1
24.42.2
24.42.3
24.42.4
24.42.4.1
24.42.4.1.1
24.42.5
24.42.5.1
24.42.5.1.1
24.42.6
Conversion of umlauts with preliminary
DME program (deleted)
PY-TH Thailand
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-TH-FP Subsequent
Activities
PY-TH-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
PY-US USA
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-US-GR Gross
PY-US-GR-PT Integration with
Time Management
US: Management of Family and Medical
Leave
PY-US-NT Net
PY-US-NT-TX Tax
Withholding Federal or State Income
Taxes at a Flat Rate
PY-US-DD Deductions /
1023
1024
1028
1029
1030
1030
1030
1031
1032
1032
1033
1033
1035
1039
1041
1042
1042
1043
______________________________________________________________
SAP AG
lxix
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.42.6.1
24.42.7
24.42.7.1
24.42.7.1.1
24.42.7.1.2
24.42.7.2
24.42.7.2.1
24.42.7.2.2
24.42.7.3
24.42.7.3.1
24.42.7.3.2
24.42.7.3.3
24.42.7.3.4
24.42.7.3.5
24.42.7.3.6
24.42.8
24.42.8.1
24.42.8.1.1
24.42.8.1.2
24.42.9
24.42.9.1
24.43
Calculating the Remittance Amount
New Processing Class for Deductions with
Balance/Totals Functionality
PY-US-FP Subsequent
Activities
PY-US-FP-DM Data Medium
Exchange
Payment Document Validation for
Remuneration Payment (new)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
PY-US-FP-RS Remuneration
Statement
Supply remuneration statement only via
Internet
Supply Remuneration Statement in
Internet as PDF
PY-US-FP-DT Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
PY-US-RP Reporting
PY-US-RP-TR Tax Reporter
U.S. Tax Reporter Program Deletions
Deletion of Previous Tax Reporter
Transactions
PY-US-IE Interface to
External Payroll Systems
End of Support for ADP DOS Interface for
U.S. Payroll Outsourcing
PY-VE Venezuela
1044
1044
1045
1045
1045
1045
1046
1046
1047
1047
1047
1048
1049
1050
1050
1051
1054
1054
1054
______________________________________________________________
lxx
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.43.1
24.43.2
24.43.3
24.43.4
24.43.4.1
24.43.4.1.1
24.43.4.1.2
24.43.4.1.3
24.43.4.1.4
24.43.4.1.5
24.43.4.1.6
24.43.4.1.7
24.44
24.44.1
24.44.2
24.44.2.1
24.44.2.1.1
24.44.3
24.44.3.1
24.44.3.2
24.44.3.2.1
24.44.3.2.2
24.44.3.3
HR: Changes to the SAP Reference IMG in
Release 4.5A
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-VE-FP Subsequent
Activities
PY-VE-FP-DE Data Transfer to
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-ZA South Africa
HR: Changes to the SAP Reference IMG in
Release 4.5A
PY-ZA-NT Net
PY-ZA-NT-TX Employment Tax
Calculation of Deemed Remuneration in
the Current Tax Year
PY-ZA-FP Subsequent
Activities
Payment Document Validation for
Remuneration Payment (new)
PY-ZA-FP-RS Remuneration
Statement
Supply remuneration statement only via
Internet
Supply Remuneration Statement in
Internet as PDF
PY-ZA-FP-DT Data Transfer to
1055
1059
1061
1061
1061
1061
1062
1063
1064
1064
1065
1067
1067
1071
1072
1072
1072
1073
1074
______________________________________________________________
SAP AG
lxxi
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.44.3.3.1
24.44.3.3.2
24.44.3.3.3
24.44.3.3.4
24.44.3.3.5
24.44.3.3.6
24.44.3.3.7
24.44.3.3.8
24.44.4
24.44.4.1
24.44.4.1.1
24.45
24.45.1
24.45.1.1
24.45.1.2
24.45.1.3
24.45.2
24.45.2.1
24.45.2.2
24.45.3
24.45.3.1
24.45.3.2
24.45.3.3
24.45.4
Other Applications
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Using the Payment Medium Workbench (PMW)
for Remuneration Payments
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PY-ZA-RP Reporting
PY-ZA-RP-I5 IRP5 Tax Return
SARS - Foreign Income Declaration
PY-XX Payroll: General
Parts
PY-XX-TL Tools
Wage Type Configuration Tool
HR Process Workbench: Starting Processes
With Event Dependency (New)
HR Process Workbench: Connecting a
Server Group to a Process Step
PY-XX-BS Bases
Absence Valuation: Refinement of
Partial-Day Absences
Payroll for Awards in Compensation
Management (new)
PY-XX-FO Forms
Creating Forms With the HR Forms
Workplace (New)
Supply remuneration statement only via
Internet
Supply Remuneration Statement in
Internet as PDF
PY-XX-DT Data Transfer
1074
1074
1075
1076
1076
1077
1077
1078
1080
1081
1082
1084
1084
1086
1086
1087
1088
______________________________________________________________
lxxii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
24.45.4.1
24.45.4.2
24.45.4.3
24.45.4.4
24.45.4.5
24.45.4.6
24.45.4.7
25
25.1
25.2
25.3
25.4
25.5
25.6
25.7
25.7.1
25.7.1.1
25.7.1.2
25.8
25.8.1
Controlling Posting of Payroll Results
to Accounting (changed)
Posting Characteristics of Wage Types
(changed)
Document Split for Posting Payroll
Results to Accounting (enhanced)
Payment Document Validation for
Remuneration Payment (new)
Log for Preliminary DME Program
(Extended)
Account Assignment Object for Funds
Management and Grants Management
Conversion of umlauts with preliminary
DME program (deleted)
PE Training and
Event Management
Structure changes in SAP Reference IMG
HR: Structural changes in the SAP
Reference IMG for SAP R/3 Enterprise
HR: Structure changes in the SAP
Reference Implementation Guide (IMG)
Changes to the SAP Reference IMG in
Release 4.0A
HR: Changes to the SAP Reference IMG for
Release 4.0B
HR: Changes to the SAP Reference IMG in
Release 4.5A
PE-IN Integration
PE-IN-CB Billing and
Activity Allocation
New Functions in Billing and Activity
Allocation of Training and Event
Own Field and Conversion for Attendee
Numbers in Table T77REFDOC
PE-DA Day-to-Day
Activities
New Business Add-In for Additional
Checks When Booking Attendees
1089
1089
1091
1091
1091
1092
1094
1096
1096
1101
1102
1107
1108
1112
1112
1113
1114
1114
______________________________________________________________
SAP AG
lxxiii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
26
26.1
26.1.1
26.1.1.1
26.1.1.2
26.1.2
26.1.2.1
26.1.2.2
26.1.2.3
26.1.2.4
26.1.2.5
26.1.2.6
26.1.2.7
26.1.2.8
26.1.2.9
26.1.2.10
26.1.2.11
26.1.2.12
26.1.2.13
26.1.2.14
26.1.2.15
26.1.2.16
26.1.2.17
26.1.2.18
26.2
26.2.1
26.2.1.1
26.3
26.3.1
26.3.2
BC Basis Components
BC-BMT Business
Management
BC-BMT-OM Organizational
Management
Filtering HR Master Data Generically
(New)
Serialize HR Master Data (New)
BC-BMT-WFM SAP Business
Workflow
WebFlow function (extended)
Interface for the import and export of
workflow definitions (new)
Asynchronous agent specification (new)
Support of WSDL Web services (new)
Freely definable attributes for work
items (new)
Graphical workflow log (extended)
Binding editor (extended)
Binding in the workflow system (changed)
Conditions for work item execution
(extended)
Work queues (changed)
Programming exits for work items (new)
Agent determination (extended)
Workflow Builder (extended)
Workflow system background job (changed)
Delete workflows (changed)
WAPI Interface (extended)
Define workflow on an ad hoc basis
(deleted)
SAPforms plug-in (changed)
BC-CST Client/Server
Technology
BC-CST-IC Internet
Communication Manager
SAP Web Dispatcher (New)
BC-MAS mySAP.com
Application Server
BSP Extensions (New)
Integrating the SAP J2EE Application
1115
1115
1115
1116
1116
1117
1119
1121
1122
1122
1122
______________________________________________________________
lxxiv
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
26.3.3
26.3.4
26.4
26.4.1
26.5
26.5.1
26.5.2
26.5.2.1
26.5.3
26.5.3.1
26.5.3.1.1
26.6
26.6.1
26.6.1.1
26.6.1.2
26.6.1.3
26.6.2
26.6.2.1
26.6.2.2
26.6.2.2.1
26.6.3
26.6.3.1
26.6.4
26.6.4.1
26.6.4.2
26.6.5
26.6.5.1
Server into SAP Web AS
Enhancing Security Aspects with BSP
Applications (Changed)
Model View Controller (New)
BC-MID Middleware
Legacy System Migration Workbench
BC-SEC Security
Simplified Security Administration Using
the Trust Manager (enhanced)
BC-SEC-DIR Directory
Directory integration and user data
synchronization (new)
BC-SEC-USR User and
Authorization Management
BC-SEC-USR-ADM User and
Authorization Management
Global User Manager (Deleted)
BC-SRV Basis Services /
Communication Interfaces
BC-SRV-ADR Address
Management
Address-independent communication data
Attributes "Gender" and "Group
indicator" for forms of address
International address versions for
private addresses and contact perso
BC-SRV-ARL SAP ArchiveLink
Document Finder (enhanced)
BC-SRV-ARL-VIE SAP ArchiveLink
Viewer
Document Viewer (enhanced)
BC-SRV-BSF Business Service
Functions
Exchange rate maintenance (enhanced)
BC-SRV-COM E-mail, Fax, and
Telephony Interfaces
HTTP Node for SMS/Pager Messages in
SAPconnect (new)
SMTP for Fax and SMS/Pager Messages in
SAPconnect (new)
BC-SRV-EDI IDoc interface
Structure Change in "SAP Web Application
1123
1123
1125
1126
1127
1127
1128
1128
1128
1129
1130
1131
1131
1132
1132
______________________________________________________________
SAP AG
lxxv
SAP
System
Table of Contents
SAP AG
______________________________________________________________
26.6.6
26.6.6.1
26.6.6.1.1
26.6.6.2
26.6.6.2.1
26.6.7
26.6.7.1
26.6.7.1.1
26.6.8
26.6.8.1
26.6.9
26.6.9.1
26.6.10
26.6.10.1
26.6.10.2
26.7
26.7.1
26.7.1.1
26.7.1.2
27
Server"
BC-SRV-GBT Generic Business
Tools
BC-SRV-GBT-ALM Alert Framework
Alert Management (new)
BC-SRV-GBT-PPF Post Processing
Framework
Post Processing Framework (PPF)
Configuration (Enhanced)
BC-SRV-KPR SAP Knowledge
Provider
BC-SRV-KPR-CMS Content
Management Service
Client-Specific Customizing for HTTP
Repositories
BC-SRV-QUE SAP Query
InfoSet Query / SAP Query / Quick Viewer
BC-SRV-SRM SAP Records
Management
BC-SRV-SSF SAP Smart Forms
SAP Smart Forms: Classic Form Printing
SAP Smart Forms: Web Forms
BC-UPG Upgrade General
BC-UPG-OCS Online
Correction Support (Support Packages)
SAP Add-On Installation Tool (SAINT)
(Extended)
Support Package Manager (SPAM)
(Extended)
27.2
ICM Incentives and
Commission Management
Programs that start automatically or are
started manually for the
Commissions System
28
CFM Corporate
27.1
1132
1133
1133
1134
1134
1134
1134
1136
1137
1137
1137
1138
1139
1139
______________________________________________________________
lxxvi
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
28.1
28.2
28.3
28.4
28.4.1
28.4.1.1
28.5
28.5.1
28.5.2
28.5.3
28.5.4
28.5.5
28.5.5.1
28.5.5.2
28.5.5.3
28.5.6
28.5.6.1
28.5.6.2
28.5.6.3
28.5.6.4
28.5.7
28.5.7.1
28.5.7.2
28.6
28.6.1
28.6.2
28.6.3
Finance Management
SAP R/3 Enterprise Financial Services
1.10 (New)
1140
1140
CFM-BF Basic Functions
CFM-BF-BP Business Partner
New functions for the SAP Business
Partner for Financial Services
CFM-TM Transaction
Manager
Linking products
Revenue classification
1142
1146
Automatic creation
Key Date Valuation Enhancements
CFM-TM-TR Transaction
Management
Compound Swap and EONIA Swap
Deleting old transactions and old coding
Early Repayment
CFM-TM-AC Transfer to
Financial Accounting
Statistical reporting according to AWV
(Z1 and Z4)
Posting Interface for the Parallel
Valuation Areas (Enhanced)
Linking other transactions to parallel
position management
CFM-TM-IS Information
System
New features in CFM reporting
Customer Drilldown Reporting
Enhancements (Modificat.-Free)
CFM-PA Portfolio
Analyzer
Reorganization of Single Records in the
Area Menu (Changed)
Activate the Analysis Structure after
Release Upgrade
Inclusive Indicator in the Calculation
of Accrued Interest (Enhanced)
1149
1151
1151
1151
1153
1153
1153
1156
1156
1156
1156
______________________________________________________________
SAP AG
lxxvii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
28.7
28.7.1
28.7.2
28.7.3
28.7.4
28.7.5
28.7.5.1
28.7.6
28.7.6.1
28.7.6.2
28.7.6.3
28.8
28.8.1
28.8.2
29
29.1
29.2
29.2.1
29.2.2
29.2.3
29.2.4
29.2.5
29.2.5.1
29.2.6
29.2.6.1
CFM-MR Market Risk
Analyzer
Reorganization of Single Records in the
Area Menu (Changed)
Increased Length of Fields for
Volatilities (Changed)
Activate the Analysis Structure after
Release Upgrade
Inclusive Indicator in the Calculation
of Accrued Interest (Enhanced)
CFM-MR-NPV NPV Analysis
Creation and Valuation of Eonia Swaps
(Enhanced)
CFM-MR-GAP Gap Analysis
Creation and Valuation of Eonia Swaps
(Enhanced)
Interest Result Evaluation for Forward
Exchange Transactions (Changed)
Spreads in the Cash Flow Evaluation
(Changed)
CFM-CR Credit Risk
Analyzer
Glossary in SAPTerm (New)
Mass Data Capability in the
Postprocessing Function (Enhanced)
FS Financial
Services
SAP R/3 Enterprise Financial Services
1.10 (New)
FS-CML Loans
Structural Changes in the Loans
Customizing Settings
Changes to the Loans Management Menu
Update Task (new)
Expiring Currencies
FS-CML-CN New business
Interested Party Management (Changed)
FS-CML-PO Portfolio
Archiving (new)
1157
1157
1157
1158
1158
1159
1159
1160
1160
1160
1161
1163
1163
1163
______________________________________________________________
lxxviii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
29.2.6.2
29.2.6.2.1
29.2.6.2.2
29.2.6.2.3
29.2.7
29.2.7.1
29.2.7.1.1
29.2.7.1.1.1
29.2.7.2
29.2.7.2.1
29.2.7.2.1.1
29.2.7.2.2
29.2.7.2.2.1
29.2.7.2.2.2
29.2.7.3
29.2.7.3.1
29.2.8
29.2.8.1
29.2.8.2
29.2.8.2.1
29.2.8.2.2
29.2.8.2.3
29.2.8.2.4
29.2.8.2.5
29.2.8.2.5.1
29.2.8.3
29.2.8.3.1
29.2.8.3.1.1
FS-CML-PO-BO Business
Operations
New Features for Charges and Single
Postings (Enhanced)
Workplace for Business Operations:
Initial Screen (Changed)
New Features of the Payoff Function
FS-CML-AC Accounting
FS-CML-AC-PO Posting
FS-CML-AC-PO-TR Balance Sheet
Transfer
Balance Sheet Transfer (New)
FS-CML-AC-RPM
Receivables/Payment Management
FS-CML-AC-RPM-IBS Incoming Bank
Statement
Postprocessing of the Electronic Account
Statement (New)
FS-CML-AC-RPM-PP Payment
Postprocessing
Release Objects NBZE and MANSO (Deleted)
New Features of Payment Post Processing
FS-CML-AC-VA Valuation
Parallel Valuation Areas (Enhanced)
FS-CML-BD Basic Data
Currency Conversion to the Euro for
Collateral and Objects (New)
FS-CML-BD-MD Master Data
Display of Change Documents (Enhanced)
APIs for Collateral Objects, Objects and
Contracts (Enhanced)
Wertberichtigung (neu)
FS-CML-BD-MD-BP Business
Partners
New functions for the SAP Business
Partner for Financial Services
FS-CML-BD-RI Risk Settings
FS-CML-BD-RI-CS Credit Standing
Calculation
Prerequisites for the Credit Standing
Calculation (Changed)
1169
1169
1169
1170
1171
1171
1171
1171
1173
1174
1176
1176
1180
1180
______________________________________________________________
SAP AG
lxxix
SAP
System
Table of Contents
SAP AG
______________________________________________________________
29.2.9
29.2.9.1
29.2.9.2
29.2.9.3
29.3
29.3.1
29.3.1.1
29.4
29.4.1
30
30.1
30.2
30.3
30.4
30.5
30.5.1
30.5.2
30.5.3
30.5.4
30.5.5
30.5.6
30.5.7
30.5.8
FS-CML-IS Information
System
NPVs for Asset-Side Borrower's Note
Loan's (New)
Drilldown Reporting
Customer Drilldown Reporting
Enhancements (Modificat.-Free)
FS-SR Statutory
Reporting for Insurance Companies
FS-SR-DE Germany
Multi-Million Loan Report and
Maintenance of Reporting Indicators
FS-BP Business Partner
New functions for the SAP Business
Partner for Financial Services
PSM Public Sector
Management
Structure Changes in Public Sector
Management (New and Changed)
Changes to the Component Hierarchy
(enhanced)
Activation switch for components of SAP
R/3 Enterprise Public Services
Changes to the Public Sector Management
Menu (enhanced)
PSM-FM Funds Management
Preparing FI Documents for Archiving
(new)
Activating the Old FM Authorization
Check (new)
Vendor View Document Interface
Function Call (Changed)
Allow Initial Value for Account
Assignment Elements (new)
Funded Program (new)
Structure Changes in the IMG of Funds
Management
Upgrade Funds Management (FI-FM) to SAP
R/3 Enterprise Public Sector
1180
1181
1182
1184
1184
1184
1189
1189
1190
1190
1191
1192
1192
1194
1195
1199
______________________________________________________________
lxxx
SAP AG
SAP System
Table of Contents
SAP AG
______________________________________________________________
30.5.9
30.5.10
30.5.11
30.5.11.1
30.5.11.2
30.5.11.3
30.5.11.4
30.5.11.5
30.5.11.6
30.5.12
30.5.12.1
30.5.12.1.1
30.5.12.1.2
30.5.12.1.3
30.5.12.2
30.5.12.2.1
30.5.12.2.2
30.5.12.3
30.5.12.3.1
30.5.13
30.5.13.1
30.5.14
30.5.14.1
30.5.14.2
30.5.14.3
Fast Entry Payment Receipts (Changed)
Upgrade Public Sector (IS-PS) to SAP R/3
Enterprise Public Services
PSM-FM-MD Master Data
Automatic Generation of Cover Pools
(new)
Copying the Standard Hierarchy of
Commitment Item into the Following
Changing the Funds Center Hierarchy
(new)
Functions for the Functional Area
(enhanced)
"Reversal Date" and "Expiry Date" in the
Fund Master Record (changed)
Subdivision of Master Data (new)
PSM-FM-BU Budgeting and
Availability Control
PSM-FM-BU-BF Basic Functions
of Budgeting
Derivation Strategy in Budget Entry
(New)
Transferring Residual Budget from Cover
Pools (new)
PSM-FM-BU-AC Availability
Control
Availability control in Batch Input
(changed)
SAP Enhancement SAPLBPFC (changed)
PSM-FM-BU-RB Revenues
Increasing the Budget
Definition of Additional Revenue in Rule
Maintenance (enhanced)
PSM-FM-BCS Budget Control
System
Budget Control System (New)
PSM-FM-PO Funds
Management-Specific Postings
External Data Transfer (changed)
Master Data Enhancement of Customers and
Vendors (Changed)
PSM-FM-PO-EF Earmarked Funds
1199
1200
1200
1201
1202
1202
1203
1204
1204
1205
1205
1205
1206
1206
1207
1209
1210
______________________________________________________________
SAP AG
lxxxi
SAP System
Table of Contents
SAP AG
______________________________________________________________
30.5.14.3.1
30.5.14.4
30.5.14.4.1
30.5.14.4.2
30.5.14.5
30.5.14.5.1
30.5.15
30.5.15.1
30.5.15.2
30.5.15.3
30.5.15.4
30.5.15.5
30.5.15.6
30.5.15.7
30.5.15.8
30.5.15.9
30.5.15.10
30.5.15.11
30.5.15.12
30.5.15.13
30.5.15.14
30.5.15.15
30.5.15.16
and Funds Transfers
Business Add-Ins for Earmarked Funds
(new)
PSM-FM-PO-RE Request
Request Functions (enhanced)
Deferral Functions (enhanced)
PSM-FM-PO-CA Cash Desk
IS-PS Dunning Program Enhancement and
Execution (enhanced)
PSM-FM-UP Actual Update
and Commitment Update
Carryforward Level Flag with Numeric
Value (Changed)
New Item in the Document Carried Forward
(Changed)
PBET: Version Posting Date Derivation
(Changed)
Purchase Requisitions Generated from
Sales Orders Update FM (Changed)
Condition Field in Funds Management
Changes to Commitment Reconstruction in
Funds Management (Changed)
SD Order Update in Funds Management (FM)
(Changed)
Stock Transfer Orders Can Update Funds
Management Commitment
Updating Down Payment Clearing (Changed)
Budget-Relevant Transaction Types of
Asset Accounting (Changed)
Deactivating Check for Identical Fiscal
Years in Payment Selection
Integrating Controlling and Funds
Management (changed)
Log for Subsequent Postings of Financial
Accounting Documents (changed
Activating/Deactivating Funds Management
(changed)
Check of Critical Business Transactions
(new)
Period-End Closing for Payment Transfer
(changed)
1212
1212
1216
1217
1217
1217
1218
1218
1219
1220
1220
1222
1222
1222
1223
1223
1224
1225
______________________________________________________________
lxxxii
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
30.5.15.17
30.5.15.18
30.5.16
30.5.16.1
30.5.16.2
30.5.16.3
30.5.17
30.5.17.1
30.5.17.2
30.5.17.3
30.5.18
30.5.18.1
30.5.18.2
30.5.18.3
30.5.18.4
30.5.18.5
30.5.18.6
30.5.18.7
30.5.18.8
30.5.18.9
30.5.18.10
30.5.18.11
30.5.18.12
30.5.18.13
30.5.18.14
30.5.18.15
30.6
30.6.1
30.6.2
Daily Selection with Payment Selection
(changed)
Payment Matching (changed)
PSM-FM-CL Closing
Operations
Functions for Closing Operations
(changed/enhanced)
Programs for the Commitment Carryforward
(deleted)
SAP Enhancements for Year-End Closing
Operations (changed/enhanced)
PSM-FM-IS Information
system
BAdI: Change list header of lists of the
SAP List Viewers (ALV)(new)
Delta Update Business Information
Warehouse (enhanced)
Reports in the Information System
(deleted)
PSM-FM-DE Special Function
Public Sector Germany
1225
1226
1227
1229
1229
1231
1231
1231
1231
1232
Payment transfer (enhanced)
Structural and Grouping Change (new)
SAP Enhancement for Budget Carryforward
(changed)
PSM-GM Grants
Management
New Application Component: Grants
Management (New)
PSM-GM-UP Actual Update
1233
1234
1234
______________________________________________________________
SAP AG
lxxxiii
SAP
System
Table of Contents
SAP AG
______________________________________________________________
30.6.2.1
30.7
30.7.1
30.7.1.1
30.7.1.2
30.7.2
30.7.2.1
30.7.3
30.7.3.1
30.7.4
30.7.4.1
30.8
30.8.1
31
31.1
31.2
31.3
31.4
31.4.1
31.4.2
31.4.3
31.4.4
31.4.5
and Commitment Update
Stock Transfer Orders Can Update Funds
Management Commitment
PSM-FG Functions for US
Federal Government
PSM-FG-PP US Prompt
Payment Act
Federal Government: Improper Invoices
(New)
Prompt Payment Act: Fast Pay and
Accelerated Pay (New)
PSM-FG-TC Central Cash
Desk Procedure
Changes to Federal Government Treasury
Confirmation Processing (Change
PSM-FG-AP Cost-Relevant
Asset
US Federal Government: Accountable
Properties (New)
PSM-FG-RS Sampling
Procedure Invoice Verification
US Federal Government: Payment
Certification Statistical Sampling (New
PSM-FA Fund Accounting
Express Installation for an FI-SL System
(new)
1235
1235
1236
1236
1236
1236
1238
1238
1239
1239
1239
1239
1240
IS-B Bank Components
SAP R/3 Enterprise Financial Services
1.10 (New)
New functions for the SAP Business
Partner for Financial Services
IS-B-BCA Bank Customer
Accounts
Average Daily Balance (ADB)
Annual Percentage Yield (APY)
Business Partner Tax ID
Dormancy and Escheat Compliance
Standard Funds Availability
1241
1241
1245
______________________________________________________________
lxxxiv
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
31.4.6
31.4.7
31.4.8
31.4.9
31.4.10
31.4.11
31.4.12
31.4.13
31.4.14
31.4.15
31.4.15.1
31.4.15.2
31.4.16
31.4.16.1
31.4.16.1.1
31.4.16.1.2
31.4.16.2
31.4.16.2.1
31.4.16.3
31.4.16.3.1
31.4.16.3.2
31.4.16.3.3
31.4.16.3.4
31.4.17
31.4.17.1
31.4.17.2
31.4.17.2.1
31.4.18
31.4.18.1
31.4.18.1.1
31.5
31.5.1
31.5.1.1
31.5.2
BCA US/Canada: Overview of Enhancements
Permanent Holds New Features
Reports for IRA Portfolios
Retirement Plan
Create BCA Account for a Retirement Plan
Retirement plan payment transactions
Retirement Plan Standing Order
Time Deposit Enhancements
Withholding Tax on Withdrawals
IS-B-BCA-BF Basic Functions
Changes in the BCA Customizing Structure
Note Window for Payment Transaction
Blocks
IS-B-BCA-MD Master Data
IS-B-BCA-MD-CD Condition
Dynamic Balances
IS-B-BCA-MD-PR Product
definition
Extended payment notes during account
closing
IS-B-BCA-MD-AC Account
Principle of dual control for account
closure
Time periods during account balancing
Resubmission function
Changes in the account master data
IS-B-BCA-AM Account
Management
IS-B-BCA-AM-BF Basic functions
Define Customer Fields
IS-B-BCA-PT Periodic Tasks
IS-B-BCA-PT-IC Interest /charge
calculation
Compensation hierarchy enhancements
IS-B-DP Transaction Data
Pool
IS-B-DP-BD Basic Data
Deletion of Objects in the SEM Banking
Data Pool
IS-B-DP-EDT External Data
1263
1265
1265
1265
1267
1268
1269
1269
______________________________________________________________
SAP AG
lxxxv
SAP
System
Table of Contents
SAP AG
______________________________________________________________
31.5.2.1
31.5.2.2
31.6
31.6.1
31.6.2
31.6.2.1
31.6.2.2
31.6.2.3
31.6.3
31.6.3.1
31.7
31.7.1
31.7.2
31.7.3
31.7.3.1
31.7.3.2
31.7.3.3
31.7.4
31.7.4.1
31.7.4.2
31.7.4.3
31.8
31.8.1
Transfer
New Transfer Category for Financial
Product Class Data
IDoc Framework for RFC Interface for
External Data Transfer
IS-B-PA Profitability
Analysis
Activities and Changes after the Upgrade
IS-B-PA-STC Single
Transaction Costing
NPV of Charges and Commission
Distribution of Charges and Commission
to Periods
Interest Contribution Based on Average
Volume
IS-B-PA-PA Profitability
Analysis
SD Interface for Bank Operating Concerns
IS-B-RA Risk Analysis
Activate the Analysis Structure after
Release Upgrade
Inclusive Indicator in the Calculation
of Accrued Interest (Enhanced)
IS-B-RA-MR Market Risk
Analysis
Reorganization of Single Records in the
Area Menu (Changed)
Increased Length of Fields for
Volatilities (Changed)
Creation and Valuation of Eonia Swaps
(Enhanced)
IS-B-RA-CL Default Risk and
Limit System
Glossary in SAPTerm (New)
Mass Data Capability in the
Postprocessing Function (Enhanced)
Initial Screen for Processing Business
Partner Relationships (Changed)
IS-B-SA Strategy
Analyzer
IS-B-SA-ALM Asset/Liability
1270
1270
1271
1271
1272
1272
1273
1273
1273
1274
1274
1274
1275
1275
1276
1276
1277
1277
______________________________________________________________
lxxxvi
SAP AG
SAP
System
Table of Contents
SAP AG
______________________________________________________________
31.8.1.1
31.8.1.2
31.8.1.3
31.8.1.4
Management
Creation and Valuation of Eonia Swaps
(Enhanced)
Interest Result Evaluation for Forward
Exchange Transactions (Changed)
Spreads in the Cash Flow Evaluation
(Changed)
Complete Balance Sheet and Profit/Loss
Simulation (new)
1277
1277
1277
1278
1278
______________________________________________________________
SAP AG
lxxxvii
SAP System
______________________________________________________________
______________________________________________________________
SAP AG
1
SAP System
______________________________________________________________
1 SAP Reference IMG structure changes in Release 4.70
Use
Release notes about SAP Reference IMG structure changes are in the associated IMG areas. You can find
them as follows:
1.
Call the complete list for the Release.
2.
Search in the list for the term Structure.
The first entry found is marked.
3.
To find more entries, continue with Find Next.
Effects on Existing Data
To copy the changes into your Project IMGs and the Release views, you must regenerate them.
______________________________________________________________
SAP AG
2
SAP System
______________________________________________________________
2 Activation Switch for the SAP R/3 Enterprise Extension Set
Use
As of SAP R/3 Enterprise Extension Set 1.10, you can implement certain functions flexibly.
SAP R/3 Enterprise consists of the SAP R/3 Enterprise Core and the SAP R/3 Enterprise Extension Set,
which is automatically installed when you upgrade to or install SAP R/3 Enterprise.
This Extension Set contains several components (SAP R/3 Enterprise Extensions and other components),
in which new functions are delivered.
To use the functions of the components of the SAP R/3 Enterprise Extension Set, you activate a switch
for the relevant component. You can therefore specifically implement only those components that you
want to use.
Activating a switch for a specific component does not configure any commercial processes. It creates
technical settings that enable you to use the functions in the activated components of the SAP R/3
Enterprise Extension Set.
Effects on System Administration
You can only use the functions in the components of the SAP R/3 Enterprise Extension Set if you have
previously set the activation switch for the corresponding components under Activation Switch for SAP
R/3 Enterprise Extension Set.
Effects on Customizing
Activating the switch for a component under Activation Switch for SAP R/3 Enterprise Extension Set can
lead to automatically generated enhancements to the following structure types:
o
Menu
o
Implementation Guide (IMG)
o
Application component hierarchy
See also
See the release information for the individual components of the SAP F/3 Enterprise Extension Set in the
SAP Service Marketplace under http://service.sap.com/releasenotes.
______________________________________________________________
SAP AG
3
SAP System
______________________________________________________________
3 Accessibility
Use
We are in the process of making SAP software accessible to users with disabilities. For general
information about the accessibility of the SAP System, see the SAP Library -> Getting Started:
Accessibility Supplement. You can also find information about the accessibility of specific functions in
the Release Notes for individual components. The titles of these Release Notes begin with "Accessible:"
to allow you to recognize this information easily.
______________________________________________________________
SAP AG
4
SAP System
______________________________________________________________
4 CA
Cross-Application Components
4.1 CA-ESS
Employee self-service
4.1.1 HRESSWWW Enhancement Replaced
Use
Enhancement HRESSWWW was divided into four enhancements, but the functionality has not changed.
Reason for the new division: The four sub-functions can now be activated independently.
The new enhancements are:
o
HRESSW1 (search string)
o
HRESSW2 (check starting date)
o
HRESSW3 (propose starting date for ESS)
o
HRESSW4 (password/user assignment for ESS user)
Effects on Customizing
The existing Customizing actions are retained.
4.1.2 Customizing for the Leave Request ESS Application (Enhanced)
Use
As of SAP R/3 Enterprise HR Extension 1.10 (EA-HR 110), you can use the T554S_WEB view to
maintain attendance and absence types for the Leave Request Web application. This view enables you
to swap the workflow templates used for customer-specific ones. In addition, you can use the WEBMO
feature to target particular entries in the view on the basis of your employees' organizational assignments.
Until now, you deactivated attendance and absence types in the V_T554S_ESSEX view that you did not
want to use in the Leave Request Web application. This view remains unchanged in the Implementation
Guide under Personnel Time Management -> Web Applications -> Leave Request.
If you do not want to use the enhanced Customizing options, you do not have to make any changes. The
V_T554S_ESSEX view, however, does not support the new and improved workflow templates available
with SAP R/3 Enterprise HR Extension 1.10 (EA-HR 110). It supports only the WS20000081 and
WS01000109 workflow templates.
The new workflow templates enable employees and approvers to be notified by e-mail, for example. You
can use them only if you manage the absence types for the Web application in the new view,
T554S_WEB:
o
Leave Request (with Approval) (WS04200009)
o
Leave Request (Without Approval) (WS12400004)
______________________________________________________________
SAP AG
5
SAP System
______________________________________________________________
o
Cancel Leave Request (with Approval) (WS12400005)
o
Cancel Leave Request (Without Approval) (WS12400007)
For more information about the new workflow templates, see the SAP Library: Human Resources ->
Personnel Management -> Personnel Administration -> Workflow Scenarios in Personnel
Administration -> Processing and Canceling Leave Requests.
Note that making an entry in the T554S_WEB releases the absence types for use in the Web application;
it does not deactivate them (as in the V_T554_ESSEX view).
Effects on Data Transfer
Caution
The V_T554S_ESSEX view is also used for the Record Working Times Web application (CATS
regular). You must not therefore delete the entries in this view.
SAP R/3 uses the RPU470T554S_ESSEX XPRA to transfer your entries during an upgrade from the
V_T554S_ESSEX view to the T554S_WEB view. This view is available in the Implementation Guide
under Personnel Time Management -> Web Applications -> Leave Request (Old). The entries in the
V_T554S_ESSEX view remain unchanged, which means that you can continue to use it.
4.2 CA-DMS
Document Management
4.2.1 Structure Changes in Document Management
Use
From this release you can now edit documents in the Web interface.
Because of this the structure for document management has been extended. The following activity has
been added:
Set Up WebDocuments (BSP).
See also
Document Processing in the Web Interface
4.2.2 Document processing in the Web interface
Use
From SAP R/3 Enterprise PLM Extension 1.10 (EA_APPL 110) you can edit document info records
and assigned original application files in the Web interface.
These processing functions are grouped under the term WebDocuments. Users can also edit documents,
even if they do not familiar with the functions of document management (application component
______________________________________________________________
SAP AG
6
SAP System
______________________________________________________________
CA-DMS); for example, employees from product management or engineering.
You can carry out the following editing functions:
o
Select a document from a personal list (stack)
You get a list of up to 10 documents that you have previously been editing. You can display or edit
the documents from this list.
o
Find a document
You can enter different search criteria (such as document data, class data, linked objects, free text
search).
You can further edit the documents from the results list; or you can display or change original
application files.
o
Display documents
Selected document data is presented in the form of a datasheet. If a thumbnail exists for a graphical
original application file, then it is displayed on the data sheet. The integrated viewer allows the
display of original application files in all file formats.
o
Change document
You can change the document data (for example, enterprise-specific additional data), or you can add
an original application file. You can use other functions, such as distributing a document to a
recipient list.
o
Create document
If you create a document, you can check in an original application file into a central secure storage
area.
Effects on Data Transfer
The technological basis for the processing of documents in the Web interface is Business Server Pages
(BSP) and MIME objects from the Web Application Builder. Acces to the Net is via HTTP protocol.
The exchange of different types of data in the Internet is controlled by Multipurpose Internet Mail
Extensions (MIME) log. The Business Server Page for document processing is complete. You do not
need to carry out any additional activities.
Effects on Customizing
To use the functions you need to edit the Customizing (IMG) for Document Management.
o
Check the system settings in Customizing for Document Management; such as Control Data, and
General Data.
o
You make special, additional settings for processing in the Web interface in Customizing for
Document Management in the following activities: Set Up WebDocuments (BSP).
See also
You can get detailed information in the SAP Library, under Document Management, Processing
Documents with WAS-Based Web Applications.
______________________________________________________________
SAP AG
7
SAP System
______________________________________________________________
4.2.3 CA-DMS-EDT
Document Processing
4.2.3.1 Structural Changes in PLM-LDM
Use
o
In the IMG of Logistics General, the structure Product Data Replication was placed at the same
level as Configuration Management.
o
In the IMG of Cross-Application Components, CAD Desktop was arranged under CAD
Integration.
4.2.3.2 CAD desktop
Use
From SAP R/3 Enterprise PLM Extension 1.10 (EA_APPL 110) there is an interface for CAD
integration available with the CAD desktop.
CAD structures are displayed in the CAD desktop in a fully-configurable interface, which allows you to
display and manage a variety of document information stored in the SAP system, such as person
responsible, status, and material links, all in the form of display variants.
The CAD desktop is a tool for the creation and processing of document structures directly from the CAD
system. It supports various CAD systems (Pro/ENGINEER, CATIA, Inventor, others in development).
The interfaces are developed by partner firms and offered by SAP. The support of concurrent engineering
and versioning enables simultaneous processing (for example, of an assembly) by multiple users, where
the different processing statuses can be saved in the system.
The CAD desktop is called from a CAD system via SAP direct integration. You can easily manage
assemblies engineered in the CAD system from the comfort of the CAD desktop. You can choose from
the following views:
o
SAP view
o
CAD view
o
CAD worklist
o
CAD working directory
The SAP system ensures consistent datasets and reduced idle time during the editing process, thanks to
conflict solution mechanisms and checking mechanisms.
Versioning in the CAD desktop allows you to save changed originals as new versions, without
overwriting the source version of the original application file. You can display or change the last-released
version of an original or a document info record.
Status management allows you with status networks (defined in Customizing) to also set different
statuses in the CAD desktop for your document info records, and to comply with predefined processing
sequences.
______________________________________________________________
SAP AG
8
SAP System
______________________________________________________________
Effects on Customizing
CAD Desktop
4.3 CA-CL
4.3.1 CA-CL-CHR
Classification
Characteristics
4.3.1.1 Where-Used List for Characteristics and Characteristic Values
Use
The where-used lists for characteristics and characteristic values have been brought together in a new
transaction.
You can generate where-used lists for characteristics and values by using the same transaction. You can
also include object dependencies.
Effects on System Administration
The development of cross-application components, such as classification, now belongs to the software
layer SAP_ABA (SAP application basis), and no longer to SAPAPPL (SAP appplication software).
4.4 CA-CAD
CAD Integration
4.4.1 Structural Changes in PLM-LDM
Use
o
In the IMG of Logistics General, the structure Product Data Replication was placed at the same
level as Configuration Management.
o
In the IMG of Cross-Application Components, CAD Desktop was arranged under CAD
Integration.
4.4.2 CAD desktop
Use
From SAP R/3 Enterprise PLM Extension 1.10 (EA_APPL 110) there is an interface for CAD
integration available with the CAD desktop.
CAD structures are displayed in the CAD desktop in a fully-configurable interface, which allows you to
______________________________________________________________
SAP AG
9
SAP System
______________________________________________________________
display and manage a variety of document information stored in the SAP system, such as person
responsible, status, and material links, all in the form of display variants.
The CAD desktop is a tool for the creation and processing of document structures directly from the CAD
system. It supports various CAD systems (Pro/ENGINEER, CATIA, Inventor, others in development).
The interfaces are developed by partner firms and offered by SAP. The support of concurrent engineering
and versioning enables simultaneous processing (for example, of an assembly) by multiple users, where
the different processing statuses can be saved in the system.
The CAD desktop is called from a CAD system via SAP direct integration. You can easily manage
assemblies engineered in the CAD system from the comfort of the CAD desktop. You can choose from
the following views:
o
SAP view
o
CAD view
o
CAD worklist
o
CAD working directory
The SAP system ensures consistent datasets and reduced idle time during the editing process, thanks to
conflict solution mechanisms and checking mechanisms.
Versioning in the CAD desktop allows you to save changed originals as new versions, without
overwriting the source version of the original application file. You can display or change the last-released
version of an original or a document info record.
Status management allows you with status networks (defined in Customizing) to also set different
statuses in the CAD desktop for your document info records, and to comply with predefined processing
sequences.
Effects on Customizing
CAD Desktop
4.5 CA-BP
SAP Business Partner
4.5.1 Changes in the IMG Structure of the SAP Business Partner
Use
The following changes have been made in the IMG structure of the SAP Business Partner:
The basic settings of Business Partner have been extended by way of the business partner roles with the
activity Properties of Business Partner Roles.
For more information on this subject, see the release information Properties of Business Partner Roles.
Accordingly, the activity Properties of Business Partner Relationship Categories has been included in the
basic settings of the business partner relationships.
For more information on this subject, see the release information Properties of Business Partner
______________________________________________________________
SAP AG
10
SAP System
______________________________________________________________
Relationship Categories.
4.5.2 Properties of BP Roles and BP Relationships
Use
Business partner roles
Using the new IMG activity you can
o
change the standard title of a BP role
o
hide BP roles that are not required in the selection list
o
place important BP roles at the beginning of the selection list used for the selection of roles
Business partner relationship categories
Using the new IMG activity for BP relationship categories you can
o
change the standard title of a BP relationship category
o
change the standard definitions for BP relationship categories from the view of business partner 1
(e.g. has the contact person) and from the view of business partner 2 (e.g. is contact person of)
o
hide BP relationship categories in the selection list that are not required
o
place important BP relationship categories at the beginning of the selection list used for the selection
of the BP relationship category, and determine the sequence of the tab pages of the available BP
relationships.
Effects on Customizing
Make the settings for the characteristics of business partner roles and business partner relationship types
in the Implementation Guide of the SAP Business Partner:
o
Business Partner -> Basic Settings -> Business Partner Roles ->
Properties of Business Partner Roles
o
Business Partner Relationships -> Basic Settings ->
______________________________________________________________
SAP AG
11
SAP System
______________________________________________________________
Properties of Business Partner Relationship Categories Properties of Business Partner Relationship
Categories
4.5.3 Changes to the Locator and to the Business Partner Interface
Use
Locator
The locator can be displayed in different ways on the initial screen of the transaction. You can thus adapt
the locator to suit your individual requirements. You can use the pushbutton Settings to select the
various possible way of displaying the locator.
The following possibilities exist:
o
Narrow
You can display the locator as before in its narrow format in the left-hand side of the screen.
o
Full screen
You can display the locator in its full screen format across the entire screen.
o
Hidden
You can hide the locator and thus start the transaction without the locator.
In addition to making the locator narrower or wider step by step, you can use the pushbuttons Minimum
and Maximum to display the locator in its narrow or full screen format in a single step.
Business Partner Interface
The pushbutton Open has been included in the standard toolbar. Using this pushbutton you can call up a
business partner that already exists in the system via the business partner number.
The field Business Partner is now ready for input only when the business partner maintenance is called
up for the first time.
The following changes have been made on the tab page Status: The section Status Management has
been renamed User Status and now contains only the user status. The system status Do not release has
been included in the section Lock. The system status Can be archived has been added to the section
Archiving; this system status is available to you only in connection with the CRM System.
______________________________________________________________
SAP AG
12
SAP System
______________________________________________________________
4.5.4 International Address Versions
Use
You can create any number of international address versions that are set to active in a system for an
address for business partners of the business partner category 'person'.
Until now this was only possible for business partners of the BP category 'organization' and 'group'.
In addition to the address and communication data, the name fields (first name, last name, birth name,
academic title, etc.) are now taken into consideration for all BP categories.
In order to be able to use the international address versions, you have to set them in the Customizing.
Effects on Customizing
Make the settings for the international address versions in the IMG of the Business Address Services:
o
SAP Customizing IMG -> SAP Web Application Server -> Basis Services -> Address Management
-> Activate International Address Versions
4.5.5 Changes in the IMG structure for Release 6.20
Use
The following changes have been made in the IMG structure of the SAP Business Partner:
The field groupings of the business partner relationships have been extended by way of the activity
Configure Field Attributes for Each Client.
For more information, see the release information Changes to the Business Partner Relationships.
Authorization Managment along with the activity Establish Authorization-Relevant Field Groups have
been included in the basic settings of the business partner relationships.
For more information, see the release information Changes to the Business Partner Relationships.
4.5.6 Various New Features and Changes in Business Partner
Changes to the Interface
Use
The following changes have been made to the locator:
o
The group of pushbuttons for changing the width of the locator has been arranged along the
left-hand edge of the window.
This brings the advantage that the group of pushbuttons is always arranged along the left-hand edge
of the window, regardless of the width of the locator, and does not move with the locator when it is
______________________________________________________________
SAP AG
13
SAP System
______________________________________________________________
made wider or narrower.
o
The number of pushbuttons in the locator area has been reduced.
The pushbuttons Previous Search and Next Search on the tab page Search below the search
criteria have been removed and replaced by entries in the context menu of the hit list.
On both tab pages of the locator, the pushbuttons Remove from my objects and Refresh have
been omitted, leaving only the pushbuttons Choose and Add to my objects that can be accessed
via the hit list.
With the pushbutton Choose, you transfer the business partners selected in the hit list into the work
area.
With the pushbutton Add to my objects you transfer the business partners selected in the hit list
into your worklist.
Changes to Status Managment
Use
The pushbutton Assign status profile can be found on the interface at the user status.
If you have defined several status profiles in the Customizing, you must first make a one-off selection of
a status profile and assign it to the business partner in order to be able to define a required status for the
business partner in question.
The pushbutton Assign status profile allows you to assign a business partner more easily to a status
profile.
After the assignment of the status profile, the defined statuses are displayed for selection in the dialog
box. If you have selected a status, the selected status profile as well as the assigned status are transferred
and displayed on the interface.
After you have assigned the business partner to a status profile, the text on the pushbutton changes from
Assign status profile to Insert status. Thus, after the assignment of a status profile, the pushbutton
refers only to the selection of the status within the selected status profile.
Tree Structure for the Industries
See also
Dependency of the Fields Form of Address and Gender
Use
You can define a dependency between the fields Form of Address and Gender in the Customizing of
the Business Address Services (BAS).
When you enter a gender-specific form of address (e.g. Mr/Mrs) or make a change, the assignment of the
gender is automatically adapted.
If you change the indicator for the gender and it no longer matches the form of address, you receive an
error message.
The adaptation of the gender is based on the form of address and not the opposite.
Effects on Customizing
Make the settings for the dependency of the fields Form of Address and Gender in the IMG of the
Business Address Services (BAS):
______________________________________________________________
SAP AG
14
SAP System
______________________________________________________________
o
SAP Customizing IMG -> SAP Web Application Server -> Basis Services -> Address
Management-> Maintain Texts for Form of Address
Change History for Address, Bank and Payment Card Details, Industries and
Identification Numbers
Use
Via the pushbutton Change History below the relevant input area you can display the change
information for a selected address, bank details, payment card details, industry or identification number.
Changes to Data Cleansing
Use
In order to enable data exchange of data cleansing cases with other systems, the following changes were
made to the interface for data cleansing:
o
Source/target decision
When you store a data cleansing case, a screen appears where you decide which of the data records
constitutes the source and which the target for data cleansing.
The data record that should remain in the system in the long-term is regarded as the target for data
cleansing. You can determine only one target record, but it can refer to several source records if
necessary.
Once you have made the source/target decision, you can only transfer the data from the source
objects to the target, but not in the other direction.
o
Status of the data cleansing case
Additional statuses are now available to you for a data cleansing case. However, not all the available
statuses are displayed on the interface for the value selection.
The selection depends on
a)
whether a system is able to make a source/target decision.
You make this setting in the Customizing.
b)
which initial status is set
This setting is controlled by a system table and you cannot make it yourself.
Changes to the objects involved (e.g. business partners) are not allowed in the case of the status R
(rejected), D (done) B or (blocked).
Effects on Data Transfer
A data exchange of cleansing cases makes sense, if subsequent actions should occur in other systems (e.g.
because there are other referencing objects there). The exchange takes place via the new SAP Exchange
Infrastructure, and the messages defined for this purpose are stored in the Interface Repository as
message types COM_HYPO*.
If data exchange should take place, it makes sense to define only one system (= 'master' of the data
cleansing) as able to make a decision for a cleansing case (see below for the Customizing).All other
systems should not have this ability (='clients' of the data cleansing).
Effects on System Administration
If a data exchange is required, the SAP Exchange Infrastructure has to be set up accordingly (particularly
the System Landscape Directory). For more information, see the appropriate section of the basis
______________________________________________________________
SAP AG
15
SAP System
______________________________________________________________
component BC-AI.
Effects on Customizing
Table/view COMC_CLEAR_ACT was extended by way of a field, 'hypothesis decision' , which makes
it possible to establish whether a system should be able to decide on cleansing cases. The indicator should
only be set for a system in the system landscape if a data exchange has been set up.
The new system table, COMC_CLEAR_STAT, controls which statuses and which status transfers can be
included in a system.
4.5.7 CA-BP-BP
Business Partners
4.5.7.1 Changes to Data Cleansing
Use
In order to enable data exchange of cleansing cases with other systems, the following changes were made
to the interface for data cleansing:
o
Source / target decision
When you store a data cleansing case, a screen appears where you decide which of the data records
constitutes the source and which the target for data cleansing.
The data record that should remain in the system in the longterm is regarded as the target for data
cleansing. You can determine only one target record; however it can refer to several source records.
When you have made the source / target decision, you can only transfer the data from the source
objects to the target, but not in the other direction.
o
Status of the data cleansing case
Addtional statuses are now available to you for a data cleansing case. However, not all the available
statuses are displayed on the interface for the value selection.
The selection of the statuses depends on
a)
whether a system is able to make a source / target decision.
You select this setting in customizing.
b)
which initial status is set.
This setting is controlled by a system table, you cannot set it yourself.
You cannot make changes to the objects involved (i.e. business partners) in the case of any of the
following statuses:
-
R (rejected)
-
D (done)
-
B (blocked)
Effects on Data Transfer
A data exchange of data cleansing case makes sense if subsequent actions should occur in other systems
e.g. because there are other referencing objects there.
The exchange takes place via the SAP Exchange Infrastructure and the messages defined for this purpose
are stored in the Interface Repository as message types COM_HYPO* .
______________________________________________________________
SAP AG
16
SAP System
______________________________________________________________
If you want to carry out a data exchange, define just one system to make a decision for a cleansing case
('Master' of data cleansing).
All other systems should not be allowed to decide on a cleansing case. ('Clients' of data cleansing).
Effects on System Administration
If you want to carry out a data exchange of data cleansing cases, you must set up the SAP Exchange
Infrastructure accordingly (particularly the System Landscape Directory).
Further information can be found in the basis component BC-AII.
Effects on Customizing
The system table COMC_CLEAR_STAT controls which status and which status transfers can be set in a
system.
The view COMC_CLEAR_ACT has been extended by way of the field Hypothesis Decision. In this
field you can define whether a system can make a cleansing case decision or not.
This definition should only be made for a system if a data exchange has been set up.
Enter the settings for data cleansing from the SAP Business Partner implementation guide:
o
SAP Customizing Implementation Guide -> Cross-Application Components -> SAP Business
Partner -> Data Cleansing -> Activate Data Cleansing
4.5.7.2 Deletion of Business Partners without an Archiving Procedure
Use
You have the possibility to delete business partners that are temporary, no longer needed or that have
been loaded by mistake into a system, without archiving these records beforehand.
This allows you to decrease the load on you database and to improve the performance of your system.
In preparation for the actual deletion procedure, you can determine the data records for deletion and set
the relevant system status, via the transaction Set Deletion/Archiving Flag (BUPA_DEL).
If you require additional selection criteria, you can implement these with the help of a BAdI.
With the transaction Business Partner -> Deletion of Business Partners (BUPA_PRE_DA), you can
delete the business partners for which a deletion or archiving flag has already been set, or which have the
system status can be deleted.
In both cases, checks are first carried out in order to ensure that the data selected for deletion is no longer
used actively in the system. These checks are defined as event modules of the event DELE1 in the
Business Data Toolset (BDT).
The changes made to the dataset and the business partners that are still being used and therefore cannot be
deleted, are recorded in the application log.
In order to evaluate the log, choose transaction Evaluate Application Log (SLG1) and enter the object
BDT_DATAARCHIVING and the subobject CA_BUPA.
Effects on Existing Data
The business partner is deleted along with all its central components.
You can also delete other, customer-specific data parts. To do this you must define an appropriate module
______________________________________________________________
SAP AG
17
SAP System
______________________________________________________________
for the event DELE2 of the Business Data Toolset (transaction BUS7).
See also
For more information, see note 415007.
4.5.7.3 International Bank Account Number (IBAN)
Use
The international bank account number (IBAN) is an internationally valid ID number of a bank account,
which consists of the combination of the ISO code of the bank country, bank number or bank key and
account number. The maximum length of the international bank account number is 34 alphanumeric
characters and varies from country to country.
The aim of using the IBAN is to simplify the handling of cross-border financial transactions via the
uniform identification of the country, bank number and account number.
In the Business Partner menu, a field for the IBAN has been included in the input area for the bank details
on the tab page Payment Transactions
You can now
o
generate an IBAN for bank details and transfer the default value into your bank data
o
derive bank details from an IBAN that you know of, and then just enter an appropriate bank details
ID
In the input area for the bank details on the tab page Payment Transactions, you can recognize by the
change of color of the icon in the column IBAN that the international bank account number is there.
Effects on Existing Data
The functionality for the international bank account number was delivered until Standard Release 4.6C in
support packages.
Since the IBAN is stored independently of the bank details of the business partner, it is possible to
regenerate the IBAN at any time for existing data.
Effects on Data Transfer
You can transfer international bank account numbers (IBAN) from external systems with the help of
BAPIs into the SAP System.
4.5.8 CA-BP-RS
Business Partner Relationship
4.5.8.1 Changes to the Business Partner Relationships
Indicator Standard Relationship
Use
______________________________________________________________
SAP AG
18
SAP System
______________________________________________________________
You can identify business partner relationships as the standard relationship.
If you have defined more than one business partner relationship of a relationship type for a business
partner, the BP relationship identified as the standard relationship is selected automatically by the system
in certain scenarios.
You can only ever identify one business partner relationship of a relationship type during a particular
period as the standard relationship.
Nor is it possible to set the indicator standard relationship for a BP relationship for another business
partner of the same relationship type in the same period.
If you have already identified a business partner relationship (1) as the standard relationship, and you
then assign the indicator to another business partner relationship (2) of the same relationship type in the
same period, the indicator is reset for the first business partner relationship and is transferred to the
second relationship.
However, if the validity periods of the two business partner relationship are not the same or do not
overlap, the indicator remains in force for the first business partner relationship as well.
You can assign the indicator standard relationship only to business partner relationships of certain
relationship types.
Of the BP relationship types supplied by SAP, the indicator is provided for the contact person
relationship.
User-defined business partner categories, for which the indicator should be set, must be implemented
with the time constraint categories '0' and '4'.
Field Groupings for Business Partner Relationships
Use
As can already be done for business partners, you can now also maintain field attributes at client-level for
the business partner relationships.
Effects on Customizing
Make the settings for field grouping at client-level in the IMG of the SAP Business Partner:
o
SAP Customizing IMG -> Cross-Application Components -> SAP Business Partner -> Business
Partner Relationships -> Basic Settings -> Field Groupings -> Configure Field Attributes for Each
Client.
Authorization Management
Use
You can carry out authorization checks in the business partner relationships for business partner
relationship categories and field groups.
The authorization check on the basis of the BP relationship categories is carried out for the activities
'create', 'change', 'display' and 'delete'.
The authorization check on the basis of the field groups is carried out for the activities 'change' and
'display'.
In order to be able to carry out an authorization check for field groups, you have to define the
authorization-relevant field groups in the Customizing.
Effects on Customizing
______________________________________________________________
SAP AG
19
SAP System
______________________________________________________________
Make the following settings for authorization managment in the IMG of the SAP Business Partner:
o
SAP Customizing IMG -> Cross-Application Components -> SAP Business Partner -> Business
Partner Relationships -> Basic Settings ->Authorization Management -> Define Field Groups
Relevant to Authorizations.
4.6 CA-GTF
General Application Functions
4.6.1 Terminology for Country Version Brazil (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following Brazilian terms have been
updated in the system:
o
Branch has been renamed business place
o
NBM code has been renamed NCM code
o
CGC has been renamed CNPJ number
4.6.2 CA-GTF-TS
4.6.2.1 CA-GTF-TS-CE
Technical Application Support
Conversion Exits
4.6.2.1.1 Data Elements of Reference Document Numbers (changed)
Use
The data elements listed below have been replaced by new data elements in many tables and structures. If
a field exit was defined for one of these data elements, you must make the adjustments necessary. You
can find more information in note 0029377.
Old data element
F130BELN
FEBFILTER
FRBNR
INVNU
LBLNE
LFSNR
MELFNKD
MTSNR
RECNXBLNR
new data element
F130BELN1
FEBFILTER01
FRBNR1
INVNU1
LBLNE1
LFSNR1
MELFNKD1
MTSNR1
RECNXBLNR1
______________________________________________________________
SAP AG
20
SAP System
______________________________________________________________
RECPPOSTRUNREFN
RESIMVVABBLN
SXBLNR
VVABBLN
XBLNI
XBLNR
XBLNR_EB
XBLNR_EBS
XBLNR_FBWE
XBLNR_SRV
XBLNR_V
XIDENT
4.6.3 CA-GTF-SCM
RECPPOSTRUNREFN1
RESIMVVABBLN1
SXBLNR1
VVABBLN1
XBLNI1
XBLNR1
XBLNR_EB1
XBLNR_EBS1
XBLNR_FBWE1
XBLNR_SRV1
XBLNR_V1
XIDENT1
Schedule Manager
4.6.3.1 Schedule Manager (extended)
Use
From Release 4.70, Schedule Manager offers the following extensions:
o
In task planning, you can copy and schedule subplot plans (task groups). You can schedule tasks,
task groups, and task plans periodically and can use a negative offset for a task, if you schedule a
task plan for a key date.
o
In the monitor, you can select the monitor view by period for a task plan and restrict it by job name.
The context-sensitive menu for the monitor allows you to go directly to the workflow inbox of your
workplace.
o
In the flow definition, you can now specify SAP organizational objects and SAP Office distribution
lists as the recipient of a user decision, and specify SAP organizational objects as the recipient of an
error mail. You can select freely the user name used by the system to check authorization in jobs in
the flow definition. The system executes the client check for program variants on a cross-client
basis. User decisions and error messages make available the termination of the whole flow
definition that is being run. You can print the details of all tasks in a flow definition and create flow
definitions with user-defined worklist categories. You can use a flow definition to synchronize
closing processes in different SAP systems.
o
Application-Specific Templates: Product Cost Planning contains a default flow definition. For IBS
Financial Services, task plans and flow definitions are available in the Bank Analyzer for the
components "Balance Analyzer", "Profit Analyzer", and "Risk Analyzer". A background job is
available for the period lock in Controlling.
______________________________________________________________
SAP AG
21
SAP System
______________________________________________________________
4.7 CA-NO
Messages
4.7.1 New Developments in Notifications: Several Customer Subscreens
Possibl
Use
Several Customer Subscreens:
Up until release 4.6C, for each notification type a maximum of one customer subscreen could be included
in the notification header data. An area of 4 lines was reserved for this subscreen. From release 4.70, for
each notification type it is possible to include one or more customer subscreens in the notification header
data. The size of the customer subscreens can be freely defined as long as they do not exceed the total
size of the tab pages.
Enhancements in User Exits:
In the customer enhancement QQMA0001, the interface of the function modules
EXIT_SAPMIWO0_008 and EXIT_SAPMIWO0_008 was enhanced. Three new import parameters
allow you to execute your own PBO and PAI program parts, depending on the output location (tab page,
subscreen area, screen).
Effects on Customizing
From release 4.70, a second screen area "customer subscreen (>1 Screen/NType)" (091) will be available
for the inclusion of customer subscreens in the notification header. Previously, only the subscreen area
"customer subscreen (one Screen/NType)" (090) was available for this purpose.
When using screen area 090 you assigned the screen to be included under "notification header: screen
areas'. When you use the new screen area 091, a field for the direct assignment of the screen is available
in Customizing for the simplified and extended views.
In Customizing for the simplified and extended views, there is a new field called "tab page allocation".
You can use this field to freely choose the number of subscreens (beween one and five) that you want to
appear on each of the following tab pages: 10\TAB01, 10\TAB02, 10\TAB03, 10\TAB19, 10\TAB20 and
10\TAB21. The fewer subscreens you assign to one tab page, the more space there is available for each
subscreen on that tab page.
The predefined number of five possible screen areas for each notification tab page is still the default
value, so no further activities are required when upgrading. Note that you can only use one of the screen
areas (090 or 091) for each notification type.
4.8 CA-TS
Time Sheet
4.8.1 Cross-Application Time Sheet Enhancements (General)
Use
______________________________________________________________
SAP AG
22
SAP System
______________________________________________________________
Enhancements for transfer to service entry for Materials Management (MM-SRV)
The Cross-Application Time Sheet (SAP CATS) enables internal and external employees to enter data for
service entry for Materials Management (MM-SRV). Previously, it was not possible to delete these
data records after approval. This is now possible. For more information, see Returns for Service Entry
Sheets from Time Sheets (New).
Enhancements for Recording in Controlling (CO)
Previously, the Cross-Application Time Sheet only supported the Hours unit when transferring data
records to activity allocation in Controlling (CO). The Time Sheet now supports all units.
In Customizing for the data entry profile, a new indicator is now available, Take Account of Period
Lock. This indicator enables you to avoid data being entered in the Time Sheet for days that occur in the
locked period for Controlling (CO):
o
If you set the indicator, and enter a data record for a day that occurs in the period locked for
Controlling (CO), the system displays an error message.
o
If you do not set the indicator, and enter a data record for a day that occurs in the locked period for
Controlling (CO), the system does not display an error message. In this instance, you must change
the posting date in the transfer program RCATSTCO (Transfer to Controlling) manually.
Caution
Previously, the SAP R/3 system always performed this check for statistical key figures. However,
this check is now dependent on whether you set the Take Account of Period Lock in the data entry
profile you use.
Fill worklist using iView (new)
You can now provide a user's worklist with working time attributes that the user has already assigned
using the CATS Worklist from myObjects iView. This iView is delivered with the Projects Business
Package.
New fields: Task Type, Task Level, Task Component
The Task Type, Task Component, and Task Level fields enable you to specify the task elements that
are relevant for analysis. Previously, this option was only available in CATS for service providers. Now
you can also use these fields in other Time Sheet user interfaces. Make the necessary settings in the
Implementation Guide (IMG), under Cross-Application Components -> Time Sheet -> Settings for
all User Interfaces -> Time Recording -> Task Levels, Components, and Categories.
Enhanced document flow
The document flow that is displayed in the Time Sheet user interface and transaction CAT8 (Time Sheet
Documents and Follow-On Documents) has been enhanced. Now, you can view the follow-on
documents that are generated in the target component, and the document flow right up to Billing.
4.8.2 CATS notebook: Recording Working Times Offline (New)
Use
______________________________________________________________
SAP AG
23
SAP System
______________________________________________________________
For a number of releases, the Cross-Application Time Sheet (SAP CATS) has been available for
recording working times and activities as a Web application and directly in the SAP R/3 system. Now the
Cross-Application Time Sheet is also available as on offline solution, CATS notebook. CATS notebook is
part of the new solution, Time & Travel notebook. This new solution enables you to record working
times, activities, and trip costs offline.
To be able to implement CATS notebook, the following prerequisites must be fulfilled.
o
SAP PlugIn 2002.1 must be installed (see section 'Effects on Customizing').
o
The files for installingCATS notebook must be present. You can find these files in the SAP
Marketplace, under service.sap.com/cats.
CATS notebook enables you to record working times on notebooks (laptop computers) wherever you are.
The notebooks do not require a connection to the SAP R/3 system for time recording. CATS notebook is
aimed primarily at employees who have to travel a lot and cannot always have a connection to the SAP
R/3 system to record their working times.
The application was developed in Java and runs in a Web browser. It uses standard SAP technology for
synchronizing mobile devices with SAP R/3 Mobile Engine.After the data has been transferred from
CATS notebook to the SAP R/3 system, you can process it in the same way you would process data
records that have been entered using a different user interface of the Cross-Application Time Sheet. CATS
notebook uses the same business logic and the same database table (CATSDB) as the other user interfaces
of the Cross-Application Time Sheet.
Effects on Customizing
CATS notebook uses part of the standard Customizing for the Cross-Application Time Sheet. Make the
appropriate settings in Customizing, under Cross-Application Components -> Time Sheet ->
Settings for all User Interfaces. Certain settings in Customizing for the Time Sheet are not relevant for
CATS notebook. There are additional Customizing tables that are only relevant for CATS notebook. These
Customizing tables and additional objects are delivered with SAP R/3 PlugIn 2002.1. For more
information, see the documentation on CATS notebook. You can find the documentation in the SAP
Service Marketplace, under service.sap.com/cats.
See also
If you want to create a customer message for SAP Support, use component CA-TS-NB.
For further informtion, see the SAP Marketplace:
o
Documentation on CATS notebook: service.sap.com/cats
o
Documentation on Mobile Engine: service.sap.com/mobile -> Groups -> SAP Markets ->
Documentation
o
Information on SAP R/3 PlugIns: service.sap.com/R3-plug-in
For changes or supplements to the available information, see SAP Note 497017.
4.8.3 User Interfaces for the Time Sheet (Enhanced)
Use
______________________________________________________________
SAP AG
24
SAP System
______________________________________________________________
Numerous user interfaces are now available for the Cross-Application Time Sheet (SAP CATS). These
user interfaces enable you to tailor time recording to suit your individual needs. In previous releases the
term "Time Sheet" was usually used to refer to transaction CAT2 in the SAP R/3 system. Now however,
the different user interfaces have been given unique product names that are described here. In future, the
term "Time Sheet" will only be used to refer to all SAP CATS user interfaces and functions.
The independent time sheet user interfaces are distinguished from the enhancing user interfaces by the
following characteristics:
o
The entry screen offers you an overview of the entire data entry period.
o
You can access data that has already been entered and correct, complete, and delete it.
The enhancing user interfaces enable you to record working times quickly wherever you are. If you want
to display or change data that you have entered using an enhancing user interface, you can use one of the
independent user interfaces. You can combine any independent and enhancing user interfaces.
Independent user interfaces
o
CATS classic (transaction CAT2 in the SAP R/3 system)
o
CATS regular (Internet application component CATW, Employee Self-Service application in Web
browser)
o
CATS for service providers (transacton CATSXT in the SAP R/3 system)
o
CATS notebook (mobile offline solution for notebooks based on Mobile Engine)
Enhancing User Interfaces
o
CATS instant (application in the Enterprise Portal)
o
CATS phone (mobile offline solution for WAP-enabled mobile telephones)
For more information, see SAP Library, under Cross-Application Components -> Time Sheet ->
User Interfaces.
For information on the availability of these user interfaces, see SAP Marketplace, under
service.sap.com/cats.
4.8.4 Personal Templates in the Cross-Application Time Sheet (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL_470), you can further simplify data entry in certain
user interfaces of the Cross-Application Time Sheet (SAP CATS). In CATS classic, CATS regular, and
CATS notebook, you can save personal templates in addition to using worklists and default values.
You can save account assignment rows entered in the data entry area as a personal template. The system
saves all working time attributes that are visible and ready for input as part of the personal template.
These are then always displayed when you start the application and when you change to a different data
entry period. This means that you then only have to enter your working times.
______________________________________________________________
SAP AG
25
SAP System
______________________________________________________________
See also
For more information, see SAP Library, under Cross-Application Components -> Cross-Application
Time Sheet -> User Interfaces -> CATS classic -> Data Entry View -> Create Personal
Templates.
4.8.5 Display and Approve Working Times and Tasks (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), new programs are available for displaying
and approving working times and tasks.
o
o
Display
-
RCATS_DISPLAY_ACTIVITIES (Display Working Times)
-
RCATSXT_DISPLAY_ACTIVITIES (Display Working Times and Tasks)
-
RCATSXT_DISPLAY_ACTIVITY_DTL (Working Times and Tasks: Display Details)
Approval
-
RCATS_APPROVE_ACTIVITIES (Approve Working Times)
-
R_APPROVE_ACTIVITIES_EXPENSES (Approve Working Times and Trip Costs)
You can access the new programs via the menu (SAP Easy Access).
The following programs for displaying and approving working times and tasks are still deliverd but are
no longer available in the menu.
o
o
Display
-
Transaction CADO (Selection with Personnel Number)
-
Transaction CAOR (Selection Using Organizational Structure)
Approval
-
Transaction CAPS (Selection According to HR Master Data)
-
Transaction CAT4 (Selection Using Organizational Structure)
-
Transaction CAPP (Selection Using Time Sheet Data)
4.8.6 Enhancements in CATS for service providers
Use
IMG activity for adapting the user interface
You can tailor the user interface for CATS for service providers to suit your requirements in the
Implementation Guide (IMG), under Cross-Application Components -> Time Sheet -> Specifc
______________________________________________________________
SAP AG
26
SAP System
______________________________________________________________
Settings for CATS for service providers -> Customize Interface -> Set Up Central Functions
Tab page Document Flow
In the SAP standard system, the Document Flow tab page is no longer displayed in the History/Worklist
screen area. Instead, the Selective Document Flow function is available in this screen area.
New functions in the History screen area
o
At a glance, you can see if preceding data records exist for a data record in the History area. CATS
for service providers displays an appropriate icon for these data records. If you click on the icon,
you can have the system display the change history for a data record.
o
You can approve or reject the data.
o
You can use SAP Smart Forms to print out data or send it by email.
o
You can filter displayed data according to status, for example, only display approved data records.
Set data release in Customizing
You can make the settings for releasing data in the IMG, under Cross-Application Components ->
Time Sheet -> Specific Settings for CATS for service providers -> Set Up Data Entry Profiles. In
earlier releases, data in CATS for service providers was always released when the data was saved. Now
however, you can schedule a separate release step.
Drag&Drop to assist data entry
You can use Drag&Drop as follows to make it easier to enter data:
o
Drag a data record from the My Account Assignments screen area to a day in the calendar.
CATS for service providers displays the data record together with the day, and any possible default
values for the tasks components in the data entry area.
o
Drag a data record from the History screen area to a day in the calendar.
CATS for service providers copies the data record to this day.
Changed derivation logic
Business Add-In (BAdI) CATS_DERIVATIVES now determines derivation values from task type, task
level, and task component. In the SAP standard system, you can no longer change the derivation values
when entering data. To enable this, you must create a customer-specific implementation of this BAdI.
4.8.7 Business Add-Ins (BAdIs) for the Cross-Application Time Sheet (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), new BAdIs are available for the Time Sheet.
CATS_DERIVATIVES
This BAdI enables you to change derived values for task types, task levels, and task components.
CATS_REPORTING
This BAdI enables you to tailor the new programs for displaying and approving working times and tasks
to suit customer-specific requirements.
______________________________________________________________
SAP AG
27
SAP System
______________________________________________________________
CATS_WORKLIST_ADDIN
This BAdI enables you to influence the setup of the worklist.
CATSXT_EVENT
This BAdI enables you to implement customer fields and data checks for CATS for service providers.
4.8.8 Account Assignment Dimensions for Fund Accounting (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can enter the following account
assignment information using the Cross-Application Time Sheet (SAP CATS):
o
Funds
o
Functional areas
o
Grants
The account assignment objects fund, functional area, and grant are analyzed by Controlling (CO) and
Funds Management (FM). The following options are available to transfer the account assignment
information to these components:
o
Transfer to Human Resources and use cost assignments via Payroll.
In Payroll, the account assignment information is written in payroll table C1 (cost assignments from
different infotypes)and after the payroll results have been posted to Accounting, this information is
available to Controlling and Funds Management. For more information, see SAP Library, under
Human Resources -> Personnel Time Management -> Integrating Time Management with
Other Components -> Cost Assignment.
o
Transfer to activity allocation or use statistical key figures in Controlling (CO)
In this case, account assignment information is transferred directly to Controlling. Separate fields
are available in activity allocation for the sender fund, sender functional area, and the sender grant.
For more information, see SAP Library, under Cross-Application Components ->
Cross-Application Time Sheet -> Process for Transferring Data to the Target Components
-> Data Transfer to Controlling (CO).
Effects on Existing Data
The database table for the Time Sheet (CATSDB) and the database table for transferring data from the
Time Sheet to Controlling (CATSCO) now contain the additional fields.
Effects on Customizing
The new fields for additional account assignment information are ready for input in all data entry profiles
in the standard system. Therefore, after you have upgraded the data entry profiles that are implemented at
your enterprise, the new fields are present. Program RCATSFAW_3 (Time Sheet: Hide New Fields for
Release 4.7) enables you to hide these fields.
See also
For more information, see the Fund Accounting Handbook and the release information, Account
______________________________________________________________
SAP AG
28
SAP System
______________________________________________________________
Assignment Dimensions for Fund Accounting in Personnel Time Management.
4.8.9 Returns for Service Entry Sheets from Time-Sheets (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can retrospectively change a time or quantity
in a time sheet that you have already converted into a service entry sheet. As soon as you convert the
changed time sheet into external services, the system additionally generates both a service entry sheet
with the new data and one in which the original data has been cancelled and in which the Returns
Indicator has been set.
Note:
A return is only possible if a time sheet is used and converted into external services
(CATS/CATM)
The returns indicator cannot be selected manually but is set by the system when a changed
time sheet is converted into external services.
Effects on Existing Data
The additionally generated returns sheet cancels the already existing service entry sheet. You can check
this in the PO history for the underlying purchase order.
Effects on Customizing
To facilitate the use of the returns function for time sheets during the service entry process, you must
select the relevant Activation Indicator in Customizing for External Services Management:
Source Determination and Default Values -> Specify for Client -> Returns Active.
4.9 CA-JVA
Joint Venture Accounting
4.9.1 Replacement of actual posting transactions
Use
The special JVA actual posting transactions :
-
Repost line item RI (KB71)
-
IAA prior period based (KB27)
were replaced by the standard transactions KB61 and KB21N.
The JV functionality ( Recovery indicator handling) is now incorporated
in the standard transactions
______________________________________________________________
SAP AG
29
SAP System
______________________________________________________________
4.9.2 Switch for activating Joint Venture Accounting in a system
Use
Up to core release 4.6C, Joint Venture Accounting was rolled out and shipped separately as an Add-On
component. As of R/3 Enterprise Joint Venture Accounting is a so called Enterprise Extension, and will
be shipped together with core.
To be able to use Joint Venture Accounting, it has to be activated in IMG.
Effects on Data Transfer
Activation of Joint Venture Accounting creates an active-entry for the JVA component in table TBE11.
Effects on Customizing
First, Joint Venture Accounting has to be activated system wide:
The following client independent table entries will be created:
-
TJ01 (Business Transactions),
-
T022/T (FI-SL Activity: Fixed Data and Texts)
-
T8J03/4 (JV Billing levels and Texts)
-
EDIFCT (IDoc: Assignment of FM to log. message and IDoc type)
Second, Joint Venture Accounting has to be activated for each individual client:
The following client dependent table entries will be created:
-
T881 (FI-SL Ledger)
-
T886 (FI-SL Activity)
-
TRWCA (FI/CO Interface: Active Components)
-
T8J0A/B (JV Functions and Texts)
-
T8J0J/K (JV Function Items and Texts)
4.9.3
4.9.4 Production Sharing Accounting (Enhanced)
Use
______________________________________________________________
SAP AG
30
SAP System
______________________________________________________________
Activate PSC Rollup
This function creates new rollup user exits into the SAP customer's exit program. It does not delete
existing exits but searched for the next free exit. During the rollup, the system creates or changes data as
required.
For example, PSA master data such as production sharing contracts and calculation types do not exist in
JVA; these data objects are stored only in PSA. During rollup, therefore, the system calls user exits to
adjust the data derived from JVA.
PSA Document Number Ranges
This function involves defining a range of document numbers that are required for posting documents to
the PSA ledger.
Document numbers are used to post documents to the PSA ledger during the rollup of cost data to the
PSA ledger as well as during manual transfers between production sharing contracts.
Activate Planning
This transaction is available for you to activate plan versions in the PSC ledger.
Configuration Activities (Enhanced)
Production configuration screens are available for you to specify whether data entry fields in the daily
production transactions are required, optional, or suppressed.
As of SAP R/3 Release 4.7 for Production Sharing Accounting, other new configuration includes the
definition of a source company code, which defines a source system (such as Joint Venture Accounting)
for a given company code. This is necessary because the source system determines the sending/receiving
tables and ledgers.
Volume conversion factors
Volume conversion factors are available for you to specify the factors for the system to use when
converting volumes from one unit of measure into another unit of measure.
Calculation types
Calculation types are available so that you can:
--identify specific calculations when you assign validation rules for rolling up cost data from the source
to the PSA ledger
--define calculation schemes, which contain specific parameters that the system uses when carrying out
calculations
--sub-divide cost categories when it is necessary to distinguish between different types of costs, for
example
Calculation Categories (New)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, the following new calculation categories
are available. These new calculation categories allow the PSC calculation to be processed as a real
entitlement calculation.
·
Entitlement Adjustments
·
Gross Entitlement
______________________________________________________________
SAP AG
31
SAP System
______________________________________________________________
·
Product Adjustments
·
Net Profit Oil incl. Excess
·
Net Excess Profit
·
Net Entitlement
For each category, new calculation types are available. Also, new formulas are defined to calculate the
new categories correctly.
PSA Master Data (Details & Overview)
This transaction creates a production sharing contract (PSC) master data record. The PSC master data
record contains information such as the PSC name and description, the date the contract was signed, the
currency to be used, etc.
PSA Products
This transaction creates a production sharing accounting (PSA) master data record. The transaction
involves creating a code and description for the new PSA product and assigning a unit of measure to the
product.
PSA Equity Groups
As of SAP R/3 Release 4.7 for Production Sharing Accounting, in addition to a JVA equity group, a PSA
equity group can be defined to influence the partner split.
This is possible for an entire PSC which is defined as a no equity group PSC. In this case every
calculation type needs the assignment of a PSC EG. For each type a different or the same equity can be
used; the JVA equity group is not transferred from JVA to PSA for these PSCs.
It is also possible to assign a PSA equity group to a regular PSC, where the system splits some calculation
types by the JVA equity group share and some by the PSA equity group share. The PSA equity group can
be assigned to the calculation type for the PSC/Product combination, even though the JVA equity group
is still stored in the ledger records.
PSA Groups
PSA Groups are available in order to stipulate that when the costs of a PSC within a group of PSCs
exceed the cost recovery cap, the excessive costs are transferred in the current period to a producing PSC.
Only one PSC in a group of PSCs can be designated as producing. (In contrast, for PSCs that are not in a
group and that have costs exceeding the cost recovery cap, the excessive costs are transferred from the
current period to the following period.)
Calculation Scheme (Header & Detail)
Calculation schemes include details of the formulas. Calculation schemes define the percentages that the
system uses for different calculations. Percentages are specified on a sliding scale basis. Three new
sliding scale methods are available:
·
Revenue Cost Index, which sums the cumulative contractor cost and the cumulative contractor
share of profit oil, and divides the amount by the cumulative contractor cost bank
·
Cumulative production in volume, which is based on the total production recorded in the PSA
ledger
·
Cumulative production in value, which is based on the total revenue recorded in the PSA ledger
______________________________________________________________
SAP AG
32
SAP System
______________________________________________________________
Further, in order for the system to execute calculations, you must assign calculation schemes to
calculation types. This assignment links the percentages in the schemes to the formulas within the
calculation categories.
Planning & Forecast (New)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, the following new planning and forecast
features are available.
Version Numbers
Version numbers can be used for plan data to allow to store and calculate multiple versions of
Entitlement Calculation.
Planned Production Data Entry
It is possible to enter volumes for the plan version in the same way that actual volumes are entered.
Populate Cost Plans
A new Rollup for Plan data function is available to transfer plan data from JVA to PSA and store it with a
designated version number.
Actual data is always stored with version 001 and record type 0, while plan data is stored with record type
1. For plan versions all defined versions (special ledger standard functionality) can be used.
Copy Plan Versions
You can use the system to copy plan data as well as actual data to a new plan version.
Entitlement Plan Calculation
Entitlement calculation features, including posting, are available for plan data.
Entitlement Plan Calculation Reversal
It is possible to reverse posted plan entitlement.
PSA Ship Codes
This transaction allows you to define ship codes and their corresponding descriptions for use in the daily
processing transactions.
PSA Oil Types
This transaction allows you to define oil types and the maximum API (gravity) for use in the daily
processing transactions.
PSA Terminal Codes
This transaction is available to define the terminal codes to be used for the lifting transactions.
Terminals for Lifting (New)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, you can enter lifting by terminal. The
system then splits the volumes for the lifting either once a period or month, depending on the ratio of the
production volumes on PSC level.
______________________________________________________________
SAP AG
33
SAP System
______________________________________________________________
The system stores the split postings as transfer postings from the terminal to the PSCs before the
production interface prepares the input data for the calculation.
Assigning Joint Ventures to PSCs for Rollup Processing
This transaction is available to assign joint ventures (JVs) to production sharing contracts (PSCs).
A JV represents a petroleum production project or installation in Joint Venture Accounting; in the
Production Sharing Accounting system its equivalent is a PSC.
You must assign a JV to a PSC because a JV is one of the keys for posting in the JVA ledger, which is the
usual source for cost postings that are rolled up to the PSA ledger as the bases for PSA cost calculation
processing.
Assigning Cost Derivation Rules to PSCs and Products
This transaction is available to specify that certain transactional data should be blocked from being rolled
up from the JVA ledger to the PSC ledger.
This is useful if, for example, there are costs in JVA unrelated to PSA processing that need to be
excluded.
Assigning Rules to Determine Cost Data for Calculation Types
Use this transaction to assign validation rules to combinations of production sharing contracts (PSCs) and
production sharing accounting (PSA) products for specific calculation types. As the system copies
selected cost records from the source ledger into the PSA ledger during rollup, it uses validation rules to
assign calculation types to the cost records.
The calculation types assigned to cost records during rollup are used later during execution of the PSA
calculation process. These calculation types are used to select cost records from the PSA ledger for
specific types of cost calculation.
Assigning Products to PSCs
A PSC specifies how production volumes from various products should be shared between the parties
involved.
This transaction specifies which products are included in a PSC.
Assigning Calculation Schemes and Calculation Types to PSCs
This transaction allows you to assign calculation schemes, which comprise percentages to be applied to a
base amount for a range of production volumes, to calculation types.
By assigning calculation schemes to calculation types, you specify the order in which the system
processes calculations.
Assigning a PSC to Terminal
This transaction allow you to specify a combination production sharing contract (PSC), product, venture,
and equity type (ET) for a terminal.
Each terminal can have more than one combination of PSC, product, venture, and ET.
Executing PSA Rollup
This transaction allows you to copy cost data from the source ledger [usually the Joint Venture
Accounting (JVA) ledger] to the PSA ledger. The PSA ledger is a direct copy of the JVA ledger.
______________________________________________________________
SAP AG
34
SAP System
______________________________________________________________
As a result of this transaction, all costs are updated for all PSCs that are mapped to JVs in the JVA
company codes that are activated for PSA.
Further, the system assigns data from the JVA ledger to calculation types as well as production sharing
contracts and products.
Actual Production Data Entry
This transaction allows you to enter production volumes and prices for the month. Production volumes
are used as the bases for PSA calculations and prices are used when the system calculates production
revenues.
PSC Periods
The Opening PSC Periods transaction allows you to specify the fiscal year and periods that should be
opened for a particular company code in order to allow PSC transactions.
You can also use the Displaying PSC Periods transaction to display periods that are open.
Daily Data (Changed)
You can enter daily, transactional data into the system for pricing, production volumes, adjustments to
production volumes, and lifting
After daily data is entered, you use an interface to update monthly production and pricing data with the
daily data.
As of SAP R/3 Release 4.7 for Production Sharing Accounting, there are now five separate daily data
entry transaction: one for production, another for pricing, a third for adjustment data, a fourth for lifting
by PSC and a fifth for lifting by terminal.
Data Interfaces (Enhanced)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, the production interface is now available
as the existing interface to transfer volumes and prices to the volume input table.
Further, a new transaction, the Arms/Non-arms length transaction, is available for situations when
arms-length countries enter into special agreements that include unique pricing.
Also, a user-defined interface, the Malaysian Production Interface, is available. In addition, the Weighted
Average price transaction, which establishes the frequency with which the system calculates the selling
price, and the Crude Oil Entitlement Percentage (COEP) transaction, which applies the percentage to the
monthly production by PSC in order to identify the contractor share and the government share of
production, are available for use in conjunction with the Malaysian Production Interface.
Production Adjustments (New)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, you can enter production adjustments
(that is, gains or losses of production volumes) which have to be posted in the production volume table
with volume type PA.
Within the calculation only the Net Production is calculated.
Actual Entitlement Calculations
The Executing Actual Entitlements Calculations transaction allows you to execute the processing of
actual entitlements and to review the results, which are stated as volumes and amounts for the PSCs for
the various deductions.
______________________________________________________________
SAP AG
35
SAP System
______________________________________________________________
Further, you can reverse actual entitlement records.
Transferring Funds
This transaction allows you to transfer funds from one production sharing contract (PSC) to another on an
ad hoc basis, separate from the system's automated rollup of costs from the source ledger. The transfer
involves forwarding a credit amount from one PSC to another.
You would normally use manual transfer after initial calculations reveal excess profit in one PSC and a
cost carry forward condition in another PSC.
You can reverse a manual transfer if required. (For example, if you executed a manual transfer for a
combination of PSC and product in an accounting period and then subsequently needed to enter new cost
or volume data for the PSC or product, you would need to reverse the manual transfer in order to enter
the new cost or volume data.) Reversing a transfer involves executing two transfer reversals: one for the
receiver record, and one for the sender transfer record.
Entitlement Transfers (New)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, the system can execute transfers either
from one partner to another or from the contractor to the government.
Handling of Transfers (New)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, the system stores the transfer first in a
#pre-post# table which then becomes effective only when the calculation is posted.
The reason for this handling is that the prices for the production are not known at the time of entering the
entitlement transfer. Also handling for reversals is available.
Document Display by Period
This transaction allows you to review the results of PSC processing, organized by fiscal year and period.
Reporting (New)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, new features for reporting include the
capability to choose either the number of decimals or the scaling of amounts/volumes used for reporting
data, as well as the possibility to display "in kind" rather than "in value".
Further, the following new reports are available:
o
Production Data with Adjustments - Produces a report with an overview of production data with
adjustments
o
Lifting Data - Provides data about lifting, include the entitlement of each partner that is a contractor
for a PSC or a group of PSCs
o
Flat Prices - Provides details about prices per unit and corresponding periods
o
Adjustments - Provides an overview of adjustments to production volumes
o
Entitlement Calculation Printout - Displays the actual entitlement that was previously executed
o
Storage Entitlement Report - Displays an overview of total stock entitlement for the government and
each of the partners
o
Partner Entitlement Report - Provides details about the entitlement of each partner that is a
contractor for a PSC or for a group of PSCs
______________________________________________________________
SAP AG
36
SAP System
______________________________________________________________
o
Master Data Report - Provides an overview of PSC master data, including details such as the sign
date, the reporting frequency, and the ID of the person who created the master data
o
Partner List Report - Provides an overview of actual or planned quantities or amounts calculated for
a particular partner / PSC / product combination
o
Volumes by Volume Type - Provides an overview of production volume records.
Ledgers 4R and 4S (New)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, ledgers 4R und 4S are available. Ledgers
4R and 4S store information on a partner and category level. The postings to these ledgers include both
the government and operator portions.
Each calculation type (including production) is stored separately in the new ledgers and is split by partner
(including operator) and government.
Direct Partner Postings (Enhanced)
In SAP R/3 Release 4.6C for Production Sharing Accounting, the system transferred direct partner
postings JVA to PSA in 4.6C.
The split by partner is not executed for direct partner postings because the partner is already provided.
As of SAP R/3 Release 4.7 for Production Sharing Accounting, the calculation of the carry forward
differs from regular cost because the system recovers regular costs first and then recovers the direct
partner postings.
Carry Forward Year-End Balances (New)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, the Carry Forward Year-End Balances
transaction is available to carry forward balances to period zero of a new year.
This facilitates inception-to-date reporting. The carry forward is calculated for values as well as volumes.
Contractor/Government Split (Enhanced)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, the split between the contractor and the
government is no longer defined only in the sliding scale as it was in 4.6C.
The system now builds totals for all amounts, the total amount, the government amount, and the
contractor amount, rather than only the total amount as in 4.6C.
This enhanced functionality executes the government/contractors split only on the detail lines and sums
the total lines.
Sliding Scale Frequencies (Enhanced)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, the sliding scale frequencies tell the
entitlement calculation, not only the frequency but also the type of calculation. There are three new PSA
frequencies:
o
Cumulative production in volume
o
Cumulative production in value
o
Revenue/Cost Index
Volume Types (New)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, The following three volume types are
______________________________________________________________
SAP AG
37
SAP System
______________________________________________________________
new in PSA:
o
TP for Take or Pay
o
FG for Free Gas
o
PA for Production Adjustments
Equal Priority (New)
As of SAP R/3 Release 4.7 for Production Sharing Accounting, the equal priority function allows the
system to calculate the recovery and the carry forward across multiple calculation types. That is, the
system treats multiple calculation types as a unit.
Previously, all costs were recovered in the order of calculation type assignments
4.10 CA-DSG
Digital Signature
4.10.1 Digital Signature (extended)
Use
Since release 4.0A, the SAP system has provided digital signatures, to secure digital documents and
business processes. Previously, such digital signatures were only available for selected positions in the
SAP system. If a function was to be connected to further applications, the program code had to be
extended according to the application. This is very time consuming.
As of release 6.20, a standardized and flexible programming interface is available, with which the digital
signature can be connected to any areas in both R/3 systems and other systems, such as APO, CRM, etc.
In principle, no changes are made to the existing functions, and the following functions are added:
o
The document to be signed is called up by the relevant application and forwarded to the signature
tool. When the signature function is called up, the default values in the application decide if the
document to be signed should be managed by the application itself or by the signature function.
o
For signature strategies with several individual signatures, it is possible to run a verification on
executed signatures to check their validity. The verification is independent of whether or not the
document is managed by the signature function or the application.
o
The user has the option of displaying the document before the signature operation. (However, this is
currently only available for .txt type files.)
Effects on Customizing
To implement the digital signature for the required applications, you must perform the following
activities in the Customizing, after the upgrade:
o
Create the general user settings (see Defining Basis Settings for Digital Signature).
o
If you want to use the signatures without a signature strategy, create the corresponding settings (see
______________________________________________________________
SAP AG
38
SAP System
______________________________________________________________
Specify Signature Method for Approval using Simple Signature).
o
If you want to work with signature strategies, you must define authorization groups, individual
signatures and a signature strategy.
Further notes
For more information on the digital signature, see the following release information:
o
Digital Signature (for Release 4.0A)
o
Digital Signatures (for Release 4.5A)
o
Changes to the Digital Signature (for Release 4.6C)
______________________________________________________________
SAP AG
39
SAP System
______________________________________________________________
5 FI
Financial Accounting
5.1 Structure Changes for Country Version Brazil
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), there are a number of new and changed
activities in the Implementation Guide for activities relating to Brazil:
New Activities
Cross-Application Components -> General Application Functions -> Nota Fiscal -> Materials
Management -> Invoice Verification -> Maintain Movement Types for Vendor Invoices
Financial Accounting -> Financial Accounting Global Settings -> Tax on Sales/Purchases ->
Basic Settings -> Brazil ->
o
Define Sequence for Tax Law Determination
o
Assign Alternative Calculation Procedure per FI/MM Tax Code
o
Define Tax Types
o
Condition-Based Tax Calculation (see Release Note)->
-
Activate Condition-Based Tax Calculation
-
Map MM Tax Values to Nota Fiscal Fields
-
Map SD Tax Values to Nota Fiscal Fields
-
Map MM Tax Laws to Nota Fiscal Fields
-
Define Internal Codes for Tax Conditions
-
Assign Internal Codes for Tax Conditions to Condtion Types
-
Assign Tax Rate Tables to Condition Tables
Financial Accounting -> Financial Accounting Global Settings -> Tax on Sales/Purchases ->
Calculation -> Settings for Tax Calculation in Brazil ->
o
Access Tax Manager's Workplace (see Release Note)
o
Define Sequence for SD Tax Code Determination
o
Define Tax Groups for Dynamic Exceptions
o
Tax Rates -> Maintain SubTrib Dynamic Exceptions
Financial Accounting -> Accounts Receivable and Accounts Payable -> Business Transactions
-> Interest Calculation -> Interest Calculation -> Maintain Interest Rates for Vendor Operation
(Brazil)
Changed Activities
Cross-Application Components -> General Application Functions -> Nota Fiscal ->
______________________________________________________________
SAP AG
40
SAP System
______________________________________________________________
o
CGC Branches has been renamed to CNPJ Business Places to comply with new terminology
(see Release Note), and within the Define Business Places activity, the regional tax codes have
been redefined as state tax numbers.
o
NBM Codes has been renamed to NCM Codes
Financial Accounting -> Financial Accounting Global Settings -> Tax on Sales/Purchases ->
Calculation -> Settings for Tax Calculation in Brazil ->
o
Additional Standard Tax Codes has been renamed Define FI/MM Tax Codes
Through Release 4.6C, you had to customize tax codes in three different activities. First you had to
maintain the conditions of the tax code under Financial Accounting -> Financial Accounting
Global Settings -> Tax on Sales/Purchases -> Calculation -> Define Tax Codes for Sales
and Purchases (transaction FTXP), where you specified whether the tax code was for input or
output tax. Then, you had to maintain additional Brazil-specific information under Calculation ->
Settings for Tax Calculation in Brazil -> Additional Standard Tax Codes. Finally, for the
automatic determination of tax code in stock transfer processes, you had to map in table T007_IT
the SD tax codes (created in SD Tax Code activity in the same menu) to the incoming and
outgoing tax codes.
As of Enterprise, the Define FI/MM Tax Codes activity has a new view assigned to it, which
enables you to maintain all the fields mentioned in the three previously required activities in a single
line. In addition, table T007_IT has been replaced by the new Brazil-specific table J_1BT007.
o
Tax Rates
-
Dynamic Exceptions - Grouping has been renamed Define Tax Groups for Dynamic
Exceptions, and is no longer under Tax Rates , but one level higher in the IMG structure.
The tax groups have been enhanced so that you can now assign up to three key fields
(previously only one) for defining dynamic exceptions.
-
The individual tax rate tables have been renamed and grouped together as follows, based on
the example of IPI:
- IPI (Normal) renamed to Maintain IPI Values
- IPI (Exceptions) renamed to Maintain IPI Material-Dependent Exceptions
- Dynamic Exceptions - IPI renamed to Maintain IPI Dynamic Exceptions
-
Each of the dynamic exceptions tables have been enhanced so that they now can contain up to
three dynamic value fields, based on the Customizing of the tax group assigned to each entry.
5.2 Country Version India in Standard R/3 System
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), Country Version India is no longer delivered as
an add-on but as part of the standard R/3 System.
Integration of functions in the SAP Easy Access menu
The functions for withholding tax have been integrated into the SAP Easy Access menu, under
Accounting -> Financial Accounting -> Accounts Payable -> Withholding Tax -> India and
Accounting -> Financial Accounting -> Accounts Receivable -> Withholding Tax -> India.
______________________________________________________________
SAP AG
41
SAP System
______________________________________________________________
You can access all other functions using the area menu J1ILN, which you can call from the SAP Easy
Access screen using the transaction code J1ILN.
Country Version India Implementation Guide
The Country Version India Implementation Guide (IMG) has been integrated into the standard Reference
IMG (see Changes to Structures for Country Version India).
Release Notes
You can access release notes from previous add-on releases using the links below.
SAP Library Documentation
The SAP Library documentation for Country Version India is also delivered on the standard SAP Library
documentation CD (see below).
New and Changed Functions
For information about new and changed functions for Country Version India, see the other release notes
for this release.
Effects on Existing Data
You do not need to change any data.
Effects on Customizing
IMG activity
What to do
Activate Country Version India for Specific Fiscal Years Delete the entry ZIND and create a new
entry for IND.
See also
SAP Library -> Financials or Logistics -> Country Versions -> Asia-Pacific -> India.
Release Notes from Country Version India Add-On (FI)
Release Notes from Country Version India Add-On (SD)
Release Notes from Country Version India Add-On (MM)
5.3 Accessible: Financial Accounting (Modified)
Use
Note the following with regard to the accessibility of Financial Accounting in the SAP System:
Accounts Payable Accounting
o
To make displaying or confirming changed vendor master records accessible, use transction FK08
instead of transaction FK09.
Posting
o
To make posting to G/L accounts accessible, use the standard transaction for G/L postings (F-02)
______________________________________________________________
SAP AG
42
SAP System
______________________________________________________________
instead of the Enjoy transction (FB50).
o
To make posting an invoice accessible, use the standard transactions for invoice postings (F-43,
F-22) instead of the Enjoy transactions (FB60, FB70).
o
To make posting a credit memo accessible, use the standard transactions for credit memo postings
(F-41, F-27) instead of the Enjoy transactions (FB65, FB75).
Parking
o
To make document parking in G/L accounts accessible, use the standard transaction for G/L account
parking (F-65) instead of the Enjoy transaction (FV50).
o
To make parking an invoice accessible, use the standard transactions for invoice parking (F-63,
F-64) instead of the Enjoy transactions (FV60, FV70).
o
To make parking a credit memo accessible, use the standard transactions for credit memo parking
(F-66, F-67) instead of the Enjoy transactions (Fv65, FV75).
Document Lists
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the document overviews have been changed over
to ALV Grid. To access the new lists, choose Select Document List as normal from the posting and
parking transactions (FB03, FBV3, FBU3). As standard, the accessible view of the document lists is
displayed.
This changeover also applies to the list display in the balance control for FB01, FBV1, FB10 and for
incoming payments (FB05, FBZ1), which you choose via Overview.
Accounting Editing Options
o
To make entering a document accessible, you can preconfigure the document overview as ALV grid
control. To do this, set the indicator Document Overview as ALV Grid Control on the tab page
Document Entry in transaction FB00.
o
To make displaying a document accessible, choose As ALV Grid Control on the tab page
Document Display in transaction FB00.
Tables
To make navigating in tabular displays accessible, the individual table cells have been named. The table
values can therefore be assigned uniquely.
See also
For general information about the accessibility of the SAP System, see the SAP Library -> Getting
Started: Accessibility Supplement.
______________________________________________________________
SAP AG
43
SAP System
______________________________________________________________
5.4 Condition-Based Tax Calculation (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), a new method for calculating taxes in Brazil
is available, which makes use of the standard condition technique. Tax rates, tax laws, and special
indicators that influence whether tax line items are included in the nota fiscal are all stored in the system
as condition records. An additional tax calculation procedure, TAXBRC, is delivered for this new
method, in addition to the existing one for Brazil, TAXBRJ.
Effects on Existing Data
You can continue to calculate taxes using the former method: when the system processes the tax
procedure assigned to the country (TAXBRJ), it calculates the taxes externally by calling function
module J_1BCALCULATE_TAXES. We do, however, recommend that you assign the new procedure
TAXBRC and use the condition-based tax calculation functions, as it enables you to flexibly adapt the tax
calculation logic to cover new legal requirements or special customer needs.
You will need to migrate your existing tax rate table entries to condition records, which you can do
directly from the Tax Manager's Workplace described below. You can check all tables and subsequently
convert the entries, whereby the system generates condition records. After the initial migration, each time
you create or change a tax rate table entry, the system automatically generates a condition record as
needed.
Effects on Customizing
If you want to employ the new condition-based tax calculation, you need to activate it and carry out all
related Customizing activities, under Financial Accounting -> Financial Accounting Global Settings
-> Tax on Sales/Purchases -> Basic Settings -> Brazil -> Condition-Based Tax Calculation, all of
which are new:
o
Activate Condition-Based Tax Calculation
o
Map MM Tax Values to Nota Fiscal Fields
o
Map SD Tax Values to Nota Fiscal Fields
o
Map MM Tax Laws to Nota Fiscal Fields
o
Define Internal Codes for Tax Conditions
o
Assign Internal Codes for Tax Conditions to Condtion Types
o
Assign Tax Rate Tables to Condition Tables
In addition, you need to assign the new tax calculation procedure TAXBRC to the country in
Customizing, under Financial Accounting -> Financial Accounting Global Settings -> Tax on
Sales/Purchases -> Basic Settings -> Assign Country to Calculation Procedure.
A new Customizing tool called the Tax Manager's Workplace is available that enables you to make all
tax-related settings for Brazil. You access it under the same path as above through Tax on
Sales/Purchases, then Calculation -> Settings for Tax Calculation in Brazil -> Access Tax
Manager's Workplace , or alternatively by entering transaction J1BTAX. You can use the Tax Manager's
Workplace regardless if you use condition-based tax calculation; it simply brings all tax activities to a
single transaction (only the Migration, Nota-Fiscal Mapping, and Condition Mapping options under the
______________________________________________________________
SAP AG
44
SAP System
______________________________________________________________
Condition Setup pulldown menu are relevant only for condition-based tax calculation).
5.5 Terminology for Country Version Brazil (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following Brazilian terms have been
updated in the system:
o
Branch has been renamed business place
o
NBM code has been renamed NCM code
o
CGC has been renamed CNPJ number
5.6 Data Medium Exchange Engine (Changed)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following new features have been added
to the Data Medium Exchange Engine (DMEE):
o
DMEE for incoming files
The main application of incoming files is in conjunction with the electronic account statement.
DMEE converts an incoming account statement file to a new file in MultiCash format, which the
system can then process further (for instance, automatic posting and clearing).
o
Version management
DMEE can store different versions of a format tree, including temporary versions, which you can
then compare. SAP delivers version 000 (active version) and version 999. You cannot change
version 999; it serves as a reference version.
o
Business Add-Ins
Additional Business Add-Ins cover specific requirements not cannot be handled by the standard
DMEE functions.
SAP delivers format trees in the application areas listed below. These format trees can be used to generate
files without any further configuration in DMEE. In addition, you can use the format trees as templates to
create new trees to cover any regional or bank-specific formats not supported by SAP. Furthermore, two
example trees SAP_EXAMPLE are delivered for the tree types PAYM and MCSH.
o
Payment program
DMEE format trees now cover most of the standard formats previously supported by SAP as
individual file generation programs (RFFO*). These new format trees enable you to us the
additional features of the Payment Medium Workbench (PMW), such as the flexible configuration
of the note to payee.
The following format trees are delivered in this release for the first time:
______________________________________________________________
SAP AG
45
SAP System
______________________________________________________________
Country
Australia
Format tree
AU_BECS
AU_BECS_B
Belgium
BE_BEPDTA
BE_DOM80
Finland
FI_A_AUTOGIRO
FI_LUM2
LM03
TS
France
FR_ETEBAC_VRT-DOM
FR_ETEBAC_VRT-ETR
Hong Kong Special Administrative Region AUTOPLAN1
Netherlands
DMEE_BTL91
CLIEOP03
New Zealand
NZ_MTS
Portugal
PS2
Republic of Ireland
IE_AIB
IE_BOI
South Africa
ACB_ZA
Sweden
SE_A_AUTOGIRO
SE_BANKGIROT
SE_POSTGIROT
SE_UTLI_SISU
United Kingdom
GB_BACS
o
Withholding tax reporting
DMEE format trees are available for creating withholding tax returns as a DME file in the following
countries:
Country
France
South Korea
United Kingdom
United States
o
Format tree
IDWTFILE_FR_DAS2
KR_BUSINESSINCOME
IDWTFILE_UK_CIS23E
IDWTFILE_UK_CIS25E
IDWTFILE_UK_CIS36E
IDWTFILE_UK_S16TMA
IDWTFILE_US_1042
IDWTFILE_US_1099
Value-added tax (VAT) reporting
DMEE format trees TW_GUI_403 and TW_GUI_DETAIL are provided for VAT reporting in
Taiwan.
______________________________________________________________
SAP AG
46
SAP System
______________________________________________________________
See also
For more information, see the SAP Library -> Financials -> Financial Accounting (FI) -> Accounts
Payable (FI-AP) -> FI Accounts Receivable and Accounts Payable -> Payments -> Executing
the Payment Program -> Payment Medium Workbench -> Data Medium Exchange Engine.
Alternatively, go to transaction DMEE and choose Help -> Application help.
5.7 Structure Changes in the FI Implementation Guide (IMG)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following changes apply to the Financial
Accounting Implementation Guide (IMG):
The following IMG activities have been added:
Financial Accounting Global Settings
o
The section Accrual Engine has been added
o
The section Parallel Reporting has been added under Company code.
General Ledger Accounting
o
Under Business Transactions, the section Manual Accruals has been added.
o
Under Business Transactions, the section Provisions for Awards has been added.
o
Under Business Transactions -> Closing -> Closing/Opening Postings (Only certain
countries), the IMG activity Define Account Determination has been added.
Special Purpose Ledger
o
Under Actual Posting -> Settings for Accounting Integration -> Document Split-> Additional
Activities, the following IMG activities have been added:
-
Define Business Transaction
-
Define Split Procedure
-
Define Constants
Define Split Rules
Accounts Receivable/Accounts Payable Accounting
o
o
Under Internet Services -> Edit Internet Addresses, the following IMG activities have been
addes:
-
Edit URL Type
-
Edit URL Address
Under Business Transactions -> Interest Calculation, the note Print has been added with the
following IMG activities:
-
Define Interest Forms (with SAPScript)
-
Assign Forms for Interest Indicator (Reassigned)
______________________________________________________________
SAP AG
47
SAP System
______________________________________________________________
-
Define Sender Details for Interest Forms
o
Under Business Transactions -> Outgoing Payment -> Automatic Outgoing Payment ->
Payment Media, the IMG activity Define Identification for Cross-Payment Run Payment
Media has been added.
Bank Accounting
o
Under Business Transactions -> Payment Transactions -> Electronic Account Statment, the
following IMG activities have been added:
o
o
-
Configure Returns Processing
-
Business Add-In: Processing Returns
Under Business Transactions -> Payment Transactions, the node Online Payments has been
added with the following IMG activities:
-
Define Process Steps
-
Define Document Types
-
Define Identification for Cross-Payment Run Payment Media
Under Business Transactions -> Payment Transactions -> Payment Order, the IMG activity
Define Clearing Accounts for Cross- Country Bank Account Transfers has been added.
The following IMG activities have been renamed:
Financial Accounting Global Settings
o
Under Withholding Tax -> Extended Withholding Tax -> Basic Settings, the following IMG
activity has been renamed:
-
Define Official Withholding Tax Key
(previously: Define Official Withholding Tax Code)
5.8 Release Notes from Country Version India Add-On (FI)
Use
The Release Notes from Releases 3.0A and 4.0A of Country Version India for Financial Accounting (FI)
are listed below. For more Release Notes, see the alias globalization in SAPNet, and choose Media
Center -> Country-Specific Documentation -> Country Version India - Release Notes.
Release 3.0A
o
Copy Invoice Reference
o
Profit Center Posting
o
One-Time Vendors
o
Annual Returns
o
Copying House Banks to TDS Documents
o
Challan Update
______________________________________________________________
SAP AG
48
SAP System
______________________________________________________________
o
Certificate Printing
o
Tax Adjustment
o
Customer Tax Clearing
o
Tax on Services
o
Tax Adjustment on Down Payment Clearing
o
Payment Due Dates
Release 4.0A
o
Challan Update Program
o
Reversal of TDS
o
Certificate Printing Program
o
PAN for One-Time Vendors
o
Business Area Posting for TDS Provisions
o
Migration from Classic to Extended Withholding Tax
o
Health Check for Withholding Tax Migration
o
Annual Returns for Extended Withholding Tax
o
Cash Journal Postings
o
Withholding Tax on Interest Payments to Customers
o
Challan Update for Withholding Tax on Inerest Payments to Customers
o
Certificate Printing for Witholding Tax on Customers
o
MIS Report for Withholding Tax
o
Customizing Settings for Income Tax Act
o
Asset Accounting: Customizing Settings
5.9 Payments with the Orbian payment system (enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can use automatic discounting for
payments with the Orbian payment system.
It has been possible to process payments with the Orbian payment system since R/3 4.6C with Support
Package 20.
The Orbian payment system offers you a new electronic means of payment that you can process in the
Internet and that represents an alternative to the traditional payment process. Its distinguishing feature is
that combines a means of payment in the form of Orbian Credits and a financial instrument in the form of
Primary Orbian Credits.
______________________________________________________________
SAP AG
49
SAP System
______________________________________________________________
Integrating the Orbian payment system does not entail changes to the standard functions of the payment
program and the electronic bank statement in the SAP system.
With transaction FBWO you can discount Orbian Credits if so required before their due date. The SAP
List Viewer (ALV) functions support you in this if you carry out the following discounting process steps:
o
Choose the Orbian Active Accounts from which you wish to discount cash amounts
o
Assign the amounts to the corresponding house bank accounts
o
Start discounting and create a file with payment data in Orbian format
You can then transfer this file to the Orbian payment system.
See also
You can find additional information in the documentation which you receive as user of the Orbian
payment system.
5.10 Plants Abroad (Enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the restriction on plants abroad is lifted. This
restriction prevented the use of tax calculation with jurisdiction codes in the same client in a company
code.
You can now use tax calculation with jurisdiction code and the function plants abroad for company codes
within one client.
You can use the plants abroad function for company codes that are assigned to a country that uses the tax
calculation without jurisdiction code. This means a country that uses tax calculation with jurisdiction
code cannot have a plant abroad, and a plant abroad cannot be situated in such a company.
See also
For more information, see the SAP Library under Taxes -> Tax on Sales/ Purchases -> Current Settings
and Implementation Guide -> Plants Abroad.
5.11 Changes to Structures for Country Version India
Use
As of SAP R/3 4.7, Country Version India is no longer delivered as an add-on, but forms part of the
standard system.
SAP has discontinued the Country Version India Implementation Guide (IMG) and has added its
activities have been added to the standard Reference IMG as follows:
Activities relating to withholding tax are now located in Customizing for Financial Accounting (FI),
under Financial Accounting Global Settings -> Withholding Tax.
______________________________________________________________
SAP AG
50
SAP System
______________________________________________________________
Activities relating to excise duty and excise invoices are in Customizing for Logistics - General, under
Tax on Goods Movements -> India.
As far as the activities under Preparatory Activities are concerned, two of them (Activate Country
Version India for Accounting Interface and Activate Processes) are no longer relevant and have been
removed from the IMG entirely. The activity Execute Country Installation Program is already included in
the standard IMG under the name Localize Sample Organizational Units. And the other two activities
(Activate Country Version India for Specific Fiscal Years and Activate Business Transaction Events)
have been added to the standard IMG.
For information about other changes to the IMG relating to changes in the functions in Country Version
India, see the other release notes.
5.12 FI-GL
General Ledger Accounting
5.12.1 Valuation Posting (Enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the valuation posting FBB1 to post
directly to subledger accounts (account type = D, K). However, you cannot enter terms of payment or tax
amounts.
5.12.2 Manual Accruals (New)
Use
From SAP R/3 Enterprise Financials Extension 1.10 (EA_APPL 110), the Manual Accruals component
allows you to calculate and post accruals automatically in General Ledger Accounting, for example for
license fees, rent payments or rent income. You can also vary the accrued amounts for the various periods
involved.
The calculation and posting of accruals can be performed according to a freely definable number of
accounting principles (parallel valuation methods). You have the option of defining your own calculation
methods to calculate accruals.
The Manual Accruals component has integrated reporting with a connection to the Business Information
Warehouse (BW). You can also simulate future accruals in a simulation program.
Effects on Customizing
Before you can implement Manual Accruals, you have to make extensive Customizing settings. You can
find the Customizing settings in the SAP Reference IMG under Financial Accounting -> General
Ledger Accounting -> Manual Accruals.
______________________________________________________________
SAP AG
51
SAP System
______________________________________________________________
5.12.3 Parallel Valuation Methods (Changed)
Use
From SAP R/3 Enterprise Financials Extension 1.10 (EA_APPL 110), you have the option of using two
new solution scenarios for parallel valuation methods in your SAP system.
Previously you had the following options for depicting parallel valuation methods:
Bisher hatten Sie folgende Möglichkeit, eine parallele Rechnungslegung abzubilden:
o
Depiction using additional accounts
You can create additional accounts. All postings that are the same for all accounting principles are
made to joint accounts. On the other hand, postings that differ according to accounting principle are
posted to a specific account area.
You now have extra options as follows:
o
Depiction using an additional company code
You can create an additional company code. This procedure is supported by certain reports in
Financial Accounting (FI) and Asset Accounting (FI-AA).
o
Depiction using an additional ledger
You can depict a parallel valuation method in your SAP system by defining an additional ledger in
the Special Ledger application component. You then assign your additional (parallel) accounting
principle to this additional ledger. This ensures that postings that are the same for both accounting
principles are posted to both the general ledger and to the additional ledger.
The posting data that differs according to accounting principle is posted to either the general ledger
or the additional ledger, depending on the accounting principle.
With all solution scenarios, it is possible to depict more than two accounting principles. This means that
you could, for example, also define two additional ledgers or create two additional company codes.
Effects on Existing Data
If you have already set up a parallel valuation method or methods, you can still use this procedure
without restrictions.
Effects on Customizing
To depict a parallel valuation method using an additional ledger, you have to make various settings in
Customizing: You can find the setting in Customizing, under Financial Accounting -> Financial
Accounting Global Settings -> Company Code -> Parallel Valuation Methods -> Accounting
Principles and Additional Ledgers.
At this point in Customizing, the IMG activities are also grouped together from the various SAP
application components that you need to be able to depict a parallel valuation method.
See also
For detailed information on depicting Parallel Valuation Methods, see the SAP Library, under
Accounting -> Financials -> General Ledger Accounting -> Parallel Valuation Methods.
______________________________________________________________
SAP AG
52
SAP System
______________________________________________________________
5.12.4 Provisions for Awards (New)
Use
In SAP R/3 Enterprise Financials Extension 1.10 (EA_APPL 110), the Provisions for Awards component
allows you to calculate and post provisions automatically for incentive schemes (such as stock option
programs). The calculation and posting of provisions can be performed according to a freely definable
number of accounting principles (parallel accounting).
Reporting in Provisions for Awards provides you with the following functions:
o
Predefined SAP reports
o
Connection to the Business Information Warehouse (BW)
o
Simulation of future provisions
Effects on Data Transfer
The Provisions for Awards component is connected with the SAP components HR (component
Long-Term Incentives) and Treasury:
o
You take over all data that affects the granting of awards to individual employees from the HR
component Long-Term Incentives..
o
The Long-Term Incentives component takes over the data that you need to valuate the awards with a
price from the Treasury component..
o
Effects on System Administration
To be able to transfer data from HR and Treasury, you have to set up the data transfer from HR. You
make these settings in Provisions for Awards Customizing. To make these settings, however, you need
special authorizations for the HR system.
Effects on Customizing
Before you can implement Provisions for Awards, you have to make extensive Customizing settings. You
can find the Customizing settings in the SAP Reference IMG under Financial Accounting -> General
Ledger Accounting -> Business Transactions -> Provisions for Awards.
See also
For detailed information on Provisions for Awards, see the SAP Library, under Accounting -> Financial
Accounting -> General Ledger Accounting -> Provisions for Awards.
5.12.5 FI-GL-GL
Basic Functions
5.12.5.1 Document Overview in the ALV List for Document Entry/Parking (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can display the document in the overview as
an ALV list when you are entering or parking documents. The variants are not copied from the previous
______________________________________________________________
SAP AG
53
SAP System
______________________________________________________________
display.
You make the setting in the editing options for document entry.
5.12.5.2 Displaying Parked Documents (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), in the FI Enjoy transactions (Vendor Parking),
you can display parked documents as they were entered in the corresponding transactions. You cannot
change or post the document in the display.
You still call up parked documents via transaction FBV3. The system recognizes whether the document
was entered with the classic parking transaction FBV1 or an FI Enjoy transaction.
You display documents entered using the classic parking transaction via the display transaction FBV3.
See also
Displaying classic parked documents: Transaction FBV3.
5.12.5.3 Entering Long Texts in the FI Enjoy Transactions (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can enter a long text for each G/L account
item via @0J@ with Quickinfo Long Text when you enter or park an accounting document in an FI
Enjoy transaction (Vendor Parking).
The symbol @0J@ with Quickinfo Long Text shows that a long text exists for a G/L account item.
5.12.5.4 Personalized Tree (Changed)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), working with account assignment templates and
screen variants in the FI Enjoy transactions (for example, Vendor Invoice Entry) is much easier. As a
result of a complete personalization, the user only receives his user-specific list of account assignment
templates and screen variants. He can process this list using the context menu.
To activate the personalized tree, choose the templates within the transaction (tree on the left hand side).
You can process the individual entries and the folder via the context menu (right mouse button):
o
Add entries
o
Remove entris
o
Empty folder
______________________________________________________________
SAP AG
54
SAP System
______________________________________________________________
In addition, the tree settings (folders open/closed) are saved specific to the user so that when you open a
folder, it is open the next time you start the transaction.
The settings are saved separately for vendor/G/L account/customer transactions.
See also
For more information, see notes 430830 and 425554 and the Help Portal (http://help.sap.com) under SAP
R/3 Enterprise Core 4.70 (SAP_APPL 470) -> Search (menubar) -> Search term: Screen variant.
5.12.5.5 Generic Object Services for FI Document Display Transactions
(Extended
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system automatically provides you with the
correct business object type (for example, FIPP, BKPF, BSEG) when you call up the menu path System
-> Object Services. You no longer have to select a relevant business object.
The object services now also work for FI documents that have already been archived. Prerequisite for this
is that the referred objects (attachments, links, and so on) still exist in the system (database).
You can call up the generic object services via System -> Object Services or via the symbol in the upper
left of the title bar. The object services within the FI document display transactions (transactions FB02,
FB03, FBV3, FBV2) offer functions that are available in different applications and that are uniform
across the system. With these functions, additional services for business objects are offered, for example,
creating a note for a business object. In particular, the generic services are used to display links to the
optical archive ('Attachment list').
To use services for object BSEG (accounting item for FI document), you first have to switch to the item
screen of the document display (for example, to display workflows for object BSEG; this is relevant for
the payment release approval workflow).
The attachment list can only be called up if the user has display authorization for all items of a document
within the document display. If this is not the case, the user is denied access to the attachment list (and
therefore, to the optically archived incoming invoices and so on).
See also
For more information, see Application Connection to the Object Services.
5.12.5.6 ALE remote comparison for distributed FIDCC1/2 - FI-GL (enhanced)
Use
All FI documents of the activated company code are transferred from the decentralized sender system to
the central receiver system using the ALE message types FIDCC1 and FIDCC2 (IDoc FIDCCP01 or
FIDCCP02). In the central system, the FI application is updated, that is, the FI documents, the general
ledger in GLT0, and the subledger.
______________________________________________________________
SAP AG
55
SAP System
______________________________________________________________
If all the data was transferred succesfully, the general ledger data in ledger 00 of table GLT0 must agree
in the sender and receiver system for a company code.
Previously, this could not be checked using SAP standard methods.
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use transaction GCAR to carry out a
ledger comparison across more than one system.
This enables you to check whether the general ledger data from the decentralized systems was completely
transferred to the central general ledger with ALE.
Effects on Existing Data
In order for you to use the comparison tool GCAR, an ALE comparison ledger must exist in the central
system. This ledger must be stored in table GLFUNCT, because in addition to the G/L-relevant account
assignments, the logical system LOGSYS can also be stored there.
If the COS ledger 0F is updated in the standard, this can operate as the ALE comparison ledger and be
specified in transaction GCAR.
If you want to update a separate ALE comparison ledger, you have to create this ledger, and, via the
BAdI definition F050S008, BAdI method ALE_COMPARE_LEDGER_UPDATE, inform the system of
the ledger name so that it can be updated.
See consultant note 517580.
Effects on Customizing
If you use your own ALE comparison ledger, you have to carry out the following activities in the central
system; see note 517580:
o
Create the ALE comparison ledger in GLFUNCT. The ledger name must start with 'Z'.
o
Assign the ALE comparison ledger to all ALE company codes; required for transaction GCAR.
o
Implement BAdI definition F050S008 with SE19 and inform the system of the name of the ALE
comparison ledger. This triggers the update of the ALE comparison ledger.
o
At random intervals, start the ALE comparison tool, specifiying the ledgers to be compared:
Specify the ALE comparison ledger as the base ledger (0F or own ledger)
In the sender system speciy the general ledger 00 as the comparison ledger and specify the name of
the logical sender system. Select 'Remote comparison'.
See also
When you call up GCAR, any differences between the ledgers are listed.
5.12.5.7 Tax Invoices and VAT Reporting (Changed)
Use
As of SAP R/3 Release 4.70, the functions for creating, tracking, and reporting tax invoices as used in
South Korea have been enhanced as follows:
o
You now print tax invoices without generating a clearing document.
o
The reporting solution has been changed.
Reports RFUMSV45 (VAT summary in the official format) and RFUMSV49 (VAT summary for
controlling purposes) have been replaced.
______________________________________________________________
SAP AG
56
SAP System
______________________________________________________________
The new reports are RFUMSV45R, which fulfills the same purpose as its predecessor; and
RFUMSV49R, which you use to time-stamp the tax invoices before running RFUMSV45R.
Nor do you have to use the Advance Return for Taxes on Sales/Purchases report anymore. Report
RFUMSV45R fulfills all statutory VAT reporting requirents.
o
The terminology has been redefined.
Tax offices are now referred to more correctly as district tax offices, and regional tax offices are
now referred to as local tax offices.
Effects on Existing Data
Migrate all tax invoices that you created in previous releases and which you have not yet reported to the
authorities in the VAT Summary Report using the Migrate Tax Invoices program.
If you are upgrading from a release before 4.5B (from the Country Version South Korea add-on), migrate
your tax invoices as follows:
1.
Download program RFIDKRMIG1 from SAPserv (see SAP Note 385850).
2.
Migrate the tax invoices from the add-on.
5.12.5.8 Advance Return for Tax on Sales and Purchases (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create your advance return for tax on
sales and purchases with report RFUMSV00 in XML (Extended Mark-Up Language). You receive an
XML file that you can process further in order to send it to the relevant tax authorities. XML offers a
flexible alternative to the statistical, propietary formats currently used for data transfer in several
countries.
With XML, you can easily adapt your data to the requirements and formats of the respective national tax
authorities. You do this by creating an appropriate stylesheet. You then send the data to the tax authority
electronically.
See also
For more information, see the SAP Library under Accounting -> Financial Accounting -> Financial
Accounting General Topics (FI) -> Taxes (FI-AP/AR)-> Tax on Sales/Purchases, Sales Taxes, and
Additional Taxes -> Advance Return for Tax on Sales/Purchases with XML and the documentation for
report RFUMSV00.
5.12.5.9 Condition-Based Excise Determination in MM (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system can calculate excise duties and sales
tax in Materials Management (MM) using the standard condition technique.
SAP has enhanced the existing tax procedure, TAXINJ, so that it now supports formula-based and
condition-based excise determination. The R/3 System also comes with a new tax procedure, TAXINN,
______________________________________________________________
SAP AG
57
SAP System
______________________________________________________________
which only handles condition-based excise determination.
Which Tax Procedure Must I Use?
Existing customers must continue to work using the same tax procedure.
If you switch to a new tax procedure, you cannot display any documents that you have already posted
using the old tax procedure.
If you have worked with formula-based excise determination in previous releases and wish to continue,
you do not have to do anything. However, if you wish to start using the condition-based excise
determination method, proceed as specified below.
We recommend that new customers use the condition-based excise determination and tax procedure
TAXINN.
How Do the New Functions Work?
First, customize the system in the activities listed below. Then, for each material, create one condition
record for each form of excise duty and sales tax that applies, and enter the tax code for purchasing
documents (see below) in every condition record.
When you come to create a purchase order, enter the tax code in each line item. The tax code tells the
system whether to look in the condition types for formula-based or condition-based excise determination.
Effects on Existing Data
Existing customers can leave all of their existing vendor master data and material master data as it is.
When you have to enter new excise rates, you can use either the Excise Rate Maintenance transaction for
formula-based excise determination or create condition records as described above if you want to use
condition-based excise determination.
When you come to create a purchase order, the system determines on the basis of the tax code in the line
item whether to use formula-based or condition-based excise determination. This way, you can use both
methods concurrently, and even within the same purchasing document.
No tool is available for migrating the excise data from the old method to the new one.
Effects on Customizing
To set up the new excise determination method, carry out the following activities:
IMG activity
What to do
Check Calculation Procedure
Existing customers: Adjust your tax procedure to
match the changes to TAXINJ. Steps 560-583 are new, as are 593-598.
New customers: Create a copy of TAXINN.
Select Tax Calculation Procedure
New customers only: Assign the copy of TAXINN to
India.
Maintain Excise Defaults
New customers only: Enter the condition type that you
use for countervailing duty.
Define Tax Code for Purchasing Documents Define a tax code.
Assign Tax Code to Company Codes
Assign the tax code to the company codes that it is
relevant for.
______________________________________________________________
SAP AG
58
SAP System
______________________________________________________________
Classify Condition Types
Specify which condition types you want to use for
condition-based excise determination.
Define Tax Accounts
Check which G/L accounts the various taxes will be
posted to. Define G/L accounts for the account keys used in the tax procedure.
See also
SAP Library -> Logistics -> Country Versions -> India -> Materials Management (MM) ->
Condition-Based Excise Determination.
5.12.5.10 FI-GL-GL-MD
Master Data
5.12.5.10.1 Chart of Accounts and Financial Statement Version (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the country template for India comes with a chart
of accounts and a financial statement version specifically for use by companies with operations there.
Effects on Existing Data
We recommend that if you set up a new company code for a company in India, you use this chart of
accounts and financial statement version as the basis for creating your own.
Effects on Customizing
If you want to work with the new settings, carry out the following IMG activities:
IMG activity
Master Data
your own specific needs
Define Financial Statement Versions
it as necessary
What to do
Copy the chart of accounts CAIN and adjust it to meet
Copy the financial statement version BAIN and adjust
See also
SAP Library -> Financials -> Country Versions -> Asia-Pacific -> India -> Financial Accounting
(FI) -> General Ledger Accounting (FI-GL).
5.12.5.11 FI-GL-GL-AP
G/L Account Posting
5.12.5.11.1 Changing Last Adjustment Dates in Line Items (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the Change Last Adjustment Dates
program to change the last adjustment dates of individual line items.
______________________________________________________________
SAP AG
59
SAP System
______________________________________________________________
SAP has added two new fields to the selection screen, where you enter the number and fiscal year of the
document that contains the line item that you want to change.
Since the program now covers line items as well as G/L accounts, its name has also changed from Reset
Inflation Master Records per G/L Account to Change Last Adjustment Dates.
See also
SAP Library -> Financials -> Financial Accounting (FI) -> General Ledger (FI-GL) -> Closing and
Reporting (FI) -> Preparing Financial Statements -> Inflation Accounting -> Inflation Adjustment
of G/L Accounts -> Changing of Last Adjustment Dates.
5.12.5.12 FI-GL-GL-CL
Closing Operations
5.12.5.12.1 Chart of Accounts and Financial Statement Version (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the country template for India comes with a chart
of accounts and a financial statement version specifically for use by companies with operations there.
Effects on Existing Data
We recommend that if you set up a new company code for a company in India, you use this chart of
accounts and financial statement version as the basis for creating your own.
Effects on Customizing
If you want to work with the new settings, carry out the following IMG activities:
IMG activity
Master Data
your own specific needs
Define Financial Statement Versions
it as necessary
What to do
Copy the chart of accounts CAIN and adjust it to meet
Copy the financial statement version BAIN and adjust
See also
SAP Library -> Financials -> Country Versions -> Asia-Pacific -> India -> Financial Accounting
(FI) -> General Ledger Accounting (FI-GL).
5.12.5.12.2 Changing Last Adjustment Dates in Line Items (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the Change Last Adjustment Dates
program to change the last adjustment dates of individual line items.
SAP has added two new fields to the selection screen, where you enter the number and fiscal year of the
______________________________________________________________
SAP AG
60
SAP System
______________________________________________________________
document that contains the line item that you want to change.
Since the program now covers line items as well as G/L accounts, its name has also changed from Reset
Inflation Master Records per G/L Account to Change Last Adjustment Dates.
See also
SAP Library -> Financials -> Financial Accounting (FI) -> General Ledger (FI-GL) -> Closing and
Reporting (FI) -> Preparing Financial Statements -> Inflation Accounting -> Inflation Adjustment
of G/L Accounts -> Changing of Last Adjustment Dates.
5.12.5.12.3 Accumulated Balance Audit Trail (Modified)
Use
From Release 4.70, the reports for the accumulated balance audit trail for classic sorting (RFKLET00)
and open item sorting (RFKKET00) are summarized in one report (RFKLET01).
The new report gives you the following advantages:
o
Superfluous selection parameters are removed
o
The dataset is always stored in the database tables
You can access the new report from the SAP Easy Access screen under Accounting -> Financial
Accounting -> General Ledger -> Periodic Processing -> Closing -> Document -> Balance Audit
Trail -> All Accounts, or Open Item Accounts -> From Balance Audit Trail Dataset -> Extract for
Accumulated Classic Balance Audit Trail .
Effects on Existing Data
The previous reports are still available.
Note
In a Unicode environment, the previous reports do not function with sequential data.
Effects on Data Transfer
You can copy existing data into the new database tables:
o
You can copy existing data using the previous reports before the Unicode changeover and then use
the new report.
o
You can recreate the dataset from the existing databases using the new report.
5.12.5.12.4 Closng/Opening Postings (New)
Use
From Release 4.70, you can use a revised version of report RFSUMB00 to carry out the following
postings for year-end closing:
o
Postings for the profit and loss statement for year-end closing
______________________________________________________________
SAP AG
61
SAP System
______________________________________________________________
o
Postings for closing and opening the balance sheet accounts for the new fiscal year
The relevant documents are created for these postings.
Caution
This report only has to be executed in certain countries, for example, Italy, Turkey, Slovakia, Columbia,
Rumania, Portugal. In these countries, documents have to be created via the closing/carryforward
postings in order to comply with the legal requirements. In all other countries, it is sufficient to execute
the report for the carryforward.
You can access the report from the SAP Easy Access screen under Accounting -> Financial Accounting
-> General Ledger -> Periodic Processing -> Closing -> Closing/Opening Postings. There is a
separate report variant for each country for which the report has to be executed.
Effects on Customizing
Before you can run the report, you have to define the account determination. You can make the setting in
Customizing under Accounting -> Financial Accounting -> General Ledger Accounting ->
Business Transactions -> Closing -> Closing/Opening Postings (only specific countries) ->
Define Account Determination.
5.12.5.12.5 COS: Extension of Functional Area Field (modified)
Use
For Release 4.70, the field Functional Area has been extended from four to sixteen places.
Effects on Existing Data
You only have to make a change if you use BAPIs (Business Application Programming Interfaces) where
the functional area is transferred to the BAPI in the interface. Since the functional area in the BAPI
interfaces could not be extended, the new field FUNC_AREA_LONG, which has 16 places, has been
added to the BAPI interfaces in addition to the old field FUNC_AREA. If you use a BAPI in which the
functional area is transferred to the BAPI on the interface, when you call up the BAPI you have to fill the
field FUNC_AREA_LONG.
In all other cases, you do not have to make any adjustment:
o
If you still only use 4 spaces for the functional area
o
If you want to use the functional area with more than four spaces in the future.
5.12.5.12.6 Foreign Currency Valuation of SL Balances (Modified)
Use
From Release 4.70 you can use the foreign currency valuation report (SAPF100) to valuate a G/L account
by using the account balance from an additional (special purpose) ledger.
The additional SL ledger (from the application component Special Purpose Ledger (FI-SL)) must contain
the additional dimensions for which a valuation is to be carried out, for example, the profit center, cost
______________________________________________________________
SAP AG
62
SAP System
______________________________________________________________
center, and so on.
The system carries out the foreign currency valuation as follows:
o
Individual periods or the end balance are valuated. The selection is made using the key date. From
the key date, the system determines the relevant period in the SL component.
o
The expense/revenue is determined according to the dimensions of the SL, meaning that all of the
ledger dimensions for this account are valuated and not the total balance of the account. There is
therefore a profit/loss, for example, for each functional area.
o
The postings are also posted to the SL via the general ledger. The totals in the G/L and SL are
therefore identical, but the detailed valuations only exist in the SL.
During posting, the data of the additional SL dimensions is entered in the batch input fields.
o
The account determination is carried out in the same way as the balance valuation.
If you access the report and want to use the new functions, you have to enter additional parameters on the
selection screen: The name of the SL and possibly an alternative exchange rate type.
Effects on System Administration
You have to specify the additional dimensions of your SL that are to be considered in the foreign
currency valuation in the structure CI_SAPF100_IN_OUT in the ABAP Dictionary. SAP has defined
this structure as a customer include so that there is no need to change the standard. In the structure, names
from table BSEG (structure COBL) are used as field names since these field names are required for batch
input, for example:
Dimension in SL (GLU1)
StructureCI_SAPF100_OUT_IN (G/L)
RPRCTR
PRCTR
RFAREA
FKBER
SBUSA
PARGB
5.12.5.12.7 Structure Changes in Inflation Accounting
Use
As of SAP R/3 Release 4.70, the Implementation Guide (IMG) for Inflation Accounting is easier to use.
SAP has restructured it, rewritten the documentation, and reworked some of the screens.
Note that only the IMG structure and documentation have changed, but not the views themselves, so you
do not have to make any changes to existing Customizing settings.
Changes in the IMG
Until now, there was one group of IMG activities for Inflation Accounting under Financial Accounting
(FI), and more activities under Asset Accounting (FI-AA) and Materials Management (MM). That
meant that to customize Inflation Accounting for FI-AA, for example, you had to work through the
activities under FI and those under FI-AA.
SAP has now changed the IMG so that each of the components now has its own self-contained IMG for
Inflation Accounting. Now, to customize Inflation Accounting for FI-AA, for example, you no longer
______________________________________________________________
SAP AG
63
SAP System
______________________________________________________________
have to work through the IMG activities under Revaluation for the Balance Sheet and then the
activities under Inflation Accounting. Nor do you have to work through the activities under Financial
Accounting -> Financial Accounting Global Settings -> Inflation Accounting. Instead, you just have
to work through the activities under Inflation Accounting. Similarly, the IMG activities for FI and MM
have also been restructured.
The IMGs are still located at the same position in the SAP Reference Structure:
o
Financial Accounting -> Financial Accounting Global Settings -> Inflation Accounting
o
Financial Accounting -> Asset Accounting -> Special Valuation -> Revaluation of Fixed
Assets -> Revaluation for the Balance Sheet -> Inflation Accounting
o
Materials Management -> Valuation and Account Assignment -> Balance Sheet Valuation
Procedures -> Configure Replacement Cost Procedure (Inflation)
Changes in the SAP Library
The Inflation Accounting documentation in the SAP Library has also been split up between the three
components. It is now located under the following paths:
o
Financial Accounting (FI) -> General Ledger Accounting (FI-GL) -> Closing and Reporting
-> Preparing Financial Statements -> Inflation Accounting
o
Financial Accounting (FI) -> Asset Accounting (FI-AA) -> Special Valuation -> Replacement
Values (General) -> Inflation Accounting
o
Materials Management (MM) -> Evaluation -> Balance Sheet Valuation (MM-IM-VP) ->
Replacement Cost Valuation (Inflation)
5.12.6 FI-GL-IS
Information System
5.12.6.1 DRB (Enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , the Document Relationship Browser (DRB)
offers an extended selection of object types. Object types have been added to the DRB, and object types
that were already connected in earlier releases have been completed.
New object types:
o
Profit center document
o
Costing-based profitability analysis
o
Electronic account statement
o
Production order
o
Backflush document
The connection of these object types only affects the functions within the DRB. There are no separate
access programs.
Enhanced object types:
______________________________________________________________
SAP AG
64
SAP System
______________________________________________________________
o
Accounting document
From the document display (transaction FB03), you can branch to the DRB. You can use report
RDRBFI00 to access the DRB and to find archived accounting documents via the archive
information system (SAP AS).
o
Controlling document
From the line item reports (for example, transaction KSB1, KSB5, KOB1), you can branch to the
DRB.
The DRB functions can find Controlling documents in the archives of all archiving objects that
archive Controlling line items. There are several field catalogs and info structures for this.
See also
For more information about the Document Relationship Browser, see the SAP note 492938.
5.13 FI-AP
Accounts Payable
5.13.1 FI-AP-AP
Basic Functions
5.13.1.1 Returns for Section 16 of the Taxes and Management Act (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), companies in the United Kingdom can use the
R/3 System to comply with Section 16 of the Taxes and Management Act, 1970.
Under the terms of this act, you may be required to file a return with a list of external service providers
that you have paid more than GBP 1,000 to over the course of the tax year.
You prepare the return using the Generic Withholding Tax Reporting program in conjunction with a new
output group, UK1, and a new DME tree, IDWTFILE_UK_S16TMA (see tree documentation).
To track the payments, you can use the sample withholding tax type and codes provided.
We recommend that you implement this new function at the beginning of the tax year to ensure that all
the payments are covered. However, if you wish to implement it during the course of the tax year, you
can do so (see below).
Effects on Existing Data
Once you have made the Customizing settings described below, add the new withholding tax types and
codes to the appropriate vendor masters.
If, after the tax year has already started and you have already made payments to a vendor, you discover
that you must include this vendor in the return as well, run the Program for Recreating Withholding Tax
Data for that vendor. This program checks all payments posted in the tax year to date and assigns the new
withholding tax codes to them.
You can also use this report if you implement the entire solution partway through the tax year.
Effects on Customizing
______________________________________________________________
SAP AG
65
SAP System
______________________________________________________________
Work through the following Customizing activities:
IMG activity
What to do
Define Withholding Tax Type for Payment Posting Check the new withholding tax type supplied,
16.
Define Withholding Tax Codes
Check the withholding tax codes, 01 and 02.
Assign Withholding Tax Types to Company Codes Assign the new withholding tax types to your
company codes.
See also
SAP Library -> Financials -> Country Versions -> Europe and Africa -> United Kingdom ->
Extended Withholding Tax.
5.13.1.2 Annual Returns Under Section 194 A (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can prepare an annual return of tax deducted
under Section 194 A of India's Income Tax Act (earnings from interest other than interest on securities).
The annual return program creates a return in the required format.
This only applies to the Extended Withholding Tax solution. It is not available for Classic
Withholding Tax.
Some of the sections of the form (sections 4, 7, and 8) are for interest subject to a lower rate of
withholding tax or entirely exempt from withholding tax. So that the system can fill out these sections
properly, you must post such withholding tax items using separate withholding tax codes and assign each
withholding tax code the appropriate exemption code.
Effects on Existing Data
When you have completed the Customizing activities listed below, add the following to your customer
masters and vendor masters:
o
Withholding tax types
o
Withholding tax codes
o
Recipient types
In the customer master, there is no field for the recipient type. Instead, enter the recipient type in the
Withholding Tax Number field.
Do not enter the exemption reasons that you have defined (see below) in the vendor master. The system
uses the exemption reasons that you have assigned to the withholding tax codes in the Customizing
activities.
Effects on Customizing
Assuming that you already use the Extended Withholding Tax solution, you must make the following
additional settings:
______________________________________________________________
SAP AG
66
SAP System
______________________________________________________________
IMG activity
What to do
Define Official Withholding Tax Keys
Create a new official withholding tax key, 194A.
Define Withholding Tax Types for Invoice Posting Define new withholding tax types for Section
194 A.
Define Withholding Tax Types for Payment Posting Define new withholding tax types for Section
194 A.
Assign Withholding Tax Types to Company Codes Assign the new withholding tax types to the
company codes that withhold taxes under Section 194 A.
Define Withholding Tax Codes
Define new withholding tax codes, for taxes to be
deducted at the normal and reduced rates, and for exemptions.
Define Accounts for Withholding Tax to be Paid Over
Specify which G/L accounts you want to
post the withholding tax payable to.
Define Reasons for Exemption
Define the reasons for exemption (see the F1 Help to
the Exemption Reason field in this activity).
Assign Exemption Reasons to Withholding Tax Codes
Assign each reduced-rate and exempt tax
code to an exemption reason.
Check Recipient Types
Create new recipient types (CO for companies and OT
for other) for each new withholding tax code.
Maintain Tax Due Dates
Maintain the tax due dates for this section.
Maintain Number Groups
Maintain the number groups for the remittance
challans.
Assign Number Ranges to Number Groups
Make the settings for the remittance challans.
Maintain Number Ranges
Make the settings for the remittance challans.
Maintain Number Groups and SAPscript Forms
Specify on which SAPscript forms you want to
print out withholding tax certificates for Section 194 A, and how you want to number them.
See also
SAP Library -> Financials -> Country Versions -> Asia-Pacific -> India -> Financial Accounting
(FI) -> Taxes (FI-AP/AR) -> Withholding Tax -> Extended Withholding Tax -> Exemptions and
Reduced Rates for Section 194 A.
5.13.1.3 Annual Returns Under Section 194 C (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), when you create an annual return under Section
194 C of India's Income Tax Act, the system automatically shows the type of company on the return.
This applies only to the Extended Withholding Tax solution. This function already exists in Classic
Withholding Tax.
We recommend that you only implement this change at the begininning of a new fiscal year because of
the change in the withholding tax codes.
Effects on Existing Data
______________________________________________________________
SAP AG
67
SAP System
______________________________________________________________
When you have completed the Customizing activities listed below, change the following in your
customer masters and vendor masters:
o
Enter the new withholding tax codes and mark them as Liable.
o
For the old withholding tax codes, deselect Liable.
o
Enter the recipient types.
In the customer master, there is no field for the recipient type. Instead, enter the recipient type in the
Withholding Tax Number field.
Effects on Customizing
IMG activity
What to do
Define Withholding Tax Codes
For each withholding tax code that you currently use
for this section of the Income Tax Act, create three new codes (one for each type of company allowed
in the form).
Assign Types of Companies to Withholding Tax Codes
Assign one type of company to each of
the withholding tax codes.
Check Recipient Types
Create new recipient types (CO for companies and OT
for other) for each new withholding tax code.
See also
SAP Library -> Financials -> Country Versions -> Asia-Pacific -> India -> Financial Accounting
(FI) -> Taxes (FI-AP/AR) -> Withholding Tax -> Extended Withholding Tax -> Automatic
Determination of Type of Company for Section 194 C.
5.13.1.4 Canceled TDS Certificates (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), when you cancel a TDS certificate in Classic
TDS, as used in India, the system does not delete it.
The excise authorities require you to number TDS certificates consecutively and without any gaps. Now,
when you cancel a certificate, the system marks it as canceled, but does not delete it from the database.
Once you have canceled a certificate, you cannot print it. It is not shown in any annual returns, but it is
still archived.
5.13.1.5 TDS Programs (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the Classic TDS programs as used in India can
be run concurrently by more than one user. The following programs are affected:
o
Print TDS Certificates
______________________________________________________________
SAP AG
68
SAP System
______________________________________________________________
o
Post TDS
o
Challan Update
5.13.1.6 Annual Returns for Classic TDS (Deleted)
Use
The four reports used for preparing annual returns for the Classic TDS (Tax Deducted at Source)
solution for India have been deleted.
Users working with Classic TDS solution must now use the Annual Returns report, which in the
previous release was only for Extended Withholding Tax, but has now been enhanced to support
Classic TDS as well.
See also
SAP Library -> Financials -> Country Versions -> Asia-Pacific -> India -> Financial Accounting
(FI) -> Taxes (FI-AP/AR) -> Withholding Tax -> Annual Returns.
5.13.1.7 Classic TDS Program (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the Classic Tax Deduction at Source program, as
used in India, allows users to retrieve and process individual invoices more quickly.
SAP has added a new field, Process Invoices Only, to the program's selection screen.
When you execute the program, select this field and enter the invoice number.
5.13.1.8 Withholding Tax Reporting (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create withholding tax returns for South
Korea using the Generic Withholding Tax Reporting program. You can use the program to create tax
returns (business income only) as a DME file and prepare withholding tax certificates on paper.
If you use this program, we recommend that you calculate withholding tax when you post an invoice, in
line with South Korean accounting principles. New sample withholding tax types and withholding tax
codes are provided.
For more information about the settings provided, see the documentation mentioned below.
Effects on Existing Data
When you have completed the Customizing activities listed below, add the following to your vendor
______________________________________________________________
SAP AG
69
SAP System
______________________________________________________________
masters:
o
Withholding tax types
o
Withholding tax codes
o
Recipient types
Effects on Customizing
Assuming that you already use the Extended Withholding Tax solution, you must make the following
additional settings:
IMG activity
What to do
Define Official Withholding Tax Keys
Check the keys supplied.
Define Withholding Tax Types for Invoice Posting Define new withholding tax types. Copy the
samples provided, if you want.
Assign Withholding Tax Types to Company Codes Assign the new withholding tax types to the
company codes that withhold these taxes.
Check Income Types
Define income types for residents (1) and nonresidents
(2).
Define Withholding Tax Codes
Define new withholding tax codes. Again, you can
copy the samples provided. Assign an income type and an official withholding tax key to each code.
Define Accounts for Withholding Tax to be Paid Over
Specify which G/L accounts you want to
post the withholding tax payable to.
Check Recipient Types
Create new recipient types (for example, lawyer,
doctor) for each new withholding tax code.
See also
SAP Library -> Financials -> Country Versions -> Asia-Pacific -> South Korea -> Financial
Accounting (FI) -> Taxes (FI-AP/AR) -> Extended Withholding Tax
5.13.1.9 Withholding Tax Reports (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), three of the withholding tax reports used in South
Korea have been enhanced.
The main change is that all the reports now handle withholding tax items generated at the time of invoice
posting. The new features of each report are listed below:
Withholding Tax Certificates Report
SAP has enhanced the Withholding Tax Certificates report so that it incorporates the latest legal changes
to withholding tax certificates. It covers withholding taxes deducted at the time of invoice posting, and
each certificate itemizes all vendor invoices that you have withheld tax on.
On the selection screen, you can select which withholding tax types and withholding tax codes you want
______________________________________________________________
SAP AG
70
SAP System
______________________________________________________________
it to cover. When you enter the selection criteria and choose Enter, the system displays a list of the
accounting documents that it has found. You then select which documents you want to cover in the
withholding tax certificates.
The selection screen also includes fields for the type of residence and the type of income, which are
assigned to withholding tax codes in Customizing. What you enter in these fields controls whether the
system marks the vendor as a resident or nonresident, and what type of income it prints on the certificate.
When you print out the certificates, you can number the pages in each certificate. You can also decide
whether oyu want to print out only one copy of each certificate (for the vendor only) or three copies (for
yourself, the vendor, and the tax authorities).
The report uses the international address versions, if they have been maintained.
So that you can reprint certificates, a new field has been added to the selection screen, where you can
enter the vendor's VAT registriation number.
Any amounts given in foreign currencies will be shown in Korean won using the exchange rate valid on
the payment date. This also applies to withholding tax that is calculated at the time of invoice posting.
Withholding Tax DME Output Report
SAP has enhanced the Withholding Tax DME Output report so that the data medium exchange (DME)
file supports the latest file format published by the tax authorities.
This report now also covers withholding tax items generated at the time of invoice posting, and it reports
all withholding tax items that you have generated.
Finally, on the selection screen, you can also specify which withholding tax types and withholding tax
codes the report should cover.
Detail Information on Income and Inhabitant Tax
The Detail Information on Income and Inhabitant Tax report now covers withholding tax deducted at the
time of invoice posting. It lists the documents on the basis of the vendor invoices, and, again, the
selection screen has been enhanced so that you can enter withholding tax types and withholding tax
codes.
Effects on Customizing
IMG activity
What to do
Define Fiscal Regional Codes for Other Countries Define the types of income as published by the
tax authorities (used for "other income" only).
Check Income Types
Define two types of residence (1: resident 2:
nonresident)
Define Withholding Tax Codes
For each code, enter the type of income and the type
of residence that applies to it.
______________________________________________________________
SAP AG
71
SAP System
______________________________________________________________
5.13.1.10 Entering Long Texts in the FI Enjoy Transactions (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can enter a long text for each G/L account
item via @0J@ with Quickinfo Long Text when you enter or park an accounting document in an FI
Enjoy transaction (Vendor Parking).
The symbol @0J@ with Quickinfo Long Text shows that a long text exists for a G/L account item.
5.13.1.11 Document Types for Journal Vouchers and Provisions (Changed)
Use
The view in which you specify which document types you want the system to use when you (a) enter
journal vouchers and (b) enter provisions for tax on services received has changed.
Instead of one single view (J_1IEWTDOCKEY) containing both settings, there are now two views
(J_1IEWTDTPRV and J_1IEWTJV respectively).
Effects on Customizing
The only effect that this has on the system is that you have to change your Customizing settings. Maintain
the following activities:
o
Specify Document Type (journal vouchers)
o
Specify Document Type (provisions for taxes)
5.13.1.12 Extended Withholding Tax and ALE Distribution for Master Data and
Documents
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), extended withholding tax is supported for the
ALE distribution of documents and master data. If you use distributed systems and withholding tax, you
can now also use extended withholding tax.
o
Document dispatch
If you use extended withholding tax, withholding tax information is dispatched. However, the
withholding tax is generally only calculated in the receiver system; this ensures correct
accumulation.
o
Master data
Withholding tax master data for extended withholding tax is sent for vendors and for customers.
See also
For more information, see the SAP Library under Accounting -> Financial Accounting -> Financial
Accounting General Topics (FI) -> Taxes (FI-AP/AR)-> Withholding Tax -> Extended Withholding Tax.
______________________________________________________________
SAP AG
72
SAP System
______________________________________________________________
For more information about changing over from withholding tax to extended withholding tax, see
Accounting -> Financial Accounting -> Financial Accounting General Topics (FI)-> Taxes (FI-AP/AR)
-> Withholding Tax -> Withholding Tax Changeover.
5.13.1.13 Withholding Tax Analysis Report for Extended Withholding Tax (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use program RFWT1000 to analyze your
settings for extended withholding tax:
The program consists of three subfunctions:
o
Check withholding tax settings
Here you can look at your current Customizing settings and check them for consistency.
o
Calculate withholding tax
Here you can simulate the withholding tax calculation for an example document.
o
Check field status
Here you can look at the current field status settings.
The subfunction Check withholding tax settings is located on the initial screen. To go to the other
functions, choose the relevant button.
See also
Documentation of program RFWT1000.
5.13.1.14 FI-AP-AP-MD
Master Data
5.13.1.14.1 Customer-Specific Fields in Business Partner Master Data (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , you can define additional data in the master data
of your customers and vendors. To do this, you develop subscreens to which you add the required fields.
You can access your subscreens in the master records of the business partner via integrated buttons; there,
your screens are integrated on a tab page. You can assign up to 32 tab pages/subscreens to each button.
With a change of release, upgrade, or a support package, you copy your own subscreens and data and the
relevant tables without having to make any modifications.
Effects on Customizing
In the Implementation Guide for Financial Accounting or Logistics, make the following settings:
Financial Accounting
1.
Choose Accounts Payable/Accounts Receivable Accounting -> Customer Accounts or Vendor
______________________________________________________________
SAP AG
73
SAP System
______________________________________________________________
Accounts -> Master Data -> Transfer Customer Master Data Fields -> Prepare Modification-Free
Enhancement in Customer Master or Vendor Master and make the relevant settings for defining
your subscreens.
2.
To connect your subscreens and data to the standard application, use the following BADIs:
-
Business Add-In: Processing Master Data Enhancements
-
Business Add-In: Customer Subscreens
-
Business Add-In: Processing Master Data Enhancements with Batch Input
General Logistics
1.
Choose Business Partner -> Customer or Vendor -> Control -> Copy Customer Master Data Fields
-> Prepare Modification-Free Enhancement of Vendor or Customer Master Record, and make the
relevant settings for defining your subscreens.
2.
To connect your subscreens and data to the standard application, use the following BADIs:
-
Business Add-In: Processing Master Data Enhancements
-
Business Add-In: Customer Subscreens
-
Business Add-In: Processing Master Data Enhancements with Batch Input
See also
For more information, see the respective Customizing activity and the documentation for the individual
BADIs.
5.13.1.14.2 Extended Withholding Tax and ALE Distribution for Master Data and
Documents
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), extended withholding tax is supported for the
ALE distribution of documents and master data. If you use distributed systems and withholding tax, you
can now also use extended withholding tax.
o
Document dispatch
If you use extended withholding tax, withholding tax information is dispatched. However, the
withholding tax is generally only calculated in the receiver system; this ensures correct
accumulation.
o
Master data
Withholding tax master data for extended withholding tax is sent for vendors and for customers.
See also
For more information, see the SAP Library under Accounting -> Financial Accounting -> Financial
Accounting General Topics (FI) -> Taxes (FI-AP/AR)-> Withholding Tax -> Extended Withholding Tax.
For more information about changing over from withholding tax to extended withholding tax, see
Accounting -> Financial Accounting -> Financial Accounting General Topics (FI)-> Taxes (FI-AP/AR)
-> Withholding Tax -> Withholding Tax Changeover.
______________________________________________________________
SAP AG
74
SAP System
______________________________________________________________
5.13.1.15 FI-AP-AP-IC
Invoices and Credit Memos
5.13.1.15.1 Amount Split in the FI Enjoy Document Parking Transaction (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can split amounts in the FI Enjoy transactions
for parking invoices and credit memos.
5.13.1.16 FI-AP-AP-PT
Payment Transactions
5.13.1.16.1 Payment Cards
Use
From this release, you can use the functions forPayment Cards in Accounting in the role
SAP_FI_AP_PCARD.
See also
For more information, see:
o
o
The program documentation
-
Read inbound file
-
Edit card file
-
Edit log
The SAP Library of the respective maintenance transactions for the paymemnt card master record or
the card document under Help -> Application Help
5.13.1.16.2 Domestic Payments by PAYMUL (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create DME files for domestic payments
in Denmark in the PAYMUL format.
SAP delivers a new payment method, P (Domestic Payment PAYMUL), which is linked to a Payment
Medium Workbench (PMW) format and a DME format.
Effects on Existing Data
Add the payment method to the master records of the vendors that want you to pay using this format.
______________________________________________________________
SAP AG
75
SAP System
______________________________________________________________
Effects on Customizing
IMG activity
What to do
Adjust Note to Payee
Specify what information you want to include in the
note to payee in the DME files.
Assign Payment Medium Format and Note to Payee to Payment Method Assign the note to payee to
the payment method.
Create/Assign Selection Variants
Create a selection variant that the system will use
when you execute the payment program.
Adjust Payment Medium Format
Check the PMW formats and the DMEE formats
provided, and adjust them, if necessary.
See also
Domestic Payment PAYMUL (PMW format documentation)
Domestic Payment PAYMUL (DME format tree documentation)
5.13.1.16.3 Payments in Finland (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create payment files for the following
payment methods using the Payment Medium Workbench (PMW):
Method
A
M
U
Description
Autogiro
Domestic Payments (LM03 Format)
Foreign payments (LUM2 Format)
For each payment method, SAP delivers a PMW format and a DME format. SAP has changed the
payment methods so that they now use these formats.
SAP will discontinue maintenance of the classic payment medium programs covered by these formats. In
future, when the financial institutions announce changes to their formats, SAP will only change the PMW
formats to match.
We therefore recommend that you switch to the PMW before these institutions announce any changes to
their file formats.
Effects on Customizing
Assuming that you want to use the PMW formats, make the following Customizing settings:
IMG activity
What to do
Adjust Note to Payee
Specify what information you want to include in the
note to payee in the DME files.
Assign Payment Medium Format and Note to Payee to Payment Method Assign the note to payee to
the payment method.
______________________________________________________________
SAP AG
76
SAP System
______________________________________________________________
Create/Assign Selection Variants
when you execute the payment program.
Adjust Payment Medium Format
provided, and adjust them, if necessary.
Create a selection variant that the system will use
Check the PMW formats and the DMEE formats
If you do not want to use the PMW, you must reassign the classic payment medium programs to the
payment methods.
See also
For more information about the formats, see the format documentation itself, which you can display in
the IMG activity Assign Payment Medium Format and Note to Payee to Payment Method in the
appropriate payment method.
5.13.1.16.4 Payments by BACS (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create BACS payment files using the
Payment Medium Workbench (PMW).
Note that SAP will discontinue maintenance of the existing program, RFFOGB_T, and that any changes
made by BACS in future will be made in the PMW formats only.
We therefore recommend that you switch to the PMW before BACS announces any changes to its file
formats.
Effects on Customizing
IMG activity
What to do
Set Up Payment Methods per Country for Payment Transactions Change the BACS payment
methods (in the standard system, D (Direct Debit) and E (BACS Transfer)) so that they use the PMW
format GB_BACS.
See also
GB_BACS (PMW format documentation)
GB_BACS (DME format tree documentation)
5.13.1.16.5 Payments with Bank of Ireland and Allied Irish Banks (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create payment files in the formats used
by the Bank of Ireland (BOI) and Allied Irish Banks (AIB) using the Payment Medium Workbench
(PMW).
Note that SAP will discontinue maintenance of the existing program, RFFOGB_T, and that any changes
made by BOI and AIB in future will be made in the PMW formats only. We therefore recommend that
______________________________________________________________
SAP AG
77
SAP System
______________________________________________________________
you switch to the PMW before BOI and AIB announce any changes to their file formats.
SAP has changed payment method E so that it supports electronic funds transfer using the BOI format
only. F is a new payment method that supports the AIB format. You can of course decide which tree is
used with which payment method.
Effects on Existing Data
Add the new payment method, F, to the master records of the vendors that want you to pay using this
format.
Effects on Customizing
IMG activity
What to do
Set Up Payment Methods per Country for Payment Transactions
F
Check the payment methods E and
See also
IE_BOE (PMW format documentation)
IE_BOI (DME format tree documentation)
IE_AIB (PMW format documentation)
IE_AIB (DME format tree documentation)
5.13.1.16.6 Payments in Sweden (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create payment files for the following
payment methods using the Payment Medium Workbench (PMW):
Method
A
H
I
P
S
Description
Autogiro for Individuals
Foreign Payments (Handelsbanken)
Domestic Payments (Bankgirot)
Domestic Payments (Postgirot)
Foreign Payments (SE-Banken)
For each payment method, SAP delivers a PMW format and a DME format. SAP has changed the
payment methods so that they now use these formats.
SAP will discontinue maintenance of the classic payment medium programs covered by these formats. In
future, when the financial institutions announce changes to their formats, SAP will only change the PMW
formats to match.
We therefore recommend that you switch to the PMW before these institutions announce any changes to
their file formats.
Effects on Customizing
______________________________________________________________
SAP AG
78
SAP System
______________________________________________________________
Assuming that you want to use the PMW formats, make the following Customizing settings:
IMG activity
What to do
Adjust Note to Payee
Specify what information you want to include in the
note to payee in the DME files.
Assign Payment Medium Format and Note to Payee to Payment Method Assign the note to payee to
the payment method.
Create/Assign Selection Variants
Create a selection variant that the system will use
when you execute the payment program.
Adjust Payment Medium Format
Check the PMW formats and the DMEE formats
provided, and adjust them, if necessary.
If you do not want to use the PMW, you must reassign the classic payment medium programs to the
payment methods.
See also
For more information about the formats, see the format documentation itself, which you can display in
the IMG activity Assign Payment Medium Format and Note to Payee to Payment Method in the
appropriate payment method.
5.13.1.16.7 Automatic Scheduling of the Payment Program (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use report RFF110S to
automatically schedule a proposal or an update run of payment program SAPF110S. To do this, proceed
as follows from the SAP Easy Access menu: Accounting -> Financial Accounting ->
Customers/Vendors -> Periodic Processing -> Schedule Payment Program Periodically.
You can save your selection criteria as a variant. If you use selection variables as selection criteria, you
can schedule a payment run with identical selection criteria periodically. At the time when you want to
execute the variant, the system calculates the current data. You can still use the follow-on functions
provided by the payment program (transaction F110).
Report RFF110S is integrated into the Schedule Manager, so that you can also schedule proposal and
update runs of the payment program SAPF110S automatically with the Schedule Manager. Previously,
you could only do this for proposal runs.
See also
For more information, see the report documentation.
5.13.1.16.8 Payment Program SAPF110S (Enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following functions are available in the
______________________________________________________________
SAP AG
79
SAP System
______________________________________________________________
area Paying with the Payment Program SAPF110S:
o
Debit balance check with report RFF110SSP
o
Following new Business Transaction Events (BTEs):
-
00001820 Payment Program: Item Selection
-
00001830 Payment Program: Process Group
Effects on Customizing
If you want to use the BTEs, carry out the IMG activity Business Transaction Events in the
Implementation Guide (IMG) for Financial Accounting.
See also
For more information about the debit balance check, see the documentation for the report.
For more information about BTEs, see the IMG for Financial Accounting under Financial Accounting
Global Settings -> Business Transaction Events.
5.13.1.17 FI-AP-AP-CR
Correspondence
5.13.1.17.1 Balance Confirmation (Enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the following new functions in the
balance confirmation:
o
Cross-company code balance confirmation (with individual request)
This applies for the Customer Balance Confirmation (SAPF130D) and the Vendor Balance
Confirmation (SAPF130K).
A balance confirmation is created for each customer/vendor. All company codes assigned to the
correspondence company code are taken into account. The balance confirmation is addressed to the
correspondence company code.
For more information, see the documentation for the reports Customer Balance Confirmation and
Vendor Balance Confirmation in the section Group Version.
o
New event for faxing, archiving, and sending as e-mail (Business Transaction Event 2410)
For more information, see the documentation for the function module
FI_OPT_ARCHIVE_BALANCE_CONFIRM.
Effects on Customizing
To use the cross-company code balance confirmation, make the following setting in the Implementation
Guide for Financial Accounting: Financial Accounting Global Settings -> Correspondence ->
Assign Company Codes to Correspondence Company Codes
______________________________________________________________
SAP AG
80
SAP System
______________________________________________________________
5.13.1.18 FI-AP-AP-CL
Closing Operations
5.13.1.18.1 Returns for Section 16 of the Taxes and Management Act (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), companies in the United Kingdom can use the
R/3 System to comply with Section 16 of the Taxes and Management Act, 1970.
Under the terms of this act, you may be required to file a return with a list of external service providers
that you have paid more than GBP 1,000 to over the course of the tax year.
You prepare the return using the Generic Withholding Tax Reporting program in conjunction with a new
output group, UK1, and a new DME tree, IDWTFILE_UK_S16TMA (see tree documentation).
To track the payments, you can use the sample withholding tax type and codes provided.
We recommend that you implement this new function at the beginning of the tax year to ensure that all
the payments are covered. However, if you wish to implement it during the course of the tax year, you
can do so (see below).
Effects on Existing Data
Once you have made the Customizing settings described below, add the new withholding tax types and
codes to the appropriate vendor masters.
If, after the tax year has already started and you have already made payments to a vendor, you discover
that you must include this vendor in the return as well, run the Program for Recreating Withholding Tax
Data for that vendor. This program checks all payments posted in the tax year to date and assigns the new
withholding tax codes to them.
You can also use this report if you implement the entire solution partway through the tax year.
Effects on Customizing
Work through the following Customizing activities:
IMG activity
What to do
Define Withholding Tax Type for Payment Posting Check the new withholding tax type supplied,
16.
Define Withholding Tax Codes
Check the withholding tax codes, 01 and 02.
Assign Withholding Tax Types to Company Codes Assign the new withholding tax types to your
company codes.
See also
SAP Library -> Financials -> Country Versions -> Europe and Africa -> United Kingdom ->
Extended Withholding Tax.
______________________________________________________________
SAP AG
81
SAP System
______________________________________________________________
5.13.1.18.2 Structure Changes in Inflation Accounting
Use
As of SAP R/3 Release 4.70, the Implementation Guide (IMG) for Inflation Accounting is easier to use.
SAP has restructured it, rewritten the documentation, and reworked some of the screens.
Note that only the IMG structure and documentation have changed, but not the views themselves, so you
do not have to make any changes to existing Customizing settings.
Changes in the IMG
Until now, there was one group of IMG activities for Inflation Accounting under Financial Accounting
(FI), and more activities under Asset Accounting (FI-AA) and Materials Management (MM). That
meant that to customize Inflation Accounting for FI-AA, for example, you had to work through the
activities under FI and those under FI-AA.
SAP has now changed the IMG so that each of the components now has its own self-contained IMG for
Inflation Accounting. Now, to customize Inflation Accounting for FI-AA, for example, you no longer
have to work through the IMG activities under Revaluation for the Balance Sheet and then the
activities under Inflation Accounting. Nor do you have to work through the activities under Financial
Accounting -> Financial Accounting Global Settings -> Inflation Accounting. Instead, you just have
to work through the activities under Inflation Accounting. Similarly, the IMG activities for FI and MM
have also been restructured.
The IMGs are still located at the same position in the SAP Reference Structure:
o
Financial Accounting -> Financial Accounting Global Settings -> Inflation Accounting
o
Financial Accounting -> Asset Accounting -> Special Valuation -> Revaluation of Fixed
Assets -> Revaluation for the Balance Sheet -> Inflation Accounting
o
Materials Management -> Valuation and Account Assignment -> Balance Sheet Valuation
Procedures -> Configure Replacement Cost Procedure (Inflation)
Changes in the SAP Library
The Inflation Accounting documentation in the SAP Library has also been split up between the three
components. It is now located under the following paths:
o
Financial Accounting (FI) -> General Ledger Accounting (FI-GL) -> Closing and Reporting
-> Preparing Financial Statements -> Inflation Accounting
o
Financial Accounting (FI) -> Asset Accounting (FI-AA) -> Special Valuation -> Replacement
Values (General) -> Inflation Accounting
o
Materials Management (MM) -> Evaluation -> Balance Sheet Valuation (MM-IM-VP) ->
Replacement Cost Valuation (Inflation)
______________________________________________________________
SAP AG
82
SAP System
______________________________________________________________
5.14 FI-AR
Accounts Receivable
5.14.1 FI-AR-AR
Basic Functions
5.14.1.1 Withholding Tax Reports (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), three of the withholding tax reports used in South
Korea have been enhanced.
The main change is that all the reports now handle withholding tax items generated at the time of invoice
posting. The new features of each report are listed below:
Withholding Tax Certificates Report
SAP has enhanced the Withholding Tax Certificates report so that it incorporates the latest legal changes
to withholding tax certificates. It covers withholding taxes deducted at the time of invoice posting, and
each certificate itemizes all vendor invoices that you have withheld tax on.
On the selection screen, you can select which withholding tax types and withholding tax codes you want
it to cover. When you enter the selection criteria and choose Enter, the system displays a list of the
accounting documents that it has found. You then select which documents you want to cover in the
withholding tax certificates.
The selection screen also includes fields for the type of residence and the type of income, which are
assigned to withholding tax codes in Customizing. What you enter in these fields controls whether the
system marks the vendor as a resident or nonresident, and what type of income it prints on the certificate.
When you print out the certificates, you can number the pages in each certificate. You can also decide
whether oyu want to print out only one copy of each certificate (for the vendor only) or three copies (for
yourself, the vendor, and the tax authorities).
The report uses the international address versions, if they have been maintained.
So that you can reprint certificates, a new field has been added to the selection screen, where you can
enter the vendor's VAT registriation number.
Any amounts given in foreign currencies will be shown in Korean won using the exchange rate valid on
the payment date. This also applies to withholding tax that is calculated at the time of invoice posting.
Withholding Tax DME Output Report
SAP has enhanced the Withholding Tax DME Output report so that the data medium exchange (DME)
file supports the latest file format published by the tax authorities.
This report now also covers withholding tax items generated at the time of invoice posting, and it reports
all withholding tax items that you have generated.
Finally, on the selection screen, you can also specify which withholding tax types and withholding tax
codes the report should cover.
______________________________________________________________
SAP AG
83
SAP System
______________________________________________________________
Detail Information on Income and Inhabitant Tax
The Detail Information on Income and Inhabitant Tax report now covers withholding tax deducted at the
time of invoice posting. It lists the documents on the basis of the vendor invoices, and, again, the
selection screen has been enhanced so that you can enter withholding tax types and withholding tax
codes.
Effects on Customizing
IMG activity
What to do
Define Fiscal Regional Codes for Other Countries Define the types of income as published by the
tax authorities (used for "other income" only).
Check Income Types
Define two types of residence (1: resident 2:
nonresident)
Define Withholding Tax Codes
For each code, enter the type of income and the type
of residence that applies to it.
5.14.1.2 Document Display: Invoice Status (Enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the invoice status function is integrated in the
document display. You can use it to display the open proportion of an (already cleared) item.
For any (cleared) item, all relevant residual items, credit memos, partial payments, and bills of exchange
are selected using the invoice reference or the clearing document number (bill of exchange) and displayed
in the line item list. The remaining open amount of an item is displayed in the totals line at the end of the
list.
The links from residual items to residual items, bill of exchange payments to residual items, and
cross-company code bill of exchange items are considered. Partial payments of residual items are not
taken into account.
The invoice status can be used to assess the remaining risk represented by a receivable.
Effects on Customizing
You can access the function 'Invoice status' on the detail screen of the customer or vendor item in the
'Environment' menu or directly using the key combination Ctrl + F10.
You do not have to create a separate layout variant for the line item list. You can use the layout variant
defined in the accounting editing options (FB00) for the line item list.
5.14.1.3 Entering Long Texts in the FI Enjoy Transactions (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can enter a long text for each G/L account
______________________________________________________________
SAP AG
84
SAP System
______________________________________________________________
item via @0J@ with Quickinfo Long Text when you enter or park an accounting document in an FI
Enjoy transaction (Vendor Parking).
The symbol @0J@ with Quickinfo Long Text shows that a long text exists for a G/L account item.
5.14.1.4 Withholding Tax Analysis Report for Extended Withholding Tax (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use program RFWT1000 to analyze your
settings for extended withholding tax:
The program consists of three subfunctions:
o
Check withholding tax settings
Here you can look at your current Customizing settings and check them for consistency.
o
Calculate withholding tax
Here you can simulate the withholding tax calculation for an example document.
o
Check field status
Here you can look at the current field status settings.
The subfunction Check withholding tax settings is located on the initial screen. To go to the other
functions, choose the relevant button.
See also
Documentation of program RFWT1000.
5.14.1.5 FI-AR-AR-MD
Master Data
5.14.1.5.1 Customer-Specific Fields in Business Partner Master Data (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , you can define additional data in the master data
of your customers and vendors. To do this, you develop subscreens to which you add the required fields.
You can access your subscreens in the master records of the business partner via integrated buttons; there,
your screens are integrated on a tab page. You can assign up to 32 tab pages/subscreens to each button.
With a change of release, upgrade, or a support package, you copy your own subscreens and data and the
relevant tables without having to make any modifications.
Effects on Customizing
In the Implementation Guide for Financial Accounting or Logistics, make the following settings:
Financial Accounting
1.
Choose Accounts Payable/Accounts Receivable Accounting -> Customer Accounts or Vendor
______________________________________________________________
SAP AG
85
SAP System
______________________________________________________________
Accounts -> Master Data -> Transfer Customer Master Data Fields -> Prepare Modification-Free
Enhancement in Customer Master or Vendor Master and make the relevant settings for defining
your subscreens.
2.
To connect your subscreens and data to the standard application, use the following BADIs:
-
Business Add-In: Processing Master Data Enhancements
-
Business Add-In: Customer Subscreens
-
Business Add-In: Processing Master Data Enhancements with Batch Input
General Logistics
1.
Choose Business Partner -> Customer or Vendor -> Control -> Copy Customer Master Data Fields
-> Prepare Modification-Free Enhancement of Vendor or Customer Master Record, and make the
relevant settings for defining your subscreens.
2.
To connect your subscreens and data to the standard application, use the following BADIs:
-
Business Add-In: Processing Master Data Enhancements
-
Business Add-In: Customer Subscreens
-
Business Add-In: Processing Master Data Enhancements with Batch Input
See also
For more information, see the respective Customizing activity and the documentation for the individual
BADIs.
5.14.1.5.2 Extended Withholding Tax and ALE Distribution for Master Data and
Documents
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), extended withholding tax is supported for the
ALE distribution of documents and master data. If you use distributed systems and withholding tax, you
can now also use extended withholding tax.
o
Document dispatch
If you use extended withholding tax, withholding tax information is dispatched. However, the
withholding tax is generally only calculated in the receiver system; this ensures correct
accumulation.
o
Master data
Withholding tax master data for extended withholding tax is sent for vendors and for customers.
See also
For more information, see the SAP Library under Accounting -> Financial Accounting -> Financial
Accounting General Topics (FI) -> Taxes (FI-AP/AR)-> Withholding Tax -> Extended Withholding Tax.
For more information about changing over from withholding tax to extended withholding tax, see
Accounting -> Financial Accounting -> Financial Accounting General Topics (FI)-> Taxes (FI-AP/AR)
-> Withholding Tax -> Withholding Tax Changeover.
______________________________________________________________
SAP AG
86
SAP System
______________________________________________________________
5.14.1.6 FI-AR-AR-IC
Invoices and Credit Memos
5.14.1.6.1 Amount Split in the FI Enjoy Document Parking Transaction (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can split amounts in the FI Enjoy transactions
for parking invoices and credit memos.
5.14.1.7 FI-AR-AR-MP
5.14.1.7.1 FI-AR-AR-MP-BF
Manual Payments
Basic Functions
5.14.1.7.1.1 Fast Entry Payment Receipts (Changed)
Use
A special screen was available for fast entry payment receipt (transaction F-26) in systems where the user
parameter 'PNZ' was not set. If you assigned an account to a revenue type or object, the IS-PS specific
screen SAFMF05A 2124 was called instead of screen SAFMF05A 124. You can limit open items to a
revenue type orobject on this screen. This screen is no longer available with the SAP R/3 Enterprise
Public Services 1.10 (EA-PS 110) release.
To select documents by revenue type or object, from now on select Fast Entry Payment Receipt:
Header Data (SAPMF05A 123). For additional selections, select the indicator Selection According to
Reference Key Partner (RF05A-XINPP). On the screen that follows (SAPMF05A 124) you can enter
the revenue type and the object in the field Reference Key Partner(RF05A-SLREF) and limit the open
items.
5.14.1.7.1.2 Open Item Clearing (Enhanced)
Use
Average due date for cash discount
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the function 'Average due date for
cash discount'. A joint due date for cash discount is determined for a group of open items according to
cash discount terms 1(S1) and 2 (S2). Both due dates (S1)/(S2) are displayed in the open item processing.
o
If the average due date (S1) is earlier than the document date of the payment receipt, cash discount
terms 1 are applied to all items.
o
If the average due date (S2) is earlier than the document date of the payment receipt, cash discount
______________________________________________________________
SAP AG
87
SAP System
______________________________________________________________
terms 2 are applied to all items.
The days in arrears are set according to the average due date for cash discount terms 1 and 2
(including a tolerance).
o
If both average due dates S1 and S2 have been exceeded, the original value in the arrears days is
valid.
All active customer debit items that have cash discount terms (cash discount percentage rate 1 or 2) are
considered. Customer credit memos, special G/L transactions (bill of exchange, down payments), and all
vendor items are not considered.
You can reset the change by executing the function 'Reset average due date for cash discount'. If there
are additional manual changes to items after the average due date has been calculated (cash discount, item
active), you cannot reset the changes.
The following details are reset for the items:
o
Cash discount amount
o
Cash discount percentage rate
o
Days in arrears
Days in arrears and due date for cash discount
The value date of the payment item (bank clearing) can be used to determine the cash discount due date
and the days in arrears instead of the document date of the payment document. The payment item is
deemed to be the first line item for incoming and outgoing payments. If no value date can be determined
in this way, the document date is used to calculate the cash discount due date.
Write-off difference automatically
You can use this function to write off payment differences that arise from open item clearing and that are
within certain (larger) tolerance limits automatically. The function corresponds to the function codes
AG/AD used in the R/2 system to write off differences in open item processing.
You define the additional tolerance limits in Customizing for business partner tolerances (table T043G),
field 'Permitted payment differences for automatic write-off (function code AD)'. These settings do not
have any effect on the existing function for writing off payment differences within the tolerance limits for
'permitted payment differences'. Only the previous tolerance limits are used for posting in open item
processing.
If the clearing posting is unsuccessful because the payment difference is too large, you can still accept the
difference amount using the function 'Write-off difference automatically (AD)'. In this case, define
higher limit amounts for the new tolerances. Note that the tolerance limits of the employee are also
considered for the tolerance checks (see documentation for the field BEADS).
The function is only displayed in open item processing if tolerance limits have also been defined for the
business partner.
Value date online check
When you are clearing the bank clearing account, you can check whether the value date of the bank item
agrees with the value date of the selected item in the bank clearing account. If there is a difference, the
item is selected but not activated.
However, you can manually activate the item in open item processing. The first line item of the payment
______________________________________________________________
SAP AG
88
SAP System
______________________________________________________________
document is deemed to be the bank item. The check corresponds to the function of report RFFVAL00.
Choice of selection procedure
When you select the open items in the batch input procedure (BI selection), for example, account
statement postprocessing with FEBAN, you can determine the procedure used to select the open items.
You can choose between two procedures:
o
OR selection (standard procdeure): All items that fulfill at least one of the selection criteria
specified are selected.
o
AND selection: Only those items that fulfill all selection criteria are selected.
You can configure the selection procedure on the batch input screen using the button OR <> AND, and
this is then valid for all subsequent selections within a transaction.
You can switch between the selection procedures, whereby the text of the button reflects the type of
selection:
o
OR <> AND: Selection with OR link
o
AND <> OR: Selection with AND link
Displaying the bank connection used in the payment
In the document display (FB03), the bank details of the business partner (vendor/customer) used for the
payment (with SAPF110S) are displayed on the one-time account additional data screen. The bank
details are saved in the payment run in the one-time account data for the clearing item.
The function is only available for those clearing items of a document created by the payment program
SAPF110S.
The bank details saved in the one-time account data are deleted from the document when you reset
clearing (via transaction FBRA).
Effects on Customizing
Calculation of days in arrears
Extension of the business partner tolerance group (table T043G) with an additional field (reference date
for cash discount determination) with two possible forms:
o
(Blank): Document date (standard)
o
1: Value date
Write off difference automatically
The field 'Permitted payment differences for automatic write-off (function code AD)' has been added to
table T043G (business partner tolerances.
You maintain the tolerances in Customizing.
Value date online check
The indicator 'Check value date' (field PRVAL) has been added to the G/L account tolerances table
(T043S). If you set this indicator, the value date is checked during clearing.
Displaying the bank details used in the payment
You can activate this function via the view maintenance VT042_1 at company code level.
______________________________________________________________
SAP AG
89
SAP System
______________________________________________________________
5.14.1.8 FI-AR-AR-PT
Payment Transactions
5.14.1.8.1 Domestic Payments by PAYMUL (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create DME files for domestic payments
in Denmark in the PAYMUL format.
SAP delivers a new payment method, P (Domestic Payment PAYMUL), which is linked to a Payment
Medium Workbench (PMW) format and a DME format.
Effects on Existing Data
Add the payment method to the master records of the vendors that want you to pay using this format.
Effects on Customizing
IMG activity
What to do
Adjust Note to Payee
Specify what information you want to include in the
note to payee in the DME files.
Assign Payment Medium Format and Note to Payee to Payment Method Assign the note to payee to
the payment method.
Create/Assign Selection Variants
Create a selection variant that the system will use
when you execute the payment program.
Adjust Payment Medium Format
Check the PMW formats and the DMEE formats
provided, and adjust them, if necessary.
See also
Domestic Payment PAYMUL (PMW format documentation)
Domestic Payment PAYMUL (DME format tree documentation)
5.14.1.8.2 Payments in Finland (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create payment files for the following
payment methods using the Payment Medium Workbench (PMW):
Method
A
M
U
Description
Autogiro
Domestic Payments (LM03 Format)
Foreign payments (LUM2 Format)
______________________________________________________________
SAP AG
90
SAP System
______________________________________________________________
For each payment method, SAP delivers a PMW format and a DME format. SAP has changed the
payment methods so that they now use these formats.
SAP will discontinue maintenance of the classic payment medium programs covered by these formats. In
future, when the financial institutions announce changes to their formats, SAP will only change the PMW
formats to match.
We therefore recommend that you switch to the PMW before these institutions announce any changes to
their file formats.
Effects on Customizing
Assuming that you want to use the PMW formats, make the following Customizing settings:
IMG activity
What to do
Adjust Note to Payee
Specify what information you want to include in the
note to payee in the DME files.
Assign Payment Medium Format and Note to Payee to Payment Method Assign the note to payee to
the payment method.
Create/Assign Selection Variants
Create a selection variant that the system will use
when you execute the payment program.
Adjust Payment Medium Format
Check the PMW formats and the DMEE formats
provided, and adjust them, if necessary.
If you do not want to use the PMW, you must reassign the classic payment medium programs to the
payment methods.
See also
For more information about the formats, see the format documentation itself, which you can display in
the IMG activity Assign Payment Medium Format and Note to Payee to Payment Method in the
appropriate payment method.
5.14.1.8.3 Payments by BACS (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create BACS payment files using the
Payment Medium Workbench (PMW).
Note that SAP will discontinue maintenance of the existing program, RFFOGB_T, and that any changes
made by BACS in future will be made in the PMW formats only.
We therefore recommend that you switch to the PMW before BACS announces any changes to its file
formats.
Effects on Customizing
IMG activity
What to do
Set Up Payment Methods per Country for Payment Transactions Change the BACS payment
methods (in the standard system, D (Direct Debit) and E (BACS Transfer)) so that they use the PMW
______________________________________________________________
SAP AG
91
SAP System
______________________________________________________________
format GB_BACS.
See also
GB_BACS (PMW format documentation)
GB_BACS (DME format tree documentation)
5.14.1.8.4 Payments with Bank of Ireland and Allied Irish Banks (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create payment files in the formats used
by the Bank of Ireland (BOI) and Allied Irish Banks (AIB) using the Payment Medium Workbench
(PMW).
Note that SAP will discontinue maintenance of the existing program, RFFOGB_T, and that any changes
made by BOI and AIB in future will be made in the PMW formats only. We therefore recommend that
you switch to the PMW before BOI and AIB announce any changes to their file formats.
SAP has changed payment method E so that it supports electronic funds transfer using the BOI format
only. F is a new payment method that supports the AIB format. You can of course decide which tree is
used with which payment method.
Effects on Existing Data
Add the new payment method, F, to the master records of the vendors that want you to pay using this
format.
Effects on Customizing
IMG activity
What to do
Set Up Payment Methods per Country for Payment Transactions
F
Check the payment methods E and
See also
IE_BOE (PMW format documentation)
IE_BOI (DME format tree documentation)
IE_AIB (PMW format documentation)
IE_AIB (DME format tree documentation)
5.14.1.8.5 Payments in Sweden (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create payment files for the following
payment methods using the Payment Medium Workbench (PMW):
______________________________________________________________
SAP AG
92
SAP System
______________________________________________________________
Method
A
H
I
P
S
Description
Autogiro for Individuals
Foreign Payments (Handelsbanken)
Domestic Payments (Bankgirot)
Domestic Payments (Postgirot)
Foreign Payments (SE-Banken)
For each payment method, SAP delivers a PMW format and a DME format. SAP has changed the
payment methods so that they now use these formats.
SAP will discontinue maintenance of the classic payment medium programs covered by these formats. In
future, when the financial institutions announce changes to their formats, SAP will only change the PMW
formats to match.
We therefore recommend that you switch to the PMW before these institutions announce any changes to
their file formats.
Effects on Customizing
Assuming that you want to use the PMW formats, make the following Customizing settings:
IMG activity
What to do
Adjust Note to Payee
Specify what information you want to include in the
note to payee in the DME files.
Assign Payment Medium Format and Note to Payee to Payment Method Assign the note to payee to
the payment method.
Create/Assign Selection Variants
Create a selection variant that the system will use
when you execute the payment program.
Adjust Payment Medium Format
Check the PMW formats and the DMEE formats
provided, and adjust them, if necessary.
If you do not want to use the PMW, you must reassign the classic payment medium programs to the
payment methods.
See also
For more information about the formats, see the format documentation itself, which you can display in
the IMG activity Assign Payment Medium Format and Note to Payee to Payment Method in the
appropriate payment method.
5.14.1.8.6 Payment Program SAPF110S (Enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following functions are available in the
area Paying with the Payment Program SAPF110S:
o
Debit balance check with report RFF110SSP
______________________________________________________________
SAP AG
93
SAP System
______________________________________________________________
o
Following new Business Transaction Events (BTEs):
-
00001820 Payment Program: Item Selection
-
00001830 Payment Program: Process Group
Effects on Customizing
If you want to use the BTEs, carry out the IMG activity Business Transaction Events in the
Implementation Guide (IMG) for Financial Accounting.
See also
For more information about the debit balance check, see the documentation for the report.
For more information about BTEs, see the IMG for Financial Accounting under Financial Accounting
Global Settings -> Business Transaction Events.
5.14.1.9 FI-AR-AR-DU
Dunning
5.14.1.9.1 Performance Dunning Program
Use
Previously the dunning program selected all the items in the customer account but only actually dunned
"dunnable" items. In particular, a large number of advance postings were selected (K items), but these
were not actually dunned. You can now exclude these from the selection by excluding the respective
reconciliation accounts from the selection.
5.14.1.10 FI-AR-AR-OI
Open Item Management
5.14.1.10.1 Residual Items in Invoice Currency (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can carry out residual item postings in
invoice currency.
The residual items are cleared in the payment document (similar to transfer posting with clearing) and
posted to the same customer as an open item in the currency of the original invoice.
The clearing document number in the original invoice, in the residual item of the payment document, and
in the new residual item documents is the number of the payment document.
For a payment document that covers one or more residual items, these residual items are cleared
irrespective of the currency and a new residual item document is posted for each residual item.
The following information is transferred from the invoice for the new residual items:
o
Document date, reference document number, currency key
______________________________________________________________
SAP AG
94
SAP System
______________________________________________________________
o
Invoice reference
The following information is used for the new residual items for the transfer posting from the payment:
o
Posting date
o
Translation date
The amounts of the new residual items are translated as follows:
The amount in document currency of the new residual item is determined from the local currency amount
using the date of the payment document.
The amounts of the second and third local currency of the new residual item are taken from the residual
item of the payment document.
Note: Even if Customizing specifies a determination of the second and third local currency based on the
document currency, only the exchange rates based on the time of payment are changed. This has no effect
on the amounts in the parallel currency.
Effects on Customizing
Make the required settings for the residual item posting in invoice currency.
To activate the function in the required company code, you must have defined a document type.
See also
For more information, see the documentation of the Implementation Guide under Financial Accounting
-> Accounts Receivable and Accounts Payable Accounting -> Business Transactions -> Open Item
Clearing -> Clearing Differences -> Residual Item Posting in Invoice Currency.
5.14.1.11 FI-AR-AR-CR
Correspondence
5.14.1.11.1 Balance Confirmation (Enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the following new functions in the
balance confirmation:
o
Cross-company code balance confirmation (with individual request)
This applies for the Customer Balance Confirmation (SAPF130D) and the Vendor Balance
Confirmation (SAPF130K).
A balance confirmation is created for each customer/vendor. All company codes assigned to the
correspondence company code are taken into account. The balance confirmation is addressed to the
correspondence company code.
For more information, see the documentation for the reports Customer Balance Confirmation and
Vendor Balance Confirmation in the section Group Version.
o
New event for faxing, archiving, and sending as e-mail (Business Transaction Event 2410)
For more information, see the documentation for the function module
FI_OPT_ARCHIVE_BALANCE_CONFIRM.
______________________________________________________________
SAP AG
95
SAP System
______________________________________________________________
Effects on Customizing
To use the cross-company code balance confirmation, make the following setting in the Implementation
Guide for Financial Accounting: Financial Accounting Global Settings -> Correspondence ->
Assign Company Codes to Correspondence Company Codes
5.14.1.12 FI-AR-AR-CL
Closing Operations
5.14.1.12.1 Structure Changes in Inflation Accounting
Use
As of SAP R/3 Release 4.70, the Implementation Guide (IMG) for Inflation Accounting is easier to use.
SAP has restructured it, rewritten the documentation, and reworked some of the screens.
Note that only the IMG structure and documentation have changed, but not the views themselves, so you
do not have to make any changes to existing Customizing settings.
Changes in the IMG
Until now, there was one group of IMG activities for Inflation Accounting under Financial Accounting
(FI), and more activities under Asset Accounting (FI-AA) and Materials Management (MM). That
meant that to customize Inflation Accounting for FI-AA, for example, you had to work through the
activities under FI and those under FI-AA.
SAP has now changed the IMG so that each of the components now has its own self-contained IMG for
Inflation Accounting. Now, to customize Inflation Accounting for FI-AA, for example, you no longer
have to work through the IMG activities under Revaluation for the Balance Sheet and then the
activities under Inflation Accounting. Nor do you have to work through the activities under Financial
Accounting -> Financial Accounting Global Settings -> Inflation Accounting. Instead, you just have
to work through the activities under Inflation Accounting. Similarly, the IMG activities for FI and MM
have also been restructured.
The IMGs are still located at the same position in the SAP Reference Structure:
o
Financial Accounting -> Financial Accounting Global Settings -> Inflation Accounting
o
Financial Accounting -> Asset Accounting -> Special Valuation -> Revaluation of Fixed
Assets -> Revaluation for the Balance Sheet -> Inflation Accounting
o
Materials Management -> Valuation and Account Assignment -> Balance Sheet Valuation
Procedures -> Configure Replacement Cost Procedure (Inflation)
Changes in the SAP Library
The Inflation Accounting documentation in the SAP Library has also been split up between the three
components. It is now located under the following paths:
o
Financial Accounting (FI) -> General Ledger Accounting (FI-GL) -> Closing and Reporting
-> Preparing Financial Statements -> Inflation Accounting
o
Financial Accounting (FI) -> Asset Accounting (FI-AA) -> Special Valuation -> Replacement
Values (General) -> Inflation Accounting
______________________________________________________________
SAP AG
96
SAP System
______________________________________________________________
o
Materials Management (MM) -> Evaluation -> Balance Sheet Valuation (MM-IM-VP) ->
Replacement Cost Valuation (Inflation)
5.15 FI-BL
Bank Accounting
5.15.1 FI Cash Journal (Extended)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the following additional functions:
o
Document split
In the FI cash journal, you can post expenses and receipts that consist of several line items: You can
have different account assignments for a revenue or an expense (for example, split over different
profit centers), or you can split the total amount of an external document that contains different tax
codes.
o
Support for one-time vendors and customers
In the FI cash journal, you can execute a posting that posts to a one-time account: If you use a
one-time account in the cash journal, the dialog box for entering one-time account data is called up
automatically and the entries are saved in the cash journal.
See also
For more information, see the SAP Library under Accounting -> Financial Accounting -> Bank
Accounting -> Payment Transactions -> Cash Journal.
5.15.2 Repetitive Codes (Modified)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the master data maintenance for Repetitive
Codes has been technically and functionally revised. Previously, you could only use repetitive codes to
create payment advice notes in Cash Management (TR-CM). The system then used these payment
advice notes to create payment orders in a subsequent step. Now you create payment orders from
repetitive codes in one step. You can no longer create payment advice notes.
You can use repetitive codes for recurring payments in the followng areas:
o
Bank account transfers
o
Payments to business partners
o
Online payments to vendors
You can access the processing of repetitive codes in the application menu under Accounting ->
Financial Accounting -> Banks -> Master Data -> Repetitive Codes.
The fast entry with repetitive codes is located in the application menu under Accounting -> Financial
______________________________________________________________
SAP AG
97
SAP System
______________________________________________________________
Accounting -> Banks -> Outgoings -> Payments with Repetitive Codes.
Effects on Existing Data
When you call up the function for processing repetitive codes, the existing repetitive codes are
automatically converted to the new version.
See also
For more information about processing repetitive codes, see the SAP Library under Accounting ->
Financial Accounting (FI) -> Bank Accounting (FI-BL) -> Bank Accounting (FI-BL) -> Bank
Master Data -> Processing Repetitive Codes.
For more information about fast entry with repetitive codes, see the SAP Library under Accounting ->
Financial Accounting (FI) -> Bank Accounting (FI-BL) -> Bank Accounting (FI-BL) -> Payment
Transactions -> Fast Entry with Repetitive Codes.
For more information about using repetitive codes for online payments, see the release information
Transaction for Entering Online Payments.
5.15.3 FI-BL-MD
Master Data
5.15.3.1 FI-BL-MD-BK
Bank Master Data
5.15.3.1.1 IBAN (International Bank Account Number) (new)
Use
As from SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can save the IBAN in your SAP
system master data for use when you create payment media. The following master data are examples:
o
Vendors
o
Customers
o
House bank accounts
o
Treasury business partners
o
Employee data
o
Central business partners
The IBAN is a standardized, uniform ID number for displaying bank details in accordance with the ECBS
(European Committee for Banking Standards). You can simplify payment processing by using this
standard both domestically and above all abroad. This can also bring advantages regarding bank charges.
SAP includes the IBAN in the standard system in those payment medium formats where the relevant state
central bank or the overwhelming number of credit institutions prescribe the use of the IBAN. This
applies mostly to European countries.
The functions for using the IBAN have already been delivered by SAP in various Support Packages,
including (among others) SAPKA46C21, SAPKH46C21, SAPKA46D10 and SAPKA50A01. It may be
that your company is already using the IBAN.
______________________________________________________________
SAP AG
98
SAP System
______________________________________________________________
You will find pushbuttons for the bank details data you can use to create and change an IBAN. The
symbol on the pushbutton tells you whether or not an IBAN is present for a set of bank details (green
arrow = yes, white arrow = no).
See also
You can find additional information on the IBAN if you have received this function by Support Package
in SAP Note 392091 (IBAN: Use for vendors and customers).
5.15.4 FI-BL-BM
Cash Balance Management
5.15.4.1 FI-BL-BM-CM
Check Management
5.15.4.1.1 Integration of check management in PMW and IDoc
Use
The payment register that offers various display, processing and reporting functions has to date only
contained entries from the check management transactions.
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can also receive entries for payments
where the payment medium was created using the Payment Medium Workbench (PMW). You can
display the data with the check management transactions. For reporting it is worthwhile creating
matching ALV layouts in the check register.
Note: in the Payment Medium Workbench (PMW) you can use the 'Check number' created both in the
note to payee and when you create the payment medium (for example for mapping in the DME Engine).
The same function is available to you when you generate payment IDocs with program RFFOEDI1.
Effects on Existing Data
The system only creates entries in the payment register after you have activated this function. Old
payments are not transferred to the register.
Effects on Customizing
To activate this function you have to flag an additional check lot with the PMW payment method. To do
this, when processing the check lot you have to define in the detail screen of the check lot the payment
method in the payment method list. Make the following setting in the Implementation Guide (IMG)
Accounts Receivable and Accounts Payable : Define number ranges for checks.
You are recommended to define only one check lot for each payment method, and to use the payment
method as a prefix to the check number so as to avoid conflicts with actual check number ranges.
Example:
Lot
list
9900
Check number from Check number to
Next lot
Payment method
U000000000001
(no entry)
U
U999999999999
______________________________________________________________
SAP AG
99
SAP System
______________________________________________________________
9901
T000000000001
5.15.4.2 FI-BL-BM-BE
T999999999999
(no entry)
T
Bill of Exchange Management
5.15.4.2.1 Printouts of Bill of Exchange Transaction Records (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the Bill of Exchange Transactions program as
used in Thailand and Turkey offers more features for printing bill of exchange transaction records.
First, a new IMG activity has been added to the SAP Reference Implementation Guide, where you can
specify which SAPscript form you want to use for the transaction records.
Second, the program provides more data for the transaction record forms, for example, the name and
address of the customer, or the endorsee.
If you want to create a new form, copy the SAPscript form provided and adjust the copy accordingly.
Then enter the form in the IMG activity listed below.
Effects on Customizing
IMG activity
What to do
Specify SAPscript Form for Transaction Records
Enter the SAPscript form for the transaction
records, if the standard form does not meet your requirements.
5.15.4.2.2 Bill of Exchange Transactions Program (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the Bill of Exchange Transactions program as
used in Thailand and Turkey offers a new feature.
When you run the program, it displays a list of the bills of exchange selected, as before.
If you want to see the total value or the average due date of a range of the bills in the list, select them and
choose Info About Selection. The program displays the information in a dialog box.
5.15.5 FI-BL-PT
Payment Transactions
5.15.5.1 Cross-country bank account transfers (new)
Use
You can give transfer requests for bank account transfers from Treasury (TR) to the bank using the
______________________________________________________________
SAP AG
100
SAP System
______________________________________________________________
payment program for payment requests (Transaktion F111). Until now this was always subject to the
restriction that the company code of the sending bank account and that of the receiving bank account had
to be in the same country and have the same local currency.
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) this restriction has been lifted.
In the payment program for payment requests (transaction F111) the number of postings from
cross-country bank account tranfers is detailed in the payment run status display. If errors occur (for
example, incomplete Customizing) and also for reporting purposes program RFPRQP00 is available to
you.
Effects on Customizing
For each company code define a clearing account for payment requests if this has not yet been done in
Treasury. Make the following settings in bank accounting Customizing: Define clearing accounts for
cross-country bank account transfers.
5.15.5.2 Transaction for entering online payments (enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the transaction for the online data entry of
payment requests has been restructured and provided with additional functions. As is already the case for
vendors and recipients without a master record (free form payments) you can now use online date entry
for customers.
Various functions support you in entering the payment data. For instance, some fields are predefined with
the date of the last entry. You can also create variants. For free form payments you can get the recipient
data from a customer or vendor master record without the subledger account existing in the current
company code.
If you have defined the payment data in the system for repetitive payments to a vendor under a Repetitive
Code, you can use this for the data entry.
Parallel to the payment request the program creates an accounting document. You can select the
document type for this document. With free form payments you can determine whether you post to G/L
accounts, vendor or customer accounts.
Effects on Existing Data
The system copies variants that you have created with the previous transaction. Hence you can continue
to use them. However, no information for the date fields is saved in the variants for the new transaction as
used to be the case with variants with the old transaction. Consequently the content of the date fields of
the old variants is lost.
Effects on Customizing
The vendor payment requests are managed in the system under the origin FI-AP-PR, the customer
payment requests under origin FI-AR-PR and the free form payments under origin FI-BL. For each of
these origins you can make the following settings in the Implementation Guide (IMG) for Bank
Accounting:
o
Specify the desired process step. To do so use the IMG activity Define Process Steps .
______________________________________________________________
SAP AG
101
SAP System
______________________________________________________________
o
Specify the document types for the corresponding accounting document. To do so use the IMG
activity Define Document Types.
See also
You can find additional information about further changes for payment requests in the release
information cross-payment run payment medium creation.
More information about repetitive codes can be found in the SAP library under Accounting -> Financial
Accounting (FI) -> -> Bank Accounting (FI-BL) -> Bank Accounting (FI-BL) -> Bank Master Data
-> Maintain Repetitive Codes.
More information about payment media can be found in the report documentation creation of
cross-payment run payment media.
5.15.5.3 Check Printing Program RFFOUS_C (Enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the indicator Do Not Void Checks has been
added to the check printing program RFFOUS_C. You can use this indicator to prevent the system noting
voided checks, such as test prints, page overflow, and form summary section in the check register.
You may have to adjust existing report variants for the check printing program RFFOUS_C and existing
SAPScript forms in accordance with the documentation of the new parameter.
See also
Documentation for the new parameter Do Not Void Checks .
5.15.5.4 Cross-Payment Run Payment Medium Creation (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can summarize payments from different
payment runs in one payment medium. This allows you to separate internal accounting from the deadlines
specified by the banks for the submission of payment media. In addition, you can achieve an
improvement in performance by processing the payment runs in parallel, without creating large numbers
of unnecessary payment files as a result.
You can use this function for the following payments:
o
Vendor and customer payments
o
Payments from Treasury
o
Online payments
o
Payments with repetitive code
o
Personnel payments
o
Payments from travel expenses
______________________________________________________________
SAP AG
102
SAP System
______________________________________________________________
Effects on Existing Data
Once you have activated the function, the system summarizes all of the corresponding payment runs
selected in payment media. Payment runs that you executed before activating the function are not
affected, meaning you must create the related payment media as before.
Effects on Customizing
To activate the function, you have to define run identifications for payment runs that can only be
processed using the program for creating cross-payment run payment media. To do so, make the
following setting in the Implementation Guide (IMG) for Bank Accounting: Define indentification for
cross-payment run payment media.
See also
You can find additional information on creating online payments in the release information transaction
for creating online payments.
You can find more information on creating cross-payment run payment media in the documentation for
program SAPFPAYM_MERGE, in which the reporting options and link to the Payment Medium
Workbench are explained.
5.15.5.5 FI-BL-PT-BS
Bank Statement
5.15.5.5.1 FI-BL-PT-BS-EL
Electronic Bank Statement
5.15.5.5.1.1 DRB (Enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , the Document Relationship Browser (DRB)
offers an extended selection of object types. Object types have been added to the DRB, and object types
that were already connected in earlier releases have been completed.
New object types:
o
Profit center document
o
Costing-based profitability analysis
o
Electronic account statement
o
Production order
o
Backflush document
The connection of these object types only affects the functions within the DRB. There are no separate
access programs.
Enhanced object types:
o
Accounting document
From the document display (transaction FB03), you can branch to the DRB. You can use report
______________________________________________________________
SAP AG
103
SAP System
______________________________________________________________
RDRBFI00 to access the DRB and to find archived accounting documents via the archive
information system (SAP AS).
o
Controlling document
From the line item reports (for example, transaction KSB1, KSB5, KOB1), you can branch to the
DRB.
The DRB functions can find Controlling documents in the archives of all archiving objects that
archive Controlling line items. There are several field catalogs and info structures for this.
See also
For more information about the Document Relationship Browser, see the SAP note 492938.
5.15.5.5.1.2 Conversion of Incoming Electronic Bank Statments in LUM2 Format
(New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system offers a new report for converting
electronic bank statements that contain information about foreign payments that have been made in the
Finnish LUM2 format using the Payment Medium Workbench.
When the bank sends you an electronic bank statement, use the new Conversion Program to convert the
file into MultiCash format.
Once the file has been converted, import it using the standard Electronic Bank Statement Program.
To access the conversion program, from the SAP Easy Access menu, choose Accounting -> Financial
Accounting -> Banks -> Incomings -> Bank Statement -> Import -> RFEBFILUM00.
Effects on System Administration
Add a function module to the program as described in SAP Note 418855.
Effects on Customizing
IMG activity
What to do
Make Global Settings for Electronic Bank Statement See the program documentation below for
instructions.
See also
Report documentation
5.15.5.5.1.3 Electronic Bank Statement (extended)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the functions of the Electronic bank
statement were extended as follows:
______________________________________________________________
SAP AG
104
SAP System
______________________________________________________________
o
Processing Returns
You can find further information in the release note Processing returns in the electronic bank
statement (new).
o
Search from open items in several bank subaccounts (worklist)
In Customizing of the Electronic bank statement in the IMG-activity Maintain basic settings for
the electronic bank statement under Assign bank accounts to transaction category you can
specify a worklist for General Ledger accounts.
When postprocessing the bank statement (from screen SAP Easy Access to Accounting ->
Banks -> Incomings-> Bank statement -> Postprocess) you can search in several subaccounts
for the open items that the system could not clear during immediate bank statement posting.
o
Setting "No automatic clearing"
In the IMG_activity mentioned above, you can set it so that the Electronic Bank Statement does
not automatically clear an open item, if the selection criteria is only the amount .
You can thereby prevent items being cleared only because the amount of the open item is consistent
with the bank statement.
o
Interpretation algorithm 120 (Document number search without proof reading), 121 (Reference
document number search without proof reading)
The new interpretation algorithms search for document numbers or Reference document numbers in
the payment note and do not check whether the document number or the reference document
number exist in the system. They only check if the number lies in the number interval which you
specify when importing the bank statement. If you set this interpretation alogorithm in Customizing
of the Electronic bank statement, then the Electronic bank statement can also clear open items
that exist in a different bank company code.
o
Link between document and line items
In the bank statement document display that you posted with the posting parameter Post
immediately />, you can display the line items which belong to the bank statement.
Select Object Services -> Links.
See also
You can find further information in the SAP library under >Accounting -> Financial Accouting ->
Bank Accounting -> Electronic Bank Statement.
5.15.5.5.1.4 Postprocessing the electronic bank statement (new)
Use
As of SAP R/3 Enterprise Financials Extension 1.10 (EA_APPL 110) you can use the new
transaction FEBAN to select and correct much more quickly bank statement items that the function
electronic bank statement had not posted automatically.
To do this, in the SAP Easy Access screen choose Financial Accounting -> Banks -> Incomings ->
Bank Statement -> Postprocess.
You can use the filter, search and sorting functions of the SAP List Viewer (ALV) to display and edit the
items in bank statements in such a way as best suits your method of working. With just one key stroke
you can trigger the automatic posting of several items at the same time automatically. The note to payee,
______________________________________________________________
SAP AG
105
SAP System
______________________________________________________________
which contains important information for the automatic posting of bank statement items, remains visible
in a separate window while you process the posting screen.
See also
You can find a detailed description of the function in the SAP library under Accounting -> Financial
Accounting (FI) -> Bank Accounting (FI-BL) -> Electronic Account Statement.
5.15.5.5.1.5 Processing of returns in the electronic bank statement (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can
process return debit memos individually with the Electronic bank statement. The system creates a line
item with the debit memo amount (negative) from the returns and also a line item with charges if
necessary. Both the returns line items as well as the charge can be processed according to their own
posting rules. A previously cleared item can be reopened and blocked for payment.
I fthe format you are using to transfer the bank statement data does not provide fields for charges or the
Return reason, you can search for this information with the Business Add-In (BAdI)
FIEB_RETURNS_ADDIN in the bank statement data.
Effects on Customizing
Execute the following activities in the Bank Accounting Customizing:
o
Set up processing of returns
o
Business-Add-In: Processing of returns
Only execute this activity if you want to use the BAdI.
See also
YOu can find further information in the SAP library under Accounting -> Financial Accounting ->
Bank Accouting -> Electronic Bank Statement.
5.16 FI-AA
Asset Accounting
5.16.1 New Account Assignment Objects in the Asset Master Record
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following new account assignment objects are
also included in the time-dependent data in the asset master record:
-
Funds center
-
Funds center for investment purposes
-
Functional area
______________________________________________________________
SAP AG
106
SAP System
______________________________________________________________
-
Functional area for investment purposes
-
Fund
-
Fund for invesment purposes
-
Grant
-
Grant for investment purposes
-
Real estate object
-
Work breakdown structure (WBS) element (for costs)
Account assignment objects "for investment purposes" differ from the other objects in that only APC
postings can be made to them. It is not possible to post depreciation to these objects. You specify the
details for account assignment to each of these objects in Customizing. Choose Financial Accounting ->
Asset Accounting -> Integration with the General Ledger -> Additional Account Assignment Objects.
Effects on Customizing
The system continues as before if you do not make any changes to Customizing. In order for you to be
able to enter the new account assignment objects in the asset master record, they have to be active in the
given company code.
o
Activating the account assignment objects:
-
Asset Accounting -> Integration with the General Ledger -> Additional Account Assignment
Objects
The active objects also have to be ready for input according to the screen layout rule for the
time-dependent data.
o
Maintenance of screen layout rules:
-
Asset Accounting -> Master Data -> Screen Layout -> Define Screen Layout for Asset Master
Data
5.16.2 Customizing: Resetting Asset Transactions (New)
Use
Up to now, you could delete both asset master records and transactions together using the Reset Company
Code Customizing function (transaction OABL, in IMG choose Asset Accounting -> Preparing for
Production Startup -> Tools -> Reset Company Code). Now you can delete just the transactions while
keeping the master records by selecting a checkbox in the transaction.
______________________________________________________________
SAP AG
107
SAP System
______________________________________________________________
5.16.3 Parallel Valuation in Asset Accounting
Use
In addition to the existing options for parallel valuation, it is now possible to update values in a different
company code or in a special ledger. This function can be used, for example, to post values to an
alternative company code from a depreciation area that records differences between areas, and then to
create a separate financial statement in the alternative company code.
It is also possible for more than one depreciation area to post automatically online, without needing to
post to a different company code or to a special ledger.
Effects on Customizing
You make Customizing settings using transaction ACCMAP.
5.16.4 FI-AA-AA
5.16.4.1 FI-AA-AA-MA
Basic Functions
Asset Maintenance
5.16.4.1.1 Investment Support Areas Modifiable Using BAPIs for Asset Master
Recor
Use
You can now create and delete investment support depreciation areas using the "FixedAsset" BAPI
methods. To achieve this, the "Investment_Support" table was added to the interfaces of the following
methods:
o
"CreateFromData1" for creating asset master records
"Change" for changing asset master records
"CreateInclValues" for legacy data transfer
Using the "CreateFromData1" method, you can create investment support depeciation areas by
transferring one or more investment support keys.
Using the "Change" method, you can now create and delete investment support depreciation areas.
Using the "CreateInclValues" method, you can also transfer investment support to assets from a legacy
system.
See also
For more information, refer to the documentation of the "Investment_Support" import parameter in the
BAPI Explorer.
______________________________________________________________
SAP AG
108
SAP System
______________________________________________________________
5.16.4.1.2 Creating Subnumbers in Purchase Orders and Purchase Requisitions
(New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create asset main numbers and
subnumbers in the transactions ME21N "Create Purchase Order" and ME51N "Create Purchase
Requisition".
5.16.4.2 FI-AA-AA-DE
Depreciation
5.16.4.2.1 Enhancement of User Exits in Depreciation Calculation
Use
User exits EXIT_SAPLAFAR_001 and EXIT_SAPLAFAR_004 were expanded, especially for Japanese
group depreciation. The enhancements to the functions were incorporated into the existing program code
for depreciation calculation.
1.
User Exit EXIT_SAPLAFAR_001
Import parameter I_SUMLFDAFA and export parameter E_SUMLFDAFA were added to this user
exit. Global parameter SUMLFDAFA contains the current depreciation up to this point for the asset
being processed. It is calculated by adding the planned depreciation and the depreciation for the
current year for all transactions. The SUMLFDAFA value is transferred to I_SUMLFDAFA, and the
calculated value is returned to SUMLFDAFA via E_SUMLFDAFA. For transactions that are in the
year in which the asset reaches its scrap value, this parameter serves as an indicator for reducing the
depreciation.
2.
User Exit EXIT_SAPLAFAR_004
If an asset is assigned to a group asset, then the asset numbers belonging to the group asset are
stored in the user exit in the I_ANTS-ANLN1_ABG and I_ANTS-ANLN2_ABG fields when the
group asset is processed. This makes it possible for the system to read specific data of individual
assets while processing the group asset. The E_PERCENT_ACT and E_PERCENT_V fields were
also added to the interface of the user exit. The field is an activation flag, that is used to show that
dividing all value adjustments into value adjustments for the current and prior years is controlled by
the E_PERCENT_V field. E_PERCENT_V shows the percentage that should be calculated as value
adjustments (depreciation) in the previous year (E_PERCENT_V = 1 means 100%).
Effects on Existing Data
The existing functions are not affected.
Effects on Customizing
For more information, refer to these IMG activities:
Develop Enhancement for Determining Base Value
______________________________________________________________
SAP AG
109
SAP System
______________________________________________________________
Develop Enhancement for Calculating Proportional Values
5.16.4.2.2 Change to Rounding with Base Method Immediate Depreciation
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system no longer rounds when you use
this method. This applies regardless of what the settings for rounding may be in Customizing.
Effects on Existing Data
Until now there were undesired rounding effects when a complete depreciation key (depreciation method
V) was used. Particularly in the case of an inverse posting using the same amount, there was sometimes
nonetheless a net book value remaining on the asset.
It is possible that there might be rounding differences after the upgrade if depreciation is recalculated.
5.16.4.3 FI-AA-AA-TR
Transactions
5.16.4.3.1 New BAdI for Changing the Asset Document
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the BADI_FIAA_DOCLINES BAdI allows
you to change the asset accounting document, as created by the system, to meet your own specifications.
There are several different methods available (refer also to the documentation of the BAdI).
The system then performs only the checks for the asset reconciliation accounts on the changed document.
5.16.4.3.2 Changes to Posting
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following changes have been made to
posting transactions:
o
The old posting transactions based on AB01 allowed a generic retirement on the asset subnumber.
The new Enjoy posting transactions now generally allow generic posting to a subnumber
(acquisitions, retirements, post-capitalization and intracompany transfers) using the Multiple assets
function.
o
If the Joint Venture Accounting extension is active in the company code that is to be posted, then
you can enter the cost type manually in the Enjoy posting transactions.
o
It is now possible to post a retirement to a fixed asset using the FI transactions without posting
______________________________________________________________
SAP AG
110
SAP System
______________________________________________________________
values to book depreciation. Previously this was not possible and the system issued an error
message.
o
The display of asset accounting documents was changed over to the ALV Grid Control for all
posting transactions.
5.16.4.3.3 Settlement of Investment Support for Assets Under Construction
(Extended)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can also settle investment support from
independent assets under construction (AUC), and from AUC that belong to investment measures posted
to the AUC during the settlement year.
Previously, you could only post investment support to completed assets in the year of capitalization.
When determining the proportion of investment support to be transferred for partial capitalization or
distribution to several receivers, it is assumed that investement support posted to the AUC during the year
of capitalization also refers to asset acquisitions during the year of capitalization.
If the investment support that you post to AUC refer to prior-year acquisitions, you must use the
transaction type Kxx for the investment support measure xx.
Effects on Existing Data
If you used transaction type Ixx to post to the AUC investment support that refers to prior-year
acquisitions, delete these postings and repost them using the relevant transaction type Kxx.
Effects on Customizing
Check whether a transaction type Kxx is also created for the investment support measures used. (Usually
these transaction types are created automatically when you set up the investment support measure.) To do
this, use the process step
Check Transaction Types for Support Measures.
5.16.4.3.4 FI-AA-AA-TR-AC
Acquisitions
5.16.4.3.4.1 New Transaction Type for Post-Capitalization
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the new transaction type 401 is available for
depreciating post-capitalizations from the start of the fiscal year, regardless of the period control entered.
The asset value date of the posting determines the fiscal year.
Depending on your needs, you can either use the new transaction, or continue to use transaction type 400.
______________________________________________________________
SAP AG
111
SAP System
______________________________________________________________
5.16.4.3.5 FI-AA-AA-TR-ST
Elemen
Budget Monitoring by Statistical Order / WBS
5.16.4.3.5.1 Change to Budget Monitoring with Orders/WBS Elements
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), there is a change to Customizing related to
monitoring budgets using statistical orders or WBS elements. Until now, you had to specify in
Customizing for Asset Accounting or Investment Management that the asset accounting transaction type
was relevant for the budget. This IMG activity has now been replaced by the new central controls for
additional account assignment in Asset Accounting.
Effects on Existing Data
The previously existing control using the Budget relevant indicator is automatically migrated to the new
structure during the upgrade.
See also
For more infomation, also see the Release Information on the subject of New Account Assignment
Objects.
5.16.4.3.6 FI-AA-AA-TR-PG
Posting Depreciation to the General Ledger
5.16.4.3.6.1 New Report for Periodic Posting of APC Values: RAPERB2000
Use
Report RAPERB2000 is an improvement of report RAPERB00 for posting periodic APC values. The
main differences between the two reports:
o
The new APC posting run supports all expanded account assignments during posting.
o
APC values are posted directly to the general ledger. The report no longer generates a BDC folder.
In order to be able to post the documents directly, you have to enter a document type with external
number assignment for the company code.
o
Checks during the test run were expanded, they are now identical to those in the update run.
o
The log output was completely reworked and converted to ALV grid technology.
o
RAPERB2000 allows a restart if there is an update termination. The assigned document numbers are
now also included in the log.
o
It is possible to start the periodic posting run for several company codes at the same time using
report RAPERB2010.
o
The link to the Schedule Manager was improved, you can go directly to the Monitor.
o
APC values can be posted directly to a special ledger or to an alternative company code on the basis
______________________________________________________________
SAP AG
112
SAP System
______________________________________________________________
of an accounting principle (refer to Parallel Valuation in Asset Accounting).
o
For derived depreciation areas, you can post real APC differences.
o
The partner information from the asset line item of the original document is copied into the periodic
posting document. The system generates a separate FI document per month, per depreciation area
and per trading partner.
Effects on Customizing
You have to enter a document type with external number assignment for the company code (Proceed).
5.16.4.3.6.2 New Report for Depreciation Posting: RAPOST2000
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), Report RAPOST2000 replaces Report
RABUCH00 for posting depreciation. The main differences between the new and old reports are:
o
The new depreciation posting run supports the expanded account assignments that are also new in
SAP R/3 Enterprise Core 4.70 (SAP_APPL 470).
o
Depreciation is posted directly to the general ledger. The system no longer creates a BDC folder. In
order to make direct posting of documents possible, the 'Batch input only' setting is not allowed in
document types for depreciation posting (for example, AF).
o
The checks that take place in the test run were expanded, they are now identical to those that take
place in an update run.
o
If there is an error due to a locked cost center, you can continue immediately after correcting the
asset master record.
o
You can display the log of a depreciation posting run using report RAPOST2001. This report
replaces the previous report, RABUCH30.
o
It is possible to start the depreciation posting run for multiple company codes at the same time using
report RAPOST2010.
o
The link to the Schedule Manager was improved. It is possible to jump directly to the monitor.
o
If you have cost accounting across company codes, you can set the report for the document type
(and thereby also the internal or external number assignment) of the other company code.
Independently of the depreciation area, the report accesses the clearing accounts that were set up in
Customizing between the company codes.
5.16.5 FI-AA-SVA
Special valuation
5.16.5.1 Depreciation Using Half-Year and Annual Rates in Japan (New)
Use
______________________________________________________________
SAP AG
113
SAP System
______________________________________________________________
Japanese tax laws allow companies to depreciate property with a different percentage rate in the first half
of the fiscal year than in the second half. You can reflect this in the system using the Explicit percentage
rate, Japanese half-year depreciation depreciation method. The procedure described in the
documentation of the report is allowed only for fiscal years that have 12 periods. At the present time we
cannot offer a solution for fiscal years that have lengths other than 12 periods.
Effects on Customizing
In Customizing for Asset Accounting, create a depreciation key and assign a base method to it that
contains the Explicit percentage rate, Japanese half-year depreciation depreciation method. The
declining-balance method and multi-level method of the depreciation key do not contain a percentage
rate, since this is determined automatically from table T097JP.
The depreciation percentage rate for the planned useful life of an asset is fixed in table T097JP. During
the first half of the year, the system calculates using twice the planned useful life; in the second half of
the year it uses the normal useful life.
When you use various multiple-shift factors in the time-dependent data, then the percentages are
multiplied by the respective multiple-shift factors. For the second half of the year, the system only takes
time intervals into account that fall in the second half of the year.
5.16.5.2 FI-AA-SVA-HI
Handling of Inflation
5.16.5.2.1 Reverse Multiple Asset Revaluation Documents (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the R/3 System offers a new program that you
can use to reverse multiple asset revaluation documents simultaneously.
The program's name is J_1AAINFL_REVERSE.
See also
SAP Library -> Financials -> Financial Accounting (FI) -> Asset Accounting (FI-AA) -> Special
Valuation -> Replacement Values (General) -> Inflation Accounting -> Reverse Multiple Asset
Revaluation Documents.
5.16.5.2.2 Revaluation After End of Useful Life (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can revaluate assets after they reach the end
of their useful life. Up until now, this option was not supported.
Effects on Existing Data
If you want to revaluate assets after the end of their useful life, the assets need to be assigned an
appropriate depreciation key. In that case, you may need to assign your asset master records a different
______________________________________________________________
SAP AG
114
SAP System
______________________________________________________________
depreciation key.
For details, see the SAP Library documentation listed below.
Effects on Customizing
Specify in the IMG activity Maintain Inflation Methods whether you want to activate this function or not.
You must carry out this activity, otherwise the system will not allow you to execute the Asset
Revaluation (Inflation) program.
See also
SAP Library -> Asset Accounting (FI-AA) -> Special Valuation -> Replacement Values (General)
-> Inflation Accounting -> Revaluation of Assets at Regular Intervals -> Asset Revaluation
(Inflation) Program -> Revaulation After End of Useful Life.
5.16.5.2.3 Structure Changes in Inflation Accounting
Use
As of SAP R/3 Release 4.70, the Implementation Guide (IMG) for Inflation Accounting is easier to use.
SAP has restructured it, rewritten the documentation, and reworked some of the screens.
Note that only the IMG structure and documentation have changed, but not the views themselves, so you
do not have to make any changes to existing Customizing settings.
Changes in the IMG
Until now, there was one group of IMG activities for Inflation Accounting under Financial Accounting
(FI), and more activities under Asset Accounting (FI-AA) and Materials Management (MM). That
meant that to customize Inflation Accounting for FI-AA, for example, you had to work through the
activities under FI and those under FI-AA.
SAP has now changed the IMG so that each of the components now has its own self-contained IMG for
Inflation Accounting. Now, to customize Inflation Accounting for FI-AA, for example, you no longer
have to work through the IMG activities under Revaluation for the Balance Sheet and then the
activities under Inflation Accounting. Nor do you have to work through the activities under Financial
Accounting -> Financial Accounting Global Settings -> Inflation Accounting. Instead, you just have
to work through the activities under Inflation Accounting. Similarly, the IMG activities for FI and MM
have also been restructured.
The IMGs are still located at the same position in the SAP Reference Structure:
o
Financial Accounting -> Financial Accounting Global Settings -> Inflation Accounting
o
Financial Accounting -> Asset Accounting -> Special Valuation -> Revaluation of Fixed
Assets -> Revaluation for the Balance Sheet -> Inflation Accounting
o
Materials Management -> Valuation and Account Assignment -> Balance Sheet Valuation
Procedures -> Configure Replacement Cost Procedure (Inflation)
Changes in the SAP Library
The Inflation Accounting documentation in the SAP Library has also been split up between the three
______________________________________________________________
SAP AG
115
SAP System
______________________________________________________________
components. It is now located under the following paths:
o
Financial Accounting (FI) -> General Ledger Accounting (FI-GL) -> Closing and Reporting
-> Preparing Financial Statements -> Inflation Accounting
o
Financial Accounting (FI) -> Asset Accounting (FI-AA) -> Special Valuation -> Replacement
Values (General) -> Inflation Accounting
o
Materials Management (MM) -> Evaluation -> Balance Sheet Valuation (MM-IM-VP) ->
Replacement Cost Valuation (Inflation)
5.16.5.3 FI-AA-SVA-IS
Investment Support
5.16.5.3.1 New Report for Posting the Maximum Investment Support Amount
Use
The new report RAINZU10N replaces the previous report RAINZU10 for automatic posting of the
maximum investment support amount. This report contains the following functions:
o
Direct posting: Investment support is posted directly to the fixed asset. It is no longer necessary to
create a batch input session that then has to be processed later.
o
When you use parallel currencies and investment support is managed on the liabilities side of the
balance sheet, the system now determines and posts the investment support amount historically in
the parallel currencies. Before, the amount in local currency was translated to the other currencies
on the posting date.
o
Comprehensive changes were made to the output of the report, including the use of the ALV grid
control.
5.16.6 FI-AA-LM
Leasing Processing
5.16.6.1 Asset Accounting Engine, and Additive Interface
Use
The Asset Accounting Engine makes it possible for external applications to simply and easily use the
functions of Asset Accounting. The Asset Accounting Engine supports creating and changing asset
master records, as well as posting of asset transactions. If interested, contact your SAP consultant.
5.16.7 FI-AA-IS
Information System
5.16.7.1 Changes in the Asset Explorer
______________________________________________________________
SAP AG
116
SAP System
______________________________________________________________
Use
In Release 4.6A, the asset value display transaction was replaced by the Asset Explorer. In the first step
of this replacement, all the functions of the asset value display could not be duplicated in the Asset
Explorer.
The following functions, which in part were contained in the asset value display transaction, can now be
called from the Asset Explorer. The integration of these functions means that the full functions of the old
asset value display transaction are available in the Asset Explorer. Therefore, the old asset value display
transaction is no longer accessible.
Details of New Functions and Changes in the Asset Explorer:
o
Posssible to display all asset subnumbers and main asset numbers by entering an asterisk (*) in the
subnumber field.
o
Two types of simulation are now possible for Asset Accounting in the Asset Explorer.
-
Simulation of transactions
-
Simulation with changed depreciation terms
o
Display of Asset Accounting document header
o
Jump to depreciation log
o
Jump to original documents
o
Breakdown of group assets
o
Maintenance of additional report calls
o
Jump to old asset value display transaction (AW01) from Asset Explorer by choosing Goto -> More
functions is no longer available.
o
When posted values are determined, planned depreciation for special periods is also included.
o
There is a new "Refresh Asset" pushbutton. When you choose this pushbutton, the system imports
the information on the asset again from the database, without your having to start transaction
AW01N again.
5.16.7.2 FI-AA-IS-ST
Standard Reports
5.16.7.2.1 Year-End Income Tax Depreciation Report (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), a new report is available for calculating
depreciation on assets as per India's Income Tax Law. In order for it to function correctly, use the
Customizing settings already delivered with the system since Country Version India Add-On Release
______________________________________________________________
SAP AG
117
SAP System
______________________________________________________________
4.0A.
To access the report, from the SAP Easy Access screen, choose Accounting -> Financial Accounting
-> Fixed Assets -> Information System -> Reports on Asset Accounting -> Taxes -> Country
Specifics -> India -> Year-End IT Depreciation Report.
Effects on Existing Data
If you have already been working with your assets using the settings described in the release note, you
can use the report without having to do anything.
Effects on Customizing
If you intend to start working with the report as of this release, make the Customizing settings as
described in the release note. If you are already working with these settings, you do not have to do
anything.
See also
SAP Library -> Financials -> Country Versions -> India -> Financial Accounting (FI) -> Asset
Accounting (FI-AA) -> Year-End Income Tax Depreciation Report.
5.16.7.2.2 Changed Assignment in Mid-Quarter Convention Acquisitions Report
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), there is a change in report RAUSMQ10. The
report shows asset acquisition by fiscal year quarters. As of now, the report assigns postings to the quarter
based on the asset value date of the posting, rather than by the posting date, as was the case previously.
This makes it easier to assign acquisition postings to the correct quarter.
5.17 FI-SL
Special Purpose Ledger
5.17.1 Using Pooled Tables (Deleted)
Use
From Release 4.70, you can no longer use pooled tables. This means that you can no longer post to
ledgers that are based on pool tables.
From Release 4.70, SAP supports transparent tables only.
Transparent tables have the following advantages when compared to pooled tables:
o
Shorter processing times
o
Better enhancement facilities
______________________________________________________________
SAP AG
118
SAP System
______________________________________________________________
o
Better facility for reading data with external tools
o
Support for Euro conversion
New pooled tables
You cannot create new ledgers on pooled tables.
Existing pooled tables
SAP recommends that you take the following steps:
1.
Check if your system contains ledgers that are based on pooled tables. To do this, run report
RGUPOOL0. Note that the report does not check whether or not the ledgers in question are being
used productively.
Moreover, note that your system might contain sample ledgers L0, G0 and LR (for pooled tables
GLT1 and GLT2). If these ledgers are displayed in the report output list, check whether you use
these them at all.
2.
Convert your pool tables to transparent tables.
For details on how to convert the tables, see the documentation. Guide to Converting Pooled Tables
to Transparent Tables.
Effects on Existing Data
From this Release, you can no longer post data from pooled tables to ledgers.
5.17.2 Archive Connection for Line Item Reports and Summary Reports
(Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), if you are in a Report Writer or Report Painter
summary report, you have the option of calling up the corresponding line items if these have already been
archived (Report-Report interface).
You can also access the archived line items if you have chosen only the database as a data source for the
totals records in transaction GD13.
The standard transactions in the Special Ledger (GD13, GD20, GS23, GD33) are all connected to
Customizing table ASACCESS01. There, you have the option of issuing a default value for the
#Archive# checkbox that appears in the dialog box for the data source.
See also
For further information on evaluating archived FI-SL data, see the info for archiving object
FI_SL_DATA. To see this info, call up transaction SARA and choose Goto -> Info.
To read further information on the Archive Information System (SAP AS), see the SAP Library, under
Cross-Application Components -> Application Data Archiving (CA-ARC) -> Introduction to Data
Archiving (CA-ARC) -> Archive Information System (SAP-AS).
______________________________________________________________
SAP AG
119
SAP System
______________________________________________________________
5.17.3 FI-SL-IS
Information System
5.17.3.1 DRB (Enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , the Document Relationship Browser (DRB)
offers an extended selection of object types. Object types have been added to the DRB, and object types
that were already connected in earlier releases have been completed.
New object types:
o
Profit center document
o
Costing-based profitability analysis
o
Electronic account statement
o
Production order
o
Backflush document
The connection of these object types only affects the functions within the DRB. There are no separate
access programs.
Enhanced object types:
o
Accounting document
From the document display (transaction FB03), you can branch to the DRB. You can use report
RDRBFI00 to access the DRB and to find archived accounting documents via the archive
information system (SAP AS).
o
Controlling document
From the line item reports (for example, transaction KSB1, KSB5, KOB1), you can branch to the
DRB.
The DRB functions can find Controlling documents in the archives of all archiving objects that
archive Controlling line items. There are several field catalogs and info structures for this.
See also
For more information about the Document Relationship Browser, see the SAP note 492938.
5.17.3.2 Transport Report Writer, Sets and Groups (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system transports Report Writer objects, sets
and groups (object types in the transport: R3OB REWR and R3OB Sets) using the transport object type
R3TR TDAT (Customizing: Table contents). This transport object type takes the place of the previous
transport of application-defined objects.
There are no changes to the transport transactions GCTR or GCTS as a result of this. Transport requests
using R3OB transport objects from low release statuses can still be imported as before (except to unicode
______________________________________________________________
SAP AG
120
SAP System
______________________________________________________________
systems).
Effects on System Administration
The following object types are used for transporting report writer objects:
Object type for the transport
Report Writer objekt
R3TR TDAT GRW_JOB
Report group
R3TR TDAT GRW_JOB_VARIANT
Variant of a report group
R3TR TDAT GRW_KEYFIG
Key figure
R3TR TDAT GRW_LAYOUT
Standard layout
R3TR TDAT GRW_LIBRARY
Library
R3TR TDAT GRW_MODEL
Template
R3TR TDAT GRW_REPORT
Report
R3TR TDAT GRW_REPORT_TEXT
Report text
R3TR TDAT GRW_SET
Set
R3TR TDAT GRW_VARIABLE
Variable
You no longer use the Export Application-Defined Objects step, since the objects are already exported
in the Export step. Nor do you use the Import Application-Defined Objects step since the objects are
already imported in the Import step. In the Method Execution step, the postprocessing method
G_RW_AFTER_IMPORT is used for running checks that used to be made in the Import
Application-Defined Objects step. Any errors or warning messages are listed in the Method Execution
log as of SAP R/3 Enterprise Core 4.70.
5.18 FI-RL
Retail Ledger
5.18.1 Retail Ledger
Use
As of SAP R/3 Enterprise Financial Extension 1.10 (EA_APPL 110) the Retail Ledger is available
for use. The Retail Ledger is an application from Accounting, which has been designed specifically for
use in retail.
The Retail Ledger is part of the analytical application "Profit Center Analysis in Retail". The Retail
Ledger is used for collecting actual data from Financial Accounting, Controlling, Human Resources and
Materials Management. From a technical point of view, the Retail Ledger is a standard ledger from the
application component Special Purpose Ledger (FI-SL), which essentially uses the functions of the FI-SL
component. As the Retail Ledger is part of a scenario over SAP R/3, the area menu only offers limited
functions. You can create simple reports using the Totals Record Display. Other functions are a document
display and line item search to display data, an application for balance carry forward, ledger comparison,
to match data from the Retail Ledger with the general ledger, and a transaction for archiving data.
All the functions within the area menu are based on functions from the application component Special
Purpose Ledger. A separate reporting within SAP R/3 (for example, using the Report Painter) is not
provided for so no Report Painter reports will be delivered for the Retail Ledger.
______________________________________________________________
SAP AG
121
SAP System
______________________________________________________________
With the SAP R/3 System, the complete scenario "Profit Center Analysis in Retail" includes an OLTP
System, and with SAP BW and SEM a Data Warehouse and a Strategic Management System. It therefore
only provides for data collection for the Retail Ledger. Reporting, Analysis and Planning are applications,
which assume a transfer of the movement data from the Retail Ledger. Business Content is expected to be
available for this with BW Release 3.1C / SEM 3.2.
Reporting and Planning and indeed other functions are also possible within the Retail Ledger using FI-SL
functions.
Effects on Existing Data
When you activate the Retail Ledger, a new dataset is created in the table group PCRRETAIL (Ledger
7R) with the aim or replacing the movement data from Profit Center Accounting (Ledger 8A) for
customers from the retail sector.
A significant difference compared to Ledger 8A is the data modeling of the table group PCRRETAIL,
which shows the characteristics Profit Center and Cost Center in the summarized dataset (table
PCRRETAILT). The line items (tables PCRRETAILA and PCRRETAILP) are simply to be regarded as
detailed information. They are not a basis for reporting and can, for example, be archived at the end of the
fiscal year.
Effects on Data Transfer
With normal use of the Retail Ledger, data is transferred online.
Data can, for example, be transferred per period when setting up the ledger. To do this, there is a menu
item called Data Transfer in Customizing for the Retail Ledger.
Under Data Transfer there are functions to change the settings that allow follow-up posting or lock the
ledger for data. These settings are made by company code.
The actual data transfer is carried out in two different ways:
1.
Data from Financial Accounting, Materials Management, Sales and Human Resources is transferred
from Financial Accounting.
It should be noted that if data is summarized within Financial Accounting, it may prevent data being
adopted at a level of detail required in the Retail Ledger. Make sure that any summarization of data
within Financial Accounting takes the requirements of the Retail Ledger into account.
You transfer data by period. Start the program in the background for different periods in parallel.
2.
There are different transactions for transferring data from Controlling:
a)
Actual data and statistical key figures of type 2 (totals values) are transferred to the Retail
Ledger using "Transfer Actual Data".
b)
There is a special transaction for plan data.
c)
Statistical key figures of type 1 (fixed values) are also transferred using their own transaction.
Effects on System Administration
The Retail Ledger is delivered with the software component EA-FIN in a separate application component
FI-RL, with a specific add-on switch (FI-RL). The switch must be set for the Retail Ledger in the add-on
for the following points:
3.
When installing the special purpose ledger FI-SL, all add-on ledgers are set to "not active" as
standard. This means that the application programs are not generated for the Retail Ledger either. If
______________________________________________________________
SAP AG
122
SAP System
______________________________________________________________
the switch for the Retail Ledger is now set under View in the IMG, a complete generation takes
place and takes the Retail Ledger into account (by starting RGZZGLUX). Using AFTER-IMPORT
methods a complete generation of the FI-SL application program including the Retail Ledger takes
place after transporting the activated switch to the target system. The generation only takes place if
the Retail Ledger has not already been set up in the target system.
4.
Visibility in the area menu and IMG: Both the area menu and the IMG can be found under
Accounting -> Financial Accounting or directly under Financial Accounting.
The Retail Ledger uses functions from the component FI-SL, which are prerequisites for the posting of
data in the Retail Ledger. These include, in particular, local posting periods, permitted document types
and local number ranges.
Effects on Customizing
The Retail Ledger has its own Customizing:
o
A significant part is the activation of the Retail Ledger. The ledger is activated by selecting the
company codes for which data is to be updated to the Retail Ledger. The operations and field
movements that are delivered in the Business Add-In (BAdI) "Operations and Field Movements" as
sample implementation are set up. The sample implementation assumes that operations from
Controlling are adopted directly (and not via Financial Accounting). If you create your own
implementation, you have to deactivate the implementation provided first. Variable field movements
delivered by SAP are used for this. The activation has an automatic transport link.
o
There is also a transaction for setting up the plan versions in the Retail Ledger that are already in
Controlling. These versions have to be set up to take on plan data from Controlling with the
corresponding version. There is also an automatic transport link here.
The Retail Ledger takes on the authorization objects from the component FI-SL (Special Purpose
Ledger). The transactions of the Retail Ledger (area menu or IMG) check at the start of the transaction
whether authorization exists for the respective transaction.
The authorization objects that are checked at the start of the Retail Ledger transaction are:
-
G_ADMI_CUS
-
G_GLTP
-
G_REPO_LOC
5.19 FI-TV
Travel Management
5.19.1 BOR und Workflows in Travel Management
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) includes the following changes to object type
BUS2089 in the Business Object Repository (BOR):
______________________________________________________________
SAP AG
123
SAP System
______________________________________________________________
o
Interfaces
-
o
Interface IFFIND added (supports generic object services)
Attribute
-
EmployeeTrip.Employee set to obsolete and should no longer be used (problems during
synchronization between object types EmployeeTrip and Employee)
-
EmployeeTrip.RequestStatus added (Transaction TRIP)
-
EmployeeTrip.RequestBeginDate added (Transaction TRIP)
-
EmployeeTrip.RequestBeginTime added (Transaction TRIP)
-
EmployeeTrip.RequestEndDate added (Transaction TRIP)
-
EmployeeTrip.RequestEndTime added (Transaction TRIP)
-
EmployeeTrip.RequestLastChangedBy added (Transaction TRIP)
-
EmployeeTrip.RequestEstimatedCost added (Transaction TRIP)
-
EmployeeTrip.TravelerName added (Infotype 0001)
-
EmployeeTrip.TravelerCompCode added (Infotype 0001)
-
EmployeeTrip.TravelerPersonnelArea added (Infotype 0001)
-
EmployeeTrip.TravelerEmployeeGroup added (Infotype 0001)
-
EmployeeTrip.TravelerEmployeeSubgroup added (Infotype 0001)
-
EmployeeTrip.TravelerBusArea added (Infotype 0001)
-
EmployeeTrip.TravelerPersonnelSubarea added (Infotype 0001)
-
EmployeeTrip.TravelerPayrollArea added (Infotype 0001)
-
EmployeeTrip.TravelerCostCenter added (Infotype 0001)
-
EmployeeTrip.TravelerOrgUnit added (Infotype 0001)
-
EmployeeTrip.TravelerPosition added (Infotype 0001)
-
EmployeeTrip.TravelerJob added (Infotype 0001)
-
EmployeeTrip.TravelerSAPMailUser added
-
EmployeeTrip.TravelerUser added
-
EmployeeTrip.TravelerRgrpStatutory added (Infotype 0017)
-
EmployeeTrip.TravelerRgrpEnterprise added (Infotype 0017)
-
EmployeeTrip.TravelerEgrpExpenseType added (Infotype 0017)
-
EmployeeTrip.TravelerEgrpTravelManag added (Infotype 0017)
-
EmployeeTrip.isRequest added (Transaction TRIP)
-
EmployeeTrip.isPlan added (Transaction TRIP)
-
EmployeeTrip.isExpense added (Transaction TRIP)
______________________________________________________________
SAP AG
124
SAP System
______________________________________________________________
o
Events
-
EmployeeTrip.Requested set to obsolete, and cannot be used anymore
-
EmployeeTrip.RequestCreated added
-
EmployeeTrip.RequestWaits added
-
EmployeeTrip.ExpenseWaits added
-
EmployeeTrip.RequestSettled added
-
EmployeeTrip.RequestTransferredFI added
-
EmployeeTrip.ExpenseSettled added
-
EmployeeTrip.ExpenseTransferredFI added
-
EmployeeTrip.TransferredFIReset added
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) includes the following enhancements to the
Workflow for Travel Management:
o
o
Single Step Activities
-
TS20000130 'Set Trip Status to Approved' changed to 'Background Task'
-
TS12500023 'Mail Trip Settled' added
-
TS12500024 'Mail Request Settled' added
-
TS12500025 'Mail Request Transferred to FI' added
-
TS12500026 'Mail Trip Transferred to FI' added
-
TS12500027 'Mail Trip On-Hold' added
-
TS12500028 'Mail Travel Request On-Hold' added
-
TS12500044 'Approve Travel Request (TRIP)' added
-
TS12500046 'Mail Travel Request Missing' added
Multi-Step Tasks (Workflows)
-
WS12500014 'Mail: Trip has been settled' added
-
WS12500016 'Mail: Trip has been transferred to FI' added
-
WS12500017 'Mail: Trip On-Hold' added
-
WS12500021 'Approve travel request automatically' added (Transaction TRIP)
-
WS12500022 'Approve travel expense statement automatically' added (Transaction TRIP)
Presettings
The event 'Requested' is no longer completed in Travel Management. You should use the event
'RequestCreated' in event linking. You set this up in the SAP Easy Access Menu under Tools ->
Business Workflow -> Development -> Administration -> Event Manager -> Type Linkage (transaction
SWETYPU).
Effects on Existing Data
______________________________________________________________
SAP AG
125
SAP System
______________________________________________________________
The changes and enhancements do not effect any existing data.
5.19.2 Standardization of Travel Manager (TRIP) and Planning Manager (TP01)
Use
The Travel Manager (TRIP) and Planning Manager (TP01) transactions have been standardized in the
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110). You can now process planning information in
the Travel Manager (transaction TRIP), and have access to the general trip information regarding cost
distribution and additional destinations (stopovers) in the Planning Manager (TP01).
5.19.3 FI-TV-PL
Travel Planning
5.19.3.1 Mobile Travel Planning for PDAs
Use
As of SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) , employees can complete their own travel
planning anywhere, and at any time, using Mobile Travel Planning. This allows your employees to react
to appointment changes and new planning requirements whenever they occur.
The business traveler can use their PDA, with an active connection to the Mobile Workplace, to complete
the following tasks:
o
Check bookings
o
Make ad-hoc cancellations
o
Make new bookings
In addition to this, the application also includes the following functions:
o
Overview of planned trips
o
Display of current flight information
o
Create and Change existing travel plans
o
Availability queries for flights, hotels and rental cars
o
Reservation of flights, hotels and rental cars
o
Mobile Travel Planning is based on the mySAP Mobile Workplace Framework with Internet
Transaction Server (ITS), and runs in connection with a R/3 Travel Planning System. The
application is compatible with PDAS with MS Pocket PC#, for example iPAQ.
Mobile Travel Planning uses HTML templates for the displays. You can download these templates from
the SAP Service Marketplace: http://service.sap.com/tm-downloads.
See also
For more information about Mobile Travel Planning, see the SAP Service Marketplace:
______________________________________________________________
SAP AG
126
SAP System
______________________________________________________________
http://service.sap.com/tm.
5.19.3.2 SABRE Interface for SAP R/3 Travel Planning
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) allows you to also use the external reservation
system SABRE.
All existing SAP R/3 Travel Planning functions for booking flights, hotels, and rental cars can be used
with SAP. All airline carriers, hotel chains and car rental providers that can be booked in the SABRE
system are available for selection.
In addition to this, the standard system contains a synchronization process that runs between SAP Travel
Planning and SABRE to ensure that the data in both systems is up-to-date and consistent.
Effects on System Administration
The settings required for communication between the SAP and SABRE systems are made in Customizing
under Travel Planning -> Technical Control Parameters.
See also
For more information see the documentation for this function in Customizing for Travel Management
under Travel Planning ->Technical and Organizational Requirements
5.19.3.3 Flight Bookings
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) includes the following new functions for booking
flights:
o
Automatic price determination
The SAP system automatically determines the price for a flight when it is selected from the flight
request screen, it is not necessary to start the pricing function manually. You can activate or
deactivate this function, as required, in Customizing under Process Control -> Dialog and Planning
Control -> Planning Control -> Define Price and Availability Strategies.
o
Improved user interface for flight availability queries
-
Enhanced best price availability query
Users can call up the Best Price query directly from the list of available flights.
-
Improved availability query dialog
Dynamic screen layout depending upon whether the query is for a single flight, return flight, or
multiple connections. This improved layout simplifies the use for the occasional and regular
traveler.
______________________________________________________________
SAP AG
127
SAP System
______________________________________________________________
-
Additional information in the display of available flight connections
The available flights lists contains additional information about electronic ticketing, aircraft,
meals, and other services. This information is displayed either in the list, or in the mouse-over
popups. If you use the SABRE reservation system, the flight distance in miles, and the
statistical flight schedule/delay information (% of flights on time for US domestic flight) will
also be displayed.
-
Improved seat display
The reserved seat display has been improved through the display of additional seat
information. You can display seats reserved by other employees, and for Jumbo Jets, you also
have the choice of deciding between seating in the upper or lower deck.
o
Interlining with company specific rates
It is possible to book different legs of a multiple connection flight with different airlines as long as
they are within the same company specific rate (Corporate Nego Fare). You do not need to make
any additional settings for enterprise-specific rates.
o
More flexibility for creating and setting up flight travel policy
-
Definition of class rules linked to booking classes ( = Reservation Booking Designator
'RBD')
You make the settings in Customizing for Travel Management under Travel Planning -> Trip
Rules and Profiles -> Trip and Class Rules for Flights -> Flight Class rule -> Determine
Class Rules.
-
Flight profile depending on trip duration
If the trip rules for flights should be dependent upon the trip duration, you can derive the trip
duration from either the total trip duration or only the flight duration (total trip duration less
time on the ground).
You make the settings required for this function in Customizing under Travel Planning ->
Expert View -> Further Control Parameters -> Define Enterprise-Wide Control Parameters.
-
Preferred carriers
Improved logic for completing availability queries for preffered carriers. In addition to the
standard availability query, a Specific targeted availability query is completed for the preffered
carrier.
The settings required to usse this dunction are made in Customizing under Travel Planning
->Trip Rules and Profiles ->Trip and Class Rules -> Availability query Control.
Effects on Customizing
Make the required Customizing Settings as described in the sections above.
5.19.3.4 Hotel Bookings
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) includes the following new functions for making
hotel bookings:
______________________________________________________________
SAP AG
128
SAP System
______________________________________________________________
o
Advanced search in availability query dialog
The hotel availability query screens have been simplified. It is now possible to complete the query
either using a simple or advanced search mode. If you choose to use the advanced search it is
possible to search for hotels using additional search criteria (for example hotel, hotel chain,
location).
You activate this function by making the required settings in Customizing for Travel Management
under Travel Planning -> Process Control -> Dialog and Planning Control -> Travel Planning
Control ->Define Price and Availability Strategies.
o
Hotel Accommodation Limit (Maximum Amounts)
You can now sent maximum amounts for accommodations depending on region and location. You
can define whether a user can select rooms that exceed the maximum amount set, or whether to
remove these rooms from the display so that they cannot be selected.
To use this function, you must make the appropriate settings in Customizing under Travel Planning
->Process Control -> Dialog and Process Control -> Travel Planning Control -> Define Maximum
Amounts for Accommodation
o
Improved Local Hotel Catalog
Hotels that should be given priority can be stored in a company specific hotel catalog. Previously,
the availability check for these hotels could only be started once a specific hotel had been selected,
now however the system automatically starts an availability query for hotels stored in the hotel
catalog as soon as the search query is started.
You do not need to make any Customizing settings for the direct availability query, however you
must enter the hotels that should be active in the hotel catalog under
Travel Planning -> Master Data -> Travel Service Providers -> Hotels -> Hotel Catalog. (Note,
hotel catalogs are processed differently by different reservation systems).
Effects on Customizing
Make the appropriate Customizing settings for the functions listed, as described in the section above.
5.19.3.5 Car Rental Bookings
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) includes the following new functions for making
rental car bookings.
The car rental availability query screens have been simplified. It is now possible to complete the query
using either a simple or advanced search mode. If you choose to use the advanced search it is possible to
search for car rental offers using additional search criteria including entries regarding the rental car
provider, the branch where the vehicle is to be picked up and the vehicle itself (vehicle class, type,
transmission, air conditioning and other extras).
Effects on Customizing
You activate this new function in Customizing for Travel Management under Travel Planning -> Process
______________________________________________________________
SAP AG
129
SAP System
______________________________________________________________
Control -> Dialog and Travel Planning Control -> Travel Planning Control -> Define Price and
Availability Strategies by selecting the field advanced search possible.
5.19.3.6 Enhanced Functions for Booking German Rail (Deutsche Bahn)
Services
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) includes the following new functions for making
rail bookings with German Rail (Deutsche Bahn):
o
Trip rules for rail bookings
You can define rules for choosing classes when booking rail services provided by German Rail
(Deutsche Bahn).
You define these rules in Customizing under Travel Management -> Travel Planning -> Trip Rules
and Profiles -> Trip and Class Rules -> Class Rules for Rail -> Define Class Rules or Specify Class
Rules.
o
Major customer rates (MCR)
You enter the data for your Major Customer Rate(s) in Customizing under Travel Planning -> Rates
and Discounts -> Rail Rates and Prices (Major Customer Rate Deutsche Bahn). When you make a
rail booking, the price will be determined according to the major customer rate. You can define and
enter different major customer rates for different groups of employees.
o
Book outbound and return journeys at the same time
The dialog has been changed to allow you to book outbound and return journeys at the same time.
Effects on Customizing
The Customizing settings required for these new functions are described in the sections above.
5.19.3.7 Enterprise-Specifc Information in PNR - Improved Communication with
Travel Agencies
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) allows you to set up the information, sent in the
PNR (Passenger Name Record) to the travel agency or provider, in a more flexible way.
o
You can extend the information, transferred in the PNR, with enterprise specific information using a
Business Add-In. For example, this allows you to send user information or employee email
addresses to the travel agency.
The settings required for this function are made in Customizing under Travel Management ->
Travel Planning -> Process Control -> Enterprise-Specific Elements in Booking Record ->
Business Add-In: Define Dynamic PNR Elements.
o
The PNR can either contain the private or business address. In addition to this, the user now has the
option of overwriting this information during the booking process.
Customizing settings made under: Travel Planning -> Expert View -> Further Control Parameters
______________________________________________________________
SAP AG
130
SAP System
______________________________________________________________
-> Assign Building Addresses.
o
Remark lines/notes that contain enterprise-specific information, and are valid for all employees can
also be added to the PNR.
You make the Customizing settings for this function under Travel Management -> Travel Planning
-> Process Control -> Enterprise Specific Elements of Booking Record -> Define Static PNR
Elements.
The following inmprovements have been made for the communication with the travel center/agency:
o
By using a specific queue type you can prioritize the processing of all last minute and urgent
bookings. If you set up an emergency queue, all bookings made less than 24 hours before the trip is
scheduled to start will be automatically transferred to this queue (taking into account weekends and
public holidays). In addition to this you can define your own routines for determining queues using
a Business Add-In.
The Customizing settings for this function are made under Travel Management -> Travel Planning
-> Master Data -> Technical Control Parameters for Travel Planning -> Sales Offices and Queues
-> Queues -> Define Sales Office Activities or Business Add-In: Maintain Travel Agency Queues.
o
Electronic Ticketing
If electronic ticketing is available for a flight, the user can decide whether to use the electronic ticket
or whether to request a standard paper ticket. This choice is supplied during the booking process as a
dialog box.
5.19.3.8 Reason codes
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) allows you to analyze bookings that do not meet
your travel policies using reason codes.
If you have specified that users can book specific alternatives that do not meet the enterprise travel
policy, as long as they enter a reason for their selection, you can define these reason codes in
Customizing. This allows you to decide whether the reason field is a required field and therefore the user
must enter a reason , or whether an entry in this field is option. You can also decide whether the user can
enter their own comments alongside the predefined reason code selected.
The settings for this function depend on the travel profile for the corresponding employee groups.
The reason code and the corresponding descriptions are added to the booking record (PNR) as a reason
line (remark element). This line is updated during the synchronization process.
By entering reason codes for all of the possible reasons, you have the ability to structure and evaluate the
reasons selected by the employees.
Effects on Customizing
o
Definition of Reason Codes
Travel Management -> Travel Planning -> Process Control -> Dialog and Process Control ->
Travel Planning Control -> Define Reason Codes
o
Screen Control (Optional or Required Field Settings)
Travel Management -> Travel Planning -> Process Control -> Dialog and Process Control ->
Travel Planning Control Define Treatment of Messages for Priorities.
______________________________________________________________
SAP AG
131
SAP System
______________________________________________________________
5.19.3.9 Synchronization of Traveler Profiles Between AMADEUS and SAP
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) significantly reduces the administrative
requirements for comparing traveler profilers between the central reservation systen AMADEUS and
SAP Travel Planning:
SAP now supports the synchronization of traveler profiles per organizational area using SAP Business
Connectors.
The following information is included:
o
Travel Preferences
o
Credit Card Information
o
Company Address
The data record to be sent, can be modified using the Business Add-In FITP_PREFERENCES_DATA.
Effects on Existing Data
You can use the synchronization process the first time you create profiles in the Amadeus system and
continue to use it to send any SAP HR data that has been changed.
Effects on Customizing
You make the settings required for profile synchronization in Customizing under Travel Management ->
Travel Planning -> Master Data -> Technical Control Parameters for Travel Planning -> External
Reservation Systems -> Synchronization of Travel Preferences with External Reservation Systems.
5.19.3.10 Upload Current Table Contents for IATA Locations and Providers
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) significantly reduces the administrative
requirements for maintaining the Customizing tables for IATA locations, travel service providers and
train stations (for Deutsche Bahn). SAP provides the current table contents including new and deleted
IATA locations, airline carriers, hotel chains, rental car providers and train stations for German Rail
(Deutsche Bahn) - including synonyms, for download at regular intervals. These downloads can be found
in the SAP Service Marketplace.
Once you have downloaded the files to your local computer, you can use the new upload report
RFTP_TABLE_UPLOAD to import thw new table contents into the corresponding Customizing Tables
in your Travel Planning System.
The file provided for download update the following tables or views:
o
TA21L (IATA locations)
o
TA21L1 (language specific descriptions/names for IATA locations
______________________________________________________________
SAP AG
132
SAP System
______________________________________________________________
o
V_TA21P_F (Airlines)
o
V_TA21P_H (Hotel chains)
o
V_TA21P_C (Rental car providers)
o
TA22RSS (Deutsche Bahn, Train stations)
o
TA22RSSY (Deutsche Bahn: Train station synonyms)
See also
Further information is available in the SAP Service Marketplace. http://service.sap.com/tm-download.
5.19.3.11 Structure Changes in the Implementation Guide for R/3 Travel
Planning
Use
The new functions and enhancements for Travel Planning in SAP R/3 Enterprise Travel Extension 1.10
(EA-HR 110) require a new IMG Structure.
If you have implemented Travel Planning in the past, you should make your Customizing settings for
Travel Planning again. Migration using a report is not possible.
This document provides an overview of the changes and additions made to R/3 Travel Planning
Customizing:
o
Technical and Organizational Prerequisites
o
Master Data
o
-
Technical Control Parameters
Settings for Reservation Systems (See SABRE Interface for SAP Travel Planning).
Sales Offices, Queues, RFC Destinations and assignment of these technical parameters to
employee groups.
-
Geographical Situation
Settings for IATA locations and search helps for IATA locations; Assignment of locations
without IATA codes to official IATA locations.
Rates and Discounts
-
o
Settings for customer specific hotel rates.
Trip Rules and Profiles
-
Trip Activity Types
Settings for enterprise-specific trip activity types; Assignment of trip activity types allowed for
different employee groups.
-
Trip and Class Rules
Settings for allowed classes and segments/routes for flights, hotels, rental cars and German
Rail (Deutsche Bahn).
______________________________________________________________
SAP AG
133
SAP System
______________________________________________________________
o
o
Process Control
-
Dialog and Planning Control
Settings for dialog control, customer specific steps for price and availability strategies,
maximum amounts for hotel accommodation, and reason codes for bookings that do not meet
travel policy; Assignment of specific control rules to employee groups.
-
Enterprise-Specific Elements of Booking Record
Settings for enterprise-specific elements in the PNR (booking record).
-
Payment Methods
Definition of payment methods and assigment of payment methods to employee groups.
Expert View
-
New control parameters
See also
Structure Changes for R/3 Travel Expenses.
5.19.3.12 Further New Functions in Travel Planning
Use
o
Corporate Credit Cards
More flexible processing of corporate credit cards whereby you can assign credit cards in
accordance with your company structure. Personnel master data from mySAP Human Resources
and organizational assignment information are used as criteria. For example, this allows you to
assign different credit cards to different cost centers.
You make the Customizing settings required for this function under Travel Planning -> Process
Control -> Payment Methods
o
Travel Planning Dialog Control
You can create company specific information messages for individual processing steps. It is, for
example possible to display travel information and the contact person at the travel agency after a
booking been made using simple Customizing settings. In addition to this it is possible to define
certain fields as being mandatory or optional using field control.
5.19.4 FI-TV-COS
Travel Expenses
5.19.4.1 Public Sector Germany: German Federal Travel Expenses Legislation
Description
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) enables you to implement the Travel Expenses
application for all federal states in Germany. The extension includes the state travel expenses laws and,
where required, the international travel expenses regulations.
______________________________________________________________
SAP AG
134
SAP System
______________________________________________________________
It is, therefore, now possible to create and settle business trips (domestic and international) without
reference to a separation allowance.
The travel expense laws for the following states are included:
o
Baden-Wuerttemberg
o
Bavaria
o
Bremen
o
Hamburg
o
Hessen
o
Mecklenburg-Vorpommern
o
North Rhine-Westphalia
o
Rhineland Palatinate
o
Saarland
o
Sachsen
o
Thueringen
The states not listed (Berlin, Brandenburg, Niedersachsen, Sachsen-Anhalt and Schleswig-Holstein) use
the German Federal Travel Expense Laws.
Effects on Customizing
1.
Special Rules for Industry Solutions
To be able to use the special rules for state travel expense laws you need to activate the corresponding
state legislation in Customizing for Travel Expenses under Activate Special Rulesfor Industry Solutions
The state specific Customizing settings for each state are stored in separate trip provision variants. The
variants are:
State
Baden-Wuerttemberg
Bavaria
Bremen
Hamburg
Hessen
Mecklenburg-Vorpom.
Rhineland Palatine
Saarland
Sachsen
Thueringen
Law
LRKG & LARVO
LRKG & BayARV
BremRKG
HmbRKG
HRKG & HARV
LRKG
LRKG
SRKG
SächsRKG & InternationalRegulations
SächsRKVO
ThürRKG & ThürARV
Trip Provision Variant
DW
DY
DM
DH
DS
DV
DP
DL
DC
DT
______________________________________________________________
SAP AG
135
SAP System
______________________________________________________________
The other states, which are settled according to the BRKG (German Federal Travel Expense Laws), use
trip provision variant D1.
2.
Feature TRVCT
Set up the feature TRVCT so that employees are assigned to the required trip provision variants using
their organizational assignment.
The standard SAP settings for the characteristic should only be used as an example.
5.19.4.2 Public Sector Germany: Border Crossing Rules
Description
The various state travel expense laws, and corresponding international travel regulations, contain
different legislation regarding border crossings. These regulations define the per diem/flat rate
reimbursement amount for the day on which the border crossing takes place: Depending upon the time of
the border crossing either the domestic or international per diem will be paid. For international per diems
you can define whether the per diem for the border crossing point is used or whether the per diem from
the previous place of work is paid.
In addition to this you can define whether the border crossing rules are valid for one-day and/ or multiple
day trips and whether they are valid for outbound trips (border crossing from domestic to international
country) and/ or return trips (border crossing from international to domestic country).
The SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) allows you to define these border crossing
rules per Federal State for Travel Expense Accounting.
As the border crossing rules can result in payments for amounts that are not the same as those included in
the employment taxation guidelines, this may lead to additional amounts or income-related expenses.
Effects on Customizing
You make the settings for the required Federal State in Customizing for Travel Management under
Define Border Crossing Rules (Public Sector Germany.
5.19.4.3 Public Sector Germany: Comparison Calculation for Meals Per Diems
Use
The SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) enables you to complete a comparison
calculation that checks whether travel expenses should be settled using meals statements or using a meals
per diem/flat rate.
Some federal expense laws allow meals expenses to be settled using meals statements rather than per
diems. This is linked with the prerequisite that the total amounts for the meals statements including any
cost of living savings is larger than the total per diems amount for the whole trip.
The comparison calculation for meals compares the two amounts and therefore allows the approving
manager or expense clerk to check that this prerequisite is met.
______________________________________________________________
SAP AG
136
SAP System
______________________________________________________________
When you complete the calculation comparison, you can decide to reimburse either the meals statements
or per diems. If you decide to reimburse the flat rate meals per diem amount, the meals statements that
were entered are deleted. On the oter hand, if you decide to reimburse the meals expenses using meals
statements the per diem/flat rate indicator on the general data screen will be deactivated.
Effects on Customizing
You activate the comparison calculation for meals in Customizing for Travel Expenses under Set Up
Comparison Calculation (Public Sector Germany).
5.19.4.4 Public Sector Germany: Comparison Calculation for Accommodation
Use
Some Federal State Travel Expense Laws and/or International Travel Expense Legislation allow you to
reimburse accommodation receipts upto a certain maximum amount without the requirement for further
checks or proof. The maximum amount paid depends on the following factors:
o
The total accommodation per diem amount that would be paid without accommodation receipts or
o
A specific amount per night
With the SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110), you can activate a comparison
calculation for accommodation, that determines the maximum amount for the total accommodation
expenses (with receipts/statements) that can be reimbursed without further checks being made.
You can choose whether this comparison calcuation is completed for domestic trips only, international
trips only, or for all trips.
Effects on Customizing
You set up the comparison calculation for accommodation in Customizing for Travel Expenses under Set
Up Compariosn Calculation (Public Sector Germany).
5.19.4.5 Public Sector Germany: Several Domestic Business Trips on One Day.
Use
The Federal State Travel Expense Laws for Bavaria and Saarland stipulate that, if several domestic
business trips are completed within one day the per diem must be determined individually for each trip,
however the total per diems for these trips are not allowed to exceed the full per diem amount for that
day.
The laws for the other states within Germany state that the absence times for these trips should be
cumulated to determine the per diem for this day.
As of SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110), you can enter several domestic business
trips for the same day, by using trip schema with the characteristic Several Business Trips/Day (See
the IMG activity Define Schemas and Individual Field Control). You create several trips on one day as
different trip segments within one trip and not as several individual trips. You should enter the start of the
first trip as the start time for the overall trip and the end of the last trip as the end of the complete trip.
______________________________________________________________
SAP AG
137
SAP System
______________________________________________________________
You then create the separate trips as stopovers/trip segments within this trip.
Effects on Customizing
Define a schema with the characteristic Several Business Trips/Day in Customizing for Travel
Expenses under Define Schemas and Individual Field Control .
5.19.4.6 Clearing Additional Amounts and Income-Related Expenses
Use
If additional amounts and income-related expenses occur when you settle a trip, you can clear these
amounts against one another. In earlier releases this was only possible within meals accounting.
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) allows you to clear additional amounts and
income-related expenses across the different expense categories, as long as the expenses category is not
for expenses that been paid by the company or for renumeration in kind. company).
Effects on Customizing
You set up clearing of additional amounts and income-related expenses in Customizing for Travel
Expenses under Wage Types for Interfaces -> Set-up Clearing of Additional Amounts and
Income-Related Expenses.
Clearing takes places using the clearing wage types created and set up using IMG activity Assign
Tax-Exempt Clearing Wage Types for Add. Amounts.
If you use any wage types for additional amounts that vary from the SAP standard wage types delivered,
you must assign the corresponding tax-exempt wage types for clearing wage types to each of the
additional wage types used.
This function was devised for Public Sector Germany, if you want to use the function for other country
versions, you should check and test the correct functional procedures extensively before implementation.
5.19.4.7 Federal State Travel Expense Laws for Rhineland Palatine: Trip
Segment Reimbursement
Use
The SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) allows you to set up the Travel Expense
component according to the Federal State Travel Expense Laws for Rhineland Palatine.
The following changes/additions have been made to cover all of the requirements set out in the Federal
State Travel Expense Laws for Rhineland Palatine:
Reduction of Kilometer/Miles Limit for Recognized Private Cars
The Miles/Kilometer rate for recognized private cars is scaled according to the kilometers/miles traveled
in a calendar year. The number of kilometers, after the basic scaling amount, to be reimbursed during the
year reduces by one twelfth for each full calendar month that has been completed (§3 LVO, Abs. 2-3). To
be able to use and implement this rule correctly you must enter the date from which the private vehicle
______________________________________________________________
SAP AG
138
SAP System
______________________________________________________________
will be recognized for all relevant employees in Infotype 0017 (travel priviledges), field Start Date for
Yearly Cumulation.
Further notes
The Federal State Travel Expense Laws for Rhineland Palatine also contain special rules regarding half
cent amounts for regular use of vehicles for business purposes. Note, to implement travel expenses
according to the Federal State Travel Expense Laws for Rhineland Palatine, you must also set up an
additional currency with three decimal places.
For more information, see the Implementation Guide for Travel Expenses under Define Per Diems/Flat
Rates for Travel Costs.
5.19.4.8 Kilometer Accounting: Enhancement of Cumulation According to
Period Parameters
Use
As of Add-on HR-PS 4.52A, you can enter the cumulation procedure per vehicle type and class
(Customizing activity assign cumulation procedure for vehicle type/class). For the method
Cumulation according to period parameters, you then had to enter a valid period parameter for the
employee in the corresponding trip provision variant. You did this in the Infotype 0017 (travel
priviledges) for the employee.
As of SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110), you also have the option of entering the
period parameters using IMG activity Assign cumulation procedure for vehicle type/class.
This alternative is recommended for cases where the same period parameter should be used for all
employees using specific combinations of vehicle types/classes in the same trip provision variant.
5.19.4.9 Public Sector France: Travel Expense Accounting for Domestic,
International, and Seminar Trips
Use
As of SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) you can also use R/3 Travel Expense
Accounting for Public Sector France. The extension includes all of the appropriate legal requirements and
legislation required for business trips within France, international trips, and seminar trips within France.
To use this function, all reimbursement amounts must be tax-exempt.
You should create all trip data using the Travel Expense Manager ( Transaction PR05). The other entry
transactions for travel expenses are not available for use with Public Sector France. You must specify
whether a trip is a domestic trip, international trip, or seminar trip when creating the trip. You cannot
create a mix of domestic, international or seminar destinations within one trip.
Individual specific trip schemas have been created for each trip type: domestic trips, international trips
and domestic seminar trips.
______________________________________________________________
SAP AG
139
SAP System
______________________________________________________________
Effects on Customizing
o
A specific trip provision variant for Public Sector France is provided with standard Customizing.
This trip provision variant 'FR', contains all of the settings required for Public Sector France.
o
Activate Special Rules for Industry Solutions
To use the specual rules for Public Sector France, you must activate the appropriate accounting rules in
Customizing for Travel Expenses under Activate Special Rules for Industry Solutions.
o
Feature TRVCT
Set up feature TRVCT using IMG activity Assign trip provision variants to organizational areas so that
the appropriate employees are assigned to the trip provision variant for Public Sector France.
The settings in the standard system should be seen and used as an example only.
o
Define Characteristics for Statutory Trip Types
If you want to create your own statutory trip types, you need to select the appropriate characteristics.
See also
Public Sector France: Processing Deductions
For more information about the solution for Public Sector France, see the SAP Library under Travel
Expenses -> Country and Industry Versions for Travel Expenses -> France -> Industry Solution Public
Sector France.
5.19.4.10 Public Sector France: Processing Deductions
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) includes the settings required for handling
deductions in travel expense accounting according to legal requirements for Public Sector France:
o
Domestic Trips
According to the French Laws for Public Sector France:
-
Deductions can be made due to complimentary/free accommodation or meals
-
Travel expenses reimbursements can be reduced by 50 % if the traveler is provided with
accommodation in special accommodation for the Public Sector.
A deduction of 50% or 100% for accommodation or meals can be made, per day within a trip. The entries
are stored in the Standard Customizing activity Define Deductions (V_T706A ) 10 new fixed values
have been created for the deduction indicator keys:
-
Deduction Values 1, 2, 3, 4, 5: Deductions for Meals - Public Sector
-
Deduction Values 6, 7, 8, 9, 0: Deductions for Accommodation - Public Sector France
______________________________________________________________
SAP AG
140
SAP System
______________________________________________________________
Two entries for each of these values (for 50% and 100%) are delivered in standard Customizing. In the
travel expense dialog, these entries are displayed with their corresponding long texts showing the
percentages.
Note:
The entries for accommodation always refer to the night leading into the date displayed, in other words a
deduction entered for the 01.12.2002 reduces the amount for the night of the 30th November into the 1st
of December. The first night is, therefore, not normally available for data entry.
o
International Trips
No differentiation is made for meals or accommodation for international trips. Both flat rates/per diems
are processed together. For this reason, only one column for deductions is displayed on the deductions
screen. This single entry for deductions is made in the same way described above.
In certain circumstances an extra half of the flat rate/per diem rate may be paid. The traveler therefore
receives 150% of the per diem/ flat rate. If a deduction is made for this day, it can only be taken from the
original per diem/flat rate, the additional amount cannot be reduced.
Effects on Customizing
All of the settings required for handling deductions in accordance with the regulations for Public Sector
France are included in Standard Customizing. You should check these settings in the appropriate IMG
activities.
See also
For more information about the solution for Public Sector France, see the branch and industry solution
documentation for Public Sector France in the SAP Library.
5.19.4.11 Public Sector France: Processing Advances
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) includes the settings required for handling
advances in Travel Expense Accounting according to legal requirements for Public Sector France:
The legal requirement state that advances for business trips must be limited to 75% of the expected
reimbursement amount for domestic trips and 100% for international trips.
To simplify the calculation of these advances, you can choose the new Determine Advance function to
simulate the trip. This displays the results for the trip and automatically calculated the advance amount
still available for the trip. This amount can then be approved or manually changed.
See also
For more information about the solution for Public Sector France, see the branch and industry solution
documentation for Public Sector France in the SAP Library.
______________________________________________________________
SAP AG
141
SAP System
______________________________________________________________
5.19.4.12 Public Sector France: Standard Form for Travel Expenses
Use
As of SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110), the standard form for travel expenses
includes special functions for Public Sector France:
International Trips/Seminar Trips: Trip Itinerary
For international trips, stopovers are defined by the arrival at and departure from the destination location.
This means an international trip is made up of a independent trip segments and can lead to time gaps.
Seminar trips For Seminar trips, only external stays at the seminar location and also any private
destinations required are entered. These external stays are individual trips that are entered as one trip to
reduce the accommodation per diems required. As with international trips, this can also lead to time gaps.
The trip itinerary on the standard form displays these trip segments, numbered sequentially.
International Trips: Indemnite Journaliere IJ
The IJ is entered in the form block Meals, The individual amount (Base IJ), the number of IJ's as well as
the reimbursement amount are displayed for each line. The reimbursement amount in calculated from the
individual amount and the number of IJs. The deductions from the IJ are displayed per day. The
deductions amount is calculated as a percentage of the IJ (50 or100 %). The percentage share and
deduction amount are determined and displayed as negative values in the reimbursement amount column.
The total reimbursement amount is the total reimbursement amount per line minus the deductions.
Domestic Trips: Indemnite Repas (IR)
The individual amount for the IR, the number of IR's and the reimbursement amount are displayed per
line. The reimbursement amount is calculated by multiplying the individual amount by the number of
IR's.
Deductions are calculated and displayed in the same way as the deductions for international trips.
Domestic Trips: Indemnite Nuitee
The accommodation per diem, the number of nights/days and the reimbursement amount are displayed
for each line. The deductions are entered per night and are indicated by an R in the number of days/nights
column. The reimbursement amount after deductions is also displayed.
See also
For more information about the solution for Public Sector France, see the branch and industry solution
documentation for Public Sector France in the SAP Library.
5.19.4.13 Three Month Rule: First Level
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) contains the first level of functions in Travel
Management for complying with the three month rule. Complete realization of this function is planned
for a later release.
______________________________________________________________
SAP AG
142
SAP System
______________________________________________________________
You want to group together reoccurring trips to a specific destination for tax reasons, so that you can
change the accounting and taxation method used after a certain period of time (for example three
months). In order to be able to recognize reoccurring destinations, you must enter detailed information
when entering the specific destination, meaning that you can only enter the destination location using
input help. Input help displays a list of the destinations used in previous trips for the current personnel
number.
If you travel to the same destination again, you can copy this destination from the list, or if a new
destination is required, you can enter this in the lower half of the popup by entering the street and location
information. This ensures that trips to the same destination are stored with the same information.
The following options are available:
0 = Accounting and Taxation method for trips to reoccurring destinations is not changed (for example 3
Month Rule in Germany).
1 = Accounting and taxation method is changed for trips to reoccurring destinations (for example 3
Month Rule in Germany). Company pays tax for old tax-free amount.
2 = Accounting and taxation method is changed for trips to reoccurring destinations (for example 3
Month Rule in Germany). Employee pays tax for old tax-free amount.
3 = Table PTRV_TRIP_CHAIN (used to store trips according to destination) is only maintained for
statistical reasons.
In the case of 1, 2, or 3 enter the duration in months and days (Constants REIDM and REIDD). The
duration is calculated from the number of months entered in REIDM and the number of days entered
under REIDD. The maximum gap allowed between two trips to the same destination is defined in REIGP.
The validity period for the change of accounting/taxation method begins when the duration calculated is
exceeded. This means that the accounting and taxation method is only changed once the duration (for
example three months) has been reached.
Restrictions
In the first release of the SAP R/3 Enterprise Addon, all three settings will fill table
PTRV_TRIP_CHAIN with the destinations from all trips. If a destination, for which the accounting and
taxation method should be changed after a set period, is found, this date will be saved for all trips to this
destination in table PTRV_TRIP_CHAIN, field ACTION_DATE_REQ.
At present the accounting program does not react to this date. In this case, the user can use method
SET_DIFFERENT_WAGETYPE from BAdI TRIP_RECURRENT_DEST (transaction SE19) to assign
the expenses that are recorded after the determined date to a different wage type.
The Travel Calendar (PR02) and Weekly Report (PR04) transactions are not supported.
5.19.4.14 Enhancement to BAPI Interface for Travel Management
Use
In SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110), the interface for function module
BAPI_TRIP_CREATE_FROM_DATA has been enhanced and extended.
o
The new table ADVANCE allows you to enter advances when creating a trip using the R/3 Travel
______________________________________________________________
SAP AG
143
SAP System
______________________________________________________________
Management application
o
The new parameter (structure) CHANGE allows you to change the standard entries, created by the
function module, in the Travel Expense Table AEND (used to log the change history for a trip).
In addition to this, external influences can affect the function module: The new parameter
BATCH_INPUT_ONLY ensures that the employees trips are not saved directly to the R/3 database, but
are stored in a batch input folder instead (you can enter the name of this folder in parameter
BATCH_SESSION_NAME).
5.19.4.15 New Functions for Credit Card Clearing in Travel Management
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) includes the following changes/new functions for
credit card clearing in Travel Management:
o
You can now define and enter your own credit card companies in Customizing, including
non-certified companies.
o
You can complete clearing with several different credit card companies at one time. The field
service provider has been added to Customizing to help you do this. This field allows you to
control the account assignment of credit card transactions.
o
You can no longer change the amount, currency and exchange rate for receipts that have been paid.
o
Transaction keys are no longer restricted and can be freely defined. This allows you to confirm the
key required directly with the credit card company and to enter these into the system.
o
In FI, both the credit card number and the transaction number can be entered as assignment criteria
during clearing.
o
New evaluation options in Reporting: Two new reports are available in the SAP Menu under Tools
-> Credit Card Information:
- Correct Transactions with Errors
- Create File with Corrected Transactions
Effects on Customizing
There is a new section in the Customizing for Travel Management under Travel Expenses -> master
data: Credit Card Clearing. This section contains the activities Define Credit Card Companys and
Define Assignment Tables for Credit Card Clearing
Furthermore you can specify whether the credit card number and transaction number should be
transferred to FI separately for each expense and offsetting posting for each wage type under Define
assignment of wage type to symbolic account (activate flag 'Credit Card Information' in the column
'symbolic expense account' and '2nd symbolic clearing account').
See also
For more information, see the SAP Library under Travel Management -> Database Management for
Travel Expenses -> Credit Card Clearing.
______________________________________________________________
SAP AG
144
SAP System
______________________________________________________________
5.19.4.16 Avoidance of Cross-Company Code Postings in Travel Management
Use
Select Time for Reading Vendor
The reimbursement of travel expenses to the employee can take place in Financial accounting using a
person-based vendor. This vendor was previously found by searching in the company code to which the
employee was assigned at the end of the accounting period entered when creating a posting run. If the
employee changed organizations in between this date and the start of the trip this lead to cross-company
code postings.
As of SAP Enterprise Travel Extension 1.10 (EA-HR 110) you can select the time from which the master
company code should be selected using a Customizing activity. The time can lie between the end date for
the accounting period, the system date and the end date of the trip. The last choice provides you with the
best option for avoiding cross-company code postings.
Search for Vendors in Expense Company Code
Up to now person-based vendors, used to reimburse travel expenses to an employee, were searched for in
all wage types in the master company code. If several account assignments to different company codes
existed within one trip, cross-company code postings were required.
You can now use a Customizing activity to specify that the expense company code is searched for each
wage type separately. SAP recommends that you either make this setting for all or none of the wage
types. If account assignments to different company codes occur within a trip, the expense and creditor
postings are made in the expense company code. This means you no longer need to make cross-company
code postings.
Effects on Customizing
You can specify whether the master company code should be determined according to the end date for
the period, system date or the trip end date in Customizing under Travel Expense Control (Expert View),
Column 17, line 'other accounting'
You can use IMG activity Define assignment of wage types to symbolic accounts to specify whether the
offsetting entry should be made in the same company code as the expense posting. You do this by
activating the flag 'Set Expense Company Code' next to the column 'symbolic account for offsetting
entry' for each wage type.
5.19.4.17 Travel Management for Finnland
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) fulfils the country specific requirements for
Finnland (trip provision variant 44).
This contains the following statutory and enterprise-specific functions for Travel Expense Accounting:
o
Settlement of receipts
o
Calculation of statutory meals per diems including requirements for deductions due to
______________________________________________________________
SAP AG
145
SAP System
______________________________________________________________
complimentary/free meals.
o
Calculation of statutory accommodation per diems
o
Customizing entries for trip provision variant 44 Finnish Accounting.
5.19.4.18 Creating and Posting Receipts and Advances in Foreign Currencies
Use
Receipts and advances can be entered in any foreign currency in Travel Management, however
previously trip settlement (and therefore all receipts and advances) could only take place in the trip
currency, hard currency or in the trip or hard currency per receipt or advance. SAP Enterprise Travel
Extension 1.10 (EA-HR 110) allows you to settle and post receipts and advances in the currency they
were entered.
The travel expense form only contains individual totals for each currency, and does not contain a total
amount, as with the travel expense form for hard currency.
Effects on Customizing
You activate this function in Customizing for Travel Management in the IMG activity Define Global
Settings
5.19.4.19 Structure Changes in the Implementation Guide for R/3 Travel
Expenses
Use
This document provides and overview of the Customizing activities for Travel Expenses that have been
changed or added for SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110).
Travel Expenses
o
Master Data
-
Control Parameters for Travel Expenses
Activity Assign Organizational Areas to Trip Provision Variants renamed to Assign
Organizational Areas and TRVCT Feature to Trip Provision Variants
-
Control Parameters from Trip Facts
New activity Define Absence Types for Public Sector Germany
Activity User Exit renamed to User Exit Include: Additional Action Options For Data Entry
-
Travel Expense Types
New: Define Input Tax for International Per Diems
-
New Section Credit Card Clearing with activities:
Define Assignment Table for Credit Card Clearing
New: Define Credit Card Companies
______________________________________________________________
SAP AG
146
SAP System
______________________________________________________________
o
o
Dialog and Travel Expense Control
-
Dialog Control
New: Set Up Comparison Calculation: Public Sector Germany
-
Dialog Control for Integration of Time Sheet (CATS) with Travel Management
New: Integration Travel Management - Time Sheets (CATS for Service Providers)
New: Integration Travel Management - CATS Approval
-
Travel Expense Control
New: DefineRules for Border Crossings (Public Sector Germany)
New: Set Up Clearing of Add. Amounts and Income Rel. Expenses
Renamed section: Input Tax and Wage Types for Interfaces to Wage Types for Interfaces
-
o
Transfer to Accounting
-
o
New: Assign Altern. Wage Types to Travel Exp. Types for Indiv. Receipts
New: Assign Altern. Wage Types to PS Expense Types for Per Diems/ Flat Rates
New: Assign Tax-Exempt Clearing Wage Types for Add. Amounts
Deleted: Determine FI Payment Date
Deleted Check Travel Expense Wage Type Group
New: Determine FI Payment Date
Employee Self Services in Travel Management replaces the section Internet Application
Components.
-
The old IMG activities for processing Travel Expenses using Excel have been deleted.
o
New organizational activity Web-GUI Transactions and new section for Offline Travel Expenses.
o
Separation Allowance - Public Sector Germany
-
This section contains the activities for setting up and using Separation Allowances for Public
Sector Germany.
Integration of Travel Planning and Travel Expenses
o
Integration of Travel Planning and Travel Expenses
-
New section Settings for Travel Manager
New activity: Edit Graphics in BDN
Renamed: Define Assignment Trip Schema to Travel Plan Type to Assign Trip Activity Types
Integration of Travel Management and Payroll
o
Wage Types
New: Include Travel Expenses in Payroll
o
The country specific modules for payroll in the separate countries were deleted and added to an
organizational activity.
Business Add-Ins and User Exits in Travel Management
This is a new section and contains an overview of the enhancement options for Travel Management:
o
Planning
______________________________________________________________
SAP AG
147
SAP System
______________________________________________________________
o
-
New: Business Add In: Define Dynamic PNR Elements
-
New: Business Add-In: Define Travel Agecy Queues
-
New: Business Add-In: Compare Travel Preferences from SAP and GDS
Entry
-
New: Business Add-In: Data Import/Data Export
-
New: Business Add-In: Receipt Wizard
-
New: Business Add-In: Interfaces for Offline Travel Expenses
-
New: User Exit: Save Trips (PR01, PR04, PR05, TRIP) Bef. Assigning Trip Number
-
New: User Exit: Inclued Rate Data in Trip Provision Variant
-
New: User Exit: Save Trips (PR01, PR04, PR05, TRIP) After Assigning Trip Number
and the organizational activities:
o
o
-
New: User Exit Include: Additional Action Options for Data Entry
-
New: Screen Modifications: Adjustment of "User Data" Screen
Posting
-
New: Business Add-In: Adjustments During Account Determination
-
New: Business Add-In: Assign Alternative Wage Types
-
New: User Exit Include: Adjsutments When Creating Vendor Master Records
Approval
-
o
o
New: Business Add-In: Automatic Approval of Travel Expenses
Settlement
-
New: Business Add-In: Assign Alternative Wage Types to Part of Trip
-
New: User Exit Include: Additional Adjustment Options During Settlement
-
New: User Exit Include: Enterprise-Specific Adjustments to Form
Statistics
-
New: User-Exit: Create/Change Trip Statistics
-
New: User-Exit: Delete/Reorganize Trip Statistics
See also
Structure Changes for R/3 Travel Planning
5.19.4.20 Offline Travel Expenses: Enter Travel and Entertainment Expenses
______________________________________________________________
SAP AG
148
SAP System
______________________________________________________________
Offline
Use
The SAP solution for settling travel and entertainment expenses has been available as an Employee Self
Service application, or directly in the R/3 System, for several Releases. This function is now available for
SAP R/3 4.6C and SAP Enterprise Travel Extension 1.10 (EA-HR 110) as an Offline Solution: Offline
Travel Expenses.
You must fulfil the following prerequisites to use the Offline Travel Expenses application:
o
You must have implemented Basis Plug-In PI2002.1 or higher for Release 4.6C. You need support
package SAPKB46C01 for this Plug-In.
o
LCP 17 for R/3 4.6C must be installed. For more information, see Notes 87484 and 86241.
o
The files required for installing Offline Travel Expenses must be available. These files will be
provided for download from SAP Service Marketplace as soon as they are available:
Http:\\service.sap.com/tm.
Offline Travel Expenses enables you to enter travel and entertainment expenses using mobile devices
(Notebooks), regardless of your location and without requiring a connection to SAP R/3. This function is
targeted at employees that are often away on business and that are therefore, not connected to the SAP
R/3 system, but that need to enter their travel expenses.
The application was developed in Java, and runs in a Web-browser. You use the SAP standard
technology for synchronizing mobile devices with SAP R/3: The Mobile Engine. Once the data, created
offline, is transferred to SAP R/3 it can be processed in the same way as the data created online.
When implementing Offline Travel Expenses, you can also implement the CATS Notebook product for
entering time sheets offline. For more information see CATS Notebook.
Effects on System Administration
Some technical changes to the standard system are required if you want to use Offline Travel Expenses in
connection with SAP R/3 4.6C. These changes are supplied with the LCP 47 and are also included in
SAP Note 507633. If you do not want to implement Offline Travel Expenses, these changes do not affect
other application interfaces.
Effects on Customizing
Offline Travel Expenses uses the standard Customizing for entering travel expenses. Additional
Customizing activities can be found in Customizing for Travel Expenses under Employee Self Services
for Travel Management -> Offline Travel Expenses.
See also
For more information see the SAP Library documentation for Offline Travel Expenses
If you want/need to create a customer message for SAP Support, use component FI-TV-COS-PTM.
More information regarding Offline Travel Expenses can be found in the SAP Service Marketplace:
o
Current information for Offline Travel Expenses: service.sap.com/tm
o
Mobile Engline Documentation: service.sap.com/mobile -> Groups -> SAP Markets ->
______________________________________________________________
SAP AG
149
SAP System
______________________________________________________________
Documentation
o
Information about SAP R/3 Plug-Ins: service.sap.com/R3-plug-in
5.19.4.21 Alternative Processing of Paid Receipts
Use
Up to now, receipts that had already been paid by the company could only be posted to a clearing
account, and clearing this posting against the posting for the invoice receipt (that was posted to the
expense account using the master account assignment for the employee) had to be completed manually.
SAP Enterprise Travel Extension 1.10 (EA-HR 110) includes a Customizing activity that allows you to
specify that offsetting entries for the expense account (for the paid receipt) should take place using the the
same master account assignment. The master cost assignment is defined at the time of the trip. If the paid
receipt is assigned to the same CO Object as the master account assignment, it does not need to be posted
in travel Management. If, however, the CO Object is different, a cost center reposting to the expense
account takes place.
Effects on Customizing
You can use IMG activity Define Assignment of Wage Types to Symbolic Accounts to specify that the
offsetting entry for the expense account should take place using the same account as the master account
assignment (The symbolic account in the '2nd symbolic clearing account' and 'symbolic expense
account' fields must be the same but with reversed plus/minus signs, and the flag 'set master company
code' next to column 'symbolic account for offsetting entry' must be selected). You should do this for all
wage types used for expense types that are paid by the company.
5.19.4.22 Enhancement of Posting Interface for Travel Management
Use
Splitting Receipts or Receipt Items Per Expense Receipt
A trip normally contains several travel expense receipts as well as any per diems/flat rates. Previously,
when creating a posting run, the details for the trip transfer documents or the account receviable/expense
lines could only displayed at trip level. This meant that the postings in FI could only take place at trip
level.
SAP Enterprise Travel Extension 1.10 (EA-HR 110) contains new selection criteria that allow you to
create trip transfer documents for each individual travel expense receipt as well as a further document for
all per diems/flat rates. This means that postings are made at receipt level in FI, invoice distribution is
possible, and further processing steps are simplified.
______________________________________________________________
SAP AG
150
SAP System
______________________________________________________________
5.19.4.23 Receipt Wizard: Enter and Process Complex Receipts
Use
The Receipt Wizard helps the user to enter and process complex receipts (for example, a hotel receipt for
several days that includes private amounts and other expense types). Using the Receipt Wizard you can
o
Calculate and Deduct Private Expenses
o
Divide Receipts
o
Split Receipt into Different Expense Types
The Wizard ensures that you cannot make any unwanted changes to the original data, for example during
credit card clearing or for receipts that have been paid by the company.
Example Hotel Receipt
The traveler users a personal corporate credit card that debits the employer's account. The following
amounts were invoiced to this card:
Date
18/02/02
18/02/02
18/02/02
18/02/02
18/02/02
19/02/02
19/02/02
19/02/02
19/02/02
19/02/02
20/02/02
20/02/02
20/02/02
20/02/02
20/02/02
20/02/02
Description
Room Charge
State Tax
County Tax
Parking
Telephone
Room Charge
State Tax
County Tax
Parking
Restaurant
Room Charge
State Tax
County Tax
Parking
Telephone - NET
TV - Movie
***TOTAL***
BAmount
99.00
6.93
4.95
14.00
13.27
99.00
6.93
4.95
14.00
23.00
99.00
6.93
4.95
14.00
57.73
9.99
478.63
The amounts for the private expenses: Telephone calls, restaurant and TV should be paid back to the
company by the employee. The parking and internet amounts should be paid by the company but should
be assigned to the expense types rental car and communication and not Accommodation, and in
addition to this, the accommodation receipt should be created per day.
______________________________________________________________
SAP AG
151
SAP System
______________________________________________________________
System Entries
A paid accommodation receipt for 478.63 is created either automatically via credit card clearing or using
travel expense transactions TRIP or PR05. This receipt is selected and the Receipt Wizard is started. The
user is taken through the following steps:
1.
Initial Screen The user is provided with a short introduction about the Receipt Wizard, this screen
contains a 'Do not show again' option for frequent users.
2.
Private Expenses The user enters their private expenses. If the receipt has already been paid, these
expenses are assigned to specific expense types (see the Customizing section), if the receipt has not
yet been paid, these amounts are deducted from the total. For the example above, the user would
enter 13.27, 23.00 and 9.99.
3.
Split Receipt The user enters the expense types and amounts that should not be entered under the
expense type accommodation. In the example above this would be 3 x 14.00 for expense type
Rental Car paid by company and 57.73 for expense type communication, paid by company.
4.
Divide Receipt This screen only appears if the receipt covers several days. If the user wants to
divide the receipt into individual receipts for each day he is requested to enter the price per day
(including tax) and the number of days. The remaining receipt amount divided by the number of
days from the additional receipt information screen is provided as a default value.
5.
Overview and Save A list is displayed with all of the information regarding the new receipts. The
new receipts (and the original receipt, but with the changed amounts) are only transferred to the trip
when the user chooses Execute.
The information about where a new receipt has been derived from (the original receipt) remains. If the
new receipt is deleted, the amount is added back onto the original receipt.
The Receipt Wizard is not available in transactions PR02 and PR04.
Effects on Existing Data
This enhancement does not have any negative effects on existing data. You can use the new function for
existing receipts, as long as you have met the requirements in Customizing.
Effects on Customizing
You have to activate the Receipt Wizard for each expense type in the Customizing Activity Enter Travel
Expense Types for Individual Receipt (T706B1).
A Business Add-In is available for enhancements. You can find this Business Add-In in Customizing
under Business Add-Ins and User Exits in Travel Management under the step Business Add-In:
Receipt Wizard, or you can call up the Business Add-In directly using transaction SE18. The name of the
BAdI is TRIP_RECEIPT_WIZARD.
See also
For more information about the Receipt Wizard, see the SAP Library under Travel Management ->
Travel Expenses -> Create Trip Facts -> Receipt Entry Functions -> Receipt Wizard.
For more information about Customizing for expense types, see the SAP Library under Travel
Management -> Travel Expenses -> Transfers to Financial Accounting -> Posting Personal
______________________________________________________________
SAP AG
152
SAP System
______________________________________________________________
Expenses using the Receipt Wizard.
5.19.4.24 Separation Allowances: Public Sector Germany
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) includes the Separation Allowance Manager that
allows you to create, maintain, settle and transfer separation allowances for external stays as well as daily
return trips for Public Sector Germany. This solution includes the legal requirements for the separate
German Federal States (Bundesländer). At present this solution covers the requirements for Berlin,
Brandenburg, Hamburg Mecklenburg-Vorpommern, Sachsen-Anhalt und Schleswig-Holstein.
5.19.4.25 Payment of Separation Allowances using Different Payment Methods
Use
As of SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110), you can decide to pay separation
allowances using a payment method that differs to the one used for standard business trips. For example
You can decide to reimburse business trips via FI and separation allowances via payroll. To do this you
must complete the appropriate steps in Customizing.
Effects on Customizing
For information about the IMG activities required for paying separation allowances, see the IMG
documentation under Travel Expenses ->Separation Allowances for Public Sector Germany
5.19.4.26 Travel Expenses: France and German Federal Travel Expense Laws
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) contains the HR-PS solutions for Travel
Expenses France and the German Federal Travel Expense Laws for the different Bundesländer (States).
See also
For more information, about Public Sector France, see
o
Public Sector France: Travel Expense Accounting for Domestic, International and Seminar Trips
o
Public Sector France: Processing Deductions
o
Public Sector France: Processing Advances
o
Public Sector France: Standard Form for Travel Expenses
For more information about the German Federal Travel Expense Laws for the different Bundesländer
(States), see
o
Public Sector Germany: Travel Expense Laws for the different Bundesländer (States)
______________________________________________________________
SAP AG
153
SAP System
______________________________________________________________
o
Kilometer/Miles Accounting: Enhancement of Cumulation according to Period parameters
o
LRKG Rhineland-Palantine: Trip segment reimbursement
o
Calculation of additional amounts and income-related expenses
o
Public Sector Germany: Several domestic trips on one day
o
Public Sector Germany: Comparison Calculation - Accommodation
o
Public Sector Germany: Comparison Calculation - Meals per diems>/>
o
Public Sector Germany: Border Crossing Rules
5.19.4.27 Comparison Calculation for Travel Expenses: Public Sector
Use
As of SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110), you can complete a comparison
calculation for accommodation or meals receipts
The meals comparison calculation determines a maximum amount for the total amount of
accommodation expenses with statements, that can be paid out without further checks. You can decide
whether the reimbursement of the total accommodation expenses is limited to this maximum amount or
whether the total amount should be reimbursed.
If you want to use the comparison calculation for accommodation, you can also choose whether this
comparison should be completed for domestic trips, international trips, or all trips, The comparison
calculation can only take place if you have entered accommodation receipts.
The meals comparison calculation compares the total amount for the meals receipts minus the cost of
living saving with the possible meals per diems amount. The meals comparison calculation is completed
for both domestic and international trips, and as with the accommodation comparison calculation, can
only be completed if you have entered meals receipts.
The comparison calculation for trip segment reimbursement and travel costs compares the actual
amounts for the trip segment reimbursement and the travel cost receipts with the fictitious reimbursement
amounts for trip segment reimbursement and the travel cost of a comparison trip. As the trip duration for
a comparison trip often changes due to the selection of different transportation methods, you can also
include the meals per diems and accommodation per diems in the comparison calculation
You can choose whether to use the comparison calculation for trip segment reimbursement and travel
costs for domestic trips, international trips or both domestic and international trips.
Again, you cn only complete this comparison calculation if you have created travel cost receipts for
public transport or you have entered trip segment information.
Effects on Customizing
You activate the different comparison calculations in Customizing for Travel Expenses under Set up
Comparison Calculation (Public Sector Germany.
See also
For more information about comparison calculations for Public Sector Germany, see
Public Sector Germany: Comparison Calculation for Meals
______________________________________________________________
SAP AG
154
SAP System
______________________________________________________________
Public Sector Germany: Comparison Calculation for Accommodation
5.19.4.28 Separation of Travel Requests and Requests for Travel Expense
Reimbursement in Public Sector.
Use
SAP R/3 Enterprise Travel Extension 1.10 (EA-HR 110) allows you to separate travel requests and
requests for travel expense reimbursements in Public Sector. This means that at least one transferred
version of the travel request and one version of the travel expense statement remains once the travel
expenses have been transferred. This allows you to ensure that the travel request data is available when
settlement takes place, this can be particularly useful for control reasons.
This area includes the following new functions:
o
In IMG activity Define Schemas and Individual Field Control, you can use an existing trip
schema as a template for a travel request schema. To do this, place the cursor on the trip schema.
This will call up a list of fields and screens that can be shown/hidden in the schema. Choose Copy
for Request Schema to copy the trip schema and use it as a request schema.
o
The fields that are relevant for creation or settlement rules cannot be accessed or changed in either
schema. The fields that are marked as being not ready for input in the trip schema are also not
available in the request schema. This means that the request schema can only contain the same
number of fields and screens as the trip schema. This function is not available for fast entry,
advance, planning or per diem schemas or weekly reports.
o
Transaction PR05 only suggest schemas that are request schemas or trip schemas that do not have a
separate request schema. If you want to ensure that all trips are entered with a request, you must
ensure that all trip schemas also have a request schema.
o
If you select a schema that isn't a request schema, the system issues an error message and you can
then create a new entry from there.
o
If the trip provision variant has active request versioning, feature TRVPA will not be evaluated
when the trip is saved. A request will always have the status request created, to be settled and a
trip will always have the status trip created, to be settled. After the request has been approved it
cannot be changed or deleted. It can, therefore only be canceled once it has been successfully
transferred, and it remains in the system.
o
If a request has been transferred the appropriate trip schema will be automatically set when any
changes are made. This means that the fields and screens specified in Customizing will be available
for making entries.
o
Once you have created a trip, you can display the corrections by either choosing the appropriate
button, or by using report RPR_APPROVE_TRAVEL_EXPENSES. This report also allows you to
display and compare the request forms. Furthermore you can display and print the forms for both
versions.
Effects on Customizing
______________________________________________________________
SAP AG
155
SAP System
______________________________________________________________
To use travel requests versions for Public Sector you must activate this function in Customizing under
Activate special rules for Industry Solutions
See also
For more information see the SAP Library under FI - Travel Management -> FI Travel Expenses ->
Country and Industry Solutions for Travel Expense Accounting.
______________________________________________________________
SAP AG
156
SAP System
______________________________________________________________
6 TR
Treasury
6.1 Various enhancements in cash management
Use
Cash position/Liquidity forcast
o
You can specify a calender and then only columns for working days in this calender, are displayed.
Until now, only the weekend could be hidden in the display and the amounts cumulated until the
next Monday
o
For the amount columns, you can choose between narrow, medium, or wide format.
o
You can go into payment orders in the cash position.
o
In the liquidity forcast, you can enter the FI line items (-> SAP note 16713).
o
For the liquidity forcast, the calculation of the planning date (at the time of posting) can be affected.
You can find further information in F1-help for the 'DtCo' column (Control of planning date for
planning groups) in the view V_T035.
Account clearing
o
For each account you can determine a minimum balance (in view V_T018C), which can be used as
the credit limit (when entering a negative amount) or as the base amount (when entering a positive
amount). If the amount is not reached during clearing, the account is highlighted and a warning is
issued when saving.
o
Accounts with various different currencies can be included. The 'Account currency' parameter
remains empty and the currency relevant for clearing is entered in the new 'Planning currency'
parameter. You can find further information in the F1-help for the new 'Planning currency'
parameter.
Creating payment requests for bank account transfers
o
When creating payment requests from payment advice notices you can determine the relevant
payment method via the new view V_T018Z and therefore you can include several payment
methods in one run (from report RFFDZA00).
Payment advice comparison
o
With the new report RFFDIS47, you can compare bank statement payment advice notices to manual
payment advice notices. This is an alternative to report RFFDIS46 with which the bank statement
can be compared to manual payment advice notices. You can find further information in the report
documentation for report RFFDIS47.
Contract accounts receivable
o
The contract accounts receivable update (FI-CA) in cash management is included in the structure
and reconciliation program (this function was made available by support package also in release
4.6C)
Scheduling agreement for supplier (Order update from SD)
______________________________________________________________
SAP AG
157
SAP System
______________________________________________________________
o
A design gap has been closed. Please consider SAP note 320916.
6.2 TR-CM
Cash Management
6.2.1 Various enhancements in cash management
Use
Cash position/Liquidity forcast
o
You can specify a calender and then only columns for working days in this calender, are displayed.
Until now, only the weekend could be hidden in the display and the amounts cumulated until the
next Monday
o
For the amount columns, you can choose between narrow, medium, or wide format.
o
You can go into payment orders in the cash position.
o
In the liquidity forcast, you can enter the FI line items (-> SAP note 16713).
o
For the liquidity forcast, the calculation of the planning date (at the time of posting) can be affected.
You can find further information in F1-help for the 'DtCo' column (Control of planning date for
planning groups) in the view V_T035.
Account clearing
o
For each account you can determine a minimum balance (in view V_T018C), which can be used as
the credit limit (when entering a negative amount) or as the base amount (when entering a positive
amount). If the amount is not reached during clearing, the account is highlighted and a warning is
issued when saving.
o
Accounts with various different currencies can be included. The 'Account currency' parameter
remains empty and the currency relevant for clearing is entered in the new 'Planning currency'
parameter. You can find further information in the F1-help for the new 'Planning currency'
parameter.
Creating payment requests for bank account transfers
o
When creating payment requests from payment advice notices you can determine the relevant
payment method via the new view V_T018Z and therefore you can include several payment
methods in one run (from report RFFDZA00).
Payment advice comparison
o
With the new report RFFDIS47, you can compare bank statement payment advice notices to manual
payment advice notices. This is an alternative to report RFFDIS46 with which the bank statement
can be compared to manual payment advice notices. You can find further information in the report
documentation for report RFFDIS47.
Contract accounts receivable
o
The contract accounts receivable update (FI-CA) in cash management is included in the structure
and reconciliation program (this function was made available by support package also in release
______________________________________________________________
SAP AG
158
SAP System
______________________________________________________________
4.6C)
Scheduling agreement for supplier (Order update from SD)
o
A design gap has been closed. Please consider SAP note 320916.
6.2.2 TR-CM-CM
Basic Functions
6.2.2.1 Various enhancements in cash management
Use
Cash position/Liquidity forcast
o
You can specify a calender and then only columns for working days in this calender, are displayed.
Until now, only the weekend could be hidden in the display and the amounts cumulated until the
next Monday
o
For the amount columns, you can choose between narrow, medium, or wide format.
o
You can go into payment orders in the cash position.
o
In the liquidity forcast, you can enter the FI line items (-> SAP note 16713).
o
For the liquidity forcast, the calculation of the planning date (at the time of posting) can be affected.
You can find further information in F1-help for the 'DtCo' column (Control of planning date for
planning groups) in the view V_T035.
Account clearing
o
For each account you can determine a minimum balance (in view V_T018C), which can be used as
the credit limit (when entering a negative amount) or as the base amount (when entering a positive
amount). If the amount is not reached during clearing, the account is highlighted and a warning is
issued when saving.
o
Accounts with various different currencies can be included. The 'Account currency' parameter
remains empty and the currency relevant for clearing is entered in the new 'Planning currency'
parameter. You can find further information in the F1-help for the new 'Planning currency'
parameter.
Creating payment requests for bank account transfers
o
When creating payment requests from payment advice notices you can determine the relevant
payment method via the new view V_T018Z and therefore you can include several payment
methods in one run (from report RFFDZA00).
Payment advice comparison
o
With the new report RFFDIS47, you can compare bank statement payment advice notices to manual
payment advice notices. This is an alternative to report RFFDIS46 with which the bank statement
can be compared to manual payment advice notices. You can find further information in the report
documentation for report RFFDIS47.
Contract accounts receivable
______________________________________________________________
SAP AG
159
SAP System
______________________________________________________________
o
The contract accounts receivable update (FI-CA) in cash management is included in the structure
and reconciliation program (this function was made available by support package also in release
4.6C)
Scheduling agreement for supplier (Order update from SD)
o
A design gap has been closed. Please consider SAP note 320916.
______________________________________________________________
SAP AG
160
SAP System
______________________________________________________________
7 CO
Controlling
7.1 CO Document Header: Reference Transaction Filled for Internal
Document
Use
From Release 4.7 (R/3 Enterprise), the following fields will also be filled in the CO document header
(COBK table) for CO internal postings:
o
Reference transaction (AWTYP field) is filled with the fixed value COBK (cost accounting
document).
o
Reference organizational unit (AWORG field), is filled with the controlling area.
This only affects CO documents for actual postings (value type 04). For documents with other value
types (e.g. plan, down payments, splitting), the fields remain blank.
Effects on Existing Data
Documents that have already been posted are not changed. The change only applies to the new documents
that are posted. A program is not provided in the standard system for adapting the old documents.
Effects on Data Transfer
Customer programs that rely upon the fields in CO internal postings not being filled may need to be
adapted.
7.2 CO-OM
Overhead Cost Controlling
7.2.1 Transfer of Actual Data into Controlling (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the infrastructure of the batch input for actual
postings in Controlling is no longer maintained. Instead, you are provided with the BATCHMAN
transaction. This provides tools that support the data transfer from external systems into the Controlling
system in SAP R/3 for all actual posting transactions. The data transfer is logged whereby earlier posting
runs can be displayed, documents that could not be updated are listed in an error list (can be
postprocessed automatically, semi-automatically or manually) and data transfers can be reversed.
Effects on Data Transfer
A BAdI (Business Add-In) implements the upload of posting data into SAP R/3. A sample
implementation that uploads the data from an Excel sheet saved in TXT format is delivered. Customer
requirements for external data formats must be realized in customer BAdI implementations.
Effects on Customizing
______________________________________________________________
SAP AG
161
SAP System
______________________________________________________________
To implement and activate the upload of your own external data formats, use the activity below in the
implementation guide (IMG) for Cost Center Accounting:
Implement the Transfer of External CO Actual Data.
7.2.2 BAPIs for Actual Postings in Controlling (Extended)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) some new business application programming
interfaces (BAPI) have been developed, and some existing ones have been improved in CO-OM
(Overhead Cost Controlling). The new developments or additions support the following functions:
o
Searching for documents
o
Reading planning data
o
Checking and posting secondary cost allocations
o
Reversing actual postings from all CO transactions
o
Profitability segments as sender and receiver account assignments
o
Flexible control of valuation of activity allocations.
Effects on Existing Data
New BAPIs
Document reader
This BAPI finds CO documents in SAP R/3 according to certain criteria:
o
Account assignment object
o
Reference transaction (information on the components outside of CO that wrote the document)
o
Interval for posting date and period/fiscal year (important for special periods).
Manual cost allocation
You can use this BAPI to check and post the "manual cost allocation" transaction. The transaction
enables you to allocate specific secondary costs between the selected account assignment objects, in the
same way as distribution and assessment where this is done automatically.
Reversal
Reversal BAPIs have been introduced for all transactions.
BAPI Extensions
Customer fields
For nearly all transactions (except for "manual cost allocation") you can check and post customer fields
also.
Profitability segment
For the "primary cost reposting", "revenue reposting" and "manual cost allocation" transactions, you can
______________________________________________________________
SAP AG
162
SAP System
______________________________________________________________
assign profitability segments as senders and receivers.
External valuation
When you allocate activity, you can determine how the allocated activity quantity is to be valuated. The
valuation can either be transferred in the interface to the BAPI or be dynamically determined (by the
implementation of a corresponding BAdI) from the account assignment data. You can specify total prices
or fixed and variable price portions as well as total values or fixed and variable value portions.
Transaction currency per row
In the "primary cost reposting", "revenue reposting" and "manual cost allocation" transactions, you can
specify the transaction currency in each row (no longer on the header level only).
Extension of the interface for activity allocation in Joint Venture Accounting
If the Joint Venture Accounting component is active, you can specify the valuation period and year for
the valuation with plan prices in activity allocations.
See also
Release Note: BAdI for The Valuation of Activity Allocations.
7.2.3 Valuation of activity allocations
Use
Activity allocations are valuated with standard rules from SAP R/3 Enterprise Core 4.70 (SAP_APPL
470) depending on the transaction in which they are entered:
o
If the receiver of the activity allocation is an object with a costing variant (for example, a production
order), the strategy sequence that is assigned to the costing variant is processed for the valuation.
o
For all the other receiver objects, the following strategy sequence applies:
-
1. External price
-
2. Actual price
-
3. Plan price
(Until now, these rules only applied for activity allocations for logistics confirmation. The system always
used the plan price for valuating the activity allocations in Controlling, providing the user did not
manually enter an external price.)
7.2.4 BAdI For The Valuation of Activity Allocations (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the Business Add In EXT_VALUATION_IAA
has been introduced for the valuation of activity allocations. This enables you to determine the valuation
of activity allocations and thus override the standard valuation in conjunction with the account
assignment objects (sender and receiver) and their characteristics.
______________________________________________________________
SAP AG
163
SAP System
______________________________________________________________
You can specify the price and the total value for the activity quantity to be valuated.
The BAdI is effective for
o
The manual entry of activity allocations (transactions KB21N and KB21)
o
The transfer of data from the time sheet (CA-TS) to Controlling (transaction CAT7)
o
The entry of cost-relevant confirmation from Logistics (transactions CO1F, CO11N, CO15, IW41,
IW42, IW44, IW48, CN25, CN27, CAT5 and CAT9)
o
The posting of activity allocations using the BAPI AcctngActivityAlloc.Post (function module
BAPI_ACC_ACTIVITY_ALLOC_POST).
Effects on Customizing
To implement and activate your own valuation control, use the activity below from the implementation
guide (IMG) for Cost Center Accounting:
Implement External Valuation of Activity Allocations.
7.2.5 Overhead Rates: Calculation Base Cost Center/Activity Type (Extended)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can define calculation bases for overhead
rates according to cost center and activity type. For each controlling area, you assign individual cost
centers or cost center ranges, or individual activity types or activity type ranges, to the calculation bases.
Previously, you could only define bases according to cost element and origin.
Effects on Customizing
To define calculation bases, use:
Defining calculation bases according to cost center and activity type
7.2.6 Transactions for The Manual Actual Postings in Controlling (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the use of the old transactions for manual actual
postings in Controlling (KB11, KB15, KB21, KB27, KB31, KB41, KB51, KB71) is restricted to batch
input. When you call these up using the transaction code, the system goes to the corresponding new
transaction (KB11N, KB15N, KB21N, KB31N, KB41N, KB51N). The functions in the KB27 and KB71
transactions have now been integrated into transactions KB21N and KB61.
______________________________________________________________
SAP AG
164
SAP System
______________________________________________________________
7.2.7 Deletion Program for Archiving Object CO_CCTR_ID (Extended)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you are provided with a new deletion
program. The deletion program provided in earlier releases has been removed.
Effects on Customizing
If you use your own variants for the deletion program, you need to enter new variants in the
object-specific customizing.
See also
For more information on the CO_CCTR_ID archiving object, see the SAP Library under
Cross-Application Components -> Archiving Application Data (CA-ARC) -> Controlling (CO) ->
Archiving Cost Center Data (CO-OM-CCA) -> Archiving Cost Center - Actual Data (CO-OM-CCA).
7.2.8 WBS Element Groups (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can use the following additional
functions for the WBS element groups:
New transaction
You can change WBS element groups with the new transaction KJH2.
New authorization object
Using the new authorization object K_PRPS_SET you can restrict the authorization to display WBS
element groups (transaction KJH3) and change WBS element groups (transaction KJH2).
The new authorization object contains the following fields:
o
Group name
o
Activity
The protected activities in maintenance of WBS element groups are:
-
02 = change
-
03 = display
Effects on System Administration
If you want to use the new object you must maintain authorizations and roles. SAP delivers the object in
the authorization SAP_ALL with all authorizations for all groups.
______________________________________________________________
SAP AG
165
SAP System
______________________________________________________________
7.2.9 CO-OM-CEL
Cost Element Accounting
7.2.9.1 CO-OM-CEL-RE
Reconciliation Financial Accounting / Controlling
7.2.9.1.1 Partner Functional Area for Reconciliation Between CO and FI
Use
Before Release 4.70 the Partner Functional Area field was used for summarization during the CO-FI
reconciliation (KALC transaction).
The FI documents created during the CO-FI reconciliation were summarized accordingly by the system,
since this field did not exist in FI.
Since this system behavior sometimes caused problems, this summarization was deactivated for release
4.70.
For more information, see the OSS note no. 431218 (created for Release 4.70) in the standard system.
Effects on Existing Data
The Partner Functional Area field will not be used for future reconciliation postings when FI documents
are created.
Data that has already been posted is not affected.
Effects on System Administration
If you want to reactivate summarization with the Partner Functional Area field, the correction
instructions in note no. 431218 need to be removed from the system.
The system then behaves as it did for releases prior to 4.70.
7.2.10 CO-OM-CCA
7.2.10.1 CO-OM-CCA-PL
Cost Center Accounting
Cost Center Planning
7.2.10.1.1 Read BAPIs for Overhead Cost Planning (New)
Use
In the SAP R/3 releases 4.5A and 4.6A, business application programming interfaces (BAPIs) were
delivered for the data transfer to Overhead Cost Planning (function group 6026 or transaction BAPI,
object "CostActivityPlanning").
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), four read BAPIs are provided for these check and
update BAPIs ("ReadActivityInput", "ReadActivityOutput", "ReadKeyFigure", and "ReadPrimCost").
You can use these BAPIs to re-export the posted data. However, they only take into account the data that
was created with the corresponding update BAPIs or with manual planning. Data from automatic
transactions such as settlement or assessment is not taken into account.
______________________________________________________________
SAP AG
166
SAP System
______________________________________________________________
See also
For more information on the new BAPIs, see the BAPI transaction or the online documentation for the
BAPIs (function group 6026).
7.2.10.2 CO-OM-CCA-CM
Commitments and Funds Commitments
7.2.10.2.1 Comitment Update for Invoice Receipt Without Goods Receipt
Use
The following situation occurs for an order:
- Evaluated goods receipt
- Invoices are created whose unit price is higher than the purchase order value
In earlier releases, the system assumed that the value of the goods received is also higher than the
purchase order value and consequently increased the commitment by this difference.
This procedure was changed for Release R/3 Enterprise (4.70). If you want the same system procedure as
for earlier releases, you must install the modification from note 490624.
Effects on Existing Data
Existing commitments are not affected.
Recalculation according to the logic described above is executed if the order is changed again, or can be
triggered by the correction report RKANBU01.
If you installed the above note, no action is required.
See also
Note 216255
7.2.11 CO-OM-OPA
Overhead Cost Orders
7.2.11.1 Resource-Related Billing for Internal Orders With Revenues (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can process resource-related billing for
internal orders with direct revenues.
Up to now, resource-related billing was not possible for:
o
Sales documents with cost collectors
o
Service orders with revenues
______________________________________________________________
SAP AG
167
SAP System
______________________________________________________________
o
WBS elements with revenues
Costs of internal orders could only be taken into account after they were settled to one of the objects in
resource-related billing.
Direct resource-related billing is now possible for internal orders with revenues using a sales document
without cost collectors. The process is based on the current solution for resource-related billing for
projects/WBS elements.
Effects on Customizing
To use the new functions, You must define in Customizing for sales document items that account
assignments are possible for internal orders. To do this, go to:
Control Sales-Order-Related Production / Sales Order Controlling
7.2.11.2 Deletion Program for Archiving Object CO_ORDER (enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , a new deletion program is available for the
archiving object CO_ORDER. The deletion program available in previous releases was removed.
The new deletion program provides a standard log, which displays the number of deleted entries for each
table.
Effects on Customizing
If you use your own variants for the deletion program, you must enter new variants in object-specific
Customizing.
See also
For more information on the archiving object CO_ORDER, see the SAP Library under Cross-Application
Components -> Archiving Application Data (CA-ARC) -> Controlling (CO) -> Archiving Internal
Orders (CO-OM-OPA) -.> Archiving Orders With Transaction Data (CO-OM-OPA).
7.2.11.3 Static Processing of Resource-Related Billing (Deleted)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the static processing of resource-related
billing (transaction VA90), as announced for Release 4.5, is no longer available. Instead you can use the
dynamic processing (transaction DP90). It contains all of the required functions.
Effects on Existing Data
You must convert your existing orders to dynamic processing.
______________________________________________________________
SAP AG
168
SAP System
______________________________________________________________
Effects on Customizing
You must convert your system to the dynamic processing of resource- related billing. You can do this
even before converting to SAP R/3 Enterprise for all Releases from 4.5B and above.
For more information about converting to dynamic processing, see Customizing (IMG) for creating
quotations and billing under Static Processing (Process before Release 4.5).
7.2.11.4 CO-OM-OPA-PL
Order Planning
7.2.11.4.1 Planning and Budgeting in Any Currency (new)
Use
International groups often use one uniform company code currency (group currency) in CO. However, it
may be necessary to plan and budget in the respective local currency as the majority of costs will be
incurred in the local currency. The local currency is usually the corresponding company code currency.
Previously only budgeting of jobs (orders and projects) was possible in the local currency.
From Release 4.70, you can also budget investement programs in the local currency. In addition, it is
possible to plan investment programs, appropriation requests and jobs directly in the local currency.
As was previously the case for orders and projects, plan and budget values for investment programs and
appropriation requests are also saved in both the controlling area and local currencies defined in the
master record of each object. If you change or re-specify the exchanged rates used, it is now possible to
recalculate the values in the local currency using the values in the controlling area currency, and
vice-versa.
In reporting for IM, it is even possible to calculate evaluations in any report currency (plan, budget and
assigned values). If the values are available in the specified report currency, they are issued unchanged. If
they are not available, they are converted from the controlling area currency into the report currency.
Effects on Existing Data
Before Release 4.70, the plan values for appropriation requirements, were only saved in the controlling
area currency. This was also the case if a local object currency was specified in the master record for the
appropriation requirement. From Release 4.70, the plan values for appropriation requirements are always
saved in the controlling area and local currencies. Therefore, you must adjust appropriation requests that
were created in an earlier release and use a local currency that varies from the local object currency. The
easiest way to do this is to use the program RAIMCRC2 to recalculate the plan values in the local object
currency for appropriation requests whose plan values are in the controlling area currency (transaction
IMCRC2, menu path: Financial Accounting -> Investment Management -> Appropriation Requests ->
Tools -> Recalculate Currency Plan for Appropriation Requests). Before you run the program, select the
relevant option in the Process Control section of the initial screen.
Effects on Customizing
Adjustment of Planning and Budget Profiles
To enable the planning of investment programs, appropriation requests and jobs in a transaction currency
different to the controlling area currency, you must adjust the relevant planning profiles.
______________________________________________________________
SAP AG
169
SAP System
______________________________________________________________
To enable the budgeting of investment programs in a transaction currency different to the controlling area
currency, you must adjust the relevant budget profiles.
In the planning currency (or budgeting currency) section of the planning (or budget) profile, you must
define the transaction currency in which planning (or budgeting) is to be executed:
o
Only in the controlling area currency (default),
o
Only in the object currency
(= local currency defined in object master record ) or
o
In a transaction currency chosen at the start of planning/budgeting
(this option is not possible for appropriation requests).
In the planning or budget profiles, you must also define the exchange rate types to be used for the
conversion of total values that are not dependent on the fiscal year.
To adjust the planning profiles, use the process steps:
Maintain Planning Profiles (investment programs)
Maintain Planning Profile for Cost Planning (appropiation requests)
To adjust the budgeting profiles, use the process steps:
Define Budget Profiles for Investment Programs (investment programs)
Exchange Rate Types
In the fiscal-year-dependent data of the CO planning versions, you must also define the exchange rate
types to be used for conversion of plan values that are not dependent on the fiscal year.
For conversion of fiscal-year-dependent budget values and fiscal-year-dependent plan values of
appropriation request variants not yet assigned to a plan version, each exchange rate type is taken from
the fiscal-year-dependent data of the CO planning versions 0.
As the plan or budget values are stored in the transaction, controlling area, and local currencies, the
exchange rates used must enable the conversion of the transaction currency into the controlling area and
local currencies. Where necessary, the exchange rates used must be extended.
To enter the exchange rate types, use the process step:
Define Versions (investment programs)
Change Planning or Budget Currency
If you always planned or budgeted existing investment programs/measures in the controlling area
currency, it is not subsequently possible to change the planning or budget currency to the object currency
in the planning or budget profiles. This conversion is not prevented in Customizing, but leads to an error
when you next plan or budget existing investment programs/measures. Alternatively, you can convert the
planning or budget currency into the transaction currency in the planning or budget profiles, and set the
object currency indicator as default.
A similar restriction does not exist for appropriation requests. You can change the planning currency in
the planning profile at any time.
Use the process step under "Adjust the Planning and Budgeting Profiles".
Detailed Planning
______________________________________________________________
SAP AG
170
SAP System
______________________________________________________________
When you call up detailed planning from structure-based cost planning or revenue planning, the standard
SAP planning profiles are used, to which the standard SAP planning layouts are assigned. These planning
profiles cannot be changed in the planning transactions. Import the standard SAP planning layouts
1-401-IM, 1-402-IM, 1-403-IM, 1-701-IM, 1-702-IM and 1-703-IM using the transaction OKBF from
client 000 in your client.
To execute the import, choose the process step:
Import Standard Planning Layouts.
Reporting Currency for IM Reporting
In IM reporting, if you want to be able to specify a reporting currency that is different to the controlling
area and object currencies used in the investment program items or subordinate appropriation requests
and measures, another exchange rate type is required for the due conversion of plan, budget, or values
into the reporting currency. You define this exchange rate type in Customizing for the program type for
the investment program to be reported ( Group Reporting).
To enter additional reporting currencies, use the process step:
Define Program Types (investment programs)
See also
For more information on the new functions, see the application help for the relevant transactions, or the
corresponding IMG documentation.
7.2.11.5 CO-OM-OPA-BU
Order Budgeting
7.2.11.5.1 Availability Control in Object Currency (new)
Use
Before SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), active availability control for orders and projects
only worked based on the controlling area currency.
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can also execute active availability control in
the object currency. This setting is useful if the budget for jobs was entered in an object currency
different to the controlling area currency, as it eliminates the effects of exchange rate fluctuations on the
budget available in the object currency (current budget - assigned value).
Note that you can only use the new function for projects if all objects (WBS elements, networks, orders)
in the budget hierarchy are in the same object currency.
Effects on Existing Data
Before SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the assigned values for orders and projects were
only saved in the controlling area currency on the database. From SAP R/3 Enterprise Core 4.70
(SAP_APPL 470), the assigned values are saved either in the controlling area currency or the object
______________________________________________________________
SAP AG
171
SAP System
______________________________________________________________
currency.
Effects on Data Transfer
You can also execute availability control in the object currency for existing jobs. Note: If activity control
was active already for the existing jobs or projects, after making the relevant change in the budget profile
settings, you must reconstruct availability control using transaction KO31 or CJBN.
Effects on Customizing
To enable availability control in the object currency, you must set the object currency flag in the budget
profiles of your jobs, under availability control.
To do so, use the steps:
Maintain Budget Profile (internal orders)
Maintain Budget Profile (projects)
See also
For more information on this function, see the SAP Library.
7.2.11.6 CO-OM-OPA-CM
Commitments and Funds Commitments
7.2.11.6.1 Field Control for Funds Commitments (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the field control functions for fund commitments
in Funds Management are also available in the IMG for internal orders.
Effects on Customizing
In Customizimg for internal orders, you can now execute five process steps for field control. You find the
IMG activities under
Controlling -> Internal Orders -> Commitments and Funds Management -> Funds Management
-> Field Control: Funds Management.
You can then choose:
Define Field Status Variant
Assign Field Status Variant to Company Cod
Define Field Status Groups
Define Field Selection String
Assign Field Selection String
______________________________________________________________
SAP AG
172
SAP System
______________________________________________________________
7.2.11.6.2 Comitment Update for Invoice Receipt Without Goods Receipt
Use
The following situation occurs for an order:
- Evaluated goods receipt
- Invoices are created whose unit price is higher than the purchase order value
In earlier releases, the system assumed that the value of the goods received is also higher than the
purchase order value and consequently increased the commitment by this difference.
This procedure was changed for Release R/3 Enterprise (4.70). If you want the same system procedure as
for earlier releases, you must install the modification from note 490624.
Effects on Existing Data
Existing commitments are not affected.
Recalculation according to the logic described above is executed if the order is changed again, or can be
triggered by the correction report RKANBU01.
If you installed the above note, no action is required.
See also
Note 216255
7.2.11.7 CO-OM-OPA-CL
Periodic Order Closing
7.2.11.7.1 Settlement of Investment Support for Assets Under Construction
(Extended)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can also settle investment support from
independent assets under construction (AUC), and from AUC that belong to investment measures posted
to the AUC during the settlement year.
Previously, you could only post investment support to completed assets in the year of capitalization.
When determining the proportion of investment support to be transferred for partial capitalization or
distribution to several receivers, it is assumed that investement support posted to the AUC during the year
of capitalization also refers to asset acquisitions during the year of capitalization.
If the investment support that you post to AUC refer to prior-year acquisitions, you must use the
transaction type Kxx for the investment support measure xx.
Effects on Existing Data
If you used transaction type Ixx to post to the AUC investment support that refers to prior-year
acquisitions, delete these postings and repost them using the relevant transaction type Kxx.
______________________________________________________________
SAP AG
173
SAP System
______________________________________________________________
Effects on Customizing
Check whether a transaction type Kxx is also created for the investment support measures used. (Usually
these transaction types are created automatically when you set up the investment support measure.) To do
this, use the process step
Check Transaction Types for Support Measures.
7.2.11.7.2 CO-OM-OPA-CL-IC
Interest Calculation
7.2.11.7.2.1 Interest Calculation for Special Periods (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can carry out a special interest
calculation for special periods in projects or internal orders.
Constraints
o
When postings in special periods are due, the balance of the previous period for the time frame of
one day is calculated with interest. This is in addition to the interest debits and interest revenues.
Due to technical reasons this cannot be prevented.
o
In the log, the postings in special periods are shown as value dates in the past.
o
If you calculate interest for special periods in a special way, you must start a separate interest
calculation run for each special period. This could lead to inconsistencies otherwise.
See also
For more information about calculating interest for special periods, see SAP Note 206182.
7.2.12 CO-OM-IS
Information System, iViews
7.2.12.1 DRB (Enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , the Document Relationship Browser (DRB)
offers an extended selection of object types. Object types have been added to the DRB, and object types
that were already connected in earlier releases have been completed.
New object types:
o
Profit center document
o
Costing-based profitability analysis
o
Electronic account statement
______________________________________________________________
SAP AG
174
SAP System
______________________________________________________________
o
Production order
o
Backflush document
The connection of these object types only affects the functions within the DRB. There are no separate
access programs.
Enhanced object types:
o
Accounting document
From the document display (transaction FB03), you can branch to the DRB. You can use report
RDRBFI00 to access the DRB and to find archived accounting documents via the archive
information system (SAP AS).
o
Controlling document
From the line item reports (for example, transaction KSB1, KSB5, KOB1), you can branch to the
DRB.
The DRB functions can find Controlling documents in the archives of all archiving objects that
archive Controlling line items. There are several field catalogs and info structures for this.
See also
For more information about the Document Relationship Browser, see the SAP note 492938.
7.2.12.2 Display of Archived Line Items in The Line Item Report (Extended)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can export line items in the line item
report from the database and archive, as well as display these in a line item report. In previous releases,
you could either read and display line items from the database or line items from the archive.
You can display all documents (source and follow-up documents) linked to line item documents using the
Document Relationship Browser (DRB). This enables you to display all documents that belong to a
business transaction or process chain, regardless of the application.
To access the functions of the Document Relationship Browser, and to display linked documents, choose
Extras -> Relationship Browser.
See also
For more information on the Document Relationship Browser, see the SAP Library under mySAP
Technology Components -> SAP Web Application Server -> Basis Services / Communication Interface
(BC-SRV) -> Business Workplace and Services (BC-SRV-OFC) -> Document Relationship Browser.
7.3 CO-PC
7.3.1 CO-PC-PCP
Product Cost Controlling
Product Cost Planning
______________________________________________________________
SAP AG
175
SAP System
______________________________________________________________
7.3.1.1 External Cost Estimate Interface Through BAPIs
Use
Unified interfaces for the BOR (Business Object Repository) object Costestimate BUS2044 are available
from Release 4.70.
o
BAPI_COSTESTIMATE_GETLIST provides an additional selection condition (costing run) and
enables selection of existing cost estimates.
o
BAPI_COSTESTIMATE_GETDETAIL provides the partner cost component split and the direct
partner cost component split for existing cost estimates. All results are also output in auxiliary cost
component splits.
o
The interface BAPI_COSTESTIMATE_CREATE_SPLIT enables cost estimates to be imported
from non-SAP systems into R/3 systems or created in R/3 systems. Data on the cost component
split, partner cost component split, direct partner cost component split, auxiliary cost component
split, and costing header data can be output.
o
BAPI_COSTESTIMATE_DELETE enables you to delete a cost estimate in R/3 based on the
costing key.
o
BAPI_COSTESTIMATE_DELETE_MULTI enables you to delete multiple cost estimates in R/3
based on selection criteria.
o
BAPI_COSTESTIMATE_MARKING enables you to mark multiple cost estimates based on
selection criteria.
o
BAPI_COSTESTIMATE_RELEASING enables you to release multiple cost estimates based on
selection criteria.
o
BAPI_COSTESTIMATE_ALLOW_MARK enables you to issue marking allowance for one or
more cost estimates for a given company code, posting period, fiscal year, valuation view, costing
variant, and costing version. The corresponding cost estimates are selected in marking.
o
BAPI_COSTESTIMATE_ALLOW_MA_GET provides the organizational measures for the
selection criteria.
o
BAPI_COSTESTIMATE_UPDATE_PRICE enables multiple cost estimates to be selected and
updated in the material master. Either planned price 1 to 3, commercial price 1 to 3, or tax price 1 to
3 are updated.
Effects on Existing Data
If you implement the interface, note the following.
o
BAPI_COSTESTIMATE_CREATE_SPLIT
If you are using non-SAP systems and create a cost estimate based on this data, you can use the cost
estimate in an R/3 environment, for example as a reference cost estimate or in transfer control. You
can transfer the results to Actual Costing/Material Ledger, Profitability Analysis, Sales Order
Costing, and Inventory Valuation.
o
BAPI_COSTESTIMATE_DELETE and BAPI_COSTESTIMATE_DELETE_MULTI
The functionality of these interfaces corresponds to the functionality of transaction CKR1 Delete
Test Data. Read the documentation in transaction CKR1 under Application Help Deleting Material
Cost Estimates.
______________________________________________________________
SAP AG
176
SAP System
______________________________________________________________
o
BAPI_COSTESTIMATE_MARKING und BAPI_COSTESTIMATE_RELEASING
The functionality of these interfaces corresponds to the functionality of transaction CK24 Price
Update. Keep in mind the consequences that result from inventory revaluations.
o
BAPI_COSTESTIMATE_ALLOW_MARK
The functionality of these interfaces corresponds to the functionality Issue Allowance for Marking in
transaction CK24 Price Update.
Example scenario: If you want to issue marking allowance for multiple company codes, you can
automate this process with this BAPI.
7.3.1.2 Flexible Material Selection for Costing Runs
Use
The selection of materials for costing runs in Product Cost Planning will be expanded from Release
4.70 onwards.
In addition to the existing functionality, you can create a selection list that you can edit in the
maintenance transaction. You create a selection list by selecting materials based on the following
characteristics:
o
Material master data
o
BOM usage
o
Costing run reference
o
Additional material fields
o
Existing cost estimates
7.3.1.3 Mass Costing of Sales Orders
Use
A mass costing function for sales orders is available from Release 4.70. This function enables you to
execute mass costing of sales orders in the background and select the order items based on various
criteria. You can also mark cost estimates in valuated sales order stocks.
Effects on Customizing
If you use mass costing for sales orders, you should check the requirements classes in Customizing to
make sure that sales order items are not automatically costed or marked when the document is saved. You
do this in Customizing for Cost Object Controlling under Product Cost by Sales Order -> Control of
Sales-Order-Related Production/Product Cost by Sales Order -> Check Requirements Classes.
______________________________________________________________
SAP AG
177
SAP System
______________________________________________________________
7.3.2 CO-PC-OBJ
Cost Object Controlling
7.3.2.1 Mass Costing of Sales Orders
Use
A mass costing function for sales orders is available from Release 4.70. This function enables you to
execute mass costing of sales orders in the background and select the order items based on various
criteria. You can also mark cost estimates in valuated sales order stocks.
Effects on Customizing
If you use mass costing for sales orders, you should check the requirements classes in Customizing to
make sure that sales order items are not automatically costed or marked when the document is saved. You
do this in Customizing for Cost Object Controlling under Product Cost by Sales Order -> Control of
Sales-Order-Related Production/Product Cost by Sales Order -> Check Requirements Classes.
7.3.2.2 Results Analysis Using Dynamic Items (Enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) additional data is updated in the document
flow of resource-related billing, which are evaluated in the results analysis methods 14 and 15 (results
analysis using dynamic items). The additional database fields significantly improve the performance of
these results analysis methods, because results analysis must no longer evaluates the document flow of
sales and distribution documents (SD documents) to determine the posting date of the revenues assigned
to billed expenditures.
Effects on Existing Data
The enhanced function is active for newly created billing documents only. For existing document flow
entries you must still use the existing results analysis.
If you implement the results analysis methods 14 and 15 intensively, you can adjust the old document
flow entries for the new logic with the program RDPRAFKDAT, thereby improving performance in
period-end closing. You do not need to make any other settings to activate this function.
7.3.3 CO-PC-ACT
Actual Costing/Material Ledger
7.3.3.1 Distribution of Usage Differences
Use
______________________________________________________________
SAP AG
178
SAP System
______________________________________________________________
You can implement the distribution of consumption differences as part of the SAP R/3 Enterprise
Financial Extension 1.10.
Physical and system quantity differences (for example, inventory differences) can occur if exact
quantities of materials, activities, and business processes cannot be posted when making confirmations
(if, for example, you are using backflushing with BOMs or are making back confirmations of activities
using a task list). The distribution of usage variances allows you to post theses differences to the
withdrawing production order, product cost collector, or the finished material.
Effects on Customizing
SAP recommends that you use your own movement types if you want to implement the distribution of
usage variances.
You create movement types in Customizing for Materials Management under Inventory Management and
Physical Inventory -> Movement Types -> Copy/Change Movement Types.
7.3.3.2 CO-PC-ACT-MAC
Multilevel Actual Costing
7.3.3.2.1 Alternative Valuation Run
Use
From Release 4.70 you can implement the Alternative Valuation Run as an enhancement to the existing
Actual Costing solution.
In addition to the standard costing run, the alternative valuation run enables you to calculate cumulative
actual values from periodic costing
The alternative valuation run enables you to calculate the cumulative actual values, from periodic actual
costing, over several periods. You can also execute several different alternative valuation runs for a single
plant using different criteria (for example, different prices or valuation methods), and then evaluate and
compare the results.
7.3.3.2.2 Revaluation of Consumption
Use
As of Release 4.70 you can revaluate comsumption for the actual period using actual prices. In particular,
t his enables you to valuate the cost of goods sold using actual prices. In earlier Releases it was only
possible to use the results from actual costing to valuate materials already delivered to the warehouse.
Effects on Customizing
In order to control and use the revaluation of consumption function, you need to create special movement
types for the revaluation in Customizing for Actual Costing/Material Ledger under Material Update and
then Define Movement Type Groups for the Material Ledger. You then assign this movement type group
to the movement types that you want use for the revaluation of consumption under Assign Material
______________________________________________________________
SAP AG
179
SAP System
______________________________________________________________
Ledger Movement Type Groups.
7.4 CO-PA
Profitability Analysis
7.4.1 Changes to the IMG Structure in Profitability Analysis
Use
With SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following changes have been made to the
Implementation Guide (IMG) for Profitability Analysis.
Under Planning -> Integrated Planning -> Transfer Cost Center Planning/Process Planning, the
following IMG activities have been included:
o
o
Under Initial Steps:
-
Activate Transfer of Cost Component Split During Activity Allocation
-
Assign PA Transfer Structure to Business Transaction
Under Direct/Indirect Activity Allocation:
-
o
Maintain Cost Component Split Assignments for Activity Allocation
Under Set Up Template Allocation:
-
Maintain Cost Component Split Assignments for Activity Allocation
The same IMG activities were included in the appropriate places under Flows of Actual Values ->
Transfer of Overhead.
See also
For more information, see the Release information Activate Transfer of Cost Component Split During
Activity Allocation.
7.4.2 CO-PA-SPP
Sales and Profit Planning
7.4.2.1 New features in CO-PA Planning
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), CO-PA Planning now offers the new planning
method Planning Sequence. This method enables you to execute all possible combinations of planning
methods in a single processing run.
Furthermore, you can now apply variables in the definition of planning levels and planning packages.
______________________________________________________________
SAP AG
180
SAP System
______________________________________________________________
7.4.2.2 CO-PA-SPP-IP
Integrated Planning
7.4.2.2.1 Transfer of Cost Component Split for Activity Allocations (New)
Use
If you use the cost component split for price calculation in Cost Center Accounting or Activity-Based
Costing, it is possible from SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) to split the prices into
their cost elements when updating them during allocations to Profitability Analysis (for actual and
planning data).
See also
For more information, see the documentation on the IMG activity Activate Transfer of Cost Component
Split During Activity Allocation.
7.4.3 CO-PA-ACT
7.4.3.1 CO-PA-ACT-OH
Flows of Actual Values
Transfer of Overhead
7.4.3.1.1 Transfer of Cost Component Split for Activity Allocations (New)
Use
If you use the cost component split for price calculation in Cost Center Accounting or Activity-Based
Costing, it is possible from SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) to split the prices into
their cost elements when updating them during allocations to Profitability Analysis (for actual and
planning data).
See also
For more information, see the documentation on the IMG activity Activate Transfer of Cost Component
Split During Activity Allocation.
7.4.3.2 CO-PA-ACT-PA
Periodic Adjustments
7.4.3.2.1 New features for periodic valuation and top-down distribution
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), it is possible to valuate individual valuation
views separately in periodic valuation. The fields Document Number and Reference Document
Number are available as selection criteria.
In the top-down distribution of actual data, it is now possible to process individual valuation views
______________________________________________________________
SAP AG
181
SAP System
______________________________________________________________
separately.
When selecting reference data, you can specify a reference currency as fixed. If necessary, several record
types can be processed in a single run. This means that you can use data with different record types as
reference data, which can be cumulated using record types.
7.4.4 CO-PA-IS
Information System
7.4.4.1 DRB (Enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , the Document Relationship Browser (DRB)
offers an extended selection of object types. Object types have been added to the DRB, and object types
that were already connected in earlier releases have been completed.
New object types:
o
Profit center document
o
Costing-based profitability analysis
o
Electronic account statement
o
Production order
o
Backflush document
The connection of these object types only affects the functions within the DRB. There are no separate
access programs.
Enhanced object types:
o
Accounting document
From the document display (transaction FB03), you can branch to the DRB. You can use report
RDRBFI00 to access the DRB and to find archived accounting documents via the archive
information system (SAP AS).
o
Controlling document
From the line item reports (for example, transaction KSB1, KSB5, KOB1), you can branch to the
DRB.
The DRB functions can find Controlling documents in the archives of all archiving objects that
archive Controlling line items. There are several field catalogs and info structures for this.
See also
For more information about the Document Relationship Browser, see the SAP note 492938.
______________________________________________________________
SAP AG
182
SAP System
______________________________________________________________
8 IM
Investment Management
8.1 IM-FA
Capital Investments
8.1.1 Planning and Budgeting in Any Currency (new)
Use
International groups often use one uniform company code currency (group currency) in CO. However, it
may be necessary to plan and budget in the respective local currency as the majority of costs will be
incurred in the local currency. The local currency is usually the corresponding company code currency.
Previously only budgeting of jobs (orders and projects) was possible in the local currency.
From Release 4.70, you can also budget investement programs in the local currency. In addition, it is
possible to plan investment programs, appropriation requests and jobs directly in the local currency.
As was previously the case for orders and projects, plan and budget values for investment programs and
appropriation requests are also saved in both the controlling area and local currencies defined in the
master record of each object. If you change or re-specify the exchanged rates used, it is now possible to
recalculate the values in the local currency using the values in the controlling area currency, and
vice-versa.
In reporting for IM, it is even possible to calculate evaluations in any report currency (plan, budget and
assigned values). If the values are available in the specified report currency, they are issued unchanged. If
they are not available, they are converted from the controlling area currency into the report currency.
Effects on Existing Data
Before Release 4.70, the plan values for appropriation requirements, were only saved in the controlling
area currency. This was also the case if a local object currency was specified in the master record for the
appropriation requirement. From Release 4.70, the plan values for appropriation requirements are always
saved in the controlling area and local currencies. Therefore, you must adjust appropriation requests that
were created in an earlier release and use a local currency that varies from the local object currency. The
easiest way to do this is to use the program RAIMCRC2 to recalculate the plan values in the local object
currency for appropriation requests whose plan values are in the controlling area currency (transaction
IMCRC2, menu path: Financial Accounting -> Investment Management -> Appropriation Requests ->
Tools -> Recalculate Currency Plan for Appropriation Requests). Before you run the program, select the
relevant option in the Process Control section of the initial screen.
Effects on Customizing
Adjustment of Planning and Budget Profiles
To enable the planning of investment programs, appropriation requests and jobs in a transaction currency
different to the controlling area currency, you must adjust the relevant planning profiles.
To enable the budgeting of investment programs in a transaction currency different to the controlling area
currency, you must adjust the relevant budget profiles.
In the planning currency (or budgeting currency) section of the planning (or budget) profile, you must
______________________________________________________________
SAP AG
183
SAP System
______________________________________________________________
define the transaction currency in which planning (or budgeting) is to be executed:
o
Only in the controlling area currency (default),
o
Only in the object currency
(= local currency defined in object master record ) or
o
In a transaction currency chosen at the start of planning/budgeting
(this option is not possible for appropriation requests).
In the planning or budget profiles, you must also define the exchange rate types to be used for the
conversion of total values that are not dependent on the fiscal year.
To adjust the planning profiles, use the process steps:
Maintain Planning Profiles (investment programs)
Maintain Planning Profile for Cost Planning (appropiation requests)
To adjust the budgeting profiles, use the process steps:
Define Budget Profiles for Investment Programs (investment programs)
Exchange Rate Types
In the fiscal-year-dependent data of the CO planning versions, you must also define the exchange rate
types to be used for conversion of plan values that are not dependent on the fiscal year.
For conversion of fiscal-year-dependent budget values and fiscal-year-dependent plan values of
appropriation request variants not yet assigned to a plan version, each exchange rate type is taken from
the fiscal-year-dependent data of the CO planning versions 0.
As the plan or budget values are stored in the transaction, controlling area, and local currencies, the
exchange rates used must enable the conversion of the transaction currency into the controlling area and
local currencies. Where necessary, the exchange rates used must be extended.
To enter the exchange rate types, use the process step:
Define Versions (investment programs)
Change Planning or Budget Currency
If you always planned or budgeted existing investment programs/measures in the controlling area
currency, it is not subsequently possible to change the planning or budget currency to the object currency
in the planning or budget profiles. This conversion is not prevented in Customizing, but leads to an error
when you next plan or budget existing investment programs/measures. Alternatively, you can convert the
planning or budget currency into the transaction currency in the planning or budget profiles, and set the
object currency indicator as default.
A similar restriction does not exist for appropriation requests. You can change the planning currency in
the planning profile at any time.
Use the process step under "Adjust the Planning and Budgeting Profiles".
Detailed Planning
When you call up detailed planning from structure-based cost planning or revenue planning, the standard
SAP planning profiles are used, to which the standard SAP planning layouts are assigned. These planning
profiles cannot be changed in the planning transactions. Import the standard SAP planning layouts
1-401-IM, 1-402-IM, 1-403-IM, 1-701-IM, 1-702-IM and 1-703-IM using the transaction OKBF from
______________________________________________________________
SAP AG
184
SAP System
______________________________________________________________
client 000 in your client.
To execute the import, choose the process step:
Import Standard Planning Layouts.
Reporting Currency for IM Reporting
In IM reporting, if you want to be able to specify a reporting currency that is different to the controlling
area and object currencies used in the investment program items or subordinate appropriation requests
and measures, another exchange rate type is required for the due conversion of plan, budget, or values
into the reporting currency. You define this exchange rate type in Customizing for the program type for
the investment program to be reported ( Group Reporting).
To enter additional reporting currencies, use the process step:
Define Program Types (investment programs)
See also
For more information on the new functions, see the application help for the relevant transactions, or the
corresponding IMG documentation.
8.1.2 IM-FA-IA
Appropriation Requests
8.1.2.1 Transfer of Appropriation Requests to Measures (Extended)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use an operative or standard WBS as a
template when creating projects from appropriation requests. It is also possible to create several projects
from a request, as long as they do not use measure replacement.
From SAP R/3 Core 4.70 (SAP_APPL 470), you can distribute the plan values or the costing of a request
to several measures, independent of the measure type (order or project).
See also
For more information on the transfer of appropriation requests to measures, see the SAP Library under
Financials -> Investment Management -> Appropriation Requests -> Transfer to a Measure to be
Implemented.
8.1.2.2 Enhancement of Field Transfer From A Request in WBS Element (new)
Use
______________________________________________________________
SAP AG
185
SAP System
______________________________________________________________
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you have the enhancement (user exit) AAIR0006,
in which you can intervene in the transfer of request data from the WBS element during creation of a
WBS element from an appropriation request.
Effects on Customizing
To call up the development of your own enhancements, use:
Enhancement for Field Transfer From Request in WBS Element
See also
Details are described in the enhancement documentation.
8.1.2.3 IM-FA-IA-MD
Master Data
8.1.2.3.1 BAdI: Checking Appropriation Requests (neu)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the new Business Add-In (BAdI)
APPREQUEST_UPDATE enables you to implement user-defined checks for appropriation requests. The
BAdI provides methods for checking data before saving or status changes. These methods provide
complete information about master data and the status of appropriation requests.
There is also a method in which you can update additional user-defined data when saving a request.
Effects on Customizing
To implement this BAdI, use the following step in the Implementation Guide for (IMG) Investment
Management:
BAdI: Check Request Master Data
See also
For more information, see the definition docmentation for the BAdI.
8.1.3 IM-FA-IP
Investment Programs
8.1.3.1 Reorganization of Investment Programs (New)
Use
Starting in SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can automatically and consistently
detach closed measures and appropriation requests from the program positions they are assigned to. This
is particularly important if you want to set the deletion flag on the measures or appropriation requests,
______________________________________________________________
SAP AG
186
SAP System
______________________________________________________________
since this is not possible if they are still assigned to an investment program position.
To reach the new function, in the Easy Access Menu choose Accounting -> Investment Management ->
Programs -> Periodic Processing -> Reorganization.
This new function removes a serious limitation that previously existed with regard to archiving measures
and appropriation requests when they were assigned to investment program positions. Archiving this kind
of measure and appropriation request (or, more precisely, setting the deletion flag necessary for
archiving) was not possible until the investment program they were assigned to was completely deleted.
This in turn required that all of the measures and appropriation requests related to the investment program
had already been closed. Since long-term measures were often not closed until several years after the
investment program was created, there was an unnecessarily long wait before archiving of measures and
appropriation requests could take place.
Effects on System Administration
If you want to set deletion flags for closed measures or appropriation requests in connection with
archiving, but they are still assigned to investment program positions, you first have to perform a
reorganization of all existing investment programs.
See also
For more information, examples, and a detailed description of how to perform the reorganization, refer to
the application help in the transaction.
8.1.4 IM-FA-IE
Investment Orders
8.1.4.1 Settlement of Investment Support for Assets Under Construction
(Extended)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can also settle investment support from
independent assets under construction (AUC), and from AUC that belong to investment measures posted
to the AUC during the settlement year.
Previously, you could only post investment support to completed assets in the year of capitalization.
When determining the proportion of investment support to be transferred for partial capitalization or
distribution to several receivers, it is assumed that investement support posted to the AUC during the year
of capitalization also refers to asset acquisitions during the year of capitalization.
If the investment support that you post to AUC refer to prior-year acquisitions, you must use the
transaction type Kxx for the investment support measure xx.
Effects on Existing Data
If you used transaction type Ixx to post to the AUC investment support that refers to prior-year
acquisitions, delete these postings and repost them using the relevant transaction type Kxx.
Effects on Customizing
______________________________________________________________
SAP AG
187
SAP System
______________________________________________________________
Check whether a transaction type Kxx is also created for the investment support measures used. (Usually
these transaction types are created automatically when you set up the investment support measure.) To do
this, use the process step
Check Transaction Types for Support Measures.
8.1.4.2 IM-FA-IE-BU
Order Budgeting
8.1.4.2.1 Change to Budget Monitoring with Orders/WBS Elements
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), there is a change to Customizing related to
monitoring budgets using statistical orders or WBS elements. Until now, you had to specify in
Customizing for Asset Accounting or Investment Management that the asset accounting transaction type
was relevant for the budget. This IMG activity has now been replaced by the new central controls for
additional account assignment in Asset Accounting.
Effects on Existing Data
The previously existing control using the Budget relevant indicator is automatically migrated to the new
structure during the upgrade.
See also
For more infomation, also see the Release Information on the subject of New Account Assignment
Objects.
8.1.5 IM-FA-PR
8.1.5.1 IM-FA-PR-BU
Projects as Investment Measures
Project Budgeting
8.1.5.1.1 Change to Budget Monitoring with Orders/WBS Elements
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), there is a change to Customizing related to
monitoring budgets using statistical orders or WBS elements. Until now, you had to specify in
Customizing for Asset Accounting or Investment Management that the asset accounting transaction type
was relevant for the budget. This IMG activity has now been replaced by the new central controls for
additional account assignment in Asset Accounting.
Effects on Existing Data
The previously existing control using the Budget relevant indicator is automatically migrated to the new
structure during the upgrade.
______________________________________________________________
SAP AG
188
SAP System
______________________________________________________________
See also
For more infomation, also see the Release Information on the subject of New Account Assignment
Objects.
8.1.6 IM-FA-IS
Information System
8.1.6.1 Depreciation Forecast and Primary Cost Planning (Extended)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), changes have been made to the reduction of the
depreciation simulation basis for planned investments to be capitalized in project structure planning for
depreciation forecasts and primary cost planning.
Previously, capitalization postings were only included for WBS elements with depreciation simulation
data. Now however, the depreciation simulation basis of a WBS element is also transferred using
capitalization postings to hierarchically subordinate WBS elements without their own depreciation
simulation data.
Internal orders without depreciation simulation parameters, which are assigned to WBS elements, are
treated in the same way as WBS elements without depreciation simulation parameters.
This increases the accuracy of the depreciation forecast (reports RASIMU01/RASIMU02) and primary
cost planning (reports RAKOPL01/RAKOPL02).
If no hierarchically subordinate WBS element has depreciation simulation data, the actual values are
displayed during maintenance of depreciation basis data.
______________________________________________________________
SAP AG
189
SAP System
______________________________________________________________
9 EC
Enterprise Controlling
9.1 EC-PCA
Profit Center Accounting
9.1.1 Archive Connection for Line Item Reports (New)
Use
Evaluating Line Items
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the line item reports "Profit Center: Actual Line
Items" (transaction KE5Z, program RCOPCA02) and "Profit Center: Plan Line Items" (transaction
KE5Y, program RCOPCA08) can read from the database and from the archive.
The archive can be accessed either via the Archive Information System (SAP AS) or by manual file
selection. You make these settings by choosing Extras -> Data Source on the selection screen.
If you use SAP AS to access the archive, it is of no relevance whether the data was archived with object
PCA_OBJECT or EC_PCA_ITM,
Calling up Line Items from Report Writer/Report Painter Reports
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), all line items belonging to the totals record will be
displayed provided that you have assigned a variant to the line item report in the report/report interface,
selected "archive" under "data source" and "database" for this variant and activated "Use Info System".
Provided that corresponding SAP AS info structures exist, it is of no relevance whether the data was
archived with object PCA_OBJECT or EC_PCA_ITM,
All line items belonging to the totals record are displayed, provided that no variant is assigned to the line
item report in the report/report interface, but automatic archive access is activated for this area in table
ASACCESS01.
Provided that you have chosen the data source "Archive" with "Select Files Manually" in the variant
assigned via the report/report interface, only line items from certain archived files (and the database) will
be displayed.
See also
For further information on evaluating archived profit center data, see the info for archiving object
EC_PCA_ITM. To see this info, call up transaction SARA and choose Goto -> Info.
To read further information on the Archive Information System (SAP AS), see the SAP Library, under
Cross-Application Components -> Application Data Archiving (CA-ARC) -> Introduction to Data
Archiving (CA-ARC) -> Archive Information System (SAP-AS).
9.1.2 Displaying Linked Documents for Line Items (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can display all documents (origin documents
and subsequent documents) linked to actual line item documents in the profit center. You can use the
______________________________________________________________
SAP AG
190
SAP System
______________________________________________________________
Document Relationship Browser (DRB) for this purpose. Using the DRB, you can display all documents
belonging to a business transaction or a process chaing.
To access the Document Relationship Browser and to display linked documents, choose Extras ->
Relationship Browser.
See also
For further information on the Document Relationship Browser, see the SAP Library under
mySAP-Technology Components -> SAP Web Application Server -> Basis Services / Communikation
Interface (BC-SRV) -> Business Workplace and Services (BC-SRV-OFC) -> Document Relationship
Browser.
9.1.3 EC-PCA-IS
Information System
9.1.3.1 DRB (Enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , the Document Relationship Browser (DRB)
offers an extended selection of object types. Object types have been added to the DRB, and object types
that were already connected in earlier releases have been completed.
New object types:
o
Profit center document
o
Costing-based profitability analysis
o
Electronic account statement
o
Production order
o
Backflush document
The connection of these object types only affects the functions within the DRB. There are no separate
access programs.
Enhanced object types:
o
Accounting document
From the document display (transaction FB03), you can branch to the DRB. You can use report
RDRBFI00 to access the DRB and to find archived accounting documents via the archive
information system (SAP AS).
o
Controlling document
From the line item reports (for example, transaction KSB1, KSB5, KOB1), you can branch to the
DRB.
The DRB functions can find Controlling documents in the archives of all archiving objects that
archive Controlling line items. There are several field catalogs and info structures for this.
See also
______________________________________________________________
SAP AG
191
SAP System
______________________________________________________________
For more information about the Document Relationship Browser, see the SAP note 492938.
______________________________________________________________
SAP AG
192
SAP System
______________________________________________________________
10 RE
Real Estate Management
10.1 RE-RT
Rental
10.1.1 RE-RT-RA
Rental Accounting
10.1.1.1 Performance Dunning Program
Use
Previously the dunning program selected all the items in the customer account but only actually dunned
"dunnable" items. In particular, a large number of advance postings were selected (K items), but these
were not actually dunned. You can now exclude these from the selection by excluding the respective
reconciliation accounts from the selection.
10.2 RE-PR
Real Estate General Contract
10.2.1 Accrual/deferral for general contracts
Use
Accrual / deferral of flow records of the Real Estate General Contract is possible.
You will find this function:
Real Estate Management -> Real estate general contract -> Postings -> Accrual / deferral
Transactions: FOABG Accrual/deferral runs; F01T Reversal of accrual/deferral runs
Effects on Customizing
Set existing flow types as relevant for accrual/deferral. Create new reference flow types. The relationship
keys 5,6,7 and 8 are used. Maintain the account determination for the accrual /deferral postings.
10.2.2 Index adjustment for Real Estate general contracts
Use
Index adjustment of the Real Estate General Contract is possible.
You will find this function:
______________________________________________________________
SAP AG
193
SAP System
______________________________________________________________
Real Estate Management -> Real estate general contract -> Processes -> Index -> Rent Adjustment Forecast of Future Rent Payments
Transactions: FOMAFCC Index-linked Contract Forecast
10.2.3 Returned debit memos - Statistics
Use
Statistics for returned debit memos from electronic account statement are possible.
You will find this function:
Real Estate Management -> Rental accounting -> Incoming payments/account maintenance -> Account
statements -> Returned debit memos
Transaction: FORALSR Returned debit memos - Statistics
10.3 RE-FX
Flexible Real Estate Management
10.3.1 New in Flexibe Real Estate Management
Use
In SAP R/3 Enterprise Financials Extension 1.10 (EA_APPL 110) the Flexible Real Estate Management
component provides the following additional functions that were not available in mySAP Financials Real
Estate, Release 4.6C and earlier Releases:
o
Flexible definition of spaces as rental objects
o
Display of architectural structure and link to CAD systems
o
Contract management (one contract maps lease-out, lease-in as well general customer and vendor
contracts)
o
Correspondence with SAP technology Smart Forms (as well as correspondence with Microsoft
Word)
Effects on Data Transfer
The Flexible Real Estate Management component is used in conjuction with the Financial Accounting
und Plant Maintenance components.
______________________________________________________________
SAP AG
194
SAP System
______________________________________________________________
Effects on System Administration
To be able to transfer data from the Financial Accounting and Plant Maintenance components, you have
to enable the data transfer.To do this, make the necessary settings in Customizing for Flexible Real Estate
Management in the Accounting System Integration, PM Link: Settings per Architectural Object Type and
PM Link: Settings per Object Type sections.
Effects on Customizing
To use the Flexible Real Estate Management component, you have to implement a wide range of
Customizing settings. You make these settings in the task level menu of Flexible Real Estate
Management -> Customizing (transaction RECACUST).
See also
For detailed information on the Flexible Real Estate Management component, refer to SAP Library
under the heading Financial Accounting -> Flexible Real Estate Management.
10.3.2 Accessibility: Flexible Real Estate Management
Use
The following applies to accessibility of the SAP System in the area of Flexible Real Estate management:
To make the application accessible, set the user-specific parameter RECALOCATOROFF to 'X'. To do
so, choose the menu path
System -> User Profile -> Own Data -> Parameters.
To call new objects in master data dialogs, choose @2Q@ Process Object.
See also
For general information about the accessibility of the SAP System, see the SAP Library -> Getting
Started: Accessibility Supplement.
______________________________________________________________
SAP AG
195
SAP System
______________________________________________________________
11 LO
Logistics - General
11.1 Country Version India in Standard R/3 System
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), Country Version India is no longer delivered as
an add-on but as part of the standard R/3 System.
Integration of functions in the SAP Easy Access menu
The functions for withholding tax have been integrated into the SAP Easy Access menu, under
Accounting -> Financial Accounting -> Accounts Payable -> Withholding Tax -> India and
Accounting -> Financial Accounting -> Accounts Receivable -> Withholding Tax -> India.
You can access all other functions using the area menu J1ILN, which you can call from the SAP Easy
Access screen using the transaction code J1ILN.
Country Version India Implementation Guide
The Country Version India Implementation Guide (IMG) has been integrated into the standard Reference
IMG (see Changes to Structures for Country Version India).
Release Notes
You can access release notes from previous add-on releases using the links below.
SAP Library Documentation
The SAP Library documentation for Country Version India is also delivered on the standard SAP Library
documentation CD (see below).
New and Changed Functions
For information about new and changed functions for Country Version India, see the other release notes
for this release.
Effects on Existing Data
You do not need to change any data.
Effects on Customizing
IMG activity
What to do
Activate Country Version India for Specific Fiscal Years Delete the entry ZIND and create a new
entry for IND.
See also
SAP Library -> Financials or Logistics -> Country Versions -> Asia-Pacific -> India.
Release Notes from Country Version India Add-On (FI)
Release Notes from Country Version India Add-On (SD)
Release Notes from Country Version India Add-On (MM)
______________________________________________________________
SAP AG
196
SAP System
______________________________________________________________
11.2 Changes to Structures for Country Version India
Use
As of SAP R/3 4.7, Country Version India is no longer delivered as an add-on, but forms part of the
standard system.
SAP has discontinued the Country Version India Implementation Guide (IMG) and has added its
activities have been added to the standard Reference IMG as follows:
Activities relating to withholding tax are now located in Customizing for Financial Accounting (FI),
under Financial Accounting Global Settings -> Withholding Tax.
Activities relating to excise duty and excise invoices are in Customizing for Logistics - General, under
Tax on Goods Movements -> India.
As far as the activities under Preparatory Activities are concerned, two of them (Activate Country
Version India for Accounting Interface and Activate Processes) are no longer relevant and have been
removed from the IMG entirely. The activity Execute Country Installation Program is already included in
the standard IMG under the name Localize Sample Organizational Units. And the other two activities
(Activate Country Version India for Specific Fiscal Years and Activate Business Transaction Events)
have been added to the standard IMG.
For information about other changes to the IMG relating to changes in the functions in Country Version
India, see the other release notes.
11.3 Exports Under Excise Regulations (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), Country Version India allows you to process
exports and deemed exports under excise regulations. New functions for exports have been added as
follows:
o
You can create, change, display, and cancel excise bonds. When the bond is no longer of use, you
can also close it.
o
There are various transactions for creating and processing ARE-1s.
o
Reports include two statutory reports, the Running Bond Report and the Export Report.
o
To track bonds we have provided a Bond Summary Report. Another transaction, the ARE
Document Ageing Analysis, allows you to track ARE documents according to their current status.
The following new functions are also offered for deemed exports:
o
You can capture, change, display, cancel, and close licenses.
o
There are various transactions for creating and processing ARE-3s.
______________________________________________________________
SAP AG
197
SAP System
______________________________________________________________
o
To track licenses, you can use the License Summary Report; and to track ARE-3s, use the ARE
Document Aging Analysis.
Finally, SAP has also provided a new role containing all excise bonding activities, Bonding Clerk
(technical name: SAP_CIN_BONDING_CLERK).
Effects on Customizing
To set up the solution, carry out the following IMG activities:
IMG activity
What to do
Make Settings for ARE-1 Procedure
Make the basic settings for processing exports.
Make Settings for ARE-3 Procedure
Make the basic settings for processing deemed
exports.
Maintain License Types
Maintain the various license types for when you come
to enter your customers' deemed export licenses.
Maintain Output Type
Check the output type supplied with the SAP System.
Specify Printers
Specify which printers to print out the ARE
documents on.
Maintain Postal Addresses
Enter the addresses of your local excise departments,
to be printed on the AREs.
Maintain Excise Groups
Enter each excise group's local excise department.
Maintain Series Groups
Enter a default customs department for each series
group.
Maintain Number Ranges
Maintain number ranges for bonds (number range
J_1IBOND), ARE-1s (J_1IARE1), licenses (J_1ILIC), and ARE-3s (J_1IARE3).
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Sales and Distribution
(SD) -> Exports Under Excise Regulations.
11.4 New functions in the High Performance Retailing (HPR) project
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), there is a range of functions available for
improving performance. These functions were developed as part of the HPR project and have now
become part of the standard delivery.
Here is a list of the areas in which the system has new functional enhancements. For further details, see
the release information for the specific areas:
o
Multi-Step Replenishment
o
Parallel Processing
o
Collective Purchase Order
______________________________________________________________
SAP AG
198
SAP System
______________________________________________________________
o
Assortment List
o
Investment Buying
o
Promotion Discounts
o
ALE Change Pointer
o
Change Pointers for Condition Records (WIND)
o
POS Outbound
11.5 LO-MD
Logistics Basic Data
11.5.1 Structural Changes in PLM-LDM
Use
o
In the IMG of Logistics General, the structure Product Data Replication was placed at the same
level as Configuration Management.
o
In the IMG of Cross-Application Components, CAD Desktop was arranged under CAD
Integration.
11.5.2 CAD desktop
Use
From SAP R/3 Enterprise PLM Extension 1.10 (EA_APPL 110) there is an interface for CAD
integration available with the CAD desktop.
CAD structures are displayed in the CAD desktop in a fully-configurable interface, which allows you to
display and manage a variety of document information stored in the SAP system, such as person
responsible, status, and material links, all in the form of display variants.
The CAD desktop is a tool for the creation and processing of document structures directly from the CAD
system. It supports various CAD systems (Pro/ENGINEER, CATIA, Inventor, others in development).
The interfaces are developed by partner firms and offered by SAP. The support of concurrent engineering
and versioning enables simultaneous processing (for example, of an assembly) by multiple users, where
the different processing statuses can be saved in the system.
The CAD desktop is called from a CAD system via SAP direct integration. You can easily manage
assemblies engineered in the CAD system from the comfort of the CAD desktop. You can choose from
the following views:
o
SAP view
o
CAD view
o
CAD worklist
______________________________________________________________
SAP AG
199
SAP System
______________________________________________________________
o
CAD working directory
The SAP system ensures consistent datasets and reduced idle time during the editing process, thanks to
conflict solution mechanisms and checking mechanisms.
Versioning in the CAD desktop allows you to save changed originals as new versions, without
overwriting the source version of the original application file. You can display or change the last-released
version of an original or a document info record.
Status management allows you with status networks (defined in Customizing) to also set different
statuses in the CAD desktop for your document info records, and to comply with predefined processing
sequences.
Effects on Customizing
CAD Desktop
11.5.3
11.5.4 LO-MD-PL
Plant Master
11.5.4.1 Multiple Assignment of Assortments to Sites/New Store Openings
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-Retail 110), you can now choose whether to have an n:m
assignment of sites to assortments. That is, a site may have several different assortments, and an
assortment may be assigned to several different sites, thus circumventing the old 1:1 assignment
restriction. This function is similar to the multiple assignment of customers to assortments, which already
exists. Because articles are listed for assortments (not for sites), the listing conditions that are created are
valid for all the sites assigned to this assortment. This results in much easier maintenance of assortment
data, a significant reduction in the number of listing conditions that need to be stored in the database, and
better system performance.
When a site is created, the system automatically creates a local, site-specific assortment for it.
o
With the old 1:1 assignment restriction, each site has exactly one local assortment and cannot be
assigned to any other assortments.
o
With the new n:m assignment , each site still has exactly one local assortment, but can can be
assigned to as many other assortments as desired.
This function is particularly relevant for new store openings. Large retailers and retailers in a high-growth
period may open, on average, a new store every other day or even more frequently. The store opening
process is critical because it can be the first impression a retail chain makes in a new market. Therefore
this process requires simple and efficient maintenance, including the setup of the new store's master data
as well as its initial ordering.
To streamline this process, you can divide stores into logical groups, based on criteria you choose: for
example, geographical location, size, or demographics. For each group you create, you can (optionally)
select one store as a reference site for the group. When you open a new store and add it to that group, it
______________________________________________________________
SAP AG
200
SAP System
______________________________________________________________
automatically inherits all the master data (including assortment data) defined in the reference site.
Essentially you create a pointer from the new store to the reference site. Whenever data in the reference
site changes, it is automatically transferred to all stores within the group. A site cannot have more than
one reference site.
There is a new transaction for maintaining assignments of assortiments and sites. The screen is divided
into the following areas:
o
Area for selecting assortments
o
A tree structure showing assortments and the stores to which they are assigned
o
A tree structure showing available sites
This provides a overview of the current assignments so you can better choose which additional
assignments to make.
Exclusion modules are normally used for local assortments, enabling you to create exceptions for certain
articles and for subsequent listings. You can use exclusion modules for general assortments as well.
As before, an assortiment can be assigned to only one distribution chain.
Effects on Customizing
In Customizing for General Control, Retail Master Data, you can decide whether you want to enable the
new n:m assignment of sites to assortments, or the previous 1:1 restriction. To enable multiple
assignment, select the Multiple Assignment is Active flag.
IMPORTANT: Once you set this flag in the productive system, you can no longer switch back to the old
1:1 assignment restriction.
SAP provides programs for customers upgrading from an older release of R/3 Enterprise and wishing to
implement the new n:m assignment .
See also
Assortment List
11.5.4.2 Mass Maintenance of Master Data
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-Retail 110), the mass maintenance tool has been enhanced
to include:
o
Vendor master data
o
Purchasing info records
o
Logistics and replenishment data
o
Purchase orders
This mass maintenance tool focuses on four main aspects. First, it provides a user-friendly interface to
execute data maintenance. Second, it provides a tool that can be easily adapted to handle new types of
mass maintenance. Third, it improves performance. It uses parallelism to accelerate saving a mass
______________________________________________________________
SAP AG
201
SAP System
______________________________________________________________
maintenance session and, in the case of logistics data, uses high performance updating optimized for
retail. Finally, the tool provides an error recovery functionality that allows for the recovery and
reprocessing of errors that occurred during the save process.
o
Common properties
All the mass maintenance tools are based on the same basic framework and user interface. The
features of this interface include:
-
You can define the scope of data in a selection area using standard selection criteria or defining
your own.
-
You can use the navigation tree to drill down along the objects hierarchy (for example, by
Purchasing Organization -- Vendor -- Site in the info record mass maintenance).
-
You can display and maintain each entry easily in the maintenance grid.
-
You can search for entries within the navigation tree.
-
You can mass update and clear entries within the maintenance grid.
-
You can apply formulas to fields in the grid.
-
You can filter records from the maintenance grid.
-
You can use an integrated error recovery tool that lists errors and allows you to correct them on
the fly.
-
You can view and manage data at the reference site level in the vendor/site, purchasing info
record, and logistics/replenishment mass maintenance tools.
-
You can check for common errors before saving the data.
-
User exits are provided to update your own custom fields and perform checks for your specific
business rules
NOTE: Some fields required by customers for updating are not available due to technical reasons.
These fields are: UPC/EAN, Commodity code, and Quantity. SAP hopes to address these in a
future release.
o
Vendor/site master data
You can now use vendor/site records in an optional form of source determination that will be
delivered in a user exit. You can take advantage of the purchasing reference site functionality to
group stores with similar sourcing requirements rather than maintaining every site individually.
Because this increases the importance of vendor/site records, you can mass maintain these records
using this tool. It provides visibility into purchasing reference sites by displaying the data the
dependent sites adopted from the purchasing reference site.
o
Purchasing info record master data
Purchasing reference sites can also be used with purchasing info records. You can set up purchasing
info records for a purchasing reference site if there is data that differs from site to site. This allows
you to avoid using site-specific purchasing info records.
The purchasing info record mass maintenance tool can be used to maintain purchasing info records
______________________________________________________________
SAP AG
202
SAP System
______________________________________________________________
generally and also simulates the impact purchasing reference site changes have on their dependent
sites.
o
Logistics/replenishment master data
Logistics reference sites are available to improve the management of article/site logistics master
data. This mass maintenance tool is designed to update logistics, replenishment, and forecasting
parameters for articles at distribution centers and stores. .
It uses the same general framework as the others and also allows you to maintain data at logistics
reference store level while copying it automatically to the dependent sites. This new copy logic is
only used when standard reference handling is turned off for the changed field and when the
dependent site entry is the same as the reference site entry.
The performance of logistics/replenishment data updating has been significantly improved.
o
Purchase orders
Purchasing in high volumes requires retailers to have the ability to make a large number of changes
to existing purchase orders. Using the new purchase order maintenance transaction, you can make
mass changes to PO headers, line items, and schedule lines. This transaction has the same usability
features described in the common properties section.
The standard selection fields available are: Purchase organization, Purchasing group, Document
type, Vendor, Supplying site, Article, Receiving site, Delivery complete indicator, Delivery date. In
addition, you can specify your own selection fields using dynamic selection criteria.
The fields available for updating are: Inco terms, Payment terms, Vendor article number, Delivery
date, Delivery complete indicator, Deletion indicator, Season category, and Season year.
NOTE: Purchase order mass maintenance covers only those purchase orders having a status of
released, released with partial deliveries, and unreleased.
11.5.5 LO-MD-MM
Material Master
11.5.5.1
11.5.5.2 Customer, Vendor, and Material Master Data (Changed)
Use
As of SAP R/3 Enterprise Core Release 4.70 (SAP_APPL 470), you can maintain customer, vendor, and
material master data relating to excise duty for Country Version India in the standard master data
transactions.
______________________________________________________________
SAP AG
203
SAP System
______________________________________________________________
You can therefore now maintain this data in the Excise Rate Maintenance transaction or in the master
record transactions.
You can maintain the data in the standard master record transactions as follows:
o
In the customer master and vendor master, you access the additional fields by choosing CIN
Details. This button is available from all screens in the master records.
o
In the material master, the additional fields are displayed at plant level, on the Foreign Trade:
Import Data tab and the Foreign Trade: Export Data tab, in the Excise Data group box.
Effects on Existing Data
The system displays data from releases prior to 4.70 in the standard transactions automatically (but see
Customizing below). The data is still stored in the same tables, so there is no need to migrate it.
Effects on Customizing
In order for the Excise Data group box to appear in the material master, carry out the IMG activity
Assign Users to Material Master Screen Sequence for Excise Duty.
11.5.5.3 Material Variant Distribution (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can send the values assigned during
configuration in the material master IDocs when distributing material variants. You can send the values
in the following ways:
o
Send material variants using ALE
ALE -> Master Data Distribution -> Cross Application -> Material -> Send
o
Send with change pointers
If you have changed the values assigned during configuration for a material variant and have
activated the generation of change pointers for message type MATMAS while creating or changing
a material in dialog processing, the system generates a change pointer.
When posting configuration data, there are rules in the target system to which you must adhere.
o
The system runs checks in the target system in the background based on dependencies, and only
posts the data if the configuration is consistent and complete.
o
The configuration profile is only transported with the IDoc for information purposes. It is not
posted. The system compares the configuration profile in the IDoc in the source system with the
existing profile in the target system. The material is only posted if these profiles have the same
scenario and name.
o
You can decrease or deactivate the consistency checks using three different modification functions.
For more information, see the documentation on the function module
CUXM_SET_CONFIGURATION.
When sending configuration data, note the following restrictions:
o
Retail configurations cannot be transferred.
______________________________________________________________
SAP AG
204
SAP System
______________________________________________________________
o
Multilevel configurations of material variants cannot be transported (if you are using the customer
exit in note 211898).
o
If you overwrite units of measure in the configuration, they are not transported; the system always
copies the unit of measure from the master data in the target system.
Note
o
If you have overwritten material master data in the target system using an IDoc, and there is no
configuration in the IDoc, but there is configuration available in the target system, then the
configuration remains unchanged in the target system (no deletion).
o
If you change the cross-plant material status and the distribution lock for a material is reversed, the
complete material is sent. In this case, all the configuration data is sent as well even if you have not
changed the material status in the dialog box (for example, when activating planned changes, using
IDocs and so on).
Effects on Customizing
To be able to send material variants using ALE or change pointers, you have to make the following
settings in the Customizing for the material master:
Make Global Settings
o
To send using ALE activate indicator Send When Complete.
o
To send using change pointers activate indicator When Configuration is Changed.
11.5.5.4 Prepack Allocation Planning
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), there is a new prepack allocation planning
transaction that allows you to link several prepack articles to a generic articles and define the structure of
these prepack articles. You can plan how the prepack articles are to be allocated to the stores. Allocation
tables and vendor purchase orders can be generated and kept in synchronization. You can used planned
data from Merchandise and Assortment Planning (MAP) to verify whether the allocation plan
corresponds correctly to the style plan.
The new transaction can handle generic articles that have two characteristics or fewer. The primary
characteristic should represent the size and the secondary characteristic should represent the color. The
primary and secondary characteristics are determined by the sequence defined in Customizing: Maintain
Sequence of Characteristics
For the prepacks defined within this transaction, only variants of the selected generic article can be
assigned as components. Prepack articles containing variants of different generic articles must be created
with the previously existing function.
You can define the components of a prepack article using a matrix. You enter the quantity of each
component needed to complete the prepack article. For example, Article A might include three of
Component X and two of component Y. You can also define the structure of a prepack article using quota
scales linked to the main characteristic of the generic article
You can use assortments or allocation rules to determine the stores that are to carry the articles, and
______________________________________________________________
SAP AG
205
SAP System
______________________________________________________________
assign prepacks to them. You can define delivery phases that are specific to a combination of site group
and prepack article. You can plan stock that is to be kept at the distribution center for in-season
replenishment ("putaway"). An interface to the MAP transaction provides the planned quantities for the
style by color and assortment, thus enabling the user to verify whether the allocated quantities correspond
to the planned quantities.
The component list for a prepack article can be changed, provided the settings in Customizing allow it.
New prepacks can be defined and added to the allocation; existing prepacks can be removed from the
allocation.
The prepack allocation planning transaction allows you to trigger the creation of purchase orders as
subsequent documents of the allocation table. Purchase orders will be changed automatically when
changes are made to the allocation table.
Effects on Existing Data
Existing data will not be affected
Effects on Data Transfer
Communication between an earlier SAP R/3 Release and SAP R/3 Enterprise will not run into problems.
But in SAP R/3 Enterprise, new information is available. For a prepack article created with the new
transaction, the Material Master will show the generic article to which it belongs. This information will
not be available when the data is sent to an earlier SAP R/3 Release.
Effects on System Administration
None.
11.5.5.5 Variant Handling by Characteristics
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-Retail 110), maintaining variants of a generic article has
been made quicker and easier.
Fashion retailers have to deal with styles offered in various colors and sizes. It is rarely sufficient to
perform certain functions for all the variants assigned to the style. Instead, you need to perform these
functions for a subset of variants having some attribute in common; color, for example.
In SAP R/3 Enterprise Retail, styles are mapped as generic articles with different variants. You define a
variant by specifying the characteristics and their values (for example, the characteristic color might have
value blue). This way you can select, for example, all blue shirts regardless of size
With this enhancement you can maintain a subset of variants of a generic article in which these variants
all share a common characteristic value (for example, all blue shirts). Master data can be maintained for
this group level and is copied to all variants specified in the selection. If a variant has already been
maintained differently, the group level data will not override the variant's data.
Additional features include:
o
Listing variants by characteristic
You can maintain listing data in the article master for a subset of variants defined by characteristic,
______________________________________________________________
SAP AG
206
SAP System
______________________________________________________________
and listing can be performed for the defined subsets. Thus, you can list variants by color.
o
Defining price groups for variants
Sales prices and cost for variants of a generic article often differ based on their characteristic values;
for example, white shirts might be less expensive than other colors. To make article master data
maintenance, variants are now arranged in a grid (matrix), with the price/cost price
displayed/entered in the grid cells. You can easily copy the same price/cost for a subset of variants.
o
Planning markdown for a subset of variants
Because sales can vary depending on article color, you often need to mark down a generic article
only for specific colors. In markdown planning, you can now select variants by characteristic.
Effects on Customizing
No Customizing settings are necessary.
11.5.5.6 Mass Maintenance of Master Data
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-Retail 110), the mass maintenance tool has been enhanced
to include:
o
Vendor master data
o
Purchasing info records
o
Logistics and replenishment data
o
Purchase orders
This mass maintenance tool focuses on four main aspects. First, it provides a user-friendly interface to
execute data maintenance. Second, it provides a tool that can be easily adapted to handle new types of
mass maintenance. Third, it improves performance. It uses parallelism to accelerate saving a mass
maintenance session and, in the case of logistics data, uses high performance updating optimized for
retail. Finally, the tool provides an error recovery functionality that allows for the recovery and
reprocessing of errors that occurred during the save process.
o
Common properties
All the mass maintenance tools are based on the same basic framework and user interface. The
features of this interface include:
-
You can define the scope of data in a selection area using standard selection criteria or defining
your own.
-
You can use the navigation tree to drill down along the objects hierarchy (for example, by
Purchasing Organization -- Vendor -- Site in the info record mass maintenance).
-
You can display and maintain each entry easily in the maintenance grid.
-
You can search for entries within the navigation tree.
______________________________________________________________
SAP AG
207
SAP System
______________________________________________________________
-
You can mass update and clear entries within the maintenance grid.
-
You can apply formulas to fields in the grid.
-
You can filter records from the maintenance grid.
-
You can use an integrated error recovery tool that lists errors and allows you to correct them on
the fly.
-
You can view and manage data at the reference site level in the vendor/site, purchasing info
record, and logistics/replenishment mass maintenance tools.
-
You can check for common errors before saving the data.
-
User exits are provided to update your own custom fields and perform checks for your specific
business rules
NOTE: Some fields required by customers for updating are not available due to technical reasons.
These fields are: UPC/EAN, Commodity code, and Quantity. SAP hopes to address these in a
future release.
o
Vendor/site master data
You can now use vendor/site records in an optional form of source determination that will be
delivered in a user exit. You can take advantage of the purchasing reference site functionality to
group stores with similar sourcing requirements rather than maintaining every site individually.
Because this increases the importance of vendor/site records, you can mass maintain these records
using this tool. It provides visibility into purchasing reference sites by displaying the data the
dependent sites adopted from the purchasing reference site.
o
Purchasing info record master data
Purchasing reference sites can also be used with purchasing info records. You can set up purchasing
info records for a purchasing reference site if there is data that differs from site to site. This allows
you to avoid using site-specific purchasing info records.
The purchasing info record mass maintenance tool can be used to maintain purchasing info records
generally and also simulates the impact purchasing reference site changes have on their dependent
sites.
o
Logistics/replenishment master data
Logistics reference sites are available to improve the management of article/site logistics master
data. This mass maintenance tool is designed to update logistics, replenishment, and forecasting
parameters for articles at distribution centers and stores. .
It uses the same general framework as the others and also allows you to maintain data at logistics
reference store level while copying it automatically to the dependent sites. This new copy logic is
only used when standard reference handling is turned off for the changed field and when the
dependent site entry is the same as the reference site entry.
The performance of logistics/replenishment data updating has been significantly improved.
______________________________________________________________
SAP AG
208
SAP System
______________________________________________________________
o
Purchase orders
Purchasing in high volumes requires retailers to have the ability to make a large number of changes
to existing purchase orders. Using the new purchase order maintenance transaction, you can make
mass changes to PO headers, line items, and schedule lines. This transaction has the same usability
features described in the common properties section.
The standard selection fields available are: Purchase organization, Purchasing group, Document
type, Vendor, Supplying site, Article, Receiving site, Delivery complete indicator, Delivery date. In
addition, you can specify your own selection fields using dynamic selection criteria.
The fields available for updating are: Inco terms, Payment terms, Vendor article number, Delivery
date, Delivery complete indicator, Deletion indicator, Season category, and Season year.
NOTE: Purchase order mass maintenance covers only those purchase orders having a status of
released, released with partial deliveries, and unreleased.
11.5.5.7 Calculating Planned Delivery Time
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can calculate and change planned
delivery times.
This function enables you to procure goods from your vendors more easily and, thereby, avoid
out-of-stock or overstock situations in the warehouse.
Up until now, the data had to be maintained manually for the planned delivery time in 3 different places:
o
At vendor level
o
At material level
o
At purchasing info record level.
The values that are maintained manually in these areas are, however, largely based on values gained from
experience. They would quickly become invalid if the vendor's behavior changed.
The new function allows you to:
1.
Calculate the planned delivery time.
When calculating the planned delivery time, the system determines the number of days between the
purchase order being placed with the vendor and the actual goods receipt. The system calculates this
for any combinations of vendor, plant, material, purchasing organization, and vendor subrange.
2.
Change the planned delivery time data.
This function helps you decide whether you would like to retain the planned delivery time you
entered manually or whether you would like to replace it with the planned delivery time calculated
by the system. You can make this decision for every single value in the master data for the vendor,
material and purchasing info record.
______________________________________________________________
SAP AG
209
SAP System
______________________________________________________________
Note that any change you make to the planned delivery times could affect procurement.
Important: The system calculates the planned delivery time in calendar days, not in working days.
Effects on System Administration
SAP recommends you use this function regularly.
Effects on Customizing
You do not need to make any Customizing settings.
11.5.6 LO-MD-RA
Assortment
11.5.6.1 LO-MD-RA-MT
Assortment Maintenance
11.5.6.1.1 Layout Workbench
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the new design of the Layout Workbench
provides the following enhancements:
A new entry in the layout workbench by layout modules:
This allows you to efficiently maintain layout modules within mySAP Retail. You can use mass
maintenance to assign a large number of articles to layout module versions and variants. In addition, you
can replace or delete article assignments in all or selected layout modules where the article was assigned.
You can maintain layout module variants and their assignments to assortments with this same transaction.
If you select a layout module version, all the articles belonging to this version can be listed for all or
selected assortments. From here you can also navigate to all other transactions for space management.
A new layout maintenance transaction within the Layout Workbench
The new, user-friendly layout maintenance transaction enables you to maintain layouts, the assignments
of layouts to layout modules (= layout areas), and the assignment of layouts to assortments and thus to
stores. Copy and replacement features help make working with the layout concept inside SAP Retail
much easier. In contrast to the old transaction, which was located within Customizing, this transaction
can be used in the productive system. It also automates the follow-on activities that result from changing
a layout (for example, if you delete a layout, the system automatically deletes all assignments for that
layout).
11.5.6.1.2 Multiple Assignment of Assortments to Sites/New Store Openings
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-Retail 110), you can now choose whether to have an n:m
assignment of sites to assortments. That is, a site may have several different assortments, and an
______________________________________________________________
SAP AG
210
SAP System
______________________________________________________________
assortment may be assigned to several different sites, thus circumventing the old 1:1 assignment
restriction. This function is similar to the multiple assignment of customers to assortments, which already
exists. Because articles are listed for assortments (not for sites), the listing conditions that are created are
valid for all the sites assigned to this assortment. This results in much easier maintenance of assortment
data, a significant reduction in the number of listing conditions that need to be stored in the database, and
better system performance.
When a site is created, the system automatically creates a local, site-specific assortment for it.
o
With the old 1:1 assignment restriction, each site has exactly one local assortment and cannot be
assigned to any other assortments.
o
With the new n:m assignment , each site still has exactly one local assortment, but can can be
assigned to as many other assortments as desired.
This function is particularly relevant for new store openings. Large retailers and retailers in a high-growth
period may open, on average, a new store every other day or even more frequently. The store opening
process is critical because it can be the first impression a retail chain makes in a new market. Therefore
this process requires simple and efficient maintenance, including the setup of the new store's master data
as well as its initial ordering.
To streamline this process, you can divide stores into logical groups, based on criteria you choose: for
example, geographical location, size, or demographics. For each group you create, you can (optionally)
select one store as a reference site for the group. When you open a new store and add it to that group, it
automatically inherits all the master data (including assortment data) defined in the reference site.
Essentially you create a pointer from the new store to the reference site. Whenever data in the reference
site changes, it is automatically transferred to all stores within the group. A site cannot have more than
one reference site.
There is a new transaction for maintaining assignments of assortiments and sites. The screen is divided
into the following areas:
o
Area for selecting assortments
o
A tree structure showing assortments and the stores to which they are assigned
o
A tree structure showing available sites
This provides a overview of the current assignments so you can better choose which additional
assignments to make.
Exclusion modules are normally used for local assortments, enabling you to create exceptions for certain
articles and for subsequent listings. You can use exclusion modules for general assortments as well.
As before, an assortiment can be assigned to only one distribution chain.
Effects on Customizing
In Customizing for General Control, Retail Master Data, you can decide whether you want to enable the
new n:m assignment of sites to assortments, or the previous 1:1 restriction. To enable multiple
assignment, select the Multiple Assignment is Active flag.
IMPORTANT: Once you set this flag in the productive system, you can no longer switch back to the old
1:1 assignment restriction.
SAP provides programs for customers upgrading from an older release of R/3 Enterprise and wishing to
implement the new n:m assignment .
______________________________________________________________
SAP AG
211
SAP System
______________________________________________________________
See also
Assortment List
11.5.6.2 LO-MD-RA-ASL
Assortment List
11.5.6.2.1 POS Outbound Reports for Assortment Lists
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), there is a central group report that you can
run to analyze data for generating assortment lists via POS outbound processing. It comprises several
individual reports. If you execute the central group, it runs all the associated reports for a full analysis.
Alternatively, you can run the individual reports independently or in any combination you desire.
You can select reports from an online transaction. No Customizing changes are necessary.
The individual reports are:
o
Object Analysis
This report checks the IDoc types to be exported via POS outbound processing and determines
whether the program will encounter any errors. You can target this report to specific sites and/or
articles.
o
Reorganization Check for Assortment Lists
If the RWDPOSRS fails to complete a reorganization run for some reason, you can run this
troubleshooting report to determine possible causes.
o
Dummy Initialization for Assortment Lists
Initializing assortment data for a new store can be time-consuming since so much data is involved.
However, the previously existing analysis report could only be run after the initialization run takes
place. Troubleshooting the data before actually performing the initialization can save time by
uncovering possible problems. To meet this need, the dummy initialization report simulates an
initialization run and analyzes the results so that you can address any problems. This helps ensure
that you will have a clean initialization run.
No data is actually sent or processed by the dummy initialization report.
o
IDoc Analysis for Assortment Lists
It often happens that you need to find a specific object among thousands of IDocs. This report
provides a quick and easy way to search for such an object. (See also transaction WE09.)
o
Change Pointer Deletion
Standard ALE report RBDCPCLR enables you to delete change pointers, but it does not provide any
______________________________________________________________
SAP AG
212
SAP System
______________________________________________________________
suitable navigation features for retail. This new report interfaces with RBDCPCLR to make it easier
to use for the retail area.
o
Reorganization
Similar to the Change Pointer Deletion report above, this report interfaces with report RWDPOSRS
to make it easier to use for the retail area.
o
Reprocess Handling
When troubleshooting, you need to be able to reproduce errors so you can determine how to fix
them. This report allows you to do a test rerun using the same change pointers that were handled in
the previous download. However, there is usually some time delay (perhaps a few days) between the
POS run and the analysis, during which time the system may detect new change pointers. This may
cause the reprocessing report to include more articles than the original download. This new data is
in addition to all the previous data. None of the previous data will be omitted.
NOTE: This report will not work if the change pointers were already deleted after the previous run.
11.5.6.2.2 Assortment List
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), there are four additional reports for
generating assortment lists.
Previously, there were only three reports for generating assortment lists. In Customizing, you could
specify that assortment lists be generated both in electronic form (IDocs) and report form (for display
and/or printing).
The first three new reports correspond to the three old reports and contain most of the same data, but they
now allow you to split the print version run from the IDoc run. This provides a significant increase in
throughput speed. You still get IDocs automatically, but you can choose whether or not you want to
generate the report as well. You can even decide to generate a print version several days after generating
the IDocs, perhaps at a time when system processing demands are light. To generate the print version,
you run the fourth report (RWBBVCRE_HPR).
Function
New Transaction
Full version (initial)
WDBI_HPR
Change version
WDBU_HPR
Manual request
WDBM_HPR
Create print from IDoc
Old Report
Old Transaction
RWDBBINI
WDBI
RWBBINI_HPR
RWDBBUPD
WDBU
RWDBBUPD_HPR
RWDBBMAN
WDBM
RWDBBMAN_HPR
--
RWBBVCRE_HPR
--
New Report
______________________________________________________________
SAP AG
213
SAP System
______________________________________________________________
WBBV_HPR
You can still use the old reports if you wish - all seven reports appear on the assortment list menu. The
selection screens are generally the same except for a few new fields.
The following requirements apply:
o
If you are using the new reports, all stores for which you want to generate assortment lists must
belong to the same distribution chain. If you want to include stores in three different distribution
chains, for example, you must open three separate sessions and run one report in each screen. This
improves efficiency by restricting analysis of change pointers to a given distribution chain. There is
much less data through which the system has to search.
o
For performance reasons, all stores within a report run must use the same IDoc reduction settings in
the assortment list profile.
o
The new reports contain most -- but not all -- of the same master data as the old reports. This is
sufficient for most customers. However, if you require this missing data (specifically: classification
data, old labeling data, and layout module versions for space management), you must implement a
user exit to include this additional data.
Effects on System Administration
You must run a migration report (RWDBBMIG) once only, prior to using the new change version report.
The migration report builds the conditions index (database table WIND) from the change pointers for the
assortment list, along with performing other necessary data conversions. (For more information on the
WIND table, see the documentation in transaction MEI4.)
Effects on Customizing
For more Customizing information, see Business Add-Ins.
11.5.6.2.3 New Change Pointers for Condition Records (WIND)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you have the following additional options for
adjusting documents in condition changes:
o
Direct entries in the worklist after condition changes
o
Including additional data in an entry in the worklist
In the previous procedure, the entries were created in the worklist based on the change pointers for
condition changes (message type CONDBI) in worklist creation (transaction ME14). In the new
procedure, the change pointers are no longer needed. When a condition is changed, entries are created
directly in the worklist. This removes the previous step in the process of creating the worklist from
change pointers, which was very performance-intensive. In addition, you do not have to create change
pointers for condition changes if they are not going to be used in other processes.
The Customizing that was valid for the previous worklist creation and that defines which condition types
should be included in the worklist (table T6I1) is also valid for the direct entry. However, there are
______________________________________________________________
SAP AG
214
SAP System
______________________________________________________________
additional filter options in the new procedure. You can define for each document category for which
types of condition changes (amount change, validity, pricing relevance) entries should be made in the
worklist. There is also a BAdI that is dependent on the document category filter criterion with which
customer-defined filter criteria can be implemented.
The following example describes the options offered by the BAdI:
Due to changing purchasing conditions, perishable materials are regularly repriced in short time periods.
Therefore, sales prices do not need to be updated using the pricing worklist procedure. Use the material
type, in this case, as an additional filter criterion in the retail pricing application (document category 10).
When the basic purchase price of a perishable material is changed, the system does not create a worklist
entry for this document category due to the filter criterion that was implemented.
The additional data in a worklist entry consists of header data from the conditions with which you can
improve performance for the follow-on processing and of variable customer fields with which you can
carry out selective subsequent processing. You make settings in Customizing for filling the customer
fields (table T6I2S).
Effects on Existing Data
If you do not use change pointers for condition changes, the level of data for change pointers is reduced
considerably. A change pointer generally consists of several entries in table BDCP and BDCP2.
The following changes are made:
o
The width of table WIND increases from 45 to 262 bytes due to the additional tables.
o
The number of table entries in the worklist can be reduced due to the additional filter criteria.
o
Change pointers are no longer needed for message type CONDBI.
Effects on System Administration
The process step for creating the worklist from change pointers (transaction ME14) is no longer needed in
the new procedure.
The check for existing document indexes (table S111) that can be used in the previous worklist creation
must be implemented as an additional filter criterion in the BAdI (see example coding).
The migration of the worklist from the old to the new worklist entries is carried out using report
RMEBEMIG. The report enhances the entries that are available using information from the condition
records.
If you are converting from the old to the new procedure, a special adjustment procedure is required for
every document category. This procedure is described in each of the applications that use the new
procedure.
Effects on Customizing
Implement the new Customizing for the direct creation of worklist entries. If you are installing this for
the first time or if you have not yet used the document adjustment function for a certain document
category, set the indicator manually for migration and direct entry in Customizing. When converting from
the old to the new procedure, the indicators in the migration procedure are set automatically.
You also determine the types of condition changes for each document category as filter criteria for which
worklist entries should be created and how the variables should be filled.
Once you have made settings for direct entries in the worklist for all the document categories used, you
______________________________________________________________
SAP AG
215
SAP System
______________________________________________________________
do not have to create change pointers from message type CONDBI. Deactivate message type CONDBI in
ALE Customizing.
You can also carry out this deactivation using the migration report.
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Master Data -> Conditions ->Automatic Updating of Documents After Condition Changes.
11.5.7 LO-MD-BP
Business Partners
11.5.7.1 Customer-Specific Fields in Business Partner Master Data (New)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , you can define additional data in the master data
of your customers and vendors. To do this, you develop subscreens to which you add the required fields.
You can access your subscreens in the master records of the business partner via integrated buttons; there,
your screens are integrated on a tab page. You can assign up to 32 tab pages/subscreens to each button.
With a change of release, upgrade, or a support package, you copy your own subscreens and data and the
relevant tables without having to make any modifications.
Effects on Customizing
In the Implementation Guide for Financial Accounting or Logistics, make the following settings:
Financial Accounting
1.
Choose Accounts Payable/Accounts Receivable Accounting -> Customer Accounts or Vendor
Accounts -> Master Data -> Transfer Customer Master Data Fields -> Prepare Modification-Free
Enhancement in Customer Master or Vendor Master and make the relevant settings for defining
your subscreens.
2.
To connect your subscreens and data to the standard application, use the following BADIs:
-
Business Add-In: Processing Master Data Enhancements
-
Business Add-In: Customer Subscreens
-
Business Add-In: Processing Master Data Enhancements with Batch Input
General Logistics
1.
Choose Business Partner -> Customer or Vendor -> Control -> Copy Customer Master Data Fields
-> Prepare Modification-Free Enhancement of Vendor or Customer Master Record, and make the
relevant settings for defining your subscreens.
2.
To connect your subscreens and data to the standard application, use the following BADIs:
-
Business Add-In: Processing Master Data Enhancements
-
Business Add-In: Customer Subscreens
______________________________________________________________
SAP AG
216
SAP System
______________________________________________________________
-
Business Add-In: Processing Master Data Enhancements with Batch Input
See also
For more information, see the respective Customizing activity and the documentation for the individual
BADIs.
11.5.7.2 LO-MD-BP-CM
Customer Master
11.5.7.2.1 Customer, Vendor, and Material Master Data (Changed)
Use
As of SAP R/3 Enterprise Core Release 4.70 (SAP_APPL 470), you can maintain customer, vendor, and
material master data relating to excise duty for Country Version India in the standard master data
transactions.
You can therefore now maintain this data in the Excise Rate Maintenance transaction or in the master
record transactions.
You can maintain the data in the standard master record transactions as follows:
o
In the customer master and vendor master, you access the additional fields by choosing CIN
Details. This button is available from all screens in the master records.
o
In the material master, the additional fields are displayed at plant level, on the Foreign Trade:
Import Data tab and the Foreign Trade: Export Data tab, in the Excise Data group box.
Effects on Existing Data
The system displays data from releases prior to 4.70 in the standard transactions automatically (but see
Customizing below). The data is still stored in the same tables, so there is no need to migrate it.
Effects on Customizing
In order for the Excise Data group box to appear in the material master, carry out the IMG activity
Assign Users to Material Master Screen Sequence for Excise Duty.
11.5.7.3 LO-MD-BP-VM
Vendor Master
11.5.7.3.1 Customer, Vendor, and Material Master Data (Changed)
Use
As of SAP R/3 Enterprise Core Release 4.70 (SAP_APPL 470), you can maintain customer, vendor, and
material master data relating to excise duty for Country Version India in the standard master data
transactions.
You can therefore now maintain this data in the Excise Rate Maintenance transaction or in the master
______________________________________________________________
SAP AG
217
SAP System
______________________________________________________________
record transactions.
You can maintain the data in the standard master record transactions as follows:
o
In the customer master and vendor master, you access the additional fields by choosing CIN
Details. This button is available from all screens in the master records.
o
In the material master, the additional fields are displayed at plant level, on the Foreign Trade:
Import Data tab and the Foreign Trade: Export Data tab, in the Excise Data group box.
Effects on Existing Data
The system displays data from releases prior to 4.70 in the standard transactions automatically (but see
Customizing below). The data is still stored in the same tables, so there is no need to migrate it.
Effects on Customizing
In order for the Excise Data group box to appear in the material master, carry out the IMG activity
Assign Users to Material Master Screen Sequence for Excise Duty.
11.5.7.3.2 Calculating Planned Delivery Time
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can calculate and change planned
delivery times.
This function enables you to procure goods from your vendors more easily and, thereby, avoid
out-of-stock or overstock situations in the warehouse.
Up until now, the data had to be maintained manually for the planned delivery time in 3 different places:
o
At vendor level
o
At material level
o
At purchasing info record level.
The values that are maintained manually in these areas are, however, largely based on values gained from
experience. They would quickly become invalid if the vendor's behavior changed.
The new function allows you to:
1.
Calculate the planned delivery time.
When calculating the planned delivery time, the system determines the number of days between the
purchase order being placed with the vendor and the actual goods receipt. The system calculates this
for any combinations of vendor, plant, material, purchasing organization, and vendor subrange.
2.
Change the planned delivery time data.
This function helps you decide whether you would like to retain the planned delivery time you
entered manually or whether you would like to replace it with the planned delivery time calculated
by the system. You can make this decision for every single value in the master data for the vendor,
material and purchasing info record.
Note that any change you make to the planned delivery times could affect procurement.
______________________________________________________________
SAP AG
218
SAP System
______________________________________________________________
Important: The system calculates the planned delivery time in calendar days, not in working days.
Effects on System Administration
SAP recommends you use this function regularly.
Effects on Customizing
You do not need to make any Customizing settings.
11.5.8 LO-MD-SN
Serial Numbers
11.5.8.1 Registration and archival of configured serial numbers (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) functional gaps in the configuration of serial
numbers (and equipment) are closed. Up to now the following limitations existed:
o
For referenced configurations (for example, the configuration of a sales document item), the
configuration master record could be mistakenly deleted (for example, by deleting the item), even
though it still needs the serial number.
o
A configured serial number cannot be archived.
Both restrictions are now highlighted by a suitable registration of configuration references.
For further information on functionality, see SAP note 486752, for example:
o
Information on the report RIXPRA10, which enables the (initial) registration of all pre-existing
configuration references.
o
Information on downgrading the functionality up to release 4.5B.
11.5.8.2 Synchronization of construction type and material number (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can use the equipment category to
control whether the construction type is kept synchronous with the material number in the master record
for serialized equipment.
Effects on Existing Data
If the system contains master records for which the construction type and material number are different,
and these numbers should be kept synchronous in the future, then you can perform the conversion report
RIEQUI_SYNC_MATNR_SUBMT. After the conversion you can set the indicator in Customizing such
that the construction type must always be the same as the material number.
Effects on Customizing
______________________________________________________________
SAP AG
219
SAP System
______________________________________________________________
In Customizing for Plant Maintenance and Customer Service, under Maintain Equipment Category,
you must set the check indicator Keep Construction Type and Material Number Synchronous.
See also
11.5.8.3 Synchronization of equipment number and serial number (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), when you create master records for
serial numbers, you can use
the material master record to control that the serial numbers and equipment numbers are kept
synchronous. To do this, you must set the indicator Serialization Level in the material master record to
1.
As the equipment number is, by definition, unique at client level, by synchronizing the serial number and
the equipment number you can make serial numbers unique material-wide. The prerequisite for thisis
that all material master records have the indicator serialization level set to 1.
See also
11.5.8.4 Functions in the serial number history (enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can use the serial number history to
track where the serial numbers were installed and removed.
The different data is displayed in the history with different colors, which are explained in the legend.
Every field in the history has a
quick info text. You can call up the action log for the history as a
dialog box.
See also
11.5.9 LO-MD-RPC
Retail Pricing
11.5.9.1 Business Add-Ins in Retail Pricing
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the following Business Add-Ins
(BAdI) in the applications sales price calculation, market-basket price calculation and the pricing worklist
______________________________________________________________
SAP AG
220
SAP System
______________________________________________________________
in Retail Pricing to fulfill special requirements in these applications:
Business Add-In SPC_SEL_CHECK: Detail selection of article/organization levels in sales price
calculation.
This BAdI acts as a filter in sales price calculation when you select organization levels or exclude certain
article/organization level combinations. You can use this BAdI, for example, to restrict pricing in
wholesale for defined distribution chain/pricelist combinations. You can also exclude articles with certain
characteristics from pricing in stores, for example, perishables if you only want sales prices at distribution
chain level to be valid for these articles.
For more information, see BAdI: Detail Selection of Mat./Org. Levels in Sales Price Calculation.
Business Add-In SPC_POSTING_CONTROL: Control for updating conditions in sales price
calculation.
This BAdI specifically controls the updating of main and additional conditions in sales price calculation.
For this, the BAdI acts like a filter for the general controls for condition updating maintained in
Customizing. For example, the sales price does not have to be updated if it is the same as the current sales
price. However, for retail pricing, in a case like this, a different margin should be saved based on the
purchasing conditions that have changed and the margin is then used in subsequent retail pricing runs.
For more information, see BAdI: Control for Condition Updating in Sales Price Calculation.
Business Add-In SPC_DOCINDEX_CONTROL: Control for Creating Document Indices in Sales
Price Calculation
This BAdI acts like a filter in sales price calculation when you update document indices for retail pricing
documents. This BAdI allows you to exclude individual document indices or indeed all of them when
performing an update. For example, you may not want to create any document indices for perishable
articles, as you do not use the pricing worklist function for these articles due to the fact that the
purchasing and sales prices often change.
For more information, see BAdI: Control for Document Index Creation in Sales Price Calculation.
Business Add-In MIXED_PP_QUANTITIES: Defaulting vendor mixed price factors in sales price
calculation
This BAdI allows you to preassign weighting factors in purchase price determination using the vendor
mixed price. These weighting factors are default values for the relevant vendors when you are performing
sales price calculation. For example, you could use data from purchase orders from a certain period of
time in the past as your basis.
For more information, see BAdI: Preassigning Vendor Mixed Price Factors in Sales Price Calculation.
Business Add-In PWL_SP_DETERMINATION: Determining a default for the sales price when
generating the pricing worklist
This BAdI allows you to control the structuring of pricing worklist entries when the pricing worklist is
being generated. The BAdI has several functions here. Firstly, you can carry out checks with the BAdI on
whether an entry in the pricing worklist is really necessary. Pricing worklist entries can be suppressed if
purchase prices have changed slightly when you are implementing threshold values for a change in the
purchase price. Furthermore, you can define the sales price determination sequence that is to be used for
sales price calculation using this BAdI. This way the current sales price can be defaulted for articles
facing a certain amount of competition if the purchase price is increased. The entry in the pricing worklist
can then be used to check the margin that has been changed. Finally, you can use this BAdI to make
changes to the sales price calculation. You can implement rules, for example, so that only a fraction of
the purchase price increase, which possibly varies depending on the article group or characteristic, is
transferred to the consumer in the form of a higher sales price.
For more information, see BAdI: Change Retail Pricing When Generating the Pricing Worklist.
Business Add-In MBP_ADD_LIST_FIELDS: Additional Fields in Market-Basket Price Calculation
______________________________________________________________
SAP AG
221
SAP System
______________________________________________________________
This BAdI allows you to fill unrestricted-use fields in market-basket price calculation with prices and
values for which the customers can define their own meanings. Other prices could also be extracted from
sales price calculation. Additional sales or income values could also be defined for these prices for sales
quantities. You could also create sales or income differences.
For more information, see BAdI: Additional Fields in Market-Basket Price Calculation.
Business Add-In SMOD_LWVK1001: Enhancing communication structure KOMK for price
determination
This BAdI is from the migration of user exit LWVK1001. You can use this BAdI to control filling
communication structure KOMK for price determination in Purchasing and in purchase price conditions
from the database.
For more information, see BAdI: Enhancing Communication Structure KOMK for Price Determination.
Business Add-In SMOD_LWVK1002: Enhancing communication structure KOMP for price
determination
This BAdI is from the migration of user exit LWVK1002. You can use this BAdI to control filling
communication structure KOMP in sales price calculation for price determination in Purchasing and for
sales price conditions from the database.
For more information, see BAdI: Enhancing Communication Structure KOMP for Price Determination.
To copy the enhancements for user exits LWVK1001 and LWVK1002, use the modification adjustment
function (transaction SPAU).
Effects on Data Transfer
Business Add-In SPC_SEL_CHECK can affect pricing documents that are created subsequently for sales
price conditions and that you have transferred from old systems.
Pricing documents form the basis of the pricing worklist function. If you take sales price conditions from
old systems, then you have to create pricing documents subsequently for these conditions if you want to
use the pricing worklist function. Some of the sales price conditions may conflict with the filter and
exclusion rules in the BAdI. You must define whether pricing documents should still be created for these
sales price conditions so they can be included in the pricing worklist function. You do this by
implementing the BAdI methods (see example coding for method CHECK_CALC_ITEM).
Effects on Customizing
You configure the implementation for these Business Add-Ins in Customizing for Retail Pricing. Use the
following menu path in the Implementation Guide (IMG): Logistics - General -> Retail Pricing ->
Business Add-Ins for Retail Pricing.
11.5.9.2 General Parameters for Retail Pricing
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use different parameters for sales price
calculation with which you can determine which validity start date is defaulted when the user calls it on
the selection screen.
Furthermore, you can determine in sales price calculation whether the reference plant should be used in
retail pricing for distribution chains or whether price lists should be used in price determination in
Purchasing. You can define default values for document quantities for price determination in Purchasing
______________________________________________________________
SAP AG
222
SAP System
______________________________________________________________
and Sales if you cannot transfer these from the master data in certain situations.
You can define default values for the integrated article maintenance for the purchase price and sales price
determination sequence for when the user calls the sales view for the first time.
You can define a special document schema in sales price determination that is used for determining the
calculation schema for price determination in Retail. This document schema was maintained in earlier
releases in IMG activity General Control, Retail Master Data. This document schema will be
implemented by XPRA report WVXPRA08 in a release upgrade. For more information, see Transferring
a maintained document schema from TWPA to TWRPGP.
Effects on Customizing
The general parameters for Retail Pricing are fixed in Customizing for Retail Pricing: General Parameters
for Pricing.
11.5.9.3 New Change Pointers for Condition Records (WIND)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you have the following additional options for
adjusting documents in condition changes:
o
Direct entries in the worklist after condition changes
o
Including additional data in an entry in the worklist
In the previous procedure, the entries were created in the worklist based on the change pointers for
condition changes (message type CONDBI) in worklist creation (transaction ME14). In the new
procedure, the change pointers are no longer needed. When a condition is changed, entries are created
directly in the worklist. This removes the previous step in the process of creating the worklist from
change pointers, which was very performance-intensive. In addition, you do not have to create change
pointers for condition changes if they are not going to be used in other processes.
The Customizing that was valid for the previous worklist creation and that defines which condition types
should be included in the worklist (table T6I1) is also valid for the direct entry. However, there are
additional filter options in the new procedure. You can define for each document category for which
types of condition changes (amount change, validity, pricing relevance) entries should be made in the
worklist. There is also a BAdI that is dependent on the document category filter criterion with which
customer-defined filter criteria can be implemented.
The following example describes the options offered by the BAdI:
Due to changing purchasing conditions, perishable materials are regularly repriced in short time periods.
Therefore, sales prices do not need to be updated using the pricing worklist procedure. Use the material
type, in this case, as an additional filter criterion in the retail pricing application (document category 10).
When the basic purchase price of a perishable material is changed, the system does not create a worklist
entry for this document category due to the filter criterion that was implemented.
The additional data in a worklist entry consists of header data from the conditions with which you can
improve performance for the follow-on processing and of variable customer fields with which you can
carry out selective subsequent processing. You make settings in Customizing for filling the customer
fields (table T6I2S).
______________________________________________________________
SAP AG
223
SAP System
______________________________________________________________
Effects on Existing Data
If you do not use change pointers for condition changes, the level of data for change pointers is reduced
considerably. A change pointer generally consists of several entries in table BDCP and BDCP2.
The following changes are made:
o
The width of table WIND increases from 45 to 262 bytes due to the additional tables.
o
The number of table entries in the worklist can be reduced due to the additional filter criteria.
o
Change pointers are no longer needed for message type CONDBI.
Effects on System Administration
The process step for creating the worklist from change pointers (transaction ME14) is no longer needed in
the new procedure.
The check for existing document indexes (table S111) that can be used in the previous worklist creation
must be implemented as an additional filter criterion in the BAdI (see example coding).
The migration of the worklist from the old to the new worklist entries is carried out using report
RMEBEMIG. The report enhances the entries that are available using information from the condition
records.
If you are converting from the old to the new procedure, a special adjustment procedure is required for
every document category. This procedure is described in each of the applications that use the new
procedure.
Effects on Customizing
Implement the new Customizing for the direct creation of worklist entries. If you are installing this for
the first time or if you have not yet used the document adjustment function for a certain document
category, set the indicator manually for migration and direct entry in Customizing. When converting from
the old to the new procedure, the indicators in the migration procedure are set automatically.
You also determine the types of condition changes for each document category as filter criteria for which
worklist entries should be created and how the variables should be filled.
Once you have made settings for direct entries in the worklist for all the document categories used, you
do not have to create change pointers from message type CONDBI. Deactivate message type CONDBI in
ALE Customizing.
You can also carry out this deactivation using the migration report.
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Master Data -> Conditions ->Automatic Updating of Documents After Condition Changes.
11.5.10 LO-MD-SE
Season
11.5.10.1 Markdown Planning
______________________________________________________________
SAP AG
224
SAP System
______________________________________________________________
Use
As of SAP R/3 Enterprise Retail Core 4.70 (SAP_APPL 470), the following enhancements are
available in Season for markdown planning:
o
You can now assign price points for markdown plans that differ from those in standard pricing.
o
Prices can be automatically rounded down to make sure that customer receives the full percentage
off. For example, for an item that normally sells for $9.99, a 50% markdown yields a markdown
price of $4.99, not $5.00. This complies with US legal requirements. In Customizing for Markdown
Types you can maintain whether standard rounding is used or not.
o
Mass maintenance is now available on the detailed planning screen (similar to that on the rough
planning screen). You can change data for several articles at once; for example, you can change the
markdown percentage for all articles in a given merchandise category.
o
You can now specify selection criteria based on article categories, characteristics (color, for
example), characteristic values (blue, for example), purchasing groups, vendor sub-ranges, layout
modules, seasonal article categories (MARA-SAITY) and cross-distribution chain article status
(MARA-MSTAV).
o
You can now hold article selection criteria and reuse them for choosing new articles as well as for
marking articles or stores for mass maintenance on every planning level. (See Define Selection
Variant in Customizing.)
o
There are special authorizations for markdown plans; for example, at the merchandise category
level, sales organization level, or distribution chain level. This can be used to allow planners to
make changes to their own plans, but view the plans of their coworkers in read-only mode.
o
Support for a multi-user environment. Several people can work simultaneously on a markdown plan,
although they cannot modify the same article at the same time. (In other words, the lock is at the
item line level rather than at the header data level.
o
You can check whether an article is listed in two or more different markdown plans or promotions
with overlapping validity periods.
o
You can activate prices at the price list level.
o
A business Transaction Event (BTE) is provided after article selection, allowing you to populate
fields of a markdown plan at the item level with specific values.
o
A flexible tool allows you to automatically populate the initial stock field using the currently
available mass maintenance functionality.
o
Report RWMFA300 has been expanded to provide additional fields, totals at different planning
levels, and additional usability features to enable you to compare planned and actual sales data more
efficiently.
o
You are now able to distinguish between normal sales price conditions and sales prices resulting
from price changes initiated by markdowns.
o
There is a new archiving object: W_MARKDOWN.
______________________________________________________________
SAP AG
225
SAP System
______________________________________________________________
11.5.10.2 LO-MD-SE-MDF
Markdown Planning
11.5.10.2.1 Markdown Planning
Use
As of SAP R/3 Enterprise Retail Core 4.70 (SAP_APPL 470), the following enhancements are
available in Season for markdown planning:
o
You can now assign price points for markdown plans that differ from those in standard pricing.
o
Prices can be automatically rounded down to make sure that customer receives the full percentage
off. For example, for an item that normally sells for $9.99, a 50% markdown yields a markdown
price of $4.99, not $5.00. This complies with US legal requirements. In Customizing for Markdown
Types you can maintain whether standard rounding is used or not.
o
Mass maintenance is now available on the detailed planning screen (similar to that on the rough
planning screen). You can change data for several articles at once; for example, you can change the
markdown percentage for all articles in a given merchandise category.
o
You can now specify selection criteria based on article categories, characteristics (color, for
example), characteristic values (blue, for example), purchasing groups, vendor sub-ranges, layout
modules, seasonal article categories (MARA-SAITY) and cross-distribution chain article status
(MARA-MSTAV).
o
You can now hold article selection criteria and reuse them for choosing new articles as well as for
marking articles or stores for mass maintenance on every planning level. (See Define Selection
Variant in Customizing.)
o
There are special authorizations for markdown plans; for example, at the merchandise category
level, sales organization level, or distribution chain level. This can be used to allow planners to
make changes to their own plans, but view the plans of their coworkers in read-only mode.
o
Support for a multi-user environment. Several people can work simultaneously on a markdown plan,
although they cannot modify the same article at the same time. (In other words, the lock is at the
item line level rather than at the header data level.
o
You can check whether an article is listed in two or more different markdown plans or promotions
with overlapping validity periods.
o
You can activate prices at the price list level.
o
A business Transaction Event (BTE) is provided after article selection, allowing you to populate
fields of a markdown plan at the item level with specific values.
o
A flexible tool allows you to automatically populate the initial stock field using the currently
available mass maintenance functionality.
o
Report RWMFA300 has been expanded to provide additional fields, totals at different planning
levels, and additional usability features to enable you to compare planned and actual sales data more
efficiently.
o
You are now able to distinguish between normal sales price conditions and sales prices resulting
from price changes initiated by markdowns.
______________________________________________________________
SAP AG
226
SAP System
______________________________________________________________
o
There is a new archiving object: W_MARKDOWN.
11.5.11 LO-MD-PR
Promotion
11.5.11.1 Promotion Discounts
Use
As of SAP R/3 Enterprise Retail Core 4.70 (SAP_APPL 470), you can enter discounts for a large
number of articles in a promotion quickly and easily. For example, you can create discounts for:
o
All or selected articles of a promotion
o
All articles within a base merchandise category
o
All articles within a merchandise category hierarchy level (either one or two levels above the base
merchandise category level)
o
All articles, for example, for a given store or within a distribution channel
Discounts can be either for an absolute value (for example, $1.00) or a percentage (for example, 20%).
Discounts can be on the following levels:
o
Store
o
Price list
o
Distribution channel
You choose which level you want by assigning the appropriate price activation type. You can also enter
across-the-board reductions for all or selected articles within a promotion using the mass maintenance
dialog box. To change an existing discount amount, first deactivate the article, then enter the new
discount amount and resave the promotion.
Effects on Data Transfer
Discounts for a range of promotions can be downloaded via POS Outbound Processing. When you
choose manual request, you can select the field for preparing promotion discounts. There is also an IDoc
type for promotion discounts: WPDREB01.
Effects on Customizing
In Customizing for promotion types, you can assign discount condition types for absolute value discounts
and for percentage discounts. These become the default for any promotions you subsequently create using
that promotion type.
You assign condition tables to the condition types in Customizing.
______________________________________________________________
SAP AG
227
SAP System
______________________________________________________________
11.5.11.2 Promotion: Minor Enhancements
Use
As of SAP R/3 Enterprise Retail Core 4.70 (SAP_APPL 470), the following enhancements are
available in promotions:
o
You can now assign price points for promotions that differ from those in standard pricing. The
system will use these price points as the default for price point adjustments during mass
maintenance.
o
During mass maintenance, you can choose whether you want the system to use standard rounding,
or always round down to the nearest price. For example, if an article is normally priced at 99¢ and
has a promotion price reduction of 50%, standard rounding results in a price of 50¢ while rounding
down results in a price of 49¢. This complies with US requirements that the customer always
receive the full percentage off the normal price.
o
Normally when you activate a promotion price, the system calculates and stores information about
the markup, margin, purchase price, and so on. To improve performance, however, you can choose
to generate sales price conditions without having the system calculate them. In Customizing for
promotion types, specify without calculation. With this setting, you simply enter the sales price and
activate it. When you save the promotion, the system generates the sales price conditions. The
system automatically proposes without calculation in the header data. You can accept or reject this
proposal for a given promotion. Regardless of the header data, you can still choose whether or not
perform calculations for selected articles within the promotion.
o
In addition to the reference distribution chain and reference site, there is also a reference price list
available in Customizing for promotion types. A Business Add-In for promotion (BAdI) is also
available so you can implement your own logic for price determination.
o
The following key figures have been added to sales planning reports: sales volume at standard sales
price, gross margin, and lost sales dollars.
o
The previous two-step process for selecting and pricing articles has now been combined into a
single step.
o
A BAdI allows you to automatically populate or modify the default values at the item level when
you assign a new article to a promotion. You can use this BAdI to modify any or all of the fields that
are available for entry in the item overview or item detail screens.
o
Market basket pricing is now supported. You can assign articles within market baskets to a
promotion.
o
The allocation strategy is now included in promotions. You can assign either an allocation strategy
or an allocation rule to a promotion item. The allocation strategy defaults from the allocation type in
the promotion header data. The allocation strategy (like the allocation rule) can be used to generate
an allocation table or to simulate an allocation.
o
The multiuser functionality is now available in transaction WAK2. This enhances the functionality
previously provided by the special multiuser transaction WAK12. When you select a promotion,
you can decide whether you want to maintain the entire promotion (in which case other users cannot
work on it) or only selected articles within the promotion (in which case, only those articles are
locked while other users can work on the articles which are not locked). Several users can display
header data (for example, site groups, themes, promotion modules, and so on) at the same time, but
______________________________________________________________
SAP AG
228
SAP System
______________________________________________________________
not change it. However, they can change data pertaining to the item lines (for example, promotion
prices, volumes, pricing conditions, bonus buys, and free goods) Also, they can assign new items to
a promotion or delete items from a promotion.
See also
For information on the new promotion discounts function, see the Promotions Discounts release note.
11.5.12 LO-MD-QO
Quantity optimizing
11.5.12.1 Parallel Processing
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110) you can convert existing reports, which do not
enable you to carry out internal parallel processing in your worklist, into reports that automatically plan
several online parallel processes on available servers in a server group.
By doing this, the system can put the available computer infrastructure to better use and shorten the job
execution time considerably.
The new job planning guarantees that the distribution will always be up-to-date and balanced through the
following:
o
Worklist preselection.
o
Estimation of current workload.
o
Balanced workload distribution among the desired number of parallel jobs.
A report, which is generated for the actual report, is planned and starts the parallel jobs. You do not have
to change or enhance existing programs.
By using parallel processing as oppose to sequential processing, you are increasing the data throughput in
the critical time frame.
You no longer have to deal with manual planning of parallel jobs which is prone to errors and involves
maintaining a lot of variants that distribute the worklist among the parallel jobs. Changes to the worklist
therefore no longer lead to varying runtimes for the individual jobs. Regular checks and updates on the
balance of the distribution are no longer necessary.
The follow-on process control is simplified considerably and is also more transparent by virtue of the fact
that the number of planned jobs whose finishes have to be synchronized is reduced. The follow-on job
starts once this jobs finishes. The target minimum runtime is roughly the equivalent of the runtime on a
server divided by the number of servers available.
There is no reduction in data.
Effects on Customizing
The following activities must be carried out in Customizing for the external parallel processing:
o
Settings for External Parallel Processing
See also
______________________________________________________________
SAP AG
229
SAP System
______________________________________________________________
For more information, see the report documentation:
o
Load Distribution and External Parallel Processing
o
Framework for Parallel Reports
11.5.12.2 New Change Pointers for Condition Records (WIND)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you have the following additional options for
adjusting documents in condition changes:
o
Direct entries in the worklist after condition changes
o
Including additional data in an entry in the worklist
In the previous procedure, the entries were created in the worklist based on the change pointers for
condition changes (message type CONDBI) in worklist creation (transaction ME14). In the new
procedure, the change pointers are no longer needed. When a condition is changed, entries are created
directly in the worklist. This removes the previous step in the process of creating the worklist from
change pointers, which was very performance-intensive. In addition, you do not have to create change
pointers for condition changes if they are not going to be used in other processes.
The Customizing that was valid for the previous worklist creation and that defines which condition types
should be included in the worklist (table T6I1) is also valid for the direct entry. However, there are
additional filter options in the new procedure. You can define for each document category for which
types of condition changes (amount change, validity, pricing relevance) entries should be made in the
worklist. There is also a BAdI that is dependent on the document category filter criterion with which
customer-defined filter criteria can be implemented.
The following example describes the options offered by the BAdI:
Due to changing purchasing conditions, perishable materials are regularly repriced in short time periods.
Therefore, sales prices do not need to be updated using the pricing worklist procedure. Use the material
type, in this case, as an additional filter criterion in the retail pricing application (document category 10).
When the basic purchase price of a perishable material is changed, the system does not create a worklist
entry for this document category due to the filter criterion that was implemented.
The additional data in a worklist entry consists of header data from the conditions with which you can
improve performance for the follow-on processing and of variable customer fields with which you can
carry out selective subsequent processing. You make settings in Customizing for filling the customer
fields (table T6I2S).
Effects on Existing Data
If you do not use change pointers for condition changes, the level of data for change pointers is reduced
considerably. A change pointer generally consists of several entries in table BDCP and BDCP2.
The following changes are made:
o
The width of table WIND increases from 45 to 262 bytes due to the additional tables.
o
The number of table entries in the worklist can be reduced due to the additional filter criteria.
______________________________________________________________
SAP AG
230
SAP System
______________________________________________________________
o
Change pointers are no longer needed for message type CONDBI.
Effects on System Administration
The process step for creating the worklist from change pointers (transaction ME14) is no longer needed in
the new procedure.
The check for existing document indexes (table S111) that can be used in the previous worklist creation
must be implemented as an additional filter criterion in the BAdI (see example coding).
The migration of the worklist from the old to the new worklist entries is carried out using report
RMEBEMIG. The report enhances the entries that are available using information from the condition
records.
If you are converting from the old to the new procedure, a special adjustment procedure is required for
every document category. This procedure is described in each of the applications that use the new
procedure.
Effects on Customizing
Implement the new Customizing for the direct creation of worklist entries. If you are installing this for
the first time or if you have not yet used the document adjustment function for a certain document
category, set the indicator manually for migration and direct entry in Customizing. When converting from
the old to the new procedure, the indicators in the migration procedure are set automatically.
You also determine the types of condition changes for each document category as filter criteria for which
worklist entries should be created and how the variables should be filled.
Once you have made settings for direct entries in the worklist for all the document categories used, you
do not have to create change pointers from message type CONDBI. Deactivate message type CONDBI in
ALE Customizing.
You can also carry out this deactivation using the migration report.
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Master Data -> Conditions ->Automatic Updating of Documents After Condition Changes.
11.6 LO-BM
Batches
11.6.1 Original Batches (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), a new batch type is available in the form of the
original batch.
You can use an original batch to store the original attributes of a production lot or procurement lot. You
do this by creating the batch directly for a production order item or a purchase order item.
You can create original batches for an item in a purchase order, in a production order, or in a process
______________________________________________________________
SAP AG
231
SAP System
______________________________________________________________
order. It is irrelevant if
o
the material to produce or procure is not inventory-managed
o
different materials are produced in one lot
o
a lot is produced in partial quantities
You can use original batches to
o
Store attributes of a material that do not change within the production process.
This means, for example, that you can retain attributes of a starting material that cannot or should
not be placed in storage.
Example
In the production of chromium-nickel steel, the percentage portions of carbon, chrome, and
nickel in the metal melt is important. Further production steps such as rolling or cutting do not
changes these attributes. The attributes can be stored in an original batch for the metal melt,
and are valid for all batches produced from this particular metal melt.
o
Be able to copy characteristics of the original batch into the quality certificate.
Note
The original batch is connected to the batch where-used list and the Batch Information Cockpit.
11.6.2 Structure Changes in Batch Management
Use
o
Tools
This section has been replaced with the sections Worklist and Batch Information Cockpit.
o
Batch Information Cockpit
The following sections are new:
o
-
Follow-Up Actions
-
Selection Enhancements
-
Batch-Related Objects
Batch Derivation
In this section you maintain the settings for batch derivation.
11.6.3 LO-BM-BC
Batch Specification
11.6.3.1 Batch Class Conversion
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), this function enables you to quickly and
______________________________________________________________
SAP AG
232
SAP System
______________________________________________________________
easily change the assignment of a material subject to batch management and its batches, to the batch
class. Any existing characteristic value assignments are kept.
If there are requests for an existing batch class that render it necessary to split the class into two or more
mutually independent classes, you can do this using the Batch Class Conversion function.
The conversion is divided into two steps:
1.
Creating a conversion with the material subject to batch management and a new batch class
2.
Performing the conversion
You create, check, delete, and so on conversions using one online transaction. You can perform
conversions both online and in the background.
11.6.4 LO-BM-WUL
Batch Where-Used List
11.6.4.1 Batch Where-Used List in Repetitive Manufacturing
Use
As of SAP R/3 Enterprise 4.70 (SAP_APPL 470), the update of the batch where-used list by a
batch-specific update (multibatch functions) have been enhanced. You can now link materials produced
in repetitive manufacturing with their component batches that were actually used.
See also
Subpoint Batch Where-Used List in Repetitive Maunfacturing (New) in the release note Usability
Improvements in Repetitive Manufacturing (REM).
11.6.5 LO-BM-BIC
Batch Information Cockpit
11.6.5.1 Further Development of the Batch Information Cockpit
Use
For SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the following functions were added to the Batch
Information Cockpit, which forms a central switch point with wide-ranging analysis and control options:
More Extensive Selection Options
The following selection tab pages were added to the standard selection:
o
ATP/Display units of measure
You can use this selection tab page to obtain information about
______________________________________________________________
SAP AG
233
SAP System
______________________________________________________________
o
-
the availability of batches
-
the division of stocks to other alternative units of measure
BAdI
You can use this selection taba pge to create your own selection using a BAdI. SAP delivers two
example implementations for this selection tab oage:
a)
Selection with inspection lots
b)
Selection with objects with batch reference (for example, deliveries, storage bins, handling
units).
Simplified Selection
Users that regularly call up the Batch Information Cockpit using the same selection criteria have the
option of storing these criteria in a selection variant. You also have the option to call up the Batch
Information Cockpit and simultaneously start a selection using the stored selection criteria.
Customer-Specific Enhancements
You can use Business Add-Ins to integrate customer-specific enhancements with regards to selection (see
above) and follow-up actions for mass changes - such as selecting batches from inspection lots in order to
trigger repeat checks, or changing the batch status of several batches that were determined using the batch
where-used list.
Effects on Customizing
You make settings for the follow-up actions and the selection enhancements in Customizing for Batch
Management under Batch Information Cockpit -> Follow-Up Actions or Selection Enhancements.
11.6.6 LO-BM-DRV
Derivation
11.6.6.1 Batch Derivation
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the function Batch Derivation
for produced batch master data and classification data (attributes) that perform the following actions for
the component batches used in them:
o
transfer
o
offer for selection
o
display
You can call up and use derivation in Logistics at fixed times (for example, when you post goods receipts
for production orders, when you release process and manufacturing orders, when the usage decision is
made).
The component batches of a produced batch are determined using the batch where-used list. The batch
______________________________________________________________
SAP AG
234
SAP System
______________________________________________________________
where-used list has been enhanced, so that you can expand both planned goods movements and those that
have already taken place.
To fulfill the requirements that occur in various business processes, there are two different derivation
types:
o
Static derivation
With this derivation type, the system transfers the attributes determined from the produced batch to
the component batch/es.
o
Dynamic derivation
With this derivation type, the attributes are not transferred. The derivation is simulated and the
values are only displayed; they are not stored.
You can also decide whether the derivation should be started from a component or a product. The values
are always transferred from components (senders) to products (receivers), in other words, in the same
direction as the value flow.
o
Pull derivation (1 receiver, n senders)
The derivation is started from a transaction (for example goods issue or process order) that affects
the order. Here the system can summarize, cumulate, and calculate data from various senders
(example of use: pick and pack activities).
o
Push derivation (n receivers, 1 sender)
Here the derivation is performed during a transaction that affects the components (for example,
making the usage decision for a bulk batch). The data from a bulk batch is transmitted to the batches
of numerous materials issuing from that batch (example of use: filling).
Effects on Customizing
You make the settings for batch derivation in Customizing for Batch Management under Derivation of
Batch Data.
11.7 LO-VC
11.7.1 LO-VC-CHR
Variant Configuration
Characteristic Value Assignment / Interface Design
11.7.1.1 Distribution of Interface Designs (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can distribute interface designs for
variant configuration.
On the selection screen for distribution of interface designs in variant configuration , you have the
following selection options:
o
You can select several interface designs.
______________________________________________________________
SAP AG
235
SAP System
______________________________________________________________
o
You can define the target system.
o
You can specify the number of interface designs to be put together in one IDoc.
o
You can display the generated IDoc numbers.
Effects on Customizing
o
Before you can distribute interface designs, you must maintain a Distribution Model in Customizing
for Application Link Enabling (ALE). .
o
The generated IDoc is only saved to the target system if all the characteristics that are in the IDoc
for the interface design also exist in the target system. However, you can still save it if not all
characteristics of the interface design exist in the target system, by using the Business Add-In
(BAdI) Ignore Non-Existent Characteristics to define that any characteristics of the interface design
that do not exist in the target system are ignored during distribution.
11.8 LO-ECH
Engineering Change Management
11.8.1 21 CFR Part 11 Enhancement on Electronic Records (New)
Use
As of Release 4.70, you can use the function 21 CFR Part 11 Enhancement on Electronic Records (in the
following referred to as Part 11) to switch the logging of data changes in individual data elements or
entire tables on and off according to your individual requirements. Although changing the logging status
from on to off or vice versa is also possible in previous SAP Releases, it has hitherto been regarded as a
modification and treated accordingly. The function Part 11 now enables you to make such changes
without technically carrying out modifications. Changes in the logging status are also preserved following
an upgrade or a correction via support package.
Furthermore, with the evaluation function, you have the option of evaluating logged data very specifically
according to individually entered selection criteria. In the process, it is immaterial whether the logging
status has been changed with Part 11 or was already set to on in the standard system. The
evaluation/analysis of change document objects, table logs, or long texts can be carried out either
separately or jointly. It is also possible to evaluate already archived data.
Part 11 contains the following individual functions:
o
Comparison of logging status between the system supplied by SAP and the individual configuration
(e.g. following an update or import of a support package).
o
Switching on and off the creation of change documents for individual fields and the table logging
function. This is possible for both current system data and already archived data.
o
Logging and evaluation of changes in long texts.
o
Evaluation of logged data according to individual search criteria and listing of changed data in an
audit trail. This can be exported in common file formats.
o
Creation of a graphical navigation aid for the changed transactions and tables which supports the
user in setting and evaluating the data.
______________________________________________________________
SAP AG
236
SAP System
______________________________________________________________
A change in the logging status of certain tables or table fields may be necessary to satisfy the
requirements of the U.S. Food and Drug Administration (FDA) in the field of regulated production, for
example, with regard to the regulation 21 CFR Part 11 Electronic Records/ Electronic Signature.
Compliance with this regulation is a strict precondition for determination of the compliance of your SAP
system with FDA regulations.
Effects on Existing Data
No existing change document objects are changed or new ones generated. The existing database increases
with the volume of data to be logged.
Effects on Customizing
To record changes to data or terminate such recording, you must change the logging status in
Customizing for the relevant tables or change documents. To do so, use the activity Logging -> Change
Configuration of Logging in the SAP Reference IMG for Logistics (General).
11.9 LO-MDS
Merchandise Distribution
11.9.1 LO-MDS-AL
Allocation
11.9.1.1 Allocation Tables for Customers
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the allocation table for pure
customers, in addition to using it for plants as goods recipients.
You can create sales orders as follow-on documents from the allocation table too.
You can use a new report for this with which you can create all the other follow-on documents for the
allocation table too.
The following transactions are therefore obsolete and no longer available:
o
WA05 allocation table follow-on document generation: generate purchase orders
o
WA06 allocation table follow-on document generation: generate deliveries
o
WA07 allocation table follow-on document generation: generate warehouse orders
o
WA60 allocation table follow-on document generation: create variants to generate purchase orders
in the background
o
WA61 allocation table follow-on document generation: create variants to generate deliveries in the
background.
Up until now, you could only display the list for displaying worklists using the Customizing activity for
generating follow-on documents (transaction OWA1).
With the new report for follow-on document generation (transaction WA08), you enter the tools for
displaying the list "ALV Classic" or "ALV Grid" to make adjustments directly in the list display of the
______________________________________________________________
SAP AG
237
SAP System
______________________________________________________________
worklist for follow-on document generation.
You can plan jobs in parallel to create follow-on documents in the background.
You can use the following user exits for this:
o
o
Recipient determination
-
Recipients were defined up until now using plants/customer groups, allocation rules, or by
entering them manually.
-
Now recipient determination works using customer-specific function modules where parameter
tables can also be used.
Delivery date determination
-
Up until now, this involved entering default values at header or item level or assigning delivery
dates to recipients individually.
o
Complex selection of articles
o
Customers always sales orders, plants either stock transport orders or sales orders
o
Manual assignment of AT numbers, you can also enter information using a prefix, for example.
o
Customer-specific source of supply for customers
11.9.1.2 New Allocation Strategies Based on SAP BW
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), you can use 3 new allocation strategies that
all access data (historical or plan data) in SAP BW.
"Quotas from SAP BW" Strategy: Quotas Based on SAP BW Data
The allocation strategy, "Quotas from SAP BW", accesses article sales history or merchandise category
sales history from an allocation table item. The system does this using the query selected in SAP BW for
a time period and then returns a quota for each plant. The actual allocation table quantities for the
recipients are calculated on the basis of a planned quantity for the item using quotas determined in SAP
BW.
"Top-Down (SAP BW)" Strategy: Planned Quantities for Recipients
In the "top-down (SAP BW)" allocation strategy, you can incorporate the following factors:
o
Sales data over a period of time
o
Putaway of a partial quantity of the total quantity into warehouse stock (optional)
o
Trend factors for all recipients or for individual recipients using allocation rules (optional)
o
Current available stock in stores, although alternative articles can be used (optional)
o
On-order stock in stores (optional)
o
Min./max. order quantities in allocation units (optional)
______________________________________________________________
SAP AG
238
SAP System
______________________________________________________________
o
Put away remainder of stock allocation (optional)
o
Rounding in accordance with rounding profile (optional)
"Bottom-Up (SAP BW)" Strategy
The "bottom-up (SAP BW)" strategy is also based on sales quantities and data from SAP BW. However,
it can be called without entering a planned quantity from the allocation table item first. It calculates
quantities for recipients. The planned quantity is the result of aggregated quantities of recipients for an
item. Sales up to a particular date can also be included, for example, up to a certain delivery date.
The following factors are included:
o
Sales data using a period of time, although you can use alternative articles, merchandise categories
or a merchandise category hierarchy (optional)
o
Expected sales up to the delivery date in stores, although you can also use alternative articles,
merchandise categories or a merchandise category hierarchy (optional)
o
Putaway of a partial quantitiy of the total quantity into warehouse stock (optional)
o
Trend factors for all the recipients or for individual recipients using allocation rules (optional)
o
Current available stock in stores, although you can use alternative articles (optional)
o
Weeks of supply entry (optional)
o
Min./max. order quantities in allocation units (optional)
o
On-order stock in stores (optional)
o
Rounding in accordance with rounding profile
11.9.2 LO-MDS-CPO
Collective Purchase Order
11.9.2.1 Collective Purchase Order: Improved Throughput and Parallel
Processing
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can increase the throughput of collective
purchase order generation (transaction WF10) and, therefore, shorten the runtime.
o
The collective purchase order performance is improved by a new internal technical design. The new
internal design does not affect the user interface or the functionality.
o
You can use parallel processing, which makes the runtime shorter and makes better use of system
resources. The parallel processing can take place at various points in time (when issue documents
are selected, when the issue documents are aggregated into collective purchase orders, when
collective purchase orders are generated, and when the issue documents are updated). Generating
collective purchase orders usually takes the longest amount of time: it is therefore here that parallel
processing has the greatest effect.
o
Functions are integrated for measuring the runtime and can help you to find the optimum settings
______________________________________________________________
SAP AG
239
SAP System
______________________________________________________________
for your parallel processing. The following options are available:
-
You receive information on the relative runtime, which is similar to transaction SE30.
-
You also receive information on technical data (for example, on which servers are used and
how many tasks have been processed).
The runtime measurement is intended for the testing and implementation phases, and can also be
used for specific runtime checks in the production operations. You should not have it switched on
permanently in a production operation.
o
You can use an indicator in the collective purchase order generation to move temporary data from
the main memory to the local file system or database and, therefore, reduce the demand on the main
memory.
Note:
There will be no improvement on throughput if you generate collective purchase orders directly
from perishables planning.
Effects on Existing Data
o
o
Collective purchase order
-
The operational dataset is not affected.
-
If you set the indicator in the tab page for technical parameters to temporarily save the issue
documents, then temporary data is updated in the database (cluster table MDS_TMP).
Runtime measurement
If the runtime measurement is switched on, data is updated in tables WTRAH and WTRAD.
Effects on System Administration
o
o
Collective Purchase Order
-
If you want to parallel process collective purchase orders, you have to enter the master data for
parallel processing using transaction W_PARA and the parameters for parallel processing in
transaction WF10.
-
If you set the indicator in the tab page for technical parameters to temporarily save the issue
documents, you have to start program R_CPO_DELETE_TEMPORARY_DATA on a regular
basis (SAP recommends you do it on a daily basis), to delete this data again. The data can be
deleted again as soon as the collective purchase orders have been generated.
Runtime measurement
-
Create a number range (number range object WTRA_LOGNR).
-
Once you have switched on the runtime measurement, you have to start program
WTRA_DELETE_PROTOCOL_FROM_DB at regular intervals to delete the log data again.
-
The user requires authorization to delete the data (authorization object W_WTRA_LOG).
-
You can set a retention indicator in Customizing that flags the runtime measurement logs for
retention (use transaction WTRA1 to maintain the data for this). You enter the data in view
V_TWTRAS, which is not part of the IMG.
-
In the delete program you can confirm the retention indicator for the logs. If you do not make
any settings (defaults), then the logs will not be flagged as being relevant for retention.
______________________________________________________________
SAP AG
240
SAP System
______________________________________________________________
Changes to the interface
o
o
Collective purchase order
-
In transaction WF10 there is a new tab page for technical parameters (for example, for parallel
processing controls and for the runtime measurement).
-
If the collective purchase orders are generated in the background (not in dialog processes), then
they are displayed in a log.
-
Error and warning messages are displayed in the application log.
Runtime measurement
-
Use transaction WTRA1 to make settings for the runtime measurement.
-
Delete log data in transaction WTRA2.
-
Display the results in WTRA3.
11.9.3 LO-MDS-DPR
Distribution Processing
11.9.3.1 Distribution monitor: Restriction to adjustment-relevant items
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the distribution monitor
(transaction WF30) via the indicator Adjust Worklist to restrict the selection to distribution records that
still need to be adjusted manually. This way, only distribution records with the following characteristics
are selected:
o
The distribution is not yet complete
o
A goods receipt has already been posted
o
GR quantities exist for which no adjustments have been made.
11.9.3.2 Automatic Delivery Generation After Manual Adjustment
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), delivery generation after manual adjustment
can be started automatically in the situation that is described below. Previously, it was only possible to
trigger delivery generation manually in this case.
Previous procedure:
1.
The automatic adjustment in goods receipt is called.
2.
Because the difference permitted between the goods receipt quantity and the ordered quantity has
been exceeded, the system cannot carry out the automatic adjustment.
______________________________________________________________
SAP AG
241
SAP System
______________________________________________________________
3.
You adjust the quantities manually.
4.
Then, you start the delivery generation manually for the deliveries that are still missing.
New shorter procedure available as of SAP R/3 Enterprise Core 4.70:
1.
The automatic adjustment in goods receipt is called.
2.
Because the difference permitted between the goods receipt quantity and the ordered quantity has
been exceeded, the system cannot carry out the automatic adjustment.
3.
You make the adjustments manually. When you save, the system starts the automatic delivery
generation.
Customizing settings required in the plant profile for distributing materials:
o
Time of adjustment: goods receipt with a check run on the size of the difference
o
Time of the delivery generation: goods receipt
The BAdI, WFRM_CRE_FOLLON_DOC, triggers this. In the standard system, the BAdI is active and
the example coding is executed. Using this BAdI, you can access the procedure in the standard system
and adjust it to suit your needs.
Effects on Customizing
In the standard system, the BAdI, WFRM_CRE_FOLLON_DOC, is active and the example coding is
executed. You only have to access the procedure to change the system response if you want to.
11.10 LO-SRS
SAP Retail Store
11.10.1
Short text (Titel)
Time Recording in SAP Retail Store
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), you can no longer use the SAP Retail Store
functions to record your working time. Instead, you can use the much broader range of functions offered
by Time Manager's Workplace (HR) using the SAP GUI for HTML in the portal, Retail Store
Management.
Effects on Existing Data
If you have used time recording in SAP Retail Store until now, you will need to run the report,
RPTEXTPT, once to convert to the new time recording procedure.
Effects on System Administration
Cancel the regular running of program RPTEXTPT.
______________________________________________________________
SAP AG
242
SAP System
______________________________________________________________
11.10.2 Cash Control
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), the store manager can use different
functions to enter cash stocks and payment methods similar to cash using this Internet application in a
store. These cash amounts could include checks or amounts debited from credit cards but entered
manually in a store. The purpose of this Internet application is to map cash stocks and the business
transactions involved realistically in Financial Accounting in the SAP R/3 System.
This involves the following 3 main functions:
o
Cash paid in and cash paid out
This function is used to create special business transactions with cash in and out. Cash paid out
could be, for example, for small invoices for the running of the store such as cleaning work or
postage. Cash paid in could be a late payment from a regular custoemr that was entered as cash paid
out.
o
Cash balancing (or shift-end closing)
With this function, you can compare the sales data that is transferred via the POS interface to the
SAP R/3 System with the counted cash stocks. Foreign currency, checks and non-electronic credit
card transactions based on manual documents are included in this function together with cash stocks
in the store's local currency. Adjustment postings are triggered for the accounts concerned in
Financial Accounting if variances occur between the system data and the cash counted.
o
Bank deposit
This function concerns the business transaction where cash is paid into the bank from the safe in the
store.
Effects on System Administration
The function is subject to the general authorization concept of SAP Retail Store. However, you need
authorization in addition to execute transaction WOSCR_CBL (authorization object S_TCODE).
Effects on Customizing
You can maintain the transaction screen mostly in cash control Customizing under the SAP Retail Store
settings. The following settings are particularly noteworthy:
o
Initial Screen (selection menu)
-
o
By setting up account groupings in Customizing, you determine the input screens (detail
screens) for the functions cash paid in/paid out, cash balancing and bank deposit. There is a
menu on the initial screen with a radio button for each entry screen. You enter the text for the
radio buttons in Customizing when you define the account grouping.
Cash Paid In and Cash Paid Out
-
Whether the function should be used for one or more assignment numbers
-
For which accounts (business transactions) input lines should appear
-
Whether a column should appear for the posted amounts and/or difference amounts
-
Which headings should be used for the G/L account column and for the posted amounts
______________________________________________________________
SAP AG
243
SAP System
______________________________________________________________
column
o
o
Whether reasons can or must be entered when differences occur and which can be selected
Cash Balancing
-
Whether the function should be used for one or more assignment numbers
-
For which currencies (local currency and foreign exchange), checks and payment cards should
entry lines appear
-
Which headings should be used for the G/L account column and for the columns for counted
and posted amounts
-
To which accounts should the counted amounts and difference amounts be posted
-
Where total amount lines should appear
-
Whether reasons can or must be entered when differences occur and which can be selected
Bank Deposit
-
Whether the function should be used for one or more assignment numbers
-
For which currencies (local currency and foreign exchange) and checks should entry lines
appear
-
To which accounts the system should post the amounts to be paid in and any differences
-
Where total amount lines should appear
-
Whether reasons can or must to be entered if differences occur and which can be selected.
BAdI WOSCR_CBL enables you to adjust the screen too for selecting postings and enhancing updates
that are to be made. The following enhancements are examples:
o
Processing customer-defined fields on HTML screens
o
Modifying the posting selection
o
Enhancing the posting lines with text
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Distributed Data Processing -> SAP Retail Store -> Sales.
11.10.3 Expense Invoice
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), you can enter and update in the system
invoices received in the store. The following functions are available for this:
o
You can post incoming invoices directly in the system.
o
You can use a search function to select and assign a known vendor if necessary.
o
You can select an account to which the invoice amount is to be posted.
______________________________________________________________
SAP AG
244
SAP System
______________________________________________________________
o
You can calculate input tax amounts in the system for various tax codes or enter them directly.
Effects on System Administration
The function is subject to the general authorization concept of SAP Retail Store. You also need
authorization to carry out transaction WOSCR_EXI (authorization object S_TCODE).
Effects on Customizing
You can adjust the appearance of the transaction in "Expense Invoice" Customizing under "SAP Retail
Store". The following settings are of particular note:
o
Which general ledger accounts can be used for updating the invoice amount.
o
Which tax types are to be possible.
There is also BAdI WOSCR_EXI that you can use for adjustments to the flow logic. You can use the
following enhancements:
o
Processing user-defined fields on HTML screens.
o
Controlling the posting logic, for example, by filling additional fields in the posting lines of a FI
posting.
See also
For more information, see the documentation for SAP Retail (SAP Library -> Logistics -> SAP Retail)
under Distributed Data Processing -> SAP Retail Store -> Purchasing.
11.10.4 Physical Inventory in SAP Retail Store
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), you can use the following additional
functions:
o
Plan a physical inventory with a small scope by creating physical inventory documents. You can
determine the articles to be counted either by entering them individually or by using the article
selection function (for example, selection by merchandise category).
o
Support for physical inventory counts with PDC devices with a function for sending newly created
physical inventory documents automatically to the PDC device and monitoring PDC activities in the
store. You can make settings in Customizing for which PDC procedure should be used in the store.
(PDC procedure with ITS file transfer or PDC procedure for mass processing).
You can see the status of the PDC transactions in the store including any error messages that
occurred, and, in the case of a PDC inbound containing errors, you can trigger a repeat processing.
-
If you use the PDC procedure with ITS file trasnfer, you can enter the count results of a
physical inventory by PDC file.
-
If you use the PDC procedure for mass processing, you can send physical inventory documents
to the PDC device.
Effects on Customizing
______________________________________________________________
SAP AG
245
SAP System
______________________________________________________________
To create physical inventory documents, you must make the following settings in the area Materials
Management -> Inventory Management and Physical Inventory -> Physical Inventory -> Default Values
for Batch Input
o
Under the report name "RM07II31", you can determine the maximum number of items for normal
stock.
o
Under the report name "RM07IE31", you can determine the maximum number of items for each
physical inventory document for special stock "sales order stock".
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Distributed Data Processing -> SAP Retail Store -> Inventory Management.
11.10.5 Sales Order in SAP Retail Store
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), you can use the following new functions.
o
Common initial screen for all the functions in sales document and customer master record
processing.
Sequenced search functions for customers and sales documents for the customers allow the user to
identify the customer master record and the document for processing using the name and address of
the customer.
o
Processing sales document categories including queries, quotations and returns in addition to the
sales document category, order that was previously available.
o
Creating a sales document with a reference to another sales document or billing document ("copy").
o
Article identification as an alternative to the R/3 article number also using the EAN or a number
defined by the customer and identifiers that are implemented using a BAdI.
o
Entry and display of additional order item fields such as unit price, item category,
collection/delivery indicator, and delivery group.
o
Display of automatically generated subitems, for example, in sales sets and free-goods discounts.
o
Address input for one-time customers.
o
Display of change documents and the document flow for a sales document.
o
High-performance enhancement concept for additional checks and data manipulation, and additional
output and input fields such as adding individual screens to the dialog process.
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Distributed Data Processing -> SAP Retail Store -> Sales.
______________________________________________________________
SAP AG
246
SAP System
______________________________________________________________
11.10.6 Mass Maintenance of Master Data
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-Retail 110), the mass maintenance tool has been enhanced
to include:
o
Vendor master data
o
Purchasing info records
o
Logistics and replenishment data
o
Purchase orders
This mass maintenance tool focuses on four main aspects. First, it provides a user-friendly interface to
execute data maintenance. Second, it provides a tool that can be easily adapted to handle new types of
mass maintenance. Third, it improves performance. It uses parallelism to accelerate saving a mass
maintenance session and, in the case of logistics data, uses high performance updating optimized for
retail. Finally, the tool provides an error recovery functionality that allows for the recovery and
reprocessing of errors that occurred during the save process.
o
Common properties
All the mass maintenance tools are based on the same basic framework and user interface. The
features of this interface include:
-
You can define the scope of data in a selection area using standard selection criteria or defining
your own.
-
You can use the navigation tree to drill down along the objects hierarchy (for example, by
Purchasing Organization -- Vendor -- Site in the info record mass maintenance).
-
You can display and maintain each entry easily in the maintenance grid.
-
You can search for entries within the navigation tree.
-
You can mass update and clear entries within the maintenance grid.
-
You can apply formulas to fields in the grid.
-
You can filter records from the maintenance grid.
-
You can use an integrated error recovery tool that lists errors and allows you to correct them on
the fly.
-
You can view and manage data at the reference site level in the vendor/site, purchasing info
record, and logistics/replenishment mass maintenance tools.
-
You can check for common errors before saving the data.
-
User exits are provided to update your own custom fields and perform checks for your specific
business rules
NOTE: Some fields required by customers for updating are not available due to technical reasons.
These fields are: UPC/EAN, Commodity code, and Quantity. SAP hopes to address these in a
future release.
o
Vendor/site master data
______________________________________________________________
SAP AG
247
SAP System
______________________________________________________________
You can now use vendor/site records in an optional form of source determination that will be
delivered in a user exit. You can take advantage of the purchasing reference site functionality to
group stores with similar sourcing requirements rather than maintaining every site individually.
Because this increases the importance of vendor/site records, you can mass maintain these records
using this tool. It provides visibility into purchasing reference sites by displaying the data the
dependent sites adopted from the purchasing reference site.
o
Purchasing info record master data
Purchasing reference sites can also be used with purchasing info records. You can set up purchasing
info records for a purchasing reference site if there is data that differs from site to site. This allows
you to avoid using site-specific purchasing info records.
The purchasing info record mass maintenance tool can be used to maintain purchasing info records
generally and also simulates the impact purchasing reference site changes have on their dependent
sites.
o
Logistics/replenishment master data
Logistics reference sites are available to improve the management of article/site logistics master
data. This mass maintenance tool is designed to update logistics, replenishment, and forecasting
parameters for articles at distribution centers and stores. .
It uses the same general framework as the others and also allows you to maintain data at logistics
reference store level while copying it automatically to the dependent sites. This new copy logic is
only used when standard reference handling is turned off for the changed field and when the
dependent site entry is the same as the reference site entry.
The performance of logistics/replenishment data updating has been significantly improved.
o
Purchase orders
Purchasing in high volumes requires retailers to have the ability to make a large number of changes
to existing purchase orders. Using the new purchase order maintenance transaction, you can make
mass changes to PO headers, line items, and schedule lines. This transaction has the same usability
features described in the common properties section.
The standard selection fields available are: Purchase organization, Purchasing group, Document
type, Vendor, Supplying site, Article, Receiving site, Delivery complete indicator, Delivery date. In
addition, you can specify your own selection fields using dynamic selection criteria.
The fields available for updating are: Inco terms, Payment terms, Vendor article number, Delivery
date, Delivery complete indicator, Deletion indicator, Season category, and Season year.
NOTE: Purchase order mass maintenance covers only those purchase orders having a status of
released, released with partial deliveries, and unreleased.
______________________________________________________________
SAP AG
248
SAP System
______________________________________________________________
11.10.7 PDC Link in SAP Retail Store
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), you can link PDC devices using dedicated
interfaces as well as a browser. This concerns the following areas:
o
Store order
o
Goods receipt
o
Goods movement
o
Physical inventory
The data exchange between the SAP System and the PDC devices can carry out many functions
automatically, which simplifies using them considerably. An SAP Business Connector with a special
Add-On for SAP Retail Store is used to link the PDC interfaces with the stores. Software is available
from third-parties (for example, PanSoft) to transfer data from the SAP Business Connector to the PDC
device to process data in the PDC device and to transfer the data back to the SAP Business Connector.
A typical example for using this new PDC link is in physical inventory:
1.
The store manager determines which articles should be counted using the physical inventory screen
in SAP Retail Store.
2.
SAP R/3 transfers the data using the SAP Business Connector and the docking station to the PDC
device.
3.
A store associate takes the PDC device, performs the stock count on its display, enters the count
results, and then takes the device back to the docking station.
4.
The data entered is automatically transferred using the Business Connector to the central SAP R/3
System and updated there too.
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Distributed Data Processing -> SAP Retail Store.
11.10.8 Store Groups/New Store Openings
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-Retail 110), you can group similar stores together and
maintain data for the entire group at once, rather than each store individually. This increases the
performance and manageability of listing, makes changes to store data easier, and decreases the time
required to set up data for new stores. It also provides an overview of the existing data at group level or at
individual store level.
______________________________________________________________
SAP AG
249
SAP System
______________________________________________________________
Site groups may be defined for different reasons: geographic location, size, or demographics . Some
retailers use the same store groups for all functional areas, others use different store groups for different
functional areas. Also, large retailers and retailers in rapid growth sometimes can open a new store every
other day or even more frequently. The store opening process is critical because it can be the first
impression a retail chain makes in a new market. Therefore, this process requires simple and efficient
maintenance, including the setup of the new store#s master data as well as its initial ordering.
You can use of store groups for purchasing data (vendor/site data and purchasing info records, purchasing
conditions), assortment data, and logistics/replenishment data. After the master data for the new store has
been set up using a reference store and a multiplier for consumption data, you can now run the forecast
for the new store and afterwards run replenishment to create the initial store orders automatically.
o
Store Grouping for Purchasing Data
You can maintain vendor/site data as well as purchasing info records and purchasing conditions for
a group of sites. To accomplish this, you can use reference sites for purchasing; these reference sites
represent all sites assigned to the reference site. The data is only stored at the level of the reference
site and is used where no specific site level data exists.
As an extension of supply source definition, vendor/site data can be used to limit the vendor only to
the assigned sites. If an assignment is made for a reference site, all sites assigned to this reference
site are to be supplied by the vendor.
Vendor discounts for new store opening can easily be defined using trigger conditions. These
conditions are set up when a new store is opened and trigger the appropriate vendor discounts for
the time the trigger condition is active.
o
Store Grouping for Assortments
Previously there was a 1:1 relation of assortment to site, so each site has its own assortment. An
article is listed for an assortment (not for a site) and a listing condition is created when the article is
listed.
You can now choose whether to have an n:m assignment of sites to assortments. That is, a site may
have several different assortments, and an assortment may be assigned to several different sites, thus
circumventing the old 1:1 assignment restriction. This function is similar to the multiple assignment
of customers to assortments, which already exists. Because articles are listed for assortments (not
for sites), the listing conditions that are created are valid for all the sites assigned to this assortment.
You could, for example, define multiple assortments for each merchandise category and list those
products for each assortment that are considered to be the optimal mix for the assigned group of
sites (list high fashion products store groups in large urban areas).
For more information on multiple assignments, see Release Note Multiple Assignment of
Assortments to Sites/New Store Openings
o
Store Grouping for Logistics/Replenishment Data
Previously, logistics and replenishment data for stores could only be maintained for all stores
(general reference store) or for all stores belonging to a specific distribution chain (reference store at
distribution chain level). Thus the only grouping level for maintaining logistics data is the
______________________________________________________________
SAP AG
250
SAP System
______________________________________________________________
distribution chain. Replenishment and logistics data typically do not differ by distribution chain, but
rather they vary by site group: store size, geographical location, and so on. Therefore, a maintenance
level other than distribution chain is needed.
The maintenance of logistics and replenishment data at site group level is provided in a separate
mass maintenance tool . For more information, see Release Note Mass Maintenance of Master Data
11.10.9 SAP Retail Store
Use
As of SAP R/3 Enterprise, SAP Retail Store can be found in the component SAP R/3 Enterprise
Retail 1.10 (EA-RETAIL 110).
Effects on System Administration
Note that once you have installed the component, it must also be activated, to allow you to use SAP
Retail Store.
11.11 LO-MAP
Merchandise and Assortment Planning
11.11.1 MAP: Methods for Linking Planning Steps - Aggregation and
Disaggregation
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), in addition to the following methods for
linking planning steps,
o
Pure Documentation
o
SAP Copy Management
o
Transaction/Program
you can also select the following new methods:
o
Disaggregation
o
Aggregation
If you choose disaggregation or aggregation as the step link method, when the planning scenario is
activated, a report will automatically be generated. This report can be used later without having to be
programmed, to transfer data from a source planning step to a target planning step. Independently of
Customizing for the planning hierarchy concerned, the plan data is aggregated or disaggregated according
to the proportional factors defined in the planning hierarchy or the proportions that already exist. The
selection screen of the disaggregation or aggregation report generated enables you to limit the plan data
to be transferred to certain planning levels, periodicities and key figures. In order for this report to be
______________________________________________________________
SAP AG
251
SAP System
______________________________________________________________
generated there must be at least one common key figure in the source and target planning steps.
11.11.2 MAP: Assortment Planning
Use
As of SAP R/3 Enterprise Retail 1.10, MAP supports planning at assortment level. The following
functions help the planner responsible to compile the correct product mix for the coming timeframe for
planning:
o
Using assortments as planning levels; creating key figure plannings for assortments
o
Listing from MAP; the following combinations of planning levels are supported with regard to the
generation of listing conditions:
o
-
Articles and assortments
-
Season category/material group and assortments; if planning does not take place at article
level, the articles can be determined using the season category and the material group.
-
Category and assortments; if the article level is not used in the planning hierarchy, the articles
can be determined from the category instead.
-
Listing from MAP means that the listing conditions can be generated directly from manual
planning.
-
If no assortment is planned in the planning hierarchy, a dialog box appears asking the user to
enter the assortments to be used.
Additional indicators; when using assortments and articles in the planning hierarchy, listing is
supported by the following additional indicators:
-
Listing check: This indicator is set if the article/assortment combination is already listed in the
timeframe for planning.
-
Listing plan: This indicator can be set if the article/assortment combination is to be listed in the
planning period.
-
Discontinuation plan: This indicator can be set if a listed article is to be discontinued in the
timeframe for planning.
o
Call the job schedule for the listing from manual planning
o
Call the transaction for the listing conditions from manual planning
Effects on Customizing
After the upgrade you can continue to use existing planning scenarios just as before. In the standard
system, the new planning functions will not be used at first. They can, however, be made productive by
using a standard network for the design of planning scenarios.
______________________________________________________________
SAP AG
252
SAP System
______________________________________________________________
11.11.3 MAP: Attributes
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) master data attributes can be used for
displaying in manual planning and as operands in formula groups. After selecting a planning level during
the design of the scenario, the fields in the relevant master data table can be assigned to the planning level
concerned for display purposes in manual planning. Numerical fields can also be used as operands in
formula groups.
In addition, customers can also implement their own attributes for use in manual planning. The attributes
can be ready for input and can also be used in formulas from formula groups.
Effects on Customizing
After the upgrade, existing planning scenarios can continue to be used as before. In the standard system,
the new planning functions will not be used at first. They can, however, be made productive by using a
standard network for the design of planning scenarios.
Customer-defined attributes can be implemented using BAdIs.
11.11.4 MAP: Data targets for the BW Interface
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can store actual data read from the SAP BW
in the MAP database table not only for all planning steps that have the BW indicator set, but you can also
limit the data to certain selected planning steps.
There are two advantages to this:
o
By choosing individual planning steps, you can keep the dataset that has to be read from the BW
and stored in the MAP database table to a minimum.
o
It enables greater flexibility when designing planning scenarios, as it is not necessary for the whole
planning level (for example, the sales organization) to be included, if only the data for one (for
example, Germany) of the values (such as France, Great Britain, USA) in the planning level
concerned is of interest. This can be illustrated using the purchasing organization as an example: In
previous releases, the data for all purchasing organizations had to be read in and stored in the
relevant database table.
11.11.5 MAP: Calculation Sequence in Formula Groups
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can determine the sequence for
calculating formulas in formula groups more specifically when setting up planning layouts. This is
significant when the formula groups contain different formulas, and the result of one formula is used
______________________________________________________________
SAP AG
253
SAP System
______________________________________________________________
directly in another formula. Up to Release 46C, the calculation sequence could only be determined by the
formula type (arithmetic formula, range of coverage calculation, value of the previous period) and the
alphabetic order of the left hand side of the formulas. However for formulas of type "arithmetic formula"
and "value of the previous period", users can enter a number, which will determine the calculation
sequence (within a period).
Effects on Customizing
No Customizing is required. The existing formula groups are calculated in the same order as before. The
system will only change the sequence of the formulas when you enter values for the calculation sequence.
11.11.6 MAP: New authorization object W_WXP_HIER
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can manage authorizations for the
planning hierarchy as well (at planning scenario level and planning hierarchy version level). This
function can, for example, be used to prevent unauthorized changes to the planning hierarchy.
Effects on System Administration
No action is necessary to be able to use this function. Every user has full authorization for the planning
hierarchies as standard.
11.11.7 MAP: New Authorization Object W_WXP_LAY
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), it is not only possible to manage
authorizations for planning at planning step level, (compare object W_WXP_PLAN), but also at the
detailed level of the planning layout and the manual planning variant. This function can, for example, be
used in order to only give certain users access to layout-specific functions, such as article planning or
color planning.
In addition, not only can authorizations be given or withheld for "planning functions" such as displaying
or changing planning data, but also for creating or changing the planning layout itself.
Effects on System Administration
The new authorization object does not have any effect on existing authorizations. It is only if you want to
grant authorizations at planning layout level or for creating planning layouts that you need to maintain
these for the new authorization object.
11.11.8 MAP: Blocking Data Cells and Changing Row Totals in Manual Planning
Use
______________________________________________________________
SAP AG
254
SAP System
______________________________________________________________
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), two new related functions have been
included in manual planning for planning layouts with simple key columns.
1.
Blocking: Individual data cells can be "blocked" against manual changes or automatic changes
resulting from total cells being divided.
2.
Changing row totals: Normally, row totals are calculated and displayed automatically by the
system. It is now also possible to change these total values manually. Changing a total value causes
the new total to be shared out amongst all the data cells that are involved in the calculation and are
not blocked. In the process, the proportions of the individual cell values are retained. The user can
also block total cells. Increasing the value in a data cell, for example, causes the values of all the
other cells that are not blocked to be reduced in order that the total value remains the same.
11.11.9 MAP: Generic read module
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), a generic read module (RFC-enabled
function module) is available. You can use this module to call planning data and to use this data in a
customer-specific context. The module extracts selected key figures from the basis scenario/step.
11.11.10 MAP: Material Planning and Characteristics Planning
*Short text
MAP: Material Planning and Characteristics Planning
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110) the functions for processing two planning
units in manual planning have been improved. These planning units are materials, particularly generic
materials, and classification system characteristics. These improvements are particularly useful for
planning in the fashion industry, where the planning of generic materials and classification system
characteristics is very important.
o
Material planning: You can now not only plan key figures for a material but also the master data for
the material itself. The user can use the following functions from the planning screen:
-
Create a new material and its planning on the fly. If the user also wishes to plan the
classification system characteristics (for example, color), they can assign a value set for the
characteristic directly to the new material.
-
Include an existing material in the planning layout on the fly. Just as when creating a new
material, the user can also assign any number of characteristic values to the existing material.
-
Remove a material from the planning layout
-
Jump directly to the standard maintenance of the material master data
-
Change the material type of a material (-> "Activate" a planned material)
______________________________________________________________
SAP AG
255
SAP System
______________________________________________________________
o
Automatically create material variants for a generic material based on its planned characteristic
value assignments
Plan classification system characteristics (for example, color): From the planning screen, the user
can use the following functions:
-
Include characteristic values (for example, colors) in the planning layout and plan this on the
fly
-
Remove characteristic values from the planning layout
-
Replace one characteristic value with another but keep the plan data belonging to it (for
example, "dark green" instead of "dark blue")
-
Automatically generate all variants for a certain generic material and characteristic value
Effects on Customizing
After the upgrade you can continue to use existing planning scenarios just as before. In the standard
system, the new planning functions will not be used at first. They can, however, be made productive by
using a standard network for the design of planning scenarios.
11.11.11 MAP: Simplification of the Transport of Planning Scenarios and
Layouts
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the transport of planning scenarios and
layouts has been simplified by the following three factors:
o
When transporting a planning layout, the system automatically transports the manual planning
variants that are assigned, including the Excel layouts.
o
The order in which planning layouts and scenarios are imported into a target system no longer has
any consequences.
o
When using a network for entering planning scenarios, the system recognizes any inconsistencies
caused by incorrect transports and provides help for repairing them.
Effects on Customizing
The separate report RWIS_PLAN14 ('Transport of Manual Planning Variants') is contained in report
RWIS_PLAN04 ('Transport Link Planning Layouts') and is therefore no longer required.
11.12 LO-AB
Agency Business (Global Trade)
11.12.1 Updating of Business Volume in Customer Settlements
Use
______________________________________________________________
SAP AG
256
SAP System
______________________________________________________________
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the customer settlement
document in agency business to update bonus-relevant business volumes for subsequent settlement in
Purchasing (MM-PUR-VM-SET).
When you generate customer settlements from single settlement requests, the system updates the business
volumes that are relevant to subsequent settlement and posts the provisions for accrued income based on
the document conditions in the customer settlement. The system determines the condition records for the
subsequent settlement independent of the settings in the copying control (from the single settlement
request to the customer settlement).
Effects on System Administration
In the sales area data of the customer master, there is a new indicator - Document Index Active - that is
the same as the indicator in the vendor master. If you want to use the subsequent updating of business
volume in the customer settlement, you have to set this indicator for all the customers for whom you
expect retroactive rebate arrangements in the course of the year.
Note that this indicator is only valid for customer settlements. If you want to include single settlement
requests in the subsequent updating of business volume too, you must also set the indicator, Subsequent
Update in Accordance with Indicator in Customer Master in Subsequent Settlement Control
(transaction WMN9).
Effects on Customizing
In Subsequent Settlement in Customizing, you can enter the residence time for archiving for the
document category, Customer Settlement.
In Customizing for billing types under Agency Business, you can use the Additional Item Data field to
include purchasing condition records (especially condition records from subsequent settlement) in pricing
in the customer settlement. If you set this indicator, the system determines the relevant data (purchasing
organization, invoicing party, different invoicing party) from the single settlement request. Otherwise the
fields are empty during the price determination in customer settlement, and condition records that relate
to these fields are deleted from the price determination.
11.12.2
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can use new functions for document lists
in Agency Business.
Use the cancel function to cancel the following documents:
o
Settlement request lists
o
Posting lists
o
Remuneration lists
Use BAPI BAPI_SETREQSLIST_COPY_AND_ADD to copy and enhance:
o
Settlement request lists
______________________________________________________________
SAP AG
257
SAP System
______________________________________________________________
11.12.3 Customer Settlement
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) Agency Business contains a new document
category "Customer Settlement". This new document category can be used instead of the posting list for
customer settlement.
You can generate the customer settlement document from the settlement request list. In doing so, the
system groups all single settlement requests into a single settlement document. Price determination is run
for each individual item in the customer settlement document. The currencies for the single settlement
requests can differ from the currency of the customer settlement document.
Using the customer settlement document, the system posts the receivables or payables to the customer.
Furthermore, the system updates the data to the Logistics Information System (LIS) or to SAP Business
Information Warehouse (SAP BW).
Using the customer settlement document, you can generate one or more remuneration lists.
You can archive customer settlement documents using archiving object WCI.
Effects on Customizing
In Customizing for Payment Types under Agency Business you can use field customer settlement
type to select a suitable billing type for the customer settlement document.
In Customizing for billing document type under Agency Business you can use field additional item
data to be able to include purchasing condition records (in particular, condition records for subsequent
settlement) in price determination for the customer settlement. If you set this indicator, the system
determines the relevant data (purchasing organization, invoicing party, alternative invoicing party) based
on the single settlement requests. In all other situations, the fields are left initial during price
determination in the customer settlement and condition records relating to these fields are removed
during price determination.
11.12.4 Expense Settlement
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) Agency Business contains a document
category for settling expenses with a customer.
The expense settlement document is a single document for which no preceding document (in particular a
sales order) is required in the system. You can create an expense settlement manually or, alternatively, in
expense managment in SAP Global Trade.
You enter the article and the site at item level. The system runs price and account determination. Account
determination takes place in the expense settlement document (in contrast to other agency documents) in
the same way as in Sales and Distribution (SD).
The expense settlement document can then be used to create remuneration list(s).
______________________________________________________________
SAP AG
258
SAP System
______________________________________________________________
The data from the expense settlement document can be updated in the Logistics Information System
(LIS) or in SAP Business Information Warehouse (SAP BW).
11.12.5 Interface to SAP Business Information Warehouse
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), there is an interface between Agency
Business and SAP Business Information Warehouse (SAP BW). This means that you can use the
technology of SAP BW to make a statistical analysis of agency business data. Doing this leads to an
improvement in how mass data is handled and in the performance of data updating.
The following documents are relevant for updating statistical data:
o
Individual invoices to the vendor
o
Single settlement reuquest
o
Remuneration lists
11.12.6 Item Category in Agency Documents
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can assin an item category to an item
contained in an agency document. The item category differentiates between a standard item and a return
item. You can handle both standard items and return items in a single agency document.
11.12.7 LO-AB-RS
Remuneration settlement
11.12.7.1 Remuneration List Enhancement
Use
Use remuneration lists to group conditions in agency documents and bill them to your business partners at
a later date.
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110) you can use the remuneration list
enhancement that can be used as an alternative to the previous remuneration list function. The following
are possible with the remuneration list enhancement:
o
Create multiple remuneration lists from a single agency document.
o
Create remuneration lists for vendors and customers.
o
Create remuneration lists got a remuneration recipient that differs from the partner stated in the
agency document (for example, customer association).
______________________________________________________________
SAP AG
259
SAP System
______________________________________________________________
Each remuneration list to be created based on an agency document for a remuneration list partner (vendor
or customer) is represented by a condition type group. Important data for the remuneration list is assigned
to the condition type group, for example:
o
Relevant condition types
o
Remuneration list types
o
Rules for determining the remuneration list date
o
Rules for determining the remuneration list recipient
When an agency document is created, the remuneration list data is determined for the condition type
groups required by the billing type. The remuneration list data is updated to a specific table. The system
defines the document required using the table and the relevant selection criteria.
The remuneration lists created with this enhancement are handled in the same way as the remuneration
lists created using the standard functionality and are processed using the same transactions and reports.
Only the creation process for the remuneration list is different.
Effects on Existing Data
The remuneration list enhancement does not affect existing data. The enhancement can only be used with
agency documents created after the remuneration list enhancement was activated.
Effects on Customizing
The following activities must be processed in Customizing for the remuneration list enhancement in
agency business:
o
Define Condition Type Groups and Assign Condition Types
o
Define Remuneration List Groups and Assign Type Groups
o
Assign Billing Types to Remuneration List Groups
See also
For more information, see the documentation for the following BAdI:
Erweiterungen für erweiterte Vergütungslistenerstellung
11.13 LO-GT
Global Trade
11.13.1 LO-GT-TC
Trading Contract
11.13.1.1 Open order/Open delivery
Use
As of SAP R/3 Enterprise Global Trade 1.10 (EA-GLTRADE 110), there is a new report called open
order/open delivery, which used in a trading contract. The open order quantity refers to the orders that
have not been included in the follow-on delivery document of the trading contract. The open delivery
______________________________________________________________
SAP AG
260
SAP System
______________________________________________________________
quantity refers to the orders that have been delivered but have not yet been billed. It provides a report at
each item level. You can get the information on open quantities and values for both sales and purchasing
in one screen. When calling up the report for a trading contract, the system also reads the information
from the follow-on logistics documents, so, you only need to access the trading contract to get a general
picture of how many orders are open for the trading contract and how many are open for delivery.
For example, in a simultaneous sales and purchasing contract if the open quantity is the same as the
contract quantity, no follow-on processes have been executed. When the open delivery quantity is half of
the contract quantity, then half of the goods have been delivered. When the open order/open delivery is
zero, the contract for that item has been fulfilled.
The way in which the open value is calculated depends on the Customizing settings.
Effects on Customizing
To execute the open order/open delivery report in the trading contract, you must maintain the
Customizing settings for calculation. SAP provides sample function modules in the standard system and
you can maintain your own calculation method by adding new function modules. For more information,
see: Customizing for open order/open delivery.
11.13.1.2 Profit Simulation
Use
As of SAP R/3 Enterprise Global Trade 1.10(EA-GLTRADE 110), there is a new report called profit
simulation that is used in a trading contract. It provides an online profit simulation during trading contract
processing, taking all relevant pricing elements such as purchase price, sales price, expenses, surcharges
and discounts into account. The report is also available for follow-on logistics documents such as
deliveries.
The profit simulation is useful when, for example, you want to calculate a proper sales price, while
considering all expenses and surcharges and, at the same time, to keep an eye on the total profitability of
the entire simultaneous sales and purchase. You can use profit simulation to monitor detailed price
information for each item, then you can adjust the price of the item. You cannot change prices from
within the profit simulation report. If you must make any changes, you must go to the price overview or
expense view.
When executing the profit simulation report, you can choose the currency and the exchange rate for the
report. There are two default choices,
o
Use customized currency and todays rate
o
Use home currency and document rate
Alternatively, you can customize both settings to suit your requirements.
The way in which profit is calculated is freely customizable. For example, you can calculate the estimated
profit based on the sales price, the purchase price and all the expenses relevant for the trading contract.
SAP provides sample function modules for calculating the profit. You can create your own profit
calculation by creating new function modules.
The profit simulation report is only useful when the trading contract is a simultaneous sales and
purchasing contract.
______________________________________________________________
SAP AG
261
SAP System
______________________________________________________________
Effects on Customizing
In addition to customizing settings for profit simulation, customizing settings for Sales and Distribution
(SD), Material Management (MM), pricing in retail (Retail) and in standard R/3 Enterprise must also be
maintained properly. For example, if you plan to use the profit simulation to calculate the estimated profit
including sales price, surcharges, expenses, and purchasing price, then you must also maintain all the
customizing settings for pricing and expenses in trading contract. For more information, see: Pricing.
If you plan to execute the profit simulation for a logistics document, you should also maintain the
customizing settings for a logistics document. For more information, see: Profit simulation for logistics
document.
11.13.1.3 Trading Contract (TC)
Use
As of SAP R/3 Enterprise Global Trade 1.10 (EA-GLTRADE 110), a new document exists called a
Trading Contract. In a trading company, one person or one department usually carries out both the sales
and purchasing processes . By using a Trading Contract, you can maintain all data for both sales and
purchasing contracts simultaneously in one document. This helps cut the administrative costs associated
with order processing. As all the data, including price and expenses information for the sale and purchase,
is entered in the trading contract, it is easy for you to assess a precisely planned profitability.
If sales and purchasing are carried out separately, the trading contract can be used as a one-side contract,
that is, as a sales contract or a purchasing contract. You can use Position Management to control material
positions. In addition, the trading contract can be used as a pre-contract or a long-term contract for sales
and purchasing activities. You also can create a trading contract with reference to a pre-contract or
long-term contract.
The trading contract is used as a base document for further processes, for example:
o
You can generate sales orders and purchase orders with the trading contract.
o
You can create follow-on delivery documents with reference to the trading contract by using the
Trading Execution Workbench (see also Release Note Trading Execution Workbench).
o
You can create expense documents with reference to the trading contract (see also Release Note
Trading Expenses).
You can track the status of all the follow-on logistics processes by displaying the extended document
flow.
By differentiating trading contract types, you can easily control different types of business, such as
imports and exports. For example, you can create a shipping instruction, a customs clearance request for
an export deal; a discharge request or an import shipment request for an import deal. Multiple currencies
can be used in the trading contract and a statistical currency exists in the trading contract.
Status control in the trading contract allows you to manage key processes for the entire trading contract.
For example, when creating contracts, you can have the statuses waiting for approval, approved and so
on. You can maintain the status based on your own business process and use your own business terms.
Different trading contracts can have different statuses.
______________________________________________________________
SAP AG
262
SAP System
______________________________________________________________
Effects on Existing Data
When you release the trading contract, the system automatically generates a follow-on sales order and
purchase order.
You cannot change any sales or purchase data with standard SD/MM transactions. Instead, you must
make the changes to the trading contract and then re-release it. The changes will then be passed on to the
follow-on sales or purchase order.
Effects on Customizing
In addition to Customizing settings for all functions processed within the Trading Contract component,
you should also maintain Customizing settings for Sales and Distribution (SD) and Material Management
(MM), Pricing in Retail (Retail) in the standard R/3 Enterprise System. For example, if you plan to use
the trading contract as a simultaneous sales and purchasing contract, you should also maintain all
Customizing settings for sales order processing and purchase order processing. You must also maintain
Customizing settings for related retail pricing.
11.13.2 LO-GT-TE
Expenses
11.13.2.1 New Screen for Trading Expenses
Use
As of SAP R/3 Enterprise Global Trade 1.10 (EA-GLTRADE 110), a new expense maintenance
screen has been implemented, that makes data entry easier to perform. In this screen, you enter parameter
combinations made up of business-oriented parameters instead of selecting a document type directly.
Each item line corresponds to a single vendor billing document. You can jump to the document from the
expense maintenance screen. When you save the screen, account posting is executed. The vendor billing
document for the trading expenses can be seen in the document flow.
Effects on Customizing
You can select the expense maintenance method in Customizing. SAP offers two options for determining
the document type:
1.
Document type is determined using parameters combinations, which are determined dynamically
2.
Document type is selected directly
This new screen is available only if you select the first option. For more information, see Determination
Method for Vendor Billing Document Type
11.13.2.2 Trading Expenses
Use
As of SAP R/3 Enterprise Global Trade 1.10 (EA-GLTRADE 110), the Trading Expenses function
has been enhanced. Now you are able to capture any costs that are incurred along with contract
______________________________________________________________
SAP AG
263
SAP System
______________________________________________________________
processing. You can handle various kinds of costs and commissions, which may be realized at different
times and posted to different accounts.
In terms of process and account posting, expenses are classified into two categories: planned expenses
and unplanned expenses. Planned expenses are treated as pricing conditions in contract pricing. The data
entered can be referrenced when you post to the account. Unplanned expenses can be maintained during
or after logistics processing. These are posted directly to the account via vendor billing documents.
To allocate an expense to the appropriate logistics document, there are two possibilities. You can
maintain the expenses both during and after the logistics document is processed. In the first case, the
expense maintenance screen is called directly via the logistics document. In the latter case, you must
select the document to which the expenses are to be allocated.
These expenses are then distributed to the original trading contract item. When you enter the actual
expense data, the system automatically finds the original contract item and assigns the expense value
according to the distribution rule. The distributed value and the original contract item data are stored in
the vendor billing document.
Effects on Customizing
Since the planned expenses are included in the contract pricing schema, the pricing conditions for
expenses must be included in the assigned contract pricing schema.
For more information, see:
o
Define Calculation Schema (Purchase Expense)
o
Define Calculation Schema (Sales Expense)
o
Assign Condition Type Group to Trading Contract Type
11.13.3 LO-GT-TEW
Trading Execution Workbench
11.13.3.1 Trading Execution Workbench (TEW)
Use
As of SAP R/3 Enterprise Global Trade 1.10 (EA-GLTRADE 110), there is a new tool called the Trading
Execution Workbench (TEW). It provides a central cockpit where traders can process all steps needed to
fulfill a trading contract and generate all necessary follow-on documents. In addition, TEW automates a
large part of the data entry, making processing quicker, easier, and more error-free. Smart functions
anticipate which tasks you want to perform and suggest the appropriate source and target documents
automatically.
The TEW uses trading contracts as a basis for the entire business process (for example, creating sales
orders, purchase orders, deliveries, customs clearance forms, and so on). You can use a trading contract
as the source document for all subsequent follow-on documents. The document flow diagram keeps track
of how far a contract has progressed, and is automatically updated whenever you create a new follow-on
document. You can affect how the document flow appears by setting the display parameters on the TEW
initial screen (for example, whether all documents should be displayed or not), and can change the
settings whenever you want.
______________________________________________________________
SAP AG
264
SAP System
______________________________________________________________
In TEW, each business transaction is called a business process step, representing a specific SAP business
object, such as an outbound delivery or purchase order. You define your own business process steps in
Customizing: Define business process step, then assign action classes to them to perform the specific
logic required for those transactions. Furthermore, by specifying a combination of steps, you can build a
business scenario; for example, when the trader creates a delivery, you can have the system automatically
generate both a delivery document and shipping notification. SAP provides basic business mapping flows
and classes that you can use as templates. You also can design new business scenarios based on your own
business requirements.
Effects on Existing Data
If you create a document in TEW, you cannot further process it using standard SD/MM transactions.
Conversely, if you create a standard SD/MM document, you cannot process it in TEW. This is because a
TEW document can contain additional data that the standard transactions do not recognize.
Effects on Customizing
TEW is highly flexible and highly customizable to support different lines of business (for example, steel,
oil, food), allowing you to mirror your own business procedures as closely as possible. In addition to
Customizing settings for the workbench itself, you must maintain Customizing settings for all functions
processed in TEW. For example, if you plan to have traders process sales orders in TEW, then you must
maintain all Customizing settings for sales order processing. You must also maintain the organizational
structures for both sales order processing and purchase order processing.
11.13.4 LO-GT-PM
Position Management
11.13.4.1 Association Management
Use
Association Management provides an audit trail, linking all the documents that describe the transactions
that take place throughout the life of a trading contract.
Association Management enables you to create an actual link between document items in sales and in
purchasing. It helps you to determine the current item status. All document items with a portfolio record
can be used with the association process. When you create a link, the system searches for the appropriate
partner item based on the assigned portfolio. One item on the sales side can be associated with multiple
items on the purchasing side, and vice versa. Once an association is established, its history is updated
automatically as documents are processed. The links can be changed up until the time the contract is
complete.
Once a portfolio record has been assigned to a contract item, you can create an association link within
contract processing. After the contract is processed initially, you still can maintain association links
during subsequent logistics processing. This can be done independently or using the logistics document
process.
o
If you maintain an association independently, you must use the special business process mode for
the association in the Trading Execution Workbench. You maintain the association link in the
existing document.
______________________________________________________________
SAP AG
265
SAP System
______________________________________________________________
o
If you maintain the association with the logistics document process, the system automatically calls
the association maintenance function before you enter the document maintenance screen. The
system will not allow you to proceed until the association link has been confirmed. Only associated
items can be processed to the next step.
Effects on Customizing
In addition to the Customizing settings for Association Management, you must maintain additional
parameters in the contract type and the TEW type. For more information, see:
o
Contract Types
o
Maintain Trading Execution Types
11.13.4.2 Portfolio Management
Use
In large trading companies, documents and data proliferate rapidly. Portfolio Management is a tool for
cataloging commodities and other items by a self determined group. This grouping improves trading
contract processing.
As of SAP R/3 Enterprise Global Trade 1.10 (EA-GLTRADE 110), you can decide dynamically
which item characteristics to assign when processing a contract. You create the portfolio type in
customizing according to certain key combinations and validity periods in advance. When the material
and its quantity have been defined in a contract, the system finds the appropriate portfolio record using
your defined access sequence that enables the system to search more efficiently. Once the portfolio has
been confirmed and the contract released, this assignment cannot be changed during the follow-on
logistics document processes.
The portfolio is also used for selecting the association partner. When you create a new association link,
the system searches the open partner items based on the assigned portfolio record. The system allows you
to freely define the association determination strategy in Customizing.
Effects on Customizing
In addition to the Customizing settings for Portfolio Management, you also must check Customizing for
the trading contract type. Because the portfolio is assigned to the contract item, the portfolio
determination logic also should be assigned to the contract type.
For more information about the trading contract type, see Contract Types
11.13.4.3 Position Management
Use
As of SAP R/3 Enterprise Global Trade 1.10 (EA-GLTRADE 110), a new concept called Position
Management has been adopted. Position Management helps you to reduce selling losses and optimize
stock balances.
______________________________________________________________
SAP AG
266
SAP System
______________________________________________________________
The material positions are classified into three basic types: short positions, long positions and associated
positions.
o
A long position is one where the purchasing quantity and value are not associated with sales
quantities.
o
Aa short position is one where the sales quantity and value are not associated with purchasing
quantities.
o
An associated position means the item quantities are already associated.
These positions can be further subdivided according to your own business requirements.
Once a material position has been decided in a trading contract, the system monitors its transition until
the item has been completely processed. To define a material position, the system first assigns a dynamic
key called a portfolio to the contract item. It then searches for the appropriate partner item based on this
key. After the material position has been defined in the contract, the system updates the position
according to document processing.
A standard report is provided for monitoring the item position. This report shows you the extent to which
the open item has been processed and gives you a status overview.
Effects on Existing Data
Since the portfolio record is assigned in the trading contract, you should map the trading contract as the
basis of your business process. In addition, you need to process the document using the Trading
Execution Workbench (TEW), since the item position can only be transferred to the follow-on document
correctly using the TEW.
Effects on Customizing
To monitor the item position correctly, all further processes should be executed via the TEW. There are
two sub-modules under position management: Portfolio Management and Association Management. You
also need to ensure that these three areas are customized correctly:
o
Trading Execution Workbench (TEW)
o
Portfolio Management
o
Associaton Management
11.14 LO-HU
Handling Unit Management
11.14.1 Business Add-Ins for Handling Unit Management (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following Business Add-Ins (BAdIs) are
available in the area Handling Unit Management.
Effects on Customizing
To activate a Business Add-In, you must create an active implementation. To do this, go to Customizing
______________________________________________________________
SAP AG
267
SAP System
______________________________________________________________
for Logistics - General and choose Handling Unit Management --> System Modifications --> Business
Add-Ins in Handling Unit Management -->
o
Business Add-In for Determining Allowed Packaging Material
o
Business Add-In for Automatic Packing
o
Business Add-In für Enhancements to HUTransaction
o
Business Add-In for Enhancements to HU Monitor
o
Business Add-In for General Checks and Actions in HUM
o
Business Add-In for the Check, Whether Packing is Allowed for the Item
o
Business Add-In for Reducing the Material Quantity to Pick
o
Business Add-In for Label Printing
o
Business Add-In for Data Updates
o
Business Add-In for Enhancements to Packing Instruction Function
o
BAdI for Packing Instruction Determination Using Customer's Own Fields
o
Business Add-In for Customer-Specific Subscreen in Packing Instruction
______________________________________________________________
SAP AG
268
SAP System
______________________________________________________________
12 SD
Sales and Distribution
12.1 Country Version India in Standard R/3 System
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), Country Version India is no longer delivered as
an add-on but as part of the standard R/3 System.
Integration of functions in the SAP Easy Access menu
The functions for withholding tax have been integrated into the SAP Easy Access menu, under
Accounting -> Financial Accounting -> Accounts Payable -> Withholding Tax -> India and
Accounting -> Financial Accounting -> Accounts Receivable -> Withholding Tax -> India.
You can access all other functions using the area menu J1ILN, which you can call from the SAP Easy
Access screen using the transaction code J1ILN.
Country Version India Implementation Guide
The Country Version India Implementation Guide (IMG) has been integrated into the standard Reference
IMG (see Changes to Structures for Country Version India).
Release Notes
You can access release notes from previous add-on releases using the links below.
SAP Library Documentation
The SAP Library documentation for Country Version India is also delivered on the standard SAP Library
documentation CD (see below).
New and Changed Functions
For information about new and changed functions for Country Version India, see the other release notes
for this release.
Effects on Existing Data
You do not need to change any data.
Effects on Customizing
IMG activity
What to do
Activate Country Version India for Specific Fiscal Years Delete the entry ZIND and create a new
entry for IND.
See also
SAP Library -> Financials or Logistics -> Country Versions -> Asia-Pacific -> India.
Release Notes from Country Version India Add-On (FI)
Release Notes from Country Version India Add-On (SD)
Release Notes from Country Version India Add-On (MM)
______________________________________________________________
SAP AG
269
SAP System
______________________________________________________________
12.2 Condition-Based Tax Calculation (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), a new method for calculating taxes in Brazil
is available, which makes use of the standard condition technique. Tax rates, tax laws, and special
indicators that influence whether tax line items are included in the nota fiscal are all stored in the system
as condition records. An additional tax calculation procedure, TAXBRC, is delivered for this new
method, in addition to the existing one for Brazil, TAXBRJ.
Effects on Existing Data
You can continue to calculate taxes using the former method: when the system processes the tax
procedure assigned to the country (TAXBRJ), it calculates the taxes externally by calling function
module J_1BCALCULATE_TAXES. We do, however, recommend that you assign the new procedure
TAXBRC and use the condition-based tax calculation functions, as it enables you to flexibly adapt the tax
calculation logic to cover new legal requirements or special customer needs.
You will need to migrate your existing tax rate table entries to condition records, which you can do
directly from the Tax Manager's Workplace described below. You can check all tables and subsequently
convert the entries, whereby the system generates condition records. After the initial migration, each time
you create or change a tax rate table entry, the system automatically generates a condition record as
needed.
Effects on Customizing
If you want to employ the new condition-based tax calculation, you need to activate it and carry out all
related Customizing activities, under Financial Accounting -> Financial Accounting Global Settings
-> Tax on Sales/Purchases -> Basic Settings -> Brazil -> Condition-Based Tax Calculation, all of
which are new:
o
Activate Condition-Based Tax Calculation
o
Map MM Tax Values to Nota Fiscal Fields
o
Map SD Tax Values to Nota Fiscal Fields
o
Map MM Tax Laws to Nota Fiscal Fields
o
Define Internal Codes for Tax Conditions
o
Assign Internal Codes for Tax Conditions to Condtion Types
o
Assign Tax Rate Tables to Condition Tables
In addition, you need to assign the new tax calculation procedure TAXBRC to the country in
Customizing, under Financial Accounting -> Financial Accounting Global Settings -> Tax on
Sales/Purchases -> Basic Settings -> Assign Country to Calculation Procedure.
A new Customizing tool called the Tax Manager's Workplace is available that enables you to make all
tax-related settings for Brazil. You access it under the same path as above through Tax on
Sales/Purchases, then Calculation -> Settings for Tax Calculation in Brazil -> Access Tax
Manager's Workplace , or alternatively by entering transaction J1BTAX. You can use the Tax Manager's
______________________________________________________________
SAP AG
270
SAP System
______________________________________________________________
Workplace regardless if you use condition-based tax calculation; it simply brings all tax activities to a
single transaction (only the Migration, Nota-Fiscal Mapping, and Condition Mapping options under the
Condition Setup pulldown menu are relevant only for condition-based tax calculation).
12.3 Changes to Structures for Country Version India
Use
As of SAP R/3 4.7, Country Version India is no longer delivered as an add-on, but forms part of the
standard system.
SAP has discontinued the Country Version India Implementation Guide (IMG) and has added its
activities have been added to the standard Reference IMG as follows:
Activities relating to withholding tax are now located in Customizing for Financial Accounting (FI),
under Financial Accounting Global Settings -> Withholding Tax.
Activities relating to excise duty and excise invoices are in Customizing for Logistics - General, under
Tax on Goods Movements -> India.
As far as the activities under Preparatory Activities are concerned, two of them (Activate Country
Version India for Accounting Interface and Activate Processes) are no longer relevant and have been
removed from the IMG entirely. The activity Execute Country Installation Program is already included in
the standard IMG under the name Localize Sample Organizational Units. And the other two activities
(Activate Country Version India for Specific Fiscal Years and Activate Business Transaction Events)
have been added to the standard IMG.
For information about other changes to the IMG relating to changes in the functions in Country Version
India, see the other release notes.
12.4 Exports Under Excise Regulations (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), Country Version India allows you to process
exports and deemed exports under excise regulations. New functions for exports have been added as
follows:
o
You can create, change, display, and cancel excise bonds. When the bond is no longer of use, you
can also close it.
o
There are various transactions for creating and processing ARE-1s.
o
Reports include two statutory reports, the Running Bond Report and the Export Report.
o
To track bonds we have provided a Bond Summary Report. Another transaction, the ARE
Document Ageing Analysis, allows you to track ARE documents according to their current status.
The following new functions are also offered for deemed exports:
______________________________________________________________
SAP AG
271
SAP System
______________________________________________________________
o
You can capture, change, display, cancel, and close licenses.
o
There are various transactions for creating and processing ARE-3s.
o
To track licenses, you can use the License Summary Report; and to track ARE-3s, use the ARE
Document Aging Analysis.
Finally, SAP has also provided a new role containing all excise bonding activities, Bonding Clerk
(technical name: SAP_CIN_BONDING_CLERK).
Effects on Customizing
To set up the solution, carry out the following IMG activities:
IMG activity
What to do
Make Settings for ARE-1 Procedure
Make the basic settings for processing exports.
Make Settings for ARE-3 Procedure
Make the basic settings for processing deemed
exports.
Maintain License Types
Maintain the various license types for when you come
to enter your customers' deemed export licenses.
Maintain Output Type
Check the output type supplied with the SAP System.
Specify Printers
Specify which printers to print out the ARE
documents on.
Maintain Postal Addresses
Enter the addresses of your local excise departments,
to be printed on the AREs.
Maintain Excise Groups
Enter each excise group's local excise department.
Maintain Series Groups
Enter a default customs department for each series
group.
Maintain Number Ranges
Maintain number ranges for bonds (number range
J_1IBOND), ARE-1s (J_1IARE1), licenses (J_1ILIC), and ARE-3s (J_1IARE3).
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Sales and Distribution
(SD) -> Exports Under Excise Regulations.
12.5 Release Notes from Country Version India Add-On (SD)
Use
The Release Notes from Releases 3.0A and 4.0A of Country Version India for Sales and Distribution
(SD) are listed below. For Release Notes from earlier releases, see the alias globalization in SAPNet,
and choose Media Center -> Country-Specific Documentation -> Country Version India - Release Notes.
Release 3.0A
o
Printing of Excise Invoice for Other Movements
Release 4.0A
______________________________________________________________
SAP AG
272
SAP System
______________________________________________________________
o
CENVAT Payment Can Be Done Immediately at the Time of Removal
o
Item Level Accounting Postings for Excise Invoices
o
Performance Improvements
o
Authorization for Excise Invoice Creation
o
Excise Invoices Can Be Created Based on Intercompany Billing Documents
o
Posting of CENVAT to Profitability Segments
o
Business Area Postings of Fortnightly Payments
o
Text Entry During Fortnightly Payments
o
Printing of Annexure of Excise Invoices
o
Enhancements to Automatic Creation of Excise Invoices
o
Default of Purchase Order Details to Depot Receipts
o
Entry of Cess During Capture of Excise Invoices in Depots
o
CVD Indicators Can Be Maintained for Depot Receipt
o
Suppplementary Excise Invoices at Depots
o
Supplementary Excise Invoice Selection During Depot Selection
o
Depot Stock Display
12.6 SD-MD
Master Data
12.6.1 SD-MD-CM
Conditions
12.6.1.1 Deleting Bonus Buys
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can delete bonus buys that were created
from the system.
Bonus buys that have been created have a limited validity period, however, they are still available in the
system. You can now select and delete bonus buys according to certain criteria.
1.
The system then displays the bonus buys available based on these specific criteria.
You can select the bonus buys using, for example, a promotion that uses the bonus buys, a bonus
buy category, a bonus buy type, or the type of condition target. You can also base your selection on
the validity period.
2.
You can then select which bonus buys you want to delete.
A tree is displayed that you can sort using different criteria (for example, created by, discount type,
promotion, and bonus buy).
______________________________________________________________
SAP AG
273
SAP System
______________________________________________________________
3.
The system transfers the deletion request to the POS systems to which it is linked.
The system deletes the bonus buy entries in all the relevant tables (KONBBYH, KONBBYPRQ,
KONBBYT, KONDN, KONDNS, KOTN*, STXH and STXL).
You can also delete bonus buys from the promotion maintenance. For this, the system preassigns the
bonus buy numbers and the appropriate promotion number in the selection screen of the delete program.
When you select bonus buys for deletion in the promotion, the system processes the selection screen of
the delete program in the background. For any other selections, the processing is done on the screen.
The promotion maintenance updates the relevant screen displays itself.
Effects on Existing Data
The system logs which bonus buys up until now were distributed among which stores. When you delete a
bonus buy, the deletion indicator is set for all the entries belonging to it. By selecting specific entries, the
deletion information can then be sent to the stores concerned.
You cannot archive bonus buys.
Effects on System Administration
When you delete bonus buys, the SAP System database and the POS systems' database must constantly
be kept closed to avoid the data being distorted.
SAP recommends you plan program BBY_POS_DELETE as a daily background job. If the expected data
volume is not too high, you can call the program directly from program BBY_DELETE.
See also
For more information, see the SAP Retail documentation (SAP Libraryk -> Logistics -> SAP Retail)
under Master Data -> Conditions -> Bonus Buy.
12.6.1.2 New Change Pointers for Condition Records (WIND)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you have the following additional options for
adjusting documents in condition changes:
o
Direct entries in the worklist after condition changes
o
Including additional data in an entry in the worklist
In the previous procedure, the entries were created in the worklist based on the change pointers for
condition changes (message type CONDBI) in worklist creation (transaction ME14). In the new
procedure, the change pointers are no longer needed. When a condition is changed, entries are created
directly in the worklist. This removes the previous step in the process of creating the worklist from
change pointers, which was very performance-intensive. In addition, you do not have to create change
pointers for condition changes if they are not going to be used in other processes.
The Customizing that was valid for the previous worklist creation and that defines which condition types
should be included in the worklist (table T6I1) is also valid for the direct entry. However, there are
additional filter options in the new procedure. You can define for each document category for which
types of condition changes (amount change, validity, pricing relevance) entries should be made in the
______________________________________________________________
SAP AG
274
SAP System
______________________________________________________________
worklist. There is also a BAdI that is dependent on the document category filter criterion with which
customer-defined filter criteria can be implemented.
The following example describes the options offered by the BAdI:
Due to changing purchasing conditions, perishable materials are regularly repriced in short time periods.
Therefore, sales prices do not need to be updated using the pricing worklist procedure. Use the material
type, in this case, as an additional filter criterion in the retail pricing application (document category 10).
When the basic purchase price of a perishable material is changed, the system does not create a worklist
entry for this document category due to the filter criterion that was implemented.
The additional data in a worklist entry consists of header data from the conditions with which you can
improve performance for the follow-on processing and of variable customer fields with which you can
carry out selective subsequent processing. You make settings in Customizing for filling the customer
fields (table T6I2S).
Effects on Existing Data
If you do not use change pointers for condition changes, the level of data for change pointers is reduced
considerably. A change pointer generally consists of several entries in table BDCP and BDCP2.
The following changes are made:
o
The width of table WIND increases from 45 to 262 bytes due to the additional tables.
o
The number of table entries in the worklist can be reduced due to the additional filter criteria.
o
Change pointers are no longer needed for message type CONDBI.
Effects on System Administration
The process step for creating the worklist from change pointers (transaction ME14) is no longer needed in
the new procedure.
The check for existing document indexes (table S111) that can be used in the previous worklist creation
must be implemented as an additional filter criterion in the BAdI (see example coding).
The migration of the worklist from the old to the new worklist entries is carried out using report
RMEBEMIG. The report enhances the entries that are available using information from the condition
records.
If you are converting from the old to the new procedure, a special adjustment procedure is required for
every document category. This procedure is described in each of the applications that use the new
procedure.
Effects on Customizing
Implement the new Customizing for the direct creation of worklist entries. If you are installing this for
the first time or if you have not yet used the document adjustment function for a certain document
category, set the indicator manually for migration and direct entry in Customizing. When converting from
the old to the new procedure, the indicators in the migration procedure are set automatically.
You also determine the types of condition changes for each document category as filter criteria for which
worklist entries should be created and how the variables should be filled.
Once you have made settings for direct entries in the worklist for all the document categories used, you
do not have to create change pointers from message type CONDBI. Deactivate message type CONDBI in
ALE Customizing.
______________________________________________________________
SAP AG
275
SAP System
______________________________________________________________
You can also carry out this deactivation using the migration report.
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Master Data -> Conditions ->Automatic Updating of Documents After Condition Changes.
12.7 SD-BF
Basic Functions
12.7.1 SD-BF-PR
Pricing and Conditions
12.7.1.1 Condition-Based Excise Determination in SD (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can calculate excise duties and sales taxes
applicable in India in sales documents using standard pricing procedures (condition-based excise
determination).
All excise duties and sales taxes are included in the pricing procedures themselves (not in tax
procedures).
We recommend that new customers follow this procedure.
There are four new pricing procedures:
Pricing procedure
JINFAC
JINEXP
JINDEP
JINSTK
Use
Sales from manufacturing plants
Export sales
Sales from depots
Stock transfers
For more details about the procedures, including which condition types are supplied, see the
documentation mentioned below.
Effects on Existing Data
Once you have made the Customizing settings below, assign the appropriate customer pricing procedures
to your customer master records.
Create condition records for all excise duties and sales taxes.
Effects on Customizing
IMG activity
What to do
Define and Assign Pricing Procedures
Copy the pricing procedures supplied, adjust them to
match your needs, and set up the pricing determination procedures.
See also
______________________________________________________________
SAP AG
276
SAP System
______________________________________________________________
SAP Library -> Logistics -> Country Versions -> India -> Sales and Distribution (SD) -> Pricing.
12.7.2 SD-BF-TX
Taxes
12.7.2.1 Condition-Based Excise Determination in SD (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can calculate excise duties and sales taxes
applicable in India in sales documents using standard pricing procedures (condition-based excise
determination).
All excise duties and sales taxes are included in the pricing procedures themselves (not in tax
procedures).
We recommend that new customers follow this procedure.
There are four new pricing procedures:
Pricing procedure
JINFAC
JINEXP
JINDEP
JINSTK
Use
Sales from manufacturing plants
Export sales
Sales from depots
Stock transfers
For more details about the procedures, including which condition types are supplied, see the
documentation mentioned below.
Effects on Existing Data
Once you have made the Customizing settings below, assign the appropriate customer pricing procedures
to your customer master records.
Create condition records for all excise duties and sales taxes.
Effects on Customizing
IMG activity
What to do
Define and Assign Pricing Procedures
Copy the pricing procedures supplied, adjust them to
match your needs, and set up the pricing determination procedures.
See also
SAP Library -> Logistics -> Country Versions -> India -> Sales and Distribution (SD) -> Pricing.
______________________________________________________________
SAP AG
277
SAP System
______________________________________________________________
12.8 SD-SLS
Sales
12.8.1 Evaluation of open sales documents according to US-GAAP guideline
SFAS 133.
Use
According to SFAS 133 - Accounting for Derivative Instruments and Hedging Activities - the balance
sheets to the market value must be prepared for open values in certain sales documents. Changes to the
market value should be taken into consideration in earnings in as far as they affect net income.
To support the selection of relevant documents, SAP provides report SDFAS133.
Further Information:
Report Documentation for SDFAS133
12.8.2 SD-SLS-SO
Sales Orders
12.8.2.1 Purchase Requisitions Generated from Sales Orders Update FM
(Changed)
Use
As of SAP R/3 Enterprise Public Services 1.10, a purchase requisition that is generated out of an SD
order line item creates a commitment line in Funds Management (FM). Budget can be assigned during
this update.
Effects on Existing Data
Existing purchase requisitions cannot be updated automatically. This means that the new function applies
only to newly created SD order lines.
Effects on Customizing
The purchase requisitions are treated as normal purchase requisitions in FM, so no special customizing is
needed.
12.8.2.2 SD Order Update in Funds Management (FM) (Changed)
Use
As of SAP R/3 Enterprise Public Services 1.10, billing-relevant SD orders update commitment line items
in FM.
Effects on Existing Data
______________________________________________________________
SAP AG
278
SAP System
______________________________________________________________
Existing SD orders can be rebuilt using program RFFMR07. You can access this in the Implementation
Guide by choosing Public Sector Management -> Funds Management Government -> Actual and
Commitment Update/Integration -> R/3 Internal Data Transfer -> Rebuild -> Rebuild FM Data for SD
Orders.
Effects on Customizing
The function is active in all the FM update profiles. No special customizing is needed.
12.9 SD-BIL
12.9.1 SD-BIL-IV
12.9.1.1 SD-BIL-IV-SM
Billing
Processing Billing Documents
Expense-Related Billing
12.9.1.1.1 Resource-Related Billing for Internal Orders With Revenues (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can process resource-related billing for
internal orders with direct revenues.
Up to now, resource-related billing was not possible for:
o
Sales documents with cost collectors
o
Service orders with revenues
o
WBS elements with revenues
Costs of internal orders could only be taken into account after they were settled to one of the objects in
resource-related billing.
Direct resource-related billing is now possible for internal orders with revenues using a sales document
without cost collectors. The process is based on the current solution for resource-related billing for
projects/WBS elements.
Effects on Customizing
To use the new functions, You must define in Customizing for sales document items that account
assignments are possible for internal orders. To do this, go to:
Control Sales-Order-Related Production / Sales Order Controlling
12.9.1.1.2 Archiving CO Line Items (Enhanced)
Use
______________________________________________________________
SAP AG
279
SAP System
______________________________________________________________
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can archive CO line items for orders and
projects when you bill them according to resources. In this way, you can significantly improve the
performance of your entire system.
Effects on Customizing
To be able to use the enhanced archiving function, you must enter residence times for the CO line items
and residence times for dynamic item processor sources (DIP sources). To do this, use the activity
Residence Time of the DIP Source in the IMG for creating quotations and billing.
12.9.1.1.3 Document Flow Evaluations of Resource-Related Billing (New)
Use
Document Flow Evaluations for Order
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can evaluate the document flow of billed
resources/expenses for a customer order, service order, contract, or project using a new program. The
program displays the billed, rejected, and open resources/expenses in a structure overview similar to the
expenditure view in resource-related billing. You can change the structure interactively. The billing
requests are listed in detail for each resource item. You can navigate to the billing request directly from
the result overview. Many other functions, such as filtering, enable you to make a flexible evaluation.
You evaluate the document flow using the transactions DP99A, DP99B and DP99C. These transactions
differ only in their selection options.
Document Flow Evaluation for Billing Request
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can display expenditures billed using the
document from a billing request or a credit memo request. When you use the transaction DP98, you
receive a corresponding list with all billed resource items for the billing request.
12.9.1.1.4 DI Processor (Enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the following enhancements for the dynamic
item processor (DI Processor) are available:
o
New Business Add-Ins (BAdIs):
Business Add-Ins (BAdIs) are developed for all customer enhancements. These BAdIs have the
same status as customer enhancements, which are still supported. Only the customer enhancement
AD010006 was migrated to BAdI SMOD_AD010006 and is available only as a BAdI.
In addition to the BAdI's with functions from customer enhancements, new Business Add-Ins are
also delivered.
o
Improved Control Options for Transferring Quantity and Costs
There are enhanced setting options available for transferring quantity and costs in material
determination of dynamic item processor profiles (DIP profile). The Transfer quantity indicator
______________________________________________________________
SAP AG
280
SAP System
______________________________________________________________
was therefore renamed as Transfer Quantity/Costs. You can specify that a resource item is
transferred to a sales and distribution document only if the costs do not equal 0, or only if the
quantity does not equal 0.
o
Increase of Material Determination Lines per DIP Profile
You can define more than 999 material determination lines in the DIP profile now.
o
New Analysis Program for DIP Profile
The consistency check used up to this point for DIP profiles is replaced with a new analysis
program. The new program checks for consistency in the profile. However, it still can check only
one profile per program run. Therefore, it now offers more information, enables you to print the
entire profile, and simulate material determination. To call up the new program, use Customizing or
the transaction ODP2.
If you want the check consistency for multiple profiles at the same time, you can use the existing
program found in transaction ODP2A.
Effects on Customizing
You find the setting options for the new functions in Customizing for Project System under the
activities Revenues and Earnings --> Integration with SD Documents --> Creating Quotations
and Project Billing --> Maintain Profiles for Quotations and Billing and Check Profile Settings.
See also
o
For more information about Business Add-Ins, see the Customizing (IMG) for Project System
under Develop Enhancements for Generating Quotations and Billing.
o
For more information about the improved control options for transferring quantity and costs, see the
documentation for the data element Transfer Quantity and Costs.
12.9.1.1.5 Billing Requests for Sales Order Items (Enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can create a common billing request for
multiple sales order items in the billing order items with service products business process. The
individual items can also have different forms of billing at the same time.
12.9.1.1.6 Collective Processing for Resource-Related Billing (Enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you have additional selection options for
sales orders or service orders when collectively processing resource-related billing. You can find this
improved collective processing in the following programs:
o
The transaction DP96 offers an improved selection of sales orders.
o
Die transaction DP97 extends the selection options for service orders.
______________________________________________________________
SAP AG
281
SAP System
______________________________________________________________
12.9.1.1.7 Static Processing of Resource-Related Billing (Deleted)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the static processing of resource-related
billing (transaction VA90), as announced for Release 4.5, is no longer available. Instead you can use the
dynamic processing (transaction DP90). It contains all of the required functions.
Effects on Existing Data
You must convert your existing orders to dynamic processing.
Effects on Customizing
You must convert your system to the dynamic processing of resource- related billing. You can do this
even before converting to SAP R/3 Enterprise for all Releases from 4.5B and above.
For more information about converting to dynamic processing, see Customizing (IMG) for creating
quotations and billing under Static Processing (Process before Release 4.5).
12.10 SD-EDI
Electronic Data Interchange
12.10.1 BAdIs in the Price Catalog
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), you can use the following Business Add-Ins
(BAdIs) in the price catalog:
BAdI PRIREADMATERIAL:
BAdI PRIREADMATERIAL is called in the price catalog outbound processing.
This BAdI allows you to fill the fields in the price catalog with your own data. This way, you can fill
catalog fields in the price catalog that cannot be supplied with data in the standard system, but for which
data is available in customer-defined tables or enhancements in the system. This BAdI also allows you to
read conditions or bills of material using a logic other than that for the price catalog, and to integrate the
data with the price catalog.
The BAdI consists of 5 methods:
o
You can enhance basic data using method READ_MATERIAL.
o
Use method READ_BOM to enhance reading bills of material. The method is called for every
material even if no bill of material was found for the material in the system. You can read BOM
information individually as well so that you can store it.
o
Use method READ_CONDITION to implement enhancements for reading conditions.
o
Method READ_CONDITION_COMPLETE allows you to enhance and change conditions. In
contrast to READ_CONDITION, this method has a considerably enhanced interface. In particular,
______________________________________________________________
SAP AG
282
SAP System
______________________________________________________________
you can access the bill of material information.
o
Method READ_BOM_COMPONENTS is called in the routine that executes the access to the bill of
material (BOM). It allows you to directly process the BOM components that were determined. You
can only call the method if the material has a BOM. The method allows you to change the BOM
components.
BAdI PRICHECKPOSITION:
BAdI PRICHECKPOSITION is also called in the outbound processing of the price catalog.
This BAdI allows you to implement an additional check for the catalog item. This way, you can define
additional mandatory fields in the catalog or check logistic dependencies.
This BAdI contains 5 methods:
o
In method CHECK_POSITION, the entire catalog item is checked except for customer-specific
conditions.
o
In method CHECK_CUSTOMER_PRICE, you can check the conditions for each customer.
o
Method CHECK_BOM allows you to check the components from K007 for a material and to set a
return code. The return code controls the behavior once the method is returned:
-
'0': no further action
-
'1': status record (K003S) is set to containing errors and the transport indicator in K003S is set
to 'no transport'.
-
'2' and all other values apart from 0 and 1: status record is set to containing errors and the
transport indicator is set to 'to be transported'.
o
With method CHECK_CUSTOMER_PRICES_ALL, you can check the conditions in their context.
This way, all the conditions can be transferred from K008C. The current material item is also
transferred. This way, you can see the conditions for customers for each of the current materials. In
table IT_CUSTOMERS, you can enter the cutsomers for whom errors occurred. This table is
interpreted from the method after it is returned and the status records concerned (K003S) are set to
the status containing errors without transport.
o
Method CHECK_POSITION_CUST allows you to run a check at customer/material level and to set
the transport indicator in the transported K003S.
BAdI PRISETPARTNER:
BAdI PRISETPARTNER is also called in the outbound processing of the price catalog.
This BAdI has 2 methods:
o
Method ADJUST_K00C allows you to change fields in table K000C (customer-independent price
catalog fields) in transaction VPRICAT. Use this method to set the partner type and partner number
that are to be used to send the IDoc to the relevant customer. This way, you can avoid manual
maintenance.
o
Method SET_PARTNER_PARMS is called when you create IDoc PRICAT02. It allows you to set
the message code and the message function to access the partner profile. Message codes and
message functions are key fields for the partner profile. If you do not set them using method
SET_PARTNER_PARMS, then they will be blank.
BAdI PRICAT_OUT_EXTIN:
______________________________________________________________
SAP AG
283
SAP System
______________________________________________________________
BAdI PRICAT_OUT_EXTIN is also called in the outbound processing of the price catalog.
This BAdI is used to fill the ExtensionIn parameter of BAPI
BAPI_PRICECATALOGUE_SAVREPLICA in the price catalog - outbound. A table ExtensionIn in the
BAPI interface is the standard enhancement technology for BAPIs.
This interface is relevant if you are sending price catalogs using message type PRICECATALOGUE.
Parameter ExtensionIn allows you to transfer data to the BAPI in addition to data that is defined in the
standard system. In doing this, you can also transfer the data to the IDoc that is to be sent and that was
generated using the BAPI interface.
The additional data is transported using a segment (E1BPAREX) in the IDoc. The BAPI also contains
BAdI method calls so you can process this data using customer-specific coding in the price catalog inbound. If the data is not to be transferred between two SAP R/3 Systems, a converter must interpret
user-specific segments.
Method OUTBOUND_EXTENSIONIN imports the complete BAdI interface. Parameter
RT_EXTENSIONIN is a changing parameter. This way, the table in the method can be filled with
customer-specific data. The ExtensionIn parameter is included in the standard delivery and is supported
by the enhancement technology for BAdIs.
BAdI PRICAT_IN_EXTIN:
BAdI PRICAT_IN_EXTIN is called in the inbound processing for the price catalog.
This BAdI has 2 methods:
o
Method CHECK_INBOUND_EXTENSION allows a check to be run on the parameters that were
transferred to the BAPI at the start of the processing in BAPI
BAPI_PRICECATALOGUE_SAVREPLICA. Parameter ExtensionIn can also be checked. Using
parameter RV_SUBRC, you can suppress any further processing. The system message fields are
evaluated after the method has been called in BAPI BAPI_PRICECATALOGUE_SAVREPLICA if
RV_SUBRC is not equal to 0.
o
Method UPDATE_INBOUND_EXTENSION enables you to process data from table parameter
ExtensionIn. This parameter may contain customer-specific data that is either to be integrated into
the standard tables of the price catalog or to be stored in customer-defined tables. To integrate the
standard tables of the price catalog, you use BAPI_Table_Extensions. These are enhancement
concept objects for BAPIs. They are delivered in the standard system with the key contents and
enhanced to include their own fields in appedixes. This method receives Table_Extensions via the
interface and can then fill them. For each table in the price catalog, a corresponding
Table_Extension is delivered. You can find more information in the source text of module
BAPI_PRICECATALOGUE_SAVREPLICA using the extension name. It concerns the changing
parameter of method UPDATE_INBOUND_EXTENSION. After the return from the method call,
the entries are compared with the standard tables. If you want to update user-defined tables, you can
call your own update module in the method that will update your own tables.
The changing parameters are empty when you call them. They can be filled in the method. They are
used to provide customer-defined fields in the standard tables. If you make entries in these
structures and fields, parameter 'entries_made' must be set to 'X' to transfer the data from these
structures and tables to the standard tables of the price catalog. These parameters are BAPI table
extensions. In the customer system, these structures can be enhanced with APPENDS. This
enhancement corresponds exactly to the enhancement of the relevant standard tables. The
customer-specific fields are transported with MOVE_CORRESPONDING after the method call to
the standard tables. This involves the enhancement technology used in the standard system for
______________________________________________________________
SAP AG
284
SAP System
______________________________________________________________
BAPIs.
BAdI PRISETTEXTPARMS:
BAdI PRISETTEXTPARMS is called in the price catalog outbound processing.
This BAdI is used to restrict the text IDs and languages for material texts that potentially have to be
included in a price catalog. The restriction is useful for a general overview of the catalog. It is just as
important for performance reasons not to run a search for all the possible material texts in all languages.
The BAdI supports method ADJUST_LANGUAGES_OUT. This method receives the text IDs and
languages via the interface as tables using 2 changing parameters. By implementing this method, you can
restrict the text IDs and languages by deleting the entries in the tables.
12.10.2 Support for Scales in the Price Catalog
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), you can create scales in the price catalog.
Scales in the price catalog - inbound:
The inbound processing for the logical messages PRICE CATALOGUE stores the scales in the inbound
price catalog.
You can display them by choosing a new tab page at EAN level (transaction PRICAT).
Scales in the price catalog - outbound:
Up until now, logical message PRICAT (IDocs PRICAT01 and PRICAT02) sent scale information. This
is done by reading the scales from the master data (not from the price catalog) at the time of the IDoc
being created.
You can now save the scales in the price catalog when you create them. You can display and change the
scales using transactions VPRICAT (outbound) and PRICAT (inbound). The engineering change
management takes account of changes to the scales too. To display and change the scales, you choose
new tab pages at EAN level too.
Message PRICECATALOGUE (using new IDoc type PRICECATALOGUE02) sends the scales from the
catalog data.
The function of message type PRICAT (IDocs PRICAT01 and PRICAT02) has not changed.
IDoc enhancement for message PRICECATALOGUE02:
Until now, you could not add any customer-defined segments to message PRICECATALOGUE. This is
because the BAPI that this message concerns (BAPI_PRICECATALOGUE_SAVREPLICA) does not
support customer enhancements. This BAPI is now enhanced in its interface to include parameter
EXTENSIONIN. This parameter allows customer-specific data to be transferred to the BAPI. This data is
processed in the BAPI using 2 methods from the new BAdI PRICAT_IN_EXTIN with the help of
Table_Extensions. As message PRICECATALOGUE concerns the BAPI technically (by generating the
message from the BAPI interface), the new IDoc type PRICECATALOGUE02 receives a new segment to
transport customer enhancements. This segment is filled by BAdI PRICAT_OUT_EXTIN in the price
catalog - outbound.
______________________________________________________________
SAP AG
285
SAP System
______________________________________________________________
12.11 SD-POS
POS Interface
12.11.1 SD-POS-OUT
POS Interface - Outbound
12.11.1.1 New Change Pointers for Condition Records (WIND)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you have the following additional options for
adjusting documents in condition changes:
o
Direct entries in the worklist after condition changes
o
Including additional data in an entry in the worklist
In the previous procedure, the entries were created in the worklist based on the change pointers for
condition changes (message type CONDBI) in worklist creation (transaction ME14). In the new
procedure, the change pointers are no longer needed. When a condition is changed, entries are created
directly in the worklist. This removes the previous step in the process of creating the worklist from
change pointers, which was very performance-intensive. In addition, you do not have to create change
pointers for condition changes if they are not going to be used in other processes.
The Customizing that was valid for the previous worklist creation and that defines which condition types
should be included in the worklist (table T6I1) is also valid for the direct entry. However, there are
additional filter options in the new procedure. You can define for each document category for which
types of condition changes (amount change, validity, pricing relevance) entries should be made in the
worklist. There is also a BAdI that is dependent on the document category filter criterion with which
customer-defined filter criteria can be implemented.
The following example describes the options offered by the BAdI:
Due to changing purchasing conditions, perishable materials are regularly repriced in short time periods.
Therefore, sales prices do not need to be updated using the pricing worklist procedure. Use the material
type, in this case, as an additional filter criterion in the retail pricing application (document category 10).
When the basic purchase price of a perishable material is changed, the system does not create a worklist
entry for this document category due to the filter criterion that was implemented.
The additional data in a worklist entry consists of header data from the conditions with which you can
improve performance for the follow-on processing and of variable customer fields with which you can
carry out selective subsequent processing. You make settings in Customizing for filling the customer
fields (table T6I2S).
Effects on Existing Data
If you do not use change pointers for condition changes, the level of data for change pointers is reduced
considerably. A change pointer generally consists of several entries in table BDCP and BDCP2.
The following changes are made:
o
The width of table WIND increases from 45 to 262 bytes due to the additional tables.
o
The number of table entries in the worklist can be reduced due to the additional filter criteria.
______________________________________________________________
SAP AG
286
SAP System
______________________________________________________________
o
Change pointers are no longer needed for message type CONDBI.
Effects on System Administration
The process step for creating the worklist from change pointers (transaction ME14) is no longer needed in
the new procedure.
The check for existing document indexes (table S111) that can be used in the previous worklist creation
must be implemented as an additional filter criterion in the BAdI (see example coding).
The migration of the worklist from the old to the new worklist entries is carried out using report
RMEBEMIG. The report enhances the entries that are available using information from the condition
records.
If you are converting from the old to the new procedure, a special adjustment procedure is required for
every document category. This procedure is described in each of the applications that use the new
procedure.
Effects on Customizing
Implement the new Customizing for the direct creation of worklist entries. If you are installing this for
the first time or if you have not yet used the document adjustment function for a certain document
category, set the indicator manually for migration and direct entry in Customizing. When converting from
the old to the new procedure, the indicators in the migration procedure are set automatically.
You also determine the types of condition changes for each document category as filter criteria for which
worklist entries should be created and how the variables should be filled.
Once you have made settings for direct entries in the worklist for all the document categories used, you
do not have to create change pointers from message type CONDBI. Deactivate message type CONDBI in
ALE Customizing.
You can also carry out this deactivation using the migration report.
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Master Data -> Conditions ->Automatic Updating of Documents After Condition Changes.
12.11.1.2 New Functions in POS Interface Outbound
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110), POS outbound has the following new
features:
o
There is now an extra parallel processing level in POS outbound processing. This means that only
one background job per distribution chain is required and that synergies exist with the selection of
change pointers.
o
In the POS outbound profile, the performance of price determination can now be improved using the
indicator "Upload Prices Directly". A definite data structure is a prerequisite.
o
You can improve the performance of price determination using the new "Store-Independent Prices"
______________________________________________________________
SAP AG
287
SAP System
______________________________________________________________
indicator. A prerequisite is that no store-dependent prices exist.
o
You can improve the performance of price determination even more by using the indicator "Prices
by Store in A071". To be able to use this, all store-dependent prices must be stored in table A071
only and there must only be a relatively small number of them.
o
A new IDoc type WPDREB01 (promotion discount) can now be created using POS outbound. This
means that discount information can be distributed to the downstream systems (generally store
retailing systems) at higher levels than article level (for example, 5% discount on the entire
assortment or a certain material group).
o
The extended condition document index can be used by POS outbound.
o
The way in which change pointers are saved as been changed, meaning an improvement in
performance for POS outbound. A prerequisite is that the old change pointers are migrated first.
o
Access to condition intervals has been optimized even more.
o
The implementation of the interval scanner has been changed enabling a much quicker analysis of
condition intervals.
o
In new listings it is now taken into consideration that the name of the assortment does not
necessarily have to match the name of the store.
o
Condition access to the function module WWS_CONDITION_INTERVALS_GET has been
optimized. This leads to an improvement in performance.
o
Change pointers are now processed more efficiently, giving better performance.
o
The (physical) deletion of conditions can now be recognized by the change message. In most cases,
the deletion of promotional and normal conditions is also supported. Partial interval deletions of
condition records that have previously been split still cannot be recognized however.
o
If the "Copy tax codes in variants" indicator is not set, the price copy for variants is switched off.
This is only necessary, however, if different tax indicators are used for the variants of a generic
article.
o
Parallel prices are now taken into account.
o
Basic prices and comparison prices are now taken into account.
o
The new "m:n assignments" functionality for assortments is supported.
o
The creation of a trigger file can now be suppressed explicitly using the POS outbound profile.
o
Bonus buys can now be deleted automatically.
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Distributed Data Processing -> POS Interface -> POS Interface - Outbound.
______________________________________________________________
SAP AG
288
SAP System
______________________________________________________________
13 MM
Materials Management
13.1 Country Version India in Standard R/3 System
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), Country Version India is no longer delivered as
an add-on but as part of the standard R/3 System.
Integration of functions in the SAP Easy Access menu
The functions for withholding tax have been integrated into the SAP Easy Access menu, under
Accounting -> Financial Accounting -> Accounts Payable -> Withholding Tax -> India and
Accounting -> Financial Accounting -> Accounts Receivable -> Withholding Tax -> India.
You can access all other functions using the area menu J1ILN, which you can call from the SAP Easy
Access screen using the transaction code J1ILN.
Country Version India Implementation Guide
The Country Version India Implementation Guide (IMG) has been integrated into the standard Reference
IMG (see Changes to Structures for Country Version India).
Release Notes
You can access release notes from previous add-on releases using the links below.
SAP Library Documentation
The SAP Library documentation for Country Version India is also delivered on the standard SAP Library
documentation CD (see below).
New and Changed Functions
For information about new and changed functions for Country Version India, see the other release notes
for this release.
Effects on Existing Data
You do not need to change any data.
Effects on Customizing
IMG activity
What to do
Activate Country Version India for Specific Fiscal Years Delete the entry ZIND and create a new
entry for IND.
See also
SAP Library -> Financials or Logistics -> Country Versions -> Asia-Pacific -> India.
Release Notes from Country Version India Add-On (FI)
Release Notes from Country Version India Add-On (SD)
Release Notes from Country Version India Add-On (MM)
______________________________________________________________
SAP AG
289
SAP System
______________________________________________________________
13.2 Condition-Based Tax Calculation (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), a new method for calculating taxes in Brazil
is available, which makes use of the standard condition technique. Tax rates, tax laws, and special
indicators that influence whether tax line items are included in the nota fiscal are all stored in the system
as condition records. An additional tax calculation procedure, TAXBRC, is delivered for this new
method, in addition to the existing one for Brazil, TAXBRJ.
Effects on Existing Data
You can continue to calculate taxes using the former method: when the system processes the tax
procedure assigned to the country (TAXBRJ), it calculates the taxes externally by calling function
module J_1BCALCULATE_TAXES. We do, however, recommend that you assign the new procedure
TAXBRC and use the condition-based tax calculation functions, as it enables you to flexibly adapt the tax
calculation logic to cover new legal requirements or special customer needs.
You will need to migrate your existing tax rate table entries to condition records, which you can do
directly from the Tax Manager's Workplace described below. You can check all tables and subsequently
convert the entries, whereby the system generates condition records. After the initial migration, each time
you create or change a tax rate table entry, the system automatically generates a condition record as
needed.
Effects on Customizing
If you want to employ the new condition-based tax calculation, you need to activate it and carry out all
related Customizing activities, under Financial Accounting -> Financial Accounting Global Settings
-> Tax on Sales/Purchases -> Basic Settings -> Brazil -> Condition-Based Tax Calculation, all of
which are new:
o
Activate Condition-Based Tax Calculation
o
Map MM Tax Values to Nota Fiscal Fields
o
Map SD Tax Values to Nota Fiscal Fields
o
Map MM Tax Laws to Nota Fiscal Fields
o
Define Internal Codes for Tax Conditions
o
Assign Internal Codes for Tax Conditions to Condtion Types
o
Assign Tax Rate Tables to Condition Tables
In addition, you need to assign the new tax calculation procedure TAXBRC to the country in
Customizing, under Financial Accounting -> Financial Accounting Global Settings -> Tax on
Sales/Purchases -> Basic Settings -> Assign Country to Calculation Procedure.
A new Customizing tool called the Tax Manager's Workplace is available that enables you to make all
tax-related settings for Brazil. You access it under the same path as above through Tax on
Sales/Purchases, then Calculation -> Settings for Tax Calculation in Brazil -> Access Tax
Manager's Workplace , or alternatively by entering transaction J1BTAX. You can use the Tax Manager's
______________________________________________________________
SAP AG
290
SAP System
______________________________________________________________
Workplace regardless if you use condition-based tax calculation; it simply brings all tax activities to a
single transaction (only the Migration, Nota-Fiscal Mapping, and Condition Mapping options under the
Condition Setup pulldown menu are relevant only for condition-based tax calculation).
13.3 Changes to Structures for Country Version India
Use
As of SAP R/3 4.7, Country Version India is no longer delivered as an add-on, but forms part of the
standard system.
SAP has discontinued the Country Version India Implementation Guide (IMG) and has added its
activities have been added to the standard Reference IMG as follows:
Activities relating to withholding tax are now located in Customizing for Financial Accounting (FI),
under Financial Accounting Global Settings -> Withholding Tax.
Activities relating to excise duty and excise invoices are in Customizing for Logistics - General, under
Tax on Goods Movements -> India.
As far as the activities under Preparatory Activities are concerned, two of them (Activate Country
Version India for Accounting Interface and Activate Processes) are no longer relevant and have been
removed from the IMG entirely. The activity Execute Country Installation Program is already included in
the standard IMG under the name Localize Sample Organizational Units. And the other two activities
(Activate Country Version India for Specific Fiscal Years and Activate Business Transaction Events)
have been added to the standard IMG.
For information about other changes to the IMG relating to changes in the functions in Country Version
India, see the other release notes.
13.4 Release Notes from Country Version India Add-On (MM)
Use
The Release Notes from Releases 3.0A and 4.0A of Country Version India for Materials Managment
(MM) are listed below. For more Release Notes, see the alias globalization in SAPNet, and choose
Media Center -> Country-Specific Documentation -> Country Version India - Release Notes.
Release 3.0A
o
CENVAT Credit on Capital Goods After Budget 2000 (Changed)
o
Multiple Goods Receipts for Single Excise Invoices
o
Enhancements to CVD Solution
o
Pricing Date Control in Excise
o
Order Price Unit in Excise
o
Alternate Assets MODVAT Capitalization
______________________________________________________________
SAP AG
291
SAP System
______________________________________________________________
o
Enhancements for 57 F4
o
User Exits for Customer Validations
Release 4.0A
o
Procurement Transactions for Excise Invoices
o
New Transactions Based on User Roles for Incominng Excise Invoices
o
Capture Excise Invoices with Reference to Multiple POs for the Same Vendor
o
Capture Excise Invoice and Post CENVAT in a Single Step
o
Open Schedule Quantity Defaulted in Excise Capture for Scheduling Agreement
o
Accounting Document Simulation for CENVAT Postings
o
Rejection Codes for Excise Invoices
o
Single-Screen Transaction for All Excise-Related Entries
o
Stock Transfer Orders Through MM Route
o
Excise Invoices for Multiple Import Purchases
o
Customs Invoices Can Be Captured Using Logistics Invoice Verification and Conventional Invoice
Verification
o
Material Type at Line Item Level
o
Excise Invoice Capture Without PO
o
Excise Invoice Without PO - Capture and Post in a Single Step
o
Recalculation of Duty and Excise Defaults Restore Feature Available
o
Split of Nondeductible Taxes During Excise Invoice Capture
o
Error or Warning Messages Displayed at the Time of Saving
o
Reversal of Excise Duty
o
MIGO Solution Available as a Note 0408158 (Featuring All Functionalities as in MB01)
o
Excise Invoice Defaults in Excise Popup at Goods Receipt
o
Split Accounting Lines for CENVAT Posting
o
Authorization for Incoming Excise Invoices Extended
o
Authorization Available for Part I Entry at GR
o
Authorization Available for Register Update Transaction
o
User Exit Available for Incoming Excise Invoice Transaction for Defaulting Values
o
User Exit Available for Incoming Excise Invoice Transaction Before Database Update
o
User Exit Available for Register Update for Validations on Fetched Records Based on Selection
Criteria
o
User Exit Available for Register Update of RGSUM Register
o
User Exit Available for Excise Invoice Create for Other Movements to Default the Excise Details
______________________________________________________________
SAP AG
292
SAP System
______________________________________________________________
o
Register Update Separately Handled for Receipts and Issues Based on Classification Code
o
Ship-From Vendor Can Be Defaulted and Captured in Incoming Excise Invoices for Other
Movements
o
Removal Time Can Be Captured in Excise Invoices for Other Movements
o
Field Selection of Incoming Excise Invoices
o
Transaction Code Customizing for Incoming Excise Invoices
o
Excise Group Setting for Part I Indicator for Blocked Stock, Stock Transfer Order, and
Consumption Stock
o
Multiple Goods Receipts and Multiple/Single Credit Settings Available at Excise Group Level
o
Rejection Code Master Setting for Posting on Hold Is Available
o
Stock Transport Orders
13.5 MM: Overview of Changes to SAP R/3 Enterprise Core 4.70
Use
In the following, you can see an overview of all changes in the application component MM-Materials
Management. You can display the corresponding release infos directly.
o
Purchasing (MM-PUR)
-
Accessibility Barriers Removed: Purchasing Lists Converted to ALV Grid (Changed)
-
Business Add-Ins in Purchasing
-
Matchcodes Superseded by Search Helps in Purchasing
-
Continuation of Conventional Purchase Order and Purchase Requisition Transactions
-
Reports for Inclusion of Derivative Financial Instruments in Balance Sheet
-
New Change Documents in Purchasing
-
Version Management in Purchasing
-
Changeability of Configuration Controllable in Purchasing
-
Display of Commitments in External Purchasing Documents and Purchase Requisitions
-
Commitment in Stock Transfer Documents
-
Release Transactions in New Interactive Design
-
New Workflows for Refusal to Release
-
Reminder Level as Selection Criterion for Reminders and Expediters Relating to Purchasing
Documents
-
Copying Rules for Conditions in Purchasing
-
Automatic Generation of Purchase Orders from Purchase Requisitions in New Interactive
______________________________________________________________
SAP AG
293
SAP System
______________________________________________________________
Design
o
-
Enjoy Purchase Requisition - Assign and Process
-
Release of Enjoy BAPIs: BAPI_PO_CREATE1 and BAPI_PO_CHANGE
-
Consignment Also Possible on Cross-Company- Code Basis
-
Different Delivery Types in a Single Stock Transfer Document
-
Supplementation of Personal Settings in Enjoy Purchase Order
-
Underdelivery Tolerance in the Case of Stock Transport Orders
Service (MM-SRV)
-
o
o
Returns for Service Entry Sheets from Time- Sheets
Inventory Management (MM-IM)
-
Functional Enhancements in MIGO
-
Replacing the MB* Transactions with Transaction MIGO
-
Business Add-Ins in Inventory Management
-
Functional Supplement for BAPI CreateFromData
-
Create a Subcontract Order with Batch Number
-
Output Determination: Program for Creating Condition Records
-
SAP Smart Forms in Inventory Management
Invoice Verification (MM-IV)
-
Overview of Developments in Logistics Invoice Verification
-
All Functions in Logistics Invoice Verification
-
Automatic Quantity and Amount Distribution for Multiple Account Assignment
-
Business Add-Ins in Logistics Invoice Verification
-
Enhancements to BAPIs in Logistics Invoice Verification
-
EDI: Posting to Material and G/L Accounts Using Customer Exit
-
Enhancements to the Invoice Overview
-
Verifying Freight Invoices in the Background
-
Displaying MM and FI Document Numbers
13.6 MM-CBP
PP-MRP)
Consumption-Based Planning (See Also
13.6.1 MM-CBP-CBP
Consumption-Based Planning (See Also PP-MRP)
______________________________________________________________
SAP AG
294
SAP System
______________________________________________________________
13.6.1.1 Alternative Historical Data/Post Distribution Forecasting
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110) you can improve the accuracy of forecasting
by using alternative historical data (AHD) / Post Distribution Forecasting (PDF) as the data basis for
consumption-based planning.
These new functions mean that you no longer need the past consumption values as the data basis for the
forecast.
Using alternative historical data/Post Distribution Forecasting has the following advantages if the
consumption values available do not reflect the actual requirements sufficiently:
o
Improved forecast precision for distribution centers (avoiding the bullwhip effect).
o
Reduced stock in the distribution center due to a decreased safety stock.
o
Increased revenue by avoiding missed sales.
You can also contstruct delivery relationships. A delivery relationship states which recipients (plants
and/or customers) are to receive a certain material from a plant. Delivery relationship determination is
useful in a Pst Distribution Forecasting scenario in which the forecast in the distribution center is created
on the basis of store and/or customer requirements and it is necessary to restrict the receiving plants
and/or customers. However, Post Distribution Forecasting scenarios are also possible without explicit
determination of the delivery relationship.
Only use the functions alternative historical data and Post Distribution Forecasting for retail materials and
plants.
Effects on Data Transfer
In principle, alternative historical data can originate from any data source. In the standard system, a
scenario is delivered, for which the alternative historical data is read from the component SAP BW into
SAP R/3. You can connect to another now SAP BW data source using the Business Add-In (BAdI)
provided.
The following BAdI is provided for this purpose:
o
BAdI: AHD/PDF scenario
Effects on System Administration
Note that delivery relationship determination and loading alternative historical data can influence runtime
and hence affect system performance.
Effects on Customizing
Carry out the following IMG activities in Customizing for alternative historical data, Post Distribution
Forecasting, delivery relationship determination and for data retraction for Retail/CP:
o
Control of Alternative Historical Data and Post Distribution Forecasting
o
Profile for Delivery Relationship Determination
o
Document Types for Delivery Relationship Determination
o
Data Retraction for Retail/CP
______________________________________________________________
SAP AG
295
SAP System
______________________________________________________________
13.6.1.2 Multi-Step Replenishment
Use
As of SAP R/3 Enterprise Retail 1.10 (EA-RETAIL 110) you can use multi-step replenishment.
Multi-step replenishment is a performance-optimized variant of the sales forecast and store
replenishment. Multi-step replenishment can only be used for stores.
The aim of multi-step replenishment is to reduce the time requirement within the critical time frame.
IMPORTANT:
o
You should use multi-step replenishment as an alternative to replenishment particularly if it will
improve performance.
o
Use multi-step replenishment if there are sufficient system resources available outside the time
frame. If there are not sufficient free resources available outside the critical time frame, multi-step
replenishment will not bring any improvement to performance.
Using multi-step replenishment improves performance by moving the burden out of the critical time
frame to a time before or after.
Using multi-step replenishment causes minimal changes to the procedure.
For more detailed information on the process of multi-step replenishment, see
ISR_WSRP_REPLENISHMENT and also the SAP Library under Logistics ->SAP Retail -> Purchasing
-> Requirements Planning -> Multi-Step Replenishment.
Effects on Existing Data
The dataset grows because tables WRPL and WRPT have been extended. However, the volume of data to
be processed is reduced by various optimizations.
Effects on Data Transfer
Note the following about data transfer for multi-step replenishment:
o
Sales forecast: When using the standard tables (MAPR, MVER, PROP and PROW) data transfer is
not required. When transferring consumption data, use the transfer program with transaction
WFCS04.
Effects on System Administration
Schedule the relevant program.
Effects on Customizing
Activate multi-step replenishment for a store in Custumizing for POS Inbound Updates by setting the
"Update replenishment-based Inventory Management" field to "1" (Integrated replenishment-based
inventory management).
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail ->
______________________________________________________________
SAP AG
296
SAP System
______________________________________________________________
Purchasing -> Requirements Planning -> Multi-Step Replenishment).
13.7 MM-PUR
Purchasing
13.7.1 Accessibility Barriers Removed: Purchasing Lists Converted to ALV Grid
Control (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can display most of the lists used in
Purchasing via ALV grid control. This makes the lists set out below fully accessible to
disabled/handicapped users of the SAP system.
Prerequisites
In the SAPGUI, you can activate the lists in one of two ways:
- Via the selection criterion Scope of List (see also Effects on Customizing)
- Via the parameter ID ME_USE_GRID = 'X' in the user master record
In the SAP WEBGUI, select the Accessibility indicator when you log on. You then obtain all lists in
ALV grid control format.
Lists that have been converted to the new format
o
Activated via the selection criterion Scope of List in the SAPGUI:
Transaction
ME2B
ME2C, ME3C, ME4C
ME2K, ME3K
ME2L, ME3L, ME4L
ME2M, ME3M, ME4M
ME2N, ME3N, ME4N
ME2W
ME3B, ME4B
ME4S
ME5A, ME5K
ME56
ME57
ME58
ME55
ME5F
ME28, ME35K, ME35L, ME45
o
Report
Purchasing documents by requirement tracking number
Purchasing documents by material group
Purchasing documents by account assignment
Purchasing documents by vendor
Purchasing documents by material
Purchasing documents by document number
Purchasing documents by supplying plant
Purchasing documents by requirement tracking number
RFQs by collective number
List display of purchase requisitions
Assign source of supply to requisition
Assign and process purchase requisitions
Ordering: assigned purchase requisitions
Collective release of purchase requisitions
Release reminder: purchase requisitions
Release purchasing documents
Activated via parameter ID ME_USE_GRID = 'X' in SAPGUI
______________________________________________________________
SAP AG
297
SAP System
______________________________________________________________
Transaction
Report
ME06
Analyze source list
ME0M
Source list for material
ME16
Deletion proposals for info records
ME1E
Quotation price history
ME1L
Info records for vendor
ME1M
Info records for material
ME1P
Purchase order price history
ME1W
Info records for material group
ME91A, ME91E, ME91F
Purchasing documents: reminders/urging letters
ME92F, ME92K, ME92L
Monitor order acknowledgments
ME9A, ME9E, ME9F, ME9K, ME9L
Message output
MEQ6
Analyze quota arrangement
MEQ8, MEQM
Quota arrangement for material
ME2S
PO reporting with services
ME3S
Contract reporting with services
CATM
Import CATS data
ML83
Print/transmit messages: service entry sheet
ML84
List of service entry sheets
Effects on Customizing
To be able to activate ALV grid control lists via the list scope, make the following settings in
Customizing:
-> Purchasing -> Reporting ->
o
Maintain Purchasing Lists -> Define Scope of List -> Detail View: Select Use ALV Grid Control
indicator
o
Maintain Purchase Requisition Lists-> Define Scope of List -> Select ALV Grid indicator
See also
You can display all Release Notes on system accessibility for disabled persons in a single step.
13.7.2 Business Add-Ins in Purchasing (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following Business Add-Ins (BAdIs) are
available in Purchasing:
o
Deactivate 'Hold' Function for Enjoy Purchase Order
ME_HOLD_PO
______________________________________________________________
SAP AG
298
SAP System
______________________________________________________________
o
Extend Processing of Enjoy Purchase Order
ME_PROCESS_PO_CUST
o
Customer's Own Screens in Enjoy Purchase Order
ME_GUI_PO_CUST
o
Define Follow-On Processing for External Purchasing Documents
ME_PURCHDOC_POSTED
o
Define Follow-On Processing for Purchase Requisitions
ME_REQ_POSTED
o
Control Changeability of Configuration Data
ME_CIP_ALLOW_CHANGE
o
Activate Additional Updating in Change Documents
ME_CHDOC_ACTIVE
o
Supplementation of Delivery Interface from Purchase Order
MM_EDI_DESADV_IN
o
Adopt Header Text When Copying Purchase Requisitions
ME_REQ_HEADER_TEXT
o
Activate Requisition Commitment Update from Other Applications
ME_REQ_OI_EXT
o
Adopt Tax Jurisdiction Code from Delivery Address
ME_TAX_FROM_ADDRESS
o
Run Through Items Again in the Event of Changes in EKKO
ME_CHECK_ALL_ITEMS
o
Control of Pricing Type: Additional Fields
ME_DEFINE_CALCTYPE
Effects on Customizing
You can maintain these Business Add-Ins in Customizing for Purchasing in the section Business Add-Ins
for Purchasing.
See also
Further informationen on Business Add-Ins is available in the SAP library under Basis -> ABAP
Workbench -> Changes to SAP Standard -> Business Add-Ins.
13.7.3 Matchcodes Superseded by Search Helps in Purchasing
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), all matchcodes are superseded because they are
not supported in Unicode systems.
______________________________________________________________
SAP AG
299
SAP System
______________________________________________________________
The IDs of the matchcodes MEBE, MEBZ and MEOR are replaced by elementary search helps of the
same name. In the new search helps, database views, which take the place of the generated pool tables,
are used as the selection method.
Since the views read directly from database tables, a suitable index has been created for the table used in
each case.
The former matchcodes, new search helps, and database indexes are as follows:
MatchSelection method
New index
code
ID
old & new
for table
MEBE
L
M_MEBEL
MEBE
X
M_MEBEX
MEBZ
F
M_MEBZF
MEOR
V
M_MEORV
Search help
MEBEL
EKBE -A
MEBEX
EKBE -B
MEBZF
EKBZ -A
MEORV
EORD -V
Effects on Existing Data
If pool tables were still used in existing elementary search helps (MEBEL), these were likewise replaced
by database views. The names of the new database views similarly match up with those of the pool tables.
There is thus no need for corrections in ABAP programs that use the pool tables.
The matchcodes, the matchcode IDs, the pool tables, and their pool/clusters have been deleted.
See also
Release Note on Matchcode Changeover
13.7.4 Continuation of Conventional Purchase Order and Requisition
Transactions
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), please note the following planning regarding the
conventional PO (ME21, ME22, ME23) and purchase requisition transactions: (ME51, ME52, ME53):
Maintenance:
An appropriate maintenance service will continue to be available for bugs that occur during interactive
use or during use of the batch input facility in Release Enterprise Core 4.70.
Further development:
______________________________________________________________
SAP AG
300
SAP System
______________________________________________________________
There will be no further development of the conventional purchase order and purchase requisition
transactions.
Future releases:
SAP reserves the right to discontinue the conventional PO and requisition transactions in future releases.
13.7.5 Reports for Inclusion of Derivative Financial Instruments in Balance
Sheet (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), SAP provides a report (RMFAS133) enabling
you to determine purchasing documents affected by the Statement of Financial Accounting Standards
(SFAS) 133. SFAS 133 stipulates that all derivative instruments are to be included in the balance sheet at
their market value.
Two further reports facilitate a) the comparison of document lists (RMFASDTA) created at different
times, and b) the deletion of no-longer-needed data (RMFASDEL).
13.7.6 Perishables Processing
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the following new functions for
perishables processing:
Using the new allocation table and collective purchase order function modules for document
generation:
SAP is providing new function modules for the allocation table and collective purchase order processes
that will improve performance when generating documents.
Linking SAP BW with perishables planning:
You can use the new interfaces (methods: S160_EVALUATE and S160_FIL_EVALUATE from BAdI
WDFR_BADI) to use InfoObjects in SAP BW as a source of information rather than the retailing
information system (perishables information structure S160 and customer-defined info structure). You
could, for example, use the sales data from the SAP BW InfoObjects. You must create and maintain the
data structures, InfoObjects and data contents in SAP BW beforehand.
More flexible options for accessing the program run:
You can use new interfaces for this (method in BAdI: WDFR_BADI). These interfaces allow you to
access the perishables planning process without having to make any modifications. The method names
are chosen so they match the FORM routine names. This way, you can completely replace the perishables
planning list creation with method TX_XX_FILL and the document generation with method
FDIS_BELEGE_GENERIEREN.
______________________________________________________________
SAP AG
301
SAP System
______________________________________________________________
Perishables planning list that can be saved
The previous function for saving is divided into 2 functions for saving the perishables planning list and
for generating documents. Up until now, the documents were created with the save function. Subsequent
and further processing are not included in the function.
Add vendors
You can use the new function "Add Vendor" to add a new vendor that already exists in the system to an
article in the perishables planning list.
Effects on Existing Data
You can use transaction WDFR2 "Change Perishables Planning List" to subsequently process the
perishables planning and to create documents at the very last minute. This improves general system
performance and reduces the system load. Transaction WDFR3 "Display Perishables Planning List"
completes the perishables processing.
13.7.7 MM-PUR-GF
Basic Functions
13.7.7.1 New Change Documents in Purchasing (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following new change documents are
available in Purchasing:
o
Versions of purchasing document (REVISION)
In this change document, the system documents the changes to a version.
See also: Version Management in Purchasing (New)
o
Document assignment in purchasing (EINKDOKUMENT)
In this change document, the system documents assignments of a DMS document to a purchase
requisition or an external purchasing document and any deletions of such assignments.
o
Subcontracting components (MDSB)
In this change document, the system documents the changes made to the subcontracting components
in a subcontracting purchase requisition or an external subcontracting purchasing document.
o
Import/export data (EXPIMPBELEG)
In this change document, the system documents changes you make to import or export data.
Furthermore, the following change documents have been extended through the addition of the
time-independent conditions (table KONVC):
o
Purchasing document (EINKBELEG)
o
Change document: External Services Management (MM_SERVICE)
Changes to time-independent conditions in a purchasing document or within the framework of External
Services Management are now documented by the system.
Note
______________________________________________________________
SAP AG
302
SAP System
______________________________________________________________
You can now also generally display the change documents via ALV grid control.
Effects on Customizing
With the exception of the versions of the purchasing document, you archive the aforementioned change
documents via the Business Add-In (BAdI) ME_CHDOC_ACTIVE: Activate Additional Updating in
Change Documents.
You can maintain the Business Add-In in Customizing for Purchasing in the section Business Add-Ins for
Purchasing.
13.7.7.2 Version Management in Purchasing (New)
Use
As of Release 4.70, a Version Management facility is available in Purchasing, enabling you to generate
versions of purchase requisitions and external purchasing documents (e.g. purchase orders).
A version comprises a collection of change documents generated as a result of the subsequent processing
of a purchasing document. The version thus indicates the status of the purchasing document, thus
enhancing the previous change log for purchasing documents.
Version Management affords the following advantages for procurement:
o
It is easier to retain an overview of changes made to requisitions and external purchasing documents
even if comprehensive changes have been made to a certain document:
-
The changes are easy to retrace
-
You can check which data has been passed on to the vendor
o
Communication with the vendor is facilitated. For example, you can now refer to a certain version
of a PO when phoning a vendor.
o
Changes to long texts (e.g. the delivery text) are documented. This is of particular interest in the
procurement of capital goods. Hitherto, it has not been possible to retrace changes affecting long
texts. With Version Management, it is even possible to compare different editions of a text with
each other.
Effects on Customizing
In order to be able to use Version Management, you must activate it in Customizing for Purchasing under
Version Management ->
o
Set up Version Management for Purchase Requisitions for the relevant combination of document
category and document type.
o
Set up Version Management for External Purchasing Documents for the relevant combination of
document category, document type, and purchasing organization.
______________________________________________________________
SAP AG
303
SAP System
______________________________________________________________
13.7.7.3 Changeability of Configuration Controllable in Purchasing
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can decide whether or not the configuration
of materials is to be changeable in purchase requisitions or external purchasing documents.
The function Configuration in Purchasing itself has been in existence since Release 4.6C. Please therefore
also refer to the Purchasing release note of the same name for Release 4.6C.
Effects on Customizing
You activate and deactivate the changeability of the configuration data in Purchasing via the Business
Add-In ME_CIP_ALLOW_CHANGE: Control Changeability of Configuration Data.
You can maintain the Business Add-In in Customizing for Purchasing in the section Business Add-Ins for
Purchasing.
13.7.7.4 Display of Commitments in External Purchasing Documents and
Purchase Requisitions (New)
Use
As SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can display the relevant commitment directly in
purchase orders, scheduling agreements, and purchase requisitions
Invoke the commitment display from within the already posted document via the following menu path:
Environment -> AC Commitment Documents
Note:
The commitment displayed relates to the whole document and is not item-specific.
13.7.7.5 Commitment in Stock Transfer Documents (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can have a commitment generated by the
system in both stock transport requisitions and stock transport orders (for the longer-distance transfer of
materials) and display the commitment in the documents. You activate or deactivate the function via the
Business Add-In ME_COMMITMENT_STO_CH.
You invoke the commitment display for each item from within the already posted document via the
following menu path:
Environment -> FI/CO Commitment Documents
Note:
______________________________________________________________
SAP AG
304
SAP System
______________________________________________________________
The commitment of the stock transport requisition is reduced or cancelled out by the stock
transport order. The commitment of the stock transport order is reduced or cancelled out by the
value of the goods issue document.
A commitment can only be generated for items with single account assignment.
Effects on Existing Data
A data record is generated for the individual document items in the table COOI.
Effects on Customizing
The pricing condition type in the calculation schema for stock transfers must be set to non-statistical in
order for the commitment to be updated with the net value:
IMG: MM -> Purchasing -> Conditions -> Define Price Determination Process -> Define
Calculation Schema -> RM2000-> Condition Type P101: Non-statistical
13.7.7.6 MM-PUR-GF-TAX
Taxes
13.7.7.6.1 Condition-Based Excise Determination in MM (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system can calculate excise duties and sales
tax in Materials Management (MM) using the standard condition technique.
SAP has enhanced the existing tax procedure, TAXINJ, so that it now supports formula-based and
condition-based excise determination. The R/3 System also comes with a new tax procedure, TAXINN,
which only handles condition-based excise determination.
Which Tax Procedure Must I Use?
Existing customers must continue to work using the same tax procedure.
If you switch to a new tax procedure, you cannot display any documents that you have already posted
using the old tax procedure.
If you have worked with formula-based excise determination in previous releases and wish to continue,
you do not have to do anything. However, if you wish to start using the condition-based excise
determination method, proceed as specified below.
We recommend that new customers use the condition-based excise determination and tax procedure
TAXINN.
How Do the New Functions Work?
First, customize the system in the activities listed below. Then, for each material, create one condition
record for each form of excise duty and sales tax that applies, and enter the tax code for purchasing
documents (see below) in every condition record.
______________________________________________________________
SAP AG
305
SAP System
______________________________________________________________
When you come to create a purchase order, enter the tax code in each line item. The tax code tells the
system whether to look in the condition types for formula-based or condition-based excise determination.
Effects on Existing Data
Existing customers can leave all of their existing vendor master data and material master data as it is.
When you have to enter new excise rates, you can use either the Excise Rate Maintenance transaction for
formula-based excise determination or create condition records as described above if you want to use
condition-based excise determination.
When you come to create a purchase order, the system determines on the basis of the tax code in the line
item whether to use formula-based or condition-based excise determination. This way, you can use both
methods concurrently, and even within the same purchasing document.
No tool is available for migrating the excise data from the old method to the new one.
Effects on Customizing
To set up the new excise determination method, carry out the following activities:
IMG activity
What to do
Check Calculation Procedure
Existing customers: Adjust your tax procedure to
match the changes to TAXINJ. Steps 560-583 are new, as are 593-598.
New customers: Create a copy of TAXINN.
Select Tax Calculation Procedure
New customers only: Assign the copy of TAXINN to
India.
Maintain Excise Defaults
New customers only: Enter the condition type that you
use for countervailing duty.
Define Tax Code for Purchasing Documents Define a tax code.
Assign Tax Code to Company Codes
Assign the tax code to the company codes that it is
relevant for.
Classify Condition Types
Specify which condition types you want to use for
condition-based excise determination.
Define Tax Accounts
Check which G/L accounts the various taxes will be
posted to. Define G/L accounts for the account keys used in the tax procedure.
See also
SAP Library -> Logistics -> Country Versions -> India -> Materials Management (MM) ->
Condition-Based Excise Determination.
13.7.7.7 MM-PUR-GF-REL
Release (Approval)
13.7.7.7.1 Release Transactions in New Interactive Design
Use
As of SAP Release 4.70, the release (approval, clearance) facility for purchasing documents is available
______________________________________________________________
SAP AG
306
SAP System
______________________________________________________________
in the new interactive design just like the existing functionality for creating, displaying and maintaining
requisitions and purchase orders.
With the Release Purchase Requisition (ME54N) and Release Purchase Order (ME29N) transactions,
an authorized person can display the current version of a requisition or PO and - without switching
transactions - effect release with his or her release codes on the basis of this information.
Note
These transactions enable you not only to release but also to reject a requisition or requisition item.
13.7.7.7.2 New Workflows for Refusal to Release (Rejection) (New)
Use
As of Release 4.70, new workflows are available for the release procedure:
o
Refuse Individual Release of Purchase Requisitions
workflow WS65400027, task TS65400032
o
Refuse Overall Release of Purchase Requisitions
workflow WS65400029, task TS65400034
These workflows enable you to inform the creator of a purchase requisition of the rejection of the
requisition. The individual concerned then receives a work item with which he or she can process
the rejected requisition in Change Purchase Requisition (ME52N).
o
Refuse Release of Purchase Orders
workflow WS65400030, task TS65400035
This workflow enables you to inform the creator of a purchase order of the rejection of the PO. The
individual concerned then receives a work item with which he or she can process the rejected PO in
Change Purchase Order (ME22N).
13.7.7.8 MM-PUR-GF-OC
Message Determination
13.7.7.8.1 Reminder Level as Selection Criterion for Reminders and Expediters
relating to Purchasing Documents (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), a further selection criterion is available for the
issue of reminders and expediters relating to purchasing documents with delivery schedule lines: the
maximum reminder level. You can thus enter the desired number of reminders and/or expediters when
making your selection (ME91, ME91A, ME91E, ME91F), so that only those documents that have
reached the reminder level specified are found and displayed.
______________________________________________________________
SAP AG
307
SAP System
______________________________________________________________
13.7.8 MM-PUR-VM
Vendor-Material Relationships and Conditions
13.7.8.1 Calculating Planned Delivery Time
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can calculate and change planned
delivery times.
This function enables you to procure goods from your vendors more easily and, thereby, avoid
out-of-stock or overstock situations in the warehouse.
Up until now, the data had to be maintained manually for the planned delivery time in 3 different places:
o
At vendor level
o
At material level
o
At purchasing info record level.
The values that are maintained manually in these areas are, however, largely based on values gained from
experience. They would quickly become invalid if the vendor's behavior changed.
The new function allows you to:
1.
Calculate the planned delivery time.
When calculating the planned delivery time, the system determines the number of days between the
purchase order being placed with the vendor and the actual goods receipt. The system calculates this
for any combinations of vendor, plant, material, purchasing organization, and vendor subrange.
2.
Change the planned delivery time data.
This function helps you decide whether you would like to retain the planned delivery time you
entered manually or whether you would like to replace it with the planned delivery time calculated
by the system. You can make this decision for every single value in the master data for the vendor,
material and purchasing info record.
Note that any change you make to the planned delivery times could affect procurement.
Important: The system calculates the planned delivery time in calendar days, not in working days.
Effects on System Administration
SAP recommends you use this function regularly.
Effects on Customizing
You do not need to make any Customizing settings.
13.7.8.2 MM-PUR-VM-SET
Subsequent Settlement
13.7.8.2.1 Updating of Business Volume in Customer Settlements
______________________________________________________________
SAP AG
308
SAP System
______________________________________________________________
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the customer settlement
document in agency business to update bonus-relevant business volumes for subsequent settlement in
Purchasing (MM-PUR-VM-SET).
When you generate customer settlements from single settlement requests, the system updates the business
volumes that are relevant to subsequent settlement and posts the provisions for accrued income based on
the document conditions in the customer settlement. The system determines the condition records for the
subsequent settlement independent of the settings in the copying control (from the single settlement
request to the customer settlement).
Effects on System Administration
In the sales area data of the customer master, there is a new indicator - Document Index Active - that is
the same as the indicator in the vendor master. If you want to use the subsequent updating of business
volume in the customer settlement, you have to set this indicator for all the customers for whom you
expect retroactive rebate arrangements in the course of the year.
Note that this indicator is only valid for customer settlements. If you want to include single settlement
requests in the subsequent updating of business volume too, you must also set the indicator, Subsequent
Update in Accordance with Indicator in Customer Master in Subsequent Settlement Control
(transaction WMN9).
Effects on Customizing
In Subsequent Settlement in Customizing, you can enter the residence time for archiving for the
document category, Customer Settlement.
In Customizing for billing types under Agency Business, you can use the Additional Item Data field to
include purchasing condition records (especially condition records from subsequent settlement) in pricing
in the customer settlement. If you set this indicator, the system determines the relevant data (purchasing
organization, invoicing party, different invoicing party) from the single settlement request. Otherwise the
fields are empty during the price determination in customer settlement, and condition records that relate
to these fields are deleted from the price determination.
13.7.8.2.2 Discontinued Functions in Subsequent Settlement
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can no longer use the following
functions:
o
Settlement with a credit memo as a settlement document
You can no longer use this form of settlement. Use vendor billing documents instead. For more
information, see the release notes - Converting Subsequent Settlement to Vendor Billing Documents
for Release 4.5.
o
External data transfer using reports "RWMBONF0", "RWMBONF1" and "RWMBONF2"
You can no longer use these reports to transfer data externally. For more information, see the release
notes - New Functions in Subsequent Settlement for Release 4.6A and in particular the section on
external data transfer.
______________________________________________________________
SAP AG
309
SAP System
______________________________________________________________
You can only use the old reports for recompiling data if an error occurs. Note that the reports are not
completely Unicode-compliant. No data files in Unicode format can be processed. Only existing
ASCII files - files on the application server - can be read for recompilation purposes.
Files on a front end (for example, on a PC) - these are files that are in binary format for technical
reasons - can no longer be read after a conversion to Unicode. Therefore, they must be converted
into ASCII format and stored on an application server.
It was already documented in earlier releases that the functions named here would be discontinued. Up
until now, the old functions were available in parallel with the new. You can no longer use the old
functions.
See also
For more information, see the documentation on SAP Retail (SAP Library -> Logistics -> SAP Retail)
under Purchasing -> Subsequent Settlement.
13.7.8.2.3 Reorganization of Information Structures for Business Volume and
Incom
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use a new function to reorganize the
information structures for business volume and income. This function was already announced for 4.6C,
but was not released until now.
Read the release notes on the reorganization of business volume and income for Release 4.5.
A performance measure was introduced for the purposes of parallel processing. The rebate arrangements
that are to be processed are valuated for the runtime in a start operation. This process has the advantage
that the rebate arrangements that are performance-intensive are processed first. This way, the processes
and system resources that are available are put to optimal use and the total runtime for the processing is
minimized.
See also
For more information, see the documentation on SAP Retail (SAP Library -> Logistics -> SAP Retail)
under Purchasing -> Subsequent Settlement.
13.7.8.3 MM-PUR-VM-CON
Conditions
13.7.8.3.1 Copying Rules for Conditions in Purchasing (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can also define new copying rules for
Conditions in Purchasing. The copying function enables you to create new condition records from
existing ones with minimum effort. You establish relationships between source and target condition
tables and define selection criteria for condition records in the copying rules.
______________________________________________________________
SAP AG
310
SAP System
______________________________________________________________
Hitherto it was only possible to define new copying rules for condition records in Sales and Distribution
(SD).
Effects on Customizing
The activity can be found in Customizing for Purchasing under:
-> Conditions -> Define Price Determination Process -> Copy Control For Conditions
13.7.9 MM-PUR-OA
13.7.9.1 MM-PUR-OA-SCH
Vendor Outline Agreements
Scheduling Agreement
13.7.9.1.1 New Change Pointers for Condition Records (WIND)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you have the following additional options for
adjusting documents in condition changes:
o
Direct entries in the worklist after condition changes
o
Including additional data in an entry in the worklist
In the previous procedure, the entries were created in the worklist based on the change pointers for
condition changes (message type CONDBI) in worklist creation (transaction ME14). In the new
procedure, the change pointers are no longer needed. When a condition is changed, entries are created
directly in the worklist. This removes the previous step in the process of creating the worklist from
change pointers, which was very performance-intensive. In addition, you do not have to create change
pointers for condition changes if they are not going to be used in other processes.
The Customizing that was valid for the previous worklist creation and that defines which condition types
should be included in the worklist (table T6I1) is also valid for the direct entry. However, there are
additional filter options in the new procedure. You can define for each document category for which
types of condition changes (amount change, validity, pricing relevance) entries should be made in the
worklist. There is also a BAdI that is dependent on the document category filter criterion with which
customer-defined filter criteria can be implemented.
The following example describes the options offered by the BAdI:
Due to changing purchasing conditions, perishable materials are regularly repriced in short time periods.
Therefore, sales prices do not need to be updated using the pricing worklist procedure. Use the material
type, in this case, as an additional filter criterion in the retail pricing application (document category 10).
When the basic purchase price of a perishable material is changed, the system does not create a worklist
entry for this document category due to the filter criterion that was implemented.
The additional data in a worklist entry consists of header data from the conditions with which you can
improve performance for the follow-on processing and of variable customer fields with which you can
carry out selective subsequent processing. You make settings in Customizing for filling the customer
fields (table T6I2S).
Effects on Existing Data
______________________________________________________________
SAP AG
311
SAP System
______________________________________________________________
If you do not use change pointers for condition changes, the level of data for change pointers is reduced
considerably. A change pointer generally consists of several entries in table BDCP and BDCP2.
The following changes are made:
o
The width of table WIND increases from 45 to 262 bytes due to the additional tables.
o
The number of table entries in the worklist can be reduced due to the additional filter criteria.
o
Change pointers are no longer needed for message type CONDBI.
Effects on System Administration
The process step for creating the worklist from change pointers (transaction ME14) is no longer needed in
the new procedure.
The check for existing document indexes (table S111) that can be used in the previous worklist creation
must be implemented as an additional filter criterion in the BAdI (see example coding).
The migration of the worklist from the old to the new worklist entries is carried out using report
RMEBEMIG. The report enhances the entries that are available using information from the condition
records.
If you are converting from the old to the new procedure, a special adjustment procedure is required for
every document category. This procedure is described in each of the applications that use the new
procedure.
Effects on Customizing
Implement the new Customizing for the direct creation of worklist entries. If you are installing this for
the first time or if you have not yet used the document adjustment function for a certain document
category, set the indicator manually for migration and direct entry in Customizing. When converting from
the old to the new procedure, the indicators in the migration procedure are set automatically.
You also determine the types of condition changes for each document category as filter criteria for which
worklist entries should be created and how the variables should be filled.
Once you have made settings for direct entries in the worklist for all the document categories used, you
do not have to create change pointers from message type CONDBI. Deactivate message type CONDBI in
ALE Customizing.
You can also carry out this deactivation using the migration report.
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Master Data -> Conditions ->Automatic Updating of Documents After Condition Changes.
13.7.10 MM-PUR-REQ
Purchase Requisitions
13.7.10.1 PBET: Version Posting Date Derivation (Changed)
Use
______________________________________________________________
SAP AG
312
SAP System
______________________________________________________________
As of SAP R/3 Enterprise Public Services 1.10, the Funds Management posting date for period-based
encumbrance tracking (PBET) can be derived from the version posting date of purchasing documents
(purchase requisition and purchase order).
Effects on Existing Data
No impact on existing data.
Effects on Customizing
You have to activate version management for the purchasing documents.
13.7.10.2 Purchase Requisitions Generated from Sales Orders Update FM
(Changed)
Use
As of SAP R/3 Enterprise Public Services 1.10, a purchase requisition that is generated out of an SD
order line item creates a commitment line in Funds Management (FM). Budget can be assigned during
this update.
Effects on Existing Data
Existing purchase requisitions cannot be updated automatically. This means that the new function applies
only to newly created SD order lines.
Effects on Customizing
The purchase requisitions are treated as normal purchase requisitions in FM, so no special customizing is
needed.
13.7.10.3 Stock Transfer Orders Can Update Funds Management Commitment
Use
As of SAP R/3 Enterprise Public Services 1.10, the stock transfer order process is supported by Funds
Management (FM). Purchase orders and requisitions for stock transfers are updated in FM as
commitments. The purchase order is reduced by the goods issue (with PO reference).
Effects on Existing Data
Existing data is not automatically transferred into FM.
Effects on System Administration
You must activate this feature using the BADI ME_COMMITMENT_STO_CH. Activating it triggers an
update in other modules (such as Controlling and Grants Management) also.
Effects on Customizing
No additional customizing is required.
______________________________________________________________
SAP AG
313
SAP System
______________________________________________________________
13.7.10.4 Continuation of Conventional Purchase Order and Requisition
Transactions
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), please note the following planning regarding the
conventional PO (ME21, ME22, ME23) and purchase requisition transactions: (ME51, ME52, ME53):
Maintenance:
An appropriate maintenance service will continue to be available for bugs that occur during interactive
use or during use of the batch input facility in Release Enterprise Core 4.70.
Further development:
There will be no further development of the conventional purchase order and purchase requisition
transactions.
Future releases:
SAP reserves the right to discontinue the conventional PO and requisition transactions in future releases.
13.7.10.5 Enjoy Purchase Requisition - Assign and Process (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), in the further processing of requisitions you can
access virtually all the processing and interface functions of the Enjoy purchase requisition transaction to
easily assign sources and convert requisitions into follow-on documents (RFQs or POs).
The further processing of requisitions can now be carried out via a user-friendly single-screen transaction
with three screen areas in accordance with the Enjoy approach.
o
You can make changes to individual requisitions or access multiple requisitions
o
The assignment of individual or multiple requisitions to sources of supply is accelerated
o
The targeted conversion of requisitions into RFQs and POs is facilitated
Transaction ME57 thus also provides you with all the functions of the conventional transactions ME56
and ME58.
Prerequisites:
Activate Enjoy further processing via ALV grid control in the selection window via the scope of list (see
also Effects on Customizing). As a result, the lists are also accessible to disabled/handicapped users.
Effects on Customizing
To be able to activate the ALV grid list via the list scope, make the following setting in Customizing:
______________________________________________________________
SAP AG
314
SAP System
______________________________________________________________
o
Maintain Purchasing Lists -> Define Scope of List -> Detail View: select Use ALV Grid Control
indicator
13.7.10.6 Automatic Generation of Purchase Orders from Requisitions in New
Interactive Design
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the new Enjoy transaction ME59N to
automatically generate POs from purchase requisitions. This new transaction also satisfies requirements
regarding accessibility to disabled/handicapped persons.
The new transaction for automatic PO generation also provides the following options:
o
The following options are available for the log:
-
No details
-
Error messages only
-
All messages (i.e. including warning messages)
o
You can now release against different contracts in a single purchase order. This is controlled via the
additional parameter ' per contract'.
o
The results are shown in interactive lists. You can go directly to the underlying requisition, the
assigned contract, or the generated purchase order.
o
You also have various export options for the list of results:
-
Unconvertiert
-
Spreadsheet
-
Rich text format
-
HTML format
13.7.11 MM-PUR-PO
Purchase Orders
13.7.11.1 PBET: Version Posting Date Derivation (Changed)
Use
As of SAP R/3 Enterprise Public Services 1.10, the Funds Management posting date for period-based
encumbrance tracking (PBET) can be derived from the version posting date of purchasing documents
(purchase requisition and purchase order).
______________________________________________________________
SAP AG
315
SAP System
______________________________________________________________
Effects on Existing Data
No impact on existing data.
Effects on Customizing
You have to activate version management for the purchasing documents.
13.7.11.2 Stock Transfer Orders Can Update Funds Management Commitment
Use
As of SAP R/3 Enterprise Public Services 1.10, the stock transfer order process is supported by Funds
Management (FM). Purchase orders and requisitions for stock transfers are updated in FM as
commitments. The purchase order is reduced by the goods issue (with PO reference).
Effects on Existing Data
Existing data is not automatically transferred into FM.
Effects on System Administration
You must activate this feature using the BADI ME_COMMITMENT_STO_CH. Activating it triggers an
update in other modules (such as Controlling and Grants Management) also.
Effects on Customizing
No additional customizing is required.
13.7.11.3 Release of Enjoy BAPIs: BAPI_PO_CREATE1 and BAPI_PO_CHANGE
(New)
Use
The new BAPIs BAPI_PO_CREATE1 and BAPI_PO_CHANGE are officially released as of SAP R/3
Enterprise Core 4.70 (SAP_APPL 470). Both BAPIs are based on the function logic of the Enjoy
purchase order:
Both BAPI_PO_CREATE1 and BAPI_PO_CHANGE provide the following new options:
o
You can create or change partners individually (except for the partner role LF - vendor).
o
You can supply or change the delivery address in the BAPI.
o
Header and item texts can be processed by the BAPIs.
o
You can also define the item categories with the external display values (e.g. "B" instead of "1").
o
You can create, change, and delete condition records using the BAPIs and carry out a new price
determination (pricing) process.
o
The configuration (e.g. as BOM in subcontracting) can be used in the BAPIs (but only if existing
______________________________________________________________
SAP AG
316
SAP System
______________________________________________________________
configurations or BOMs are used.
o
You can create or change subitems.
o
The BAPIs have an ALE interface and can be invoked via EDI.
o
Purchase orders can nw also be saved with the status On Hold via the BAPIs (but note that service
and third-party orders cannot be put on hold).
The following special functions are available in the case of the BAPI BAPI_PO_CREATE1:
o
You can create the PO with reference to another document (RFQ, requisition, contract, scheduling
agreement, or another PO).
o
You can define the vendor address in addition to the delivery address in the BAPI_PO_CREATE1.
o
Version Management can also be used with the BAPI_PO_CREATE1.
o
Import/export data can be supplied.
o
Numbering of PO items can be influenced via the BAPI.
o
A warning message heuristic indicates when interfaces are likely to be populated incorrectly.
The following special function is effective in BAPI_PO_CHANGE:
o
A firewall prevents the manipulation of data that, according to the business logic of the purchase
order, is not changeable in Purchasing (such as the PO number, vendor, etc.).
13.7.11.4 Consignment Also Possible on Cross-Company-Code Basis (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can also order for consignment stock from
supplying plants belonging to other company codes, i.e. using the item category consignment. Up to and
including Release 46C, it was not possible to create a cross-company-code purchase order with the item
category consignment.
Effects on Customizing
The following field has been added in Customizing for Purchasing under Purchase Order -> Set Up Stock
Transport Order -> Assign Delivery Type and Checking Rule (T161V):
- DT Consgt (delivery type for stock transfers to consignment stock)
______________________________________________________________
SAP AG
317
SAP System
______________________________________________________________
13.7.11.5 Different Delivery Types in a Single Stock Transfer Document (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), it is possible to include both cross-company-code
and intra-company-code stock transfer items in a single document.
Up to and including Release 4.6C, only one delivery type could be specified via the document type and
the issuing (supplying) plant. As of SAP R/3 Enterprise, two new fields enable you to specify one
delivery type in the cross-company-code case (cross company logic) and one in the internal case (internal
posting logic).
Effects on Customizing
The following fields have been added in Customizing for Purchasing under Purchase Order -> Set Up
Stock Transport Order -> Assign Delivery Type and Checking Rule (T161V):
-
Delivery Type 1 (Delivery type for stock transfers within a company code) and
-
Delivery Type 2 (Delivery type for stock transfers between two company codes)
13.7.11.6 Continuation of Conventional Purchase Order and Requisition
Transactions
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), please note the following planning regarding the
conventional PO (ME21, ME22, ME23) and purchase requisition transactions: (ME51, ME52, ME53):
Maintenance:
An appropriate maintenance service will continue to be available for bugs that occur during interactive
use or during use of the batch input facility in Release Enterprise Core 4.70.
Further development:
There will be no further development of the conventional purchase order and purchase requisition
transactions.
Future releases:
SAP reserves the right to discontinue the conventional PO and requisition transactions in future releases.
13.7.11.7 Automatic Generation of Purchase Orders from Requisitions in New
Interactive Design
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use the new Enjoy transaction ME59N to
automatically generate POs from purchase requisitions. This new transaction also satisfies requirements
______________________________________________________________
SAP AG
318
SAP System
______________________________________________________________
regarding accessibility to disabled/handicapped persons.
The new transaction for automatic PO generation also provides the following options:
o
The following options are available for the log:
-
No details
-
Error messages only
-
All messages (i.e. including warning messages)
o
You can now release against different contracts in a single purchase order. This is controlled via the
additional parameter ' per contract'.
o
The results are shown in interactive lists. You can go directly to the underlying requisition, the
assigned contract, or the generated purchase order.
o
You also have various export options for the list of results:
-
Unconvertiert
-
Spreadsheet
-
Rich text format
-
HTML format
13.7.11.8 Supplementation of Personal Settings in Enjoy Purchase Order
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can make the following new personal
settings:
1. There are two new indicators among the basic settings for Additional Planning (SAP Retail):
-
Selection Screen: This indicator enables you to specify that you are to be able to define new
selection criteria with each "additional requirements planning" run.
-
Default Quantity: This indicator enables you to specify that the SAP system is to determine
default quantities for the additional items.
2. In the case of the default values for the PO item, you can use the new Always Propose indicator to
specify whether the values maintained in your personal settings are to take priority over any values from
preceding documents (requisitions or contracts, for instance).
______________________________________________________________
SAP AG
319
SAP System
______________________________________________________________
13.7.11.9 Underdelivery Tolerance in the Case of Stock Transport Orders (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can activate the underdelivery tolerance for
stock transport orders for goods issues too. A new indicator is available for this purpose in Customizing
for the stock transport order, enabling you to specify the combination of issuing and receiving plants in
respect of which the the defined underdelivery span is tolerated. In the event of underdelivery within the
tolerance limit, the indicator causes the "Outward Delivery Completed" Indicator to be set automatically
in the purchase order and prevents any follow-on processes (planned order, production order) from being
triggered in the issuing plant.
Effects on Customizing
To activate the underdelivery tolerance, select the relevant indicator in Customizing for Purchasing
under:
-
Purchase Order -> Set Up Stock Transport Order -> Assign Document Type, One-Step
Procedure, Underdelivery Tolerance.
13.7.11.10 Create a Subcontract Order with Batch Number (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can determine in Purchasing, as early as
when you create a subcontract order, which batch of the subcontracting component (material provided) is
to be delivered to the subcontractor. This may be useful if the material for the subcontracting requires
specific characteristics that you map onto your system using batches.
In order to be able to display the batch numbers from the purchase order during the transfer posting of the
material provided, from the normal storage location stock to the stock of material provided to vendor, you
must refer to the purchase order; a collective posting is not possible.
Transfer posting via the SC stock monitoring list
With the report on SC stock monitoring for vendor (transaction code ME2O) it is possible to display the
batches of the material provided and make a transfer posting directly into the stock of material provided
to vendor.
On the initial screen of the report, you can use the indicator Group by batches to determine how the batch
information should be displayed.
Goods receipt posting in Inventory Management
During the goods receipt posting to the subcontract order with transaction MIGO or MB01, the batch
number from the purchase order is the default suggestion for the consumption posting of the
subcontractor components. You can change this default value if necessary.
See also
For more information on batch management in Materials Management, refer to the SAP Library under
Logistics -> Materials Management -> Inventory Management -> Inventory Management and
______________________________________________________________
SAP AG
320
SAP System
______________________________________________________________
Physical Inventory -> Batch Management.
For more information on subcontracting in Materials Management, refer to the SAP Library under
Logistics -> Materials Management -> Inventory Management -> Inventory Management and
Physical Inventory -> Special Stocks and Special Forms of Procurement -> Subcontracting.
13.7.11.11 Improved Performance with Investment Buying
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system is able to process condition
changes relevant for Investement Buying more quickly.
The new functions bring the following improvements:
o
The length of the time frame needed is reduced
o
Fewer system resources are required
o
The dataset in the database and in internal tables is reduced
The process has been changed at the following points:
o
When maintaining condition changes, the system writes an entry directly in table WIND.
o
The Investment Buying algorithm has been reduced, which concerns the dataset selected and the
steps running internally.
o
You can choose whether the system performs a listing check. This can improve runtime if only part
of the whole assortment is listed in the selected plants.
Effects on Existing Data
In order to keep the amount of data in the database to a minimum, program RWVLB00C needs to be
scheduled regularly. This program replaces program MEI5.
Effects on System Administration
Program RWVLB00C should be scheduled at regular intervals.
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Purchasing -> Ordering -> Order Optimizing.
13.7.11.12 Calculating Planned Delivery Time
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can calculate and change planned
delivery times.
This function enables you to procure goods from your vendors more easily and, thereby, avoid
______________________________________________________________
SAP AG
321
SAP System
______________________________________________________________
out-of-stock or overstock situations in the warehouse.
Up until now, the data had to be maintained manually for the planned delivery time in 3 different places:
o
At vendor level
o
At material level
o
At purchasing info record level.
The values that are maintained manually in these areas are, however, largely based on values gained from
experience. They would quickly become invalid if the vendor's behavior changed.
The new function allows you to:
1.
Calculate the planned delivery time.
When calculating the planned delivery time, the system determines the number of days between the
purchase order being placed with the vendor and the actual goods receipt. The system calculates this
for any combinations of vendor, plant, material, purchasing organization, and vendor subrange.
2.
Change the planned delivery time data.
This function helps you decide whether you would like to retain the planned delivery time you
entered manually or whether you would like to replace it with the planned delivery time calculated
by the system. You can make this decision for every single value in the master data for the vendor,
material and purchasing info record.
Note that any change you make to the planned delivery times could affect procurement.
Important: The system calculates the planned delivery time in calendar days, not in working days.
Effects on System Administration
SAP recommends you use this function regularly.
Effects on Customizing
You do not need to make any Customizing settings.
13.7.11.13 Order Cancelation
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) it is much easier to process order cancelations
since you are now in a position to delete overdue/incorrect purchase orders and to change the delivery
date of a purchase order.
You process order cancelations in the Planning Workbench.
You can process order cancelations online or in the background.
See also
For more information, see the SAP Retail documentation (SAP Library -> Logistics -> SAP Retail) under
Purchasing -> Requirements Planning -> Planning Workbench.
______________________________________________________________
SAP AG
322
SAP System
______________________________________________________________
13.7.11.14 Progress Tracking (New)
Use
As of SAP R/3 Enterprise PLM Extension 1.10 (EA_APPL 110), the Progress Tracking function is
available as part of the Project System and Materials Management.
Progress Tracking enables you to closely monitor the progress of network components in the Project
System and purchase orders in Materials Management. By tracking events that you have defined yourself
in Customizing for Progress Tracking or in the Progress Tracking function itself, you gain improved
control over the progress of your network components or purchase orders. For example, for tracking a
purchase order you could create events for internal occurrences such as issuing a purchase order. For
tracking a network component, your events could include goods issue, and goods receipt. Scheduling
dates for events allows you to analyze variances and recognize problems early on. You can also stipulate
dates for events using enhancements for either system dates or external data.
The Progress Tracking function has a clearly arranged and intuitive interface that is independent of the
current object that you are tracking. The appearance of the interface is flexible: You can adapt the initial
selection screen to your own needs by including customer-specific fields and on the main Progress
Tracking screen, which is made up of two SAP List Viewer (ALV) overviews, you can define and
maintain user or application-specific layouts.
Although Progress Tracking contains all the capabilities of the Monitoring Dates function that is found in
the Project System in SAP Release 4.6, Progress Tracking has a much more generic approach that allows
it to be used for other objects, such as purchase orders.
In comparison to Monitoring Dates, Progress Tracking offers among other things:
o
Comprehensive Customizing for creating default settings
o
A far more attractive user interface, for which user and application- specific layouts can be created
and where it is possible to filter, group and total the displayed entries
o
The option of including customer-specific fields
o
A multitude of BAdIs which provide diverse options for fulfilling particular customer requirements
Effects on Customizing
To use Progress Tracking, complete the following steps in the Implementation Guide (IMG) for the
Project System or Materials Management by choosing Logistics -> Project System -> Progress ->
Progress Tracking or Logistics -> Materials Management -> Purchasing -> Purchase Orders ->
Progress Tracking.
o
Define Standard Events
o
Define Event Scenarios
o
Maintain Relationships Between Events in a Scenario
o
Assign Default Scenarios to Material Groups
o
Maintain Priorities for an Event
o
Define Progress Tracking Profile
o
Define Status Info Types
______________________________________________________________
SAP AG
323
SAP System
______________________________________________________________
o
Number Range Status Information
o
Customer-Specific Evaluations
See also
For more information about Progress Tracking, refer to the SAP Library: Logistics -> Project System
-> Progress Tracking or Logistics -> Materials Management -> Purchasing -> Progress Tracking.
13.8 MM-SRV
External Services
13.8.1 MM-SRV-SR
Service Entry
13.8.1.1 Returns for Service Entry Sheets from Time-Sheets (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can retrospectively change a time or quantity
in a time sheet that you have already converted into a service entry sheet. As soon as you convert the
changed time sheet into external services, the system additionally generates both a service entry sheet
with the new data and one in which the original data has been cancelled and in which the Returns
Indicator has been set.
Note:
A return is only possible if a time sheet is used and converted into external services
(CATS/CATM)
The returns indicator cannot be selected manually but is set by the system when a changed
time sheet is converted into external services.
Effects on Existing Data
The additionally generated returns sheet cancels the already existing service entry sheet. You can check
this in the PO history for the underlying purchase order.
Effects on Customizing
To facilitate the use of the returns function for time sheets during the service entry process, you must
select the relevant Activation Indicator in Customizing for External Services Management:
Source Determination and Default Values -> Specify for Client -> Returns Active.
13.9 MM-IM
Inventory Management
13.9.1 Goods Movements and Excise Documents Combined (New)
Use
______________________________________________________________
SAP AG
324
SAP System
______________________________________________________________
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), users working in manufacturing plants can enter
incoming and outgoing excise invoices when they enter a goods receipt or goods issue in the standard
Goods Movements transaction, MIGO.
Users working in depots can enter incoming excise invoices when they enter a goods receipt. When they
enter a goods issue, they can assign the appropriate register RG 23D entries to it.
Other excise documents are also supported, for example, subontract orders. For more information, see the
documentation mentioned below.
Incoming Excise Invoices
When goods are delivered to your company, the user runs the Goods Movements transaction and enters
the goods receipt details and the excise invoice information on the same screen: For these purposes, SAP
has added two new tabs to the Goods Movements transaction, one for information about the excise
invoice at header level and one for item level.
As well as speeding up your business processes, it also means that the person who enters the goods
receipt can also post the excise duty to the CENVAT account instantly, improving your company's cash
flow.
Outgoing Excise Invoices
Similarly, users can also create and post outgoing excise invoices in the Goods Movements transaction
when they post a goods issue.
Effects on Customizing
Activate the functions for each excise group that wants to work with them, in the MIGO group box in the
IMG activity Maintain Excise Groups.
See also
SAP Library -> Logistics -> Country Versions -> Asia-Pacific -> India -> Materials Management
(MM) -> Goods Movements and Excise Documents Combined.
13.9.2 MM-IM: Overview of Release Infos for SAP R/3 Enterprise Core 470
Use
In the following, you will see an overview of all release infos in the application component MM
Inventory Management for SAP R/3 Enterprise Core 4.70 (SAP_APPL 470). You can also display
the release infos directly.
o
Functional Enhancements in MIGO (changed)
o
Replacing the MB* Transactions with Transaction MIGO (new)
o
Business Add-Ins in Inventory Management (new)
o
Functional Supplement for BAPI CreateFromData (changed)
o
Create a Subcontract Order with Batch Number (new)
o
Output Determination: Program for Creating Condition Records (new)
______________________________________________________________
SAP AG
325
SAP System
______________________________________________________________
o
SAP Smart Forms in Inventory Management (new)
13.9.3 MM-IM-GF
Basic Functions
13.9.3.1 Business Add-Ins in Inventory Management (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following Business Add-Ins (BAdI) are
available:
o
Change item data in transaction MIGO
(MB_MIGO_ITEM_BADI)
o
Maintain external detail subscreens for transaction MIGO
(MB_MIGO_BADI)
o
Check/complete dialog data for transaction MB21/MB22
(MB_RESERVATION_BADI)
Effects on Customizing
Maintain these Business Add-Ins in Customizing for Inventory Management under Maintain Customer
Exits and Business Add-Ins.
See also
For more information on Business Add-Ins, see the SAP Library under Basis -> ABAP Workbench ->
Changes to SAP Standard -> Business Add-Ins.
13.9.3.2 Output Determination: Program for Creating Condition Records (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) there is a program for creating the particular
condition records for output determination in Inventory Management, that are recommended by default
for output determination. The program only creates condition records for goods receipt/issue slips; the
condition records for label printing and mails still have to be created manually.
The program is called Batch input for condition records output determination (RM07NKON). For
more information, see the report documentation.
Effects on Existing Data
This report only creates the condition records if they do not yet exist in the system. Existing condition
records are not overwritten.
See also
For more information on the settings for output determination, see the Implementation Guide (IMG) for
______________________________________________________________
SAP AG
326
SAP System
______________________________________________________________
Inventory Management under Output Determination -> Tips for Fast Setting of Output Determination.
13.9.4 MM-IM-GR
Goods Receipt
13.9.4.1 Functional Supplement for BAPI CreateFromData (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), in the (BAPI) method for posting goods
movements CreateFromData (function module: BAPI_GOODSMVT_CREATE), there are functional
enhancements in the subcontracting area.
With this method, when posting a goods receipt to a subcontract order, component quantities specified in
the subcontract order cannot be changed. Usually only those component quantities specified in advance
can be posted as a goods issue.
Posting a subsequent adjustment was also not possible with this method.
Because of these functional enhancements, the following functions were added:
o
When posting a goods receipt to a subcontract order, it is now possible to change the default
quantities of the components from the purchase order.
The method therefore completely supports the functions of transaction MB01 for the process
"Goods receipt for subcontract order".
o
To be able to take any excess or underconsumptions of component quantities into account
afterwards, you can now also use this method for subsequent adjustment.
The method therefore completely supports the functions of transaction MB04 for the process
"Subsequent adjustment of material provided".
See also
For more information, see the relevant BAPI documentation.
13.9.4.2 Create a Subcontract Order with Batch Number (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can determine in Purchasing, as early as
when you create a subcontract order, which batch of the subcontracting component (material provided) is
to be delivered to the subcontractor. This may be useful if the material for the subcontracting requires
specific characteristics that you map onto your system using batches.
In order to be able to display the batch numbers from the purchase order during the transfer posting of the
material provided, from the normal storage location stock to the stock of material provided to vendor, you
must refer to the purchase order; a collective posting is not possible.
Transfer posting via the SC stock monitoring list
With the report on SC stock monitoring for vendor (transaction code ME2O) it is possible to display the
batches of the material provided and make a transfer posting directly into the stock of material provided
______________________________________________________________
SAP AG
327
SAP System
______________________________________________________________
to vendor.
On the initial screen of the report, you can use the indicator Group by batches to determine how the batch
information should be displayed.
Goods receipt posting in Inventory Management
During the goods receipt posting to the subcontract order with transaction MIGO or MB01, the batch
number from the purchase order is the default suggestion for the consumption posting of the
subcontractor components. You can change this default value if necessary.
See also
For more information on batch management in Materials Management, refer to the SAP Library under
Logistics -> Materials Management -> Inventory Management -> Inventory Management and
Physical Inventory -> Batch Management.
For more information on subcontracting in Materials Management, refer to the SAP Library under
Logistics -> Materials Management -> Inventory Management -> Inventory Management and
Physical Inventory -> Special Stocks and Special Forms of Procurement -> Subcontracting.
13.9.4.3 Functional Enhancements in MIGO (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the transaction for goods movements MIGO
has the following new functions:
o
Transfer Postings and Stock Transfers
You can now also set MIGO for transfer postings and stock transfers. To do this, choose the actions
Transfer posting, Remove from storage or Place in storage from the list box for the business
transaction (Action Can Be Carried Out in the MIGO Transaction).
o
Subsequent Adjustment
It is now also possible to use MIGO for subsequent adjustment in subcontracting. To do this, choose
the action Subsequent adjustment in the list box for business transaction (Action Can Be Carried
Out in the MIGO Transaction) .
o
New Business Add-Ins for MIGO
There are new Business Add-Ins available for MIGO.
See release info Business Add-Ins in Inventory Management.
o
Change Default Values
It is now possible to change the default values for the movement type and special stock indicator
directly, without calling the dialog box for the default values. Enter the desired movement type and
the special stock indicator in MIGO, in the first line on the top right and choose Execute (Enter).
o
Manual Entry of Number of GR Slips to Print
It is now possible to enter manually the number of GR slips to be printed when posting a goods
movement.
The Number of GR Slips field is only visible, if the field in Customizing for MIGO field selection
for each movement type has been included. In Inventory Management Customizing, choose
Settings for Enjoy Transactions -> Settings for Goods Movements (MIGO) -> Field Selection
______________________________________________________________
SAP AG
328
SAP System
______________________________________________________________
per Movement Type.
o
Manual Selection for the Version of GR/GI Slips
It is now possible to enter manally enter the version for the GR/GI slip (individual slip, individual
slip with check text, collective slip). Until now, the system determined the version from the settings
in Customizing (Maintain Conditions).
The system now behaves in the following way:
-
In the header data on the General tab page, the version appears as a list box. When the
material document is displayed, the Print button does not appear if the material document has
not yet been printed. To create messages during the display, you must now select the checkbox
to the right of the printer symbol. Both the checkbox for printing and the version are ready for
input, if messages have not yet been created for the material document.
-
Version proposal:
If the user manually changes the proposed version, this version is held for the current
transaction as the user default and is then proposed during creation of the next document of
this transaction type. If the user does not yet have a user default for the transaction type, the
default version is determined from Customizing (default version per transaction).
-
In the display of the material document, the version saved in the material document is
proposed. The user can change the version in the header data and then start message
determination from the checkbox. The message determination is executed with the manually
changed version. However, the version in the material document is not changed, as this is the
version when the material document is created.
See also
Release info Replacing the MB* Transactions with the Transaction MIGO
13.9.4.4 Replacing the MB* Transactions with Transaction MIGO (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can set the transaction for goods
movements MIGO for transfer postings and stock transfers too, as well as for subsequent adjustment in
subcontracting.
See the release info Functional Enhancements in MIGO.
Therefore, MIGO can replace all conventional transactions for posting goods movements, that start with
MB*.
In this release, you can use both MIGO and the conventional MB* transactions at the same time without
restrictions.
Only SAP, however, can set the maintenance for the conventional MB* transactions in a later version, so
that you can then only use MIGO.
______________________________________________________________
SAP AG
329
SAP System
______________________________________________________________
13.9.4.5 SAP Smart Forms in Inventory Management (new)
Use
As of SAP R/3 Enterprise Core 4.70(SAP_APPL 470), the Smart Form MMIM_GRPO_SINGLE
(goods receipt slip) is available for printing individual slips for goods receipts (message type WE01). The
SAPscript layout is the same as the form WESCHEINVERS1.
Unlike a traditional SAPscript form, Smart Forms offer the following advantages:
o
Create and maintain forms in half the time
o
Adjust forms without program knowledge, thanks to thorough graphical user interfaces
o
Web Publishing with the help of a generated XML output
The SAP Smart Forms replace SAPscript forms. SAPscript forms are still supported and can be used
without modification. SAPscript texts can be used in Smart Forms. The migration of SAPscript forms
into Smart Forms is also supported.
You can create, change and display Smart Forms using transaction SMARTFORMS.
Effects on Customizing
Maintain Smart Form MMIM_GRPO_SINGLE in Customizing for Inventory Management under
Output Determination -> Assign Forms and Programs.
To be able to use the Smart Form, you must assign program SAPFM07P_SMART and Smart Form
MMIM_GRPO_SINGLE to output type WE01:
o
Output type: WE01
o
Program: SAPFM07P_SMART
o
Form routine: ENTRY_WE01
o
Smart Form: MMIM_GRPO_SINGLE
See also
For more information on SAP Smart Forms, see the SAP Library, under Basis -> Basis Services /
Communications Interface (BC-SRV) -> SAP Smart Forms (BC-SRV-SCR).
13.9.5 MM-IM-GI
Goods Issue and Return Delivery
13.9.5.1 Functional Supplement for BAPI CreateFromData (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), in the (BAPI) method for posting goods
movements CreateFromData (function module: BAPI_GOODSMVT_CREATE), there are functional
enhancements in the subcontracting area.
With this method, when posting a goods receipt to a subcontract order, component quantities specified in
______________________________________________________________
SAP AG
330
SAP System
______________________________________________________________
the subcontract order cannot be changed. Usually only those component quantities specified in advance
can be posted as a goods issue.
Posting a subsequent adjustment was also not possible with this method.
Because of these functional enhancements, the following functions were added:
o
When posting a goods receipt to a subcontract order, it is now possible to change the default
quantities of the components from the purchase order.
The method therefore completely supports the functions of transaction MB01 for the process
"Goods receipt for subcontract order".
o
To be able to take any excess or underconsumptions of component quantities into account
afterwards, you can now also use this method for subsequent adjustment.
The method therefore completely supports the functions of transaction MB04 for the process
"Subsequent adjustment of material provided".
See also
For more information, see the relevant BAPI documentation.
13.9.5.2 Functional Enhancements in MIGO (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the transaction for goods movements MIGO
has the following new functions:
o
Transfer Postings and Stock Transfers
You can now also set MIGO for transfer postings and stock transfers. To do this, choose the actions
Transfer posting, Remove from storage or Place in storage from the list box for the business
transaction (Action Can Be Carried Out in the MIGO Transaction).
o
Subsequent Adjustment
It is now also possible to use MIGO for subsequent adjustment in subcontracting. To do this, choose
the action Subsequent adjustment in the list box for business transaction (Action Can Be Carried
Out in the MIGO Transaction) .
o
New Business Add-Ins for MIGO
There are new Business Add-Ins available for MIGO.
See release info Business Add-Ins in Inventory Management.
o
Change Default Values
It is now possible to change the default values for the movement type and special stock indicator
directly, without calling the dialog box for the default values. Enter the desired movement type and
the special stock indicator in MIGO, in the first line on the top right and choose Execute (Enter).
o
Manual Entry of Number of GR Slips to Print
It is now possible to enter manually the number of GR slips to be printed when posting a goods
movement.
The Number of GR Slips field is only visible, if the field in Customizing for MIGO field selection
for each movement type has been included. In Inventory Management Customizing, choose
Settings for Enjoy Transactions -> Settings for Goods Movements (MIGO) -> Field Selection
per Movement Type.
______________________________________________________________
SAP AG
331
SAP System
______________________________________________________________
o
Manual Selection for the Version of GR/GI Slips
It is now possible to enter manally enter the version for the GR/GI slip (individual slip, individual
slip with check text, collective slip). Until now, the system determined the version from the settings
in Customizing (Maintain Conditions).
The system now behaves in the following way:
-
In the header data on the General tab page, the version appears as a list box. When the
material document is displayed, the Print button does not appear if the material document has
not yet been printed. To create messages during the display, you must now select the checkbox
to the right of the printer symbol. Both the checkbox for printing and the version are ready for
input, if messages have not yet been created for the material document.
-
Version proposal:
If the user manually changes the proposed version, this version is held for the current
transaction as the user default and is then proposed during creation of the next document of
this transaction type. If the user does not yet have a user default for the transaction type, the
default version is determined from Customizing (default version per transaction).
-
In the display of the material document, the version saved in the material document is
proposed. The user can change the version in the header data and then start message
determination from the checkbox. The message determination is executed with the manually
changed version. However, the version in the material document is not changed, as this is the
version when the material document is created.
See also
Release info Replacing the MB* Transactions with the Transaction MIGO
13.9.5.3 Replacing the MB* Transactions with Transaction MIGO (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can set the transaction for goods
movements MIGO for transfer postings and stock transfers too, as well as for subsequent adjustment in
subcontracting.
See the release info Functional Enhancements in MIGO.
Therefore, MIGO can replace all conventional transactions for posting goods movements, that start with
MB*.
In this release, you can use both MIGO and the conventional MB* transactions at the same time without
restrictions.
Only SAP, however, can set the maintenance for the conventional MB* transactions in a later version, so
that you can then only use MIGO.
______________________________________________________________
SAP AG
332
SAP System
______________________________________________________________
13.9.6 MM-IM-ST
Stock Transfer/Transfer Posting
13.9.6.1 Stock Transfer Orders Can Update Funds Management Commitment
Use
As of SAP R/3 Enterprise Public Services 1.10, the stock transfer order process is supported by Funds
Management (FM). Purchase orders and requisitions for stock transfers are updated in FM as
commitments. The purchase order is reduced by the goods issue (with PO reference).
Effects on Existing Data
Existing data is not automatically transferred into FM.
Effects on System Administration
You must activate this feature using the BADI ME_COMMITMENT_STO_CH. Activating it triggers an
update in other modules (such as Controlling and Grants Management) also.
Effects on Customizing
No additional customizing is required.
13.9.6.2 Consignment Also Possible on Cross-Company-Code Basis (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can also order for consignment stock from
supplying plants belonging to other company codes, i.e. using the item category consignment. Up to and
including Release 46C, it was not possible to create a cross-company-code purchase order with the item
category consignment.
Effects on Customizing
The following field has been added in Customizing for Purchasing under Purchase Order -> Set Up Stock
Transport Order -> Assign Delivery Type and Checking Rule (T161V):
- DT Consgt (delivery type for stock transfers to consignment stock)
13.9.6.3 Different Delivery Types in a Single Stock Transfer Document (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), it is possible to include both cross-company-code
and intra-company-code stock transfer items in a single document.
Up to and including Release 4.6C, only one delivery type could be specified via the document type and
the issuing (supplying) plant. As of SAP R/3 Enterprise, two new fields enable you to specify one
delivery type in the cross-company-code case (cross company logic) and one in the internal case (internal
______________________________________________________________
SAP AG
333
SAP System
______________________________________________________________
posting logic).
Effects on Customizing
The following fields have been added in Customizing for Purchasing under Purchase Order -> Set Up
Stock Transport Order -> Assign Delivery Type and Checking Rule (T161V):
-
Delivery Type 1 (Delivery type for stock transfers within a company code) and
-
Delivery Type 2 (Delivery type for stock transfers between two company codes)
13.9.6.4 Commitment in Stock Transfer Documents (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can have a commitment generated by the
system in both stock transport requisitions and stock transport orders (for the longer-distance transfer of
materials) and display the commitment in the documents. You activate or deactivate the function via the
Business Add-In ME_COMMITMENT_STO_CH.
You invoke the commitment display for each item from within the already posted document via the
following menu path:
Environment -> FI/CO Commitment Documents
Note:
The commitment of the stock transport requisition is reduced or cancelled out by the stock
transport order. The commitment of the stock transport order is reduced or cancelled out by the
value of the goods issue document.
A commitment can only be generated for items with single account assignment.
Effects on Existing Data
A data record is generated for the individual document items in the table COOI.
Effects on Customizing
The pricing condition type in the calculation schema for stock transfers must be set to non-statistical in
order for the commitment to be updated with the net value:
IMG: MM -> Purchasing -> Conditions -> Define Price Determination Process -> Define
Calculation Schema -> RM2000-> Condition Type P101: Non-statistical
13.9.6.5 Underdelivery Tolerance in the Case of Stock Transport Orders (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can activate the underdelivery tolerance for
stock transport orders for goods issues too. A new indicator is available for this purpose in Customizing
for the stock transport order, enabling you to specify the combination of issuing and receiving plants in
______________________________________________________________
SAP AG
334
SAP System
______________________________________________________________
respect of which the the defined underdelivery span is tolerated. In the event of underdelivery within the
tolerance limit, the indicator causes the "Outward Delivery Completed" Indicator to be set automatically
in the purchase order and prevents any follow-on processes (planned order, production order) from being
triggered in the issuing plant.
Effects on Customizing
To activate the underdelivery tolerance, select the relevant indicator in Customizing for Purchasing
under:
-
Purchase Order -> Set Up Stock Transport Order -> Assign Document Type, One-Step
Procedure, Underdelivery Tolerance.
13.9.6.6 Functional Supplement for BAPI CreateFromData (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), in the (BAPI) method for posting goods
movements CreateFromData (function module: BAPI_GOODSMVT_CREATE), there are functional
enhancements in the subcontracting area.
With this method, when posting a goods receipt to a subcontract order, component quantities specified in
the subcontract order cannot be changed. Usually only those component quantities specified in advance
can be posted as a goods issue.
Posting a subsequent adjustment was also not possible with this method.
Because of these functional enhancements, the following functions were added:
o
When posting a goods receipt to a subcontract order, it is now possible to change the default
quantities of the components from the purchase order.
The method therefore completely supports the functions of transaction MB01 for the process
"Goods receipt for subcontract order".
o
To be able to take any excess or underconsumptions of component quantities into account
afterwards, you can now also use this method for subsequent adjustment.
The method therefore completely supports the functions of transaction MB04 for the process
"Subsequent adjustment of material provided".
See also
For more information, see the relevant BAPI documentation.
13.9.6.7 Create a Subcontract Order with Batch Number (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can determine in Purchasing, as early as
when you create a subcontract order, which batch of the subcontracting component (material provided) is
to be delivered to the subcontractor. This may be useful if the material for the subcontracting requires
specific characteristics that you map onto your system using batches.
______________________________________________________________
SAP AG
335
SAP System
______________________________________________________________
In order to be able to display the batch numbers from the purchase order during the transfer posting of the
material provided, from the normal storage location stock to the stock of material provided to vendor, you
must refer to the purchase order; a collective posting is not possible.
Transfer posting via the SC stock monitoring list
With the report on SC stock monitoring for vendor (transaction code ME2O) it is possible to display the
batches of the material provided and make a transfer posting directly into the stock of material provided
to vendor.
On the initial screen of the report, you can use the indicator Group by batches to determine how the batch
information should be displayed.
Goods receipt posting in Inventory Management
During the goods receipt posting to the subcontract order with transaction MIGO or MB01, the batch
number from the purchase order is the default suggestion for the consumption posting of the
subcontractor components. You can change this default value if necessary.
See also
For more information on batch management in Materials Management, refer to the SAP Library under
Logistics -> Materials Management -> Inventory Management -> Inventory Management and
Physical Inventory -> Batch Management.
For more information on subcontracting in Materials Management, refer to the SAP Library under
Logistics -> Materials Management -> Inventory Management -> Inventory Management and
Physical Inventory -> Special Stocks and Special Forms of Procurement -> Subcontracting.
13.9.6.8 Functional Enhancements in MIGO (Changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the transaction for goods movements MIGO
has the following new functions:
o
Transfer Postings and Stock Transfers
You can now also set MIGO for transfer postings and stock transfers. To do this, choose the actions
Transfer posting, Remove from storage or Place in storage from the list box for the business
transaction (Action Can Be Carried Out in the MIGO Transaction).
o
Subsequent Adjustment
It is now also possible to use MIGO for subsequent adjustment in subcontracting. To do this, choose
the action Subsequent adjustment in the list box for business transaction (Action Can Be Carried
Out in the MIGO Transaction) .
o
New Business Add-Ins for MIGO
There are new Business Add-Ins available for MIGO.
See release info Business Add-Ins in Inventory Management.
o
Change Default Values
It is now possible to change the default values for the movement type and special stock indicator
directly, without calling the dialog box for the default values. Enter the desired movement type and
______________________________________________________________
SAP AG
336
SAP System
______________________________________________________________
the special stock indicator in MIGO, in the first line on the top right and choose Execute (Enter).
o
Manual Entry of Number of GR Slips to Print
It is now possible to enter manually the number of GR slips to be printed when posting a goods
movement.
The Number of GR Slips field is only visible, if the field in Customizing for MIGO field selection
for each movement type has been included. In Inventory Management Customizing, choose
Settings for Enjoy Transactions -> Settings for Goods Movements (MIGO) -> Field Selection
per Movement Type.
o
Manual Selection for the Version of GR/GI Slips
It is now possible to enter manally enter the version for the GR/GI slip (individual slip, individual
slip with check text, collective slip). Until now, the system determined the version from the settings
in Customizing (Maintain Conditions).
The system now behaves in the following way:
-
In the header data on the General tab page, the version appears as a list box. When the
material document is displayed, the Print button does not appear if the material document has
not yet been printed. To create messages during the display, you must now select the checkbox
to the right of the printer symbol. Both the checkbox for printing and the version are ready for
input, if messages have not yet been created for the material document.
-
Version proposal:
If the user manually changes the proposed version, this version is held for the current
transaction as the user default and is then proposed during creation of the next document of
this transaction type. If the user does not yet have a user default for the transaction type, the
default version is determined from Customizing (default version per transaction).
-
In the display of the material document, the version saved in the material document is
proposed. The user can change the version in the header data and then start message
determination from the checkbox. The message determination is executed with the manually
changed version. However, the version in the material document is not changed, as this is the
version when the material document is created.
See also
Release info Replacing the MB* Transactions with the Transaction MIGO
13.9.6.9 Replacing the MB* Transactions with Transaction MIGO (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can set the transaction for goods
movements MIGO for transfer postings and stock transfers too, as well as for subsequent adjustment in
subcontracting.
See the release info Functional Enhancements in MIGO.
Therefore, MIGO can replace all conventional transactions for posting goods movements, that start with
MB*.
In this release, you can use both MIGO and the conventional MB* transactions at the same time without
restrictions.
______________________________________________________________
SAP AG
337
SAP System
______________________________________________________________
Only SAP, however, can set the maintenance for the conventional MB* transactions in a later version, so
that you can then only use MIGO.
13.9.7 MM-IM-VP
Balance Sheet Valuation Procedures
13.9.7.1 Structure Changes in Inflation Accounting
Use
As of SAP R/3 Release 4.70, the Implementation Guide (IMG) for Inflation Accounting is easier to use.
SAP has restructured it, rewritten the documentation, and reworked some of the screens.
Note that only the IMG structure and documentation have changed, but not the views themselves, so you
do not have to make any changes to existing Customizing settings.
Changes in the IMG
Until now, there was one group of IMG activities for Inflation Accounting under Financial Accounting
(FI), and more activities under Asset Accounting (FI-AA) and Materials Management (MM). That
meant that to customize Inflation Accounting for FI-AA, for example, you had to work through the
activities under FI and those under FI-AA.
SAP has now changed the IMG so that each of the components now has its own self-contained IMG for
Inflation Accounting. Now, to customize Inflation Accounting for FI-AA, for example, you no longer
have to work through the IMG activities under Revaluation for the Balance Sheet and then the
activities under Inflation Accounting. Nor do you have to work through the activities under Financial
Accounting -> Financial Accounting Global Settings -> Inflation Accounting. Instead, you just have
to work through the activities under Inflation Accounting. Similarly, the IMG activities for FI and MM
have also been restructured.
The IMGs are still located at the same position in the SAP Reference Structure:
o
Financial Accounting -> Financial Accounting Global Settings -> Inflation Accounting
o
Financial Accounting -> Asset Accounting -> Special Valuation -> Revaluation of Fixed
Assets -> Revaluation for the Balance Sheet -> Inflation Accounting
o
Materials Management -> Valuation and Account Assignment -> Balance Sheet Valuation
Procedures -> Configure Replacement Cost Procedure (Inflation)
Changes in the SAP Library
The Inflation Accounting documentation in the SAP Library has also been split up between the three
components. It is now located under the following paths:
o
Financial Accounting (FI) -> General Ledger Accounting (FI-GL) -> Closing and Reporting
-> Preparing Financial Statements -> Inflation Accounting
o
Financial Accounting (FI) -> Asset Accounting (FI-AA) -> Special Valuation -> Replacement
Values (General) -> Inflation Accounting
o
Materials Management (MM) -> Evaluation -> Balance Sheet Valuation (MM-IM-VP) ->
Replacement Cost Valuation (Inflation)
______________________________________________________________
SAP AG
338
SAP System
______________________________________________________________
13.9.7.2 Enhancements in Balance Sheet Valuation
Use
The following text gives you an overview of the developments within balance sheet valuation for SAP
R/3 Enterprise Core 4.70 (SAP_APPL 470).
o
Integration of Valuation Alternatives
-
You can directly update the table of valuation alternatives (CKMLPR_EB) from balance sheet
valuation. This function is included in the following transactions: MRN0, MRN1, MRN2,
MRN3, MRN9, MRF1, MRL4, MRL5, and MRY1.
-
You can involve the table of valuation alternatives directly in balance sheet valuation. This
function is included in the following transactions:: MRN0 and MRN3 (comparison price),
MRN1 and MRN2 (base price), MRN9 (level assignment), MRL1 and MRL2 (material price),
MRF1 and MRL3 (lowest price comparison).
-
You can adopt prices from the material ledger into the table of valuation alternatives, or update
them as physical inventory prices in the material master (transaction MRY4).
-
You can use additional price fields for adopting prices from the material master into the
valuation alternatives table (transaction MRY2).
-
Youcan display valuation alternatives using a simple list (transaction MRY3). The SAP
standard system does not currently contain any wider-reaching analysis functions.
o
Enhanced Log Function During Material Master Update
In future, each run of the lowest price determination by movement rate (transaction MRN2) during
the update will automatically generate an entry in a special log file. Also, the option for creating
change documents when updating prices in the material master has been enhanced in the following
transactions: MRN0, MRN1, MRN3, MRN9, MRF1, MRL4, MRL5, MRY1, and MRY4.
o
Enhanced Options when Using Report Variants
All parameters will be stored individually in the programs within balance sheet valuation. This has
the advantage that you can then use consistent variant variables. Also, it is now easier to include
other parameters. Odl variants are automatically converted after "collecting" on the selection screen
and subsequent "Save".
o
Entering Document Header Text and Reference Document Number During Automatic Price
Change
You can enter a document header text (BKTXT) and a reference if you perform an automatice price
change in balance sheet valuation using direct update or batch input. This function is included in the
following transactions: MRN0, MRN1, MRN2, MRN3, MRN9, MRF1, MRL4, MRL5, MRY1.
o
Additional Options when Constructing LIFO/FIFO Receipt Data by Document Extract
You can use additional settings when running a document extract for LIFO/FIFO valuation
(transaction MRL9 and MRF3):
-
Storing invoice differneces - If you regularly use the document extract to construct individual
receipt records, it can be useful to avoid placing distributed invoice differences into interim
storage.
______________________________________________________________
SAP AG
339
SAP System
______________________________________________________________
-
o
Inclusion/exclusion of specific document categories - You can explicitly include or exclude the
following document categories: order settlements, account maintenance documents,
non-order-related subsequent debits.
Lowest Price Determination: Link Comparison to Market Price
During the process 'Lowest Price Determination by Market Prices' (transaction MRN0) and
'Loss-Free Valuation' (transaction MRN3) you can make settings to decide which link the
comparison price should have to the market price. The following settings are possible: Lowest price
comparison, comparison price as replacement value or no comparison price. In future in both
processes, you can select several price fields/valuation alternatives. The system adopts the lowest
price.
13.10 MM-IV
Invoice Verification
13.10.1 MM-IV-GF
General Functions
13.10.1.1 CENVAT Credit on Capital Goods after Budget 2000 (Changed)
Use
When you purchase capital goods, you can credit 50% of the excise duty to your CENVAT account as
soon as you receive the goods. This is done when you verify the vendor excise invoice. For the balance
credit which is available it is possible to take it into CENVAT using this functionality. It is also possible
to transfer only a portion of the balance credit into CENVAT.
If you have already taken the credit on capital goods purchases into onhold before April 2000, you can
transfer it to the CENVAT account using this function.
Effects on Existing Data
This procedure is the same for all materials, irrespective of whether the material type indicator is set to A
(assets), C (consumables) or T (tools).
13.10.2 MM-IV-LIV
Logistics Invoice Verification
13.10.2.1 Overview of Developments in Logistics Invoice Verification
Use
The following text gives you an overview of the developments in Logistics Invoice Verification for SAP
R/3 Enterprise Core 4.70 (SAP_APPL 470).
o
All Functions in Logistics Invoice Verification
o
Automatic Quantity and Amount Distribution in Multiple Account Assignment
______________________________________________________________
SAP AG
340
SAP System
______________________________________________________________
o
Displaying MM and FI Document Numbers
o
Clearing the GR/IR Clearing Account for External Service Purchase Orders
o
Enhancements to the Invoice Overview
o
Verifying Freight Invoices in theBackground
o
Enhancement to BAPIs in Logistics Invoice Verification
o
Business Add-Ins in Logistics Invoice Verification
o
EDI: Posting to Material and G/L Accounts Using Customer Exit
o
The include RMMR1MI1 that was used as a replacement for the customer exit in automatic
invoicing plan settlement (MRIS), has been deleted as of SAP R/3 Enterprise Core 4.70
(SAP_APPL 470). To change header and item data in invoicing plan settlement, you should now
use the Business Add-In MRM_MRIS_HDAT_MODIFY (Change Header Data for Invoicing Plan
Settlement), or the Business Add-In MRM_MRIS_IDAT_MODIFY (Change Item Data for
Invoicing Plan Settlement).
o
The customer exit EXIT_RMVKON00_003 and EXIT_RMVKON90_001 (customer exit for
conventional invoice verification) for consigment and pipeline settlement (MRKO) was deleted as
of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470). To change the vendor and document type
in consignment settlement, you should now use the Business Add-In
MRM_MRKO_HDAT_MODIFY. Note that when you switch from consignment settlement in
conventional invoice verification to Logistics Invoice Verification, all documents must have been
settled using the customer exit EXIT_RMVKON90_001.
o
In the transactions Enter Invoice (MIRO), Park Invoice (MIR7), and Enter Invoice for
Verification in the Background (MIRA), you can use segment texts in the vendor line (field
SGTXT) in the header on the Basic Data tab page. The entries in the Document Header Text
(BKTXT) field on the Detail tab page are no longer copied into the segement text of the vendor line.
Instead they are only copied into the documennt header text of the FI document.
o
In the transactions Enter Invoice (MIRO), and Park Invoice (MIR7), you can use the bundle
indicator (field LOTKZ) in the header on the Basic Data tab page for the area Public Sector.
o
In the ArchiveLink: Administration of Stored Documents transaction (OAAD) you can use a
search help for invoice document numbers for business object 2081, document type MMILOGINV.
Effects on Customizing
Late Blocks:
In Customizing for Materials Management, you can make settings to specify when materials are blocked
when you enter an invoice:
o
In the allocation phase, all materials contained in the invoice are blocked.
o
During simulation or posting, materials are blocked if their stock needs to be changed.
o
During posting, materials are blocked if their stock needs to be changed.
For more information, see Customizing for Materials Management -> General Settings for Materials
Management -> Set Up Material Block for Invoice Verification.
______________________________________________________________
SAP AG
341
SAP System
______________________________________________________________
13.10.2.2 All Functions in Logistics Invoice Verification
Use
In SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), as in SAP R/3 4.6C, Logistics Invoice
Verification contains all functions from conventional Invoice Verification, as well as many other
functions, for example, cross-company-code posting and invoice reduction.
The following new transactions have been redesigned after close discussions with customers and usability
experts.
o
Logistics Invoice Verification (MIRO)
o
Document Parking (MIR7)
o
Display/Change Invoice (MIR4)
o
Enter Invoice for Verification in the Background (MIRA)
o
Invoice Overview (MIR6)
o
Release Blocked Invoices (MRBR)
Logistics Invoice Verification completely replaces conventional Invoice Verification in
o
the SAP Easy Access menu
o
the Implementation Guide (IMG)
o
the structure in the SAP Library
Maintenance of conventional Invoice Verification has been discontinued as of SAP R/3 4.6C.
See also
For more information, see the SAP Library under Logistics Invoice Verification.
13.10.2.3 MM-IV-LIV-CRE
Entry
13.10.2.3.1 Automatic Quantity and Amount Distribution for Multiple Account
Assignment
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), on the screen for multiple account
assignment in Logistics Invoice Verification, you can enter varying amounts and quantities. Manual
calculation of amounts is no longer necessary; this means that you can prevent invoices containing
transmission errors.
o
Changing the Total Amount and the Total Quantity
______________________________________________________________
SAP AG
342
SAP System
______________________________________________________________
The total amount and total quantity fields are ready for input. If you enter a total amount or a total
quantity, and choose Check (Enter) or Back (Transfer), this triggers automatic distribution to the
relevant account assignment objects according to the distribution schema.
o
Changing Amounts and Quantities in Account Assignment Lines
If you change amounts and quantities in the account assignment lines, once you choose Check
(Enter), the system adds the total amounts and total quantities. Any total amounts and quantities
that have been recently entered are overwritten by the calculated amounts and quantities - the
system issues a customizable error message.
The automatically calculated values are then used as default values. You can change these values until
you save the invoice.
If roudings occur, these are added to the items with the largest quantity or the greatest amount.
See also
For more information, see the SAP Library under Logistics Invoice Verification in the section Change
Account Assignments.
13.10.2.3.2 Enhancements to BAPIs in Logistics Invoice Verification
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following new methods exist (BAPI =
Business Application Programming Interface). The parentheses contain the name of the relevant function
module.
Business Object IncomingInvoice (incoming invoice)
o
ParkFromData (BAPI_INCOMINGINVOICE_PARK)
Park Invoice
o
SaveFromData (BAPI_INCOMINGINVOICE_SAVE)
Enter Invoice for Verification in the Background
You can use the methods CreateFromData, ParkFromData and SaveFromData to enter incoming
invoices that
o
contain withholding tax
o
contain an amount split, in other words, that post to several vendor lines
o
that contain postings to G/L accounts
o
that contain postings to material accounts
You can display further relevant information using the GetDetail method.
See also
To display more information, choose Tools -> Business Framework -> BAPI Explorer.
For more information, see the relevant BAPI documentation.
______________________________________________________________
SAP AG
343
SAP System
______________________________________________________________
13.10.2.3.3 Displaying MM and FI Document Numbers
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), when you post an incoming invoice, the
system can display invoice document numbers generated in Materials Management, the document
number of the accounting document in Financial Accounting, and the number of the invoice reduction
document where applicable.
Generated document numbers can be displayed in the status line for the following transactions:
o
Enter Invoice (MIRO)
o
Park Invoice (MIR7)
o
Cancel Invoice (MR8M)
o
Invoice Overview (MIR6)
Generated document numbers can be displayed in the output list for the following transactions:
o
Evaluated Receipt Settlement (MRRL)
o
Revaluation (MRNB)
o
Invoicing Plan (MRIS)
o
Invoice Verification in the Background (RMBABG00)
The setting to decide whether the FI document number is also displayed, is made for each user using the
parameter IVFIDISPLAY.
13.10.2.3.4 Clearing the GR/IR Clearing Account for External Service Purchase
Orders
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following new functions are available:
When you enter invoices for external service purchase orders for which no service-based invoice
verification is planned, the GR/IR Clearing (field WEREC) indicator in the item list controls the
postings to the GR/IR clearing account. When you enter invoices, the system sets the GR/IR Clearing
indicator as a default.
o
If the GR/IR clearing indicator is set, then when you post the invoice, the GR/IR clearing account is
cleared completely, even if you only post a partial invoice.
o
If you post partial invoices and do not want the GR/IR clearing account to be completely cleared
when you post, you must deselect the GR/IR clearing indicator.
The final invoice indicator (field EREKZ) then only controls the commitment reduction. When you enter
purchase orders for external services and subsequently enter an invoice, the system does not propose this
______________________________________________________________
SAP AG
344
SAP System
______________________________________________________________
indicator as set.
o
If the final invoice indicator is selected, the commitment is completely reduced.
o
If the final invoice indicator is not selected, this means that if you are expecting further invoices for
thie PO item, the commitment is reduced according to the amount in the invoice you enter.
Note: If you enter invoices for purchase orders that are not for external services, or for external service
purchase orders that are not planned for service-based invoice verification, then the GR/IR clearing
indicator is not displayed in the item list.
If you set the final invoice indicator when you enter an invoice for a service-based invoice verification,
the system automatically sets the GR/IR clearing indicator. This means that the commitments are
completely canceled out and the GR/IR clearing account is completely balanced for the PO item affected.
See also
For more information, see the SAP Library under Logistics Invoice Verification in the section Settlement
of External Service Purchase Orders.
13.10.2.4 MM-IV-LIV-IVB
Invoice Verification in Background
13.10.2.4.1 Enhancements to the Invoice Overview
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the following new functions exist:
Enhanced Selection Criteria
The following selection criteria have been enhanced in the Invoice Overview transaction (MIR6):
o
Document type
o
Reference
o
Document header text
You can select posted invoice documents, and display those invoices in the invoice overview that
o
were created using the BAPI BAPI_INCOMINGINVOICE_CREATE
o
were created using evaluated receipt settlement (ERS)
o
were created with Logistics Invoice Verification using invoicing plan settlement
o
cancel another document
o
were parked
You can also select and edit held and parked invoices that have the following statuses:
o
Held
o
Parked
o
Parked as complete
______________________________________________________________
SAP AG
345
SAP System
______________________________________________________________
Additional Information in the List of Invoice Documents
The following additional information is displayed in the list of invoice documents:
o
Origin of the invoice document
o
Document type
o
Document date
o
Posting date
o
Document header text
See also
For more information, see the SAP Library under Logistics Invoice Verification in the section Invoice
Overview.
13.10.2.4.2 Verifying Freight Invoices in the Background
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), when you enter an incoming invoice for
verification in the background (MIRA), you can assign a transportation service provider. If you select
this, you can settle freight costs with transportation service providers in Logistics Invoice Verification for
background verification.
See also
For more information, see the SAP Library under Shipments in the section Shipment Cost Settlement
with Service Agent.
13.10.3 MM-IV-INT
Interfaces
13.10.3.1 Business Add-Ins in Logistics Invoice Verification
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), Logistics Invoice Verification offers you use
of the following Business Add-Ins (BAdIs) for the transactions Enter Invoice (MIRO), Park Invoice
(MIR7), and Enter Invoice for Verification in the Background (MIRA):
o
BAdI MRM_HEADER_DEFAULT to preassign various header fields
o
BAdI MRM_PAYMENT_TERMS to set terms of payment
o
BAdI MRM_UDC_DISTRIBUTE to distribute unplanned delivery costs. You can distribute
unplanned delivery costs according to your own rules, for example under
o
BAdI MRM_TRANSACT_DEFAULT to preassign various transaction fields
______________________________________________________________
SAP AG
346
SAP System
______________________________________________________________
o
BAdI MRM_WT_SPLIT_UPDATE to change the withholding tax data and the data for a vendor
split
o
BAdI MRM_TOLERANCE_GROUP to set vendor-specific tolerance groups
Other Business Add-Ins:
o
BAdI MRM_RELEASE_CHECK for additional checks before invoices are released, in other words,
you can restrict the list of invoices to be released by defining your own criteria.
o
BAdI MRM_MRIS_HDAT_MODIFY to change header data for invoicing plan settlement
o
BAdI MRM_MRIS_IDAT_MODIFY to change item data for invoicing plan settlement
o
BAdI MRM_MRKO_HDAT_MODIFY to change the document header data for consignment
settlement
Effects on Customizing
You maintain Business Add-Ins in the Implementation Guide (IMG) for Logistics Invoice Verification in
activity Maintain Business Add-Ins for Invoice Verification.
See also
For more information about Business Add-Ins, see the SAP Library under Basis -> ABAP Workbench
-> Changing the SAP Standard (BC) -> Business Add-Ins.
13.11 MM-EDI
13.11.1 MM-EDI-IV
Electronic Data Interchange
Invoice Verification
13.11.1.1 EDI: Posting to Material and G/L Accounts Using Customer Exit
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can use a customer enhancement to
assist you posting to material or G/L accounts during processing of EDI incoming invoices using
Logistics Invoice Verification. To do this, use the enhancement MRMH0002 with the customer exit
EXIT_SAPLMRMH_015.
See also
For more information, see the SAP Library under Logistics Invoice Verification in the section Invoices
Received Via EDI.
______________________________________________________________
SAP AG
347
SAP System
______________________________________________________________
14 LE
Logistics Execution
14.1 LE-MOB
Mobile Data Entry
14.1.1 Business Add-Ins for Logistics Execution (new)
Use
As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics
Execution in the following areas:
o
Warehouse Management
o
Shipping
o
Transportation
o
Mobile Data Entry
Effects on Customizing
To activate the Business Add-In, you have to create an active implementation.
To do so, go to the Customizing for Logistics Execution, and choose
o
o
o
Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management
->
-
Business Add-In for Determining Quant
-
Business Add-In for Determining Storage Type
-
Business Add-In for Determining Storage Unit Type
-
Business Add-In for Entering Inventory Data in Inventory Management
Shipping -> System Modifications -> Business Add-Ins in Shipping
-
Business Add-In for Delivery Processing
-
Business Add-In for Price Determination in the Delivery
-
Business Add-In for Subsequent Outbound Delivery Split
-
Business Add-In for Posting Goods Movements
-
Business Add-In for Additional Header Detail Screen in Delivery Transaction
-
Business Add-In for Additional Item Detail Screen in Transaction
-
Business Add-In for Additional Overview Screen in Delivery Transaction
Transportation --> System Modifications --> Business Add-Ins in Transportation
-
Business Add-In for Checks when Creating a Shipment Cost Document
-
Business Add-In for Creating a Shipment Cost Document
______________________________________________________________
SAP AG
348
SAP System
______________________________________________________________
o
-
Business Add-In for Shipment Cost Account Assignment
-
Business Add-In for Checks During Shipment Cost Processing
-
Business Add-In for Transferring Shipment Cost Items
-
Business Add-In for Saving Shipment Cost Documents
Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry
-
Business Add-In for Queue Determination
14.2 LE-IDW
14.2.1 LE-IDW-CEN
Decentralized WMS Integration
Central Processing
14.2.1.1 Subsequent Changes to the Delivery (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), in inbound and outbound deliveries, you can
subsequently change certain data after it has been distributed by the central Enterprise Resource Planning
system (ERP system) to the decentralized Warehouse Management System (WMS). You can make these
changes in either the central or decentralized system. The interface between the systems performs a
subsequent change in the partner system for the following delivery data that is planned for a comparison:
o
o
o
Changes to the inbound delivery header data
-
Gross and net weight
-
Volume
-
Delivery date
-
Door
-
Delete delivery (only using the interface)
-
External identification
Changes to the inbound delivery item data
-
Gross and net weight
-
Volume
-
Expiration date
-
Delivery quantity
-
Delete delivery item (only using the interface)
Changes to the outbound delivery header data
______________________________________________________________
SAP AG
349
SAP System
______________________________________________________________
o
o
-
Gross and net weight
-
Volume
-
Delivery date
-
Door
-
Delete delivery (only using the interface)
-
Incoterms
-
Route
-
Shipping condition
-
Delivery priority
-
Unloading point
-
Picking date
-
Loading date
-
Shipment date
-
Goods issue date
Changes to the outbound delivery item data
-
Gross and net weight
-
Volume
-
Delivery quantity
-
Delete delivery item (only using the interface)
Changes to the partner data for inbound and outbound deliveries
-
Delete or change a partner from a partner role
-
Change a partner's address
Effects on Customizing
If you have not yet generated a distribution model for inbound and outbound deliveries, you create this
distribution model in Customizing under Logistics -> Logistics Execution -> Decentralized WMS
Integration -> Central Processing -> Distribution -> Generate Distribution Model. Here you set the Use
change management for inbound and outbound deliveries indicator.
If the distribution model for inbound and outbound deliveries already exists, enter the following methods
in the central system manually into the distribution model using ALE Customizing:
o
InboundDelivery.DeliveryChange
o
OutboundDelivery.DeliveryChange
You also set the filter for recipient determination for these methods:
o
From the central system to the decentralized system, recipient determination takes place using the
warehouse number filter.
______________________________________________________________
SAP AG
350
SAP System
______________________________________________________________
o
From the decentralized system to the central system, you can use the logical system filter for
recipient determination if both systems have a release status of SAP R/3 Enterprise.
You then generate the partner profile for the new methods, and distribute the distribution model to the
connected decentralized WMS.
Within the decentralized WMS, a blocking concept must be introduced to ensure that you cannot process
the delivery simultaneously in both systems. To implement this, choose in Customizing Logistics ->
Logistics Execution -> Decentralized WMS Integration -> Central Processing -> Distribution Model ->
Activate Cross-System Lock.
See also
For more information on the cross-system lock, see the SAP Library under Basis -> Client-Server
Technology -> Cross-System Lock (CSL).
14.2.1.2 Delayed Distribution of Inbound and Outbound Deliveries to the
Decentralized Warehouse Management System (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can distribute inbound and outbound
deliveries to the decentralized Warehouse Management System (WMS) with a delay. Here, you can
decide as of which point the inbound or outbound delivery is staged, and can therefore be transferred to
the decentralized WMS.
Effects on Customizing
Make the following settings in Customizing for the warehouse number and the delivery type:
1.
For the warehouse number, set whether deliveries should be distributed directly after they are
created, or with a delay.
For more information, see the Implementation Guide (IMG) under Logistics Execution -->
Decentralized WMS Integration --> Central Processing --> Application --> Activiate Decentralized
WMS. This setting affects all inbound and outbound deliveries that are processed in the relevant
warehouse number.
2.
For the corresponding delivery type, set the distribution mode for the deliveries. The permitted
modes for distributing inbound and outbound deliveries are as follows:
a)
Distribution occurs according to your settings for the warehouse number.
b)
Distribution is suppressed.
c) Distribution occurs immediately after the delivery is created.
For more information, see the Implementation Guide (IMG) under Logistics Execution --> Shipping
--> Deliverie --> Define Delivery Types. You can use this activity to set the distribution for each
delivery type independently of the warehouse number. Note, that any settings you make here
overwrite the settings for the warehouse number.
Note
You can distribute suppressed inbound or outbound deliveries at a time to the decentralized WMS at a
______________________________________________________________
SAP AG
351
SAP System
______________________________________________________________
time of your choosing, by selecting the function 'For Distribution' in the delivery monitor (transaction
VL06).
14.2.2 LE-IDW-DEC
Local Operations
14.2.2.1 Several ERP systems to one decentralized WMS
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), it is technically possible to connect several ERP
systems to one decentralized WMS. This possibility also changes the filter criteria in particular, in as far
as the new filter criterion "logical system" is used to find the ERP system.
For the following methods of the delivery, the central ERP system is determined using the filter criterion
"logical system":
o
InboundDelivery.ConfirmDecentral
o
InboundDelivery.DeliveryChange
o
OutboundDelivery.ConfirmDecentral
o
OutboundDelivery.DeliveryChange
o
OutboundDelivery.SplitDecentral
Effects on Existing Data
For the method GoodsMovement.CreateFromData, the ERP system is still found using the filter criteria
"plant" and "storage location". For this to function correctly, all ERP systems that are connected to a
decentralized WMS must have unique and mutually exclusive plant-storage location combinations. You
should manage inventory for the various ERP systems at plant-storage location level, in order that
inventory differences can be ascribed to one specific ERP system. When you clear inventory
differences, always make an additional selection using the plant-storage location. These fields can be
taken from the free selection.
To clear inventory differences, from the SAP menu choose: Logistics --> Logistics Execution --> Internal
Whse Processes --> Physical Inventory --> In Warehouse Management --> Clear Differences -->
Inventory Management.
The following prerequisites must be fulfilled if you connect several ERP systems to one decentralized
WMS:
o
Unique numbers for master data in the decentralized WMS
The different customer masters, vendor masters, creditor masters, and material masters from the
various ERP systems must have unique numbers, so that a master record can always be read
exclusively on the decentralized WMS.
o
Unique numbers for organizational units in the decentralized WMS
The different plants and storage locations in the decentralized WMS must have unique numbers.
o
Unique numbers for deliveries in the decentralized WMS
Deliveries from different ERP systems must be unique in the decentralized WMS. When you
replicate the deliveries, ensure that the deliveries are unique in the decentralized system.
______________________________________________________________
SAP AG
352
SAP System
______________________________________________________________
Effects on System Administration
If several ERP systems are connected to a decentralized WMS, then existing distribution models must be
changed as described below. For the following methods, the filter criteria for recipient determination are
changed as follows:
o
InboundDelivery.ConfirmDecentral
o
InboundDelivery.DeliveryChange
o
OutboundDelivery.ConfirmDecentral
o
OutboundDelivery.DeliveryChange
o
OutboundDelivery.SplitDecentral
You must perform the following activities for changing the filter criteria once only:
1.
Maintain the filter object type
To do this, from the SAP menu choose: Tools -> ALE -> ALE Development -> Recipient
Determination -> Define Filter Object Type.
Add the following entry to the table
ALE Object Type
LOGSYS
Table Name
TBDLS
Field Name
LOGSYS
2.
Assign the filter object type to a BAPI
To do this, from the SAP menu choose: Tools -> ALE -> ALE Development -> Recipient
Determination -> Assign Filter Object Type to BAPI.
Add the following entries to the table:
Object Type
Method
Filter Object Type
LIKP
CONFIRMDECENTRAL
LOGSYS
LIKP
DELIVERYCHANGE
LOGSYS
LIKP
SPLITDECENTRAL
LOGSYS
BUS2015
CONFIRMDECENTRAL
LOGSYS
BUS2015
DELIVERYCHANGE
LOGSYS
3.
Change the filter criteria in the relevant distribution model for each of the methods mentioned
above.
a)
Maintain the distribution model and distribute the views (see also: Maintain Distribution
Model and Distribute Views)
b)
Create a new filter group containing the following values:
Logical System = Enter the logical ERP system
Warehouse number = Do not enter a value
Because no distribution model exists yet, the distribution model can be generated automatically using the
Customizing activity Generate Distribution Model.
The filter for the above method are generated automatically, as described above.
Effects on Customizing
______________________________________________________________
SAP AG
353
SAP System
______________________________________________________________
Maintain the distribution model in the Implementation Guide. To do this, from Customizing choose: SAP
Web Application Server --> Application Link Enabling (ALE) --> Modelling and Implementing Business
Processes --> Maintain Distribution Model and Distribute Views.
14.2.2.2 Subsequent Changes to the Delivery (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), in inbound and outbound deliveries, you can
subsequently change certain data after it has been distributed by the central Enterprise Resource Planning
system (ERP system) to the decentralized Warehouse Management System (WMS). You can make these
changes in either the central or decentralized system. The interface between the systems performs a
subsequent change in the partner system for the following delivery data that is planned for a comparison:
o
o
o
Changes to the inbound delivery header data
-
Gross and net weight
-
Volume
-
Delivery date
-
Door
-
Delete delivery (only using the interface)
-
External identification
Changes to the inbound delivery item data
-
Gross and net weight
-
Volume
-
Expiration date
-
Delivery quantity
-
Delete delivery item (only using the interface)
Changes to the outbound delivery header data
-
Gross and net weight
-
Volume
-
Delivery date
-
Door
-
Delete delivery (only using the interface)
-
Incoterms
-
Route
-
Shipping condition
-
Delivery priority
______________________________________________________________
SAP AG
354
SAP System
______________________________________________________________
o
o
-
Unloading point
-
Picking date
-
Loading date
-
Shipment date
-
Goods issue date
Changes to the outbound delivery item data
-
Gross and net weight
-
Volume
-
Delivery quantity
-
Delete delivery item (only using the interface)
Changes to the partner data for inbound and outbound deliveries
-
Delete or change a partner from a partner role
-
Change a partner's address
Effects on Customizing
If you have not yet generated a distribution model for inbound and outbound deliveries, you create this
distribution model in Customizing under Logistics -> Logistics Execution -> Decentralized WMS
Integration -> Central Processing -> Distribution -> Generate Distribution Model. Here you set the Use
change management for inbound and outbound deliveries indicator.
If the distribution model for inbound and outbound deliveries already exists, enter the following methods
in the central system manually into the distribution model using ALE Customizing:
o
InboundDelivery.DeliveryChange
o
OutboundDelivery.DeliveryChange
You also set the filter for recipient determination for these methods:
o
From the central system to the decentralized system, recipient determination takes place using the
warehouse number filter.
o
From the decentralized system to the central system, you can use the logical system filter for
recipient determination if both systems have a release status of SAP R/3 Enterprise.
You then generate the partner profile for the new methods, and distribute the distribution model to the
connected decentralized WMS.
Within the decentralized WMS, a blocking concept must be introduced to ensure that you cannot process
the delivery simultaneously in both systems. To implement this, choose in Customizing Logistics ->
Logistics Execution -> Decentralized WMS Integration -> Central Processing -> Distribution Model ->
Activate Cross-System Lock.
See also
For more information on the cross-system lock, see the SAP Library under Basis -> Client-Server
Technology -> Cross-System Lock (CSL).
______________________________________________________________
SAP AG
355
SAP System
______________________________________________________________
14.3 LE-WM
Warehouse Management
14.3.1 Business Add-Ins for Logistics Execution (new)
Use
As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics
Execution in the following areas:
o
Warehouse Management
o
Shipping
o
Transportation
o
Mobile Data Entry
Effects on Customizing
To activate the Business Add-In, you have to create an active implementation.
To do so, go to the Customizing for Logistics Execution, and choose
o
o
o
Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management
->
-
Business Add-In for Determining Quant
-
Business Add-In for Determining Storage Type
-
Business Add-In for Determining Storage Unit Type
-
Business Add-In for Entering Inventory Data in Inventory Management
Shipping -> System Modifications -> Business Add-Ins in Shipping
-
Business Add-In for Delivery Processing
-
Business Add-In for Price Determination in the Delivery
-
Business Add-In for Subsequent Outbound Delivery Split
-
Business Add-In for Posting Goods Movements
-
Business Add-In for Additional Header Detail Screen in Delivery Transaction
-
Business Add-In for Additional Item Detail Screen in Transaction
-
Business Add-In for Additional Overview Screen in Delivery Transaction
Transportation --> System Modifications --> Business Add-Ins in Transportation
-
Business Add-In for Checks when Creating a Shipment Cost Document
-
Business Add-In for Creating a Shipment Cost Document
-
Business Add-In for Shipment Cost Account Assignment
-
Business Add-In for Checks During Shipment Cost Processing
______________________________________________________________
SAP AG
356
SAP System
______________________________________________________________
o
-
Business Add-In for Transferring Shipment Cost Items
-
Business Add-In for Saving Shipment Cost Documents
Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry
-
Business Add-In for Queue Determination
14.3.2 Structure changes in the Logistics Execution IMG
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the R/2-R/3 link in the area of Logistics
Execution no longer exists, because the system no longer supports migration from R/2 to SAP R/3
Enterprise. The following activities have been removed from Logistics Information in the implementation
guide (IMG):
Deleted nodes under Warehouse Management:
o
Define Decentralized Link to R/2
Deleted nodes under Shipping:
o
R/2-R/3 Link
o
Define Indicator for Communication
o
Define Mail Control
o
Define Conversion of Customer Numbers R/2-R/3
o
Define Number Ranges for Decentralized Deliveries
o
Check Delivery Types and Item Categories
o
Define Output for Communication
o
Define Transfer of Texts
o
Define Batch Check by Delivery Item
SAP recommend migrating from R/2 to R/3 release 4.6C.
14.3.3 Delayed update of outbound delivery (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can delay updating the source outbound
delivery following confirmation of transfer orders (TOs).
By using this function, you avoid lock problems when you confirm transfer orders for outbound
deliveries and update the outbound delivery data correspondingly. This function also improves system
______________________________________________________________
SAP AG
357
SAP System
______________________________________________________________
performance because the system does not process and lock the entire outbound delivery every time you
confirm a transfer order item.
You can update the outbound delivery at the following times:
o
The system transfers the confirmation data to the source outbound delivery immediately every time
you confirm a transfer order item. In this case, the delayed update of the outbound delivery is not
active.
o
The system transfers the confirmation data to the outbound delivery as soon as all of the items of a
transfer order have been confirmed.
o
The system transfers the confirmation data to the outbound delivery as soon as all of the transfer
orders that were created for one outbound delivery have been confirmed.
This type of update is not designed for TOs for multiple deliveries. For TOs for multiple deliveries,
make sure that the system transfers the confirmation data to the outbound delivery as soon as all of
the items of the TO have been confirmed.
Effects on Customizing
You activate the delayed update of the outbound delivery in the Customizing for Warehouse Management
under Interfaces -> Shipping -> Define Shipping Control -> Shipping Control per Warehouse Number
with the indicator Late Delivery Update.
A Business Add-In for Influencing the Late Update of Deliveries is also available in the Customizing for
Warehouse Management under System Modifications -> Business Add-Ins in Warehouse
Management. You can use this to specify exactly when you want to update an outbound delivery at a later
time.
14.3.4 LE-WM-TFM
Stock Movements
14.3.4.1 Business Add-Ins for Logistics Execution (new)
Use
As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics
Execution in the following areas:
o
Warehouse Management
o
Shipping
o
Transportation
o
Mobile Data Entry
Effects on Customizing
To activate the Business Add-In, you have to create an active implementation.
To do so, go to the Customizing for Logistics Execution, and choose
o
Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management
->
______________________________________________________________
SAP AG
358
SAP System
______________________________________________________________
o
o
o
-
Business Add-In for Determining Quant
-
Business Add-In for Determining Storage Type
-
Business Add-In for Determining Storage Unit Type
-
Business Add-In for Entering Inventory Data in Inventory Management
Shipping -> System Modifications -> Business Add-Ins in Shipping
-
Business Add-In for Delivery Processing
-
Business Add-In for Price Determination in the Delivery
-
Business Add-In for Subsequent Outbound Delivery Split
-
Business Add-In for Posting Goods Movements
-
Business Add-In for Additional Header Detail Screen in Delivery Transaction
-
Business Add-In for Additional Item Detail Screen in Transaction
-
Business Add-In for Additional Overview Screen in Delivery Transaction
Transportation --> System Modifications --> Business Add-Ins in Transportation
-
Business Add-In for Checks when Creating a Shipment Cost Document
-
Business Add-In for Creating a Shipment Cost Document
-
Business Add-In for Shipment Cost Account Assignment
-
Business Add-In for Checks During Shipment Cost Processing
-
Business Add-In for Transferring Shipment Cost Items
-
Business Add-In for Saving Shipment Cost Documents
Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry
-
Business Add-In for Queue Determination
14.3.4.2 Transfer order for multiple outbound deliveries (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can create a transfer order (TO) for multiple
outbound deliveries.
You use transfer orders for multiple deliveries in particular if you want to process a number of outbound
deliveries of the same material each with only one, or only a few outbound delivery items. The individual
items in the transfer order are based on different outbound deliveries.
You can also use a transfer order for multiple deliveries to optimize routes in the warehouse by grouping
together material items from different outbound deliveries, which are stored close together.
You create a TO for multiple deliveries
______________________________________________________________
SAP AG
359
SAP System
______________________________________________________________
o
With function module L_TO_CREATE_DN_MULTIPLE
Using this function module, you select the outbound deliveries and then create a cross-delivery TO
directly for the selected outbound deliveries.
o
For a group of outbound deliveries via the transaction Create Transfer Order for Multiple Orders
(LT0S). To do this, choose Logistics -> Logistics Execution -> Outbound Process -> Goods Issue
for Outbound Delivery -> Picking -> Create Transfer Order -> For multiple deliveries.
After you have created a transfer order for multiple deliveries, you can split it into smaller transfer orders
according to certain criteria (for example, volume, weight, or TO items), so that these smaller transfer
orders can be processed by several pickers. To do this, use user exit MWMTO012.
The system supports the same functions for transfer orders for multiple deliveries as for regular transfer
orders.
14.3.4.3 Delayed update of outbound delivery (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can delay updating the source outbound
delivery following confirmation of transfer orders (TOs).
By using this function, you avoid lock problems when you confirm transfer orders for outbound
deliveries and update the outbound delivery data correspondingly. This function also improves system
performance because the system does not process and lock the entire outbound delivery every time you
confirm a transfer order item.
You can update the outbound delivery at the following times:
o
The system transfers the confirmation data to the source outbound delivery immediately every time
you confirm a transfer order item. In this case, the delayed update of the outbound delivery is not
active.
o
The system transfers the confirmation data to the outbound delivery as soon as all of the items of a
transfer order have been confirmed.
o
The system transfers the confirmation data to the outbound delivery as soon as all of the transfer
orders that were created for one outbound delivery have been confirmed.
This type of update is not designed for TOs for multiple deliveries. For TOs for multiple deliveries,
make sure that the system transfers the confirmation data to the outbound delivery as soon as all of
the items of the TO have been confirmed.
Effects on Customizing
You activate the delayed update of the outbound delivery in the Customizing for Warehouse Management
under Interfaces -> Shipping -> Define Shipping Control -> Shipping Control per Warehouse Number
with the indicator Late Delivery Update.
A Business Add-In for Influencing the Late Update of Deliveries is also available in the Customizing for
Warehouse Management under System Modifications -> Business Add-Ins in Warehouse
Management. You can use this to specify exactly when you want to update an outbound delivery at a later
time.
______________________________________________________________
SAP AG
360
SAP System
______________________________________________________________
14.3.5 LE-WM-BIN
Inventory at the Storage Bin Level
14.3.5.1 Business Add-Ins for Logistics Execution (new)
Use
As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics
Execution in the following areas:
o
Warehouse Management
o
Shipping
o
Transportation
o
Mobile Data Entry
Effects on Customizing
To activate the Business Add-In, you have to create an active implementation.
To do so, go to the Customizing for Logistics Execution, and choose
o
o
o
Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management
->
-
Business Add-In for Determining Quant
-
Business Add-In for Determining Storage Type
-
Business Add-In for Determining Storage Unit Type
-
Business Add-In for Entering Inventory Data in Inventory Management
Shipping -> System Modifications -> Business Add-Ins in Shipping
-
Business Add-In for Delivery Processing
-
Business Add-In for Price Determination in the Delivery
-
Business Add-In for Subsequent Outbound Delivery Split
-
Business Add-In for Posting Goods Movements
-
Business Add-In for Additional Header Detail Screen in Delivery Transaction
-
Business Add-In for Additional Item Detail Screen in Transaction
-
Business Add-In for Additional Overview Screen in Delivery Transaction
Transportation --> System Modifications --> Business Add-Ins in Transportation
-
Business Add-In for Checks when Creating a Shipment Cost Document
-
Business Add-In for Creating a Shipment Cost Document
-
Business Add-In for Shipment Cost Account Assignment
-
Business Add-In for Checks During Shipment Cost Processing
______________________________________________________________
SAP AG
361
SAP System
______________________________________________________________
o
-
Business Add-In for Transferring Shipment Cost Items
-
Business Add-In for Saving Shipment Cost Documents
Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry
-
Business Add-In for Queue Determination
14.3.6 LE-WM-STU
Storage Unit Management
14.3.6.1 Stock overview for SU-managed bulk storage (changed)
Use
To calculate the current stock overview in storage unit managed (SU-managed) bulk storage, the system
reads all of the open transfer orders (TOs) for the corresponding bulk storage type. On the basis of these
TOs, the system balances out the stock level in the source storage type and the destination storage type at
totals level. As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system calculates the current
stock situation based on dummy quants, which are derived from the open transfer orders for the storage
type.
These dummy quants only exist for the purpose of correctly calculating the stock level in the particular
storage type. The system does not save dummy quants in the database; they are only available for a short
time for internal system calculations.
For an overview of the material stocks, choose Logistics -> Logistics Execution -> Internal Warehouse
Processes -> Bins and Stock -> Display -> Bin Stock per Material or Total Stock per Material
(Warehouse Management)
In the detail overview per storage type, the quantity available per quant is not shown in the standard
system because the system cannot assign a particular quant for removal from storage to the stock removal
TO in advance in SU-managed bulk storage. However, you can display the stock overview per quant
based on a list variant. Make sure that in the system
o
The available quantity per dummy quant corresponds to a negative quant
o
The available quantity per quant corresponds to the current total quantity of this quant, in
SU-managed bulk storage.
If you display the quant data from the stock overview, make sure
o
That the system does not display dummy quants as these do not exist in the database
o
That the system displays the quantity to be removed in the destination quantity for SU-managed
bulk storage.
______________________________________________________________
SAP AG
362
SAP System
______________________________________________________________
14.3.7 LE-WM-IFC
Interfaces
14.3.7.1 Links between IDoc and business object (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the system stores the link between the IDoc and
corresponding business object on receipt of the IDoc.
This makes it possible to display the corresponding business object from the IDoc with detailed data. You
can also display the IDoc from the business object.
The following message types are linked with the following business objects:
Message Type
WMCATO
WMTOCO
WMTORD
WMINVE
WMPIHU
WMSUMO
WMTREQ
Business Object
Transfer order
Transfer order
Transfer order
Physical inventory document
Transfer order
Transfer order
Transfer requirement
Effects on Data Transfer
The links are only created for new IDocs. No links are made for IDocs that existed before the release
upgrade, nor can these be linked in retrospect.
14.3.7.2 Task and Resource Management (LE-TRM)
Use
You can use Task and Resource Management (TRM) to control and optimize the processes in the
warehouse. TRM provides the following features that supports this optimization:
Task-Resource Optimization
TRM optimizes warehouse processes by determining optimal routes and creating and prioritizing tasks to
be executed by warehouse resources.
Execution Control
TRM enables you to control the execution of tasks in predefined areas of your site, facilitating
task-resource optimization by preventing the crowding of resources.
Monitoring and Response Tools - TRM Monitor
TRM enables you to monitor all aspects of warehouse operations and invoke methods to respond to
______________________________________________________________
SAP AG
363
SAP System
______________________________________________________________
constantly changing circumstances in the warehouse.
Alerts and Exception Handling Tools - TRM Alert Monitor
TRM provides information on actual and arising problematic situations in the warehouse, and enables
you to handle exceptions.
Mobile Presentation
TRM allows you to customize the presentation of data to a resource on a variety of presentation devices.
LES and TRM work together to manage and maintain warehouse operations. However, each system
maintains a separation and has clearly defined responsibilities. LES provides the details about what
activity should be performed for which object, while TRM determines how and when the request is
executed.
Effects on Customizing
To integrate TRM with WMS, you must assign WM warehouses to TRM sites and control the WM-TRM
link for transfer orders. For more information, see the following Implementation Guide (IMG) activities:
o
Logistics Execution -> Warehouse Management -> Interfaces -> Task and Resource Management
-> Assign Site.
o
Logistics Execution -> Warehouse Management -> Interfaces -> Task and Resource Management
-> Control WMS-TRM Interface for Transfer Orders.
There are also mandatory and optional settings in the IMG for Logistics Execution -> Task and Resource
Management, where you do the following:
o
Make general TRM settings, including defining the TRM sites, activities and exception reason codes
o
Define number ranges for requests, tasks, resources and warehouse supervisor messages
o
Make Resource Management settings, including defining resource types and resource element types
o
Maintain task critical time windows, mechanisms that facilitate the synchronization of tasks
o
Make Site Map Management settings, including defining TRM objects such as zones and working
areas , as well as enhancing WM objects such as storage bins, storage types and staging areas
o
Make settings that affect the way in which data is presented on resource presentation devices, such
as defining menus and pushbuttons
o
Make route-related settings
o
Create execution control for your sites
o
Make settings related to the TRM Monitor and Alert Monitor
o
Create user exits if desired
See also
For more information on TRM, see the SAP Library for Task & Resource Management.
______________________________________________________________
SAP AG
364
SAP System
______________________________________________________________
14.3.8 LE-WM-GF
Other Functions
14.3.8.1 Delayed update of outbound delivery (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you can delay updating the source outbound
delivery following confirmation of transfer orders (TOs).
By using this function, you avoid lock problems when you confirm transfer orders for outbound
deliveries and update the outbound delivery data correspondingly. This function also improves system
performance because the system does not process and lock the entire outbound delivery every time you
confirm a transfer order item.
You can update the outbound delivery at the following times:
o
The system transfers the confirmation data to the source outbound delivery immediately every time
you confirm a transfer order item. In this case, the delayed update of the outbound delivery is not
active.
o
The system transfers the confirmation data to the outbound delivery as soon as all of the items of a
transfer order have been confirmed.
o
The system transfers the confirmation data to the outbound delivery as soon as all of the transfer
orders that were created for one outbound delivery have been confirmed.
This type of update is not designed for TOs for multiple deliveries. For TOs for multiple deliveries,
make sure that the system transfers the confirmation data to the outbound delivery as soon as all of
the items of the TO have been confirmed.
Effects on Customizing
You activate the delayed update of the outbound delivery in the Customizing for Warehouse Management
under Interfaces -> Shipping -> Define Shipping Control -> Shipping Control per Warehouse Number
with the indicator Late Delivery Update.
A Business Add-In for Influencing the Late Update of Deliveries is also available in the Customizing for
Warehouse Management under System Modifications -> Business Add-Ins in Warehouse
Management. You can use this to specify exactly when you want to update an outbound delivery at a later
time.
14.4 LE-TRM
Task & Resource Management
14.4.1 Task and Resource Management (LE-TRM)
Use
You can use Task and Resource Management (TRM) to control and optimize the processes in the
warehouse. TRM provides the following features that supports this optimization:
______________________________________________________________
SAP AG
365
SAP System
______________________________________________________________
Task-Resource Optimization
TRM optimizes warehouse processes by determining optimal routes and creating and prioritizing tasks to
be executed by warehouse resources.
Execution Control
TRM enables you to control the execution of tasks in predefined areas of your site, facilitating
task-resource optimization by preventing the crowding of resources.
Monitoring and Response Tools - TRM Monitor
TRM enables you to monitor all aspects of warehouse operations and invoke methods to respond to
constantly changing circumstances in the warehouse.
Alerts and Exception Handling Tools - TRM Alert Monitor
TRM provides information on actual and arising problematic situations in the warehouse, and enables
you to handle exceptions.
Mobile Presentation
TRM allows you to customize the presentation of data to a resource on a variety of presentation devices.
LES and TRM work together to manage and maintain warehouse operations. However, each system
maintains a separation and has clearly defined responsibilities. LES provides the details about what
activity should be performed for which object, while TRM determines how and when the request is
executed.
Effects on Customizing
To integrate TRM with WMS, you must assign WM warehouses to TRM sites and control the WM-TRM
link for transfer orders. For more information, see the following Implementation Guide (IMG) activities:
o
Logistics Execution -> Warehouse Management -> Interfaces -> Task and Resource Management
-> Assign Site.
o
Logistics Execution -> Warehouse Management -> Interfaces -> Task and Resource Management
-> Control WMS-TRM Interface for Transfer Orders.
There are also mandatory and optional settings in the IMG for Logistics Execution -> Task and Resource
Management, where you do the following:
o
Make general TRM settings, including defining the TRM sites, activities and exception reason codes
o
Define number ranges for requests, tasks, resources and warehouse supervisor messages
o
Make Resource Management settings, including defining resource types and resource element types
o
Maintain task critical time windows, mechanisms that facilitate the synchronization of tasks
o
Make Site Map Management settings, including defining TRM objects such as zones and working
areas , as well as enhancing WM objects such as storage bins, storage types and staging areas
o
Make settings that affect the way in which data is presented on resource presentation devices, such
as defining menus and pushbuttons
o
Make route-related settings
______________________________________________________________
SAP AG
366
SAP System
______________________________________________________________
o
Create execution control for your sites
o
Make settings related to the TRM Monitor and Alert Monitor
o
Create user exits if desired
See also
For more information on TRM, see the SAP Library for Task & Resource Management.
14.5 LE-SHP
Shipping
14.5.1 Structure changes in the Logistics Execution IMG
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the R/2-R/3 link in the area of Logistics
Execution no longer exists, because the system no longer supports migration from R/2 to SAP R/3
Enterprise. The following activities have been removed from Logistics Information in the implementation
guide (IMG):
Deleted nodes under Warehouse Management:
o
Define Decentralized Link to R/2
Deleted nodes under Shipping:
o
R/2-R/3 Link
o
Define Indicator for Communication
o
Define Mail Control
o
Define Conversion of Customer Numbers R/2-R/3
o
Define Number Ranges for Decentralized Deliveries
o
Check Delivery Types and Item Categories
o
Define Output for Communication
o
Define Transfer of Texts
o
Define Batch Check by Delivery Item
SAP recommend migrating from R/2 to R/3 release 4.6C.
______________________________________________________________
SAP AG
367
SAP System
______________________________________________________________
14.5.2 LE-SHP-DL
Delivery Processing
14.5.2.1 Business Add-Ins for Logistics Execution (new)
Use
As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics
Execution in the following areas:
o
Warehouse Management
o
Shipping
o
Transportation
o
Mobile Data Entry
Effects on Customizing
To activate the Business Add-In, you have to create an active implementation.
To do so, go to the Customizing for Logistics Execution, and choose
o
o
o
Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management
->
-
Business Add-In for Determining Quant
-
Business Add-In for Determining Storage Type
-
Business Add-In for Determining Storage Unit Type
-
Business Add-In for Entering Inventory Data in Inventory Management
Shipping -> System Modifications -> Business Add-Ins in Shipping
-
Business Add-In for Delivery Processing
-
Business Add-In for Price Determination in the Delivery
-
Business Add-In for Subsequent Outbound Delivery Split
-
Business Add-In for Posting Goods Movements
-
Business Add-In for Additional Header Detail Screen in Delivery Transaction
-
Business Add-In for Additional Item Detail Screen in Transaction
-
Business Add-In for Additional Overview Screen in Delivery Transaction
Transportation --> System Modifications --> Business Add-Ins in Transportation
-
Business Add-In for Checks when Creating a Shipment Cost Document
-
Business Add-In for Creating a Shipment Cost Document
-
Business Add-In for Shipment Cost Account Assignment
-
Business Add-In for Checks During Shipment Cost Processing
-
Business Add-In for Transferring Shipment Cost Items
______________________________________________________________
SAP AG
368
SAP System
______________________________________________________________
o
Business Add-In for Saving Shipment Cost Documents
Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry
-
Business Add-In for Queue Determination
14.5.2.2 Conversion of Matchcode Objects in Delivery Processing
Use
For delivery documents, both document data and special database tables are updated, that allow for
effective access to deliveries in various stages of processing. Until now, the function of matchcode
objects has been used for these tables. As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) , this
function is no longer available.
The previous tables for the matchcode pools for deliveries will be replaced by new transparent tables and
views. The transparent tables are automatically updated during normal delivery processing.
The following relationship exists between matchcode tables and the new tables or views:
Matchcode Tab. New Object
Type
Outbound Deliveries
M_VMVLASHP_IDX_GDSI
Table
M_VMVLB SHP_IDX_PICK
Table
M_VMVLC SHP_IDX_GDSI
Table
M_VMVLDSHP_IDX_CRED
Table
M_VMVLI SHP_VIEW_EXTI
View
identification
Inbound Deliveries
M_VMVMA
(removed)
M_VMVMB
SHP_VIEW_TRAI View
identification
M_VMVMC
SHP_VIEW_BOLN View
M_VMVMD
SHP_VIEW_EXVE View
M_VMVME
SHP_IDX_GDRC Table
M_VMVMF
SHP_IDX_PUTA Table
Rough Goods Receipts
M_VMVG SHP_IDX_ROGR
Table
Contents
Outbound deliveries: Not posted for GI
Outbound deliveries: Not picked
Outbound deliveries: Not posted for GI
Outbound deliveries: After credit checks
Outbound deliveries: External
Inbound deliveries: Initiating document
Inbound deliveries: Shipment
Inbound deliveries: Tracking number
Inbound deliveries: External identification
Inbound deliveries: Not posted for GR
Inbound deliveries: Not putaway
Rough goods receipts for vendor
Effects on Existing Data
The entries in the previous matchcode tables will be automatically copied into the new tables (index
tables) when you upgrade to SAP R/3 Enterprise Core 4.70 (SAP_APPL 470). If, in your subsequent
productive system, you need to correct the entries in the index tables, you must use the
RLE_SHP_IDX_TABLE_MAINTAIN reoprt.
______________________________________________________________
SAP AG
369
SAP System
______________________________________________________________
The matchcode objects VMVL (outbound deliveries), VMVM (inbound deliveries), and VMVG (rough
goods receipts) are deleted after the data transfer during the upgrade, along with the corresponding
objects (matchcode IDs, matchcode tables). You should therefore check your programs to see if any of
these objects are used, and should replace these according to the above procedure. Because the new tables
and views contain at least the same fields as the previous tables, for programs, you normally only need to
adjust the SELECT links to matchcode tables and the data definition of the target table or target structure
for these links.
Any modifications to the matchcode objects are lost during the upgrade.
Effects on System Administration
You can use the RLE_SHP_IDX_TABLE_MAINTAIN report to analyze the data status in the index
tables, and to correct it where necessary.
See also
Release Note for matchcode conversion.
14.5.2.3 Partial Goods Receipt for Inbound Delivery (New)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), you have the option of posting partial goods
receipts for inbound deliveries. For goods movement-relevant inbound deliveries, you can make goods
receipt postings using the confirmation of putaway from one or more transfer orders.
You can perform a partial goods receipt posting for an inbound delivery using the following procedures:
1.
Creating and confirming several transfer orders
2.
Step-by-step confirmation of a transfer order, in other words, you only post a part of the items or
quantities.
You can display the individual partial goods receipts in the document flow of the inbound delivery using
the relevant number of the existing material documents.
In addition, you can cancel partial goods receipts that have already been posted, at material document
level. You can cancel single material documents or all material documents. You cannot cancel partial
quantities within the material document items. Instead you can only cancel the complete document
created and then return transfer the quantities again.
14.5.3 LE-SHP-GI
Goods Issue
14.5.3.1 Business Add-Ins for Logistics Execution (new)
Use
As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics
______________________________________________________________
SAP AG
370
SAP System
______________________________________________________________
14.6 LE-TRA
Transportation
14.6.1 LE-TRA-FC
Freight Processing
14.6.1.1 Business Add-Ins for Logistics Execution (new)
Use
As of SAP R/3 Enterprise 4.70 (SAP_APPL 470) Business Add-Ins (BAdIs) are available in Logistics
Execution in the following areas:
o
Warehouse Management
o
Shipping
o
Transportation
o
Mobile Data Entry
Effects on Customizing
To activate the Business Add-In, you have to create an active implementation.
To do so, go to the Customizing for Logistics Execution, and choose
o
o
o
Warehouse Management -> System Modifications -> Business Add-Ins in Warehouse Management
->
-
Business Add-In for Determining Quant
-
Business Add-In for Determining Storage Type
-
Business Add-In for Determining Storage Unit Type
-
Business Add-In for Entering Inventory Data in Inventory Management
Shipping -> System Modifications -> Business Add-Ins in Shipping
-
Business Add-In for Delivery Processing
-
Business Add-In for Price Determination in the Delivery
-
Business Add-In for Subsequent Outbound Delivery Split
-
Business Add-In for Posting Goods Movements
-
Business Add-In for Additional Header Detail Screen in Delivery Transaction
-
Business Add-In for Additional Item Detail Screen in Transaction
-
Business Add-In for Additional Overview Screen in Delivery Transaction
Transportation --> System Modifications --> Business Add-Ins in Transportation
-
Business Add-In for Checks when Creating a Shipment Cost Document
-
Business Add-In for Creating a Shipment Cost Document
-
Business Add-In for Shipment Cost Account Assignment
______________________________________________________________
SAP AG
372
SAP System
______________________________________________________________
o
-
Business Add-In for Checks During Shipment Cost Processing
-
Business Add-In for Transferring Shipment Cost Items
-
Business Add-In for Saving Shipment Cost Documents
Mobile Data Entry -> System Modifications -> Business Add-Ins in Mobile Data Entry
-
Business Add-In for Queue Determination
14.6.1.2 Direct Navigation from the Shipment Cost Document to the Reference
Document.
Use
When you create, change, and display a shipment cost document (transactions VI01, VI02, VI03), you
can access the reference document directly by double-clicking on it.
______________________________________________________________
SAP AG
373
SAP System
______________________________________________________________
15 PLM
Product Lifecycle Management
15.1 Accessibility
Use
We are making SAP software accessible to users with disabilities. For more information on accessibility,
see the SAP Library, Getting Started: Accessibility Supplement. For information on the accessibility
of individual functions, see the release notes for the individual components. To enable you to find these
release notes more easily, their titles begin with Accessibility.
See also
Accessiblity in the SAP System
15.2 PLM-PPM
Product and Process Modeling
15.2.1 PLM-PPM-PDN
Product Designer
15.2.1.1 Product Designer
Use
As of SAP R/3 Enterprise PLM Extension 1.10 (EA_APPL 110), you can use the Product Designer
to optimize engineering processes, even in the early phase of product development.
The following functions form the essentail basis for the product designer:
o
The high-performance workbench of integrated Product and Process Engineering (iPPE) lets
you manage product data in extremely flexible structures, adding to it constantly.
-
Developers structure the diverse requirements and product information. As a result of the first
phase of a new development, you create the requirement structure..
-
On the basis of this requirement structure, the engineering process gradually develops the
product structure, with various product variants.
-
The product model becomes more and more detailed. In this process, development engineers
search for possible solutions. Concept processing is very useful during the search for solutions.
o
Document Management is a clearly structured way of managing the documents that come into
existence and integrating them in engineering processes, especially in the first phase of product
development.
o
The Web user interface particulary supports users without knowledge of SAP, or without access to
an SAP GUI (Graphical User Interface).
The integrated SAP Business Workflow (WebFlow) allows you to design transparent,
standardized business processes.
______________________________________________________________
SAP AG
374
SAP System
______________________________________________________________
o
You can extract selected data from the complex iPPE Model, then convert it to a material BOM
(application component LO-MD-BOM).
Effects on System Administration
In the SAP menu, you call the functions as follows: Logistics, Central Functions, Engineering,
Product and Process Engineering.
Effects on Customizing
To use the functions, you need to follow the Implementation Guide (IMG):
o
Integrated Product and Process Engineering
The settings for the iPPE model are supplied in their entirety in R/3 Enterprise. You can check this
data in Customizing for Integrated Product and Process Engineering.
o
Document Management
-
The settings for processing documents are defined in Customizing for Document
Management.
-
Special settings for processing on the Web user interface are defined in the following
activities: Set Up WebDocuments (BSP).
See also
For more information, see the SAP Library, Product Designer.
15.2.1.2 Accessibility: Web User Interface of the Product Designer
Effects on System Administration
To make the Web user interface of the product designer accessible, define the following setting on the
Web user interface:
1.
In the toolbox, choose Settings.
2.
In the Additional Functions box, set the Accessibility indicator.
3.
Save this setting.
See also
Accessibility in the SAP System
15.2.2 PLM-PPM-RPL
Product Data Replication
15.2.2.1 Structural Changes in PLM-LDM
Use
o
In the IMG of Logistics General, the structure Product Data Replication was placed at the same
______________________________________________________________
SAP AG
375
SAP System
______________________________________________________________
level as Configuration Management.
o
In the IMG of Cross-Application Components, CAD Desktop was arranged under CAD
Integration.
15.2.2.2 Business Add-Ins (BAdIs) in PLM PDR
Use
From SAP R/3 Enterprise PLM Extension 1.10 (EA_APPL 110) you can now use the following BAdIs in
PLM Product Data Replication:
o
BAdI: Modify UPS Data
o
BAdI: Set Up Additional Classes
15.2.2.3 Product Data Replication (Changed)
Use
From SAP R/3 Enterprise PLM Extension 1.10 (EA_APPL 110), you can, with mySAP PLM
product data replication, control and check each step that belongs to the distribution process.
Product development happens centrally, using mySAP PLM. You can register production systems, and
sales and distribution systems targeted for individual products. This ensures that the local systems are
provided with the complete product and changes to the product. Users, who can also register for products,
are informed of any product changes at the time of distribution.
The product model includes all the objects that belong to a product, such as materials, BOMs, documents,
classes, characteristics, classifications, and even the configuration model.
The distribution of product data succeeds on the basis of consistent packets. Packets incorporate the
complete product with the corresponding objects, such as classes, materials, and documents, or the
changes to the product model that have accumulated since the previous distribution to the target system.
Effects on Customizing
Before you can distribute product data, you must make the following system settings for the following
areas in the Customizing (IMG) for Product Data Replication:
o
Document distribution
o
Configuration management
o
ALE
15.2.2.4 Product Data Distribution
______________________________________________________________
SAP AG
376
SAP System
______________________________________________________________
16 QM
Quality Management
16.1 New Developments for SAP R/3 Enterprise PLM Extension 1.10
(EA_APPL
Use
This release information will provide you with an overview of the main developments in release SAP R/3
Enterprise PLM Extension 1.10 (EA-APPL 110) in the area mySAP PLM Quality Management.
Stability Study
You can find a description of this new development in the Release Information for Stability Studies.
This release information explains:
o
What a stability study is.
o
How stability studies are integrated in quality management processes.
o
The role of quality notifications in stability studies.
o
How the stability study process is structured and how it can be controlled.
o
What changes were made to the QM Customizing to include stability studies and how to use the
Customizing for stability studies.
You can find a detailed description of the stability study solution in the application help.
Flexible Inspection Specifications
You can find a description of this new development under Release Information for Flexible Inspection
Specifications.
This release information explains:
o
What flexible inspection specifications are.
o
How flexible inspection specifications are used.
o
What happens when flexible inspection specifications are implemented.
o
How to activate flexible inspection specifications.
16.2 New Business Add-Ins
Use
A series of new Business Add-Ins (BAdIs) allows you to make functional enhancements without
modification.
You can find these BAdIs in Customizing under Quality Management -> Environment -> Tools ->
Business Add-Ins.
______________________________________________________________
SAP AG
377
SAP System
______________________________________________________________
Enhancements (BAdIs) in Quality Planning:
o
There is one BAdI especially for input processing.
o
In the Engineering Workbench you can maintain additional customer-specific fields for the
inspection plan at characteristic-, operation-, and header level.
o
When you save the inspection plan in the Engineering Workbench, all of the planning data is made
available to a BAdI.
o
On the overview screen of the Engineering Workbench, you can define an additional pushbutton at
characteristic-, operation-, and header level. You can use this pushbutton to call up your own
programs.
Enhancements (BAdIs) for Quality Inspections:
o
Flexible specification selection is supported in a BAdI.
o
You can display any desired data in an inspection lot and you can change inspection lot data in the
structure QALS_ADDON, using additional subscreen areas.
o
In the transactions for the physical-sample record, you can activate an additional tab page depending
on the screen control key for the physical sample type.
o
You can display additional data on a subscreen of the header screen for results recording.
o
You can display additional data on a subscreen of the header screen for the usage decision.
o
When you save in results recording, all inspection lot data is made available to a BAdI.
o
You can program your own rules for the valuation of characteristics and original values, for
example, reject if measured value and tolerance limit are equal.
Enhancements (BAdIs) for Quality Certificates:
o
You can maintain additional customer-specific fields for the characteristics in the certificate profile.
You can make changes to the certificate characteristic data when copying characteristics into the
certificate profile.
Enhancements (BAdIs) in Logistics:
o
You can make changes to the criteria for the assignment of the quality information record in
procurement.
o
The check of the required QM system in the procurement process can be replaced with a
customer-specific program.
Enhancements (BAdIs) for Quality Notifications:
o
The notification data can be changed when saving.
o
You can change the activities of follow-up functions in the action box and the way that they are
displayed.
o
Depending on the notification type, you can implement the free reference object screen in
accordance with your requirements.
o
You can replace the node attribute of an object in the document flow graphic of the quality
notification. You can, for example, display the inspection lot short text for the object "inspection
lot" as an attribute.
______________________________________________________________
SAP AG
378
SAP System
______________________________________________________________
o
For each notification type, you can use a BAdI to control if the changing of a user status is allowed.
16.3 New Developments for SAP R/3 Enterprise Core 4.70
(SAP_APPL 470
Use
This release information will provide you with an overview of the main developments in release SAP R/3
Enterprise Core 4.70 (SAP_APPL 470) in the area mySAP PLM Quality Management.
Input Processing for Measured Values
This new development allows you to process measured values according to your own, user-defined rules.
You can find a more detailed description in the Release Information for Input Processing.
New Business Add-Ins
A series of new Business Add-Ins allows you to make functional enhancements without modification.
You can find a description of this new development under Release Information for New
Business-Add-Ins in mySAP PLM Quality Management.
New Developments in Notifications: Several Customer Subscreens for Each Notification Type
From release 4.70, it is possible to include one or more customer subscreens in the notification header
data for each notification type. The size of the customer subscreens can be freely-defined as long as the
sum of the subscreens does not exceed the total size of the tab page.
You can find a description of this new development under Release Information for Customer Subscreens
in notifications.
16.4 QM-IM
Quality Inspection
16.4.1 Flexible Inspection Specifications
Use
From SAP R/3 Enterprise PLM Extension 1.10 (EA-APPL 110), the new flexible inspection
specifications function will be available in Quality Management.
This function is generally used when performing stability studies. However, it can also be used for
inspection lots in other processes. To use it in other processes, you must either perform a
customer-specific implementation of the corresponding Business Add-In or use customer functions.
Flexible inspection specifications allow you to make changes to inspection specifications during
inspection lot creation and within results recording. This is made possible by:
______________________________________________________________
SAP AG
379
SAP System
______________________________________________________________
o
Flexible specification selection
o
Flexible specification changing
This function is especially useful in cases where inspections cannot be planned completely in advance,
for example:
o
Inspections as a service
o
Inspections of complaints
o
Inspections for stability studies
A universal plan contains a wide variety of inspection specifications and all of the inspection
characteristics. This universal plan is assigned during inspection lot creation. The flexible inspection
specifications function then allows you to select the characteristics and specifications that are actually
relevant to the particular inspection.
After specification selection (selection of material specification/task list) during inspection lot creation,
the system displays a list of all characteristic specifications that have already been read.
From this list you can choose the characteristics that are relevant for the current inspection. These
characteristics are then copied to the inspection lot. In addition, you can change the following
specifications:
o
Operation short text
o
Characteristic short text
o
All limit pairs (lower/upper tolerance limit, tolerance limit pair 1 and 2, plausibility limits)
o
Target value
o
Decimal places
o
Inspection method
o
Info. fields for characteristic
o
Sampling procedure
o
Selected set
o
Control indicator (required characteristic/optional characteristic)
If not all characteristics in the template (universal plan) were copied, or if the specifications of the
characteristics were changed, a corresponding system status ("FLEX") will be set in the inspection lot.
If errors occur when you are selecting characteristics or changing specifications, these errors will be
output in an error log.
You must determine when the flexible inspection specifications function can be used during the
implementation process.
______________________________________________________________
SAP AG
380
SAP System
______________________________________________________________
For example, in stability studies the flexible inspection specification function can only be used for
manual inspection lots with inspection lot origin 16 (inspection lot for initial test or manual inspection lot
for storage condition).
Apart from the inspection lot origin, other information from the inspection lot is also available. This
information may or may not trigger the opening of a window for the changing of specifications.
You can, for example, use the inspection setup in the material master to plan a manual sample
calculation. During inspection lot creation, the system checks whether or not the relevant indicator is set.
If manual sample determination is allowed, the flexible inspection specifications function is called,
otherwise it is not called. This process can be restricted to specific inspection lot origins.
The flexible inspection specifications function can also be used in to change inspection specifications in
results recording.
Using a customer function, you can implement the call of the screen mentioned above with inspection
specifications using a pushbutton.
All characteristics for which no results have been recorded, which have not yet been completed, and
which are not in skip status are then displayed on this screen. .
For the listed characteristics, you can change the following:
o
Characteristic short text
o
All limit pairs (lower/upper tolerance, tolerance limit pair 1 and 2, plausability limits)
o
Target value
o
Decimal places
o
Inspection method
o
Info. fields for characteristic
o
Selected set
Effects on System Administration
Activation of Flexible Inspection Specifications
The function for flexible inspection specifications is available for manual inspection lots for stability
studies in the standard. You can change the specifications at lot creation using corresponding follow-up
functions for the study.
To use this function for other inspection lot origins, you must perform the following steps:
Flexible Specifications at Inspection Lot Creation
You must create an implementation for BAdI QPAP_FLEX_PLAN similar to the one that is used in the
stability study for BAdI QPAP_FLEX_PLAN_16.
The inspection lot origin is the filter for the BAdI. This means that you can create different
implementations for the different origins.
Within the implementation, more criteria that allow or disallow flexible inspection specifications can be
______________________________________________________________
SAP AG
381
SAP System
______________________________________________________________
queried. It can, for example, be of significance that a manual sample calculation must be performed
(query of QALS-STAT31 = 'X'). This is planned in the inspection data in the material master.
You should also read the documentation for the BAdI definition.
Flexible Specifications in Results Recording
To use the flexible inspection specifications function within results recording, you must first activate two
customer functions in the customer enhancement QEEM0024. These are:
o
EXIT_SAPLQEEM_024
o
EXIT_SAPLQEEM_028
Enhancement QEEM0024 is used to implement an extra pushbutton in the header screen for results
recording.
In EXIT_SAPLQEEM_024 you must program coding for the call of the function. In
EXIT_SAPLQEEM_028 you must program the name of the pushbutton.
The function module QST05_FLEX_PLAN_RES_REC can be called directly within
EXIT_SAPLQEEM_024. Since the call of the flexible inspection specifications function is generally to
be dependent on certain parameters, such as the inspection lot origin, we recommend that you code
additional queries (for example, query of I_QALS-HERKUNFT) in the exit before calling the function
module QST05_FLEX_PLAN_RES_REC. Customer-specific requirements can be taken into
consideration.
Notes
When using the function module in stability studies, corresponding authorization checks have been
implemented (see BAdI implementation QPAP_FLEX_PLAN_16). If the flexible inspection
specifications function is to be used, you must assign the relevant authorization for object
Q_MATERIAL with the value '0' to the relevant users.
The call of this function module depends on certain status fields in the inspection lot.
This should be taken into consideration for customer-specific usages.
A documentation for flexible inspection specifications is included in the BAdI implementation for the
stability study (see implementation QPAP_FLEX_PLAN_16).
If you make changes to the specifications for a selected characteristic, the field
ET_PLMKBS_TAB-QPMK_REF will be filled accordingly (value 9) by the system and copied to the
database table QAMV for characteristic specifications.
A specific system status is set in the inspection lot ("FLEX") if the flexible inspection specifications
function was actually used, that is, not all of the characteristics in the task list were copied, or
specifications were changed.
______________________________________________________________
SAP AG
382
SAP System
______________________________________________________________
16.4.2 QM-IM-RR
Results Recording
16.4.2.1 QM-IM-RR-CHR
Characteristic Results
16.4.2.1.1 Input Processing
Use
This new development allows you to:
o
Round entered measured values according to your own rules.
o
Convert entered measured values using your own formulas.
o
Document the original value.
You can, for example, output the entered value (original value) independently of the planned number of
decimal places. If two decimal places have been planned, but your measured value has only one decimal
place, then only one decimal place will be output (output = input).
You can also make the number of decimal places dependent on the actual measured size of the measured
value (significant digits).
The input is processed using a BAdI method.
To use input processing for measured values, you must first do the following:
o
Define the key for input processing, with the attribute of the BAdI parameters, in Customizing. You
can find the relevant Customizing table under Quality Management -> Quality Inspection ->
Results Recording -> Define Parameters for Input Processing.
o
Set the control indicator for input processing in the (master) inspection characteristic.
o
Enter the input processing key in the quantitative data of the (master) inspection characteristic.
o
Choose "98" as the value for the number of decimal places in the certificate profile for the (master)
inspection characteristic.
16.5 QM-QN
Quality Notifications
16.5.1 QM-QN-NT
Creating Quality Notifications
16.5.1.1 New Developments in Notifications: Several Customer Subscreens
Possibl
Use
Several Customer Subscreens:
______________________________________________________________
SAP AG
383
SAP System
______________________________________________________________
Up until release 4.6C, for each notification type a maximum of one customer subscreen could be included
in the notification header data. An area of 4 lines was reserved for this subscreen. From release 4.70, for
each notification type it is possible to include one or more customer subscreens in the notification header
data. The size of the customer subscreens can be freely defined as long as they do not exceed the total
size of the tab pages.
Enhancements in User Exits:
In the customer enhancement QQMA0001, the interface of the function modules
EXIT_SAPMIWO0_008 and EXIT_SAPMIWO0_008 was enhanced. Three new import parameters
allow you to execute your own PBO and PAI program parts, depending on the output location (tab page,
subscreen area, screen).
Effects on Customizing
From release 4.70, a second screen area "customer subscreen (>1 Screen/NType)" (091) will be available
for the inclusion of customer subscreens in the notification header. Previously, only the subscreen area
"customer subscreen (one Screen/NType)" (090) was available for this purpose.
When using screen area 090 you assigned the screen to be included under "notification header: screen
areas'. When you use the new screen area 091, a field for the direct assignment of the screen is available
in Customizing for the simplified and extended views.
In Customizing for the simplified and extended views, there is a new field called "tab page allocation".
You can use this field to freely choose the number of subscreens (beween one and five) that you want to
appear on each of the following tab pages: 10\TAB01, 10\TAB02, 10\TAB03, 10\TAB19, 10\TAB20 and
10\TAB21. The fewer subscreens you assign to one tab page, the more space there is available for each
subscreen on that tab page.
The predefined number of five possible screen areas for each notification tab page is still the default
value, so no further activities are required when upgrading. Note that you can only use one of the screen
areas (090 or 091) for each notification type.
16.6 QM-ST
Stability Studies
16.6.1 Stability Study
Use
From SAP R/3 Enterprise PLM Extension 1.10 (EA-APPL 110) the new stability study function will be
available in Quality Management.
Stability studies are performed to examine the effects of different conditions, for example, temperature,
humidity, brightness and so on, on a product and on the properties of this product over a predefined
period of time.
To perform a stability study, you must form physical samples of the product and store these physicals
samples under controlled conditions (storage conditions). Then parts of these physical samples must be
removed at planned or unplanned times during the stability study and tested according to predefined or
flexible inspection specifications.
______________________________________________________________
SAP AG
384
SAP System
______________________________________________________________
The stability study is integrated in the quality management processes (quality notification, sample
management, inspection planning, and inspection processing), and also uses plant maintenance functions,
for example, maintenance planning and scheduling.
Since some existing SAP objects have been used in the development of this new solution, some new
terms have been created (see glossary):
Stability study: Quality notification with particular notification type
Testing schedule: Maintenance plan with particular maintenance plan type
Strategy: Maintenance strategy
The stability study has its own node in Customizing under Quality Management.
The delivery of several Customizing settings for the stability study allows you to use the functions
immediately.
You can adapt the process to suit any additional requirements you may have by changing or enhancing
the default settings.
Quality Notifications as Basis for Stability Studies
Stability studies are based on quality notifications with specific notification types (see information for
Customizing). Each stability study is stored in the system as a quality notification. All objects that are
created in the course of the stability study are assigned to this notification. Examples of such objects are:
o
Initial sample
o
Stability bill of material
o
Any documents
o
Inspection lot for initial test
o
Physical samples for the storage conditions
o
Testing schedule for storage conditions with the associated inspection plans
o
Inspection lots for the stability tests
You can also assign any objects that are defined as "business objects" in the SAP system to stability
studies. The assignments of all objects to the stability study and the relationships between these objects
can be displayed in a graphic using the document flow of the notification.
Various other quality notification functions are available for stability studies, for example, connection to
the SAP Business Workflow, structuring and printing of additional shop papers, free configuration of the
user interface, or freely-definable partner determination procedures.
Controlling the Process Using the Action Box and Follow-Up Functions
The stability study process is controlled using the action box in the notification. The delivered follow-up
functions for this action box serve as proposals. You are free to make any required changes. Changes to
the follow-up functions can be made without modification.
When a follow-up function is executed, a corresponding user status is set in the stability study that
reflects the current processing status. You can change or extend the status profile as required. User
statuses can be used to create worklists for processing and evaluating stability studies. In addition, the
user status is used to control which follow-up functions can currently be executed, and which ones are
currently unavailable.
______________________________________________________________
SAP AG
385
SAP System
______________________________________________________________
Process Phases of a Stability Study
Once the study has been opened, the process is divided into the following phases:
o
Phase 1 - Initial test
o
Phase 2 - Stability planning
o
Phase 3 - Stability tests
The default settings delivered by SAP allow for the following steps in the individual phases:
Initial test
-
Assign stability bill of material
-
Create physical sample record for initial sample
-
Confirm or release initial sample
-
Create inspection lot for initial test
-
Test initial sample
-
Make a decision as to whether the stability study will be continued or not
Stability planning
-
Specify storage conditions
-
Perform inspection planning for each storage condition
-
Perform test scheduling for each storage condition
-
Calculate storage quantities; label samples; place samples in storage
-
Determine start date
Stability tests
-
Call current worklists for the stability tests to be executed
-
Simulate future worklists using a graphical scheduling overview
-
Automatically create inspection lots for each date and storage condition
-
Execute and complete stability tests
-
Complete or cancel stability studies (or deactivate/activate)
-
Remove stability samples from storage, form reserve samples
Note
New User Parameter Q_EWB_CALL
You must perform inspection planning for the storage conditions in stability studies using the
Engineering Workbench (EWB). You can use the EWB to assign a strategy and maintenance packages to
an inspection plan for a storage condition.
A new user parameter Q_EWB_CALL, was introduced to call the EWB. This new parameter has the
following effects:
If the value 'X' is set in this parameter in your user settings, the EWB will automatically be called when
______________________________________________________________
SAP AG
386
SAP System
______________________________________________________________
you display the plan from the testing schedule, inspection lot, results recording, or usage decision. In an
inspection plan, you can then also display the packages assigned for a storage condition in an operation.
If this parameter is not set, transaction QP03 will be called for the display of an inspection plan, or the
corresponding transaction will be called for routings or reference operation sets. This is the same scenario
as in previous releases.
Note that you can switch between display and change transactions in the EWB, as long as you have the
appropriate authorizations.
The user parameter mentioned above is not just used in stability studies. It can be used switch to the EWB
from other transactions to display the plan.
Maintenance of Report Variants
Report variants used in stability studies cannot be maintained in Customizing. You maintain these
variants directly in the relevant report or transaction.
Effects on Customizing
The stability study functions can be used immediately with the delivered Customizing settings. You do
not need to perform any additional Customizing activities to be able to perform a stability study in the
system.
The follow-up functions delivered by SAP for the notification can be used as delivered, but are a
proposal. The process controlled by the follow-up functions can be changed or supplemented using
customer-specific modules and follow-up actions.
The status profile can also be adapted to suit your requirements using user statuses.
We recommend that you test the process with the delivered default settings in a test system before
making any changes.
The Customizing functions for the stability study are included in a separate node under "Quality
Management" in the IMG.
______________________________________________________________
SAP AG
387
SAP System
______________________________________________________________
17 PM
Plant Maintenance
17.1 Structure changes in Plant Maintenance and Customer Service
(changed)
Use
From SAP R/3 Enterprise PLM Extension 1.10 (EA-APPL 110) there are the following changes in
the Implementation Guide (IMG) of Plant Maintenance and Customer Service:
Under Master Data in Plant Maintenance and Customer Service -> Technical Objects -> Settings
for Fleet Management, the following IMG activities were amended:
o
Set List Processing for Fleet Management Objects
o
Set Reference Object Screen for Vehicles
o
Consumption-Relevant Counter Reading Update
-
Define Tolerance Check for Usage Control
-
Create Gas Station
-
Assign Auxiliary Materials and Consumables
-
Define Key and Cost Object for Updating Material Documents
Under Plant Maintenance and Service Processing -> Maintenance- and Service Orders the node
Interface for Procurement Using External Catalogs (OCI) was amended with the following IMG
activities:
o
Define Catalogs
o
Assign Catalog of Order Type
o
Convert HTML to SAP Fields
o
Convert HTML Field Values
o
Configure Conversion Functions
The new Business Add-Ins (BAdIs) were inserted under System Enhancements and Data Transfer
The structure of Work Clearance Management was revised.
17.2 Structure changes in Plant Maintenance and Customer Service
(changed)
Use
______________________________________________________________
SAP AG
388
SAP System
______________________________________________________________
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the implementation guide (IMG) of Plant
Maintenance and Customer Service contains the following changes:
Under Master Data in Plant Maintenance and Customer Service -> Basic Settings -> Measuring
Points, Counters, and Measurement Documents , the following IMG activities have been included:
o
Make System Settings for Measuring Points and Measurement Documents
o
Define Field Selection for Measuring Points and MeasurementDocuments
Under Task Lists -> Control Data the IMG activity Define Field Selection was inserted.
Under Information systems for Plant Maintenance and Customer Service, the IMG activity
Configure Measurement Document Update was added.
Under System Enhancements and Data Transfer ->Business Add-Ins the new Business Add-Ins
were added.
17.3 Connection of partner to central address management (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) all partner screens in the area of Plant
Maintenance and Customer Service will be connected to the central address management. This gives you
the option of entering several communication methods (for example, telephone numbers) for an address
on the partner screen.
See also
For futher information see SAP note 390890.
17.4 Business Package for Assets (new)
Use
The integration with the solution mySAP Enterprise Portals has created the technical prerequisites for
working comfortably with enterprise portals.
The Business Package for Assets offers you an e-business solution that allows you to manage your asset
lifecycle in a quality-oriented logistics chain. Current information on each phase in the lifecycle of an
asset is in demand here and can be accessed at any time using the portal.
You can find further information using our product management:
mySAP Product Lifecycle Management - Asset Life-Cycle Management.
See also
______________________________________________________________
SAP AG
389
SAP System
______________________________________________________________
17.5 Project-oriented maintenance (new)
Use
Project-oriented maintenance is implemented for planning shutdowns. We offer you an interface to
Primavera P3, with which you can plan major maintenance projects, such as shutdowns, revisions,
inspections or overhauls, with a minimum outlay of time and money.
For further information contact our product management: mySAP Product Lifecycle Management Asset Life-Cycle Management.
See also
17.6 Mobile scenarios for Plant Maintenance and Customer Service
(new)
Use
Various mobile scenarios are available for Plant Maintenance and Customer Service.
You can get further information from our product management:
mySAP Product Lifecycle Management - Asset Life-Cycle Management.
See also
17.7 PM-EQM
Technical Objects
17.7.1 Displaying lower-level objects as symbols (changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the lower-level objects are displayed in the
structural display as symbols with quick info texts. You can see the symbols in the following functions:
o
Display structural display for equipment
o
Display structural display for functional locations
o
Display structural display for material
See also
______________________________________________________________
SAP AG
390
SAP System
______________________________________________________________
17.7.2 BAPIs for technical objects (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the following Business Application
Programming Interfaces (BAPI)/methods are available:
Equipment:
PieceOfEquipment.GetStatus
This module is for reading the (system- and user-) status of an existing piece of equipment.
Functional locations:
FunctionalLocation.GetStatus
This module is for reading the (system- and user-) status of an existing functional location.
17.7.3 Display of indirectly assigned BOMs (changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the display of indirectly assigned BOMs for
displaying structural displays for technical objects was changed as follows:
o
As soon as the field construction type in the master record for the technical object is filled, the
construction type is also displayed in the structural display.
o
If the construction type is assigned to a material BOM and the field for the BOM explosion is
selected, then this is also displayed under the construction type in the structural display.
See also
17.7.4 Material search using classes (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), in the structural displays for technical objects
you can use classes/> to display materials that appear in the structure and in the substructure.
The system reads all the classes for the classified and visible material and displays these in a dialog box.
You must select a class and the system lists all the materials that are assigned to the class. zugeordnet
sind, auf. The system also displays the characteristic value assignment.
If you perform the structural display during order processing, you can select the material found and copy
it into the order.
See also
______________________________________________________________
SAP AG
391
SAP System
______________________________________________________________
17.7.5 Material where-used-list (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can call up a material where-used-list in
the structural display for technical objects as well as in order processing. This where-used-list shows you
which materials for the technical object are withdrawn from storage most often.
Effects on Customizing
In Customizing for Plant Maintenance and Customer Service under Define Selection Process for
Structural Display and BOM, you must define the parameter Number of orders for material
where-used-list.
See also
17.7.6 Multiplying out quantities in structural displays (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), if multi-level BOMs are displayed in
structural displays, you can slect whether the "requirement quantity on the lower level" should be
multiplied out with the "quantity on the higher level".
Example
A technical object (higher level) is composed of 5 wheels. A wheel (lower level) is composed of:
o
4 screws
o
1 tire
o
1 rim
If the lower level is multiplied out with the higher level, this gives the following requirement quantities:
o
20 screws
o
5 tires
o
5 rims
See also
17.7.7 Search for technical objects (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can select by master data and class
characteristics in the list editing of technical objects. To do this the system uses the following search
strategies:
______________________________________________________________
SAP AG
392
SAP System
______________________________________________________________
o
If you enter a technical object in the selection screen and specify additional class characteristics,
then the system searches first by the master data and then by the class characteristics.
o
If you do not enter a technical object in the selection screen but specify class characteristics, then
the system first searches by class characteristics, then by master data.
You can use the Business Add-In (BAdI) IHSA_LIST_EDITING to override this search strategy.
See also
17.7.8 New archival objects (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) archiving is also available for the following
objects:
o
Objekt links (archival object PM_NET)
o
Installation (archival object PM_IBASE)
17.7.9 PM-EQM-EQ
Equipment
17.7.9.1 Installation and removal with simultaneous goods movement
Use
As of SAP R/3 Enterprise PLM Extension 1.10 (EA-APPL 110) a function exists for installing and
removing equipment with simultaneous goods movement. This function offers you the following
alternatives:
o
You can dismantle an installed piece of equipment from a piece of equipment or a functional
location and simultaneously transfer it to stock in a storage location.
o
You can remove a piece of equipment from a storage location and install it for a piece of equipment
or functional location in one step.
A prerequisite for this function is that you have activated the tab page for serialization data in the master
record of the equipment and that the equipment has both a material- and a serial number.
Only the following predefined standard movement types are supported:
o
Installation
201, 221, 241, 261, 281, 502, 562
o
Removal
202, 222, 242, 262, 282, 501, 531, 561, 581
______________________________________________________________
SAP AG
393
SAP System
______________________________________________________________
17.7.9.2 Consupmtion control for vehicles (new)
Use
Previously you could only create vehicles in the SAP system as equipment with vehicle-specific data. It
is now possible to define counters for recording auxiliary material and consumables and to determine
average data for consumption.
From SAP R/3 Enterprise PLM Extension 1.10 (EA-APPL 110) there area many new functions
available for Fleet Management: You can enter counter readings (for example, kilometers traveled,
operating hours) on one screen, on which the consumption- and maintenance information is displayed
simultaneously.
The new functions complement the previous counter reading recording and reporting for vehicles.
The new functions take into account the pecularities of vehicles and lead to a significantly simplified
administration in daily dealings with vehicle-relevant data.
Here is an overview of the major new functions:
o
Consumption-relevant counter reading update
For example, you can enter counter readings of kilometers traveled, update material documents on
the consumption of a vehicle, define rules for the average consumption, and thereby check the
recorded consumption:
o
Mapping of gas stations in the system
For a goods withdrawal, the material documents for the consumption of a vehicle can be posted
directly to a gas station mapped in the system.
o
Selecting and displaying vehicle-specific data
You can select, for example, by vehicle type, licence plate number, and display vehicle-specific and
consumption-relevant data in the results list.
o
Vehicle-specific enhancements in the order and notification
In the order and in the notification you can use vehicle-specific data to search for a piece of
equipment. It is also possible to enter the vehicle counter reading directly in the order or the
notification.
o
Update of vehicles' consumption data
You can find further information in the release note for updates.
Effects on Customizing
You must make the settings for consumption control in Customizing for Plant Maintenance and
Customer Service under Consumption- Relevant Counter Reading Update.
17.7.9.3 Registration and archival of configured serial numbers (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) functional gaps in the configuration of serial
numbers (and equipment) are closed. Up to now the following limitations existed:
______________________________________________________________
SAP AG
394
SAP System
______________________________________________________________
o
For referenced configurations (for example, the configuration of a sales document item), the
configuration master record could be mistakenly deleted (for example, by deleting the item), even
though it still needs the serial number.
o
A configured serial number cannot be archived.
Both restrictions are now highlighted by a suitable registration of configuration references.
For further information on functionality, see SAP note 486752, for example:
o
Information on the report RIXPRA10, which enables the (initial) registration of all pre-existing
configuration references.
o
Information on downgrading the functionality up to release 4.5B.
17.7.9.4 Search for replacement equipment/-components (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can search for a replacement component
from order processing. The system bases its search on the classification data. You can select a component
in the results list and copy it into the order.
This function is also available in the object information for notifications or in the equipment master
record; however, the results list here has a purely informative character.
See also
17.7.9.5 Synchronization of construction type and material number (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can use the equipment category to
control whether the construction type is kept synchronous with the material number in the master record
for serialized equipment.
Effects on Existing Data
If the system contains master records for which the construction type and material number are different,
and these numbers should be kept synchronous in the future, then you can perform the conversion report
RIEQUI_SYNC_MATNR_SUBMT. After the conversion you can set the indicator in Customizing such
that the construction type must always be the same as the material number.
Effects on Customizing
In Customizing for Plant Maintenance and Customer Service, under Maintain Equipment Category,
you must set the check indicator Keep Construction Type and Material Number Synchronous.
See also
______________________________________________________________
SAP AG
395
SAP System
______________________________________________________________
17.7.9.6 Synchronization of equipment number and serial number (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), when you create master records for
serial numbers, you can use
the material master record to control that the serial numbers and equipment numbers are kept
synchronous. To do this, you must set the indicator Serialization Level in the material master record to
1.
As the equipment number is, by definition, unique at client level, by synchronizing the serial number and
the equipment number you can make serial numbers unique material-wide. The prerequisite for thisis
that all material master records have the indicator serialization level set to 1.
See also
17.7.10 PM-EQM-BM
Bills of Material (Plant Maintenance)
17.7.10.1 Display of indirectly assigned BOMs (changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the display of indirectly assigned BOMs for
displaying structural displays for technical objects was changed as follows:
o
As soon as the field construction type in the master record for the technical object is filled, the
construction type is also displayed in the structural display.
o
If the construction type is assigned to a material BOM and the field for the BOM explosion is
selected, then this is also displayed under the construction type in the structural display.
See also
17.7.11 PM-EQM-SF
17.7.11.1 PM-EQM-SF-MPC
Additional Functions
Measuring Points and Counters
17.7.11.1.1 Consupmtion control for vehicles (new)
Use
Previously you could only create vehicles in the SAP system as equipment with vehicle-specific data. It
is now possible to define counters for recording auxiliary material and consumables and to determine
average data for consumption.
______________________________________________________________
SAP AG
396
SAP System
______________________________________________________________
From SAP R/3 Enterprise PLM Extension 1.10 (EA-APPL 110) there area many new functions
available for Fleet Management: You can enter counter readings (for example, kilometers traveled,
operating hours) on one screen, on which the consumption- and maintenance information is displayed
simultaneously.
The new functions complement the previous counter reading recording and reporting for vehicles.
The new functions take into account the pecularities of vehicles and lead to a significantly simplified
administration in daily dealings with vehicle-relevant data.
Here is an overview of the major new functions:
o
Consumption-relevant counter reading update
For example, you can enter counter readings of kilometers traveled, update material documents on
the consumption of a vehicle, define rules for the average consumption, and thereby check the
recorded consumption:
o
Mapping of gas stations in the system
For a goods withdrawal, the material documents for the consumption of a vehicle can be posted
directly to a gas station mapped in the system.
o
Selecting and displaying vehicle-specific data
You can select, for example, by vehicle type, licence plate number, and display vehicle-specific and
consumption-relevant data in the results list.
o
Vehicle-specific enhancements in the order and notification
In the order and in the notification you can use vehicle-specific data to search for a piece of
equipment. It is also possible to enter the vehicle counter reading directly in the order or the
notification.
o
Update of vehicles' consumption data
You can find further information in the release note for updates.
Effects on Customizing
You must make the settings for consumption control in Customizing for Plant Maintenance and
Customer Service under Consumption- Relevant Counter Reading Update.
17.7.11.1.2 Measurement value graphic (changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470), the graphic of measurement documents is
linked to the Graphical Framework (GFW), which can be used to control various external graphic tools.
This has the following advantages:
o
The values are easier to recognise.
o
The time axis is automatically scaled.
o
The values of different measuring points can be displayed at the same time.
______________________________________________________________
SAP AG
397
SAP System
______________________________________________________________
17.7.11.1.3 Generation of interval documents (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can use interval documents for the
counter reading transfer.
Example
A commercial airline is mapped in the SAP system as a hierarchical structure of technical objects
(functional locations and equipment). The airplanes are individually maintained using
counter-based maintenanceplans. Depending on the frequency of the recording in this example each
airplane incurs 5000 or more measurement documents every day. For a typical stock of 50 to 500
airplanes, this means a volume of documents that present databases can barely (if at all) handle.
Because only the latest counter reading is relevant for maintenance planscheduling, an option was created
to group the counter readings on the lower-levels into interval documents. This means that the same
measurment document is used as long as the equipment is installed in the same functional location or
main piece of equipment. That is, there is only one measurement document for each installation interval
of a piece of equipment, thus giving rise to the term "interval document".
Effects on Customizing
For further information see the Implementation Guide for Plant Maintenance and Customer Service
under Make System Settings for Measuring Points and Measurement Documents.
See also
For further information, see our Help Portal under help.sap.com.
17.7.11.1.4 Update of vehicles' consumption data (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) consumption data of vehicles is udated into
the Plant Maintenance Information System (PMIS).
Measuring points with counters are used to update the consumption data of vehicles. When you save a
measurement document a new event is triggered and the data is written to the PMIS.
In addition, a new standard info structure (S114) is created, which you can evaluate using the vehicle
consumption analysis.
Effects on Customizing
You must make the settings for the update in Customizing for Plant Maintenance and Customer
Service under Set Measurement Document Update.
See also
______________________________________________________________
SAP AG
398
SAP System
______________________________________________________________
17.8 PM-PRM
Preventive Maintenance
17.8.1 Worklist for notifications (enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the "Worklist for notifications from
preventive maintenance" is available with enhanced functions.
The new functions affect the following notifications:
o
Manually created notifications
o
Notifications that were generated using maintenance plans (maintenance plan notifications)
The worklist for notifications can be used to compile several notifications that should be processed
together into one maintenance- or service order ("worklist"). For this purpose, enter a task list in a
maintenance- or service notification (see Assigning a task list to the notification.
Operations are automatically generated for the order if you
o
Group several notifications into one order
o
Assign a notification to an order
In doing this, the system cancles the task lists assigned to a notification, copies the operations from the
task list into the order, and writes the notification in the object list of the order. The reference between the
notification and the operation remains comprehensible. If no task list is assigned to a notification, then
the system generates a dummy operation for the notification in the order.
Example
You can use the worklist, for example, to group together all the notifications for a particular
building or for a particular work center, and, for example, to optimize the circuit for maintenance
activities for which a special analysis chest is required.
In the operations of the task list every notification contains the tasks for the later execution. The
organization, printing of shop papers, and confirmation are greatly simplified by grouping the
notifications into one order.
The main new functions in overview:
o
Assign order operations or change assignment
o
Delete notifications, including operations, from the object list of the order
o
Display notifications for an operation
o
Change header notification in the order
Effects on Customizing
To assign operations to the object list entries or to change assignments, you must actiavate the function in
Customizing of Plant Mainteanance and Customer Service under Define notification and order
integration.
See also
______________________________________________________________
SAP AG
399
SAP System
______________________________________________________________
17.8.2 PM-PRM-MP
Maintenance Plans
17.8.2.1 Generation of interval documents (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can use interval documents for the
counter reading transfer.
Example
A commercial airline is mapped in the SAP system as a hierarchical structure of technical objects
(functional locations and equipment). The airplanes are individually maintained using
counter-based maintenanceplans. Depending on the frequency of the recording in this example each
airplane incurs 5000 or more measurement documents every day. For a typical stock of 50 to 500
airplanes, this means a volume of documents that present databases can barely (if at all) handle.
Because only the latest counter reading is relevant for maintenance planscheduling, an option was created
to group the counter readings on the lower-levels into interval documents. This means that the same
measurment document is used as long as the equipment is installed in the same functional location or
main piece of equipment. That is, there is only one measurement document for each installation interval
of a piece of equipment, thus giving rise to the term "interval document".
Effects on Customizing
For further information see the Implementation Guide for Plant Maintenance and Customer Service
under Make System Settings for Measuring Points and Measurement Documents.
See also
For further information, see our Help Portal under help.sap.com.
17.8.2.2 Separate completion of maintenance call dates (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can use the indicator completion date
to influence the maintenance process when completing notifications and orders. For example, you can
prevent that every employee, who can complete orders and notifications, simultaneously uses this data to
influence the scheduling of maintenance plans.
You can use the indicator to :
Activate a separate completion for the
o
maintenance plan for completing the maintenance call objects "notification" and "order".Activate a
dialog for a separate completion for the maintenance plan
o
when using the list editing for completing notifications and orders.
o
Activate the additional functionality for completing the maintenance call objects "notification" and
______________________________________________________________
SAP AG
400
SAP System
______________________________________________________________
"order" using the Business Add-In IWO1_ORDER_BADI, thus preventing the data being passed on
to the maintenance plan.
Effects on Customizing
To have the option of separate completions for maintenance call dates, in Customizing for Plant
Maintenance and Customer Service you must set the indicator completion date under Define
Maintenance Plan Category.
For further information on the function of separate completions for maintenance call dates, see the
documentation on the indicator completion date.
See also
17.8.2.3 Change document for preventive maintenance (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can generate change documents for
preventive maintenance objects.
The system documents changes to the following objects:
o
Maintenance plan
Change documents are written for all the relevant fields in maintenance plans. The system also
documents when a maintenance cycle or a maintenance item is added or deleted.
o
Maintenance item
In maintenance items change documents are written for all the relevant fields. Changes to the object
list and to the settlement rule are not documented.
o
Maintenance calls
The system documents all the relevant changes to scheduled or manually created calls. Newly added
calls and changes to waiting calls are not documented.
You can call up the change documents from the maintenance plan.
Note
No change documents are generated when long texts are changed.
Effects on Customizing
You can activate the writing of change documents in Customizing of Plant Maintenance and
Customer Service under Configure Maintenance Plan Categories
See also
______________________________________________________________
SAP AG
401
SAP System
______________________________________________________________
17.8.2.4 Change status of task lists and scheduling (changed)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the validity date of the task lists (particularly
the assignment of maintenance packages at operation level) is considered correctly during the scheduling
of maintenance plans.
Task lists are connected with engineering change management. You can use engineering change
management to change the master data of the task list with date validity. This can mean that data which is
valid today is no longer valid in the future because the data has been changed, deleted or amended.
Among this task list data are the maintenance packages to which individual operations can be assigned.
The maintenance packages are, in turn, the basis for scheduling strategy-based maintenanceplans.
The scheduling determines a "first" scheduling screen for this totality of "used" packages. If a schedule is
determined with a concrete plan date, then the system checks the validity of the packages for this date.
Invalid packages are deleted and not displayed. If there is no valid package for the determined date, then
the whole schedule is deleted. Subsequent schedules are based on this schedule and continue the package
sequence of the strategy.
Displaying the task list in the maintenance plan
The cycles (packages) current used are displayed in the master data of a strategy plan or a maintenance
item with strategy reference. In the maintenance plan header or in the maintenance item, the display can
take place at a freely definable time. The system determines the respective status for valid cycles and
displays these.
Adaption of maintenance plan costing
The maintenance plan costing uses the calls that exist in a costing period for a maintenance plan (as well
as calls with the status called up and also waiting). The dates that are still outstanding in this period are
"simulated" on the basis of the existing dates. This simulation for strategy plans takes place under
consideration of engineering change management for task lists.
Adaption of graphic scheduling overview
In the graphic scheduling overview you can simulate additional schedules for a freely definable period of
time in addition to the pre-existing schedules. The simulation for strategy plans also takes place under
consideration of engineering change management for task lists.
See also
17.8.2.5 Scheduling log for maintenance plans (changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the scheduling log is available in another
output format (the application log).
______________________________________________________________
SAP AG
402
SAP System
______________________________________________________________
If you use transaction IP30 to perform scheduling for one or more maintenance plans, the system displays
the scheduling log directly after the scheduling. Use the indicator Application log to select this. You can
also call up logs independently of scheduling and display, for example, all the logs for a particular period
of time.
You can use the application log to perform a precise analysis of the corresponding notifications and to
display more detailed information. Colored symbols (Stop for a termination, red for an error, yellow for a
warning, green for information) are used to differentiate between the different notification categories.
You can use the pushbuttons of the corresponding error categories to make a targeted reduction of the
notification amount.
See also
17.9 PM-WOC
Maintenance Processing
17.9.1 Worklist for notifications (enhanced)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) the "Worklist for notifications from
preventive maintenance" is available with enhanced functions.
The new functions affect the following notifications:
o
Manually created notifications
o
Notifications that were generated using maintenance plans (maintenance plan notifications)
The worklist for notifications can be used to compile several notifications that should be processed
together into one maintenance- or service order ("worklist"). For this purpose, enter a task list in a
maintenance- or service notification (see Assigning a task list to the notification.
Operations are automatically generated for the order if you
o
Group several notifications into one order
o
Assign a notification to an order
In doing this, the system cancles the task lists assigned to a notification, copies the operations from the
task list into the order, and writes the notification in the object list of the order. The reference between the
notification and the operation remains comprehensible. If no task list is assigned to a notification, then
the system generates a dummy operation for the notification in the order.
Example
You can use the worklist, for example, to group together all the notifications for a particular
building or for a particular work center, and, for example, to optimize the circuit for maintenance
activities for which a special analysis chest is required.
In the operations of the task list every notification contains the tasks for the later execution. The
organization, printing of shop papers, and confirmation are greatly simplified by grouping the
notifications into one order.
The main new functions in overview:
______________________________________________________________
SAP AG
403
SAP System
______________________________________________________________
o
Assign order operations or change assignment
o
Delete notifications, including operations, from the object list of the order
o
Display notifications for an operation
o
Change header notification in the order
Effects on Customizing
To assign operations to the object list entries or to change assignments, you must actiavate the function in
Customizing of Plant Mainteanance and Customer Service under Define notification and order
integration.
See also
17.9.2 Change header notification in order (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can change the header notification of a
maintenance- or service order.
The header notification of an order
o
Can be replaced by another header notification
o
Can have the notification characteristic "header notification" deleted entirely from the order, that is,
decouple the existing header notification
See also
17.9.3 Copy notification long text into order (new)
Use
From SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) on, you can automatically copy the
notification header long text into the order long text when you are generating maintenance- or service
orders from notifications.
Effects on Customizing
For the long text to be copied, in Customizing of Plant Maintenanceand Customizing Service you
must set the indicator Long Text under Define notification- and order integration.
See also
______________________________________________________________
SAP AG
404
SAP System
______________________________________________________________
17.9.4 Separate completion of maintenance call dates (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can use the indicator completion date
to influence the maintenance process when completing notifications and orders. For example, you can
prevent that every employee, who can complete orders and notifications, simultaneously uses this data to
influence the scheduling of maintenance plans.
You can use the indicator to :
Activate a separate completion for the
o
maintenance plan for completing the maintenance call objects "notification" and "order".Activate a
dialog for a separate completion for the maintenance plan
o
when using the list editing for completing notifications and orders.
o
Activate the additional functionality for completing the maintenance call objects "notification" and
"order" using the Business Add-In IWO1_ORDER_BADI, thus preventing the data being passed on
to the maintenance plan.
Effects on Customizing
To have the option of separate completions for maintenance call dates, in Customizing for Plant
Maintenance and Customer Service you must set the indicator completion date under Define
Maintenance Plan Category.
For further information on the function of separate completions for maintenance call dates, see the
documentation on the indicator completion date.
See also
17.9.5 Document flow (changed)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) there is an improved document flow for
maintenance- and service processing:
o
The performance was improved.
o
The document flow was restructured.
o
More documents are displayed.
o
The description of the documents was revised.
o
The documents are partially displayed at item level.
See also
______________________________________________________________
SAP AG
405
SAP System
______________________________________________________________
17.9.6 Assigning a task list to a notification (enhanced)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can enter a task list in maintenance- and
service notifications. If this notification is later assigned to an order, then the system copies the
operations of the task list into the order.
You can find further information under Worklist for notifications.
Effects on Customizing
To assign a notification to a task list, in Customizing for PlantMaintenance and Customer Service
you must show the tab page maintenance plan for the notification type under Configure screen
templates for notification types.
See also
17.9.7 Assigning and displaying operations in the object list (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can assign operations that have not yet
been assigned in a maintenance- or service order to an object list entry, and change or display the
assignment.
You can find further information on the peculiarities of notifications under Worklist for notifications.
Effects on Customizing
To be able to assign operations to the object list entries or change assignments, you must activate the
function in Customizing for Plant Maintenance and Customer Service under Define notification- and
order integration.
See also
For further information, see our Help Portal under help.sap.com.
17.9.8 PM-WOC-MN
Maintenance Notifications
17.9.8.1 BAPIs for maintenance- and service notifications (new)
Use
From SAP R/3 Enterprise PLM Extension 1.10 (EA_APPL 110) the following Business Application
Programming Interfaces (BAPI) methods exist for maintenance- and service notifications:
o
NotifCreate
______________________________________________________________
SAP AG
406
SAP System
______________________________________________________________
You can use this method to create maintenance- and service notifications, including items, causes,
tasks, activities, long texts, and partners.
o
NotifDataAdd
You can use this method to add further items, causes, tasks, activities, long texts, and partners to
pre-existing maintenance- and service notifications.
o
NotifDataDelete
You can use this method to delete items, causes, tasks, activities, long texts, and partners for
pre-existing maintenance and service notifications.
o
NotifDataModify
You can use this method to change items, causes, tasks, activities, long texts, and partners in
pre-existing maintenance- and service notifications.
o
NotifGetDetail
You can use this method to read pre-existing maintenance- and service notifications together with
their respective items, causes, tasks, activities, long texts, and partners from the database.
o
NotifClose
You can use this method to complete pre-existing maintenance- and service notifications.
o
NotifPostpone
You can use this method to put back pre-existing maintenance- and service notifications.
o
NotifPutinprogress
You can use this method to release pre-existing maintenance- and service notifications.
o
NotifChangeusrstat
You can use this method to change the user status of pre-existing maintenance- and service
notifications.
o
NotifTaskComplete
You can use this method to set tasks from maintenance- or service notifications to completed.
o
NotifTaskRelease
You can use this method to release tasks from maintenance- or service notifications.
o
NotifTaskSuccess
You can use this method to indicate tasks from maintenance- or service notifications as successful.
After executing these BAPIs you must execute the function modules BAPI_ALM_NOTIF_SAVE and
BAPI_TRANSACTION_COMMIT so that the data is written to the database. Lists can be created with
the following methods:
NotifListEqui
This method can be used to create a list of maintenance- or service notifications for a piece of equipment.
NotifListFuncloc
This list can be used to create a list of maintenance- or service notifications for a functional location.
NotifListPartner
This list can be used to create a list of maintenance- or service notifications for a combination of partner
roles and partners.
NotifListPlangroup
______________________________________________________________
SAP AG
407
SAP System
______________________________________________________________
This list can be used to create a list of maintenance- or service notifications for a combination of
maintenance planner groups and
maintenance planning plants.
NotifListSortfeld
This list can be used to create a list of maintenance- or service notifications for a sort field.
17.9.8.2 Search for replacement equipment/-components (new)
Use
As of SAP R/3 Enterprise Core 4.70 (SAP_APPL 470) you can search for a replacement component
from order processing. The system bases its search on the classification data. You can select a component
in the results list and copy it into the order.
This function is also available in the object information for notifications or in the equipment master
record; however, the results list here has a purely informative character.
See also
17.9.8.3 New Developments in Notifications: Several Customer Subscreens
Possibl
Use
Several Customer Subscreens:
Up until release 4.6C, for each notification type a maximum of one customer subscreen could be included
in the notification header data. An area of 4 lines was reserved for this subscreen. From release 4.70, for
each notification type it is possible to include one or more customer subscreens in the notification header
data. The size of the customer subscreens can be freely defined as long as they do not exceed the total
size of the tab pages.
Enhancements in User Exits:
In the customer enhancement QQMA0001, the interface of t