Submit Concurrent Requests at the OS level

CONCSUB is a utility for allowing the Sysadmin user name and password to have the ability to submit concurrent requests at the OS level. This utility, unlike many of the Applications utilities, is not menu driven. It runs from the command line, submits a concurrent request, and returns you to the command prompt once the concurrent request completes. You can check the status of your concurrent request via the Concurrent Request form

Syntax

CONCSUB applsys/pwd ‘responsibility application short name’ ‘responsibility name’ ‘username’ [wait=] CONCURRENT ‘Program application short name’ PROGRAM

CONCSUB Parameters and Their Meanings

Applsys/pwd

Oracle application user name and password that connects to Applications Object Library.

Responsibility Application Short Name

Application short name of the responsibility you want to run the request for.

Responsibility Name

Name of the responsibility for which you want to run the request.

Username

User name of the person who is submitting the request.

Wait

Do you want CONCSUB to wait before returning the OS command prompt?

N (default value) waits until the job completes.

Y returns you to the command prompt.

“n” is the number of seconds to wait before it exits.

If this parameter is used, it has to come before concurrent.

Program Application Short Name

Short name of the program (for deactivate, abort, and verify, the program application short name is FND).

PROGRAM

The program to submit (e.g., DEACTIVATES, VERIFY, ABORT).

Tables Used by Concurrent Request Concurrent Program

FND_CONCURRENT_REQUESTS

Contains a complete history of all concurrent requests (both past history and those scheduled to run in the future).

FND_RUN_REQUESTS

Stores information about the reports in a report set that a user submits including the report set’s parameter values.

FND_CONC_REQUEST_ARGUMENTS

Records all arguments passed by Concurrent Managers to concurrent requests as those requests are running.

FND_DUAL

Records when a request does not update any database tables.

FND_CONCURRENT_PROCESSES

Records information about Oracle Applications processes and OS processes.

FND_CONC_STAT_LIST

Collects runtime performance statistics for concurrent requests.

FND_CONC_STAT_SUMMARY

Contains Concurrent Program performance statistics generated by the Purge Concurrent Request program or the manager data program. These programs use the data in FND_CONC_STAT_LIST to compute these statistics।

Different Types of Concurrent Manager

Different Types of Concurrent Manager

Conflict Resolution Manager (CRM)

The Conflict Resolution Manager enforces all compatibility rules and based on priorities and run rules, determines

which jobs can run when if there is a conflict in timing. You cannot change its definition, but can set its values for sleep

time for each work shift or for parallel Concurrent Processing, if applicable.

Product Specific Concurrent Manager

There are many product specific Concurrent Managers. The list includes

Inventory, MRP, and Projects, as well as any

User-defined managers. These managers are specialized to perform Concurrent Processing specifically for those

products for which they are built. Utilizing these managers can help you off-load some of the processing from the

Standard Manager.

Internal Concurrent Manager (ICM)

The Internal Concurrent Manager (ICM) is the controlling manager for all of the others. When you start the Concurrent

Managers, this is the only one that you actually have direct control over. This manager in turn starts all of the others

depending on their schedules and work shifts. It controls starting and stopping all other managers based on the

definition of their work shifts and it monitors for failures. If there are failures, it cleans up after them. Its definition

cannot be changed after its startup. On starting, you can, by parameter passing, set its values for sleep time, PM ON

on cycle, and queue size.

Scheduler Manager

The Scheduler Manager, added in 11i, assists the ICM and the CRM in scheduling and conflict resolution.

Standard Manager

The Standard Manager (as the name implies) is the manager that ships with the Oracle E-Business Suite and accepts

any and all requests and does not, as configured, have any specialization rules. The Standard Manager is

Customizable but care needs to be taken to ensure that, if you change the rules on the Standard Manager, that all jobs

Have a manager that is able to run them.

Transaction Managers

Conventional Concurrent Managers run batch type jobs that are typically long running, involve large amounts of data,

and run asynchronously. Transaction Managers run synchronous processing of certain reports requested from a client

Program but run as a server side program. These managers run as immediate programs, are started automatically by

the ICM, and communicate with Transaction Managers automatically. Running the job is transparent to the calling user

