R12 Payment Manager (New Module)

• 11i Payment Workbench is replaced with Oracle Payments
• Oracle centralized all disbursement activities into one application to reduce redundancy across the apps
• Oracle Payments also manages the interfaces between E-Business Suite products and financial institutions such as banks and credit card processors
• Utilizes a dashboard to guide users to take actions on payments
• Utilizes payment templates that have the ability to fully automate the payment process from selection of invoices, to printing or electronic transmission

• Payment Dashboard

Monitor the progress of the recent pay run processes

Highlight any payment processes that require attention and automatically prompt to take appropriate actions

Shortcuts and tabs for initiating, reviewing and adjusting proposed funds disbursements.

• Payment Templates

1. Templates provide a way to store section criteria, payment attributes, and processing rules that can be reused for single pay runs or scheduled pay runs.
2. EBS will update the dates based on information in the template

• Pre-defined payment instructions
• Includes the invoice selection criteria
• Includes instructions on how validation failures are going to be handled.

• Payment Submission R12

1. Select Payment Template
2. Run Cash Requirements Report <optional>
   1. By Submitting  Single Request by Entering Payment Process Name <similar to Batch Name in 11i>
   2.  View Selected Invoices online

b. Oracle will automatically generate the Scheduled Payment Selection Report

    Which is the equivalent to the Preliminary Payment Register in 11i

1. Add Invoices, Update Amounts or Unselect Invoices to be paid
2. Submit Payment
3.  Format Payment
4.  Print/Transmit Payments
5.  Confirm Payments
6.  Run the Payment Register

Multi-Org Access Control’ (MOAC)

Multi-Org or multiple organization access (MOAC) is basically the ability to access multiple operating units from a single application responsibility. In Release 11i, when one had to enter or process data for multiple operating units, one had to login to different responsibilities because each responsibility could only access one operating unit. If one was managing Payables for Sweden, Norway and Finland one needed to define three different responsibilities. In Release 12, one would create a Security Profile and assign as many operating units as you required. One can tie that security profile to a single responsibility using a profile option called “MO: Security Profile”.

Benefits of MOAC_

• Access multiple operating units within a single application responsibility
• Responsibilities are assigned a Security Profile which is a group of Operating Units
• Assignment is through the profile option ‘MO: Security Profile’ set at the Responsibility Level
• MOAC Setup includes-
  • Define Operating Units in HR
  • Define Security Profile composed of Operating Units
  • Run Security List Maintenance Program
  • Assign Security Profile to Profile Option
  • Profile Options
  • MO: Operating Unit

    - Used when Multi-Org is NOT enabled

    - On upgrade, assigned operating unit of 11i responsibility

• MO: Security Profile

    - Assign security profile name at User or Responsibility level

• MO: Default Operating Unit - Assign default operating unit

R12 General Ledger new feature

• We can generate simultaneous Accounting for Multiple Reporting Requirements by defining legal entities and the setup needed to address each accounting and reporting requirement using the Accounting Setup Manager.
• Centralized Accounting Setup- is a central location to define accounting-related setup across all financial applications.
• Enhanced Reporting Currency Functionality and support all journal sources.
• Improved Processing Efficiency:

•   Simultaneous Data Access to Multiple Legal Entities and Ledgers

•   Simultaneous Opening and Closing of Periods for Multiple Ledgers

•   Cross-Ledger and Foreign Currency Allocations

•   Simultaneous Currency Translation of Multiple Ledgers

•   Financial Reporting Across Ledgers

•   Automatic Journal Copy

•   Streamline Automatic Posting

•   Streamline AutoReversal Criteria Setup

•   Streamline Consolidation Mappings

•   Replacement for Disabled Accounts

• Data Security:

•   Data Security across Legal Entities and Ledgers

•   Management Reporting Security

•   Prevent Reversal of Journals with Frozen Sources

•   Prevent Reversal of Unposted Journals

•   Control Accounts

•   Definition and Setup Security

• Auditability for Journal Line Reconciliation

• Entered Currency Reporting and Analysis

• Foreign Currency Recurring Journals

• Intercompany Balancing Support for Encumbrances

• Integration with Subledger Accounting

• Intercompany feature enhanced: This is now part of Oracle Advanced Intercompany System     product.

• Account Analysis and Drilldown is a new web-based interface that allows to easily review and analyze general ledger financial data. 

• GL Standard Reports Integration With XML Publisher

• New Terms: Ledger replaces Set of Books. A group of Ledger is called Ledger set, in a Ledger Sets, user can simultaneously-

• Open/Close Periods
• Create Journals
• Translate and Revalue Balances
• View Information
• Submit Standard Reports
• Submit Financial Statements

Sub Ledger Accounting Flow Chartà

Accounting Setup Manager in R12- There is a single page for setups-

R12 Account Payables new feature

• Legal Entity: New addition to the Oracle E-Business Suite that enhances the ability to manage one’s legal corporate structure and track data from the legal perspective.

Objective :This article shows Repository Creation Utility (RCU) 11.1.1.9.0 Installation On Oracle Linux 6 (64bit) which is pre-requisite for OIM installation

Installation Details :
To download the RCU installation go to the below link:

http://www.oracle.com/technetwork/middleware/data-integrator/downloads/index.html

Make sure that the below db parameters are updated with the values given below

