Oracle Database Discussions

I have a sybase procedure that calls another. One parameter, State_Code, is passed. When I migrate the called procedure defines 13 income parameters ...

CREATE OR REPLACE PROCEDURE "MSANAICS"."SP_RESCREEN_UNADJUSTED"
(
State_Code IN SMALLINT DEFAULT NULL,
RCT1 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1,
RCT2 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1,
RCT3 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1,
RCT4 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1,
RCT5 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1,
RCT6 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1,
RCT7 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1,
RCT8 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1,
RCT9 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1,
RCT10 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1,
RCT11 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1,
RCT12 IN OUT OMWB_EMULATION.GLOBALPKG.RCT1
)
AS ...

and the calling command in the other procedures converts as follows ...

MSANAICS.sp_ReScreen_Unadjusted SP_INSERT_UNADJUST.StateCode_,
RC1 => RC1_CALL,
RC1_CALL => RC2_CALL);

It would seem to me that all these RC variables wouldn't need to be passed but obviously Oracle thinks different. Can someone tell me why these RC variables need to be declared as parameters instead on just local variables? How should I get around this inconsistancy? Can I add dummy variables to the calling command to get it to work?

Thanks
Jeff Johnson