Convert an Employee record to a Contingent worker record

Hi friends,
I have a requirement in HRMS where a list of Employees needs to be converted to a Contingent Worker.
Since the employee details, address, etc... are already loaded, is it possible to convert/change the employee's person type from Employee to Contingent Worker? However, payroll or grade doesnot exists for these employees.
Kindly provide your valuable suggestions in this regard.
Regards,
Ahmed.
Edited by: user629449 on Oct 26, 2009 2:19 PM

Pl see if MOS Doc 744203.1 (Person_type Error In Hr_contingent_worker_api.Convert_to_cwk) is helpful
HTH
Srini

Similar Messages

How to Create Placement for contingent worker using API in 11i?

We need to Create Placement for contingent workers using an API or program without using EBS forms.
On the People form, there is an Action - Create Placement that does just what we need. We can select an Ex-contingent worker, create placement, and save. This creates a new Period Of Placement (PDP) record for the contingent worker with a new primary assignment. The result is the contingent worker can have multiple periods of placement to reflect different jobs they have worked on, for example one contract from Jan 10 - April 4, another from May 1 - 20, and a third starting Aug 7 without an end (yet).
There are several APIs we find in the Integration Repository for 11i dealing with Contingent Workers, Assignments, and changing a Period of Placement, but we can't find any for creating a PDP.
Thank you if you can advise on how to do this.
Skip

We need to Create Placement for contingent workers using an API or program without using EBS forms.
On the People form, there is an Action - Create Placement that does just what we need. We can select an Ex-contingent worker, create placement, and save. This creates a new Period Of Placement (PDP) record for the contingent worker with a new primary assignment. The result is the contingent worker can have multiple periods of placement to reflect different jobs they have worked on, for example one contract from Jan 10 - April 4, another from May 1 - 20, and a third starting Aug 7 without an end (yet).
There are several APIs we find in the Integration Repository for 11i dealing with Contingent Workers, Assignments, and changing a Period of Placement, but we can't find any for creating a PDP.
Thank you if you can advise on how to do this.
Skip

Why not use work records in IB messages?

Adding a derived / work record to a message now (tools 8.50) displays the following warning:
Warning - Record TPT_EXP_HDR_WRK is a work record. (158,2758)
The message then displays a "Structure references work records. (158,2759)" warning, for which the explanation is: "Work records should not be used to create rowset-based messages. Use dynamic views instead." The only reference to this I can find in PeopleBooks is:
"Note. Avoid using derived/work records in messages. Work records don't behave like regular records when used with PeopleCode rowset methods. A good alternative is to use dynamic views."
I understand the difference between work records ad regular records, but fail to see why this should preclude their use in messages. Can anyone explain why this is so, and what problems may be encountered by using work records in messages?
Thanks,

Barney, I've seen the error as well and thought it seemed odd, considering that messages don't write to the database. I ignore the warning and use derived/work records anyway. I have not had any problems.
There are generic subscription programs that use the message record name to generate SQL inserts for subscriptions. Of course, if you were to use one of these generic subscription handlers, then you would have problems.

Rehire contingent worker to employee into a different business group

How to rehire contingent worker as an employee to a different business group programatically. I used hr_employee_api.hire_into_job to rehire into the same BG.
Can any one suggest a solution ?
Regards
Thomas

Hi,
I got the answer to my question. We can use the party_id of the existing record in per_all_people_f in the create_person API and pass all the values like business_group_id and other details and the CWK will be rehired as an employee in a different BG.
From PUI, we can hire the CWK into a different BG by entering his last name national_identifier and enter the employee type and save, then there will be a popup showing the EMP/CWk matching the criteria in different BGs and select the appropriate emp/cwk and you can rehire them
Regards
Thomas

Contingent Worker to Perm Employee Bug

Hi,
We are currently encountering a bug where it is not possible to hire an Ex-Contingent Worker.
Once you have ended the contingent workers placement and created the employees employment it is not possible to query back the person (Using a responsibility with no restrictions) in the enter&maintain screen.
If I look at the database, no period of service has been created for the new employee.
What is strange is that I do not encounter this problem if I create a new contingent worker and leave them assigned to the default business group. As soon as I assign the person to a department I encounter this problem.
I find it surprising that something so fundamental (Hiring etc) should be a bug in the software so I am sure it has to be how we have set the product up but any help would be greatly appreciated.
Thanks in advance for any help.

