Workflow API

•A function activity is usually defined by a PL/SQL stored procedure that performs some automated processing within a workflow process.
•The PL/SQL procedure for a function activity must follow a standard API.

All PL/SQL stored procedures called by function activities in a workflow process must follow the standard API format so that the Workflow Engine can properly execute the activity.

procedure
(itemtype in varchar2,
itemkey in varchar2,
actid in number,
funcmode in varchar2,
resultout out varchar2);


•itemtype: The internal name for the item type.
•itemkey: A string that represents a primary key generated by the workflow-enabled application for the item type. The item key uniquely identifies the item within an item type.
•actid: The ID number of the activity from which this procedure is called.
•funcmode: The execution mode of the function activity, either RUN or CANCEL.
•resultout: A result that is returned depending on the result type specified for the activity.

•RUN
–Executed when activities are executed for the first time
–Executed following CANCEL mode when a loop is revisited with On Revisit set to Reset
•CANCEL
–Executed for activities revisited in a loop with On Revisit set to Reset
–Executed for activities that are part of a process that has been canceled by a call to WF_ENGINE.AbortProcess( )

•If a result type is specified in the property page of the activity in the Workflow Builder, this parameter represents the expected result returned when the procedure completes.
•Possible resultout values are:
–COMPLETE:
–WAITING
–DEFERRED:
–NOTIFIED::
–ERROR:

•A post-notification function can be used to couple processing logic to a notification activity.
•Post-notification functions for notification activities must follow the same standard API as PL/SQL procedures for function activities.
•However, notification activities use different execution modes than function activities


All PL/SQL stored procedures referenced by notification activities as post-notification functions in a workflow process must follow the standard API format so that the Workflow Engine can properly execute the activity.

•The resultout parameter is ignored for the ‘RESPOND’, ‘FORWARD’, and ‘TRANSFER’ execution modes, unless the parameter value is in the form ‘ERROR%’.
•If you want to fail the Respond, Forward, or Transfer operation after the post-notification function has executed, you can:
–Return resultout = ERROR:
–Raise an exception in your procedure

You can reference the following global WF_ENGINE variables in your post-notification function:
•WF_ENGINE.context_nid = notification_ID
•WF_ENGINE.context_text = new_recipient_roleif the function is called in TRANSFER or FORWARD mode
or
WF_ENGINE.context_text = responderif the function is called in RESPOND mode

•Use WF_CORE APIs to raise and catch errors in your PL/SQL procedures.
•The Workflow Engine sets the status of the function activity to “ERROR” if:
–The PL/SQL procedure raises an unhandled exception
–The PL/SQL procedure returns a result beginning with “ERROR:”


Use the following APIs to start or run a workflow process:
•WF_ENGINE.CreateProcess
•WF_ENGINE.StartProcess
•WF_ENGINE.LaunchProcess
•WF_ENGINE.SetItemOwner
•WF_ENGINE.SetItemUserKey
•WF_ENGINE.GetItemUserKey
•WF_ENGINE.SetItemParent
•WF_ENGINE.Event
•WF_ENGINE.Background
•WF_ENGINE.CreateForkProcess
•WF_ENGINE.StartForkProcess

Use the following APIs to communicate attribute information to the Workflow Engine:
•WF_ENGINE.SetItemAttribute
•WF_ENGINE.SetItemAttrDocument
•WF_ENGINE.SetItemAttributeArray
•WF_ENGINE.GetItemAttribute
•WF_ENGINE.GetItemAttrDocument
•WF_ENGINE.GetItemAttrClob
•WF_ENGINE.GetItemAttrInfo

•WF_ENGINE.AddItemAttr
•WF_ENGINE.AddItemAttributeArray
•WF_ENGINE.GetActivityAttribute
•WF_ENGINE.GetActivityAttrClob
WF_ENGINE.GetActivityAttrInfo


Use the following APIs to communicate state changes to the Workflow Engine:
•WF_ENGINE.CompleteActivity
•WF_ENGINE.CompleteActivityInternalName
•WF_ENGINE.BeginActivity
•WF_ENGINE.AssignActivity
•WF_ENGINE.GetActivityLabel
•WF_ENGINE.AbortProcess
•WF_ENGINE.SuspendProcess

•WF_ENGINE.ResumeProcess
•WF_ENGINE.HandleError
•WF_ENGINE.ItemStatus


•For standalone Oracle Workflow, a calling application can launch a Web browser and pass a Workflow Monitor URL.
•You can monitor a specific item type and key through the following URLs:
–Process Diagram URL
–Notifications List URL
–Activities List URL

•To generate Workflow Monitor URL strings, call the following functions:
–Process Diagram: WF_MONITOR.GetDiagramURL( )
–Notifications List: WF_MONITOR.GetEnvelopeURL( )
–Activities List: WF_MONITOR.GetAdvancedEnvelopeURL( )
•The calling application must supply the Web agent string, item type, and item key, and specify whether to run the monitor in ADMIN or USER mode.

Download PDF format Etrms

Etrms and Some Usefull documents

http://cid-ae545c16904514ec.skydrive.live.com/browse.aspx/Ora%20Apps%20docs/

GL Features in R12

1.Multi Org

In Release 11i, a user assigned to an Operating Unit (OU) would process data from the products deployed in that OU. To process data for another OU, a user would log out of the first and into the second. The data generated in that OU would be accounted for according to rules generated by various product accounting engines, and posted to general ledger in ways appropriate for the different products, some generating part of the detail at different times in the process. General Ledger sets of books (Sob) were self-contained, reflecting the balances of the entity to which you’d assigned the Sob, and managed by users assigned to the Sob.

In Release 12.0, by contrast, users can be assigned to multiple operating units, and are supported by processes and transactions that can span operating units. Their data is book-kept according to rules stored in a single accounting engine,and the accounting is stored in subledger tables that are standard across all products. Complete accounting is maintained for every appropriate event, and all subledger entries are fully balanced and detailed. A single, common posting engine summarizes to your required level of detail, and posts to General Ledger.Sets of Books are replaced by the accounting entity’s ‘ledger’ for data, and its ‘Ledger Set’ for processing, from reporting, opening and closing, through allocations. Ledgers can be combined into ledger sets, and GL users are assigned to the ledger sets. User access to multiple operating units is called ‘Multi-Org Access Control’,(MOAC).