->AL32UTF8 as the database character set.
->SHARED_POOL_SIZE is greater than or equal to 147456KB.
->SGA_MAX_SIZE is greater than or equal to 147456KB.
->DB_BLOCK_SIZE is greater than or equal to 8KB
->OPEN_CURSOR = 800
SQL> alter system set open_cursors=800 scope=spfile;
->PROCESSES=500
SQL> alter system set processes=500 scope=spfile;

SQL> alter system set session_cached_cursors=500 scope=spfile;
SQL> alter system set session_max_open_files=50 scope=spfile;
SQL> alter system set aq_tm_processes=1 scope=spfile;
SQL> alter system set job_queue_processes=10 scope=spfile;

Also you can edit the init.ora file and change the calues of open_cursor and processes.

Follow the next steps in order to run and install RCU:

1. If you are running “Oracle DB XE”, first set the RCU_JDBC_TRIM_BLOCKS environment variable to TRUE,
before the installation:
# export RCU_JDBC_TRIM_BLOCKS=true

2. After unzipping the RCU file, you will have a folder call “RcuHome”.
Run the installer from /RcuHome/bin:
# ./rcu
[oracle@a2f ~]$ pwd
/u01/app/oracle
[oracle@a2f ~]$ unzip /Downloads/ofm_rcu_linux_11.1.1.9.0_disk1_1of1.zip
[oracle@a2f ~]$ ls -ltr
total 28
drwxr-xr-x 32 oracle oinstall 4096 Dec 21 19:24 rcuHome
drwxr-xr-x 7 oracle oinstall 4096 Feb 20 19:54 Middleware
[oracle@ bin]$ pwd
/u01/app/oracle/rcuHome/bin
[oracle@ bin]$ ls -ltr rcu
-r-xr--r-- 1 oracle oinstall 9220 Aug 22 2015 rcu
[oracle@mpoojari bin] ./rcu

3. Choose ‘Create’ to create new schema and press ‘Next’:

Objective : In this article we will se how access policies are created in OIM and how auto provisioning is done .

Access Policies:
Access policies are a list of roles and the resources with which roles are to be provisioned or deprovisioned. Access policies are used to automate the provisioning of target systems to users. This is explained with the help of the following example:

A user belongs to multiple roles created in Oracle Identity Manager. Suppose a role Role1 have membership rule assigned to it. Membership rules can be designed based on the organization that the user belongs to, such as "Organization Name = "Org1". Roles can have access policies assigned to them. An access policies states which resource would be provisioned and/or denied to a role when the access policy is applicable. Therefore, when a user is created in the Org1 organization, it satisfies a membership rule and grants the Role1 role to the user. This in turn triggers the access policy assigned to the role and then provision or deny the resources mentioned in the access policy.

Terminologies Used in Access Policies

The following terminologies are associated with access policies:

Resource

A resource is a logical entity in Oracle Identity Manager that can be provisioned to a user or an organization in Oracle Identity Manager. For example, Microsoft Active Directory (AD), Microsoft Exchange, SAP, UNIX, and Database is modeled as a resource in Oracle Identity Manager.Resources are templated definitions that are associated with one or more workflows called Provisioning Process in Oracle Identity Manager, which model the lifecycle management, such as how to 

provision, revoke, enable, and disable.Resources also have entities called forms associated with them. Forms represent a collection of attributes associated with the resource. For instance, a form associated with AD server includes 

attributes such as SAM Account Name, Common Name, and User Principal Name. Forms also contain an attribute of type IT Resource (see "IT Resource Type" for details).Resources can be marked Allow Multiple, which would multiple instances of a resource to be provisioned to a user or an organization.

Account

Accounts are actual instances of a resource that are created and provisioned to a user or organization in Oracle Identity Manager. For example, an e-mail account on an Exchange server is an account (instance) of resource type Exchange.

Accounts have specific values for the attributes of the associated form.

IT Resource Type

IT resource type is a logical entity in Oracle Identity Manager used to model a physical target and all its attributes including (but not limited to) the connectivity information and the credentials required to connect to the physical computer. For example, IT resource type AD server is used to model an actual AD server.IT Resource Instance .These are actual instances of specific IT resource type that represent the actual physical target. They also have specific values for all the attributes of the physical target, such as IP address, port, user name, and password. Two physical AD servers in a deployment are represented by two instances of IT resource type AD Server.

Account Discriminator

Account discriminator is a collection of attributes on a form that uniquely identify the logical entity on which accounts are created. This term is sometimes loosely referred to as a target. For instance, for an AD server, an account discriminator can be a combination of AD server (an attribute of type IT Resource) and Organization Name.Typically account discriminators are attributes of type IT Resource.Attributes are marked as account discriminators by setting the Account Discriminator property of a Form field to True

Creating User & Roles :

1.Login to Orcale Identity Self Service control .

2.Login to System admin console .

Search for Application Instance OUD Server

Objective : This article shows how to solve some of the package error that arsises during 11g r2 installation at step 18. 

Solution:

I had faced the following error for package during 11 g r2 installation and was wandering the solution for it . This is only for the following listed packages . Any other package error you get you need to fix the issue for successfull installation . 

Some of the minimum requirements for installation are not completed . Review and fix the issues listed in the following table and recheck the system .

