Mar 29, 2010

Data Structure of Oracle Payables

Data Structure of Oracle Payables


Ap_invoices_all
: Invoices > Entry > Invoices
This table stores all the invoices you enter.  For an invoice to be approved, the total invoice amount must be stored in ap_invoice_distributions_all and ap_payment_schedules_all.
Some columns of interest includes :
·         Invoice_num
·         Invoice_date
·         Amount_paid
·         Invoice_currency_code
·         Invoice_type_lookup_code
·         Payment_status_flag


Ap_invoice_distributions_all
: Invoices > Entry > Invoices
This table stores the accounting information for the invoice you have entered. There is one row for each invoice disribution, that is this table corresponds to the Distributions window.
Some columns of interest includes :
·         Line_type_lookup_code
·         Dist_code_combination_id (credit entry)
·         Accts_pay_code_combination_id (debit_entry)
·         Base_amount (in functional currency)


Ap_checks_all
: Payments > Entry > Payments
This table stores payments to suppliers.
Some columns of interest includes :
·         Amount (in functional currency)
·         Check_date
·         Bank_account_name
·         Check_number
·         Payment_method_lookup_code
·         Payment_type_flag


Ap_invoice_payments_all
: Payments > Entry > Payments
This table stores invoice payments to suppliers.  This table is updated when you confirm an automatic payment batch, enter a manual payment or process a Quick Payment.  Void payments are represented as a negative of the original payment line.
Some columns of interest includes :
·         Accounting_date
·         Period_name
·         Amount
·         Payment_num


Ap_payment_distributions_all
: Payments > Entry > Payments
This table stores accounting information for payments.  There is at least one CASH payment distribution for each invoice payment.  Additional rows may include DISCOUNT, GAIN and LOSS distributions where appropriate.
Some columns of interest includes :
·         Line_type_lookup_code (CASH/DISCOUNT/GAIN/LOSS)
·         Base_amount

Data Structure of Oracle General Ledger




Data Structure of Oracle General Ledger


Gl_code_combinations
: Setup > Accounts > Combinations
This table stores the valid account combinations.
The value in your chart of account segments are stored in the columns segment1 to segment30 depending on your application configuration.
For example, say your chart of accounts is
Company – Cost Centre – Account
then segment1 = company, segment 2 = cost centre and segment3 = account.
However, this sequencing of segments is not guaranteed therefore, its best to check your configuration.
Another important column is the account_type which signifies your account is an Asset, Liability, Revenue, Expense or Owners Equity account.

Gl_je_batches
: Journals > Enter
This table stores the journal entry batches. Journal entries are batched in General Ledger.
Some columns of interest includes :
·         Name
·         Set_of_books_id (when you have more than one set of book, you’ll also need to link to gl_sets_of_books)
·         Status
·         Default_period_name
·         Posted_date
·         Posting_run_id

Gl_je_headers
: Journals > Enter
This table stores the journal entry headers.  There is always two journal lines for each journal header.
Some columns of interest includes :
·         Je_category
·         Period_name
·         Set_of_books_id (when you have more than one set of book, you’ll also need to link to gl_sets_of_books)
·         Posted_flag
·         Je_source
·         Name
·         Status

Gl_je_lines
: Journals > Enter
This table stores the journal entry lines. 
The entered_dr and entered_cr stores the amount in the entered currency whereas the accounted_dr and accounted_cr stores the amount in the functional currency.
Other columns of interest includes :
·         Set_of_books_id (when you have more than one set of book, you’ll also need to link to gl_sets_of_books)
·         Period_name
·         Status
·         Description
·         Reference_1..reference10 (these columns links back to your Subledgers)
For example, for Purchasing transactions
Reference_1 = ‘PO
Reference_2 = po_headers_all.po_header_id
Reference_3 = po_distributions_all.po_distribution_id

Payables Open Interface Error in SQL LOAD LOG File

Example of Error File : 

 Payables Open Interface Error in SQL LOAD LOG Files 
=============================================================================
*****************************************************************************************

=============================================================================


SQL*Loader: Release 9.2.0.1.0 - Production on Thu Aug 14 17:30:30 2008

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

Control File:   AP_INVOICES_INTERFACE.ctl
Data File:      AP_INV_TEST.TXT
  Bad File:     AP_INV_TEST.bad
  Discard File:  none specified

 (Allow all discards)

Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array:     64 rows, maximum of 256000 bytes
Continuation:    none specified
Path used:      Conventional

Table AP_INVOICES_INTERFACE, loaded from every logical record.
Insert option in effect for this table: APPEND
TRAILING NULLCOLS option in effect

   Column Name                  Position   Len  Term Encl Datatype
