Sei sulla pagina 1di 15

1. What are parameters we need to configure for finance analytics before a full load?

For Oracle 11i $$FILTE !"#!$ET!%F!"%%&$!I' $$$ET!%F!"%%&$!I'!LI$T $$FILTE !"#!$ET!%F!"%%&$!T#(E $$$ET!%F!"%%&$!T#(E!LI$T For Oracle EBS R12 $$FILTE !"#!LE')E !I' $$LE')E !I'!LI$T $$FILTE !"#!LE')E !T#(E $$LE')E !T#(E!LI$T

*. What are the domain +alues we need configure for supply chain and order management? ,. In+oice Type 'omain -alues (ic. Types 'omain -alues %rder Types 'omain -alues (ic. $tatus 'omain -alues In+oice $tatus 'omain -alues %rder %+erall $tatus 'omain -alues (ay /ethod 'omain -alues /o+ement Types 'omain -alues In+oice $ource Type 'omain -alues 0. 1ame the cs+ files need configure for /ar.eting ,nalytics. ,. /ar.etingLead2uality /ar.etingLead$tatus 3. 4ow to ,pply $iebel 5 / $chema 5hanges For %racle? %n the machine where %racle "I ,pplications is installed6 run the following command7 ..8%racle"I8dwrep8bin8''LI/( 9: ;:$E < 9( ;(,$$W% '< 95 ;%'"5 connect string< 9) $$E! %LE 9F ;..8%racle"I8dwrep8''L!%LT(.5TL< 9L ;..8oracle"I8dwrep8''L!%LT(.log<

=. 4ow to apply change capture script in $iebel transactional database? In the ',56 na+igate to 'esign < Tables o o o o %n the toolbar6 clic. 2uery In the Image $uffi> field6 enter ?1ull $elect a record ight@clic. and select 5hange 5apture $cripts < )enerate Image and Trigger $cripts In the Trigger and Image Tables dialog bo>6 select ,ll Tables in the List $elect the appropriate database type6 and chec. the :nicode 'atabase option if the database is :nicode 5hec. the )enerate Image Table $cripts option6 and clic. %& This process generates a $2L script $a+e the $2L script and pipe it to the transactional database

o o o o o

A. What is a WI' and what is the reason to generate a %W WI'? ,. WI' means warehouse I'. %W!WI' is generated for maintaining uniBue identifier in the table. C. 4ow do we configure gl natural accounts when you configure for E"$ $ource system? ,. #ou set up )eneral Ledger accounts using the following configuration files that are located in the $(/$er+er8$rcFiles directory7 file!group!acct!names.cs+ @ this file specifies the group account names and their corresponding group account codes. file!group!acct!codes!ora.cs+ @ this file maps )eneral Ledger accounts to group account codes. file!grpact!fstmt.cs+ @ this file maps Financial $tatement Item 5odes to group account codes. D. What is chart of accounts and how do we implement those when you configure your "I apps E. What is the difference between test run and dry run? A. Dryrun