Package : libaio-0.3105
Package : compact-libstdc++-33-3.2.3
Package : libaio-devel-0.3105
Package : libgcc-3.4.6
Package : libstdc++-3.4.6
Package : unixODBC-2.2.11
Package : unixODBC-devel-2.2.11
Package : pdksh-5.2.14

So when you face this issue there is no need to worry , you need to just ignore the error by checking  on Ignore all  option and click on Next , your database 11g r3 will be installed successfully .  These are the pacakages not required on OEL 6/7 64 bit . 

Reconciliation.
Reconciliation is a process to create , modify or delete user accounts and user information. It is a process of comparing and synchronizing accounts information in target system with OIM. Data flows into Oracle Identity Manager from External Source.
->It is used by Oracle Identity Manager to find any identity - related activity on the target system .
->Synchronize Oracle Identity Manager user information with target account details .
->Some target systems push updated information in Oracle Identity Manager in real time . There are some connectors siebel connectors which are real time , where there is no need to run the job . Ther are online , means once you modify the target resource immediately
connector triggers the event and it is updated in OIM , it gets synchronized immediately . It depends upon the performance whether you require real time connectors or offline connectors .Running the jobs means offline synchronization.
->OIM polls other target systems periodically for any change in user identities .

Types of Reconciliation :
1) Trusted Reconciliation(Authoritative)

2) Target Reconciliation( Non Authoritative)

1)Trusted Reconcilitaion :
Process of loading identities into IDM is known as Trusted or Authoritative Reconciliation. In the process we load user profiles into IDM. User gets created into IDM.
->Used to create , modify and delete user identities in Oracle Identity Manager .
->Any target system can be configured for trusted reconciliation .
-> Generally , HR systems are designed as trusted sources for identity creation .
-> Target systems can be configured as trusted sources for a specific attribute or a set of attributes of the user account .
-> A trusted source can also be configured for a specific role or user type

This article explains predefined reports available in Oracle Fusion Payables that cover the following areas:

• Invoices
• Payments
• Payables to Ledger Reconciliation
• Period Close
• Prepayments
• Income Tax and Withholding

A user can schedule and run reports from the Scheduled Processes work area. In some cases, one can access and open reports in the Reports and Analytics work area. Let’s have a look on these reports-

Invoice Report

Payments Reports

This article outline the steps involved in the changing the field labels in oracle fusion HCM.

Rules to follow: Ensure to activate the sandbox is activated before trying the steps on personalization or customization.

1. Navigate to the desired page where you wish to see the new label.
 

For example, if you wish to change the field label from "Person Number" to "Employee Number" in the Hire an Employee Page. Navigate to Hire an Employee Page as shown above.

2. Select Administration > Customize <Page Name> Pages...

Objective:

In this training article we will understand all about Payables to General Ledger reconciliation report and the points needs to be considered while running the report.

What is Payable to General Ledger Reconciliation Report?

Payable to General ledger Reconciliation Report facilitates the reconciliation of payables data to the general ledger. It has an interactive reporting capability which provides both summarized and detailed reconciling data for review. The Summary report help us to see payables and accounting beginning and ending balances, as well as summarized activity for the period and how this activity was accounted. We can drill down to any amount in the Summary report Difference column in order to get the Differences Detail report for that item. The Differences Detail reports display the real-time details that make up balances from the Summary report, and indicate potential causes for differences between actual and reconciling amounts.

Points to be considered while using Payable to General Ledger Reconciliation Report:

We need to consider the following points while using the Payables to General Ledger Reconciliation report:

• Differences Between Transactional and Accounted Amounts
• Differences Between Summary and Detail Amounts
• Differences Between the Reconciliation Report and Other Payables Reports
• Differences Due to Rounding
• Variances Due to Transactions not Validated

Let us discuss the above points one by one.

Differences between Transactional and Accounted Amounts:

Ideally the Summary report should display no differences between payables transactional amounts and accounted amounts. In addition, the Payables Begin Balance - Accounting Amount and the Payables End Balance - Accounting Amount should agree with the Payables Trial Balance report run with the Liability Account As-of Date on the last day of the previous period, and the last day of the period being reconciled, respectively.

Any differences that we find need further investigation and correction. Common reasons for differences between transactional amounts and accounted amounts include:

• Transactions that are not accounted.
• Transactions with subledger accounts that fall outside the account range of the report.
• Transaction amounts that do not agree with the subledger journal line amounts.
• Journals posted to the subledger or general ledger that did not come from Payables.
• Subledger journals that are not transferred or posted to general ledger.

After finding and correcting discrepancies, we must rerun the Extract Reconciliation Data from Payables to General Ledger program and review the Summary report. Its worth noting that the Summary report may contain variance amounts if the Payables Begin Balance plus the period activity differ from the Payables End Balance. This applies to both the Payables Amount and the Accounting Amount.

Differences between Summary and Detail Amounts:

The Non-Payables Begin Balance amount is the portion of a general ledger liability account beginning balance that did not originate from Payables transactions. We can drill down on this amount to see a list of general ledger journal lines that have an accounting date that falls within the current fiscal year, but prior to the period of the reconciliation report, and that have an account combination that falls within the account range of the report. The drill down page does not include non-Payables journal lines dated in previous fiscal years, which means that these journal lines may not match the Non-Payables Begin Balance amount. The drill down page is only intended to provide current fiscal year journals that might have posted erroneously to the payables account. The journal source for these journals is typically not Payables. However, we may see manual subledger journal entries that were entered for the Payables source directly into the subledger, but not necessarily linked to a specific Payables transaction. Most of these entries represent adjustment journal entries.