2. Multi-Org Access Control (Changed functionality): Multi-Org Access Control enables companies that have implemented a Shared Services operating model to efficiently process business transactions by allowing them to access, process, and report on data for an unlimited number of operating

units within a single applications responsibility. This increases the productivity of Shared Service Centers, as users and processes no longer have to switch applications responsibilities when processing transactions for multiple operating units at a time. Data security and access privileges are still maintained using security profiles that now support a list of operating units.

3. Multi-Org Security Profile Preferences(Changed functionality): A Multi-Org Security Profile defines the list of operating units to which a user has access. If a user typically uses a subset of the operating units in his security profile, he may set up Preferences to limit the operating units available to him
during transaction processing. The user can also set a default ‘operating unit’ tominimize manual data entry when an operating unit context is required.

4. Enhanced Multi-Org Reporting(Changed functionality): Consistent with the Multi-Org Access Control feature, users are able to run reports using two levels:

• Ledger: The report runs for all operating units within a ledger to which the
user has access
• Operating Unit: The report runs for a selected operating unit that belongs to the user’s security profile.

5. Multi-Org Integration with Accounting Setup Manager:(New functionality) The Accounting Setup Manager is a central location to define your accountingrelated setup across all financial applications. Here, you can define your legal entities and their accounting context, which includes the ledgers that will contain the accounting data for each legal entity. Multi-Org is integrated into the Accounting Setup Manager such that users can define operating units and their relationship to ledgers. For each operating unit, users can also select a legal entity to provide a default legal context during transaction processing. This centralizes your setup and makes it easier to inquire on and maintain relationships between ledgers, legal entities, and operating units.

6.GL Accounting Setup- Simultaneous Accounting for Multiple Reporting Requirements:(New functionality)

Companies that are global in nature and that have operations in different localities often have multiple reporting requirements. These companies and their subsidiaries often need to satisfy the accounting and reporting requirements for each country as well as those of the parent company. This involves performing accounting in accordance with accounting principles and standards of multiple countries and in different currencies, charts of accounts, and/or calendars. The reporting requirements can also be statutory in nature, and one subsidiary may even need to satisfy multiple sets of statutory requirements. Oracle General Ledger simplifies the simultaneous management of the accounting for all of these different reporting requirements in this latest release. You are able to define your legal entities and the setup needed to address each accounting and reporting requirement using the Accounting Setup Manager. New enhancements and integration with Subledger Accounting enable Oracle General Ledger to perform accounting for all reporting requirements of a legal entity simultaneously.

7. Centralized Accounting Setup(New feature): The Accounting Setup Manager is a central location to define your accounting-related setup across all financial applications. Here you can define your legal entities and their accounting context, which includes the ledgers* that contain the accounting data for each legal entity. If a legal entity has multiple reporting requirements, you can include additional reporting currencies or ledgers in the accounting context to satisfy the additional requirements.

8. Enhanced Reporting Currency Functionality (Changed functionality) : Multiple Reporting Currencies functionality is enhanced to support all journal sources. Reporting sets of books are now simply reporting currencies. Every journal that is posted in the primary currency of a ledger can be automatically converted into one or more reporting currencies. This conversion can be performed by Subledger Accounting, to convert all subledger journal entries, or by General Ledger, to convert more summarized General Ledger journals. You can choose to convert any journal sources and

categories.

9. Improved Processing Efficiency- Simultaneous Data Access to Multiple Legal Entities and Ledgers: -New feature.

Can access multiple legal entities and ledgers when you log into Oracle General Ledger using a single responsibility. This improves processing efficiency by reducing the need to switch between responsibilities when trying to access data for different ledgers or legal entities.

10.Simultaneous Opening and Closing of Periods for Multiple Ledgers: (New feature) The Open and Close Periods Programs have multiple enhancements. You are able to run any of the Open and Close Periods Programs from the Concurrent Manager. This allows you to take advantage of scheduling and request set capabilities for greater processing efficiency. Also, if you manage multiple

ledgers, you can open or close periods for multiple ledgers simultaneously. You can even keep the status of periods across multiple ledgers in synch with new programs that ensure a specific period is Open or Closed for all of the ledgers you manage.

11. Cross-Ledger and Foreign Currency Allocations:(New feature) You are able to allocate financial data from one or more ledgers to a different target ledger. This enables you to perform cross-ledger allocations, which is useful for purposes such as allocating corporate or regional expenses to local

subsidiaries when each entity has its own ledger. This is possible even if the target ledger is in a different currency than the source ledger(s) because you can create allocations in foreign currencies. Foreign currency allocations are also useful within a single ledger if you need to allocate amounts to a currency that is different from the primary currency of a ledger.

12. Simultaneous Currency Translation of Multiple Ledgers (New functionality) If business manages multiple ledgers; you can run the Translation program for multiple ledgers simultaneously.

13. Financial Reporting Across Ledgers (New Functionality): Business is able to run Financial Statement Generator (FSG) reports for multiple ledgers simultaneously. This is useful if you manage multiple ledgers and want to run a balance sheet or income statement report for all ledgers at the same time.

14. Automatic Journal Copy:(New Feature) Business is able to automatically copy an existing journal batch to create a new journal batch with the same journals and journal lines. This reduces the amount of work you need to do to re-create a journal that has already been defined. During the copying process, you have the option to change the period and effective date of the journal batch.

15. Streamline Automatic Posting(New Feature): AutoPost Criteria can be shared across ledgers that have the same chart of accounts and calendar. This dramatically reduces the number of AutoPost Criteria sets you need to define. Furthermore, you can automatically post journals across multiple ledgers imultaneously.

16. Streamline AutoReversal Criteria Setup:(New feature) AutoReversal Criteria can be shared across ledgers. This dramatically reduces the number of AutoReversal Criteria sets you need to define.

