Administration Data import export Import Definition data target - robinfeng/beashelp GitHub Wiki
定义数据目的
Navigation: Administration > Data import/export > Import: help-zahnrad Definition data target No contents entries on this page Contents There is a number of predefined data targets
Resource Master data - resource Operation Master data - Operation Item Master data - Item. The template item predefined in beas constitutes the template. help-hinweisNote: This import does not use the SAP Business One-SDK. Consequently, no tests are performed. If fields are not filled with permitted values (e.g. card code with a non-existing business partner), then this entry cannot be edited or moved in SAP Business One. Routing Routing stored in the item Bill of Materials Bill of material stored in the item Itemstore Warehouse definition saved in the item. If there is no warehouse, one is automatically created in SAP Business One. If an stock level is specified, it will be posted. Batch and serial numbers are not recorded. Note: No inventory adjustment takes place. If, for instance, the import is performed 2 times then the inventory is entered 2 times. Price Importing the price for a price list. This cannot be used to create new price lists. Expanded price lists or special price lists are not supported. Customer Business partner information Addresses Business partner delivery addresses Contact Business partner contact Attendance Attendance QC header QC Inspection plan head data QC position QC Inspection plan position data Manual Manual definition of a data target
Manual definition
A manual target definition is done by specifying a SELECT instruction in a table as well as specifying the table as well as specifying the primary.
help-hinweisNote: Manual imports are very dangerous since beas does not check the import process. The database should definitely be backed up first. The user should be very familiar with the structure of the source data if he wants to perform such an import.
However, the manual import is also very suitable to add additional fields, e.g. separate UDFs, retroactively per UPDATE to already existing imported areas.
The definition is done via DETAILS under "manual source database definition".
Table: The target table, e.g. beas_pers SELECT the select instruction, e.g. * from beas_pers Primary the primary key of the table, e.g. pers_id If it is made up of several keys, then they must be separated by commas.
help-hinweisNote: The select instruction is not verified. Erroneous entries can lead to a crash. The instruction should therefore first be validated through EXTRA/SYSTEM/SQL. A WHERE instruction does not have to be added since it is generated automatically.
help-beispiel Example: calculation price comparison If only the calculation price u_kalk_pr is to be adjusted in the item master OITM, then the manual import is a better choice.
Table oitm select select itemcode,u_kalk_pr primary itemcode
It is important to specify the itemcode since it represents the primary key. Now the source database must still be defined and the fields itemcode and u_kalk_pr must be allocated via the FIELDs.
返回 主页