And there is a standard 1C Accounting database on platform 8.3.
Task:
Establish data exchange between databases.Solution:
Installed 1C Data Conversion, edition 2.1.Uploaded.
I launch the “Start Assistant” (Fig. 1).
1. Next.
2. Select "Create new data exchange rules (from scratch)". Further.
3. In the third step, the program asks you to specify the source and destination configurations.
I create a source configuration (1C UT):
- since I have 1C UT on platform 8.1, I take external processing MD81Exp.epf from the ITS disk (you can download it).
- I open 1C UT. File --> Open --> MD81Exp.epf .
I specify the file into which information about the metadata structure will be uploaded. It must be in XML format.
I click the "Upload" button.
I do the same with the receiver base. With 1C Accounting 8.3. Only for this I use external processing MD83Exp.epf (you can download it).
I go back to 1C Data Conversion.
We stopped at step 3. I click the “New” button and specify the generated metadata structure file. This structure will be loaded into the configuration directory.
4. In the fourth step, select the “Automatically create all possible data exchange rules” option.
Now a new window has opened before us. Object conversion rules have been created. You need to create rules for downloading data. To do this, go to the second tab “Data upload rules” and click the “Create upload rules” button.
How to use exchange rules
To transfer data from one database to another using exchange rules, you need to create exchange rules and use processing.How to create exchange rules
Using exchange rules, data can be transferred between databases with any configuration. This article explains the creation of exchange rules for databases with the same configurations (Enterprise Accounting 2.0). This transfer can be done using standard processing. But this processing transfers data of reference types only by reference, and transfers data of primitive types and predefined data by value. For a more complex transfer, when, for example, you need to search for a directory element by name, you need to create exchange rules.Information bases created by 1C have a similar data structure. Therefore, it will be easier to write rules for these databases. If the information base manufacturers are different, then it is more difficult to write transfer rules, and in some cases it is not advisable.
Rules are created in the infobase with the "Data Conversion" configuration.
1) Infobase configurations
To create transfer rules between databases, you will need descriptions of the structure of these databases. To unload the information base structure, special processing is used (MD82Exp.epf, MD83Exp.epf), which are supplied along with “Data Conversion”.
After downloading the database structure, it must be added to the list of configurations.
2) Data exchange rules
List of conversions
Adding a new conversion
Editing exchange rules
A conversion rule for an object can be created automatically by clicking on the "Synchronize objects..." button. Below is an example of creating a rule manually for the "Currencies" directory. After clicking the "Add" button on the "Object Conversion Rules" tab, the assistant for adding a new rule will open.
1) First you need to select the source and destination infobase objects.
2) Here you need to set the transfer settings.
3) In event handlers in the built-in language, you can write your own algorithms for processing data during transfer.
Automated control systems in most cases consist of separate databases and often have a geographically distributed structure. At the same time, correctly implemented data exchange is a necessary condition for the effective operation of such systems.
The initial setup of the exchange may require a number of actions, not only in terms of programming, but also consulting, even if we are dealing with homogeneous sources, as is the case with products on the 1C:Enterprise platform. Why setting up 1C exchange (or, as it is also called, data synchronization in 1C 8.3) can become the most time-consuming and expensive task of an integration project, we will look at in this article.
Data exchange in the 1C environment allows you to:
- Eliminate double entry of documents;
- Automate related business processes;
- Optimize interaction between distributed departments;
- Promptly update data for the work of specialists from different departments;
- “Differentiate” between different types of accounting.*
*In cases where the data of one type of accounting differ significantly from another, it is necessary to ensure the confidentiality of information and “delimit” information flows. For example, data exchange between 1C UT and 1C Accounting does not require uploading management data into the regulatory accounting database, i.e. synchronization in 1C will be incomplete here.
If we imagine the standard process for implementing primary data exchange, when at least one of its objects is a 1C product, then we can distinguish the following stages:
- Coordination of the composition of the exchange;
- Definition of transport (exchange protocols);
- Setting rules;
- Scheduling.
Identification of the composition of 1C exchange
Objects of exchange can be divided into “source” and “receiver”. At the same time, they can perform two roles at the same time, which will be called a two-way exchange. The source and destination are determined logically depending on the need or the functionality of the system.*
*For example, when integrating “WA: Financier” - a solution for maintaining financial accounting and managing treasury processes, developed on the basis of “1C:Enterprise”, WiseAdvice experts recommend it as a master system. This is due to the availability of control tools to comply with the rules of the application policy, and, accordingly, to ensure the effectiveness of the solution.
Next, based on the received and recorded requirements from users, a list of data for exchange is created, its volume, requirements for the frequency of exchange are determined, and the process of working with errors and handling exceptional situations (collisions) is prescribed.
At the same stage, depending on the fleet of existing systems and the structure of the enterprise, the exchange format is determined:
Distributed information base
- RIB implies exchange between identical 1C database configurations, with a clear “master-slave” control structure for each exchange pair. As an element of a technology platform, RIB, in addition to data, can transmit configuration changes and administrative information of the database (but only from master to slave).
Universal data exchange in 1C
- A mechanism that allows you to configure the exchange of 1C databases, both with configurations on the 1C:Enterprise platform and with third-party systems. The exchange is carried out by transferring data into a universal xml format in accordance with the “Exchange Plans”.
EnterpriseData
- The latest development of 1C, designed to implement data exchange in xml format between products created on the 1C:Enterprise platform with any automation systems. The use of EnterpriseData simplifies the modifications associated with the exchange. Previously, when a new configuration was included in a system, it was necessary to implement a mechanism for importing and exporting data, both for it and for existing systems. Now systems that support EnterpriseData do not need any modifications, having only one entry-exit point.
Definition of transport (exchange protocols)
For the system on the 1C:Enterprise 8 platform, a wide range of possibilities is provided for organizing exchange with any information resources using generally accepted universal standards (xml, text files, Excel, ADO connection, etc.). Therefore, when determining the transport for exchange data, you should rely on the database capabilities of the third-party system.
Synchronization of directories
The basic principle of effective synchronization of directories is the presence of a single entry point. But if we are talking about working with directories that have historically been filled out according to different rules, it is necessary to clearly define synchronization fields to bring the exchange to a “common denominator.”*
*At this stage, it may be necessary to carry out work to normalize the reference data on the side of the data source. Depending on the state of the directories and their volume, the process of comparing elements, recognizing, identifying errors and duplicates, as well as filling in missing fields and assigning synchronization fields, may require the work of a whole group of experts, both on the part of the integrator (the owner of the master data normalization technique) and from the customer's side.
Setting rules
The ability to display data from source systems in receivers depends on correctly defined exchange rules. The rules, presented in xml format, regulate the correspondence of key details of source-receiver objects. The 1C:Data Conversion solution is designed to automate the creation of rules for implementing both one-time and permanent exchanges.
Guarantees no data loss during exchange Exchange Plan. This is an integral part of any configuration on the 1C:Enterprise platform, which fully describes the 1C exchange procedure: data composition (documents with “identifying” details) and nodes (receiver-transmitter information bases), as well as activation of RIB for selected exchange directions.
Any change in the data entered into the Exchange Plan is recorded and receives the “changed” sign. Until the changed data matches each other in the receiver-transmitter nodes, the sign will not be reset, and the system will send control messages to both nodes. After uploading the data and confirming their full compliance in both systems, the sign is reset.
Exchange schedule in 1C
To automate regular exchange, the frequency of data uploading is set. The frequency of exchange depends on the need and technical capabilities. Also, configurations on the 1C:Enterprise platform allow you to configure data exchange when an event occurs.
Having considered the standard process of implementing an exchange, let’s pay attention to factors that will require improvements at different stages:
- Non-standard, highly modified database configurations;
- Different versions of the 1C:Enterprise platform;
- Configuration versions that have not been updated for a long time;
- Objects of exchange that have previously undergone modifications;
- The need for non-standard exchange rules;
- A very different set and composition of details in existing reference books.
Since even standard actions to implement primary data exchange require expert knowledge, they are recommended to be carried out with the participation of 1C specialists. Only after completing all the steps described above should you proceed to setting up the exchange in the configuration. Let's look at the integration of databases using the example of 1C:UPP and 1C:Retail (exchange with 1C:UT is set up using the same scheme). Also included in standard synchronization is the SCP - SCP exchange, which is typical for large-scale automation systems at the largest industrial enterprises.
In the “Service” submenu, select “Data exchange with products on the platform...” (selecting direct exchange with “Retail” often results in errors at the COM object level). Please note the service message “This feature is not available.”
To resolve this issue, you need to select "Configure Communications"
...and check the box. Next, ignore the error message.
In the data synchronization settings, select “Create an exchange with “Retail”...
Before configuring connection settings through a local or network directory, you should make sure that there is space on the disk for the directory. Although, as a rule, it does not take up more than 30-50 MB, in exceptional cases it may require up to 600 MB. You can create the required directory directly from the configurator.
When connecting via a network directory, we ignore the offer to configure the connection via an FTP address and by email by clicking “Next”.
In the settings, we manually enter prefixes - symbols of the databases (usually BP, UPP, RO), set the rules and the start date for data upload. The prefix will be indicated in the name of the documents to indicate the database in which they were created. If the upload rules are not edited, the data will be uploaded by default according to all available parameters.
We create an exchange settings file for “Retail” so as not to repeat our actions. If you need to immediately send data immediately after setting up synchronization, check the box.
To automate the exchange process, you need to set up a schedule.
Menu "Retail".
Check the box and select “Synchronization”.
We perform the “reverse” setup by selecting Production Enterprise Management.
Load the settings file created in UPP.
We put a tick, the system picks up the address automatically.
We act in the same way as in UPP.
Verification data comparison (Manual data comparison is recommended to be done at the preparatory stage, since this work can become the most labor-intensive in the process of implementing the exchange). The comparison window opens by double clicking the mouse.
In case of an error in synchronization, “Details...” will be replaced with “Never...”.
“Details...” opens the log with updated information on the exchange.
Ready.
Data exchange between 1C 8 application solutions is something without which it is not possible to build a full-fledged enterprise information space.
- Why are data exchanges needed and how to use them?
- Types of exchanges between 1C.
- How to configure data exchange between 1C databases?
You will find out the answers to these questions below.
There are usually two reasons for introducing exchanges:
The organization has a branch network
In this case, you simply need to set up the exchange between different branches. For this purpose, there is a mechanism in the 1C 8.3 enterprise system. With which you can flexibly configure the exchange of information. For example, for branches you can disable the visibility of documents for other branches and at the same time the central office will see documents of all branches. Another example is setting up an exchange between the 1C Retail databases of an office and stores.
Separation by type of accounting
As a rule, this means that the organization maintains different records in different information databases. This separation allows you to filter information that is “unnecessary” for another type of accounting for various information bases. Example: so-called “Management accounting” will be entered into the “Trade Management” database, where all transactions are reflected, and management sees the full picture of events, and only the documents necessary for accounting and tax accounting are uploaded to the regulated accounting database “Enterprise Accounting”.
What are the exchange mechanisms between 1C databases?
Data exchanges can be classified in two ways: the mechanisms used and the transport used for the exchange.
1C data exchange mechanisms
Typically, two mechanisms are used for exchange:
- Distributed information base (RIB)— a mechanism that allows you to set up data exchange between branches. The mechanism implies that absolutely identical database configurations are exchanged. The mechanism can transfer database configuration changes. The mechanism is implemented at the technology platform level.
- A universal mechanism for exchanging between configurations— the mechanism is developed by 1C for application solutions. It is universal and based on . Data exchange is carried out using xml rules, which are created in a special configuration - . Using this mechanism, you can implement both one-time exchange and constant exchange between 1C configurations. The mechanism is implemented at the configuration level; you can integrate it into your configuration from the technological configuration.
Transport for data exchange
Transport can be a fairly wide range of technologies. Let's consider the main ones implemented in the universal exchange mechanism 1C 8.2:
Get 267 video lessons on 1C for free:
- Local or network directory- the simplest transport. One information security creates a file on disk, the second reads it and adds its own file.
- FTP resource— exchange is similar to exchange through a catalog. The difference is that the exchange is carried out via the FTP protocol.
- Postal messages or E-mail— the exchange takes place via email. The configurations send mail messages to each other and regularly check the mail address for new messages.
- Direct connection (COM)— the exchange is carried out through a direct connection of one database to another using funds.
- Internet (Web service)— the transport is a web service. One infobase connects to , the web service connects to the second infobase and transports the message. To carry out such transport you must have.
How to set up data exchange between 1C databases?
For the basics of setting up data exchange in 1C using the “1C Data Conversion” configuration, see the example in the video:
1C data exchange according to schedule in 1C 8.2
If you need to configure automatic uploading on a schedule, just configure .
For client-server version
In the “Data exchange settings” directory, on the “Automatic exchange” tab, you need to create a new scheduled task, where you specify the schedule:
For file option
In the “Data exchange settings” directory, on the “Automatic exchange” tab, you need to create a new routine task, where, on the “Exchange by events” tab, specify the events on which the exchange will be launched. For example, when a specific user starts:
Send this article to my email
The main reasons for the need to implement exchange between 1C databases are the presence of branches and the separation of accounting types, because Often companies operate in several information databases. Setting up 1C 8.3 exchange allows you to eliminate double work - entering the same documents and directories in two programs, as well as quickly deliver the necessary system objects for various branches and departments.
In the case when it is necessary to exchange between branches, the RIB (Distributed Information Base) is used. This is an exchange mechanism between identical configurations. It represents a tree with the most important root node on top, below a pair of interconnected nodes. Changes can be made in any node of this system, and they will be transmitted to other connected nodes. It also distributes not only data, but also configuration changes from the root node to the slave nodes.
If it is necessary to separate types of accounting, for example, maintaining operational ones in the trading database, and regulated ones in the accounting database, universal exchange mechanisms with flexible data synchronization settings are available.
One of the latest 1C developments is the EnterpriseData data exchange format. It is easy to use and is intended for exchange within the company both between 1C databases and third-party programs.
The implementation of data exchange in an enterprise can be represented in the form of sequential procedures.
First of all, it is necessary to determine between which databases there should be an exchange; will it be a two-way or one-way exchange; if one-way, then which database will transmit information and which will only receive; if this is a complex branch network, then it is necessary to register a database construction scheme.
Then we select the appropriate format: RIB, universal format; exchange according to exchange rules; exchange without exchange rules.
The next step is to select a vehicle to carry out the exchange. A large selection of technologies is available, let’s highlight the main ones: directory (local or network), FTP resource, COM connections, web service, email.
The fourth step will be to identify the data: documents, reference books and, if necessary, detail them down to their individual details to be transferred.
And in conclusion, a schedule of exchange frequency is prescribed
Each option for setting up 1C 8.3 exchange requires careful preparation. Its implementation is beyond the capabilities of every user; it is necessary to take into account many nuances and understand the principles of the exchange. Particular attention will need to be paid to configuration if the databases: contain modifications or many additional ones. details, differ in platform versions or use outdated versions of configurations, the enterprise is large and uses an automated system consisting of a large number of databases. Errors are unacceptable here, because... may lead to irreparable consequences. Independent implementation of exchange in 1C is recommended only if you need to set up a simple transfer of information between standard configurations.
If you doubt your abilities, it is better not to save, but to contact a competent specialist who will help solve the complex problem of setting up 1C 8.3 exchanges.
If you still decide to configure 1C exchanges without involving experts, it is recommended to first test on copies of the databases, and before starting work in the working databases, upload the configurations to be able to return to the original state in case of errors.
Below we give a detailed example of setting up 1C 8.3 exchange unilaterally between standard configurations Trade Management 11 (UT) and Enterprise Accounting 3.0 (BP). The example is relevant for many companies engaged in wholesale and retail trade. In the UT, management accounting is maintained, in the BP - regulated, the exchange is necessary to facilitate the work of users.
This algorithm is also suitable for other standard configurations on the 1C 8.3 platform
First of all, we will carry out preparatory work for the information receiver, i.e. for BP. We launch the program in Enterprise mode. You need to set the Data synchronization constant (section Administration → Data synchronization).
Pay attention to the Prefix field; here you need to specify a value that will allow you to subsequently distinguish (by the value of the directory code or document number) in which program the objects were originally created. In our example, the usual abbreviation BP and UT is suitable, if the 1C 8.3 exchange setup is performed for a complex exchange between a large number of databases, as well as identical configurations, you will need to enter each database with its own clear designation.
Since the power supply unit is only a receiver of information, we proceed to setting up the UT.
Here, just like in the BP, you need to enable synchronization and specify a prefix. This information is available in the Master data and administration section → Data synchronization settings.
Select the setup method: Specify settings manually. Further.
Let's set up a direct connection option, when both programs are located on the same local network, specify the parameters for connecting to the information security directory on this network, and also fill in the user authentication information (in the BP database). Further.
The system will check the correctness of the specified data and, if the result is positive, will display the 1C 8.3 exchange settings window.
Click the Change data upload rules link to access settings for the exchange. We will clarify the master data - upload only those used in documents, select organizations and the option of working with contracts - without reference, separation of documents by warehouse. The exchange begins on March 1 of the current year.
We write down the introduced rules and close them.
Since the example is about one-way transmission of information, in the next settings window to receive data from another program, you should set the values to Do not send. Record and close. Further.
Now you need to check the entered parameters and if they are correct, click Next, otherwise return to the previous step by clicking Back.
You will then be prompted to synchronize. Click Finish.
If it is necessary to correlate identical objects of two configurations, a window for comparing data will open. We perform the comparison and click Next.
When transferring objects, problematic situations may arise; you can view the results by clicking the Warnings during data synchronization link.
After synchronization is completed, a window will be displayed confirming the successful completion of this process.
Here, using the Configure command or later, in the synchronization script, you can configure a schedule for automatically performing the exchange.
Need to set up data exchange?
WE'VE BEEN PROGRAMMING 1C FOR 15 YEARS AND MAKING FREE VIDEO INSTRUCTIONS
We have a team of programmers who have extensive experience in setting up 1C exchange:
Between 1C configurations,
In setting up 1C exchange with other programs.
Why choose us?
Up to 2 hours response time for urgent tasks, even on weekends and holidays.
40+ full-time programmers with 1C experience from 5 to 20 years.
We make video instructions on completed tasks.
Live communication through any messengers convenient for the client.
99% of tasks are performed via remote access (TeamViewer or RDP), which significantly reduces task completion time.
Official partners of the 1C company since 2006.
Experience of successful automation from small firms to large corporations.
99% of clients are satisfied with the results, which is confirmed by letters of gratitude.
Loading...
