Free Oracle Magazine Profit:The Executive's Guide to Oracle Applications

Enter your e-mail address to receive notifications when there are new posts

Profit Magazine: The Executive's Guide to Oracle Applications

Oracle API Availability -Purchasing

Posted on June 17th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

To get the brief idea about some available standard available Oracle Application interfaces applicable within oracle purchasing modules and hopefully it should serve to familiarize individuals with limited knowledge of Oracle’s API functionality.

1. Open Requisition Interface

What you can do:
By this you can Automatically import requisitions from other oracle Application system or any other system using this interface. This allows you to integrate your oracle purchasing application with new or existing applications, such as material requirement planning, inventory management.etc.

What tables involved

  • PO_REQUISITIONS_INTERFACE_ALL
  • PO_REQ_DIST_INTERFACE_ALL

2. Requisition Reschedule

What you can do:

This is required when you are having Oracle Master Scheduling/MRP or a non-Oracle MRP system integrated with your oracle Purchasing, you may find that you need to reschedule requisitions as your
Planning requirements change. This API’S lets you reschedule requisition lines according to changes in your planned orders.

What tables involved

  • PO_RESCHEDULE_INTERFACE

3. Purchasing Documents Open Interface

What you can do:

You can Automatically import and update standard purchase orders, price/sales catalog information, and responses to request for Quotations(RFQ’s) from suppliers through this interface. This interface uses the API’s to process document data in the oracle applications interface table to ensure that it is valid before importing it into oracle purchasing. After the data is validated, the program converts the information in the interface table into the appropriate document in purchasing.

What tables involved

  • PO_HEADERS_INTERFACE
  • PO_LINES_INTERFACE
  • PO_DISTRIBUTIONS_INTERFACE

4. Receiving Open Interface

What you can do:

You can Automatically import receipt information from other oracle applications or other system using the receiving open interface. This interface lets you integrate your oracle purchasing applications with new or existing applications. E.g. you can load bar-coded and other receiving information from scanners.
More over the good things is that you can also bring Advance Shipment Notices (ASNs) sent from suppliers by this interface.

What tables involved

  • RCV_HEADERS_INTERFACE
  • RCV_TRANSACTIONS_INTERFACE

What you can’t done by this API’s

  • Serial numbering
  • Separate receive and deliver
  • Corrections
  • Returns
  • Movement statistics
  • Dynamic locators
  • Receiving against Internal Orders
  • Receiving against Inter-Organization transfers
  • Receiving against Drop Ship Orders
  • Receiving against RMAs

For more information for these three interface, you can refer these documenst.

  • Part No. A95953-02

Posted in Oracle Purchasing | 10 Comments »

Learn and implement - Purchase Orders in Oracle EBS Suite.

Posted on June 16th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Lets take a quick look on different types of Purchase Orders , and some of the important tips before implementing within Oracle ebs-Suite of PO module.

  • Standard Purchase Orders: You generally create standard purchase orders for one-time purchase of various items. You create standard purchase orders when you know the details of the goods or services you require, estimated costs, quantities, delivery schedules, and accounting distributions.
    • Suggested Use: Choose a standard purchase order when you require vendor commitment to specific items/services, quantities and delivery schedules, but a long-term agreement is not appropriate.
  • Blanket Purchase Agreements: You create blanket purchase agreements when you know the detail of the goods or services you plan to buy from a specific supplier in a period, but you do not yet know the detail of your delivery schedules. You can use blanket purchase agreements to specify negotiated prices for your items before actually purchasing them. Blanket purchase agreements can be created for a single organization or to be shared by different business units of your organization (global agreements).
    Much organization it is sometimes called as “standing order” or an “open order”.

    • Suggested Use: Choose a blanket agreement when you’ve negotiated volume discounts and want to create releases against these negotiated volumes, or when you commit to specific items, quantities or amounts.
  • Blanket Releases: You can issue a blanket release against a blanket purchase agreement to place the actual order (as long as the release is within the blanket agreement affectivity dates).
  • Contract Purchase Agreements/Order: You create contract purchase agreements with your suppliers to agree on specific terms and conditions without indicating the goods and services that you will be purchasing. You can later issue standard purchase orders referencing your contracts.
    • Suggested Use : Negotiate pricing on your entire volume of business. Use a contract to manage terms and conditions for this type of negotiation; couple it with a catalog quotation to reference pricing on a per item basis when you create standard purchase order lines.
  • Global Agreements: You may need to negotiate based on an enterprises’ total global purchase volume to enable centralizing the buying activity across a broad and sometimes diverse set of businesses. Using global agreements (a special type of blanket purchase agreement), buyers can negotiate enterprise-wide pricing, business by business, then execute and manage those agreements in one central shared environment. Enterprise organizations can then access the agreement to create purchase orders that leverage pre-negotiated prices and terms.
  • Planned Purchase Orders: A planned purchase order is a long-term agreement committing to buy items or services from a single source. You must specify tentative delivery schedules and all details for goods or services that you want to buy, including charge account, quantities, and estimated cost.
    • Suggested Use: Choose a planned purchase order when you want to encumber the order before creating releases. Also use to provide vendor scheduling for capacity management while issuing releases to confirm order commitment.

