DBA Data[Home] [Help]

APPS.PAYWSDYG_PKG dependencies on STANDARD

Line 69: -- | so that it is in the standard format for Dynamically |

65: -- | must not contain the CREATE TRIGGER clause (or the CREATE |
66: -- | statement will raise an exception since this procedure adds |
67: -- | that code itself). The trigger name |
68: -- | should have been obtained via a call to "get_trigger_name" |
69: -- | so that it is in the standard format for Dynamically |
70: -- | Generated triggers, but that isn't vaildated here. |
71: -- | PARAMETERS : p_trigger - Name of the trigger to create |
72: -- | p_table - Table to add the trigger to |
73: -- | p_action - Triggering action, I U or D for Insert Update or |

Line 77: -- | RAISES : Standard - Any errors encountered by the trigger creation DDL|

73: -- | p_action - Triggering action, I U or D for Insert Update or |
74: -- | Delete respectively |
75: -- | p_sql - PL/SQL block to use for the trigger body |
76: -- | RETURNS : None |
77: -- | RAISES : Standard - Any errors encountered by the trigger creation DDL|
78: -- +---------------------------------------------------------------------------+
79: PROCEDURE create_trigger(
80: p_trigger IN VARCHAR2,
81: p_table IN VARCHAR2,

Line 104: -- | DESCRIPTION: Enables or disables the specified trigger. Uses the standard |

100: ) RETURN VARCHAR2;
101: --
102: -- +---------------------------------------------------------------------------+
103: -- | NAME : enable_trigger |
104: -- | DESCRIPTION: Enables or disables the specified trigger. Uses the standard |
105: -- | DDL 'ALTER TRIGGER ... ENABLE/DISABLE' command (executed |
106: -- | using the AOL do_ddl procedure). Any trigger can be enabled |
107: -- | or disabled, if the user has correct permissions, not just |
108: -- | those generated dynamically. |

Line 112: -- | RAISES : Standard - Any errors encountered by the ALTER TRIGGER |

108: -- | those generated dynamically. |
109: -- | PARAMETERS : p_trigger - Trigger name |
110: -- | p_enabled - TRUE to enable the trigger, FALSE to disable |
111: -- | RETURNS : None |
112: -- | RAISES : Standard - Any errors encountered by the ALTER TRIGGER |
113: -- | statement DDL |
114: -- +---------------------------------------------------------------------------+
115: PROCEDURE enable_trigger(p_trigger IN VARCHAR2,p_enabled IN BOOLEAN);
116: --

Line 189: -- | RAISES : Standard - Anything that is raised by modules it calls, e.g. |

