So, you have created RTF template which has output in excel form.
But in the output, some of the columns are shown merged. Please see below column G and H are merged under SDO header -
So, you have created RTF template which has output in excel form.
But in the output, some of the columns are shown merged. Please see below column G and H are merged under SDO header -
We've seen the definition and structure of a custom ESS Job in Oracle Fusion here
Now let's see how to create a job set comprising of multiple ESS jobs.
ESS Job Set is useful when there's a need to run multiple ESS jobs for any activity (in sequence or parallel) in Oracle Cloud. Basically, the traditional Concurrent Request Set from EBS has been replaced with an ESS Job Set in Oracle ERP Cloud.
Let's see how to define an ESS Job Set.
Below example will create a job set which will run two HCM jobs shown below. Read Only initial parameter values come from the job set but non-read only parameters come from the job definition.
1. Identify the jobs to be included in ESS Job Set -
a. Generate Cloud Usage Metrics (seeded job)
b. XX HCM Job (custom job)
2. Run these jobs individually. This will ensure that the jobs are running without issues and users will be able to collect runtime information about the ESS jobs.
3. Create Job Set
- Navigate to the product specific task. In this example "Manage Custom Enterprise Scheduler Jobs for HCM Core Processes"
- Click on Manage Job Sets tab.
- Enter the new job set details.
- Search for first Job. For example search by Name CloudMetricsNumberOfNamedUsers.
Under Bill Presentment Architecture in ERP Cloud, we can create custom templates for AR Invoices, Debit Memos and Credit Memos. But what if we want BU specific templates for these receivables transactions
We are going to take a look at the setups to default Business Unit specific Templates in Print Receivables Transactions.
- First, create custom templates in BI for each Business Unit
- Now, navigate to Task: 'Manage Standard Lookups'
- Create Lookup type “ARBPA_SELECT_INV_TEMPLATE”
- Module: Receivables
- Create Lookup Code : <Business Unit Name>
- Meaning: <Custom Template name>
- Description: <Default Output format>
- Save and Close.
- Now, navigate to Scheduled Processes and select ESS Job: 'Print Receivables Transactions'
- Provide Business Unit Name in the parameter. You'll see that the corresponding Custom Template Name defined in the Lookup will appear in the parameter -
Oracle Developer Connect portal is an integrated repository of all the SOAP Web Services provided by Oracle ERP cloud.
What is it ?
- A cloud developer portal that runs on your cloud instance and provides information about the specific set of services deployed to your cloud instance.
- Very useful resource to integrate or extend Oracle Cloud Applications and develop customized business solutions.
- Discover business object services, look up service endpoints and view metadata.
- Includes definitions for all SOAP-based web services that are marked for external use.
- Reflects the current service interface and includes patches as well as service data object customizations, if any.
What are the prerequisites ?
- To use the Developer Connect portal, your job role must have one of the following privileges -
FND_INTEGRATION_SPECIALIST_JOB
FND_APPLICATION_DEVELOPER_JOB ZCA_CUSTOMER_RELATIONSHIP_MANAGEMENT_APPLICATION_ADMINISTRATOR_JOB.
- Alternatively, you can create a custom role with ATK_WEB_SERVICE_INFO_ACCESS_PRIV entitlement and then grant the custom role to desired user
Indeed we can use basic authentication (login/password) to authenticate all Webservices in Oracle ERP Cloud .. but what if we want to have a better level of security ? Let's see more effective methods to securely access Webservices in Oracle Fusion.
Oracle Web Services Manager (OWSM) policies enforce and enable web service security in Oracle Fusion Applications.
Whilst the basic authentication might be sufficient in some cases, there are more secure ways to use Fusion Applications web services.
This involves the use of a secure session header token. The token expires within a few hours of being generated.
Tokens are encrypted and signed.