Manual subledger journals created during the current reconciling period display in the Summary report under Other Accounting, and become part of the Non-Payables Begin Balance amount in subsequent periods. Manual general ledger journals that may affect payables accounts are created directly in the general ledger and does not display under Other Accounting on the Summary report, but display instead under the Non-Payables Activity amount.

Summary amounts may not reflect totals on detail pages due to the reason that the data was modified after the data extract was run for a given accounting period. If transactions or accounting were created or modified between the time the extract was executed, and the moment you drill down from a summary amount to its detail amounts, the summary amount will not reflect the detail page totals.

To limit discrepancies between the summary and detail reports, we need to set the Payables accounting period status to Closed or Permanently Closed. Its to be noted that there may still be discrepancies if accounting activities take place in the subledger or general ledger after the extract is run. It is therefore advisable to perform these accounting activities prior to closing the Payables period and running the extract.

Security rules in the setup may restrict you from seeing data from certain business units or segment values. It is recommended that appropriate security be given to users for all business units and accounting flexfield segment values that each user is responsible for reconciling.

Differences between the Reconciliation reports and Other Payable Reports:

There can be differences between the data displayed in the Payables to General Ledger Reconciliation report and other Payables reports. The reports and reasons for the differences are as follows:

* Intercompany Transactions: We cannot exclude intercompany transactions from the Payables Aging report. If you run the Payables to General Ledger Reconciliation report to exclude intercompany transactions or show intercompany transactions only, then the Payables to General Ledger Reconciliation report and the Payables Aging report will not display compatible data.

* Dates: The Payables to General Ledger Reconciliation report displays Payables balances for the first and last date of a period. You can run the Payables Aging report only for the current date.

* Payables Invoice Register and Payables Payment Register: We cannot exclude intercompany transactions from the Payables Invoice and Payment Registers. When we run the Payables to General Ledger Reconciliation report to exclude intercompany transactions or show intercompany transactions only, then the Payables to General Ledger Reconciliation report and the Payables Invoice and Payment Registers will not display compatible data.

Differences due to Rounding:

Because of rounding, the sum of the invoice distribution base amounts and the invoice payment base amounts for a fully paid invoice may not match. Any rounding differences between the original invoice liability amount and the sum of the corresponding payment liabilities are written off by Payables when the final payment, or prepayment application, against the invoice is accounted. Therefore, the total accounting amount of the invoice and payment liability for a fully paid invoice always match. However, because the payables amounts are taken from the invoice distributions and invoice payments, rounding differences can show up in the Payables variance Payables Amount section of the Payables to General Ledger Reconciliation Report.

Differences due to Transactions not Validated:

The Payables Begin Balance and Payables End Balance amounts only include validated transactions. If the current period contains unvalidated transactions, the unvalidated transactions are reported as a Payables Variance. Unvalidated transactions are transactions that are incomplete or that have validation issues, such as invalid accounts or amount variances, that must be corrected.

For example, if there is $ 500 of unvalidated invoice transactions in the current period, the report would show the following:

Payables Begin Balance = $ 15,000

Invoices = $ 2,500

Payables Variance = $ 500

Payables End Balance = $ 17,000

In this article we will try to understand Oracle Fusion Payables Enhancements done by Oracle in Fusion Applications Release 9 along with brief overview of new features introduced.

Payment Enhancements Overview

This feature allows Payable department to make a single consolidated payment for multiple invoices processed by different business units (Business Unit in Fusion Application is equivalent to Operating Unit of R12 EBS).

What is centralized payments in Oracle Fusion Applications?

Objective:

In this training article we will discuss a new feature in Oracle Fusion Payables - Third-Party Payments.

What is Third Party Payment?

A third Party payment is a payment that a company makes to a designated party on behalf of the supplier on the invoice. Payments are generally made to the original supplier providing the goods or services. However there can be specific arrangements made wherein suppliers can specify a different party to be paid on their behalf. Payments made to other parties on behalf of the suppliers are called Third-Party Payments. In some industries, it is a common practice for customers to make payments from their Payables application to a third party (other than the invoicing supplier). Following are a few instances where third-party payments are made:

- A supplier files for bankruptcy. Let’s say the supplier has some outstanding receivables from certain customers. The court or the collection agency then sends a notification to all the customers saying that any outstanding payments that are due should be paid to them instead of to the supplier.

- A supplier has a cash flow problem. Here, the supplier sells all of their receivables to a third party. The third party then notifies the customers about this change.

This is a new enhancement feature in Fusion Financials. Now let us discuss the terminology used in this enhanced feature.

Terminologies used for Third-Party Transfers:

We In order to easily relate to the actual terms provided in the application, we will be using the following terms quite frequently during this session:

• Supplier will be referred to as Invoicing Supplier.
• Supplier Site will be referred to as Invoicing Supplier Site.
• Third-Party Supplier is the party to whom the payment will be processed, and will be referred to as Remit-to Supplier.
• Supplier Site of the third party will be referred to as Remit-to Address or Third-Party Site.

