Quantcast
Channel: Apps2Fusion Articles
Viewing all 930 articles
Browse latest View live
↧

Format Mask Feature in Oracle HCM Cloud BI Report

August 2, 2017, 2:09 pm
$
0
0

Introduction

One of the most common requirement while working with Data Columns having DATE datatype is to get the correct format. While some prefer ‘MM-DD-YYYY’ some regions use ‘DD-MM-YYYY’ and others might be comfortable with ‘YYYY-MM-DD’. When working with Oracle HCM Cloud UI Pages users may set their preferences (read complete article here) explicit conversion mechanism might be required when this data is to be passed as a BIP Report.

An individual has two options in this case:

  1. Use SQL Functions in SQL Query to get desired format

  2. Use Template (RTF/XPT) specific formatting.

In case of Oracle HCM Cloud many a times the SQL Based Date Functions like TO_CHAR (), TO_DATE () are not honored and they still return data in a specific format.

In such case, we may make use of the FORMAT MASK feature available.

Let-us try to have a look at a worked example

Worked Example

We would create a very simple data model for this purpose.

SQL Query Used For Data Model

select to_char(sysdate, 'DD-MM-YYYY') date1

         sysdate date2,

         trunc(sysdate) date3

from dual

 

Once the Data Model is created and we try to have a look at the Sample Data it would appear as below:

Next, we would need to create a Report Template in which we will fill the following details:

Column Name

Formatting Mask

Formatting Style

Sample Data

DATE1

 

Microsoft

02-08-2017

DATE2

DD-MM-YYYY

Microsoft

02-08-2017

DATE3

MM-DD-YYYY

Oracle

08-02-2017

 

On the Template, this setting would be found under the Data Formatting Options as shown:

 

The Report would look as below:

 

Summary

This is how we can use different format mask on the Date Data Type to get different date formats as required by the external 3rd party system.

As of today only Microsoft and Oracle are the two Formatting Style Supported and one would need to key in (Free Flow Text) a valid date combination for the Report to display correct dates. There is currently no validation in place and in case an incorrect combination is entered the Report would go into error.

Please do try different combinations  (valid ones ofcourse) and do share your findings.

That’s it from mw for the time being. Good bye till next time, have a great day and do feel free to send your feedbacks/review comments on this article.

↧
Search

Creating a Worker Detail Report Using OTBI In Oracle HCM Cloud

August 7, 2017, 11:03 am
$
0
0

Introduction

In one of the previous article, we have seen how to run the delivered “Worker Report” in Oracle HCM Cloud Application. The “Worker Report” is a BIP Report, which has an underlying SQL, and in case one has an intent to add/remove data columns, he/she would need to have a fair idea of the database tables. This at times could be a challenge if there is a critical requirement and the technical team is pre-occupied Under such circumstances creating an OTBI Analysis might come to the rescue.

End Users would be able to create a simple Analysis to get a complete view of the employee records and proceed with their work. Moreover, as OTBI Reports fetches data based on the logged in user’s security roles so one added advantage is that an individual (one who runs the report) is only able to view the data he/she is authorized to view.

So let-us get started with building a simple yet exhaustive “Worker Detail Report”.

Worked Example

For this example, we would be using the “Workforce Management – Worker Assignment Real Time” Subject Area.

A complete list of all the columns along with the data-source can be found below:

Column Name

Data-Source

Person Number

"Worker"."Person Number"

Full Name

"Worker"."Employee Name"

Address Line 1

"Worker"."Employee Mailing AddressLine1"

Address Line 2

"Worker"."Employee Mailing AddressLine2”

City

"Worker"."Employee Mailing City Name"

County

"Worker"."Employee Mailing Region1"

State

"Workforce Management - Worker Assignment Real Time"."Worker"."Employee Mailing Region2"

Postal Code

"Worker"."Employee Mailing Postal Code"

Assignment Status

"Worker"."Assignment Status"

Assignment Category

"Worker"."Assignment Category"

Person Hire Date

"Worker"."Employee Hire Date"

Manager Name

"Worker"."Manager Name"

Business Unit

"Business Unit"."Business Unit Name"

Department

"Department"."Department Name"

Grade

"Grade"."Grade Name"

Job Code

"Job"."Job Code"

Job

"Job"."Job Name"

Legislation

"Legal Employer"."Legislation"

Legal Employer

"Legal Employer"."Name"

Location Name

"Location"."Worker Location Name"

Location Address Line1

"Location"."Address Line 1"

Location Address Line2

"Location"."Address Line 2"

Location City

"Location"."City"

Location County

"Location"."Region 1"

Location State

"Workforce Management - Worker Assignment Real Time"."Location"."Region 2"

Location Postal Code

"Location"."Postal Code"

Territory

"Worker Legislation"."Territory Short Name"

Employment Category

"Worker Assignment Details"."Employment Category"

User Person Type

"Worker"."Person Type"

When mapped the Criteria Tab would appear as below:

The Analysis XML created is given in below table:

Analysis XML

