Oracle PLSQL Wrapper Utility

You can wrap the PL/SQL source text for any of these stored PL/SQL units, thereby preventing anyone from displaying that text with the static data dictionary views *_SOURCE:

a. Package specification
b. Package body
c. Type specification
d. Type body
e. Function
f. Procedure

A file containing wrapped PL/SQL source text is called a wrapped file. A wrapped file can be moved, backed up, or processed by SQL*Plus or the Import and Export utilities.

To produce a wrapped file, use either the PL/SQL Wrapper utility or a DBMS_DDL subprogram. The PL/SQL Wrapper utility wraps the source text of every wrappable PL/SQL unit created by a specified SQL file.

PL/SQL Wrapper utility detect tokenization errors (for example, runaway strings), but not syntax or semantic errors (for example, nonexistent tables or views).

PL/SQL Source Text Wrapping Guidelines

Wrap only the body of a package or type, not the specification. Leaving the specification unwrapped allows other developers to see the information needed to use the package or type. Wrapping the body prevents them from seeing the package or type implementation.

Wrap files only after you have finished editing them.

You cannot edit wrapped files. If a wrapped file needs changes, you must edit the original unwrapped file and then wrap it.

Before distributing a wrapped file, view it in a text editor and ensure that all important parts are wrapped.

PL/SQL Source Text Wrapping with PL/SQL Wrapper Utility

The PL/SQL Wrapper utility cannot connect to Oracle Database. To run the PL/SQL Wrapper utility, enter this command at the operating system prompt (with no spaces around the equal signs):

wrap iname=input_file [ oname=output_file ]

input_file is the name of an existing file that contains any combination of SQL statements. output_file is the name of the file that the PL/SQL Wrapper utility creates—the wrapped file.

The default file extension for input_file is sql. The default name of output_file is input_file.plb. Therefore, these commands are equivalent:

wrap iname=/mydir/myfile

wrap iname=/mydir/myfile.sql oname=/mydir/myfile.plb


PL/SQL Wrapper: Release 10.1.0.5.0- Production is shipped with Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production

Comments

Post a Comment

Popular posts from this blog

Query to get FSG report details with row/column set

Below query is to fetch FSG report titles, names, and description along with will give a view to list of row sets and column sets associated with the report. -- FSG REPORTS -- SELECT fst.id_flex_structure_name , R.NAME , R.report_title , R.DESCRIPTION , R.column_set "COLUMN SET" , rw2.structure_id , rw2.DESCRIPTION "COL DESC" , R.row_set "ROW SET" , rw.DESCRIPTION "ROW DESC" , R.report_display_set "DISPLAY SET" , R.content_set "CONTENT SET" , R.row_order "ROW ORDER" , R.rounding_option "RND" , u.user_name , u.DESCRIPTION , R.creation_date FROM rg_reports_v R    , fnd_id_flex_structures_v fst    , fnd_user u    , rg_report_axis_sets_v rw    , rg_report_axis_sets_v rw2 WHERE r.structure_id = fst.id_flex_num AND R.row_set_id     = rw.axis_set_id AND r.column_set_id  = rw2.axis_set_id AND SUBSTR(fst.id_flex_structure_name,1,2) IN ('DC') AND R.created_by     = u.user_id OR...
Read more

Sub Ledger Period Close Exception Report - R12

Image
Sub Ledger period close exception Report is used by finance and accounts department to view list of un-accounted transactions in Accounts receivables before closing GL Period Un-processed transactions will be listed in the report for GL period Report summary shows following details: Against a specific ledger, period, and journal source how many exceptions are there (i.e., unprocessed transactions with count) Detail of transactions which are un-processed will be grouped against journal category and event classes This report helps in resolving exceptions quickly so that exceptions are not left to slow down the period-end close It is automatically submitted by General Ledger when closing a GL period if there are unprocessed accounting events or non-transferred journal entries. 
Read more

Sub Inventory Transfer API.

Image
Sub Inventory transfer is used to move materials from one sub-inventory to another within same organization. This is especially used to 1. Adjust on-hand quantities between sub-inventories 2. Transfer to another sub-inventories for specific business need like additional sales 3. Damages/expiry products can be moved to non-asset sub-inventories to discard it from inventory valuation report and so on., Key elements 1. From sub inventory 2. To sub inventory 3. Organization 4. Inventory item 5. Transact quantity 6. Transact unit of measure 7. Transaction type 8. Transaction action 9. Transact Reference 10. Transact date 11. Lot Number Open Interfaces mtl_transactions_interface - is used to populate sub inventory transfer details mtl_transaction_lots_interface - is used to populate lot details for particular sub inventory transfer Base Tables mtl_material_transactions - is used to get all type of material transactions like sub-inventory transfer, inter-org tra...
Read more