Hints on methods¶

Method not declared in package specification¶

Editor provides errors if the method specification is missing for public/protected/private methods.

Actions Available:

Add method specification
Add an IgnoreMissingMethodDef.

Generated method implementation has changed¶

Editor provides a warning if a method implementation that was generated, has changed.

Actions Available:

Diff with generated code
Replace from generated code
Add an IgnoreGeneratedMethod.

Missing call to General_SYS.Init_Method¶

Editor provides a warning if a method declared in the specification do not have a call to General_SYS.Init_Method() as the first line of its implementation. Some methods like Init are excepted from this check

Actions Available:

Add method call to General_SYS.Init_Method.
Add an IgnoreMissingSysinit.

Third parameter to General_Sys.Init_Method call must be the method name¶

Editor provides an error if the third parameter of the General_SYS.Init_Method() is not same as the method name.

Example of Incorrect Code:

PROCEDURE Exist (  
   formula_id_ IN VARCHAR2,  
   formula_item_id_ IN NUMBER )   
IS   
BEGIN   
   General_SYS.Init_Method(lu_name_, '&PKG', 'Exis', TRUE);

Example of Correct Code:

PROCEDURE Exist (  
   formula_id_ IN VARCHAR2,  
   formula_item_id_ IN NUMBER )   
IS   
BEGIN   
   General_SYS.Init_Method(lu_name_, '&PKG', 'Exist', TRUE);

Actions Available:

Correct the parameter
Add an IgnoreWrongInitParam.

Function/Procedure name is missing in the END statement¶

Editor provides a warning if the method name is missing at the end of the method.

Example of Incorrect Code:

PROCEDURE Prepare_Insert___ (  
   attr_ IN OUT VARCHAR2 )  
IS  
BEGIN  
   Client_SYS.Clear_Attr(attr_);  
END;

Example of Correct Code:

PROCEDURE Prepare_Insert___ (  
   attr_ IN OUT VARCHAR2 )  
IS  
BEGIN  
   Client_SYS.Clear_Attr(attr_);  
END Prepare_Insert___;

Actions Available:

Add the function/procedure name.
Add an IgnoreMissingEndName.

Function/Procedure name is wrong in the END statement¶

Editor provides an error if the method name is not correct at the end of the method.

Example of Incorrect Code:

PROCEDURE Prepare_Insert___ (  
   attr_ IN OUT VARCHAR2 )  
IS  
BEGIN  
   Client_SYS.Clear_Attr(attr_);  
END Prepare_Insert;

Example of Correct Code:

PROCEDURE Prepare_Insert___ (  
   attr_ IN OUT VARCHAR2 )  
IS  
BEGIN  
   Client_SYS.Clear_Attr(attr_);  
END Prepare_Insert___;

Actions Available:

Change the function/procedure end name.
Add an IgnoreWrongEndName.

OUT/ IN OUT parameters should be avoided in Functions¶

Editor provides a warning if a function has OUT/IN OUT parameters.

Example of Incorrect Code:

FUNCTION Check_Exist___ (  
    formula_id_ IN OUT VARCHAR2,  
    formula_item_id_ IN NUMBER ) RETURN BOOLEAN

Example of Correct Code:

�FUNCTION Check_Exist___ (  
     formula_id_ IN VARCHAR2,  
     formula_item_id_ IN NUMBER ) RETURN BOOLEAN

Actions Available:

Add an IgnoreWrongFunctionParam marker.

Parameter order is incorrect. It should be OUT, IN OUT or IN, DEFAULT¶

Editor provides a warning if the parameter order is incorrect. Parameter order should be OUT, IN OUT or IN, DEFAULT.

Example of Incorrect Code:

PROCEDURE New_From_Source6___ (  
   order_no_ IN OUT NOCOPY VARCHAR2,  
   start_date_ IN DATE,  
   eng_chg_level_ IN VARCHAR2 DEFAULT NULL,  
   owning_customer_no_ IN VARCHAR2 )

Example of Correct Code:

�PROCEDURE New_From_Source6___ (  
    order_no_ IN OUT NOCOPY VARCHAR2,  
    start_date_ IN DATE,  
    owning_customer_no_ IN VARCHAR2,  
    eng_chg_level_ IN VARCHAR2 DEFAULT NULL )

Actions Available:

Add an IgnoreWrongParamOrder marker.