Installation Guide
Contents
1. SAP DATA EXTRACTION AND RECOVERY DEX Request Maintenance I1G Cee Sux ana a ma jeee l 447EBG72 aR FOloee Stot Contioter QQ EP G Condions TA Rout Catalog DEU Request 2 All Masterdata Logistics Execution LE 5 25 Statisti B E Logistics General to isti 4 EE Logistics information System uis us 12 234 550 4 031 299 k 2 a Logistics General LO 771 pes a Application development R73 requir 0 Dace ements MD C Bits of Material BOM 38 12228769 4030 899 S Cross Application Objects in HR BP oe 179 135 nt MM t 166 857 Classif i 25 11 476 511 Consignment m orles Field Contents 3 684 897 Appi 5 ice Segment 2 Total Special Stocks with Vendor 568 39 Material Master Status 671 3 noa aP Material Consumption 5 536 583 Dy 548 107 ett 324 852 125 532 t Tables 4 g 2 Number Rangos E Ton zj Installation Guide Copyright Clive Simmonds 01 01 2007 Intelligens IT Solutions Pty Ltd South Africa INDEX 1 INSTALLATION 1 1 Start Here 1 2 License 2 Analysis 2 1 Build Catalog 2 2 Build Dependants 2 3 Local Analysis 2 4 Remote Analysis 3 Catalog 3 1 Catalog Tabs 3 2 Version Management 3 3 Analysis Menu Counting 3 4 Building a Request 3 5 Conditions 3 6 Table substitutions 3 7 Routines 4 Requests Run ZDEX then go to Requests to access this menu 4 1 Models 4 2 Backup and Restore 4 3 Rules 4 4 Request Detail2. 3 Analysis Request Selection B8 Request Description iTable Cnt Remote toca SO _Rference_ Created On ee lives First Request 25 DEX_REMOTE DEX_LOCAL WAT 21 08 2005 po Ss omplete Business Partner 4 DEX_REMOTE DEX_LOCAL Wat j18 09 2005 Technical identifies the RFC destinations for the request Analysis Classification c Technical AE Request Selection B9 Reauest Description Table Cnt _ Status Started by Started On Started At ETA End Time Master Request Identifies the current status of the request including the estimated end time duration 4 1 Models Models are used to group smaller request into a larger request Requests details are still maintained in their own requests but are accessible from one view Request Goto Catalog Rules Tools System Help Save Cti S Refresh F5 f Select F2 Copy FO Delete Shift F2 Model Create Model F6 Backup Add to Model F7 Maintain Models Supermodel 45 consists of request 30 and 32 The request list shows model 45 as EG Request Description e ci ves First Request 30 Complete Business Partner 5245 Business Partner and Assets Request 17 is not linked to any supermodel 4 2 Backup and Restore Lo Request Goto Catalog Rules Tools System Hell Save Ctrl 5 Refresh F5 Select F Copy F9 Delete Shift F2 Model t Backup j Backup Ctrl F2 Restore Ctri F1 Again much like the catalog maintenance Requests can be e
3. using the menu options available within the request SE DEX Professional SAP Data Transter SAP DATA EXTRACTION AND RECOVERY DEX Request Maintenance Bl Cee Sux aH a mDlO I G47RBR 2j eaReoleeo Sten Controler G9 EP Conditions Tl Routines e ea DEU 2 All Masterdata E Logistics Execution LE E Logistics General LO Pe 25 al S E Logistics Information System LIS LIS S 12 234 550 Sa a Logistics General LO 5 771 400 amp Application development R 3 requi 8 quirements MD ha Bils of Material 80M MD x 12 228 769 4 030 899 sx Cross Application Objects in HR BP 5 TER 179135 at agement MM 186 857 S2 Material MAP Profiles Field Contents 25 11 476 511 3 684 897 2 Price S 2 4 Total pecial Stocks with Vendor 563 K 2 Material Master Status 671 72 Materi z inate pease A 58107 Tables 2 Number Rangos E Toa nt USER MANUAL Copyright Clive Simmonds 01 01 2007 Intelligens IT Solutions Pty Ltd South Africa 3 Catalog At this point we should have installed Intedex twice on local and remote The local server should contain a catalog that is an accurate reflection of both local and remote The catalog should contain a local and remote count and should have dropped all empty tables from the catalog There are now enhancements that can be done to the catalog Thereafter we will build a request containing a portion of the catalog and ex
4. we only selected client DEPENDANT tables You can include client independant tables as well but take care when moving these tables as you will be affecting data across all clients It is possible to run the catalog build on selected tables and this is our suggestion with client dependant tables Identify an application area or look at a single table determine its development class then build the catalog using the development class with UPDATE CATALOG Switched on WRITE RULE Note that all tables require a WRITE RULE to be set for them to write to the WRITER or Calling Client By default INTEDEX leaves all WRITERULES blank This can be changed using mass change options or manually selecting tables to be converted 2 2 Build Dependants Press the DEPENDANTS icon from the catalog screen 42 Dependants Use the default selection criteria presented and execute This program will analyse each table and determine its relationship to other tables It will also reclassify certain tables if the table relationship or Program Edit Goto System Help G 3a 180600 BAR S152 nA aM DEX Analyse Table Dependants Dictionary Table to Class Classification I E to am Options Master Data Correction Date Field Analysis New Analysis Report Unresolved tables Analysis Menu Analyse Archive Analyse Views Analyse Entities Analyse Logical Databases Analyse BDT Analyse Check Tables Analyse Fields Table Name Groupings Ret
5. _ Co LeCount Rm Count Remain LcDB Size eS EE A ee ee ee E COMPLETE ADCNTRYQU Countries with active quarter ss o Q oQ o o Zooo ee ee eee Shadow Table Assignment Pers This i is used to keep track of the transfer A Yellow icon indicates 100 match An empty upside down box indicates a table that is empty on both serves and should be removed from the requests A grey light indicates a tables that has data in either systems but do not match LC Local RM Remote Rules Database Tables 423 Number Ranges Long Text Classification 7O Status gt Packages A Analysis Siats Stats Mable Name Shotin mmm 7 is an ETT tab It specifies the WRITE RULE that must be Td after data is read Write Rules REPLACE SUBSTITUTION TABLE uses the catalog substitution table to WRITE to UPDATE OLD AND INSERT NEW This will perform a standard UPDATE but will not remove data from any table REPLACE this option will delete the data from the client prior to the transfer It is the fastest technique and is faster when working on single client systems Data is truncated in this case allowing the database to self defragment INSERT NEW ONLY This will insert new records and leave old records untouched ROUTINE DRIVEN This will extract the data then pass the data to a ROUTINE written with the routine builder Here the data can be dealt with accordingly REPORT RESULTS This will not write the dat
6. a to the table in any way Data is however logged and can be viewed via the menu ANALYSIS RESULTS Packages Packages are used when Parent Child Dependant relationships have been applied A parent is needed to read data for a child The parent must first extract its data then compile a package of data The child then extracts its data according to this package The package consists of an optimised range of keys Classification gF Status amp Rules Packages 14 Analysis Stele saus __Parent_Tabie Name _ Short text Read aipe Parent Saves to Package E a a Assignment Bu ADDRNUMBER PERSNUMBER DATE_FROM NATI e This tab defines the keys and the field format of the package table e Analysis assists the RULE builder by identifying predefined fields useful for implementing rules For instance if the table has a clear date field then the field name is specified on this tab Conditions Condition List ollel EY Values ssign F Unassign Request 150 Table ADR Parent Condition List 1 Condition Keyword Descripti on This is an extension of the condition builder in the catalog From here you can create a condition Select fields for the condition And specify the values need for the condition Once a condition is defined the condition must be assigned to a table s Select the condition number and press the assign icon Save and exit Analysis Before transferring data it is important to analyse th
7. able that must be read before this table READFIELDS is the fieldname on this table that links to the parent table The parent table will have a SAVEFIELD Analysis This tab contains extra details used to perform advanced data extraction using intelligent filters 3 2 Version Management Catalog Edit Analysis Request Configuration System Save Cine Build Version Management Backup Print Ctrl F Restore Other Shift F5 Version Comparison Version Management Load Suggestions The catalog can be saved and restored compared and corrected Backup and Restore options create XML data files on your PC This allows for easy migration to other systems e Version Management allows you to toggle versions within a system without any upload or download e Load Suggestions is used to overrule a catalog with enhancements previously downloaded from sy datum or another system Edit Menu Most of the edit functions require a column to be highlighted selected first Search and Replace Select a column then select this menu option 3 3 Analysis Menu Counting Analysis Request Configuration System Help Count Local Record Count Shift F7 Text Size Report Ctrl F 8 Clear Remote Count Clear Local Count The basis for Intedex is its ability to see what tables are in use A database count is needed This can be done in two ways Firstly the traditional row count will access all rows in a database table If the table is large the count takes lon
8. aean IM o I6 l OS CJ Master Data 560 376 685 i Basis Components BC 494 3f6 685 i Cross Application Components CA 45 0 0 I Application Indpendant N A 17 0 D b J Serice SV 2 0 0 I Siamease Development Library 403A Z 0 0 gt J User Defined 37 0 0 The application hierarchy window is used to select table groups by double clicking on a node Database Tables 423 Number Ranges l Long Text Classification Status G Rules amp Packages Analysis e Database Tables Select this to deal with the tables in a request e Number ranges This tab is used to extract number range status information from the remote system e Long Text This tab is used to full long text for text related to tables in the request Database Tables a Number Ranges Long Text Classification T Status te Rules gh Packages 4 Analysis Classification Database Tables 423 Number Ranges Long Text amp Status amp Rules amp Packages A Analysis Status Status Table Name Table Type fer Hier na OMPLETE ABAPHTML System a EI ABAPHTML for Buf ABLE M BC ABA LA IEJ OMPLETE paced a ountries with active quarter ABLE M BC SRV ADR Specifies the table name and table class DEX A is the TE IIET to the DEX analysis Class is modifiable and can be altered Note that you can double click on a table name to view the table dictionary definition Status Status Status Table Name _ Project Ps
9. ax Depend Depends Max Query l Queries Cnt Max Process Max Block Size Writer or Caller RFC M Reader or Destination REC DEX_SOURCE DEX_TARGET Req No Range Small Cnt Rout No Range E Large Cnt N Range Adj Expiry Days _ Log System settings must be configured on both SOURCE and TARGET systems Firstly the Catalog is named according to the SAP System ID or SID Max Drivers depend and query settings are only required on the TARGET server Max Process Max Process governs the overall number of work processes allocated to DEX on the target server regardless of the number of drivers set Max Block Size Max Block Size is the number of records transmitted between the systems It is advisable to set this as high as possible The higher the number the few packages sent and this reduces the workload on the system On average we usually look at a value between 30 000 to 50 000 Our training system shown above is set to 300 to demonstrate packaging RFC Destination Apply the RFC destination configured previously It is critical that this is set correctly on both systems as INTEDEX communicates bidirectionally It is also important the if the RFC destination names change that all REQUESTS are adjusted to match contact support for more detail on this conversion Other options are optional N Range Adj is used to bump number range statuses up by a value when synchronising number ranges across systems INTDEX will increase
10. ct was c BUTOG1 COMREG_DAT B Date of entry in trade registe BUTO50 CRDAT A Date on which the object was c Using the keyword selection the program has identified the following tables in the request It flags each table with a HIT status A indicates that there is a high chance that the correct field has been identified in the table that matches the Creation date specified B indicates that the field is close C would indicate that some conversion is required Routines are used to perform this conversion Assigning rules to a request ga Assign This is done by first selecting the request from the request list Lo Assign Resident Rules to Request j Description BE x At this point the rule should know how to apply a filter to each table in the request The rule in this case called STATUS is now assigned a selection value Here we see the condition is EQ active The icon _ appears on the request list when a rule has been assigned to the request 4 4 Request Details Double click on the line to select a request The screen is divided into sections Classification Status window showing overall summary Application DEX Start 93 15 24 information This window can be hidden by Project DEX 23 15 30 pressing the icon on the top Status OO Duration 15 Statistics Local Remote Percentage Records 9 935 376 2 642 Size KB 2 785 685 407 DEX Application Components v CSAP Application Hierarchy r
11. d The routine builder is available to create these routines as well as transport code between systems Routines are covered in more detail in the Developers guide to Intedex 4 Requests Run ZDEX then go to Requests to access this menu or Request Goto Catalog Rules Tools System Help Ge 1 4186 0600 BHR 8053 AA l og DEX Request Selection E s ea E Sh create Model Eh Append Model Build Rute Assign Request aP Technical af Analysis Classification o Selection pEi Request Descrptr Tabl ppi Pro cata Rea Tee Re lives First Request 25 fc esth Standalone Reque Tone Request a omplete Business Partner ae ple hemes r a ea fata E m e F ij ho cn ne jamease Scripts ao stk jamease Scripts with Text ee Secu Y E Ee Al A Lb 3 D b f D Lu f ko fl a J TI A 4 al b a a u a a a D JE D f vi The initial request screen serves as a selection for request as well as a front end for functions that apply to all the tables within the request Firstly each request has a request number The table count identifies the number of tables in the request Classification Classification am Technical ds Analysis Again details are separated into tabs Classification is used to identify the request along with the number of tables in the request Technical Classification P Technical
12. e request This requires a local count on the request as well as a remote count Analysis Controller Extras System Help Clear Count Local Selected Once the tables have been counted empty tables can be SQL Trace Local All removed to clean up the request and only focus on tables that Results Remote Selected actually contain data Remote All Select Differences Remove Empty SQL Trace lf the user believes that some tables may be missing from a request Intedex has a trace function that can add additional tables to the current request Analysis Controller Clear Dex will prompt for a transcation code Capture the transaction in full then save and Comi exit DEX will detect the tables that are missing and add them to the request SQL Trace automatically 4 5 Executing a Request A request is handled by the REQUEST CONTROLLER First select tables in the request and READY them for processing Then start the controller by pressing the Stat Controller icon Request Controller meals Edit Goto System Help g 2 48 CGO BAR Anaa RAI A DEX Request Controller Frontend Request number i50 Controller Action y Table Record Count only Full Table Read and Write O Number Ranges O Long Text O Test Only O Debug breakpoint C Apply Dependants Logic Read Associated Text e The controller allows you to perform a count or a database read and write e Apply Dependant Logic is needed if Parent Child re
13. ecute this request to extract from the remote system 3 1 Catalog Tabs Table List 3 Status gP Technical a Dependants da Analysis Table Name Short text DEX Class Read Type Write Rule ABDBG_BPS ABAP Debugger Breakpoints Transaction EjfTransaction HDriver Update old and ABDBG_INFO ABAP Debugger Information on B Transaction Transaction jPriver WUpdate old and M SWwWHRINDEX ime Stamp for Indices in OrgMa Transaction ransaction Driver Update old and T4 ma TA TA This list contains the tables falling below the selected application area Key information e DEXCLASS the type of table we are dealing with e READ TYPE _ Driver Dependant e WRITE RULE default write rule can be overwritten in request Status Tables List gp Technical x Dependants 43 Analysis ene Shorttet Status PS LcCount__ RmCount_ Difference__ __ Lc DB Size_ Rm DB Size Row Size _ ABDBG_BPS ABAP Debugger Breakpoints S TD Status always shows the row count and database size for each table across both systems e LC Local e RM Remote e PS will highlight when both match e Database size is in MEGS Technical Table classification details Dependants i Tables List Y Status Technical AEC EE d Analysis _ Table Name Shorttet Parent Save Fields Read Fields C ZDEXCOD DEX Conditions Detail DEXCOH POND ITION C ZDEXCOH DEX Conditions Header CONDITION Parent is the t
14. ger The second method is to use the statistics collected from the last Database Optimiser Run This will retrieve statistical data and although this may be fairly accurate it does not update when new data is created This menu is used to execute local and remote counts on the catalog It is possible to perform a local and remote count on a request then push the results from the request back to the catalog 3 4 Building a Request g Build Catalog To build a request check the checkbox next to the selected tables or check the checkbox on the application tree to flag larger volumes gt Create Request Press the Generate Request Icon E DEX Catalog Frontend Catalog Set Classification lt Description Name of request Application DEX Project Create New Request Add to existing Request Request number SET This is a filter that only allows certain table types to be added to the request The SET will also add extra logic to a request After a request has been created several rules and enhancements may be added When a new request is created these enhancements can be reapplied via the SET This requires a previous request to be saved to a set first Enter the classification information and press EXECUTE L DEX Table Catalog DEX Catalog Frontend Req type Status Catalog Reference Appl Project Dest DEX_REMOTE Caller DEX_LOCAL Tables Note the request number 152 has been created 3 5 Conditi
15. ions Sever 2 Analysis 2 1 Build Catalog Build Catalog From ZDEX or transaction ZDEXCATALOG Press Catalog and Execute A blank catalog will be presented Press F6 or Press the BUILD CATALOG icon Depending on your system this could take a minute or two to run Return back to the catalog screen on completion or Program Edit Goto System Help 1 IB CGG GHB HHosS FH ew DEX Catalog Build Table name to gt Delivery class Client specific Data class Development class Create Catalog Update Catalog Delete Catalog Report Complete Catalog Report Errors Separately DEX Catalog Build B E Complete Catalog Date 14 10 2005 06 18 32 User BCUSER Records 2 436 Table Name Tab cat wolfe ia FE DECI D evelopm ent cass Dex Class Appl Hier Short text RANS cjo APPLO SAPDMCILSMW CA GTF Client dependant entries i TRANS REO PLoS AUTH ETERNAL ROLES TEMEI E it bree S AUTH_EXTERNAL LES TRANSP Xx G 4 APPLO S AUTH _EXTERNAL 5 TRANSP X X C 1 APPLO S AUTH_EXTERNAL i BC SEC USR PFC SAP Authorization Assistai S AUTH EXTERNAL BC SEC USR PFC SAP Authorization Assistal AAF_ ROLES TRANSP X X Gii APPLO S_AUTH_EXTERNAL C BC SEC USR PFC SAP Authorization Assistal BC SEC USR PFC SAP Authorization Assista BC SEC USR PFC SAP Authorization Assistal BC SEC USR PFC SAP Authorization Assistal CLIENT INDEPENDANT TABLES In the analysis above
16. lationships are needed e Read Associated Text should be selected if Long text relations have been defined J Test only will check that a request can be transmitted to the REMOTE server That data can be read and transmitted back to the LOCAL server and that the data can be written to the LOCAL server e DEBUG BREAKPOINT this is for internal use only Queue Controller The Request Controller adds your request details to the READER work queue This is visible via the transaction ZDEXQUEUE or program ZDEX QUEUE You must be logged into the READ client to view this queue ae Edit Settings System Help G 1 HB Ge CHB AAD HA Oe DEX Current Workload Queue 9 Start Controller Request 150 Queue fa Process Overview 9 Extract Area Packages Job Overview Settings Press the refresh icon to update the screen Press the icon to flush the queue Press the 22 _ Start Control ler to wakeup the controller if nothing is running 5 Settings Queue fA Process Overview g Extract Area Packages Job Overview i SARs Catalog WAT Work Processes Drivers Dependants Query Count Nax 1 Current i B Total Allowed Work Management Transmit Size 20 Mb Alloc Space 100 Mb Auto Tune The settings tab allows REMOTE settings to be altered Max indicates the maximum number of jobs running concurrently that can be busy Current indicates the current number of concurrent jobs running Total allows overr
17. ons A Condition allows you to define a filter on large tables It consists of a header with details The header identifies the condition and the detail section outlines the filer criteria Note that the condition functionality in the REQUEST is better Request Configuration System Helo Requests t conditions Maintain Conditions E Table View Edit Goto Selection Criteria Utilities System Help 2 1B 6 0H8 S143 A Change View Condition Header Details Zcondition 1000000030 E Condition Header T 1 Condition Detail a EEE Table Name ADRE Abbreviation TEST Description test T 0 Condition Header Condition Detail Note the condition number 100000030 3 6 Table substitutions Configuration System Help system Settings Ctril Shift F2 Actions shift Ctr 0 Table Substitution Ctri F12 Change View DEX Table Substitutions Overview New entries DEX Table Substitutions Parent Table Name jo eeskopo RSPB Table substitution allows TABLENAME to be read but the results are written to the SUBSTITUTE table Note that if a table has been joined to a parent the the pair must be specified together 3 7 Routines A routine is a subroutine written in ABAP Routines can be used to alter assist with READING WRITING and FIELD SUBSTITUTION If additional logic is needed anywhere in the process this logic can be coded into a routine The route has a type that controls where the routine can be use
18. s 4 5 Executing a Request 5 Settings OO N YN WD YW YO 12 13 14 14 15 16 17 17 18 18 19 19 20 22 26 21 1 INSTALLATION 1 1 Start Here Run transaction ZDEX 1 2 License Run transaction ZDEX Enter supplied license code If you do not have a code contact clive sy datum com or frank sy datum com Configuration 1 2 1 RFC Destinations Transaction SM59 Create 2 RFC destinations on both Source and Target Systems e Source is the driver client or client that data will be WRITTEN to Requirements are sourced from this client e Target is the client where data is READ Requirements are added to the Target client queue for processing Define a User for DEX to login as and add the user details to the RFC destinations See details below RFC Destinations R 3 connections DEX_SOURCE DEX Source DEX_TARGET DEX Target Client Users A user is required on both Source and Target systems The user on the Source system does not need to have dialog capabilities The user on the Target system only needs dialog capabilities if the Remote Queue will be used If the remote queue is not used then log onto the target system manually and run transaction ZDEXQUEUE to monitor the DEX work queues System Settings Execute transaction ZDEX Catalog H9 Request 2 Controller iy Work Queue Press the System settings icon to maintain DEX system settings Catalog WAT DEX System Settings Max Drivers 5 Drivers M
19. the number range as long as the number does not go beyond the upper limit within the range Local Processor Settings Local Processes 1 Busy wait time 5 seconds Log RFC Destinations Remote DEX _REMOTE Remote Admin DEX_ADNIN Local DEX _LOCAL Number ranges No Range offset Reg No Range Rout No Range Work Processes not needed for local Drivers Depend Query Count Max 1 1 1 Current E 0 Total Allowed 1 Transmit Size 20 Mb Alloc Space 160 Mb Auto Flush Auto Tune Local Settings The only settings that are important on the local server are the RFC destinations and the Local Processor Settings Local Processor Settings Local Processors this identifies the maximum number of local work processors to be used or are available to DEX Busy wait time When the maximum work processors have already been allocated any further incoming request will sleep for the Busy Wait Time before rechecking Actions The actions configuration table identifies what actions can be performed on the READER client DEX is preconfigured but double check that the READER client has roughly the following settings Go to the catalog via transaction ZDEXCATALOG Select the menu gt Configuration gt Actions Check that the following list exists DEX Action Table fem o oo fet o m Suggestions While still in the catalog select the menu option T Menu gt Configuration gt Suggestions gt Load Suggest
20. ules the number and ensure that no more than the total number are running Auto Tune This is used to allow Intedex to automatically speed up or slow down on the number of background jobs being used Settings defines the maximum If a particularly large table were to be read Intedex may automatically reduce the max number so that the system is not overloaded One could see the problem if the top 10 volume tables all start reading together The Autotune option uses the Alloc Space field to determine when it should start restricting work processes gt If the max allowed is set to ZERO no jobs will run The Slip icon on the application toolbar will allow a single table to execute even though the settings indicate 0 H Queue Status Request Farent Table Name Package Job no Job name H ga 32 BEFF A 685816617 READ S688 8888327BKPF O660006006 ga 32 BSEG A 68581661 READ B68 88888327BS5E6 BB60800008 The flag indicates the task handler has scheduled a job see right hand side and that the job has started reading the data Queue Status Request Parent Table Name Package Job no Job name Action E EY 32 BSEG A 86581661 READ BAGH HH88376SE6C AB8bbbb008 READ The calculator indicates that the job has read the data and is working out how to get it back to the LOCAL server The icon will change to a fork when the data is being transmitted and again once it has been received To maintain system settings use the menu option Environement S
21. urn to the catalog after the analysis is complete and REFRESH for health sake FIELD ANALYSIS This option is available within the catalog but has become obsolete as it is built into the table dependants program 2 3 Local Analysis Local Analysis consists of performing a local record count of the tables within the catalog This gives an indication of how much data already exists vs the data in the target system From the catalog select the menu option Actions gt Local Record Count The only parameters that need to be changed are the lower runtime parameters If you have a large local system with many work processes set the max count processes to a number closer to 20 match If you only have 1 or two background processes set this parameter to 1 rather than 2 Runtime Settings Max Count Processes 2 Calc Local Database Size While the program is running it will provide a progress Note that it only does this if it has idle time hence you will not see every table being listed in the progress 2 4 Remote Analysis Remote analysis is done via a request Build a request check that write rules are set Before writing data perform a remote COUNT This is done by building a request resetting all tables then starting the controller Within the controller select the RECORD COUNT action and continue DEX will count the records in the READER client and return the data back to the request Once complete update the catalog from the request
22. xported to XML and restored Catalog Rules Jools System Catalog gt Request Fe Request Catalog Correct j I F I These menu options allow rules from the catalog to be reapplied to a request It also allows local and remote counts from a catalog to update the catalog 4 3 Rules Rules are used to define selection criteria much like conditions The primary difference is that a rule is applied to a range of tables whereas a condition only applies to one table Building a Rules a Build Rule Rules Tools System Help Build Rules shit F4 The Rule builder will guide you through the process of creation a rule Assign Rules Shift F4 as well as the analysis results Maintain Rules ohift F5 Rule CREDATE Rule Description Creation Date Like Field BUTGG8 CRDAT Keywords Creat Entry Capture CPu e A rule called CREDATE is created The rule is a date and is defined by the type of fields called CRDAT This simply defines the rule CREDATE to be like a CREATE DATE field e Keywords is a list of words that other tables may use to define a similar field DEX needs to look at each table independently to identify the field in that table that can match the rule field e After an analysis has run the following results are available via the MAINTAIN RULE menu Dialog Structure Fields Cimi Rule l Table Name Field Name Hit H Fields CREDATE ADRDIFINFO START_DATE wT of Difference Table Quart BUTO CRDAT A Date on which the obje
23. ystem Settings
Download Pdf Manuals
Related Search