Could any one tell me the steps of conversions and what kind of validations an

Could any one tell me the steps of conversions and what
kind of validations and exceptions do we use during this
conversion? Please do answer in detail.

what program do we write in user exit in reports?

Question Posted / rahamathulla

3 Answers
18510 Views
iGate, I also Faced
E-Mail Answers

Answers were Sorted based on User's Feedback

Could any one tell me the steps of conversions and what kind of validations and exceptions do we u..

Answer / vans

The above posted details are perfect.

Here to load the data from legacy system to your staging
table you can use SQL LOADER.

Once loaded to the table run the package to do the required
validations.

We can use two approaches to load the data into base table.
1)Using open interface
2)Use API.

1)Using open interface
We need to place the validated date from staging table to
standard interface table and then run the standard
interface program to place the data in Base table

2)Use API

In this case we do not use interface table.We take the data
from staging table validate and call the standard API which
will place the data into base table.

Here, to the API we need to pass the required IN parameter
from the staging table once it being validated.

For example in HRMS the employee conversion we can call the
below API to create employee
hr_employee_api.create_us_employee

Is This Answer Correct ?

12 Yes

2 No

Could any one tell me the steps of conversions and what kind of validations and exceptions do we u..

Answer / nagaraju chittamsetty

Hi to all,
Conversion is one of the important RICE components.It is
one time process.
The main use of conversion transfer the data from legecy
systems to oracle base tables,To do this we need to follow
some steps.

Example take Purchasing(import standard purchase orders):

1.First take the legecy data(.csv or .dat or .txt etc) file
2.create the stagging table/temparary table based on the
interface table.
3. Create the package and run the package based on the
functional document and insert any errors into the errors
table(i.e.custom validation errors)
4.After running the package data transfered from stagging
table to respective interface tables,In purchasing module
interface tables arepo_headers_interface,po_lines_interface
and po_distributuions_interface.
5.Once data inserted into interface tables then run the
standard concurrent program which is already provided by
oracle apps.
6.Once we run the import standard purchase orders then data
is transferred into respective base tables,if any errors
occured in processing time those errors are stored into
po_interface_errors table.

I think it will give good idea on conversion of standard
purchase orders.If any clarifications and suggestions send
feed back to csnraja@gmail.com

Regards,
Nagaraju.ch

Is This Answer Correct ?

11 Yes

2 No

Could any one tell me the steps of conversions and what kind of validations and exceptions do we u..

Answer / prasad reddy

Hi,
In Oracle apps if you want to load data from legacy
system to Oracle application we go for conversion, if it is
one time process.

The following steps must be followed.

Load data from flat file to staging tables ( temp tables )
then write your own package or procedure to populate the
interface table.

Then finally you can run oracle seeded program to populate
the base table.

ex
----

Interface tables

MTL_SYSTEM_ITEMS_INTERFACE
MTL_ITEM_REVISIONS_INTERFACE
MTL_ITEM_CATEGORIES_INTERFACE

Base tables

MTL_SYSTEM_ITEMS_B
MTL_CATEGORIES_B
MTL_ITEM_REVISIONS_B

Concurrent program name is -> import items

Error table
------------
MTL_INTERFACE_ERRORS

Validations
-------------
Organization Code

SELECT organization_code
INTO l_organization_code
FROM org_organization_definitions
WHERE organization_code =
cur_rec.organization_code;

Inventory Org Id

SELECT organization_id
INTO l_organization_id
FROM mtl_parameters
WHERE organization_code = l_organization_code;

To check whether item is already exits

SELECT COUNT (*)
INTO l_item_count
FROM mtl_system_items_b
WHERE segment1 = cur_rec.segment1
AND organization_id = l_organization_id;

Item Type

IF cur_rec.item_type IS NOT NULL
THEN
SELECT lookup_code
INTO l_item_type
FROM fnd_common_lookups
WHERE lookup_type = 'ITEM_TYPE' AND meaning =

cur_rec.item_type;

very mandatory
mtl_system_items_interface
(
process_flag,
transaction_type,
item_number,
description,
organization_id,
set_process_id)
VALUES
(1,
'CREATE', or update
'Rev_hist_test', ----item_number
'IOI Revision Part', ----description
204,
1
);

I think the explanation could help you.

Regards,
-prasad