------------------------------ ---------- ----- ---- ---- ---------------------
INVOICE_NUM                         FIRST     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:INVOICE_NUM)||'1'"
INVOICE_TYPE_LOOKUP_CODE             NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:INVOICE_TYPE_LOOKUP_CODE)"
INVOICE_DATE                         NEXT     *   ^  O(") DATE DD-MON-RRRR   
VENDOR_NUM                           NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:VENDOR_NUM)"
VENDOR_SITE_CODE                     NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:VENDOR_SITE_CODE)"
INVOICE_AMOUNT                       NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:INVOICE_AMOUNT)"
TERMS_NAME                           NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:TERMS_NAME)"
DESCRIPTION                          NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:DESCRIPTION)"
LAST_UPDATE_DATE                     NEXT     *   ^  O(") DATE DD-MON-RRRR   
LAST_UPDATED_BY                      NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:LAST_UPDATED_BY)"
CREATION_DATE                        NEXT     *   ^  O(") DATE DD-MON-RRRR   
CREATED_BY                           NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:CREATED_BY)"
GL_DATE                              NEXT     *   ^  O(") DATE DD-MON-RRRR   
LEGAL_ENTITY_NAME                    NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:LEGAL_ENTITY_NAME)"
SOURCE                               NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:SOURCE)"
INVOICE_CURRENCY_CODE                NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:INVOICE_CURRENCY_CODE)"
PAY_GROUP_LOOKUP_CODE                NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:PAY_GROUP_LOOKUP_CODE)"
OPERATING_UNIT                       NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "RTRIM(:OPERATING_UNIT)"
INVOICE_ID                           NEXT     *   ^  O(") CHARACTER          
    SQL string for column : "AP_INVOICES_INTERFACE_S.NEXTVAL"

Record 1: Rejected - Error on table AP_INVOICES_INTERFACE, column INVOICE_DATE.
ORA-01858: a non-numeric character was found where a numeric was expected

Record 21: Rejected - Error on table AP_INVOICES_INTERFACE, column VENDOR_SITE_CODE.
ORA-12899: value too large for column "AP"."AP_INVOICES_INTERFACE"."VENDOR_SITE_CODE" (actual: 20, maximum: 15)

Record 376: Rejected - Error on table AP_INVOICES_INTERFACE, column VENDOR_SITE_CODE.
ORA-12899: value too large for column "AP"."AP_INVOICES_INTERFACE"."VENDOR_SITE_CODE" (actual: 23, maximum: 15)

Record 384: Rejected - Error on table AP_INVOICES_INTERFACE, column VENDOR_SITE_CODE.
ORA-12899: value too large for column "AP"."AP_INVOICES_INTERFACE"."VENDOR_SITE_CODE" (actual: 23, maximum: 15)


Record 2: Rejected - Error on table AP_INVOICES_INTERFACE.
ORA-01400: cannot insert NULL into ("AP"."AP_INVOICES_INTERFACE"."INVOICE_ID")

Record 4: Rejected - Error on table AP_INVOICES_INTERFACE, column INVOICE_DATE.
ORA-01847: day of month must be between 1 and last day of month

Record 51: Rejected - Error on table AP_INVOICES_INTERFACE, column INVOICE_DATE.
ORA-01861: literal does not match format string

Record 1: Rejected - Error on table AP_INVOICES_INTERFACE, column INVOICE_DATE.
ORA-01858: a non-numeric character was found where a numeric was expected

Record 21: Rejected - Error on table AP_INVOICES_INTERFACE, column VENDOR_SITE_CODE.
ORA-12899: value too large for column "AP"."AP_INVOICES_INTERFACE"."VENDOR_SITE_CODE" (actual: 20, maximum: 15)

Table AP_INVOICES_INTERFACE:
  1062 Rows successfully loaded.
  4 Rows not loaded due to data errors.
  0 Rows not loaded because all WHEN clauses were failed.
  0 Rows not loaded because all fields were null.


Space allocated for bind array:                 254904 bytes(52 rows)
Read   buffer bytes: 1048576

Total logical records skipped:          0
Total logical records read:          1066
Total logical records rejected:         4
Total logical records discarded:        0

Run began on Thu Aug 14 17:30:30 2008
Run ended on Thu Aug 14 17:31:10 2008

Elapsed time was:     00:00:39.78
CPU time was:         00:00:00.10



=============================================================================
*****************************************************************************************

=============================================================================

SQL*Loader: Release 9.2.0.1.0 - Production on Tue Aug 19 20:19:14 2008

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

Control File:   AP_INVOICE_LINES_INTERFACE.ctl
Data File:      AP_LINE_TEST.TXT
  Bad File:     AP_LINE_TEST.bad
  Discard File:  none specified

 (Allow all discards)

Number to load: ALL
Number to skip: 0
Errors allowed: 50
Bind array:     64 rows, maximum of 256000 bytes
Continuation:    none specified
Path used:      Conventional

Table AP_INVOICE_LINES_INTERFACE, loaded from every logical record.
Insert option in effect for this table: APPEND
TRAILING NULLCOLS option in effect

   Column Name                  Position   Len  Term Encl Datatype
------------------------------ ---------- ----- ---- ---- ---------------------
REFERENCE_2                         FIRST     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:REFERENCE_2)"
TYPE                                 NEXT     *   ^  O(") CHARACTER           
  (FILLER FIELD)
ACCOUNTING_DATE                      NEXT     *   ^  O(") DATE DD-MON-RRRR    
DESCRIPTION                          NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:DESCRIPTION)"
DIST_CODE_COMBINATION_ID             NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:DIST_CODE_COMBINATION_ID)"
LAST_UPDATED_BY                      NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:LAST_UPDATED_BY)"
AMOUNT                               NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:AMOUNT)"
CREATED_BY                           NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:CREATED_BY)"
CREATION_DATE                        NEXT     *   ^  O(") DATE DD-MON-RRRR    
ATTRIBUTE1                           NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:ATTRIBUTE1)"
ATTRIBUTE2                           NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:ATTRIBUTE2)"
ATTRIBUTE3                           NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:ATTRIBUTE3)"
TYPE_1099                            NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:TYPE_1099)"
UNIT_OF_MEAS_LOOKUP_CODE             NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:UNIT_OF_MEAS_LOOKUP_CODE)"
TAX_RATE                             NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:TAX_RATE)"
QUANTITY_INVOICED                    NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:QUANTITY_INVOICED)"
UNIT_PRICE                           NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "RTRIM(:UNIT_PRICE)"
INVOICE_ID                           NEXT     *   ^  O(") CHARACTER           
    SQL string for column : "AP_INVOICE_LINES_INTERFACE_S.NEXTVAL"

Record 22: Rejected - Error on table AP_INVOICE_LINES_INTERFACE, column DESCRIPTION.
no terminator found after TERMINATED and ENCLOSED field
Record 23: Rejected - Error on table AP_INVOICE_LINES_INTERFACE, column DESCRIPTION.
no terminator found after TERMINATED and ENCLOSED field

Record 1: Rejected - Error on table AP_INVOICE_LINES_INTERFACE, column AMOUNT.
ORA-01722: invalid number

Record 2: Rejected - Error on table AP_INVOICE_LINES_INTERFACE, column AMOUNT.
ORA-01722: invalid number

Record 56: Rejected - Error on table AP_INVOICE_LINES_INTERFACE, column DESCRIPTION.
no terminator found after TERMINATED and ENCLOSED field
Record 57: Rejected - Error on table AP_INVOICE_LINES_INTERFACE, column DESCRIPTION.
no terminator found after TERMINATED and ENCLOSED field
Record 1: Rejected - Error on table AP_INVOICE_LINES_INTERFACE.
ORA-01400: cannot insert NULL into ("AP"."AP_INVOICE_LINES_INTERFACE"."INVOICE_ID")

Record 2: Rejected - Error on table AP_INVOICE_LINES_INTERFACE.
Record 35: Rejected - Error on table AP_INVOICE_LINES_INTERFACE, column AMOUNT.
ORA-01722: invalid number

ORA-01821: date format not recognized

MAXIMUM ERROR COUNT EXCEEDED - Above statistics reflect partial run.

Table AP_INVOICE_LINES_INTERFACE:
  0 Rows successfully loaded.
  51 Rows not loaded due to data errors.
  0 Rows not loaded because all WHEN clauses were failed.
  0 Rows not loaded because all fields were null.


Space allocated for bind array:                 254388 bytes(58 rows)
Read   buffer bytes: 1048576

Total logical records skipped:          0
Total logical records read:            76
Total logical records rejected:        51
Total logical records discarded:        0

Run began on Tue Aug 19 20:19:14 2008
Run ended on Tue Aug 19 20:19:41 2008

Elapsed time was:     00:00:26.47
CPU time was:         00:00:00.06

=============================================================================
*****************************************************************************************

=============================================================================



=============================================================================
*****************************************************************************************

=============================================================================

Payables Open Interface's Control File

load data infile 'AP_INV.TXT'
append into table    AP_INVOICES_INTERFACE
fields terminated by '^' optionally enclosed by '"'
trailing nullcols
    (INVOICE_NUM              CHAR "RTRIM(:INVOICE_NUM)",
     INVOICE_TYPE_LOOKUP_CODE   CHAR "RTRIM(:INVOICE_TYPE_LOOKUP_CODE)",
     INVOICE_DATE               DATE "DD-MON-RRRR",
     VENDOR_NUM                 CHAR "RTRIM(:VENDOR_NUM)",
     VENDOR_SITE_CODE           FILLER,
     INVOICE_AMOUNT             CHAR "RTRIM(:INVOICE_AMOUNT)",
     TERMS_NAME                 CHAR "RTRIM(:TERMS_NAME)",
     DESCRIPTION                CHAR "RTRIM(:DESCRIPTION)",
     DUMMY1 FILLER,
     DUMMY2 FILLER,
     DUMMY3 FILLER,
     DUMMY4 FILLER,
     GL_DATE  DATE "TO_DATE((TO_CHAR(:GL_DATE,'DD-')||DECODE(TO_CHAR(:GL_DATE,'MON'),'AUG','SEP','SEP','SEP','OCT','OCT',TO_CHAR(:GL_DATE,'MON'))||TO_CHAR(:GL_DATE,'-YYYY')))",
     VOUCHER_NUM                CHAR "RTRIM(:VOUCHER_NUM)",
     INVOICE_RECEIVED_DATE      DATE,
     AMOUNT_APPLICABLE_TO_DISCOUNT,
     TERMS_DATE                 DATE,
     SOURCE                     CONSTANT 'MAXCIM INVOICE',
     PAYMENT_CURRENCY_CODE      CONSTANT 'USD',
     PAYMENT_METHOD_LOOKUP_CODE CONSTANT 'CHECK',
     CALC_TAX_DURING_IMPORT_FLAG CONSTANT 'N',
     ORG_ID                     CONSTANT '166',
     SHIP_TO_LOCATION           CONSTANT 'Materials Warehouse',
     INVOICE_CURRENCY_CODE      CONSTANT 'USD',
     creation_date              SYSDATE,
     last_updated_by            CONSTANT 1093,
     last_update_date           SYSDATE,
     created_by                 CONSTANT 1093,
     INVOICE_ID "AP_INVOICES_INTERFACE_S.NEXTVAL")



load data infile 'AP_LINE_TEST.TXT'
append into table    AP_INVOICE_LINES_INTERFACE
fields terminated by '^' optionally enclosed by '"'
trailing nullcols
    (REFERENCE_2              CHAR "RTRIM(:REFERENCE_2)",
     TYPE              FILLER,
     ACCOUNTING_DATE         DATE "DD-MON-RRRR",
     DESCRIPTION          CHAR "RTRIM(:DESCRIPTION)",
     DIST_CODE_COMBINATION_ID          CHAR "RTRIM(:DIST_CODE_COMBINATION_ID)",
     LAST_UPDATED_BY          CHAR "RTRIM(:LAST_UPDATED_BY)",
     AMOUNT                  CHAR "RTRIM(:AMOUNT)",
     CREATED_BY          CHAR "RTRIM(:CREATED_BY)",
     CREATION_DATE          DATE "DD-MON-RRRR",
     ATTRIBUTE1          CHAR "RTRIM(:ATTRIBUTE1)",
     ATTRIBUTE2          CHAR "RTRIM(:ATTRIBUTE2)",
     ATTRIBUTE3          CHAR "RTRIM(:ATTRIBUTE3)",
     TYPE_1099          CHAR "RTRIM(:TYPE_1099)",
     UNIT_OF_MEAS_LOOKUP_CODE      CHAR "RTRIM(:UNIT_OF_MEAS_LOOKUP_CODE)",
     TAX_RATE              CHAR "RTRIM(:TAX_RATE)",
     QUANTITY_INVOICED      CHAR "RTRIM(:QUANTITY_INVOICED)",
     UNIT_PRICE          CHAR "RTRIM(:UNIT_PRICE)",
     INVOICE_ID "AP_INVOICE_LINES_INTERFACE_S.NEXTVAL")

Oracle Forms Basic Concepts:

Oracle Forms Basic Concepts
Training  of Oracle Basic Form

The focus of the document is for consultants who are new to Oracle Forms and needs a kick-start on the concepts for better understanding of the subject.
Let’s start understanding the basic but important concepts in Forms.
What is Form :It is a developmental tool that is used for designing data entry and query screens. It is a front-end tool that runs in a Graphical User Interface (GUI).
GUI Concepts:
These concepts holds good for any user-interface.
To develop an effective GUI there are 4 basic stages:
  1. Define User Requirements
  2. Plan the User Interface
  3. Build the User Interface Elements (Create/Modify elements/functionality)
  4. User Feedback (Holds Key on the functionality and basis of the requirement)
Let’s move on to Forms Developer
How many components in Forms?
There are 3 components involved in the application development
  1. Form Builder
  2. Form Compiler
  3. Form Runtime
Form builder consists of following tools to perform a specific task
  1. Object Navigator
  2. Layout Editor
  3. Property Palette
  4. PL/SQL Editor
  5. Menu Editor
  6. Object Library

Object Navigator: It’s a hierarchal representation of all objects.
Layout Editor: It provides a virtual representation of the application user interface.
Property Palette: Each object in the form module has a property associated to it. Developer can view/set properties for one/multiple object.
PL/SQL Editor: Programmatically to enhance the functionality and appearance of an application.
Menu Editor: Create menu as per applications requirement and can add various functionality to various menu options.
Object Library: Creation of objects on some default specification. Storing some standard objects that can be re-used in other forms/menu.
Blocks: Logically related interface items are grouped into functional units called Blocks.
Types of Block:
Data Block: It is associated with or bound, to a database table or view or a set of stored procedures.
Control Block: It is not associated with any database table but items that will control the behavior of the application.
Let’s move on to the next scheme of things…
Canvas: It is a surface inside a window on which we place the interface that end user interacts.
Types of Canvas:
  1. Stacked Canvas
  2. Content Canvas
  3. Horizontal Toolbar
  4. Vertical Toolbar
  5. Tab Canvas

Let’s discuss briefly about the triggers in this section, for more information you can look through the Forms Builder Help Topics.
Note: The hierarchy of Objects in a form is
Form
Block
Record
Item

What is Triggers: These are program units which enhance the functionality of a form/application.
The following triggers can be used to enhance the functionality of the form:

What are Types of triggers in Oracle Form?

Block Processing Triggers: It fires in response to events related to record management in block.
e.g., When_Create_Record,When_Clear_Block,…
Interface Event Triggers: It fires in response to events that occur in form interface.
e.g., When_Button_Pressed,When_Checkbox_Changed,…

Master-Detail Triggers: It fires automatically when defined master-detail relationship between blocks. (Master-Detail relationship discussed further in the document)
e.g.,On_Checkdelete_Master,On_Clear_Details,…

Message Handling Triggers: It fires to issue appropriate error and information messages in response to runtime events.
e.g.,On_Error,On_Message,..

Navigational Triggers: It fires in response to Navigational Items.
e.g., Pre_Form, Post_Form, When_New_Form_Instance, When_New_Block_Instance,..

Query Time Triggers: It fires before/after the operator/application executes a query.
e.g.,Pre_Query,Post_Query,…

Transactional Triggers: It fires in response to wide variety of events that occur as a form interacts with data source.
e.g.,On_Delete,On_Update,..

Validation Triggers: It fires when it validates data in an item/record.
e.g.,When_Validate_Item,When_Validate_Record,..

Mouse Event Triggers: It fires for a mouse event.
e.g.,When_Mouse_Enter,When_Mouse_Click,..

Key Triggers: It has one to one relationship with specific Keys.
e.g.,Key F1,Key Enter,..

There are lot number triggers that can be used, please use as per the requirement with reference to Form Builder Help Topics.

What is Master- Detail Relationship? or What is Parent -Child Relationship?
Master- Detail Relationship : It is an association between two datablocks.One block is called Master Block and other Detail block. The relationship signifies that there is a primary key to foreign key relationship between the tables on the blocks associated.

What are Properties associated with blocks in a master-detail relationship?
Isolated : If you delete master records, associated detail records are not deleted from the database.
Non-Isolated: You cannot delete master records if the associated detail records exist in database.
Cascading: If you delete master records then automatically detail records will be automatically deleted from the database.

Windows : It is a container for all visual objects that make up a form, including canvases.
There are 2 types of Windows:
Document Window : It typically display the main canvases and work areas of the application where most data entry, and data retrieval is performed. It always remains within the application window frame.
Dialog Window: are free-floating, windows typically used for modal dialogs that require immediate user interaction.

Modality of the window depends on the functionality required i.e., Modal or Modeless.
Alert : It is a modal window that displays message to inform user about some application condition. E.g., STOP,CAUTION,NOTE,…
Invoking an alert : show_alert(alert_name)
Return number;

What is Record Group: It is an internal form builder structure that has column/row structure similar to database table. Static and Query based record groups can be used on the functionality of the form.

What is List of Values (LOV) : It is a pop-up window that provides end user selection list. LOV’s can be invoked programmatically or statically based on the record group. It can be positional based or automatic display.

The most important features of LOV are it provides auto-reduction and search features due to which user can locate specific values easily.

Let’s get to items on canvas which holds the key points.

Boilerplate Text Tool is used to create or edit a graphics text in the form. Graphics text is a static text in the form. E.g. Labels for items
Text Item Tool is used to create text item. It is an interface control that displays and allows editing of a text. It can be single or multi-line format.
Display Item tool are similar to text items but display items only store and displayed fetched or assigned values.
Buttons is a tool to execute commands or initiate buttons. E.g., OK ,CANCEL,..
Types : Text and Iconic Buttons
List Item is a list of text elements. A list item displays a fixed number of elements.
Types: Tlist,Pop List, Combo Box

Checkbox: It is a control that has 2 states i.e., checked or unchecked. It is used to indicate whether a certain condition is true or false.

Radio Button/Box : It is a logical set of options.

Editors: are used to edit item values in form. There are three editors that can be used at run time: Default editor, System Editor, User Named Editor

Property Class: Form builder provides a facility to create a named list of common properties and their values. This object is known as property class. Once you create a property class, you can base other objects on it. It is similar to the OOPS concept in programming languages.

Visual attribute : is a list of font, color and pattern properties and their values. This visual attribute can be attached to various objects to define object’s visual attributes.


FAQs

                                 Oracle Apps’s Technical FAQ

1) What is ERP? Architecture of apps?
         A packaged business software system that lets a company automate and integrate the majority of its business processes; share common data and practices across the enterprise; [and] produce and access information in a real-time environment.