Objective:To show how to Load OIM User data through csv sheet.

Bulk Load Utility :  Overview

The bulk load utility is an automation process to load large amount of data into OIM. This reduces the downtime required to load the data and can be used immediately after OIM is installed or anytime later during the production life time of OIM. A CSV or database tables can be used as a source of data.

Every enterprise user must have acces to OIM. You can load users from resources using reconciliation . You can
also load the users from CSV(Comma Separated Values ) file . We have a bulk load utility available which can be
run to load users ,accounts , roles , role categories etc .

The structure of this utility is available in OIM_HOME folder where oim is installed . Scripts , files and database tables are available in /OIM_HOME/server/db/oim/oracle/Utilities/oimbulkupload folder . Following are description of the files that oimbulkupload folder contains. 
1)scripts --> Contains bulk load scripts
2)csv_files --> Contains CSV files of data to be loaded. CSV files must be copied to the
folder csv_files
3)sqls --> Contains SQL files called by bulk load scripts
4)lib --> Contains the oimBulkLoad.jar file
5)sample_data --> Contains sample CSV files . It helps to verify how the CSV files should look like ,what should be the first line which represents some heading (column name ), which you must be aware of .
6)logs_YYYYMMHH_hhmi --> Contains a log directory for each transaction .

When you run this utility all users are created in a temporary table space not directly in OIM , loads the data 

validates it , if it is a valid data then only it adds into Oracle Identity Manager repository .

The first line of the CSV file should be a Control Line that represents the column , which are
USR_LOGIN,USR_FIRST_NAME,USR_LAST_NAME etc. You must make sure that all the mandatory fields are
entered in CSV file . For example last name & first is mandatory , u can leave user login empty which is not mndatory field
.

Bulk Load Database columns
Table (USR): User Data is available in USR table
Columns of USR table :
->USR_LOGIN(not required)
->USR_FIRST_NAME
->USR_LAST_NAME
Table(UD) : Account Data is available inUD_*table. (Example UD_OUD, UD_AD , UD_LINUX). For each resource
you will see a table is created .
Columns varies depeneding upon the resource.

Table(UGP) : Role Data is available in User Group table(UGP)
Columns for USR table :
->UGP_ROLENAME
->UGP_NAMESPACE(not required)
->UGP_LOGIN
->UGP_DESCRIPTION(not required)
-> UGP_NAME
->UGP_LOGIN

GPG table: It contains Role Hierarchy Data
Columns for this table :
-> UGP_NAME
->GPG_UGP_NAME

ROLE_CATEGORY table : It contains ROLE_CATEGORY Data
Columns for this table:
->ROLE_CATEGORY_NAME
->ROLE_CATEGORY_DESC(not required)

Configuring the Bulk Load Utility
-> Set JAVA_HOME to the base directory of JDK
-> Verify that JDK version is 1.6 or grwater
-> You must have write permission on the current directory .

Objective: Solution for ORA-27102 : out of memroy error & TNS Protocol adapter error ORA12505 in Oracle Dtaabase 11g r2 on Windows

ORA-2702:
Sometimes there is the possiblity that your database will be shutsown by some process and then you will be unable to connect to the database either because of not enough shared memery
available or TNS protocol adapter . If you get ORA-27102 : out of memory error as shown in below screen shot.

Move to the folder containing init.ora . Open this init.ora file and update the memory_target variable to 2.5G , so that out of memory problem is solved . You will find the init.ora file in
app/oracle/product/11.2.0/dbhome_1/dbs.

Setups Summary- Centralized Payments setups in Fusion Applications is performed via Functional Setup manager-

• Setup is performed within the financial offerings
• The Functional Area is organization structures
• Tasks associated with the setup information are
  • Assign Business Unit Business Function
  • Manage Service Provider Relationships

Assign Business Unit Business Function

Business Unit should be assigned with Business Functions. It can be either Payable Invoicing or Payable Payment Business Function. Relationship between invoice business unit and payment business unit should be established by defining the payment service provider relationship.

                                                        Diagram courtesy Oracle

Setup for Supplier Site Assignments- Similarly complete the supplier site assignment for all the invoicing business unit if you want to consolidate the supplier payments across business units.

Implementation Decision Points

• Enable centralized payments when payment processing is highly centralized in the organization or when payments are outsourced.
• At any time an invoice business unit can have only one payment service provide and this feature should not be enabled when payments are handled by more than one business unit.
• Payment business unit details are not stamped on invoices. As a result the migration from one payment service provider to another, or moving from centralized to decentralized services or the converse will happen smoothly.

Job Roles & Associated Duty Roles

Shipped Job Role –    Account Payable Supervisor

Associated Duty Role- Payables Payment creation Duty

                                         -Payables Payment Processing Duty

Objective:

In the first article we discussed the new feature of Third Party Payments in Oracle Fusion Payables. In the subsequent articles we will see the detailed configuration for the same.

Set up of Third Party Relationship

First of all we are required to create the relationship between the Supplier and the third party where the payment needs to be remitted. For that Navigate Procurement > Supplier > Manage Supplier

On the Supplier page, a new section named Third-Party Payment Relationships will be available, which will enable you to establish and maintain third-party relationships. Third-party relationships can be established only at the Site level.