Apart from these there are few more types may be defined as per there industry segment , but more or less they can be fit into any one of the above mentions type.

Posted in Oracle Purchasing | 4 Comments »

Procurement/Purchase - Requisition take a look

Posted on June 15th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Procurement/purchasing is basically buying of goods and services, based on internal requirements, which will be used as input for the processing of the end product for a given company.
The input varies from simple stationery or MRO requirement (termed as indirect goods, as they are not directly involved in production processing) to raw materials (termed as direct, as they are used for production processing) and services.

How many types of Requisition in PO module we have?

There are two different kind of Requisition

  • Internal Requisition
  • Purchase requisition

handWhat is an Internal Requisition?

A requisition from the Purchasing system that will directly result in the generation of a sales order in the Order Management system through the Order Import process in Order Management.

Why do we use internal requisition/internal sales order?
Internal Requisition/Internal Sales Order provide the mechanism for requesting and transferring material from one inventory organization to other inventory organization or expense location.

What is the location in Oracle Purchasing?
Oracle Purchasing uses locations to identify the final delivery location for both inventory and vendor sourced requisition. It is using the hr_locations table.

What is an Internal customer?
When using Internal Requisition/Internal Sales Orders, it is required to create an internal customer for each destination organization and a customer ship-to site for each deliver-to location within the destination organization. Define the same address for your customer ship-to-site as your deliver-to location.

handThen what is Purchase Requisition?

The Purchase Requisition is the procedural method by which different departments of organization may request the purchase of goods and/or services, which require processing by Procurement Department.

handWhat is life Cycle of Purchase Requisition?
If you are using i-procurement this consist of 4 distinct sub-processes like:
iproc flow

A Requisition is generated either manually or by system, which is ultimately turned into a purchase order by the buyer. Sometimes the buyer decides a request for quotation (RFQ) is required by other suppliers to determine the best price for the goods or services requested. Once the quote is back, that information is used to finalize the purchase order.

handWhat is flow of Requisition?
A functional flow of Requisition cycle can be represented as
req

handWhat are the important Tables for Requisition?
These are the main tables:

PO_Requisition_Headers_All : it stores information about requisition headers. Each row contains the requisition number and Addition relevant information. REQUISTION_HEADER_ID is primary key.

HR_Employees : it’s a view that contains information about employees. You must have a row for each requestor, requisition preparer, approver , buyer or receiver . The primary key is EMPLOYEE_ID.

PO_Requisition_Lines_All : This table stores the information about the requisition lines like quantity , item , deliver to location , requestor etc. Primary Key is REQUISTION_LINE_ID

MTL_System_Items_B : This is the definition table for items. This table holds the definitions for inventory items, and purchasing items. The primary key is INVENTORY_ITEM, ORGANIZATION_ID.

PO_REQ_Distributions_All : This table stores the information about the accounting distributions associated with each requisition line. Each requisition line must have at least one accounting distribution. Each row includes the accounting flex field id and requisition line quantity. The primary key is DISTRIBUTION_ID.

GL_CODE_Combinations: This table stores valid Accounting Flex Field segment value combinations for each accounting flex field structure within your GL application. GL_CODE_COMBINATIONS is populated by the system when a new accounting flex field combination is used, either through dynamic insertion or manually.

This can be best represented as per data model as:
reqsiaite

Here are the drill down information for these two driving table:

1. PO_Requisition_Headers_All

  • SEGMENT1 - Requisition Number
  • AUTHORIZATION_STATUS - Lookup code and can have values
    • APPROVED Document has been Approved
    • CANCELLED Document has been Cancelled
    • IN PROCESS Document is still undergoing Approval
    • INCOMPLETE Document is not yet Complete
    • PRE-APPROVED Document is Approved but not yet Accepted
    • REJECTED Document as been Rejected
    • REQUIRES REAPPROVAL Requires Reapproval
    • RETURNED Document has been Returned
  • REQUISITION_HEADER_ID Unique Requisition ID (PK)

2. PO_Requisition_Lines_ALL

  • REQUISITION_LINE_ID Requisition line unique identifier
  • REQUISITION_HEADER_ID Requisition header unique identifier
  • LINE_NUM Line number
  • QUANTITY Quantity of Line item
  • LINE_LOCATION_ID Document shipment schedule unique identifier
  • UNSPSC_CODE Standard UNSPSC CODE

How we map the Main screen for Requisition with database table.

req screens

Posted in Beginner, Oracle Purchasing | No Comments »

Data Conversion,Migration and interface ..Why important

Posted on June 9th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Do you know how many ways; we can enter the data into oracle application. Most of us can guess three different ways as:

  • The Data can be entered using the application Screens.
  • The data can be entered using Oracle’s Open System Interface.
  • The data can be stored in the database table directly

But those who works in some complex business environment may figure out some of more like:

  • 3rd Party Software (for the third options)
  • Taviz (formerly SmartDB) which is EAI tool.
  • Crossroads
  • See Beyond (formerly STC)
  • Vitria
  • Data Loader: They have macro enabled spreadsheet kind of tool
  • More4apps

And there are many more, but most of these are used for master data, and few cases for transaction data via Open interface if available.

Importance of data conversion/migration and interfaces within any ERP implementation project can’t be ignored. Since ERP mostly deals with data which finally leads into Information , thus it is equally important to understand the aspect how “data” is important in any ERP system specailly in implementation phase, no matter how simple and unified operation is. Since I been involved in some big transformation oracle apps project thus It is a absolute a good cause to share some information about integration touch point, conversion/migration and interface development to someone who is very new to ERP world as well as Oracle application.

Let’s start with some common situation, we have three cases,

  1. The Customer is running there some home grown IT application which cater most of the company need. Now management has decided to go for any ERP solutions, then the question what will happen for data which is already in the existing application?
  2. Another situation is already using ERP
    a. They want to upgrade to higher version…presuming the structure of some table get changed? Lets say 10.7 to 11i
    b. The company is acquired or merged with some other company, and the whole data need to move into the parent or child company .
    c. They want to enable some additional modules within existing application.
  3. There are few data interacting with both the cases irrespective of database technology for where data is coming and going based out of need.

The answer of the 1 is data migration and 2 is more pronounced as data conversion where as thirds is popularly known as Interface. The ways these are working haven’t much difference but it is more important to understand definition and need. I never found any big difference between migration/conversion unless there is huge transformation of data, the only things figure out is conversion might required some less steps to perform, as assumption is that set up related stuff been already been taken care before execution of activity.

Let’s understand like this: Data Migration as a process of moving required (and most often very large) volumes of data from our clients’ existing systems to new systems. Existing systems can be anything from custom-built IT infrastructures to spreadsheets and standalone databases. Data conversion can be defined as a process of converting data from one structural form to another to suit the requirements of the system to which it is migrated.

Lets take a deep drive to understand better:

Why conversion/Migration is more important in ERP?

Before Go-Live in the production environment the required master data, the open transaction data and the historical transaction data need to be imported from the old legacy applications to Oracle Applications. Since data structure and data design in legacy systems are different from those of Oracle Applications, data need to be messaged/ converted satisfying the business rules to suite the Oracle requirement. Initial data can be migrated by any other means as discussed above depending upon cetain paramater like Volumn, usage, complexity , business rule etc..

How we Define Data Conversion

  • Process where existing data from the client’s old system is extracted, cleansed, formatted, and installed into a new system.
  • These can be manual or automated.
  • The big difference is that these are One-time only process that requires extensive testing and preparation.
  • They must be executed and performed before a system goes into production.