2) Tell me some thing about SQL-LOADER.
Sql * loader is a bulk loader utility used for moving data from external files into the oracle database.
Sql * loader supports various load formats, selective loading, and multi-tables loads.             
        1) conventional
       --The conventional path loader essentially loads the data by using standard ‘insert’ statement.
        2) direct
                 -- the direct path loader (direct = true) by possess of logic involved with that, and loads directly in to the oracle data files.
EX:-
My data.csv file
                 1001, “scott tiger”,1000,40
                 1002,”gvreddy”,2345,50
Load data
Infile ‘c:\data\mydata.csv’
Into table emp
Fields terminated by “,” optionally enclosed by ‘”’
(empno, empname,sal,deptno)
>sqlldr scott/tiger@vis
control=loader.ctl  log= gvlog.log  bad=gvbad.bad  discard=gvdis.dsc .
3)  how do u dump data from pl/sql block to flat files?
       Using utl_file package, we can dump data from pl/sql block to flat file.
       PRE-REQUIREMENTS for UTL_FILE is specify the accessible directories for the UTL_FILE function in the initialization file (INIT.ORA) Using the UTL_FILE_DIR parameters.
       Ex: UTL_FILE_DIR =

EX:-
--remember to update INITSID.ORA,
--utl_file_dir = ‘c:\oradata’
Declare
Fp utl_file.file_type;
Begin
Fp := utl_file.fopen(c:\oradata’,tab1.txt’,’w’);
Utl_file.putf(fp,’%s %s \n ‘text field’, 55);
Utl_file.fclose(fp);
End;
4) What is SET-OF-BOOKS?
Collection of Chat of Accounts and Currency and Calendars is called SOB
5)     What is the interface?
         Interface Table is a table which is used as medium for transfer of data between two systems.