<saw:report xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:sawx="com.siebel.analytics.web/expression/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlVersion="201201160">      

  <saw:criteria xsi:type="saw:simpleCriteria" subjectArea="&quot;Workforce Management - Worker Assignment Real Time&quot;" withinHierarchy="true">            

     <saw:columns>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c86c8d0ff71c3cdbb">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Person Number"</sawx:expr></saw:columnFormula></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c17e2adba3ceff292">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Employee Name"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Worker</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Full Name</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="cacdc2c2f5a3d6987">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Employee Mailing AddressLine1"</sawx:expr></saw:columnFormula></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="cdb3165f8a8ac7ee6">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Employee Mailing  AddressLine2"</sawx:expr></saw:columnFormula></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="ce8f888028326a725">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Employee Mailing City Name"</sawx:expr></saw:columnFormula></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c18ba18f434ac9000">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Employee Mailing Region1"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Worker</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>County</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="785a5e078f804432ba187fbc7f00ceaf">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Workforce Management - Worker Assignment Real Time"."Worker"."Employee Mailing Region2"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Worker</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>State</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c2a2606a8bc76be37">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Employee Mailing Postal Code"</sawx:expr></saw:columnFormula></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c97b01be95f678c11">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Assignment Status"</sawx:expr></saw:columnFormula></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c972f66c42acbcdbf">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Assignment Category"</sawx:expr></saw:columnFormula></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="cb2c5a0d37722cd27">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Employee Hire Date"</sawx:expr></saw:columnFormula>            

           <saw:displayFormat>               

              <saw:formatSpec suppress="suppress" wrapText="true">                  

                 <saw:dataFormat xsi:type="saw:custom" customFormat="d-MMM-yyyy"/></saw:formatSpec></saw:displayFormat>            

           <saw:columnHeading>               

              <saw:displayFormat>                  

                 <saw:formatSpec/></saw:displayFormat></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c1183031b8f6a8661">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Manager Name"</sawx:expr></saw:columnFormula></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c22e16906b79d0755">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Business Unit"."Business Unit Name"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Business Unit</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Business Unit</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c448932d388c498ca">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Department"."Department Name"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Department</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Department</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="cfe3a3fcc6ba0b3bc">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Grade"."Grade Name"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Grade</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Grade</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="ce2bb2433315677e5">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Job"."Job Code"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Job</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Job Code</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="ce95bacb204c82fbe">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Job"."Job Name"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Job</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Job</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="ccc4042d65c5306c2">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Legal Employer"."Legislation"</sawx:expr></saw:columnFormula></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c068a6402a95b3fe7">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Legal Employer"."Name"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Legal Employer</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Legal Employer</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c52aa21b43166e04f">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Location"."Worker Location Name"</sawx:expr></saw:columnFormula></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="cc5649d068d11f1a8">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Location"."Address Line 1"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Location</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Location Address Line 1</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c4556f4bc5fe4d314">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Location"."Address Line 2"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Location</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Local Address Line 2</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="cb9469d3076598062">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Location"."City"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Location</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Location City</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c25a65b1da9a71d4f">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Location"."Region 1"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Location</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Location County</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="90db07bfbabd4adca25510edbdebfae5">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Workforce Management - Worker Assignment Real Time"."Location"."Region 2"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Location</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Location State</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c4826c5d6a32af802">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Location"."Postal Code"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Location</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Location Postal Code</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c93d42e9bcb26b277">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker Legislation"."Territory Short Name"</sawx:expr></saw:columnFormula>                        

           <saw:tableHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Worker Legislation</saw:text></saw:caption></saw:tableHeading>                        

           <saw:columnHeading>                              

              <saw:caption fmt="text">                                    

                 <saw:text>Territory</saw:text></saw:caption></saw:columnHeading></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="c61820c774b5399dc">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker Assignment Details"."Employment Category"</sawx:expr></saw:columnFormula></saw:column>                  

        <saw:column xsi:type="saw:regularColumn" columnID="cf8b1ec5318908ff2">                        

           <saw:columnFormula>                              

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Person Type"</sawx:expr></saw:columnFormula></saw:column></saw:columns>      

     <saw:filter>         

        <sawx:expr xsi:type="sawx:logical" op="and">            

           <sawx:expr xsi:type="sawx:special" op="prompted">               

              <sawx:expr xsi:type="sawx:sqlExpression">"Business Unit"."Business Unit Name"</sawx:expr></sawx:expr>            

           <sawx:expr xsi:type="sawx:special" op="prompted">               

              <sawx:expr xsi:type="sawx:sqlExpression">"Department"."Department Name"</sawx:expr></sawx:expr>            

           <sawx:expr xsi:type="sawx:special" op="prompted">               

              <sawx:expr xsi:type="sawx:sqlExpression">"Job"."Job Name"</sawx:expr></sawx:expr>            

           <sawx:expr xsi:type="sawx:special" op="prompted">               

              <sawx:expr xsi:type="sawx:sqlExpression">"Legal Employer"."Name"</sawx:expr></sawx:expr>            

           <sawx:expr xsi:type="sawx:special" op="prompted">               

              <sawx:expr xsi:type="sawx:sqlExpression">"Location"."Worker Location Name"</sawx:expr></sawx:expr>            

           <sawx:expr xsi:type="sawx:special" op="prompted">               

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Person Type"</sawx:expr></sawx:expr>            

           <sawx:expr xsi:type="sawx:special" op="prompted">               

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker Assignment Details"."Employment Category"</sawx:expr></sawx:expr></sawx:expr></saw:filter></saw:criteria>      

  <saw:views currentView="0">            

     <saw:view xsi:type="saw:compoundView" name="compoundView!1">                  

        <saw:cvTable>                        

           <saw:cvRow>                              

              <saw:cvCell viewName="titleView!1">                                    

                 <saw:displayFormat>                                          

                    <saw:formatSpec/></saw:displayFormat></saw:cvCell></saw:cvRow>                        

           <saw:cvRow>                              

              <saw:cvCell viewName="tableView!1">                                    

                 <saw:displayFormat>                                          

                    <saw:formatSpec/></saw:displayFormat></saw:cvCell></saw:cvRow></saw:cvTable></saw:view>            

     <saw:view xsi:type="saw:titleView" name="titleView!1" includeName="true"/>            

     <saw:view xsi:type="saw:tableView" name="tableView!1">                  

        <saw:edges>                        

           <saw:edge axis="page" showColumnHeader="true"/>                        

           <saw:edge axis="section"/>                        

           <saw:edge axis="row" showColumnHeader="true">                              

              <saw:edgeLayers>                                    

                 <saw:edgeLayer type="column" columnID="c17e2adba3ceff292"/>                  

                 <saw:edgeLayer type="column" columnID="c86c8d0ff71c3cdbb"/>                                                                        

                 <saw:edgeLayer type="column" columnID="cf8b1ec5318908ff2"/>                  

                 <saw:edgeLayer type="column" columnID="c97b01be95f678c11"/>                  

                 <saw:edgeLayer type="column" columnID="c972f66c42acbcdbf"/>                  

                 <saw:edgeLayer type="column" columnID="c61820c774b5399dc"/>                  

                 <saw:edgeLayer type="column" columnID="cacdc2c2f5a3d6987"/>                                    

                 <saw:edgeLayer type="column" columnID="cdb3165f8a8ac7ee6"/>                                                                        

                 <saw:edgeLayer type="column" columnID="ce8f888028326a725"/>                                    

                 <saw:edgeLayer type="column" columnID="c2a2606a8bc76be37"/>                  

                 <saw:edgeLayer type="column" columnID="c18ba18f434ac9000"/>                  

                 <saw:edgeLayer type="column" columnID="785a5e078f804432ba187fbc7f00ceaf"/>                  

                 <saw:edgeLayer type="column" columnID="c93d42e9bcb26b277"/>                  

                 <saw:edgeLayer type="column" columnID="cb2c5a0d37722cd27"/>                                    

                 <saw:edgeLayer type="column" columnID="ccc4042d65c5306c2"/>                  

                 <saw:edgeLayer type="column" columnID="c22e16906b79d0755"/>                  

                 <saw:edgeLayer type="column" columnID="c068a6402a95b3fe7"/>                  

                 <saw:edgeLayer type="column" columnID="c1183031b8f6a8661"/>                                                                                          

                 <saw:edgeLayer type="column" columnID="c448932d388c498ca"/>                                    

                 <saw:edgeLayer type="column" columnID="cfe3a3fcc6ba0b3bc"/>                                    

                 <saw:edgeLayer type="column" columnID="ce2bb2433315677e5"/>                                    

                 <saw:edgeLayer type="column" columnID="ce95bacb204c82fbe"/>                                                                        

                 <saw:edgeLayer type="column" columnID="c52aa21b43166e04f"/>                                    

                 <saw:edgeLayer type="column" columnID="cc5649d068d11f1a8"/>                                    

                 <saw:edgeLayer type="column" columnID="c4556f4bc5fe4d314"/>                                    

                 <saw:edgeLayer type="column" columnID="cb9469d3076598062"/>                                    

                 <saw:edgeLayer type="column" columnID="c25a65b1da9a71d4f"/>                                    

                 <saw:edgeLayer type="column" columnID="c4826c5d6a32af802"/>                                                                                          

                 <saw:edgeLayer type="column" columnID="90db07bfbabd4adca25510edbdebfae5"/></saw:edgeLayers></saw:edge>                        

           <saw:edge axis="column" showColumnHeader="false"/></saw:edges></saw:view></saw:views>

  <saw:prompts scope="report" subjectArea="&quot;Workforce Management - Worker Assignment Real Time&quot;"/></saw:report>

The SQL which is issued is in table below:

SQL Issued

SET VARIABLE PREFERRED_CURRENCY='User Preferred Currency 1';SELECT

  0 s_0,

  "Workforce Management - Worker Assignment Real Time"."Business Unit"."Business Unit Name" s_1,

  "Workforce Management - Worker Assignment Real Time"."Department"."Department Name" s_2,

  "Workforce Management - Worker Assignment Real Time"."Grade"."Grade Name" s_3,

  "Workforce Management - Worker Assignment Real Time"."Job"."Job Code" s_4,

  "Workforce Management - Worker Assignment Real Time"."Job"."Job Name" s_5,

  "Workforce Management - Worker Assignment Real Time"."Legal Employer"."Legislation" s_6,

  "Workforce Management - Worker Assignment Real Time"."Legal Employer"."Name" s_7,

  "Workforce Management - Worker Assignment Real Time"."Location"."Address Line 1" s_8,

  "Workforce Management - Worker Assignment Real Time"."Location"."Address Line 2" s_9,

  "Workforce Management - Worker Assignment Real Time"."Location"."City" s_10,

  "Workforce Management - Worker Assignment Real Time"."Location"."Postal Code" s_11,

  "Workforce Management - Worker Assignment Real Time"."Location"."Region 1" s_12,

  "Workforce Management - Worker Assignment Real Time"."Location"."Region 2" s_13,

  "Workforce Management - Worker Assignment Real Time"."Location"."Worker Location Name" s_14,

  "Workforce Management - Worker Assignment Real Time"."Worker Assignment Details"."Employment Category" s_15,

  "Workforce Management - Worker Assignment Real Time"."Worker Legislation"."Territory Short Name" s_16,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Assignment Category" s_17,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Assignment Status" s_18,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Employee Hire Date" s_19,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Employee Mailing  AddressLine2" s_20,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Employee Mailing AddressLine1" s_21,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Employee Mailing City Name" s_22,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Employee Mailing Postal Code" s_23,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Employee Mailing Region1" s_24,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Employee Mailing Region2" s_25,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Employee Name" s_26,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Manager Name" s_27,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Person Number" s_28,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Person Type" s_29,

  DESCRIPTOR_IDOF("Workforce Management - Worker Assignment Real Time"."Business Unit"."Business Unit Name") s_30,

  DESCRIPTOR_IDOF("Workforce Management - Worker Assignment Real Time"."Job"."Job Name") s_31,

  DESCRIPTOR_IDOF("Workforce Management - Worker Assignment Real Time"."Legal Employer"."Legislation") s_32,

  DESCRIPTOR_IDOF("Workforce Management - Worker Assignment Real Time"."Worker Assignment Details"."Employment Category") s_33,

  DESCRIPTOR_IDOF("Workforce Management - Worker Assignment Real Time"."Worker Legislation"."Territory Short Name") s_34,

  DESCRIPTOR_IDOF("Workforce Management - Worker Assignment Real Time"."Worker"."Assignment Category") s_35,

  DESCRIPTOR_IDOF("Workforce Management - Worker Assignment Real Time"."Worker"."Assignment Status") s_36,

  DESCRIPTOR_IDOF("Workforce Management - Worker Assignment Real Time"."Worker"."Person Type") s_37

