IN) and a string array by reference (i.e. In example 1.3, the declaration passes a string by value (i.e. The declaration syntax for a stored function (on its own, outside package) is: SUBROUTINE CalcPenaltyAmt(string LS_In1, ref string LS_Out2) RPCFUNC ALIAS FOR 'Penalty.P_Calc_Amount' In example 1.2, the declaration passes a string by value (i.e. SUBROUTINE SubRtnName(args) RPCFUNC ALIAS FOR 'PackageName.ProcName' The declaration syntax for a stored procedure inside a package is:

an optional alias clause can be added to allow PowerBuilder to use a different function name from Oracle (see alias format used with package declarations). if the procedure is not in a package and does not take any array parameters, then you can click the procedures button to paste in the procedure declaration directly from the database. SUBROUTINE CalcAmount(string LS_In1, ref string LS_Out2) RPCFUNC In example 1.1, the declaration passes a string by value (i.e. The declaration syntax for a stored procedure (on its own, outside package) is: Once inside the transaction user object, choose 'Declare-Local External Functions' and follow the syntax below. This function/procedure declaration is done in the transaction user object (e.g. How do you call Oracle Stored Procedures and Functions from PowerBuilder?Ĭalling Oracle Stored Procs/Functions from Powerbuilder whenever you want to make a call to an Oracle stored procedure or stored function, a good approach is to first declare it as an external function and then invoke it based on that declaration.ĭeclaring an Oracle Stored Procedure so that PowerBuilder Knows About it

Call stored procedure wysiwyg webuilder