Imp Job Interview Tip: Fix Your Resume!

Are you struggling to land an Interview with a MNC and don’t know the reason why you don’t get a call?

Many a times we have all the skills required for a particular job but we are still not able to get the interview call. The reason? It could be your resume.

Seriously – when you goto buy anything to the supermarket, lets take an example of a Perfume – what do you look for? Which item will you pick up first?  the one with best packaging.

All of the perfumes have different fragrances. Some of them you don’t like. But then there are a few that matches your taste. You like them. After that, before you even ask the price what is it that you like? The bottle. Exactly -the Packaging.

And that is what a resume means for an IT professional. If your packaging is not good, how do you expect someone to pickup and try the fragrance that you have?

 

Even if you think you have the best resume among your friends, it may not be the best professional resume that these MNCs are looking for. It always pays to hire a professional do the work for you.

Shine Resume Services can help you package your resume in a better way – to land you a job interview with whomever you want. You can easily Get noticed by recruiters with a professional CV . Are you applying for your dream job? Applying to MNC? Get world class resume from Shine. Its worth spending a few bucks in the beginning to get your resume straightened up – because you know, you will get only one chance. Most of the MNCs won’t let you submit your resume again for atleast 180 days period.

Shine india also provides Personal counseling on your CV with Shine Resume . A resume will tell the prospective employer a lot about you – and that is when they decide whether to call you for an interview or now. A professional resume brings out what employer wants to see, helping you land that most wanted interview call.

If you want to reach thousands of consultants in flash of light, Click here to send your resume to 1000+ consultant and prepare your resume to Get interview calls with Shine Resume Services.

Happy Job Searching!

Oracle Jobs in Mumbai, Bangalore, Chennai and Other Cities in India

With todays excitingly changing markets, its a must to be out there with your best foot forward. Hirings are picking up again, and if you are like me who likes challenges and a new role every few years, then i bet you must have already started looking for a new opportunity.

Whether you are an experienced professional, or you recently graudated from a college and looking for a Job in a metro city in India, or in nearby locations then you must give a try to Monster’s exciting and promising Job search services.  Monster India has thousands of jobs for freshers, engineers, experienced professionals, Management jobs and more.

Are you a Oracle Applications professional and looking for a quick start in an consulting career, or a managment career in Mumbai, Chennai, Bangalore, Noida/Delhi, Indore or another metro in India? Go to Monster India Job Search page and find some of the best recruiters across India. If the job matches your aspiration, create your resume and apply for the job. Its easy on Monster india.

If you are not getting what you want on Monster, then try Shine.

Hundreds of Job opportunities are waiting for you! on Shine Job Portal. All you have to do to find a  Job in Indore is to Post your Resume and then let Shine work for you. Recruiters will find your resume and if you fit their requirements, you will get a call soon. Shine will also help you protect your identity using its Privacy Protection features.

If you are confused about how much salary you should be asking for a particular job, then Check out the unique salary Benchmarking tool. This tool will help you negotiate your salary and provide your with the firsthand information you need to know before your talk about Money.

Hope that these two Job Portals help you in finding your next big opportunity. All the best for your career!

courtsey: www.Logicwala.com

Employee Directory in Oracle HRMS

Today I am going to talk about a not-so-popular and less known feature of Oracle HRMS. Its called the employee directory.

Well, as the name suggest, Employee Directory is a directory of all employees of any organization. Employee Directory provides a webbased frontend that helps search any employee in the organization. It allows to browse through the organizational hierarchy, check who’s who in the company, who reports to whom and how many people report to a manager….lot of information, on one page.

Its a great tool. One of the coolest feature is the employee picture. The picture that you load on employee form in Oracle HRMS – is visible here on the webpage in employee directory.

Recently at a client i implemented employee directory. Here are the quick steps to make it work:

1. Add a new menu to Employee Self Service (assuming you want this feature available to all employees).

2. Menu Item Name : Employee Directory
3. Function User Name: Simple Search
4. Function Name: HR_EMPDIR_SIMPLE_SEARCH
5. Description: Employee Directory Simple Search

Navigation to do this:

1. Goto Applications à Menu
2. Query for “Employee Self Service” in User Menu Name.
3. Scroll all the way to end and add one more line.
4. Prompt “Employee Directory”, Function “Simple Search”
5. It will provide multiple options for “Simple Search” – select the “Employee Directory Simple Search” option.
6. Save

 

Try this…and probably some time soon, i’ll also put together something to tell you how to upload bulk of Employee pictures in Oracle HRMS.

 

Have fun with oracle! Have fun at knoworacle!

 

Oracle HRMS Functional Questions

What is the difference between rehire and reverse-termination?
What is a security profile in HRMS?
Is Address form date tracked?
What are the date tracking options while deleting a record?
Can we delete an employee forever? How?
What is required to be able to pay someone in Oracle Payroll?

