Вы находитесь на странице: 1из 51

Technical Workshop Data Collection

o adf data transform and moves the data from the staging tables to the ODS. This collection program is a registered AOL concurrent program that could be scheduled and launched by the system administrator.

ATP Data adfasdfdafd Order in Destination and collects all the new Sales Order data and all the enities set Y S. !et "hange #efresh$ "ollects the changes for the Sales Order. ATP DATA MSCATPDP PULL PLANNING MSCPDC ODS LOAD MSCCLFAB.PLS MSCCLBAB.PLS MSC_CL_PULL.LAUNCH_MONITOR MSC_CL_COLLECTION.LAUNCH_MONITOR

Continuous collections p ocess% The continuous collections process is an automated process of data collection that efficiently synchroni&es the data on the planning server by loo'ing up the sources. (f you opt for continuous collections) the system automatically determine the type of collection that needs to be run on entities selected by you. The continuous collections process collects data from the sources with the least user intervention. The "ontinuous "ollections concurrent program performs continuous collections. Adfasdfasdfasd'fupioasdup*f+*lasdhfo,uaelr+nlasnerlnlnl entities. -or entities with snapshots) "ontinuous "ollections chooses net change refresh or targeted refresh based on the e.tent of changes to the entity data /since the last collection0 relative to a concurrent program parameter called Snapshot Threshold /10. (f the e.tent of changes is within the Snapshot Threshold /10) then "ontinuous "ollections invo'es net change refresh for the entity* otherwise it invo'es targeted refresh. (t thus employs the net change refresh mechanism only when it is computationally advantageous to do so. -or entities without snapshots) "ontinuous "ollections always chooses targeted refresh. These entities are typically setup entities such as calendars) demand classes) customers and suppliers that are not updated as fre2uently as entities with snapshots. You would typically schedule "ontinuous "ollections to run fre2uently for supply3demand transactions with snapshots /to ta'e advantage of net change collection of information from the transaction source instance to the planning server0 and less fre2uently for setup entities.

ASCP- Data Collection 1/51

"ontinuous collections aims to combine the benefits of targeted and net$change collections) and allows certain entities to be collected in a complete /targeted0 manner and others in a net$change manner. The system ma'es the determination of the mode to collect an entity in. The motivation for doing this is to be able to 'eep the data in the APS tables as close to the data in the source #P tables) as well as to achieve this synchrony in an efficient manner. The continuous collections feature provides the following functionality% Ability to indicate the entities to be mar'ed for continuous collection) System figures out the appropriate collection mode of complete /targeted0 or net$change for that entity. Ability to schedule the continuous collections as a separate concurrent program) which runs periodically. "ontinuous collections thus provide the ability to bring in the latest transactional data /supplies and demands0 to the planning tables in an efficient and non$obtrusive manner) with little user intervention. AUTOMATIC MSCAUTP MSCCLFAB.PLS COLLECTION MSC_CL_PULL.LAUNCH_MONITOR_CONT

A!!ition"l P" "#ete s $o Continuous Collection Sn"ps%ot T% es%ol! &'( -or entities that have a snapshot associated with the source of that entity) it will be possible to determine whether to do a targeted or net$change collections. This is done by comparing the counts of records in the snapshot and the snapshot log% Let a be the count of new records in the snapshot log since the previous run of collections /actually) it will be since last refresh of the snapshot0) and b the count of records in the snapshot. E)"#ple Suppose the Snapshot Threshold 1 is set to 45 1. /threshold = 400
select count(*) from MLOG$_BOM_BILL_OF_MATERIAL; COU T(*) !!!!!!!!!! "#$ a % "#$ select count(*) from BOM&BOM_BOM'_' ; COU T(*) !!!!!!!!!! ()* b % ()* +f a = 0 t,en -on.t /o Collect+on for t,0t 10rt+cul0r ent+t2& els+f ((a/b)*100) 3 threshold T,+s me0ns t,0t t,e c,0n4es +n t,e 50se t05le +s more t,0n t,e t,res,ol/ 1ercent04e 0n/ so +t +s 5etter off to /o 0 T0r4ete/ Collect+ons for t,+s ent+t2& T,e Cont+nuous Collect+on 6+ll /o 0 t0r4ete/ collect+on& else -o net!C,0n4e refres, for t,+s ent+t2& en/ +f

ASCP- Data Collection 2/51

threshold will be a parameter in 1) settable by the user. The threshold determines when it will be efficient to simply collect all the rows from the snapshot versus when it will be efficient to only collect the changed rows using the snapshot log. (f continuous collections are run fre2uently) then for most entities /which have snapshots0) we will collect them in net$change mode. T" *ete! F e+uenc, &Hou s( -or entities that do not have any snapshots associated with the source tables of that entity) it will not be possible to do net$change collections. -or these entities) the targeted mode will be selected. The fre2uency parameter specified by the user will determine how fre2uently these entities will be collected in targeted mode. Define two separate schedules for collections. One scheduled to run almost continuously collecting data entities which have snapshots associated with them li'e 6(P) items) transactions etc. Another program scheduled to bring setup entities that do not have snapshot associated to them li'e customers) suppliers) sourcing rules etc. scheduled to run periodically.

ASCP- Data Collection 3/51

DEFINITI NS
O "cle Applic"tions D"t" Sto e &ADS( #epresents all the source data tables used to build and maintain the planning data store within Oracle AS"P. (t represents a single source data instance. .g. transaction system /Source (nstance0 MR7_A7_888 MR7_' _999_Tn MR7_A-_999 MR7_A-_999 'ource tr0ns0ct+on t05les 'n01s,ot tr+44ers 7l0nn+n4 source tr0ns0ct+on t05les 7l0nn+n4 source 1l0nn+n4 t05les

#ows are populated in the 7#P8AD8... and 7#P8AP8... tables by database triggers /7#P8S!8...8Tn0 defined on the corresponding database snapshots /...8S!0. This activity occurs on the source instance. Ope "tion"l D"t" Sto e &ODS( Part of Oracle AS"P that represents all the planning data tables that act as destination for the collected data from each of the data sources /both ADS and Legacy0. This acts as the input for the snapshot portion of the planning process. ODS and PDS share the same physical tables where a special plan identifier /for e.ample) $90 is used for distinction. Pl"nnin* D"t" Sto e &PDS( #epresents all the tables within Oracle AS"P which encompass those in the ODS and other output tables from planning) including copies3snapshots of the input data used for the current planning run striped by the appropriate plan identifier. Collection -o ./enc% "ollection 6or'bench is a centrali&ed data repository providing collected data from the source. Data from different source instances can be viewed using the "ollection 6or'bench. The functionality here is similar to the Planner 6or'bench functionality. The collection wor'bench is used to verify that the intended data has been collected : (f necessary) troubleshoot errors in data collection and rerun the data collection program. 0e, T "ns$o #"tion To trac' data entities bac' to the source instance) APS transforms each uni2ue business entity into a uni2ue (D within APS. After the source data is transformed) the LID tables stay intact even during a complete refresh. ;ey transformation is two step process The first step is to generate the local (D for the new source 'ey) which does not e.ist in the mapping tables. The second step is to transform the source (D to the local (D. ;ey transformation is provided for (nternal (tem !umbers and following business entities "ategory Sets Suppliers Suppliers Sites "ustomers "ustomers Sites

ASCP- Data Collection !/51

0e, T "ns$o #"tion E)e cise


MSC_CATEGORY_SET_ID_LID (MSC_CATEGORY_SETS) /esc M'C_CATEGOR:_'ET_I-_LI0me ull; T21e !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!! !!!! 'R_CATEGOR:_'ET_IOT ULL UMBER 'R_I 'TA CE_IOT ULL UMBER CATEGOR:_'ET_IOT ULL UMBER MSC_COMPANY_ID_LID (MSC_COMPANIES)

/esc M'C_COM7A :_I-_LI0me ull; T21e !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!! !!!! 'R_COM7A :_IOT ULL UMBER 'R_I 'TA CE_IOT ULL UMBER COM7A :_IOT ULL UMBER 7ART ER_T:7E OT ULL UMBER MSC_COMPANY_SITE_ID_LID (MSC_COMPANY_SITE_ID_LID) /esc M'C_COM7A :_'ITE_I-_LI0me ull; T21e !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!! !!!! 'R_I 'TA CE_IOT ULL UMBER 'R_COM7A :_IOT ULL UMBER 'R_COM7A :_'ITE_IOT ULL UMBER COM7A :_'ITE_IOT ULL UMBER 7ART ER_T:7E OT ULL UMBER MSC_ITEM_ID_LID (MSC_SYSTEM_ITEMS)

/esc M'C_ITEM_I-_LI0me ull; T21e !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!! !!!! 'R_I <E TOR:_ITEM_IOT ULL UMBER 'R_I 'TA CE_IOT ULL UMBER I <E TOR:_ITEM_IOT ULL UMBER MSC_TP_ID_LID (MSC_TRADING_PARTNERS)

/esc M'C_T7_I-_LI0me ull; T21e !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!! !!!! 'R_T7_IOT ULL UMBER 'R_I 'TA CE_IOT ULL UMBER 7ART ER_T:7E OT ULL UMBER T7_IOT ULL UMBER 'R_COM7A :_IUMBER AGGREGATE_-EMA -_FLAG UMBER MSC_TP_SITE_ID_LID (MSC_TRADING_PARTNER_SITES)

/esc M'C_T7_'ITE_I-_LI0me ull; T21e !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!! !!!! 'R_T7_'ITE_IOT ULL UMBER 7ART ER_T:7E OT ULL UMBER 'R_I 'TA CE_IOT ULL UMBER T7_'ITE_IOT ULL UMBER 'R_COM7A :_IUMBER O7ERATI G_U IT UMBER LOCATIO _IUMBER

ASCP- Data Collection 5/51