17. Streamline Consolidation Mappings : You are able to define Chart of Accounts Mappings (formerly known as Consolidation Mappings) between two charts of accounts. Therefore, if you
have multiple Consolidation Definitions for parent and subsidiary ledgers that share the same chart of accounts pair, and their mapping rules are the same, you only have to define a single Chart of Accounts Mapping. This significantly reduces the number of mappings you need to define if your Consolidation Definitions involve the same pair of charts of accounts and the mapping rules are the same.

18. Replacement for Disabled Accounts: When an account is disabled, you can prevent transactions that include the account from erroring during journal import by defining a replacement account for the disabled account. Journal import replaces the disabled account with the replacement account and continue the journal import process if the replacement account is valid. This improves processing efficiency by preventing the journal import process from erroring and enabling the successful creation of the journal with minimal user intervention when an account has been disabled.

19. Data Security across Legal Entities and Ledgers: In R12 release, since you can access multiple legal entities and ledgers when you log into Oracle General Ledger using a single responsibility, Oracle General Ledger provides you with flexible ways to secure your data by legal entity, ledger, or even balancing segment values or management segment values. You are able to control whether a user can only view data, or whether they can also enter and modify data for a legal entity, ledger, balancing segment value or management segment value.

20. Management Reporting Security: You can designate any segment (except the natural account segment) of your chart of accounts to be your management segment and use Oracle General Ledger’s security model to secure the management segment for reporting and entry of management adjustments.

21. Prevent Reversal of Journals with Frozen Sources: Journals with frozen journal sources are prevented from being reversed to streamline the reconciliation of data from Subledger Accounting sources.

22. Prevent Reversal of Unposted Journals: Users are no longer allowed to reverse ‘Unposted’ journals.

23. Entered Currency Reporting and Analysis: Oracle General Ledger tracks the balances that are entered in your ledger’s primary currency. This enables customers to perform currency analysis on amounts that are entered in the ledger’s primary currency for the purposes of currency valuation and hedging.

24. Foreign Currency Recurring Journals: You can use Recurring Journals to create foreign currency journals. This enables user to pre-define journals that are recurring in nature and that are in foreign currencies and simply generate them when business need them.

25. Intercompany Balancing Support for Encumbrances: Intercompany encumbrance journals are automatically balanced during journal posting.

26. Integration with Subledger Accounting: Oracle Subledger Accounting provides tools that allow users to meet multigaap, corporate, and fiscal accounting requirements. With a flexible tool

called Accounting Methods Builder, users can determine the accounts, lines,descriptions, summarization, and dates of their journal entries. Users can also add detailed transaction information to journal headers and lines. Detailed subledger accounting journals are available for analytics,auditing, and reporting. They are summarized, transferred, imported and posted to Oracle General Ledger.

Oracle General Ledger’s integration with Subledger Accounting provides a unified process to post data to general ledger from Oracle subledgers and external feeder systems. Also, it provides a consistent view when drilling down from general ledger balances to subledger transactions. Please refer to the Oracle Subledger Accounting section of this document for more information.

27. Enhanced Intercompany: The Global Intercompany System (GIS) feature from previous releases has been incorporated into the Oracle Advanced Intercompany System product. Please refer to the Oracle Advanced Global Intercompany System section of this document for more information.

28. GL Standard Reports Integration With XML Publisher: Oracle General Ledger’s Account Analysis, General Journals and Trial Balance standard reports are now integrated with XML Publisher. Using XML Publisher allows you to leverage the formatting features of a word processing application to design the layout of your report.

In R12 a new product called Oracle Subledger Accounting is introduced.

Oracle Sub ledger Accounting is a new product in this release. Oracle Sub ledger Accounting enables corporations to comply with corporate,local and managerial accounting and audit requirements via increased control,visibility and efficiency.

HELP-MENU

• How to see application version, Form shortname and version of form
  (Help) About Oracle application
• (Help)Diagnostics ->Examine
  • Pass the apps password and investigate the value for some variable.
• (Help)Diagnostics ->Examine ….Chose $DESCRIPTIVE_FLEXFIELD$block
• (Help)Diagnostics ->Examine ….Chose $ENVIRONMENT$block
  • This has all primary environment variables.
• (Help)Diagnostics ->Examine ….Chose $PROFILE$block
  • this shows all profile options given to user who is accessing the application.
• (Help)Diagnostics ->Examine ….Chose system block…choose LAST_QUERY field
  • This will shows last query used by the form.
• (Help) Diagnostics -> Display Database error
  • This shows any database error message.
• (Help) Diagnostics -> Trace(checkbox)
  • The options are on and off for forms tracing. Tracing file (.trc) is put into user dump folder.

Oracle Purchasing Terminology

Terms used in the conventional purchasing system and as referred in Oracle Purchasing may be different. A brief explanation of the ‘Oracle Purchasing’ terms vis-à-vis the existing terminology is provided the following paragraphs. These terms are extensively used in documenting the ‘Purchasing - To Be’ flows and it is recommended that the various users of this system get acquainted with the same.

Requestor: Any Employee who requires specific items to meet his operational needs. Requestor may or may not have the system access to enter the on-line requisitions. Requestor with no computer access will give their requisitions manually on pre-printed requisition form to the requisition ‘Preparer’ within the concerned department.


Preparer: Employee in a department with the responsibility of entering Purchase Requisitions in the system.


Approver: Employee with the responsibility and authority of approving the requisition and / or the Quotation Analysis Document and / or the Purchase Orders.


Buyer: Employee in the Purchase Department with the responsibility of entering the Requests for Quotation, the Quotations received from the Supplier and the Purchase Orders in the new system.


Request For Quotation (RFQ): Synonym for ‘Inquiry’. RFQs are sent to the vendors, requesting them for their quotations for the items / services required to be purchased.

Quotation: Quotations are the ‘Vendor Offers’ for the required items / services.

Quotation Analysis: It is a ‘Comparative Statement of Quotations’.

Standard Purchase Order: Standard Purchase Orders are created for purchase of various items / services where details such as the quantity to be purchased and the negotiated costs.

