Configuration Rationale Document

Document Purpose

The intent of the Configuration Rationale Document (CRD) is to collect and explain the S4HANA configuration table
entries decided to address the requirements and process solution as defined in the project BPD (Business Process
Design) documents.
The CRD is a technical Realize phase project deliverable and it is structured according to the SAP IMG (Implementation
Guide) for each component. This structure does not necessarily reflect the project Business Process Master List in
Solution Manager but it is a prerequisite to perform ITC as structured and documented in the Level 4 Process Step of the
BPML.
SAP Solution Manager 7.2 artifacts such as Business Process Flow Diagrams, Business Process Steps and
Development libraries are referenced, but not duplicated in this document.
 PROJECT IDENTIFICATION

Project Name CPI Project Number

Customer Name Customer Number

SAP Project Manager Customer Project Manager

DOCUMENT IDENTIFICATION

Author Document Location (repository/path/name)

<Document location>
Version Status Date (YYYY-MM-DD)
0.1 Draft 2021-05-20

REVISION HISTORY

Version Date Description

th
0.1 May 20 2021 Initial Draft
th
0.2 May 26 2021 After Internal review

www.sap.com/contactsap

© 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.
REVIEW AND APPROVAL
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.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality
mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are
all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation
to deliver any material, code, or functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are
cautioned not to place undue reliance on these forward-looking statements, and they should not be relied upon in making purchasing decisions.

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
Name Date (YYYY-MM-DD)
countries. All other product and service names mentioned are the trademarks of their respective companies. See http://www.sap.com/corporate-en/legal/copyright/index.epx for additional trademark
information and notices.
Customer Project Manager
Name Date (YYYY-MM-DD)
SAP Project Manager

Name Date (YYYY-MM-DD)

Key Stakeholder

Name Date (YYYY-MM-DD)

Key Stakeholder

3
Table of Contents

1. REFERENCE MATERIAL...................................................................................................................... 7
1.1 Business Process Requirement............................................................................................... 7
1.2 Business Process Design......................................................................................................... 7
2 FUNCTIONAL COVERAGE................................................................................................................... 7
2.1 High Level Description.............................................................................................................. 7
2.2 Business Process Diagram....................................................................................................... 7
3 ASSUMPTIONS..................................................................................................................................... 8
4 SAP CONFIGURATION......................................................................................................................... 8
4.1 Inbound Processing................................................................................................................... 8
4.1.1 Revenue Accounting Item............................................................................................8
4.1.1.1 Define Interface Component.................................................................................8
4.1.1.1.1 Assign Structure.........................................................................................9
4.1.1.1.2 Prerequisite Components..........................................................................9
4.1.1.1.3 Program Enhancements...........................................................................10
4.1.1.1.4 Key Fields.................................................................................................. 10
4.1.1.1.5 Component Assignment...........................................................................11
1.1.1.2 Maintain Revenue Accounting Item class.........................................................11
4.1.1.2 Generate Interfaces for Revenue Accounting Item classes.............................15
4.1.1.3 Assign Upload Rules to Revenue Accounting Item Classes...........................16
4.1.1.4 Define Modifiable fields for RAI..........................................................................16
4.1.2 Revenue Accounting Item management...................................................................17
4.1.2.1 Define Source document item type....................................................................17
4.1.2.2 Define Logical system.........................................................................................18
4.1.2.3 Define sender components.................................................................................18
4.1.2.4 Define Reference Types......................................................................................19
4.1.2.5 Define Condition types for Standalone selling prices and Right of Return....20
4.1.2.6 Assign BRF+ applications to revenue Accounting Item classes.....................21
4.1.2.7 Maintain Decision table id for Simplified BRF plus UI......................................22
4.1.2.8 Define Job Distribution for Parallel processing................................................23
4.1.2.9 Define Exemption reasons for Revenue Accounting Items.............................24
4.1.2.10 Define Program Enhancements........................................................................24
4.2 Revenue Accounting Contracts.............................................................................................. 25
4.2.1 Select Contract management for Contract categories............................................25
4.2.2 Configuring Accounting Principle specicifc settings..............................................26
4.2.3 Assign Company code to Accounting Principle......................................................26
4.2.3.1 Exclude local currency calculation from Revenue Accounting.......................27
4.2.4 Open and Close Revenue Accounting Periods........................................................27
4.2.5 Define Number ranges............................................................................................... 28
4.2.5.1 Define Number rages for Contracts...................................................................28
4.2.5.2 Define Number ranges for Performance Obligations.......................................28
4.2.5.3 Define Number ranges for Run Ids.....................................................................29
4.2.5.4 Define Contract Categories.................................................................................30
4.2.6 Define Performance Obligation types.......................................................................30
4.2.7 Condition Types......................................................................................................... 31
4.2.7.1 Define Reserved Condition type.........................................................................31
4.2.8 Define Fullfillment types............................................................................................32

4
 4.2.9 Change Message control...........................................................................................33
