In our Oracle 11.2 PL/SQL package SPEC, there is a Proc listed twice "get_owned_inventory", just differing in params. (see below)

When LLBL Syncs notice how, in the screenshot, it **combines all the params ** from both procs into one, then when it tries to get the TypedView schema fails of course as there is no call for a proc with both sets of params in one call:

Error: 'Stored procedure 'XX_WEB_INVENTORY_PKG.GET_OWNED_INVENTORY' caused an exception during resultset retrieval. PLS-00306: wrong number or types of arguments in call to 'GET_OWNED_INVENTORY'

See screenshot for the Proc LLBL creates, it combines both sets of params into one big call.

PROCEDURE get_owned_inventory
  (
    p_user_name                    IN  VARCHAR2,
    p_search_sku                   IN  VARCHAR2,
    p_supplier_id                  IN  NUMBER,
    x_inventory                    OUT SYS_REFCURSOR,
    x_return_status                OUT VARCHAR2,
    x_return_msg                   OUT VARCHAR2
  );

 
  PROCEDURE get_owned_inventory
  (
    p_user_name                    IN  VARCHAR2,
    p_vendor_id                    IN  NUMBER,
    p_warehouse_code               IN  VARCHAR2,
    p_subinventory_code            IN  VARCHAR2,
    p_search_type                  IN  VARCHAR2,
    x_inventory                    OUT SYS_REFCURSOR,
    x_return_status                OUT VARCHAR2,
    x_return_msg                   OUT VARCHAR2
  );

Added screenshot of Wizard showing the Stored Proc twice

Which Designer version /release date are you using?

Does this occur if you select both SPs in the schema refresh wizard?, or it occurs regardless of you select one or both SPS?

5.7 (5.7.1) RTM

It happens regardless if I select 1 or both.

It seems LLBL talks to the Oracle Spec for the Proc, and combines the IN and OUT params all together for all Procs named the same

You have a stored procedure which uses overloading (this is similar to what e.g. C# does, same method name, different # of arguments), however that's not supported in our system: only stored procedures without overloading are supported.