Dynamic SQL

Dyanmic SQL:

Dynamic SQL is a programming methodology for generating and running SQL statements at run time. It is useful when writing general-purpose and flexible programs like ad hoc query systems, when writing programs that must run database definition language (DDL) statements, or when you do not know at compilation time the full text of a SQL statement or the number or data types of its input and output variables.
PL/SQL provides two ways to write dynamic SQL:

  • Native dynamic SQL, a PL/SQL language (that is, native) feature for building and running dynamic SQL statements
  • DBMS_SQL package, an API for building, running, and describing dynamic SQL statements
Native dynamic SQL code is easier to read and write than equivalent code that uses the DBMS_SQL package, and runs noticeably faster (especially when it can be optimized by the compiler). However, to write native dynamic SQL code, you must know at compile time the number and data types of the input and output variables of the dynamic SQL statement. If you do not know this information at compile time, you must use the DBMS_SQL package.



You cannot execute DDL statements, such as CREATE TABLE or DROP PROCEDURE, natively in a PL/SQL block. You can, however, execute DDL statements through several different mechanisms:
  • EXECUTE IMMEDIATE
  • DBMS_SQL.PARSE and DBMS_SQL.EXECUTE
  • DBMS_UTILITY.EXEC_DDL_STATEMENT

Comments

Post a Comment

Popular posts from this blog

Queries For Oracle Interface Errors Records.

Below are the queries to get the error records information while processing interface data. AP Invoices:   SELECT    airl.last_update_date process_date,    HU.NAME,   nvl(ail.invoice_line_id,aii.invoice_id) process_id,   'AP' module,   'Import AP Invoice' interface_name,   aii.source source,   NVL(SUBSTR( ail.dist_code_concatenated,1,instr(ail.dist_code_concatenated,'.',1,1)-1),'ALL') company,   'ERROR' status,   ail.line_type_lookup_code ,   airl.parent_table ,   ail.description ,   NVL(ail.distribution_set_name,dist_code_concatenated) ,   pvsa.vendor_site_code ,   listagg(NVL(airl.reject_lookup_code,'AP_INV_ERROR') ,';') within group (order by NVL(airl.reject_lookup_code,'AP_INV_ERROR')) error_code,   listagg(flv.meaning,';')  within group (order by NVL(flv.meaning,'AP_INV_ERROR'))error_summary,   NULL error_details,   pv.vendor_name ,   pv.segment1 ,   aii.invoice_amount,   aii.i
Read more

Customising PO Output For Communication Report in Oracle Purchasing

Image
PO Print PDF Report: Oracle EBS provided  a standard functionality to print the PO report directly from the PO form itself by clicking tools menu and view PDF option. Once we select that option output will be rendered in PDF format in the browser instantly. Internally it will run the concurrent program 'PO Output For Communication'. This concurrent program is of JAVA type which will uses the seeded package  'PO_COMMUNICATION_PVT'  for generating the XML data and later this XML data will be processed and formatted by using the XSL template of data definition 'Standard Purchase Order Data Source' in case of standard PO's. Oracle by default will provide one standard BI publisher template for this. In case if we want to have custom layout for this report we can build a new template for the same data definition and this template has to be used while doing the setup for PO Document types. Creating Custom Template and Setup this for PO Document type: To c
Read more

Oracle APPS Useful Queries

                       ACCOUNT PAYABLES Payable Open Interface Rejection:   SELECT ail.* FROM AP_INVOICES_INTERFACE ai ,   ap_invoice_lines_interface ail ,   ap_interface_rejections AIR WHERE ai.GROUP_ID='EO_AUG-13_010813_443' AND ai.status    ='REJECTED' AND ai.invoice_id=ail.invoice_id   --and ail.dist_code_concatenated='66810-00-999-00000000-00000000-00000-FI100' AND air.parent_id = DECODE(air.parent_table,'AP_INVOICES_INTERFACE',AI.INVOICE_ID,'AP_INVOICE_LINES_INTERFACE',ail.invoice_line_id,NULL) ORDER BY 2; AP Invoices Query: /*+INDEX (AP_INVOICES_ALL [XXDG_TEST]) */ SELECT  apia.invoice_id,        alc.displayed_field "Invoice Type",        apia.invoice_num "Invoice Number",        apia.invoice_date "Invoice Date",        apia.gl_date   "Invoice GL Date",        nvl(apia.VOUCHER_NUM,doc_sequence_value)"Voucher Number",        apia.description inv_Description,  
Read more