6)     What is invoice?
   Send you a request for payment
7)     What is INBOUND and OUT BOUND? (Different types of interfaces)
    Inbound Interface:
                   For inbound interfaces, where these products are the destination, interface tables as well as supporting validation, processing, and maintenance programs are provided.



  Outbound Interface:
                   For outbound interfaces, where these products are the source, database views are provided and the destination application should provide the validation, processing, and maintenance programs
8)      Tell me what r the Base tables in the AR?
          hz_parties      (party_id)     (store info about org, groups and people)
                     HZ_PARTIES stores information about parties such as organizations, people, and groups, including the identifying address information for the party.

hz_cust_accounts (cust_account_id)
                HZ_CUST_ACCOUNTS stores information about customer relationships. If a party becomes a customer, information about the customer account is stored in this table. You can establish multiplecustomer relationships with a single party, so each party can have multiple customer account records in this table.

hz_cust_acct_sites_all  (cust_acct_site_id)
                 HZ_CUST_ACCT_SITES_ALL stores information about customer sites.One customer account can have multiple sites. The address is maintained in HZ_LOCATIONS.

hz_cust_site_uses_all   (site_use_id)
                  HZ_CUST_SITE_USES_ALL stores information about site uses or business purposes. A single customer site can have multiple site uses, such as bill to or ship to, and each site use is stored as a record in this table.

hz_party_sites (party_site_id)
              HZ_PARTY_SITES stores information about the relationship between Parties and Locations. The same party can have multiple party sites.Physical addresses are stored in HZ_LOCATIONS.

hz_locations (location_id)
                HZ_LOCATIONS stores information about physical locations.

hz_Person_Profiles (person_profile_id)
                   HZ_PERSON_PROFILES stores detail information about people.

hz_Organization_Profiles (organization_profile_id)
               HZ_ORGANIZATION_PROFILES stores credit rating, financial statistics, socioeconomic and corporate linkage information for business sites. The primary key for this table is ORGANIZATION_PROFILE_ID.





9)      What r the table’s interface tables in the customer interface tables?
1)     Ra_customers_interface_all
               This table stores customer, address, and business purpose information. You do not have to enter values in this table if you do not want to import customers, addresses, or business purposes.

ADDRESS1 through 4
                       Enter the address for your customer in these four columns. You can enter up to four lines of an address.

Validation:  
      If you enter a value in ORIG_SYSTEM_ADDRESS_REF, you must enter a value in ADDRESS1. For multiple rows with the same address reference, insert values in address 1–4.

  Destination:                      HZ_LOCATIONS.ADDRESS1,
                                             HZ_LOCATIONS.ADDRESS2,
                                             HZ_LOCATIONS.ADDRESS3,
                                             HZ_LOCATIONS.ADDRESS4

           2) Ra_customer_profile_int_all
A customer level profile must exist in A_CUSTOMER_PROFILES_INTERFACE for new customers and each bill–to business purpose.
           3) Ra_contact_phones_int_all
This table stores telephone numbers for customers, addresses and contacts as well as contacts for customers and addresses.
           4) Ra_customer_banks_int_all
This table stores bank information for a customer or for a specific Bill–To address, you must enter a bank account for this customer,
            5) Ra_cust_paymethod_int_all
To import payment methods for customers and bill–to business purposes,

10) What r the staging tables in the customer interface?
                Ra_customers_stg
                Ra_customers_address_stg
                Ra_customers_point_stg
                Ra_customers_contact points_stg
                Ra_customers_relate_stg
                Ra_customer_error.
11)Tell me some mandatory columns in the customer interface tables?
 a) Ra_customers_interface_all
          1) Orig_system_customer_ref
          2) insert_update_flag
          3) customer_number 
          4) customer_status
                  5)last_updated_by     

                  6) last_updated_date 

                  7)created_by              

                  8) creation_date.       
         b) Ra_customer_profile_int_all
                    1) customer_profile_class_name
         c) Ra_contact_phones_int_all
                    1)orig_system_telephone_ref
                    2)telephone
                    3) telephone_type
         d) Ra_customer_banks_int_all
                    1) bank_a/c_name     
                    2)bank_a/c_no  
                    3)bank_a/c_currency_code
         e) Ra_cust_paymethod_int_all
                     1) payment_method_name

12)Tell me the Navigation for customer interface?
             Receivables à Interface à Customers


1. What tables cannot be updated through customer interface?
No updates will be allowed to be made through customer interface for 
Following tables
RA_SITE_USES_ALL
RA_CUSTOMER_RELATIONSHIPS_ALL
RA_CUST_RECEIPT_METHODS
AP_BANK_BRANCHES
AP_BANK_ACCOUNTS_ALL
AP_BANK_ACCOUNT_USES_ALL
2. How to send additional customer and address information through customer interafce 
Here is where attribute columns are used.
* Additional Customer data can be populated in 
RA_CUSTOMERS_INTERFACE_ALL.customer_attribute1 to 15
This will go into RA_CUSTOMERS.attribute1 to 15
* Additional address information can be populated in 
RA_CUSTOMERS_INTERFACE_ALL.address_attribute1 to 15
This will go into RA_ADDRESSES_ALL.attribute1 to 15
And so on.
5. What should be the batch size (number of customer records) general guidelines for optimal performance
About 10,000 records per bacth is ideal, it is suggested to keep the batch
size small.
   6. Why does customer interface error out if there is mismatch in address information?
Because the code validates against these mismatches. 
arplscin.sql and arplbcin.sql 
It validates the address being inserted or updated with respect to the tax 
location flexfield structure.  For each row being inserted or updated in 
RA_CUSTOMERS_INTERFACE, and that has not already been marked in error, 
the set_location_ccid function is called to return either an existing ccid 
for the address entered or to create a new entry in AR_LOCATION_VALUES for 
this new address.  The RA_CUSTOMERS_INTERFACE record is then updated with the 
value of the ccid returned.                                
7. How do you send records at customer level profile and address/site level profile?
For every customer record in RA_CUSTOMERS_INTERFACE_ALL, insert two records  in table RA_CUSTOMER_PROFILES_INT_ALL.    (Refer Note: 1070800.6 )
9. Does Customer Interface import salesperson data
No, Refer Enhancement Bug: 147495 
11. Customer Interface process can be used for updating the customer information How does the UPDATE work?
Current functionality of Customer Interface is to update all the data.  You cannot run Customer Interface to update only changed data. (Refer Bug: 879121 for the intended functinality)


