Frequently asked question to Techno-Functional Consultant

1.Question: What are the key benefits of forms personalization over custom.pll? Ans: a. Multiple users can develop forms personalization at any given point in time.It is fairly easy to enable and disable forms personalization. b. A programmer is not required to do simple things such as hide/disable fields or buttons. c. provides more visibility on customizations to the screen. 2.Question: Tell me some limitations of forms personalization when compared to CUSTOM.pll? Answer: a.Can t create record group queries, hence can t implement LOV Query changes. b.Can t make things interactive, i.e. can t have a message box that gives multiple choices for example Proceed or Stop etc. 3.Question: What are the Autoinvoice interface tables in AR . Ans: You can either use AutoInvoice by populating tables RA_INTERFACE_LINES_ALL, RA_INTERFACE_DISTRIBUTIONS_ALL RA_INTERFACE_SALESCREDITS_ALL RA_INTERFACE_ERROR_ALL Note : Alternately , you may decide to use API ar_invoice_api_pub.create_single_invoice for Receivables Invoice Import. 4. Question: How do you know if a specific Oracle patch has been applied in apps to your environment? Ans: Use table ad_bugs, in which column bug_number is the patch number. SELECT bug_number ,to_char(creation_date, DD-MON-YYYY HH24:MI:SS ) dated FROM apps.ad_bugsWHERE bug_number = TRIM( &bug_number ) ; 5. Question : What are the mandatory parameters passed to the concurrent program ? Ans : there are two mandatory parameters that need to be pased for all the procedures called 1.ERRBUFF 2.RETCODE Note : The retcode has three values returned by the concurrent manager 0--Success 1--Success with warning 2--Error 6.Question: What are the basic steps when defining a concurrent program? Ans: Broadly speaking there are three steps when developing a concurrent program in Oracle Apps Step 1. Make Oracle Apps identify the executable Step

2. Provide a handle to the executable by means of defining a concurrent program Step 3. Make this concurrent program accesible to selected users via their responsibility. 7. Question : What is the difference between cross-validation rules and securityrules? Ans :Cross validation rules prevent all the responsibilities/users entering invalid account combinations. Security rules are attached to specific responsibilities to prevent using few of the segment values for a segment. Cross Validation Rule: Rules that define valid combinations of segment values a user can enter in an account. Cross-validation rules restrict users from entering invalid combinations of account segment values. Security Rule: It determines the accounting transaction user can view at different levels of hierarchy, such as at Site Level >Application Level > Responsibility Level > User level. Cross Validation Rule applies across the chart of account where Security Rule is applicable at Responsibility Level or User Level. Cross Validation Rules are meant for defining the set of combinations that are excluded from the global set whereas Security Rules are to restrict Users/Responsibilities. Cross-Validation Rules are to control the certain code combinations. Security Rules are to control the certain segment values. 8. Question : How many ways can you enter a journal in GL? Ans : 1. Manual entry 2. Subledger Entry 3. Spreadsheet Entry 4. Recurring Entry 5. Mass Allocation15. 9. Question : What are cycles of GL . Ans: GL Accounting cycle can be further elaborated like this 1. Open Period. 2. Create Functional and foreign journal entries.(including the journal import from legacy systems and subledgers). 3. Reverse journal entries. 4. Post the journals. 5. Review and correct the balances. 6. Revalue foreign currency balances. 7. Translate foreign currency balances. 8. Consolidate set of books. 9. Run accounting reports. 10. Close the accounting periods 10.Question:What is a recurring invoice? Ans: Recurring Invoice is a type of invoice which occurs at definite intervals of time. The best example for a recurring invoice is Rent paid to the Owner. 11.Question:What is the difference between GL date and GL posted date in GL ? Ans: GL date is the date used to determine the correct accounting period for your transactions where as the GL posting date is the date when the journal entry is posted the GL. GL date is the date used to determine the correct accounting period for your transactions where as the GL posting date is the date when the journal entry is posted the GL, also Called Transaction Date & Posted Date.