What Is An Interface then

  • These are programs for connection between Two Systems In Order To Synchronize the Data.
  • They can be Manual, Batch or Real-Time.
  • Used Repeatedly and Should Therefore Be Designed and Constructed In the Most Efficient Manner Possible.
  • These can Be Triggered by an Event (Such As Running A Concurrent Program) Or It Can Be Scheduled To Run At A Certain Time.
  • Can Be Very Costly To Construct And Maintain.

Does the conversion/migration/interface have Life Cycle

Yes, they have, because they have a significant efforts required in development and design and implementation

  • Functional Designer works with business owners to determine the data mapping and complete the functional design using the Design Templates.
  • If the interface/conversion is automated, the Technical Designer converts functional requirements into technical specs for the construction of the interface programs.
  • The developer uses the functional and technical designs to build and test the interface/conversion programs.
  • More rounds of testing are done until the interface/conversion is migrated to the production environment for deployment.

Conversion is assumed as one time activity but never looks like small activity which can be performed with couple of days.

Lifecycle

How conversion and interface differ?

There are good numbers of parameter on which they can be categorize. Take few of them:

  • Frequency
    • conversions are a one time event
    • interfaces are ongoing
  • Occurrence in the project timeline
    • conversions executed before production
    • interfaces executed during production
  • Manner of execution
    • conversions are batch
    • interfaces may be batch or real time
  • Complexity
    • Conversion does have very complex, its totally depends upon the data mapping activity.
    • coordinating with other systems make interfaces more complex
  • Maintenance
    • Maintence of interface is bit cost intensive task.

Interface Type
You have learned how interface is differ from Conversion/Migration. Now lets take few types of interfaces:
Normally in any system , there are two kinds of interface as:

Inbound Interfaces

  • An inbound interface receives data from one system (legacy) and inserts into Oracle open interface tables.
  • A typical inbound interface would follow these steps:
    1. Extract data from legacy system into a flat file.
    2. Use SQL*Loader or equivalent tool to upload information into a temporary table.
    3. Write a PL/SQL program to take data from the temp table and insert into the Open Interface Tables.
    4. Through the concurrent manager in Oracle Applications, run the standard Oracle Interface program to transform interface tables into Oracle data.

inbound

Outbound Interfaces

o An outbound interface takes data from Oracle tables and inserts it into an external system (via tables or flat file).
o A typical outbound interface would follow these steps:
- Write a PL/SQL program to extract data from Oracle base tables into a flat file.
- Use a custom program to read that data and post it into the legacy system

outbound

