Wednesday, 4 May 2011

Autonomous transaction


Autonomous transaction

It is an independent transaction started by the another transaction the main or parent transaction, do SQL operations, commit or rollback operations the resume back to the main transaction.

Once started an autonomous transaction is fully independent. It shares no locks, resources, or commit-dependencies with the main transaction. 

More important autonomous transaction help you build modular reusable software components.You can use autonomous transaction in your report for writing error message in your database tables.

Multiple Operating Units.


Multiple Operating Units.

The following two  profile options are necessary to give access to multiple operating units.

1.MO: Security Profile
2.MO: Operating Unit
  • The profile option  "MO: Security Profile"  should not be set at Site level
  • You must set the MO:Operating Unit profile option for each responsibility.You must also define the default operating unit by setting the  MO:Operating Unit  profile at the site level. 

Benfits of XML Publisher.

Benfits of XML Publisher.


1)MLS Support
Supports 160 languages and 200 Territories.
2)XML Publisher will integrate with the workflow product
3)Rapid Development
4)Reduce Maintence Cost
5)High Performance and Scalability
6)Compressed PDF OUTPUT
7)Repeating Header and Footer
8)Greater Flexibility of customization
9)Schedule Print and FAX directly from the server
10)Support for Internet Printing Protocol(InternetFAX protocol,SMTP,WebDAV)
11)Handle Large XML input files and accept from different source like DB2,SQL server.. etc
12)Security At PDF level like (read only, Password Protection)


PL/SQL compiler directives

PL/SQL compiler directives



As of the current release of PL/SQL, we have 4 directives

1)AUTONOMOUS_TRANSACTION.
2)RESTRICT_REFERENCES
3)EXCEPTION_INIT.
4)SERIALLY_REUSABLE.



AUTONOMOUS_TRANSACTION:
A subprogram marked with this pragma can do SQL operations and commit or roll back those operations, without committing or rolling back the data in the main transaction. 

RESTRICT_REFERENCES:
To be callable From SQL statements, a stored function must obey certain purity rules, which control side-effects. If any SQL statement inside the function body violates a rule, you get an error at run time. You can declare the pragma RESTRICT_REFERENCES only in a package spec or object type spec.

EXCEPTION_INIT:
The pragma EXCEPTION_INIT associates an exception name with an Oracle error number.A pragma is an instruction to the Oracle compiler that tells it to do something. In this case you are telling Oracle to associate an error that you choose to a variable that you choose

SERIALLY_REUSABLE:
The pragma SERIALLY_REUSABLE indicates that the package state is needed only for the duration of one call to the server. An example could be an OCI call to the database or a stored procedure call through a database link. PRAGMA
Signifies that the statement is a pragma (compiler directive). Pragmas are processed at compile time, not at run time

Types of Application Patches

Types of Application Patches

There are several different types of Oracle Applications patches. These are the more common patches

1)One-off patch: This is the simplest type of patch. It is created to resolve a specific bug.
2)Minipack patch: This is a collection of one-off patches and enhancements related to a particular module
3)Family Pack patch: This is a collection of Minipack patches for a particular family group of application modules
4)Maintenance Pack patch: This is a collection of Family Packs that serves as a point-level release upgrade
5)Consolidated patch: This is a collection of one-off fixes for a Family Pack or Maintenance Pack
6)Interoperability patch: This is a patch that is required for Oracle Applications to function with a newer version of a technology stack
component;
7)NLS patch: This is a patch that updates language-specific information for multi-language installations
8)Rollup patch: This is a collection of one-off patches that update code levels for particular products
9)Legislative patch: This is a special patch for HR Payroll customers; it contains legislative data for multiple countries.

FNDLOAD

FNDLOAD

when we are working in oracle application development/implementation project? The equally important AOL data Migration takes place necessary to synchronize the data across databases instance during installation and upgarde.

Using FNDLOAD can download data from an application entity into an editable text file, which can be uploaded to another database.The Conversion between database format and text file format is specified by a configuration file.

What can be Done?


·It can be done following list

· Concurrent Programs, Executables
· Request Groups, Request Sets
· Profile Options
· Key and Descriptive Flexfields
· Menus and Responsibilities
· Forms and Form Functions
· Attachments
· Messages
· Value Sets and Values
· Lookup Types
· User Responsibilities
· Printer Definitions
· FND Dictionary
· Help Configuration
· Document Sequences
· Concurrent Manager Schedules 


Advantages when using FNDLOAD 
1. Because downloaded data is stored in a text file, version administration is possible2. No learning curve. this is relief for developer/dbas
3. Fully supported and recommended by Oracle
4. Capture the migrations in a file and use it during installations(log file).
5. Pin-point when something happened and where (database) easily

6. AOL data migration process is now simplified!


