1. Implementation Guide
  2. Set Up Launch Cloud Service

3 Set Up Launch Cloud Service

Before You Begin

This section describes the additional setup tasks you can do before implementing Launch.

Set Up VB Studio

You can set up VB Studio to extend Oracle Cloud applications. An application extension is an artifact that enables you to extend certain Oracle Cloud applications to meet your business needs. You deploy an application extension to an Oracle Cloud applications instance. Only one VB Studio instance can be provisioned in an Oracle Cloud account.

By default, a VB Studio instance is provisioned with your first Oracle Cloud Applications *-TEST instance that your organization's members can use to develop application extensions. If you need to use VB Studio with a different Oracle Cloud Applications instance, file a service request.

Oracle deletes the VB Studio instance associated with your *-TEST instance and creates a new VB Studio instance in your preferred identity domain. For more information, see Set Up VB Studio.

Define Your Enterprise Structure

Based on other Oracle Cloud applications that are being provisioned, you can define your enterprise structure, such as, Legal Entity, Business Unit, Primary Ledger, and Chart of Accounts among others.

For more information, see Enterprise Structures Business Process Model.

The following table lists the mandatory tasks you need to set up before you begin implementing Launch.

Table 3-1 Set Up Tasks

Section isMandatory

Set Up Default Item Organization

Yes

Set Up Profile Options

Mandatory profile options are documented in the section.

Set Up Search Index

Yes

Set Up Search Tags in Offer

No

Set Up Oracle Content Management

Yes

Set Up Regional Values

No

Set Up Business Configuration Values

Yes

Set Up Business Units

No

Enable Auditing in Sales Cloud

No

Set Up Design Time Restrictions Through Entity Profiles

No

Choose Your Deployment Options

Launch supports the multiple deployment options:
  • Launch integrated into Digital Business Experience stack (DBE).
  • Launch integrated into non-Digital Business Experience stack.

There are certain features applicable to DBE deployments that will have the DBE solution level validations and mandatory properties during catalog definitions design. However, for non-DBE deployments these properties may not be relevant. With the introduction of a Feature flag, we can now absolve non-DBE deployments from using DBE features or restrictions. By default, the Launch application will support DBE stack deployment. For non-DBE stack deployment, we now can set this Feature flag using a REST end point to inactive DBE features as a part of Launch application setup. Once you have set this switch, you can't toggle them.

For example, there are certain DBE specific fields like billing type, billing service type, service instance, composition type, fulfillment item code, Time based offer etc. on product offering which are required for the DBE solution. When switch is off, then these DBE specific fields and validations will not be available.

Customer Action:
  • DBE Deployments - No action required
  • Non-DBE Deployments - You should raise a Service Request with Oracle Support to disable the DBE functionality before you start using the application.

Note:

This is a one-time action and cannot be changed once you start using the application.

Set Up Default Item Organization

You must set up a default item organization for Oracle SCM Item Sync. You can integrate with Oracle SCM by implicitly creating a Product Information Management item for every product offering created in Launch Cloud Service.

To set up a default item sync to Oracle SCM, you must perform the two following steps:

  1. Set Up Item Organization in Oracle SCM

  2. Configure Item Organization for Default Item Creation

Here's how you can do it.

Step 1: Set Up Item Organization in Oracle SCM

You must be a user with the Application Implementation Consultant role to be able to view and perform the list of tasks required to set up the item organization.

To set up an item organization:

  1. Go to Navigator > My Enterprise > Setup and Maintenance.

  2. In Setup and Maintenance, click Tasks > Search and enter Manage Item Organizations.

  3. On the Manage Item Organizations page, Search Results section, click Create from the Actions drop-down list.

  4. On the Create Item Organization page, select the Create new check box.

  5. Enter information for mandatory fields such as Name and Organization and provide additional details such as Management Business Unit, Primary Ledger, Legal Entity, Legal Addresses, if already setup. If not, you may leave out the additional fields.

  6. Click Next.

  7. On the Manage Item Organization Parameters page, select your item master organization that you provided earlier from the Item Master Organization drop-down list.

  8. Click Save and Close.

Step 2: Configure Item Organization for Default Item Creation

Now that the item or inventory organization creation is complete, the same must be configured in the root item class security to allow item creation against this item or inventory organization.