FROM "Workforce Management - Worker Assignment Real Time"

ORDER BY 1, 27 ASC NULLS LAST, 29 ASC NULLS LAST, 30 ASC NULLS LAST, 38 ASC NULLS LAST, 19 ASC NULLS LAST, 37 ASC NULLS LAST, 18 ASC NULLS LAST, 36 ASC NULLS LAST, 16 ASC NULLS LAST, 34 ASC NULLS LAST, 22 ASC NULLS LAST, 21 ASC NULLS LAST, 23 ASC NULLS LAST, 24 ASC NULLS LAST, 25 ASC NULLS LAST, 26 ASC NULLS LAST, 17 ASC NULLS LAST, 35 ASC NULLS LAST, 20 ASC NULLS LAST, 7 ASC NULLS LAST, 33 ASC NULLS LAST, 2 ASC NULLS LAST, 31 ASC NULLS LAST, 8 ASC NULLS LAST, 28 ASC NULLS LAST, 3 ASC NULLS LAST, 4 ASC NULLS LAST, 5 ASC NULLS LAST, 6 ASC NULLS LAST, 32 ASC NULLS LAST, 15 ASC NULLS LAST, 9 ASC NULLS LAST, 10 ASC NULLS LAST, 11 ASC NULLS LAST, 13 ASC NULLS LAST, 12 ASC NULLS LAST, 14 ASC NULLS LAST

FETCH FIRST 75001 ROWS ONLY

A quick look at the results tab shows us the complete worker details as expected:

↧
↧

How to create a New User and assign Job Roles

August 11, 2017, 9:01 am
$
0
0

An organization needs to control who can do what on which functions under what conditions. In a nutshell a user is someone who performs certain set of functions on the basis of particular roles assigned to it; these roles come with a set of privileges to that particular Job Role.

In Oracle Fusion R12, new roles and seeded roles can be either assigned to a new user or pre existing users.

Before moving on to the steps to create a new role/duplicate role, let us understand the different types of roles in fusion financials:

  1. Duty Roles (Application Roles): Duty Roles refer to individual tasks which will be performed by users, for example Invoice creation, Journal creation. Duty roles can be customized from use to user.

  2. Job Roles: Job Roles is nothing but a collection of Duty Roles. A particular Job Role will have multiple Duty Roles under it. For example, General Accounting Manager will have Invoice creation and Journal Creation as its duty roles.

  3. Abstract Roles: Certain roles have to be performed by multiple users (irrespective of their Job Roles) whose functions are generic in nature, for example access to pay slip details, order requisitions, for example Employee.

  4. Data Roles: This role defines access to the data under a specific duty role. It defines which user can do what on which set of data? The possible actions are read, update, delete, and manage.

  1. Privileges: This refers to when access to certain job roles is defined as entitlement.

    The first step to assigning roles is:

  1. Click on the navigation bar on the top left of the screen and click on the security console. (Note: Access to the security console is available only if the Job role of IT security manager is assigned to the particular user)

  2. Now, you can create a new role or create a copy of a seeded role. For most SME’s the standard seeded roles are sufficient as there isn’t much scope to customize the Job Roles.

  3. In the search bar search for a particular Job role. Select the Job role in the dropdown starting with ORA. Create a copy of the Job Role and you can delete/add Duty roles to the same.
    (Note: Five roles have to be assigned Application implementation manager, Application implementation consultant, application implementation administrator, Employee, IT security manger)

 

 

 

Assigning Roles to existing user and creating new users.

There are two types of users: Implementation Users, Employee (End User A/c)

To create implementation users:

1. Click on add user account and enter the following details.

2. After saving the new user assign roles to the new user or pre existing user.

(Note: We cannot create two users with the same user name, even if the user name is deleted. Have to contact oracle to re enable the deleted user names.)

↧

An Overview of Assignment Data Integrity Report In Oracle HCM Cloud Application

August 13, 2017, 2:21 pm
$
0
0

Introduction

In some of the previous articles we have seen how to run some of the Diagnostic Tests like “HCM Delete Diagnostics”, “Person Setup Validations” and “Person Validations”. In this article we will try to get you acquainted with “Assignment Data Integrity Report”.

While person records do form a core part of any HCM Application Work Relationship and Assignments are considered to be the areas of prime interest to all. Any issues/errors with the work relationship records may cascade to other part of application and pose greater issues. As such, it is always advised to have a regular health checkup time-to-time for the Assignment data to ensure they are compliant and have no data integrity issues.

Oracle HCM Cloud Application has provided a delivered diagnostic test for the same. It is called “Assignment Data Integrity Report”. This report gives a complete detail of the records, which have issues along with a possible resolution too. It takes up BusinessGroupId as an input parameter ( It holds the value of 1 in most cases, but may run a query against PER_BUSINESS_GROUPS database object to find the exact value applicable for a specific environment.) In our example, the value of BusinessGroupId is 1.

The various facts which this reports checks includes:

  1. Lists all Assignment Records having multiple entries with PrimaryAssignmentFlag as ‘Y’

  2. Lists all Assignment Records having multiple entries with PrimaryFlag as ‘Y’

  3. Assignments with Invalid Effective End Date

  4. Duplicate Assignment Numbers

Let-us now try to execute this diagnostic test and check results.

Worked Example

In order to run this diagnostic test we would need to login to application with an user who has “Application Diagnostic Administrator” role. We are using HCM_IMPL and the user has all the requisite role. Next, we need to navigate to “Run Diagnostic Test” link under the top right hand corner (under the username).

Once we click on the link a new popup window would appear. We need to search for diagnostic test “Assignment Data Integrity Report” and once the Test comes up, you need to select the “Add to Run” option. Pass BusinessGroupID as 1 and run the report.

Click on “Run” and a information dialog box will appear.

A quick look at the Report would show the following results:

Summary

From the results we can clearly make out the total number of assignment records which has issues. For this example we could see that there multiple occurrences where the PrimaryAssignmentFlag and the PrimaryFlag is Y . There are however no records which has an invalid effective end date neither there is any duplication of assignment number.

As such, we may infer that this Diagnostic Report can come very handy to check the integrity of Assignment records and provide a summarized view of all erroneous records which can be identified and corrected accordingly.

↧

Creating an OTBI Analysis from Logical SQL in Oracle HCM Cloud

August 13, 2017, 3:10 pm
$
0
0

Introduction

OTBI (Oracle Transactional Business Intelligence) is a easy to use tool designed to create quick reports. But while it is easy to use sometimes it might not work as expected as the subject areas and the embedded folders within it work on the simple concept of equijoin. What this means is that if you add any column to your analysis which is not directly related with your core Subject Area attributes chances are you might not get data for those columns even if the application has data for those.

An example being, if you are trying to find list of all employees who belong to different departments and then try to extend the analysis by adding employee specific details like employee’s manager’s full name , employee’s manager’s person number, employee’s job code etc then there are chances that you might not get data for such fields and it does appears fine from an architectural point of view (this is how the OTBI analysis works) but sadly for consultants this cannot be a response they can give to their customers. We have to come up with an alternative which at times could be BIP Report (SQL Based datasource) but it would still be nice to achieve such reports in OTBI analysis. Well tough situation but hang on we have something called “Logical SQL” option.

