Wednesday 8 April 2020

Oracle Fusion Financials Training Blog

Auto Accounting Rule in Oracle Fusion Financials:

In Oracle Fusion Financials Online Training Receivable Auto Accounting Rule helps you to determine the General Ledger accounts for AR transactions that you enters manually or importing through Auto Invoice Import. System drives the GL account from these Auto Accounting Rules for AR transactions. With the help of Auto Accounting Rule, All the GL segments automatically derived in Oracle receivables transactions.

Receivables creates default accounts for revenue, receivable, freight, tax, unearned revenue, unbilled receivable, finance charges, and AutoInvoice clearing (suspense) accounts using this information.

When you enter transactions in Receivables, you can override the default general ledger accounts that Auto Accounting creates.

You can control the value that Auto Accounting assigns to each segment of your Accounting Flex field, such as Company, Division, or Account.

We can define Auto Accounting rules for these below types:

->Freight: The freight account for your transaction.

-> Receivable: The receivable account for your transaction.

-> Revenue: The revenue and finance charges account for your transaction.

-> AutoInvoice Clearing: The clearing account for your imported transactions. Receivables uses the clearing account to hold any difference between the specified revenue amount and the selling price times the quantity for imported invoice lines. Receivables only uses the clearing account if you have enabled this feature for the invoice batch source of your imported transactions.

-> Tax: The tax account for your transaction.

-> Unbilled Receivable: The unbilled receivable account for your transaction. Receivables uses this account when you use the Bill In Arrears invoicing rule. If your accounting rule recognizes revenue before your invoicing rule bills it, Receivables uses this account.

-> Unearned Revenue: The unearned revenue account for your transaction. Receivables uses this account when you use the Bill In Advance invoicing rule. If your accounting rule recognizes revenue after your invoicing rule bills it, Receivables uses this account.

For each segment, enter either the table name or constant value that you want Receivables to use to get information. When you enter an account Type, Receivables displays all of the segment names in your Accounting Flexfield Structure. Segments include such information as Company, Product, Account, and Sub-Account. Receivables lets you use different table names for different accounts. Choose one of the following table names:

-> Salesreps: Enter this option to use salesperson when determining your revenue, freight, receivable, AutoInvoice clearing, tax, unbilled receivable, and unearned revenue accounts. If you choose this option for your AutoInvoice clearing, tax, or unearned revenue accounts, Receivables uses the revenue account associated with this salesperson. If you choose this option for your unbilled receivable account, Receivables uses the receivable account associated with this salesperson.

-> Transaction Types: Enter this option to use transaction types when determining your revenue, freight, receivable, AutoInvoice clearing, tax, unbilled receivable, and unearned revenue accounts.

-> Standard Lines: Enter this option to use the standard memo line item or inventory item you selected when determining your revenue, AutoInvoice clearing, freight, tax, unbilled receivable, and unearned revenue accounts. If you choose this option for your AutoInvoice clearing, freight, tax, unbilled receivable or unearned revenue accounts, Receivables uses the revenue account associated to this standard memo line item or inventory item. If the transaction has a line type of "LINE" with an inventory item of freight ("FRT"), Auto Accounting uses the accounting rules for the freight type account rather than the revenue type account.

->Taxes: Enter this option to use tax codes when determining your tax account.

If you did not enter a Table Name, enter a Constant value for this segment, or select one from the list of values.

Oracle Fusion HCM Training Blog

The Changing Face of Oracle Fusion HCM 


The same number of the perusers of my blog know, I have been working with Oracle Fusion HCM Online Training since "Beta 16" - which was quite a while back at this point!

Throughout the years, I've seen the item change and develop with each new discharge. At some point, these progressions have been presenting new usefulness however from time to time we've seen a significant change to the 'look and feel' of the item. With Release 13 we are going to see another.

I will be giving an introduction on this extremely subject at Collaborate 2018 in Las Vegas in April. Be that as it may, I suspected I'd give a brisk review here.

Similarly as with every single current item, the first form frequently gets alluded to as "Great" when new forms show up. Prophet Cloud is the same and I will allude to the first look and feel as "The Classic Version".

The Classic Version: 

Once upon a time, the "Combination" screens were planned as "Workareas" and made up of 4 areas.

1 is the "Worldwide" locale which showed up at the highest point of the screen and regularly was utilized for route. It would in general continue over all screens.

2 is the "Undertaking territory" where the errands accessible to that particular workarea (in light of the client's jobs) were shown.

3 is the "Value-based territory" where the majority of the exchange preparing for the picked task was performed.

4 is a discretionary district and was known as the "Logical territory". Here, valuable extra data was shown dependent on the setting of the exchange.

The "Rearranged User Interface" (SUI): 

Next up was the Simplified User Interface, or SUI to its companions.

The possibility of the SUI was that it rearranged the UI for "easygoing" clients, for example, directors or workers. It existed nearby the great screens which would in general be utilized for the more "proficient" clients who utilized the framework as an instrument for their work - for example HR Specialists.

The SUI was gotten to by means of a "Springboard" page with symbols to encourage route. The workareas were chopped down and improved to make the exchanges easier to finish. For workareas with various utilizations, tabs were utilized to isolate information and to keep each screen "uncluttered".

The "New" Simplified User Interface: 

Thus, presently we go to the following new UI!

In any case, sit tight for it...... I will speak progressively about this at Collaborate 2018, so I'm not going to give a spoiler here :( If you need to know more, tag along to my Collaborate introduction "The Changing Face of Oracle Fusion HCM".