4.2.10 Assign BRF + Applications to Revenue Accounting Process...............................33
4.3 Integration with cost object controlling.................................................................................33
4.3.1 Assign RA Version and Currency Type to Company Code and Acct. Principle. . .33
4.3.2 Specify RA Keys and RA Versions that will Integrate with Revenue Acct............34
4.4 Revenue Accounting Postings............................................................................................... 34
4.4.1 Define Posting specification for General ledger transfer........................................34
4.4.2 Configure Account Determination for Specific Transactions.................................35
4.4.3 Configure parallel processing for Revenue Posting...............................................35
4.4.4 Define reasons for shifting contracts to next period...............................................36
4.4.5 Switch on Posting Optimization................................................................................37
4.4.6 Assigning Additional Revenue Posting Aggregation Dimensions........................37
5 BRF PLUS CONFIGURATION AND SET UP......................................................................................38
5.1 Maintain RAI processing Decision table................................................................................38
5.1.1 Process header........................................................................................................... 38
5.1.2 Process POB............................................................................................................... 38
5.1.3 Process SSP............................................................................................................... 39
5.2 Account Determination............................................................................................................ 39
5.2.1 Recognized Revenue................................................................................................. 39
5.2.2 Decision table to determine Receivable Adjustment Account...............................39
5.2.3 Decision table to determine Gl Account for Revenue Adjustment for Allocation
effect 39
5.2.4 Decision table to derive Gl Accounts for unbilled receivable................................40
5.2.5 Decision table to derive Gl accounts for Deferred Revenue...................................40
5.2.6 Decision table to derive Gl accounts for Deferred Cost..........................................40
5.2.7 Decision table to derive Gl accounts for Recognized cost.....................................40
6 INTEGRATION WITH BRIM................................................................................................................ 41
6.1 Activate Integration with Revenue Accounting.....................................................................41
6.2 Define RFC destination of the Receiving system..................................................................42
6.3 Activate Provider contract items for Revenue Accounting Items........................................42
6.4 Define service Types............................................................................................................... 43
6.5 Assign service ids to service type.......................................................................................... 44
6.6 Define Reference Types.......................................................................................................... 44
6.7 Define Source item Types....................................................................................................... 45
6.8 Define Number ranges for Revenue Accounting Item ids....................................................46
6.9 Define Price Condition used to Determine Standard alone Selling Price...........................47
6.10 GL Account determination in BRIM...................................................................................47
FICA GL Determination Procedure used as benchmark to derive RAR GL..................................47
6.10.1 Maintain Main Transactions and sub transaction...................................................47
6.11 Rationale.............................................................................................................................. 47
7 PREREQUISITES AND DEPENDENCIES..........................................................................................48
8 UNIT TEST TRACKER........................................................................................................................ 48
9 SAP CORRECTION NOTES................................................................................................................ 48

5
1. REFERENCE MATERIAL

1.1 Business Process Requirement

1.2 Business Process Design

BPD Description Link to Document

BPD ID
BPD-XX-YYYY

2 FUNCTIONAL COVERAGE

2.1 High Level Description

2.2 Business Process Diagram

Below diagram depicts the high-level process diagram for Revenue Accounting and Reporting module.

3 ASSUMPTIONS

Below are the assumptions in relation to the configuration.

 RAR and BRIM integration will be the joint responsibility of BRIM, RAR, IT team of XYZ.

6
  RAR is set to full auto mode or minimum user intervention during the day to day high volume
processing environment

 RAR will be designed for all known objects and cannot assure future accounting or compliance
changes without detailed review.

4 SAP CONFIGURATION

4.1 Inbound Processing

4.1.1 Revenue Accounting Item

4.1.1.1 Define Interface Component

Jira/Plan Reference Define Interface component

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item  Define Interface components

Transport Request

This configuration activity provides access to the interface components that can be used when defining
revenue accounting item classes.

SAP provides preconfigured interface components that can be used immediately. These include basic
components, which are mandatory for each record type ( MAIN AND CONDITION), as well as other optional
components which can be added to a Revenue Accounting Item Class.

In XYZ,we will use the standard Interface compoenents.

4.1.1.1.1 Assign Structure

Jira/Plan Reference Define Interface component – Assigned structure

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item  Define Interface components

7
Transport Request

We are using the standard business content delivered by SAP.Each Interface Component may contain up to
several data structures, dependent on status of a Revenue Accounting Item. We propose to use RAW,
PROCESSABLE AND PROCESSED statuses.

4.1.1.1.2 Prerequisite Components

Jira/Plan Reference Define Interface component – Prerequisite components

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item  Define Interface components

Transport Request

This setting indicates which interface components are prerequisites. Prerequisite components get activated
automatically when the current component is used in the revenue accounting item class.

We are using the standard business content delivered by SAP and for XYZ, we are not configuaring
anything.

4.1.1.1.3 Program Enhancements

Jira/Plan Reference Define Interface component – Program Enhancements

SAP Transaction SPRO

8
Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item  Define Interface components

Transport Request

Note: No prgram enhancements are identified

4.1.1.1.4 Key Fields

Jira/Plan Reference Define Interface component – Key Fields

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item  Define Interface components

Transport Request

We are using the standard business content delivered by SAP. Under Key Fields, for each combination of
record type and status, the structure of key fields used to generate the database tables is maintained.

4.1.1.1.5 Component Assignment

Jira/Plan Reference Define Interface component – Component Assignment

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item  Define Interface components

Transport Request

We are using the standard business content delivered by SAP

Under Assign Components to Class Type and Record Type, you find which combination of class type and
record type has been assigned to which interface components.

9
 1.1.1.2 Maintain Revenue Accounting Item class

Jira/Plan Reference Maintain Revenue Accounting Item class

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item  Maintain Revenue Accounting item classes

Transport Request

In this transaction, you define revenue accounting item classes and their technical attributes. For each
Revenue Accounting Item Class it is required to define:
 The interface that you use to transfer revenue accounting item information to the system
 The data store to be used for the revenue accounting items

Input: Following standard RAI classes are used and activated.

RevAccItems Class Type Name

CA01 Order Item Order Item
CA02 Fullfillment Item Fullfillment Item
CA93 Invoice Item Invoice Items

On Activation the config screen will appear as under.

Result:

10
RAI Classes

Order Items

Order items require following mandatory interface components:

 Basic Fields for Conditions 
 Basic Fields for Order Items ( Conditions) 
 Basic Fields for Main Items 
 Basic Fields for Order Items (Main Items) 
 CA Basic Fields for Main Items 
 CA Basic Fields for Order Items (Main Items) 

Fulfillment Items
Fulfillment items require following mandatory interface components:
 Basic Fields for Conditions
 Basic Fields for Main Items 
 Basic Fields for Fulfillment Items ( Main Items) 
 CA Basic Fields for Main Items 