12.Question : Can you please explain Two- Three- and Four way Matching ? Ans : Two-, Three-, and Four-way Matching 2-way matching verifies that purchase order and invoice information match within your tolerances as follows: Quantity billed is less than or equal to Quantity ordered Invoice price is less than or equal to Purchase order price 3-way matching adds a third criterion to verify that receipt and invoice information match with the quantity tolerances you define: Quantity billed is less than or equal to Quantity received 4-way matching adds a fourth criterion to verify that acceptance documents and invoice information match within the quantity tolerances you define: Quantity billed is less than or equal to Quantity accepted When you match to a purchase order, Payables automatically performs 2-way matching. In the Purchasing Options window you can choose to additionally use 3-way or 4-way matching. You can change the invoice match option at the supplier, supplier site and purchase order shipment levels. If the invoice and purchase order do not match within the tolerances you define for quantity and price, Approval places a matching hold on the invoice. You must release the hold before you can pay the invoice 13.Question : What is the use of Temp tables in Interface programs ? Ans : Temporary tables are used in Interface programs to hold the intermediate data. The data is loaded into temporary tables first and then, after validating through the PL/SQL programs, the data is loaded into the open interface tables. 14.Question : What is Multi Org . Ans : The ability to define multiple organizations and the relationships among them within a single installation of Oracle Applications. These organizations can be sets of books, business groups, legal entities, operating units, or inventory organizations. 15.Question : Difference between parent request and child request ? Ans : A parent request is a concurrent request that submits another concurrent request. In the case of Standard Request Submission, a report set is a parent. When you submit a report set, the report set submits the reports or programs that you have included in the report set. A parent request may be sequential or parallel which determines whether the requests it submits run one at a time or all at once. A child request is a concurrent request submitted by another concurrent request. When you submit a concurrent request to run a report set, the report set submits the reports in the set for concurrent processing. The requests submitted by the report set are child requests. 16.Question :What is called first? Forms Personalization or CUSTOM.pll Ans: First your form personalization is called, and then CUSTOM.pll is called.

17.Question :Where is the metadata for Forms Personalization stored?These personalizations are stored in FND tables Ans: personalizations are stored in FND tables 18.Question :What is the difference between Inbound and outbound interface ? Ans : Inbound Interfaces An inbound interface receives data from one system (legacy) and inserts into Oracle open interface tables. A typical inbound interface would follow these steps: 1. Extract data from legacy system into a flat file. 2. Use SQL*Loader or equivalent tool to upload information into a temporary table. 3. Write a PL/SQL program to take data from the temp table and insert into the Open Interface Tables. 4. Through the concurrent manager in Oracle Applications, run the standard Oracle Interface program to transform interface tables into Oracle data. Outbound Interfaces An outbound interface takes data from Oracle tables and inserts it into an external system (via tables or flat file). A typical outbound interface would follow these steps:- Write a PL/SQL program to extract data from Oracle base tables into a flat file.- Use a custom program to read that data and post it into the legacy system 19.Question:What Is an Open Interface Table (OIT)? Ans: For inbound interfaces, the interface table is the intermediary table where data from the source application temporarily resides until it is validated and processed into an Oracle base table through a standard import concurrent program. Open Interface Tables are standard Oracle tables. Oracle uses OITs to provide a simple interface to Oracle base tables. Oracle has list of all the open interface that oracle offered in there product. 20.Question: What is the difference between Bad file and discrad file ? Ans : Bad File : After a record is accepted for processing by SQL*Loader, a row is sent to Oracle for insertion. If Oracle determines that the row is valid, then the row is inserted into the database. If not, the record is rejected, and SQL*Loader puts it in the bad file. The row may be rejected, for example, because a key is not unique, because a required field is null, or because the field contains invalid data for the Oracle datatype. The bad file is written in the same format as the datafile. So rejected data can be loaded with the existing control file after necessary corrections are made Discard File : The discard file contains records that were filtered out of the load because they did not match any record-selection criteria specified in the control file. The discard file therefore contains records that were not inserted into any table in the database. You can specify the maximum number of such records that the discard file can accept. Data written to any database table is not written to the discard file. The discard file is written in the same format as the datafile. The discard data can be loaded with the

