Saturday, 31 May 2014

Date parameters in Oracle Report Query

1.If the date is already in the format 'mm/dd/yyyy' in database, then at the time of defining date as parameter, no need to write as;

 XXX_TRX_DATE BETWEEN NVL(TO_DATE(:P_DATE_FROM,'mm/dd/yyyy'),XXX_TRX_DATE)
AND NVL(TO_DATE(:P_DATE_TO,'mm/dd/yyyy'),XXX_TRX_DATE)

instead following can be written:

 XXX_TRX_DATE BETWEEN NVL(:P_DATE_FROM, XXX_TRX_DATE)
AND NVL(:P_DATE_TO, XXX_TRX_DATE)

No need to convert to TO_DATE format, as its already in 'mm/dd/yyyy' format.
If its not in above format, then we need to convert into TO_DATE format.


2. While executing the parameter date query, always change the Type of the bind variables to 'Date' for the date parameters in TOAD as shown below.


3. If you are creating xml data template for the parameter query. Always  define the parameter datatype as 'Date' as shown below;

<parameter name="p_XXX_date" dataType="Date" />

Tuesday, 13 May 2014

Oracle Apps explained through real time example with technical terms

Story

The below example explains a few of the important terms and concepts used in the Oracle E-Business Suite. This would be a good starting point for the beginners to better understand the concepts behind Oracle Applications.

Say David is the owner of a wholesale fruit shop. He buys various fruits like apples, oranges, mangos and grapes etc from farmers directly and sells them to retail shop owners and also to the direct customers.

The farmers are referred to as VENDORS/SUPPLIERS in Oracle Applications. David
keeps track of all his vendors’ information like addresses, bank account and the amount he owes to them for the fruits that he bought etc, in a book named PAYABLES.

David gets an order from a retail shop owner of Fresh Mart, for a shipment of 11 bags of apples, 25 bags of oranges and 32 kgs of grapes. In Oracle Apps, bags and kgs are referred to as UOM (unit of measure), Fresh Mart is called CUSTOMER and the order is referred to as SALES ORDER. David maintains a book called
ORDER MANAGEMENT where he writes down all the details of the SALES ORDERS that he gets from his customers.
Say the fruits have been shipped to the customer Fresh Mart. David now sends him the details like cost of each bag/fruit, the total amount that the customer has to pay etc on a piece of paper which is called INVOICE / TRANSACTION. Once the INVOICE has been sent over, the customer then validates this against the actual quantity of fruits that he received and will process the payments accordingly. The invoice amount could be paid as a single amount or could be paid in installments. David’s customer, Fresh Mart pays him in installments (partial payments). So David has to make a note of the details like date received, amount received, amount remaining, amount received for what goods/shipments/invoice etc, when David receives the payments. This detail is called RECEIPT, which will be compared to the invoice by David to find how much Fresh Mart has paid to him and how much has to be paid yet. This information is maintained in a book named RECEIVABLES to keep track of all the customers, their addresses (to ship the items), what and how much he has shipped to his customers and the amount his customers owe him etc.

David’s fruit business has begun to improve and has attracted more and more customers. As a result, David decided to buy a cold storage unit where he could stock more fruits. In Apps, this cold storage unit is known as WAREHOUSE and all the fruits are referred to as INVENTORY. Due to increase in customers, David needs to hire more people to help him out in his business without any hiccups. These workers are called EMPLOYEES. At the end of every month, David pays the salary for all his employees through Checks. These checks are nothing but PAYROLL in Apps.

At the end of every month, David prepares a balance sheet in a book called GENERAL LEDGER to determine how much profit/loss he got and keeps track of the money going out and going in.
As the business grows, it becomes impossible to record everything on a paper. To make everybody’s life easier, we have very good tools in the market, which help the business men to keep track of everything. One such tool is Oracle E-Business Suite.
Oracle Applications is not a single application, but is a collection of integrated applications. Each application is referred to as a module and has it own functionality trying to serve a business purpose.
Few of the modules are Purchasing, Accounts Payables, Accounts Receivables, Inventory, Order Management, Human Resources, General Ledger, Fixed Assets etc.

Here is a high level business use of various modules:

Oracle Purchasing handles all the requisitions and purchase orders to the vendors.

Oracle Accounts Payables handles all the payments to the vendors.

Oracle Inventory deals with the items you maintain in stock, warehouse etc.

Order Management helps you collect all the information that your customers order.

Oracle Receivables help you collect the money for the orders that are delivered to the customers.

Oracle Human Resources helps maintain the Employee information, helps run paychecks etc.

Oracle General Ledger receives information from all the different transaction modules or sub ledgers and summarizes them in order to help you create profit and loss statements, reports for paying Taxes etc. For Example: when you pay your employees that payment is reported back to General Ledgers as cost i.e money going out, when you purchase inventory items and the information is transferred to GL as money going out, and so is the case when you pay your vendors. Similarly when you receive items into your inventory, it is transferred to GL as money coming in, when your customer sends payment, it is transferred to GL as money coming in. So all the different transaction modules report to GL (General Ledger) as either “money going in” or “money going out”, the net result will tell you if you are making a profit or loss.

All the equipment, shops, warehouses, computers can be termed as ASSETS and they are managed by Oracle Fixed Assets.

There is a lot more in Oracle applications. This is the very basic explanation just to give an idea of the flow in ERP for the beginners.