as the job runs extremely quickly and in real time. The calling client is notified of the ultimate outcome of the program

Execution by a completion message and a set of values returned to them.

A Transaction Manager is owned by an application and associated with a data group. Due to this association, and the

fact that it runs immediate programs, the Transaction Manager can only run programs contained within its program

Library.

$FND_TOP/sql/afcmstat.sql script gives you a list of concurrent managers and their respective status

Executable Concurrent Manager Description

CYQLIB Capacity Manager.

FNDCRM Conflict Resolution Manager.

ARLIBR Receivables Tax Engine.

FNDIMON Internal Monitor.

FNDLIBR Applications Object Library (AOL) — The ICM and the Standard Manager are both members of this library.

FNDSCH Scheduler Manager.

INVLIBR Inventory Manager Library.

MRCLIB Oracle MRP Library.

PALIBR Oracle Project Accounting.

POXCON Purchase Order Document Approval.

RCVOLTM Receiving Transaction Manager.

Account Receivable Profile Options

In this post i will share some interesting information about Oracle Receivable Module.this information gather form different sources (metalink,Google and my personal experience as well)
I will update this information as i got any further assistance from any source

AR: Allow Overapplication in Lockbox

This profile option controls how AutoLockbox handles receipts when the payment amount is greater than the balance due for a transaction. When a payment exceeds the balance due, AutoLockbox closes the transaction and leaves a negative balance due for the item if both of the following are true:

• AR: Allow Overapplication in Lockbox is set to Yes

• the open debit item’s transaction type has Allow Overapplication set to Yes

If either of these are not true, AutoLockbox applies only enough to close the transaction and leaves the remaining receipt amount unapplied.

This profile option can be set by the system administrator at the site, application, and responsibility levels but cannot be updated by the user.

AR: Allow summary table refresh

Set this profile option to Yes if you want to allow the data contained within the transaction summary and open balance tables to be initialized or reset.

After the tables are populated, changes that occur to transaction balances are updated in the summary tables via business events.

Use this profile option for added security to ensure that the summary tables are refreshed only when necessary.

This profile option can be set by the system administrator or user at the application level.

AR: Allow Update of Existing Sales Credits

This profile option determines whether a user can update existing sales credits or if additional sales credit records need to be created to maintain an audit trail.

AR: Always Default Transaction Balance for Applications

This profile option determines the default amount applied value that displays in the Applications window, whether you enter applications directly or by using the Search and Apply feature. The default value includes discount amounts, where applicable.

If you set the profile option to Yes, then the default amount applied is the remaining transaction amount.

If you set the profile option to No, or if a null value exists, then the defaulting rule is:

1. If the unapplied receipt amount is greater than or equal to the transaction, then the default amount applied is the remaining transaction amount.

2. If the unapplied receipt amount is less than the remaining transaction amount, then the default amount applied is the unapplied receipt amount.

3. If the unapplied receipt amount is negative, then the default amount applied is the remaining transaction amount.

This profile option can be set by the system administrator at the site, application, responsibility, and user levels. The user can also update this profile option.

AR: Application GL Date Default

This profile option determines how Receivables determines the default GL Date when you apply receipts. Choose one of the following values:

• Later of Receipt GL date and Invoice GL date: Choose this value to use either the receipt GL date or the invoice GL date, whichever is later, as the default GL date for your receipt applications. This is the default value.

• Later of Receipt GL date, Invoice GL date, and Current date: Choose this value to use the receipt GL date, the invoice GL date, or the current date, whichever is later, as the default GL date for your receipt applications.

This profile option can be set by the system administrator at the site, application, and responsibility levels but cannot be updated by the user.

AR: AutoInvoice Gather Statistics

This profile option determines if the AutoInvoice Master program analyzes and gathers information about the interface tables each time AutoInvoice is run. Analyzing tables ties up system resources.

If the value for this profile option is set to Yes, or is null, AutoInvoice analyzes the interface tables and gathers statistics.

If the value is set to No, AutoInvoice does not analyze the interface tables.

This profile option can be set by the system administrator at the site, application, responsibility, and user levels. The user can also update this profile option.

