Krishanu Bose

Fusion Payables is tightly integrated with Oracle Document Capture (ODC), Oracle Imaging and Process Management (IPM), Oracle Content Management and Oracle BPEL process Manager to provide a seamlessly integrated solution supporting the entire payables cycle starting from scanning of physical invoices, invoice image recognizition using OCR to pre-populate invoice header, routing of the scanned invoices to AP entry specialists and subsequent approval and payment of invoices. Oracle is the only vendor in the market today offering a fully integrated solution without the use of third party bolt-on solutions.

Once the invoice arrives in a centralized mail room, the imaging specialist would sort and prepare the invoices based on parameters like invoice amount, due date, supplier, etc. and then scan these invoices using ODC. Next the images are automatically sent to Forms Recognition for intelligent recognition to extract key invoice header data like PO number, Supplier, Invoice Number, Invoice Amount and Invoice Date from scanned images using Optical Character Recognition (OCR) capabilities. Once the key header data recognition is completed, the invoice images are sent to Oracle Imaging and Process Management for storage and subsequent routing to accounts payable invoice entry specialists using Oracle BPEL Process Manager workflows. The BPEL process is generated whenever an invoice image is saved successfully in Imaging and Process Management, and this image is then routed to the AP invoice entry operator based on pre-configured rules like invoice amount, supplier, etc. The AP specialist views the scanned image and then fills up the remaining fields of the invoice to kick-off the subsequent process of invoice validation, approval, accounting and payment.

Business Units (BU) definition: A business unit is a unit of an enterprise that performs one or many business functions that can be rolled up in a management hierarchy. A business unit can process transactions on behalf of many legal entities. Normally, it will have a manager, strategic objectives, a level of autonomy, and responsibility for its profit and loss. (1)

Prior to Oracle Fusion Applications, operating units in Oracle E-Business Suite were assumed to perform all business functions, while in PeopleSoft, each business unit had one specific business function. Oracle Fusion Applications blends these two models and allows defining business units with one or many business functions. (2)

In Fusion Procurement context we need to understand the function of the following types of BU’s”

1. Procurement BU
2. Requisitioning BU
3. Sold-To BU
4. Client BU

Procurement Business units: As the name suggests, Procurement BU’s are responsible for the procurement business function which involves vendor management, negotiation of contracts and purchase agreements, issue of order and subsequent administration.

Client Business Unit: Any BU that will be serviced by the Procurement BU needs to be set as the Client BU. In case of Shared Services model where the Procurement services are centralized to one BU, the Procurement BU will be serving all the requisitions from the Client BU’s.

Requisitioning Business Unit: As the name suggests Requisitioning BU is the business unit that raises the requisition for the goods or services that it needs to the Procurement BU. Sometimes, the Requisitioning BU may be responsible for the financial impact of the purchase, in which case it will also be defined as the Sold-To BU. In case there is another BU which takes the financial responsibility of the purchase then, this Sold-To BU will be different from the Requisitioning BU.

I’ll take an example to explain the above concept.

A mobile manufacturing company having global presence has its headquarters based in Norway (XYZ Norway). Its manufacturing division is based in India (XYZ India). The India operation sources its parts from the branch based in Singapore (XYZ Singapore) which does the centralized purchase of chips from different manufacturing companies based in Taiwan and Japan. However, the payment to the supplier is done by headquarter in Norway. In this case the Requisitioning BU would be XYZ India, Purchasing BU would be the XYZ Singapore BU and the Sold-To BU would be XYZ Norway

Another example to make this clearer. I’ll take the example one of my colleagues Suchismita, uses to explain the concept;

In a normal family, when the teenage daughter while returning home sees the designer shoe on the shop’s display, and promptly she approaches her mother with the request, knowing very well that her need would be fulfilled. The mother being a simple homemaker approaches the dad, and the dad being a doting father purchases the shoe and gives to the daughter.

If we take the above example, the daughter is the Procurement BU as she is buying the shoe from the supplier (shoe store). The mother is the requisitioning BU and the father is the Sold-To BU as he is taking the financial responsibility of the purchase. (3)

Following is the list of setups to be done to ensure this works in the system.