Oracle Apps  Important Terminology and Tools:

Invoice
Receipt
Customer
Vendor
Buyer
Supplier
Purchase Order
Requisition
ACH: Account Clearance House
Sales Order
Pack Slip
Pick Slip
Drop Ship
Back Order
ASN: Advance Shipping Notice
ASBN: Advance Shipping Billing Notice
ATP: Available to Promise
Lot/Serial Number
DFF: Descriptive Flex Fields
KFF: Key Flex Fields
Value Sets
Organization
Business Unit
Multi Org
Folders
WHO Columns
Oracle Reports
Oracle Form
Workflow Builder
Toad
SQL Developer
SQL Navigator
Discoverer Reports
XML/BI Publisher
ADI: Application Desktop Integrator
Winscp

Putty

Sunday, 11 May 2014

Important Oracle Apps Interview questions

Important Oracle Apps Interview questions

Especially questions are solely asked based on your CV. Following are some of the questions for oracle apps interviews.

  1. What are the types of oracle reports?
      Ans: Tabular,
              Group left,
              Group Above,
              Matrix,
              Matrix with group,
              Form,
              Form letter,
              Mailing label.

     2.  What are the table used during report creation? (Questions based on reports created or mention in     CV)

     3. What are the types of report triggers? Mention sequentially.
 
     Ans: Before parameter form,
             After Parameter form,
             Before Report,
             Between pages,
             After report.
     
     4. Mention the mandatory user parameter.

     Ans: P_CONC_REQUEST_ID

     5. What is legacy system of your client?
  
     6. What is the connection or relation between 'concurrent request' and 'data definition' ?

     Ans: 'Short Name' to be copied in 'Code' field of the data definition window.

     7. Date when the project started and went live. And the your role during the supporting phase of the project.

     8. Explain the complete flow of SCM with tables include.

     9.Explain the Interface programs steps.

     10. Name all the TCA tables.

     11.  What are the ways to create Order in Oracle apps.

     12. Give the difference between test plan and test scripts.

     13. Questions related to AIM documentations.

     14. How to Copy the existing order entry data to a new in Order creation window.

     15.How to make changes to an existing standard report. Explain whole process.

     16.Name any 5 tables from PO and AR modules.

     17.What are the types of triggers in PLSQL. Explain.

     18. Primary keys between tables oe_order_headers_all and oe_order_lines_all.

     19. Difference bet VARCHAR(30) and CHAR(30).

     20. State Bulk collect in PLSQL with example.

     21. Collection in PLSQL.

     22. Difference between ROWNUM and ROWID.

     23. What is System Profile options in apps.

     24. How to attach concurrent program to a request group.

* Please comment if you have some different important interview questions.

    Important Points for Oracle standard Reports

    Important Points for Oracle standard Reports

    Following are the points that are mandatory every time when we edit or create report in Oracle standard Report. 

    1. For a sql query having parameter and binding variables, the parameters will be added automatically on the "USER PARAMETERS" on the left side of Object navigator window. 
         If date parameter is used then right click on the date parameter, go to -> Property inspector. 
         Change the 'Input Mask' to any desired input value. And change the 'Datatype' -> Date.

    2. Click the '+' button (green button) and add a parameter with naming as .P_CONC_REQUEST_ID'.

    3. Edit the 'Before trigger' and 'After Trigger' option.

    Friday, 11 April 2014

    Complete cycle from Creating to registering Oracle report using .RTF and XML Data Template.

    1.Client supply the report layout in any format (excel).

    2.Create and write the query in TOAD (or any other IDE). The output of the query must be similar to the
       client data format. Knowing the important apps tables with columns names and join condition between          them is a key for creating queries for report. In most of the cases, the client provide the tables
       names and column names to be used.

    3.Create a data template (XML) using the query. If you have sample data template file, then just modify the
       existing ones.

    4.Generally, during report creating using data template, we use 'XDODTEXE' as an executable program.
       'XDODTEXE' is an default executable java concurrent program. So, no need to create executable
       program if you are using data template file to create report.

    5. To create the concurrent program. Go to 'Application Developer' in apps -> Concurrent -> Program
       Enter Program ->(Any valid report name. The report name will be used later and will be seen in report          output).
       Short Name->(enter any name)
       Application->(XX_CUSTOM)

       Executable Name-> XDODTEXE (As already mentioned above).
       Format-> (xml).

    6. Copy the report name and pass it to DBA. So that the DBA can add rresponsibility in the resquest group)

    7. Copy the short name and close the form.

    8. In the apps, Go to th eXM: publisher Administrator -> Home -> data Definition.

    9. Click 'Create data template'.

    10.Paste the short name to 'code' field.

    11. Enter name-> (any), Application->XX_Custom

    12.Click apply.

    13.In data template -> click add file and browse the data template xml file.

    14.Run the request in SRS window.

    15. View the output in XML format.

    16.save the ouput xml file in .xml format. (this will be used for importing in BI Publisher)

    17. Create and design the layout in BI Publisher.

    18.REGISTERING THE .RTF FILE:

    19. Go to the data definition and copy the name.

    20.Go to template -> Create 'Template'.

    21.Paste the name, Application as 'XX-CUSTOM' and type as 'RTF'.

    22.In the file -> Browse the .RTF file.

    23.Go to the SRS window of the particular responsibility of AR (Let us consider the DBA
       has attached the AR responsibility) and see the output of the report.