: 
MP4 | Video: h264, 1280x720 | Audio: AAC, 44.1 KHz, 2 Ch
Genre: eLearning | Language: English + srt | Duration: 5 lectures (3h 59m) | Size: 1.94 GB
Oracle EBS R12 Technical - Item Conversion Using Interface Table method complete flow
What you'll learn
Oracle Apps Technical
Oracle EBS Technical
Order to Cash Cycle in Oracle Apps
Procure to pay cycle in oracle Apps
Requirements
Oracle SQL and PLSQL
Description
Item import program can be used to create new Inventory items or to update existing inventory items. We can import items with all attributes information or use item templates to set attributes and import items linking with item template.
Uses
Import New Inventory Items in Master Organization
Assign Items to child Organization (Step1 has to be finished before this task can be executed)
Update existing Inventory item attributes information
Assign Item Category Assignments
Lot numbers can be imported along with items
Serial numbers can be imported along with items
Execution Methods
Run "Import Items" concurrent program from inventory responsibility manually.
Use PLSQL wrapper code to kick of the "Import Items" Concurrent program from backend.
Parameters
All Organizations: Yes / No (Select Yes if you want to import items belonging to various organizations reglardless of current selection in form)
Validate Items: Yes / No (Select Yes if you would like to validate Items. With out validation we can not proceed to Processing)
Process Items: Yes / No (Select Yes to process / import items)
Delete Processed Items: Yes / No (Select Yes to purge data in interface tables for the processed records)
Process Set: You can use this parameter to process records in batches. It will use SET_PROCESS_ID column in interface table.
Create or Update Items: 1 / 2/ 3. (1- Create New Items, 2 - Update Existing Items, 3 - Sync Items. Option 3 should be used if we have some items to be created and some to be updated)
Gather Statistics: Yes / No. (Helps to increase performance of SQL queries based on items table)
Pre-requisites
Master Organization should be defined.
Child Organization should be defined.
Code Combinations should be defined.
Item Templates (If using item templates in interface table)
Defining Item Status Codes
Item Types should be defined.
Issues
Don't try to load both master item record and child item record at a time. If you want to do that make sure you use process set column.
Revision numbers have to be in chronological order, meaning it can be like AA, BB, CC ... or 1,2,3,....but i can't be AA, 1, BB, 2 etc.
Category assingments, Lot numbers, serial numbers has to be linked properly to the respective tables.
Interface tables
MTL_SYSTEM_ITEMS_INTERFACE
MTL_ITEM_REVISIONS_INTERFACE (If importing revisions)
MTL_ITEM_CATEGORIES_INTERFACE (If importing categories)
Error Tables
MTL_INTERFACE_ERRORS (View errors after import)
Base tables
MTL_SYSTEM_ITEMS_B
MTL_ITEM_REVISIONS_B
MTL_CATEGORIES_B
MTL_CATEGORY_SETS_B
MTL_ITEM_STATUS
MTL_ITEM_TEMPLATES
Who this course is for
Oracle Apps Technical
Homepage
https://www.udemy.com/course/oracle-apps-r12-technical-item-conversion/Buy Premium From My Links To Get Resumable Support,Max Speed & Support Me
Links are Interchangeable - No Password - Single Extraction