data load user manual
LINK 1 ENTER SITE >>> Download PDF
LINK 2 ENTER SITE >>> Download PDF
File Name:data load user manual.pdf
Size: 1546 KB
Type: PDF, ePub, eBook
Category: Book
Uploaded: 26 May 2019, 14:19 PM
Rating: 4.6/5 from 562 votes.
Status: AVAILABLE
Last checked: 9 Minutes ago!
In order to read or download data load user manual ebook, you need to create a FREE account.
eBook includes PDF, ePub and Kindle version
✔ Register a free 1 month Trial Account.
✔ Download as many books as you like (Personal use)
✔ Cancel the membership at any time if not satisfied.
✔ Join Over 80000 Happy Readers
data load user manualIf your questions still aren't answered having read There are a large number of new features and links to some of the most significant additions are included below. Full details of the new features in Version 5 are on the DataLoad web site. Do you want to add them? Search As the name of the module suggests, this process is designed for the initial load of data which means the import should be done into a fresh client since the data does not get updated but inserted only !Click the Add Modules tab and find the Initial Data Load module within the list of all modules available in the central repository. Most popular tools like Microsoft Excel or OpenOffice Spreadsheet have an option to export data into this format.This template is only an intermediary step that simplifies preparation of resulting CSV files that can then be imported into Openbravo ERP. Each sheet of this template must be exported into its own CSV file later.Data extraction from this data sources and transformation of this data to the format required by the IDL module can be very hard and take a lot of time if has to be done manually.Once this is done instead of extracting and transforming all these data manually an ETL tool can help with this task. And if you want to look for another tool have a look to the Tools, Open-source ETL frameworks, and Proprietary ETL frameworks sections of the ETL document.Here are some generic ones that will enable you to import the sample data given here into a fresh client. Note that the import of your custom data into your custom client is analogous (but not identical) to this process! Hence, create the necessary enterprise structure that will then hold the data. If you are going to import entities that require accounting or you will use the accounting functionality of Openbravo ERP be sure to create legal Organization(s) with accounting.http://huynhgiabaohotel.com/uploads/FCK/execute-job-oracle-manually.xml
- Tags:
- data load user manual, data load user manual, data load user manual pdf, data load user manual download, data load user manual free, data load user manual software.
Details on how to model the structure of the enterprise within Openbravo ERP and create the client and the organizations accordingly can be found here. When creating the client, make sure you select the Initial Data Load reference data along with other you might need to be initialized within the new client, for example: Initial Client Setup Then, when creating the organization using the Initial organization setup process, remember the name that you give the organization since it will be very important later when importing legacy data into a specific organization. For example: Initial organization setup To do so, follow the steps:Keep in mind that these sample files are only the result of saving each one of the sheets inside the IDLImportTemplate.xls template as a separate CSV file explained earlier.It checks data types, mandatory fields and that references to fields in other tables are valid (such as 'Country', 'Region', 'Tax Category', etc).The steps to follow in this case is:The result is 'Success' if all rows have been processed successfully and is 'Fail' if any of the rows has been rejected, because it does not pass a validation check or because it cannot be imported into the system as part of the Process process.If the cause of the rejection is a Java exception, the second log panel will display the full Java stack trace that can be used to discover the cause of the error.Each bank must have a business partner associated in order to have transactions associated with, such as bank statements.All the entries are posted to the general ledger.However, we recommend doing a few tests in order to double check the quality and consistency of the imported data.This process only needs to be executed in case when the accounting process is not scheduled as a background job. If it is, the process will automatically post all pending transactions that need to be accounted for.http://huyminhtechco.com/storage/excise-manual-2015-16-pdf.xmlThis process only needs to be executed in case when the accounting process is not scheduled as a background job. If it is, the process will automatically post all pending transactions that need to be accounted for.This page was last modified on 8 June 2012, at 05:28. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License. This page was last modified on 8 June 2012, at 05:28. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License. Protocol Version When this option is used, ifFor more information andOn Windows,If the contents of the inputA characterFor example, ifFor example, ifFor example, ifFor security reasons, such operationsFor duplicate-key errors, thisIf you do useIf binary logWhen encryption is required, be sure toFor more information on theIn other words, rows that have theWith LOCAL, theArguments to these clausesLINES TERMINATED BY '\n' STARTING BY '' For example,Some programs, such asTo read such files, useOtherwise, LOADFor example, many programsAn example of suchAlso, if you specify anObserve that the second field in theTo avoid ambiguity,For example, ifSome two-character sequences that areThis causes bothIf you need to beFor example, the followingWith user variables,The following statement setsIf there areThis occurs because the server has noQuery OK, 2 rows affected (0.00 sec). Records: 2 Deleted: 0 Skipped: 0 Warnings: 0If you do not do. Procedures Make sure that you have already installed the appropriate ProCalV5 database components onto your server and client. Place the ProCalV5 Data Load Utility disk into your CD-ROM drive or if you downloaded this executable from Prime Technologies, navigate to the folder. Run setup.exe and perform the installation. If the setup program does not automatically launch, go to the CD ROM and run the setup.exe program. This installation ONLY installs the PCDataLoad.exe program. The installation program will, by default, install the program into the C:\Program Files\Prime Technologies\ProCalV5 directory. If this is not where you installed the ProCalV5 client program you must change the installation directory to your ProCalV5 directory. The program will also allow for the addition of multiple Test Point Groups for existing assets. While the Source File structure is predefined, the DL Utility allows some flexibility for defining User Defined Variables from site to site. This feature will be detailed later in the manual. Each run of the program inserts asset records into a specified ProCalV5 Company. This program can be run multiple times for a specific Company. For example, you may want to run this program once for each Department at each Company. The input records defined in the Source File will be used to set the field values for the added records. However, the DL Utility will allow you to choose a default value for many fields. You can choose those values during the initiation phase of each run of the utility. If a default value is chosen, then for all Source File records that have a blank value for that field, the default value will be used. For example, if you would like to set the Calibration Frequency to “Annually” for all your Instruments except for the pressure transmitters, set the “Calibration Frequency” field in the Source File records for the temperature transmitters to a specific value (e.g. Quarterly) and leave all the other Source File records’ “Calibration Frequency” field blank. Then, during the run of the DL Utility, set the “Calibration Frequency” default value to “Annually”. Each Source File record with a blank value in its “Calibration Frequency” field (all the records but the temperature transmitters) will be set to “Annually” in ProCalV5. A log file with the results of each run will be created and saved to the designated location. The log file will show the start time, the end time, which assets and Test Point Groups were created and any errors encountered during the run. The name of the Log file is displayed on the initiation screen of the DL Utility. The program may be run in a “Test Run” mode. Running the program in this mode will process the source file and create a log file of what would happen if the program were run in production mode. Running in “Test Run” mode allows you to check the source file for errors. The user will be able to indicate (by use of a check box) that missing list values will be added to the company if they are in the spreadsheet and do not exist in the company. The following lists may have values added to them during a load: Classifications Departments Documents Instrument Types Manufacturers System Types Equipment Types Locations Buildings Signal Types UDV List values Internationalization The program will be internationalized to display the screen labels, error messages and log file entries in the current user’s preferred locale. Note that the program will use the system’s default locale until the user logs into the system. The program will also be internationalized to allow the user running the program to indicate what locale should be used when processing the source file. An excel file will be created for each currently available languages (French, Italian, German, Spanish and Portuguese). Several Excel Worksheets exist in the Excel file for each asset type and for Test Point Groups. The columns specified in the table below MUST be defined in the source file. The physical order of the fields in the source file is not significant. Instruments Worksheet Co lumn Name Note Instrument ID Required Field Description Fields will be left blank if spreadsheet is blank. System ID The System Record must exist or must be getting created in the current run of the utility (System is defined in the “System” worksheet). Failed Cal Alert Type Must match predefined dropdown Found Out of Cal Alert Type Must match predefined dropdown Exp Man Hours Numeric field Late Cal Compl Rpt Type Must match predefined dropdown As Found Failure Compl Rpt Type Must match predefined dropdown Failed Cal Compl Rpt Type Must match predefined dropdown Item Approval Policy Must match predefined dropdown Calibration Approval Policy Must match predefined dropdown Note Text field Loops Worksheet Column Name Note Loop ID Required Field Description Fields will be left blank if spreadsheet is blank. Failed Cal Alert Type Must match predefined dropdown Found Out of Cal Alert Type Must match predefined dropdown Exp Man Hours Numeric field Late Cal Compl Rpt Type Must match predefined dropdown As Found Failure Compl Rpt Type Must match predefined dropdown Failed Cal Compl Rpt Type Must match predefined dropdown Item Approval Policy Must match predefined dropdown Calibration Approval Policy Must match predefined dropdown Instrument IDs List of Instruments that belong to this Loop, separated by a semi-colon. Instrument must exist or must be getting created in the current run of the utility. Note Text field Test Instruments Worksheet Column Name Note Test Instrument ID Required Field Description Fields will be left blank if spreadsheet is blank. Failed Cal Alert Type Must match predefined dropdown Found Out of Cal Alert Type Must match predefined dropdown Exp Man Hours Numeric field Late Cal Compl Rpt Type Must match predefined dropdown As Found Failure Compl Rpt Type Must match predefined dropdown Failed Cal Compl Rpt Type Must match predefined dropdown Item Approval Policy Must match predefined dropdown Calibration Approval Policy Must match predefined dropdown Note Text field Equipment Worksheet Column Name Note Equipment ID Required Field Description Fields will be left blank if spreadsheet is blank. Integer field. Input Type Input Signal Type. Spaces are allowed but will be ignored. Output Values Semicolon separated values. This cell should only have values if Correlation to Output for the row is “Manual” Correlation to Output Choose from the drop down list. Output Type Output Signal Type. If the Test Type column contains a value, only the Test Type will be created. MPF As Found Result “Pass”, “Fail” or “Unknown” MPF As Left Result “Pass”, “Fail”, “Unknown” or “Not Entered” MPF Test Performed “Yes” or “No” User Defined Variables In addition to the fields listed above, the DL Utility allows you to populate User Defined Variable fields. The Source File spreadsheet column must be defined as it appears in ProCalV5. No mapping table is needed to define what fields in the Source File goes to what User Defined Field in ProCalV5. As long as the fields are named the same, the mapping is done automatically. If text is entered, the Log will show an error. If text or a decimal is entered, the Log will show an error. If the date is not in a correct format, the log will show an error. If the List value does not already exist in the database, the Utility will create a new List value in ProCalV5 and populate the corresponding field. If this column exists on the spreadsheet and is not populated, no action will be taken in ProCalV5. User Defined Variables can be populated on any asset type. If a Department is either specified in an asset’s worksheet or defaults from the Main screen in the Utility and the Department has an assigned Approval Policy, those Policies will be populated on the Master Record. A Test Point Group’s Control Limits will be set to the default setting from the Company screen, Additional Info tab. If the “Next Cal Date” column is blank on an asset row then the utility will attempt to calculate the asset’s “Next Calibration Date” based on the “Calibration Frequency” and “Last Cal Date” column values. All asset records will be added as “Approved’. No Change Control record will be created. If the asset has an Item Approval Policy, all signatures will be signed by the user running the utility. When the user clicks on the “Start Conversion” button, the utility will ensure that all the columns in the Worksheet are there. If they are not, an error will be displayed in a pop up message stating which Worksheets are invalid and which fields are missing. The utility checks against the “Required Fields” for each asset type. If a field is required and it is not populated by the column value or a default value then an error is generated. Additionally, if a User Defined Variable (UDV) is a Required Field then the worksheet must also include a column for that UDV. For example, if all the Worksheets are invalid, the following message will be displayed in the pop up message (fld1, fld2, etc are just placeholders. The real column names will be listed): The following Worksheets are invalid: Instruments (Missing fld1, fld2, UDV fld1) Loops (Missing fld3) Test Instruments (Missing fld4) Equipment (Missing fld1) Systems (Missing fld3) Test Groups (Missing fld3) List Processing Some values in the spreadsheet are associated with ProCalV5 lists (e.g. Manufacturers). All list values must exist in the associated list prior to loading the spreadsheet. The following are the lists that are processed by the utility. Each row in the “Test Groups” worksheet will produce one Test Point Group for the item designated in the “Item Type” and “Item ID” columns. Set the “Num Cal Pts” column to designate the number of test points you want for the group. Set the specific test point inputs in the “Input Values” column. Use a semi-colon (“;”) to separate the values. The number of values in this column must match the value in the “Num Cal Pts” column. If you would like the utility to set the inputs automatically, leave the “Input Values” column blank and the test points inputs will be evenly distributed across the Input Range. If the “Correlation to Output column” is “Manual” you should fill in the “Output Values”. These are your expected output values for each test point. The number of values in this column must match the number of values in the “Input Values” column. If your correlation is anything but “Manual” then you must leave this column blank. The utility will calculate the correct expected output values for each test point. Resolutions for the input and output fields will first look to the spreadsheet that is being processed, and if that is blank, then will use the Company’s default values. Calculated the same as ProCalV5 does it. Setting Default Values on the Data Load Utility Main Screen These values on the Main screen will only populate records with corresponding fields on the spreadsheet that are left blank. If the spreadsheet contains a value, the value in the Main screen will not overwrite it. Location - If the Location column’s row is blank on the spreadsheet, the default value will be used. If the Location is left blank on the spreadsheet and the Building field is populated, an Error will be generated. See “General Processing Rules”, above, for information on Approval Policies tied to a specific Department. Calibration Frequency - If the Calibration Frequency column’s row is blank on the spreadsheet, the default value will be used. This value only applies if the Stated Accuracy is “Percent of Range” or “Percent of Reading Range”. This value only applies if the Stated Accuracy is “Percent of Reading” or “Percent of Reading Range”. Once the information is entered on the spreadsheet you must save your work before running the Utility. To start the Utility either navigate to where you installed the Utility, or if you created a shortcut, double click on the icon. The main screen will be invoked. To Logon you will use the same User ID and Password already setup in the ProCalV5 database. Only System Administrators can log onto the DL Utility. A file open dialog will appear. Find your Source File and click on the “Open” button. Now you have to choose the Company into which you want to add data. Simply choose the company from the drop down list. After you choose a company you can choose default values for many fields. These values are used to populate your fields for any records in your Source File where those fields are blank. These fields will contain only selections that already exist in the target Company. See “Setting Default Values on the Data Load Utility Main Screen”, above, for details. You should also decide if you want to run in “Test Mode” or “Production Mode”. For “Test Mode”, leave the “Run as Test” check box checked. This will process the Source File without actually updating your database. A full log will be generated, recording any errors found in the Source File. Running in “Test Mode” allows you to check the Source File before committing the file to your system. When you finish your selections, simply click the “Start Conversion” button. Your conversion will commence, with its progress displayed in the memo field (center of screen), the slide bar (bottom left of screen) and the counts (bottom right side of the screen). At the completion of the conversion you will get a pop up screen telling you that you are finished and the location of the log file. Click Ok and then close the DL Utility by clicking on the Close button. The log file has this basic format: Header Specifies Conversion Start Date and Time, Type of Run (Test Run or Production), the Target Company Name, any default values that may have been selected, the Source File path and file name, the Log File path and file name and the DL Utility version number. Asset and Error Information This section lists the assets and Test Point Groups that are added and any errors that are encountered during the conversion. See Appendix A for possible error messages. Footer and Summary This section specifies the Conversion Completion Date and Time, Total Input Records Processed, Total Asset and Test Point Records Created and the Total Errors encountered and the length of time it took to complete the load. Conversion Completed on 30-Apr-2015 10:19:22 Summary. 52 Total Records Processed 4 System Records Would Have Been Created 2 Equipment Records Would Have Been Created 2 Instrument Records Would Have Been Created 2 Loop Records Would Have Been Created 1 Test Instrument Records Would Have Been Created 4 Test Point Group Records Would Have Been Created 148 Errors encountered during the process Total Conversion Time: 00:00:20 Help us improve this article with your feedback. If you hate cookies, or are just on a diet, you can disable them altogether too. Just note that the Freshdesk service is pretty big on some cookies (we love the choco-chip ones), and some portions of Freshdesk may not work properly if you disable cookies. All rights are reserved. It is a breach of copyright if this manual is copied or reproduced, in whole or in part, using any means whatsoever, without prior written approval from Trace Solutions Limited, and civil and criminal sanctions may result. This manual describes SDL functionality up to and including release 3.30.20 of the software. Trace Solutions Limited reserves the right to make changes to this manual or the accompanying software products without notice to any person or company. Trace Solutions Limited shall not be liable for any indirect, special, consequential or incidental damages resulting from the use of this manual or the accompanying software whether caused through the negligence or otherwise of Trace Solutions Limited. Support The team of experienced support personnel is available from 09:00 to 17:30 to answer queries and provide assistance as required. If this is different from that of the software being run it is likely the software has been upgraded. Where to find help If clarification is needed contact the Trace Help Desk on: 020 7825 1234 The team of experienced support personnel is available from 09:00 to 17:30 to answer queries and provide assistance as required. They will also help provide a work-around for any known problem waiting to be fixed. It is split into various main sections. Each entity will have a sub section to itself detailing all relevant information. There are also separate sections on the different ways of using SDL (Bulk Entry; Text File Upload; Data Maintenance; Client Extract). Contents The Contents list is comprehensive and should help users find what they are looking for even though no Index exists. Overviews At the beginning of each section there is an overview, explaining the general background and any important information. Icon What is it for. Notes Mappings Short cut for File\ Open\ Mappings This will open the Mappings window. Text File Short cut for File\ Open\ Text File (Tab delimited). This will open the Text File browse window, so that the user can select which text file they wish to import into SDL. Data Maintenance Short cut for File\ Open\ Data Maintenance This will open the Data Maintenance routine window; users may select an entity and view and amend all data within that entity. Bulk Entry Short cut for File\ Open\ Bulk Entry This will open the Bulk routine select window; users may select an entity and then enter new data for that entity. Database Connection Short cut for File\ Open\ Connection Cash List This will open the Connection Cash select window; users may select a different database to connect to. Save Press save to attempt an upload of new or modified data into the database. Print The print functionality isn’t available in every window. Insert Row Within a data window, press the insert row to add a new row. Delete Row Within a data window, select rows you wish to delete and then press the Delete Row button. Find Column Allows the user to find a particular column in the data window. Minimise, Controls windows. The functionality has not altered. The functionality in this area is limited. Numeric A synonym for decimal. Example 2: (Numeric 7,4) means that you may input seven characters in total, with three before the decimal place and four after. SDL This is an abbreviation for the Structured Data Load module. In general this will be all property related entities, i.e. Client, Creditor, Manager, Lease etc. SDL may be used in different ways. This gives the user the advantage of loading larger files on a regular basis but without the inconvenience of setting up mappings as for Text File Upload. This is best for saving time when users want to upload large amounts of information on a regular basis. Text files can be used to: o create new data o update existing data (only available on limited entities). Client Extract: Mappings are not required. Some data within the database may be viewed and amended. This section will detail. This record can be modified by the user, but cannot be deleted. The System Configuration record is found under: File. Open ? System Configuration. Contents The fields have the following functions. Lines will only be grouped together if they are below each other in the file and have the same document type, invoice ref, creditor ref, invoice date and office code. Each entity is uploaded individually, subject to certain entities which can. More entity records can be written as bespoke. Debtor (c) only basic fields generated when Lease imported. - data can also be amended via text file. ? Debtor Bank ? Head Lease ? Head Lease Charge ? Head Lease Charge History. Head Lease Custom Data. Head Lease Diary (b) also generated when Head Lease imported. Head Lease Expiry (a) only generated when Head Lease imported. Head Lease Note ? Head Lease Option (b) also generated when Head Lease imported. Head Lease Review (b) also generated when Head Lease imported. Landlord ? Lease - data can also be amended via text file. ? Lease Charge (b) also generated when Lease imported. Lease Custom Data ? Lease Diary (b) also generated when Lease imported. Lease Expiry (a) only generated when Head Lease imported. Lease Note ? Lease Option (b) also generated when Lease imported. Lease Review (b) also generated when Lease imported. Manager ? Period Date ? Property - data can also be amended via text file. ? Property Accounting (b) also generated when Property imported, if a Client Account record exists. ? Property Budget ? Property Capital Valuation. Property Custom Data. Property Rating Information. Property To Fund Ownership. Property to Manager. Property Type ? Property Valuation. Supplier Record ? Tenancy Note ? Tenant ? Tenancy Record ? Unit ? Unit Apportionment. Unit Custom Data ? Unit Diary ? Unit Document ? Unit Measurement (Total). Unit Rating Information. Ad hoc charges ? Cashbook Receipt ? Cashbook Payment ? Creditor Invoice ? Debtor Opening Balances. Debtor Receipts ? Document Logging ? Opening Cashbook Receipt. Opening Cashbook Payment. Accruals and Prepayments. Journal Transfers and Adjustments. Opening Balances Journal. Opening Property Expense Journal Posting. Property Expense Journal Posting FM Entities. FM - Asset Picture. The aim is to simply warn a user that they are using a powerful tool that can manipulate and alter the data in their database. The disclaimer message may be switched off by checking the Do not show this window again check box. To enter the module, the user must read and accept the disclaimer message before being able to use the module. The standard log in window will then be displayed. Back ups ? One file text file per Entity. Preliminaries may be seen as the most important stages, as they contain the foundations for the whole import process. Back ups Ensure that a back up exists. This may be used for both the trial and live uploads as appropriate. Trace specialist help should be sought for the most efficient method. Trace may provide you with template spreadsheets per entity. Volume of Data Consider the volume of data within the source file. Splitting the data into various files may make the upload process faster. Please check the detailed notes below to ensure that your requirements are met prior to upload. Only entities that automatically generate associated records will be listed below. You may assume that entities that are not listed will not generate any record other than their own. See below for details on uploading: Bespoke. Property ? Unit ? Lease ? Head Lease ? Creditor Further records may be generated as part of bespoke work. Property Accounting Record For details of what information will be populated into which fields contact a Trace consultant. Unit Maintenance record. The From and To Dates will default to Blank. Lease Charge maintenance record New record(s) generated. A maximum of 2 charge records may be generated if the required fields have been entered on the Lease. Note that the Charge Type code and the Due Date code must be supplied for charge records to be generated. The Debtor Account No will be populated from the generated Debtor record; it is also possible to populate the Transaction Type Code and Charged To Date fields. ? Lease maintenance record New record generated. This will be generated from the Term end date. Note that these records will only be generated if the Next Review Date and Pattern fields are entered on the Lease Entity. Note that these records will only be generated if all associated Option fields have been entered. Any system generated debtor Account No.Populated from the 'Lease Ref' on the uploaded Lease entity. Populated from 'Tenant Ref' on the uploaded Lease reference. Populated from 'Tenant Name' on the Tenant Maintenance record. Populated from 'Search Name' on the Tenant Maintenance record. Populated from 'Building' on the Tenant Maintenance record.