FNDLOAD lcts for User Tables, EIT Definitions, Elements

Question

Hi,
Can someone point me to lcts for the following :
1. HRMS user tables (structure and values)
2. EIT definition and values (Generic one or particular to Life Event Extra information)
3. Element and element link definitions.
Regards.

Answer 1

Hi Vinayak,
We wrote our own custom LCT file to migrate Links. iSetup doesn't provide migration for element links.
Ofcourse - you may need to edit the API call as we needed few segments to migrate.
# $Header: ele_links.lct 1.0.0.0 2007/01/18 12:41:05 appldev ship $
# links.lct - LINK loader file
# -- DEFINE SECTION --
# Entities:
# LINK_INFO
# Parameters:
# BUSINESS_GROUP_ID
# ELEMENT_NAME
DEFINE LINK_INFO
KEY BUSINESS_GROUP_ID VARCHAR2(100)
KEY ELEMENT_NAME VARCHAR2(100)
BASE ELEMENT_BG_ID VARCHAR2(100)
BASE ELEMENT_LEG_CODE VARCHAR2(100)
BASE BUSINESS_GROUP_NAME VARCHAR2(100)
BASE EFFECTIVE_START_DATE VARCHAR2(100)
BASE EFFECTIVE_END_DATE VARCHAR2(100)
BASE COSTABLE_TYPE VARCHAR2(100)
BASE LINK_TO_ALL_PAYROLLS_FLAG VARCHAR2(100)
BASE MULTIPLY_VALUE_FLAG VARCHAR2(100)
BASE STANDARD_LINK_FLAG VARCHAR2(100)
BASE TRANSFER_TO_GL_FLAG VARCHAR2(100)
BASE COSTING_SEGMENT11 VARCHAR2(100)
BASE BALANCING_SEGMENT11 VARCHAR2(100)
END LINK_INFO
# -- DOWNLOAD SECTION --
# For each entity, specify the SQL statement to use to flesh out
# its entity definition. SELECT columns must be in same order and
# datatype as the entity's attributes as defined above.
# Convert dates to varchar2 using:
# to_char(sysdate, 'DD/MM/YYYY')
# Protect against null parameter passing using
# and (:parm is null or (:parm is not null and col like :parm))
# -- DOWNLOAD SECTION --
# For each entity, specify the SQL statement to use to flesh out
# its entity definition. SELECT columns must be in same order and
# datatype as the entity's attributes as defined above.
# Convert dates to varchar2 using:
# to_char(sysdate, 'DD/MM/YYYY')
# Protect against null parameter passing using
# and (:parm is null or (:parm is not null and col like :parm))
DOWNLOAD LINK_INFO
"select l.business_group_id, t.element_name,
t.business_group_id element_bg_id,
t.legislation_code element_leg_code, b.name business_group_name,
'1900/01/01 00:00:00' effective_start_date,
fnd_date.date_to_canonical(l.effective_end_date),
l.costable_type, l.link_to_all_payrolls_flag, l.multiply_value_flag,
l.standard_link_flag, l.transfer_to_gl_flag,
c.segment11 cost_seg11, bc.segment11 balance_seg11
from pay_element_links_f l, per_business_groups b, pay_element_types_f t,
pay_cost_allocation_keyflex c, pay_cost_allocation_keyflex bc
where l.business_group_id = :BUSINESS_GROUP_ID
and l.business_Group_id = b.business_group_id
and l.element_type_id = t.element_type_id
and t.element_name = nvl(:ELEMENT_NAME, t.element_name)
and trunc(sysdate) between t.effective_start_date
and t.effective_end_date
and l.cost_allocation_keyflex_id = c.cost_allocation_keyflex_id(+)
and l.balancing_keyflex_id = bc.cost_allocation_keyflex_id(+)"
# -- UPLOAD section --
# For each entity, specify the pl/sql block to use to upload the
# entity into the database. Bind names must match DEFINE attribute names.
# If the relevant tables have table handlers defined, use the LOAD_ROW
# procedure.
# Non-leaf entities must include the BEGIN keyword.
# Child entities may use bind names from their parents' definitions.
# Use command line parameters to control branching between desired behavior.
# For example, in the upload statement below, we use the parameter
# UPLOAD_MODE to specify whether we are doing a regular upload or a
# special upload of translated columns.
UPLOAD LINK_INFO
" Declare
l_tmp NUMBER;
cursor link_csr (p_bg_id NUMBER, p_et_id NUMBER) is
select element_link_id
from pay_element_links_f
where business_group_id = p_bg_id
and element_type_id = p_et_id;
cursor elem_csr (p_bg_id NUMBER, p_el_nm VARCHAR2) is
select element_type_id
from pay_element_types_f
where ((:ELEMENT_BG_ID IS NULL AND
legislation_code = :ELEMENT_LEG_CODE)
or (:ELEMENT_BG_ID IS NOT NULL AND
business_group_id = p_bg_id))
and element_name = p_el_nm;
l_bg_id NUMBER;
l_et_id NUMBER;
l_link_id NUMBER;
l_ed DATE;
l_esd DATE;
l_eed DATE;
l_comment_id NUMBER;
l_ovn NUMBER;
l_warn BOOLEAN;
l_cost_segs VARCHAR2(1000);
l_bal_segs VARCHAR2(1000);
Begin
l_bg_id := 456; --- Either hard code this or pass it as parameter...
open elem_csr (l_bg_id, :ELEMENT_NAME);
fetch elem_csr into l_et_id;
If elem_csr%NOTFOUND Then
Close elem_csr;
raise_application_error(-20001, 'Unable to find Element Name: ' ||
:ELEMENT_NAME);
End If;
Close elem_csr;
open link_csr(l_bg_id, l_et_id);
fetch link_csr into l_link_id;
If link_csr%NOTFOUND Then
close link_csr;
l_ed := fnd_date.canonical_to_date(:EFFECTIVE_START_DATE);
pay_element_link_api.create_element_link
(p_effective_date => l_ed
,p_element_type_id => l_et_id
,p_business_group_id => l_bg_id
,p_costable_type => :COSTABLE_TYPE
,p_link_to_all_payrolls_flag =>
:LINK_TO_ALL_PAYROLLS_FLAG
,p_standard_link_flag => :STANDARD_LINK_FLAG
,p_transfer_to_gl_flag => :TRANSFER_TO_GL_FLAG
,p_cost_segment11 => :COSTING_SEGMENT11
,p_balance_segment11 => :BALANCING_SEGMENT11
,p_cost_concat_segments => l_cost_segs
,p_balance_concat_segments => l_bal_segs
,p_element_link_id => l_link_id
,p_comment_id => l_comment_id
,p_object_version_number => l_ovn
,p_effective_start_date => l_esd
,p_effective_end_date => l_eed);
l_eed := fnd_date.canonical_to_date(:EFFECTIVE_END_DATE);
If l_eed != to_date('31-DEC-4712', 'DD-MON-YYYY') Then
l_ed := l_eed;
pay_element_link_api.delete_element_link
(p_effective_date => l_ed
,p_element_link_id => l_link_id
,p_datetrack_delete_mode => 'DELETE'
,p_object_version_number => l_ovn
,p_effective_start_date => l_esd
,p_effective_end_date => l_eed
,p_entries_warning => l_warn);
End If;
Else
dbms_output.put_line('Link already exists for element: ' || :ELEMENT_NAME);
End If;
End; "
Edited by: vaibhav468 on Sep 28, 2009 4:44 PM