Blanket Purchase Agreement: Blanket purchase agreements are signed with the vendor for the supply of goods / services over a period. Such agreements can be used when details of the goods / services you plan to buy from a specific supplier in a period are known, but you do not yet know the details of your delivery schedules. They can also be used to specify negotiated prices for your items before actually buying them.

Blanket Release: You can issue a Blanket Release against a Blanket Purchase Agreement to place the actual order with the vendor. The Releases should be within the Blanket Agreement effectivity dates.

Planned Purchase Order: It is a long term agreement committing to buy items / services from a single source. The tentative delivery schedule is given to the vendor along with other details like quantities and estimated costs.

Schedule Release: This document is issued to the vendor against a Planned Purchase Order to place the actual order. This document will confirm the specific quantity and delivery date to the vendor.

Contract Purchase Agreements: Contract Purchase Agreements may be entered into with suppliers to agree on specific terms and conditions without indicating the goods or services that will actually be purchased. Standard Purchase Orders can be issued at a later date referencing such Contracts.


Purchasing Cycle:

Requisitions: Requisitions generated by various departments of your organization. They basically say that ‘I WANT THIS ITEM’ mentioning the item quantity and required date

Request for Quotation: The purchasing person sends the requirement to various suppliers giving details of the item and can also specify own terms and conditions such as payment terms, price etc.

Quotations: The Supplier responds to the RFQ and sends their quotations mentioning details of the item and all their terms and conditions regarding payment terms, discount, delivery schedules, etc.

Purchase Orders: The quotations received from various suppliers are compared and PO made for them in which all the terms and conditions of the firm are mentioned as regards to Payment, price, etc.

Receiving Goods: Suppliers ship the goods, which are received in your organization

Payments: After clearance from the receiving department about the receipt of goods, payments are made to the suppliers.

Close the PO: After the items are received, payments made you can close the PO.


Purchasing Requirements
· Item
· Quantity
· Ship to Address
· Bill to Address
· Delivery Schedules
· Terms and Conditions
· PO Numbering
· Approval Authority
· Supplier
· Accounts

FAQ

What is the interface?
Interface Table is a table which is used as medium for transfer of data between two systems.

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

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

What are the User PARAMETERS in the Reports?
P_CONC_REQUEST_ID
P_FLEX_VALUE

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

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.

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.

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]
where current of clause?
1) use cursor to update or delete the current row
Where current of <>

What is the package?
Group logically related pl/sql types, items and subprograms.
1. package specification
2. package body
Advantages of a package:
A. Modularity
B. Easier Application Design
C.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.

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)
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

LOCKS?
Is to reduce concurrency
1) share lock
it allows the other users for only reading not to insert
2) exclusive lock
only one user can have the privileges of insert or
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.

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

AOL features in OM

Order Management uses the following AOL features
Document Sequences - Order Entry used Order Number Sources for order
numbering. It let you define sequences that were used to automatically
number Orders and Returns. You assigned an Order Number source to an
Order Type.

Order Management uses the AOL Document Sequences feature to meet
Order Numbering requirements. This lets you number Order and Returns
using Manual, Automatic or Gapless sequences.You can define Document Sequences using the AOL Define Document Sequences form. When you define an Order Transaction Type, the application automatically creates a Document Sequence Category of the same name. You can assign a pre-defined sequence to one or more Document Sequence Categories, using the AOL Sequence Assignments
form. When an Order is created, Order Management calls AOL Document
Sequence APIs to number the Order.

Attachments - In Order Entry you could define Notes and addition rules regarding when they were attached to an Order or Line. You had to manually choose to add the eligible Notes to the Order or Line. You could also define how the Notes were printed on various Reports. Database triggers were used to duplicate Note definition data in AOL.

Order Management drives off the AOL Attachment functionality enabling you to attach images and web pages (in addition to short or long text). It also offers multi-lingual Document capability. Attachment definition and usage data is stored only in AOL. Automatic Addition rule definitions are stored in Order Management (OE_ATTACHMENT_RULES,OE_ATTACHMENT_RULE_ELEMENTS).

In addition to the attributes
(Customer, Ship-to, Invoice-to, Order Type, Item, PO #) that were previously available, you can now define rules based on the Order Category,Line Category and Line Type.
Oracle Order Management - Sales Order
The Profile Option ‘OM: Apply Automatic Attachments’ determines
whether rule based attachments are automatically applied

How to Download Etrm PDF format files

Use the following :
http://appsre.us.oracle.com/11idoc/11.5.1/html/trmset.html

Information Templates In PO

Oracle Internet Procurement 11i uses information templates to pass necessary order processing information to suppliers. You may set up information templatesto gather additional informationWhen an information template is assigned to a category or item, Internet Procurement 11i prompts users to provide the information specified in the template

To define an information template:

1. Navigate to the Define Information Template window. From the Oracle
Purchasing menu, select Setup>Information Templates.

2. Enter an attribute name and description. The attribute name is the actual
field prompt that is displayed in Internet Procurement 11i.

3. Optionally, enter a default value to automatically appear in the field.

4. Indicate whether the field is mandatory for Internet Procurement 11i users.
If the field is mandatory, users will be prompted to enter a value in the field
before proceeding to complete the requisition.

5. Indicate whether to activate the attribute to actually display on Self
Service Purchasing pages. In certain circumstances, you may want to define an
attribute, but delay enabling it for display to Internet Procurement 11i users.

6. Choose Associate Template to associate the template with an item or an item
category. The Information Template Association window appears.

7. Select the type of association (item number or item category) you want to
associate with the template.

8. If you selected Item Number in the previous step, enter the number. If you
selected Item Category, enter the category.

General Ledger FAQ

What is Journal Import?

A) Journal import is an interface used to bring journal entries from legacy systems and other modules into the General Ledger.(Specifically Journal Import gets entries from legacy data into the GL base tables.

The tables populated during journal Import are

GL_JE_BATCHES,

GL_JE_HEADERS,

GL_JE_LINES,

GL_IMPORT_REFERENCES

What is the use of GL_Interface?

A) Gl_Interface is the primary interface table of General ledger. It acts as an interface between data originating from other modules such as AP,AR, Legacy data and the Gl Base tables.

