Administration Guide CUSTOMER Document Version: 1.0 – yyyy-mm-dd SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Administration Guide CUSTOMER
Document Version: 1.0 – yyyy-mm-dd
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Content
1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
2 Installation Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7
3 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
4 Migration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
5 Monitoring. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
6 Security Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
7 Extensibility. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
2 C U S T O M E RSAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Content
1 Getting Started
This document is a single source of information for the implementation of SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting. It contains implementation information as well as security and operation information and is divided into the following sections:
● Installation Information● Configuration● Migration● Monitoring● Security Information● Extensibility
Planning Information
For more information about implementation topics not covered in this guide, see the following content on SAP Service Marketplace.
Table 1:
Content Location on SAP Service Marketplace
Latest versions of installation and upgrade guides http://service.sap.com/instguides
General information about SAP Revenue Accounting and Reporting
http://service.sap.com/
Sizing, calculation of hardware requirements http://service.sap.com/quicksizer
Released platforms and technology-related topics http://service.sap.com/platforms
http://service.sap.com/pam
Network security http://service.sap.com/securityguide
High availability http://www.sdn.sap.com/irj/sdn/ha
Performance http://service.sap.com/performance
Information about support package stacks, latest software versions, and patch level requirements
http://service.sap.com/sp-stacks
Information about Unicode technology http://www.sdn.sap.com/irj/sdn/i18n
SAP Sales and Distribution Integration with SAP Revenue Accounting and ReportingGetting Started C U S T O M E R 3
Useful Links
Table 2:
Content Location on SAP Service Marketplace
Information about creating error messages http://service.sap.com/messages
SAP Notes search http://service.sap.com/notes
SAP Software Distribution Center http://service.sap.com/swdc
SAP Online Knowledge Products http://service.sap.com/rkt
Important SAP Notes
You must read the following SAP Notes before you start the installation. These SAP Notes contain the most recent information regarding installation, as well as corrections to the installation documentation.
Table 3:
SAP Note Number Title
1987012 Release Strategy Note for REVREC 100
1841471 Release strategy for ABAP add-ons for interface components
1960535 SD Core Changes for the Integration with Revenue Accounting and Reporting
2145357 SD core changes for RA migration
2025378 Profitability Object Number missing for order item
1992006 CO-PA Activation for Add-On “Revenue Accounting and Reporting”
2106948 Revenue Accounting Relevance for Credit/Debit memo request
2157588 Field FARR_RELTYPE not copied
2168058 SD/FI-CA: Creation of invoice item RAIs for revenue accounting
2176036 Incorrect POB conditions after migration
2234306 No RAI created when goods issue
4 C U S T O M E RSAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Getting Started
SAP Note Number Title
2256360 Revenue Accounting-relevant delivery items are not transferred when batch splits exist
2293834 SD/FI-CA: Creation of invoice items of revenue accounting for SD bills terminates
2295169 Activation of the function 'Cost Recognition' in CO-PA for add-on solution 'FI Revenue Accounting'
2301126 Migration of SD Revenue Recognition to Revenue Accounting
2315379 Initial load program generates a runtime error during reset
2328733 Revenue accounting: Enhancements for the SD/FI-CA integration (SAP_APPL)
2333465 Field FARR_RELTYPE not displayed properly in Sales Order documents
2335777 SD core change for Revenue Accounting PAOBJNR
2361659 Prerequisite Note for Note 2333465
2365079 FI-RA conditions are relevant for accrual
2386245 Account determination suppressed for migration reset
Technical System Landscape
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting provides functions to integrate sales and distribution documents with SAP Revenue Accounting and Reporting.
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting is delivered as product version SAP SALES INTEGR SAP RAR 1.0 that integrates with SAP REVENUE ACCOUNTING 1.1.
This product consists of software component version REVRECSD 1.0 SP 5 and requires a minimum software version of SAP ERP 6.0 without the enhancement package. You install it on top of your sales and distribution system. Depending on whether sales and distribution and financials applications run on the same system, you have deployment options.
Deployment in Different Systems
Sales and Distribution isn't managed in the same system as financials. You install SAP SALES INTEGR SAP RAR 1.0 on top of your sales and distribution system. It can be installed from SAP ERP 6.0 or higher; if your sales and distribution system is already on SAP ERP 6.0, you don't have to upgrade.
SAP REVENUE ACCOUNTING 1.1 can be installed on SAP ERP 6.0 Enhancement Package 5 or higher. If your financials system is below that system level, you must to SAP ERP 6.0 Enhancement Package 5.
SAP Sales and Distribution Integration with SAP Revenue Accounting and ReportingGetting Started C U S T O M E R 5
Data Harmonization Requirements
For deployment on different systems, the systems need harmonized master data and configuration. SAP Revenue Accounting and Reporting doesn't have key-mapping or value-mapping functions in its portfolio. You need to harmonize these data and settings in both systems:
● Company codes, including company code currencies and currency settings● CO-PA configurations, structures, value fields, and operations, if used● Customers, business partners● Accounts and account assignments, profit centers, and business areas
Deployment in One System
In many cases, sales and distribution runs in the same system as financials and controlling. In this case, both products are installed on the same stack.
Required alternative product versions, instances, and minimal support package stacks for SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting.
Table 4:
Product Version Instance Support Package
SAP ERP 6.0 SAP ECC server 15
EHP2 for SAP ERP 6.0 Central applications 06
EHP3 for SAP ERP 6.0 Central applications 05
EHP4 for SAP ERP 6.0 Central applications 05
EHP5 for SAP ERP 6.0 Central applications 10
EHP6 for SAP ERP 6.0 Central applications 06
EHP6 for SAP ERP 6.0 on HANA Central applications 01
EPH7 for SAP ERP 6.0 Central applications 01
SAP sFinancials 1.0 Smart financials Initial shipment stack
6 C U S T O M E RSAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Getting Started
2 Installation Information
Preparation
Before installation, install these SAP Notes:
Table 5:
SAP Note Title
1960535 SD Core Changes for the Integration with Revenue Accounting and Reporting
2025378 Profitability Object Number missing for order item
2145357 SD core changes for RA migration
1987012 Release Strategy Note for REVREC 100
1841471 Release strategy for ABAP add-ons for interface components
Related Guides
Table 6:
Upgrade and Update Guide for SAP ERP 6.0 http://service.sap.com/erp-inst
Upgrade and Update Guide for SAP ERP 6.0 Enhancement Package 5
http://service.sap.com/erp-ehp5-inst
Upgrade and Update Guide for SAP ERP 6.0 Enhancement Package 6
http://service.sap.com/erp-ehp6-inst
Upgrade and Update Guide for SAP ERP 6.0 Enhancement Package 7
http://service.sap.com/erp-ehp7-inst
Installation and Upgrade Guide SAP NetWeaver 7.0 http://service.sap.com/installNW70
Installation and Upgrade Guide SAP NetWeaver 7.0 Enhancement Package 2
http://service.sap.com/installNW70
Installation and Upgrade Guide SAP NetWeaver 7.3 http://service.sap.com/installNW73
Installation and Upgrade Guide SAP NetWeaver 7.4 http://service.sap.com/installNW74
SAP Sales and Distribution Integration with SAP Revenue Accounting and ReportingInstallation Information C U S T O M E R 7
Postinstallation
Using the hierarchy maintenance transaction, activate all Web Dynpro applications whose name starts with FARR_. Web Dynpro applications are activated under default_host/sap/bc/webdynpro/sap.
8 C U S T O M E RSAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Installation Information
3 Configuration
SAP Revenue Accounting and Reporting IMG Path
The Customizing activity for this product is available at Sales and Distribution Revenue Accounting and Reporting .
Application Integration
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting and SAP Revenue Accounting and Reporting communicate with RFC function calls. If these instances are installed in different systems, you need to define an RFC destination with connection type 3 (connection to ABAP system). The solution tries to establish a bgRFC connection as the preferred connection type. You should create an RFC destination that supports the bgRFC protocol. To do this, run the RFC destinations transaction, choose the Special Options tab, and select Classic with bgRFC as the Transfer Protocol.
To use the integration component, activate the Customizing activity Sales and Distribution Revenue Accounting and Reporting Integrate with Revenue Accounting .
For more information about general background communication, see http://help.sap.com SAP Supply Chain Management SAP SNC, UI Add-On for Purchase Order Collaboraiton SAP SNC, UI Add-On for Purchase Order Collaboration 1.0 Connectivity Components of SAP Communication Technology Classic SAP Technologies (ABAP) RFC Background Communication bgRFC (Background Remote Function Call) .
SAP Sales and Distribution Integration with SAP Revenue Accounting and ReportingConfiguration C U S T O M E R 9
4 Migration
When you start using SAP Revenue Accounting and Reporting, you need to migrate your data for your existing open contracts into the system. This process is detailed on the SAP Help Portal. This chapter refers to migrating data from SAP Sales and Distribution.
The load transfers information about operational documents and posted revenue to SAP Revenue Accounting and Reporting. It has to select all operational contracts (and their related documents) that impact revenue recognition and pass this information to SAP Revenue Accounting and Reporting using defined Interfaces. The load also has to evaluate which revenue was posted in GL up to and including the transfer date. This information is passed with a separate interface (legacy data interface).
The load only selects items that are relevant for revenue accounting in accordance with the RAI settings that are maintained in Customizing at Sales and Distribution Revenue Accounting and Reporting Maintain Revenue Accounting Item Settings .
If the migration of all revenue accounting-relevant open contracts isn't possible in one period (for example, due to data volume), migration packages can be defined in Customizing and the migration may be limited to one migration package. After completing the migration of all contracts in one package, subsequent packages may be defined in later periods.
10 C U S T O M E RSAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Migration
5 Monitoring
Alert Monitoring
Proactive, automated monitoring is the basis for ensuring reliable operations for your SAP system environment. SAP provides the infrastructure and recommendations needed to set up your alert monitoring to recognize critical situations for SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting as quickly as possible. We don't offer specific data in the computer center management system (CCMS) for alert monitoring. Nevertheless, general monitoring options can be used.
Table 7:
Product Version Location
SAP Enhancement Package 3 for SAP NetWeaver 7.0 http://help.sap.com/nw703 System Administration and
Maintenance Information Technical Operations for SAP
NetWeaver Administration of SAP NetWeaver Systems
Application Server ABAP (AS ABAP) Monitoring and
Administration Tools for Application Server ABAP
SAP Enhancement Package 1 for SAP NetWeaver 7.3 http://help.sap.com/nw731 System Administration and
Maintenance Information Technical Operations for SAP
NetWeaver Administration of Application Server ABAPMonitoring and Administration Tools for Application Server
ABAP
To enable the auto-alert mechanism of CCMS, see SAP Note 617547 .
Background RFC Communication
The bgRFC transaction and authorization object, S_BGRFC, are required for monitoring or customizing activities.
For more information regarding troubleshooting and monitoring for background communication, go to http://help.sap.com , SAP Supply Chain Management SAP SNC, UI Add-On for Purchase Order CollaborationSAP SNC, UI Add-On for Purchase Order Collaboration 1.0 Connectivity .
Caution
Background communication requires that you applied SAP Note 2013706 .
SAP Sales and Distribution Integration with SAP Revenue Accounting and ReportingMonitoring C U S T O M E R 11
Application Log
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting uses the application log to report issues during processing. You use the display and delete logs transactions. SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting uses object FARR with the subobject RAI_LOADfor messages issued during the initial load of RAI.
For more information about the maintenance of the application log, see the following at http://help.sap.com :
● Displaying logSupply Chain Management SAP SNC, UI Add-On for Purchase Order Collaboration SAP SNC, UI Add-On
for Purchase Order Collaboration 1.0 Connectivity Application Log (BC-SRV-BAL) Displaying log● Analyze log
Supply Chain Management SAP SNC, UI Add-On for Purchase Order Collaboration SAP SNC, UI Add-On for Purchase Order Collaboration 1.0 Connectivity Application Log (BC-SRV-BAL) Analyze log
● Deleting logSupply Chain Management SAP SNC, UI Add-On for Purchase Order Collaboration SAP SNC, UI Add-On
for Purchase Order Collaboration 1.0 Connectivity Application Log (BC-SRV-BAL) Deleting log● Archiving object BC_SBAL
Supply Chain Management SAP SNC, UI Add-On for Purchase Order Collaboration SAP SNC, UI Add-On for Purchase Order Collaboration 1.0 Connectivity Application Log (BC-SRV-BAL) Archiving Object BC_SBAL
Backup and Restore
You need to back up your system landscape regularly to ensure you can restore and recover it in case of failure.
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting is based on SAP ERP 6.0, which is based on SAP NetWeaver technology. All related SAP NetWeaver backup procedures also work for SAP ERP 6.0.
For more information, see the best practices document at http://service.sap.com/bp-roadmap Backup and Restore for SAP System Landscapes .
Reconciliation
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting integrates with SAP Revenue Accounting and Reporting, but is loosely coupled. In this loosely coupled architecture, different components manage their own data. This requires reconciliation between the components.
SAP Revenue Accounting and Reporting supports the reconciliation between sales orders and invoices and the resulting RAIs. The reconciliation is executed in SAP Revenue Accounting and Reporting. SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting provides all required callback routines used by this check.
12 C U S T O M E RSAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Monitoring
Software Change Management
Software change management standardizes and automates software distribution, maintenance, and testing procedures for complex software landscapes and multiple software development platforms. These functions support your project teams, development teams, and application support teams.
The goal of software change management is to establish consistent, solution-wide change management that enables specific maintenance procedures, global rollouts (including localizations), and open integration with third-party products.
Transport and Change Management
All components of SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting are client-enabled.
For transport and change management issues, the procedures of SAP NetWeaver apply. For more information, see SAP NetWeaver documentation.
Development Requests and Development Release Management
The standard procedures of SAP NetWeaver apply.
Support Packages and Patch Implementation
We recommend that you implement support package stacks (SPS), which are sets of support packages and patches for the respective product version used in the given combination. The technology for applying support packages and patches will not change. You can find detailed information about the availability of SPS for SAP ERP 6.0 at http://service.sap.com/sp-stacks .
Read the corresponding release and information notes before you apply any support packages or patches of the selected SPS. Use the maintenance optimizer of SAP Solution Manager to select, download, and install the needed software components and support packages. For more information, see the following:
● SAP Solution Manager at http://help.sap.com SAP Solution Manager Change Management Maintenance Optimizer
● SAP Service Marketplace at http://service.sap.com/solman-mopz● Documentation for SAP Add-On Installation Tool● For more information about the implementation of support packages, http://service.sap.com/patches
SAP Support Packages in Detail● For more information about the tools necessary for implementing patches, see SAP NetWeaver
documentation.
SAP Sales and Distribution Integration with SAP Revenue Accounting and ReportingMonitoring C U S T O M E R 13
6 Security Information
With the increasing use of distributed systems and the Internet for managing business data, the demands on security are on the rise. When using a distributed system, your data and processes must support your business needs without unauthorized access to critical information. User errors, negligence, or attempted manipulation of your system shouldn't result in loss of information or processing time. These demands on security apply to the SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting.
User Administration and Authentication
User Management
User management for SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting uses the mechanisms provided with SAP NetWeaver AS ABAP and AS Java, for example, tools, user types, and password policies.
Table 8: User Management Tools
Tool Detailed Description Comment
User maintenance for ABAP-based systems
You use the user maintenance transaction to generate users in the ABAP-based systems.
For more information, see User and Role Administration of Application Server ABAP.
Used for all deployment options of the SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Role maintenance You use the role maintenance transaction to generate profiles for users.
For more information, see User and Role Administration of Application Server ABAP.
Used for all deployment options of the SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
User Management Engine with SAP NetWeaver AS Java
You use this User Management Engine for creating Portal users.
For more information, see User Management Engline.
Used for deployment option SAP NetWeaver Portal
14 C U S T O M E RSAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Security Information
Integration into Single Sign-On Environments
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting supports the SSO mechanisms provided by SAP NetWeaver. The security recommendations and guidelines for user administration and authentication as described in the SAP NetWeaver Security Guide also apply.
For more information on the available authentication mechanisms, see User Authentication and Single Sign-On.
Authorizations
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting uses the authorization concept provided by SAP NetWeaver AS ABAP or AS Java. The recommendations and guidelines for authorizations as described in the SAP NetWeaver AS Security Guide ABAP or SAP NetWeaver AS Security Guide Java also apply.
The SAP NetWeaver authorization concept is based on assigning authorizations to users based on roles. For role maintenance, use the profile generator on AS ABAP and the user management engine’s user administration console on AS Java.
Standard Roles
We don't deliver standard roles with SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting.
Standard Authorization Objects
We don't deliver standard authorization objects with SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting. For sales document processing, the standard objects delivered with the sales and distribution modules are sufficient.
Session Security Protection
To increase security and prevent access to the SAP logon ticket and security session cookies, we recommend activating secure session management.
We also recommend using SSL to protect the network communications where these security-relevant cookies are transferred.
Session Security Protection on AS ABAP
To activate session security on AS ABAP, set the corresponding profile parameters and activate the session security for the clients using the relevant transaction.
For more information, a list of the relevant profile parameters, and detailed instructions, see Activating HTTP Security Session Management on AS ABAP in the AS ABAP security documentation.
Session Security Protection on AS Java
On AS Java, set the HTTP provider properties as described in Session Security Protection.
SAP Sales and Distribution Integration with SAP Revenue Accounting and ReportingSecurity Information C U S T O M E R 15
Network and Communication Security
Your network infrastructure is extremely important in protecting your system. Your network needs to support the communication necessary for your business needs without allowing unauthorized access. A well-defined network topology can eliminate many security threats based on software flaws (at the operating system level and application level) or network attacks, such as eavesdropping. If users can't log on to your application or database servers at the operating system or database layer, then there's no way for intruders to compromise the machines and gain access to the backend system’s database or files. Additionally, if users can't connect to the server LAN, they can't exploit well-known bugs and security holes in network services on the server machines.
The network topology for the SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting is based on the topology used by SAP NetWeaver. The security guidelines and recommendations described in the SAP NetWeaver Security Guide apply. Details that apply specifically are described in the following topics:
● Communication Channel Security● Network Security● Communication Destinations
For more information, see the following sections in the SAP NetWeaver Security Guide:
● Network and Communication Security● Security Guides for Connectivity and Interoperability Technologies
Communication Channel Security
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting sends information to SAP Revenue Accounting and Reporting as RAIs.
This table illustrates the communication channels used by SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting, the protocol used for the connection, and the types of data transferred.
Table 9:
Communication Path Protocol Used Type of Data Transferred
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting to SAP Revenue Accounting and Reporting
RFC RAI
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting SAPGUI Applications
DIAG UI control data
RFC and DIAG connections are protected with SNC.
RecommendationWe recommend using secure protocols (SSL, SNC) whenever possible.
For more information, see Transport Layer Security and Web Services Security in the SAP NetWeaver Security Guide.
Ports
16 C U S T O M E RSAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Security Information
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting runs on SAP NetWeaver and uses the ports from AS ABAP or AS Java. For more information, see AS ABAP Ports and AS Java Ports in the corresponding SAP NetWeaver Security Guide. For other components, see TCP/IP Ports Used by SAP Applications on SAP Developer Network.
Communication Destinations
This table gives an overview of the communication destinations used by SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting.
Table 10:
Destination Delivered Type User, Authorizations Description
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting to SAP Revenue Accounting and Reporting
No RFC User-based authorizations
RAI creation
Third party to SAP Revenue Accounting and Reporting
No RFC User-based authorizations
Transfer of legacy data from third party systems to SAP Revenue Accounting and Reporting
Internet Communication Framework Security
You should activate required services for the applications running in your system. For SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting no services are required.
Services for Security Lifecycle Management
Security Chapter in the EarlyWatch Alert Report
This service regularly monitors the security chapter in the EarlyWatch alert (EWA) report of your system. It tells you
● Whether SAP Security Notes have been identified as missing on your systemAnalyze and implement the identified SAP Notes if possible. If you cannot implement the SAP Notes, the report should be able to help you decide on how to handle the individual cases.
● Whether an accumulation of critical basis authorizations has been identifiedVerify whether the accumulation of critical basis authorizations is okay for your system. If not, correct the situation. If you consider the situation okay, check for any significant changes compared with former EWA reports.
● Whether standard users with default passwords have been identified on your systemChange the corresponding passwords to nondefault values.
SAP Sales and Distribution Integration with SAP Revenue Accounting and ReportingSecurity Information C U S T O M E R 17
Security Optimization Service
The security optimization service (SOS) can be used for a more thorough security analysis of your system.
● Critical authorizations in detail● Security-relevant configuration parameters● Critical users● Missing security patches
This service is available as a self-service within SAP Solution Manager, as a remote service, or as an on-site service. We recommend you use it regularly and after significant system changes or in preparation for a system audit.
Security Configuration Validation
The security configuration validation can be used to monitor a system landscape continuously for compliance with predefined settings. This primarily covers configuration parameters, but it also covers critical security properties like the existence of a nontrivial gateway configuration or ensuring standard users don't have default passwords.
Secure Operations Standard
With the E2E solution operations standard security service, a best practice recommendation is available on how to operate SAP systems and landscapes securely. It guides you through the most important security operation areas and links to detailed security information from SAP’s knowledge base wherever appropriate.
18 C U S T O M E RSAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Security Information
7 Extensibility
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting provides field extensibility to pass a defined set of information to SAP Revenue Accounting and Reporting. This is a small subset of information available in sales orders. If the information is insufficient, you can extend the data passed to SAP Revenue Accounting and Reporting. It is a prerequisite that SAP Revenue Accounting and Reporting is extended by the same fields.
SAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting uses extension include INCL_EEW_FARRIC_SD01MI. This structure is included in all relevant tables and internal structures. When you add a customer field to this structure, it is available in all relevant components.
To transfer information from sales orders to the extension include structure, create a BAdI implementation for enhancement spot FARRIC_SD, BAdI FARRIC_BADI_ORDER, and method ORDER_DATA_TO_ARL_CUSTOM. Parameter IT_RAI_MAIN_ITEM contains all RAIs created in SAP Revenue Accounting and Reporting. Copy all items to be enhanced with custom information to ET_RAI_MAIN_ITEM and enter the required information.
Do not use parameters IT_RAI_CONDITIONS and ET_RAI_CONDITIONS.
SAP Sales and Distribution Integration with SAP Revenue Accounting and ReportingExtensibility C U S T O M E R 19
Important Disclaimers and Legal Information
Coding SamplesAny software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, unless damages were caused by SAP intentionally or by SAP's gross negligence.
AccessibilityThe information contained in the SAP documentation represents SAP's current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP in particular disclaims any liability in relation to this document. This disclaimer, however, does not apply in cases of willful misconduct or gross negligence of SAP. Furthermore, this document does not result in any direct or indirect contractual obligations of SAP.
Gender-Neutral LanguageAs far as possible, SAP documentation is gender neutral. Depending on the context, the reader is addressed directly with "you", or a gender-neutral noun (such as "sales person" or "working days") is used. If when referring to members of both sexes, however, the third-person singular cannot be avoided or a gender-neutral noun does not exist, SAP reserves the right to use the masculine form of the noun and pronoun. This is to ensure that the documentation remains comprehensible.
Internet HyperlinksThe SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint about where to find related information. SAP does not warrant the availability and correctness of this related information or the ability of this information to serve a particular purpose. SAP shall not be liable for any damages caused by the use of related information unless damages have been caused by SAP's gross negligence or willful misconduct. All links are categorized for transparency (see: http://help.sap.com/disclaimer).
20 C U S T O M E RSAP Sales and Distribution Integration with SAP Revenue Accounting and Reporting
Important Disclaimers and Legal Information
SAP Sales and Distribution Integration with SAP Revenue Accounting and ReportingImportant Disclaimers and Legal Information C U S T O M E R 21
go.sap.com/registration/contact.html
© 2017 SAP SE or an SAP affiliate company. All rights reserved.No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice.Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names mentioned are the trademarks of their respective companies.Please see http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
Related Documents