AR: Bank Directory Source

This profile option is used by iReceivables for bank account transfer payments that make use of the Automated Clearing House (ACH) network. The profile option provides iReceivables with access to the E-Payment routing directory via the Federal Reserve Financial Services web site, a local file downloaded from this web site, or both. iReceivables uses the E-Payment routing directory to derive the name of the bank or financial institution from the routing number that a customer enters to pay an invoice using an ACH bank account transfer.

This profile option can be set by the system administrator at the site, application, responsibility, and user levels but cannot be updated by the user.

AR: Bank Directory URL

This profile option is used by iReceivables to identify the URL in Oracle iReceivables that will host the Federal Reserve Financial Services web site. This profile option is set when the AR: Bank DIrectory Source profile option is set to Web Services or Web Service First then Local.

This profile option can be set by the system administrator at the site level but cannot be updated by the user.

Useful Queries for Oracle Applications 11i

1. Responsibilities Listing
Purpose	To get list of responsibilities.
Description	Query useful when user wants to get application wise responsibility list
Parameters	None
Query	SELECT (SELECT application_short_name FROM fnd_application fa WHERE fa.application_id = frt.application_id) application, frt.responsibility_id, frt.responsibility_name FROM apps.fnd_responsibility_tl frt;

2. Menus Listing
Purpose	To get Menus Associated with responsibility
Description	User to check menu attached with a reponsilblity
Parameters	responsibility_id Which user can get from query of section Responsibilities Listing
Query	SELECT DISTINCT a.responsibility_name, c.user_menu_name FROM apps.fnd_responsibility_tl a, apps.fnd_responsibility b, apps.fnd_menus_tl c, apps.fnd_menus d, apps.fnd_application_tl e, apps.fnd_application f WHERE a.responsibility_id(+) = b.responsibility_id AND a.responsibility_id = ‘20538’ AND b.menu_id = c.menu_id AND b.menu_id = d.menu_id AND e.application_id = f.application_id AND f.application_id = b.application_id AND a.LANGUAGE = ‘US’;

3. Submenu And Function Listing
Purpose	To get submenus and Function attached to this Main menu.
Description	By using this query user can check function and sub menus attached to that specific menu
Parameters	User_menu_name Which user can get from query of section Menu Listing
Query	SELECT c.prompt, c.description FROM apps.fnd_menus_tl a, fnd_menu_entries_tl c WHERE a.menu_id = c.menu_id AND a.user_menu_name = ‘F4 UK PAY Navigator’;

4. User And Assigned Responsibility Listing
Purpose	To get assigned responsibility to a user.
Description	User wants to check responsibility attached to a specific user
Parameters	None
Query	SELECT UNIQUE u.user_id, SUBSTR (u.user_name, 1, 30) user_name, SUBSTR (r.responsibility_name, 1, 60) responsiblity, SUBSTR (a.application_name, 1, 50) application FROM fnd_user u, fnd_user_resp_groups g, fnd_application_tl a, fnd_responsibility_tl r WHERE g.user_id(+) = u.user_id AND g.responsibility_application_id = a.application_id AND a.application_id = r.application_id AND g.responsibility_id = r.responsibility_id ORDER BY SUBSTR (user_name, 1, 30), SUBSTR (a.application_name, 1, 50), SUBSTR (r.responsibility_name, 1, 60);

5. Responsibility And Assigned Request Group Listing
Purpose	To get responsibility and attached request groups.
Description	Every responsibility contains a request group(request group is basis of submitting requests)
Parameters	None
Query	SELECT responsibility_name responsibility, request_group_name, frg.description FROM fnd_request_groups frg, fnd_responsibility_vl frv WHERE frv.request_group_id = frg.request_group_id ORDER BY responsibility_name

