How Can i get PLSQL Procedure out values in Shell Script?

Question

Hi,
I need to use PLSQL Procedure out values in shell script by using that parameter i need to check and call the other procedure. Please can you guide me how can i?
#!/bin/ksh
# Function to call validation program
SQL_PKG_CALL()
echo "Inside SQL_PKG_CALL for $file"
sqlplus -s /nolog << EOF
     whenever sqlerror exit failure
     connect ${APPS_LOGIN}
     variable exit_value NUMBER
     set serveroutput on size 100000
     DECLARE
          l_errbuf VARCHAR2(10000) := NULL; l_retcode NUMBER := NULL;lv_test VARCHAR2(4000) := NULL;
     BEGIN
          fnd_global.apps_initialize ( USER_ID => ${USER_ID}, RESP_ID => ${RESP_ID}, RESP_APPL_ID => ${RESP_APPL_ID}
                         , SECURITY_GROUP_ID => ${SECURITY_GROUP_ID}
          #Calling PLSQL procedure for create and attache document
          XXAFPEEP_SO_DOC_ATTACH_INT.DOCUMENT_ATTACH (p_errbuf => l_errbuf, p_retcode => :RETMSG, p_fileName => $file
                                   , p_debug => 'Y', p_rettest => lv_test);
          # to print the procedure return values
          DBMS_OUT.PUT_LINE('Return Message: '|| lv_test);
          #${RETCODE}=l_retcode;
          print :RETMSG;
     END;
EXIT 0
EOF
# Program starts here
echo "+---------------------------------------------------------------------------+"
echo "Program Start"
APPS_LOGIN=${1} # Apps Login
USER_ID=${2} # User ID
RESP_ID=${5} # Responsiblity ID
RESP_APPL_ID=${6} # Responsiblity Application ID
SECURITY_GROUP_ID=${7} # Security Group ID
DIRECTORY_PATH=${8} # Directory --Attached file locations
DIRECTORY_NAME=${9} # Directory Name for plsql
echo "User ID : $USER_ID"
echo "Responsibility ID : $RESP_ID"
echo "Responsibilith Application ID : $RESP_APPL_ID"
echo "Security Goup ID : $SECURITY_GROUP_ID"
echo "Directory Path : $DIRECTORY_PATH"
echo "Direcotry Name : $DIRECTORY_NAME"
echo
#files direcotry
cd $DIRECTORY_PATH
echo Present Working Directory: `pwd`
echo
#for all file names
ALL_FILES=`ls *.pdf`
for file in $ALL_FILES
do
     if [ -f $file ]
     then
          #log "Processing $file" # future
          echo Processing: $file
          # Calling the PL/SQL Program
          SQL_PKG_CALL;
          #echo "Retcode : $RETCODE"
          echo "RetMessage : $RETMSG"
     else
          log "Skipped $file: invalid file"
          echo "Skipping current file $file: not a valid file."
     fi
done
Thanks
Sudheer

Answer 1

Saubhik's provided the solution, but just for fun:
Test procedure:
create or replace procedure get_ename
   ( p_empno in emp.empno%type
   , p_ename_out out emp.ename%type )
is
begin
   select ename into p_ename_out
   from   emp
   where  empno = p_empno;
end get_ename;Test data:
SQL> select empno, ename from emp order by 1;
EMPNO ENAME
7369 SMITH
7499 ALLEN
7521 WARD
7566 JONES
7654 MARTIN
7698 BLAKE
7782 CLARK
7788 SCOTT
7839 KING
7844 TURNER
7876 ADAMS
7900 JAMES
7902 FORD
7934 MILLER
14 rows selectedTest call from SQL*Plus to show it working:
SQL> declare
  2     v_ename emp.ename%type;
  3  begin
  4     get_ename(7844,v_ename);
  5     dbms_output.put_line(v_ename);
  6  end;
  7  /
TURNER
PL/SQL procedure successfully completed.Demo shellscript (borrowing the function idea from Saubhik):
#!/bin/ksh
empno=${1:-NULL}
exec_sql() {
    sqlplus -s william/w@//vm.starbase.local:1521/eleven <<END_SQL
    spool get_out_value.sh.log
    set serverout on size 2000 feedback off
    declare
       v_name emp.ename%type;
    begin
       get_ename(${empno},v_name);        
       dbms_output.put_line('# ' || v_name);
    end;
    spool off
    exit
END_SQL
ename=$(exec_sql ${empno} | awk '/^# / {print $2}')
print Employee ${empno} = ${ename}Demo:
/Users/williamr: get_out_value.sh 7844
Employee 7844 = TURNER
/Users/williamr: get_out_value.sh    
Employee NULL =Note this substitutes the word NULL if no empno is passed, and it ignores error output or anything else by only looking for lines beginning '# ' and then taking the following word. Error messages will appear in the logfile. (In this example it probably doesn't need the NULL substitution because a missing parameter would cause a syntax error which the script will handle anyway, but it could be useful in more complex examples.)
For a production script you should probably use an OS authenticated account so you don't have to deal with password strings.