What is Actual Flag?

A) Actual flag represents the Journal type.

A-Actual

B-Budget

E- Encumbrance.

What is Encumbrance?

A) It is a process of Reservation of funds for anticipated expenditure from a budget. Encumbrance integrates GL, Purchasing and Payables modules.

How many Key Flex Fields are there in General Ledger?

A)One. Accounting Key Flex Field.

How many types of Budgets are there?

A)Two Types.

Expenditure Budgets

Revenue Budgets.

What are Spot Rate, Corporate Rate, Transaction Calendar and Accounting Calendar?

Spot Rate:

An exchange rate which you enter to perform conversion based on the rate on a specific date. It applies to the immediate delivery of currency.
Corporate Rate:
An Exchange rate that we define to standardize rates for our company. This rate is the standard market rate determined by the senior financial management for use through out the organization.
User Rate:
Conversion rate that is defined by the user.
EMU Fixed Rate: An exchange rate that is provided automatically by the General Ledger while entering journals. It uses a foreign currency that has a fixed relationship with the euro.
Transaction Calendar: Defines the business days and holidays for any calendar.
Accounting Calendar: Defines different types of calendars namely Fiscal, Federal Fiscal, Month etc.

What is Security Rule?

Security Rules are defined to control the access of a flexfield segment value (Financial information) at a responsibility level.

What are Cross Validation & ADI?

CVS – Cross validate segments – Allows only valid code combinations.
ADI – Allow dynamic inserts. – Allows any code combination irrespective of validity.
ADI would prevail if both of CVS and ADI are checked.

What is Translation?

A) Translation is a process used to convert functional currency to other reporting currencies at the account balances level.

What is Revaluation?

A) It is process used to revalue assets and liabilities denominated in foreign currency into functional currency based on period end exchange rate we specify. Unrealized gains/losses are resulted because of exchange rate fluctuations which are recorded in unrealized gain/loss account in GL.

What is FSG (Financial Statement Generator)?

A) Financial statement generator feature helps us to generate reports such as balance sheets and income statements with out programming. It also provides a high degree of control on the rows, columns, contents and calculations on the report. Different components such as row set, column set, content set, row order, display set have to be defined before a statement is generated, of which row set and column set are mandatory.

What is Consolidation?

A) Consolidation is a period-end process of combining the financial results of separate business subsidiaries with the parent company to form a single combined statement of financial results.

At what level General Ledger data is secured?

A) GL data is secured at Set of Book level. Subledger module data is secured at Responsibility level (i.e., at Operating Unit Level).

Account Receivables FAQ

1) What is Autolockbox?
A) Auto lockbox is a service that commercial banks offer corporate customers to enable them to out source their account receivable payment processing. Auto lockbox can also be used to transfer receivables from previous accounting systems into current receivables. It eliminates manual data entry by automatically processing receipts that are sent directly to banks. It involves three steps
Import (Formats data from bank file and populates the Interface Table),
Validation(Validates the data and then Populates data into Interim Tables),
Post Quick Cash(Applies Receipts and updates Balances in BaseTables).
2)What is Transmission Format?
A) Transmission Format specifies how data in the lockbox bank file should be organized such that it can be successfully imported into receivables interface tables. Example, Default, Convert, Cross Currency, Zengen are some of the standard formats provided by oracle.
3)What is Auto Invoice?
A) Autoinvoice is a tool used to import and validate transaction data from other financial systems and create invoices, debit-memos, credit memos, and on account credits in Oracle receivables. Using Custom Feeder programs transaction data is imported into the autoinvoice interface tables.
Autoinvoice interface program then selects data from interface tables and creates transactions in receivables (Populates receivable base tables) . Transactions with invalid information are rejected by receivables and are stored in RA_INTERFACE_ERRORS_ALL interface table.
4) What are the Mandatory Interface Tables in Auto Invoice?
A)RA_INTERFACE_LINES_ALL, RA_INTERFACE_DISTRIBUTIONS_ALL
RA_INTERFACE_SALESCREDITS_ALL.
5) What are the Set up required for Custom Conversion, Autolockbox and Auto Invoice?
A) Autoinvoice program Needs AutoAccounting to be defined prior to its execution.
6) What is AutoAccounting?
A) By defining AutoAccounting we specify how the receivables should determine the general ledger accounts for transactions manually entered or imported using Autoinvoice. Receivables automatically creates default accounts(Accounting Flex field values) for revenue, tax, freight, financial charge, unbilled receivable, and unearned revenue accounts using the AutoAccounting information.
7) What are Autocash rules?
A) Autocash rules are used to determine how to apply the receipts to the customers outstanding debit items. Autocash Rule Sets are used to determine the sequence of Autocash rules that Post Quickcash uses to update the customers account balances.
8) What are Grouping Rules? (Used by Autoinvoice)
A) Grouping rules specify the attributes that must be identical for lines to appear on the same transaction. After the grouping rules are defined autoinvoice uses them to group revenues and credit transactions into invoices debit memos, and credit memos.
9) What are Line Ordering Rules? (Used by Autoinvoice)
A) Line ordering rules are used to order transaction lines when grouping the transactions into invoices, debit memos and credit memos by autoinvoice program. For instance if transactions are being imported from oracle order management , and an invoice line ordering rule for sales_order _line is created then the invoice lists the lines in the same order of lines in sales order.
10) In which table you can see the amount due of a customer?
A) AR_PAYMENT_SCHEDULES_ALL
11) How do you tie Credit Memo to the Invoice?
At table level, In RA_CUSTOMER_TRX_ALL, If you entered a credit memo, the PREVIOUS_CUSTOMER_TRX_ID column stores the customer transaction ID of the invoice that you credited. In the case of on-account credits, which are not related to any invoice when the credits are created, the PREVIOUS_CUSTOMER_TRX_ID column is null.
12)What are the available Key Flex Fields in Oracle Receivables?
A) Sales Tax Location Flex field, It’s used for sales tax calculations.
Territory Flex field is used for capturing address information.
13). What are Transaction types? Types of Transactions in AR?
A) Transaction types are used to define accounting for different transactions such as Debit Memo, Credit Memo, On-Account Credits, Charge Backs, Commitments and invoices.

