<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="FeedCreator 1.7.3" -->
<rss version="2.0">
	<channel>
		<title>OAF Screen in Self Service HRMS - Without Programming - Part 1</title>
		<description>Comments for OAF Screen in Self Service HRMS - Without Programming - Part 1 at http://apps2fusion.com , comment 1 to 10 out of 10 comments</description>
		<link>http://apps2fusion.com</link>
		<lastBuildDate>Thu, 11 Mar 2010 04:50:11 +0100</lastBuildDate>
        <generator>FeedCreator 1.7.3</generator>
		<item>
			<title>...</title>
			<link>http://apps2fusion.com/apps-training/apps-functional-documents/ame-sshr/417-oaf-screen-sshr-ame-self-service#comment-6960</link>
			<description>Yes- learn it quickly :) 
You will have to learn jdeveloper sooner or latter, there will be no choice for Apps Developers as entire development suite in Fusion Apps [except OBIEE and few other things] will be managed from jDeveloper.

See this for controller extension
[url]http://oracle.anilpassi.com/oa-framework-extending-controller-steps-2.html[/url]


Thanks,
Anil Passi - Anil Passi-</description>
			<pubDate>Wed, 07 Oct 2009 06:53:15 +0100</pubDate>
		</item>
		<item>
			<title>Extending the Controller at function level </title>
			<link>http://apps2fusion.com/apps-training/apps-functional-documents/ame-sshr/417-oaf-screen-sshr-ame-self-service#comment-6959</link>
			<description>Sorry to ask a newbie question but segment data validation requirements have forced me to ask this.
How do i go about Extending the Controller at function level as advised above?. Hope it doesn't involve Jdeveloper for i will then have to learn it quickly :).

Kind regards

Ken - Ken</description>
			<pubDate>Wed, 07 Oct 2009 05:10:21 +0100</pubDate>
		</item>
		<item>
			<title>Validate Start and End Date</title>
			<link>http://apps2fusion.com/apps-training/apps-functional-documents/ame-sshr/417-oaf-screen-sshr-ame-self-service#comment-6940</link>
			<description>Hi Ken

If you use Hook or Functional Trigger, those are based on BASE TABLES, i.e. PER%
However, when you implement AME, data goes to HR_API_TRANSACTIONS first, held within a CLOB, until the transaction is finalized post-approval. Therefore, the best bet for you is to &quot;Extend The Controller AT FUNCTION LEVEL&quot;


Thanks,
Anil Passi - Anil Passi-</description>
			<pubDate>Thu, 01 Oct 2009 08:38:39 +0100</pubDate>
		</item>
		<item>
			<title>...</title>
			<link>http://apps2fusion.com/apps-training/apps-functional-documents/ame-sshr/417-oaf-screen-sshr-ame-self-service#comment-6939</link>
			<description>Hi Anil,
Thanks for the good article. Aluta Continua.
One question, i have a situation where i have two date segments start date and end date just like in your example. 
I need to validate the end date such that the value entered is not more six months than start date. I.e add_months(start_date,6) is less than end_date condition must be met. 

The user should be notified of incorrect date entry on click of apply button or without navigating away from the segments page. I've created a user hook on HR_SIT_API on create of SIT record which unfortunately validates after the last approver approves but not at point of data entry on segment.

Kindly advise on how i can validate the above.
Thanks - Ken</description>
			<pubDate>Thu, 01 Oct 2009 07:44:59 +0100</pubDate>
		</item>
		<item>
			<title>Validating date segments query</title>
			<link>http://apps2fusion.com/apps-training/apps-functional-documents/ame-sshr/417-oaf-screen-sshr-ame-self-service#comment-6938</link>
			<description>Hi Anil,