To set up item class security for the new item or inventory organization:

  1. Go to Navigator > My Enterprise > Setup and Maintenance.

  2. In Setup and Maintenance, click Tasks > Search and enter Manage Item Classes.

  3. On the Manage Item Classes page, select the Root Item Class and click Edit.

  4. On the Edit Item Class page, go to the Templates and Formats subtab.

  5. On the Item Templates subtab, select any template, for example, Finished Goods template, edit and make it the default.

  6. For the selected template, update the following attributes:

    1. Item Status: Active

    2. Lifecycle Phase: Production

    3. Primary Unit of Measure

    4. Positive Deviation Factor

    5. Negative Deviation Factor

  7. Click Save and Close.

Set Up Profile Options

A profile is a set of configurable options that affect the way your application looks and behaves. As a system administrator, you can control how your application operates by setting the profile options to the required values.

Here's how you can go about it:

  1. Go to Navigator > My Enterprise > Setup and Maintenance.

  2. In Setup and Maintenance, click Tasks > Search, and enter Manage Administrator Profile Value in the Search field.

  3. On the Manage Administrator Profile Value page, search for the profile codes as provided in the table and set the Site Profile Value for each of the profile codes.

    Table 3-2 Profile Options

    Profile Option Code Description Is Mandatory? Turn Off/Turn On

    ORA_ATC_DEFAULT_ORG_CODE

    Organization code for creating an item in SCM for the Product Offers created in Launch.

    Yes

    N/A

    ORA_ATC_EXPORT_I N_MEMORY_COUNT

    Used for the export functionality to define the number of objects that can be kept in memory. The default value is 1000 that you may change if required.

    No

    		 N/A

    ORA_ATC_IMPORT_T HREAD_COUNT

    This profile option determines the number of parallel threads that run during the import. The default value is 10.

    Criteria to configure the profile option:
    • Number of ESS servers configured on the instance: You can get this information by contacting Oracle Support.
    • Other active processes: Other application processes that may be simultaneously running on this server and utilizing the same ESS servers.

    Note: If the Launch Cloud Service import is the only process running on the instance, you can configure the number of threads up to 10 times the number of ESS servers. If there are other processes likely to be running simultaneously, reduce the number of threads proportionally.

    No

    N/A

    ORA_FND_SEARCH_ EXT_ENABLED

    Validate if this has been set.

    Yes

    N/A

    ORA_ATC_LAUNCH_A PPROVAL_ VOTE_PERCENTAGE

    The percentage range is between 0 and 100.

    Defines the voting percentage required to mark the request as approved during parallel approvals. The default is 100 percent, which means all approvals are required.

    No

    N/A

    ORA_ATC_LAUNCH_A PPROVAL_TYPE
    Defines the approval type for offers. The default is parallel.
    • Parallel
    • Sequential

    Note:If you define the approval type as sequential, you must not override the default approver during offer confirmation. Doing so will change the approval type to parallel.

    No

    		 N/A

    ORA_FND_APPROVALS

    Enables the UI that's optimized for finding and acting on approvals (This is used to enable the Approval Card in the Tools section).

    Yes

    Set the profile value as Yes to enable the Approvals UI under Tools.

    FND_APPROVALS_OSCS

    Enables approval tasks to be ingested into Oracle Search Cloud Service (The approvals UI is based on elastic search. The ingestion will happen only if you enable this profile option).

    Yes

    Set the profile value as Yes to enable elastic search and the Approvals UI.

    ORA_ATC_LAUNCH_A PVL_VTPTG

    The percentage range is between 0 and 100.

    Defines the voting percentage required to mark the request as approved during parallel approvals. The default is 100 percent, which means all approvals are required.

    No

    Set the percentage for a successful parallel approval process.

For more information on creating and setting profile option values in the Setup and Maintenance work area, see Create and Edit Profile Options.

Set Up Search Index

Use this topic to set up elastic search on the landing page of top-level entities.

You must run the Oracle Enterprise Scheduler job to create the index in the Search instance configured in the environment. The Oracle Enterprise Scheduler job creates the index in Search instance and also performs the initial ingestion. The records which are already created will be ingested once the Oracle Enterprise Scheduler job is completed.

Here are the details of the Oracle Enterprise Scheduler job:

  • Oracle Enterprise Scheduler job name: ESS job to create index definition and perform initial ingest to OSCS.

  • Index name parameter: fa-crm-productcatalog.