before i post answers to these questions, lets hear from you..Post your answers in the comments and then who knows, may be i won’t have to answer at all

-ashish

Salary form in Oracle HR

I have been asked this question by many clients and consultants recently, and the solution is pretty straight forward. So, i thought i’ll share it here with y’all.

Oracle released a Family pack RUP 2 for HRMS last year, and it brought in a new feature – The web based Salary Administration form.

For many users, it was a thrill. But for a lot others, it was a challenge to get it to work. They are used to the old form based salary administration interface. Some of them even have custom hooks on the form that can not be implemented on the webpage so easily.

So, the Question is, how to revert to the salary form after applying this RUP, so you can still continue using the form based salary administration.

Here’s the answer. And as i said, its pretty straightforward.

Taskflows come to rescue.

Here are the steps to replace “New Salary Framework Page” with “Old Salary Form”:

• Select any HRMS or Super HRMS Manager Responsibility (Example: US HRMS Manager)
• Open the “Define Taskflow” form. (Security->Task Flow Definitions)
• Query the Taskflow that is used by the Person form function (For Example: US HRMS PERSON TASKFLOW). Normally, this is the custom Taskflow.
• Go to “Node section – Name field” and add “SALFORMNODE” by inserting a new row and selecting “SALFORMNODE” from Lov in the Name field.
• Then Query “NASSIGN” node in “Node Section”.
• In “Navigation Options Section”, delete record that has “SALREVIEW” for Node. Select “Yes” in the delete warning window.
• In Navigation Options, insert new record with the following details:
  Seq: 1
  Node: SALFORMNODE
  Button: Checked
  Label: &Salary (leave the default &Salary as is)
• Save and Exit the “Define Taskflow” form.
• Logout the current applications and re-login to check that the “Old Salary form” is launched instead of “New Salary Page” when “Salary” button is selected in Assignment Window.

Try this, and let us know if you still have any issues. Most probably, it’s because you are using Oracle

cheers!

Oracle Business Accelerators for EBS

 

Oracle has – after a long wait – released the new set of tools called Oracle Business Accelarators, for eBusiness Suite.

What are Accelarators:

Accelarators, as per Oracle, are the next generation tools for rapid and precise implementation. They Automatically configure the EBS Flows based on leading industry practices. These accelarators user a highly structured, prescribed method reducing impact due to varying implementation skills.

As of now, Accelarators are only available to trained Oracle Partners and Oracle Consulting.

To know more about these tools and to get trainined in them, you may visit https://accelerators.oracle.com/

 

Oracle Timecard (OTL) Automation

Recently i have seen many requests for OTL timecard automations in Oracle. One of the reasons is the financial downturn in the martket.

Many companies have announced furlough for employees- meaning the offices and manufacturing units will be shutdonw for a specified amount of time and it will be mandatory for employees to either take that time off from their vacation time, flex time, may be borrow it from next year or simply be unpaid for that time period. Whatever be the case, it saves company a lot of money that it was otherwise obligated to pay in vacation time or paid days. Now because its mandatory, it has to be in the system for the payroll to pick it up.

If the organization uses time entry system – like oracle – to enter vacation/flex time, and processes payroll then following needs to happen in order for a succesfull furlough automation.

- Employees time must be entered on the online timecard.

- The timecard must be approved by manager or Auto-approval process.

- This OTL timecard must be transferred to Batch Element Entries for Payroll.

To automate this process we will use HXC Timecard APIs provided by Oracle. These APIs help us in creating a timecard for a day, week, and also attach elements/ projects to the timecard. Also, the APIs submit the timecard with a workflow process type so it can either be picked for AUTO processing or Manual approval.

Before we go into the details, we have to see how a typical timecard is built. For the sake of simplicity, we will consider Monthly Paid (exempt) employees.

A timecard is a combination of DAYS. Each DAY will be one Row in a table. For Every day that you need to enter time (e.g. Saturday Sunday will not need a time entry being a holiday) you need a DETAIL type row also. And, for each DETAIL record that has to go into an element or project for costing or payroll purpose, we need an ATTRIBUTE also.

These are nothing but the TIME BUILDING BLOCKS. To make things simple, lets go and see these records:

select * from hxc_time_building_blocks

TYPE: MEASURE ( Number of hours to be put in that particular day) or RANGE (For period like week or day).
SCOPE: TIMECARD, DAY, DETAIL or APPLICATION_PERIOD

Now, if you see a typical timecard, this is how it looks (Use the hierarchical Query below):