11
Invoice Items

Invoice items require following mandatory interface components:

 Basic Fields for Conditions 
 Basic Fields for Main Items 
 Basic Fields for Invoice Items ( Main Items) 
 CA Basic Fields for Main Items 

Adding Customer Fields to a RAI Class

Customer fields can be added to the RAI structures. Customer fields are maintained per RAI class and
added to the RAI structure for status raw and, status Processable.

In XYZ, we do not have any custom fileds.

RAI Release status

This section explains how to respond to the release status in the above step.
Under certain conditions, the generation of runtime objects for RAIs might require the deletion of already
generated objects. This will lead to a loss of all already stored RAIs as the storage tables will be deleted and
regenerated. The system behaviour depends on the configuration status of the revenue accounting item
class:
 In Processing
the system completely deletes existing objects and generates them again. In this case, data is lost.
 Transportable
the system completely deletes existing objects and generates them again. In this case, data is lost.
 Released as Productive
If a class is generated for the first time with the status Released as Productive, the system deletes all
already existing objects and generates them again. In this case, data is lost.
For all subsequent generations for a class with the status Released as Productive, the system generates
only those objects that did not already exist or that have to be adjusted. All data that already existed
remains unaffected.

12
Order RAIs
Customer fields required in ARL

In XYZ, No custom field is created / required in the Order RAI

Fulfillment RAIs

In XYZ,No custom field is created / required in the Fulfillment RAI

Invoice RAIs

In XYZ,No custom field is created / required in the Invoice RAI

13
4.1.1.2 Generate Interfaces for Revenue Accounting Item classes

Jira/Plan Reference Generate Interfaces for Revenue Accounting Item classes

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing

Menu Path
Revenue Accounting Item  Generate Interfaces for Revenue Accounting item classes

Transport Request

Generation of Interface Components

In this transaction the interfaces for transferring revenue accounting items and the data store for revenue
accounting items are generated.Following activities need to be executed:

1. Check:
This function is used to check selected revenue accounting item classes.

2. Generate:
This function is used to generate the objects for the interface and the data store of a class.
Generation is possible only if the class has the necessary generation status.
During the generation process - under certain circumstances - the system can delete already
generated objects, which will result in a loss of data.

3. Delete:
If runtime objects have been generated and the configuration status is not productive, the runtime
objects for a certain RAI class can be deleted.

4. Display:
This function is used to display the runtime objects that have been generated.

5. History
This function display the history

6. Log
This function display the log of activities

7. Configuration
This function explains about Configuration

14
4.1.1.3 Assign Upload Rules to Revenue Accounting Item Classes

Jira/Plan Reference Assign Upload Rules to Revenue Accounting Item Classes

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item Assign Upload Rules to Revenue Accounting Item Classes

Transport Request

Per revenue accounting item class, the behavior during upload is defined as below:

1. Upload as Processable Item

Consistent items are created as Processable items.
Erroneous items are created as raw revenue accounting items.

2. Upload as Raw Item

Consistent items and erroneous items are created as raw revenue accounting items.

Revenue accounting items with invalid values in the key fields are not created at all.

4.1.1.4 Define Modifiable fields for RAI

Jira/Plan Reference Define Modifiable fields for RAI

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing

Menu Path
Revenue Accounting Item  Define Modifiable fields for Revenue Accounting Item Classes

Transport Request

We have adopted standard SAP business content.

In this activity it is specified which fields of revenue accounting items can be changed dependent on the
revenue accounting item class, the record type and the processing status.

This allows RAIs to be corrected manually in the Revenue Accounting Engine before processing.
The function is available for revenue accounting items with the following statuses:
 Raw (0)

15
  Processable (2)

In the standard system no fields are specified, which means that RAIs cannot be changed.

Note: No requirements are identified for this section

4.1.2 Revenue Accounting Item management

4.1.2.1 Define Source document item type

Jira/Plan Reference Define Source document item type

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item management  Define source document item type

Transport Request

Srcltm Type Class Type Item Type description

CAFI Fullfillment Item CA Fullfillment Item
CAII Invoice Item CA Invoice Item
CAOI Order Item CA Provider Contract item
CAOO Order Item CA One of Charge item
CAOX Order Item CA External Order Item

4.1.2.2 Define Logical system

Jira/Plan Reference Define Logical system

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item management  Define Logical system

16
Transport Request

In this activity, you define the logical systems from which revenue accounting retrieves source items.

4.1.2.3 Define sender components

Jira/Plan Reference Define Sender components

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item management  Define sender components

Transport Request

To constitute the link to the source item, from which a revenue accounting item has been retrieved, in this
activity, you maintain the sender components and assign them the respective logical systems and source
item types.

All sender components are defaulted from Standard Business Content

17
Assign source item types

4.1.2.4 Define Reference Types

Jira/Plan Reference Define Reference Types

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item management  Define Reference types

Transport Request

A reference type is used to bundle POBs. In the standard system, all the POBs created for one sales order
are bundled in one revenue accounting contract (reference type SDO). The following are the default
reference types delivered by the standard SAP RAR add-on:
• Business partner
• Customer
• Sales order

18
4.1.2.5 Define Condition types for Standalone selling prices and Right of Return

Jira/Plan Reference Define Condition types for Standard alone Selling Prices (SSP) and Right of Return

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path Revenue Accounting Item management  Define condition types for Standalone selling prices
and Right of Return

Transport Request

SSP can be transmitted to a revenue accounting contract in a couple of different ways. One of the more
efficient ways is to send an SSP using condition types of the sales order. Another method is to maintain and
pass the values directly from the BRF+ decision tables.
To send the SSP to the revenue accounting contract using the condition types assigned to the SD sales
order, it is mandatory that condition types for the SSP to be maintained in the SAP RAR configuration.