(ossible +alues are True and False. Indicates whether tas.s are e>ecuted without in+o.ing Informatica wor.flows. The following processes are e>ecuted7 change capture6 truncation of tables6 drop and creation of inde>es6 and analyFe statements. This option should be used for debugging purposes only and not used in a production en+ironment. Test Run (ossible +alues are True and False. When set to True6 the e>ecution plan will not stop on errors. 1G. 4ow a parameter file can be created and what it consists of?

A. 'uring an ETL e>ecution6 ',5 reads and e+aluates all parameters associated with that
ETL run6 including static and runtime parameters defined in ',56 parameters held in flat files6 and parameters defined e>ternally to ',5. ',5 consolidates all the parameters for the ETL run6 deduplicates any redundant parameters6 and then creates an indi+idual parameter file for each Informatica session. This file contains the e+aluated name@+alue pairs for all parameters6 both static and runtime6 for each wor.flow that ',5 e>ecutes. The parameter file contains a section for each session under a wor.flow. ',5 determines the sessions under a wor.flow during runtime by using the Informatica pmrep function List%bHect'ependencies. The naming con+ention for the parameter file is ;Informatica foldername<.;wor.flow instance name<.;primary source name<.;primary target name<.t>t ',5 writes this file to a location specified in the ',5 system property Informatica(arameterFileLocation. The location specified by the property Informatica(arameterFileLocation must be the same as the location specified by the Informatica parameter property $(/$ourcefile'ir. 11. Tell me the Fact tables related to the accounts payable? ,. W!,(!",L,15E!F 6W!,(!I1-!'I$T!F6W!,(!I,5T!F J. 1*. What is $5' mapping? E>plain the $5' Type * scenario. 10. What is difference between mapplet and reusable transformation? 13. 1ame the stored procedure need to deploy in transactional database for oracle sales analytics? ,. Find!audit!+alues.

1=. 4ow can we update a record in target table without using :pdate strategy? ,. :sing 'atadri+en concept in session properties. 1A. What modules and what +ersion of "I,(($ you are implemented? ,. ERP Analytics @ %racle Financial ,nalytics @ %racle (rocurement and $pend ,nalytics @ %racle 4uman esources ,nalytics @ %racle $upply 5hain and %rder /anagement ,nalytics @ %racle $pend 5lassification ,nalytics @ %racle (roHect ,nalytics CRM Analytics @ %racle $ales ,nalytics @ %racle $er+ice ,nalytics @ %racle /ar.eting ,nalytics @ %racle 5ontact 5enter ,nalytics @ %racle Loyalty ,nalytics @ %racle (rice ,nalytics 1C. What is the difference between an acti+e and passi+e transformation. )i+e me an e>ample. ,. ,n acti+e transformation can change the number of rows that pass through it6 but a passi+e transformation cannot change the number of rows that pass through it. E>ample for ,cti+e7 Koiner 6 :nion6 ,ggregatorJ.. E>ample for (assi+e7 E>pression6 $eBuence generator6 $tored (rocedureJ 1D. When we use a K%I1E transformation? ,. )enerally Koiner transformation is used to Hoin the heterogeneous tables.

1E. What is the difference between static and dynamic loo. up transformations.
A.

Dynamic Cache:

The informatica ser+er builds a cache of the source when the wor.flow runs for the first time and it updates the cache records dynamically after each row it loads to the target. /eans6 if a target row gets updated6 the dynamic cache also gets updated automatically after that particular row committed in the target Static Cache

5an be configured as connected as well as unconnected loo.up. $upports loo.up on flat file. 5an ha+e any relational operator in loo.up condition. *G. What are the different types of target load types and e>plain the use of them. ,. ormal !oa": The database log is not bypassed and therefore the target database can reco+er from an incomplete session. B#!$ !oa": "ul. loading6 impro+es the performance of a session that inserts a large amount of data to the target database. When bul. loading6 the Integration $er+ice bypasses the database log6 which speeds performance. Without writing to the database log6 howe+er6 the target database cannot perform rollbac.. ,s a result6 you may not be able to perform reco+ery. 21. What is the difference between incremental and full wor. flows and how we can define them Lin a "I ,pps proHectM? ,. In most %"I, proHects we create both incremental and full load mappings for each tables in 'W4 target. "elow you can find the difference b9w both. Full Load is the entire data dump load ta.ing place the +ery first time. In this we gi+e the last e>tract date as empty so that all the data gets loaded Incremental @ Where delta or difference between target and source data is dumped at regular inter+als. 4ere we gi+e the last e>tract date such that only records after this date are loaded. 1ote7 Full load7 $$Last!E>tract!'ate N either lea+e it blan. or gi+e some old date so that all the records are loaded Incremental load7 $$Last!E>tract!'ate N The date from which you need the data Lto get latest recordM.

**. E>plGain :pdate strategy transformation ,. Active and Connected Transformation


Till now, we have only inserted rows in our target tables. What if we want to update, delete or reject rows coming from source based on some condition? In ower Center, we set the update strategy at two different levels! ". #. Within a session Within a $apping

#%. What are &'(, &I) and ) mappings? A. &'( *&ource 'ependent (+traction, $appings!

&ource------'ata load-------------.&tage tables &I)*&ource Independent )oad, $appings! &tage Tables---------'ata )oad---------./AW Tables ) * ost )oad rocess, $appings! /AW Tables ---------'ata )oad----------./AW Tables #0. 1ow can we restrict duplicate records in Informatica? A. /y enabling distinct property in the sorter transformation we can restrict the duplicate records. #2. What technology components do I need to buy to run the BI Apps? A database to host the Data warehouse Oracle BI Suite EE Plus or Oracle BI Suite SE !OBIEE" E#$ component options to OBIEE% either Oracle Data Integrator& or In'ormatica Application content per application

&Oracle Data Integrator !ODI" is currently only a(ailable 'or certain release against a speci'ic release o' a source system) *uture plans are to ha(e ODI 'ully a(ailable .

2%. Why use ',5 for scheduling Hobs?.

A. Scheduling Tasks: It helps in scheduling an execution plan run. An execution plan can be scheduled for
different frequencies or recurrences by defining multiple schedules. (An execution plan is defined based on business requirements for when the data warehouseneeds to be loaded. Execution plans are scheduled in sequence, not in parallel) Automate Execution: It can be quite difficult and error prone to run different workflowsmanually and DAC helps us to automate execution of workflows according to our needs. Easy Flow Management: It helps easy management of workflow execution. ake a simple example I ha!e created " different workflows #rd should only be run after $th and "th workflow. %unning them manually can always lea!e a possibility of error and result in wrong data load. DAC can help us define dependency and order of the workflows in which they should be run. &'. 4ow do you configure a custom wor.flow in ',5 and how can you add that an e>isting subHect area. A. 3ou must create custom wor4flows for all customi5ed mappings. The general re6uirements for
creating custom wor4flows are as follows! Create the wor4flow such that each loads only one table. This helps to integrate the wor4flow with the 'AC. The wor4flow name should match a session name that is used inside the wor4flow. This helps the 'AC to collect certain statistics. 7ail parent if this tas4 fails should be chec4ed for all the sessions within a wor4flow. 7ail parent if this tas4 does not run should be chec4ed for all the sessions within a wor4flow.

The &top on (rrors parameter should be set to " for all sessions with a wor4flow. This parameter is located in the (rror 1andling area of the Config 8bject tab in Informatica 'esigner. &et the appropriate source and target connection values in Informatica 'esigner. If the wor4flow is going to be used for full load command, you can choose to load in bul4 mode *applicable only to 8racle and '/#-9'/ databases,. If the wor4flow is going to be used for the full load command in the 'AC, then in the roperties tab of Informatica 'esigner, set the Target )oad type to /ul4. This re6uires that the target table does not have any indices during the load. The 'AC will drop the indices automatically: no action is re6uired on your part. 7or all entities, such as dimension and fact tables, create two wor4flows, one to be used for a full load and the other to be used for an incremental load. This provides an opportunity to tune each of these load scenarios. If the wor4flow is designed for loading a dimension in a full mode, ma4e sure the wor4flow also includes a session for the unspecified row creation. 3ou can decide to truncate the target table in the wor4flow, but it is necessary that while defining a tas4 in the 'AC, you choose appropriate truncate option. This helps the 'AC to decide whether to drop and create indices on the table. If some sessions have to be run in serial order and if all the sessions need to be rerun upon failure of the wor4flow, then you should consider designing a single wor4flow that has sessions run in serial. If upon failure, not all of the sessions need to be run again, then consider designing separate wor4flows and define dependencies in the 'AC. 9se views created by the 'AC as the main source table in all e+tract processes. If a wor4flow uses a list of values, ma4e it depend on the 7i+ )ist 8f ;alues and Copy to 8)T tas4 definition in the 'AC. If a wor4flow uses e+change rates, ma4e it depend on the (+tract for (+ch<ate tas4 definition in the 'AC. If a wor4flow uses cost lists, ma4e it depend on the )oad Cost )ists tas4 definition in the 'AC. 3ou can import the wor4flows into the 'AC repository=s temporary area while defining tas4s.

&(. 4ow can we build a custom e>ecution plan? A. ". Create custom logical and physical folders !
Tools . seed data . tas4 folders #.<egister the new folders ! eg - Custom>mappings 'esign . source system folders %. $odify e+isting 'AC tas4s to use the custom mappings and wor4flows 0. &ynchroni5e Tas4*s ,<ight clic4 on 'AC tas4 and select synchroni5e. This will add the source and target tables to the tas4. ma4e sure the 'AC tas4 name and informatica tas4 name are the same. 2. Assemble the &ubject Area ?. @enerate e+ecution plan*( , parameters . ( parameters include the Infa repository folders related to the container that the ( belongs to . This could be the missing step.(+ecution . select ( . select arameters sub-tab . verifyAupdate the folder names . @enerate B. /uild the ( #C.

What are the different types of e>ecution plans you .now.

A. An e+ecution plan is a unit of wor4 that enables you to organi5e, schedule, and e+ecute (T) processes. An e+ecution plan comprises the following objects! subject areas, ordered tas4s, inde+es, tags, parameters, source system folders, and phases. 'AC supports single-source and multi-source e+ecution plans, which are described in the following sections!

&ingle-&ource (+ecution lans $ulti-&ource (+ecution lans

&ingle-&ource (+ecution lans! A single-source e+ecution plan e+tracts data from a single instance of a single source system container, such as &iebel B.D or 8racle (/& "" $ulti-&ource (+ecution lans!

There are two types of multi-source e+ecution plans!

+omogeneous This type of e+ecution plan e+tracts data from multiple instances of the same source system. 7or e+ample, a business might have an instance of 8racle (/& ""i in one location and time 5one and another instance of 8racle (/& ""i in another location and time 5one. In such cases, the timing of data e+traction from the different instances can be staggered to meet your business re6uirements. +eterogeneous This type of e+ecution plan e+tracts data from one or more instances of dissimilar source systems. 7or e+ample, a business might have an instance of &iebel B.D in one location, an instance of 8racle (/& ""i in another location, and a second instance of 8racle (/& ""i in yet a third location. 3ou can also stagger the timing of data e+traction when you use this type of e+ecution plan.

%E.

4ow can we .ic. off a full load after running continuous incremental loads?

A. If you select <eset 'ata &ources option ,it will refresh the dates then automatically 'AC runs full load.

)o to Tools @< ETL /anagement @< eset 'ata $ources


%".

What is the prune days concept in ',5 and how you implemented?

A. 'AC stores a value called )A&T><(7<(&1>'AT( at the end of an (T) e+tract. 'uring the ne+t run, 'AC captures changes to the source data )A&T><(7<(&1>'AT( with the )A&T>9 ' date of records in the source. by comparing this

&o if the )A&T><(7<(&1>'AT( is less than )A&T>9 ' of a source record, then the record being processed has either been updated or created between the time of last e+ecution and the current run /ut what will happen if a record in the source is committed between the time of starting the data e+tract and completing the e+tract with a commit date that is less than the )A&T><(7<(&1>'AT( Prune days to the rescue,,, The solution to the above problem is to set the parameter. If the prune days parameter is set to " for e+ample, the change capture process will use )A&T><(7<(&1>'AT( G rune days as the cutoff timestamp for change capture. %#. What is tas4 phase dependency? A. A tas4 phase dependency allows you to change the order in which tas4s are e+ecuted. When you set a tas4 phase dependency, you wor4 with three properties! Action) The action to be ta4en in relation to the phase dependency. ossible values are the following! Wait) Allows you to set a tas4 to wait for other tas4s of a specified phase to be completed before it runs. Bloc-) Allows you to bloc4 all tas4s of a specified phase from being e+ecuted until the specified tas4 has been e+ecuted. .rain) Applicable only for bloc4s. Allows you to specify whether the action you choose affects all tas4s of a specified phase or related tas4s. *3ou can view a tas4=s related tas4s by navigating to (+ecution lans . All 'ependencies and viewing the specified tas4=s predecessor tas4s., ossible values are! All) Indicates the action will affect all tas4s. /elated) Indicates the action will affect only related tas4s. 3ou can view a tas4=s related tas4s by navigating to (+ecution lans . All 'ependencies and viewing the specified tas4=s predecessor tas4s. <9F(>'A3&

Phase) The phase that applies to the action you choose. %%.

What are configuration tags? ,nd what is the use of them e>plain me a scenario.

A. A configuration tag is an object that controls the inclusion of tas4s in subject areas. When a tas4 is tagged, it is not eligible to be included in the collection of tas4s for any subject area, unless the tag is part of the subject area definition HInclude Tas4H property. A configuration tag can function in one of the following ways!

/emo(e tas-s 'rom all sub0ect areas /eassign auto generated tas-s to a speci'ic sub0ect area Add non-auto generated tas-s to a sub0ect area

%0. (+plain about

indices in ',5? When the indices can be dropped and created and why?

A. The Indices tab displays a list of all the indices associated with the selected source system container. It is recommended that you do not register any indices for source tables. 'uring the (T) process, when a table is going to be truncated, all the indices as defined in the repository will be dropped before the data is loaded and will be created after the data is loaded automatically. While this improves the (T) performance, the preconfigured wor4flows have the bul4 load option turned on. The bul4 load will fail if there are indices on the table. Therefore, it is important to 4eep the inde+ definitions in sync with the database. 7or e+ample, if you create an inde+ on the database, and it is not registered in the repository, the inde+ will not be dropped and the load will fail. %2. What is the depth of a tas4? A. The level of dependency is referred to as a depth of tas4. Tas4s that have no dependencies are depth E. Tas4s that depend on other tas4s of depth E are depth ". Tas4s that depend on other tas4s of depth " or E are depth #, and so on. %?. Can we set depth of a tas4 manually if so how? A. 3es, 3ou can define the depth of tas4s manually by creating a tas4 group. 7or creating a tas4 group, goto 'esign . Tas4 @roups . Few and enter the tas4 group name. 8ne the new tas4 group is created, in the lower pane goto child tas4s option and clic4 on AddA<emove button and add your &'( I &I) tas4s. 8nce the tas4s are added go to dependency order column and set E for &'( and " for &I) and by doing this you are forcing the dac to e+ecute &'( first and then &I).

12)

&o' DAC Determines the Or"er o( Tas) E*ecution 'ithin an E*ecution Plan +

,. ,n e>ecution plan is a collection of subHect areas and a uniBue collection of tas.s. , tas. can ha+e prereBuisite tas.s that need to be e>ecuted before its own e>ecution. ',5 determines the order of tas.s based on the following considerations7 , tas.Os source and target table The dependency algorithm first loo.s at a tas.Os source and target table. For e>ample6 suppose table , is populated by tas. T1 by reading from table "6 and table " is populated by tas. T* by reading from table 5. The algorithm would determine tas. T* should be e>ecuted before T1. The dependency algorithm ne>t considers the following7 Tas) ,hase ,n ETL process typically goes through se+eral phases. ,n e>ample of a typical %rder in which phases are e>ecuted is as follows7

1. E>tract 'imension *. E>tract Fact 0. Load 'imension 3. Load Fact and Load 4ierarchy Le>ecuted in parallelM =. Load ,ggregate tables A. :pdate 'imensions , tableOs Truncate ,lways properties The order of e>ecution based on Truncate ,lways properties is as follows7 1. Insert *. :psert 0. (hysical data source 3. (riority ',5 randomly organiFes tas.s that ha+e the same property +alues. If some tas.s need to be e>ecuted in a particular order6 you can create a tas. group that allows you to specify an e>ecution order. &o' "o you "etermine the -n(ormatica Ser.er Ma*imum Sessions Parameter Settin/ in DAC+
13) A. 3ou set the $a+imum &essions parameter value when you register the Informatica &erver in the 'AC client. This parameter specifies the ma+imum number of wor4flows that can be e+ecuted in parallel on the Informatica server. If the number of sessions is 5ero or is not specified, the 'AC server assigns the default value of "E. 14)

0hat are the "ynamic an" static ,arameters in DAC+ 0hat is the use o( them+

,. In the 'AC, there are two types of parameters! static and runtime. The value of static
parameters remains constant for all (T) runs. (+amples of static parameters include language codes and currencies. The value of runtime parameters is dynamic, and the 'AC updates this value for each (T) run. (+amples of dynamic parameters include last refresh dates and last WI' se6uence numbers.

0hat is Authentication (ile+ -( you ha.e "ac client installe" can you access DAC re,ository 'ithout Authentication (ile+
56) A. When you configure a connection to the 'AC <epository, the configuration process includes creating a new authentication file or selecting an e+isting authentication file. The authentication file authenticates the database in which the repository resides. If you create a new authentication file, you will specify the table owner and password for the database.

A user with the Administrator role must distribute the authentication file to any user account that needs to access the specified 'AC <epository 5 )

&o' can 'e mi/rate a DAC re,ository in 1et'een multi,le en.ironments+

,. "y e>porting and importing ',5 metadata. 22. E*,lain DAC e*,ort3im,ort+

,. The 'AC=s ImportA(+port feature enables you to import or e+port source system-specific 'AC
metadata into or out of the 'AC repository. 3ou can use this feature to migrate 'AC metadata from one environment to another, such as from a development environment to test or production environments. #o import DA7 metadata ". #. In the 'AC menu bar, select Tools, then select 'AC <epository $anagement, then select Import. &elect the directory from which you want to import 'AC metadata, or accept the default directory. %. 0. &elect the appropriate source system containers. &elect the appropriate categories of metadata you want to import!

$ogical) Imports all information contained in the 'esign view and database connection information.

System) Imports all information contained in the &etup view, e+cept passwords for servers and database connections.

o
2.

/un #ime) Imports information about (T) runs *contained in the (+ecute view,

If you are importing metadata into a blan4 repository or to completely replace the current metadata in the repository, select Truncate <epository Tables. This action overwrites the content in the current repository. &electing the Truncate <epository Tables option greatly increases the speed of the import process.

?.

*8ptional, &elect (nable /atch $ode to insert the imported metadata into the repository as an array insert. This action increases the speed of the import process.

B. D.

Clic4 8J. ;erify the import process by reviewing the log file K8racle/IK'ACKlogKimport.log.

E8porting DA7 9etadata The 'AC=s ImportA(+port feature enables you to import or e+port source system-specific 'AC metadata into or out of the 'AC repository. 3ou can use this feature to migrate 'AC metadata from one environment to another, such as from a development environment to test or production environments. #o e8port DA7 metadata ". #. In the 'AC menu bar, select Tools, then select 'AC <epository $anagement, then select (+port. &elect the directory to which you want to e+port 'AC metadata, or accept the default directory. %. 0. &elect the appropriate source system containers. &elect the appropriate categories of metadata you want to e+port!

$ogical) (+ports all information contained in the 'esign view and database connection information.

System) (+ports all information contained in the &etup view, e+cept passwords for servers and database connections.

o
2. ?.

/un #ime) (+ports information about (T) runs *contained in the (+ecute view,.

Clic4 8J. ;erify the e+port process by reviewing the log file K8racle/IK'ACKlogKe+port.log.

30. E*,lain the u,/ra"e3mer/e o,tions (or DAC?


A. The 9pgradeA$erge Wi5ard enables you to upgrade and merge the content of 'AC repositories. It contains dialogs that guide you through the stages of an upgrade or merge. The 9pgradeA$erge Wi5ard enables you to suspend an upgrade or merge process before it is complete and return to it at a later time. 3ou can also repeat a stage that you just completed or reset the process to start from the beginning. 55)

0hat are Micro ET! E*ecution Plans + &o' can you Buil" an" run them +

A. $icro (T) e+ecution plans are (T) processes that you schedule at very fre6uent intervals, such as hourly or half-hourly. They usually handle small subject areas or subsets of larger subject areas. The 'AC trac4s refresh dates for tables in micro (T) e+ecution plans separately from other e+ecution plans and uses these refresh dates in the change capture process. After a micro (T) e+ecution plan runs, the 'AC populates refresh date values in the <efresh 'ates child tab of the (+ecution lans tab. If a subject area is used in a regular e+ecution plan *an e+ecution plan with the Jeep &eparate <efresh 'ates option not selected, as well as a micro (T) e+ecution plan,

the 'AC maintains refresh dates for the tables in the regular e+ecution plan in the <efresh 'ates child tab of the hysical 'ata &ources tab *&etup view,. In cases of a subject area being used in both a regular and micro (T) e+ecution plan and the micro (T) e+ecution plan is suspended for a few days but the regular e+ecution plan runs nightly, the 'AC automatically detects the last refresh date for the tables common to both e+ecution plans and intelligently e+tracts only the most recent records for the micro (T) e+ecution plan.

#o create a micro E#$ e8ecution plan ". In the 'AC toolbar, select the appropriate source system container from the dropdown list in the toolbar. #. %. 0. 2. In the $enu bar, clic4 ;iews . 'esign . &ubject Areas. In the &ubject Areas tab, assemble a small subject area. In the Tas4s child tab, inactivate all tas4s that are not re6uired for the e+ecution plan. Create a new e+ecution plan. a. b. c. d. ?. Favigate to (+ecute . (+ecution lans. (nter a name for the e+ecution plan &elect the Jeep &eparate <efresh 'ates chec4 bo+. Clic4 &ave.

Associate one or more subject areas with the e+ecution plan. a. b. Clic4 the &ubject Areas child tab. Clic4 AddA<emove in the bottom pane toolbar.

c. In the Choose &ubject Areas dialog bo+, select the appropriate source system container. d. e. Luery for the subject area you want to associate with the e+ecution plan. &elect the subject area and clic4 Add.

3ou can associate multiple subject areas with an e+ecution plan, but all the subject areas must be from the same source system container. f. B. Clic4 8J to close the window.

@enerate the runtime parameters. a. b. c. Clic4 the arameters child tab. Clic4 @enerate in the bottom pane toolbar. 7or each 'atasource type, enter the appropriate name in the ;alue field.

D. In the top pane of the (+ecution lans tab, ma4e sure the new e+ecution plan is highlighted, and clic4 /uild. The 'AC builds the e+ecution plan. C. Favigate to the 8rdered Tas4s child tab and verify the se6uence of tas4s.

The e+ecution plan is now ready to run as a micro (T) e+ecution plan. "E. Create a schedule for the micro (T) e+ecution plan.

5:) +ow to compare 'olders in In'ormatica? A. We can compare two folders in Informatica using a simple option =Compare= /elow is the procedure. And which will be useful when you want to upgrade your source system in standard 8/I Applications. In'ormatica 'older comparison; 8pen Informatica repository manager *&tart-. All rograms-.Informatica D.?-.client-.<epository $anager, Connect to the repository Clic4 on 7older and clic4 on Compare &elect the repository and folder names what ever you want to compare and clic4 on ne+t &elect the objects whatever you want to compare *&ources,Targets,$appings etcM, and clic4 on ne+t After comparison process completes ,below window will be opened &elect the &ave results to file chec4 bo+ and clic4 on finfish &ave the file *save in rtf format is recommended,.

Potrebbero piacerti anche