This action might not be possible to undo. Are you sure you want to continue?
Robert Smith ABeam Consulting, USA
18 Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Step 1: Create Discoverer EUL . . .17 About the Author . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Step 3: Creating Business Areas . . . . . . . . . . . . . . . . . . . . . . .13 Conclusion and Lessons Learned . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 Step 2: Define User Report Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7 Step 4: Defining Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 About ABeam Consulting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
You will also learn how to create a Discoverer EUL. but not in a format that is very useful. Log into Discoverer Administrator connecting to database as <database account: e. Step 1: Create Discoverer EUL Oracle now provides an end user layer (EUL) when you load the Discoverer 10g product. you will see a popup window that says there are no EULs available to this user and prompts you to create one – click Yes. Creating a custom Discoverer End User Layer (EUL) will allow you to obtain the data your company needs to assist in closing the following modules: • • • • • • • • Purchasing Accounts Payable Accounts Receivable Order Management OPM Inventory OPM Production OPM MAC OPM Costing This paper will identify some key universal data elements needed to ensure accurate and timely OPM and financials month-end closings.g. in most cases the reports a user will need are for specific company processes that require manipulating the seeded EUL to create a custom version. the data generated will be easily accessible. click Finish Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 3 . Following are the steps to create a custom EUL: 1. This is particularly true with the Oracle Process Manufacturing (OPM) reports. Proper use of a query tool such as Oracle Discoverer allows companies to customize the data they need to make their month-end closing run smoother. However. This EUL has pre-configured business areas with the joins already defined. By creating your own EUL. you can control how elements are defined. Enter the Schema/Password that contains the FND tables – this has to be set to APPS/<pwd>. Using Oracle® Business Intelligence Discoverer to query the valuable information your company needs to ensure a timely and accurate month-end close can eliminate some of those hours. Standard Oracle reporting provides valuable information. and you will be able to share it in a variety of formats. 2.Introduction Month-end closing can be hard enough without having to spend hours obtaining the information you need. create business areas and create user reports to obtain data that will aid in the monthend closing process. You MUST check the box beside the “New EUL is for use by Oracle Applications users ONLY” option. What’s more. 3. APPS>/<pwd>. In some cases this seeded EUL will meet the requirements of a company.
Since the financial variances are based on costing formulas. in some industries you should review WIP batches to ensure they really are in WIP. After obtaining the list. throughout the month users can be proactive and use exceptionbased reports to correct issues or prepare them with documentation of final numbers. If a receipt is past due it is typically because it has not yet been entered or it is truly past due. there could be a variance and the production floor did exactly as their formula said. As users have learned. however. This leads to the logical question typically asked by Accounting: how can I know if all the transactions are in the system and if they are accurate? Once this question can be answered. 2. This review assumes the scheduled arrival date from the purchase order is accurate. 3. 1. Discoverer is strongly recommended for the conversion of this data due to its ability to be customized easily. they need to ensure they understand the business processes related to their areas. Depending on your network. Once again. Ensure OPM Production transactions are complete – Review production batches in completed status and not yet closed. Below are some examples of necessary data that will ensure all transactions are completed in a timely and accurate manner.NOTE: If you do not have any EUL on the system you may need to log into Discoverer on the new instance as EUL_US/EUL_US. Ensure Production Variances are accurate both financially and through production – The financial variance is found while reviewing the subledger. you can export the results to Excel for further sorting and analysis. accounting can work with manufacturing personnel to proactively monitor the monthly activity and assist in system and financial accuracy. This exception-based approach is what users should look for when reviewing their processes and requesting reports appropriately. Oracle provides a seeded report called Expected Receipts Report. Ensure OPM Receipt/Void/Return transactions are complete – Review open purchase orders for past due receipts. Converting this report to Discoverer is strongly recommended to allow users to tailor the report to their specific needs and export to Microsoft Excel. Step 2: Define User Report Requirements For users to determine what reports are needed. as opposed to not entered at all. This listing can be reviewed by accounting and other personnel to ensure it is past due. Also. OPM will create an entry for each transaction. but they must make sure all transactions are completed to ensure accurate financial and manufacturing reporting. The cloned instances start out with EUL_US EUL on the db so this should not be necessary on the cloned instances. which allows you to enter your cutoff date and run it. Month-end closing reflects what happened in a month. This report only displays receipts that are due. This accurate reporting will also benefit the manufacturing personnel as this past due information is used to calculate vendor performance criteria. since some of their objectives are based on batch inputs and outputs. This causes much dispute between accounting Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 4 . This review can be accomplished within the application by using the production workbench and viewing the batches by status. creating the EUL may take some time — anywhere from less than 5 minutes to around 20 minutes. not yet received. Making sure all batches are in their proper status also helps manufacturing.
7. Ensure OPM costing item standards from period to period are accurate – Users should review item costs (either standard or actual) from one period to another to ensure any large variance is able to be explained. users need to view (in total. Discoverer will allow for better data manipulation than the seeded Oracle report. If the levels are consistently where they are expected. by item) the beginning inventory quantity. Ensure OPM Inventory transactions are complete – Since these transactions are not scheduled. Oracle provides a Daily Transaction Detail Report. indicators on which both groups are judged. they are harder to predict. transaction (by type) quantity and ending inventory. Users should also review all transactions with the CREI document type. Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 5 . cycle count adjustments. Reviewing inventory levels is always a concern and Discoverer will allow users to present the data to meet their company’s requirements. which in many companies is not time effective. this step should not be run alone. Ensure OPM Transfer transactions are complete – Review open inventory transfers that have a scheduled delivery date that is past due. so they must go through all transactions. Ensure OPM Shipping transactions are complete – Review order lines that have a past due scheduled ship date. 4. The user is looking for inventory adjustment transactions for the month and the ability to compare to past months to ensure all are entered. However. Discoverer allows users to review batches in the ways that reflect their own unique processes. The list can be exported to Excel for further review and manipulation. 6. This “creating” of inventory should be monitored. 5. Incomplete inventory transfers will cause inventory inaccuracies. Discoverer will allow this data to be reported on an exception basis to facilitate quicker responses from manufacturing. you could assume all transactions are completed. Missing customer expectations will not be tolerated forever. export and review data in a user friendly manner. CREI transactions do not occur after the initial inventory load. This is particularly helpful prior to the cutoff date to get a feel of where inventory levels are.and manufacturing and leads to the need for a report to validate production formula usage. 9. However. These “create immediate” entries should be rare and have complete documentation to accompany them. A better way to get this information is to use a query tool like Oracle Discoverer and query the IC_TRAN_CMP table for ADJI document types. Provide a perpetual view of inventory – Often times. It should become a tool which validates the steps outlined above. this allows users to verify whether shipment is late or just not recorded. Oracle provides a seeded Inventory Transfer Report that can be run for in-transit and pending transfers with the scheduled release date range ending on the pre-defined cutoff date. but the user can’t specify the type of transactions. 8. etc. Accurate and timely reporting of these adjustments are important to manufacturing and accounting as they drive expenses and inventory values. Perform Preliminary Close of each warehouse – This review will allow the user to run their inventory valuation reports throughout the month to monitor inventory levels. Manufacturing personnel are usually more concerned about accurate sales numbers than accounting. As with past due receipts. Nonshipped lines do not create revenue (sales). This review can be accomplished in the application by going to the shipping transaction form and querying not shipped lines with a scheduled ship date range ending with the pre-defined cutoff date. which affect manufacturing personnel and accounting objectives. they are still important because many industries have a high quantity of monthly adjustments due to miscellaneous use. In many companies. Discoverer will allow users to analyze. By reviewing this proactively it can also identify a serious problem.
Discoverer makes the review of the subledger almost enjoyable as it can provide flexibility that the seeded report cannot. AR Aging by customer party – Many users utilize Oracle’s party concept with customers and would like to see the aging for these parties. Discoverer will allow for this view of data. sub-totals Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 6 . you should make sure it has at least the following pieces of information: • • • • • • • Description of what the report is used for Business flow using the report Fields required on the report and screen shots of where in the application the data resides Report header information Report field layout Field sorting Report totals. but represents a majority of the requests made by users. Purchase Price Variance (PPV) review – Before the month-end is completed. the sales order prices should be compared to standards to ensure margins are being met. This document is important to ensure proper communication with the technical team or Discoverer administrator. For users used to working with Oracle AIM documentation. Sales Order price versus standard and/or list prices – Before the month-end is completed. This is where a powerful query tool like Oracle Discoverer can be utilized to obtain all the data a user requires to make the results more flexible and easier to export to Microsoft Excel. Now that the users have identified what data they want. 11. Discoverer can provide users with exception reports that will allow for easier review of any questionable data. the document is the MD050. they need to create a functional report specification document for their Discoverer Administrator to review. the PPV should be reviewed and any large variances should be investigated to ensure accuracy. 14. Discoverer will allow for this through the use of seeded tables and calculated fields. but many times users would like to see the details of the values. especially to validate GL accounts. 13. This information will allow users to explain month-end numbers and correct errors if any are found. Unfortunately. the seeded aging reports only show details at the account level. This is where Discoverer will provide benefit. 12. Identifying and correcting during the month is less stressful then rushing around at month end. The above data is not the only data necessary. It gives accounting time to correct and also to investigate why an unexpected result occurred. The subledger should become the accountant’s best friend. 10. Accounts Receivable Reconciliation Report details – The AR Reconciliation Report shows totals. Discoverer will allow users to tailor the view of the report and allow for easier exporting.This view is not possible through standard Oracle reporting. Run Test Subledger(s) – This review should be done throughout the month to catch any flagrant accounting errors. 15. Review details of the Accounts Payable Account Analysis – The Accounts Payable Account Analysis seeded report will show users the transactions detail in the accounts specified within the parameters. Whatever your company calls the document. and against the list price to see when sales are changing the prices.
In the next section we will illustrate the steps necessary to create a business area.gme_batch_header.After the functional specification is completed. A common technique to ensure the data is accurate is to create the SQL in a tool like Toad to ensure the data returned is what the user is seeking. and Item Number of the Products of the Batch for batch in WIP status. gme.gme_material_details and gmi. Within Oracle AIM this is the MD070. Depending on the company the user can then create their own report or the Discoverer administrator will create the report for them. Step 3: Creating Business Areas For this example we are going to assume the user has requested a report including Batch Number. the next step for the Discoverer Administrator is to determine if there is a current business area that contains the tables and joins for the requested data.ic_item_mst_b. Following are the steps required to create a new business area: 1. After ensuring the understanding of the data requested. Batch Status. the next step is for the Discoverer administrator to review and generate a technical report specification. then the Discoverer administrator will notify the user of the business area that will allow them to get their report. The purpose of this document is to determine where the data requested is stored in Oracle and how it is joined together. Log on to 10g Discoverer Administrator to begin the process Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 7 . However. If there is. if there is not a business area that could be adjusted to meet the data requirements of the report specification. a new business area will need to be created. Through our technical review we have discovered the tables needed are gme.
Click “Create a new business area” and then select the Next > button 3. These schemas are called users on the screen below. Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 8 . Remember in our example we need the GME and GMI schemas.2. Select the schemas owning the tables needed.
gme_batch_header. Select the tables to add to the business areas. Click the Next > button. For our example we determined we needed gme. Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 9 .gme_material_details and gmi. Using the defaults is recommended. 5. Continue the configuration.ic_item_mst_b. Click the Next > button.4. gme. 6. 7.
8. 9. Click the Next > button. Click Finish. Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 10 . Objects are loaded when completed business area appears. 10. Name the business area.
gme_batch_header to the gme.ic_item_mst_b.11.gme_material_detail and then join gme. Open the new business area and highlight the first table to join and click “Insert Join. Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 11 .” 12. Create joins on tables which have been identified in the technical review. In our example we need to join the gme. Join the master items table with the detail items table.gme_material_detail to gmi.
Click the Next > button. Select appropriate values and click the Finish button. Repeat steps 11 – 14 for each table that needs joins. 15.13. 14. Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 12 . You will return to the main screen.
for this example we are going to assume the user has requested a report requiring Batch Number. 17. Step 4: Defining Reports Now that the business area is defined. and Item Number of the Products of the Batch for batch in WIP status. Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 13 . Below are the steps to create a Discoverer report. To review. Next. grant user access to the business area by clicking Tools>Security and adding the user name to the newly created Business Area. Click OK. the report can be defined.16. The report is ready to be created. Batch Status.
After selecting type click the Next > button. Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 14 . Most reports are able to be satisfied by Page-Detail Table. Click “Create a new workbook” and select type of workbook to create. 2. Logon to Oracle 10g Discoverer Desktop (Note: Many times a colon (: ) is needed after the user name to allow the user to access Discoverer). For our example it does as well.1.
This is where you define the conditions for your query. select the Next> button. After selecting columns.3. 5. In our example we need to select only the items that are products and also only batches that are in WIP status. 4. This is where you could change the order of the columns. Batch Status and Item Number. click the Next > button. Change layout if necessary. Click the New button to create conditions and select columns and values. Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 15 . When complete. For our example we need Batch Number. The next step is to select the fields requested in the report specifications. Create conditions.
When complete select the Next > button. Select column to sort by if the specification identified a sort. select the Finish button to begin the query. This is where users define calculated fields through mathematics or functions. Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 16 . Define calculations. so when complete click the Next > button. Our example does not require calculations so when complete.6. 7. Our example does not specify. Click the OK button and then repeat for additional conditions. 8.
Oracle Discoverer Best Practices | August 2008 | © ABeam Consulting 17 . The biggest risk here is wasted time developing something not wanted. 2. business area and report are not hard. This is the fastest way for users to develop the feeling that Oracle is inaccurate. Conclusion and Lessons Learned Month-end closing is a critical part of the business calendar and having the right data at the right time will let you make timely and accurate decisions. The difficult part of the process is the review of the user specifications and determining if a current business area exists that meets the needs of the user. As this paper has shown. When the query completes. Test queries thoroughly before releasing to general user population. Through the years the following lessons have been learned by the author: 1. Utilize resources. Once the basic understanding is there. Trust users. but fails in the field. The technical resources within your company can assist in helping understand tables and joins. 3. 4. With some thought and practice you too can “Discoverer” your month-end closing. The risk here is the report tests positive in development. Over time. business areas can become more complex. This is highly dependent on the strength of the business area design. Make sure you know what the user really wants before the report is developed.9. This is just like with Oracle report development. the report is essentially complete. the steps to creating a EUL. Titles can be added per the specification as well as any column name changes. users will be able to generate their own reports.
This reference guide will describe in detail the screen and steps discussed above. and enhance organizational performance for leading multinational and domestic companies worldwide. leverage technology innovation. Headquartered in Tokyo. Company and product names mentioned may be trademarks or registered trademarks of their respective owners. All rights reserved. Mr. As a former plant controller.500 professionals serve more than 700 clients throughout Asia.com. For more information. About the Author Mr.learndiscoverer. Order Management and Oracle Process Manufacturing (OPM) modules. ABeam Consulting. extensive knowledge of business process evaluation and the mapping of these processes to the Oracle Financials. www. ABeam’s 3. agriculture. the Americas and Europe. Smith is a CPA with a thorough knowledge of accounting & finance principles. please visit www. Pragmatic approaches ensure that clients gain measurable value more quickly. steel. Company and product names mentioned may be trademarks or registered trademarks of their respective owners. ABeam partners with clients to diagnose and solve their real challenges with solutions that combine industry and operational best practices with technical expertise. Copyright © 2008 ABeam Consulting.com that has provided helpful hints and suggestions in the past. Manufacturing and Supply Chain modules. Copyright 2008. he has project experience in the chemical. Also the authors of the handbook have a website www. Smith is a Senior Consultant with ABeam Consulting and has more than 13 years of experience in the manufacturing industry working with Oracle’s E-Business Suite focused on Financials. As a consultant.abeam.com 18 . food and beverage.Additional information about Discoverer can be found in the Oracle Press Oracle Discoverer 10g Handbook. All rights reserved. pharmaceutical and brick industries. Purchasing. In addition. he has effectively interfaced with both production and finance departments as well as end users and management. ABeam. About ABeam Consulting ABeam Consulting provides business transformation services that create strategic advantage. improve business processes.
This action might not be possible to undo. Are you sure you want to continue?
We've moved you to where you read on your other device.
Get the full title to continue listening from where you left off, or restart the preview.