4.1.2.6 Assign BRF+ applications to revenue Accounting Item classes

Jira/Plan Reference Assign BRF+ Applications to Revenue Accounting item classes

SAP Transaction SPRO

Code

Menu Path SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

19
 Revenue Accounting Item management  Assign BRF+ Applications to Revenue Accounting
item classes

Transport Request

A BRFplus application relates to a particular function you want to enhance using business rules modeled
with BRFplus. You collect all BRFplus objects for this function in one BRFplus application.

You can assign a BRFplus application to a revenue accounting item class.

List of Applications provided as standard business content are as follows.

we recommend from copying standard template FARR_AP_SD_PROCESS_TEMPLATE to create XYZ

specific BRF application a s aprt of best practice.

Follow the sequence of steps given below to create BRF apploication from the standard business content.
STEP 1: Enter T-code BRF+ or BRFPLUS
STEP 2: SEARCH THE APPLICATION for FARR_AP_SD_PROCESS_TEMPLATE
STEP 3: Select the above apploication and right click to choose COPY from the context menu
STEP 4: Input the Name XXXXXXXXXX, storage type = customizing and choose development package.

4.1.2.7 Maintain Decision table id for Simplified BRF plus UI

Jira/Plan Reference Maintain Decision Table ID for Simplified BRF plus UI

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path Revenue Accounting Item management  Maintain Decision Table ID for Simplified BRF plus
UI

Transport Request

20
In In this Customizing activity, you define decision table ID for a decision table in a BRFplus application. Any
decision table that the user wants to maintain using the simplified UI for BRFplus decision tables must be
configured in this Customizing activity by assigning a unique decision table ID.

You also can maintain a list of related decision tables for each decision table ID. By maintaining the related
decision tables, you can navigate to these related decision tables on the Simplified BRFplus UI for Decision
Tables.

By default following decsion tables are available for BRIM

21
4.1.2.8 Define Job Distribution for Parallel processing

Jira/Plan Reference Define Job Distribution for Parallel Processing

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item management  Define Job Distribution for Parallel Processing

Transport Request

In this Customizing activity, you define the number of jobs running in parallel on the server or server group

App type Server Logon /server No of Tasks Jobs P.Wa

group

FARR_BZREC 1

FARR_CHECK 1

FARR_CLCA 1

FARR_CLLIA 1

FARR_CONTR 1

FARR_CPRP 1

FARR_MIGCT 1

FARR_MIGED 1

FARR_MIPST 1

FARR_POST 1

FARR_PRDL 1

FARR_RADI 1

FARR_RAGL 1

FARR_RAI0 1

FARR_RAI2I 1

FARR_RAI4T 1

FARR_RAI4T 1

FARR_RAICK 1

FARR_RARK 1

FARR_RECON 1

FARR_REPOS 1

FARR_ROUND 1

FARR_TRANS 1

GLE_ADB 1

GLE_ECS 1

22
4.1.2.9 Define Exemption reasons for Revenue Accounting Items

Jira/Plan Reference Define Exemption Reasons for Revenue Accounting Items

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item management  Define Reasons for Revenue Accounting Items

Transport Request

In this activity, you define the exemption reasons for revenue accounting items.
You can exempt revenue accounting items from processing. The system then moves these items to a
separate table which excludes them from ordinary processing.
You can specify whether the item can be restored or not.

4.1.2.10 Define Program Enhancements

Jira/Plan Reference Define Program Enhancements

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Inbound processing 

Menu Path
Revenue Accounting Item management  Define Program Enhancements

Transport Request

The SAP Revenue Accounting Engine provides 3 areas, which allow coding based enhancement of the SAP
standard solution.

BAdI: Creation of Raw Revenue Accounting Items

This Business Add-In (BAdI) is used to create revenue accounting items with status raw.

23
BAdI: Creation of Processable Revenue Accounting Items

This Business Add-In (BAdI) is used for transferring revenue accounting items from status raw to
processable.

BAdI: Determine Contract ID per Revenue Accounting Item

This Business Add-In (BAdI) is used for determining a contract ID for each revenue accounting item in order
to group all items that belong together.

Note: No BADIs or Program Enhancements are Identified

4.2 Revenue Accounting Contracts

4.2.1 Select Contract management for Contract categories

Jira/Plan Reference Select contract management for Contract categories

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting contract

Menu Path
 Configure Accounting principle specific settings

Transport Request

In this Customizing activity, you choose which contract categories you want to process with either Contract
Management (CM) or Contract Management Classic (CM Classic).
Set the indicator Create Contracts With CM Instead of CM Classic for all contract categories that use the
new contract management.
You can activate new contract management for new contracts based on a contract category in Customizing
under Revenue Accounting Contracts -> Define Contract Categories.
You cannot make any further changes to Customizing once a contract uses this contract category with the
respective version that was created.

Cocd Company Name Contr cat Contract Contact with CM instead

category of Classic CM
description

1720 US XYZ services 01 X – Active

2910 Canada XYZ services 01 X - Active

8210 Puerto XYZ services 01 X – Active

1810 India XYZ services 01 X – Active

4.2.2 Configuring Accounting Principle specicifc settings

Jira/Plan Reference Configuring Accounting principle Specific settings

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting Revenue Accounting Contracts-

Menu Path
Configure Accounting principle specific settings

Transport Request

24
In this Customizing activity, you can perform the following tasks for each specific accounting principle:
• Specify the way the contract balance is displayed
• You can specify how you would like to present contract balance, either contract liability and contract asset
or unbilled receivable and deferred revenue.

• Enable Contract Modification

• Enable Cost recognition
• Specify posting level of contract liability and contract asset (unbilled receivable and deferred revenue).
• Specify the local currency calculation method – Actual exchange rate Method / Fixed exchange rate
method.
Specify the accounting principle you created and mention the relevant settings as per your requirement