I( Ite# Nu#/e s
select * from msc_+tem_+/_l+/ 6,ere +n=entor2_+tem_+/ > ?$; 'R_I <E TOR:_ITEM_I- 'R_I 'TA CE_I- I <E TOR:_ITEM_I!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!! !!!!!!!!!!!!!!!!! ?*@ )? # ?## )? A **A )? ? A?## )? ) A"#) )? B A"@$ )? " A"@A )? * A(?$ )? ( A(?A )? @ select /+st+nct su5str(se4ment?C?C?#) Item_ um5er from mtl_s2stem_+tems 6,ere +n=entor2_+tem_+/ +n (?*@C?##C**ACA?##CA"#)CA"@$CA"@ACA(?$CA(?A); ITEM_ UMBER !!!!!!!!!!!!!!! A'?$$$? A'?(@*B A'*?$$? A'*A$$? A'#*((( A'#*@@@ A')A**# A')#?$? A')#?$A

II( C"te*o , Sets


select c0te4or2_set_+/Cc0te4or2_set_n0me from mtl_c0te4or2_sets 6,ere c0te4or2_set_n0me % .In=&Items.; CATEGOR:_'ET_I- CATEGOR:_'ET_ AME !!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! AB In=&Items select * from msc_c0te4or2_set_+/_l+/ 6,ere sr_c0te4or2_set_+/ % AB;

'R_CATEGOR:_'ET_I- 'R_I 'TA CE_I- CATEGOR:_'ET_I!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!! !!!!!!!!!!!!!!! AB )? A


select c0te4or2_set_n0meC/escr+1t+onCcontrol_le=elC/ef0ult_fl04 from msc_c0te4or2_sets 6,ere c0te4or2_set_+/ % A CATEGOR:_' -E'CRI7TIO CO TROL_LE<EL -EFAULT_FLAG !!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!! !!!!!!!!!!!! In=&Items In=entor2 C0te4or2 'et A ?

ASCP- Data Collection "/51

III( Supplie s
select =en/or_+/C=en/or_n0me from 1o_=en/ors 6,ere =en/or_n0me l+De .'EF.; <E -OR_I- <E -OR_ AME !!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ?"#* 'E'U7-EFAULT ?"#A 'E'U7LC-? ?"#" 'E'U7LC-A select * from msc_t1_+/_l+/ 6,ere sr_t1_+/ +n (?"#AC?"#"C?"#*); 'R_T7_I- 'R_I 'TA CE_I- 7ART ER_T:7E T7_I- 'R_COM7A :_I- AGGREGATE_-EMA -_FLAG !!!!!!!! !!!!!!!!!!!!!! !!!!!!!!!!!! !!!!! !!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!! ?"#A )? ? ?#B?* !? ?"#" )? ? ?#B?# !? ?"#* )? ? ?#B?" !?

PARTNER_T1PE 9 = > 4

ENTIT1 <endor "ustomer Organi&ation "arrier


0meGC 70rtner_t21eC10rtner_+/

select su5str(10rtner_n0meC?C"$) GA7' 70rtner from msc_tr0/+n4_10rtners 6,ere 10rtner_+/ +n (?#B?#C?#B?*C?#B?#)

A7' 70rtner 0me 7ART ER_T:7E 7ART ER_I!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!! !!!!!!!!!! 'E'U7LC-? ? ?#B?* 'E'U7LC-A ? ?#B?#

I2( Supplie Sites


select =en/or_s+te_+/C=en/or_s+te_co/e from 1o_=en/or_s+tes_0ll 6,ere =en/or_+/ % ?"#A; <E -OR_'ITE_I- <E -OR_'ITE_CO!!!!!!!!!!!!!! !!!!!!!!!!!!!!! "?(@ 'E'ITLC-? select * from M'C_T7_'ITE_I-_LI6,ere 'R_T7_'ITE_I- % "?(@ 0n/ 10rtner_t21e % ?;
'R_T7_'ITE_I- 7ART ER_T:7E 'R_I 'TA CE_I- T7_'ITE_I- 'R_COM7A :_I- O7ERATI G_U IT LOCATIO _I!!!!!!!!!!!!! !!!!!!!!!!!! !!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!!!!! !!!!!!!!!!!!!! !!!!!!!!!!! "?(@ ? )? ?(??A !? A$*

ASCP- Data Collection #/51

select t1_s+te_co/e from msc_tr0/+n4_10rtner_s+tes 6,ere 10rtner_s+te_+/ % ?(??A T7_'ITE_CO-E !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 'E'ITLC-?

2( Custo#e s
select customer_+/Ccustomer_n0me from r0_customers 6,ere customer_n0me l+De .Com1uterF.; CU'TOMER_I- CU'TOMER_ AME !!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *?") Com1uterl0n/ 'tores ?$$) Com1uter 'er=+ce 0n/ Rent0ls ?A(@ Com1uter 'er=+ce 0n/ Consult+n4 "*?( Com1uter 'er=+ce 0n/ Rent0ls select * from msc_t1_+/_l+/ 6,ere sr_t1_+/ +n (*?")C?$$)C?A(@) 'R_T7_I- 'R_I 'TA CE_I- 7ART ER_T:7E T7_I- 'R_COM7A :_I- AGGREGATE_-EMA -_FLAG !!!!!!!! !!!!!!!!!!!!!! !!!!!!!!!!!! !!!!! !!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!! ?$$) )? A #? !? A ?A(@ )? A #" !? A *?") )? A (#?* !? A

select su5str(10rtner_n0meC?C"$) GA7' 70rtner 70rtner_t21eC 10rtner_+/ from msc_tr0/+n4_10rtners 6,ere 10rtner_+/ +n (#?C#"C(#?*);

0meGC

A7' 70rtner 0me 7ART ER_T:7E 7ART ER_I!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!! !!!!!!!!!! Com1uter 'er=+ce 0n/ Rent0ls A #? Com1uter 'er=+ce 0n/ Consult+n A #" Com1uterl0n/ 'tores A (#?*

2I( Custo#e Sites


select s+te_uses_0ll&s+te_use_co/eC s+te_uses_0ll&s+te_use_+/C s+te_uses_0ll&loc0t+on from HI_CU'T_ACCT_'ITE'_ALL ACCT_'ITEC HI_CU'T_ACCOU T' CU'T_ACCTC HI_CU'T_'ITE_U'E'_ALL 'ITE_U'E'_ALLC RA_CU'TOMER' RA 6,ere CU'T_ACCT&CU'T_ACCOU T_I- % ACCT_'ITE&CU'T_ACCOU T_IA - 'ITE_U'E'_ALL&CU'T_ACCT_'ITE_I- % ACCT_'ITE&CU'T_ACCT_'ITE_IA - RA&CU'TOMER_I- (J) % CU'T_ACCT&CU'T_ACCOU T_IA - RA&CU'TOMER_I- % ?$$) A - 'ITE_U'E'_ALL&ORG_I- +s OT ULL; 'ITE_U'E_C 'ITE_U'E_I- LOCATIO

ASCP- Data Collection $/51

!!!!!!!!!! !!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 'HI7_TO ?$A( Tem1e (O7') BILL_TO ?$A# C,0tt0noo40 (O7') 'HI7_TO ?$A) C,0tt0noo40 (O7') BILL_TO ?$B* C,0tt0noo40 'HI7_TO ?$B# C,0tt0noo40 BILL_TO ?A*( C,0tt0noo40 (7KM) 'HI7_TO ?A*@ C,0tt0noo40 (7KM) BILL_TO ?#B) GLte5or4 'HI7_TO ?@$* GLte5or4 BILL_TO ?(** Essen 'HI7_TO ?(*# Essen select * from M'C_T7_'ITE_I-_LI6,ere 'R_T7_'ITE_I- +n (?$A(C?$A#C?$A)C?$B*C?$B#C?A*(C?A*@C?#B)C?@$*C?(**C?(*#) 0n/ 10rtner_t21e % A;
'R_T7_'ITE_I- 7ART ER_T:7E 'R_I 'TA CE_I- T7_'ITE_I- 'R_COM7A :_I- O7ERATI G_U IT LOCATIO _I!!!!!!!!!!!!! !!!!!!!!!!!! !!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!!!!! !!!!!!!!!!!!!! !!!!!!!!!!! ?$A# A )? ?B#)# !? ?$@? ?$A) A )? ?B#)( !? ?$@? ?$A( A )? ?B#)@ !? ?$@A ?$B* A )? ?)?@( !? @"B ?$B# A )? ?)AAA !? @"B ?A*( A )? ?)A$? !? @B$ ?A*@ A )? ?)AA# !? @B$ ?#B) A )? ?)A$B !? ?$"B ?(** A )? ?)A$) !? ?$($ ?(*# A )? ?)A"$ !? ?$($ ?@$* A )? ?)A"? !? ?$"B

select t1_s+te_co/eCloc0t+on from msc_tr0/+n4_10rtner_s+tes 6,ere 10rtner_s+te_+/ +n (?B#)#C?B#)(C?B#)@C?)?@(C?)AAAC?)A$?C?)AA#C?)A$BC?)A$)C?)A"$C?)A"?); T7_'ITE_CO-E !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! BILL_TO BILL_TO BILL_TO BILL_TO 'HI7_TO 'HI7_TO 'HI7_TO 'HI7_TO BILL_TO 'HI7_TO 'HI7_TO LOCATIO !!!!!!!!!!!!!!!!!!!!!!!!! C,0tt0noo40 C,0tt0noo40 (7KM) Essen GLte5or4 C,0tt0noo40 C,0tt0noo40 (7KM) Essen GLte5or4 C,0tt0noo40 (O7') C,0tt0noo40 (O7') Tem1e (O7')

ASCP- Data Collection %/51

2II( C" ie
'ELECT CARRIER_I- C FREIGHT_CO-EC LA'T_U7-ATE_-ATE FROM M'H_CARRIER' 6,ere fre+4,t_co/e % .Fe/e9. CARRIER_I- FREIGHT_CO-E LA'T_U7-A !!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!! ?A#A# Fe/e9 $(!-EC!@@ select * from msc_t1_+/_l+/ 6,ere sr_t1_+/ +n (?A#A#); 'R_T7_I- 'R_I 'TA CE_I- 7ART ER_T:7E T7_I- 'R_COM7A :_I- AGGREGATE_-EMA -_FLAG !!!!!!!!!! !!!!!!!!!!!!!! !!!!!!!!!!!! !!!!! !!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!! ?A#A# )? * ?#(@? !? select su5str(10rtner_n0meC?C"$) GA7' 70rtner from msc_tr0/+n4_10rtners 6,ere 10rtner_+/ +n (?#(@?); 0meGC 70rtner_t21eC 10rtner_+/

A7' 70rtner 0me 7ART ER_T:7E 7ART ER_I!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!! !!!!!!!!!! Fe/e9 * ?#(@?

2III( O *"ni3"tion
select or4&or40n+N0t+on_co/eC or4&or40n+N0t+on_+/C or4&m0ster_or40n+N0t+on_+/C ,0otl&n0me from MTL_7ARAMETER' or4C HR_ALL_ORGA IIATIO _U IT'_TL HAOTL 6,ere HAOTL&ORGA IIATIO _I-(J) % ORG&ORGA IIATIO _I0n/ or4&or40n+N0t+on_+/ +n (A$*CA$BCA$(CA$@CA?$); ORG ORGA IIATIO _I- MA'TER_ORGA IIATIO _I- AME !!! !!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!! <? A$* A$* 'et, M? A$B A$* 'e0ttle M0nuf0ctur+n4 '? A$( A$* C,+c04o 'u50ssem5l2 7l0nt MA A$@ A$* Boston M0nuf0ctur+n4 -A A?$ A$* M+0m+ -+str+5ut+on Center select su5str(10rtner_n0meC?C"$) GA7' 70rtner from msc_tr0/+n4_10rtners 6,ere 10rtner_t21e % "; 0meGC 70rtner_t21eC 10rtner_+/

A7' 70rtner 0me 7ART ER_T:7E 7ART ER_I!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!! !!!!!!!!!! B-EO'et, " ?#@AA B-EO'e0ttle M0nuf0ctur+n4 " ?#@A" B-EOC,+c04o 'u50ssem5l2 7l0nt " ?#@A* B-EOBoston M0nuf0ctur+n4 " ?#@A# B-EOM+0m+ -+str+5ut+on Center " ?#@A)

ASCP- Data Collection 1&/51

Sn"ps%ot 4 A snapshot is a replica of a target master table at a single point$in$time. Oracle uses snapshots) also referred to as materialized views. Snapshots are updated from one or more master tables via individual batch updates) 'nown as a refresh) from a single master site. There are several types of snapshot) (n Data "ollection uses #O6(D snapshots /to support bac'ward compatibilty for snapshots based on master tables from Oracle ? database0. Sn"ps%ot Lo* 4 6hen you create a snapshot log for a master table) Oracle creates an underlying table as the snapshot log. A snapshot log holds the primary 'eys and3or the #O6(Ds of rows that have been updated in the master table. A snapshot log can also contain filter columns to support fast refreshes of snapshots with sub2ueries. The name of a snapshot log@s table is MLOG$_master_table_name. The snapshot log is created in the same schema as the target master table. One snapshot log can support multiple snapshots on its master table. Re$ es% P ocess 4 A snapshot@s data does not necessarily match the current data of its master table at all times. A snapshot is a transactionally /read0 consistent reflection of its master table as the data e.isted at a specific point in time /that is) at creation or when a refresh occurs0. To 'eep a snapshot@s data relatively current with the data of its master table) the snapshot must be periodically refreshed. A snapshot refresh is an efficient batch operation that ma'es a snapshot reflect a more current state of its master table. You must decide how and when to refresh each snapshot to ma'e it more current. -or e.ample) snapshots based on master tables that applications update often may re2uire fre2uent refreshes. (n contrast) snapshots based on relatively static master tables usually re2uire infre2uent refreshes. (n summary) you must analy&e application characteristics and re2uirements to determine appropriate snapshot refresh intervals. Co#plete Re$ es%es To perform a complete refresh of a snapshot) the server that manages the snapshot e.ecutes the snapshot@s defining 2uery. The result set of the 2uery replaces the e.isting snapshot data to refresh the snapshot. Oracle can perform a complete refresh for any snapshot. Depending on the amount of data that satisfies the defining 2uery) a complete refresh can ta'e a substantially longer amount of time to perform than a fast refresh. F"st Re$ es%es To perform a fast refresh) the server that manages the snapshot first identifies the changes that occurred in the master since the most recent refresh of the snapshot and then applies them to the snapshot. -ast refreshes are more efficient than complete refreshes when there are few changes to the master because the participating server and networ' replicate a smaller amount of data. You can perform fast refreshes of snapshots only when the master table has a snapshot log. Fo ce Re$ es%es To perform a force refresh of a snapshot) the server that manages the snapshot tries to perform a fast refresh. (f a fast refresh is not possible) then Oracle performs a complete refresh. Ase the force setting when you want a snapshot to refresh if a fast refresh is not possible.

The following Snapshots are defined in the source instance. -or each snapshot there is a synonym defined. Asing these synonym and other production tables in the source instance there are various views created.

ASCP- Data Collection 11/51

SNAPSHOT NAME
MTL_-EMA -_' MTL_MTR8_TM7_' MTL_OH_PT:'_' MTL_RE'ER<ATIO '_' MTL_'U77L:_' MTL_':'_ITEM'_' MTL_U_-EMA -_' MTL_U_'U77L:_' 7O_ACCE7TA CE'_' 7O_CHA GE_REPUE'T'_' 7O_'I_CA7A_' BOM_BOM'_' BOM_I <_COM7'_' BOM_O7R_ ETMORE'_' BOM_O7R_RE''_' BOM_O7R_RT '_' BOM_O7R_'EP'_' BOM_RE'_CH G'_' BOM_'UB_COM7'_' BOM_'UB_O7R_RE''_' MR7_FORECA'T_-ATE'_' MR7_FORECA'T_-'G _' MR7_FORECA'T_ITEM'_' MR7_'CH-_-ATE'_' MI7_-'CR_KOB'_' MI7_FLOM_'CH-'_' MI7_RE7T_ITEM'_' MI7_RE7T_'CH-'_' MI7_MLI E'_' MI7_MO7R'_' MI7_MO7R_RE''_' MI7_MO7R_'UB_RE''_' MI7_MREP_O7R'_' OE_O-R_LI E'_' M'H_TRI7_' M'H_TRI7_'TO7_' M'M_LK_O7R'_' M'M_LK_O7R_ ME_' M'M_LK_O7R_RE''_' M'M_LK_REP_O7R'_' AHL_'CH_MTL'_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' MR7_' M'H_' M'H_' MR7_' MR7_' MR7_' MR7_' AHL_'

S1NON1M NAME
_-EMA _MTR8_TM7 _OH_PT:' _MTL_RE'ER<ATIO ' _'U77L: _':'_ITEM' _U_-EMA _U_'U77L: _7O_ACCE7TA CE' _7O_CHA GE_REPUE'T' _'I_CA7A _BOM' _I <_COM7' _O7R_ ETMORE' _O7R_RE'' _O7R_RT ' _O7R_'EP' _RE'_CH G' _'UB_COM7' _'UB_O7R_RE'' _FORECA'T_-ATE' _FORECA'T_-'G _FORECA'T_ITEM' _'CH-_-ATE' _-'CR_KOB' _FLOM_'CH-' _RE7T_ITEM' _RE7T_'CH-' _MLI E' _MO7R' _MO7R_RE'' _MO7R_'UB_RE'' _MREP_O7R' _O-R_LI E' _TRI7 _TRI7_'TO7 _LK_O7R' _LK_O7R_ ME _LK_O7R_RE'' _LK_REP_O7R' _'CH_MTL'

ASCP- Data Collection 12/51

DATA C ''ECTI N SET(P STEPS


Oracle AS"PBs data collection architecture) shown in the figure below) depicts the data ob+ects) procedures) and data flow between source data and Oracle AS"P. The ma+or repositories are ADS) ODS) and PDS. Procedures enable data cleansing) data collecting) data communication) and net$change handling between data repositories. 6hen Oracle AS"P and its source data reside on the same instance) communication between them is enabled by PL3SCL based public AP( procedures or interface tables. (n a distributed environment) procedure calls are made using database lin's.

Oracle AS"P supports the following configurations for installation and deployment. "entrali&ed planning Decentrali&ed planning

These configurations offer you enough fle.ibility to design a mode of planning that suits your business ob+ectives. Doth configurations are supported using a consistent architecture as outlined in the previous section. The sole distinction is that centrali&ed planning uses database lin's to pull data into the Oracle AS"P data store.

ASCP- Data Collection 13/51

Cent "li3e! Pl"nnin* The following figure shows the centrali&ed planning configuration%

Oracle AS"P wor's as a central Planning Server across several source data instances. The collection program is installed on the planning server and the data stripped by instance8id is moved into staging tables within Oracle AS"P during the data collection process. After the planning process) results can be pushed bac' to each instance. Decent "li3e! Pl"nnin* The following figure shows the decentrali&ed planning configuration%

Oracle AS"P and its source data reside in the same database. !o database lin' is re2uired in this case. Two components can communicate through the planning ob+ect AP(s and the interface tables defined in Oracle Applications. Depending on the type of configuration that is selected the setup steps will change. .g. -or "entrali&ed configuration there is no need to set up database lin's) where as in Decentrali&ed configuration the database lin's will have to set up before proceeding with any other setup steps.

ASCP- Data Collection 1!/51

The Oracle APS setup for data collection involves three steps stablish database lin's Define (nstances 3 Associate Organi&ations from where the data is being pulled. Specify parameters for the data to be collected from each instances for each named re2uest set D"t"/"se Lin.s The Planning Database Lin' is defined by the database administrator on the APS /destination0 planning instance. The Application Database administrator on the transaction /Source0 instance. There are two Database lin's created. One on the source instance that points to the destination instance /'nown as the Application Database Lin'0. One on the destination instance that points to the source instance /'nown as the Planning Database Lin'0. Doth the lin's are bidirectional. The Planning Database lin' is used for Data collection from transaction source to the planning instance. 6hen an action such as releasing a planned order or re2uisition occurs in the APS planning system) the data is EpublishedF to the transaction instance. The first step in this process is to send a signal via the Planning database lin' to the transaction instance. This initiates a remote procedure that pulls the planned order or re2uisition from the planning instance to the transaction instance. The Application Database lin' is used for "ompleting the EPublishingF process. The remote procedure that pulls the planned order or re2uisition record from the planning instance to the transaction instance does so by using the Application Database lin'. E)"#ple o$ " Cent "li3e! Deplo,#ent 6ith 99i95 you can now collect from a single source instance into mutiple planning server instances. This is useful during rollout of new Advanced Planning releases. You can deploy the new relase of Advanced Planning on a test planning server instance while still generating production plans out of a production planning server instance. Doth planning server instances can share the same production source transaction instance. This allows you to leverage the setup and transaction data in the production source instance to do volume testing on the test planning server instance. You can do so without duplicating the source instance) thus avoiding substantial storage and maintenance costs. -ollowing is an e.planation of what ( am doing here. ( have two database instances on two different machines called GS THB and GAPSB. (nstance GS THB is a production instance) which is the Source transaction instance. ( wil be using the Decentrali&ed configuration i.e. ( will have Oracle AS"P and its source data reside in the same database) but ( will also collect the Source instance into GAPSB planning server instance. This way ( can do my test plan runs on the GAPSB instance before running them on the production instance. ( am collecting S TH source transaction instance into two AS"P planning server instances.

ASCP- Data Collection 15/51

DATABASE SETH O "cle Apps O "cle ASCP

DATABASE APS O "cle ASCP

-ollowing database lin' is created in Source instance% In sou ce &Applic"tion D"t"/"se Lin.( 55555555555555555555555555555
cre0te 1u5l+c /0t050se l+nD A7' connect to 011s +/ent+f+e/ 52 011s us+n4 .A7'&6orl/.;

-ollowing database lin' is created in planning instance% In APS &Pl"nnin* D"t"/"se Lin.( 5555555555555555555555555
cre0te 1u5l+c /0t050se l+nD 'ETH connect to 011s +/ent+f+e/ 52 011s us+n4 .'ETH.

Test the APS lin' as follows% In APS S6L7Plus8 55555555555555555555


select +nst0nce_n0me from =$+nst0nce; I 'TA CE_ AME !!!!!!!!!!!!!!!! A7' select +nst0nce_n0me from =$+nst0nceQ'ETH; I 'TA CE_ AME !!!!!!!!!!!!!!!! 'ETH

Test the source lin' as follows% In SETH S6L7Plus8 55555555555555555555


select +nst0nce_n0me from =$+nst0nce; I 'TA CE_ AME !!!!!!!!!!!!!!!! 'ETH select +nst0nce_n0me from =$+nst0nceQA7'; I 'TA CE_ AME !!!!!!!!!!!!!!!! A7'

ASCP- Data Collection 1"/51

De$ine Inst"nces !avigation path for defining the instances. Advanced Planning Administration Admin(nstances The Database Administrator uses this form to setup instance names and to specify the release version of the source database) Application Database lin' and Planning Database lin' associated with the instance names.

In SETH S6L7Plus8 55555555555555555555


select Inst0nce_+/C Inst0nce_Co/eC mA0_/5l+nDC 0Am_/5l+nD from mr1_01_011s_+nst0nces_0ll I 'TA CE_I- I ' MAA_-BLI E AAM_-BLI E !!!!!!!!!!! !!! !!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!! )? B-E 'ETH A7' )? B-E

(n 99.I.95 MR7_A7_A77'_I 'TA CE'_ALL table can have more than one row. Defore to 99.I.95 the table used was MR7_A7_A77'_I 'TA CE'.

ASCP- Data Collection 1#/51

In APS S6L7Plus8 55555555555555555555


select Inst0nce_+/C Inst0nce_Co/eC mA0_/5l+nDC 0Am_/5l+nD from msc_011s_+nst0nces I 'TA CE_I- I ' MAA_-BLI E AAM_-BLI E !!!!!!!!!!! !!! !!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!! )? B-E 'ETH A7' A? T'T

"omplete the following -ield and -lag in the Application (nstance 6indow.

FIELD/FLAG
(nstance "ode (nstance Type <ersion Application Database Lin' Planning Database Lin' nable -lag Allow ATP

DESCRIPTION
"hoose from 7ultiple instances Discrete) Process) Discrete and Process or Other. (f the source is discrete) only the discrete entitles are collected. (- Process) then only OP7 related entities are collected Ani2ue version for the specified instance A lin' to connect to the Application database to Oracle AS"P A lin' to connect to the Oracle AS"P to the Application database Select this option to enable the collection Process Specify a destination that will be used in the ATP process from the source instance in the Application (nstances form. This is because of 99i95 "ollection from a Single Source into 7ultiple Planning Servers feature Specify a destination instance that will be considered in the Auto #elease process in the Application (nstances form. This is because of 99i95 "ollection from a Single Source into 7ultiple Planning Servers feature The difference between instance time &one and J7T nter the default assignment set for this instance. The assignment is used to resolve sourcing for order promising in2uiries.

Allow #elease

J7T Difference "urrency Assignment Set

Set up Organi&ations by clic'ing on the Organi&ations Dutton. The Organi&ations window lists the organi&ation within the instance. To enable data collection for an organi&ation within an instance) select the enabled chec' bo..

ASCP- Data Collection 1$/51

6ith 99i95 AS"P permits collection of data for only specified organi&ations of a source instance. This will support independent planning processes in independent business units of a company that is running a single instance of the Oracle e$Dusiness Suite. The organi&ation specific collection functionality applies to both Standard and "ontinuous

ASCP- Data Collection 1%/51

"ollections. Asing "ollection Jroup the Organi&ation specific collection is deployed. You can perform by specifying a collection Jroup or by doing collections for all Organi&ations. Defore running Data "ollection run the following SCL scripts to verify that same valid user is created in both the source /S TH0 and AS"P /APS0 instance.
'ELECT U'ER_IFROM F -_U'ER MHERE U'ER_ AME % .MFG.; U'ER_I!!!!!!!!!! ?$)( 'ELECT A77LICATIO _IFROM F -_A77LICATIO _<L MHERE A77LICATIO _ AME % .A/=0nce/ 'u11l2 C,0+n 7l0nn+n4.; !! 1r+or to ??&#&?$ T,e 011l+c0t+on 0me !! +s ROr0cle A/=0nce/ 'u11l2 C,0+n 7l0nn+n4S A77LICATIO _I!!!!!!!!!!!!!! BA* 'ELECT res1ons+5+l+t2_+/ FROM F -_res1ons+5+l+t2_=l MHERE res1ons+5+l+t2_n0me % .A/=0nce/ 'u11l2 C,0+n 7l0nner. A - 011l+c0t+on_I/ % BA*; RE'7O 'IBILIT:_I!!!!!!!!!!!!!!!!! A?)"*

#un the Data collection successfully and !avigate to the following path Advanced Planning Administration AdminOrgani&ation Security Organi&ation security restricts plan information access to authori&ed individuals. Oracle AS"P allow users to associate +ob responsibilities to organi&ations for security purposes. This ensures that you see3change planning data in an organi&ation only if you have a +ob responsibility associated with the organi&ation. Examples: Aser 9 is restricted to organi&ation 7= Aser = has global authori&ation to access all organi&ations including organi&ations 79 and 7=. Aser = creates a plan for organi&ations 79 and 7= /owning organi&ation is 790. Aser 9 can access this plan and view and e.ecute only the portion of this plan related to organi&ation 7=.

The Assign Organi&ations to #esponsibilities page appears.

ASCP- Data Collection 2&/51

(n the #esponsibility field) select the responsibility that you want to associate to organi&ations. The list of values for the #esponsibility field includes all responsibilities defined in the #esponsibilities form in the Planning Server. /limited to Oracle AS"P responsibilities0. -rom the Available Organi&ations column) select and move any organi&ation to the Assigned Organi&ations column using the 7ove button. You can use the 7ove All button to select all organi&ations for the specified responsibility. You can use the #emove button to remove any selected organi&ation from the Assigned Organi&ations column. You can also use the #emove All button to remove all selected organi&ations. Select the Save button.

To view the collected Data navigate to "ollections <iew "ollected Data.

ASCP- Data Collection 21/51

ASCP- Data Collection 22/51

ASCP- Data Collection 23/51

DATA C ''ECTI N PA)A*ETE)S


Data Pull Parameters window

Inst"nce 4 Source instance code from list of values. Collection G oup 9"ollection Jroup to perform collection of data for only specified organi&ation of a source instance. Nu#/e o$ -o .e s 4 One or greater. (ncrease this number to increase the amount of computational resources to devoted to thePlanning Data Pull process. This allows you to specify the number of wor'ers for the Data Pull) which can now be different from the number of wor'ers specified for the ODS load process. Ti#eout &Minutes( 4 The ma.imum amount of time you would li'e to allocate to the Planning Data Pull process. (f the Planning Data Pull process has not completed within this amount of time) it will be terminated with an error. Pu *e P e:iousl, Collecte! D"t" $ This parameter decides whether the ODS Data needs to be completely purged or !ot /e.cept Sales Order which is still decided by Sales Order Parameter0. This parameter can have values of Y S3!O /Default is Y S0

ASCP- Data Collection 2!/51

1es K Purge previously "ollected Data and rebuild the data for the entities set to Yes /e.cept Sales Orders) this will be driven by the Sales Order Paramater0. Only "omplete #efresh can be specified in the "ollections 7ethod with this set to Y S. AS # cannot perform TA#J TT D 3 ! T "HA!J #efresh. No K Do not Purge previously "ollected Data. Only Targetted3!et "hange #efresh can be specified in the "ollections method with this set to !O. (n case of Targetted #efresh $ purge and rebuild specific entities which are set to Yes. (n case of !et "hange #efresh $ bring over the incremental changes for the entities set to Yes.

Collection Met%o! $ This parameter decides the type of "ollections to be performed. "omplete #efresh $ Deletes the data in Destination for ALL ntities /e.cept Sales Order which is still driven by the sales order parameter0 and "ollects all the new data O!LY for the entities set to Y S on the @Planning Data Pull@ form. Targetted #efresh $ Deletes the data in Destination O!LY for the ntities set to Y S in @Planning Data Pull@ form and "ollects all the new data O!LY for that entities. !et "hange #efresh$ "ollects the changes for all the ntities set to Y S in @Planning Data Pull@ form. An"l,3e St"*in* T"/les 4 Yes or !o /default0. Set this to Yes periodically to recompute database access statistics on the APS staging tables. This speeds up the subse2uent Planning ODS Load process. Use Co#p"n, Associ"tion 4 allows users that have been established in the system to be related with a company such as a customer or supplier. The customer or supplier must previously be defined in the system. This feature allows a customer@s or a supplier@s user to gain access to selected applications such as Advanced Supply "hain Planning and "ollaborative Planning. No K During data collections the destination instance will not accept new users@ company association nor e.isting users with changes to their company association. C e"te use s "n! en"/le use co#p"n, "ssoci"tion K Since Oracle APS is designed to wor' with multiple source instances or systems) a user created on one of the sources can automatically be created on the planning server or destination instance. -irst) a system administrator creates the new user and specifies the user@s contact information during setup. The user will be created on the destination instance or planning server and will be assigned the responsibility) Supply "hain "ollaboration Planner. The new user can log into "ollaborative Planning and can view data visible to her company. En"/le use co#p"n, "ssoci"tion $ Selecting this option re2uires that the new user be established on both the source instance and on the destination instance. Ase this option when you would li'e to assign multiple responsibilities to the new user. -irst) create the new user on the source instance and specify the user@s contact information during the setup. Second) create the user on the destination instance or planning system and assign the user responsibilties. The user will have all the assigned responsibilities. The remaining parameters in the Planning Data Pull Parameters are a list of business entities. Selecting Yes for an entity means collect the information for that entity over from the

ASCP- Data Collection 25/51

source instance. Selecting !o for an entity means don@t collect the information for that entity over from the source instance. Planning ODS Load Parameters window

Inst"nce 4 Source instance code from list of values. Ti#eout &Minutes( 4 The ma.imum amount of time you would li'e to allocate to the Planning Data Pull process. (f the Planning Data Pull process has not completed within this amount of time) it will be terminated with an error. Nu#/e o$ -o .e s 4 One or greater. (ncrease this number to increase the amount of computational resources to devoted to thePlanning Data Pull process. This allows you to specify the number of wor'ers for the Data Pull) which can now be different from the number of wor'ers specified for the ODS load process. Rec"lcul"te Resou ce A:"il"/ilit, 4 This defaults to the value /Yes or !o0 that you set forthe #esources Availability business entity in the Planning Data Pull Parameters window. The value that you set here is the one that actually determines whether resources availability is collected or not. Rec"lcul"te Sou cin* Histo , 4 This defaults to the value /Yes or !o0 that you set for the Sourcing History business entity in the Planning Data Pull Parameters window. The value that you set here is the one that actually determines whether sourcing history is collected or not. (f you select Yes) then AS"P will collect all new sourcing history not already on the planning server in the time range ,/today $ . months0 through /today0L from the source transaction system. The number . is given by the value that you set for the profile option 7S"% Sourcing History Start Date Offset /in months0. During planning) AS"P will use the total cumulative sourcing history on the planning server in addition to the planned sourcing in the plan to determine whether sourcing percentages in sourcing rules are being respected or not.

ASCP- Data Collection 2"/51

Pu *e Sou cin* Histo , 4 <alid values are Yes and !o /default0. (f you select Yes) then all sourcing history present on the planning server will be deleted before the collection process commences. Data Changes That Can e Colle!ted in "et Change #ode 6hen the net change mode for collections is selected !o0) the data changes shown in the following table can be collected. (f you set the collections parameter "omplete #efresh to yes) the collections program collects the entire data for the entity. You can run data collections in net change mode for these transactions% DATA ELEMENT Sales orders COMMENTS "ancellations of or modifications to sales orders are captured. The Pull Sales Orders collections parameter must be set to Yes. #eservations against #eservations against both e.ternal and internal sales order demands demands are captured. The Pull #eservations collections parameter must be set to Yes. 7aster production 7PS demands that are added) modified or relieved in the source schedule demands instance are captured. The Pull 7PS collections parameter must be set to Yes. 7aster demand The Pull 7DS collections parameter must be set to Yes. schedule 6(P component Demand changes due to cancellation of 6(P +obs) changes in the demands state of 6(P +obs /for e.ample) operations within a +ob have been performed or cancelled0) and changes to 6(P +obs because of changes in item information are captured. The Pull 6(P collections parameter must be set to Yes. 6(P repetitive item Demand changes due to cancellation of 6(P repetitive schedules) demands changes in the state of 6(P repetitive schedules) and changes to 6(P repetitive schedules because of changes in item information are captured. The Pull 6(P collections parameter must be set to Yes. -orecast demands "hanges and deletions in forecasts are captured. The Pull -orecast collections parameter must be set to Yes. Aser demands "hanges to user demands because of changes to item information are captured. 7aster production "hanges in supply schedules or item information are captured. The schedule supplies Pull 7PS collections parameter must be set to Yes. Aser supplies "hanges to user supplies because of changes to item information are captured. Purchase order "hanges to PO supplies because of re+ections) returns) or supplies cancellations or changes to item information are captured. The collections parameter Pull PO collections parameter must be set to Yes. On$hand supplies The Pull On Hand collections parameter must be set to Yes. 6or' orders in Oracle "hanges in 6(P Mobs are captured. The Pull 6(P collections 6or' in Process parameter must be set to Yes. #esource availability The #ecalculate !#A collections parameter must be set to Yes. Supplier capacity The Pull Supplier "apacity collections parameter must be set to Yes. Dills of material All DO7 changes are captured% new components) disabled components) component 2uantities) effectivity dates) DO7 revisions)

ASCP- Data Collection 2#/51

and component substitutes. The Pull DO73#outing collections parameter must be set to Yes. #outing operations "hanges to and deletions of routing operations as a result of changes to operation se2uences /for e.ample) the addition of new operations) the disabling of operations) or the changing of operation dates0) the disabling of a routing) the changing of routing dates) or changes to item information /for e.ample) the disabling of an item) the creation of a new item0 are captured. The Pull3DO7 #outing collections parameter must be set to Yes. "omponents needed "hanges to and deletions of components needed for a routing for a routing operation are captured. The Pull DO73#outing collections parameter operation must be set to Yes. #esources attached "hanges to and deletions of operation resources or operation to a routing operation resource se2uences within a routing are captured. The Pull DO73#outing collections parameter must be set to Yes. #esource "hanges in resource re2uirements of 6(P +obs because of completion re2uirements for 6(P of the 6(P +obs) completion of operations within the 6(P +obs) or +obs changes in item information are captured. The Pull 6(P collections parameter must be set to Yes. (tems or (tem "hanges in items and items categories are captured. categories "apacity "hanges in supplier capacity and resource capacity are captured. Transactions /supply and demand0 change more fre2uently than setup entities. After data collections) the collections program maintains snapshots of transaction entities. ach time you run data collections) the collections program loo's at the snapshot to determine if the transaction entity has changed since the previous collections. (f it has) the collections program collects the incremental data changes and updates the snapshot. As setup entities change less fre2uently) the collections process does not 'eep snapshots for these and cannot perform net change collections on them. Schedule either a targeted or a complete refresh for setup. You cannot run data collections in net change mode for the following setup entities% "AT JO#Y S TS D -AALT (T 7 "AT JO#Y Simulation sets Department resources #esource shift setup Hard reservations Pro+ects or pro+ect tas's Anits of measure /class conversion) conversions0 Sourcing information Dills of resources "alendar information /start dates calendar (nter$organi&ation ship methods dates) calendar wee') calendar shifts) shift Dates) shift e.ceptions) shift times) period start dates0 Parameters Planners Dusiness intelligence systems periods Purchase orders suppliers #esource groups Demand classes Supplier fle. fences Availability to promise rules Trading partners /customer or customer sites) supplies) supplier sites) organi&ation) organi&ation sites) location associations) customer) vendor) buyer) contacts0

ASCP- Data Collection 2$/51

T+E DATA C ''ECTI N P) CESS


The Data collection consists of the following Pull p o* "# "ollects the data from the ADS) and stores the data into the staging tables. This pull program is a registered AOL concurrent program that could be scheduled and launched by a system administrator. (f you are using a legacy program) you must write your own pull program. The pull program performs the following ma+or processes. #efresh snapshots. Launch the pull 6or'ers to perform pulls from the appropriate source tables and insert the data in the Staging tables. ODS Lo"! A PL3SCL program which performs the data transform and moves the data from the staging tables to the ODS. This collection program is a registered AOL concurrent program that could be scheduled and launched by the system administrator. The Launch87onitor procedure performs the following ma+or processes% ;ey Transformation $ Jenerate new local (D for global attributes such as items) category set) vendor; vendor site) customer and customer site. Launch the ODS Load 6or'ers to perform "reate) Apdate) and Delete operations for each entity in ODS /7S"PD"60. #ecalculate the sourcing history based on the latest sourcing information and the data from transaction systems. #ecalculate the net resource availability based on the calendars) shifts and department resources information. Purge the data in the Staging tables /7S"PD"P0.

To understand the Data "ollection process first we need to understand the architecture of the data in the source instance. -or that we need to understand the following. 6hen the data in transaction /Source0 instance is : added or changed. The changes are reflected in the snapshots after the #efresh Snapshot process completes successfully. ( will e.plain this with an e.ample. ( will ta'e an e.ample of Dill of 7aterial. ( have defined the following bill.

ASCP- Data Collection 2%/51

e$ore Data Colle!tion


select +n=entor2_+tem_+/ ITEM_I-C se4ment? ITEM_ AMEC or40n+N0t+on_+/ ORG_Ifrom mtl_s2stem_+tems 6,ere +n=entor2_+tem_+/ +n (@*?*C@*?#C@*?)) 0n/ or40n+N0t+on_+/ % A$B; ITEM_I- ITEM_ AME !!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!! @*?* 'E-CTE'T$? @*?# 'ETE'T-C$A @*?) 'E-CTE'T$" ORG_IA$B A$B A$B

'ELECT A''EMBL:_ITEM_I- ITEM_I-C 'EGME T? ITEM_ AMEC BOM&ORGA IIATIO _I- ORG_I-C BILL_'EPUE CE_I- BILL_'EP_IFROM BOM_BILL_OF_MATERIAL' BOMC MTL_':'TEM_ITEM' MTL MHERE A''EMBL:_ITEM_I- % @*?* A - BOM&ORGA IIATIO _I- % MTL&ORGA IIATIO _IA - A''EMBL:_ITEM_I- % I <E TOR:_ITEM_I-; ITEM_I- ITEM_ AME ORG_I- BILL_'EP_I!!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!!! @*?* 'E-CTE'T$? A$B "B*"( 'ELECT COM7O E T_ITEM_I- ITEM_I-C 'EGME T? ITEM_ AMEC COM7O E T_PUA TIT: COM7O E T_PT:C O7ERATIO _'EP_ UM O7_'EP UM FROM BOM_I <E TOR:_COM7O E T' COM7'C MTL_':'TEM_ITEM' MTL MHERE BILL_'EPUE CE_I- % "B*"( A - MTL&ORGA IIATIO _I- % A$B A - COM7O E T_ITEM_I- % I <E TOR:_ITEM_I-; ITEM_I- ITEM_ AME COM7O E T_PT: O7_'EP UM !!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!!!!! !!!!!!!!!! @*?) 'E-CTE'T$" ? ?$ @*?# 'ETE'T-C$A ? A$ 'ELECT A''EMBL:_ITEM_I- ITEM_I-C 'EGME T? ITEM_ AMEC BOM&ORGA IIATIO _I- ORG_I-C ROUTI G_'EPUE CE_I- RTG_'EP_IFROM BOM_O7ERATIO AL_ROUTI G' BOMC MTL_':'TEM_ITEM' MTL MHERE A''EMBL:_ITEM_I- % @*?* A - BOM&ORGA IIATIO _I- % MTL&ORGA IIATIO _IA - A''EMBL:_ITEM_I- % I <E TOR:_ITEM_I-; ITEM_I- ITEM_ AME ORG_I- RTG_'EP_I!!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!! @*?* 'E-CTE'T$? A$B @A?( 'ELECT O7ERATIO _'EP_ UM O7_'EP UMC BO-&-E7ARTME T_CO-E -E7T_ AMEC O7ERATIO _'EPUE CE_I- O7_'EP_I-

ASCP- Data Collection 3&/51

FROM BOM_O7ERATIO _'EPUE CE' BO'C BOM_-E7ARTME T' BOMHERE ROUTI G_'EPUE CE_I- % @A?( A - BO-&-E7ARTME T_I- % BO'&-E7ARTME T_I-; O7_'EP UM -E7T_ AME O7_'EP_I!!!!!!!!!! !!!!!!!!!! !!!!!!!!!! ?$ 'EMFG ?#*@? A$ 'EPLT: ?#*@A 'ELECT BR&RE'OURCE_I-C RE'OURCE_CO-E RE'OURCE_CO-EC U'AGE_RATE_OR_AMOU T_I <ER'E AMOU T_I <ER'EC -ECO-E('CHE-ULE_FLAGC?C.:es.C. o.) 'CHE-ULE_FLAG FROM BOM_O7ERATIO _RE'OURCE' BORC BOM_RE'OURCE' BR MHERE O7ERATIO _'EPUE CE_I- +n (?#*@?C?#*@A) A - BR&RE'OURCE_I- % BOR&RE'OURCE_I-; RE'OURCE_I- RE'OURCE_C AMOU T_I <ER'E 'CH !!!!!!!!!!! !!!!!!!!!! !!!!!!!!!!!!!! !!! ?)B# 'EAsm5lr ?A :es ?)BB 'ETester ?A :es select 6e&6+1_ent+t2_n0me KOB_ AMEC sc,e/ule/_st0rt_/0te 'TART_-ATEC sc,e/ule/_com1let+on_/0te COM7_-ATEC 't0rt_Tu0nt+t2 'TRT_PT:C et_Pu0nt+t2 ET_PT: from 6+1_ent+t+es 6eC 6+1_/+screte_Uo5s 6/U 6,ere 6e&1r+m0r2_+tem_+/ % @*?* 0n/ 6/U&MI7_ent+t2_+/ % 6e&MI7_E TIT:_I-; KOB_ AME 'TART_-AT COM7_-ATE 'TRT_PT: ET_PT: !!!!!!!!!!!!!!!!!!!! !!!!!!!!! !!!!!!!!! !!!!!!!!!! !!!!!!!!!! 'E-CKOB? $@!AUG!$* ??!AUG!$* "$$ "$$ 'ELECT 'U77L:_T:7E_CO-EC ITEM_IC 'EGME T? ITEM_ AMEC 7O_LI E_I-C MR7_7RIMAR:_PUA TIT: MR7_PT:C EE-_B:_-ATE FROM MTL_'U77L: M'C MTL_':'TEM_ITEM' M'I MHERE +tem_+/ +n (@*?#C@*?)) A - +tem_+/ % +n=entor2_+tem_+/ 0n/ M'I&ORGA IIATIO _I- % M'&MR7_TO_ORGA IIATIO _I-; 'U77L:_T:7 ITEM_I- ITEM_ AME 7O_LI E_I- MR7_PT: EE-_B:_!!!!!!!!!! !!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!! !!!!!!!!! 7O @*?# 'ETE'T-C$A A"")* ?$$ ?A!AUG!$* 7O @*?) 'E-CTE'T$" A"")" ?$$ ?A!AUG!$*

'ELECT MOP&ORGA IIATIO _I- ORG_I-C se4ment? ITEM_ AMEC 'UBI <E TOR:_CO-E 'UBI <_CO-EC TRA 'ACTIO _PUA TIT: TRA _PT:

ASCP- Data Collection 31/51

FROM MTL_O HA -_PUA TITIE' MOPC MTL_':'TEM_ITEM' M'I MHERE MOP&+n=entor2_+tem_+/ +n (@*?#C@*?)) A - MOP&ORGA IIATIO _I- % M'I&ORGA IIATIO _IA - MOP&I <E TOR:_ITEM_I- % M'I&I <E TOR:_ITEM_IORG_I- ITEM_ AME 'UBI <_CO- TRA _PT: !!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!! A$B 'ETE'T-C$A 'tores ?$$ A$B 'E-CTE'T$" 'tores ?$$

%$ter &e$resh Snapshot


select +n=entor2_+tem_+/ ITEM_I-C Item_ 0me ITEM_ AMEC or40n+N0t+on_+/ ORG_Ifrom mr1_sn_s2s_+tems 6,ere +n=entor2_+tem_+/ +n (@*?*C@*?#C@*?)) 0n/ or40n+N0t+on_+/ % A$B; ITEM_I- ITEM_ AME !!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!! @*?* 'E-CTE'T$? @*?# 'ETE'T-C$A @*?) 'E-CTE'T$" ORG_IA$B A$B A$B

select A''EMBL:_ITEM_I- A'':_I-C ITEM_ AME A'':_ AMEC BOM&ORGA IIATIO _I- ORG_I-C BILL_'EPUE CE_I- BILL_'EP_IFROM MR7_' _BOM' BOMC MR7_' _':'_ITEM' MTL MHERE A''EMBL:_ITEM_I- % @*?* A - BOM&ORGA IIATIO _I- % MTL&ORGA IIATIO _IA - A''EMBL:_ITEM_I- % I <E TOR:_ITEM_I-; A'':_I- A'':_ AME ORG_I- BILL_'EP_I!!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!!! @*?* 'E-CTE'T$? A$B "B*"( 'ELECT COM7O E T_ITEM_I- ITEM_I-C ITEM_ AME ITEM_ AMEC COM7O E T_PUA TIT: COM7O E T_PT:C O7ERATIO _'EP_ UM O7_'EP UM FROM MR7_' _I <_COM7' COM7'C MR7_' _':'_ITEM' MTL MHERE BILL_'EPUE CE_I- % "B*"( A - MTL&ORGA IIATIO _I- % A$B A - COM7O E T_ITEM_I- % I <E TOR:_ITEM_I-; ITEM_I- ITEM_ AME COM7O E T_PT: O7_'EP UM !!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!!!!! !!!!!!!!!! @*?) 'E-CTE'T$" ? ?$ @*?# 'ETE'T-C$A ? A$ 'ELECT A''EMBL:_ITEM_I- ITEM_I-C 'EGME T? ITEM_ AMEC BOM&ORGA IIATIO _I- ORG_I-C ROUTI G_'EPUE CE_I- RTG_'EP_IFROM MR7_' _O7R_RT ' BOMC MR7_' _':'_ITEM' MTL

ASCP- Data Collection 32/51

MHERE A''EMBL:_ITEM_I- % @*?* A - BOM&ORGA IIATIO _I- % MTL&ORGA IIATIO _IA - A''EMBL:_ITEM_I- % I <E TOR:_ITEM_I-; ITEM_I- ITEM_ AME ORG_I- RTG_'EP_I!!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!! @*?* 'E-CTE'T$? A$B @A?( 'ELECT O7ERATIO _'EP_ UM O7_'EP UMC BO-&-E7ARTME T_CO-E -E7T_ AMEC O7ERATIO _'EPUE CE_I- O7_'EP_IFROM MR7_' _O7R_'EP' BO'C BOM_-E7ARTME T' BOMHERE ROUTI G_'EPUE CE_I- % @A?( A - BO-&-E7ARTME T_I- % BO'&-E7ARTME T_I-; O7_'EP UM -E7T_ AME O7_'EP_I!!!!!!!!!! !!!!!!!!!! !!!!!!!!!! A$ 'EPLT: ?#*@A ?$ 'EMFG ?#*@? 'ELECT BR&RE'OURCE_I-C RE'OURCE_CO-E RE'OURCE_CO-EC U'AGE_RATE_OR_AMOU T AMOU T_I <ER'EC -ECO-E('CHE-ULE_FLAGC?C.:es.C. o.) 'CHE-ULE_FLAG FROM MR7_' _O7R_RE'' BORC BOM_RE'OURCE' BR MHERE O7ERATIO _'EPUE CE_I- +n (?#*@?C?#*@A) A - BR&RE'OURCE_I- % BOR&RE'OURCE_I-; RE'OURCE_I- RE'OURCE_C AMOU T_I <ER'E 'CH !!!!!!!!!!! !!!!!!!!!! !!!!!!!!!!!!!! !!! ?)B# 'EAsm5lr &$("""" :es ?)BB 'ETester &$("""" :es select 6e&6+1_ent+t2_n0me KOB_ AMEC sc,e/ule/_st0rt_/0te 'TART_-ATEC sc,e/ule/_com1let+on_/0te COM7_-ATEC 't0rt_Tu0nt+t2 'TRT_PT:C et_Pu0nt+t2 ET_PT: from 6+1_ent+t+es MEC MR7_' _-'CR_KOB' M'-K 6,ere 6e&1r+m0r2_+tem_+/ % @*?* 0n/ M'-K&MI7_ent+t2_+/ % 6e&MI7_E TIT:_I-; KOB_ AME 'TART_-AT COM7_-ATE 'TRT_PT: ET_PT: !!!!!!!!!!!!!!! !!!!!!!!! !!!!!!!!! !!!!!!!!!! !!!!!!!!!! 'E-CKOB? $@!AUG!$* ??!AUG!$* "$$ "$$ 'ELECT 'U77L:_T:7E_CO-EC ITEM_IC ITEM_ AME ITEM_ AMEC 7O_LI E_I-C MR7_7RIMAR:_PUA TIT: MR7_PT:C EE-_B:_-ATE FROM MR7_' _'U77L: M'C MR7_' _':'_ITEM' M'I MHERE +tem_+/ +n (@*?#C@*?)) A - +tem_+/ % +n=entor2_+tem_+/ 0n/ M'I&ORGA IIATIO _I- % M'&MR7_TO_ORGA IIATIO _I-;

ASCP- Data Collection 33/51

'U77L:_T:7E ITEM_I- ITEM_ AME 7O_LI E_I- MR7_PT: EE-_B:_!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!! !!!!!!!!! 7O @*?# 'ETE'T-C$A A"")* ?$$ ?A!AUG!$* 7O @*?) 'E-CTE'T$" A"")" ?$$ ?A!AUG!$* 'ELECT MOP&ORGA IIATIO _I- ORG_I-C ITEM_ AME ITEM_ AMEC 'UBI <E TOR:_CO-E 'UBI <_CO-EC TRA 'ACTIO _PUA TIT: TRA _PT: FROM MR7_' _OH_PT:' MOPC MR7_' _':'_ITEM' M'I MHERE MOP&+n=entor2_+tem_+/ +n (@*?#C@*?)) A - MOP&ORGA IIATIO _I- % M'I&ORGA IIATIO _IA - MOP&I <E TOR:_ITEM_I- % M'I&I <E TOR:_ITEM_I-; ORG_I- ITEM_ AME 'UBI <_CO- TRA _PT: !!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!! A$B 'ETE'T-C$A 'tores ?$$ A$B 'E-CTE'T$" 'tores ?$$

S%LES O&DE& 6e will discuss the sales order differently) 6e will loo' at three different 'ind of sales orders vi& Sales Order for Standard (tem) ATO 7odel and 7ulti Level 7ulti Organi&ation /7L7O0. %TO #odel Defore we start the discussion of collecting 7odel : here is what the DO7 loo's li'e for this 7odel.
LE< ITEM_ UMBER Item -esc ITEM_T:7E UOM O7T MEO !!! !!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!! !!! !!! !!! $ 'EATOA$? -elu9 L01to1 ATO mo/el E0 ? 'EATO"$? 7o6er 'u11l2 O1t+on Cl0ss ATO O1t+on Cl0ss E0 :es :es &A 'ECM#$? ??$ < 7o6er 'u11l2 7urc,0se/ +tem E0 :es o &A 'ECM#$A AA$ < 7o6er 'u11l2 7urc,0se/ +tem E0 :es o ? 'EATO"$A H0r/ -+sD O1t+on Cl0ss ATO O1t+on Cl0ss E0 :es :es &A 'ECM#$" ?$ GB H-7urc,0se/ +tem E0 :es o &A 'ECM#$* A$ GB H-7urc,0se/ +tem E0 :es o &A 'ECM#$# *$ GB H-7urc,0se/ +tem E0 :es o &A 'ECM#$) ($ GB H-7urc,0se/ +tem E0 :es o ? 'EATO"$" RAM O1t+on Cl0ss ATO O1t+on Cl0ss E0 :es :es &A 'ECM#$B A#) MB RAM 7urc,0se/ +tem E0 :es o &A 'ECM#$( #?A MB RAM 7urc,0se/ +tem E0 :es o ? 'EATO"$* 'oft60re O1t+on Cl0ss ATO O1t+on Cl0ss E0 :es o &A 'ECM#$@ Mor/ 7rocess+n4 'oft60re 7urc,0se/ +tem E0 :es o &A 'ECM#?$ '1re0/',eet 'oft60re 7urc,0se/ +tem E0 :es o &A 'ECM#?? Me5 Bro6ser 'oft60re 7urc,0se/ +tem E0 :es o &A 'ECM#?A 7roUect M0n04ement 'oft60re 7urc,0se/ +tem E0 :es o ? 'EATO"$# C-!ROM O1t+on Cl0ss ATO O1t+on Cl0ss E0 :es :es &A 'ECM#?" ?)8 C-!ROM 7urc,0se/ +tem E0 :es o &A 'ECM#?* *(8 C-!ROM 7urc,0se/ +tem E0 :es o 1 SKATO306 INTEL PROSet Wirele C!r" P#r$%! e" ite& E! N' N' 1 SKATO30( P')er C'r" P#r$%! e" ite& E! N' N'

( have created this 7odel in 79) Please review S0ATO<=> and S0ATO<=? are Standard 7andatory "omponents /S7"0. ( created a sales order /sales Order !umber K II5?40 for 7odel S;ATO=59 and configured it. 6hen ( run the Data "ollection after the configured item is created) the following two views will be populated. MRP_AN@_SALES_ORDERS_2 and MRP_AN<_SALES_ORDERS_2 as follows. MRP_ANA_SALES_ORDERS_2 : stores reservation data for Sales Order.

ASCP- Data Collection 3!/51

select m0nso=&+n=entor2_+tem_+/ ITEM_I-C ms+&se4ment? ITEM_ AMEC ms+&/escr+1t+on -E'CRI7TIO C 1r+m0r2_uom_Tu0nt+t2 7UOM_PT:C /eco/e(reser=0t+on_t21eC?C.'oft Reser=0t+on.C AC.H0r/ Reser=0t+on.C "C.'u11l2 Or/er Reser=0t+on.) GRE'<ER<ATIO /em0n/_+/ -M-_Ifrom mr1_0nA_s0les_or/ers_= m0nso=C mtl_s2stem_+tems ms+ 6,ere s0les_or/er_num5er l+De .##$B*F. 0n/ m0nso=&+n=entor2_+tem_+/ % ms+&+n=entor2_+tem_+/ 0n/ m0nso=&or40n+N0t+on_+/ % ms+&or40n+N0t+on_+/;

T:7EGC

no ro6s selecte/

6e do not have any reservation on this Sales Order. MRP_AN@_SALES_ORDERS_2 : stores data of the oe8order8lines8all) all Sales Order line information.
select m0nso=&+n=entor2_+tem_+/ ITEM_I-C ms+&se4ment? ITEM_ AMEC ms+&/escr+1t+on -E'CRI7TIO C 1r+m0r2_uom_Tu0nt+t2 7UOM_PT:C /eco/e(reser=0t+on_t21eC?C.'oft Reser=0t+on.C AC.H0r/ Reser=0t+on.C "C.'u11l2 Or/er Reser=0t+on.) GRE'<ER<ATIO /em0n/_+/ -M-_Ifrom mr1_0nA_s0les_or/ers_= m0nso=C mtl_s2stem_+tems ms+ 6,ere s0les_or/er_num5er l+De .##$B*F. 0n/ m0nso=&+n=entor2_+tem_+/ % ms+&+n=entor2_+tem_+/ 0n/ m0nso=&or40n+N0t+on_+/ % ms+&or40n+N0t+on_+/;

T:7EGC

ITEM_I- ITEM_ AME -E'CRI7TIO 7UOM_PT: RE'<ER<ATIO T:7 -M-_I!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!!!!!!!! !!!!!!!!!! @#"@ 'EATOA$?*@#"( -elu9 L01to1 ? 'oft Reser=0t+on ?)$*A#

MRP_AN<_SALES_ORDERS_2 : stores data Standard mandatory "omponents and selectd Option for the sales order.
select m0nso=&+n=entor2_+tem_+/ ITEM_I-C ms+&se4ment? ITEM_ AMEC ms+&/escr+1t+on -E'CRI7TIO C /em0n/_+/ -EMA -_I-C 1r+m0r2_uom_Tu0nt+t2 7UOM_PT:C reTu+rement_/0te REP_-ATE from mr1_0n"_s0les_or/ers_= m0nso=C mtl_s2stem_+tems ms+ 6,ere s0les_or/er_num5er l+De .##$("F. 0n/ m0nso=&+n=entor2_+tem_+/ % ms+&+n=entor2_+tem_+/ 0n/ m0nso=&ORGA IIATIO _I- % ms+&or40n+N0t+on_+/; ITEM_I- ITEM_ AME -E'CRI7TIO -EMA -_I- 7UOM_PT: REP_-ATE !!!!!!!! !!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!! !!!!!!!!!! !!!!!!!!! @*"# 'EATOA$? -elu9 L01to1 ?)$*?# ? ?*!'E7!$* @**? 'EATO"$* 'oft60re O1t+on Cl0ss ?)$*?@ ? ?*!'E7!$* @*#B 'ECM#?A 7roUect M0n04ement 'oft60re ?)$*A" ? ?*!'E7!$* @**$ 'EATO"$" RAM O1t+on Cl0ss ?)$*?( ? ?*!'E7!$* @*#A 'ECM#$B A#) MB RAM ?)$*AA ? ?*!'E7!$*

ASCP- Data Collection 35/51

@*"@ 'EATO"$A H0r/ -+sD O1t+on Cl0ss ?)$*?B ? ?*!'E7!$* @*#? 'ECM#$) ($ GB H-?)$*A? ? ?*!'E7!$* @**A 'EATO"$# C-!ROM O1t+on Cl0ss ?)$*A$ ? ?*!'E7!$* @*#@ 'ECM#?* *(8 C-!ROM ?)$*A* ? ?*!'E7!$* *+++ SKATO30( P')er C'r" 160+1, 1 1+-SEP-0+ *++3 SKATO306 INTEL PROSet Wirele C!r" 160+1, 1 1+-SEP-0+

!ow ( will Progress the Order and create a 6or' Order for the configured (tem and run data collection again) observe what happens to S0ATO<=> and S0ATO<=? S7" in 7#P8A!>8SAL S8O#D #8< and reservation in 7#P8AP98SAL S8O#D #8<. MRP_APA_SALES_ORDERS_2 : stores reservation data for Sales Order.
select m01?&+n=entor2_+tem_+/ ITEM_I-C se4ment? ITEM_ AMEC m01?&or40n+N0t+on_+/ ORG_I-C 1r+m0r2_uom_Tu0nt+t2 7RIMAR:_PT:C /eco/e(reser=0t+on_t21eC?C.'oft Reser=0t+on.C AC.H0r/ Reser=0t+on.C "C.'u11l2 Or/er Reser=0t+on.) GRE'<ER<ATIO /em0n/_+/ -M-_I-C su5str(s0les_or/er_num5erC?C??) 'ALE'_OR-ERC 0to_l+ne_+/ from mr1_01?_s0les_or/ers_= m01?C mtl_s2stem_+tems ms+ 6,ere s0les_or/er_num5er l+De .##$B*F. 0n/ m01?&+n=entor2_+tem_+/ % ms+&+n=entor2_+tem_+/ 0n/ m01?&or40n+N0t+on_+/ % ms+&or40n+N0t+on_+/;

T:7EGC

ITEM_I- ITEM_ AME ORG_I- PT: RE'<ER<ATIO T:7E -M-_I- 'ALE'_OR-ER ATO_L I!!!!!!!! !!!!!!!!!!!!!! !!!!!!! !!!! !!!!!!!!!!!!!!!!!!!!!!!! !!!!!!! !!!!!!!!!!! !!!!!!!!! @*B@ 'EATOA$?*@*B( A$B " 'u11l2 Or/er Reser=0t+on "?)?#" ##$B*&Or/er ?)$A#?

After 6(P +ob is created we have created a supply Order reservation for this sales Order. MRP_AP@_SALES_ORDERS_2 : stores data of the oe8order8lines8all) all Sales Order line information.
select m01?&+n=entor2_+tem_+/ ITEM_I-C se4ment? ITEM_ AMEC m01?&or40n+N0t+on_+/ ORG_I-C 1r+m0r2_uom_Tu0nt+t2 7RIMAR:_PT:C /eco/e(reser=0t+on_t21eC?C.'oft Reser=0t+on.C AC.H0r/ Reser=0t+on.C "C.'u11l2 Or/er Reser=0t+on.) GRE'<ER<ATIO /em0n/_+/ -M-_I-C su5str(s0les_or/er_num5erC?C??) 'ALE'_OR-ERC 0to_l+ne_+/ from mr1_01A_s0les_or/ers_= m01?C mtl_s2stem_+tems ms+ 6,ere s0les_or/er_num5er l+De .##$B*F. 0n/ m01?&+n=entor2_+tem_+/ % ms+&+n=entor2_+tem_+/ 0n/ m01?&or40n+N0t+on_+/ % ms+&or40n+N0t+on_+/;

T:7EGC

ITEM_I- ITEM_ AME ORG_I- PT: RE'<ER<ATIO T:7 -M-_I- 'ALE'_OR-ER ATO_L I!!!!!!!! !!!!!!!!!!!!!! !!!!!!! !!!! !!!!!!!!!!!!!!!! !!!!!!! !!!!!!!!!!! !!!!!!!!! @*B@ 'EATOA$?*@*B( A$B " 'oft Reser=0t+on ?)$A)* ##$B*&Or/er ?)$A#?

ASCP- Data Collection 3"/51

As far as this is concerned no changes. S;$D"T ST59 S;$D"T ST5= $ "omponent S;$D"T ST5> $ "omponent Once this bill is defined the following tables are populated.
SELECT ASSEMBLY_ITEM_ID ITEM_ID, SEGMENT1, BOM.ORGANIZATION_ID ORG_ID, BILL_SEQUENCE_ID BILL_SEQ_ID FROM BOM_BILL_OF_MATERIALS BOM, MTL_SYSTEM_ITEMS MTL WHERE ASSEMBLY_ITEM_ID = 830 AND BOM.ORGANIZATION_ID = MTL.ORGANIZATION_ID AND ASSEMBLY_ITEM_ID = IN!ENTORY_ITEM_ID" ITEM_ID SEGMENT1 ORG_ID BILL_SEQ_ID ####### ########### ###### ########### 830 S$#DCTEST01 %0 183%8 SELECT COM&ONENT_ITEM_ID ITEM_ID, SEGMENT1, COM&ONENT_QUANTITY COM&ONENT_QTY FROM BOM_IN!ENTORY_COM&ONENTS COM&S, MTL_SYSTEM_ITEMS MTL WHERE BILL_SEQUENCE_ID = 183%8 AND MTL.ORGANIZATION_ID = %0 AND COM&ONENT_ITEM_ID = IN!ENTORY_ITEM_ID" ITEM_ID ####### 830' 831 SEGMENT1 COM&ONENT_QTY ########### ############# S$#DCTEST0% % S$#DCTEST03 %

There are three Snapshots involved in this e.ample. 7TL8SYS8(T 7S8S! for (tems) DO78DO7S8S! for bill material header) and DO78(!<8"O7PS8S!. -or each of these snapshot there is a synonym created <i&. 7#P8S!8SYS8(T 7S) 7#P8S!8DO7S) and 7#P8S!8(!<8"O7PS respectively. (f you run the following SCL scripts before the #efresh Snapshot Process is run you will get &ero row returned. (f you run the same scripts after the #efresh Snapshot Process is successfully run. (t will return some row.
SELECT COUNT()* FROM MR&_SN_BOMS WHERE ASSEMBLY_ITEM_ID = 830 " COUNT()* ########## 0

ASCP- Data Collection 3#/51

SELECT COUNT()* FROM MR&_SN_IN!_COM&S WHERE BILL_SEQUENCE_ID = 183%8 COUNT()* ########## 0

Additionally there are some views that are created on the snapshot synonyms) which are used in the data collections process to load the data from the source instance into the G7S" stagingB tables. (n this e.ample there are two views that are used to load the Dill of 7aterial data into the staging tables. They are 7#P8AP8DO7S8< and 7#P8AP8DO78"O7PO! !TS8< After the #efresh Snapshot Process is successfully run. #un the following SCL scripts.
SELECT ASSEMBLY_ITEM_ID SEGMENT1, BOM.ORGANIZATION_ID BILL_SEQUENCE_ID FROM MR&_A&_BOMS_! BOM, MTL_SYSTEM_ITEMS MTL WHERE ASSEMBLY_ITEM_ID = AND BOM.ORGANIZATION_ID = MTL.ORGANIZATION_ID AND ASSEMBLY_ITEM_ID = IN!ENTORY_ITEM_ID" ITEM_ID, ORG_ID, BILL_SEQ_ID 830

ITEM_ID SEGMENT1 ORG_ID BILL_SEQ_ID ####### ########### ###### ########### 830 S$#DCTEST01 %0 3++,+ SELECT COM&S.IN!ENTORY_ITEM_ID ITEM_ID, SEGMENT1, USAGE_QUANTITY USAGE_QTY FROM MR&_A&_BOM_COM&ONENTS_! COM&S, MTL_SYSTEM_ITEMS MTL WHERE MTL.IN!ENTORY_ITEM_ID = COM&S.IN!ENTORY_ITEM_ID -./ MTL_ORGANIZATION_ID = %0 -./ BILL_SEQUENCE_ID = 3++,+ ITEM_ID ####### 831 830' SEGMENT1 USAGE_QTY ########### ######### S$#DCTEST03 % S$#DCTEST0% %

(f you loo' at the LOAD8DO7) procedure for data pull it pulls the Dill of 7aterial data from above two views and populates the following two staging tables. 7S"8ST8DO7S and 7S"8ST8DO78"O7PO! !TS After the data pull is complete and before the purge staging process is started the following SCL scripts can be run.

ASCP- Data Collection 3$/51

SELECT ASSEMBLY_ITEM_ID SEGMENT1, BOM.ORGANIZATION_ID BILL_SEQUENCE_ID FROM MSC_ST_BOMS BOM, MTL_SYSTEM_ITEMS MTL WHERE ASSEMBLY_ITEM_ID = AND BOM.ORGANIZATION_ID = MTL.ORGANIZATION_ID AND ASSEMBLY_ITEM_ID = IN!ENTORY_ITEM_ID"

ITEM_ID, ORG_ID, BILL_SEQ_ID 830

ITEM_ID SEGMENT1 ORG_ID BILL_SEQ_ID ####### ########### ###### ########### 830 S$#DCTEST01 %0 3++,+ SELECT COM&S.IN!ENTORY_ITEM_ID ITEM_ID, SEGMENT1, USAGE_QUANTITY USAGE_QTY FROM MSC_ST_BOM_COM&ONENTS COM&S, MTL_SYSTEM_ITEMS MTL WHERE MTL.IN!ENTORY_ITEM_ID = COM&S.IN!ENTORY_ITEM_ID -./ MTL.ORGANIZATION_ID = %0 -./ BILL_SEQUENCE_ID = 3++,+ ITEM_ID ####### 831 830' SEGMENT1 USAGE_QTY ########### ######### S$#DCTEST03 % S$#DCTEST0% %

(f you loo' at the LOAD8DO7) procedure for ODS data load it pulls the Dill of 7aterial data from above two staging tabled and populates the following two tables. 7S"8DO7S 7S"8DO78"O7PO! !TS. Defore the data is populated in the above two table there is process of ;ey transformation that ta'es place. 6here the Source (nventory (tem (d are 7apped to the inventory (tem (dB in the Planning instance. -or (nventory item (d the mapping is stored in the following table. 7S"8(T 78(D8L(D
SELECT SR_IN!ENTORY_ITEM_ID SR_ITEM_ID, IN!ENTORY_ITEM_ID ITEM_ID FROM MSC_ITEM_ID_LID WHERE 01_2.34.5o16_2547_2/ IN (830 ,830',831 *" SR_ITEM_ID ITEM_ID ########## ####### 830 %333 830' %338 831 %33, SELECT IN!ENTORY_ITEM_ID ITEM_ID, ITEM_NAME, SR_IN!ENTORY_ITEM_ID SR_ITEM_ID, ORGANIZATION_ID ORG_ID

ASCP- Data Collection 3%/51

FROM WHERE ITEM_ID ####### %333 %338 %33,

MSC_SYSTEM_ITEMS ITEM_NAME LI$E 9S$#DC:9" ITEM_NAME SR_ITEM_ID ORG_ID ########### ########## ###### S$#DCTEST01 830 %0 S$#DCTEST0% 830' %0 S$#DCTEST03 831 %0

-inally the Dill of 7aterial data is now in the ODS data store.
SELECT ASSEMBLY_ITEM_ID ITEM_ID, ITEM_NAME, BOM.ORGANIZATION_ID ORG_ID, BILL_SEQUENCE_ID BILL_SEQ FROM MSC_BOMS BOM, MSC_SYSTEM_ITEMS MTL WHERE ASSEMBLY_ITEM_ID = %333 AND BOM.ORGANIZATION_ID = MTL.ORGANIZATION_ID AND ASSEMBLY_ITEM_ID = IN!ENTORY_ITEM_ID" ITEM_ID ITEM_NAME ORG_ID BILL_SEQ_ID ####### ########### ###### ########### %333 S$#DCTEST01 %0 3++,+ SELECT COM&S.IN!ENTORY_ITEM_ID ITEM_ID, ITEM_NAME, COM&S.ORGANIZATION_ID ORG_ID, USAGE_QUANTITY USAGE_QTY FROM MSC_BOM_COM&ONENTS COM&S, MSC_SYSTEM_ITEMS MTL WHERE BILL_SEQUENCE_ID = 3++,+ AND COM&S.IN!ENTORY_ITEM_ID = MTL.IN!ENTORY_ITEM_ID AND COM&S.ORGANIZATION_ID = MTL.ORGANIZATION_ID" ITEM_ID ####### %338 %33, ITEM_NAME ORG_ID USAGE_QTY ########### ###### ######### S$#DCTEST0% %0 % S$#DCTEST03 %0 %

Aser has the fle.ibility in determining when a snapshot of information from the source system should be ta'en) and in deciding what information to capture with each +ob. The data collection program can be set to run upon submission of a +ob re2uest) and at specified time intervals) and to collect different type of information with different fre2uency. -or e.ample dynamic data such as sales orders can be collected fre2uently) while static data such as department resources can be collected at longer intervals. The ob+ective is to set up data collection as needed to create a current replica of information for the APS system to use in its model. To a degree this is an self$balancing decision. (n the incremental refresh /net change0 mode) collection wor'ers can detect and collect only changed data. The data will be at least as old as the +ob run time. Data collection process is run as a re2uest set. Data can be collected from only one instance with each re2uest set. #e2uest sets are divided into one or more FstagesF which are lin'ed to

ASCP- Data Collection !&/51

determine the se2uence in which your re2uests are run. ach stage consists of one or more re2uests that you want to run in parallel /at the same time in any order0. To run re2uests in se2uence) you assign re2uests to different stages) and then lin' the stages in the order you want the re2uests to run. The concurrent manager allows only one stage in a re2uest set to run at a time. 6hen one stage is complete the following stage is submitted. A stage is not considered to be complete until all of the re2uests in the stage are complete. One advantage of using stages is the ability to run several re2uests in parallel and then move se2uentially to the ne.t stage. (n Data collection there are two stages Data Pull Stage and ODS Load Stage. (n the Data Pull Stage : Planning Data Pull) #efresh Snapshot and Planning Data Pull 6or'er re2uest are run. (n the ODS Load Stage : Planning ODS Load) Planning ODS Load 6or'er) and Planning Data "ollection Purge Staging tables re2uest are run. Si. different processes comprise the structure of Data "ollection process each of these processes are launched during the Data collection run.

ASCP- Data Collection !1/51

CONCURRENT PROGRAM Planning Data Pull #efresh "ollection Snapshots Drop "hanged Snapshots

FILENAME 7S""L-AD.pls 7#P"L AD.pls

SHORTNAME PAC0AGE NAME B COMMENT 7S"PDP 7S#-6O# msc8cl8pull.launch8monitor 7#P8"L8# -# SH8S!APSHOT.# # SH8S!APSHOT This file tries to find the changes made to snapshots since the DAS # L AS (f the information being searched for does not e.ist then the snapshot is dropped. This file creates snapshots logs and the Snapshots on 6S7 tables for collecting data for the Planning Server. This file creates snapshots logs and the Snapshots on DO7 tables for collecting data for the Planning Server. This file creates snapshots logs and the Snapshots on (!< tables for collecting data for the Planning Server. This file creates snapshots logs and the Snapshots on 7#P tables for collecting data for the Planning Server. This file creates snapshots logs and the Snapshots on PO tables for collecting data for the Planning Server. This file creates snapshots logs and the Snapshots on O tables for collecting data for the Planning Server. This file creates snapshots logs and the Snapshots on 6SH tables for collecting data for the Planning Server. This file creates snapshots logs and the Snapshots on AHL tables for collecting data for the Planning Server for the APS "7#O (ntegration. This file creates snapshots logs and the Snapshots on 6(P tables for collecting data for the Planning Server. "reates synonym in the APPS schema for snapshots This file creates views on the snapshots for the Planning Server. This file creates triggers on the snapshots for the Planning Server.

7S"D#OPS.s2l 7S"D#OPS

"reate 6S7 Snapshots "reate DO7 Snapshots "reate (!< Snapshots "reate 7#P Snapshots "reate PO Snapshots "reate O Snapshots "reate 6SH Snapshots "reate AHL Snapshots "reate 6(P Snapshots "ollections Synonyms "ollections <iews "ollections Triggers

7S"6S7S!.s2l 7S"6S7S! 7S"DO7S!.s2l 7S"DO7S! 7S"(!<S!.s2l 7S"(!<S!

7S"7#PS!.s2l 7S"7#PS! 7S"PONS!.s2l 7S"PONS! 7S"O!TS!.s2l 7S"O!TS! 7S"6SHS!.s2l 7S"6SHS! 7S"AHLS!.s2l 7S"AHLS!

7S"6(PS!.s2l

7S"6(PS!

7S"SY!7S.s2l 7S"SY!7S 7S"<( 6S.s2l 7S"T#(JS.s2l 7S"<( 6S 7S"T#(JS

ASCP- Data Collection !2/51

CONCURRENT FILENAME PROGRAM Planning Data 7S""L-AD.pls Pull 6or'er Planning ODS Load Planning ODS Load 6or'er Planning Data "ollection $ Purge Staging Tables "ollaboration ODS Load 7S""LDAD.pls 7S""LDAD.pls 7S""LDAD.pls

SHORTNAME PAC0AGE NAME B COMMENT 7S"PDP6 7S"PD" 7S"PD"6 7S"PD"P msc8cl8pull.launch8wor'er msc8cl8collection.launch8monitor msc8cl8collection.launch8wor'er 7S"8"L8"OLL "T(O!.Purge8Staging 8Tables

7S"N"PD.pls

7S"NPADO

7S"8"L8PADL(SH.PADL(SH

Some additional scripts in O7S"8TOP3s2l : directory 7S"D LDAP.SCL 7S"P#O-Y.s2l S"#(PT TO D L T TH 7S"8OP #AT(O!8"O7PO! !TS TADL S 6(TH DAPL("AT # "O#DS 6H ! TH "ASTO7 # APJ#AD S -#O7 99.I.4 This file updates the P#O-(L OPT(O! 7S"8SOA#" 8S TAP to Yes /7S"% Source Setup #e2uired0. This file will be called from the d driver of the "ollections Standard "hec'in at the end. Once the d driver of the "ollections patch has been applied then the profile option is set to Yes. This file updates the P#O-(L OPT(O! 7S"8SOA#" 8S TAP to !o /7S"% Source Setup #e2uired0 once the snapshots) <iews) Triggers) Synonyms have been applied. This is upgrade script for S" purpose. This script is patchset H prere2uisite. This script inserts a record in msc8companies with company8name of P7y "ompanyP. This scripts modifies following inde.es for S" purpose. $ 7S"8TP8(D8L(D8A9 $ msc8trading8partners8u> $ msc8trading8partners8u= $ 7S"8TP8S(T 8(D8L(D8A9 Add Language script for 7S" This s2l estimates the AS"P plan memory si&es of HLS 7DP and S"O. The s2ls in this scripts goes off on the PDS data. This script analyses the 7S" schema

7S"P#O-!.s2l 7S"NAPJ.s2l 7S"N(!DN.s2l

7S"!L(!S.s2l 7S"PL!77.s2l mscstat.s2l

ASCP- Data Collection !3/51

C NC())ENT P) ,)A*
Planning Data Pull #efresh Snapshot Planning Data Pull 6or'er Planning ODS Load Planning ODS Load 6or'er Planning Data "ollection : Purge Staging tables

S+ )T NA*E
7S"PDP 7S#-6O# 7S"PDP6 7S"PD" 7S"PD"6 7S"PD"P

Pl"nnin* D"t" Pull &MSCPDP(


Planning Data Pull is launched by Data Pull Stage. This is the process) which launches and then controls the remaining Data Pull processes /#efresh Snapshot and Planning Data pull wor'er0. The number of wor'ers launched is determined by the parameter defined in the Data Pull parameters. The Planning Data Pull program maintains a list of tas's) and communicates with wor'ers so that it has a constant picture of the status of each tas'. Asing this list the Data Pull program assign the ne.t tas' to available wor'ers. "omplete refresh : (gnores the most recent refresh data and collects all data. (ncremental refresh : "ollects only the incremental changes since the most recent refresh.

Refresh Snapshot (MSRFWOR)


#efresh Snapshot Process consistently refresh one or more snapshots. The refresh snapshot uses Oracle@s replication management AP(Bs following pac'ages DD7S8S!APSHOT.# -# SH. A "omma$separated list of snapshots is provided and the Type of refresh to perform for each snapshot listed* Q-@ or Qf@ indicates a fast refresh) Q"@ or Qc@ indicates a complete refresh. The refresh snapshot process is started and purge the staging tables process is also submitted during the refresh snapshot process is running. -or purging the staging tables 7S"8"L8"OLL "T(O!.PA#J 8STAJ(!J8TADL S8SAD procedure is called. The purpose of calling this procedure is that there is a "O77(T after every tas' : (f the previous data pull failed then there would be data left in the staging tables.

Pl"nnin* D"t" Pull -o .e &MSCPDP-(


As of now there are >I tas's that are performed by the Planning Data Pull wor'er. These tas's are submitted one by one to the wor'er. ach tas' pulls the data from the appropriate source tables and insert the data in the Staging tables.

ASCP- Data Collection !!/51

The Planning Data Pull wor'ers communicates with Planning Data Pull program via the use of database pipes. 7essages sent between processes on database pipes include new tas's) tas' completion messages etc. Please refer to the appendi. for a complete list of tas's and procedures called.

Pl"nnin* ODS Lo"! &MSCPDC(


Planning Data load is launched by Planning ODS Load process. This is the process) which launches and then controls the remaining Data load processes. ;ey transformation ta'es place here before the source data is made is available to APS. ;ey transformation ta'es place only for Ite#s; C"te*o ies; Supplie s; "n! Custo#e s. ;ey Transformation : To trac' data entities bac' to the source instance) APS transforms each uni2ue (D within APS) and this process is called as ;ey Transformation. Jenerate new local (D for global attributes such as ite#s) c"te*o , set) :en!o ; :en!o site) custo#e and custo#e site. Launch the ODS Load 6or'ers to perform "reate) Apdate) and Delete operations for each entity in ODS /7S"PD"60. #ecalculate the sourcing history based on the latest sourcing information and the data from transaction systems. #ecalculate the net resource availability based on the calendars) shifts and department resources information. The Planning Data load program maintains a list of tas's) and communicates with wor'ers so that it has a constant picture of the status of each tas'. Asing this list the Data load program assign the ne.t tas' to available wor'ers.

Pl"nnin* ODS Lo"! -o .e &MSCPDC-(


As of now there are =I tas's that are performed by the Planning ODS Load wor'er. These tas's are submitted one by one to the wor'er. ach tas' pulls the data from the appropriate staging tables and insert the data in the ODS tables. #eadme for patch 3553500
M'CO'0les or/er offset -02s M'COCost T21e M'COCollect+on M+n/o6 for Tr0/+n4 70rtner C,0n4es (-02s

MRP8Cuto$$ D"te O$$set Mont%s profile option is used for resource availability. Please refer to the appendi. for a complete list of tas's and procedures called.

Pl"nnin* D"t" Collection 9 Pu *e St"*in* T"/les &MSCPDCP(


The data in the staging tables is purged after the planning ODS load is successfully completed. The data collection process will attempt to purge the already e.tracted data and any data orphaned as a result of a termination of Data "ollection process.
ASCP- Data Collection !5/51

MRP8Pu *e B"tc% Si3e profile option is used to determine the number of records to deleted at a time. The tables) which are purged by the Purge Staging tables process) are%
7S"8ST8DO78"O7PO! !TS 7S"8ST8DO7S 7S"8ST8D 7A!DS 7S"8ST8#OAT(!JS 7S"8ST8"O7PO! !T8SADST(TAT S 7S"8ST8#OAT(!J8OP #AT(O!S 7S"8ST8OP #AT(O!8# SOA#" S 7S"8ST8OP #AT(O!8# SOA#" 8S CS 7S"8ST8P#O" SS8 -- "T(<(TY 7S"8ST8OP #AT(O!8"O7PO! !TS 7S"8ST8D(LL8O-8# SOA#" S 7S"8ST8DO#8# CA(# 7 !TS 7S"8ST8"AL !DA#8DAT S 7S"8ST8P #(OD8STA#T8DAT S 7S"8ST8"AL8Y A#8STA#T8DAT S 7S"8ST8"AL86 ;8STA#T8DAT S 7S"8ST8# SOA#" 8SH(-TS 7S"8ST8"AL !DA#8SH(-TS 7S"8ST8SH(-T8DAT S 7S"8ST8# SOA#" 8"HA!J S 7S"8ST8SH(-T8T(7 S 7S"8ST8SH(-T8 N" PT(O!S 7S"8ST8! T8# SOA#" 8A<A(L 7S"8ST8(T 78"AT JO#( S 7S"8ST8"AT JO#Y8S TS 7S"8ST8SAL S8O#D #S 7S"8ST8# S #<AT(O!S 7S"8ST8SYST 78(T 7S 7S"8ST8D PA#T7 !T8# SOA#" S 7S"8ST8S(7ALAT(O!8S TS 7S"8ST8# SOA#" 8J#OAPS 7S"8ST8SA- TY8STO";S 7S"8ST8D S(J!ATO#S 7S"8ST8ASS(J!7 !T8S TS 7S"8ST8SOA#"(!J8#AL S 7S"8ST8S#8ASS(J!7 !TS 7S"8ST8S#8# " (PT8O#J 7S"8ST8S#8SOA#" 8O#J 7S"8ST8(!T #O#J8SH(P87 THODS 7S"8ST8SAD8(!< !TO#( S 7S"8ST8(T 78SAPPL( #S 7S"8ST8SAPPL( #8"APA"(T( S 7S"8ST8SAPPL( #8-L N8- !" S 7S"8ST8SAPPL( S 7S"8ST8# SOA#" 8# CA(# 7 !TS 7S"8ST8T#AD(!J8PA#T! #S 7S"8ST8T#AD(!J8PA#T! #8S(T S 7S"8ST8LO"AT(O!8ASSO"(AT(O!S 7S"8ST8A!(T8!A7D #S 7S"8ST8P#OM "TS 7S"8ST8P#OM "T8TAS;S 7S"8ST8PA#A7 T #S 7S"8ST8A!(TS8O-87 ASA# 7S"8ST8AO78"LASS8"O!< #S(O!S

ASCP- Data Collection !"/51

7S"8ST8AO78"O!< #S(O!S 7S"8ST8D(S8P-7"87 ASA# S 7S"8ST8D(S8TA#J T8L < LS 7S"8ST8D(S8TA#J TS 7S"8ST8D(S8DAS(! SS8PLA!S 7S"8ST8D(S8P #(ODS 7S"8ST8ATP8#AL S 7S"8ST8PLA!! #S 7S"8ST8D 7A!D8"LASS S 7S"8ST8PA#T! #8"O!TA"TS

Packa-e .o/0 Proce/1res


for the Data "ollection process.
PAC2A,E NA*E DESC)IPTI N

7S""LAAD.pls 7S""LAAS.pls 7S""LDAD.pls 7S""LDAS.pls 7S""L-AD.pls 7S""L-AS.pls

7S""LMAD.pls 7S""LMAS.pls 7#P"L AD.pls 7#P"L AS.pls 7#P"LHAD.pls 7#P"LHAS.pls

This pac'age e.ecutes the tas' assigned by the Pull wor'er. This pac'age collects data from staging tables to ODS. This pac'age launch the pull programBs 7onitor36or'er processes. This pac'age is used to e.change partitions with the tables. This pac'age launches the #efresh Snapshot process. This pac'age has some functions used while collections.

I3portant S4' scripts


-ollowing are the SCL scripts that are used to create to the database ob+ects used in the Data "ollection Process. The following SCL Scripts are for reference only) they are provided here for debugging purpose.

Snapshot Logs BOMM&SNL.0;< MTLM&SNL.0;<

Create Snapshot Ta !es BOMM&SN&.0;< MTLM&SN&.0;<


ASCP- Data Collection !#/51

MR&M&SNL.0;< WI&M&SNL.0;< &OM&SNAL.0;< OEM&SNAL.0;< Create S"non"#s MR&M&SNS.0;< Create Tr%ggers MR&M&CRT.0;<

MR&M&SN&.0;< WI&M&SN&.0;< &OM&SNA&.0;< OEM&SNA&.0;< Create $%e&s MR&M&CR!.0;<

A5o1t the A1thor


San+eev ;ale is a Sr. Technical Analyst for Oracle 6orldwide "ustomer Support in Orlando) -lorida. He currently supports the entire manufacturing suite of products including 7aster Scheduling37#P) 6or' in Process) "ost 7anagement) Dill of 7aterial.

ASCP- Data Collection !$/51

APPENDI6
Planning Data Pull 6or'er /MSCPDP-0 tas' list. The procedures are defined in the pac'age body 7S"8"L8PALL86O#; #) 7S""LAAD.pls. TAS2 NA*E
TAS;8(T 79 TAS;8(T 7= TAS;8(T 7> TAS;8PO8SAPPLY TAS;86(P8SAPPLY TAS;8OH8SAPPLY TAS;87PS8SAPPLY TAS;87DS8D 7A!D TAS;86(P8D 7A!D TAS;8SAL S8 O#D # TAS;8D(S

TAS;8LOAD8 -O# "AST

LOAD8 -O# "ASTS

P) CED()E NA*E
LOAD8(T 7 LOAD8(T 7 LOAD8(T 7 LOAD8PO8SAPPLY LOAD86(P8SAPPLY LOAD8OH8SAPPLY LOAD87PS8SAPPLY LOAD87DS8D 7A!D LOAD86(P8D 7A!D LOAD8SAPPL( #8 "APA"(TY LOAD_BISAA= for 99.5 source LOAD_BISA=? for 95.? source LOAD_BISAAC for 99.I source. LOAD8DO7 LOAD8#OAT(!J LOAD8 "AL !DA#8DAT LOAD8S"H DAL LOAD8# SOA#" LOAD8T#AD(!J8 PA#T! # LOAD8SAD8 (!< !TO#Y LOAD8HA#D8 # S #<AT(O! LOAD8SOA#"(!J LOAD8 SAPPL( #8"APA"(TY LOAD8"AT JO#Y LOAD8DO# LOAD8A!(T8!A7D # LOAD8SA- TY8STO"; LOAD8P#OM "T LOAD8PA#A7 T # LOAD8AO7 LOAD8ATP8#AL S LOAD8AS #8SAPPLY LOAD8AS #8D 7A!D LOAD8PLA!! #S LOAD8D 7A!D8"LASS LOAD8DAY #8 "O!TA"T

Planning ODS Load 6or'er /MSCPDC-0 tas' list. The procedures are defined in the pac'age body 7S"8"L8"OLL "T(O!) 7S""LDAD.pls TAS2 NA*E
TAS;8SAPPLY TAS;8DO# TAS;8"AL !DA#8 DAT TAS;8(T 7 TAS;8# SOA#" TAS;8SAL S8O#D # TAS;8 SAD(!< !TO#Y TAS;8HA#D8 # S #<AT(O! TAS;8SOA#"(!J TAS;8SAPPL( #8 "APA"(TY TAS;8"AT JO#Y TAS;8DO7 TAS;8A!(T8 !A7D # TAS;8SA- TY8 STO"; TAS;8P#OM "T TAS;8PA#A7 T # TAS;8D(S8 TA#J T8L < LS TAS;8D(S8TA#J TS TAS;8D(S8 DAS(! SS8 PLA!S TAS;8D(S8 P #(OD TAS;8ATP8#AL S TAS;8! T8 # SOA#" 8A<A(L TAS;8PLA!! #S TAS;8D 7A!D8 "LASS TAS;8D(S8 P-7"8 7 ASA# S

P) CED()E NA*E
LOAD8SAPPLY LOAD8DO# LOAD8 "AL !DA#8 DAT LOAD8(T 7 LOAD8# SOA#" LOAD8SAL S8O#D # LOAD8SAD8 (!< !TO#Y LOAD8HA#D8 # S #<AT(O! LOAD8SOA#"(!J LOAD8SAPPL( #8 "APA"(TY LOAD8"AT JO#Y LOAD8DO7 LOAD8A!(T8!A7D # LOAD8SA- TY8STO"; LOAD8P#OM "T LOAD8 PA#A7 T # LOAD8D(S8 TA#J T8L < LS LOAD8D(S8 TA#J TS LOAD8D(S8 DAS(! SS8 PLA!S LOAD8D(S8 P #(ODS LOAD8ATP8#AL S LOAD8! T8 # SOA#" 8A<A(L LOAD8PLA!! #S LOAD8D 7A!D8 "LASS LOAD8D(S8P-7"8 7 ASA# S

TAS;8DO7 TAS;8#OAT(!J TAS;8"AL !DA#8 DAT TAS;8S"H DAL TAS;8# SOA#" TAS;8T#AD(!J8 PA#T! # TAS;8SAD8(!< !TO#Y TAS;8HA#D8 # S #<AT(O! TAS;8SOA#"(!J TAS;8SAPPL( #8 "APA"(TY TAS;8"AT JO#Y TAS;8DO# TAS;8A!(T8!A7D # TAS;8SA- TY8STO"; TAS;8P#OM "T TAS;8PA#A7 T # TAS;8AO7 TAS;8ATP8#AL S TAS;8AS #8 SAPPLY TAS;8AS #8 D 7A!D TAS;8PLA!! #S TAS;8D 7A!D8 "LASS TAS;8DAY #8 "O!TA"T

ASCP- Data Collection !%/51

P'ANNIN, DATA C ''ECTI N

DATA P('' 7)e81est Set Sta-e9

DS ' AD 7)e81est Set Sta-e9

Plannin- Data P1ll

Plannin-

DS 'oa/

Short !ame .ecute 7ethod .ecute -ile !ame Pac'age Dody

% % % %

MSCPDP PL3SCL Stored Procedure


#sc_cl_pull.l"unc%_#onito

MSCCLFAB.pls
)e:resh Snapshot

Short !ame .ecute 7ethod .ecute -ile !ame Pac'age Dody

% % % %

MSCPDC PL3SCL Stored Procedure #sc_cl_collection.l"unc%_#onito MSCCLBAB.pls


DS 'oa/ Worker

Plannin-

Short !ame .ecute 7ethod .ecute -ile !ame Pac'age Dody

% % % %

MSRF-OR PL3SCL Stored Procedure


# p_cl_ e$ es%_sn"ps%ot. e$ es%_sn"ps%ot

MRPCLEAB.pls

Short !ame .ecute 7ethod .ecute -ile !ame Pac'age Dody

% % % %

MSCPDCPL3SCL Stored Procedure


#sc_cl_collection.l"unc%_Do .e

MSCCLBAB.pls

Plannin- Data P1ll Worker

Plannin- Data Collection ; P1r-e Sta-in- ta5les

Short !ame .ecute 7ethod .ecute -ile !ame Pac'age Dody

% MSCPDP% PL3SCL Stored Procedure % #sc_cl_pull.l"unc%_Do .e % MSCCLFAB.pls

Short !ame .ecute 7ethod .ecute -ile !ame Pac'age Dody


APS 5&/51

% MSCPDCP % PL3SCL Stored Procedure % #sc_cl_collection.pu *e_st"*in*_t"/les % MSCCLBAB.pls

DATA C ''ECTI N
SO'RCE (TRANSACTION) DESTINATION (PLANNING ( APS) PLANNING DATA)ASE LIN*

CORE APPS
(T 7S DO7 #TJ 7DS S"P

PLANNING DATA DEFINE RUN B COLLECTIONS

DATA COLLECTION

SOURCE INSTANCES 95.? 99.5 99i

P')LIS+ APPLICATION DATA)ASE LIN*

DEFINE RUN B PLANS

SOURCE &TRANSACTION(
STEP A

DESTINATION &PLANNING 4 APS(


STAGING TABLES CUSTOM DATA MANIPULATION &i$ e+ui e!( STEP @ STEP @ RUN PLAN PLAN FEEDBAC0

APPLICATION DATA STORE

PLANNING DATA PULL


Refresh ADS Snapshot Net Change Handling

ODS LOAD

PLANNING DATA STORE

ODS LOAD

&PDS(
5 ODS Sn"ps%ot E Pl"n Output

&ADS(

OPERATION DATA STORE

&ODS(
P U B L
APS 51/51