Thanks for the good article. Aluta Continua.
One question, i have a situation where i have two date segments start date and end date just like in your example. I need to validate the end date such that the value entered is not more six months than start date. I.e add_months(start_date,6)  - Ken</description>
			<pubDate>Thu, 01 Oct 2009 07:41:46 +0100</pubDate>
		</item>
		<item>
			<title>Gr8 Article</title>
			<link>http://apps2fusion.com/apps-training/apps-functional-documents/ame-sshr/417-oaf-screen-sshr-ame-self-service#comment-6935</link>
			<description>Hi Anil,
         I have been following your site for some time now. Got very useful information on it.
Keep up the good work

Cheers,
Sachin Shirke - Sachin Shirke</description>
			<pubDate>Wed, 30 Sep 2009 09:50:20 +0100</pubDate>
		</item>
		<item>
			<title>Gud work</title>
			<link>http://apps2fusion.com/apps-training/apps-functional-documents/ame-sshr/417-oaf-screen-sshr-ame-self-service#comment-6927</link>
			<description>Hi Anil.

You are doing a gud work. - vikash007</description>
			<pubDate>Mon, 28 Sep 2009 21:29:56 +0100</pubDate>
		</item>
		<item>
			<title>EIT or SIT</title>
			<link>http://apps2fusion.com/apps-training/apps-functional-documents/ame-sshr/417-oaf-screen-sshr-ame-self-service#comment-6926</link>
			<description>Hi Arun,

This is just an example, and I intend to use this example to cover all possible scenarios that will help anyone to learn every possible technical aspect of Self Service HRMS.

In this specific case, of course you are right that the EIT could be used.
Barring the few steps of EIT Security/EIT Registration, remainder steps will remain largely the same whether EIT or SIT.

These series of articles are an attempt to explain SSHR architecture, and this will be applicable to any SSHR screen/process flow in Employee or Manager Self Service.

Thanks,
Anil Passi - Anil Passi-</description>
			<pubDate>Mon, 28 Sep 2009 20:21:35 +0100</pubDate>
		</item>
		<item>
			<title>Why SIT?</title>
			<link>http://apps2fusion.com/apps-training/apps-functional-documents/ame-sshr/417-oaf-screen-sshr-ame-self-service#comment-6924</link>
			<description>Hi Anil,

    This is very good article. Thanks for sharing this. I'm quite exited to see the future parts of this article where requirement D is covered on how Line Manager's Manager can approve the leave from SIT transaction. 

    While reading this, I got a big doubt about why you have chosen SIT instead of EIT.  As you have fields like &quot;Brief description of their complaint&quot; which is free text, the possibility of a re using the combination code is minimal. This way EIT (DFF) which does not store any combination code would be much easier in terms of performance and reporting. 

     I recently designed a solution for a Ticket subsidy system using EIT where claims department can raise a Ticket subsidy request (after validating the ticket receipt out side the system...that’s why its not in ESS or MSS) which checks for allowed balance for the year and automatically create an element entry and generate various letters for different situation like over the limit or no limit etc... In this system, I decided for EIT as it’s more flexible in terms of reporting and quite easy to maintain as there is no requirement of start date and end date like SIT. But this solution required some programming in terms of validation like checking for balance between EIT entries before committing as multiple entries are allowed in a singe transaction, creating the element entries. I was able to cover these logic in API Userhooks (could have done it thru extending the standard workflow as well :) ). 

    Please let me know if I’m wrong on my points as its quite interesting to always debate between EIT and SIT.

Cheers
Arun 
arun@oraclehrms.co.uk




 - Arun@oraclehrms.co.uk</description>
			<pubDate>Mon, 28 Sep 2009 18:40:19 +0100</pubDate>
		</item>
		<item>
			<title>AME</title>
			<link>http://apps2fusion.com/apps-training/apps-functional-documents/ame-sshr/417-oaf-screen-sshr-ame-self-service#comment-6921</link>
			<description>Dear Anil,
Very useful information. If you could please provide AME setup information from the beginning, will be very very helpful for us.

Thanx &amp; Regards,
Kadhiresan L
 - Kadhiresan</description>
			<pubDate>Mon, 28 Sep 2009 10:43:21 +0100</pubDate>
		</item>
	</channel>
</rss>