Disadvantages
1. Applications patching mechanisms use FNDLOAD heavily possibility of negative impact is not zero
2. No validation against migrating database/instance sensitive data 


The Syntax 
To use FNDLOAD, the following syntax is needed.

FNDLOAD apps/appspwd 0 Y mode configfile datafile entity [parameter1.....]
· The mode is either DOWNLOAD or UPLOAD.
· The configfile is the file that Fndload needs to download on upload data.
· T he data file is the output file, in which the downloaded data is written
· The entity is the entity you want to download,
·


Example of download:
FNDLOADapps/pwd 0 Y DOWNLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt \ PROGRAM CONCURRENT_PROGRAM_NAME= concurrent_program_short_name> APPLICATION_SHORT_NAME=application_short_name

Example of Upload
FNDLOAD apps/pwd 0 Y UPLOAD ${FND_TOP}/patch/115/import/afcpprog.lct myfile.ldt - CUSTOM_MODE=FORCE undocumented parameter

Where is Config File Located

· Configuration files with extension .lct
o On Unix - all the configuration files are in $FND_TOP/patch/115/import directory
o On Unix Oracle also places the original configuration files in $FND_TOP/admin/import directory
·Data files with extension .ldt
· The configfiles (.lct) are delivered and maintained by Oracle
· It has entity definitions, parent-child relationships and user input parameters identified by :NAME

oDownloading a parent automatically downloads all children - (Example) Concurrent Program download


Sample Script Code for these Objects : 

1 - Printer Styles
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcppstl.lct file_name.ldt STYLE PRINTER_STYLE_NAME=printer style name


2 - Lookups
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/aflvmlu.lct file_name.ldt FND_LOOKUP_TYPE APPLICATION_SHORT_NAME=prod LOOKUP_TYPE=lookup name


3 - Descriptive Flexfield with all of specific Contexts
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt DESC_FLEX P_LEVEL=?COL_ALL:REF_ALL:CTX_ONE:SEG_ALL? APPLICATION_SHORT_NAME=prod DESCRIPTIVE_FLEXFIELD_NAME=desc flex name P_CONTEXT_CODE=context name


4 - Key Flexfield Structures
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt KEY_FLEX P_LEVEL=?COL_ALL:FQL_ALL:SQL_ALL:STR_ONE:WFP_ALL:SHA_ALL:CVR_ALL:SEG_ALL? APPLICATION_SHORT_NAME=prod ID_FLEX_CODE=key flex code P_STRUCTURE_CODE=structure name


5 - Concurrent Programs
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct file_name.ldt PROGRAM APPLICATION_SHORT_NAME=prod CONCURRENT_PROGRAM_NAME=concurrent name



6 - Value Sets
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET FLEX_VALUE_SET_NAME=value set name


7 - Value Sets with values
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afffload.lct file_name.ldt VALUE_SET_VALUE FLEX_VALUE_SET_NAME=value set name


8 - Profile Options
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct file_name.ldt PROFILE PROFILE_NAME=profile option APPLICATION_SHORT_NAME=prod


9 - Requset Group
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct file_name.ldt REQUEST_GROUP REQUEST_GROUP_NAME=request group APPLICATION_SHORT_NAME=prod


10 - Request Sets
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct file_name.ldt REQ_SET APPLICATION_SHORT_NAME=prod REQUEST_SET_NAME=request set


11 - Responsibilities
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct file_name.ldt FND_RESPONSIBILITY RESP_KEY=responsibility


12 - Menus
FNDLOAD apps/apps@seed115 O Y DOWNLOAD $FND_TOP/patch/115/import/afsload.lct file_name.ldt MENU MENU_NAME=menu_name


13 Forms/Functions
FNDLOAD apps/apps@seed115 0 Y DOWNLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt FND_FORM_CUSTOM_RULES The Upload syntax for all styles: FNDLOAD apps/apps@seed115 0 Y UPLOAD $FND_TOP/patch/115/import/affrmcus.lct file_name.ldt



14. 
User/Responsibilities
FNDLOAD apps/apps@seed115 0 Y DOWNLOAD @FND:patch/115/import/afscursp.lct file_name.ldt FND_USER Then UPLOAD FNDLOAD apps/apps@seed115 0 Y UPLOAD [UPLOAD_PARTIAL] @FND:patch/115/import/afscursp.lct file_name.ldt FND_USER []

Default username/passwords in Oracle Applications

*****Default username/passwords in Oracle Applications*****

Many Applications users are predefined in the Vision Demo.
The following username/password pairs have System Administrator responsibility.



1.SYSADMIN/SYSADMIN
2.MFG/WELCOME
3.OPERATIONS/WELCOME
4.SERVICES/WELCOME
5.MRC/WELCOME
6.HRMS/WELCOME


Note: password are small case.