12. What are some of the important fields that Customer Interface does not load?
Not all fields in RA_CUSTOMERS are being loaded by the interface. 
SIC_CODE                
GSA_INDICATOR                
FOB_POINT                
SALES_CHANNEL_CODE                
FREIGHT_TERM                
WAREHOUSE_ID                
PRICE LIST     
SHIP_PARTIAL                               
PAYMENT_TERM_ID   in RA_SITE_USES.PAYMENT_TERM_ID 
(Refer Enhancement Request Bug: 245300)
13. New TCA/Customer Model, how to load customer as PERSON or ORGANIZATION through Customer Interface?
a) Populate ra_customers_interface_all . person_flag = 'Y'
   Run Customer Interface process will load this record as PERSON
b) Populate ra_customers_interface_all . person_flag = 'N' ( or NULL ) 
   Run Customer Interface process will load this record as ORGANIZATION

13) Tell me what is the procedure to develop an interface?           
a.       First we will get the Requirement document.
b.      We will create control file based on that plot file.
c.       Then the control files which loads the data into staging tables.
d.      Through pl/sql programs we will mapping and validate the data and then dump into the interface tables.
e.       Through the standard programs we will push the data from interface tables to Base tables.
14)  What validations u did in the customer interface?
a.       customer name : the same customer reference can’t have different customer names with in this table
HZ_PARTIES.PARTY_NAME
b.      customer number : must be null if your r using automatic customer numbering, must exit if you are not using automatic customer numbering. This value much be unique with in HZ_PARTIES
c.       customer status : must be ‘A’ for active or ‘I’ for inactive
                             HZ_PARTIES_STATUS
d.      bank account num or bank account currency code :
                         if the bank a/c already exist do not enter a value
                         if the bank a/c does not exist  you must enter a value
e.       bank a/c name : it must exist in AP_BANK_ACCOUNTS or if it does not exist values must exist for BANK_A/C_CURRENCY_CODE
                                                                        BANK_A/C_NUM
                                                                        BANK_NAME
                                                                        BANK_BRANCH_NAME
               Note : every interface table has two error msg
1)      Error code.
2)      Error msg.

15)  How can u call a standard interface program from sql or pl/sql code?
    FND_REQUEST.SUBMIT_REQUEST (‘PO’,’EXECUTABLE NAME’,,,,PARAMETERS)
16)   API’s FOR CUSTOMER INTERFACE?
HZ_CUST_A/C_VZPUB.UPDATE_CUST_A/C
HZ_CUST_A/C_VZPUB.CREATE_CUST_A/C
       FND_PROFILES
       FND_APPLICATIONS
       FND_GLOBAL
       FND-FILE
       FND_CONCSUB(can submit conc program in host invironment)
17) Tell me some API?
FND_FILE.PUTLINE(FND_FILE.LOG)
FND_FILE.PUTLINE(FND_FILE.OUTPUT)
Is the Program exits, delete conc program and its executables.
IF      FND_PROGRAM.PROGRAM_EXITS(‘EMP’,APPLICATION_NAME_IN) THEN
          FND_PROGRAM.DELETE_PROGRAM(‘EMP’,APPLICATION_NAME_IN)
          FND_PROGRAM.DELETE_EXECUTABLE(‘EMP’,APPLICATION_NAME_IN)
END;
18)  What are profile options?
Is the Functional and Technical behavior of Oracle Applications Package.
       EX: - I want to assign the user3 responsibility to p4 printer then
                         System Administrator àProfile àSystem
                                    (FND_PROFILE_OPTIONS)
19)  Oracle E-Business suite?
Oracle apps + analytical components software.
                            (Oracle discover)
                            (Oracle sales analyzer)
                            (Oracle financial analyzer)
                            (Oracle marketing analyzer)
24) What is multi org?
        “Legal entity has more than one operating unit is called as multi org”
          a) Business group --- Human resources information is secured by 
                                           Business group
           b) Legal entity.    --- inter-company and fiscal/tax reporting.
                                            Security à responsibility à operating unit.        
  c) Operating unit --- secures AR, OE, AP, PA and PO Information.
  d) Organizations  --- is a specialize unit of work at particular locations


25) What are the User PARAMETERS in the Reports?
              P_CONC_REQUEST_ID
              P_FLEX_VALUE

26)  FND USER EXITS:-
FND SRWINIT        sets your profile option values, multiple organizations and allows Oracle Application Object Library user exits to detect that they have been called by an Oracle Reports program. 
FND SRWEXIT       ensures that all the memory allocated for AOL user exits have been freed up properly.
FND FLEXIDVAL   are used to display flex field information like prompt, value etc
FND FLEXSQL      these user exits allow you to use flex fields in your reports
FND FORMAT_CURRENCY   is used to print currency in various formats by using formula column

26) PL/SQL stored procedure parameters?
       or      what are the two parameters that are mandatory for pl/sql type concurrent program?
               Procedure/function (ERRBUF   OUT
                                                RETCODE OUT
                                               ………………….)
       ERRBUF :-    Used to write the error message to log or request file.
       RETCODE :- Populate log request file with program submission details info.
27) What is Value Set?
       --The value set is a collection (or) container of values.
       --When ever the value set associated with any report parameters. It provides list of values to the end user to accept one of the values as report parameter value.
       -- If the list of values needed to be dynamic and ever changing and define a table based values set.


27) What r the validation types?
1) None          -------- validation is minimal.
2) Independent ------input must exist on previously defined list of values
3) Dependent    ------input is checked against a subset of values based on a
                                 prior value.
3) Table             ----- input is checked against values in an application table
4) Special          ------values set uses a flex field itself.
5) Pair              ------ two flex fields together specify a range of valid values.
6) Translatable independent ----- input must exist on previously defined list
                                                     of values; translated values can be used.
7) Translatable dependent ------- input is checked against a subset of values
                                   based on a prior values; translated value can be used.
28) Form development process?
      a) open template form
      b) Save as .fmb
     c) Change the form module name as form name.
     d) Delete the default blocks, window, and canvas
      e) Create a window.
      f) Assign the window property class to window
      g) Create a canvas   (subclass info)
      h) Assign canvas property class to the canvas
      I) assign the window to the canvas and canvas to the window
       j) Create a data block       
       k) Modify the form level properties. (sub class item à Text item)
       l)  Modify the app_cusom package. In the program unit.
       m) Modify the pre-form trigger (form level)
       n) Modify the module level properties ((console window, First navigation
       p) Save and compile the form.
           Place the .fmx in the server directory.
       Q) Register in the AOL
                                    APPLICATION à FORM
                                    APPLICATION à FUNCTION
                                    APPLICATION à MENU
29)How do u customize the Reports?
a.       Identify the Short name of the standard report in which module we have to customize
   Ex: - if u want to customize in the AR module path is
              Appl top\ar\11.5.0\reports\US\ .rdf
b.      Open the .rdf file in Report builder and change the name of the module.
c.      Open the data module and modify the query (what is client requirements) assign the columns to the attributes.
d.      Go to report wizard and select, what r the newly created columns.
e.       Then Compile it. Then u will get a .rep file in the specified module. If it is not in the specified directory then we have to put in the server directory.
f.       Then Register in the AOL   Concurrent àexecutable.
                                                  Concurrent à program.
g.      go to system administrator  SecurityàResponsibilityàrequest
                 h)  Add and assign a concurrent program to a request group
30) Registering parametric report?
               Any applications will have two parameters,
                              1) from-period   2) to-period
      a) Go to object navigator and create the parameters.
                User parameters à from_no, to_no (data type char and width 30)
      b) Open the report layout and write the query(we have to reg the table in AOL)
          Select empno,ename,from g_emp where empno between :from_no and to_no
      c) Compile and put the .RDP file in the server directory.
      d) Registering in AOL.
                Concurrent à executable
                Concurrent à program   then go to “PARAMETERS”
      e) Go to Application à validation àset.  then go to “EDIT INTO”
               After entering the VALUE SETS (1) And TOKENS (2)
