PLS-00306: wrong number or types of arguments

I need a fresh pair of eyes. Here is a function def and a function call. Why is it not working? Thanks
FUNCTION:
PROCEDURE Create_ServiceRequest
( p_api_version               IN NUMBER,
p_init_msg_list          IN VARCHAR2      := FND_API.G_FALSE,
p_commit               IN VARCHAR2      := FND_API.G_FALSE,
x_return_status          OUT NOCOPY VARCHAR2,
x_msg_count               OUT NOCOPY NUMBER,
x_msg_data               OUT NOCOPY VARCHAR2,
p_resp_appl_id          IN NUMBER     := NULL,
p_resp_id               IN NUMBER     := NULL,
p_user_id               IN NUMBER     := NULL,
p_login_id               IN NUMBER     := NULL,
p_org_id               IN NUMBER     := NULL,
p_request_id IN NUMBER := NULL,
p_request_number          IN VARCHAR2     := NULL,
p_service_request_rec IN service_request_rec_type,
p_notes IN notes_table,
p_contacts IN contacts_table,
-- Added for Assignment Manager 11.5.9 change
p_auto_assign IN VARCHAR2 Default 'N',
p_default_contract_sla_ind     IN VARCHAR2 Default 'N',
x_request_id               OUT NOCOPY NUMBER,
x_request_number          OUT NOCOPY VARCHAR2,
x_interaction_id OUT NOCOPY NUMBER,
x_workflow_process_id OUT NOCOPY NUMBER,
-- These 3 parameters are added for Assignment Manager 115.9 changes.
x_individual_owner OUT NOCOPY NUMBER,
x_group_owner OUT NOCOPY NUMBER,
x_individual_type OUT NOCOPY VARCHAR2
FUNCTION CALL THAT DOES NOT WORK:
CS_ServiceRequest_PUB.Create_ServiceRequest(
                              p_api_version      => 2.0
,p_init_msg_list      => Fnd_Api.g_false
,p_commit      => Fnd_Api.g_false
,x_return_status      => x_status
                    ,x_msg_count      => x_msgcount
                    ,x_msg_data      => x_msgdata
                              ,p_resp_appl_id => 0
                              ,p_resp_id => 0
,p_user_id => 0     
                              ,p_login_id => 0
,p_org_id      => v_org_id
,p_request_id           => v_incident_id
,p_request_number           => v_incident_number
,p_service_request_rec => l_service_request_rec
,p_notes      => l_notes
,p_contacts      => l_contacts
,p_auto_assign => 'N'
,p_default_contract_sla_ind => 'N'
);

PROCEDURE Create_ServiceRequest
( p_api_version               IN NUMBER,
p_init_msg_list          IN VARCHAR2      := FND_API.G_FALSE,
p_commit               IN VARCHAR2      := FND_API.G_FALSE,
x_return_status          OUT NOCOPY VARCHAR2,
x_msg_count               OUT NOCOPY NUMBER,
x_msg_data               OUT NOCOPY VARCHAR2,
p_resp_appl_id          IN NUMBER     := NULL,
p_resp_id               IN NUMBER     := NULL,
p_user_id               IN NUMBER     := NULL,
p_login_id               IN NUMBER     := NULL,
p_org_id               IN NUMBER     := NULL,
p_request_id IN NUMBER := NULL,
p_request_number          IN VARCHAR2     := NULL,
p_service_request_rec IN service_request_rec_type,
p_notes IN notes_table,
p_contacts IN contacts_table,
-- Added for Assignment Manager 11.5.9 change
p_auto_assign IN VARCHAR2 Default 'N',
p_default_contract_sla_ind     IN VARCHAR2 Default 'N',
x_request_id               OUT NOCOPY NUMBER,
x_request_number          OUT NOCOPY VARCHAR2,
x_interaction_id OUT NOCOPY NUMBER,
x_workflow_process_id OUT NOCOPY NUMBER,
-- These 3 parameters are added for Assignment Manager 115.9 changes.
x_individual_owner OUT NOCOPY NUMBER,
x_group_owner OUT NOCOPY NUMBER,
x_individual_type OUT NOCOPY VARCHAR2
IS
l_api_version CONSTANT NUMBER := 3.0;
l_api_name CONSTANT VARCHAR2(30) := 'Create_ServiceRequest';
l_api_name_full CONSTANT VARCHAR2(61) := G_PKG_NAME||'.'||l_api_name;
l_return_status VARCHAR2(1);
-- Added for making call to 11.5.10 signature of Create SR public API
l_sr_create_out_rec          sr_create_out_rec_type;
BEGIN
-- Standard start of API savepoint
SAVEPOINT Create_ServiceRequest_PUB;
--BUG 3630159:
--Added to clear message cache in case of API call wrong version.
-- Initialize message list if p_init_msg_list is set to TRUE
IF FND_API.To_Boolean(p_init_msg_list) THEN
FND_MSG_PUB.Initialize;
END IF;
-- Standard call to check for call compatibility
IF NOT FND_API.Compatible_API_Call(l_api_version, p_api_version, l_api_name,
G_PKG_NAME) THEN
-- RAISE FND_API.G_EXC_UNEXPECTED_ERROR; #BUG 3630127
RAISE FND_API.G_EXC_ERROR;
END IF;
-- Initialize API return status to success
l_return_status := FND_API.G_RET_STS_SUCCESS;
CS_ServiceRequest_PUB.Create_ServiceRequest
( p_api_version => 4.0,
p_init_msg_list => p_init_msg_list,
p_commit => p_commit,
x_return_status => l_return_status,
x_msg_count => x_msg_count,
x_msg_data => x_msg_data,
p_resp_appl_id => p_resp_appl_id,
p_resp_id => p_resp_id,
p_user_id => p_user_id,
p_login_id => p_login_id,
p_org_id => p_org_id,
p_request_id => p_request_id,
p_request_number => p_request_number,
p_service_request_rec => p_service_request_rec,
p_notes => p_notes,
p_contacts => p_contacts,
p_auto_assign => p_auto_assign,
p_auto_generate_tasks     => 'N',
x_sr_create_out_rec      => l_sr_create_out_rec,
p_default_contract_sla_ind => p_default_contract_sla_ind,
p_default_coverage_template_id => NULL
x_return_status     := l_return_status;
x_request_id          := l_sr_create_out_rec.request_id;
x_request_number     := l_sr_create_out_rec.request_number;
x_interaction_id     := l_sr_create_out_rec.interaction_id;
x_workflow_process_id     := l_sr_create_out_rec.workflow_process_id;
x_individual_owner     := l_sr_create_out_rec.individual_owner;
x_group_owner          := l_sr_create_out_rec.group_owner;
x_individual_type     := l_sr_create_out_rec.individual_type;
IF (l_return_status = FND_API.G_RET_STS_ERROR) THEN
RAISE FND_API.G_EXC_ERROR;
ELSIF (l_return_status = FND_API.G_RET_STS_UNEXP_ERROR) THEN
RAISE FND_API.G_EXC_UNEXPECTED_ERROR;
END IF;
EXCEPTION
WHEN FND_API.G_EXC_ERROR THEN
ROLLBACK TO Create_ServiceRequest_PUB;
x_return_status := FND_API.G_RET_STS_ERROR;
FND_MSG_PUB.Count_And_Get
( p_count => x_msg_count,
p_data => x_msg_data
WHEN FND_API.G_EXC_UNEXPECTED_ERROR THEN
ROLLBACK TO Create_ServiceRequest_PUB;
x_return_status := FND_API.G_RET_STS_UNEXP_ERROR;
FND_MSG_PUB.Count_And_Get
( p_count => x_msg_count,
p_data => x_msg_data
WHEN OTHERS THEN
ROLLBACK TO Create_ServiceRequest_PUB;
x_return_status := FND_API.G_RET_STS_UNEXP_ERROR;
IF FND_MSG_PUB.Check_Msg_Level(FND_MSG_PUB.G_MSG_LVL_UNEXP_ERROR) THEN
FND_MSG_PUB.Add_Exc_Msg(G_PKG_NAME, l_api_name);
END IF;
FND_MSG_PUB.Count_And_Get
( p_count => x_msg_count,
p_data => x_msg_data
END Create_ServiceRequest;

Similar Messages

  • PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMI

    I am trying to submit the payables open interface import program using BPEL process. BUT I am unable to submit the concurrent program. The invoke function is failing with below message.
    [2010/08/25 17:06:22] Faulted while invoking operation "OFAPOPIIMPORT" on provider "OFAPOPIIMPORT".less
    -<messages>
    -<input>
    -<Invoke_1_OFAPOPIIMPORT_InputVariable>
    -<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="InputParameters">
    -<InputParameters xmlns:db="http://xmlns.oracle.com/pcbpel/adapter/db/APPS/XX_BPEL_FND_REQUEST_SUBMIT_REQ/FND_REQUEST-24SUBMIT_REQUEST/" xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/APPS/XX_BPEL_FND_REQUEST_SUBMIT_REQ/FND_REQUEST-24SUBMIT_REQUEST/">
    <db:APPLICATION>200</db:APPLICATION>
    <db:PROGRAM>APXIIMPT</db:PROGRAM>
    <db:DESCRIPTION>Test</db:DESCRIPTION>
    <db:START_TIME/><db:SUB_REQUEST/>
    <db:OperatingUnit>NYSIF</db:OperatingUnit>
    <db:Source>DBL</db:Source>
    <db:Group/>
    <db:BatchName>TESTRAMBPEL1</db:BatchName>
    <db:HoldName/>
    <db:HoldReason/>
    <db:GLDate/>
    <db:Purge>N</db:Purge>
    <db:TraceSwitch>N</db:TraceSwitch>
    <db:DebugSwitch>N</db:DebugSwitch>
    <db:SummarizeReport>N</db:SummarizeReport>
    <db:CommitBatchSize>1000</db:CommitBatchSize>
    <db:UserID>4842</db:UserID>
    <db:LoginID>1683090</db:LoginID>
    </InputParameters>
    </part>
    </Invoke_1_OFAPOPIIMPORT_InputVariable>
    </input>
    -<fault>
    -<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    -<part name="code">
    <code>6550
    </code>
    </part>
    -<part name="summary">
    <summary>
    file:/C:/product/10.1.3.1/OraBPEL_1/bpel/domains/default/tmp/.bpel_APOPIIMPORT_1.0_91d4c6c1050ed25d005bc0d396a9db24.tmp/OFAPOPIIMPORT.wsdl [ OFAPOPIIMPORT_ptt::OFAPOPIIMPORT(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'OFAPOPIIMPORT' failed due to: Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the APPS.XX_BPEL_FND_REQUEST_SUBMIT_REQ.FND_REQUEST$SUBMIT_REQUEST API. Cause: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    [Caused by: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    ; nested exception is:
         ORABPEL-11811
    Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the APPS.XX_BPEL_FND_REQUEST_SUBMIT_REQ.FND_REQUEST$SUBMIT_REQUEST API. Cause: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    [Caused by: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    Check to ensure that the API is defined in the database and that the parameters match the signature of the API. Contact oracle support if error is not fixable.
    </summary>
    </part>
    -<part name="detail">
    <detail>
    Internal Exception: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    Error Code: 6550
    </detail>
    </part>
    </remoteFault>
    </fault>
    </messages>
    [2010/08/25 17:06:22] "{http://schemas.oracle.com/bpel/extension}remoteFault" has been thrown. More...
    -<remoteFault xmlns="http://schemas.oracle.com/bpel/extension">
    -<part name="code">
    <code>6550
    </code>
    </part>
    -<part name="summary">
    <summary>
    file:/C:/product/10.1.3.1/OraBPEL_1/bpel/domains/default/tmp/.bpel_APOPIIMPORT_1.0_91d4c6c1050ed25d005bc0d396a9db24.tmp/OFAPOPIIMPORT.wsdl [ OFAPOPIIMPORT_ptt::OFAPOPIIMPORT(InputParameters,OutputParameters) ] - WSIF JCA Execute of operation 'OFAPOPIIMPORT' failed due to: Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the APPS.XX_BPEL_FND_REQUEST_SUBMIT_REQ.FND_REQUEST$SUBMIT_REQUEST API. Cause: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    [Caused by: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    ; nested exception is:
         ORABPEL-11811
    Error while trying to prepare and execute an API.
    An error occurred while preparing and executing the APPS.XX_BPEL_FND_REQUEST_SUBMIT_REQ.FND_REQUEST$SUBMIT_REQUEST API. Cause: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    [Caused by: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    Check to ensure that the API is defined in the database and that the parameters match the signature of the API. Contact oracle support if error is not fixable.
    </summary>
    </part>
    -<part name="detail">
    <detail>
    Internal Exception: java.sql.SQLException: ORA-06550: line 1, column 13:
    PLS-00306: wrong number or types of arguments in call to 'FND_REQUEST$SUBMIT_REQUEST'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    Error Code: 6550
    </detail>
    </part>
    </remoteFault>
    I thought I am providing the values for the required parameters. But still I am unable to submit. Could some one help me on fixing this issue?
    Thanks,

    That's probably your problem.
    Look at http://download-west.oracle.com/docs/cd/B31017_01/integrate.1013/b28351/T430238T430241.htm
    Search for "One-time Workaround for Concurrent Programs" in that document.

  • Pl. help debug - PLS-00306: wrong number or types of arguments in call

    Hi,
    I am trying to create a wrapper function to all a procedure in Oracle EBusiness Suite 11i.
    When I compile the following code
    ==========
    CREATE OR REPLACE PROCEDURE gme.KIL_ProcessAlloc IS
    vFileName VARCHAR2(30) := '1006251.csv';
    vLoc VARCHAR2(20) := '/u041/applmgr/opm/opmappl/utllog';
    v_InHandle utl_file.file_type;
    vNewLine VARCHAR2(1000);
    vLineNo PLS_INTEGER;
    c1 PLS_INTEGER;
    c2 PLS_INTEGER;
    c3 PLS_INTEGER;
    c4 PLS_INTEGER;
    c5 PLS_INTEGER;
    c6 PLS_INTEGER;
    c7 PLS_INTEGER;
    c8 PLS_INTEGER;
    c9 PLS_INTEGER;
    c10 PLS_INTEGER;
    c11 PLS_INTEGER;
    c12 PLS_INTEGER;
    c13 PLS_INTEGER;
    c14 PLS_INTEGER;
    c15 PLS_INTEGER;
    c16 PLS_INTEGER;
    c17 PLS_INTEGER;
    c18 PLS_INTEGER;
    c19 PLS_INTEGER;
    c20 PLS_INTEGER;
    c21 PLS_INTEGER;
    c22 PLS_INTEGER;
    c23 PLS_INTEGER;
    c24 PLS_INTEGER;
    c25 PLS_INTEGER;
    c26 PLS_INTEGER;
    c27 PLS_INTEGER;
    c28 PLS_INTEGER;
    c29 PLS_INTEGER;
    c30 PLS_INTEGER;
    c31 PLS_INTEGER;
    c32 PLS_INTEGER;
    c33 PLS_INTEGER;
    c34 PLS_INTEGER;
    TYPE AllocArray IS TABLE OF GME_INVENTORY_TXNS_GTMP%ROWTYPE
    INDEX BY BINARY_INTEGER;
    l_Allocdata AllocArray;
    TYPE MtlDetailArray IS TABLE OF gme_material_details%ROWTYPE
    INDEX BY BINARY_INTEGER;
    l_MtlDetaildata MtlDetailArray;
    TYPE xTranArray IS TABLE OF GME_INVENTORY_TXNS_GTMP%ROWTYPE
    INDEX BY BINARY_INTEGER;
    l_xtrandata xTranArray;
    TYPE defTranArray IS TABLE OF GME_INVENTORY_TXNS_GTMP%ROWTYPE
    INDEX BY BINARY_INTEGER;
    l_deftrandata defTranArray;
    t_messagecount number;
    t_messagelist varchar2(10000);
    t_returnstatus varchar2(1);
    BEGIN
    v_InHandle := utl_file.fopen(vLoc, vFileName, 'r');
    vLineNo := 1;
    LOOP
    BEGIN
    utl_file.get_line(v_InHandle, vNewLine);
    EXCEPTION
    WHEN NO_DATA_FOUND THEN
    EXIT;
    END;
    vNewLine := TRANSLATE(vNewLine, 'A''', 'A');
    c1 := INSTR(vNewLine, ',', 1,1);
    c2 := INSTR(vNewLine, ',', 1,2);
    c3 := INSTR(vNewLine, ',', 1,3);
    c4 := INSTR(vNewLine, ',', 1,4);
    c5 := INSTR(vNewLine, ',', 1,5);
    c6 := INSTR(vNewLine, ',', 1,6);
    c7 := INSTR(vNewLine, ',', 1,7);
    c8 := INSTR(vNewLine, ',', 1,8);
    c9 := INSTR(vNewLine, ',', 1,9);
    c10 := INSTR(vNewLine, ',', 1,10);
    c11 := INSTR(vNewLine, ',', 1,11);
    c12 := INSTR(vNewLine, ',', 1,12);
    c13 := INSTR(vNewLine, ',', 1,13);
    c14 := INSTR(vNewLine, ',', 1,14);
    c15 := INSTR(vNewLine, ',', 1,15);
    c16 := INSTR(vNewLine, ',', 1,16);
    c17 := INSTR(vNewLine, ',', 1,17);
    c18 := INSTR(vNewLine, ',', 1,18);
    c19 := INSTR(vNewLine, ',', 1,19);
    c20 := INSTR(vNewLine, ',', 1,20);
    c21 := INSTR(vNewLine, ',', 1,21);
    c22 := INSTR(vNewLine, ',', 1,22);
    c23 := INSTR(vNewLine, ',', 1,23);
    c24 := INSTR(vNewLine, ',', 1,24);
    c25 := INSTR(vNewLine, ',', 1,25);
    c26 := INSTR(vNewLine, ',', 1,26);
    c27 := INSTR(vNewLine, ',', 1,27);
    c28 := INSTR(vNewLine, ',', 1,28);
    c29 := INSTR(vNewLine, ',', 1,29);
    c30 := INSTR(vNewLine, ',', 1,30);
    c31 := INSTR(vNewLine, ',', 1,31);
    c32 := INSTR(vNewLine, ',', 1,32);
    c33 := INSTR(vNewLine, ',', 1,33);
    c34 := INSTR(vNewLine, ',', 1,34);
    -- l_allocdata(vLineNo).sourceno := SUBSTR(vNewLine,1,c1-1);
    -- l_allocdata(vLineNo).sizeno := SUBSTR(vNewLine,c1+1,c2-c1-1);
    -- l_allocdata(vLineNo).status := SUBSTR(vNewLine,c2+1,c3-c2-1);
    -- l_allocdata(vLineNo).latitude := SUBSTR(vNewLine,c3+1,c4-c3-1);
    -- l_allocdata(vLineNo).longitude := SUBSTR(vNewLine,c4+1,c5-c4-1);
    -- l_allocdata(vLineNo).testfor := SUBSTR(vNewLine,c5+1);
    l_allocdata(vLineNo).trans_id := SUBSTR(vNewLine,1,c1-1);
    l_allocdata(vLineNo).item_id := SUBSTR(vNewLine,c1+1,c2-c1-1);
    l_allocdata(vLineNo).co_code := SUBSTR(vNewLine,c2+1,c3-c2-1);
    l_allocdata(vLineNo).orgn_code := SUBSTR(vNewLine,c3+1,c4-c3-1);
    l_allocdata(vLineNo).whse_code := SUBSTR(vNewLine,c4+1,c5-c4-1);
    l_allocdata(vLineNo).lot_id := SUBSTR(vNewLine,c5+1,c6-c5-1);
    l_allocdata(vLineNo).location := SUBSTR(vNewLine,c6+1,c7-c6-1);
    l_allocdata(vLineNo).doc_id := SUBSTR(vNewLine,c7+1,c8-c7-1);
    l_allocdata(vLineNo).doc_type := SUBSTR(vNewLine,c8+1,c9-c8-1);
    l_allocdata(vLineNo).doc_line := SUBSTR(vNewLine,c9+1,c10-c9-1);
    l_allocdata(vLineNo).line_type := SUBSTR(vNewLine,c10+1,c11-c10-1);
    l_allocdata(vLineNo).reason_code := SUBSTR(vNewLine,c11+1,c12-c11-1);
    l_allocdata(vLineNo).trans_date := SUBSTR(vNewLine,c12+1,c13-c12-1);
    l_allocdata(vLineNo).trans_qty := SUBSTR(vNewLine,c13+1,c14-c13-1);
    l_allocdata(vLineNo).trans_qty2 := SUBSTR(vNewLine,c14+1,c15-c14-1);
    l_allocdata(vLineNo).qc_grade := SUBSTR(vNewLine,c15+1,c16-c15-1);
    l_allocdata(vLineNo).lot_status := SUBSTR(vNewLine,c16+1,c17-c16-1);
    l_allocdata(vLineNo).trans_stat := SUBSTR(vNewLine,c17+1,c18-c17-1);
    l_allocdata(vLineNo).trans_um := SUBSTR(vNewLine,c18+1,c19-c18-1);
    l_allocdata(vLineNo).trans_um2 := SUBSTR(vNewLine,c19+1,c20-c19-1);
    l_allocdata(vLineNo).completed_ind := SUBSTR(vNewLine,c20+1,c21-c20-1);
    l_allocdata(vLineNo).staged_ind := SUBSTR(vNewLine,c21+1,c22-c21-1);
    l_allocdata(vLineNo).gl_posted_ind := SUBSTR(vNewLine,c22+1,c23-c22-1);
    l_allocdata(vLineNo).event_id := SUBSTR(vNewLine,c23+1,c24-c23-1);
    l_allocdata(vLineNo).text_code := SUBSTR(vNewLine,c24+1,c25-c24-1);
    l_allocdata(vLineNo).transaction_no := SUBSTR(vNewLine,c25+1,c26-c25-1);
    l_allocdata(vLineNo).action_code := SUBSTR(vNewLine,c26+1,c27-c26-1);
    l_allocdata(vLineNo).material_detail_id := SUBSTR(vNewLine,c27+1,c28-c27-1);
    l_allocdata(vLineNo).organization_id := SUBSTR(vNewLine,c28+1,c29-c28-1);
    l_allocdata(vLineNo).locator_id := SUBSTR(vNewLine,c29+1,c30-c29-1);
    l_allocdata(vLineNo).subinventory := SUBSTR(vNewLine,c30+1,c31-c30-1);
    l_allocdata(vLineNo).alloc_um := SUBSTR(vNewLine,c31+1,c32-c31-1);
    l_allocdata(vLineNo).alloc_qty := SUBSTR(vNewLine,c32+1,c33-c32-1);
    l_allocdata(vLineNo).def_trans_ind := SUBSTR(vNewLine,c33+1,c34-c33-1);
    vLineNo := vLineNo+1;
    END LOOP;
    utl_file.fclose(v_InHandle);
    FOR i IN 1..vLineNo-1 loop
    GME_API_PUB.insert_line_allocation (
         1,
         100,
         FALSE,
         True,
         l_allocdata(i),
         null,
         null,
         false,
         false,
         false,
         l_MtlDetailData,
         l_xtrandata,
         l_deftrandata,
         t_messagecount,
         t_messagelist,
         t_returnstatus);
    end loop;
         IF (t_returnstatus <> 'S') THEN
    for i IN 1 .. t_messagecount LOOP
    dbms_output.put_line('The text is '||FND_MSG_PUB.get(i,t_messagelist));
    END LOOP;
    END IF;
    -- COMMIT;
    EXCEPTION
    WHEN OTHERS THEN
    RAISE;
    END KIL_ProcessAlloc;
    ===============
    I get this
    Warning: Procedure created with compilation errors.
    SQL> sho err
    Errors for PROCEDURE GME.KIL_PROCESSALLOC:
    LINE/COL ERROR
    145/8 PLS-00306: wrong number or types of arguments in call to
    'INSERT_LINE_ALLOCATION'
    145/8 PL/SQL: Statement ignored
    =================
    The package specs of GME_API_PU is under:
    ===============
    PROCEDURE insert_line_allocation (
    p_api_version IN NUMBER := gme_api_pub.api_version
    ,p_validation_level IN NUMBER := gme_api_pub.max_errors
    ,p_init_msg_list IN BOOLEAN := FALSE
    ,p_commit IN BOOLEAN := FALSE
    ,p_tran_row IN gme_inventory_txns_gtmp%ROWTYPE
    ,p_lot_no      IN     VARCHAR2 DEFAULT NULL
    ,p_sublot_no      IN     VARCHAR2 DEFAULT NULL
    ,p_create_lot     IN BOOLEAN DEFAULT FALSE
    ,p_ignore_shortage     IN BOOLEAN DEFAULT FALSE
    ,p_scale_phantom     IN BOOLEAN DEFAULT FALSE
    ,x_material_detail     OUT gme_material_details%ROWTYPE
    ,x_tran_row     OUT gme_inventory_txns_gtmp%ROWTYPE
    ,x_def_tran_row     OUT gme_inventory_txns_gtmp%ROWTYPE
    ,x_message_count OUT NUMBER
    ,x_message_list OUT VARCHAR2
    ,x_return_status     OUT VARCHAR2);
    GME_API_PUB.insert_line_allocation
    ===========
    What am I doing wrong...why am I getting PLS-00306.
    Can someone help?
    Thank you
    Sundar
    [email protected]

    Hi John,
    Thanks a ton - a nice Christmas gift. Thank you for being a Santa :-).
    I used the same subscript as the one used for in parameter and the procedure compiled without errors.
    A corollary: If (any of the) Out parameter is null (all columns of the row/array), will the array row element still be stored ? May be I cross the bridge when I come to it.
    Merry Christmas.
    Sundar

  • PLS-00306: wrong number or types of arguments in call in a for loop

    Dear all
    I recently put up another post about the same error message but as the message now relates to another part of my programme and, in my mind at least, a different conceptual idea, I thought I should start a new top. If that is not right thing to have done then please let me know. I am working in 10.2.
    I am trying to pass through multiple variables. When I run the code at the end of this question I get an error message:
    PLS-00306: wrong number or types of arguments in call to 'CUR_MAP_LIST'This relates to the line:
    FOR var_map_list IN cur_map_list (par_map_list (n))I think the reason the error message comes up is because par_map_list is a associate array / PL/SQL table and cur_map_list is based on %rowtype. Although I could be wrong. However I am not sure what I should be doing so that I don't get such an error message.
    I was reading through page 623 on Web Development 9i (by Brown; pub. McGrew-Hill) and pages 357-358 of Oracle Web Application Programming for PL/SQL Developers (by Boardman, Caffrey, Morse, Rosenzweig; pub. Prentice Hall), in order to try and write my code. As well as Oracle's Application Developer’s Guide - Fundamentals (Release 2), page 11-6. In particular the Web Development book uses the following:
    create or replace procedure query_department
    (in_dept_no owa_util.ident_arr)
    is
    cursor dept_cursor (nbt_dept_no emp.deptno%TYPE) is
    select empno, ename, mgr, sal, comm
    from scott.emp
    where deptno = nbt_dept_no;
    begin
      for x in 1 .. in_dept_no.count loop
        for dept_rec in dept_cursor(in_dept_no (x)) loop
        end loop;
      end loop;
    end;In that example the cursor selects empno, ename, mgr, sal and comm from emp. So if it is doing that the cursor must be of a VARCHAR2 and NUMBER data type. What I don't understand is the for dept_rec in part. For a start I am not sure where dept_rec comes from? If it is a NUMBER data type, how can the in_dept_no, which is a owa_util.ident_arr associate array / PL/SQL data type work with it. Unfortunately because the example is incomplete and doesn't include procedures relating to the in variables, I am unable to run it and try and learn from what it is doing, so that I can try and relate the concept to my own work.
    My programme is as follows. There may be other errors in the code not relating to this error. If so I hope to find these and resolve them once I understand what I should be doing here:
    --Global variables--
    gvar_mapviewer_host VARCHAR2(56) := 'http://tiger.iso.port.ac.uk:7785/mapviewer/omserver';
    gvar_proc_host VARCHAR2(56) := 'http://tiger.iso.port.ac.uk:7785/www/geg50160';
    gvar_xml_request VARCHAR2(100) :='?xml_request=<?xml version="1.0" standalone="yes"?>';
    --Main calling programming--
    PROCEDURE MAPS AS
    empty owa_util.ident_arr;
    var_xml_theme VARCHAR2(32767);
    BEGIN
    PROCMAPLIST (empty, var_xml_theme);
    END maps;
    --create checkboxes--
    PROCEDURE PROCCHECKLIST
    (par_check_list IN OUT owa_util.ident_arr,
      par_xml_theme OUT VARCHAR2
      AS
       CURSOR cur_map_list IS
        SELECT MT.map_title
               MI.map_id
               OMSN.map_sheet_number_id
               WRMF.web_raster_map_id
         FROM MAP_TITLE MT
              MAP_INFO MI
              MAP_SHEET_NUMBER OMSN,
              WEB_RASTER_MAP_FILE WRMF,
          WHERE MI.map_title_id = MT.map_title_id
          AND   MI.map_id = OMSN.map_id
          AND   WRMF.map_id = MI.map_id
          AND   WRMF.map_sheet_number_id = OMSN.map_sheet_number_id;
        var_map_list cur_map_list%ROWTYPE;
        var_xml_theme VARCHAR2(32767);
    BEGIN
    htp.htmlOpen;
    htp.headOpen;
    htp.headClose;
    htp.bodyOpen;
    htp.print('<FORM METHOD = "post"
                     ACTION = "'||gvar_proc_host||'.mappackage.procdisplay">');
        htp.print('<FIELDSET>
                     <LEGEND> Select the maps you wish to display </LEGEND>');
      FOR n IN 1 .. par_map_list.COUNT
      LOOP
      FOR var_map_list IN cur_map_list (par_map_list (n))
      LOOP
    htp.print('       <UL>
                       <LI>
                        <LABEL FOR = "WRMF'||
                                      var_map_list.web_raster_map_id||'">
                         <INPUT type = "checkbox"
                                id = "WRMFB'||
                                      var_map_list.web_raster_map_id||'"
                                name = "WRMFB'||
                                        var_map_list.web_raster_map_id||'"
                                value = "'||var_map_list.web_raster_map_id||'"
                                />
                                 Map title: '|| var_map_list.map_title||'<BR>
                                 Sheet number: '||var_map_list.map_sheet_number||'');
                        htp.print('</LABEL>
                       </LI>
                      </UL>');
        END LOOP;
      END LOOP;
         htp.print('</FIELDSET>');
         htp.print('<p>
                     <INPUT TYPE = "submit"
                            NAME = "Display&nbspselected&nbspmaps"
                            VALUE = "Display selected maps" />
                      </FORM>');
    htp.bodyClose;
    END PROCCHECKLIST;Thank you for reading. Kind regards
    Tim

    Dear everyone
    I have now resolved the problems I was having with multiple values and checkboxes, thanks to comments in this thread, read large chucks of Oracle PL/SQL Programming by Steve Feuerstein and suddenly realising where I am going wrong in terms of thinking.
    For a start, I when I was dealing with the multiple values, I was trying to get PL/SQL to pass them out. Of course this is done by the action part of the input form. Although I have not done much web coding, I did know about this. However because I was so engrossed in trying to understand how multiple values work, I didn't relate the two ideas. I even mind mapping the problem and still didn't get it.
    I also did not think to change my the action from post command to get, so that I could see what was coming out. However that would not have made too much of a difference because the other problem I had was related to where sub programmes were declared. The function which received the values was privately declared, and not in the package spec. This meant the web browser could not find the function as that can only make use of the programmes declared publicly.
    Once I made these changes, as well as correcting other minor typing mistakes, the values passed through as expected. The only other mistake I made was to include the name option after the submit input type. In my case I did not need to submit the value of that button. The revised code is as follows. In this version I replaced the function with a procedure that simply prints the checkbox values to screen. I have also made the input form action get, instead of post, so that the values can be seen in the web browser address bar:
    create or replace
    PACKAGE MAPSITE AS
    PROCEDURE MAPS;
    PROCEDURE PROCCHECKLIST
    (par_check_list IN OUT OWA_UTIL.IDENT_ARR
    PROCEDURE PROCDISPLAY
    (maplist IN OUT OWA_UTIL.IDENT_ARR);
    END MAPSITE;
    create or replace
    PACKAGE BODY MAPSITE AS
    --Global variables--
    gvar_mapviewer_host VARCHAR2(56) := 'http://tiger.iso.port.ac.uk:7785/mapviewer/omserver';
    gvar_proc_host VARCHAR2(56) := 'http://tiger.iso.port.ac.uk:7785/www/geg50160';
    gvar_xml_request VARCHAR2(100) :='?xml_request=<?xml version="1.0" standalone="yes"?>';
    --Main calling programming--
    PROCEDURE MAPS AS
    empty owa_util.ident_arr;
    BEGIN
    PROCCHECKLIST (empty);
    END MAPS;
    --create checkboxes--
    PROCEDURE PROCCHECKLIST
    (par_check_list IN OUT owa_util.ident_arr
      AS
       CURSOR cur_map_list IS
        SELECT MT.map_title,
               MI.map_id,
               OMSN.map_sheet_number_id,
               WRMF.web_raster_map_id
         FROM MAP_TITLE MT,
              MAP_INFO MI,
              MAP_SHEET_NUMBER OMSN,
              WEB_RASTER_MAP_FILE WRMF
          WHERE MI.map_title_id = MT.map_title_id
          AND   MI.map_id = OMSN.map_id
          AND   WRMF.map_id = MI.map_id
          AND   WRMF.map_sheet_number_id = OMSN.map_sheet_number_id;
    BEGIN
    htp.htmlOpen;
    htp.headOpen;
    htp.headClose;
    htp.bodyOpen;
    htp.print('<FORM METHOD = "post"
                     ACTION = "'||gvar_proc_host||'.mappackage.procdisplay">');
        htp.print('<FIELDSET>
                     <LEGEND> Select the maps you wish to display </LEGEND>');
      FOR var_map_list IN cur_map_list
      LOOP
    htp.print('       <UL>
                       <LI>
                        <LABEL FOR = "WRMF'||
                                      var_map_list.web_raster_map_id||'">
                         <INPUT type = "checkbox"
                                id = "WRMFB'||
                                      var_map_list.web_raster_map_id||'"
                                name = "maplist"
                                CHECKED = "' ||
                                           par_map_list ||'"
                                value = "'||var_map_list.web_raster_map_id||'"
                                />
                                 Map title: '|| var_map_list.map_title||'<BR>
                                 Sheet number: '||var_map_list.map_sheet_number||'');
                        htp.print('</LABEL>
                       </LI>
                      </UL>');
        END LOOP;
         htp.print('</FIELDSET>');
         htp.print('<p>
                     <INPUT TYPE = "submit"
                            VALUE = "Display selected maps" />
                      </FORM>');
    htp.bodyClose;
    END PROCCHECKLIST;
    ---PROCDISPLAY PROCEDURE---
    PROCEDURE PROCDISPLAY (maplist IN OUT owa_util.ident_arr)
    IS
    BEGIN
    FOR n IN 1..maplist.COUNT
    LOOP
      htp.print('Checkbox value i.e. var_map_list.web_raster_map_id is: ' ||maplist(n)||'
    <P>');
    END LOOP;
    END PROCDISPLAY;
    END MAPSITE;Kind regards
    Tim

  • PLS-00306 wrong number or types of arguments in call to 'PUT_LINE'

    Hi Guys,
    I'm practising the plsql workouts,during a anonymous PL/SQL block i got the below error,what the mistake i did ?
    declare
    v1 employee_290512%rowtype;
    cursor c1 is select * from employee_290512;
    begin
    open c1;
    loop
    fetch c1 into v1;
    exit when c1% notfound;
    dbms_output.put_line(v1);
    end loop;
    end;
    {/code}
    And i got the below error
    Error:
    ORA-06550: line 10, column 1:
    PLS-00306: wrong number or types of arguments in call to 'PUT_LINE'
    ORA-06550: line 10, column 1:
    PL/SQL: Statement ignored
    /Error.
    Please help me on this.
    Regards
    Thelak                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

    Hi there,
    i got the same error. kindly check what's wrong with my below coding;
    SQL> SET SERVEROUTPUT ON
    SQL> DECLARE
    2 TYPE Type_Tab_Data IS RECORD
    3 (
    4 ARMZIG_Q2SFX char(3),
    5 somme number(20,2),
    6 ARMZIG_Q2AN8 number(8),
    7 ARMZIG_Q2DOC number(8),
    8 ARMZIG_Q2DCT char(2),
    9 ARMZIG_Q2CO varchar2(15 char)
    10 );
    11 TYPE Tab_Data IS TABLE OF Type_Tab_Data INDEX BY BINARY_INTEGER ;
    12 t_flexnum5 Tab_Data;
    13 v_test pls_integer;
    14 v_text_erreur varchar2(200 char);
    15 BEGIN
    16 SELECT b.ARMZIG_Q2SFX,a.somme,a.ARMZIG_Q2AN8,a.ARMZIG_Q2DOC,a.ARMZIG_Q2DCT,a.ARMZIG_Q2CO
    17 BULK COLLECT INTO t_flexnum5
    18 from
    19 (
    20 SELECT sum(ARMZIG_Q2AAP/100)as somme,ARMZIG_Q2AN8,ARMZIG_Q2DOC,ARMZIG_Q2DCT,ARMZIG_Q2CO
    21 from ARMAST_ZIG_EUR
    22 where ENVZIG_ID = 'E'
    23 group by ARMZIG_Q2AN8,ARMZIG_Q2DOC,ARMZIG_Q2DCT,ARMZIG_Q2CO
    24 ) a, ARMAST_ZIG_EUR b
    25 where a.ARMZIG_Q2AN8 = b.ARMZIG_Q2AN8
    26 and a.ARMZIG_Q2DOC = b.ARMZIG_Q2DOC
    27 and a.ARMZIG_Q2DCT = b.ARMZIG_Q2DCT
    28 and a.ARMZIG_Q2CO = b.ARMZIG_Q2CO
    29 and b.ENVZIG_ID = 'E';
    30
    31 DBMS_OUTPUT.put_line(t_flexnum5);
    32
    33 END;
    34 /
    DBMS_OUTPUT.put_line(t_flexnum5);
    ERROR at line 31:
    ORA-06550: line 31, column 7:
    PLS-00306: wrong number or types of arguments in call to 'PUT_LINE'
    ORA-06550: line 31, column 7:
    PL/SQL: Statement ignored

  • PLS-00306: wrong number or types of arguments in call to 'SHOW'

    Statement : declare
    rc__ number;
    begin
    owa.init_cgi_env(:n__,:nm__,:v__);
    htp.HTBUF_LEN := 255;
    null;
    null;
    wwv_flow.show(p_request=>:p_request,p_instance=>:p_instance,p_flow_id=>:p_flow_id,p_flow_step_id=>:p_flow_step_id,p_arg_names=>:p_arg_names,p_arg_values=>:p_arg_values);
    if (wpg_docload.is_file_download) then
    rc__ := 1;
    wpg_docload.get_download_file(:doc_info);
    null;
    null;
    commit;
    else
    rc__ := 0;
    null;
    null;
    commit;
    owa.get_page(:data__,:ndata__);
    end if;
    :rc__ := rc__;
    end;
    Did someone ever see this ?
    My database throws it every time i use an ajax validation with javascript. The application is NOT affected in any way, means the validation is done correct:
    function validate(pNumber,i){
    var get = new htmldb_Get(null,html_GetElement('pFlowId').value,'APPLICATION_PROCESS=validate_number',100);
    get.add('F500_VALID_NUMBER', pNumber);
    gReturn = get.get();
    html_GetElement('err'+i).innerHTML=gReturn;
    The validate_number Application Process then uses a Stored Function for the "real" validation.
    Thanks for help,
    Jochen

    Jochen,
    yes when you trace modplsql, I can see this and I also have an error I don't know why.
    <360294694 ms>(wppr.c,497) Pl/sql block parsed...
    <360294694 ms>(wpdenv.c,1531) CGI Environment has 31 vars. Max name len 128, Max Value Len 128
    <360294694 ms> PLSQL_GATEWAY(14)=(6)WebDb
    <360294694 ms> GATEWAY_IVERSION(17)=(2)2
    <360294694 ms> SERVER_SOFTWARE(16)=(60)Oracle-Application-Server-10g/10.1.2.2.0 Oracle-HTTP-Server
    <360294694 ms> GATEWAY_INTERFACE(18)=(8)CGI/1.1
    <360294694 ms> SERVER_PORT(12)=(5)7779
    <360294694 ms> SERVER_NAME(12)=(10)net-srv05
    <360294694 ms> REQUEST_METHOD(15)=(5)POST
    <360294694 ms> PATH_INFO(10)=(15)/wwv_flow.show
    <360294694 ms> SCRIPT_NAME(12)=(10)/pls/apex
    <360294694 ms> REMOTE_ADDR(12)=(14)172.20.100.77
    <360294694 ms> SERVER_PROTOCOL(16)=(9)HTTP/1.1
    <360294694 ms> REQUEST_PROTOCOL(17)=(5)HTTP
    <360294694 ms> REMOTE_USER(12)=(17)APEX_PUBLIC_USER
    <360294694 ms> HTTP_CONTENT_LENGTH(20)=(4)149
    <360294694 ms> HTTP_CONTENT_TYPE(18)=(34)application/x-www-form-urlencoded
    <360294694 ms> HTTP_USER_AGENT(16)=(51)Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1)
    <360294694 ms> HTTP_HOST(10)=(11)172.18.2.5
    <360294694 ms> HTTP_ACCEPT(12)=(4)*/*
    <360294694 ms> HTTP_ACCEPT_LANGUAGE(21)=(18)en-us,ar-lb;q=0.5
    <360294694 ms> HTTP_COOKIE(12)=(105)LOGIN_USERNAME_COOKIE=usr1234; WWV_CUSTOM-F_941322186522444_101=725E6950E8DF04E5; oracle.uix=0^^GMT+2:00
    <360294694 ms> HTTP_REFERER(13)=(53)http://172.18.2.5/pls/apex/f?p=101:1:950664913516045
    <360294694 ms> HTTP_ORACLE_ECID(17)=(14)89781163291,1
    <360294694 ms> HTTP_ORACLE_CACHE_VERSION(26)=(7)10.1.2
    <360294694 ms> WEB_AUTHENT_PREFIX(19)=(1)
    <360294694 ms> DAD_NAME(9)=(5)apex
    <360294694 ms> DOC_ACCESS_PATH(16)=(5)docs
    <360294694 ms> DOCUMENT_TABLE(15)=(23)wwv_flow_file_objects$
    <360294694 ms> PATH_ALIAS(11)=(1)
    <360294694 ms> REQUEST_CHARSET(16)=(9)AL32UTF8
    <360294694 ms> REQUEST_IANA_CHARSET(21)=(6)UTF-8
    <360294694 ms> SCRIPT_PREFIX(14)=(5)/pls
    <360294694 ms>StrArrPosBind pos 2 Charset Id : 873
    <360294694 ms>StrArrPosBind pos 3 Charset Id : 873
    <360294694 ms>StrArrPosBind pos 11 Charset Id : 873
    <360294704 ms>Execute: ORA-06550: line 33, column 3:
    PLS-00306: wrong number or types of arguments in call to 'SHOW'
    ORA-06550: line 33, column 3:
    PLS-00306: wrong number or types of arguments in call to 'SHOW'
    ORA-06550: line 33, column 3:
    PL/SQL: Statement ignored
    apex team comments are highly appreciated.
    one more thing I can see for each ajax request I have in my page a hard parse is happening .
    Omar

  • PLS-00306: wrong number or types of arguments in call

    Hi,
    Oracle9i
    created a procedure which will retrieve the records.
    As the procedure is to only retrieve the records so it does not have any IN parameters
    But on executing the procedure gets the below error:
    PLS-00306: wrong number or types of arguments in call to 'GET_PRODUCT_DETAILS'
    I have called the procedure as below:
    =======================
    Declare
    v_cur ...%type;
    BEGIN
    Package_name.GET_PRODUCT_DETAILS(v_cur);
    END;
    Procedure Body
    ==========
    create or replace PROCEDURE GET_PRODUCT_DETAILS( v_cur OUT      Cursor)
    is
    begin
    end;
    /

    Try creating the procedure with the out parameter as sys_refcursor.
    create or replace PROCEDURE GET_PRODUCT_DETAILS( v_cur OUT sys_refCursor)
    And declare the variable in your outer block also as sys_refcursor.
    Declare
    v_cur sys_refcursor;
    BEGIN
    Package_name.GET_PRODUCT_DETAILS(v_cur);
    END;
    Of course this would require that your actual procedure GET_PRODUCT_DETAILS should have a statement like
    " open V_cur for some select statement that you use to retrieve the records".
    You could also create GET_PRODUCT_DETAILS with the same %type decalration which you use in the outer block
    eg
    create or replace PROCEDURE GET_PRODUCT_DETAILS( v_cur OUT x.y%type)
    Declare
    v_cur x.y%type;
    BEGIN
    Package_name.GET_PRODUCT_DETAILS(v_cur);
    END;
    /

  • ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments

    I am getting an error:
    "ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to 'XYZ' ORA-06550: line 1, column 7: PL/SQL: Statement ignored".
    Stored Procedure:
    PROCEDURE XYZ
    (ip_number IN NUMBER,
    op_error_code OUT NUMBER,
    op_error_text OUT VARCHAR2,
    ret_cursor OUT OUT_CURSOR);
    In the procedure I am selecting a details from few tables with respect to the input parameter 'ip_number'.
    VB Code:
    strConnectionString = CONNECTION_STRING
    Set objConnection = Server.CreateObject("ADODB.Connection")
    objConnection.Open strConnectionString
    Set objCommand = Server.CreateObject("ADODB.Command")
    With objCommand
    .ActiveConnection = objConnection
    .CommandType = adCmdStoredProc
    End With
    With objCommand
    .CommandText = "Pkg_1.XYZ"
    .Parameters.Append objCommand.CreateParameter_
    ("ip_ipnumber",adNumeric,adParamInput,8,strIPNumber)
    .Parameters.Append objCommand.CreateParameter_
    ("op_error_code",adNumeric,adParamOutput,10)
    .Parameters.Append objCommand.CreateParameter_
    ("op_error_text",adVarChar,adParamOutput,512)
    Set RS = .Execute()
    End With
    Its working fine with ASP(VB)+ Oracle9i + Windows2000.
    But in ASP(VB) + Oracle 8.1.7 + Windows2000, its giving this error:
    "ORA-06550: line 1, column 7: PLS-00306: wrong number or types of arguments in call to 'XYZ' ORA-06550: line 1, column 7: PL/SQL: Statement ignored".
    Please help.

    Your procedure has 4 parameters 1 in and 3 out parameter
    whereas in your VB code
    Parameters.Append objCommand.CreateParameter_
    ("ip_ipnumber",adNumeric,adParamInput,8,strIPNumber)
    .Parameters.Append objCommand.CreateParameter_
    ("op_error_code",adNumeric,adParamOutput,10)
    .Parameters.Append objCommand.CreateParameter_
    ("op_error_text",adVarChar,adParamOutput,512)
    There are only 3 parameter added where is the 4 th one ?
    With Warm Regards
    SSR

  • Urgent : ADO / OraOLEDB gives random PLS-00306: wrong number or types of arguments

    Hi people,
    Using our production environment of Win2K AS, IIS 5.0 --> Win2K AS, COM+ / ADO, Oracle OLE DB 9i --> Solaris Oracle 9i we have a month of trace logs telling us that some calls to our PL/SQL package methods have the "PLS-00306: wrong number or types of arguments".
    Closer examination of our development systems also revealed these errors that seem to occur fairly randomly. (No recompiles in the database [at least according to USER_OBJECT.TIMESTAMP] and no invalid packages or schema objects).
    One call on a session will succeed (so there aren't any obvious syntax or data range boundary issues) and then with no obvious reason, a second call to the same package method will fail with the error message in the subject.
    Anyone else seen this behaviour and know of a fix?
    Thanks
    Lachlan Pitts

    Hi,
    The temp in the package and the temp in the anonymous block that calls the package are two different data types. They (coincidentally) have exactly the same number and type of elements, just as they (coincidentally) have exactly the same name, but they are still different.
    Since the type is declare in the package head, you can reference it from oputside the package. You don't have to create a similar type in the calling block: just reference the package type, like this:
    declare
      v_out pkg_1.temp;
    begin
        pkg_1.DoSomething( 'a', 'b',  v_out);
        dbms_output.put_line(v_out.val1);
    end;

  • Encounter PLS-00306: wrong number or types of arguments issue

    I came across a issue of PLS-00306: wrong number or types of arguments when I tried to call a stored procedure through Toplink ValueReadquery.
    The full error message is:
    ORA-06550: line 1, column 7:
    PLS-00306: wrong number or types of arguments in call to 'FREEZE_REGISTERS'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    Error Code: 6550
    Call:BEGIN FREEZE_REGISTERS(REGISTRATION_DETAIL_in=>1951, RESERVE_USER_in=>'aUser', RESERVE_BUSINESS_CHANNEL_in=>0, RESERVE_TOKEN_in=>1, RESERVE_DATE_in=>{ts '2007-08-03 10:49:25.39'}, BUSINESS_FUNC_ID_in=>1, UPDATE_COUNT_out=>?); END;
         bind => [=> UPDATE_COUNT_out]
    Query:ValueReadQuery() ..............
    The SP was compiled successfully:
    create or replace
    Procedure FREEZE_REGISTERS
    REGISTRATION_DETAIL_ID_in in NUMBER,
    RESERVE_USER_in in VARCHAR2,
    RESERVE_BUSINESS_CHANNEL_in in NUMBER,
    RESERVE_TOKEN_in in NUMBER,
    RESERVE_DATE_in in TIMESTAMP,
    BUSINESS_FUNC_ID_in in NUMBER,
    UPDATE_COUNT_out OUT NUMBER
    IS
    BEGIN
    UPDATE REGISTER
    SET BUSINESS_FUNC_ID = BUSINESS_FUNC_ID_in,
    RESERVE_BUSINESS_CHANNEL = RESERVE_BUSINESS_CHANNEL_in,
    RESERVE_USER = RESERVE_USER_in,
    VERSION_NO = (VERSION_NO + 1),
    RESERVE_DATE = RESERVE_DATE_in,
    RESERVE_TOKEN = RESERVE_TOKEN_in
    WHERE
    GEOGRAPHIC_ID in
    (SELECT GEOGRAPHIC_ID
    FROM LEGAL_INT_TRANS
    WHERE REGISTRATION_DETAIL_ID = REGISTRATION_DETAIL_ID_in);
    --Assign the number of rows returned to UPDATE_COUNT_out
    UPDATE_COUNT_out := SQL%ROWCOUNT;
    EXCEPTION
    WHEN OTHERS THEN
    raise_application_error(-20001,'An error was encountered - '||SQLCODE||' -ERROR- '||SQLERRM);
    END;
    However, when I tried to call it in the toplink, I always got that error message. I'd compared the dataType for input values and they are compatible with the arguments defined in the SP.
    I have no any clue for this problem. Please help.

    How are you set the parameters/adding arguments to the ValueReadQuery, can you post the code used to create and execute the query?
    Regards,
    Chris

  • Strange PLS-00306: wrong number or types of arguments

    We have the code in production and in the test. the dbs, the servers are setup the same. And the codes on two are the same (verified).
    Now all a sudden the code on production failing sine yesterday afternoon:
    BEGIN REQUEST_API.DBSS_process_FUDS; END;
    ERROR at line 1:
    ORA-06550: line 1, column 93:
    PLS-00306: wrong number or types of arguments in call to 'PROCESS_FUDS'
    ORA-06550: line 1, column 93:
    PL/SQL: Statement ignored
    ORA-06512: at "SYS.DBMS_JOB", line 82
    ORA-06512: at "SYS.DBMS_JOB", line 140
    ORA-06512: at "ER.REQUEST_API", line 1190
    ORA-06512: at line 1
    Just with the test's , it still runs OK.
    Any idea? how can we look?
    Thanks a lot!

    BluShadow wrote:
    Check the call to PROCESS_FUDS and check the definition of PROCESS_FUDS and see what's different.
    It could be that something has been relying on implicit datatype conversions i.e. strings to dates and someone has entered some data that doesn't comply with the implicit conversion (i.e. you database stores dates as strings and allows people to enter cr@p data).It is 11.2.0.3
    PROCESS_FUDS is the job and defined the same on the two db.
    I did spool the code of ER.REQUEST_API from dba_source for the two dbs and dff them. Found no different.
    In the same sqlplus client on the remote server:
    on the test db:
    me@cpt1> exec ER.REQUEST_API.DBSS_process_FUDS
    PL/SQL procedure successfully completed.
    on the prod db:
    me@cpp1> exec ER.REQUEST_API.DBSS_process_FUDS
    BEGIN REQUEST_API.DBSS_process_FUDS; END;
    ERROR at line 1:
    ORA-06550: line 1, column 93:
    PLS-00306: wrong number or types of arguments in call to 'PROCESS_FUDS'
    ORA-06550: line 1, column 93:
    PL/SQL: Statement ignored
    ORA-06512: at "SYS.DBMS_JOB", line 82
    ORA-06512: at "SYS.DBMS_JOB", line 140
    ORA-06512: at "ER.REQUEST_API", line 1190
    ORA-06512: at line 1

  • PLS-00306: wrong number or types of arguments  help!!!

    Hi,
    I am new to pl/sql programming I am stuck into oracle error for my code. Plz help me with this issue my code is as follow:
    CREATE OR REPLACE PROCEDURE raise_salary
    (emp_id IN employee.employee_nb%TYPE,
    amount IN employee.salary%TYPE,
    emp_name OUT employee.employee_name%TYPE)
    IS
    BEGIN
    UPDATE employee SET salary= salary+amount WHERE employee_nb = emp_id;
    SELECT employee_name INTO emp_name FROM employee WHERE employee_nb=emp_id;
    DBMS_OUTPUT.PUT_LINE('SALARY HAS BEEN UPDATED FOR ' || emp_name);
    END;
    errror:
    Error report:
    ORA-06550: line 1, column 7:
    PLS-00306: wrong number or types of arguments in call to 'RAISE_SALARY'
    ORA-06550: line 1, column 7:
    PL/SQL: Statement ignored
    06550. 00000 - "line %s, column %s:\n%s"
    *Cause:    Usually a PL/SQL compilation error.
    *Action:                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   

    There is a problem with emp_name OUT employee.employee_name%TYPE parameter. OUT means WRITE ONLY, IN means READ ONLY. So you can not read from an OUT parameter and you are trying to do that in the line
    DBMS_OUTPUT.PUT_LINE('SALARY HAS BEEN UPDATED FOR ' || emp_name);
    CREATE OR REPLACE PROCEDURE raise_salary(emp_id   IN employee.employee_nb%TYPE,
                                             amount   IN employee.salary%TYPE,
                                             emp_name OUT employee.employee_name%TYPE) IS
    BEGIN
      UPDATE employee SET salary = salary + amount WHERE employee_nb = emp_id;
      SELECT employee_name
        INTO emp_name
        FROM employee
       WHERE employee_nb = emp_id;
    /*** DBMS_OUTPUT.PUT_LINE('SALARY HAS BEEN UPDATED FOR ' || emp_name); ***/
      --Problem in in the above line. emp_name IS Declared AS OUT
      --So it is WRITE ONLY. You can not read from it within the procedure.
    END;What you can do is to declare that parameter as IN OUT like
    CREATE OR REPLACE PROCEDURE raise_salary(emp_id   IN employee.employee_nb%TYPE,
                                             amount   IN employee.salary%TYPE,
                                             emp_name IN OUT employee.employee_name%TYPE)but there is some other more elegant and better way to do this without hitting the table twice (one for update and one for selecting the name) using RETURNING clause.
    SQL> CREATE OR REPLACE PROCEDURE raise_salary(emp_id   IN emp.empno%TYPE,
      2                                           amount   IN emp.sal%TYPE,
      3                                           emp_name IN OUT emp.ename%TYPE) IS
      4  BEGIN
      5    UPDATE emp
      6       SET sal = sal + amount
      7     WHERE empno = emp_id RETURNING ename INTO emp_name;
      8    DBMS_OUTPUT.PUT_LINE('SALARY HAS BEEN UPDATED FOR ' || emp_name);
      9  END raise_salary;
    10  /
    Procedure created.
    SQL> set serverout on
    SQL> DECLARE
      2  v_name emp.ename%TYPE;
      3  BEGIN
      4  raise_salary(7369,100,v_name);
      5  END;
      6  /
    SALARY HAS BEEN UPDATED FOR SMITH
    PL/SQL procedure successfully completed.
    SQL> NOTE: There is no commit or rollback in this (as in your original example). So you have to issue implicit commit or rollback.
    Edited by: Saubhik on Oct 29, 2010 11:44 PM
    Edited by: Saubhik on Oct 29, 2010 11:50 PM

  • PLS-00306: wrong number or types of arguments in call to 'XMLAGG'

    Hello,
    I have a procedure that creates an xml file and I need to order by an admission date using XMLAGG. When I run the query on it's own, with it not being inside a procedure it runs fine. When I try to run it within a procedure it throws back the above error message, unless I comment out the 'order by'. Does anyone know how I can get this to run with the order by within a procedure?
    We are using Oracle9i Enterprise Edition Release 9.2.0.6.0 - 64bit Production.
    Thanks.
    SELECT XMLELEMENT("Stakeholder", XMLELEMENT("ULI", a.ULI),
                                            XMLELEMENT("Gender",a.GENDER),
                                  XMLELEMENT("BirthDate", XMLATTRIBUTES(a.BIRTH_DATE_TYPE AS "type"), a.BIRTH_DATE),
                                            XMLELEMENT("HealthCareNumberInformation",XMLELEMENT("HealthCareNumber",a.HCN),
                                                                                              XMLFOREST((a.PROV_ISSUING_HCN) AS "ProvinceTerritoryIssuingHCN")),
                                            XMLELEMENT("SubmissionType",a.SUBMISSION_TYPE),
                                            (SELECT XMLAGG(XMLELEMENT("ServiceEpisode", XMLELEMENT("AdmissionDate", a2.ADMISSION_DATE )) ORDER BY a2.ADMISSION_DATE)
                                                      FROM admissions a2
                                                                , discharge d2
                                            WHERE a.uli = a2.uli
                                                      AND a.uli = d2.uli
                                                           AND a2.encounter_number = d2.encounter_number
                        )).getClobVal() AS "result"
    FROM Admissions a
         , Discharge d3
         , Diagnosis d
    WHERE a.ULI = d3.ULI
    AND a.ENCOUNTER_NUMBER = d3.ENCOUNTER_NUMBER
    AND a.ULI = d.ULI
    AND a.ENCOUNTER_NUMBER = d.ENCOUNTER_NUMBER
    GROUP BY a.ULI
         , a.GENDER
         , a.BIRTH_DATE_TYPE
         , a.BIRTH_DATE
         , a.HCN
         , a.PROV_ISSUING_HCN
         , a.SUBMISSION_TYPE

    create table mytab (a number,b number);           
    insert into mytab values (1,100);                 
    insert into mytab values (2,200);                 
    SVIL>SELECT xmlelement("A",XMLAGG(XMLELEMENT("B", b ) ORDER BY b)) FROM mytab;
    XMLELEMENT("A",XMLAGG(XMLELEMENT("B",B)ORDERBYB))
    <A><B>100</B><B>200</B></A>
    SVIL>create or replace function getx return xmltype is
      2  r xmltype;
      3  begin
      4  SELECT xmlelement("A",XMLAGG(XMLELEMENT("B", b ) ORDER BY b))
      5  into r
      6  FROM mytab;
      7  return r;
      8  end;
      9  /
    Avvertimento: funzione creata con errori di compilazione.
    SVIL>sho err
    Errori in FUNCTION GETX:
    LINE/COL ERROR
    4/1      PL/SQL: SQL Statement ignored
    4/23     PLS-00306: wrong number or types of arguments in call to 'XMLAGG'
    4/23     PL/SQL: ORA-00904: "XMLAGG": invalid identifier
    SVIL>
    SVIL>ed a
    SVIL>select * from v$version where rownum=1
      2  ;
    BANNER
    Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit ProductionThe same code works on 10.2.0.4 and 11.1.0.6, don't have other versions to test
    Testing your code
    SVIL>declare                                                                                              
      2   d integer;                                                                                          
      3   x xmltype;                                                                                          
      4  begin                                                                                                
      5     select deptno, xmlagg (xmlelement (e, ename || ',') order by ename)                               
      6     into d, x                                                                                         
      7     from emp                                                                                          
      8    where deptno = 10                                                                                  
      9   group by deptno;                                                                                    
    10  end;                                                                                                 
    11  /                                                                                                    
       select deptno, xmlagg (xmlelement (e, ename || ',') order by ename)                                    
    ERRORE alla riga 5:                                                                                       
    ORA-06550: line 5, column 19:                                                                             
    PLS-00306: wrong number or types of arguments in call to 'XMLAGG'                                         
    ORA-06550: line 5, column 19:                                                                             
    PL/SQL: ORA-00904: "XMLAGG": invalid identifier                                                           
    ORA-06550: line 5, column 4:                                                                              
    PL/SQL: SQL Statement ignored                                                                             
    SVIL>select deptno, xmlagg (xmlelement (e, ename || ',') order by ename) from emp group by deptno;        
        DEPTNO XMLAGG(XMLELEMENT(E,ENAME||',')ORDERBYENAME)                                                   
             1 <E>mike,</E><E>tom,</E>                                                                        
             2 <E>carl,</E>                                                                                    Max
    Edited by: Massimo Ruocchio on Dec 7, 2009 11:11 PM
    Corrected return type

  • PLS-00306: wrong number or types of arguments in call to '(FUNCTION)'

    Hi all,
    I've spent quite some time trying to get this to work, but is appears that none of the code samples I have tried work with this version of ODP.Net : 2.102.2.20.
    It's the most basic thing : return a weak typed resultset from an oracle function using weak typed SYS_REFCURSOR. I got this to work with a procedure, but no way this works with a function.
    I'm using the code approach from this source : http://www.oracle.com/technology/pub/articles/mastering_dotnet_oracle/williams_refcursors.html
    CREATE OR REPLACE FUNCTION
    fn_getItemsByDispNumber(p_Number in varchar2)
    return sys_refcursor
    IS
    resultset sys_refcursor;
    begin
    open resultset for
    ....select statement
    return resultset;
    end;
    Exception is : ORA-06550: line 1
    PLS-00306: wrong number or types of arguments in call to '(fn_getItemsByDispNumber)'
    Using strong types is not an option I have too many columns adn result sets that it makes no sense.
    I tried to obtain the sys_refcursor as return value and as output parameters and it's the same results. I also tried adding the return value parameter to the command object first, but with no luck (same error).
    Is there some magical trick thet must be done for this simple thing to work ?
    Thanks

    user10940202 wrote:
    The calling code looks like this :
    Dim cmd As OracleCommand = New OracleCommand("fn_getItemsByDispNumber", con)
    cmd.CommandType = CommandType.StoredProcedure
    Dim p_refcursor As OracleParameter = New OracleParameter
    p_refcursor.OracleDbType = OracleDbType.RefCursor
    p_refcursor.Direction = ParameterDirection.ReturnValue
    cmd.Parameters.Add(p_refcursor)
    Dim inputparm As OracleParameter = New OracleParameter
    inputparm.OracleDbType = OracleDbType.Varchar2
    inputparm.Name = "p_Number"
    p_refcursor.Direction = ParameterDirection.Input
    cmd.Parameters.Add(inputparm)
    cmd.Parameters.Add(p_refcursor)
    'ExecuteNonQuery() also fails with the same error message
    Dim da As OracleDataAdapter = New OracleDataAdapter(cmd)
    Dim ds As DataSet = New DataSet
    da.Fill(ds)
    I also tried to rever the order in which parameters are specified but same the same error persists. I also tried with output parameter of type SYS_REFCURSOR but no luck, same exact error.
    Is it possible that weakly typed cursors are not supported with functions ? That would be strange because it's the first use I can think of for the function concept?
    Edited by: user10940202 on Sep 14, 2009 12:44 PMHi,
    Looks like a few things are jumbled together here...
    You have p_refcursor.Direction = ParameterDirection.Input and the parameters added to the collection multiple times, etc...
    You should just need something like this:
    Dim p_refcursor As OracleParameter = New OracleParameter
    p_refcursor.OracleDbType = OracleDbType.RefCursor
    p_refcursor.Direction = ParameterDirection.ReturnValue
    Dim inputparm As OracleParameter = New OracleParameter
    inputparm.OracleDbType = OracleDbType.Varchar2
    inputparm.Name = "p_Number"
    inputparm.Value = <Some Value>
    cmd.Parameters.Add(p_refcursor)
    cmd.Parameters.Add(inputparm)Regards,
    Mark

  • PLS-00306: wrong number or types of arguments in call to 'TO_CURRENT'

    Hi,
    I'm a newbie with Oracle procedures and Oracle Spatial, and I have this problem:
    I have a table named POINT which is in a older version in Oracle Spatial, is a Relational Model with the following tables: POINT, POINT_SDO_INDEX, POINT_SDODIM, POINT_SDOGEOM, POINT_SDOLAYER. I think returned by Arcsde this way, and I can't modify this. Only POINT and POINT_SDOGEOM have data. I need this data in a newer version of Oracle, so I tried the SDO_MIGRATE.TO_CURRENT procedure, in order to do it, I created a table called NEWPOINT with the same columns as POINT, and I added a column LOC with type SDO_GEOMETRY. I'm using Oracle 10g and I tried this procedure (http://download.oracle.com/docs/cd/B13789_01/appdev.101/b10826/sdo_objmigr.htm) in SQL developer:
    begin
    execute immediate mdsys.sdo_migrate.to_current('POINT','NEWPOINT','SDO_GID','LOC','POINT','INSERT');
    end;
    SDO_GID is the same in both tables and the table NEWPOINT is empty.
    This is the error I got:
    PLS-00306: wrong number or types of arguments in call to 'TO_CURRENT'
    I think I'm doing nothing wrong, and I've been trying to solve it for 4 days without any progress. I would be gratefull if you can help me. Thanks.

    Thanks for answer so quickly Boneist, I tried what you said and I have the same error.
    This is the description of Mdsys.sdo_migrate, TO_CURRENT (1) is what I need and I don't see anything strange.
    desc mdsys.sdo_migrate
    PROCEDURE Argument Name Type IN/OUT Default
    FROM_815_TO_81X TABNAME VARCHAR2 IN unknown
    FROM_815_TO_81X COMMIT_INT NUMBER IN unknown
    OGIS_METADATA_FROM <none> IN unknown
    OGIS_METADATA_TO <none> IN unknown
    TO_CURRENT (1) LAYER VARCHAR2 IN unknown
    TO_CURRENT (1) NEWTABNAME VARCHAR2 IN unknown
    TO_CURRENT (1) GIDCOLUMN VARCHAR2 IN unknown
    TO_CURRENT (1) GEOCOLNAME VARCHAR2 IN unknown
    TO_CURRENT (1) LAYER_GTYPE VARCHAR2 IN unknown
    TO_CURRENT (1) UPDATE_FLAG VARCHAR2 IN unknown
    TO_CURRENT (2) TABNAME VARCHAR2 IN unknown
    TO_CURRENT (2) COLUMN_NAME VARCHAR2 IN unknown
    TO_CURRENT (2) COMMIT_INT NUMBER IN unknown
    TO_CURRENT (3) (FUNCTION) <return value> OBJECT OUT unknown
    TO_CURRENT (3) GEOM OBJECT IN unknown
    TO_CURRENT (3) DIM VARRAY IN unknown
    TO_81X LAYER VARCHAR2 IN unknown
    TO_81X NEWTABNAME VARCHAR2 IN unknown
    TO_81X GIDCOLUMN VARCHAR2 IN unknown
    TO_81X GEOCOLNAME VARCHAR2 IN unknown
    TO_81X LAYER_GTYPE VARCHAR2 IN unknown
    TO_81X UPDATE_FLAG VARCHAR2 IN unknown
    22 rows selected

  • PLS-00306: wrong number or types of arguments in call to 'IS NULL'

    Hello
    in a nutshell, the following script doesn't work as expected:
    DECLARE
    v_Flight CORE.T_Flight%RowType := NULL;
    BEGIN
    IF (v_Flight IS NULL) THEN
    DBMS_OUTPUT.PUT_LINE('v_Flight is null');
    END IF;
    END;
    whereby 'CORE.T_Flight' is an existing DB table.
    When running the script, the following error is printed:
    IF (v_Flight IS NULL) THEN
    FEHLER in Zeile 4:
    ORA-06550: line 4, column 6:
    PLS-00306: wrong number or types of arguments in call to 'IS NULL'
    ORA-06550: line 4, column 2:
    PL/SQL: Statement ignored
    In other words: it seams that a 'rowtype' cannot be compared against NULL. Replacing the direct comparision with the statement
    IF (NVL(v_Flight, 0) = 0) THEN ...
    produces the same error.
    Who can help me?
    (I hope I'm not boring the experts - I'm a beginner)
    thanks
    Daniel

    Hi,
    It's just a limitation of PL/SQL that we have to deal with... from the documentation: "Records cannot be tested for nullity, or compared for equality, or inequality".
    If you really need to do this check you may want to create a function for it:
    function t_flight_rec_is_null (
       p_rec in t_flight%rowtype
    ) return boolean
    is
    begin
       return p_rec.field1 is null and p_rec.field2 is null ... and p_rec.fieldN is null;
    end;cheers,
    Anthony

Maybe you are looking for

  • Scan function

    I have hp laserjet pro 200 color mfp m276nw When scanning I do not get full page It seems letter iso A4, so miss part bottom page How can I tackle this thx

  • My new Sleek + Real Rhapsody. A revi

    I've seen acouple questions from people about the Sleek, so I figured I'd post a review of mine. Sorry if it is too long-winded. I?ve owned a Creative Nomad Jukebox Zen NX for about 2-/2 years.<SPAN> Overall I was happy with it, but I wanted to take

  • Material group & Account Assignment Category

    All, Whether we can make Material group and Accout assignment link in PR.? Suppose I am creating a PR and selecting a Account Assignment , only specific material groups I shoulb able to select , whether I can make that settings ? Kindly advise the be

  • Can't grasp the relation between tab set, parent tab, standard tab set and standard tab

    Very novice to apex application building, but after trying to figure the concepts behind the tab sets I'm getting more and more confused about it as I always get different behaviour when changing things. The documentation is not very clear on this. I

  • Report server trace or debug

    HI Team, How to enable trace or debug mode for report server 6i in Oralce apps11.5.10.2? My iuuse is: We are using quoting module . The user is running reports through report server. The user is unable to run report through report server. he edited t