1. Select the Procurement Service Providers for the selected BU
2. Assign either one or many out of the Procurement, Requisitioning and Receiving business functions to the respective BU
3. Configure the Procurement Business Function for the BU and Configure the Requisitioning Business Function for the BU
4. Select the Procurement BU at the Supplier Address
5. Select the Client BU and Sold-To BU at the Supplier Site Assignment

In today’s scenario, businesses find it beneficial to channel purchases through international subsidiaries instead of directly dealing with suppliers. The reasons range from country specific legal requirements to favorable tax treatment to having better margins due to economies of scale because of centralizing procurement. Fusion Procurement provides this feature seamlessly which in hindsight seems quite intuitive.

1. Oracle® Fusion Applications Procurement Implementation Guide. Retrieved from http://docs.oracle.com/cd/E15586_01/fusionapps.1111/e20383/toc.htm
2. Oracle® Fusion Applications Financials Implementation Guide. Retrieved from http://docs.oracle.com/cd/E15586_01/fusionapps.1111/e20375/toc.htm
3. Suchismita Pattnaik, Linkedin profile: http://in.linkedin.com/in/suchismita.

Following setup needs to be done at Payables level: Setup > Invoice > Hold and Release Names.

• The Initiate Workflow option is selected for the hold type in the Hold and Release Names window.

• The hold is setup to be user releasable

• Notify After X Days: The Notify After X days setup, will cause the notification to be sent to the approver after X days of the hold being placed.

• Remind After X Days: The Remind after X days will cause a reminder to be sent to the appover after X days of the first notification, and subsequently, if no action is taken.

At AME setup Level, for the Transaction Type: Payables Holds Resolution setup Attribute, Condition, Action types, Approver groups and Rules

1. Choose the Default/seeded Attribute existed for Hold Look Up Code as shown below

Steps to Release the Hold:

1. Validate invoice on matching hold like “Amt Ord, Amt Rec, Price, Qty Ord, Qty Rec”

2. A notification will be sent to the approver for hold release

3. Once the Approver clicks on “Release Hold”, the hold gets released from the invoice.

All of us in our childhood must have heard of the proverb "Too many cooks spoil the broth". If too many people try to take charge of a task, the end product might be ruined. This applies to any task like an implementation project as well.An easy way to identify if the project is going awry is when you find many people following up to find the status of the job being done. In one of my earlier projects there was one developer writing a piece of code and there were four managers chasing the poor lady for updates and status. However, none of these managers were capable or inclined to help out the person writing a complex piece of code.One really felt bad when a bug was detected in the code and none of the managers took ownership and started blaming each other and the poor lady for writing the incorrect code.

So, the next obvious question would be wher the top management is blind to such mis-management or most of the time over-management (sometimes micro-management)? My answer would be a definite 'Yes'. For the top management what matters at the end of the day is billing and not success or failure of projects. They are mostly driven by short term objectives of ensuring that their bench strength is low and not the long term objective of ensuring customer satisfaction by delivering a good solution for the client. Also, with having too many managers, the internal dynamics of peer rivalry; of each person trying to show case himself as the better manager in the eyes of top management and trying to out-do the other in a selfish manner puts the project at a grave risk.

Most of us would have seen or been part of such a project. Do share your thoughts on why we staff so many managers when there is no necessity for so many managers without defining clear boundaries and scope and conflicting job area. And, if someone has changed such a scenario, do share your experience on how to change such a situation and bring the project back to track?

Sub Ledger Accounting (SLA) is a Rule-Based accounting engine that defines how journal entries are generated in sub-ledger transactions in Oracle sub-ledger applications. However, SLA also supports external applications generating accounting information which ultimately needs to be transferred to Oracle General Ledger. Before we get into SLA we need to know few of the basic concepts like event types, event class, etc.

Event Class - classifies transaction types for accounting rule purposes. E.g. in Payables, following are possible event classes: Invoice, Debit Memo, Prepayments, Refunds and Payments.

Event Type - for each transaction type, defines possible actions with accounting significance. E.g. in Payables, following are possible event classes: AP Invoice Events – Validation, Adjustment and Cancellation. Similarly we will have event types for other event classes.

In most of the cases we would not need to customize SLA and accounting features will work same as 11i. Some of the typical business scenarios where we would need to customize SLA in Payables are as follows:

