@DynamicComponentDependency

Code that is only included if required set of component(s) also are installed.

Category: usage_control

Example of a PL/SQL method that depends on the PROJ component

@DynamicComponentDependency PROJ
PROCEDURE Refresh_Project_Connection (
   activity_info_tab_          IN OUT Project_Connection_Util_API.Activity_Info_Tab_Type,
   activity_revenue_info_tab_  IN OUT Project_Connection_Util_API.Activity_Revenue_Info_Tab_Type,
   attributes_                 IN OUT Project_Connection_Util_API.Attributes_Type,
   activity_seq_               IN     NUMBER,
   keyref1_                    IN     VARCHAR2,
   keyref2_                    IN     VARCHAR2,
   keyref3_                    IN     VARCHAR2,
   keyref4_                    IN     VARCHAR2,
   keyref5_                    IN     VARCHAR2,
   keyref6_                    IN     VARCHAR2,
   refresh_old_data_           IN     VARCHAR2 DEFAULT 'FALSE' )
IS
   company_                           VARCHAR2(20) := keyref1_;
   voucher_type_                      VARCHAR2(20) := keyref2_;
   ...

The component tests can also be combined freely in several ways, using boolean operators as AND, OR and NOT, together with parenthesis. Some examples:

@DynamicComponentDependency PROJ AND INVENT
PROCEDURE My_New_Dependent_Code (
   ...
IS
   ...

@DynamicComponentDependency ((PROJ OR INVENT OR ORDER) AND SAMIMI)
PROCEDURE My_New_Dependent_Code (
   ...
IS
   ...

This page is generated from IFS Developer Studio at 2021-03-10 14:56.