f)       Go to Administrations
                  Sequrity à responsibility à Request
      h) Add and assign a concurrent program to a request group
31) Tell me some report names and their table names in GL, AP, AR, and PO?
1) ra_customer_trx_all   
             customer_trx_id
             trx_number          (invoice no, debit memo no, credit memo no)
             cust_trx_type_id

2) ra_customer_lines_all (details of invoice)
             cutomer_trx_id

3) ar_payment_schdules_all
             check_id
                              This table stores all transactions except adjustments and miscellaneous cash receipts. Oracle Receivables updates this table when activity occurs against an invoice, debit memo, chargeback, credit memo, on account credit, or receipt.

4) ra_cust_trx_types_all       (invoice types)
             cust_trx_type_id

5) ra_batches_all
                   Batch_id
                          This table stores information about each receipt batch that you create in
Oracle Receivables. Each row includes information about a specific batch such as batch source, status, batch type, control count, and control amount

6) ra_receivable_application_all

7) ra_adjustments_all
             This table stores information about your invoice adjustments. Each row includes general information about the adjustment you are making such as activity name, amount, accounting information, reason, and type of adjustment. You need one row for each adjustment you are making to an invoice.

     


8) ra_cash_receiots_all
             Cash_receipt_id
                This table stores one record for each receipt that you enter. Oracle Receivables creates records concurrently in the AR_CASH_RECEIPT_HISTORY_ALL, AR_PAYMENT_SCHEDULES_ALL, and AR_RECEIVABLE_APPLICATIONS tables for invoice–related receipts.

                       
1)      ap_invoice_all
                 invoice_amount, base_amount, payment_status_flag(‘y’ –fully paid
                                                                                                       ‘n’—unpaid
                                                                                                        ‘p’ –partially paid)
2)      ap_invoice_payments_all
                  invoice_id,
3)      ap_invoice_distibutions_All
                 amount, base_amount, dist_code_combination_id, line_type_lookup_code
4)      ap_payment_schdules
                 payment_status_flag(“ ‘’’’’”)
5)      ap_payment_dustributions_all
6)      ap_checks_all
                 check_id,
                 AP_CHECKS_ALL stores information about payments issued to suppliers or refunds received from suppliers. You need one row for each payment you issue to a supplier or refund received from a supplier. Your Oracle Payables application uses this information to record payments you make to suppliers or refunds you receive from suppliers.

7)      ap_accounting_events_all

8)      ap_bank_accounts_all
                    AP_BANK_ACCOUNTS_ALL contains information about your bank accounts. You need one row for each bank account you define. Each bank account must be affiliated with one bank branch. When you initiate an automatic payment batch, enter a manual check, or create a Quick payment, you can select a bank account that you define in this table.

9)  ap_bank_accounts_uses_all
               AP_BANK_ACCOUNT_USES_ALL stores information for the internal and external bank accounts you define in Oracle Payables and Oracle
Receivables applications.
             
1)      po_vendors_all
2)      po_vendors_sites_all
3)      po_headers_all
             po_header_id
4)      po_lines_all
             po_line_id
5)      po_line_locations_All
6)      po_distributions_all
             po_distribution_id,

     
1)      Gl_code_combinations
                  GL_CODE_COMBINATIONS stores valid account combinations for each Accounting Flexfield structure within your Oracle General Ledger application. Associated with each account are certain codes and flags, including whether the account is enabled, whether detail posting or detail budgeting is allowed, and others.

2)      Gl_je_batches.
               GL_JE_BATCHES stores journal entry batches.

3)      Gl_je_headers
           GL_JE_HEADERS stores journal entries. There is a one–to–many relationship between journal entry batches and journal entries. Each row in this table includes the associated batch ID, the journal entry name and description, and other information about the journal entry. This table corresponds to the Journals window of the Enter Journals form. STATUS is ’U’ for unposted, ’P’ for posted. Other statuses indicate that an error condition was found. A complete list is below.

4)      Gl_je_lines.
             GL_JE_LINES stores the journal entry lines that you enter in the Enter Journals form. There is a one–to–many relationship between journal entries and journal entry lines. Each row in this table stores the associated journal entry header ID, the line number, the associated code combination ID, and the debits or credits associated with the journal line. STATUS is ’U’ for unposted or ’P’ for posted

5)      Gl_set of books
         GL_SETS_OF_BOOKS stores information about the sets of books you define in your Oracle General Ledger application. Each row includes the set of books name, description, functional currency, and other information. This table corresponds to the Set of Books form.

6)      Gl_periods
           GL_PERIODS stores information about the accounting periods you define using the Accounting Calendar form. Each row includes the start date and end date of the period, the period type, the fiscal year, the period number, and other information. There is a one–to–many relationship between a row in the GL_PERIOD_SETS table and rows in this table.

1)      OPEN-DEBIT MEMO REPORT?
  This report shows all the open-debit memo transactions, based on customer number and dates.
        Columns  :- type, customer_no, trx_no, amt_due, remaining.
         Parameter :- type, customer, from_date, to_date.
2)      GENERATING POSITIVE PAY FILE FOR BANK REPORT?
Basically this report generates a flat file of all the payments in order to send in to the bank.
3)      UPDATE POSITIVEPAY CHECKS REPORT?
This report which updates the data into the (AP) account payables system from the plot file, the file which is sent by bank
4)      UPDATE POSITIVEPAY OUT STANDING CHECKS?
This report which shows the out standing checks  


5)      CUSTOMER PAYMENT DETAILS REPORT?
Which shows each customer original amount, amount pay and due amount based on transaction type (books, pens)

Transaction types in AR
Credit memo transaction types
Invoice, debit memo, and charge back transaction types
Commitment transaction types

Q) HOW DO YOU RECTIFY THE ERRORS IN INTERFACE TABLES?
Depending on the naming convention used, errors appear in either alphabetical order or by error code number.

31) How do u identity its name of report?
                 System administrator à concurrent à program à define
                 System administrator à concurrent à program àexecutable 
32)  Who information’s?
        1) Created by
        2) Creation date
        3) Last _updated by
        4) last_update_date
        5) last_update_value
33) FLEX FIELDS?
            Used to capture the additional business information.
                 DFF
                    KFF
Additional
Unique Info, Mandatory
Captured in attribute prefixed columns
Segment prefixed
Not reported on standard reports
Is reported on standard reports
To provide expansion space on your form With the help of []. [] Represents
descriptive Flex field.

FLEX FILED : DESCRIPTIVE : REGIGSTER

Used for entering and displaying key information
For example Oracle General uses a key Flex field called Accounting Flex field to
uniquely identifies a general account.

FLEX FILED : KEY : REGIGSTER

Oracle Applications KEY FLEX FIELDS
1) GL :- ACCOUNTING
2) AR :- SALES TAX LOCATION, TERRITORY,
3) AP :- BANK DETAILS, COST ALLOCATION, PEOPLE GROUP

Oracle Applications DESCRIPTIVE FLEX FIELDS (Partial)
1)     GL :-  daily rates
2)     AR :- credit history, information
       3) PA :- bank branch, payment terms, site address,  
      
34) What are the requests groups?
           a) Single request: - this allows you to submit an individual request.
           b) Request set    : - this allows you to submit a pre-defined set of requests.

35) Sys Admin Module?
    a) Define Custom Users, b) Define Login Users, c) Register oracle DB users,
d) Define Concurrent Programs, e) Register Concurrent Executables, f) Setting Profile Option Values, g) Define Request Types.
36) AOL?
   a) Registering tables. b) Registering views c) Registering db sequences
   d) Registering profile options e) Registering lookups and lookup codes
   f) Registering forms g) Registering Form and Non-Form functions i) registering 
       Menus and sub-menus.  j) Registering DFF and KFF. k) Libraries 