• To have a different Liability account based on Operating Unit for which the invoice is entered.
• To have different natural account (expense) based on different Invoice Type and Invoice Line type.
• To have different natural account (expense) and different liability account based on different criteria like supplier type, entering currency, pay group, etc.
• The cost center segment of Invoice distribution Liability account shall be picked from the Invoice distribution Account while the other segment values from the Liability account defined at supplier site.

To cater to some of the above requirements we can use other alternatives like using distribution sets also. But setting up a custom SLA for such scenarios is an easier approach with lower user maintenance. I will try and show a simple scenario of how to derive custom accounting for a business scenario using SLA in Oracle Payables.

Business Scenario: We need to define different liability account (natural account segment) based on Supplier Type so that business can track the liability by supplier type. The other segment values will default from supplier site. I am limiting this example to only one supplier type “Contractor". The objective would be to have a different natural account for Liability account for invoices of supplier type "Contractor" alone, while for other supplier types the normal liability account should default.

Solution:

Step1: First define a mapping set for various supplier types.

Step2: Define ADR (Account Derivation Rules)

Step3: Define JLD (Journal Line Definition)

Navigation: Setup > Accounting Setups >Sub Ledger Accounting Setups > Accounting Methods Builder > Methods and Definitions > Journal Line Definitions

Step 4: Setup AAD (Application Accounting Definition)

Navigation: Setup > Accounting Setups >Sub Ledger Accounting Setups > Accounting Methods Builder > Methods and Definitions > Application Accounting Definition

Step 5: Setup SAM (Subledger Accounting Methods)

Navigation: Setup > Accounting Setups >Sub Ledger Accounting Setups > Accounting Methods Builder > Methods and Definitions > Subledger Accounting Methods

Step 6: Assign the custom SAM to Primary Ledger

Verification of new SLA rule:

Create an invoice for supplier type ‘Contractor’ and create accounting

A common requirement that is there in almost all Payables department is to identify potential duplicate invoices. The standard Oracle report 'Invoice Audit Listing' is not effective when it comes to list down potential duplicate invoices. The 'Invoice Audit Listing' is more of a listing and the payables manager has to spend time and effort in analysing this report. Also, not to mention when it comes to performance this report takes quite a while to complete if you mention a very old 'Begin Invoice date'.

A common requirement that comes to my mind is to report all invoices which are of same amount and currency from a supplier within a given time period. Although this report is a relatively simple report to design, but as a thought i feel this should be included as a standard report in payables.

The other day i was reading an article in http://specials.rediff.com/money/2008/aug/13slide1.htm on India's top three IT companies. As per this article, Gartner has come out with a report in which they predict that, Tata Consultancy Services, Infosys Technologies, and Wipro Technologies, collectively referred as 'India-3,' will emerge as the next generation of IT service megavendors. These vendors are increasingly being considered for strategic service deals, and will augment or, in some cases, replace today's acknowledged megavendors by revenue -- IBM Global Services, Accenture and EDS -- in this space by 2011, says Gartner.

Obviously this means there will be a lot of consolidation that is bound to happen in the IT space in India, as there are a lot of tier-2 firms who cannot match the pace of growth of the top 3 firms in India. This means some of these small IT companies will be forced to sell out as the war on margins and cornering a portion of the relatively fixed marketshare will become more acute. However, for the top-3 to actually reach the levels of present generation megavendors, apart from the cost advantage, they have to position on other parameters as well. The article talks of four critical competencies on which the emerging Indian megavendors are positioning themselves.

The competencies are: process excellence; world-class HR practices; providing high quality services at a low cost; the achievement of significant and disproportionate 'mind share' compared to their actual size.

However, the catch is to continue providing high quality services at a low cost and yet try and increase the mind-share further. With wage bills increasing and worries over global slowdown, maintaining low cost is definitely a big challenge. However, i feel where Indian top-3 companies are critically lacking is in thought-leadership. The culture of innovation and path-breaking developments is still not visible. The present day megavendors have primarily reached this position due to a large investment in innovation and thought-leadership. Anyways, interesting times ahead for all in tough situations, and obviously only the toughest will survive and prosper.

In Oracle Release12, there has been some very significant changes, one among them being how we define tax. E-Business Tax is now a single point where we define our taxes for all the sub-ledger modules. In this article I will try to do a sample Tax setup using the Regime to Rate Flow of Oracle E-Business Tax in the Tax Manager responsibility.