Let-us see how we can create an analysis based on Logical SQL then.

Worked Example

We have a specific business requirement here where the customer is interested to have a report based on Succession Plan attributes. Specific data columns of interest being:

Column Name

Meaning

Plan Name

Succession Plan Name

Plan Type

Succession Plan Type

Incumbent Count

Number of Incumbents on the Succession Plan

Risk of Loss

Risk of Losing the Incumbents

Impact of Loss

Impact of Losing the Incumbents

Incumbent Full Name

Full Name of the Incumbent

Business Unit Name

Business Unit to which the Incumbent belongs

Job Code

Job Code of the Incumbent

Manager Name

Manager Name of the Incumbent

 

The meaning of the different color in the above table are described below:

We can verify what we are saying by creating a simple analysis, which will hold all the above columns.

 

Analysis XML

<saw:report xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sawx="com.siebel.analytics.web/expression/v1.1" xmlVersion="201201160">

  <saw:criteria xsi:type="saw:simpleCriteria" subjectArea="&quot;Workforce Succession Management - Incumbent Plans Real Time&quot;" withinHierarchy="true">

     <saw:columns>

        <saw:column xsi:type="saw:regularColumn" columnID="cc00f0a4902a53166">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Succession Plan Details"."Incumbent Full Name"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c2b608274e904cd19">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Succession Plan Details"."Plan Type"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c289e359d29b21624">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Succession Plan Details"."Plan Name"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c47964982f0ff1fce">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Incumbent Plan Measures"."Count of Incumbents"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c6dc7fb9cd5c6f489">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Manager Name"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c539da6f409f5e697">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Business Unit"."Business Unit Name"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c3bf27dd3ec7e59ce">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Job"."Job Code"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="cd97c0bb350db43ab">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Risk of Loss"."Risk of Loss"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="cb1510a45cfab0a16">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Risk of Loss"."Impact of Loss"</sawx:expr></saw:columnFormula></saw:column></saw:columns></saw:criteria>

  <saw:views currentView="0">

     <saw:view xsi:type="saw:compoundView" name="compoundView!1">

        <saw:cvTable>

           <saw:cvRow>

              <saw:cvCell viewName="titleView!1"/></saw:cvRow>

           <saw:cvRow>

              <saw:cvCell viewName="tableView!1"/></saw:cvRow></saw:cvTable></saw:view>

     <saw:view xsi:type="saw:titleView" name="titleView!1"/>

     <saw:view xsi:type="saw:tableView" name="tableView!1" scrollingEnabled="false">

        <saw:edges>

           <saw:edge axis="page" showColumnHeader="true"/>

           <saw:edge axis="section"/>

           <saw:edge axis="row" showColumnHeader="true">

              <saw:edgeLayers>

                 <saw:edgeLayer type="column" columnID="cc00f0a4902a53166"/>

                 <saw:edgeLayer type="column" columnID="c2b608274e904cd19"/>

                 <saw:edgeLayer type="column" columnID="c289e359d29b21624"/>

                 <saw:edgeLayer type="column" columnID="c47964982f0ff1fce"/>

                 <saw:edgeLayer type="column" columnID="c6dc7fb9cd5c6f489"/>

                 <saw:edgeLayer type="column" columnID="c539da6f409f5e697"/>

                 <saw:edgeLayer type="column" columnID="c3bf27dd3ec7e59ce"/>

                 <saw:edgeLayer type="column" columnID="cb1510a45cfab0a16"/>

                 <saw:edgeLayer type="column" columnID="cd97c0bb350db43ab"/></saw:edgeLayers></saw:edge>

           <saw:edge axis="column" showColumnHeader="rollover"/></saw:edges></saw:view></saw:views>

  <saw:prompts scope="report" subjectArea="&quot;Workforce Succession Management - Incumbent Plans Real Time&quot;"/></saw:report>

 

And the output would appear as below:

We could clearly see that Manager Name, Business Unit Name and Code fields are Blank.

Let-us try to now use the below logical sql and check results:

Logical SQL

select PlanName saw_0,PlanType saw_1,IncumbentCount saw_2,IncumbentFullName saw_3,ImpactOfLoss saw_4,RiskOfLoss saw_5,BuName saw_6,JobCode saw_7,ManagerName saw_8

from

(

select A.s_1 ImpactOfLoss,A.s_2 RiskOfLoss,A.s_3 IncumbentFullName,A.s_4 PlanName,A.s_5 PlanType,A.s_6 IncumbentCount,B.t_1 BuName,B.t_2 JobCode,B.t_4 ManagerName

from

(

SELECT

  "Workforce Succession Management - Incumbent Plans Real Time"."Risk of Loss"."Impact of Loss" s_1,

  "Workforce Succession Management - Incumbent Plans Real Time"."Risk of Loss"."Risk of Loss" s_2,

  "Workforce Succession Management - Incumbent Plans Real Time"."Succession Plan Details"."Incumbent Full Name" s_3,

  "Workforce Succession Management - Incumbent Plans Real Time"."Succession Plan Details"."Plan Name" s_4,

  "Workforce Succession Management - Incumbent Plans Real Time"."Succession Plan Details"."Plan Type" s_5,

  "Workforce Succession Management - Incumbent Plans Real Time"."Incumbent Plan Measures"."Count of Incumbents" s_6

FROM "Workforce Succession Management - Incumbent Plans Real Time"

) A,

(SELECT

  "Workforce Management - Worker Assignment Real Time"."Business Unit"."Business Unit Name" t_1,

  "Workforce Management - Worker Assignment Real Time"."Job"."Job Code" t_2,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Employee Name" t_3,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Manager Name" t_4,

  DESCRIPTOR_IDOF("Workforce Management - Worker Assignment Real Time"."Business Unit"."Business Unit Name") t_5

FROM "Workforce Management - Worker Assignment Real Time"

) B

where A.s_3 = B.t_3

) final order saw_0,saw_1,saw_2,saw_3,saw_4,saw_5,saw_6,saw_7,saw_8

And when we check the results:

We can see the columns which were not fetching data before are doing so now.

So this is how we can make use of Logical SQL to fetch data into OTBI Analysis.

Hope this was an interesting read and you all enjoyed reading it.

Thanks for your time, have a nice day!

↧
↧

An Introduction To Role Delegation Feature in Oracle HCM Cloud Application

August 13, 2017, 2:29 pm
$
0
0

Introduction

Role delegation is the assignment of a role from one user, known as the delegator, to another user, known as the proxy. The delegation can be either for a specified period, such as a planned absence, or indefinite. You can delegate roles in the Roles and Approvals Delegated to Others section on the Manage User Account page. Select Navigator - About Me - My Account.

The proxy user can perform the tasks of the delegated role on the relevant data. For example, a line manager can manage absence records for his or her reports. If that manager delegates the line manager role, then the proxy can also manage the absence records of the delegator's reports. The delegator doesn't lose the role while it's delegated. The proxy user signs in using his or her own user name, but has additional function and data privileges from the delegated role.

Multiple users can delegate the same role to the same proxy for overlapping periods. If the proxy user already has the role, then it isn't provisioned again but the proxy can access the data associated with the delegated roles.

If the proxy is a line manager, then the proxy can access his or her own manager hierarchy in addition to those from other managers.

A single delegator can't delegate the same role to the same proxy more than once for overlapping periods.

Role Delegation ends automatically if the proxy user’s assignment is terminated.

Custom Report to find Delegated Roles along with Delegator and Proxy Details

Until now, we have tried to understand what is meant by Role Delegation and other specific details about the same. While delegation of roles is a very nice feature which might come handy for senior executives and other individuals holding important strategic positions where they need some one to assist them with the work overload when they go for a vacation or take personal time-off there does comes some added responsibility for the proxy users and so there at times is a need to have complete details around the same. Each time a feature such as Role Delegation is discussed we have some obvious questions which pops up in our mind like:

  1. Which Role was Delegated?

  2. Who was the Delegator?

  3. Who was the proxy?

  4. What is the Role Delegation Start Date?

  5. What is the Role Delegation End Date?

All such questions can be answered by developing a custom BIP Report. In this example, we would try to develop the same.

SQL Used

SELECT NAMED.DISPLAY_NAME DelegDisplayName