Ensure that the Oracle Enterprise Scheduler job is completed successfully. If the job fails or the elastic search doesn't work, check for the search instance availability. To check the search instance availability, run the Oracle Enterprise Scheduler job named ESS process to check Search Cloud Service availability.

You can set up elastic search for the following entities:

  • Initiative

  • Product Specification

  • Product Offering

  • Catalog

  • Price List

  • Promotion

  • Rules

  • Product Line

For information on how to run scheduled processes, see What are scheduled processes?.

Set Up Search Tags in Offer

Use this topic to set up search tags for an offer with keywords used to discover offers by type, specialty or domain.

Setting up search tags improves search capability over the existing one. Keywords provide relevance to the search and in turn improve the user experience, especially for non-technical persons.

Here's how to set up a search tag:

  1. Click Navigator > My Enterprise > Setup and Maintenance.
  2. Search for the Manage Standard Lookups task.
  3. Search for the lookup code ORA_ATC_SEARCH_TAGS.
  4. Add the values 5G, BYOD, Christmas and so on.

Note:

Use the same Lookup Code and Meaning values for ORA_ATC_SEARCH_TAGS.

Set Up Oracle Content Management

The Integration between Launch and a Headless Third Party Content Management System (CMS) is required to manage content across your ecosystem. For more details, see Launch Cloud Service Integration Guide.

Set Up Regional Values

Use this topic to specify the ledger values for product offer price. As an administrator, you must complete this setup in the application to enable pricing for a region.

Set General Ledger ID Values

To enable pricing, obtain the required regional values for Money, Tax, and General Ledger attributes.

  1. Sign in as an Administrator.

  2. Go to Navigator > My Enterprise > Setup and Maintenance.

  3. In Setup and Maintenance, click Tasks > Search , and enter Manage Standard Lookups in the Search field.

  4. Search for the lookup type provided in the following table and add the regional values.

    Table 3-3 Lookup Types

    Lookup Type Description

    ORA_ATC_GLID

    General ledger identifier for the region. If a ledger is already set up through the task Manage Primary Ledgers, update the same ledger ID.

Set Up Business Configuration Values

Use this topic to set up business configuration values for catalog entity.

You can configure business setups that are common across design time and runtime systems to ensure the eco system setups are defined once and published into target systems. This facilitates frictionless and agile customer onboarding and enables to centrally introduce and manage your common business setups rather than doing it in each and every runtime system. Additionally, this capability reduces configuration efforts, aids in agility, and brings in consistency across the enterprise.

The seeded configuration items are documented below. All the configurations can be updated and extended by customers.

Table 3-4 Seeded Configuration Items

Configuration Characteristics Default Configuration Characteristics Value Description

Customer Type

Existing Subscriber

New Subscriber

Customer Type values are used as parameters while defining eligibility rules.

Pricelist Type

Business

Residential

Price list Type values are used to classify price list.

ELIGIBILITY_PARAMETER

Channel Code

Country

Customer Type

Pricelist Type

Market Segment Code

Retail Store Code

Account Type

Credit Score

Black List

Eligibility parameters values that are permissible to define eligibility rules.

ELIGIBILITY_OPERATOR

Contains

Equals

Not contains

Not Equals

Not starts with

Start with

In

Is null

Between

Less than

Less than or equal to

Greater than

Greater than or equal to

Eligibility operator values that are permissible to define eligibility rules.

Country

No default value. Can be updated with any standard country code defined in Fusion.

Country code values used to define eligibility rules. Country code values used to define eligibility rules. See the list of available countries with loqate geography reference data in the Oracle Help Center link below the table.

Geography validations are triggered while creating the common business configurations and using them in the promotion.

  • The country code and various geographical levels of the country are validated.
  • The promotions criteriaPara and criteriaValue are validated with the common business configurations and geographical levels.

Account Type

No default value. To be setup by the customer.

Account type values are used as parameters to define eligibility rules.

Credit Score

No default value. To be setup by the customer.

Credit score values are used as parameters to define eligibility rules.

Black List

No default value. To be setup by the customer.

Black list values are used as parameters to define eligibility rules.

IMPACT_CATEGORY

Not applicable

Impact categories are used in attribute-based pricing using value maps to group rules .

