Hi All

Firstly, I have checked this on metalink and Oracle say it's not possible so if no-one has an answer no probs, but then i always see "It's not possible" as "I challenge ye!" so here we go...

We want to add a DFF Segment for "Working pattern" to the ESS absence screen that does two things:

1. Displays/does not display based on the absence type being entered
2. Does not display for certain areas of the globe/different Business Groups

Where I have got to is to create the DFF for working pattern, populate the list dynamically with the working patterns in the system etc but I can only get it to appear on the ESS screen if I add it to the "Global Data Elements" Context field value of the DFF. This means folks in other countries around the world can also see it and those same folks don't need it and sure as hell don't want it (especially as it will cause them problems in the PUI as it is a mandatory field). Also it means it will display for all absence types.

If I add it to one of the other Context Field Values that link to the absence types themselves it displays in the PUI accordingly (depending on the absence type), but not at all in the ESS.

From what I see from Oracle, they state it is because we are using a reference field within the context field of the DFF (which apparently they do not support...). Long story short, lets just say we NEED to keep this reference field in there.

Does anyone know of a way (without a HUGE, UNSUPPORTED customisation) we can arrange for this extra segment to appear on the ESS without it appearing for all global users, and (preferably) based on the context of the absence type?

I'm not asking for much am I?!

Many thanks
Craig

Hello,

This is a bit of a work-around, and as I haven't tried it myself, may not work (I know it will in PUI, but not certain about SS).

Rather than Reference field based, try using two segments along the following lines ...

Segment(X) is table based and mandatory. It's based on the PER_BUSINESS_GROUPS view, and has a WHERE clause that ensures the Users business group is the only valid value based on the Business Group profile option. The BG Id or Name is defaulted using an SQL default.

Segment(Y) (the Working Pattern segment) is also table based and mandatory. It's based on a LookUp, or whatever table has the valid Working Pattern list, with an added value of "N/A". The WHERE clause looks at the previous segment, and if it's a BG that needs a Working Pattern, then excludes the "N/A" value, and if not, include the "N/A" as the ONLY valid value. Then a value is defaulted also based on the value of Segment(X) (the BG). If the BG is one that you DON'T need a Working Pattern for, the the defaulted value is "N/A". Hence the Working Pattern segment is mandatory for all cases, but only has a REAL value for BG's where it's applicable.

Hope this makes sense.

Regards,

Peter.

There are 2 DFFs on the ESS LOA screen.
1. Add Absence details
2. Further Absence details - called as "Additional Absence Detail Information"

I have used Further Absence details to show/hide segments.
Now the reference for this DFF is "C_LEGISLATION_CODE" but this is infact made up of <leg code>_<absence category code> (
Mind you that this is based on "Absence category" and not "absence type" )

So if you have a Annual Leave for then you can define your own structure for "UK_AL" and define the segments..
then when you select the absence type (which internally defaults absence category) the segments will be displayed..

Hi

Thanks for the proposed solutions. Shiva, I have tried yours and it is now working in ESS so that's awesome - thanks very much!

The only issue we have now is that in the PUI the further information is not accepting input directly - only when it comes from ESS can you click in the further information field to open up the applicable segments.

It seems when I check the diagnostics on the PUI, the C_LEGISLATION_CODE is showing only as 'GB' (even after selecting an absence type (and therefore category) this does not change to 'GB_xx' where xx is the category code).

Have you come across anything like this when you were configuring?

Many thanks
Craig

what is the absence category for the absence type?

you will find it on absence type definition screen

Hi Shiva

The Absence Category is Vacation, the absence type is Annual Leave and the Absence Category Code is 'V'.

We have therefore set up a new segment for context field 'GB_V' which we would expect to work in the PUI the same as it is now (thanks to your solution) in ESS.

Now, when we enter 'Annual Leave' into the Absence PUI, the category gets populated with Vacation (as expected), but the C_LEGISLATION_CODE (per the diagnostics) is still showing as only 'GB'. This means the additional segments for the 'GB_V' are not showing. If I check an absence of Annual Leave that has come through from ESS, the C_LEGISLATION_CODE is correctly showing as 'GB_V', and therefore the additional segments can be viewed/edited.

I'm thinking maybe (a) it's a bug; or (b) we need to personalise the form to refresh once a user enters an absence type to (possibly) refresh the C_LEGISLATION_CODE value?

Many thanks
Craig

create a new absence category in the lookup "ABSENCE_CATEGORY" and try..

Hi Shiva

Apologies for the delay in coming back to you - we managed to get it working in the end using a workaround of sorts. In the PUI we have made all the various fields available but made those that are specific to an absence type non-mandatory.

In the ESS we have attached the various fields to the absence categories as necessary but made them mandatory.

Many thanks for your help
Craig

Ok. No worries.

Hi Craig,

I have the same requirement like based on absence category/absence type I need to display Dff segments
however I followed the steps mentioned by you and Shiva,its not working for Global HRMS
May be for UK GB_V was working for you but same is not working for global HRMS

Hi all,

Bit late, but I have had the same issue with the C_LEGISLATION_CODE - GB_V only working in SSHR and not in Core Forms, so I thought I'd post a solution.

For Craig [ClanGowland] and sairajesh, and anyone else experiencing this issue, the way round this is a Forms Personalization to set the appropriate C_LEGISLATION_CODE in Core Forms.


Set up the "Additional Absence Detail Information" [PER_ABS_DEVELOPER_DF] DFF with a new Context code e.g. GB_V

GB_V GB Vacation
10 Part Day Indicator ABS_INFORMATION1 XX_YES_NO


In the SSHR create/update pages, you can personalize the Flex: "Further Absence Details" item with your segment list:

GB_V|Part Day Indicator


Next time a vacation is chosen in SSHR, your custom segment will appear.


In Core HRMS however, when entering a Vacancy, you will find via Diagnostics > Proprties > Item > that your C_LEGISLATION_CODE remains unchanged.
[depending on your system setup you will find the context of 'GB' or 'GB_PQP_OSP_OMP_PART_DAYS' appears]

In order to amend this do a Forms Personalization on the absence form that checks for the absence category and then automatically sets the legislation code.

10 Set C_LEGISLATION_CODE context for Vacation Form
CONDITION
Trigger Event WHEN-NEW-ITEM-INSTANCE
Trigger Object ABA.C_REASON_DESC
Condition :ABA.ABSENCE_CATEGORY = 'V'
ACTIONS
10 Property
Object Type Property
Target Object ABA.C_LEGISLATION_CODE
Property Name VALUE
Value GB_V

Note: You may notice that this is based on someone changing the 'absence reason' on the form rather than the type. I could not get it to work using type or category, but this one will work effectively enough anyway.

Close the absence form and re-open it.

Now any new vacation will trigger the setting of the C_LEGISLATION_CODE to GB_V and your pop-up for Further Information will show your custom segments.


This could be repeated for each absence category per business group. Or you could remove the condition and use =:CTL_GLOBALS.LEGISLATION_CODE||'_'||:ABA.ABSENCE_CATEGORY as the property value to set it in all instances.


Regards

Mike

Hi Mike

Thank you for taking the time to provide a detailed and useful response.

Regards

Barry