Accp Name Presentat. Lc Cont.Mod Cost.Recog Level for Default

of Calc.Method . PostingContract Contaact
Accp Lib and Ass Lia and
Ass cal
method
USGAAP Unbilled receivable / Fixed X Post Contract Calculate
Defered revenue Exchange level Per POB
rate method and Net
by
Contract

4.2.3 Assign Company code to Accounting Principle

Jira/Plan Reference Assign Company Codes to Accounting Principles

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Contracts  Assign Company codes to Accounting principle

Transport Request

In this Customizing activity, you define which company codes are supported under which accounting
principles. For each combination of company code and accounting principle, you specify a legacy data
transfer date and a migration status to indicate the date on which Revenue Accounting should be productive
for this combination.

If granular migration is used, packages can be assigned in addition and the migration settings can be
managed for individual packages as well.

Accp Company Nmae of Transf Stats Adoption Source Exc End App Comple
Code Company Date date Acc pr Acc D Ear Del
Pr usg Op

US XYZ
USGAAP 1720 services

Canada
USGAAP XYZ
2910 services

25
 Puerto
USGAAP XYZ
8210 services
India XYZ
USGAAP 1810 services

4.2.3.1 Exclude local currency calculation from Revenue Accounting

Jira/Plan Reference Exclude Local Currency Calculation from Revenue Accounting

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting   Revenue Accounting

Menu Path
Contracts  Exclude Local Currency Calculation from Revenue Accounting

Transport Request

Should it become necessry to exclude local currency calculation from being maintained in RAR, the same
can be flagged here.
Note: We haven’t identified any requirements to exclude local currencies

4.2.4 Open and Close Revenue Accounting Periods

Jira/Plan Reference Open and Close Revenue Accounting Periods

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting   Revenue Accounting

Menu Path
Contracts  Open and Close Revenue Accounting periods

Transport Request

In this activity, you configure whether an accounting period is open for revenue accounting related
transactions. The settings in this activity provide a revenue accounting perspective of period closing.

Comp Code AccP Fr.F Year Fr. Period Status

1720 USGAAP

2910 USGAAP

8210 USGAAP

1810 USGAAP

4.2.5 Define Number ranges

4.2.5.1 Define Number rages for Contracts

Jira/Plan Reference Define Number ranges for Contracts

26
SAP Transaction SPRO
Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Contracts  Number ranges – Define Number ranges for Contracts

Transport Request

In this Customizing activity, you can define the number ranges that are used for creating new revenue
accounting contracts. The number range defined here is assigned to Contract category in the subsequent
configuration settings.

No From No To No Ext

01 00000000000001 99999999999999

4.2.5.2 Define Number ranges for Performance Obligations

Jira/Plan Reference Define Number ranges for Performance Obligations

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Contracts  Number ranges – Define Number ranges for Performance obligations

Transport Request

In this Customizing activity, you can define the number ranges that are used for creating new performance
obligations. You can define only one number range for performance obligations and must use an ID of 01.
The system does not use number ranges other than 01.

Standard settings

When creating a performance obligation, if the system does not find number range 01, it automatically
creates a number range 01 that spans from 0000000000000001 to 9999999999999999. If you have defined
other number ranges that overlap the system default range, the system cannot create the default number
range and no new performance obligations can be created.

No From No To No Ext

01 0000000000000001 9999999999999999

27
4.2.5.3 Define Number ranges for Run Ids

Jira/Plan Reference Define Number ranges for run ids

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Contracts  Number ranges – Define Number ranges for Run ids

Transport Request

In this Customizing activity, you can define the number ranges that are used for creating new revenue
posting jobs (run IDs). You can define only one number range for run IDs and must use an ID of 01. The
system does not use number ranges other than 01. Run IDs are in the context of individual company codes.
Each run ID is unique in the scope of a company code.

Note: Run IDs are reference numbers that the system uses to track background jobs created for revenue
postings.

Standard settings

When creating a run ID, if the system does not find number range 01, it automatically creates a number
range 01 that spans from 00000001 to 99999999. If you have defined other number ranges that overlap the
system default range, the system cannot create the default number range and no new performance
obligations can be created.

No From No To No Ext

01 00000001 99999999

4.2.5.4 Define Contract Categories

Jira/Plan Reference Define Contract categories

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Contracts  Define Contract categories

Transport Request

In this Customizing activity, you can define contract categories and assign number ranges to them. Each
contract category is associated with a number range that is used for creating new contracts of that category.

Contr. Cat Description No. Range

01 01

28
4.2.6 Define Performance Obligation types

Jira/Plan Reference Define Performance Obligation Type

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Contracts  Define Performance obligation type

Transport Request

In this Customizing activity, you can define performance obligation types and their associated attributes.
Performance obligations may follow certain patterns. Therefore, you can define a performance obligation
type for performance obligations that always have certain attribute values. A performance obligation type is
like a template that includes all predefined attribute values to be applied on similar performance obligations.
When a user edits a performance obligation, the user can apply a performance obligation type for the system
to derive certain attribute values automatically.

Pob Pob No Ful Even Start Duratio Deferra Exclude Residua SSP SSP SSP Currency
Type name Cost type t date n l from l tolarnce Tol
Recog Type type Method Alloc %

Note: This Information is pending with XYZ and same is listed in the parking lot.

Below are the event types identified through workshop and are relevant for XYZ business process.
• Customer Invoice
• Consumption
• Intercompany Billing Process
• Manual Fulfillment
• Purchase Invoice - Drop Shipping
• Contract Release Order - Call Off

4.2.7 Condition Types

4.2.7.1 Define Reserved Condition type

Jira/Plan Reference Define Reserved Condition Type

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Contracts  Condition type  Define Reserved Condition Types

Transport Request

In this Customizing activity, you can define condition types that are reserved for Revenue Accounting.

