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’, ‘L’, ‘SQL*Loader’, ‘A’, ‘Spawned’, ‘I’, ‘PL/SQL Stored Procedure’, ‘P’, ‘Oracle Reports’, ‘S’, ‘Immediate’, fcpv.execution_method_code ) exe_method, COUNT (concurrent_program_id) COUNT FROM fnd_concurrent_programs_vl fcpv, fnd_application fa WHERE fcpv.application_id = fa.application_id GROUP BY fa.application_short_name, fcpv.execution_method_code ORDER BY 1;

13. Request Status Listing
Purpose	To calculate request time
Description	This query will shows report processing time
Parameters	None
Query	SELECT f.request_id , pt.user_concurrent_program_name user_concurrent_program_name , f.actual_start_date actual_start_date , f.actual_completion_date actual_completion_date, floor(((f.actual_completion_date- f.actual_start_date)*24*60*60)/3600) || ‘ HOURS ‘ || floor((((f.actual_completion_date- f.actual_start_date)*24*60*60) - floor(((f.actual_completion_date- f.actual_start_date)*24*60*60)/3600)*3600)/60) || ‘ MINUTES ‘ || round((((f.actual_completion_date- f.actual_start_date)*24*60*60) - floor(((f.actual_completion_date- f.actual_start_date)*24*60*60)/3600)*3600 - (floor((((f.actual_completion_date- f.actual_start_date)*24*60*60) - floor(((f.actual_completion_date- f.actual_start_date)*24*60*60)/3600)*3600)/60)*60) )) || ‘ SECS ‘ time_difference , DECODE(p.concurrent_program_name,‘ALECDC’, p.concurrent_program_name||‘['||f.description||']‘, p.concurrent_program_name) concurrent_program_name , decode(f.phase_code,‘R’,‘Running’,‘C’, ‘Complete’,f.phase_code) Phase , f.status_code FROM apps.fnd_concurrent_programs p , apps.fnd_concurrent_programs_tl pt , apps.fnd_concurrent_requests f WHERE f.concurrent_program_id = p.concurrent_program_id and f.program_application_id = p.application_id and f.concurrent_program_id = pt.concurrent_program_id and f.program_application_id = pt.application_id AND pt.language = USERENV(‘Lang’) and f.actual_start_date is not null ORDER by f.actual_completion_date-f.actual_start_date desc;

14. User And Responsibility Listing
Purpose	Check responsibility assigned to a specific USER
Description
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 and a.application_name = ‘Purchasing’ ORDER BY SUBSTR (user_name, 1, 30), SUBSTR (a.application_name, 1, 50), SUBSTR (r.responsibility_name, 1, 60)

15. Applied Patch Listing
Purpose	Check Current Applied Patch
Description
Parameters	None
Query	SELECT patch_name, patch_type, maint_pack_level, creation_date FROM applsys.ad_applied_patches ORDER BY creation_date DESC

HOW TO IDENTIFY DESCRIPTIVE FLEXFIELDS NAME

To identify the descriptive fliexfield in a form Follow the below mentioned steps

           1. Navigate to the window and block, and set the cursor at the              field for which you want to get the descriptive flex field Information.

           2. Navigate Help->Tools->Examine from the menu bar.  You may be              asked to enter a password. Enter Password of APPS Schema

           3. The Examine Field and Variable Values window initially              displays the hidden block and field names of the field              your cursor was in. Note the block name and field name displayed to assist you later selecting the correct flexfield.

           4. Click the down arrow symbol in the block field.  Select              $DESCRIPTIVE_FLEXFIELD$ in Choose a block window. Click OK.

           5. Click the down arrow symbol in the Field field.  Select              the descriptive flexfield you want.  The LOV displays              the block names and field names for all descriptive              flexfields on that form.

           6. The flexfield title that appears in the Value field is              the descriptive flexfield name with application enclosed in              a pair of parenthesis.  Note the descriptive flexfield name.              This is the title to choose in the Descriptive Flexfield              Segments form.  

