Wczytywanie danych
Wczytywanie danych służy do tworzenia lub aktualizacji wielu dokumentów.
[en] Loading data into RamBase is done via an import process, through the Input menu (INP) or the Import/export WIZARD (IOQWIZ) applications. The Input menu (INP) application lists all the import processes available in RamBase, and is the basis for the procedure. All import processes have their own file structure that needs to be used when loading data. Descriptions for the different load procedures are listed below.
Ten proces może prowadzić do:
Wiele dokumentów zostało zarejestrowanych.
Wiele dokumentów zostało zaktualizowanych.
[en] Load data in the Input menu (INP) application
[en] Loading of data is done by using files in .CSV format which are uploaded to RamBase, and processed asynchronously.
[en] To find a Input menu (INP) program, enter INP in the program field, to enter the Input menu (INP) application.
[en] Find the intended item by navigating the list and press ENTER to open the Import/export Wizard popup. If the relevant Input menu (INP) program is not activated for your company, contact RamBase Support for activation.
[en] Click the Documentation button to open the Input documentation application.
[en] Click the Send me example CSV file icon, envelope, to trigger an example file as template for the loading of data.
[en] Create the file using the template, and click the Start import icon.
[en] Click the Select file button and upload the .CSV file.
Uwaga
[en] Documentation will list which fields can be loaded, are mandatory and display examples of how the values should be defined. It is recommended loading a line or two as test to verify that the loading is working as expected.
[en] Verify load procedure
[en] After a load has been carried out, it is recommended to do some random samples to verify that the load has been carried out successfully. It is also possible to see the status of completed loading in RamBase via the In/out log view (IOL) application. Some import processes are more demanding than others. In example Loading products (ARTUPLOAD - INP/14542). To diagnose a faulty upload, in addition to the In/out log view (IOL) application, the Verify log (IVL) application must be checked.
[en] If a load fails to complete, there will be a notice in the In/out log view (IOL) or Verify log (IVL) application.
Uwaga
[en] If a load fails to complete, there will be a notice in the In/out log view (IOL) or Verify log (IVL) referring to a row number. If the data log refers to row number 27, it is actually row 28 or 29 in the .CSV file that has failed. The reason for this is that the load job starts counting at zero (0) or one (1), and the first row in the file is the header line.
[en] File structure
[en] The structure of the load file is always a table with column names and data for each row. There is no order requirement for the columns in the file, and all columns do not need to be present in the load file. A general advice is to only have columns which are to be updated or added, present.
[en] As a default rule, all columns should be in text format to avoid deformatting. Files that are to be imported into RamBase must have comma separated value - CSV format. The first row of the file is the header information. These values must be in upper case letters. The rest of the file consists of records that will be imported. Semicolon (;) must be used as data separator in both the header row and in the data rows. There are no requirements regarding the order of the columns.
[en] Each individual load has one or more columns that must be included. The remaining columns are optional, based on the data which is to be imported.
[en] Formatting
[en] The load file needs to be in a .CSV format. The file structure needs to be according to the specific load procedure, and in addition, all import files need to have correct value formatting (date, decimal, etc.).
[en] Make sure that all dates are written in the format yyyy.mm.dd (Example: 2015.04.29)
[en] Use full stop (.) as a decimal separator (Example: 3.14)
[en] Do not use a thousand separator (1000, not 1 000)
[en] Phone numbers can only contain numbers and +, no parentheses
[en] The fields within a load file must be separated with semicolons.
[en] E-mail addresses must be valid.
[en] EXTID (former identification) must be unique within one archive.
[en] If the text in a field contains a semicolon, the text must be a quoted string (Example: "Nut;101")
[en] There must not be any blank spaces before or after a value in a field.
[en] There must not be any line breaks in the file (can be detected by pressing CTRL+F and CTRL+J)
[en] When loading custom fields, "UDF_" must be added at the beginning of the values. (Example: For a custom field called TestField, UDF_TestField must be used as column header.)
[en] File example of Product sales price (ARTSALESPRICE) - INP/14540
[en] IT;SALESCUR;SALESQTY;SALESPRICE;SALESGM;EXTID;PART;SALESFROM;MFR;PLINO;PLINAME
[en] #100000;NOK;1;750;10;99;Servicetime 232333;2015.03.181512;AUDI;100000;
[en] Typical pitfalls when loading data from Excel files
[en] Excel has some behavior that you must be aware of when loading data. What can happen is that Excel automatically changes data values for some conditional values. This means that values can be changed when working in one Excel sheet, but it also means that any received Excel sheets may also contain these kinds of errors. Therefore, we strongly recommended that the following is reviewed before starting a data load:
[en] When a value has more than 12 digits, Excel will convert the number to scientific notation. For example, 123456789112 will be converted to 1.23457E+11. This can occur for EAN codes, serial numbers or other larger values that only contain numbers.
[en] For Scandinavian users, with a regional setting that sets a comma (,) as the decimal separator, numbers like 1.2 will be converted to 01.feb, which is a date. This is particularly dangerous in cases where a date field is specified back to a number, because then Excel will convert 01.feb to 44593, which is the number of days since 01.01.1900. This can occur for all decimal numbers. It is therefore recommended to open .CSV files in a program like Textpad which does not automatically convert the date fields.
[en] Excel removes leading zeros for number values. 000123 is converted to 123. This can typically happen with postal codes, EAN numbers and possibly part number.
[en] Use of external reference number EXTID
[en] EXTID is a field in RamBase which is used for previous system's reference number. This reference number can be used as a lookup between imports, which makes the import process significantly easier.
[en] When transferring data from a previous system, EXTID can be used as a primary key, or lookup between data, so that you do not need to retrieve the RamBase ID for the associated data. A good practice is to always include EXTID where possible. EXTID can also be used as the common denominator when loading data in different loads that are in some way connected. An example is when you are loading customers. Here it is beneficial to use EXTID as it will be used later when loading account transactions.
Zadania związane z tym procesem
Utwórz plik ładowania – jeśli należy utworzyć lub zaktualizować wiele dokumentów, trzeba utworzyć plik ładowania.
Przetwórz plik ładowania za pomocą odpowiedniego programu do wczytywania – plik ładowania został utworzony i musi zostać przetworzony przez program do wczytywania, aby dokumenty mogły zostać utworzone lub zaktualizowane.
Sprawdź dziennik pod kątem wczytywania wyników – po zakończeniu działania programu do wczytywania należy sprawdzić dziennik, aby sprawdzić, czy zostały zgłoszone jakieś błędy.
Jeśli jest to konieczne, zmodyfikuj wpisy, których nie udało się wczytać i powtórz proces – jeśli program do wczytywania zgłosił jakieś błędy, wiersze, w których zostały zgłoszone błędy muszą zostać zmodyfikowane i ponownie wczytane.