Creating a Tax Regime

In Oracle E-Business Tax, a Tax Regime is the system of regulations for the determination and administration of one or more taxes.

1. Navigate to the Create Tax Regime:

• Navigation: Tax Configuration àTax Regimes

• Click the Button “Create”

2. Enter a new tax regime based on the following information:

· Tax Regime Code: TESTREGIME1

· Name: Test Regime1

· Regime Level: Country

· Country Name: United States

· Parent Regime Code: Blank

· Effective From: 01-JAN-1950

· Effective To: Leave Blank

· Used to group Regimes: Unchecked

3. Expand the Controls and Defaults region

· Allow Tax Recovery: Checked

· Allow Override and Entry of Inclusive Tax Lines: Unchecked

· Allow Tax Exemptions: Checked

· Allow Tax Exceptions: Checked

· Tax Currency: USD

· Minimum Accountable Unit: 0.01

· Rounding Rule: Nearest

· Tax Precision: 2 (default)

4. Click on Button “Continue”
5. Enter tax regime configuration options:
• Party Name: Vision Operations (Note: Select the Operating Unit owning Tax Content party type)
• Configuration for Taxes and Rules: Common Configuration with Party Overrides
• Configuration for Product Exceptions: Party-Specific Configuration
• Effective From: 01-JAN-1950
• Effective To: Leave blank
6. Click on Button “Finish”
7. You will get the message “The tax regime was successfully created”

Creating a Tax

1. Navigate: Tax Configuration à Tax Regimes
2. Search for the Tax Regime you created above using the filter criteria of Country as “United States” and Tax Regime Code as “TESTREGIME1”
3. Click on button “Go”
4. Click on icon “Regime to Rate Flow”
5. Click on button “Create Tax”

6. 2Create a new Tax as per information mentioned below:
   • Tax Regime Code: TESTREGIME1 (defaults)
   • Configuration Owner: Global Configuration Owner
   • Tax Source: Create a new tax (defaults)
   • Tax: TESTTAX1
   • Tax Name: Test Tax1
   • Tax Type: SALES
   • Effective From: 01-JAN-1950 (defaults)
   • Effective To: Leave blank
   • Geography Type: STATE
   • Parent Geography Type: COUNTRY
   • Parent Geography Name: United States
   • Tax Currency: USD (defaults)
   • Minimum Accountable Unit: 0.01 (defaults)
   • Rounding Rule: Nearest (defaults)
   • Tax Precision: 2 (defaults)
   • Exchange Rate Type: Blank
7. Click on “Show Controls and Defaults”
8. Enter the details as per information mentioned below
   • Allow Override and Entry of Inclusive Tax Lines: Unchecked
   • Allow Tax Rounding Override: Unchecked
   • Allow Override for Calculated Tax Lines: Checked
   • Allow Entry of Manual Tax Lines: Checked
   • Use Legal Registration Number: Unchecked
   • Allow Duplicate Tax Registration Numbers: Unchecked
   • Allow Multiple Jurisdictions: Unchecked
   • Tax Accounts Creation Method: Create Tax Accounts (defaults)
   • Allow Tax Exceptions: Checked (defaults)
   • Allow Tax Exemptions: Checked (defaults)
   • Tax Exemptions Creation Method: Create Tax Exemptions (defaults)
   • Allow Tax Recovery: Unchecked

9. Click on Button “Apply”
10. You will get the message “The Tax has been successfully created”
11. Return to Tax Regimes. Click on “Expand All”
12. Click on icon “Create Tax Status”
13. Enter the following:
    • Tax Status Code: TESTSTATUS1
    • Name: Test Tax Status1
    • Click on Button “Apply”
    • Check as Default Tax Status: Checked
    • Default Status Effective From: 01-Jan-1950
14. Click on button “Apply”
15. You will get the message “The tax status was successfully created.”

Create Tax Rates