37) What r the type Models in the system parameters of the report?
      1) Bit map        2) Character mode
38) .What is SRW Package?         (Sql Report Writer)             
The Report builder Built in package know as SRW Package  This package extends reports ,Control report execution, output message at runtime, Initialize layout fields, Perform  DDL statements  used to create or Drop  temporary table,  Call User Exist, to format width of the columns, to page break the column, to set the colors
Ex: SRW.DO_SQL, It’s like DDL command, we can create table, views , etc.,
            SRW.SET_FIELD_NUM
            SRW. SET_FILED_CHAR
            SRW. SET FILED _DATE

37) Difference between Bind and Lexical parameters?
BIND VARIABLE :
-- are used to replace a single value in sql, pl/sql
-- bind variable may be used to replace expressions in select, where, group, order  
    by, having, connect by, start with cause of queries.
-- bind reference may not be referenced in FROM clause (or) in place of
    reserved words or clauses.
LEXICAL REFERENCE:
-- you can use lexical reference to replace the clauses appearing AFTER select,
    from, group by, having, connect by, start with.
-- you can’t make lexical reference in a pl/sql statmetns.

38) Matrix Report: Simple, Group above, Nested         
Simple Matrix Report : 4 groups
                        1.Cross Product Group
                        2. Row and Column Group
                        3. Cell Group
                        4. Cell column is the source of a cross product summary that
                           becomes the cell content.
 Frames: 1.Repeating frame for rows(down direction)
                 2.Repeating frame for columns(Across )
                 3.Matrix object the intersection of the two repeating frames


39) what is Flex mode and Confine mode?                                          
Confine mode
On:  child objects cannot be moved outside their enclosing parent objects.
            Off:  child objects can be moved outside their enclosing parent objects.
Flex mode:
            On:  parent borders "stretch" when child objects are moved against them.
            Off:  parent borders remain fixed when child objects are moved against
                    them.




40) What is Place holder Columns?                                                                  
    A placeholder is a column is an empty container at design time. The placeholder can hold a value at run time has been calculated and placed in to It by pl/sql code from anther object.
You can set the value of a placeholder column is  in  a Before Report trigger.
   Store a Temporary value for future reference. EX.  Store the current max salary as records are retrieved.

23) What is Formula Column?                                                               
 A formula column performs a user-defined computation on another column(s) data, including placeholder columns.

 A summary column performs a computation on another column's data.  Using the Report Wizard or Data Wizard, you can create the following summaries:  sum, average, count, minimum, maximum, % total.  You can also create a summary column manually in the Data Model view, and use the Property Palette to create the following additional summaries:  first, last, standard deviation, variance.

50) What is cursor?
      A Cursor is a pointer, which works on active set, I.e. which points to only one row at a time in the context area’s ACTIVE SET. A cursor is a construct of pl/sql, used to process multiple rows using a pl/sql block.

28) Types of cursors?
       1) Implicit: declared for all DML and pl/sql statements.
                           By default it selects one row only.
       2) Explicit:  Declared and named by the programmer.
                           Use explicit cursor to individually process each row returned by a 
                                         Multiple statements, is called ACTIVE SET.
                            Allows the programmer to manually control explicit cursor in the
                                         Pl/sql block
a) declare: create a named sql area
b) Open: identify the active set.
c) Fetch: load the current row in to variables.
d) Close: release the active set.
                          
      CURSOR ATTRIBUTES
a)      %is open: evaluates to true if the cursor is open.
b)     %not found: evaluates to true if the most recent fetch does not return a row
c)     %found: evaluates to true if the most recent fetch returns a row.
d)     %row count: evaluates to the total number of rows returned to far.

Example for cursor:
1)       Declare
            Vno emp.empno%type;
            Vname emp.ename %type;
            Cursor emp_cursor is
                   Select empno,ename
                            From emp;
          Begin
            Open cursor;
            For I in 1..10 loop
              Fetch emp_cursor into vno,vname;
              Dbms_output.putline(to_char(vno) ||’ ‘||vname);
            End if;
         E nd;
 
2)         Begin
              Open emp_cursor;
             Loop
                  Fetch when emp_cursor % rowcount >10 or
                                                                      Emp_curor % not found;
                 Bdms_output_put_line(to_char(vno)||’ ‘|| vname);
             End loop;
           Close emp_cursor;
           End;

       CURSOR FOR LOOP
A)    cursor for loop is a short cut to process explicit cursors
B)    it has higher performance
C)    cursor for loop requires only the declaration of the cursor, remaining things like opening, fetching and close are automatically take by the cursor for loop
   
Example:
  1)     Declare
            Cursor emp_cursor is
                   Select empno,ename
                            From emp;
          Begin
            For emp_record in emp_cursor loop
               Dbms_output.putline(emp_record.empno);
               Dbms_output.putline(emp_record.ename) 
           End loop       
          End;
 



Can we create a cursor without declaring it?

Yes – by using cursor for loop using subqueries.

BEGIN
  FOR emp_record IN ( SELECT empno, ename
                                FROM   emp) LOOP
         -- implicit open and implicit fetch occur
    IF emp_record.empno = 7839 THEN
      ...
  END LOOP; -- implicit close occurs
END;

  a) for update clause:
       1) use explicit locking to deny access for the duration of a transaction
       2) lock the rows before update or delete
 Ex : select …….
              From…….
                    For update[ of column ref] [no_wait]

  b) where current of clause?
        1) use cursor to update or delete the current row
                     Where current of < column ref>

29) Attribute data types?
       1) %type 2) %row type.

30) Exception Handilings?
       Is a mechanism provided by pl/sql to detect runtime errors and process them with out halting the program abnormally
1)     pre-defined
2)     user-defined.
PRE-DEFINED:
1)     cursor_already_open--------attempted to open an already open cursor.
2)     Dup_val_on_index   --------attempted to insert a duplicate values.
3)     Invalid_cursor          -------- illegal cursor operation occurred.
4)     Invalid_number        -------- conversion of character string to number fails.
5)     Login_denied           ---------loging on to oracle with an invalid user name
                                                   and password.
6) program_error           -------- pl/sql has an internal problem.
7) storage_error             -------- pl/sql ran out of memory or memory is
                                                   corrupted.
8) to_many_row            ---------single row select returned more than one row.
9) value_error                -------- arithmetic,conversion,truncation or size
                                                   constraint error occurred.
10) zero_devided           -------- attempted to divided by zero.


USER-DEFINED:
       Declare     : name the exception
       Raise         : explicitly raise the exception by using the raise statements
       Reference: exception handing section.

The Raise_Application_Error_Procedure:
n      You can use this procedure to issue user-defined error messages from stored sub programs.
n      You can report errors to your applications and avoid returning unhandled exceptions.
      Raise_Application_Error(error_number,message[,{true/false}]
                 Error number è between -20000 to -20999

pragma exception_init?
       It tells the compiler to associate an exception with an oracle error. To get an error message of a specific oracle error.
       Ex: pragma exception_init(exception name, oracle error number)

Example for Exceptions?
      1) Check the record is exist or not?
             Declare
                     E  emp% rowtype
             Begin 
                     e.empno := &empno;
                     select * into e from emp where empno =e.empno;
                     Dbms_output.putline(‘empno’ || e.empno);
            Exception
                    When no_data_found then
                    Dbms_output.putline(e.empno ||’doest exist’);
            End;

     2) User defined exceptions?
                   Define p_dept_desc =’gvreddy’
                   Define p_dept_number =1236
                      Declare
                           E_invalid_dept exception;
                      Begin
                          Update departments
                          Set dept_name=’&p_dept_desc’
                          Where dept_id =’&p_dept_number’;
                        If sql% not found then
                            Raise e_invalid_departments;
                        End if;
                        Commit;
                    Exception
                           When e_invalid_departments then
                           Dbms_output.putline(‘no such dept’);
                    End;                 
       
52) what is REF Cursor?
        To execute a multi-row query, oracle opens an unnamed work area that stores processing information, to access the information, an explicit, which names the work area or, a cursor variable, which points to the work area.
 where as a cursor always refers to the same query work area,  a cursor variable can refer to a different work areas, cursor variable area like ‘c’ or ‘pascal’ pointers, which hold the memory location(address) of some object instead of the object itself.