As mentioned above, geography validations are triggered while creating the common business configurations and using them in the promotion. However, you need to configure the country structure and hierarchy in fusion applications using the Manage Geographies task in customer data management. See How do I manage Geography Structures, Hierarchies, and Validation?.

For a list of available countries with loqate geography reference data, see List of Available Countries with Loqate Geography Reference Data.

Note:

Existing default configuration values can only be disabled or enabled. However, new values can be added, enabled and disabled.

Set Up Business Units

Use this topic to set up Business Units (BU) for using the BU association in Offers and Price lists.

Note:

Business unit setup is optional. You would need it only if you have an operational need of having multiple business units with exclusive product offers and pricelists for each.

A CSP organization can have many business units (BU) based on their regional and/or line of business that they operate upon. Having such segregations allow the CSP to manage and operate their operational and marketing needs - separated by their business units. Each BU can have its own set of catalog definitions for products and services and pricelists and/or can share the common ones based on how their BUs need to operate.

You must set up Business Units for using the BU association in Offer and Price lists.

Table 3-5 Profile Options to Set Up Multiple Business Units

Profile Option Code Description Is Mandatory? Turn Off/Turn On Details
HZ_ENABLE_MULTIPLE_BU_CRM Enable the multiple business units feature for Oracle Fusion Customer Relationship Management. Yes

Set the profile value as Yes to enable the multiple BU in Launch.

 -
HZ_DEFAULT_BU_CRM Specify the default business unit for Oracle Fusion Customer Relationship Management. No - To be set when you need to have a default BU associated to a Product Offering and Pricelist resource

The steps involved in setting up a business unit are shown below:

1. Create Organization > 2. Create Business Unit > 3. Create Resource Organization > 4. Create Resource User > 5. Associate BU and User to Organization > 6. Link Resource User to Security User (If Security User is already created).

Create Business Unit

You must be a user with the Application Implementation Consultant role to be able to view and perform the list of tasks required to set up a Business Unit.

To set up a Business Unit:
  1. Go to Navigator > My Enterprise > Setup and Maintenance.
  2. In Setup and Maintenance, click Tasks > Search, and enter Manage Business Units in the Search field.
  3. On the Manage Business Units page, Search Results section, click Create from the Actions drop-down list.
  4. On the Create Business Unit page, enter information for the mandatory fields such as Name and Default Set. Provide additional details such as Location and Manager, if needed. If not, you may leave out the additional fields. Provide Common as Default Set.
  5. Click Save and Close.

Create Resource Organization

You must create a resource organization to map resource user to multiple BU's. A resource organization can have multiple resource users and multiple BU's associated. All the user under an organization can access all its BU's.

To set up a Resource Organization:
  1. Go to Navigator > My Enterprise > Setup and Maintenance.
  2. In Setup and Maintenance, click Tasks > Search and enter Manage Internal Resource Organizations.
  3. On the Manage Internal Resource Organizations page, Search Results section, click Create from the Actions drop-down list.
  4. Select New Organization option and click next.
  5. Enter the organization Name.
  6. Create from the Actions drop-down list under Organization Usages.
  7. Select Resource Organization from the drop-down list and click finish.

Note:

This step can be skipped as we can create Resource Organization from Resource User create page as well.

Create Resource User

Create a Resource User for Business Unit association. This is required for the API to use Business Unit in offer and price list.

For more information, see "Create a Resource User".

Associate Business Unit to Resource User

Once the Business Unit and Resource User are created, associate the Resource User to Business Unit. Use the Resource Directory for User to BU association.

The Resource Directory offers detailed information about all the resources within the deploying organization. The Resource Directory also enables you to find and communicate with other resources, and to network and collaborate with them.

You use the Resource Directory to perform the following tasks:
  • View and modify your profile
  • View your organization, associated users, and business units
  • View information related to other organizations
  • View the profiles of other resources
You must perform the following steps to associate BU to the user:
  1. Log in to home page > Navigator > Resource Directory.
  2. Click Tasks.
  3. Click View Organizations.
  4. Search for the resource organization used while creating resource user.

  5. Drill in to the organization. You can see the organization profile with Members, Hierarchies, Teams, Business Units sub tabs.

    The resource users associated to organization can be viewed or added from Members sub tab. The business units associated or added to organization can be viewed from Business Units sub tab.

  6. Add the business unit under the business units sub tab using Add action.