This message for error 289609 is:
"A period of placement does not exist for the specified person on the specified date."
This basically means it doesn't think the person is a Contingent Worker on the date you've specified. What's the Effective Date you're passing in? What does this return:
SELECT current_npw_flag
FROM per_all_people_f
WHERE person_id = <person_id>
AND trunc(<effective_date>) BETWEEN
effective_start_date AND effective_end_date;
This should return 'Y' (not null).

Contingent worker expense claim

Hi,
We are contemplating the following steps to implement contingent worker expense claim process in R12.1.3.
1. Contractor request and PO having a line for expenses ($1000).
2. Contingent worker logs an iExpense claim ($100).
3. The claim gets approved by the supervisor.
4. Next, iExpense claim gets converted to AP invoice for the supplier and not for the contingent worker.
5. AP invoice match to expense line of PO.
6. Validate and Pay the invoice.
Steps 1-3 working fine.
When ever we are trying to export the iExpense claim to AP Invoice by running the program "Expense Report Export", it fails with the rejection reason "Payment Method is invalid". So cannot test step-4 onwards.
Contingent worker is mapped to supplier and PO in the employee setup form.
Can you please advise the probable reason for the rejection.
Thanks,
PS.

Hi,
You can use this query :
SELECT COUNT(*)
FROM per_all_people_f PAPF
WHERE 1 = 1
AND APPS.HR_PERSON_TYPE_USAGE_INFO.GET_USER_PERSON_TYPE(TRUNC(SYSDATE),PAPF.person_id) IN ('Contingent Worker', 'Ex-contingent Worker')
AND TRUNC(PAPF.effective_start_date) between '01-Jan-2011' AND '31-Dec-2011'
AND TRUNC(SYSDATE) BETWEEN papf.effective_start_date AND papf.effective_end_date
This query will also give you Hired and Terminated Contingent Workers between the given dates. If you do not want to add them, remove 'Ex-contingent Worker' from above query.
Hope This will help.
Thanks,
CAH

WANT TO CONVERT LEGACY EMPLOYEES WITH VARIOUS USER_PERSON_TYPES TO CWK TYPE

The implementation began BEFORE the introduction of CWK (Contingent Worker)as a SYSTEM_PERSON_TYPE.
As such, contractors were given a variety of USER_PERSON_TYPES, all logicaly linked to SYSTEM_PERSON_TYPE = EMP.
As part of the upgrade to Rel 12, we wish to convert the people in the system to reflect that they were / are CWK, not EMP.
Note that some of these people have entered Requisitions and PO's. Some are also vendors (for expense
reimbursement).
We wish to convert the EMP's to CWK for the appropriate periods (which we are able to identify.) However, we cannot disconnect from the
various transactions which are linked to these people.
Is there a utility or road-map or setup document that can assist?
TIA!
Sandy

In system terms you would be converting a load of employees to contractors and the ramifications are obvious; any pending transactions would have to be backed out, rolled back in again.
I would bite the bullet on this one and simply convert all your various Emp Variants (i.e., all the true CWKs who are currently EMPs on the system with a user person type) to the system CWK type on a given cut off date some time in the future. And I don't know of a way to do this other than do a mass termination and then create placement. This will sound very unpalateable to you right now but I reckon that if you proceed down a route of changing historical data, you'll hit more unseen problems down the road.
Anyway, interesting question, it would be good if you could relay your findings or outcomes to the forum.

Dynamic rooting (User Record) setting is not working in Nakisa OrgChart SP3

Dear All
The Dynamic rooting setting is not working in the Nakisa OrgChart SP3.
It is giving an error message - "Cannot find the root of your orgchart. The orgchart box may have been deleted or incorrectly specified, or no valid org structure can be found for the selected effective date. Please change the root of the chart or select another effective date."
We followed the same steps as given in the Admin guide of SP3 (P.no. 109 - shown below)
In Orgchart --> General Settings:
* Select the Org chart root value source.
User Record: Retrieves the record specified in the next step from the employee data element.
*Do one of the following to define the org chart root:
If User Record was selected in the previous step, select the field containing the ID of the required organizational object in the employee data element from the User record field drop-down list. For example, if you wish to root the org chart at the org unit of the logged-in user, select the field containing the org unit ID. Hence, we have selected the Org unit ID.
Note:
We had enabled single sign-on with logon tickets
Retained the standard settings in Security Settings --> Employee Source
Had provided full authorization to the roles
If we use the "OrgChart Root" option available in 'Orgchart root value source', the org structure gets displayed correctly from the root object defined.
As this is an standard functionality, Kindly guide us in resolving the issue.
Regards
Ravindra