Components of the standalone Oracle Forms product

The standalone Oracle Forms product is composed of the following: Forms Builder – this program is used to create and modify Forms modules.

Forms Compiler – this program is used to generate your FMX files.
Forms Runtime – this program is the engine that runs your Form logic when you form is deployed in client/server.
Forms Metric Server – this program is used in Forms load balancing.
Forms Metric Client - this program is used in Forms load balancing.
Forms CGI – this program dynamically generates the applet html that defines your form.
Forms Server – this program listens for Forms Runtime engine requests.
Forms Web Runtime - this program is the engine that runs your Form logic when your form is deployed over the web.

Difference between lexical and bind variable

Bind references are used to replace a single value in SQL or PL/SQL. Specifically, bind references may be used to replace expressions in SELECT, WHERE, GROUP BY, ORDER BY, HAVING,CONNECT BY, and START WITH clauses of queries. Binds may not be referenced in the FROM clause. An example is:

SELECT Col1,Col2

FROM XX_table

WHERE Col1 = _col1

Lexical references are placeholders for text that you embed in a SELECT statement. You can use lexical references to replace the clauses appearing after SELECT, FROM, WHERE, GROUP BY , ORDER BY , HAVING, CONNECT BY, and START WITH. You cannot make lexical references in PL/SQL. Before you reference a lexical parameter in a query you must have predefined the parameter and given it an initial value. An example is:

SELECT Col1,Col2

FROM &ATABLE

What is a Lexical Parameter

Lexical parameters are used to substitute multiple values at runtime and are identified by a preceding ‘&’. Lexical s can consist of as little a one line where clause to an entire select statement

Lexical Parameters are used to execute query dynamically.

Example: An example of a lexical parameter usage in a select statement is as follows

Select * from XX_table, XX_table 2

&where.

In the properties of the ‘where’ user parameter, make sure that the data type of the ‘where’ user parameter is set as character. If you know the maximum length that your where clause is going be, you can set the width of the where parameter to be slightly greater than that number. Otherwise, set it to some number like 100.

If your lexical parameter (‘where’) width is not enough to hold the where condition assigned to it, you will receive one of the following errors depending on your Reports version.

REP-0450 – Unhand led exception,

and ORA-6502- PL/SQL numeric or value error.

or

REP-1401 – Fatal PL/SQL error in afterptrigger

and ORA-6502-PL/SQL numeric or value error.

What is a Bind Variable In Oracle Reports

Bind parameters are used to substitute single value at runtime for evaluation and are identified by a preceding ‘:’.

An example of a bind parameter in a select statement is provided below, where :P_Name is the bind parameter reference.

Select Name,Value

From XX_Table

Where Name= _Name

These are used as tokens while registering concurrent program

Order Management Profile Options with there effects

AR: Use Invoice Accounting for Credit Memos
Receivable does not require you to enter a Revenue Account for Credit Memo transaction Types if the profile option AR: Use Invoice Accounting for Credit Memos is set to Yes. Otherwise, you must enter a Revenue Account
This profile option determines whether to assign your credit memo to the same accounts that are assigned to the invoice you are crediting.

BOM: Check for Duplicate Configuration
Indicates whether to search for an existing duplicate configuration rather than create a new item
Match and Reserve ATO Configurations allow you to check for an existing matching configuration and reserve against it. While entering an order you can search for matching active ATO configurations and associated available-to-transact quantities based on the options selected for the entered order line. To select a matching configuration the following criteria must be met:
The order must be booked
The order line cannot have an associated configuration item assigned
The profile option BOM: Check for Duplicate Configurations must be set to Match and Reserve

BOM: Component Item Sequence Increment
Indicates the value by which to increment the sequence of the component item on the bill

BOM: Configurator URL of UI Manager
User for Web based configuration required in case of oracle Configurator