Do we have some other standard way to do interface?

  • Open Interface is a table based interface registered as a concurrent program
    • process records in batches.
    • spawned(Pro-C) or PL/SQL based programs.
  • API (Application Program Interface) is a parameter based stored procedure
    • directly impacts base database tables.
    • may be called from Oracle open interfaces,Forms, Reports.
  • EDI (Electronic Data Interchange) uses industry standard data definitions(US/ANSI/X.12) for transmission of documents such as PO’s, Invoices, Sales Order, etc.Oracle provides some EDI transactions through EDI Gateway.(
  • Enterprise Application Integration (EAI) solutions are often used when complex integration requirements exist.

What Is An Open Interface Table (OIT)?

  • For inbound interfaces, the interface table is the intermediary table where data from the source application temporarily resides until it is validated and processed into an Oracle base table through a standard import concurrent program.
  • Open Interface Tables are standard Oracle tables.
    • Oracle uses OITs to provide a simple interface to Oracle base tables.
    • Oracle has list of all the open interface that oracle offered in there product.

Oracle Interface Program

  • Most Oracle modules have standard import programs (concurrent processes) to facilitate custom inbound interfaces. The specific processing performed varies by application.
  • These programs pull data from the open interface tables, validate the data, and then insert into one or more Oracle base tables.
  • Upon successful completion of processing, the program deletes the processed rows from the interface table or marks them as completed.
  • Depending on the import, errors can be viewed in various ways (exception reports, error tables, forms, etc…).

Examples of standard import programs:

  • GL: Journal Import
  • AP: Payables Open Interface
  • AR: Customer Interface
  • INV : Item Import
  • AR - Autoinvoice

Ok, thats is all about Conversion and Interfaces briefing. I will write some more for Tools used for Conversion/Interface and will discuss some granular details about a conversion/migration project and share some information about how and where AIM’s documents fits into conversion and Migration projects. So watch out this space for some more stuff for conversions.. Till than..your comment and requset you to share some information relaeted to these areas.icn thumbs 32x32

 

Posted in Conversion | 42 Comments »

Search

Posted on June 9th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post


Posted in Uncategorized | Comments Off

Resources

Posted on June 9th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

I hope you enjoy these links and gain some value from the resources provided here. There’s a ton of great stuff for oracle apps API’s , technologists and more.

Oracle API

These are some links for oracle documentation 

Oracle Documentation (Release 12) hot103cxz2.gif

Oracle Financials RXi Reports Administration Tool

Posted in Uncategorized | Comments Off

Copyright

Posted on June 9th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post


Posted in Uncategorized | Comments Off

Disclaimer

Posted on June 9th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

I am not and never worked as an employee of Oracle, anything I expressed, share here represent personal conjecture based upon experience, practice and observation.

Driven by a desire to excel by providing cost-effective and quality solutions, I was involved with many Oracle application implementation and service projects and this blog is my endeavor to re-arrange the information on my professional experience with Oracle apps ,other Oracle technology.

This is my personal website, maintained by myself (at present), during my non-office hours and mainly over the weekend. It’s an educational, non-profitable but self-sustainable website that contains information and resources related with my own work and experience with Oracle application.

It’s a part of a desperate attempt to conserve my few drops that I could manage out of the sea of available knowledge and a few special ones from my own innovations.

The opinions expressed here represent solely my own and does not represent the thoughts, intentions, plans or strategies of my current & previous employers and their clients.

Oracle Application is product of Oracle. You should consult with oracle Directly on specific facts and  situations.

Oracleappshub.com©  is purly for knowledge sharing and learning purpose, focus on Oracle Application Product and other Oracle Technology

Posted in Uncategorized | Comments Off

Understanding Accounting from Techies Mind

Posted on June 8th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

Indeed, this is one of good area, where most of techies have lot of confusion and illusion about when accounting comes. Many of consultant came from Technical background and gradually moved into doing some techno -functional role or pure functional role, thus it is essestintial to understand the basic accounting and Guided principal .

Normally, there are two basic accounting methods available in the business world:

  • Cash
  • Accrual

And most of the ERP accounting products weather its SUN system, Oracle financial or SAP have functionality to capture on the basis of set up.

Then want is the difference:

handCash Basis Accounting
This is what “Based on Realization

We Most of us use the cash method to keep track of our personal financial activities.

The cash method recognizes revenue when payment is received, and recognizes expenses when cash is paid out.

For example, our local grocery store’s record is based on the cash method. Expenses are recorded when cash is paid out and revenue is recorded when cash or check deposits are received

If we summarize, under the cash basis accounting, revenues and expenses are recognized as follows:

  • Revenue recognition: Revenue is recognized when cash is received.
  • Expense recognition: Expense is recognized when cash is paid.

Take a note the word “cash” is not meant literally - it also covers payments by check, credit card, barter, etc.

Moreover it is not standard method in compliance with accountings matching principle.

handAccrual Basis Accounting
This is what “Based on Recognition

The accrual method of accounting requires that revenue be recognized and assigned to the accounting period in which it is earned. Similarly, expenses must be recognized and assigned to the accounting period in which they are incurred.

Then the underline question is what is accounting Period, Let explain like this normally a company tracks the summary of the accounting activity in time intervals, which we normally called as Accounting periods. These periods are usually a month long. It is also common for a company to create an annual statement of records. This annual period is also called a Fiscal or an Accounting Year.

In the accrual method relies on the principle of matching revenues and expenses. This principle says that the expenses for a period, which are the costs of doing business to earn income, should be compared to the revenues for the period, which are the income earned as the result of those expenses. In other words, the expenses for the period should accurately match up with the costs of producing revenue for the period.

Take a case:
logo mvp 152Company is doing a business and they have to pay sales commissions expense, so sales commissions expense should be reported in the period when the sales were made (and not reported in the period when the commissions were paid). Similarly, Salary/Wage to employees are reported as an expense in the week/month when the employees worked and not in the week/month when the employees are paid. If a company agrees to give its employees 2-month equivalent salary of its 2006 revenues as a bonus on January 25, 2007, the company should report the bonus as an expense in 2006 and the amount unpaid at December 31, 2006 as a liability. This is most simple kind of matching principal normally has.

In general, there are two types of adjustments that need to be made at the end of the accounting period.

  1. The first type of adjustment arises when more expense has been recorded than was actually incurred or earned during the accounting period.
  2. Similarly, there may be revenue that was received but not actually earned during the accounting period. Also known as Un-earned Revenue.

The accrual method generates tax obligations before the cash has been collected (because revenue leads to tax and revenue is recognized against receivable and not against receipt of money).

If we summarize, under the accrual basis accounting, revenues and expenses are recognized as follows:

  • Revenue recognition: Revenue is recognized when both of the following conditions are met:
    • Revenue is earned
      • i.e. when products are delivered or services are provided.
    • Revenue is realized or realizable.
      • i.e. either cash is received or it is reasonable to expect that cash will be received in the future.
  • Expense recognition: Expense is recognized in the period in which related revenue is recognized (Matching Principle).

Timing differences in recognizing revenues and expenses
Various accounting books did mention four potential timing differences in recognizing revenues and expenses between these of two. Just to recap of those:

a. Accrued Revenue: Revenue is recognized before cash is received.
b. Accrued Expense: Expense is recognized before cash is paid.
c. Deferred Revenue: Revenue is recognized after cash is received.
d. Deferred Expense: Expense is recognized after cash is paid.

Compare with a Case to explain these two methods

Your company purchase a new Laptop on credit in May 2007 and pay $1,500 for it in July 2007, two months later.

Under the both case see how this makes a difference:

  • Using the cash method accounting, you would record a $1,500 payment for the month of July, the month when the money is actually paid.
  • Under the accrual method, you would record the $1,500 payment in May, when you take the Laptop and become obligated to pay for it.

Pros and cons of these Two accounting method
Maintence
: The cash method is easier to maintain because you don’t record income until you receive the cash, and you don’t record an expense until the cash is paid, where as in the accrual method, you will typically record more transactions.

Cash-basis accounting defers all credit transactions to a later date. It is more conservative for the seller in that it does not record revenue until cash receipt. In a growing company, this results in a lower income compared to accrual-basis accounting.

Do you what is meant by GAAP?
No, I don’t know, but knows most of ERP follows these. Lets explain this way:
The word”generally accepted accounting principles” (or “GAAP”) consists of three important sets of rules:
(1) The basic accounting principles and guidelines,
(2) The detailed rules and standards issued by FASB(Financial Accounting Standards Board and its predecessor the Accounting Principles Board (APB)
(3) The generally accepted industry practices.

Normally Standard GAAP will have various guided Principal, such as

  • Economic Entity Assumption
  • Time Period Assumption
  • Cost Principle
  • Matching Principle
  • Revenue Recognition Principle

Will take a seprate case of some of them to understand in better way.

If you want to know more about GAAP, weather US-GAAP, UK-GAAP , refer wikipedia

ERP/Oracle Financials
Oracle Financials have been developed to meet GAAP requirements as well as the special needs of different countries. For example, in Oracle Payables you can choose whether to record journal entries for invoices and payments on an accrual basis, a cash basis, or a combined basis where accrual journal entries are posted to one set of books and cash basis journal entries are sent to a second set of books.

Will continue with some additional accounting stuff, keep reading and commenting.icn thumbs 32x32

Posted in Basic Accounting, Beginner, JumpStart | 13 Comments »

Do you know what is “Expense Itemization Rules” in i-expense ?

Posted on June 7th, 2007 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

This is new enhancement we have seen in 2nd generation i-expense version, where there is provision of setting up of Itemization rule. In layman language, it can be explained as ..when an employee stays in a hotel on a business trip, he receives one receipt for his stay. That one receipt includes hotel stay, food, room service, laundry and other personal expenses (of course.). The Expense Itemization feature allows an employee to enter one receipt for the whole amount and lets them itemize the same.

This feature allows you to require itemization and determine which expense types for the itemization are independent of each other. If itemization is required, you can also identify into which expense types a receipt can or should be itemized. This expedites the expenses entry process and ensures more accurate accounting. This also helps in easy reconciliation for your finance department, and also no argument for clarifying personal stuff.
itemized

Take a note, oracle 11.5.10.2 does not have any seeded report that will have drill down information for itemized claim. So don’t get surprised , if Finance will ask you for detailed Itemized report. icn thumbs 32x32

Posted in Oracle Payable | No Comments »

Page 2 of 3«123»

« Previous Entries Next Entries »