14) What are the different statuses for Receipts?
A) Unidentified – Lack of Customer Information
Unapplied – Lack of Transaction/Invoice specific information (Ex- Invoice Number)
Applied – When all the required information is provided.
On-Account, Non-Sufficient Funds, Stop Payment, and Reversed receipt.

Customer Conversion:
Interface Tables :

RA_CUSTOMERS_INTERFACE_ALL

RA_CUSTOMER_PROFILES_INT_ALL
RA_CONTACT_PHONES_INT_ALL
RA_CUSTOMER_BANKS_INT_ALL
RA_CUST_PAY_METHOD_INT_ALL

Base Tables :

RA_CUSTOMERS

RA_ADDRESSES

RA_SITE_USES_ALL

RA_CUSTOMER_PROFILES_ALL

RA_PHONES

Auto Invoice:
Interface Tables :

RA_INTERFACE_LINES_ALL,

RA_INTERFACE_DISTRIBUTIONS_ALL
RA_INTERFACE_SALESCREDITS_ALL,

RA_INTERFACE_ERRORS_ALL
Base Tables :

RA_CUSTOMER_TRX_ALL,

RA_CUSTOMER_TRX_LINES_ALL,
RA_CUST_TRX_LINE_GL_DIST_ALL,

RA_CUST_TRX_LINE_SALESREPS_ALL,

RA_CUST_TRX_TYPES_ALL
AutoLockBox:
Interface Tables :

AR_PAYMENTS_INTERFACE_ALL (POPULATED BY IMPORT PROCESS)
Interim tables :

AR_INTERIM_CASH_RECEIPTS_ALL (All Populated by Submit Validation)
AR_INTERIM_CASH_RCPT_LINES_ALL,
AR_INTERIM_POSTING
Base Tables :

AR_CASH_RECEIPTS_ALL,

AR_RECEIVABLE_APPLICATIONS_ALL,

AR_PAYMENT_SCHEDULES_ALL ( All Populated by post quick cash)

ORDER MANAGEMENT FAQ

Base Tables Vs Interface Tables

Base Tables : OE_ORDER_HEADERS_ALL: Order Header Information
OE_ORDER_LINES_ALL: Items Information
OE_PRICE_ADJUSTMENTS: Discounts Information
OE_SALES_CREDITS: Sales Representative Credits.

Shipping Tables :WSH_NEW_DELIVERIES
WSH_DELIVERY_DETAILS
WSH_DELIVERY_ASSIGNMENTS
WSH_DELIVERIES

Interface Tables : OE_HEADERS_IFACE_ALL,
OE_LINES_IFACE_ALL
OE_PRICE_ADJS_IFACE_ALL,
OE_ACTIONS_IFACE_ALL
OE_CREDITS_IFACE_ALL (Order holds like credit check holds etc)

What is Order Import and What are the Setup's involved in Order Import?

A) Order Import is an open interface that consists of open interface tables and a set of API’s. It imports New, updated, or changed sales orders from other applications such as Legacy systems. Order Import features include validations, Defaulting, Processing Constraints checks, Applying and releasing of order holds, scheduling of shipments, then ultimately inserting, updating or deleting orders from the OM base tables. Order management checks all the data during the import process to ensure its validity with OM. Valid Transactions are then converted into orders with lines, reservations ,price adjustments, and sales credits in the OM base tables.

B) Setups:
· Setup every aspect of order management that we want to use with imported orders, including customers, pricing, items, and bills.
· Define and enable the order import sources using the order import source window.

3) the Order Cycle?

i) Enter the Sales Order
ii)Book the Sales Order(SO will not be processed until booked(Inventory confirmation))
iii)Release sales order(Pickslip Report is generated and Deliveries are created)
(Deliveries – details about the delivery. Belongs to shipping module (wsh_deliveries, wsh_new_deliveries, wsh_delivery_assignments etc) they explain how many items are being shipped and such details.
iv)Transaction Move Order (creates reservations determines the source and transfers the inventory into the staging areas)
v)Launch Pick Release
vi)Ship Confirm (Shipping Documents(Pickslip report, Performa Invoice, Shipping Lables))

4)Order to Cash Flow?

I. Enter the Sales Order
II.Book the Sales Order(SO will not be processed until booked(Inventory confirmation))
III.Release sales order(Pickslip Report is generated and Deliveries are created)
(Deliveries – details about the delivery. Belongs to shipping module (wsh_deliveries, wsh_new_deliveries, wsh_delivery_assignments etc) they explain how many items are being shipped and such details.
IV.Transaction Move Order (Selects the serial number of the product which has to be moved/ shipped)
V. Launch Pick Release
VI.Ship Confirm (Shipping Documents(Pickslip report, Performa Invoice, Shipping Lables))
VII. AutoInvoice (Creation of Invoice in Accounts Receivable Module)
VIII. Autolockbox ( Appling Receipts to Invoices In AR)
IX.Transfer to General Ledger ( Populates GL interface tables)
X. Journal Import ( Populates GL base tables)
XI.Posting ( Account Balances Updated).

5)What are the Process Constraints?
A. Process Constraints prevent users from adding updating, deleting, splitting lines and canceling order or return information beyond certain points in the order cycle. Oracle has provided certain process constraints which prevent data integrity violations.
Process constraints are defined for entities and attributes. Entities include regions on the sales order window such as order, line, order price adjustments, line price adjustments, order sales credits and line sales credits. Attributes include individual fields (of a particular entity) such as warehouse, shit to location, or agreement.
6) What are different types of Holds?
1)GSA(General Services Administration) Violation Hold(Ensures that specific customers always get better pricing for example Govt. Customers)
2)Credit Checking Hold( Used for credit checking feature Ex: Credit Limit)
3)Configurator Validation Hold ( Cause: If we invalidate a configuration after booking)

