Hello folks,

My client's driver is making a subscriber query using the Oracle EBS HR
driver (NOT the JDBC driver). The query succeeds for one field name and
fails for a different one. The failure make this very difficult in their
dev environment; they had changed the tenant they are using for
development, their authoritative source (Workday.com) employee IDs are
the same but their Oracle employee IDs differ between the tenants so our
match rules don't all work. The one we need to handle this change of
tenant is of course what doesn't work.

The driver is sending this message to EBS:

<EBS_EVENT>
<EVENT_NAME>oracle.apps.fnd.user.search</EVENT_NAME>
<DRIVER_TYPE>HR</DRIVER_TYPE>
<OBJECT>
<SEARCH_ATTR>
<P_ASSIGNMENT_NUMBER>101205</P_ASSIGNMENT_NUMBER>
</SEARCH_ATTR>
<READ_ATTR/>
</OBJECT>
</EBS_EVENT>

The error it is getting back is:
USER ACCOUNT EXCEPTION: ORA-21560: argument 5 is null, invalid, or out
of range

When it tries the same thing for P_PERSON_ID:
<EBS_EVENT>
<EVENT_NAME>oracle.apps.fnd.user.search</EVENT_NAME>
<DRIVER_TYPE>HR</DRIVER_TYPE>
<OBJECT>
<SEARCH_ATTR>
<P_PERSON_ID>2746</P_PERSON_ID>
</SEARCH_ATTR>
<READ_ATTR/>
</OBJECT>
</EBS_EVENT>

It gets back XML (since its the same record it should have been exactly
the same response):
<EBS_EVENT>
<EVENT_NAME>oracle.apps.fnd.user.search</EVENT_NAME>
<OBJECT>
<ROW num="1">
<ASSOCIATION>2746</ASSOCIATION>
<SRC-DN>2746</SRC-DN>
</ROW>
</OBJECT>
</EBS_EVENT>

P_ASSIGNMENT_NUMBER is being set successfully (by the driver itself on
an add command), so it's a valid field.

I know the magic here is buried somewhere in that script that comes with
the driver that has to be installed into Oracle EBS. But I don't want to
take an Oracle course to solve this if I can help it (in fact I want to
ask the client's DBAs to solve this). Any advice?

Thanks
Rob


--
rrawson
------------------------------------------------------------------------
rrawson's Profile: https://forums.netiq.com/member.php?userid=403
View this thread: https://forums.netiq.com/showthread.php?t=56505