Oracle®

Financial Services Cloud Configurations

Guide

G27259-01
March 2025
Oracle Financial Services Cloud Configurations Guide,

G27259-01

Copyright © 2021, 2025, Oracle and/or its affiliates.

This software and related documentation are provided under a license agreement containing restrictions on use and
disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or
allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit,
perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation
of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find
any errors, please report them to us in writing.

If this is software, software documentation, data (as defined in the Federal Acquisition Regulation), or related
documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then
the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any
programs embedded, installed, or activated on delivered hardware, and modifications of such programs) and Oracle
computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial
computer software," "commercial computer software documentation," or "limited rights data" pursuant to the applicable
Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction,
duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle
programs (including any operating system, integrated software, any programs embedded, installed, or activated on
delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle
data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms
governing the U.S. Government's use of Oracle cloud services are defined by the applicable contract for such services.
No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not
developed or intended for use in any inherently dangerous applications, including applications that may create a risk of
personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all
appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its
affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle®, Java, MySQL, and NetSuite are registered trademarks of Oracle and/or its affiliates. Other names may be
trademarks of their respective owners.

Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used
under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo
are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open
Group.

This software or hardware and documentation may provide access to or information about content, products, and
services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all
warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an
applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss,
costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth
in an applicable agreement between you and Oracle.
Contents

1 Getting Started with Oracle Financial Services Cloud

Default Configurations 1-1

2 Understanding Configuration Lifecycle

Creating Config ID 2-2
Using an Existing Config ID 2-3
Deleting Config ID 2-3
Closing Config ID 2-4

3 Understanding Configuration Movement

Initiating Configuration Movement from Non-Production to Pre-Production 3-2
Initiating Configuration Movement from Pre-Production to Production 3-3

4 Configurations
Understanding ID Generation 4-1
Configuring ID Generation 4-2
Configuring Company ID Generation 4-5
Configuring User Group ID Generation 4-6
Associating Company ID Generation Configuration with Tenant 4-7
Associating User Group ID Generation Configuration with Tenant 4-8
Understanding Companies 4-8
Creating Operations Company 4-10
Creating Marketing Company 4-11
Creating Operations Company Hierarchy 4-12
Understanding and Configuring Operations Company Supplier Service Instance 4-13
Creating and Editing Operations Company Supplier Service Instance 4-15
Deleting Operations Company Supplier Service Instance 4-17
Editing Tenant Details 4-17

iii
5 Operations
Credential Maintenance of Operations Company Supplier Service 5-1

6 Understanding Security Management

Secure Configurations 6-1
Post Initial Configuration 6-3

7 Understanding User Management

Creating Employee 7-1
Creating Operator 7-2
Creating Employee as Operator 7-3
Setting Up Employee as Operator 7-4
Configuring Login for an Operator 7-5

8 Understanding Entitlements Management

Configuring Transaction 8-2
List of Pre-configured Transactions 8-3
Creating Transaction Group 8-8
Creating Transaction Group Hierarchy 8-9
Creating User Group 8-10
Adding Users to User Group 8-12
Creating User Group Hierarchy 8-12
Associating Transaction Group with User Group 8-13

9 Known Issues in Oracle Financial Services Cloud

10 Financial Services Cloud Support

iv
1
Getting Started with Oracle Financial Services
Cloud
You need to perform a set of configurations immediately after the provisioning of a customer
environment. These activities are performed by the default user OracleFSCloudAdmin, and
are done only on the Non-Production tenancy. Once these initial set of configurations are
created and tested, they are then moved to the subsequent tenancies (Pre-Production and
Production) using Configuration Movement process.
To understand the initial set of configurations required for setting up Oracle Financial Services
Cloud platform, see Getting Started with Oracle Financial Services Cloud. You need to perform
these configurations before setting up your cloud service-specific configurations.
Related Topics
• Basic Configurations
• Default Configurations

Default Configurations
Some of the basic configurations in Oracle Financial Services Cloud come pre-configured with
default values. These default configurations enable you to log in and perform the basic
platform setup, like creating other users, defining their entitlements, etc.
The available basic configurations and their default values are listed below:

Table 1-1 Default Configuration Details

Configuration Default Value Reference

Tenancy • Non-Production
• Pre-Production
• Production
Operator OracleFSCloudAdmin
Operations Company OracleOperationsCompany To create a new Operations
Company, follow instructions in
Creating Operations Company.
Marketing Company OracleMarketingCompany To create a new Marketing
Company, follow instructions in
Creating Marketing Company.
User Group OracleUserGroup To create a new User Group,
follow instructions in Creating
User Group.
Transaction Group OracleTransactionGroup To create a new Transaction
Group, follow instructions in
Creating Transaction Group.
Transaction Configurations List of Preconfigured To configure a Transaction, follow
Transactions instructions in Configuring
Transaction

1-1
 Chapter 1
Default Configurations

Table 1-1 (Cont.) Default Configuration Details

Configuration Default Value Reference

Channel OracleChannel
UI Experience Not available currently

Note:
Channel and UI Experience pages are not available currently; they will be
introduced in subsequent releases.

Related Topics
• Understanding Tenancies
• User Management
• Managing Companies
• Entitlements Management

1-2
2
Understanding Configuration Lifecycle
Most of the configuration changes in Oracle Financial Services Cloud require testing before
making them available for customers to start using. To facilitate this, all configurations in Oracle
Financial Services Cloud are first created in the Non-Production tenancy and are then moved
to Pre-Production tenancy for isolation testing, from where they are finally moved to
Production tenancy where the users can start using the configurations. Movement of
configurations from one tenancy to other is using the Configuration Movement process.
All configurations in Oracle Financial Services Cloud are configured under a Config ID in Non-
Production. The Config ID tracks the configuration lifecycle of an entity and facilitates the
movement of configurations across the three tenancies. Thus, it is imperative that all
configurations pertaining to an entity are bundled under the same Config ID, thereby
simplifying the Configuration Movement process.

Figure 2-1 Lifecycle of Configurations in Oracle Financial Services Cloud

Stages in Configuration Lifecycle

The list below outlines the various stages in a Configuration lifecycle. For each stage of the
lifecycle, you would need appropriate entitlements to perform the tasks. Refer Entitlements
Management section to know more about configuring entitlements.
1. Configuration Lifecycle starts with the creation of a Config ID in Non-Production tenancy.
The Config ID essentially wraps your configurations together, making it convenient to
move across tenancies.
2. You can go ahead and start creating configurations in Non-Production tenancy after
creating a Config ID (or select an already existing Config ID).
3. After creating and testing your configurations, close the Config ID in Non-Production,
thereby freezing the configuration changes.
4. Initiate the movement of configuration from Non-Production to Pre-Production using
Configuration Movement process, initiated from the target tenancy; in this case, Pre-
Production.

2-1
 Chapter 2
Creating Config ID

5. Continue testing the configurations in Pre-Production, but note that you cannot make any
configuration changes at this point.
6. When you are satisfied with your isolation testing in Pre-Production, initiate the
Configuration Movement from Pre-Production to Production.
7. After the Configuration Movement process completes successfully, your configurations
are available at the Production tenancy.
Related Topics
• Creating Config ID
• Using an Existing Config ID
• Closing Config ID
• Initiating Configuration Movement from Non-Production to Pre-Production
• Initiating Configuration Movement from Pre-Production to Production

Creating Config ID
Configurations in Oracle Financial Services Cloud are made in the Non-production tenancy,
and are done against a Config ID and then moved to the Pre-Production tenancy. While
creating or making any configuration changes, you need to either create a Config ID or use an
existing Config ID (in Open status) to save your configurations.

Note:
You can create Config ID only in Non-Production tenancy, which is identified as the
tenancy for maintaining all Configurable Items for a customer.

To create a Config ID, follow this procedure:

1. Log in to Oracle Financial Services Cloud application using OracleFSCloudAdmin
account. If you are using another account, ensure that you have the appropriate
entitlements (Crt Cf Create Configurations).
2. Select Config ID on the top-right corner. By default, the page displays Config ID as None.
3. In the pop-up window, select Create New Config ID and select Continue. This opens the
Add Identification page.
4. In the Basic Information section, enter the following details:
a. Name: Enter the name of the Config ID.
b. Long Name: Enter the full name of the Config ID.
c. Description: (Optional) Enter a meaningful description of the Config ID.
5. Select Continue. A success message with the newly created Config ID appears.
6. Select Proceed. This activates the newly created Config ID for the current login session.
The Home page displays Active in green against Config ID.
When you create a new Config ID, it is in Open status and remains Open until you manually
change the status to Closed from Config ID Manager.
When you are ready to migrate the configurations bundled in a Config ID to the Pre-
Production tenancy, change the status of Config ID to Closed. This queues up the Config ID
for Configuration Movement.

2-2
 Chapter 2
Using an Existing Config ID

Related Topics
• Configuration ID Management
• Understanding Configuration Movement

Using an Existing Config ID

To use an existing Config ID for a set of configurations, follow this procedure:
1. Log in to Oracle Financial Services Cloud application using OracleFSCloudAdmin
account. If you are using another account, ensure that you have the appropriate
entitlements (Crt Cf Create Configurations).
2. Select Config ID on the top-right corner. By default, the page displays Config ID as None.
3. In the pop-up window, select Use an Existing Config ID and select Continue. The Config
ID Quick Access page opens and lists all Configuration IDs that are currently in Open
status.
4. From the search results, select the Config ID you want to use and select Continue. The
page displays the selected Config ID and its description.
5. Select Done. A success message including the selected Config ID appears.
6. Select Proceed.
The Home page displays Active in green against Config ID.

Deleting Config ID
You can delete a Config ID only if you have not done any configurations using it. After you
have used a Config ID for making any configuration changes, you cannot delete it. That is,
once a Config ID is Active and you have done configuration changes in the application, you
cannot delete it.

Note:
You cannot delete a Config ID that is currently under use. To do that, switch to
another Config ID and then delete it.

To delete a Config ID, follow this procedure:

1. From Menu, select Configuration, Configuration Control, and then Config ID Manager.
2. Select Action against the Config ID that you want to delete and select Delete. A
confirmation message appears asking if you are sure about deleting the Config ID and
warns that the action cannot be undone.
3. Select Yes. The page briefly displays a message saying the Config ID has been deleted.
Related Topics
• Understanding Configuration Lifecycle

2-3
 Chapter 2
Closing Config ID

Closing Config ID
After you finish a set of configurations for a customer in Non-production tenancy and is ready
for further testing in Pre-production tenancy, close the Config ID so that all the configurations
done using the Config ID are moved to the Pre-production tenancy.
Closing a Config ID bundles all the configuration changes that you have made using that
Config ID, and the closed Config ID is available in the queue for Configuration Movement.

Note:
Configurations are moved from Non-production tenancy to Pre-production tenancy in
the order in which the corresponding Config IDs are closed.

Before trying to close a Config ID, consider the following conditions:

• Close the Config ID only if it is used to perform any configurations. If you have not done
any configurations using a Config ID, you cannot close it. In this case, delete the Config ID
instead.
• If any of the configurations done using a Config ID is in In Progress status, you will not be
able to close the corresponding Config ID. Once the configuration is promoted from In
Progress to Active status, you can close the corresponding Config ID.
• Do not attempt to close the Config ID while it is Active for the current login session.
Switch to another Config ID and close it.
To close a Config ID, perform the following procedure:
1. From Menu, select Configuration, Configuration Control, and then Config ID Manager.
The page lists all Config IDs that are Open and those that are Closed, but not yet moved
to other tenancies.
2. Select Action against the Config ID you want to close and select Close. A confirmation
message appears.

Note:
You cannot re-open a closed Config ID. Proceed with Close action only if you are
sure that the configurations are ready for movement.

3. Select Yes in the confirmation message. The page briefly displays a message informing
the Config ID has been closed.
Once a Config ID is closed, the configuration changes within it are queued up for movement to
Pre-Production tenancy, and the Config ID cannot be further used to save any configurations.

2-4
3
Understanding Configuration Movement
Configuration Movement is the process through which one or more Config ID, and thereby all
the underlying configuration changes that are being tracked under the Config IDs, are moved
or copied from one customer tenancy to another tenancy. For example, from Non-Production to
Pre-Production and from Pre-Production to Production.

Customer Tenancies
On Oracle Financial Services Cloud, every customer is provisioned with three tenancies: Non-
Production, Pre-Production, and Production. The Non-Production tenancy is where you first
create all configurations as per your business needs. These configurations are then moved or
copied to the Pre-Production tenancy for business users to test and verify. This is an iterative
process until the business users verify the various configurations and thereby provide approval
to make the same configurations available to the Production environment.

Bundling and Moving Configuration Changes

Oracle Financial Services Cloud tracks all the configuration changes done in the Non-
Production environment through a Config ID. OFSC prompts you to select a Config ID before
creating, editing, or deleting any configurations in the Non-Production tenancy. One Config ID
can track multiple configuration changes and bundles these configuration changes in the Non-
Production environment.
Once the configuration changes are completed for a given Config ID, close the Config ID so
that it is not used for tracking any further configuration changes. Closing the Config ID makes
the configuration updates available for movement (copy) to other customer tenancies on the
Oracle Financial Services Cloud.

Configuration Movement Process

Configuration Movement is the process through which a Config ID, and thereby all the
underlying configuration changes that are being tracked under the Config ID, are moved from
one customer tenancy to another tenancy. For example, from Non-Production to Pre-
Production and then from Pre-Production to Production.
The Configuration Movement process is always initiated from the target tenancy. Therefore, to
move from the Non-Production tenancy to the Pre-Production tenancy, you need to initiate the
movement process from the Pre-Production tenancy. Similarly, for configuration in the Pre-
Production tenancy to be moved/copied to the Production tenancy, you need to initiate the
movement from the Production tenancy.

Note:
The direction of configuration data flow, that is from Non-Production to Pre-
Production, and then from Pre-Production to Production, is fixed and pre-configured
by Oracle Financial Services Cloud tenancy automated provisioning process itself.
You cannot reconfigure or change the direction of configuration data flow.

3-1
 Chapter 3
Initiating Configuration Movement from Non-Production to Pre-Production

Every time a Configuration Movement is initiated, the configuration tracking system identifies a
list of all the closed Config IDs that are available in the source tenancy since the last
successful movement process completed, and then moves them one after the other to the
target tenancy. Thus the Configuration Movement process works in an 'All or None’ mode. It
either results in moving the configurations for all the Config IDs identified for movement, or
does not move any of it (that is, in case of any unforeseen errors).

Initiating Configuration Movement from Non-Production to Pre-

Production
Before you initiate the Configuration Movement process from Pre-Production, ensure the
following steps are performed in Non-Production:
• Create and use a Config ID while performing configuration changes in the Non-Production
tenancy.
• After finishing the configuration changes, close the Config ID, so that it is available for
Configuration Movement.
• Generate Security Token for accessing Non-Production.

Note:
You cannot close a Config ID until you make configuration changes using it.

Generating Security Token

To initiate Configuration Movement from Non-Production to Pre-Production, you need to first
generate a security token that enables access to the Non-Production tenancy. Execute the
following Curl script to generate a valid token:

curl --location --request POST "https://

ENVIRONMENTNAME.fscloud.oraclecloud.com/non-prod/api/oauth2/v1/access" --
header "Content-Type: application/json" --data-raw
"{\"User\":\"OracleFSCloudAdmin\",\"Password\":\"ADMINPASSWORD\"}"

In the above script, replace ENVIRONMENTNAME with the customer environment name and
ADMINPASSWORD with the password for OracleFSCloudAdmin user.

Initiating Configuration Movement from Non-Production to Pre-Production

To move configuration changes from Non-Production to Pre-Production, initiate the
Configuration Movement process from the Pre-Production tenancy.
1. Log in to the Pre-Production tenancy as an administrator user.
2. From Menu, select Configuration, Configuration Control, and then Movement. The
Movement page shows the result of the previous Configuration Movement process that
was initiated from the Pre-Production tenancy, if any.
3. Select Initiate Movement. The Config ID Movement page opens up.
4. In the Config ID Movement page, enter the Security Token generated by running the curl
script in Authentication Code, and select Continue.
The page lists all closed Config IDs in the Non-Production tenancy that are ready for
movement to the Pre-Production tenancy.

3-2
 Chapter 3
Initiating Configuration Movement from Pre-Production to Production

5. Select Continue to initiate the configuration movement process from Non-Production to

Pre-Production. The page displays a confirmation message on successfully initiating the
Movement Process.
To verify if the movement is successful, check the Movement page. Once the movement is
successfully completed, the page does not list any Config ID.

Initiating Configuration Movement from Pre-Production to

Production
Before you initiate the Configuration Movement process from Production tenancy, ensure the
following:
• Successfully complete Configuration Movement process from Non-Production to Pre-
Production.
• Generate Security Token for accessing Pre-Production.
Generating Security Token
To initiate Configuration Movement from Pre-Production to Production, you need to first
generate a security token that enables access to the Pre-Production tenancy. Execute the
following Curl script to generate a valid token:

curl --location --request POST "https://

ENVIRONMENTNAME.fscloud.oraclecloud.com/pre-prod/api/oauth2/v1/access" --
header "Content-Type: application/json" --data-raw
"{\"User\":\"OracleFSCloudAdmin\",\"Password\":\"ADMINPASSWORD\"}"

In the above script, replace ENVIRONMENTNAME with the customer environment name and
ADMINPASSWORD with the password for OracleFSCloudAdmin user.

Initiating Configuration Movement from Pre-Production to Production

To move configuration changes from Pre-Production to Production, initiate the Configuration
Movement process from the Production tenancy.
1. Log in to the Production tenancy as an administrator user.
2. From Menu, select Configuration, Configuration Control, and then Movement. The
Movement page shows the result of the previous Configuration Movement process that
was initiated from the Production tenancy and was successful, if any.
3. Select Initiate Movement. The Config ID Movement page opens up.
4. In the Config ID Movement page, enter the Security Token generated by running the curl
script in Authentication Code, and select Continue. The page lists all closed Config IDs
in the Pre-Production tenancy that are ready for movement to the Production tenancy.
5. Select Continue to initiate the configuration movement process from Pre-Production to
Production. The Configuration Movement process runs in the background. However, the
page displays a progress bar and message indicating that the movement is in progress.
Once the configuration movement is complete, try to initiate the movement again and the
page displays a confirmation message saying the movement was successful.
To verify if the movement is successful, access the Movement page and try initiating
movement using the same Authentication Code used previously. If the movement is
successfully completed, the page does not list any Config IDs and displays a message
indicating the movement was successful.

3-3
4
Configurations

Understanding ID Generation
ID Generators enable you to define a uniform methodology for generating identifiers across
Oracle Financial Services Cloud, along with the capability to define patterns that are specific to
requirements of each feature. When you create entities like an Account or a Company, system
either generates the identifiers automatically, or validates the manually entered identifiers, both
based on the applicable ID Generator configuration.

Generation Type
ID Generation configuration can be of two types:
• Automatic: When you select automatic ID generation, the application generates the ID
automatically, according to the pattern defined in the configuration.
• Manual: When you select manual ID generation, the application lets you enter an ID
manually, but validates the ID against the pattern defined in the configuration.

ID Generation Pattern
ID Generation configuration of an entity defines the pattern in which an ID is generated (or
validated against) for that entity. ID generation pattern is a combination of two or more of these
components:
• Static: A static value as a component
• Sequence: A sequential component
• CheckDigit: A check digit component that uses either Mod10 or Mod11 algorithms

Note:
An ID generation pattern must have at least two components, one static component
and one sequence component. As IDs are generated in the system, the static
component remains appended to the ID as it is, while the sequential component
increments as per the definition.

ID Generation Configuration
Setting up ID Generator for an entity involves two steps:
1. Identification
2. Setup ID Generator

Identification
Under Basic Information, enter the following details:
• Name

4-1
 Chapter 4
Understanding ID Generation

• Long Name
• (Optional)Description

Setup ID Generator
Setting up ID Generator involves two steps:
• Setting up ID Attributes: This includes configuring Generation Type and Delimiter Type
for the identifier.
• Setting up ID Components: This includes choosing more than one Component Types
and its name or value.

Note:
It is mandatory to configure at least one attribute and two or more components for an
identifier.

Setting Up ID Attributes
• Setting Up Generation Type: ID Generation Type can be either Auto or Manual.
• Setting Up Delimiter Type: Select the delimiter character that you want to use between
components in the ID.

Setting Up ID Components
Configure the various components of the ID. The Component Type can be either Static,
Sequence, or CheckDigit.

Note:
You need to set up a minimum of two components and one of them should be of type
Sequence.

Configuring ID Generation
To generate identifiers for entities like Company and User Group, you need to configure the ID
Generator first and then associate it with the tenant (Non-Production).

Note:
This section gives you an overview of the generic steps involved in an ID Generator
configuration. For specific instructions on how to configure ID Generation for a
Company or a User Group, refer to the Related Links at the end of this section.

Configuring ID Generator for an entity is done using the ID Generator page and involves two
steps:
1. Add Identification
2. Setup ID Generator

4-2
 Chapter 4
Understanding ID Generation

Add Identification
Adding identification involves collecting three basic details of the ID Generation configuration:
• Name
• Long Name
• (Optional) Description

Setup ID Generator
Setting up ID Generator involves configuring the pattern for generating ID and involves two
steps:
1. Setting up ID Attributes: This includes configuring Generation Type and Delimiter Type
for the identifier.
2. Setting up ID Components: This includes choosing more than one Component Types
and its name or value.

Note:
It is mandatory to configure at least one attribute and two or more components for an
identifier.

Setting Up ID Attributes
ID attributes decide whether the ID generation should be manual or automatic. It involves
selecting the Generation Type and Delimiter Type.
• Set up Generation Type as either Auto or Manual.
– Auto: ID is generated automatically based on the pattern configured in ID Generator.
– Manual: You can enter the ID manually, but it will be validated against the pattern
configured in ID Generator.

Note:
If you select Manual, select the maximum length of the pattern in Max length /
Value. If you select Auto, the maximum length is taken as 16 by default.

• Set up Delimiter Type by selecting the Delimiter character to be used between various
components in the ID.

Setting Up ID Components
ID Components decide the pattern of the ID. Every ID should have two or more components; of
which one has to be sequential. The different types of components used in forming the ID
pattern are:
• Static: Define the static part of the ID in Static Name / Value.
• Sequence: Define the sequential part of the ID. This involves configurations like:
– Whether the ID is to be padded to the maximum length or not
– The number with which the sequence starts

4-3
 Chapter 4
Understanding ID Generation

– The number with which the sequence increments

– The maximum value of the sequence
• CheckDigit: Define the CheckDigit part of ID that uses either Mod10 or Mod11 algorithm
1. From the Menu, select Configuration, and then select ID Generator.
2. Select the entity for which you want to configure ID generation. For example, Company.
3. Select Add. This opens Creating ID Generator.
4. In Add Identification, perform these steps:
a. Enter Name for the ID Generation configuration.
b. Enter Long Name for the ID Generation configuration.
c. (Optional) Enter Description for the ID Generation configuration.
d. Select Continue.
5. In Setup ID Generator, there are two sections: Attributes and Components. In
Attributes section, follow these steps:
a. Select Add against Generation Type.
b. In Generation Type, select either Auto or Manual. If you select Auto, the ID
Generation is automatic and follows the pattern defined in this configuration. If you
select Manual, application lets you generate the identifier, but validates it against this
configuration.
c. (Optional) If you select Manual as the Generation Type, select Max length / Value. If
you have selected Auto, this field does not appear. In this case, the maximum length
is by default 16.
d. (Optional) In Delimiter Type, select the delimiter character that you want to use
between different components of the ID.
e. Select Done to return to Setup ID Generator.
6. In Components section, select Add against Add Component.
7. In Choose Component Type, select either Static, Sequence, or CheckDigit and tap
Done.
8. (Optional) If you have selected Static as Component Type, enter Static Name / Value
that forms the static component of the ID.
9. (Optional) If you have selected Sequence as Component Type, follow these steps:
a. Select Padding Ind ON or OFF.
b. Enter the value with which the sequence should start in Starts With.
c. Enter the value with the sequence should increment in Incremented By.
d. Enter the value up to which the sequence should increment in Max Value.
10. (Optional) If you have selected CheckDigit as Component Type, follow these steps:

a. Select either Mod10 or Mod11 in Algorithm.

b. Enter the format for transposing in Transpose.
c. Enter the format for adding weight in Weight.
11. Select Done in Choose Component Type.

12. Select Continue in Set Up ID Generator.

4-4
 Chapter 4
Understanding ID Generation

13. Select Finish

Related Topics
• Understanding ID Generation
• Configuring Company ID Generation
• Configuring User Group ID Generation

Configuring Company ID Generation

Configuring ID Generation for a Company ensures that the ID generation pattern is applied
every time you create a Company.
Configuring Company ID Generation involves two steps:
1. Add Identification: This step involves configuring basic details of the Company ID like
name, description, and so on.
2. Setup ID Generator: This step involves setting the pattern that the Company IDs should
follow.
To create an ID Generation Configuration for a Company, follow this procedure:

Note:
Select a Config ID before performing the following procedure.

1. From the Menu, select Configuration, and then select ID Generator, and then select
Company.
2. Select Add.
3. In the Add Identification page, enter the following attributes:
a. Name: Enter the name of the company.
b. Long Name: Enter the full name of the company.
c. Description: (Optional) Enter a meaningful description of the company.
4. Select Continue. This opens the Setup ID Generator page.
5. In the Attributes section, select Add to add a new Generation Type for the company
identifier. The Generation Type decides whether the identifier has to be generated
automatically or manually.
a. Select either Auto or Manual in Generation Type.
b. (Optional) Select the maximum length for the Company ID from the list in Max
Length / Value. All values from 1 to 16 are available for selection. This field appears
only when you select Manual in the previous step.
c. (Optional) Select the delimiter to be used in the Company ID from the list available in
Delimiter Type. The values available are: !, @, #, %, &, *, and -.
d. Select Done. This takes you back to the Setup ID Generator page.
6. Under the Components section, select Add to start adding components for the Company
ID.

4-5
 Chapter 4
Understanding ID Generation

Note:
A Company ID would require more than one component.

7. From the Choose Component Type options, select a value and then select Continue.
The possible options for component types are:
• Static: Enter Static Name / Value and select Done.
• Sequence: Turn Padding Indicator ON or OFF to choose whether to pad with zeroes
on the left. Enter the number with which the sequence starts in Starts With and how it
is incremented in Incremented By. Also enter the maximum value of sequence in Max
Value and select Done.
• CheckDigit: Select Mod10 or Mod11 under Algorithm section. Enter appropriate
values for Transpose and Weight and select Done.
8. Select Continue. This validates the ID generation pattern that you configured for the
Company and if valid, saves the configuration.
Once you have configured the Company ID Generation, you need to associate this
configuration with a tenant (Non-Production). After the Company ID Generation configuration is
associated with the tenant, you can start creating companies in the application.
Related Topics
• ID Generation
• Associating Company ID Generation Configuration with Tenant

Configuring User Group ID Generation

Configuring ID Generation for a User Group ensures that the ID generation pattern is applied
every time you create a User Group.
Configuring User Group ID Generation involves two steps:
1. Add Identification: This step involves configuring basic details of the User Group ID like
name, description, and so on.
2. Setup ID Generator: This step involves setting the pattern that the User Group IDs should
follow.
To create an ID Generation Configuration for a User Group, follow this procedure:

Note:
Select a Config ID before performing the following procedure.

1. From the Menu, select Configuration, and then select ID Generator, and then select
User Group.
2. Select Add.
3. In the Add Identification page, enter the following attributes:
a. Name: Enter the name of the user group.
b. Long Name: Enter the full name of the user group.
c. Description: (Optional) Enter a meaningful description of the user group.

4-6
 Chapter 4
Understanding ID Generation

4. Select Continue. This opens the Setup ID Generator page.

5. In the Attributes section, select Add to add a new Generation Type for the user group
identifier. The Generation Type decides whether the identifier has to be generated
automatically or manually.
a. Select either Auto or Manual in Generation Type.
b. (Optional) Select the maximum length for the User Group ID from the list in Max
Length / Value. All values from 1 to 16 are available for selection. This field appears
only when you select Manual in the previous step.
c. (Optional) Select the delimiter to be used in the User Group ID from the list available in
Delimiter Type.
d. Select Done. This takes you back to the Setup ID Generator page.
6. Under the Components section, select Add to start adding components for the User
Group ID.

Note:
A User Group ID would require more than one component.

7. From the Choose Component Type options, select a value and then select Done. The
possible options for component types are:
• Static: Enter Static Name / Value and select Done.
• Sequence: Turn Padding Ind ON or OFF. Enter the number with which the sequence
starts in Starts With and how it is incremented in Incremented By. Also enter the
maximum value of sequence in Max Value and select Done.
• CheckDigit: Select Mod10 or Mod11 under Algorithm section. Enter appropriate
values for Transpose and Weight and select Done.
8. Select Continue. This validates the ID generation pattern that you configured for the User
Group and if valid, saves the configuration.
Once you have configured the User Group ID Generation, you need to associate this
configuration with a tenant (Non-Production). After the User Group ID Generation configuration
is associated with the tenant, you can start creating user groups in the application.
Related Topics
• ID Generation
• Associating User Group ID Generation Configuration with Tenant

Associating Company ID Generation Configuration with Tenant

Follow this procedure to associate a Company ID generation configuration with a tenant.

Note:
Select a Config ID before performing the following procedure.

1. From the Menu, select Configuration, and then select Tenant.

2. Select the Associations tab.

4-7
 Chapter 4
Understanding Companies

3. Select Add.
4. Expand Required and then expand Company ID Generation Configuration section.
5. In Company ID Generator, select Add.
6. Select the Company ID Generation Configuration you want to associate and select
Continue.
7. Select Finish.
The Company ID Generation configuration association with the Tenant is complete.
If you have already associated a Company ID Generator configuration with the tenant, then the
page displays the associated Company ID Generation configuration.

Associating User Group ID Generation Configuration with Tenant

Follow this procedure to associate a User Group ID generation configuration with a tenant.

Note:
Select a Config ID before performing the following procedure.

1. From the Menu, select Configuration, and then select Tenant.

2. Select the Associations tab.
3. Select Add.
4. Expand Required and then expand User Group ID Generation Configuration.
5. In User Group ID Generator, select Add.
6. Select the User Group ID Generation Configuration you want to associate and select
Continue.
7. Select Finish.
The User Group ID Generation configuration association with the Tenant is complete.
If you have already associated a User Group ID Generation configuration with the tenant, then
the page displays the associated User Group ID Generation configuration.

Understanding Companies
Company is an abstract concept that represents statutory companies, business units, or levels
of financial consolidation and reporting. The company is an entity in the Tenant's organization
structure.
In Oracle Financial Services Cloud, you can set up instances of companies that the Tenant
wants to use across their cloud services, as well as organize them into hierarchies.

Company Types
You can create different types of companies in Oracle Financial Services Cloud:
• Financial: These companies hold financial or fiduciary responsibilities and are related to
Products, Billing Features, and Account Features that are used for all accounting.
• Marketing: These are companies that market and brand products. They are related to
Products and are used to identify the owner, define branding and other forms of marketing

4-8
 Chapter 4
Understanding Companies

(including mass mailing), along with other details like interest rates. They are used for
various forms of marketing reporting and communications.
• Operations: These companies have employees and operators, and perform operations.
They are used for all forms of administrative processing and roll-up reporting.
• Sales: These are companies that sell products and are used to identify who can sell the
product within the Company.
• Legal: These companies are legal entities and are used for legal contracts, agreements,
disclosures, and so on. They are used to define statutory and regulatory policies of various
regions where the company's Products are being sold.

Organization Unit Types

Every company should have a Main organization unit type and a Sub organization unit type.
This helps in creating an organizational structure for the company.
• A Main organization unit type indicates a high level role in organization structure, such as
a Head Office or a Zonal Office. The Main organization unit types available in OFSC are:
– Head Office
– Regional Office
– Zonal Office
– Area Office
– Business Unit
• A Sub organization unit type indicates a unit that takes additional activities, such as a
Shared Service Centre or a Branch. The Sub organization unit types available in OFSC
are:
– Branch
– Shared Service Centre
– Division
– Department

Creating Companies and Company Hierarchies

To create a Company in Oracle Financial Services Cloud, you need to perform the following
prerequisite tasks:

Note:
These configurations ensures that every company created in the tenant follows the
same ID pattern. Note that this ID pattern is applied only when you select automatic
ID generation while creating a Company. In case of manual ID generation, you can
enter an ID of your own choice, which is then validated against the pattern set.

1. Create a Company ID Generation configuration: This configuration lets you define the
pattern to be followed while creating a Company ID.
2. Associate the Company ID Generation configuration with the Tenant: This configuration
lets you associate the above configuration to a tenant, so that every company created in
the tenant follows the same pattern.

4-9
 Chapter 4
Understanding Companies

Once the Company ID Generation configuration is created and associated with the tenant, you
can go ahead with the company creation.
Procedure for creating company remains the same for all types of companies. To understand
the procedure for creating an 'Operations' type of company, see Creating Operations
Company.
To create a hierarchy of companies, associate one company to another, thereby establishing a
parent-child relationship between them. See Creating Operations Company Hierarchy.

Creating Operations Company

Follow this procedure to create a new Operations Company.

Note:
Select a Config ID before proceeding with this procedure.

1. From the Menu, select Configuration and then select Company, and then select
Operations.
2. Select Add to start creating the Company.
3. In the Add Identification page, enter the following details:
a. Enter Name and Long Name of the company.
b. Select the Main organizational unit of the company. The values available are: Head
Office, Regional Office, Zonal Office, Area Office, and Business Unit.
c. Select the Sub organizational unit of the company. The values available are: Branch,
Shared Service Centre, Division, Department.
d. (Optional) Select the calendar against Active and select the date on which the
company turns active.
e. (Optional) Select the calendar against Inactive and select the date on which the
company turns inactive.
f. Select Continue.
4. In the ID Generation page, you can either view the automatically generated identifier for
the company, or manually enter an identifier. This is based on the Company ID Generation
configuration that is associated with the tenant.
While manually entering an identifier, system validates the ID against the Company ID
Generation configuration that is associated with the tenant. If the validation fails, an error
message appears.
5. Select Continue.
6. In the Setup Contact page, you can create the contact for the company, or skip it.
• Select Create New Contact to enter contact details like Phone number, Email, and
Address.
• Select Skip Contact Section for now to skip creating the contact details.
7. Select Continue.
8. (Optional) In the Manage Associations page, you can add associations to Products,
Operators, Employees, Supplier Services, and Keyword Libraries.

4-10
 Chapter 4
Understanding Companies

9. Select Continue.
10. Select Finish.

Creating Marketing Company

Follow this procedure to create a new Marketing Company, which helps to associate products
to your organization structure in Oracle Financial Services Cloud.
Creating a Marketing Company includes four steps:
1. Add Identification
2. ID Generation
3. Setup Contact
4. Manage Associations

Note:
Select a Config ID before proceeding with this procedure.

1. From the Menu, select Configuration and then select Company, and then select
Marketing.
2. Select Add to start creating the Company.
3. In the Add Identification page, enter the following details:
a. Enter Name and Long Name of the company.
b. Select the Main organizational unit of the company. The values available are: Head
Office, Regional Office, Zonal Office, Area Office, and Business Unit.
c. Select the Sub organizational unit of the company. The values available are: Branch,
Shared Service Centre, Division, Department.
d. (Optional) Select the calendar against Active and select the date on which the
company turns active.
e. (Optional) Select the calendar against Inactive and select the date on which the
company turns inactive.
f. Select Continue.
4. In the ID Generation page, you can either view the automatically generated identifier for
the company, or manually enter an identifier. This is based on the Company ID Generation
configuration that is associated with the tenant.
While manually entering an identifier, system validates the ID against the Company ID
Generation configuration that is associated with the tenant. If the validation fails, an error
message appears on the page.
5. Select Continue.
6. In the Setup Contact page, you can create the contact for the company, or skip it.
• Select Create New Contact to enter contact details like Phone number, Email, and
Address.
• Select Skip Contact Section for now to skip creating the contact details.
7. Select Continue.

4-11
 Chapter 4
Understanding Companies

8. (Optional) In the Manage Associations page, you can add both Required associations
and Optional associations. Required associations are those that need to be configured
before closing the Config ID and initiating Configuration Movement of the company.
Optional associations are not mandatory for Configuration Movement of company records.
a. Select Required and select Add under Product ID Generation Configuration, to add
a Product ID Gen Config for the company.
b. Select Add under Product Component ID Generation Configuration, to add a
Product Component ID Gen Config for the company.
c. Select Optional and select Add under Product Components, to add a product
component for the company.
d. Select Add under Product ID Generation Configuration, to add a Product ID Gen
Config for the company.
9. Select Continue.
10. Select Finish.

Creating Operations Company Hierarchy

A company hierarchy includes a parent (root) company and one or many child companies. In
Oracle Financial Services Cloud, you can create a parent-child relationship by associating a
child company to the parent company. Currently, association is limited between companies of
same type. That is, you can associate an Operations company with other Operations
Companies only.
Follow this procedure to create a hierarchy of companies. This establishes your organization
structure or hierarchy in the system.

Note:
Select a Config ID before proceeding with this procedure.

1. From the Menu, select Configuration and then select Company, and then select
Operations.
2. Select View All to see the list of existing companies.
3. Select More Options against the parent Company and select Add Company.
4. Select Create New Operations Company and select Continue. This takes you through
the steps required to create a new Operations company and then add it as a child to the
parent company selected in the previous step.

Note:
The page also displays an option to Use an Existing Company whereby you
can associate an existing company of another type.

5. Follow instructions in Creating Operations Company to create a child Operations company.

4-12
 Chapter 4
Understanding and Configuring Operations Company Supplier Service Instance

Note:
In the third step of Creating Operations Company, you can inherit the contact
details of the parent company by selecting Use Contact from Company option.

6. (Optional) In the Manage Associations page, under Optional add the required
associations like Products, Operators, Employees, and Keyword Libraries.
7. Select Continue. A success message appears.
8. Select Finish.

Understanding and Configuring Operations Company Supplier

Service Instance
Introduction
Operations Company Supplier Service in Oracle Financial Service Cloud facilitates integration
between your organization and your suppliers. Oracle Financial Services Cloud supports a
wide range of service providers. As an administrator of the financial institution, from Operations
Company Supplier Service configuration you can select and configure which Supplier Services
(such as, Signature, Storage) and Supplier Service Components (such as, DocuSign
eSignature, Twilio SendGrid) to use, based on the business requirement.
Functionalities
Following are the functionalities of Operations Company Supplier Service in Oracle Financial
Services Cloud:
• Integration with Service Providers: Operations Company Supplier Service lets you
configure and manage interactions with suppliers. The wide range of supported supplier
integration ensures that you can continue using your preferred service providers as well as
tap into Oracle Financial Services Cloud capabilities.
• Centralized Supplier Configuration: Operations Company Supplier Service enables you
to define the supplier service providers that you want to use, specify the credentials
required (for example, user name and password), and manage other configuration details
in one place.
• Security and Credentials Management: Operations Company Supplier Service provides
you a platform to securely store and manage credentials (such as, user name and
password) that are necessary to authenticate with the supplier service providers.
Key Aspects
• Operations Company Supplier Service configuration: Captures the basic information
required to integrate suppliers with the system, associates to the Operations Company,
Supplier Service Component and the corresponding Supplier Service. Association to the
Supplier Service enables:
– Identification of appropriate Supplier Service Component's Service Interface Name.
For example, externaltwilio.messaging.
– Identification of the instance of Oracle Secure Store, which contains the parameters or
key value pairs to pass to the supplier services, with each request.

4-13
 Chapter 4
Understanding and Configuring Operations Company Supplier Service Instance

• Operations Company Supplier Service Component - Credential Maintenance:

Captures sensitive information such as, user name and password and securely stores and
manages sensitive authentication in Oracle Secure Store.

Note:
You need to enter the credentials separately in each environment (Non-
Production, Pre-Production, and Production), as each has its own instance of
Oracle Secure Store.

Configuring Operations Company Supplier Service includes following:

• Subscription and setting up Oracle Financial Services Cloud: Subscribe to Oracle
Financial Services Cloud and complete the basic configurations to get you started.
• Configuration of Operations Company Supplier Service: In Oracle Financial Services
Cloud, configurations such as Operations Company Supplier Service, are required to
integrate various supplier services like Telesign SMS, with the core systems of the financial
institution. These supplier services are crucial in achieving your business goals such as
distributing communication to your customers. You can select the required Supplier Service
and Supplier Service Component while configuring Operations Company Supplier Service
and associate with your Operations Company.
• Service Interaction and Integration:
You can use Oracle Financial Services Cloud's Credential Maintenance to configure the
required parameters to interact with the Supplier Service. This is optional and depends on
the service providers. These parameters are stored securely in Oracle Secure Store, and
are sensitive. When an integration configuration is created, you can use these parameters
for secure access. The Integration configuration passes the Secure Store key and Supplier
Service Component's Service Interface Name to the API configuration, which bridge
communication between the financial institution and services using secure authentication
mechanisms, ensuring secure data exchange.

Figure 4-1 Supplier Service Interaction

Configuration Movement
Operations Company Supplier Service

4-14
 Chapter 4
Understanding and Configuring Operations Company Supplier Service Instance

The Operations Company Supplier Service instance is configurable and it follows the
configuration movement process; that is, if you configure the Operations Company Supplier
Service instance in one environment (non-production), you can move the configuration to
different environments (Pre-Production and Production).
Operations Company Supplier Service-Credential Maintenance
The Credential Maintenance of Operations Company Supplier Service Component does not
follow the configuration movement process since each environment has its own instance of
Oracle Secure Store. Hence you need to enter the credentials in each environment (Non-
Production/Pre-Production/Production).

Creating and Editing Operations Company Supplier Service Instance

Creating Operations Company Supplier Service Instance
To create an Operations Company Supplier Service Instance, you need to provide basic
information to identify the Operations Company Supplier Service configuration instance, and
associate it to the Operations Company, Supplier Service Component and the corresponding
Supplier Service. As an administrator of the financial institution, you can select which Supplier
Services and Components to use, based on the institution's needs. The Supplier Service
Component and the Supplier Service corresponding to that Supplier Service Component will
be available as part of your initial configuration setup.

Prerequisites

Note:
Ensure that you complete the prerequisites before proceeding with creating the
Operations Company Supplier Service configuration.

Table 4-1 Prerequisite

Prerequisites Details
Set the Config ID 'Active' Config ID is set and logged in user has the requisite entitlements.
Ensure that all the dependent configurations and associations must be part of same open
Config ID.
See Creating Config ID
Create Operations Company Operations Company configuration instance has been created.
configuration instance See Creating Operations Company

Creating Operations Company Supplier Service Instance

To create a new Operations Company Supplier Service configuration instance, follow these
steps:
1. Access and log in to the Oracle Financial Services Cloud application.
2. Select a Config ID for which you want to configure Operations Company Supplier Service
Instance.
3. From Menu, select Configuration and then select Operations Company Supplier
Service.
4. On the Operations Company Supplier Service landing page, select Create.

4-15
 Chapter 4
Understanding and Configuring Operations Company Supplier Service Instance

5. Enter Basic Information such as, Name, Long Name, and Description to identify the
Operations Company Supplier Service configuration instance.
6. Adding Operations Company
You need to establish a relationship between Operations Company Supplier Service and
Operations Company. You can add only one Operations Company with a Operations
Company Supplier Service.
To add an Operations Company to the Operations Company Supplier Service, select Add
Operations Company, and choose the Operations Company from the list of existing
operations companies.
7. Adding Supplier Service Component
You need to establish a relationship between Operations Company Supplier Service and
Supplier Service Component to advise the system which Supplier Service to choose when
executing the service. You can add only an existing Supplier Service Component to the
Operations Company Supplier Service.
To add the Operations Company Supplier Service configuration instance with the Supplier
Service Component, select Add Supplier Service Component. Select the Supplier
Service Component Type. The Supplier Service Components related to the selected
Supplier Service Component Type is displayed from which you can choose the required
Supplier Service Component.
8. Set the activation of the configuration using Active Date. By default, the Active Date is set
to the current date.
9. After entering the details, select Save to continue with the association.
10. Associating to Operations Company and Supplier Service Component
After selecting Save for saving the basic information and establishing the relationship with
Operations Company and Supplier Service Component, you can associate Operations
Company Supplier Service configuration instance with the Supplier Service Component
configuration instance. Depending on the Supplier Service Component that you choose for
establishing relationship, the associations vary. Choosing the association is optional.
To associate the Operations Company Supplier Service configuration instance to an
existing configuration instance, from the Associations section, select Add. Select the
configuration instance that you want to associate. You can associate Operations Company
Supplier Service configuration to multiple configuration instances of Supplier Service
Component.
11. Select Save to save the details, or Save&Exit to save and return to the landing page.

Editing Operations Company Supplier Service Instance

You can modify the basic and attribute information of the Operations Company Supplier
Service configuration instance. You can also remove or replace the Operations Company and
Supplier Service Component relationships and the existing associations. When you replace a
Supplier Service Component, then you need to select the corresponding associations.
You can edit the details of Operations Company Supplier Service configuration instance in two
ways:
From Landing Page:
1. In the Action column, select Edit from More Menu corresponding to the Operations
Company Supplier Service name that you want to edit.
From Summary Page:
1. On the Operations Company Supplier Service landing page, hover over the name of the
Operations Company Supplier Service and select it.

4-16
 Chapter 4
Editing Tenant Details

2. From the Summary page, select Edit.

In the Update Operations Company Supplier Service page, modify the details as needed.
Select Save to save the changes, or Save&Exit to save the details and return to the landing
page.

Deleting Operations Company Supplier Service Instance

To delete the Operations Company Supplier Service instance, ensure that the configuration is
in Active or In Progress state.
You can delete an Operations Company Supplier Service configuration instance only if it is not
associated with any configuration instances. When the configuration instance is deleted, the
relationship with Operations Company and Supplier Service Component is also deleted.
You can delete an Operations Company Supplier Service configuration instance in two ways:
From Operations Company Supplier Service Landing Page:
1. In the Action column, select Delete from More Menu corresponding to the Operations
Company Supplier Service name that you want to delete.
From Operations Company Supplier Service Summary Page:
1. On the Operations Company Supplier Service landing page, hover over the name of the
Operations Company Supplier Service and select it.
2. From the Summary page, select Edit.
3. Select Actions on the top right corner and select Delete.
If there are no associations, the Operations Company Supplier Service configuration instance
is deleted after confirmation. If there are any associations, a warning message is displayed.
You need to remove the association and then delete the Operations Company Supplier Service
configuration instance. If there is any credential added to the Operations Company Supplier
Service configuration instance, then before deleting the configuration instance, you need to
remove it from Operations Company Supplier Service-Credential Maintenance.
To remove an association, expand Association section and select Actions on the top right
corner of which you want to remove. Then select Remove.

Editing Tenant Details

You can edit the details of a tenancy, like its name and description, along with its associations,
if any. Follow the procedure below to edit the tenancy details, including the associations.

Note:
You can edit Tenancy details of all three environments, Non-Production, Pre-
Production, and Production. To edit details of a tenancy, ensure that you are
logged in to the same environment.

1. Access and log in to the Oracle Financial Services Cloud application.

2. From Menu, select Configuration and then select Tenant.
3. Select More Options against the Tenant record.

4-17
 Chapter 4
Editing Tenant Details

4. Select Edit. This opens the Edit Tenant page.

5. Under Identification section, you can edit the following details: Name, Long Name, and
Description.
6. Select Continue. This opens the Mandatory Association page.
7. Under Mandatory Association, you can either Add an association, or Delete an
association.
• Add Association: Select Add against an ID Generator (either Company ID Generator
or User Group ID Generator). This opens the Associate ID Generator page. Select an
ID Generator configuration and select Done.
• Delete Association: Select Delete under Action menu against an ID Generator
configuration. A message saying the association is deleted appears
8. Select Continue. This saves the updated tenancy details.

4-18
5
Operations

Credential Maintenance of Operations Company Supplier

Service
You can associate a set of credentials and parameters with instances of the Operations
Company Supplier Service Configuration through the Credential Maintenance. These
credentials and parameters vary depending on the Service Provider and Supplier Service.
Some Service Providers may not require any credentials. Based on the specific requirements
of the Supplier Service, Oracle Secure Store stores credentials such as user name, password,
and organization identifier, which are used to establish a connection to the service. These
credentials are unique to each Service Provider and their respective service.
Managing the credentials of Operations Company Supplier Service instance involves the
following steps:
Adding a Credential
1. Access and log in to the Oracle Financial Services Cloud application.
2. Select a Config ID for which you want to add the credential.
3. From Menu, select Operations and then select Operations Company Supplier Service-
Credential Maintenance.
4. In the Action column, select Add Credential from More Menu corresponding to the
Operations Company Supplier Service name that you want to add credentials.

Note:
You can add only one credential to one Operations Company Supplier Service.
Add Credential option is not available if the service provider has not set any
credentials. If the credential is already added, you can choose Edit Credential or
Delete Credential option to modify the credential.

5. Provide the credential details and select Create to add the credentials.
Editing a Credential
1. In the Action column, select Edit Credential from More Menu corresponding to the
Operations Company Supplier Service name that you want to edit the credential.

Note:
Ensure to keep your credentials handy before proceeding as system cannot
retrieve details such as Password, client secret and so on.

2. Provide the credential details and select Update to modify the credentials.

5-1
 Chapter 5
Credential Maintenance of Operations Company Supplier Service

Deleting a Credential
1. In the Action column, select Delete Credential from More Menu corresponding to the
Operations Company Supplier Service name that you want to delete the credential.
2. In the dialog box, select Delete to confirm.

5-2
6
Understanding Security Management
Security Management provides information on Secure Configurations and generic security
recommendations for securing client-side browsers that will access services on the Oracle
Financial Services Cloud platform.

Secure Configurations
Secure configurations for Oracle Financial Services Cloud

User Identity Management

Identity management on the Financial Services Cloud platform is provided by Oracle Cloud
Infrastructure Identity and Access Management (OCI IAM). See Oracle Cloud Infrastructure
Documentation to know more about the options for configuring OCI IAM and managing user
identities on it. There are also several options for identity federation to enable a robust single
sign on (SSO) configuration for services deployed on the Financial Services Cloud platform to
securely cooperate with other identity management systems.

User Entitlement Management

Entitlements management for user identities that are granted access to the Financial Services
Cloud platform are provided at three levels in the platform:
• Purchased entitlements are managed by the platform based on the services a customer
has purchased. The platform only allows access to endpoints that belong to services a
customer has purchased
• Course-grained entitlements to each customer tenancy on the platform are managed via
the OCI IAM interface where access to customer tenancies on the Financial Services
Cloud platform are controlled via OCI IAM Application definitions. There is an OCI IAM
application defined per tenancy you have purchased on the Financial Services Cloud
platform. Granting user identities in OCI IAM access to the OCI IAM Application for a
tenancy also grants them an entitlement to access that tenancy on the Financial Services
Cloud platform from the network/web.
• Fine-grained entitlements to specific service endpoints available from the Financial
Services Cloud platform are managed via an Entitlement service domain (group of
application interfaces and a user interface) that is exposed from the platform itself.
As mentioned above, an OCI IAM application will be set up for each customer tenancy
provisioned for you on the Financial Services Cloud platform. By default, new customers are
provisioned with three tenancies on the platform:
• Production
• Pre-production
• Non-Production
In addition to the OCI IAM applications, as a convenience, an OCI IAM user group specific to
each customer tenancy on the Financial Services Cloud platform will be created and granted
access to the tenancy on the platform.

6-1
 Chapter 6
Secure Configurations

To grant a user the course-grained entitlement to log into one of your tenancies on the
Financial Services Cloud platform, the user’s OCI IAM identity will need to be granted access
to the OCI IAM application for that tenancy, or be added to the OCI IAM user group that has
been granted access to the OCI IAM application for that tenancy on the platform. A user who
does not have access to the OCI IAM application for a customer tenancy will be unable to
access the tenancy on the Financial Services Cloud platform. Granting or revoking access to
OCI IAM applications for customer tenancies in this manner may be done as described in
Oracle Cloud Infrastructure documentation.
Fine-grained entitlement configurations are also available at a minimum down to the endpoint
level for services on the Financial Services Cloud platform where control is available to grant or
revoke access by HTTP verb on each service endpoint interface exposed from the platform.
See Entitlements Management on options for configuring fine-grained entitlements.

Follow the Principle of Least Privilege

The principle of least privilege states that users should be given the least amount of privilege
(entitlements for access) to perform their jobs. Over ambitious granting of entitlements,
especially early on in an organization’s life cycle when fewer people are involved and work
needs to be done quickly, can leave an application open for abuse. Therefore, entitlements
granted to users should be audited periodically to determine their relevance to the user’s
current job responsibilities and then adjustments should be made as needed to follow the
Principle of Least Privilege.

Keep Software Current

One of the principles of good security practice is to keep all software versions and patches up
to date. To access services on the Financial Services Cloud platform please ensure that
browsers or other consuming webservices are kept current with support for TLS v1.2 or later
encryption.
TLS v1.2 is the minimum encryption standard supported by the Financial Services Cloud
platform. Access to interfaces exposed from services on the platform via software that does
meet this level of encryption will be rejected by the platform. Also, in the future the platform’s
minimum encryption standard will be increased to mitigate security vulnerabilities discovered in
older encryption standards. Keeping the software you are using to access services on the
Financial Services Cloud platform as up to date as possible will help insure that any new
minimum encryption standards for the platform will not disrupt your access to the services
deployed on it.

Secure Browser Configuration

As stated above, services deployed on the Financial Services Cloud platform are implemented
to be secure by default by requiring TLS v1.2 or later encryption support and by enforcing
access only for requests that are both authenticated and authorized for the access being
attempted. Platform services cannot however enforce security in any facilities such as the
browsers being used to access them.
Please follow best practices to secure browsers being used to access services on the Financial
Services Cloud platform by following the advice of authorities such as the US government’s
Cyber security and Infrastructure Security Agency (CISA).

Secure Access to Service APIs

Application Programming Interfaces (APIs) from services on the Financial Services Cloud are
exposed via URL endpoints implementing Representational State Transfer (REST) protocols.
These APIs are implemented to be secure by default by requiring TLS v1.2 or later encryption

6-2
 Chapter 6
Post Initial Configuration

support and by enforcing access only for requests that are both authenticated and authorized
via entitlements.
Secure headless authentication to service APIs is available via an OAuth2 API exposed by the
platform that is integrated with OCI IAM facilities (meaning it will also support any SSO
configurations made through OCI IAM).
APIs exposed from the platform cannot however enforce security in any facilities such as other
webservices or browsers being used to access them. Advice on securing every type of
webservice that might access service APIs on the Financial Services Cloud platform is beyond
the scope of this guide. Please consult with the provider of any webservices that will be
accessing service APIs on the Financial Services Cloud platform on how to configure those
webservices to be secure. Please also review advice from US government’s Cyber security
and Infrastructure Security Agency (CISA) on Web Services Integration.

Post Initial Configuration

Change Default User Passwords
The Financial Services Cloud platform provides a default OracleFSCloudAdmin account to
support initial configuration. When this configuration is complete, it is a best practice to change
the password on the default account to mitigate its potential for misuse.

Lock and Expire Default User Accounts

As stated above, the Financial Services Cloud platform provides a default
OracleFSCloudAdmin account to support initial configuration. When this configuration is
complete, and specific users have been provisioned with the administrative entitlements
granted to the OracleFSCloudAdmin account, lock and expire access for the default
OracleFSCloudAdmin account to further mitigate its potential for misuse.

Enforce Password Management

At a minimum, apply basic password management rules, such as password length, history, and
complexity, to all user passwords using the features available in Oracle Cloud Infrastructure
Identity and Access Management (OCI IAM). See Oracle Cloud Infrastructure documentation
on options for configuring IAM and managing user identities on it.

6-3
7
Understanding User Management
User Management in Oracle Financial Services Cloud (OFSC) includes on-boarding of
Employees and Operators, along with creating User profiles for them. Once the profiles are
created for an Operator, the user credentials are created and further managed using Oracle
Cloud Infrastructure Identity and Access Management (OCI IAM).
In Oracle Financial Services Cloud, a person is created as an Employee first, and on-boarded
as an Operator. Both Employee and Operator are associated to an Operations Company
(either same or different), which is the business division for which they work.

Employee
An Employee is an individual who works for the Company and is associated with a business
division.

Operator
An Operator is a person identified in relation to work to be performed in Oracle Financial
Services Cloud, like a Business Administrator. An Operator directly interacts with the business
services using secure credentials.
An Operator is an Employee with access to Oracle Financial Services Cloud and has the
appropriate entitlements for it. Operators are associated with an Operations Company, which
could be either same as that of the Employee, or a different one.
Once an Operator sets up their login in OCI IAM, their user profile is created in Oracle
Financial Services Cloud, while their credentials are created in OCI IAM itself. A User can have
access to multiple tenancies; in which case the user need to be created in each tenancy. OCI
IAM manages the login credentials for a user, whereas their Entitlements is specific to each
tenancy and is configured by OFSC.

Note:
User Management activities like creating and managing user credentials, locking and
unlocking users, resetting passwords etc are handled using OCI IAM.

Creating Employee
An Employee is a person who works for the tenant and is associated with an Operations
Company. You need to on-board a person as an Employee prior to on-boarding them as an
Operator. Both Employee and Operator must be associated to an Operations Company, which
is the business division for which they work.
Creating an Employee in Oracle Financial Services Cloud involves three steps:
1. Add Identification
2. Find Operations Company
3. Setup Contact

7-1
 Chapter 7
Creating Operator

To create an employee, follow this procedure:

1. From the Menu menu, select Entitlements and then select Employee.
2. Select Add.
3. In Setup, select Employee Only and select Continue.
4. In the Add Identification page, enter the following details:
a. Enter the employee's email ID in Email.
b. (Optional) Select either Mr., Mrs., or Miss in Prefix.
c. Enter First Name and Last Nameof the employee.
d. (Optional) Enter Middle Name/Initial of the employee.
e. (Optional) Select either Sr or Jr in Suffix.
f. (Optional) Enter the Date Of Birth of the employee.
g. (Optional) Enter the Social Security Number.
h. (Optional) Enter the Employee ID, Job Code, and Job Title of the employee.
5. Select Continue.
6. In Find Operations Company page, in Find and Select, search and select an operations
company and select Done.
7. Select Continue.
a. (Optional) In Add Phone section, select Add. Enter Phone Number and select
appropriate values in Phone Type and select Continue.
b. The Email section displays the email address entered. If required, you can edit the
email ID provided.
c. (Optional) In Add Address section, select Add. Enter Address Line 1, , Country,
State, City, Postal Code, and select the Address Type and select Done. You can
also add additional details like Address Line 2, and Address Identifier.
d. Select Continue.
8. Select Finish in the Success page. The page also displays the name of the employee.
9. (Optional)You can select Go to Details Page to view the details of the employee.
Related Topics
• Creating Employee as Operator
• Setting Up Employee as Operator
• Understanding User Management

Creating Operator
An Operator is a person in Oracle Financial Services Cloud who performs activities within the
business services. An Operator directly interacts with the application using secure credentials
and must be an Employee prior to being on-boarded as an Operator.
Oracle Financial Services Cloud offers two ways to create an Operator:
• Create an Employee as an Operator
• Set up an existing Employee as an Operator

7-2
 Chapter 7
Creating Operator

Creating an Employee as an Operator

Use this option if you want to create an Operator in one go. You can create an employee and
then proceed with assigning them Operator privileges. See Creating Employee as Operator.

Setting up an Employee as an Operator

Use this option if you have already created an Employee and want to give them Operator
privileges. See Setting Up Employee as Operator.

Creating Employee as Operator

Creating an employee as an Operator involves two steps:
1. Setup Employee
2. Setup Operator
To create an employee as Operator, follow this procedure:
1. From the Menu, select Entitlements and then select Employee.
2. Select Add.
3. In Setup, select Employee as Operator.
4. Select Continue.
5. In the Setup Operator page, select Employee.
6. In the Add Identification page, enter the personal details of the Operator.
a. Enter Email for the Operator.
b. (Optional) Select the Prefix with which the Operator is addressed.
c. Enter First Name and Last Name of the Operator.
d. (Optional) Enter Middle Name/Initial of the Operator.
e. (Optional) Select the Suffix to add to the Operator Name.
f. (Optional) Enter the Date Of Birth of the operator in mm/dd/yyyy format.
g. (Optional) Enter the Social Security Number of the Operator.
h. (Optional) Enter the Employee ID, Job Code, and Job Title of the Operator.
7. Select Continue.
8. In the Find Operations Company page, search and select an Operations Company and
select Done.
9. Select Continue.
a. (Optional) In Add Phone section, select Add. Enter Phone Number and select
appropriate values in Phone Type and select Continue.
b. The Email section displays the email address entered. If required, you can edit the
email ID provided.
c. (Optional) In Add Address section, select Add. Enter Address Line 1, , Country,
State, City, Postal Code, and select the Address Type and select Done. You can
also add additional details like Address Line 2, and Address Identifier.
d. Select Continue.
10. In Setup Operator, search and select an Operations Company and select Done.

7-3
 Chapter 7
Creating Operator

11. Select Continue.

12. In Setup, select either Needs Login or Skip Login For Now and select Continue.

• Needs Login: Select this value and select Continue to configure login for the
Operator. In Setup Login, enter Login Name and select Continue. Note that you
cannot change the Login Name after the Operator is created.

Note:
If the Login Name you entered is available in OCI IAM, you have to enter
another one.

• Skip Login For Now: Select this value and select Continue to skip the step and
configure login later.

Note:
To create login at a later point of time, follow the instructions in Configuring
Login for an Operator.

13. Select Finish in the Success page. The page also displays the name of the Operator.

Once the operator, along with their login credentials, is created, an email with Activation Link
is sent. Select the link in the email to create a new password. Once the operator sets the
password, they can log in to OFSC application using their credentials.

Note:
You can edit the Operator details to change the associated Operations Company,
provided you have not configured entitlements for the Operator.

Setting Up Employee as Operator

Setting up an employee as an Operator involves two steps:
1. Setup Operator: Search and select an Employee and an Operations Company.
2. Setup: Select whether to create login credentials for the Operator or not.
To set up an employee as an Operator, follow this procedure:
1. From the Menu, select Entitlements and then select Operator.
2. Select Add.
3. In Setup Operator, search and select an Employee and select Done.
4. In Setup Operator, search and select an Operations Company and select Done.
5. Select Continue.
6. In Setup, specify whether you need to set up login or skip it:
• Needs Login: Select this value and select Continue to configure login for the
Operator. In Setup Login, enter Login Name and select Continue. Note that you
cannot change the Login Name after the Operator is created.

7-4
 Chapter 7
Creating Operator

Note:
If the Login Name you entered is available in OCI IAM, you have to enter
another one.

• Skip Login For Now: Select this value and select Continue to skip the step and
configure login later.
7. Select Finish.
Once the operator is created, they will receive an email with Activation Link. Select the link in
the email to create a new password. Once the operator sets the password, they can log in to
OFSC application using their credentials.

Note:
You can edit the Operator details to change the associated Operations Company,
provided you have not configured entitlements for the Operator.

Configuring Login for an Operator

To configure login for an Operator, follow this procedure:
1. From the Menu, select Entitlements and then select Employee.
2. Select View All.
3. From the list of operators, select More Options and select Go to Details.
4. Expand Login and you will see the message You haven't setup the login yet. Click on
pencil icon to to create/update one.
5. Select Edit Login and enter Login Name.
6. Select Continue.
You will receive an email with Activation Link. Select the link in the email to create a new
password. Once the operator sets the password, they can log in to OFSC application using
their credentials.

7-5
8
Understanding Entitlements Management
Entitlements represents the process of validating whether a user is allowed to perform a
business function in Oracle Financial Services Cloud application or not. This involves both
authentication of users and authorization of their transactions. Entitlements enables fine-
grained access control of the service capabilities (API end-points). You can grant or revoke
access to a service capability by adding or removing the users from the user groups.
In Oracle Financial Services Cloud, users are grouped into User Groups and related
transactions are grouped into Transaction Groups, and then associate the User Groups and
Transaction Groups to configure the necessary entitlements.

Follow the steps below to configure entitlements for various users of OFSC:
1. Configure Transaction: A Transaction represents a public business function in Oracle
Financial Services Cloud that a user needs to access. Follow this procedure to configure
Transactions for all API end-points that Operators would need access to.

Note:
Oracle Financial Services Cloud offers a set of pre-configured Transactions that
covers the basic system capabilities. You need not configure Transactions for
these Transaction Types. See List of Pre-configured Transactions.

2. Create Transaction Group: A Transaction Group bundles one or more Transaction

Configurations that can be administered as a convenient single unit. Follow this procedure
to create Transaction Groups, thereby enabling fine-grained entitlement provisioning.
3. (Optional) Create Transaction Group Hierarchy: You can create a hierarchy of Transaction
Groups for ease of maintenance.
4. Create User Group: A User Group bundles one or more users who can be administered as
a convenient single unit. Follow this procedure to create a user group and add users
(Operators) to it.
5. (Optional) Create User Group Hierarchy: You can create a hierarchy of User Groups for
ease of maintenance.
6. Associate Transaction Group with User Group: Allow all users in a User Group to access
all Transactions in a Transaction Group by associating them to each other. Follow this
procedure to associate a Transaction Group with a User Group.

8-1
 Chapter 8
Configuring Transaction

Configuring Transaction
A Transaction represents a public business function in Oracle Financial Services Cloud that a
user needs to access. You need to configure Transactions for all API end-points that your
operators would need access to. Else, the service request is aborted with the standard HTTP
code of 403 Forbidden message, as the server does not process the request due to lack of
client access entitlements.

Note:
Oracle Financial Services Cloud comes with a set of pre-configured transactions that
provide the basic functions that a user would need access to. You can add these to
your Transaction Groups to provide the required entitlements.

Configuring a Transaction includes two steps:

1. Select Transaction Type
2. Add Identification

Note:
Transaction configurations can be moved from one tenancy to another using
Configuration Movement. Hence select a Config ID before proceeding with this
procedure.

Follow this procedure to configure a new transaction.

1. From the Menu, select Entitlements, and then select Transaction.
2. Select Add. This opens the Creating Transaction page.
3. In Select Transaction Type, select a Transaction Type and select Continue. The Add
Identification page opens with details of the selected Transaction Type.

Note:
All Transaction Types that are not yet configured as a Transaction are available
for selection in this page.

4. (Optional) Edit the details in Add Identification page:

a. Name: Enter a new name for the Transaction.
b. Long Name: Enter a new long name for the Transaction.
c. Description: Enter a new description for the Transaction.
d. Set Status Dates: Select the date on which the Transaction turns active.
5. Select Continue. A success message appears with the name of the newly created
Transaction.
6. Select Finish.

8-2
 Chapter 8
Configuring Transaction

You can delete a Transaction configuration from the same page. Search for the transaction you
want to delete and select More Options, and then select Delete.

Note:
You cannot delete a transaction that is already associated with a Transaction Group.

List of Pre-configured Transactions

Transaction Types that are necessary to perform the initial set up of Oracle Financial Services
Cloud services are available out-of-the-box. A total of 101 transactions, across various
domains and transaction categories are available for selection in Oracle Financial Services
Cloud. You need not configure Transactions for these transaction types.
The following table lists all the transactions that are available as part of Day 0 configurations:

Table 8-1 Transactions

Transaction Short Transaction Name Description Transaction Category

Name
Crt Operator Create Operator Create an Operator Party
Rd Operator Read Operator Read an Operator Party
Upd Operator Update Operator Update an Operator Party
Rd Operator Rls Read Operator Read Operator Party
Relationships Relationships
Crt Cmp Hierarchy Create Company Create a Company Company
Hierarchy Hierarchy
Rd Cmp Hierarchy Read Company Read a Company Company
Hierarchy Hierarchy
Upd Cmp Hierarchy Update Company Update a Company Company
Hierarchy Hierarchy
Crt Cmp Create Company Create a Company Company
Rd Cmp Read Company Read a Company Company
Upd Cmp Update Company Update a Company Company
Rd Cmp Rls Read Company Read Company Company
Relationships Relationships
Crt Employee Create Employee Create an Employee Party
Rd Employee Read Employee Read an Employee Party
Upd Employee Update Employee Update an Employee Party
Crt Cf Create Configuration Create a Configuration Configuration
Rd Cf Read Configuration Read a Configuration Configuration
Upd Cf Update Configuration Update a Configuration Configuration
Del Cf Delete Configuration Delete a Configuration Configuration
Crt Cf Tnt Movement Create Configuration Create a Configuration Configuration
Tenant Movement Tenant Movement
Rd Cf Movement Read Configuration Read a Configuration Configuration
Movement Movement
Crt Cf Unload Create Configuration Create a Configuration Configuration
Unload Unload

8-3
 Chapter 8
Configuring Transaction

Table 8-1 (Cont.) Transactions

Transaction Short Transaction Name Description Transaction Category

Name
Rd Cf Rls Read Configuration Read Configuration Configuration
Relationships Relationships
Crt Cmp Id Gn Pw Create Company Id Create a Company Id Tenant
Generation Preview Generation Preview
Rd Cmp Id Gn Pw Read Company Id Read a Company Id Tenant
Generation Preview Generation Preview
Crt Cmp Id Gn Cf Create Company Id Create a Company Id Tenant
Generation Generation
Configuration Configuration
Rd Cmp Id Gn Cf Read Company Id Read a Company Id Tenant
Generation Generation
Configuration Configuration
Upd Cmp Id Gn Cf Update Company Id Update a Company Id Tenant
Generation Generation
Configuration Configuration
Del Cmp Id Gn Cf Delete Company Id Delete a Company Id Tenant
Generation Generation
Configuration Configuration
Crt User Grp Id Gn Cf Create User Group Id Create a User Group Id Tenant
Generation Generation
Configuration Configuration
Rd User Grp Id Gn Cf Read User Group Id Read a User Group Id Tenant
Generation Generation
Configuration Configuration
Upd User Grp Id Gn Cf Update User Group Id Update a User Group Id Tenant
Generation Generation
Configuration Configuration
Del User Grp Id Gn Cf Delete User Group Id Delete a User Group Id Tenant
Generation Generation
Configuration Configuration
Crt User Grp Id Gn Pw Create User Group Id Create a User Group Id Tenant
Generation Preview Generation Preview
Rd User Grp Id Gn Pw Read User Group Id Read a User Group Id Tenant
Generation Preview Generation Preview
Rd Employee Rls Read Employee Read Employee Party
Relationships Relationships
Rd Tnt Read Tenant Read a Tenant Tenant
Upd Tnt Update Tenant Update a Tenant Tenant
Crt Tnt Create Tenant Create a Tenant Tenant
Crt Tnt Cmp Id Gn Cf Rl Create Tenant Company Create a Tenant to Tenant
Id Generation Company Id Generation
Configuration Configuration
Relationship Relationship
Rd Tnt Cmp Id Gn Cf Rl Read Tenant Company Read a Tenant to Tenant
Id Generation Company Id Generation
Configuration Configuration
Relationship Relationship

8-4
 Chapter 8
Configuring Transaction

Table 8-1 (Cont.) Transactions

Transaction Short Transaction Name Description Transaction Category

Name
Upd Tnt Cmp Id Gn Cf Update Tenant Company Update a Tenant to Tenant
Rl Id Generation Company Id Generation
Configuration Configuration
Relationship Relationship
Del Tnt Cmp Id Gn Cf Rl Delete Tenant Company Delete a Tenant to Tenant
Id Generation Company Id Generation
Configuration Configuration
Relationship Relationship
Crt Tnt User Grp Id Gn Create Tenant User Create a Tenant to User Tenant
Cf Rl Group Id Generation Group Id Generation
Configuration Configuration
Relationship Relationship
Rd Tnt User Grp Id Gn Read Tenant User Group Read a Tenant to User Tenant
Cf Rl Id Generation Group Id Generation
Configuration Configuration
Relationship Relationship
Upd Tnt User Grp Id Gn Update Tenant User Update a Tenant to User Tenant
Cf Rl Group Id Generation Group Id Generation
Configuration Configuration
Relationship Relationship
Del Tnt User Grp Id Gn Delete Tenant User Delete a Tenant to User Tenant
Cf Rl Group Id Generation Group Id Generation
Configuration Configuration
Relationship Relationship
Crt User Grp Id Gn Create User Group Id Create a User Group Id Tenant
Generation Generation
Rd User Grp Id Gn Read User Group Id Read a User Group Id Tenant
Generation Generation
Crt Cmp Id Gn Create Company Id Create a Company Id Tenant
Generation Generation
Rd Cmp Id Gn Read Company Id Read a Company Id Tenant
Generation Generation
Rd Tnt Rls Read Tenant Read Tenant Tenant
Relationships Relationships
Crt Txn Grp Cf Txn Cf Rl Create Transaction Create a Transaction Transaction
Group Configuration Group Configuration to
Transaction Transaction to Group
Configuration Configuration
Relationship Transaction
Configuration
Relationship
Rd Txn Grp Cf Txn Cf Rl Read Transaction Group Read a Transaction Transaction
Configuration Group Configuration to
Transaction Transaction to Group
Configuration Configuration
Relationship Transaction
Configuration
Relationship

8-5
 Chapter 8
Configuring Transaction

Table 8-1 (Cont.) Transactions

Transaction Short Transaction Name Description Transaction Category

Name
Upd Txn Grp Cf Txn Cf Update Transaction Update a Transaction Transaction
Rl Group Configuration Group Configuration to
Transaction Transaction to Group
Configuration Configuration
Relationship Transaction
Configuration
Relationship
Del Txn Grp Cf Txn Cf Delete Transaction Delete a Transaction Transaction
Rl Group Configuration Group Configuration to
Transaction Transaction to Group
Configuration Configuration
Relationship Transaction
Configuration
Relationship
Crt Txn Grp Cf Create Transaction Create a Transaction Transaction
Group Configuration Group Configuration
Rd Txn Grp Cf Read Transaction Group Read a Transaction Transaction
Configuration Group Configuration
Upd Txn Grp Cf Update Transaction Update a Transaction Transaction
Group Configuration Group Configuration
Del Txn Grp Cf Delete Transaction Delete a Transaction Transaction
Group Configuration Group Configuration
Crt Txn Grp Cf Hierarchy Create Transaction Create a Transaction Transaction
Group Configuration Group Configuration
Hierarchy Hierarchy
Rd Txn Grp Cf Hierarchy Read Transaction Group Read a Transaction Transaction
Configuration Hierarchy Group Configuration
Hierarchy
Upd Txn Grp Cf Update Transaction Update a Transaction Transaction
Hierarchy Group Configuration Group Configuration
Hierarchy Hierarchy
Del Txn Grp Cf Delete Transaction Delete a Transaction Transaction
Hierarchy Group Configuration Group Configuration
Hierarchy Hierarchy
Rd Txn Type Read Transaction Type Read a Transaction Type Transaction
Crt Txn Cf Create Transaction Create a Transaction Transaction
Configuration Configuration
Rd Txn Cf Read Transaction Read a Transaction Transaction
Configuration Configuration
Upd Txn Cf Update Transaction Update a Transaction Transaction
Configuration Configuration
Del Txn Cf Delete Transaction Delete a Transaction Transaction
Configuration Configuration
Rd Txn Grp Cf Rls Read Transaction Group Read Transaction Group Transaction
Configuration Configuration
Relationships Relationships
Rd Txn Cf Rls Read Transaction Read Transaction Transaction
Configuration Configuration
Relationships Relationships
Crt User Grp Create User Group Create a User Group Entitlements

8-6
 Chapter 8
Configuring Transaction

Table 8-1 (Cont.) Transactions

Transaction Short Transaction Name Description Transaction Category

Name
Rd User Grp Read User Group Read a User Group Entitlements
Upd User Grp Update User Group Update a User Group Entitlements
Crt User Grp User Rl Create User Group User Create a User Group to Entitlements
Relationship User Relationship
Rd User Grp User Rl Read User Group User Read a User Group to Entitlements
Relationship User Relationship
Upd User Grp User Rl Update User Group User Update a User Group to Entitlements
Relationship User Relationship
Del User Grp User Rl Delete User Group User Delete a User Group to Entitlements
Relationship User Relationship
Crt User Grp Hierarchy Create User Group Create a User Group Entitlements
Hierarchy Hierarchy
Rd User Grp Hierarchy Read User Group Read a User Group Entitlements
Hierarchy Hierarchy
Upd User Grp Hierarchy Update User Group Update a User Group Entitlements
Hierarchy Hierarchy
Del User Grp Hierarchy Delete User Group Delete a User Group Entitlements
Hierarchy Hierarchy
Crt User Grp Txn Grp Cf Create User Group Create a User Group to Entitlements
Rl Transaction Group Transaction Group
Configuration Configuration
Relationship Relationship
Rd User Grp Txn Grp Cf Read User Group Read a User Group to Entitlements
Rl Transaction Group Transaction Group
Configuration Configuration
Relationship Relationship
Upd User Grp Txn Grp Update User Group Update a User Group to Entitlements
Cf Rl Transaction Group Transaction Group
Configuration Configuration
Relationship Relationship
Del User Grp Txn Grp Cf Delete User Group Delete a User Group to Entitlements
Rl Transaction Group Transaction Group
Configuration Configuration
Relationship Relationship
Rd User Grp Rls Read User Group Read User Group Entitlements
Relationships Relationships
Crt Btch Executor Create Batch Executor Create a Batch Executor Tenant
Crt Btch Timer Create Batch Timer Create a Batch Timer Tenant
Crt Counter Btch Create Counter Batch Create a Counter Batch Tenant
Rd Btch Schdr Read Batch Scheduler Read a Batch Scheduler Tenant
Upd Btch Internal Update Batch Internal Update a Batch Internal Tenant
Upd System Tnt Update System Tenant Update a System Tenant Tenant
Upd System User Update System User Update a System User Tenant
Upd Tnt Update Tenant Update a Tenant Tenant
Rd System Entity Read System Entity Read a System Entity Tenant
Counter Cons Counter Consolidated Counter Consolidated
Rd System User Read System User Read a System User Tenant

8-7
 Chapter 8
Creating Transaction Group

Table 8-1 (Cont.) Transactions

Transaction Short Transaction Name Description Transaction Category

Name
Del Employee Delete Employee Delete an Employee Party
Del Operator Delete Operator Delete an Operator Party
Crt UI Exp Cons Create UI Experience Create a UI Experience Tenant
Consolidated Consolidated
Crt Entity Counter Dtl Create Entity Counter Create an Entity Counter Tenant
Set Detail Set Detail Set
Crt File Virus Scan Mst Create File Virus Scan Create a File Virus Scan Tenant
Master Master
Crt Functional Btch Create Functional Batch Create a Functional Tenant
Force Executor Force Executor Batch Force Executor

Creating Transaction Group

A Transaction Group is a group that bundles one or more Transaction configurations that can
be administered as a convenient single unit. Operators with appropriate entitlements need to
create, setup, and manage Transaction Groups to enable fine-grained entitlement provisioning.
You can bundle similar service capabilities together by adding the related Transactions to a
Transaction Group (as needed by specific job roles).
Creating Transaction Group in Oracle Financial Services Cloud includes two steps:
1. Add Identification
2. Select Transactions

Note:
Transaction Group configuration can be moved from one tenancy to another using
Configuration Movement. Hence select a Config ID before proceeding with this
procedure.

Follow this procedure to create a new transaction group.

1. Select the Menu and select Entitlements, and then select Transaction Group.
2. In the Transaction Group page, select Add.
3. In the Add Identification page of Creating Transaction Group, enter the following
details:
a. Enter Name of the Transaction Group.
b. Enter Long Name of the Transaction Group.
c. (Optional) Enter Description of the Transaction Group.
d. (Optional) In Set Status Dates section, select Active date for the Transaction Group.

8-8
 Chapter 8
Creating Transaction Group

Note:
If you do not select a date, the Transaction Group becomes active on the
same day.

4. Select Continue.
5. In the Select Transactions page, select the transaction configurations to bundle in the
Transaction Group and select Continue.

Note:
All transactions that are configured using Transaction page are available for
selection in the list. If a Transaction is configured under a different Config ID, you
are not allowed to select it in this step.

6. Select Finish in the Success message displayed.

You can associate a Transaction Group to other Transaction Groups, thereby creating a
hierarchy of Transaction Groups. See Creating Transaction Group Hierarchy.
If no longer required, you can delete a Transaction Group from the same page. Search for the
Transaction Group you want to delete, and select More Options, and then select Delete.

Note:
You cannot delete a Transaction Group under following conditions:
• If the Transaction Group is part of a Transaction Group hierarchy
• If the Transaction Group is associated with a User Group
• If the Transaction Group has associated Transaction Configurations

Creating Transaction Group Hierarchy

You can create a hierarchy of Transaction Groups by associating one Transaction Group to
another.

Note:
You can associate a Transaction Group with a new Transaction Group or with an
existing Transaction Group.

Ensure that the Transaction Groups that you want to associate are already created and active,
are of the same type, and are not associated to the same Transaction Group as part of another
association.
Follow this procedure to associate a Transaction Group with another Transaction Group.
1. From the Menu, select Entitlements, and then select Transaction Group.
2. Select View All to view a list of all Transaction Groups. If you are looking for a specific
Transaction Group, you can use the Search facility.

8-9
 Chapter 8
Creating User Group

Note:
The list indicates whether a Transaction Group is already a part of a Transaction
Group hierarchy or not. In case of a parent Transaction Group, you can expand
and view its hierarchy and associate a Transaction Group at any of the levels of
the hierarchy.

3. Select More Options of the parent Transaction Group and select Add Transaction
Group.
4. In Setup page, select one of the following options and select Continue.
• Create New Transaction Group: If you select this option, you can create a new
Transaction Group and then associate it with the selected Transaction Group. See
Creating Transaction Group.
• Using an Existing Transaction Group: If you select this option, you can select a
Transaction Group from the list and select Continue.
5. Select Finish.
The Transaction Groups are now associated with each other.

Creating User Group

A User Group groups one or more users who can be administered as a convenient single unit.
You can associate a User Group to one or more Transaction Groups, thereby allowing all users
in the User Group to access all Transactions in all associated Transaction Groups.

Note:
Verify if there is a valid User Group Id Generation Configuration created and
associated with the tenant, before proceeding with the creation of a User Group.

User Group creation involves six steps:

1. Add Identification
2. ID Generation
3. Select Operations Company
4. Select Local User Flag
5. Select Users
6. Manage Associations
Follow this procedure to create a user group.

Note:
Select a Config ID before performing the following procedure.

1. From the Menu, select Entitlements, then select User Group.

2. Select Add.

8-10
 Chapter 8
Creating User Group

3. In the Add Identification step, enter the following details:

a. Enter Name of the User Group.
b. Enter Long Name of the User Group.
c. (Optional) Enter Description of the User Group.
d. (Optional) In Set Status Dates, select Active date for the User Group.

Note:
If you do not select a date, the User Group becomes active on the same day.

e. Select Continue.
4. In the ID Generation step, you can either see the automatically generated identifier or
manually enter a value based on the User Group ID Generation configuration that is
associated with the tenant. If the ID Generation is Automatic, the page automatically
displays an identifier, whereas if the ID Generation is Manual, enter a valid identifier for the
User Group.

Note:
While manually entering an identifier, system validates the ID against the User
Group ID Generation configuration that is associated with the tenant. If the
validation fails, an error message appears. For more information on ID
Generation, see Related Links.

5. In the Select Operations Company step, select the Operations Company to which you
want to associate the User Group and select Continue.
6. (Optional) In the Select Local User Flag step, slide the Select from local Users toggle
button to the right and select Continue. This decides whether you can add operators
belonging to the selected Operations Company only, or any operator from the entire
hierarchy of the Operations Company.
7. In the Select Users step, select the Users to add to the User Group and select Continue.
8. (Optional) In the Manage Associations step, you can associate one or more Transaction
Group to the User Group. To do this, follow these steps:
a. Expand Transaction Groups section and select Add.
b. Search and select a Transaction Group to associate with the User Group.
c. Select Continue.
d. (Optional) If you want to associate more Transaction Groups to the User Group, select
Suggested tab and repeat this procedure.
9. In the Success message, select Finish.

8-11
 Chapter 8
Creating User Group

Note:
Once a User Group is created, you can perform the following updates to it:
• Add or remove Users to the User Group
• Add or remove Transaction Group Associations to the User Group

Related Topics
• Configuring User Group ID Generation
• Associating User Group ID Generation Configuration with Tenant
• Associating Transaction Group with User Group

Adding Users to User Group

Ensure that the User Groups that you want to associate are already created and in active or in
progress state, and are of the same type.
Follow this procedure to associate a User Group with a User.
1. From the Menu, select Entitlements, and then select User Group.
2. Select View All or type in at least three characters and select Search to find the User
Group.
3. Select More Options of the User Group and then select Go to Details.
4. In the Details tab, expand Users.
5. Select Edit Users.
6. In Updating User Group, select the users to associate and select Finish.
The selected Users are associated with the User Group.

Creating User Group Hierarchy

Ensure that the User Groups that you want to associate are already created and active, and
are of the same type. You can associate a User Group with either a new User Group or an
existing User Group.

Note:
You cannot associate a User Group to another User group if it has already been
associated to another User Group, or is part of another User Group hierarchy.

Follow this procedure to associate a User Group with another User Group.
1. From the Menu, select Entitlements, and then select User Group.
2. Select View All to view a list of all User Groups. If you are looking for a specific User
Group, you can use the Search facility.

8-12
 Chapter 8
Associating Transaction Group with User Group

Note:
The list indicates whether a User Group is already a part of a User Group
hierarchy or not. In case of a parent User Group, you can expand and view its
hierarchy and associate a User Group at any of the levels of the hierarchy.

3. Select More Options of the User Group and then select Add User Group.
4. In Setup page, select one of the following options and select Continue.
• Create New User Group: If you select this option, you can create a new User Group
and then associate it with the selected User Group. See Creating User Group.
• Using an existing User Group: If you select this option, you can select a User Group
from the list and select Continue.
5. Select Finish.
The User Groups are now associated with each other.

Associating Transaction Group with User Group

To grant explicit rights to a User Group, select a Transaction Group and assign it to the User
Group. Each Operator or User in the User Group is granted access rights to every Transaction
in the assigned Transaction Group.

Note:
Ensure that the User Group and Transaction Group that you want to associate are
already created and active, and are of the same type.

Follow this procedure to associate a Transaction Group with a User Group.

1. From the Menu, select Entitlements, and then select User Group.
2. Select View All or type in at least three characters and select Search to find the User
Group.
3. Select More Options of the User Group and then select Go to Details.
4. Select Associations tab and then select Add.
5. In the Suggested tab, expand Required.
6. Expand Transaction Group Configs, and under Transaction Group, select Add.
7. Select the Transaction Group to associate and select Done.
8. In Manage Associations page, view and manage the new Transaction Group, previously
associated Transaction Group, or the company to which the User Group is associated to.
9. Select Finish.
The selected Transaction Group is associated with the User Group. All users in the User Group
are now able to perform all transactions associated with the Transaction Group.

8-13
9
Known Issues in Oracle Financial Services
Cloud
The following table lists the known issues and workaround in Oracle Financial Services Cloud:

Table 9-1 Known Issues

Issue Workaround
Paragraph border styling is applied to every line of Place the paragraph in a table cell and apply
the paragraph. element-based styling to apply border style for the
table-cell.
If you define element based border styling to a Split the paragraphs across multiple contents
couple of paragraphs of a content with many instead of defining all the paragraphs in a single
paragraphs, then in the PDF output, it leaves extra content.
white space between the paragraphs.
The human readable portion of barcode displays in
PDF output, but is not displayed in HTML output.
You must specify Unit while setting the Line
Height Style Attribute. You cannot select Unit Less
while setting the Line Height Style Attribute.
Empty space is displayed instead of radius when
you generate a PDF with components that have
border radius and border style set to double,
groove, inset or outset.
An Active Status date cannot be set on a data 1. Edit the data element.
element if you first edit the data element.
2. Navigate back to the data element.
3. Set the Active Status Date.

The PDF preview of a Communication Package is Disable the emulator mode.

not displayed while using Google Chrome in
emulator mode.
The Configuration Movement screen always
displays the status as successful.
In the event of a Configuration Movement failure,
the Configuration movement screen still shows a
successful status from the last successful
configuration movement.
The association of an Operations Company to a
User Group is mandatory and irrevocable. Once
the association is established, you cannot edit the
Operation Company.

9-1
 Chapter 9

Table 9-1 (Cont.) Known Issues

Issue Workaround
Company ID Generator issues: When initial tenancy configuration is performed,
• If the Company ID Generator is set to manual, Company ID Generator pattern should be set to
it displays an error. Automatic.
• If the Company ID Generator is set to manual
and the Configuration Id is closed, it is not
possible for that instance of
CompanyIdGenConfig to be changed to
Automatic.
• Also you cannot change the
CompanyIdGenConfig feature associated to
the tenant.
Oracle Financial Services Cloud and Oracle Cloud Administrators must manually perform the following
Infrastructure Identity and Access Management tasks to synchronize changes across Oracle Cloud
(OCI IAM) do not synchronize automatically. Infrastructure Identity and Access Management
(OCI IAM) and Oracle Financial Services Cloud:
1. Manually remove the accounts from Oracle
Financial Services Cloud after they are
removed from OCI IAM.
2. Manually replicate the changes such as email
addresses and other personal information
(phone number; address, employee number
etc.) associated with the user when you make
the changes in either OCI IAM or Oracle
Financial Services Cloud.

Configuration Movement does not show date and

time of last successful configuration movement.
The maximum number of nodes that you can set
for Company hierarchy is 1000.

9-2
10
Financial Services Cloud Support
Raise a service request on https://support.oracle.com if you have any queries related to
services on the Financial Services Cloud platform.

Send us your comments

Oracle welcomes your comments and suggestions on the quality and usefulness of this
publication. Your input is an important part of the information used for revision.
• Did you find any errors?
• Is the information clearly presented?
• Do you need more information? If so, where?
• Are the examples correct? Do you need more examples?
• What features did you like most about this manual?
If you find any errors or have any other suggestions for improvement, indicate the title and part
number of the documentation along with the chapter/section/page number (if available) and
contact the Oracle Support.
Before sending us your comments, you might like to ensure that you have the latest version of
the document wherein any of your concerns have already been addressed. You can access My
Oracle Support site that has all the revised/recently released documents.

10-1