7)What is Document Sequence?
A) Document sequence is defined to automatically generate numbers for your orders or returns as you enter them. Single / multiple document sequences can be defined for different order types.
Document sequences can be defined as three types Automatic (Does not ensure that the numbers are contiguous), Gapless (Ensures that the numbering is contiguous), Manual Numbering. Order Management validates that the number specified is unique for order type.

8) What are Defaulting Rules?
A) A defaulting rule is a value that OM automatically places in an order field of the sales order window. Defaulting rules reduce the amount of information one must enter. A defaulting rule is a collection of defaulting sources for objects and their attributes.
It involves the following steps
· Defaulting Conditions - Conditions for Defaulting
· Sequence – Priority for search
· Source – Entity ,Attribute, Value
· Defaulting source/Value
10. When an order cannot be cancelled?
A) An order cannot be cancelled if,
· It has been closed
· It has already been cancelled
· A work order is open for an ATO line
· Any part of the line has been shipped or invoiced
· Any return line has been returned or credited.
11. When an order cannot be deleted?
A) you cannot delete an order line until there is a need for recording reason.
12. What is order type?
A) An order type is the classification of order. It controls the order work flow activity, order number sequence, credit check point and transaction type. Order Type is associated to a work flow process which drives the processing of the order.
13. What are primary and secondary price lists?
A) Every order is associated to a price list as each item on the order ought to have a price. A price list is contains basic list information and one or more pricing lines, pricing attributes, qualifiers, and secondary price lists. The price list that is primarily associated to an order is termed as Primary price list.
The pricing engine uses a Secondary Price list if it cannot determine the price of the item ordered in the Primary price list.
14. What is pick slip? Types?
A) It is an internal shipping document that pickers use to locate items to ship for an order.
· Standard Pick Slip – Each order will have its own pick slip with in each picking batch.
· Consolidated Pickslip – Pick slip will have all the orders released in the each picking batch.
15. What is packing slip?
A) It is an external shipping document that accompanies the shipment itemizing the contents of the shipment.
16. What are picking rules?
A) Picking rules define the sources and prioritization of sub inventories, lots, revisions and locators when the item is pick released by order management. They are user defined set of rules to define the priorities order management must use when picking items from finished goods inventory to ship to a customer.
17. Where do you find the order status column?
A) In the base tables, Order Status is maintained both at the header and line level. The field that maintains the Order status is FLOW_STATUS_CODE. This field is available in both the OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL.
18. When the order import program is run it validates and the errors occurred can be seen in?
A) Responsibility: Order Management Super User
Navigation: Order, Returns > Import Orders > Corrections

Workflow Access Levels

0-9: Reserved for Oracle Workflow
10-19: Reserved for Oracle Application Object Library
20-99: Reserved for Oracle E-Business Suite
100-999: Reserved for customer organizations
1000: Public.

Blogger Buzz: Blogger: now in even more languages

Blogger Buzz: Blogger: now in even more languages

Purchasing Options

Navigation: Setup > Organizations > Purchasing Options
Screen: Purchasing Options

Requisition Import Group - By
This value determines how the system should group all those Requisitions lines generated by Oracle Inventory based upon the Planning Mechanism. Group requisition lines for each item on a separate requisition
Rate Type
The default rate type is used when the Purchasing Document is in Foreign Currency. The user rate type will ask the user to enter the conversion rate vis-à-vis the foreign currency.
Minimum Release Amount
Minimum Release Amount will determine the minimum amount for which a release can be entered against an Agreement.
Taxable
No.
Price Break Type
Price Break indicates if the Vendor is offering any quantity discount. The Price Break Type will determine the mechanism by which the system should sum up the total Quantity so that the correct Price defaults from the Price Break.
Price Type
This value is used only for referential purpose. Fixed Price Type will indicate that the Price reflected on the Purchase Order is a Fixed Price after negotiating the same with the vendor.
Quote Warning Delay
Quote Warning Delay will determine the number of Days in Advance the system should warn the user before the Quotation expiry date.
RFQ Required
RFQ Required indicates the Buyer that an RFQ was Required for this Requisition before the same was converted into a Purchase Order.
Receipt Close Tolerance
PO Closes for receiving when 95% of the good is received.
Invoice Close Tolerance
No over Invoice Quantity Allowed i.e. the Invoice Quantity and the PO quantity should always match.
Line Type
The default line type in all the Purchasing Documents.
Invoice Matching
Determines the type of Matching the system will subject the Invoice against the source Purchase document.
Accrual
Accrue Expense Items
Determines when the Expense Items/Services will be Accrued.
Accrue Inventory Items
Inventory Accrual will be done Perpetually i.e. The system will accrue the liability on receipt of Goods which are Stockable (Current Assets) in nature.
Expense AP Accrual Account
The default Expense AP Accrual Account.
Control
Price Tolerance
The Price Tolerance allowed when the Purchase Order Price differs from the Item List Price as entered in the Item Master.
Enforce Price Tolerance
Determines whether the Price Tolerance should be enforced or not.
Enforce Full Lot Quantity
Not Applicable
Display Disposition Messages
Not Applicable
Receipt Close Point
This option determines when the system should close the Purchase Order close for receiving.
Notify if Blanket PO Exists
The option determines whether the system should Notify you, In case you are buying an Item on Standard Purchase Order though a Blanket Agreement exists for that Item.
Cancel Requisitions
In case of a Purchasing Document being cancelled, how the system should treat the associated Requisition. Should it cancel the Requisition optionally or overtime?
Allow Item Description Update
This control Attribute will determine whether the Item description can be updated or not at the time of raising a Purchasing document.
Security Hierarchy
The Security Hierarchy determines the various positions, which will have access to the various documents.
Enforce Buyer Name
This option will restrict the other buyer from accessing the documents belonging to another Buyer.
Enforce Vendor Hold
If a Vendor has been put on hold in the Vendor Master, should the system stop you from entering any Purchasing documents against that vendor?
Numbering
RFQ Number – Entry
Numbering options determines the way the system should number the various purchasing documents.
RFQ Number – Type
-do-
RFQ Number – Next Number
-do-
Quotation Number – Entry
-do-
Quotation Number – Type
-do-
Quotation Number – Next Number
-do-
PO Number – Entry
-do-
PO Number – Type
-do-
PO Number – Next Number
-do-
Requisition Number – Entry
-do-
Requisition Number – Type
-do-
Requisition Number – Next Number
-do-