BOM: Default Bill of Material Levels
Indicates the number of explosion levels to use as a default for bill of material indented explosions
Journals: Display Inverse Rate
Journals: Display Inverse Rate set to Yes, General Ledger will display inverse exchange rates in the Enter Journals and other windows. For example, assume that the profile option is set to Yes and your functional currency is USD. If you enter the AUD to USD rate as .7793 in the Daily Rates window, General Ledger will display the inverse rate, or 1.2832, in the Enter Journals window when you create a foreign currency journal using AUD as the foreign currency.

OM: Administer Public Queries
OM: Administer Public Queries is set to Yes, you will see a checkbox labeled Public. Checking this checkbox will save this query under Public Folders and all users will see it. Leaving this checkbox unchecked will save this query under Personal Folders and only you will have access to it.

Technical Aspects of CRM

Technical Aspects of CRM
While it must be emphasized that CRM is not a technology, there are a number of technical issues that need to be considered when a company decides to implement a CRM system. The first technical issue that needs to be analyzed is scalability. In a nutshell, the CRM system must be very scalable, and the volue of information within the system should never reach an end. It must be able to grow over time as the company collects more information.
The CRM systems which are the most scalable are also the most valuable. Another thing that the company must look at is communication. The goal of Customer relationship management is to build a powerful bond with your customers.

A company cannot be successful with this if they cannot effectively communicate with those they serve. It is not enough to use one method of communication. Instead, multiple forms of communication must be used. This includes the telephone, Internet, television, radio, magazine, and any other form of communication available. When a company is able to effectively communicate with their customers, this will give them the necessary resources to succeed. It is also important for companies to look at “workflow.” In this context the term workflow is used to describe the business processes the company will use to track and maintain information.

It is not enough for a company to get information. If they want to become successful and maintain a presence in the market, the company must be able to properly process and analyze the information they receive. In addition to workflow, it is also important for organizations to consider the “assignment.” The term “assignment” can be used to provide specific requests to an individual or group. By giving the correct assignments to the proper entities, a company will be capable of reaching their goals once these assignments have been carried out. One thing that all CRM systems have in common is a database. The database is the place where customer information will be stored.

The database may also be referred to as being a data warehouse. Because the company will be storing information that is related to their customers, it is important for them to look at privacy issues. Data encryption should be used at all times, and the company must make sure they are functioning within the boundaries of the law. Customer relationship management is a powerful tool because it will allow a company to track the buying habits of their clients. This information can be analyzed on an individual level, and this can allow a company to market specific products to specific customers. In addition to tracking the purchases, the company can also track the product itself, and they can store a great deal of information on it.

In order for a purchase to be repeated, the customer must be satisfied. In order for this to occur, the customer must understand the needs of the customers they serve. It could be said that CRM is just the opposite of “one size fits all.” It will deal with customers on an individual level. Privacy is an important issue that companies must consider when implementing a CRM system. If a company violates the privacy of their customers, this can damage the relationship that they’ve worked hard to build up. In order to avoid this problem, companies must be careful when implementing and utilizing a CRM system. They must know how to get the information they need without violating the privacy of their customers.

To deal with the privacy issue, it is important for companies to understand the concerns of the customers. In most cases, customers are wary of having their information stored in a database that can fall into the hands of third party companies. To handle these concerns, the company must create a policy of making sure this information is never shared under any circumstances. The customers must be informed of this policy, and the company must make sure it is followed. The only time the information should be shared is if the customer allows it. Many customers will not mind providing companies with information as long as they have asked for it. When a company uses clandestine methods to get data on their customers, this will destroy their reputation of the customers should discover it.

With Thanks to exforsys.com

Types Of application Patch

There are several different types of patches following are more common patches

One-Off Patch
This is simplest Patch to resolve a specific bug

Minipack Patch
Collection of One of Patches and enhancements related to a particular module. Alphabetic character denotes the Minipack version for the module.

Family Pack Patch
Collection of Minipack patches for a particular family group of application modules

Maintenance pack patch
This is collection of family packs that serves as point level release upgrade