29
Allocation Effect
This condition type carries differentials that result from price allocation.
When allocating transaction prices for a contract, the system aggregates all pricing conditions and then
allocates the total amount among the performance obligations in the contract. The system then represents
the allocated prices on a differential basis. Without changing the original pricing conditions, the system adds
a special condition type that carries the differential resulting from the allocation.
Right-of-Return Revenue Adjustment
This condition type carries the amount of revenue that must be deferred in order to be recognized due to a
right of return held by the customer.
Right-of-Return Cost Adjustment
This condition type carries the amount of cost that must be deferred to be recognized due to a right of return
held by the customer.
Early Termination Expense
This condition type carries the balance amount of all related assets and liabilities such as receivables,
contract assets/contract liabilities or unbilled receivables/deferred revenue if a contract was terminated early.

4.2.8 Define Fullfillment types

Jira/Plan Reference Define Fulfillment Event Types

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Contracts  Define fulfilment even type

Transport Request

30
4.2.9 Change Message control

Jira/Plan Reference Define Fulfillment Event Types

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Contracts  Define fulfilment even type

Transport Request

This will be used as and when necessary to lend clarity to the underlying processes.

4.2.10 Assign BRF + Applications to Revenue Accounting Process

Jira/Plan Reference Assign BRF+ Applications to Revenue Accounting Process

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Contracts  Condition type  Assign BRF+ Applications to Revenue Accounting process

Transport Request

In this Customizing activity, you can assign BRF plus (BRF+) applications to specific processes that require
rule-based determination for Revenue Accounting.

For XYZ, we recommend from copying standard template FARR_AP_SD_PROCESS_TEMPLATE to create

XYZ specific BRF application.

The required functions of the above mentioned BRF application are maintained separately under the
configuration node under Revenue accounting Posting.

31
4.3 Integration with cost object controlling.

4.3.1 Assign RA Version and Currency Type to Company Code and Acct. Principle

Results analysis can calculate different percentages of completion for the currency type and results analysis
version.

Specify which percentage of completion and currency type that you want to assign to the company code and
accounting principle.

Maintain entries for view V_TKKA_RR_AC using transaction SM30.

COAr Cocd RA Version AccP CC

4.3.2 Specify RA Keys and RA Versions that will Integrate with Revenue Acct.

Specify the results analysis keys and results analysis versions that will integrate with revenue accounting.

Maintain entries for view V_TKKA_RR_ME using transaction SM30.

COAr Cocd RA Version RA Key RA/RR

Integration
Method

Note: To be decided in build phase

4.4 Revenue Accounting Postings

4.4.1 Define Posting specification for General ledger transfer

Jira/Plan Reference Define Posting Specifications for General Ledger Transfer

SAP Transaction SPRO

Code

32
 SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting
Menu Path
Postings  Define Posting Specifications for General Ledger Transfer

Transport Request

In this activity, you define certain specifications (posting keys, document type and transfer account as zero
balance account when number of items exceeds the limit of 999). In addition, for that transfer account, a
specific account assignment data can be configured, such as segment, business area, and profit center.

CodC Credit PK Debit PK DocType Gl Account Profit Business Functional

Center Area Area
1720 50 40 SA
2910 50 40 SA
8210 50 40 SA
1810 50 40 SA

4.4.2 Configure Account Determination for Specific Transactions

Jira/Plan Reference Configure Account Determination for specific Transactions

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Postings  Configure Account Determination for Specific Transactions.

Transport Request

This configuration allows you to define rules that the system uses during Account Determination.

The parameterization of this config node is done in Web Dynpro screen, where following structures for
account determination have to be maintained based on a list of input attributes and leading to an output
account. Account determination is maintained with the help of Simplified BRF+ application.

Please Refer to BRF section

4.4.3 Configure parallel processing for Revenue Posting

When run a revenue posting job that involves a large number of revenue accounting contracts, the system
splits the job into several parallel tasks for better performance. In this Customizing activity, you can configure
the number of tasks.

Jira/Plan Reference Configure Parallel Processing for Revenue Posting

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Postings  Configure Parallel Processing for Revenue Posting

Transport Request

App type Server Logon /server No of Tasks Jobs P.Wa

group

33
 FARR_BZREC 1

FARR_CHECK 1

FARR_CLCA 1

FARR_CLLIA 1

FARR_CONTR 1

FARR_CPRP 1

FARR_MIGCT 1

FARR_MIGED 1

FARR_MIPST 1

FARR_POST 1

FARR_PRDL 1

FARR_RADI 1

FARR_RAGL 1

FARR_RAI0 1

FARR_RAI2I 1

FARR_RAI4T 1

FARR_RAI4T 1

FARR_RAICK 1

FARR_RARK 1

FARR_RECON 1

FARR_REPOS 1

FARR_ROUND 1

FARR_TRANS 1

GLE_ADB 1

GLE_ECS 1

4.4.4 Define reasons for shifting contracts to next period

Jira/Plan Reference Define Reasons for Shifting Contracts to Next Period

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Postings  Define Reasons for Shifting Contracts to Next Periods

Transport Request

In this Customizing activity, you can define possible reasons for shifting revenue accounting periods. When
the accountant runs revenue postings at the end of an accounting period, some issues may prevent the
postings being successfully transferred to the corresponding ledgers. If the accountant cannot solve the
issues, they can choose to shift unfinished postings into the next accounting period. When performing such
shifting, the accountant must specify a reason that explains why they have to shift the postings.

34
The Customizing activity maintains a list of predefined reasons, each identified with a reason code and
labeled with a description. When the accountant specifies the shifting reason, they can choose one from this
predefined list.

4.4.5 Switch on Posting Optimization

Jira/Plan Reference Switching on Posting Optimization

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue Accounting

Menu Path
Postings  Switching on Posting Optimization