1. Go back to the Regime to Rate Flow
2. Click on “Expand All”.
3. Click on icon “Create Tax Rate”. Enter the Tax Rates based on information mentioned below:
   • Tax Regime Code: TESTREGIME1 (defaults)
   • Configuration Owner: Global Configuration Owner (defaults)
   • Tax: TESTTAX1 (defaults)
   • Tax Status Code: TESTSTATUS1 (defaults)
   • Tax Jurisdiction Code: Blank
   • Tax Rate Code: TESTRATE1
   • Rate Type: Percentage (defaults)
   • Percentage Rate: 10
   • Effective From: 01-JAN-1950 (defaults)
   • Effective From: Leave blank

4. Click on icon “Rate Details”. Enter the Tax Rate Details based on information mentioned below:

· Tax Rate Name: Test Sales Tax Rate1

· Tax Rate Description: Test Sales Tax Rate1

· Set as Default Rate: Checked

· Default Effective From: 01-JAN-1950

· Default Effective To: Leave blank

· Allow Tax Exemptions: Checked (defaults)

· Allow Tax Exceptions: Checked (defaults)

· Internet Expenses Enabled : Checked

5. Click on the button “Apply” to return to the Create Tax Rate page.
6. Click on the button “Apply” to return to the Regime to Rate Flow page
7. You will get the message “The Tax Rate has been successfully created.”

Creating Tax Jurisdiction

1. Navigate: tax Configuration à Tax Jurisdiction
2. Click on button “Create”. Enter the Tax Jurisdiction details based on information mentioned below:
   • Tax Jurisdiction Code: TESTJUR1
   • Tax Jurisdiction Name: Test Tax Jurisdiction1
   • Tax Regime Code: TESTREGIME1
   • Tax: TESTTAX1
   • Geography Type: STATE (pick from list!)
   • Effective From: 01-JAN-1950
   • Effective To: Leave Blank
   • Geography Name: CA
   • Precedence Level: 300 (defaults)
   • Collecting Tax Authority: Blank
   • Reporting Tax Authority: Blank
   • Set as default Tax Jurisdiction: Yes (defaults)
   • Default Effective From: 01-JAN-1950
   • Default Effective To: Leave blank

3. Click on the button “Apply” to return to the Regime to Rate Flow page
4. You will get the message “The tax jurisdiction was successfully created.”

Creating Tax Accounts

1. Navigate: Tax Configuration à Taxes
2. Search for the Taxes that we created just now using the following filter criteria:
   • Country Name: United States
   • Tax Regime Code: TESTREGIME1
   • Tax: TESTTAX1
3. Click on the button “Go”. Then click on icon “Update”.
4. Click on button “Tax Accounts”.
5. Enter the Ledger as “Vision Operations (USA)”
6. Click on button “Create”
7. Enter the Tax Account details based on following information:

· Operating Unit : Vision Operations

· Tax Expense: 01-210-7710-0000-000

· Tax Recoverable/Liability: 01-000-2220-0000-000

8. Click on button “Apply” and return back to Tax Accounts page.
9. Click the button “Apply”, to return to the Update Tax page.
10. Click the button “Apply”, to return to the Taxes page.
11. You will get the message “The tax was successfully updated”.

Creating Tax Rules

1. Navigate: Tax Configuration à Tax Rules
2. Access the rule type by filtering on the following criteria:
   • Configuration Owner: Global Configuration Owner
   • Tax Regime Code: TESTREGIME1
   • Tax: TESTTAX1
3. Click on button “Go”. Then click on “Expand All”.
4. Set the following values corresponding to the Rule Types:
   • Determine Place of Supply: Ship To
   • Determine Tax Applicability: Applicable
   • Determine Tax Registration: Bill From Party
   • Determine Taxable Basis: STANDARD_TB
   • Calculate Tax Amounts: STANDARD_TC

Making Tax Available for Transactions

1. Navigate: Tax Configuration àTaxes
2. Select the Tax created based on the following filter criteria:
   • Country Name: United States
   • Tax Regime Code: TESTREGIME1
   • Tax: TESTTAX1
3. Click on button “Go”. Then click on icon “Update” on the “TESTTAX1” row.
4. Check the box “Make Tax Available for Transactions”

5. Click on button “Apply”.
6. You will get the message “This tax does not have an exchange rate type. Are you sure you want to enable this tax?” having options “Yes” and “No”. Click on “Yes”
7. You will get the message “The tax was successfully updated.”

Test your Tax Setup by creating an Invoice in Payables /Receivables or creating a Purchase Order.