So, declaring a cursor variable creates a pointers, not an object.

32) Can u define exceptions twice in same block?
       No
33) Can you have two functions with the same name in a pl/sql block?
       Yes
34) Can you have two stored functions with in the same name?
       Yes
35) Can function be overload?
       Yes
36)     What is the maximum number of statements that can be specified in a trigger statement?
One.
32) Stored procedure?
       Stored procedure is a sequence of statements that perform specific function.

53) What is procedure?
    ----    is a named pl/sql block to perform a specific task.
    ----    A procedure may have DML statements.
    ----    It may or may not return a value.
    ----    Procedure can return more than one value.
Example for procedure


1)     To accept the year as a parameter and list emp belong to the year?
                  Create or replace
                    Procedure empy(y number) is
                                 Cursor emp_cursor is
                                          Select * from emp where to_char(hiredate,’yyyy’)=’y’;
                        Emp_record  emp%rowtype;
                    Begin
                      For emp_record in emp_cursor loop
                                     Print (emp_record.empno);
                       Print (emp_record.ename);
                       Print (emp_record.sal);
                     End loop;
                    End;
Output :
               var empx number;
               Begin
                    :empx := ‘1234’;
               End;
       Exec empy(:empx);
        Print empy;
54) What is function?
   ---- is a named pl/sql block to perform a specific task, is mainly used for calculation purpose.
   ---- A function is called as part of an exception.
   ---- Every function should return a value
Example for function
       Create or replace
                    Function get_sal(p_id in emp.emp_no% type)
                                    Return number
                    Is
                                v_sal emp.sal%type :=0;
                    Begin
                           Select salary into v_salary
                                                                From emp
                                                                        Where emp_no = p_id;
                            Return v_salary
                            End get_sal;                    
                    End;

Output :
               var g_sal  number;
               Exec :g_sal := get_sal(99);
               Print g_salary;
9.Can functions be overloaded ?
Yes.
10.Can 2 functions have same name & input parameters but differ only by return datatype
No.
55) What is the package? 
    ---- Group logically related pl/sql types, items and subprograms.
1)     package specification
2)     package body
Advantages of a package:

·         Modularity
·         Easier Application Design
·         Information Hiding
·         Overloading

You cannot overload:
•Two subprograms if their formal parameters differ only in name or parameter mode. (datatype and their total number is same).
•Two subprograms if their formal parameters differ only in datatype and the different datatypes are in the same family (number and decimal belong to the same family)
•Two subprograms if their formal parameters differ only in subtype and the different subtypes are based on types in the same family (VARCHAR and STRING are subtypes of VARCHAR2)
•Two functions that differ only in return type, even if the types are in different families.

56) What is FORWARD DECLARATION in Packages?

PL/SQL allows for a special subprogram declaration called a forward declaration. It consists of the subprogram specification in the package body terminated by a semicolon. You can use forward declarations to do the following:
• Define subprograms in logical or alphabetical order.
• Define mutually recursive subprograms.(both calling each other).
• Group subprograms in a package

Example of forward Declaration:

CREATE OR REPLACE PACKAGE BODY forward_pack
IS
PROCEDURE calc_rating(. . .);            -- forward declaration 
PROCEDURE award_bonus(. . .)
 IS                                                        -- subprograms defined
 BEGIN                                    -- in alphabetical order
  calc_rating(. . .);      
 . . .
 END;

 PROCEDURE calc_rating(. . .)
 IS
 BEGIN
  . . .
 END;

END forward_pack;


56) What are triggers?
 ---- triggers are similar to procedures, in that they are the named pl/sql blocks with declarative, executable and exception-handling sections, how ever a procedure is executed explicitly from another block via a procedure call, which can also pass arguments.
 ---- A trigger is executed implicitly when ever a particular event task places. And is nothing but a event.
 ---- The triggering event is a DML (insert, update, delete) operations on a data base table
----- fires whenever a data event(such as DML) or system event(such as login or shutdown) occurs on a schema or database
Trigger timing :  1) before
                            2) after
                            3) instead of ( this is used for views)

Triggering events : 1) insert
                                2)update
                                3) delete
Trigger type :  1) statement level
                          2) row level.
Firing sequence of database triggers
1)     before statement trigger
2)     before row trigger
3)     after row trigger
4)     after statement trigger
Ex:
1)            Create or replace trigger secure_emp
                     Before
                     Insert  on emp
          Begin
           If (to_char(sysdate,’dy’) in(‘sat’,’sun’)) or
                 To_char(sysdate,’hh24:mi’)
                 Not between ’08:00’ and ’18:00’)
Then raise_application_error(-20500,’u can insert in the office timings’)
End if;
End;
Ex :-  2)  write a program to all transitions with name smith?
                Create or replace
                Trigger trigger_name
                Before insert or update or delete
                On emp
     For each row
                          When (old.ename =’smith’ or
                                      New.ename =’smith’)
               Begin
                           Raise_application_error(-20003,’smith’);
               End;
 57) Difference between triggers and procedures?
Defined with create trigger
Defined with create procedure
The data dictionary contains source code in the user_triggers.
Data dictionary contains source code in user_source
Implicitly invoked
Explicitly invoked
Commit, save point and rollback are not allowed(TCL)
Those are allowed

58) LOCKS?
           -- Is to reduce concurrency
      1) share lock
                ---it allows the other users for only reading not to insert or update or delete.
      2) exclusive lock
                 --- only one user can have the privileges of insert or update and delete of particular object
                --- others can only read.
     3) update lock
               ----multiple user can read, update delete
 Lock levels :
                       1) table level  2) table space 3) data base level.
                   
58) What is template?
   a) The TEMPLATE form is the required starting point for all development of new
           Forms.
   b) The TEMPLATE form includes platform–independent attachments of several
           Libraries.
      APPSCORE :- It contains package and procedures that are required of all forms to support  the MENUS ,TOOLBARS.
      APPSDAYPK :- It contains packages that control the oracle applications CALENDER FEATURES.
      FNDSQF  :- it contains packages and procedures for MESSAGE DICTONARY, FLEX FIELDS, PROFILES AND CONCURRENT PROCESSING.
      CUSTOM :- it allows extension of oracle applications forms with out modification of oracle application code, you can use the custom library for customization such as zoom    ( such as moving to another form and querying up specific records)

59)     What are ad-hoc reports?
Ans.:  Ad-hoc Report is made to meet one-time reporting needs. Concerned with or formed for a  
           particular purpose. For example, ad hoc tax codes or an ad hoc database query

60) What is responsibility?
       Is collection of menus, request security groups and data groups
  Menus: collection of forms is nothing but menus
  Request security groups: collection of programs.
  Data groups: is a group of modules to be made accessible by the user through
                         Responsibility
           System adminàsecurityàdefine
                                      Securityàuseràdefine

61) What are different execution methods of executabls?

FlexRpt                                   The execution file is wrnitten using the FlexReport API.
FlexSql                                   The execution file is written using the FlexSql API.
Host                                       The execution file is a host script.
Oracle Reports                        The execution file is an Oracle Reports file.
PL/SQL Stored Procedure       The execution file is a stored procedure.
SQL*Loader                             The execution file is a SQL script.
SQL*Plus                                The execution file is a SQL*Plus script.
SQL*Report                             The execution file is a SQL*Report script.
Spawned                                 The execution file is a C or Pro*C program.
Immediate                               The execution file is a program written to run as a subroutine of the concurrent manager. We recommend against defining new immediate concurrent programs, and suggest you use either a PL/SQL Stored Procedure or a Spawned C Program instead.

Composite Datatypes :
–   PL/SQL TABLES
–   PL/SQL RECORDS
-          Nested TABLE
-          VARRAY

What is the sequence of functions – group by,having,orderby in a select statements ?
Select…..
Group by…
Having…
Orderby..

Difference between User and Super User?
User : login user or front end user
Super user : it has full access of particular module

OraApps Search

Custom Search

Search This Blog