TIMECARD (12/1/2008  - 12/7/2008) TYPE: RANGE
               |_  DAY (12/1/2008 – 12/1/2008) TYPE: RANGE
                                    |_  DETAIL (12/1/2008):  8 HRS   (may have attributes)  TYPE:MEASURE
               |_  DAY (12/2/2008 – 12/2/2008)
                                    |_  DETAIL (12/2/2008):  8 HRS                                                      
               |_  DAY (12/3/2008 – 12/3/2008)
                                    |_  DETAIL (12/3/2008):  8 HRS                                                      
               |_  DAY (12/4/2008 – 12/4/2008)
                                    |_  DETAIL (12/4/2008):  8 HRS                                                      
               |_  DAY (12/5/2008 – 12/5/2008)
                                    |_  DETAIL (12/5/2008):  8 HRS                                                      
               |_  DAY (12/6/2008 – 12/6/2008)
               |_  DAY (12/7/2008 – 12/7/2008)

 SELECT htbb.time_building_block_id, htbb.TYPE, htbb.measure, htbb.unit_of_measure, htbb.start_time, htbb.stop_time,htbb.parent_building_block_id, ‘N’ parent_is_new, htbb.SCOPE,htbb.object_version_number, htbb.approval_status,htbb.resource_id, htbb.resource_type, htbb.approval_style_id,htbb.date_from, htbb.date_to, htbb.comment_text,htbb.parent_building_block_ovn, ‘N’ NEW, ‘N’ changed,htbb.application_set_id, htbb.translation_display_key
FROM apps.hxc_time_building_blocks htbb START WITH ( htbb.time_building_block_id in (6848088) AND htbb.object_version_number in (1 ) )CONNECT BY PRIOR htbb.time_building_block_id =  htbb. parent_building_block_id AND PRIOR htbb.object_version_number = htbb.parent_building_block_ovn ORDER BY htbb.time_building_block_id  ASC

NOW Over to APIs….

 

 

 

 

 

 hxc_timestore_deposit.create_timecard_bb 
– Create a Timecard building block (only timecard, no days, or details)
– Here are the parameters it takes
(
   p_start_time => to_date(‘01-DEC-2008 00:00:00′,’DD-MON-YYYY HH24:MI:SS’) ,
   p_stop_time =>  to_date(‘07-DEC-2008 23:59:59′,’DD-MON-YYYY HH24:MI:SS’),
   p_resource_id => emp.person_id ,
   p_comment_text => ‘Automated TimeCard: DEC08′,
   p_approval_style_id => 41, –This is your workflow approval style, default to AUTO APPROVE
   p_app_blocks => l_tbl_timecard_info,
   p_time_building_block_id => l_tc_bb_id –returns the id of  TC Building block
   );

hxc_timestore_deposit.create_day_bb
– Creates a DAY building block (only DAY no details)
– Here are the parameters it takes
(
   p_day => l_start_date,
   p_parent_building_block_id => l_tc_bb_id,
   p_comment_text => ‘Automated TimeCard: DEC08′,
   p_app_blocks => l_tbl_timecard_info,
   p_time_building_block_id => l_day_bb_id
   );

hxc_timestore_deposit.create_detail_bb
– Creates a DETAIL building block, in next step we have to attach the attribute to this DETAIL
– Here are the parameters it takes
(
   p_type => ‘MEASURE’,
   p_measure => 8, –Number of Hours
   p_parent_building_block_id => l_day_bb_id,
   p_comment_text => ‘Automated TimeCard: DEC08′,
   p_app_blocks => l_tbl_timecard_info,
   p_app_attributes => l_tbl_attributes_info,
   p_time_building_block_id => l_detail_bb_st_id
   );
   hxc_timestore_deposit.create_attribute (
   p_building_block_id=> l_detail_bb_st_id,
   p_attribute_name=> ‘Dummy Element Context’,
   p_attribute_value=> ‘ELEMENT – 60110′, –This is the Accrual PTO Element we want to update through this API.
   p_app_attributes=> l_tbl_attributes_info);

HXC_TIMESTORE_DEPOSIT.EXECUTE_DEPOSIT_PROCESS
–This is the Submission Call. This process will submit the timecard, days and details with attributes. Timecard will stay in SUBMITTED State until approved via Manual or AUTO Approve process.
(
   p_validate => FALSE,
   p_app_blocks => l_tbl_timecard_info,
   p_app_attributes => l_tbl_attributes_info,
   p_messages => l_tbl_messages,
   p_mode => ‘SUBMIT’,
   p_deposit_process => ‘OTL Deposit Process’,
   p_retrieval_process => ‘BEE Retrieval Process’,
   p_timecard_id => l_new_timecard_id,
   p_timecard_ovn => l_new_timecard_ovn
   );

 

Hope this article helped you in understanding the basics of the Time Entry APIs. Please note that this is  the initial and basic knowledge. You will need some more knowledge – like DELETE timecards API for rollback in case of any issues. UPDATE timecard APIs etc for a full fledge capability on OTL timecard automation.