, NAMED.FULL_NAME DelegFullName

, APPLD.PERSON_NUMBER DelegPersonNumb

, NAME.DISPLAY_NAME ProxyDisplayName

, NAME.FULL_NAME ProxyFullName

, APPL.PERSON_NUMBER PersNumb

, USR.USERNAME UsrName

, ROLE.ROLE_COMMON_NAME RoleName

, DELG.START_DATE Delegate_Begin

, DELG.END_DATE Delegate_End

, DELG.CREATED_BY Delegate_CreatedBy

, DELG.CREATION_DATE Delegate_CreateDate

, DELG.LAST_UPDATED_BY Delegate_UpdtBy

, DELG.LAST_UPDATE_DATE Delegate_UpdtDate

, USR.HR_TERMINATED Proxy_HRTerm

, USR.SUSPENDED Proxy_Suspended

FROM PER_DELEGATED_ROLES DELG

, PER_USERS USR

, PER_ROLES_DN ROLE

, PER_ALL_PEOPLE_F APPL

, PER_PERSON_NAMES_F NAME

, PER_ALL_PEOPLE_F APPLD

, PER_PERSON_NAMES_F NAMED

WHERE DELG.PROXY_PERSON_ID = USR.PERSON_ID

AND DELG.ROLE_ID = ROLE.ROLE_ID

AND APPL.PERSON_ID = DELG.PROXY_PERSON_ID

AND TRUNC(SYSDATE) BETWEEN APPL.EFFECTIVE_START_DATE AND APPL.EFFECTIVE_END_DATE

AND NAME.PERSON_ID = DELG.PROXY_PERSON_ID

AND TRUNC(SYSDATE) BETWEEN NAME.EFFECTIVE_START_DATE AND NAME.EFFECTIVE_END_DATE

AND NAME.NAME_TYPE = 'GLOBAL'

AND APPLD.PERSON_ID = DELG.DELEGATOR_PERSON_ID

AND TRUNC(SYSDATE) BETWEEN APPLD.EFFECTIVE_START_DATE AND APPLD.EFFECTIVE_END_DATE

AND NAMED.PERSON_ID = DELG.DELEGATOR_PERSON_ID

AND TRUNC(SYSDATE) BETWEEN NAMED.EFFECTIVE_START_DATE AND NAMED.EFFECTIVE_END_DATE

AND NAMED.NAME_TYPE = 'GLOBAL'

ORDER BY NAMED.FULL_NAME, NAME.FULL_NAME

Once we map this SQL into a data model and prepare a report ( we would only selected specific data columns and not all columns from the SQL ) we get a report which appears as below:

 

