Copiar parametrizacion

[Former Member]

Hola, si alguien me puede ayudar le agredeceria mucho

necesito crear una nueva base de datos a partir de una que ya esta funcionando, pero solo necesito las tablas basicas

sin movimientos, porque es otra compañia y voy a empezar a registrar movimientos, hay alguna utilidad o alguna lista de las

tablas basicas para pasarlas por SQL....gracias

[Former Member · Accepted solution]

Hola

Existe una herramienta cuya finalidad es esa. Se trata del AddOn Copy Express, el cual te permite copiar las parametrizaciones desde una base de datos a otra. Se puede migrar todas las tablas a excepción de las transacciones.

También es posible migrar consultas, busquedas formateadas y layouts. En otras palabras, esta herraminta se ajusta exactamente a tu necesidad.

Espero te sea de ayuda

Saludos Cordiales,

Edited by: Paul Ponce on Jun 28, 2010 4:58 PM

[Former Member · Accepted solution]

El problema es que Copy express se demora mucho y ademas se bloquea cuando tiene mucha informacion.

Gracias por tu colaboracion

[Former Member · Accepted solution]

Hola...

Yo creo que para copiar las parametrizaciones y aquellas tablas que no contienen mucha información se puede utilizar Copy Express, incluso es posible ir copiando de modo parcial esta información. Ahora, respecto de la migración de tablas que contienen mayor cantidad de información, deberías evaluar la posibilidad de migrarlas vía DTW. En DTW me parece que existe una opción para migración en función a consultas SQL. Revisa la documentación del DTW y te sugeriría realizar una prueba de este tipo.

Espero te sea de ayuda

Saludos Cordiales,

[former_member188440 · Accepted solution]

Retroalimentando lo que dice Paul, aqui cito parte de la ayuda de DTW

To prepare the data migration, you must extract the data to be migrated 
from your legacy system. After the data extraction, you must map 
and convert the extracted data to the format that the Data Transfer Workbench is able to import.

This version of the Data Transfer Workbench supports flat files, 
which are text-based files that contain character separated
 values (*.txt and *.csv files) and data records selected through
 ODBC. To simplify the preparation of the data files, you can
 use predefined templates. For advanced users, you can
 also maintain the tool interface and generate new templates
 that are required for your use.

Preparing Flat Files
The flat files can be prepared in two types (*.txt or *.csv files). 
Also, the flat files can be prepared by using three
 types of delimiters: Comma (,), Semicolon (;) and Tab.
 The data files can be imported or updated in the following way:

Prepare object and sub-object data in different files; for example,
 importing the Business Partners object with the Contact Person 
and Address. You separately put the data into Business Partner
 template, Contact Person template, and Address template in the different files.

Template Structure
A template is related to one object. If an object has sub-objects, 
every sub-object also has a template. A template has two lines. 
The first line is made up of properties which came from DI API. 
The second line is property explanation.

RecordKey: This key identifies the header record from other
 records. To improve the performance, RecordKey values are sorted in order during the import.

LineNum: It should be an integer which begins with 0. It is only
 used when updating existing business object and you must keep
 it empty when importing the data files.

ReadOnly Key: Keep it empty when importing the data files and 
fill the same value as in SAP Business One when updating
 existing business object. Documentu2019s key-DocEntry is an example.

ReadWrite Key: This is required both when importing the data 
files and updating existing business object. Business Partneru2019s key-CardCode is an example.

Format of the Data Files
This version of the Data Transfer Workbench supports the import 
of text-based files that contain character separated values (*.csv or *.txt files).
 SAP recommends using the predefined templates to prepare the data files.

Please refer the following information to the corresponding parts of DI APIu2019s online help.

·         Mandatory u2013 indicated whether the column must contain value in the data files

·         Comments u2013 explanation for each object name and files name.

·         Default Value u2013 A field value is automatically set up if left blank.

 Please find it in databaseu2019s table definition.

 

Extracting Data through ODBC
For data records selected through ODBC, you can extract data records from the database 
you specify by SQL commands.

To prepare data through ODBC, perform the following steps:

1.     Create a Data Source Name (DSN) by choosing Control Panel->Administrative Tools->Data Sources (ODBC).

2.     The data records selected through ODBC can be imported or updated
 in the following way: Prepare object and sub-object data respectively. 
For example, when importing the Business Partneru2019s object with the
 Contact Person and Address, you separately select the data for Business 
Partner and the data for Contact Person and Address through ODBC.

 

How to Extract Data from DifferentSource
On Step 2: Choose data files in the Data Import Wizard, specify the 
source file(s) that contain(s) the data to be imported or updated.

1.     Use the drop-down arrow to select the type of data file(s). Available
 options are as follows: Comma, Semicolon, Tab and ODBC, specify
 the source data separately to the object and sub-object.

2.     For the options Comma, Semicolon, Tab, select Browser to 
choose a file (*.CSV or *.txt).

3.     For the option ODBC, 

1)     Select Browser. The Extract through ODBC dialog box will appear.

2)     Select DSN from the drop-down arrow and enter the UserID and Password.

3)     For Select, type the SQL command that you use to extract data through ODBC.

4)     Select Test. The selection results will be shown on the
 upper part of the Extract through ODBC screen.

5)     Select OK to specify the selection results to the object.



The source data for the header is mandatory 
for all the objects. The source data for the item is optional.

 

Espero te sirva