Using this section, we will be able to add, update, and view relationships. If we have a look at the screen shot above, we find a default relationship is already available for the invoicing supplier. The default relationship will be used while defaulting the third-party supplier details on the invoice and payment pages.

Let us remember the some information which we shall be referring as an example frequently later in this session:

* Invoicing Supplier is ABC Corporation

* Invoicing Supplier Site is HQ Site

* Third party supplier is XYZ Corporation and

* Third party site is HQ Address.

Third-Party Capture on Invoices

Let us now look at the user interaction while creating invoices. NavigatePayables > Invoices > Create Invoices > Manage Installments.

After entering the supplier, site, invoice date, amount and other required information on the invoice, when you go to the Manage Installments page you will find the two fields named Remit-to Supplier and Address Name have been added if a third-party relationship is applicable for the invoice. The third-party details will be defaulted if a default relationship is applicable for the invoice.

The Remit-to Supplier field will show all the active third-party suppliers whose relationship has been established for the invoicing supplier and site selected on the invoice as of the invoice date.

Similarly, the Address Name field will display the addresses for the remit-to supplier for which the relationship is defined and active as of the invoice date.

In addition to this information, payment method and bank account related fields will be populated with values for the third-party supplier and not for the invoicing supplier.

Third-Party Payment Creation

Let us now look at the user interaction on the payment screen. NavigatePayables > Payments > Create Payment

On the Create Payment page, two fields named Payee and Payee Site have been added.

The behavior and information defaulting for the third-party supplier-related fields, including the payment method and remit-to account will be similar to that we have seen earlier.  However please note the information will be defaulted based on the payment date entered.

Invoices will be selected based on the invoicing supplier information, but the payment will be processed in favor of the selected third-party supplier.

Let’s take an example:

If we look back at the setup, we have an invoice that was created for ABC Corporation with XYZ Corporation as the third-party supplier. While processing payment the payments can be created in favor of XYZ Corporation unless the payment clerk overrides the third party on the payment.

Third-Party Details in Payment

NavigatePayables > Payments > Manage Payments

Once the payment is created, we can view the third-party payment payee details using the Manage Payments page.

Objective : Understanding Oracle Identity Manager Security 

Security Architecture:
In Oracle Identity Manager, authorization policy management is centralized as an administrative feature. Oracle Identity Manager's authorization policy management and enforcement engine is based on an embedded version of Oracle Entitlements Server (OES), which is Oracle's entitlements administration product. These authorization policies secure access control to the Oracle Identity Manager application, thereby defining 'who can do what on what data' inside the application.
Oracle Identity Manager supports the following:
1)Use standard ADF security model for functional security and use OES best practices for data security.

2)Use a consistent architecture that supports delegated administration of various entities in Oracle Identity Manager, such as roles, organizations, entitlements, application instances, and LDAP groups.

3)Use a consistent architecture that lets backend make various security decisions, for example, who can request what, who can have what, and who needs to go through approval. This architecture facilitates the security of catalog-based request module and of converged UI and backend of self service and delegated-administration.

4)Support for a scoping mechanism for delegated administration and data security of various entities. All entities are scoped by the organization structure defined as Oracle Identity Manager
metadata.

Security Principles :
Oracle Identity Manager controls access to the application by the users to allow or prevent the users to perform various operations in the application. This is controlled by the authorization engine embedded in Oracle Identity Manager with the help of authorization policies. The purpose of authorization policies is to control user's access to Oracle Identity Manager application, which includes data, UI, and API. The authorization policies determine at runtime whether or not a particular action is allowed. Authorization policies can be defined that satisfy the authorization requirements within Oracle Identity Manager.
Identity , Authentication , and Authorization are the three main principles you come across within security principles .

1)Identity indicates who are you ? . It is the answer for who are you . All your Identity information will be available with the OIM repository like Employee id ,First Name , Last Name , your credentials for OIM .(are available with OIM repository ).
2) Authentication :
Authentication is all about are you the one who you say you are ? Every application you consider first there will be Authentication process . For an enterpirse application , it is one of the mandatory things . Application must be secured with some security mechanisms. You may authenticate with user credentials or some digital certificate etc .
3) Authorization :

It indicates to what do you have access ?. What all you can do within OIM i.e. what authorization is . So here we are speaking about authorization with OIM itself not with target resource . We already know that target resource have entitlements which is a different way of provisioning .It defines an individual's permission or access rights . Authorization policies control a user's privileges in Oracle Identity Manager directly . Operation policies control users privilege in OIM directly.You need to create authorization policies .Actually you dont create authorization policies in OIM . All possible authorization policies are already created and they names it as Admin roles. Admin role is name or wrapper of one or more authorization policies . Using these admin roles you can authorize users . There are around 14 admin roles available with OIM system . So using
those admin roles you can authorize users . You can completey control the authorization system in OIM using available 14 admin roles . There in fact 18 admin roles 4 are meant for admin super user , such as root on linux system . These super user roles are useful in processes like system onbaording process . But user administartor dont need these privileges it requires only 14 admin roles taht can be effectively used to authorize all the users .within OIM system .

Oracle Entitlements Server(OES) :