From the above report we can conclude that a role named “25th_JULY_DATA” was delegated by Curtis Feitty(Person# 101) to Jessica Mullen(Person# 543) for the period of 26th July 2017 to 30th July 2017.

Similarly, one may run the same SQL query and get the complete list of all the roles which were delegated in a specific environment along with details like delegator, proxy, delegation start date, delegation end date.. etc.

↧

Creating a Parameterized ESS Job in Oracle HCM Cloud Application

August 13, 2017, 3:09 pm
$
0
0

Introduction

We have already seen how to create a simple custom ESS Job in Oracle HCM Cloud Application. Now we, will take this a little further and try to have a Parameterized Custom ESS Job created. For this example, we would create a simple BIP Report, which would comprise of the following data columns:

  1. Person Number

  2. Start Date

  3. Effective Start Date

  4. Effective End Date

We would try to fetch all this details on a specific date (using a date type input parameter say Effective Date).

The output format of the report would be PDF and we would submit the same from the Scheduled Processes link under Tools->Scheduled Processes.

So let’s get started

Worked Example

We would need to login to the application with a user having admin privileges (HCM_IMPL is the user we are using here) and try to create a simple SQL query based BIP Report.

The SQL used for the report is:

SQL Used

SELECT papf.person_number,

              papf.effective_start_date,

              papf.effective_end_date,

              papf.start_date

from   per_all_people_f papf

where  trunc(:p_effective_date) between papf.effective_start_date and papf.effective_end_date

 

We could see that we have defined a parameter (:p_effective_date) which is used to pick only records which are active on that date.

Once we prepare a Data Set using this SQL and add the relevant parameter details we should be able to see the Data Model data as shown below:

 

Next we would need to create a report from this and once created output would appear as below:

Now, that we have created a BIP Report, we can proceed with creating a ESS job from it. We have to navigate to “Setup and Maintenance” and then choose an appropriate Custom scheduler under which we want to create our custom ESS Job. For this example, we would choose “Manage Custom Enterprise Scheduler Jobs for HCM Core Setup and Related Applications”. Once there we would need to click on the (+) icon and define the ESS Job.

Attribute Name

Attribute Value

*Display Name

ParameterizedESSJob

Name

PARAMETERIZED_ESS_JOB

Path

/oracle/apps/ess/custom/ah

Application

Global Human Resources

Description

Custom ESS Job to demonstrate how to submit a parameterized ( free flow input) BIP Report

Retries

 

Job Category

 

Timeout Period

 

Job Application Name

EarHCMEss

Enable Submission from Enterprise Manager

Unchecked

Job Type

BIPJobType

Bursting Report

Uncheked

Class Name

Oracle.xdo.service.client.scheduler.BIPJobExecutable

Default Output Format

PDF

*Report ID

/Custom/Practice Samples/ParameterizedESSJobReport.xdo

Priority

 

Allow Multiple Pending Submissions

False

Enable Submissions from Scheduled Processes

Checked

 

Once populated the ESS Job Definition would appear as shown:

Now we have to define a parameter. The following details would be required for creating the same:

Attribute Name

Attribute Value

*Parameter Prompt

Effective Date

Data Type

Date or time

Read only

Uncheked

Page Element

Date Picker

Show Date and Time

Unchecked

Show Date Only

Checked

Default Date Format

yyyy-MM-dd

Default Value

System Date

Tooltip Text

Please Enter Effective Date in YYYY-MM-DD Format

Required

Checked

Do not display

Unchecked

 

The populated screen would appear as:

Running the Scheduled Job and Verifying Results

Now, since we have already created the ESS job, let-us try to run the same.We should navigate to Navigator->Tools->Scheduled Processes and search for “ParameterizedESSJob” .Once we get the same we should select the effective date from the calendar date picker and submit the same.

When we refresh the screen we will find the job has completed and a click on the job record would fetch the following details:

If we click on the “Default Document” link a pdf file will get downloaded and it will show the BIP Report data.

↧

Creating an OTBI Analysis from Logical SQL in Oracle HCM Cloud

August 16, 2017, 6:47 am
$
0
0

Introduction

OTBI (Oracle Transactional Business Intelligence) is a easy to use tool designed to create quick reports. But while it is easy to use sometimes it might not work as expected as the subject areas and the embedded folders within it work on the simple concept of equijoin. What this means is that if you add any column to your analysis which is not directly related with your core Subject Area attributes chances are you might not get data for those columns even if the application has data for those.

An example being, if you are trying to find list of all employees who belong to different departments and then try to extend the analysis by adding employee specific details like employee’s manager’s full name , employee’s manager’s person number, employee’s job code etc then there are chances that you might not get data for such fields and it does appears fine from an architectural point of view (this is how the OTBI analysis works) but sadly for consultants this cannot be a response they can give to their customers. We have to come up with an alternative which at times could be BIP Report (SQL Based datasource) but it would still be nice to achieve such reports in OTBI analysis. Well tough situation but hang on we have something called “Logical SQL” option.

Let-us see how we can create an analysis based on Logical SQL then.

Worked Example

We have a specific business requirement here where the customer is interested to have a report based on Succession Plan attributes. Specific data columns of interest being:

Column Name

Meaning

Plan Name

Succession Plan Name

Plan Type

Succession Plan Type

Incumbent Count

Number of Incumbents on the Succession Plan

Risk of Loss

Risk of Losing the Incumbents

Impact of Loss

Impact of Losing the Incumbents

Incumbent Full Name

Full Name of the Incumbent

Business Unit Name

Business Unit to which the Incumbent belongs

Job Code

Job Code of the Incumbent

Manager Name

Manager Name of the Incumbent

 

The meaning of the different color in the above table are described below:

We can verify what we are saying by creating a simple analysis, which will hold all the above columns.

 

Analysis XML

<saw:report xmlns:saw="com.siebel.analytics.web/report/v1.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sawx="com.siebel.analytics.web/expression/v1.1" xmlVersion="201201160">

  <saw:criteria xsi:type="saw:simpleCriteria" subjectArea="&quot;Workforce Succession Management - Incumbent Plans Real Time&quot;" withinHierarchy="true">

     <saw:columns>

        <saw:column xsi:type="saw:regularColumn" columnID="cc00f0a4902a53166">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Succession Plan Details"."Incumbent Full Name"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c2b608274e904cd19">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Succession Plan Details"."Plan Type"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c289e359d29b21624">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Succession Plan Details"."Plan Name"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c47964982f0ff1fce">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Incumbent Plan Measures"."Count of Incumbents"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c6dc7fb9cd5c6f489">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Worker"."Manager Name"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c539da6f409f5e697">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Business Unit"."Business Unit Name"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="c3bf27dd3ec7e59ce">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Job"."Job Code"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="cd97c0bb350db43ab">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Risk of Loss"."Risk of Loss"</sawx:expr></saw:columnFormula></saw:column>

        <saw:column xsi:type="saw:regularColumn" columnID="cb1510a45cfab0a16">

           <saw:columnFormula>

              <sawx:expr xsi:type="sawx:sqlExpression">"Risk of Loss"."Impact of Loss"</sawx:expr></saw:columnFormula></saw:column></saw:columns></saw:criteria>

  <saw:views currentView="0">

     <saw:view xsi:type="saw:compoundView" name="compoundView!1">

        <saw:cvTable>

           <saw:cvRow>

              <saw:cvCell viewName="titleView!1"/></saw:cvRow>

           <saw:cvRow>

              <saw:cvCell viewName="tableView!1"/></saw:cvRow></saw:cvTable></saw:view>

     <saw:view xsi:type="saw:titleView" name="titleView!1"/>

     <saw:view xsi:type="saw:tableView" name="tableView!1" scrollingEnabled="false">

        <saw:edges>

           <saw:edge axis="page" showColumnHeader="true"/>

           <saw:edge axis="section"/>

           <saw:edge axis="row" showColumnHeader="true">

              <saw:edgeLayers>

                 <saw:edgeLayer type="column" columnID="cc00f0a4902a53166"/>

                 <saw:edgeLayer type="column" columnID="c2b608274e904cd19"/>

                 <saw:edgeLayer type="column" columnID="c289e359d29b21624"/>

                 <saw:edgeLayer type="column" columnID="c47964982f0ff1fce"/>

                 <saw:edgeLayer type="column" columnID="c6dc7fb9cd5c6f489"/>

                 <saw:edgeLayer type="column" columnID="c539da6f409f5e697"/>

                 <saw:edgeLayer type="column" columnID="c3bf27dd3ec7e59ce"/>

                 <saw:edgeLayer type="column" columnID="cb1510a45cfab0a16"/>

                 <saw:edgeLayer type="column" columnID="cd97c0bb350db43ab"/></saw:edgeLayers></saw:edge>

           <saw:edge axis="column" showColumnHeader="rollover"/></saw:edges></saw:view></saw:views>

  <saw:prompts scope="report" subjectArea="&quot;Workforce Succession Management - Incumbent Plans Real Time&quot;"/></saw:report>

 

And the output would appear as below:

We could clearly see that Manager Name, Business Unit Name and Code fields are Blank.

Let-us try to now use the below logical sql and check results:

Logical SQL

select PlanName saw_0,PlanType saw_1,IncumbentCount saw_2,IncumbentFullName saw_3,ImpactOfLoss saw_4,RiskOfLoss saw_5,BuName saw_6,JobCode saw_7,ManagerName saw_8

from

(

select A.s_1 ImpactOfLoss,A.s_2 RiskOfLoss,A.s_3 IncumbentFullName,A.s_4 PlanName,A.s_5 PlanType,A.s_6 IncumbentCount,B.t_1 BuName,B.t_2 JobCode,B.t_4 ManagerName

from

(

SELECT

  "Workforce Succession Management - Incumbent Plans Real Time"."Risk of Loss"."Impact of Loss" s_1,

  "Workforce Succession Management - Incumbent Plans Real Time"."Risk of Loss"."Risk of Loss" s_2,

  "Workforce Succession Management - Incumbent Plans Real Time"."Succession Plan Details"."Incumbent Full Name" s_3,

  "Workforce Succession Management - Incumbent Plans Real Time"."Succession Plan Details"."Plan Name" s_4,

  "Workforce Succession Management - Incumbent Plans Real Time"."Succession Plan Details"."Plan Type" s_5,

  "Workforce Succession Management - Incumbent Plans Real Time"."Incumbent Plan Measures"."Count of Incumbents" s_6

FROM "Workforce Succession Management - Incumbent Plans Real Time"

) A,

(SELECT

  "Workforce Management - Worker Assignment Real Time"."Business Unit"."Business Unit Name" t_1,

  "Workforce Management - Worker Assignment Real Time"."Job"."Job Code" t_2,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Employee Name" t_3,

  "Workforce Management - Worker Assignment Real Time"."Worker"."Manager Name" t_4,

  DESCRIPTOR_IDOF("Workforce Management - Worker Assignment Real Time"."Business Unit"."Business Unit Name") t_5

FROM "Workforce Management - Worker Assignment Real Time"

) B

where A.s_3 = B.t_3

) final order saw_0,saw_1,saw_2,saw_3,saw_4,saw_5,saw_6,saw_7,saw_8

 

And when we check the results:

We can see the columns which were not fetching data before are doing so now.

So this is how we can make use of Logical SQL to fetch data into OTBI Analysis.

Hope this was an interesting read and you all enjoyed reading it.

Thanks for your time, have a nice day!

↧
Search

An Introduction to HCM Event Diagnostics in Oracle HCM Cloud

August 17, 2017, 3:19 pm
$
0
0

Introduction

In the previous articles, we have tried to get an overview of some most commonly used Diagnostic Tests like “Address Validations”, “Person Setup Validations”, “Person Validations”, “HCM Delete Diagnostics” to name a few. But there are still many diagnostic tests which could come handy to perform a health check of the system.

HRC – Event Types is a Diagnostic Test which provides the details of the various event types.

The diagnostic test takes Enterprise ID (has the value 0 for most cases) and Source Object (Object names on which events are fired).

Now, at this point of time the most obvious question is how to find the list of all available Event Types available and the answer to it resides in the below SQL.

SQL

Select * from hrc_evt_source_object so

 

Once we execute this query we would get data which would look as:

For this example, we would select the PersonDEO object and try to run the diagnostic test for the same.

 

Worked Example

We would need to login to the application with a user having requisite roles and permission (s/he should have Application Diagnostics Administrator role) and then navigate to ‘Run Diagnostic Tests’ as shown

Once we click on the screen, a new page would open where we have to choose ‘HRC – Event Types’ as Diagnostic Test, Add the Test to the run and submit.

 

Once submitted we can click on “View Test Results” and the following details would appear as below:

Inference / Summary

We can clearly see that complete details for a particular event can be fetched by running this diagnostic test. The details which this diagnostic test displays can be categorized into following heads:

  • Event Details

  • Event Conditions

  • Attribute Archive Requirements

  • External Handlers

  • Internal Handlers

One can run this diagnostic test for any available HCM Event and get the details.

Do give a try and do share your findings.

Bye for now.. have a nice day ahead.

↧
↧

BI Report to Identify Whether a Person is Employee or Contact In Oracle HCM Cloud Application

August 24, 2017, 4:33 am
$
0
0

Introduction

Oracle HCM Cloud is based on Person Data Model concept. What this means that irrespective of whether an individual is a Employee, Contingent Worker, Non Worker, Dependent, Contact or Beneficiary a person record should be created in the system. Person Management link under Navigator but the Person Management does not picks up details about Dependent, Contact or Beneficiary (I guess the underlying query has some joins with Assignment and Work Relationship related tables and as a Dependent / Contact does not has Assignment and WR details captured they are not picked up).

As such at times it might be difficult to identify whether a specific person# is an Employee or Contact.

A custom BI Report might help us in such scenario.

In this article we will try to create on such BI Report.

IsPersonEmporContact BI Report

We would need to create a SQL query based Data Model. Also we would have conditional formatting applied where in Employee records would be highlighted in Green colour and Contact Records in Blue.

So let us get started

SQL Query

select papf.person_number,

(SELECT 'Y'

FROM   dual

where exists

(select 1

 from fusion.per_contact_relationships pcr

 where pcr.person_id IN (select papf1.person_id from fusion.per_all_people_f papf1 where trunc(sysdate) between papf1.effective_start_date and papf1.effective_end_date and papf1.person_number = papf.person_number

UNION

select 1

from fusion.per_all_people_f papf3,

    fusion.per_all_assignments_f paaf3

where trunc(sysdate) between papf3.effective_start_date and papf3.effective_end_date

and papf3.person_number = papf.person_number

and papf3.person_id = paaf3.person_id

and paaf3.primary_flag = 'Y'

and paaf3.assignment_type = 'E'))) is_employee,

 (SELECT 'Y'

  FROM   dual

  where exists

  (select 1

   from fusion.per_contact_relationships pcr

 where pcr.contact_person_id IN (select papf2.person_id from fusion.per_all_people_f papf2 where trunc(sysdate) between papf2.effective_start_date and papf2.effective_end_date and papf2.person_number =papf.person_number))) is_contact

 from fusion.per_all_people_f papf

 where trunc(sysdate) between papf.effective_start_date and papf.effective_end_date

 and papf.person_id IN

 (SELECT pcr.contact_person_id

  FROM   per_contact_relationships pcr

  UNION

  SELECT pcr.person_id

  FROM   per_contact_relationships pcr

 )

 

Once we create the Data Model, we would need to create a Template and the final Report would look as below:

 

Verification

We should now try to validate the report output.

We would first try to for Person# 114

Next we will try to search for Person# 1040 (we can see the record comes up as a contact in report)

 

And a quick search on person management shows below screen:

We could clearly see that some of the assignment related fields are not having value which confirms that this is a contact record.

That’s it for now. Thank You for your time , have a nice day!

↧

Areas of Responsibility Report in Oracle HCM Cloud Application

August 30, 2017, 4:23 am
$
0
0

Introduction

Before we delve deep into developing a Custom BI Report on Areas of Responsibility Report let-us spend some time trying to understand what is meant by Areas of Responsibility Feature in Oracle HCM Cloud Application.

The literal meaning of Areas of Responsibility as the word suggests means the various work-streams an individual is responsible to take care of.

In context of Oracle HCM Cloud Applications Areas of Responsibility referredto as AOR means:

“You can assign a responsibility to a person and define the scope of the responsibility by identifying the people for whom the person has the responsibility; the person then appears in the Work Contacts list of those people. For example, you can assign a worker as the Human Resources (HR) representative for people in a specific organization or department hierarchy. You manage areas of responsibility using the Manage Areas of Responsibility task in the Person Management work area.

Assigning an area of responsibility doesn't affect the person records the representative can see. Access to records is controlled through security. Your security administrator can set up security profiles using areas of responsibility”

One can refer to Detailed Documentation on AOR from the product document, My Oracle Support Portal or even refer to Application Help.

For now we would try to concentrate on building a custom report to identify the AOR details like Person#, Name, Country, Responsibility Type and Responsibility Name.

Worked Example

We would try to build a custom BI Report and the expected data columns are:

  1. Person#

  2. Name

  3. Country

  4. Responsibility Type

  5. Responsibility Name

We would need to build a custom SQL query for this which is:

SQL Query

SELECT  distinct papfc.person_number,

  par.responsibility_type,

  par.responsibility_name,

  ppnfv.full_name full_name,

  per.country

FROM

 (SELECT papf.person_id,

 papf.person_number,

 paam.LEGISLATION_CODE,

(SELECT DISTINCT hlaf.country

 FROM HR_LOCATIONS_ALL_F hlaf

 WHERE hlaf.location_id=paam.location_id

AND sysdate BETWEEN hlaf.effective_start_date AND hlaf.effective_end_Date) country,

 paam.business_unit_id,

 paam.LEGAL_ENTITY_ID,

 paam.ORGANIZATION_ID,

 paam.location_id,

 paam.POSITION_ID,

 paam.job_id

  FROM per_all_people_f papf,

per_all_assignments_m paam

  WHERE 1=1

AND paam.person_id=papf.person_id

AND sysdate BETWEEN paam.effective_start_date AND paam.effective_end_date

AND sysdate BETWEEN papf.effective_start_date AND papf.effective_end_Date

AND paam.EFFECTIVE_LATEST_CHANGE='Y'

AND paam.ASSIGNMENT_TYPE IN ('E') ) per,

PER_PERSON_NAMES_F_V  ppnfv,

PER_ASG_RESPONSIBILITIES par,

per_all_people_f papfc,

per_email_addresses pea

WHERE 1=1

 AND papfc.person_id=par.person_id

 --AND per.person_number=NVL(:P_PERSON,10)

 and sysdate between ppnfv.effective_Start_date and ppnfv.effective_end_Date

 and ppnfv.person_id=papfc.person_id

 AND sysdate BETWEEN papfc.effective_Start_date AND papfc.effective_end_Date

 AND papfc.primary_email_id=pea.email_address_id(+)

 AND (nvl(par.country,NVL(per.country,1))=NVL(per.country,1) OR nvl(par.country,NVL(per.LEGISLATION_CODE,1))=NVL(per.LEGISLATION_CODE,1))

 AND nvl(par.business_unit_id,NVL(per.business_unit_id,1))=NVL(per.business_unit_id,1)

 AND nvl(par.LEGAL_ENTITY_ID,NVL(per.LEGAL_ENTITY_ID,1))=NVL(per.LEGAL_ENTITY_ID,1)

 AND nvl(par.ORGANIZATION_ID,NVL(per.ORGANIZATION_ID,1))=NVL(per.ORGANIZATION_ID,1)

 AND nvl(par.location_id,NVL(per.location_id,1))=NVL(per.location_id,1)

 AND nvl(par.POSITION_ID,NVL(per.POSITION_ID,1))=NVL(per.POSITION_ID,1)

 AND nvl(par.job_id,NVL(per.job_id,1))=NVL(per.job_id,1)

 /*AND par.responsibility_type IN ('')*/

ORDER BY par.responsibility_type,

papfc.person_number

 

Once done the Final Report should look as:

↧

Identifying Roles which controls the Menu Items in Oracle Fusion HCM Cloud Application

September 1, 2017, 8:26 am
$
0
0

Introduction

Oracle Fusion HCM Cloud Application or for that matter other modules within Oracle Fusion Application like Procurement, Sales Cloud, Service Cloud.. etc has a lot of OOTB Roles and privileges which gets shipped along with the product. These roles in conjunction with the various privileges and security policies associated with them control whether or not a user would be able to access certain menu items as well as which all operations ( like Read Only, Edit Options etc..) would one be able to perform. Add to this the need of custom roles and what you get is a huge list of roles and privileges. So far so good, but what becomes challenging is to identify which all menu items are controlled by which roles and the privileges required to access the menu item. Identifying this has been a major challenge for consultants for a long time now but thanks to the Oracle Development Team and we have been offered with a new feature “Simulate Navigator” starting release 11 which answers all such questions.

In the Security Console you can access the 'Simulate Navigator' feature which exposes the particular privileges that control the menu items. At the same place you can see which reference roles include those privileges, so roles can be copied-and-edited to closer meet your own needs.

In this article, we would try to understand the same in detail.

Demonstration

We would need to login to application and select the ‘Security Console’ Menu Item. Once there we have to choose any Role (Employee Role for this example) and select the ‘Simulate Navigator’ option as shown:

Navigation: Navigator->Tools-> Security Console.

We have so many Menus which are associated with the logged in user ( Implementation Administrator) user but we are mainly concerned about the Menu which are generally associated with an individual who has the Abstract Employee Roles.

The Simulate Navigator screen is a mock-like navigator menu that shows all the possible items (based on your implementation) and if the selected role provides access. From the above screen we can see that the menu items like Personal Information, Talent Profile, Learning,Goals..etc under “About Me” and “Spaces”, “File Import and Export” under “Tools” do not have a lock icon beside them which means that these menu items would be present for every individual who has the abstract Employee Role. Also notice that there are some menu items have a yellow alert icon (like “Reports and Analytics” and “Scheduled Processes” under Tools ) which indicates that an EL Expression is set in the Structure feature which has an impact on whether the menu item would be accessible or not.

This point gets more clear if we try to login as an Employee and then try to view the menu items he has access to:

From the above screen we can see that user ‘frank.adams’ has just the abstract employee role access and under the Tools Menu there are four items namely Spaces, Reports and Analytics, Scheduled Processes and File Import and Export. A closer look at the Simulate Navigator image would clearly show that Spaces and File Import and Export are menu items which do not have a Lock icon beside them while Reports and Analytics and Scheduled Processes can be accessed by this user as the EL expression associated with these menu items turns out to be True.

Verifying EL Expression

While from above we have seen how does Simulate Navigator works there is just one thing left for verification and that is to check whether the EL Expression for the menu items ( “Reports and Analytics” & “Scheduled Processes” turns out to be true for an individual having just the Abstract Employee Role attached to it) .

For this, we would need to login to application with an Administrator User and navigate to “Structure” and check the EL Expression attached with the “Reports and Analytics” menu item

Associated EL Expression with Reports and Analytics (Visible Property)


#{(securityContext.userGrantedResource['resourceType=FNDResourceType;resourceName=ATK_Report_and_Analytics_Menu;action=launch'])}

Now with every user account this specific resource named ATK_Report_and_Analytics_Menu is associated by default and hence our user (frank.adams) being a user too also has access to this menu.

Conclusion

With this we have come to the end of the article. I hope you guys had some insight into the SimulateNavigator feature and would now be able to find out which all menu items are associated with which specific roles and also if there are any special clauses ( EL Expression ) associated with the same (menu item) which controls whether the same would be accessible or not.

Hope this was a Good Read, thanks all for your time and have a nice day !.

↧

Oracle Fusion Financials Reporting Training

September 8, 2017, 3:46 am
$
0
0

This Oracle Financials Reporting Training provides functional and implementation training for Oracle Financial Reporting. Dive into this solution with hands-on help and direction from Subject matter experts. 

↧
↧

Overview of Oracle Fusion Financials Cloud Tax- Demo

September 12, 2017, 1:27 am
$
0
0

Oracle Fusion Tax provides a single-point solution for managing your transaction and withholding tax requirements. In the Define Tax Configuration activity, you can manage the entire configuration and maintenance of tax content.Fusion Tax automates transaction tax calculation, tax determination, and tax reporting functions across business documents, such as sales invoices, purchase requisitions, purchase orders, and supplier invoices. Users can quickly configure transaction taxes according to local and international tax requirements.

 

Overview of Oracle Fusion Financials Cloud Tax:

 

Enrol Now for Fusion Financials Cloud Tax Training 

↧

Oracle Fusion R12 Financials Cloud Introduction and Basic Navigation

September 14, 2017, 1:30 am
$
0
0

Oracle Financials Cloud provides an integrated financial management service that automates, streamlines, and manages financial processes end-to-end. Oracle Financials Cloud simplifies controls, increases productivity, and improves decision-making with superior insight. It delivers broad business capabilities including general ledger, accounts payable, accounts receivable, fixed assets, expenses, collections, and cash management, as well as centralized accounting, tax, payment, and intercompany engines.

 

Oracle Fusion R12 Financials Cloud Introduction and Basic Navigation: 

Enrol Now for Fusion Financials Cloud Training

↧
Search

Oracle Fusion Cloud Tax Configuration on R12 version- Demo

September 18, 2017, 2:51 am
$
0
0

Oracle Fusion Tax is used to set up and maintain your transaction tax requirements in all geographic locations where you do business. Foundation tax configuration refers to a set of tax setup components that you will use to satisfy your tax requirements. At transaction time, Oracle Fusion Tax uses your tax configuration to determine the taxes that apply to each transaction and to calculate the tax amounts.

Foundation tax configuration components consist of:

Tax regimes

Taxes

Tax jurisdictions

Tax statuses

Tax rates

 

Oracle Fusion Cloud Tax Configuration:

 

Enrol Now for Fusion Cloud Tax Training

↧

Oracle General Ledger Overview and its Basic configurations in Fusion Financials Cloud- R12- Demo

September 19, 2017, 5:27 am
$
0
0

Below are the Functional Setup Manager tasks which are required to be performed to rapidly implement the Oracle Fusion General Ledger:

Create Chart of Accounts, Ledger, Legal Entities, and Business Units in Spreadsheet: Downloads the rapid implementation excel spreadsheet template.
Upload Chart of Accounts: Invokes the Create Enterprise Structure process from the Scheduled Process page with the upload data file as a parameter. You need to upload your first file, ChartOfAccounts.xml, created using the template and monitor for the successful completion of the process.
Deploy Chart of Accounts: Opens the Manage Chart of Accounts Instance page. Select the accounting flexfield and press the Deploy button to deploy the accounting flexfield.
Upload Ledger, Legal Entities, and Business Units: Invokes the Create Enterprise Structure process from the Scheduled Process page with the upload data file as a parameter. You need to upload your second file, FinancialsCommonEntities.xml, created using the template and monitor for the successful completion of the process.

 

Oracle General Ledger Overview and its Basic configurations in Fusion Financials Cloud- R12:

 

 

Enrol Now for Fusion Financials Cloud Online and Self-paced Training

↧
↧

OTBI Reporting in Oracle Fusion HCM Cloud Technical

September 26, 2017, 2:33 am
$
0
0

Oracle Business Intelligence offers a complete integrated solution that generates and delivers analysis for Oracle Fusion Applications or Cloud HCM. The Oracle BI platform is an enterprise-class platform for all modes of analysis and information delivery, including Dashboards, Ad-hoc analysis, online analytical Processing (OLAP), predictive analytics and Enterprise Reporting.
1. Oracle BI products integrated with Oracle Fusion Applications include :
2. Oracle Business Intelligence Enterprise Edition(OBIEE)
3. Oracle Transactional Business Intelligence (OTBI)
4. Oracle Business Intelligence Publisher (BI Publisher)
Oracle Business Intelligence Applications (OBIA)

This tutorial deals with OTBI - Oracle Transactional Business Intelligence, which is an analysis tool used for creating reports.

By the end of this tutorial, you should be able to understand the architecture of OTBI, and how it works with Fusion; understand Subject Areas, Folders and Attributes; understand and use the BI Composer; create OTBI Analysis using BI Composer and OBIEE Answers; add Flexfields to OTBI; and create Cross-Subject Area Analysis and security.

OTBI Reporting in Oracle Fusion HCM Cloud Technical:

 

 

Enroll for Fusion HCM Technical Training

↧

Configuration of Advanced Tax Capabilities in Oracle Fusion Cloud - Demo

September 26, 2017, 5:25 am
$
0
0

The Tax Configuration: Advanced tier leads you away from mainstream compliance into specialist cases. Tax or recovery is calculated based on these and other factors. Tax recovery uses the Services tier to return the appropriate tax or recovery for the product to the entity requesting it. Other services include setup and partner integration services. Third-party tax partners deliver external data, such as tax rates, simplifying your tax processing.For example, the advanced configuration includes setting up tax rules to determine:
Tax regimes
State sales tax versus a national customs tax
Shipment and delivery details
Registrations, both yours and your customers and vendors
Tax basis that results from the combinations of the above considerations
Tax rates and recovery rates

 

Configuration of Advanced Tax Capabilities in Oracle Fusion Cloud

 


 

Enrol Now for Fusion Financials Cloud Tax Training

↧

Fusion Cloud Financial Account payable Training

October 3, 2017, 7:55 am
$
0
0

Fusion Cloud Financial Account payable:

 

This Oracle Financials Cloud Using Payables training teaches end users how to enter and maintain suppliers, process invoices, process payments, and run reports for the period close activities. This course ensures you can successfully perform your daily functions.
This course teaches you the most efficient way to use Payables in your daily work. Taking this course helps you better understand full functionality of Payables. You'll walk away with the skills to optimize the functionality so you can effectively manage your workload.
Investing in this course also gives you access to hands-on labs where you can apply your new knowledge to solving issues you encounter on the job. This course is relevant for any customers using Fusion Applications through Release 11.1.12. It's beneficial for both Oracle Cloud and on-premises deployments

 

Enroll for Fusion Cloud Financial Account Payables course.

↧
Viewing all 930 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>