All the users under Members sub tab can access all the BU under the Business Units sub tab.

Now, when you log in as the resource user, you can use the BU in offer and price list.

Enable and Configure Auditing for Launch Entities

Use this topic to configure auditing for Launch entities.

Auditing helps answering three specific questions - Who, what and when. Who took an action, on what data and when was it done. Auditing is about providing a history or chain of actions for any business data you work with - create, update, delete, export, import, or publish.

You need to enable auditing in Sales Cloud before configuring it for Launch entities.

Here's how you can enable auditing in Sales Cloud:

  1. Click Navigator > My Enterprise > Setup and Maintenance.
  2. Search for the Manage Auditing Policies task.
  3. Set Audit Level to Auditing for Oracle Fusion Applications.
  4. Save and close.

After you are done, you can record audit information on product specifications or product offerings. An audit log stores detailed change history information and can also be downloaded. It contains information about an action taken and the changes made to the specification - the date and time of the action, and the identity of the person taking the action.

Here's how you can configure auditing for an entity in Launch:

  1. Go to Administration > Audit trail > Manage auditing policies.
  2. In Audit Configurations, select either Product Offering or Product Specification as the entity type.
  3. In the Audit Status page, select the field resources or the sub resources you want to audit in the entity type.
  4. Click Update.

Set Up Design-time Restrictions Through Entity Profiles

Use this topic to set up design-time restrictions (supporting run-time capabilities) through entity profiles.

The modeling capabilities of design-time and run-time applications are common regardless of whether you publish to Oracle or non-Oracle run-time applications. However, there could be a gap between what could be modeled at design time as against what the application would actually use at run-time, depending on the service provider's ecosystem. You could then set modeling rules for design-time features available for a service provider, ensuring the design-time application follows the applied restrictions resulting in an error-free publishing to runtime applications. Such restrictions are based on the service provider's ecosystem and not on individual runtime applications. Which means, there could only be one restriction for the ecosystem and not for each runtime application. You can achieve this by setting up an entity profile.

Using the following two examples, you can set up an entity profile and follow some best practices:

  1. Example 1 - Rule: Restrict only one commitment term for the product offering entity of package type.
  2. Example 2 - Rule: Restrict one-time price.

Here's how to do it using Example 1.

Step 1: Create an entity profile of type customProfileSpecification

To create an entity profile:

  1. Define a valid ID and name to create the entity profile.
  2. Set the version to 1.0.
  3. Set the LifecycleStatus to In design.
  4. Set the @type to CustomProfileSpecificationOracle.
  5. Set the profileType to ENTITY_PROFILE.

Target product schema should be based on the entity restriction, such as, for productOfferingOracle, the @type value should be ProductOfferingOracle and the @schemaLocation value should be ProductOfferingOracle.yml. Similarly, you need to update type and schemaLocation values for other entities as well (ProductSpecificationOracle, PromotionOracle and so on ).

Step 2 : Create a restriction based on a condition

To create a restriction:

  1. Define a rule with characteristicType as RULE and relationshipType as AGGREGATION.
  2. Based on the name given in AGGREGATION, create a FEATURE characteristic (rule 1_info_productType_bundle).
  3. If the restriction has a condition, you need to define that condition in the feature characteristic with customProfileSpecCharRel as relationshipType with the value CONDITION.
  4. Create ATTRIBUTE based on the name given in the CONDITION type (condition_productType_bundle_package).
  5. In ATTRIBUTE, define the attribute name and value to satisfy the condition (attribute name defines the condition expression).
  6. Once the condition is satisfied, the respective restriction attribute (requires_term_type_commitmentTerm) is executed.

Here's how to do it using Example 2.

Step 1: Create an entity profile of type customProfileSpecification

To create an entity profile:

  1. Define a valid ID and name to construct the entity profile.
  2. Set the version to 1.0.
  3. Set the LifecycleStatus to In design.
  4. Set the @type to CustomProfileSpecificationOracle.
  5. Set the profileType to ENTITY_PROFILE.

Note:

Target product schema should be based on the entity restriction. For example, for productOfferingOracle, the @type value should be ProductOfferingOracle and the @schemaLocation value should be ProductOfferingOracle.yml. Similarly, you need to update type and schemaLocation values for other entities as well (ProductSpecificationOracle, PromotionOracle and so on ).

