The 1C configuration “Trade Management, edition 11” has several built-in exchange plans, including the configuration “Enterprise Accounting, edition 3.0” (Fig. 1).

It is a set of rules according to which objects from one configuration will be loaded into another. In our instructions, we will set up an exchange between 1C Accounting 3.0 and 1C Trade Management 11 based on the 1C 8.3 platform.

The presence of the plan we need in the list of standard exchanges greatly facilitates the integration process. However, there are a few things you need to do presets, and in both configurations.

First, let's look at the sequence of actions in 1C Enterprise Accounting 3.0. Find in the “Administration - Settings” section the item “Setting up data synchronization” (Fig. 2).

Here you need to enable the “Data synchronization” checkbox and be sure to specify the prefix of our database (Fig. 3). If you wish, you can - no data will be loaded or changed before this date.

Now go to the “Data Synchronization” tab and configure the exchange itself (Fig. 4). There may be several exchanges. For each, its own line is created (button with a plus sign “Set up data synchronization”). We already have two entries in the 1C Accounting demo database. Let's check the settings of the latter (the button with a pencil “Configure rules ...").

We only fill out the “Rules for receiving data” tab (Fig. 5), since we will not send anything. On the “Rules for sending data” tab, check the “Do not send” checkboxes.

It remains to check the connection parameters (Fig. 6). We select “direct connection”, indicate the address of the database on the disk from which we will receive data, and the user/password of the same database. The user must have full rights or at least rights to perform synchronization. Sometimes a virtual user is created specifically for exchanges.

Detailed information about the settings in this section can be obtained from Help (F1).

Similar settings are made in the 1C Trade Management 11 database.

Setting up an exchange on the Trade Management side 11

In different releases, the section we need may have a different name. In our example, this is the item “Setting up integration - Other programs” (Fig. 7).

The rest is similar. The same “Data synchronization” checkbox, the same item and similar settings. (Fig.8).

Only the prefix is ​​different. It is important!

Get 267 video lessons on 1C for free:

Go to the “Data Synchronization” tab and create a new exchange. You can select the configuration with which we want to exchange using the “Set up data synchronization” button; the exchange itself is created using the “Configure” button (Fig. 9).

From this moment, differences from the previous setting in BUKH.3.0 begin. We need to fill out the “Rules for sending data” tab (Fig. 10). And the main thing that needs to be done is to determine the composition of the data being sent.

There are several ways to select the data that we are going to transmit (Fig. 11). All of them are collected in the “Register” section. You can select either one object or a list. Or all at once.

Let's return to the previous tab and complete one more important point, already familiar to us - we will indicate the connection parameters (Fig. 12). The parameters are configured in the same way as for accounting. Only this time we are using a virtual user named "Exchange".

Launching and checking the exchange between 1C Accounting 3.0 and 1C Trade Management 11

The exchange is performed using the “Synchronize” button, which is located on the first settings page (Fig. 13). This button can be found on other pages. Moreover, there is not much difference in which of the two configurations this button is pressed. The exchange is two-way.

Press the button and move on to the next step.

If the exchange is performed for the first time, you will have to perform manual synchronization, that is, compare identical objects of two configurations, if any (Fig. 14). If this is not done, duplicates may appear.

At the next step, it will be possible to select the organizations through which the data will be transferred, and some other selections (Fig. 15).

A description of all selections appears in a special window, and full list objects that will be sent can be obtained in the report on the composition of the sent data (Fig. 16).

The exchange can take a long time; the time depends on the number of objects being transferred. After the process is completed, we get the following picture - Fig. 17. By clicking the “Setup” button, you can set up a schedule according to which the exchange will be performed automatically.

Data exchange between 1C 8 application solutions is something without which it is not possible to build a full-fledged information space enterprises.

• 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 - . By 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 within means 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 routine task, where to 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:

