Problems with Standard Apps views (eBusiness Suite)

Question

Hi all,
I am working with Oracle Application Express and Oracle eBusiness Suite 11.5.10. We have integrated OAE with EBS, but now we are having problems with the standard views (owner APPS).
I would need the help from somebody that works with OAE and EBS.
Once we want to query one of the standard views, like ap_invoices, it is necessary to initialize the session with a script like this:
begin
DBMS_APPLICATION_INFO.SET_CLIENT_INFO(219);
end;
This script lets us to access to the data from the table AP_INVOICES_ALL using the view AP_INVOICES.
Once I have run the script from SQL Commands (SQL Workshop), I try to run a query using the standard view, for example:
SELECT * FROM apps.ap_invoices
From a Report or from SQL Commands (SQL Workshop) always I get the next error:
"ORA-01722: invalid number."
However, if I run this query from SQL Plus (same db user), there is any problem, the query works and retrieves rows.
If I get the source code of the view, remove all the columns, keeping the next SQL:
SELECT 1
FROM ap.AP_INVOICES_ALL
WHERE NVL(ORG_ID,NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))),-99)) = NVL(TO_NUMBER(DECODE(SUBSTRB(USERENV('CLIENT_INFO'),1,1),' ',NULL,SUBSTRB(USERENV('CLIENT_INFO'),1,10))),-99)
Run this SQL in OAE and I obtain the error again, however from SQL Plus the query works correctly.
I suppose somebody that works this EBS and OAE has had this problem. How did you solve it?
Thanks in advance.
Regards, Luis
PD. I have tried to not used the views and use the tables filtering the ORG_ID and looks it can work, but I do not like this option.

Answer 1

Luis - I don't know where you are running these blocks - the SQL Command Processor in APEX? Anyway, for every APEX page request the engine executes something like the following, depending on your version:    begin
    dbms_application_info.set_client_info(g_user);
    dbms_session.set_identifier(substr(g_user,1,(64 - length(g_instance)-1))||':'||to_char(g_instance));
    dbms_application_info.set_module('APEX:APPLICATION '||to_char(g_flow_id),'PAGE '||to_char(g_flow_step_id));       
    exception when others then null;
    end;In the above code, the value of g_user is the logged-in username, perhaps ADMIN in your case.
Keep in mind that when you do a set_client_info in the database session, that persists only for the duration of the session. On the next page request, you'll get a new database session (or a recycled one).
Scott