Step 2 : Create a restriction without conditions

To create a restriction:

  1. Define a rule with characteristicType as RULE and relationshipType as AGGREGATION.
  2. Based on the name given in AGGREGATION, create a feature characteristic with relationshipType set as EXCLUDES, REQUIRES or ALLOWED.
  3. Based on the name given in the feature characteristic, create ATTRIBUTE.

To see sample payloads for creating restrictions, see REST API Reference for Launch Cloud Service.

To view a list of design-time restriction properties and values used to create restrictions, see "Design-time Restriction Properties to Create Entity Profiles"in the Appendix.

Configure Oracle Cloud Infrastructure Object Store to Store Content

Prerequisites

Use this topic to understand how you can integrate OCI Object Store with Launch Cloud Service to manage content. The OCI Object store can be used as a default content repository in case you have not integrated Launch with your own third party Content Management system.

For more information, see "Integrate Launch with Third Party Content Management Systems".

Here are some prerequisites:

  • Users who want to use this feature must already have the OCI object store connection details.
  • The bucket having the the content must be authenticated earlier with a long term expiration date (this date decides when the authenticated URLS would expire), and must be named as bucket-launch-resource.
  • Ensure that all the images you need are stored in the images folder within the bucket, and all the documents needed are stored in the documents folder within the bucket.

    To know more about creating buckets and preauthenticated requests, see the tasks Object Storage Buckets and Object Pre-Authenticated Requests in the Oracle Cloud Infrastructure Documentation on Oracle Help Center.

Here are the steps:

  1. Create a new ObjectStorage API object.

    API: POST https://{CXIFHost}/admin/apis

  2. Create a new system descriptor.

    API: POST https://{CXIFHost}/admin/systemDescriptors

  3. Create a new connection descriptor.

    API: POST https://{CXIFHost}/admin/connectionDescriptors

    The endpoint URL field should be object-storage host url

    The endpoint URL must be indicated as https://<namespaceName>.objectstorage.<region>.oci.customer-oci.com/n/<namespaceName>.

    For example, if the tenancy namespace name is cxcomms and the object storage is in the region us-ashburn-1, configure the endpoint URL as https://cxcomms.objectstorage.us-ashburn-1.oci.customer-oci.com/n/cxcomms.

    You must configure authentication details to successfully connect to the OCI Object Storage. So, in fabric-facing-auth, configure the oci-http-signature details.

    To configure the oci-http-signature, you must configure the API Key. If you haven't, go to the user profile section in the OCI console and on the Resources tab, select API Keys and follow the onscreen instructions to create the API Key. After you successfully create the key, you'll be prompted to download the private key file and can also view the user OCID, tenancy OCID, fingerprint, and region.

    The following fields are mandatory in oci-http-signature:

    • user-ocid: OCID of the user
    • tenancy-ocid: OCID of the tenancy
    • fingerprint: Fingerprint of the API Key
    • private-key: Content of the private key file as a string

    Note:

    The system descriptor field must be the ID of the system descriptor you created earlier.
  4. Create a new routing criteria based on the path parameter storage-system-id.

    API: POST https://{CXIFHost}/admin/routingCriteria

    Ensure that the value os-cxcomms-us-ashburn-1 isn't changed and should remain fixed.

    Note:

    Save the value of the criterion-link field as UNIXXXXX.
  5. Update the gatekeepingule.

    After you create the API key, system descriptor and connection descriptor, a new gatekeepingrule is generated. You must update this gatekeepingrule with the new routing criteria that you created in the previous step.

    API: GET https://{CXIFHost}/admin/gatekeepingRules

    From the search results for obs-native in the endpoint name, get the ID of the corresponding record and use it to update gatekeepingrule using the following steps:

    API: PUT https://{CXIFHost}/admin/gatekeepingRules/{id}

    Reference link - admin/gatekeepingRules

  6. Storing the pre authenticated URL.

    You must store the pre authenticated URL using the following API Request.

    API: PUT https://{FAHost}/crmRestApi/atcProductCatalog/11.13.18.05/productCatalogManagement/v1/configStore/cms/bucket-launch-resource

    Note:

    The request should remain as above, only the value should be replaced with appropriate pre authenticated request.