I have had a question been asked recently to explain to the layperson how oracle executables work.
The idea of Oracle customisations is simple. Place the customised file on the server and then hit the submit request and viola the process is executed! However, what exactly does this mean? A lot of apps users just see the magic of their customised process without a clear understanding of how it all goes together.
The first step is to determine what type of program is been sought to be customised as this will determine some of the treatment on the server side. This can take the form of a Report, Sql, Package, java or xml. These customisations can take parameters from the request submission screen and execute a program.
The first section is the creation of the customisation. If the customisation is a unix shell script, this is usually put in a $CUST_TOP/bin directory, where CUST_TOP is a certain directory as determined by an application setup within the Application developer (N:Application Developer --> Application --> Register).
The bin is to show that it should be a shell script or other executable. The executable then needs to be set to be executable through the chmod command. Oracle also requires the creation of a symbolic link through the command
ln -s $FND_TOP/bin/fndcpesr CUSTOM_PROGRAM_NAME
this command will make the unix shell script an executable that Oracle can handle. The shell script usually requires this additional work in relation to making it executable and usable with Oracle.
Other customisations are as simple as placing them in the relevant directory depending on their type.
SQL scripts will be put in the $CUST_TOP/sql directory.
Packages can be installed into Oracle and executed as a concurrent program without having to be placed in the relevant directories and can be installed from a sql plus session, by executing the sql file.
A report on the other hand should go into the $CUST_TOP/reports/US directory.
The next step which will be explained is to setup the application within the Oracle Application itself.
The idea of Oracle customisations is simple. Place the customised file on the server and then hit the submit request and viola the process is executed! However, what exactly does this mean? A lot of apps users just see the magic of their customised process without a clear understanding of how it all goes together.
The first step is to determine what type of program is been sought to be customised as this will determine some of the treatment on the server side. This can take the form of a Report, Sql, Package, java or xml. These customisations can take parameters from the request submission screen and execute a program.
The first section is the creation of the customisation. If the customisation is a unix shell script, this is usually put in a $CUST_TOP/bin directory, where CUST_TOP is a certain directory as determined by an application setup within the Application developer (N:Application Developer --> Application --> Register).
The bin is to show that it should be a shell script or other executable. The executable then needs to be set to be executable through the chmod command. Oracle also requires the creation of a symbolic link through the command
ln -s $FND_TOP/bin/fndcpesr CUSTOM_PROGRAM_NAME
this command will make the unix shell script an executable that Oracle can handle. The shell script usually requires this additional work in relation to making it executable and usable with Oracle.
Other customisations are as simple as placing them in the relevant directory depending on their type.
SQL scripts will be put in the $CUST_TOP/sql directory.
Packages can be installed into Oracle and executed as a concurrent program without having to be placed in the relevant directories and can be installed from a sql plus session, by executing the sql file.
A report on the other hand should go into the $CUST_TOP/reports/US directory.
The next step which will be explained is to setup the application within the Oracle Application itself.
Now let’s explore some extra different advantages of it and see if it would be proper for your applications. Stainless metal sheet is usually offered in the annealed condition and is available in most grades. Our chrome steel sheets are available in} both a normal 2B finish and various polished finishes. Polished surfaces vary from the usual #4 to a mirrored finish #8 and are normally lined with a removable vinyl coating. Our normal sheet sizes include 4’ x 8’, 4’ x 10’, and 5’ x 10’, but high precision machining custom-made sizes are also obtainable.
ReplyDelete