Menu
Oracle E-Business Suite Developer's Guide Browser version script Oracle E-Business Suite Developer's Guide Release 12.2 Part Number E22961-15 Coding Oracle Tools Concurrent Programs Oracle Tool Concurrent Programs Oracle Application Object Library lets you write concurrent programs in SQL.Plus, PL/SQL (if you have PL/SQL installed on your database), SQL.Loader, or Oracle Reports. For SQL.Plus and PL/SQL programs, the concurrent manager logs onto the database, starts your program, automatically spools output to a report output file, and logs off the database when your program is complete. If your program produces report output, you can define your program to have the concurrent manager automatically print the report output file after your program completes. Reports submitted through Standard Request Submission have printing and submission information set at run time.
SQL.PLUS Programs For SQL.Plus programs, the concurrent manager automatically inserts the following prologue of commands into your SQL.Plus script: SQL.Plus Prologue SET TERM OFF SET PAUSE OFF SET HEADING OFF SET FEEDBACK OFF SET VERIFY OFF SET ECHO OFF WHENEVER SQLERROR EXIT FAILURE The concurrent manager also inserts a command into your SQL.Plus script to set LINESIZE according to the print style of the script. If you want your SQL.Plus script to continue after a SQL error, you must insert the following line into your SQL.Plus script: WHENEVER SQLERROR CONTINUE PL/SQL Stored Procedures PL/SQL stored procedures behave like immediate concurrent programs in that they do not require the concurrent manager to create an independent spawned process. Concurrent programs using PL/SQL stored procedures can generate log files or output files. Your stored procedure concurrent program must have errbuf and retcode as the first two parameters.
Use errbuf to return any error messages, and retcode to return completion status. The parameter retcode returns 0 for success, 1 for success with warnings, and 2 for error. After your concurrent program runs, the concurrent manager writes the contents of both errbuf and retcode to the log file associated with your concurrent request. See for more information and an example. PL/SQL File I/O Processing Package FNDFILE contains routines which allow as concurrent programs to write to the request log and output files, stored under /log and /out. Note: FNDFILE is supported in all types of concurrent programs. Text written by the stored procedures is first kept in temporary files on the database server, and after request completion is copied to the log and out files by the manager running the request.
Opening and closing files is handled behind the scenes by the concurrent manager. Every read and write to the temporary files is implicitly flushed to minimize risk of data loss. The concurrent managers maintain a shared pool of temporary files; when a manager starts up, it attempts to use filenames from the pool. If no filenames exist, the manager creates new temporary log and output files.
These two files are cleared after each concurrent request, and then reused for the next request. As a result no more temporary files are created than necessary. The temporary files are named as follows, where the x's indicate a sequence number, padded to 7 digits: lxxxxxxx.req oxxxxxxx.req The directory for temporary files must be set in the environment variable APPLPTMP when the managers are started.
This directory must also be listed in the UTLFILEDIR parameter in init.ora. To write to these log and output files, simply call the necessary procedures.
Program Sql Editor
Opening and closing the files is handled by the concurrent managers. Procedure arguments and exceptions are detailed below.
There are several limitations of these procedures. The temporary files cannot be deleted, but are reduced to 0-length. Deleting them must be handled by the system administrator. This package is not designed for generic PL/SQL text I/O.
It is only used for writing to request log and output files. Using these APIs may impact your application's performance. Temporary files are first created and then copied over the network to the request log and out files. Moving large files can be slow, and can create considerable network traffic.
You may wish to be conservative with the amount of data written from your concurrent program. To facilitate debugging and testing from SQL.Plus, you can use the procedure FNDFILE.PUTNAMES(LOG, OUT, DIR).
This function sets the temporary log and out filenames and the temporary directory to the user-specified values. DIR must be a directory to which the database can write. FNDFILE.PUTNAMES should be called before calling any other FNDFILE function. If this function is not called when using SQL.Plus, FNDFILE will choose a filename from the pool, as described above.
FNDFILE.PUTNAMES works only once per session, and it does nothing if called from a concurrent program. Procedure FNDFILE.CLOSE will close the files in a command-line session. FNDFILE.CLOSE should not be called from a concurrent program; the concurrent manager will handle closing files.
SQL.Loader For SQL.Loader programs, the concurrent manager runs SQLLOAD on the control file specified on the Concurrent Program Executable form. If your program produces report output, you can define your program to have the concurrent manager automatically print the report output file after your program completes. You can either supply information about the data file in the control file, or pass the full directory path and file name of your data file as an argument. The concurrent manager passes the 'data=(full pathname of data file)' token at request run time. Without a data file name, the concurrent manager skips that token and SQL.Loader uses the data file name specified in the control file. If you port your application to a different operating or hardware system, check the directory and file name of your data file and change the value of your program argument if necessary. Accepting Input Parameters For Oracle Tool Programs You should write your program to receive arguments in the same order that you specify when you call your program and pass arguments.
Concurrent managers pass the arguments directly to your programs. In SQL.Plus and PL/SQL programs, you must name your arguments &1, &2, &3, etc. So that you are guaranteed to get the first argument you pass in &1, the second in &2, and so on. With PL/SQL stored procedures, you should define your arguments as IN parameters. In SQL.Loader programs, pass the full directory path and file name of your data file as an argument. If you port your application to a different operating or hardware system, check the directory and file name of your data file and change the value of your program argument if necessary. See: Naming Your Oracle Tool Concurrent Program If your operating system is case-sensitive, the file name of your Oracle Tool concurrent program should always be in uppercase and the extension in lowercase.
Use the information in the Oracle E-Business Suite Setup Guide for your operating system to determine the correct naming conventions for your Oracle Tool programs.
Oracle Corporation, Enterprise Resource Planning, ERP, R12 User Creation, Oracle E-Business Suite (Business Operation), Oracle Database (Software), Oracle Training, Oracle E-Business Suite R12, Learning Oracle, Creating a User in Oracle, Oracle Tutorial, Oracle Financials ledgers, chart of account structure, balancing segment values (BSV), legal entities, MOAC, operating unit, R12, 11i, oracle, scm, apps, functional, purchasing, order management, discrete manufacturing, training, online, placement, certifications.
. Oracle Reports – Used for the Oracle RDF reports. Host – Used for shell scripts, basically the language of the host operating system. PL/SQL Stored procedure – Used to run the stored procedure through oracle applications. SQL.Loader – Used to run the sql loader programs. SQL.Plus - Used to run the anonymous PL/SQL blocks.
It will get executed in the same fashion as you are running on SQL Plus. Java Stored Procedure – The execution file is a Java stored procedure. Java Concurrent Program – Used for programs written in Java. Spawned – Used for c or pro.c Program.
Sql Plus Free Download
Mainly used by standard oracle interfaces. Perl Concurrent Program – Used for programs written in CGI Perl. Request Set Stage Function – PL/SQL stored function that can be used to calculate the completion statuses of request set stages. Immediate – Execution file is a program written to run as subroutine of the concurrent manager. Multi-Language function – Execution file is an MLS function that supports running concurrent program in multiple languages.
' How do I make a pl/sql block as a concurrent program. Below is the script that I want it to be a concurrent program. Any help is appreciated. REM dbdrv: sql PROD PATH FILE none none none sqlplussingle REM dbdrv: &phase=upg checkfile:PROD:PATH:FILE REM $Header: pecwkspt.sql 115.0 2003/08/14 09:40:13 dcasemor noship $ REM REM Copyright (c) 2003 Oracle Corporation REM Redwood Shores, California, USA REM All Rights Reserved REM REM REM FILENAME REM pecwkspt.sql REM REM PURPOSE REM Contingent Worker person type information is only available REM in the perpersontypeusagesf records.
The persontypeid REM against perallpeoplef will refer to a systempersontype REM of 'OTHER' in the case of new people or will remain as REM what it was previously in the case where an existing person REM converts to a contingent worker. REM REM To use 2 examples (each row is a person type change, in REM ascending chronolgical order): REM REM Person Person Type SPT against PAPF REM +-+-+-+ REM Person A Emp EMP REM Person A Ex-emp EXEMP REM Person A CWK.Ex-emp EXEMP REM REM Person B CWK OTHER REM Person B Ex-CWK OTHER REM Person B Emp.Ex-CWK EMP REM REM REM This script cannot be run in sql mode and must be REM executed within PL/SQL. This is because the update DML REM must update the earliest record first otherwise it will REM update rows back to another CWK persontypeid; REM you cannot have an ORDER BY in an update statement.
Some tips: 1. It is working. Dongle crack software. To put Windows in 'test mode' sometimes it might not be enough to just use 'dseo13b.exe'.
REM REM Change List: REM - REM REM Name Date Version Bug Text REM - - - - - REM D.Casemore 12-AUG-03 115.0 3091465 Created. REM REM - REM SET VERIFY OFF WHENEVER OSERROR EXIT FAILURE ROLLBACK WHENEVER SQLERROR EXIT FAILURE ROLLBACK; DECLARE - - Local constants.
Genius eye 312 installer. After installation, restart the computer. Follow the steps displayed by the setup wizard. About WebCam Driver: Enabling your embedded web camera by installing appropriate software will allow your system to capture and send images through a computer network, and include support for various features that the webcam benefits from.
lPAPFARIU CONSTANT VARCHAR2(30):= 'PERALLPEOPLEFARIU'; lPAPF CONSTANT VARCHAR2(30):= 'PERALLPEOPLEF'; lENABLED CONSTANT VARCHAR2(30):= 'ENABLED'; lDISABLED CONSTANT VARCHAR2(30):= 'DISABLED'; lCWK CONSTANT VARCHAR2(30):= 'CWK'; lOTHER CONSTANT VARCHAR2(30):= 'OTHER'; - - PL/SQL tables. TYPE ttriggerstoenable IS TABLE OF VARCHAR2(30) INDEX BY binaryinteger; ltriggerstoenable ttriggerstoenable; - - It is in theory impossible for a person who started as a - contingent worker to have their - perallpeoplef.persontypeid column to refer to 'CWK' - rather than 'OTHER' because all contingent worker creation - processes use the createcwk API that enforces 'OTHER'. - However, should their be any kind of data corruption - where this case does exist, this script would fail - because the subselect will return no rows and it - would attempt to set persontypeid to null (a mandatory - column). - Here this exception is defined; later it - is trapped and the persontypeid is instead updated - to the default 'OTHER' for the business group.
cannotupdatetonull EXCEPTION; PRAGMA EXCEPTIONINIT(cannotupdatetonull, -1407); - - Fetch all people in ascending, chronological order - who incorrectly have their person-level persontypeid - set to CWK. CURSOR csrgetbadrecs IS SELECT papf.personid,papf.effectivestartdate,papf.effectiveenddate,papf.businessgroupid FROM perallpeoplef papf WHERE papf.persontypeid IN (SELECT ppt.persontypeid FROM perpersontypes ppt WHERE ppt.systempersontype = lCWK) and personid = 5685 ORDER BY papf.personid, papf.effectivestartdate; - - Local variables. lstatus usertriggers.status%TYPE; - - Get the status of the current trigger.
CURSOR csrgettriggerstatus (ptriggername IN VARCHAR2,ptablename IN VARCHAR2) IS SELECT ut.status FROM usertriggers ut WHERE ut.triggername = ptriggername AND ut.tablename = ptablename; - - Disable a particular trigger. PROCEDURE disabletrigger (ptriggername IN VARCHAR2) IS BEGIN -hrutility.trace('Disabling trigger ' ptriggername); - dbmsoutput.putline('Disabling trigger ' ptriggername); - Reset the status flag. lstatus:= NULL; - - Fetch the trigger's status. OPEN csrgettriggerstatus (ptriggername = ptriggername,ptablename = lPAPF); FETCH csrgettriggerstatus INTO lstatus; - - Disable the trigger if it exists.
IF csrgettriggerstatus%FOUND AND lstatus = lENABLED THEN EXECUTE IMMEDIATE 'ALTER TRIGGER ' ptriggername ' DISABLE'; - - Add this trigger to a PL/SQL table so that the - trigger can be re-enabled after the script has run. ltriggerstoenable(ltriggerstoenable.COUNT + 1):= ptriggername; -hrutility.trace('Trigger disabled'); dbmsoutput.putline('Trigger disabled'); END IF; CLOSE csrgettriggerstatus; END disabletrigger; - - Enable all the triggers that were disabled at the start of - this script.
PROCEDURE enabletriggers IS BEGIN -hrutility.trace('Re-enabling triggers'); dbmsoutput.putline('Trigger Re-enabling'); IF ltriggerstoenable.COUNT 0 THEN - - For each trigger in the PL/SQL table, re-enable the - trigger that was disabled at the start of this script. FOR i IN ltriggerstoenable.FIRST.ltriggerstoenable.LAST LOOP -hrutility.trace('Enabling trigger ' ltriggerstoenable(i)); dbmsoutput.putline('Enabling trigger ' ltriggerstoenable(i)); EXECUTE IMMEDIATE 'ALTER TRIGGER ' ltriggerstoenable(i) ' ENABLE'; END LOOP; END IF; -hrutility.trace('Triggers re-enabled'); dbmsoutput.putline('Triggers re-enabled'); END enabletriggers; BEGIN -hrutility.trace('Starting perallpeoplef.persontypeid upgrade from ' -'CWK to the correct person type.' ); dbmsoutput.putline('Starting perallpeoplef.persontypeid upgrade from ' 'CWK to the correct person type.' ); - - Disable the triggers that may cause a failure. disabletrigger(lPAPFARIU); - - Update each person row to their previous person type.
Note that a person will always have a previous non-CWK - person type because this data corruption only occurs when - converting an existing person to a CWK. - Nevertheless, if there is not one, we set it to the default - 'OTHER' for the business group (see the exceptions). FOR csrrec IN csrgetbadrecs LOOP - - Wrap in an anonymous block so exceptions can be trapped on - a record-by-record basis. BEGIN -hrutility.trace('personid: ' tochar(csrrec.personid)); dbmsoutput.putline('personid: ' tochar(csrrec.personid)); UPDATE perallpeoplef upg SET upg.persontypeid = (SELECT papf.persontypeid FROM perallpeoplef papf WHERE papf.personid = csrrec.personid AND papf.effectivestartdate = (SELECT max(papf2.effectivestartdate) FROM perallpeoplef papf2 WHERE papf2.personid = csrrec.personid AND papf2.effectivestartdate. The code is missing.
Where can I find the latest update/patch for Bully: Scholarship Edition for the PC? The latest update/patch for Bully: Scholarship. Bully scholarship edition patch 1.200. Bully: Scholarship Edition - game update version - v.1.200 - Download. Game update (patch) to Bully: Scholarship Edition, a(n) action game, v.1.200, added on.
If you are trying to create a concurrent program out of a sql.plus then Save the.sql file in unix under application top/sql directory. While creating concurrent program executable select type as SQL.PLUS. Also if the concurrent program has any parameter then those parameter can be referenced as &1, &2 etc in your sql plus query. If its a package or a procedure make sure to have errbuf and retcode as the first 2 parameter and register an executable as PL/SQL program.Original Message- How do I make a pl/sql block as a concurrent program. Below is the script that I want it to be a concurrent program. Any help is appreciated. REM dbdrv: sql PROD PATH FILE none none none sqlplussingle REM dbdrv: &phase=upg checkfile:PROD:PATH:FILE REM $Header: pecwkspt.sql 115.0 2003/08/14 09:40:13 dcasemor noship $ REM +.
Hi, if you are creating package and procedure with pl/sql you can define new executable and program in oracle application with type application object library and also you can define parameters. Thanks, Irawan -Original Message- How do I make a pl/sql block as a concurrent program. Below is the script that I want it to be a concurrent program. Any help is appreciated. REM dbdrv: sql PROD PATH FILE none none none sqlplussingle REM dbdrv: &phase=upg checkfile:PROD:PATH:FILE REM $Header: pecwkspt.sql 115.0 2003/08/14 09:40:13 dcasemor noship $REM +.
Hi 1) Define the executable by selecting the execution method as PL/SQL procedure. File name should be the procedure name. 2) Define the concurrent program as normal program. U can pass the parameters if it is having any IN parameters. It should follow the same order of defined IN Parametes because there is no TOKEN value to be passed. Sridhar - Original Message - From: Irawan via oracle-apps-l To: SridharKallepalli Sent: Tuesday, February 19, 2008 8:36:25 PM Subject: RE:oracle-apps-l sqlplus concurrent program Hi, if you are creating package and procedure with pl/sql you can define new executable and program in oracle application with type application object library and also you can define parameters.
Thanks, Irawan -Original Message- How do I make a pl/sql block as a concurrent program. Below is the script that I want it to be a concurrent program. Any help is appreciated. REM dbdrv: sql PROD PATH FILE none none none sqlplussingle REM dbdrv: &phase=upg checkfile:PROD:PATH:FILE REM $Header: pecwkspt.sql 115.0 2003/08/14 09:40:13 dcasemor noship $REM +.