6. Profile Option With Modification Date and User
Purpose	To get modified profile options.
Description	Query used for audit point of view i।e. when a profile is changed and by whom user
Parameters	None
Query	SELECT t.user_profile_option_name, profile_option_value, v.creation_date, v.last_update_date, v.creation_date - v.last_update_date “Change Date”, (SELECT UNIQUE user_name FROM fnd_user WHERE user_id = v.created_by) “Created By”, (SELECT user_name FROM fnd_user WHERE user_id = v.last_updated_by) “Last Update By” FROM fnd_profile_options o, fnd_profile_option_values v, fnd_profile_options_tl t WHERE o.profile_option_id = v.profile_option_id AND o.application_id = v.application_id AND start_date_active <= SYSDATE AND NVL (end_date_active, SYSDATE) >= SYSDATE AND o.profile_option_name = t.profile_option_name AND level_id = 10001 AND t.LANGUAGE IN (SELECT language_code FROM fnd_languages WHERE installed_flag = ‘B’ UNION SELECT nls_language FROM fnd_languages WHERE installed_flag = ‘B’) ORDER BY user_profile_option_name;

7. Forms Personalization Listing
Purpose	To get modified profile options.
Description	Personalization is feature available in 11.5.10.X. For More detail on form Personalization Use Following Tables (Rule_id) is reference key for these tables applsys.fnd_form_custom_actions, applsys.fnd_form_custom_scopes
Parameters	None
Query	SELECT ffft.user_function_name “User Form Name”, ffcr.SEQUENCE, ffcr.description, ffcr.rule_type, ffcr.enabled, ffcr.trigger_event, ffcr.trigger_object, ffcr.condition, ffcr.fire_in_enter_query, (SELECT user_name FROM fnd_user fu WHERE fu.user_id = ffcr.created_by) “Created By “ FROM fnd_form_custom_rules ffcr, fnd_form_functions_vl ffft WHERE ffcr.ID = ffft.function_id ORDER BY 1;

8. Patch Level Listing
Purpose	To get Patch Level.
Description	Query used to view the patch level status of all modules
Parameters	None
Query	SELECT a.application_name, DECODE (b.status, ‘I’, ‘Installed’, ‘S’, ‘Shared’, ‘N/A’) status, patch_level FROM apps.fnd_application_vl a, apps.fnd_product_installations b WHERE a.application_id = b.application_id;

9. Function Listing
Purpose	To get all Functions
Description	Complete forms and functions
Parameters	None
Query	SELECT function_id, user_function_name, creation_date, description FROM applsys.fnd_form_functions_tl order by order by user_function_name;

10. Request Attached To Responsibility Listing
Purpose	To get all Request attached to a responsibility
Description	View all request who have attached to a responsibility
Parameters	None
Query	SELECT responsibility_name , frg.request_group_name, fcpv.user_concurrent_program_name, fcpv.description FROM fnd_request_groups frg, fnd_request_group_units frgu, fnd_concurrent_programs_vl fcpv, fnd_responsibility_vl frv WHERE frgu.request_unit_type = ‘P’ AND frgu.request_group_id = frg.request_group_id AND frgu.request_unit_id = fcpv.concurrent_program_id AND frv.request_group_id = frg.request_group_id ORDER BY responsibility_name;

11. Request Listing Application Wise
Purpose	To get all request with application
Description	View all types of request Application wise
Parameters	None
Query	SELECT fa.application_short_name, fcpv.user_concurrent_program_name, description, DECODE (fcpv.execution_method_code, ‘B’, ‘Request Set Stage Function’, ‘Q’, ‘SQL*Plus’, ‘H’, ‘Host’, ‘L’, ‘SQL*Loader’, ‘A’, ‘Spawned’, ‘I’, ‘PL/SQL Stored Procedure’, ‘P’, ‘Oracle Reports’, ‘S’, ‘Immediate’, fcpv.execution_method_code ) exe_method, output_file_type, program_type, printer_name, minimum_width, minimum_length, concurrent_program_name, concurrent_program_id FROM fnd_concurrent_programs_vl fcpv, fnd_application fa WHERE fcpv.application_id = fa.application_id ORDER BY description

12. Count Module Wise Reports
Purpose	To Count Module Wise Report
Description	Application wise request counting
Parameters	None
Query	SELECT fa.application_short_name, DECODE (fcpv.execution_method_code, ‘B’, ‘Request Set Stage Function’, ‘Q’, ‘SQL*Plus’, ‘H’, ‘Host’,