OM Flow and table level Information

Steps in Order Cycle:


1) Order Entry
2) Booking
3) Pick release :
For this we have to go to
Shipping Responsibilty Release sales order
Here In this form , In the ORDER tab, we have to enter ORDER Number
And delete the Scheduled shipped Dates To & Requested Dates To.
In SHIPPING tab, set AUTO CREATE DELIVERY to YES. In INVENTORY tab enter WAREHOUSE, set AUTO ALLOCATE to YES and AUTO PICK CONFIRM to YES. IF we set AUTO PICK CONFIRM to NO, then We have to go for the following steps

1. go to Inventory Resp
Move order à Transact Move Order then it will ask for
warehouse information. Give the same name as before [M2]
In this form, In the HEADER tab, enter the BATCH
NUMBER of the order that is picked .Then Click FIND
Button. Click on VIEW/UPDATE Allocation, then
Click TRANSACT button. Then Transact button will be
deactivated then just close it and go to next step.

4) Shipping :
For this we need to go to Shipping Transaction Give the order Number, and click find
Then we can see the order status.
Then we have to click DELIVERY Tab Button, in the Action LOV
We have to choose, SHIP CONFIRM.
Then four concurrent program will run in the background.
Such As::
1.) INTERFACE TRIP Stop
2.) Commercial Invoice
3.) Packing Slip Report
4.) Bill of Lading

After this concurrent program will complete successfully, we have to run
One more WORKFLOW BACKGROUND PROGRAM.
· If we don’t want to ship all the items, that are PICKED, then we have to click LINE/LPN tab , then click DETAIL button .
Now, in that form , in the SHIPPING field, we have to enter how Much quantity of items, we want to ship . The rest remain quantity, that are Ordered will become backorder quantity .

5) Interfacing with AR :

After WORKFLOW BACKGROUND PROGRAM
Concurrent program will complete successfully, we have to run
AUTO INVOICE MASTER PROGRAM from
RECEIVABLE RESPONSIBILTY. After this program
will complete successfully , we can the invoice details in
RECEIVALE à TRANSACTIONS à TRANSACTIONS. Here in
This Form, we have to give our order number in reference field
And query for the invoice details .Then we can see the invoice details.




Table Level Information:
==========================
Order Entry
• At the header level a record gets inserted into the header table
OE_ORDER_HEADERS_ALL.
• At the line level, record(s) get inserted into the Line table
OE_ORDER_LINES_ALL.

Order Booking
• This will update FLOW_STATUS_CODE value in the table
OE_ORDER_HEADERS_ALL to “BOOKED”
• The FLOW_STATUS_CODE in OE_ORDER_LINES_ALL will change to
AWAITING_SHIPPING.
• Record(s) will be created into the table WSH_DELIVERY_DETAILS with
RELEASED_STATUS=’R’ (Ready to Release)
OE_INTERFACED_FLAG=’N’ (Not interfaced to OM)
INV_INTERFACED_FLAG=’N’ (Not interfaced to Inv)
• Record(s) will be created into WSH_DELIVERY_ASSIGNMENTS but with
DELIVERY_ID null.

Pick Release
------------------
IF “Autocreate Delivery” option = “Yes” THEN
• ) Create a record into the table WSH_NEW_DELIVERIES
• ) Update WSH_DELIVERY_ASSIGNMENTS with DELIVERY_ID, thus
• ) Update WSH_DELIVERY_DETAILS with RELEASED_STATUS=’Y

Auto Invoicing
----------------------
Before running “Autoinvoice Program”, record(s) will exist into the table
RA_INTERFACE_LINES_ALL with

INTERFACE_LINE_CONTEXT = ’ORDER ENTRY’
INTERFACE_LINE_ATTRIBUTE1 = &Order_number
INTERFACE_LINE_ATTRIBUTE3 = &Delivery_id
SALES_ORDER = &Order_number

After running the “Auto invoice Program” for the order:
Records will be deleted from the table RA_INTERFACE_LINES_ALL and new details will be created into the following RA transaction tables.
>RA_CUSTOMER_TRX_ALL with
INTERFACE_HEADER_ATTRIBUTE1=&Order_number
RA_CUSTOMER_TRX_LINES_ALL with
INTERFACE_LINE_ATTRIBUTE1 = &Order_number
SALES_ORDER = &Order_number

Know Current APPS Current Versions.

1)select product_version,patch_level from fnd_product_installations
Get current version ana Patch level information.
2)select * FROM V$VERSION
Database Version infomation.
3)select * from v$instance
Instance details
4)select WF_EVENT_XML.XMLVersion() XML_VERSION from sys.dual;
Current XML Parser Version info.
5)select TEXT from WF_RESOURCES where TYPE = 'WFTKN' and NAME = 'WF_VERSION'
Workflow version Number.
6)select home_url from icx_parameters
Oracle applications front end URL
7)SELECT VALUE FROM V$PARAMETER WHERE NAME=’USER_DUMP_DEST’
Get the Trace file location.
8) XML Publisher Vesion info.
$OA_JAVA/oracle/apps/xdo/common/MetaInfo.class.

Another way to find the Jdev Path and DBC file Location.

Log on to Sysadmin-> profiles->
Personalize Self-Service Defn Yes
2)Bounce the Apache and click on about This page.
3)Click on Java System Properties
System Property
DBCLocation :
-> /u02/app/apntstv2/ntstv2appl/fnd/11.5.0/secure/ntstv2_nacdell03/

Then Click on Technology Components
Product/Component
1)OA Framework -> 11.5.10 2CU
2)Oracle Applications Extension -> 9.0.3.8.12 (build 1271)
3)Business Components->9.0.3.13.51
4)MDS->9.0.5.4.81_481

Forward Declaration

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;