Ravindra.
You don't have to and shouldn't always include the username and password parameters for the SAP Connection string. When you omit them it will use the user's login credentials.
Remember though that:
The SAPRoleMappingConnection will need them included in order to get the details for the user in the first place.
Without the username and password specified in a connection string you can't click the option to test the connection and result in a successful connection. Remember unable to connect does not necessarily equate to wrongly configured.
I've filtered the log file for errors and the following entries were flagged up:
26 Jun 2012 10:00:06 ERROR com.nakisa.Logger - com.nakisa.framework.utility.Files : deleteFile : java.io.IOException: Unable to delete file: E:\usr\sap\D15\J00\j2ee\cluster\apps\Nakisa\OrgChart\servlet_jsp\OrgChart\root\.system\Admin_Config\__000__THY_SAP_Live_RFC_01\AppResources\attr.txt
26 Jun 2012 13:13:52 ERROR com.nakisa.Logger - com.nakisa.framework.utility.Files : deleteFile : java.io.IOException: Unable to delete file: E:\usr\sap\D15\J00\j2ee\cluster\apps\Nakisa\OrgChart\servlet_jsp\OrgChart\root\.system\Admin_Config\__000__THY_SAP_Live_RFC_01\AppResources\attr.txt
26 Jun 2012 13:43:49 ERROR com.nakisa.Logger - java.lang.reflect.InvocationTargetException
26 Jun 2012 13:55:09 ERROR com.nakisa.Logger - com.nakisa.framework.utility.Files : deleteFile : java.io.IOException: Unable to delete file: E:\usr\sap\D15\J00\j2ee\cluster\apps\Nakisa\OrgChart\servlet_jsp\OrgChart\root\.system\Admin_Config\__000__THY_SAP_Live_RFC_01\AppResources\attr.txt
26 Jun 2012 14:32:03 ERROR com.nakisa.Logger - com.nakisa.framework.utility.Files : deleteFile : java.io.IOException: Unable to delete file: E:\usr\sap\D15\J00\j2ee\cluster\apps\Nakisa\OrgChart\servlet_jsp\OrgChart\root\.system\Admin_Config\__000__THY_SAP_Live_RFC_01\AppResources\attr.txt
26 Jun 2012 15:47:44 ERROR com.nakisa.Logger - BAPI_SAP_OTFProcessor_LinkedDataElement : The dataelement ( SAPPositionVacancyDataElement ) is not defined.
26 Jun 2012 15:47:44 ERROR com.nakisa.Logger - BAPI_SAP_OTFProcessor_LinkedDataElement : while trying to invoke the method com.nakisa.framework.data.Command.getType() of an object loaded from local variable 'p_cmd'
26 Jun 2012 15:47:44 ERROR com.nakisa.Logger - com.nakisa.framework.webelement.charting.data.ChartingData : createNodesFromData : Notes Error: NullPointerException
26 Jun 2012 15:47:44 ERROR com.nakisa.Logger - BAPI_SAP_OTFProcessor_LinkedDataElement : The dataelement ( SAPPositionVacancyDataElement ) is not defined.
26 Jun 2012 15:47:44 ERROR com.nakisa.Logger - BAPI_SAP_OTFProcessor_LinkedDataElement : while trying to invoke the method com.nakisa.framework.data.Command.getType() of an object loaded from local variable 'p_cmd'
26 Jun 2012 15:47:44 ERROR com.nakisa.Logger - com.nakisa.framework.webelement.charting.data.ChartingData : createNodesFromData : Notes Error: NullPointerException
26 Jun 2012 15:47:48 ERROR com.nakisa.Logger - com.nakisa.framework.webelement.charting.data.ChartingData : createNodesFromData : Notes Error: NullPointerException
26 Jun 2012 15:47:55 ERROR com.nakisa.Logger - BAPI_SAP_OTFProcessor_LinkedDataElement : The dataelement ( SAPPositionVacancyDataElement ) is not defined.
26 Jun 2012 15:47:55 ERROR com.nakisa.Logger - BAPI_SAP_OTFProcessor_LinkedDataElement : while trying to invoke the method com.nakisa.framework.data.Command.getType() of an object loaded from local variable 'p_cmd'
26 Jun 2012 15:47:55 ERROR com.nakisa.Logger - com.nakisa.framework.webelement.charting.data.ChartingData : createNodesFromData : Notes Error: NullPointerException
At the very least it looks like SAPPositionVacancyDataElement is missing and whilst the other errors around it are unfamiliar I wonder if it might be a good first step to see if you can track down the reference to and existence of this data element? That being said it looks like your last test occurred well over an hour after this (so you may have already resolved it) and resulted in nothing but information messages. If that is the case it might be worth "rolling" your log file or manually trimming it to the right time frame when posting it? Otherwise it can be misleading as people could flag up issues you have already resolved.
So assuming you haven't tried Luke's suggestion (which should only take a couple of minutes to do) I think you should go back and do so right away .
Regards,
Stephen.

