Monday, September 2, 2019

Journal Processing in Oracle ERP Cloud

This post is an attempt to introduce journal processing in Oracle ERP Cloud.

In order for successful journal processing the ledger needs to be already setup, the target period open and proper security assigned to the user, focus of this post is only on journal entry and related tasks and not the required setups.

Create Journal - This functionality is similar to journal enter in EBS, manual entry of journals.

The other sources of journal entry are:
a. Create Journal in Spreadsheet( Similar to WebADI in EBS)
b. Import Journals - Journals from Sub-Ledgers and Other sources thru the interface tables

I will not get into both the above mentioned options but just focus on manual entry of journals.

From the spring board or welcome screen, navigate to the Journals area.
The spring board and appearance of the screen may differ based on the roles assigned to the user. Journal processing falls under the General Accounting functional area.

The above screen displays the welcome screen(springboard), on selecting Journals the following page is displayed.

The above screen displays the main journal dashboard that can display journals that require approval, import errors, incomplete journals. To the right of the screen when the task pane is clicked, more journal entry task options are displayed. To enter manual journal select Create Journal.



Required fields are labeled with an *, In order to enter and complete a JE you need to enter the accounting period, date, JE Category, Ledger, account combination and dr/cr. amount.
For some one who has used EBS the fields here need no explanation they are pretty much the same. The journal can be saved without completing all fields, or completed and posted. See below


The posting process is submitted and completes as shown below.

Typically due to separation of duties journal posting is separated out and assigned to different user/group. Journals entered can be reviewed and posted from the Manage journals screen as shown below.

That covers manual JE entry and posting in Oracle ERP Cloud. What if you would like to make sure the account has been really impacted, then navigate to account inquiry as below.

I covered the basic JE entry and posting, additional topics in journal processing would be auto posting, allocation, reversal that are not covered in this post. Thanks for reading.

Sunday, September 1, 2019

Functional Setup Manager (Oracle Cloud) overview

Folks who have implemented Oracle EBS 11i, R12 would remember to navigate into different screens and responsibilities to complete specific functionality setup, most likely the offline check list available in the implementation documentation is followed. The application would not guide the implementer, so there was possibility of missing some setups thus causing short fall of the desired functionality. The setup process has been completely revamped in the Fusion/Cloud applications, the desired functionality setup can be completed without navigating in and out of different application responsibilities thru FSM(Functional Setup Manager). Setup in Fusion applications involves selecting the offerings interested, the functional area and associated features with in each functional area. The selected features are setup using task list. Now to some screen shots to give an idea of how different the setup process is in Fusion/Cloud.
The above screen shot is the Offering page that lists all the offerings available, offering is collection of functional areas. EX: Financials is an offering that would have functional area related to General Ledger, Payables etc. Note the offering page has links to download the document detailing associated features, setup task list right from the application. The file can be downloaded in Excel/PDF/HTML. This is a great improvement from EBS, the implementer can download the task list in Excel and review all the required tasks and relate them with the task list associated.
The above screen shot relates to the new features option with in the offering page, the implementor or application admin can review the new features that have been released since specific version and decide to either implement or not. I remember in EBS prior to upgrading to new release I had to go thru the new release content document and review what changes were coming in and assess the upgrade, Fusion has made it so easy now. Some of the new features will not require setup and are automatically enabled, all this information is available right in the new features dashboard.
Finally the opt in area for the offering as shown in the above screen shot is the kind of on/off button. EX: You may have implemented General Ledger earlier now your organization decides to implement payables, you just come here and enable payables. Payables will now be eligible to be setup and use.
The above screen shot shows the task list associated with a functional area, in this example for functional area Expenses only the required tasks are shown. The implementer can verify this against the task list downloaded from the offering page just to make sure all tasks are in sync with documentation. Task list can be further filtered to display all tasks associated with the functional area. In order to complete the setup user has to have proper roles and access, Fusion is very different with EBS when comes to security. The best and easiest way to complete setup is by defining an implementation user and associating "Application Implementation Consultant" role to the user. In Fusion all setups are done from the "Setup and Maintenance" section that can be assessed in the navigator, once in the setup section/FSM area user can search for specific setup in the search tasks field this is useful if they do not know the exact offering/functional area where the task resides. EX: Typing "Manage Currency" will search for currency setup. This was an attempt by me to give an intro to EBS folks regarding the change in setup process with some screen shots. FSM has more to it, such as projects, task assignment, upload, download capabilities. I only covered the basics and hope some one could benefit by reading this.