Oracle Entitlements Server comes along with OIM installation . It is meant for Authorization Policy creation .Whatever the admin roles wee see in OIM , all admin roles will be having authorization policies , those authorization policies will be coming from Embedded OES . You can modify the existing authorization policy , but cannot create your own admin roles . For the existing admin roles you can add few more authorization policies or you can delete them from admin roles using Oracle Entitlements Server . You are allowed to define policies using OES console and we call it as Policy DefinitonService , where administartors will create authorization policies associated with an admin role  .Once you create a authorization policy you add it to one of the admin role and if you add that admin role to that user , then authorization becomes effective and that we call it as Policy Enforcement Point or Policy Authorization Service .There is an authorization engine , so wehenever te user logs in , & if he tries to create users or something like that then the Authorization engine verifies whether he is authorized to do this task, whether he is a member of that admin role . If he is not he cannot continue and pops up an error message saying that you are not authrosied to do this .This is all done by the Authorization engine . And this we call it as Policy Enforcement Point. So Oracle Identity Manger Enforcement Point is used to start the policy protected action . Users login and they could perform only those operations for which they are entitled ,the assignment of admin roles . Policy Administration Point is the system administrator who modifies / define the authorization policies . PEP is the Policy Enforcement Point to assign the privileges to the end user so that they are authorized .

Organizational Security in OIM
1. Introduction :
Information Systems department (IT arm of General Financial) have a bunch of vendors supplying necesary IT infracstructure , like desktops by Dell , Servers by Oracle and Mobile devices by Apple . Colin Adams ( CADAMS) is the adminstrator for the Information System Vendors organization which is the central group managing all the vendors . In this capacity , he administaers the users , roles , entitlements and application instances for all vendors in the organization which are required when thos users access the Information Systems IT portal for managing/tracking orders for infrastructural components and any issues raised with thier functioning .Colin logs into Self Service and he can see users , roles and organizations across the Information Systems Vendors organizations.Colin is not able to scale since his organization is rapidly on-boarding more staff in vendor organizations . To perform his duties . he decides to let each vendor manage tehr own users , roles etc.

To do this , he would identify specific vendor organization and out of their members , select particular users and grants them the administrative access on the respective vendor organization .Thereafter , that administrator would log in to Self Service and would only see users who belong to Dell . Also , if he searches Roles & Organizations and see that he can only see and manage roles published to Dell .In this way , Colin can delegate the administration of other vendor organizations to users in those organizations . 

2. Delegation

Let us assign all Admin privileges to Colin Adams for Information System Vendor Org .
1. Login to Self Service console as ADMIN
2. Navigate to Administration ->Organizations .
3. Search for the Organization Information System Vendors .
4. Navigate to Admin Roles tab .
5. Key in *Administrator* in the Query By Example text box above the Admin Role Name column

6. Select all filtered admin roles and click Assign.


7. Search for the user CADAMS.
8. Click Add.

9. Check the include sub-orgs checkbox. This makes this user the admin for Information Systems Vendor organization and all sub organizations.

This article contains easy steps to install Oracle Demantra on Windows server 2008 64 bit

Database
Oracle Database 11g
Download and install the database 11g on your system

Installing Demantra
Pre requisite
1. Download and install PDF reader in your system
2. Download and install latest version of JDK in your system
3. Also make sure you clean the temporary file of the system

Download:

This is the important part where  most of the people face issues while installing as there are different patches for Demantra for different OS

Like here for windows OS try Patch 10270826

Installation 

For Installing database please click on apps2fusion_database

After installing database connect to database as sysdba and manually create tablespace 

To do so open cmd and follow the below command  

>sqlplus / as sysdba

>create tablespace TS_DP datafile ‘ts_dp.dbf' size 1000M;

>create tablespace TS_SALES_DATA datafile 'ts_sales_data.dbf' size 500m;

>create tablespace TS_SALES_DATA_X datafile 'ts_sales_data_x.dbf' size 100m;

>create tablespace TS_SIM datafile 'ts_sim.dbf' size 500m;

>create tablespace TS_SIM_X datafile 'ts_sim_x.dbf' size 100m;

>create tablespace TS_SALES_DATA_ENGINE datafile 'ts_sales_data_eng.dbf' size 500m;

>create tablespace TS_SALES_DATA_ENGINE_X datafile 'ts_sales_data_eng_x.dbf' size 100m; 

 >exit

Now installing Demantra:

1.Unzip the patch 

2.Run the setup.exe as administrator 

Click on Install Demantra Spectrum

As earlier, we have manually installed the PDF reader and JDK in pre requisite, so here we are selecting the typical installation if it is not done then select complete install. (We recommend to install the PDF and JDK manually)

Here I have selected a particular folder for all the shortcuts of Demantra tools, you can select any option you want 

Here you have to enter the database details also here I am using sys users to connect as it become easy for installer to grant permission in further steps if you are using some other user then grant dba privilege to that user. 

In this step just assign the username and password you want for Demantra 

My Database is on same system where I am installing Demantra so I will use “localhost” in field  host Machine  

Now  we have to assign the tablespace that we have created earlier to its particular field 

Default                          : TS_DP

Temporary                     :  TEMP

Sales                             : TS_SALES_DATA

Index                             : TS_SALES_DATA_X

Simulation Index             : TS_SIM_X

Simulation                      : TS_SIM

Sales_Data_Engine Index : TS_SALES_DATA_INDEX_X

Sales_Data_Engine          :TS_SALES_DATA_ENGINE 

