conversions

Knowledge Management for Employees Conversion in 11.5.10

1 Responsibility / Navigation / Module
US HRMS Manager

2 Conversion Approach / Reference Documents
Application Program Interface (API)/ Oracle Application developers guide

3 Application Setup Requirements
N/A

4 Assumptions / Prerequisites / Validations
Organization Name, Job Name, Location Code, User Status, Position Name, Concatenated Segments, User Person Type, GL code combination mapping must be available.

5 Base Tables Effected
1. PER_ALL_PEOPLE_F
2. PER_ADDRESSES
3. PER_ALL_ASSIGNMENTS_F
4. PER_PAY_PROPOSALS
5. PER_SPECIAL_INFO_TYPES
6. PER_ANALYSIS_CRITERIA

6 Interface Tables / APIs
1. HR_EMPLOYEE_API
2. HR_PERSON_ADDRESS_API
3. HR_ASSIGNMENT_API
4. HR_UPLOAD_PROPOSAL_API
5. HR_SIT_API

7 Navigation of Import Program & Parameters
Direct Insert by executing the main procedure of the package

Knowledge Management for Attachments conversion in 11.5.10

1 Responsibility / Navigation / Module
Application Developer

2 Conversion Approach / Reference Documents
Direct insert/ Oracle Application developers guide

3 Application Setup Requirements
N/A

4 Assumptions / Prerequisites / Validations
ITEMS,
BOMS,
OE_ORDER_HEADERS,
OE_ORDER_LINES,
PO_HEADERS,
PO_LINES,
AR_CUSTOMERS and AP_INVOICES.
Operating unit mappings must exist.

List of validations:

FND_ATTACHED_DOCUMENTS
1. Organization_code
2. Item number
3. Assembly item number
4. Bill sequence id
5. Org name
6. Order number (Sales)
7. Order line number (Sales)
8. Purchase order number
9. Purchase order line number
10.Custoemr name
11.Customer number
12.Customer type
13.Invoice number

FND_DOCUMENTS
14.Document data type
15.Document category

FND_DOCUMENTS_TL
16.Language
17.Source language

5 Base Tables Effected
FND_DOCUMENTS_SHORT_TEXT
FND_DOCUMENTS_LONG_TEXT
FND_DOCUMENTS_LONG_RAW
FND_LOBS
FND_DOCUMENTS
FND_DOCUMENTS_TL
FND_ATTACHED_DOCUMENTS

6 Interface Tables / APIs
N/A

7 Navigation of Import Program & Parameters
Direct Insert by executing the main procedure of the package

Knowledge Management for AP Invoices conversion in 11.5.10

1. Responsibility / Navigation / Module
Payables manager

2. Conversion Approach / Reference Documents
Interface Tables / AP Invoices User Guide

3. Application Setup Requirements
N/A

4. Assumptions / Prerequisites / Validations
Vendors, GL code combinations, purchase Order should be created.
Required Columns validations
1. Organization id (org_id)
2. Vendor name (vendor_name)
3. Vendor site code (vendor_site_code)
4. Ap terms (terms_name)
5. AWT group name
6. Invoice number (invoice_num)
7. Invoice type lookup code
8. Accts pay code combination (accts_pay_code_combination_id)
9. Payment method lookup code
10. Code combination id
11. Item number
12. Invoice id
13. Line type lookup code
14. Tax code
15. PO Distributions

5. Base Tables Effected
AP_INVOICES_ALL
AP_INVOICES_DISTRIBUTIONS_ALL

6. Interface Tables / APIs
AP_INVOICES_INTERFACE
AP_INVOICE_LINES_INTERFACE

7. Navigation of Import Program & Parameters
Others =>request=>run => ‘payable open interface import’
Parameter
1 => Source
2 => Batch source name

8. Import Errors
AP_INTERFACE_REJECTIONS

Knowledge Management for Sales Order conversion in 11.5.10

1. Responsibility / Navigation / Module
Order Management Super User (or ) OM US Super User

2. Conversion Approach / Reference Documents
Interface Tables / Order Management User Guide

3. Application Setup Requirements
Printer need to be assigned.

4. Assumptions / Prerequisites / Validations
Customers,Items, Price list should be exist.

5. Base Tables Effected
OE_ORDER_HEADERS_ALL
OE_ORDER_LINES_ALL

6. Interface Tables / APIs
OE_HEADERS_IFACE_ALL
OE_LINES_IFACE_ALL
OE_ACTIONS_IFACE_ALL

7. Navigation of Import Program & Parameters
Orders,Returns => Import Orders =>Order Import Requests

Order Source
Order Reference
Validate Only =>No
Instances
Change Sequence
Trim Trailing Blanks=>No

Knowledge Management for Purchase Order conversion 11.5.10

1. Responsibility / Navigation / Module
Purchasing US Super User / Purchase Orders / Purchase Orders

2. Conversion Approach / Reference Documents
Interface Tables / Oracle Manufacturing APIs and Open Interfaces

3. Application Setup Requirements
Buyer must be set up so that Po’s can be approved.

4. Assumptions / Prerequisites / Validations
Items, Suppliers, Organizations, Locations, Supplier Sites, Operating Unit, Buyers mapping must be available / Required Columns Validations.

5. Base Tables Effected
PO_HEADERS_ALL
PO_LINES_ALL
PO_LINE_LOCATIONS_ALL
PO_DISTRIBUTIONS_ALL

6. Interface Tables / APIs
PO_HEADERS_INTERFACE
PO_LINES_INTERFACE
PO_DISTRIBUTIONS_INTERFACE

7. Navigation of Import Program & Parameters
Two Different Import Programs are used based on the Po Type.

i. Incase of ‘Standard Purchase Orders’, the Import Program used is ‘Import Standard Purchase Orders’.
Navigation:
Purchasing US Super User => Purchase Orders => Reports => Run => Import Standard Purchase Orders.
Parameters:
Default Buyer (Optional)
Create or Update Item (Required)
Approval Status (Required)
Batch Id (Optional)

ii. Incase of ‘Blanket Purchase Agreements ‘, the Import Program used is ‘Import Price Catalogs’.
Navigation:
Purchasing US Super User => Purchase Orders => Reports => Run => Import Price Catalogs.
Parameters:
Default Buyer (Optional)
Document Type (Required)
Document Sub Type (Optional)
Create or Update Item (Required)
Create Sourcing Rules (Required)
Approval Status (Required)
Release Generation Method (Optional)
Batch Id (Optional)

8. Import Errors
PO_INTERFACE_ERRORS