Transport Request

Note: No Scenario Identified to use Posting Optimization

4.4.6 Assigning Additional Revenue Posting Aggregation Dimensions

Jira/Plan Reference Assigning Additional Revenue Posting Aggregation Dimensions

SAP Transaction SPRO
Code
SPRO  IMG  Financial Accounting  Revenue Accounting  Revenue
Menu Path Accounting Postings  Assigning Additional Revenue Posting Aggregation
Dimensions
Transport Request

In this activity, you can select fields from structure INCL_EEW_FARR_REP. These fields are revenue
posting aggregation dimensions.

You can generate additional data records by adding fields as aggregation dimensions. Each new field that
you add increases the data volume. This has a negative effect on performance and takes up more memory.
For this reason, you should not include any more account assignments than you require. This is especially
true for those fields that can take a large number of values, such as internal order, customer order
(Bookings), or WBS element

5 BRF PLUS CONFIGURATION AND SET UP

5.1 Maintain RAI processing Decision table

Execute transaction code Simplified UI for BRF+ Decision Table
Select the desired decision table from the list that will appear on the Dyn Pro screen. You will see following
decision tables.

35
 Decision table used for customizing BRF Application Decision table name

FARR_AP_CA_PROCESS_TEMPLAT
CONTRACT_HEADER E DT_PROCESS_HEADER
FARR_AP_CA_PROCESS_TEMPLAT
ESTIMATED_QUANTITIES E DT_RAI_EST_QUAN_DET
FARR_AP_CA_PROCESS_TEMPLAT
PROCESS_ADDITIONAL_POB E DT_PROCESS_POB_ADD
FARR_AP_CA_PROCESS_TEMPLAT
PROCESS_BOM E DT_PROCESS_BOM
FARR_AP_CA_PROCESS_TEMPLAT
PROCESS_COMPOUND E DT_PROCESS_COMPOUND
FARR_AP_CA_PROCESS_TEMPLAT
PROCESS_DEFERRAL E DT_PROCESS_DEFERRAL
FARR_AP_CA_PROCESS_TEMPLAT
PROCESS_POB E DT_PROCESS_POB
FARR_AP_CA_PROCESS_TEMPLAT
PROCESS_SSP E DT_PROCESS_SSP
FARR_AP_CA_PROCESS_TEMPLAT
RECEIVABLE_ACCOUNT E DT_RAI_REC_ACCT_DET
FARR_AP_CA_PROCESS_TEMPLAT
REVENUE_ACCOUNTS E DT_RAI_REV_ACCT_DET

In the following section we will explain the procedure to maintain the Parameter Values for XYZ relevant
decision tables.

5.1.1 Process header

This decision table is required to determine Contract Category for a Company code and the resultant number
range assigned to Contract Category in the IMG.

Ensure that you are in Edit Mode to enter the required values.

Company code Contract Category Description

1720 01
2910 01
8210 01
1810 01

5.1.2 Process POB

This decision table is required to determine following POB attributes

 POB Type
 Fulfillment Type
 Deferral Method
 Start Date Type

Company Sales Material Performance POB Fulfillmen Event Deferral Duratio Start End
code org Obligation Type t type type Method n date date
Name

36
Note: This Information is pending with XYZ and same is listed in the parking lot.

5.1.3 Process SSP

It is assumed that SSPs are maintained at sales order level.

5.2 Account Determination

5.2.1 Recognized Revenue

Company code Reference Account Derived Account

5.2.2 Decision table to determine Receivable Adjustment Account

This decision table is maintained to assign Reference account maintained in this table.

Company code Reference Account Derived Account

5.2.3 Decision table to determine Gl Account for Revenue Adjustment for Allocation effect

Accn Prncple Company code Reference Account Reference Account Derived Account

5.2.4 Decision table to derive Gl Accounts for unbilled receivable

Accn Prncple Company code Reference Account Derived Account

37
5.2.5 Decision table to derive Gl accounts for Deferred Revenue

Accn Prncple Company code Reference Account Derived Account

5.2.6 Decision table to derive Gl accounts for Deferred Cost

Accn Prncple Company code Reference Account Derived Account

5.2.7 Decision table to derive Gl accounts for Recognized cost

Accn Prncple Company code Reference Account Derived Account

38
6 INTEGRATION WITH BRIM

6.1 Activate Integration with Revenue Accounting

Jira/Plan Reference Activate Integration with Revenue Accounting

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Contract Accounts Receivable and payable 

Menu Path
Integration  Revenue Accounting  Activate Integration with Revenue Accounting

Transport Request

In this activity, you activate the integration with Revenue Accounting. You also specify the following:

 Destination
You enter the RFC destination of the system in which Revenue Accounting is running. The system
uses this RFC destination when it:

o Transfers revenue accounting items to Revenue Accounting

o Transfers data to Revenue Accounting that is needed there for reconciling revenue
accounting items

Make sure that in the system where Revenue Accounting is running, an RFC destination is
configured to the system where Contract Accounts Receivable and Payable is running.
The data exchange is synchronous in both directions. Therefore, in the configuration of RFC
connections (transaction SM59) on the Special Options tab, enter Classic with RFC as the
transmission protocol.

 Condition Type of Standalone Selling Price

Here you enter the condition type that the system is to use as a default for conditions of order items
for the standalone selling price.

 Condition Type of Transaction Price

Here you enter the condition type that the system is to use as a default for conditions of order items
for the transaction price.

Service Type for Recurring Charges

Here you enter the service type that the system is to use as a default in order items for recurring charges.

39
6.2 Define RFC destination of the Receiving system

Jira/Plan Reference Define RFC destination of the Receiving system.

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Contract Accounts Receivable and payable 

Menu Path
Integration  Revenue Accounting  Define RFC destination of the Receiving system

Transport Request