existing control file, after any necessary editing or correcting. 21.Question: What Are Standards for Report Development in Oracle Apps ? Ans . For developing a Report in Oracle Applications we should follow three standards.1. Creation of Bind Variable - P_CONC_REQUEST_ID:We must create a Bind Variable called P_CONC_REQUEST_ID (We can t change this name. It is standard name.). If we run Conc. Prgm. from SRS window, it will give a Request ID. It will get store in P_CONC_REQUEST_ID automatically. This Bind Variable is useful, when we call another Conc. Prgm. with in a Conc. Prgm. 2. FND SRWINIT in Before Report Trigger:We call the USER_EXIT ( FND SRWINIT ) form Before Report Trigger. Syntax isSRW.USER_EXXIT( FND SRWINIT ):This USER_EXIT is initializing the user profiles in the report trigger i.e., before getting the date from the Database.Note:While executing the Conc. Prgm. the system allocate memory for the program which contains all details of user. In above syntax,SRW.USER_EXIT refers to D2K and purpose of this is, when we want to transfer the control from execution of report to other 3rd generation language and again transfer the control to report execution.FND SRWINIT refers to Oracle Applications. Purpose of this is to get the User Profile . FND SRWEXIT in After Report Trigger:We call the USER_EXIT ( FND SRWEXIT ) form After Report Trigger. Syntax is SRW.USER_EXXIT ( FND SRWEXIT ):This USER_EXIT is frees the memory which is occupied by user profiles. 22.Question : How to Run the SQL script from the Concurrent Program? Ans : If we want to run the SQL script from the Concurrent Program window then we should follow the below steps. 1. Develop the SQL*plus (.SQL) 2. Transfer the SQL script file (.sql) file from local machine to the server in to respectable path CUST_TOP/11.5.0/SQL/.SQL Then we have to follow the steps to implement (to run from Concurrent Program window) in Oracle Applications. 1. Create executable by executable method SQL*plus 2. Define Concurrent Program, attach executable, parameters, incompatibilities 3. Attach Concurrent Program to request group. 4. Attach request to responsibility 5. Attach responsibility to user. User will submit from SRS window.SQL Script with Parameter:Inside of SQL script we can receive the parameter value by using &1, &2, &3 and so on. First Concurrent Program parameter value will come in the place, where we have mention &1. Second Concurrent Program parameter in to &2 and so on Note:We can define max of 100 PARAMETERS for a Concurrent Program.The Format Type of Concurrent Program output should be TEXT 23.Question : What are the steps for HOST programs ? Ans : The first steps( Step1) would be , you have to create a script and save as .prog extension and put into your application top bin folder.If your custom application is XX then the scripts should goes to $XX_TOP/bin . For example, call the script CUSTOM.prog and place it under Step 2 Now,you have understood , the execution of unix program is bit different in oracle application. The only things you have to notice is you need to pass 4 mandatory parameter to execute host program.The other way around is ,you can use fndcpesr and link with your host program.It means the

fndcpesr will take care of your 4 mandatory parameter. You have to simply create a soft link with $XX_TOP/bin folder ln -s $FND_TOP/bin/fndcpesr Step 3 Next you have to make into system administrator responsibly follow 3 steps from these menu sysadmin -> concurrent-> program -> executable sysadmin -> concurrent-> program -> define sysadmin ->security -> responsibility -> request Register the concurrent program, using an execution method of 'Host'.Use the name of your script without the .prog extension as the name of the executable. Step4 Your script will be passed at least 4 parameters, between $1 and $4.These are: orauser/pwd, userid, username, request_id Any other parameters you define will be passed in $5 and higher.Make sure your script returns an exit status also. Question : What additional piece need to incorporate in code you need to simply Ans: ORA_USER_PASS=$1 USERID=$2 USERNAME=$3 REQUESTID=$4 24.Question :What is called first Forms Personalization or CUSTOM.pll ? Ans: First your form personalization is called, and then CUSTOM.pll is called. 25.Question : In the custom.pll what are the events we can write ? Ans: In the Custom.pll we can write below event. ZOOM WHEN-NEW-FORM-INSTANCE WHEN-NEW-BLOCK-INSTANCE WHEN-NEW-RECORD-INSTANCE WHEN-NEW-ITEM-INSTANCE WHEN-VALIDATE-RECORD 26.Question : How to find the custom directory in front end ? Ans: From Application Developer responsibility, navigate to Application --> Register. Query for the custom Custom Development application name. The value in the field Basepath, is the OS system variable that stores the actual directory info 27.Question : How to find, how many columns in any APPS TABLES ? Ans :-select count(*) from dba_tab_columns where table_name ='give apps table name'; 28.Question : What Is Rule Sets in Oracle GL ? Ans: A Rule set is a set of nested instructions that govern how the data in the GL_INTERFACE TABLE is transferrred . To Create a Rule Set, navigate to Interface Data Transformer > Transformation Rule Set. Below are

details to help you complete the definition for a Rule Set. 29.Question : How Would you call the Shell script from PL/SQL Ans: Declare x number ; Begin x := RUN_CMD('/usr/bin/ls /home/oracle; echo $?'); dbms_output.put_line('shell Returned with status:'x); 30.Questions: How many types of Invoices in Oracle Account Payables Ans: 1) Standard Invoice 2) Debit Memo 3) Credit Memo 4) Withholding tax invoice 5) PO Default 6) Prepayment Invoice 7) Expense Reports 8) Quick Match invoice 9) Mmixed Invoices 10) Recurring Invoice 31.Question : Which tables store segment values and descriptions? Ans: FND_FLEX_VALUES_TL FND_FLEX_VALUES 32.Question : What are the steps for building a screen from scratch? Ans : A) Copy the Form Template from $AU_TOP/Form/US Open up TEMPLATE.fmb, and save this as XXHELLOAPPS.fmb Make sure all the necessary library files are there 1. Appcore 2. Appcore2 3. FNDSQF 4. Appdaypk 5. Custom 6 . Globe 7. Vert 8 . JA 9 . JL 10 . JE, 11. Psac B) Create a new window, by right clicking on Window/newName this window as XXHELLOAPPS,and assign it SubClass Type WINDOW from picklist. C) Create a new canvas and name it XXHELLOAPPS , ensuring its Sublcass Type is Content D) Make the windows property reference canvas XXHELLOAPPS and vice versa make the canvas reference windows XXHELLOAPPS.E) Now create a block named XXHELLOAPPS . Lets keep this a control block for simplicity. F) go to form level property, and set first navigation block to XXHELLOAPPS. G) Add a label and a field named Hello_World to this block. H) Generate the form on PC using Control-T keystrokes. This will ensure that nothing critical has been missed out. I) FTP the form file to $XXPO_TOPSurely, this XX will be replaced by the naming convention at your client/company. J) cd to $XXPO_TOP