185: -- | initialisations or C for components |
186: -- | p_comp_id - The specific component (or initialisation) to |
187: -- | process, defaults to NULL for all components |
188: -- | RETURNS : None |
189: -- | RAISES : Standard - Anything that is raised by modules it calls, e.g. |
190: -- | custom errors raised by map_parameter_list. |
191: -- +---------------------------------------------------------------------------+
192: PROCEDURE automap_parameters(
193: p_id IN NUMBER,

Line 234: -- | RAISES : Standard - May raise errors if the data in the CLOB will not |

230: -- | can hold something like 2Gb. |
231: -- | PARAMETERS : return - The CLOB converted to a VARCHAR2 |
232: -- | p_clob - The CLOB to be converted |
233: -- | RETURNS : The CLOB converted to a VARCHAR2 |
234: -- | RAISES : Standard - May raise errors if the data in the CLOB will not |
235: -- | fit into the VARCHAR2. Should only happen if data |
236: -- | has been populated other than through the front |
237: -- | end Form. The Form will prevent more than 32Kb |
238: -- | being entered by the user. |

Line 271: -- | standard format __DYG where; is |

267: -- | NAME : compile_package |
268: -- | DESCRIPTION: Compile the supporting package for the specified event using |
269: -- | the AOL create_package procedure to ensure that it is created|
270: -- | in the 'proper' way. The package is named according to the |
271: -- | standard format __DYG where; is |
272: -- | the name of the table that the owning event's trigger will be|
273: -- | created against, with underscores removed and truncated so |
274: -- | that the package name does not exceed 30 characters and |
275: -- | is the primary key of the owning event. |

Line 431: -- | RAISES : Standard - Any Database (e.g. constraint) errors raised by |

427: -- | objects like packages and triggers. Doesn't delete the |
428: -- | actual event definition |
429: -- | PARAMETERS : p_id - The primary key of the event |
430: -- | RETURNS : None |
431: -- | RAISES : Standard - Any Database (e.g. constraint) errors raised by |
432: -- | the RDBMS. |
433: -- +---------------------------------------------------------------------------+
434: PROCEDURE delete_event_children(p_id IN NUMBER);
435: --

Line 442: -- | RAISES : Standard - Any Database (e.g. constraint) errors raised by |

438: -- | DESCRIPTION: Deletes the children of the specified initialisation (i.e. |
439: -- | the parameter mappings that the initialisation uses) |
440: -- | PARAMETERS : p_id - The initialisation primary key |
441: -- | RETURNS : None |
442: -- | RAISES : Standard - Any Database (e.g. constraint) errors raised by |
443: -- | the RDBMS. |
444: -- +---------------------------------------------------------------------------+
445: PROCEDURE delete_initialisation_children(p_id IN NUMBER);
446: --

Line 453: -- | RAISES : Standard - Any Database (e.g. constraint) errors raised by |

449: -- | DESCRIPTION: Deletes the children of the specified component (i.e. the |
450: -- | parameter mappings that the component uses) |
451: -- | PARAMETERS : p_id - The component primary key |
452: -- | RETURNS : None |
453: -- | RAISES : Standard - Any Database (e.g. constraint) errors raised by |
454: -- | the RDBMS. |
455: -- +---------------------------------------------------------------------------+
456: PROCEDURE delete_component_children(p_id IN NUMBER);
457:

Line 464: -- | RAISES : Standard - Any Database (e.g. constraint) errors raised by |

460: -- | DESCRIPTION: Deletes an individual parameter given its ID. |
461: -- | used by table event updates form where user delets individual|
462: -- | PARAMETERS : p_id - The component primary key |
463: -- | RETURNS : None |
464: -- | RAISES : Standard - Any Database (e.g. constraint) errors raised by |
465: -- | the RDBMS. |
466: -- +---------------------------------------------------------------------------+
467: PROCEDURE delete_parameters_directly(p_param_id IN NUMBER);
468:

Line 521: -- | a table in a standard format, so future code generation can |

517: --
518: -- +---------------------------------------------------------------------------+
519: -- | NAME : g_param_rec_type |
520: -- | DESCRIPTION: Useful to store the entire set of parameters associated with |
521: -- | a table in a standard format, so future code generation can |
522: -- | simply loop through this table. |
523: -- +---------------------------------------------------------------------------+
524: TYPE g_param_rec_type is RECORD
525: (local_form pay_trigger_parameters.parameter_name%type,

Line 540: -- | representing each dyt, and also three standard interfaces for the API|

536: -- | NAME : gen_dyt_pkg_full_code |
537: -- | DESCRIPTION: This is the main entry point for generating the dynamic code |
538: -- | that represents ALL of the dynamic triggers on a table INTO PACKAGE |
539: -- | format. This dynamic trigger package (dyt_pkg) contains a procedure|
540: -- | representing each dyt, and also three standard interfaces for the API|
541: -- | strategy, (namely after_update, after_insert, after_delete) which |
542: -- | call the former types as required. |
543: -- | |
544: -- | For each dated table, the users preference of dyt storage type is |

Line 555: -- | RAISES : Standard sql errors. |

551: -- | mentioned when preference = T.) |
552: -- | PARAMETERS : p_tab_id - Primary key of the table on which the dyt's exist |
553: -- | p_ok - Boolean indicating overall success of generation |
554: -- | RETURNS : p_ok - The resulting value |
555: -- | RAISES : Standard sql errors. |
556: -- +---------------------------------------------------------------------------+
557: PROCEDURE gen_dyt_pkg_full_code(p_tab_id IN NUMBER,p_ok IN OUT NOCOPY BOOLEAN);
558: --
559: -- +---------------------------------------------------------------------------+

Line 575: -- | RAISES : Standard sql errors. |

571: -- | p_hs - Placeholder for header code |
572: -- | p_bs - Placeholder for body code, passed in and returned |
573: -- | RETURNS : p_hs - The resulting header code |
574: -- | p_bs - The resulting body code |
575: -- | RAISES : Standard sql errors. |
576: -- +---------------------------------------------------------------------------+
577: PROCEDURE gen_dyt_pkg_proc(p_dyt_id IN NUMBER,p_dyt_name IN VARCHAR2
578: ,p_tab_name IN VARCHAR2, p_dyt_act IN VARCHAR2
579: ,p_dyt_desc IN VARCHAR2,p_dyt_info IN VARCHAR2

Line 603: -- | RAISES : Standard sql errors. |

599: -- | RETURNS : p_hs - The resulting header code |
600: -- | p_bs - The resulting body code |
601: -- | p_dyt_pkg_head_tbl - Table 32k header code |
602: -- | p_dyt_pkg_body_tbl - Table 32k body code |
603: -- | RAISES : Standard sql errors. |
604: -- +---------------------------------------------------------------------------+
605: PROCEDURE gen_dyt_pkg_rhi_proc(p_tab_name IN VARCHAR2
606: ,p_dyt_act IN VARCHAR2 ,p_dyt_info IN VARCHAR2
607: ,p_hok_params IN g_params_tab_type

Line 631: -- | RAISES : Standard sql errors. |

627: -- | p_dyt_info - Full version of trig act, eg INSERT |
628: -- | p_dyn_pkg_params - Tbl containing all parameter details |
629: -- | p_tab_dyt_pkg_name - Name of the dyt pkg |
630: -- | RETURNS : none |
631: -- | RAISES : Standard sql errors. |
632: -- +---------------------------------------------------------------------------+
633: PROCEDURE gen_dyt_db_trig(p_dyt_id IN NUMBER,p_dyt_name IN VARCHAR2
634: ,p_tab_name IN VARCHAR2, p_dyt_act IN VARCHAR2
635: ,p_dyt_desc IN VARCHAR2,p_dyt_info IN VARCHAR2