My Oracle Support Banner

POU And Leave Creation Issues With Engineer Sync In Siebel Connector (Doc ID 2562635.1)

Last updated on OCTOBER 03, 2022

Applies to:

Oracle Real-Time Scheduler - Version 2.3.0.2.0 and later
Siebel CRM Integration to Oracle Realtime Scheduler - Version 18.10 and later
Information in this document applies to any platform.

Symptoms

On : 2.3.0.2.0 version, Siebel Integration

ACTUAL BEHAVIOR
---------------
POU and Leave creation issues - Engineer sync problem

We are facing issues with the integration of POUs and Leaves from Siebel to ORS using the out of the box connector. There are some glaring gaps in the Siebel - FMW - ORS integration which are highlighted below. These are out of the box issues which you can replicate in your environments as well.

1) Upon adding/modifying POUs, engineer sync towards ORS is triggered. This resets the information that is added from ORS in the crew like extra service regions (Preferred + Allowed). There is no such segregation of service areas/regions in Siebel and hence everytime the engineer sync is triggered upon adding a new POU the extra information in ORS gets reset on the crew and subsequently on it's shifts.
2) POU Reason in Siebel (Appointment, Deadline, Sick Time, Vacation) is not mapped to POU reason in ORS. It is not even being sent out of Siebel. Is there a different functionality for this field?
3) Get geocode function from the 'Employee Exception Hours' tab does not work. It gives the folllowing error: The specialized method 'GetPOUGeoCode' is not supported on Business Component 'Employee Shift Exception Hour' used by Business Object 'Employee'.(SBL-DAT-xxxxx)

Changes

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.