Error while creating Contingent worker by api

we are going to create contingent worker by HR_CONTINGENT_WORKER_API.create_cwk api,but i am unable to create record and getting error "A person type with a system person type CWK must be specified",
Pleae advice,what could be mistake.

You're probably passing the wrong value of the p_person_type_id parameter.
What does this return:
SELECT system_person_type
FROM per_person_types
WHERE person_type_id = <p_person_type_id in API call>;
What's your PLSQL to call the API?

Cannot Update Contingent Worker Number with API when no assignment exists

Hi
I am using hr_person_api.update_gb_person to update Contingent Worker Numbers (NPW_Number in PER_ALL_PEOPLE_F). This works fine apart from one exception. I get the following error: ORA-20001: You cannot enter a Contingent Worker number because you are not creating a Contingent Worker.
The Contingent Worker failing has 4 records in PER_ALL_PEOPLE_F. The 3 date tracked (end dated) records update fine as expected....the new NPW_Number appears in PER_ALL_PEOPLE_F. However, the current active record does not update it returns the error mentioned. This appears to be because the person in question was terminated. (ie via Others and selecting End Placement in the screens).
This person now shows as Ex-Agency Person Type. This process does not generate a record in PER_ALL_ASSIGNMENTS_F. I am wondering if this causes the API some confusion?
I can go into the screen and manually change the Contingent Worker and it saves fine so I would expect the API to do the same. However it returns ORA-20001: You cannot enter a Contingent Worker number because you are not creating a Contingent Worker....for this single record only.
Any suggestions as to what may be causing the API to return this and any workaround please?
Many thanks in advance.

Sometimes APIs are not behaving as Forms do.
An ugly solution in this case could be reverse the termination (hr_ex_employee_api.reverse_terminate_employee), then update the Contingent Worker Number with your API, then terminate him/her again.

Proces not available from Contingent Worker Self Service

HI ,
There is a Oracle given functionality to Hire COntingent Workers called 'Contingent Worker Placements'.
I have added this functionality under Employee and Manager. but when i try to add the same functioanlity under the Contingent Worker Self Service Responsilbility, I get the following error,,
The XXCHR Contingent Placement Mgr function is not available under the Contingent Worker Self Service responsibility
Please help as soon as possoble.
Regards,
Preeti

Now I can see my custom layout... Thanks a lot
Would you please help me also viewing a new comment field..
I did the followings:
* Creating a new context called (NewComment) under the DFF OTL Information Types, It include only one segment called LineComment saved in Attribute1.
I added the following to the ldt file:
# Comment Field
BEGIN HXC_LAYOUT_COMPONENTS "Payroll Timecard Layout - Comments Field"
    OWNER = "ORACLE12.1.0"
    REGION_CODE = "HXC_CUI_TIMECARD"
    REGION_CODE_APP_SHORT_NAME = "HXC"
    ATTRIBUTE_CODE = "HXC_CUI_TIMECARD_COMMENTS"
    ATTRIBUTE_CODE_APP_SHORT_NAME = "HXC"
    SEQUENCE = "190"
    COMPONENT_DEFINITION = "TEXT_FIELD"
    RENDER_TYPE = "WEB"
    PARENT_COMPONENT =
   "Payroll Timecard Layout - Header Table Layout Component"
    ATTRIBUTE1 = "TOP"
    LAST_UPDATE_DATE = "2004/05/24"
    BEGIN HXC_LAYOUT_COMP_QUALIFIERS "Payroll Timecard Layout - Comments Field"
      OWNER = "ORACLE12.1.0"
      QUALIFIER_ATTRIBUTE_CATEGORY = "TEXT_FIELD"
      QUALIFIER_ATTRIBUTE1 = "N"
      QUALIFIER_ATTRIBUTE2 = "Y"
      QUALIFIER_ATTRIBUTE3 = "50"
      QUALIFIER_ATTRIBUTE4 = "3"
      QUALIFIER_ATTRIBUTE5 = "2000"
      QUALIFIER_ATTRIBUTE18 = "EXCLUDE"
      QUALIFIER_ATTRIBUTE19 = "|CSV|"
      QUALIFIER_ATTRIBUTE20 = "N"
      QUALIFIER_ATTRIBUTE21 = "Y"
      QUALIFIER_ATTRIBUTE22 = "R"
      QUALIFIER_ATTRIBUTE25 = "FLEX"
      QUALIFIER_ATTRIBUTE26 = "NewComment" --> the name of the context
      QUALIFIER_ATTRIBUTE27 = "Attribute1"
      #QUALIFIER_ATTRIBUTE28 = "LineComment" --> the name of the segment
      LAST_UPDATE_DATE = "2004/05/24"
    END HXC_LAYOUT_COMP_QUALIFIERS