> f60gen apps/apps@apps XXHELLOAPPS.fmb output = FORM/US/ XXHELLOAPPS.fmx This will create a file executable as XXHELLOAPPS.fmx K) Go to Application Developer responsibility Menu/applicaton/formRegister the form L) Register the Forms FunctionThis forms function must be registered against application "XX Purchasing". M) Now add a menu item so that this forms function becomes available to specific responsibility. 33.Question : Can you please explain P2P and O2C cycles ? Ans : Procure to Pay: 1.Oracle Purchasing: You enter Suppliers of different materials and products you want to purchase to manufacture a finished good that your organization plans to sell 2. Oracle Purchasing: You prepare a Request for Quotation (RFQ) and send it to different suppliers to get the best and/or economical price for the product. 3. Oracle Purchasing: Suppliers sends their quotations and you upload those quotations in Oracle Purchasing to get the best three quotes and further to get the one best quote. 4. Oracle Purchasing: You prepare a Purchase Order(PO) against the best RFQ to buy the goods from the supplier who quoted the suitable price and sends the PO to that supplier 5. Oracle Purchasing: The supplier receives the confirmation of purchase from PO and ships the ordered goods. You receive the goods enter a Goods Received Note GRN) in Oracle Purchasing. 6. Oracle Inventory / Oracle Assets: It s up to you whether you want to receive the goods at your head office or you Inventory directly. In either case you move the received goods to your different Raw Material Inventory from Oracle Purchasing to Oracle Inventory and the Item Count increases. If the item is Asset Type then it will move to Oracle Assets at the time of Invoice creation in Oracle Payables. 7. Oracle General Ledger: Once you move the goods to Oracle Inventory, it sends the Material Accounting to Oracle General Ledger. 8. Oracle Payables: After this the supplier sends you the invoice for the purchased goods and you Enter or Match the invoice against the PO from Oracle Purchasing in Oracle Payables. As said before, if the item is Asset in nature then it will move to Oracle Asset. 9. Oracle General Ledger: When you enter the invoice it means that you have created a Liability against that supplier and also you have recorded the expense incurred or asset purchased. Oracle Payables sends the invoice accounting to Oracle General Ledger. 10.Oracle Payables: You pay the invoice and settle the Liability. 11.Oracle General Ledger: The liability is settled and your cash movement account is updated. 12.Oracle Cash Management: As you pay the invoice Oracle Payables sends the payment information to Oracle Cash Management for Bank Reconciliation. Once reconciled, Oracle Cash Management sends the updated Bank/Cash accounting entry to Oracle General Ledger. 13.Oracle General Ledger: Your cash at bank is updated with actual balance.

14.Oracle Process Manufacturing(OPM) / Oracle Discrete Manufacturing(ODM): You start the manufacturing of your final product. Both OPM or ODM requests the different raw materials from you inventory organizations and manufactures a finished good. 15.Oracle Inventory: As the raw materials are issued to OPM and ODM the inventory sends the issuing material accounting to General Ledger and decreases the Item Count from the Raw Material Store. As the finished good is prepared, Oracle Inventory receives the finished good in Finished Good Store and increase the Item Count. Now the final product is ready to be sold in the market and from here the O2C cycle starts. Order to Cash Cycle: Order to Cash means Customer s Order Placing to Vendor s Cash Receiving. When your final product is ready to be sold, you market it. The customer gets fascinated with the marketing campaign and decides to buy your product and from here starts the O2C cycle. 1. Oracle Order Management: Customer places the order. 2. Oracle Order Management: You enter the customer order 3. Oracle Inventory: Check the available unit and the quantity ordered by the customer. 4. Oracle Order Management: You ship the product to customer site and decreases the Finished Goods inventory. 5. Oracle Receivables: The customer receives the product and you invoice the customer. 6. Oracle General Ledger: You record your revenue and receivables. 7. Oracle Receivables: The customer pays and you receive the cash/check. 8. Oracle Cash Management: Oracle Receivables sends the customer receipt for Bank Reconciliation. After reconciliation, Oracle Cash Management send the actual bank balance or Oracle General Ledger. 9. Oracle General Ledger: You have the actual bank balance.