Consolidated patch
Collection of one-off fixes for a family pack or maintenance pack Oracle Application 11.5.10 Consolidated Update 2 (CU2) is an example of consolidated patch.

Interoperability patch
Patch that is required for application to function with a newer version of technology stack

NLS patch
Patch that updates language specific information for multi language installation

Rollup patch
This is a collection of one off patches that update code levels for particular product

Legislative patch
Special patch for HR payroll customers it contains legislative data for multiple countries

HOW TO IDENTIFY THE VERSION OF A FORM

It is important to identify the current version of the program that is experiencing the problem, as a bug in the version of the program you are running may be the cause of your problem.
Form
A Form version is easily obtained via the front-end application. The navigation path is as follows –

-> Help -> About Oracle Application

Dialog Box appear
Search following
“Current Form”

—————————————-
Current Form
—————————————-
Form Application : Application Object Library
Form Name : FNDSCAUS
This Is Form name Currently Open
Form Path : /d01/oracle/prodappl/fnd/11.5.0/forms/US/FNDSCAUS.fmx
Complete path of Form
Form Version : 11.5.78
Form Last Modified : $Date: 2005/05/16 11:52 $

—————————————-
Forms
—————————————-
APPSTAND : 11.5.33
FNDSCAUS : 11.5.78
FNDSCSGN : 11.5.115

—————————————-
Form Menus
—————————————-
FNDMENU : 11.5.49

—————————————-
Forms PL/SQL
—————————————-
APPCORE : 11.5.142
CUSTOM : 11.5.5.1150.1
FNDSQF : 11.5.111
GHR : 11.5.150
GLOBE : 11.5.44.115103.4
GMS : 11.5.230.90.7
IGILUTIL2 : 11.5.97
IGILUTIL : 11.5.29
OPM : 11.5.33.115100.2
PQH_GEN : 11.5.118
PSA : 11.5.162
PSAC : 11.5.16
PSB : 11.5.24
VERT : 11.5.6

Oracle e business Suite

Before starting Oracle e business Suite I would like to discuss a little about ERP
Enterprise Resource Planning or ERP is an industry term for integrated, multi-module application software packages that are designed to serve and support multiple business functions. An ERP system can include software for manufacturing, order entry, accounts receivable and payable, general ledger, purchasing, warehousing, transportation and human resources. ERP modules may be able to interface with an organization’s own software, It’s depending on the software
Oracle E-Business Suite is the industry’s only complete and integrated set of enterprise applications, working together seamlessly to streamline every area of your business.
From sales, service, and marketing, through financial and human resources, to supply chain and manufacturing. Oracle E-Business Suite is fastest path to high-quality enterprise intelligence, It brings company a true 360-degree view of your finances, your customers, and your supply chains matters,
You can make faster, better decisions and grow profitability in a competitive marketplace.
Application software typically automates only departmental business processes. Oracle
E-Business Suite is different;
It automates all parts of your business. From Sampling, Marketing, Selling, Ordering, planning, procuring, manufacturing, fulfilling, servicing, and maintaining, to handling finance, human resources, and project management. Oracle E-Business Suite provides a comprehensive and integrated offering. In the past, we had to choose between an integrated suite and “best of breed” for rich functionality. With Oracle, we can now have an integrated suite built on unified information architecture—with the functionality we need in each individual application. These applications connect business processes within and across departmental, geographical, and line-of-business domains. With Oracle E-Business Suite’s depth of product functionality and breadth of product offering, you can take your business further by automating processes across the enterprise.

Hello

It’s my first blog entry, so I’d like to say Hello to everybody interested in Oracle Application technology!

On this blog I’ll post my thoughts on Oracle e business Suite and related development areas.

I thought it was about time I expanded my web presence and my intentions for this blog are to share some tips and tricks I find on my journeys started five to six years back.

now point, from where I got such level of motivation to start blogging.

Well men behind this are Mr. Shahid Mahmood and Mr. Sikandar Hayat www.erpstuff.com