END HXC_LAYOUT_COMPONENTS
the file uploaded successfully but i can not see any changes, no comment shown?!!

I have the converter to change pdf to word. Works sometime, other time says conversion is taking too long. Can I get what it has translated so I can use the parts?

I have the converter to change pdf to word. Works sometime, other time says conversion is taking too long. Can I get what it has translated so I can use the parts?

I would ask in the ExportPDF forum, Adobe ExportPDF (read only) (assuming that's the service to which you have subscribed). This is the Reader one.

FORM RUNTIME record=collect is not working.

Hi
FORM RUNTIME record=collect is not working which is set to user level.what to do?
rgrds

Pl post details of OS and EBS versions, along with the complete steps you took to enable this profile option. What does "not working" mean ?
MOS Doc 438652.1 - R12: Forms Runtime Diagnostics (FRD), Tracing And Logging For Forms In Oracle Applications
HTH
Srini

OTL: Purchasing timecard attributes for Contingent worker

Hi,
I am trying to create a timecard for a Contingent worker (a purchasing timecard).
Using the APIs, I am able to create the timecard in the specific template (having PO NUmber & PO Line Number).
But the issue I am facing is :
All the fields are getting populated (project, task, line number), but the 'PO Number' & 'Type' are not getting populated.
hxc_timestore_deposit.create_attribute(p_building_block_id => l_detail_bb_st_id,
p_attribute_name => 'Expenditure_Type',
p_attribute_value => 'Contract Performance Manager',
p_deposit_process => 'Projects Deposit Process',
p_app_attributes => l_tbl_attributes_info);
hxc_timestore_deposit.create_attribute(p_building_block_id => l_detail_bb_st_id,
p_attribute_name => 'PO Price Type',
p_attribute_value => 'Standard Rate',
p_deposit_process => 'Projects Deposit Process',
p_app_attributes => l_tbl_attributes_info);
hxc_timestore_deposit.create_attribute(p_building_block_id => l_detail_bb_st_id,
p_attribute_name => 'PO Header Id',
p_attribute_value => P_PO_HEADER_ID,
p_deposit_process => 'Projects Deposit Process',
p_app_attributes => l_tbl_attributes_info);
hxc_timestore_deposit.create_attribute(p_building_block_id => l_detail_bb_st_id,
p_attribute_name => 'PO Line Id',
p_attribute_value => P_PO_LINE_ID,
p_deposit_process => 'Projects Deposit Process',
p_app_attributes => l_tbl_attributes_info);
* PO Line number is getting populated correctly.
Please help !!!
Thanks,
Sambit

Did you change the Application set to Proj and Payroll? Also can you put a description of what exactly you want to do with respect to payroll element so that we can gauge the exact layout and setup required.
--Shiv

Use the sales employee, you need an HR master record

hi:
when I do vpe1 in sd model ,it prompt two transport request .
In order to use the sales employee, you need an HR master record. If you do not use the Human Resources application component (HR), you can transport the HR tables that you need for creating, changing or displaying a sales employee from client 000 into the target client.
How should i do?

I'm moving this thread to the SD forum.... This is a funtional issue not a technical one.
Regards
Juan

Convert an Employee record to a Contingent worker record

Similar Messages

Maybe you are looking for