All Done

Now to start the server just run the Start Web Server

It will start a tomcat screen 

Default users and password           dm/dm or sop/sop

Collaborator Workbench

http://localhost:8080/demantra/portal/loginpage.jsp

Web client

http://localhost:8080/demantra/portal/partnerLogin.jsp

Oracle Demantra Anywhere version of Collaborator Workbench

http://localhost:8080/demantra/portal/remoteloginpage.jsp

Oracle Demantra Anywhere version of Web client alone

http://localhost:8080/demantra/portal/anywhereLogin.jsp

Offline access to Oracle Demantra worksheets

http://localhost:8080/demantra/portal/launchDPWeb.jnlp

Dynamic Open Link (DOL) access for third-party reporting tools

http://localhost:8080/demantra/portal/DOLLogin.jsp

User Management

http://localhost:8080/demantra/portal/ userManagement.jsp

Collaborator Workbench Administration

http://localhost:8080/demantra/portal/adminLogin.jsp

Workflow Manager

http://localhost:8080/demantra/workflow/login.jsp

Technical Administration

http://localhost:8080/demantra/admin

In This article, we will try to understand Cross-Currency Payments enhancements done by Oracle in Oracle Fusion Payables.

What is a cross-currency payment?

A cross-currency payment is a payment that can pay invoices in any currency, irrespective of the currency on the invoice. For example, we can make a payment in Canadian Dollars for invoices created in US Dollars.  In today’s global business environment customer transactions go across several countries. More and more customers are looking for the business opportunities across countries. For customers to operate globally they need to be more agile, streamline their processes and look for the opportunities to improve operational efficiencies. Cross-currency payments that is payments made in a currency different from the invoice currency is one of the common payment scenarios for the customers doing business across countries. For customers especially in Europe, Asia and Latin America cross-currency payments is a very common practice. Cross-currency payments address these challenges faced by the customers and helps them effectively manage their cross-border transactions.

Cross-Currency Payments Enhancements Overview

1. Cross Currency Payments helps to create invoices with payment currency different from invoice currency.
2. Create Cross-Currency Payments by selecting invoices with invoice currency different from payment currency.
3. Relieve liability in invoice currency and credit cash in payment currency.

Objective:

In this article we will discuss the detailed introduction of java along with the link to Install Eclipse. This article will also help you to understand how to create a new project in Java.

Introduction to Java:
Java was developed by James Gosling in Sun Microsystems.
It is a platform independent programming language.
This language was initially named as OAK and later renamed as JAVA.

 What is java?

Java is an object oriented language that is:
• Concurrent
• Class based
• Object oriented
• Specifically designed to have as few implementation dependencies as possible.

Where java is used?

Java is used in various enterprise level application/frameworks all around the world.
Java has been used to develop below frameworks: –
• Hadoop
• Spring
• Hibernate
• Struts

Versions of JAVA:

Features of JAVA:

• Simple: Java is easy to learn and its syntax is quite simple, clean and easy to understand.The confusing and difficult concepts of C++ are either left out in Java or they have been re-implemented in a cleaner way.
• Object oriented: Object-oriented programming (OOP) is a programming language model organized around objects rather than "actions" and data rather than “logic”.
• Multithreading: Java multithreading feature makes it possible to write program that can do many tasks simultaneously. Benefit of multithreading is that it utilizes same memory and other resources to execute multiple threads at the same time, like While typing, grammatical errors are checked along.
• Platform Independent: Unlike other programming languages such as C, C++ etc which are compiled into platform specific machines. Java is guaranteed to be written once, run-anywhere language.
• Secure: When it comes to security, Java is always the first choice. With java secure features it enable us to develop virus free, temper free system. Java program always runs in Java runtime environment with almost null interaction with system OS, hence it is more secure.
• Robust: Java makes an effort to eliminate error prone codes by emphasizing mainly on compile time error checking and runtime checking. But the main areas which Java improved were Memory Management and mishandled Exceptions by introducing automatic Garbage Collector and Exception Handling.
• Portable: Java Byte code can be carried to any platform. No implementation dependent features. Everything related to storage is predefined, example: size of primitive data types.
• High Performance: Java is an interpreted language, so it will never be as fast as a compiled language like C or C++. But, Java enables high performance with the use of just-in-time compiler.

What is byte code in JAVA?
Byte code is an intermediate code which gets generated when a Java file is compiled using a Javac compiler. After compilation .class file is generated this contains the byte code. This code is platform independent.

Byte code and Java virtual machine(JVM):
Java byte code is the form of instructions that the Java Virtual Machine executes.
A Java programmer need not understand byte code at all.
Java Virtual Machine (JVM):
• Runs the byte code
• Makes Java platform independent
• Handles memory management

JAVA Memory Management:

C/C++ has pointers. User can allocate memory to these pointers.
If the pointer is accessed without allocating memory or invalid pointer is accessed then program crashes.
These issues are removed from Java as Java does not have pointers. Complete memory management is handled by Java itself.

Heap and Garbage Collector:

There are two types of Allocation: Heap allocation and Stack allocation.
The memory area in JVM where objects are created is called Heap.
Heap is divided into two parts. Young space and old space.

This tutorial is a continuation of Oracle Fusion Payroll - Fusion Overview(Part 1)