In this activity, you define the logical destination of the receiver system. In your system landscape, the
operational system (sender system) and the system for revenue accounting (receiver system) are installed in
various clients. The sender system must recognize the logical destination of the receiver system. Here you
can define settings to transfer the logical destination of the receiver systems automatically to the new
maintenance view V_TFK_RA_RFCDEST.

Note: The entry in the new related database table TFK_RA_RFCDEST has not been copied with a client
copy and a new entry has to be entered in the copy. The field RFCDEST in the table TFK_RA_SETTING is
now obsolete.

6.3 Activate Provider contract items for Revenue Accounting Items

Jira/Plan Reference Activate Provider Contract items for Revenue Accounting items

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Contract Accounts Receivable and payable 

Menu Path Integration  Revenue Accounting  Activate Provider contract items for Revenue Accounting
items

Transport Request

We define the derivation of the Relevant for Revenue Accounting indicator of the contract item.

Use

The derivation takes place based on the following parameters:

 Sales organization

 Distribution channel

 Division

40
  Sales area attribute 1

 Sales area attribute 2

In event 0558, you can override the value that was determined using the company code.

6.4 Define service Types

Jira/Plan Reference Define service Types

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Contract Accounts Receivable and payable 

Menu Path
Integration  Revenue Accounting  Define service types

Transport Request

In this IMG activity, you define service types.

By setting the following indicators, you can also specify for each service type, whether the system creates
items for Revenue Accounting:

 Order Item
If you set this indicator, the system creates an order item for the service type during provider contract
maintenance.

 One-Off Charge
If you set this indicator, for billable items with this service type, the system generates order items for
Revenue Accounting.

 Fulfilment Item
If you set this indicator, for billable items with this service type, the system generates fulfilment items
for Revenue Accounting.

 Invoice Item
If you set this indicator, for billable items with this service type, the system generates invoice items
for Revenue Accounting when invoicing takes place.

Service type Service Type text Order Item One time Fullfill.Item Invoice Item
change
ZVLC Volumetric business X X X

41
6.5 Assign service ids to service type

Jira/Plan Reference Assign service ids to service type

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Contract Accounts Receivable and payable 

Menu Path
Integration  Revenue Accounting  Assign service ids to service type

Transport Request

In this activity, you make settings for deriving the service types of a provider contract.

During the transfer of provider contract data in the Common Object Layer (COL), you can directly transfer a
list of service types for a provider contract item. This list of service types does not exist in this form in SAP
CRM. Instead, service IDs are used there.

Service Id Service Type Service Type text

ZVLC ZVLC Volumetric business

6.6 Define Reference Types

Jira/Plan Reference Define Reference Types

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Contract Accounts Receivable and payable 

Menu Path
Integration  Revenue Accounting  Define Reference type

Transport Request

In this activity, you define the reference types for Revenue Accounting.

6.7 Define Source item Types

Jira/Plan Reference Define Source item types

SAP Transaction SPRO

Code

42
 SPRO  IMG  Financial Accounting  Contract Accounts Receivable and payable 
Menu Path
Integration  Revenue Accounting  Define Source item type

Transport Request

In this activity, you define the source item types for Revenue Accounting.

For the integration of Contract Accounts Receivable and Payable with Revenue Accounting, SAP provides
the following values:

o CAOI: Order item (contract item)

o CAOO: Order item (one-off charge)
o CAAL: Order item (allowance)
o CAOX: Order item (external)
o CAFI: Fulfilment item
o CAII: Invoice item

SrcItm Type Description RAI Type

6.8 Define Number ranges for Revenue Accounting Item ids

Jira/Plan Reference Define Number ranges for Revenue Accounting items

SAP Transaction SPRO

Code

SPRO  IMG  Financial Accounting  Contract Accounts Receivable and payable 

Menu Path
Integration  Revenue Accounting  Define Number Ranges for Revenue Accounting item ids

Transport Request

43
In this activity, you define number ranges for the automatic assignment of revenue accounting item IDs. The
numbers from these number ranges are not used directly as revenue accounting item IDs. Instead they only
form part of an ID that is created by a program.

The ID consists of the following parts that follow one another:

 The system date on which the ID was determined, in format YYDDD, where DDD stands for the day
of the year.
 A number from one of the number ranges you define in this activity.
 A three-digit sequence number that is assigned internally

No From No To Number Ext

01 0000000001 9999999999

6.9 Define Price Condition used to Determine Standard alone Selling Price

Jira/Plan Reference Define Price Condition Used to Determine Standalone Selling Price (SSP)

SAP Transaction SPRO

Code

SPRO  IMG  Service  Transactions  Settings for Subscription Transactions 

Menu Path Integration  Integration of Revenue Accounting and Reporting  Define Price Condition
Used to Determine Standalone Selling Price (SSP)

Transport Request

In this Customizing activity, define which price condition is used to determine the Standalone Selling Price
(SSP). The SSP is used in the revenue accounting and reporting area.

Condition Type Name

PSMB Monthly Subscr.. Fee

44
6.10 GL Account determination in BRIM

FICA GL Determination Procedure used as benchmark to derive RAR GL

6.10.1 Maintain Main Transactions and sub transaction

Maintain the required Main Transactions and sub transactions to be used for account determination, as shown in
the following table:

Sub process Billable item Debit Main Debit Sub Credit Main Credit Sub Service
type transaction transactions transactions transaction type
ZVLC

6.11 Rationale

Cluster/Higher Values
(navigation along nested Field Name Field Value Rationale
configuration tables)

45
7 PREREQUISITES AND DEPENDENCIES

8 UNIT TEST TRACKER

Date of last
Status
Jira/Plan modification (do not
Configuration Activity Description Owner (Pending
Reference repeat Jira/Plan
/Complete)
references)

9 SAP CORRECTION NOTES

Did the Note

Note Nr Note Description Short Description of the Issue Resolve the
Issue?

46