There is an updated DB 1C Trade Management (hereinafter referred to as UT) edition 10.2 on the 8.1 platform.
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 it from the ITS disk external processing MD81Exp.epf (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.

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 automated system, consisting of a large number of bases. 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 others typical 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 is suitable - BP and UT, if the 1C 8.3 exchange setup is performed for a complex exchange between big amount bases, as well as identical configurations, you will need to enter each base 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 in one local network, we will indicate the parameters for connecting to the information security directory on this network, and also fill in the authentication information about the user (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 after, in the synchronization script, you can configure the schedule automatic execution exchange.

Let's look at a simple real life example. Let's say we have a company that is engaged in wholesale and retail trade, and in this company, like in any other, accounting is done. The enterprise has two standard databases, these are UT (trade management) and BP (accounting of the enterprise), respectively, in each of the databases its own records are kept, in UT there is management to reflect all transactions related to trade, in BP there is accounting. In order not to do double work, i.e. do not create the same documents in two databases (after all, movements should be in management and accounting) we will just set up synchronization between these databases.

We will set up data exchange one-way, from UT ---> BP. It is also possible to set up a two-way exchange, but in practice this is not often required, so we will not consider it in our example.

Preparatory steps for setting up exchange in BP

Let's start setting up synchronization, first go to the 1C "Enterprise Accounting 3.0" database (receiver), we need to check whether synchronization is enabled for this database, in order to do this we need to first go to the database. As soon as the database opens, go to the tab "Administration" ---> "Data synchronization settings"

It opens before us new inset, it must be filled out in the same way as in the screenshot below, with the exception of the infobase prefix. The prefix must consist of two letters, you can set any, but according to the 1C standard it is better to set the prefix by the name of the configuration, that is, for “Enterprise Accounting” the prefix will be “BP”. If you are setting up complex exchanges and there are several accounting databases, then the prefixes should clearly differ from each other; here you can use the first two letters of the organization’s name as an abbreviation.

We continue setting up data synchronization in UT

After we've done everything necessary actions in the receiver database (BP 3.0), to continue setting up data exchange we need to open the source database (UT 11.1). Go to the "Administration" tab, select "Data synchronization settings" in the menu on the left. If synchronization is not enabled, then enable it using the checkbox, and do not forget to specify the source base prefix. Once we have completed all steps 1-4 as shown in the image below, you need to click on the “Data Synchronization” hyperlink (step 5).

In the new window that appears, you need to click on the green plus sign (Set up data synchronization), in the drop-down menu select the item “Enterprise Accounting 3.0”.

Setting up important points in data exchange between UT and BP

Now we see a window with settings for data synchronization in 1C, select “Specify settings manually” and click “Next”.

We continue to configure data exchange in 1C, on the next tab we need to select the option to connect to information base receiver (direct connection to the program), connection parameters (on this computer or on a local network), the directory where the receiver base is located, as well as the necessary authentication data (user name and password in the base).

On the next page we must fill in the rules for sending and receiving data from the BP 3.0 (receiver) configuration. Click "change data upload rules".

The “Rules for sending data” window has opened in front of us, in it we set the following parameters:

• Which reference data will be sent (in our example, we are only interested in documents and the reference data used in them, so we selected the appropriate item; if you select the first item “Send all”, then all reference books will be reloaded along with the documents, often if the information is not used in the documents then it is useless for the receiver, because it does not affect the accounting in any way)
• From what date should all information be sent (we will not consider manual synchronization in this article)
• To which or which organizations to send data (in our example, we chose one organization, IP "Entrepreneur")
• Rules for forming contracts
• Generalized warehouse
• Should I roll up documents by warehouse?

After we have made the settings, click “Save and close”.

Since in our example we set up and use one-way exchange, from UT to BP, then the settings for the rules for obtaining data from “Enterprise Accounting 3.0” are not of interest to us, so we click “Next”.

In a new window, we are asked to configure rules for the receiver base (RB). In point 1, we name our database, give it a prefix. The PREFIX must be the same as we set it in the BP database itself at the beginning of this article; if the prefixes are different, data synchronization in the 1C program will not work. After that, click point 2, and then point 3.

In point 3, we need to allow documents to be processed when they are loaded into the database. Click "Save and close".

Now the window should look something like the one shown below, click “Next”.

This window contains reference Information about the created synchronization in 1C. Just click the "Next" button. If the program generated an error when setting up data synchronization, then you need to contact us so that our 1C specialist can help you right now!

Next step the program will offer to synchronize immediately after creating the data exchange settings. Let's agree to this and click "Done".

A window will appear in front of you in which you will see information about how the synchronization is proceeding. If the receiver base is not empty, i.e. records have already been kept in it, then the user in the 1C program will be asked to make a comparison of objects manually. Comparison of objects in 1C when synchronizing data is a comparison of identical objects of the receiver with identical objects in the source.

Let's look at an example, let's say in UT there is a counterparty with the name "PharmGroup LLC" and TIN 1234567, and in BP there is also a counterparty with TIN 1234567, but the name "PharmGroup", if we do not compare these two objects when comparing data at the synchronization stage, then after synchronization in the receiver (Enterprise Accounting 3.0), we will have two counterparties with TIN 1234567 and two names “PharmGroup LLC” and “PharmGroup”, respectively. In order to avoid such situations, a mechanism for comparing objects was invented.

In our example, the receiver database is empty, and therefore the object comparison window did not open. But after performing some operations, the system will definitely prompt the user to add some additional data and display the following window. We don’t need to transfer any additional data, we’ve already configured everything we need earlier, so at this step we select “Do not add documents to sending.” Click "Next".

The final stage of data exchange between 1C

At the final stage, the program will display the following window, in which the user will be informed that the synchronization was successful, click “Finish”. At this point, synchronization between databases in a one-way exchange from “Trade Management 11.1” (UT) to “Enterprise Accounting 3.0” (BP) is completed.