Beruflich Dokumente
Kultur Dokumente
1|Page
Scope for this Document
Oracle Enterprise Asset Management (eAM) is part of Oracle’s-Business Suite and
addresses the comprehensive and routine asset maintenance requirements of asset
intensive organizations.
Oracle Advanced Supply Chain Planning (ASCP) provides capabilities including
Inventory planning, Collaborative planning, and Supply chain material and resources
planning.
This document outlines the integration technical concept between Oracle Enterprise
Asset Management and Oracle Advanced Supply Chain Planning
Data Collection is a process that pulls data from designated data sources into its
planning data store. The Data collection process consists of the ‘pull process’ and
‘Operational Data Store (ODS) load process.
Data Collection programs move data from the source instance into staging tables where
Data integrity is checked before being loaded into APS instances Operational Data
store.
Pull Data programs move the data from the staging tables to the APS instances
Operational Data store
Additionally, there are some views created on the snapshot synonyms which are used
in the data collections process to load the data from the source instance into the ‘MSC
staging’ tables. In this example, there are two views that are used to load the Bill of
Material data into the staging tables.
Six different processes comprise the structure of Data Collection process. Each of these
processes are launched during the Data collection run.
2|Page
CONCURRENT PROGRAM SHORT NAME
Planning Data Pull MSCPDP
Refresh Snapshot MSRFWOR
Planning Data Pull Worker MSCPDPW
Planning ODS Load MSCPDC
Planning ODS Load Worker MSCPDCW
Planning Data Collection –Purge Staging MSCPDCP
tables
3|Page
3-Collections types: Complete, Net Change and Targeted
Refresh
Complete Refresh replaces all data for the entity, with a few exceptions:
Targeted Refresh is used to collect one of more entities in complete refresh mode. This
is very useful to synching data for certain business purposes, or collecting certain setup
data, or quick collection for setting up a test case.
Examples:
a. This can only be run for transactional entities, like WIP, PO, OM
and some setup entities like, Items, BOM, etc..
b. If you set parameter Yes for a setup entity - like ATP Rules - it is
ignored when running Net Change collections
4|Page
4-ASCP/EAM Business process
In the above diagram it is indicate that the first point of integration between the ASCP
and EAM is the collection and in order to attain the above design goals, the following
changes are required to the Collections program:
To add a new entity eAM forecasts
Slight modifications of existing collections code
To Support net change collections, we create snapshots on the following tables
MTL_EAM_ACTIVITY_ASSOCIATIONS
MTL_EAM_FORECAST_WDJ
MTL_EAM_FORECASTS
5|Page
BOM and activity routing containing the materials and resources needed for
operations, respectively
The Items of type(Eam_item_type) Asset Activity, Asset group ,rebuild able are
already getting collected as a part of Items collections
The Maintenance BOM and Routings , Resources are also getting collected as a
part of std Collection of BOM, routings
We need to collect the AssetGroup, Asset Number, Activity Associations
1-MSC_CL_ITEM_PULL.LOAD_ITEM
2-LOAD_ACTIVITY_ASSOCIATIONS
1. Msc_boms.repairable. This will be set to 1 for all “activities of the type “rebuild”
2. Msc_supplies.produces_to_stock. All the eAM work orders for the “rebuild” activity
type will have the
produces_to_stock updated to 1.
6|Page
This will be done by the Main Planning ODS load program when all the entities are
loaded
eAM utilizes the WIP_DISCRETE_JOBS table to store their work orders. The eAM work
orders are identified by a value of 1 in the column
WIP_DISCRETE_JOBS.MAINTENANCE_OBJECT_SOURCE.
The work orders can be rebuild work orders ( independent , child) and asset work
orders
On Asset work orders the primary_item is asset group
On rebuild work orders the primary Item is rebuilable_item
Collection will bring in all the existing eAM, work orders into msc_supplies
in order to collect the EAM Production Work orders some changes has been done
Changes to snapshot WIP_DSCR_JOBS_SN
Modify the Snap shot definition of WIP_DSCR_JOBS_SN, to add the following columns
Asset_class_code WDJ.Class_code
Shutdown_type wdj. SHUTDOWN_TYPE
Activity_type wdj.activity_type
7|Page
7-Collection of eAM Forecasted Work orders
In order to collect the EAM Forecast work orders some changes has been done as
following :
MTL_EAM_FORECAST_WDJ_SN
MTL_EAM_FORECASTS_SN
New Views
MSC_AP_EAM_Forecasts_V
MSC_AP_EAM_FORECAST_DESIGS_V
Procedure LOAD_EAM_FC will pull data from the_AP_ view into the staging
table
The forecast_name will be populated into MSC_ST_SUPPLIES. DESIGNATOR
8|Page
8-Collection Parameter Changes
9|Page