1s zup 3.1 synchronization with accounting. Publications. How to disable synchronization

25.10.2023

Synchronizing the CRM system “Client Base” with 1C will be useful if the work of one part of the users is carried out in 1C, and the other part in our CRM. This will allow you not to give users access to two programs at once and simply establish data exchange between programs. In order to use synchronization between 1C and CRM “Client Base”, you need to purchase the 1C module. You can do this by filling out an application on our website. The synchronization setup itself can be divided into two parts: Setting up 1C and the synchronization module, Setting up the CRM “Client Base”.

At the same time, the 1C program has the following requirements:

The version of the 1C:Enterprise 8.3 platform must be at least 8.3.4;
Work with the infobase must be performed in file or client-server mode;
Work with the infobase must be performed in managed application mode.

Setting up synchronization from the 1C side

After submitting your application, you will receive an archive containing an executable file for synchronization, a file for setting up communication in .epf format, as well as several text files with code.

Preliminary steps for universal processing to function

Make an archive copy of the 1C:Enterprise 8.2 information database

Create new metadata objects in the configuration structure.

Go to the information database in the “Configurator” mode. If the configuration tree is not yet open, open it using the menu “Configuration - Open configuration”:

1.1.1. Create a constant “KBUpload Catalog_”. In the configuration tree, right-click on the “Constants” branch and select “Add”:

In the “Properties” window that opens, set the properties of the constant. Name: CatalogUploadKB_. Synonym: Upload directory "KB". Type: String. Length: 300:

Close the Properties window.

1.1.2. Create a constant “DownloadDirectoryFromKB_”. In the configuration tree, right-click on the “Constants” branch and select “Add”. In the “Properties” window that opens, set the properties of the constant.

Name: CatalogDownloadsFromKB_. Synonym: Download directory from "KB". Type: String. Length: 300.

1.1.3. Create the constant “UploadForKBEnabled_”. In the configuration tree, right-click on the “Constants” branch and select “Add”. In the “Properties” window that opens, set the properties of the constant. Name: UploadForKBEnabled_. Synonym: Upload for KBV is enabled. Type: Boolean.

1.1.4. Create a constant “LoadFromKBEnabled_”. In the configuration tree, right-click on the “Constants” branch and select “Add”. In the “Properties” window that opens, set the properties of the constant. Name: LoadFromKBEnabled_. Synonym: Loading from KBV is enabled. Type: Boolean.

1.1.5. Create a constant “UserNameToLoadFromKB_”. In the configuration tree, right-click on the “Constants” branch and select “Add”. In the “Properties” window that opens, set the properties of the constant. Name: UserNameToDownloadFromKB_. Synonym: Username for downloading from KB. Type: String. Length: 300.

1.1.6. Create a constant “File Reading Periodicity KB_”. In the configuration tree, right-click on the “Constants” branch and select “Add”. In the “Properties” window that opens, set the properties of the constant. Name: Frequency of Reading KB Files_. Synonym: Frequency of reading text files "KB" (in seconds). Type: Number. Length: 5. Accuracy: 0. “Non-negative” flag is cocked.

1.1.7. Create a reference book “TablesKB_”. In the configuration tree, right-click on the “Directories” branch and select “Add”:

In the window that opens, on the “Basic” tab, set the following properties. Name: TablesKB_. Synonym: KB tables. On the “Data” tab, set the following properties. Code length: 5. Name length: 100. Code type: String. Main presentation: In the form of a name. On the “Numbering” tab, enable the “Auto-numbering” and “Uniqueness control” flags. Code series: Throughout the reference book.
Close the directory window.

1.1.8. Create a directory “Compliance with KB_Requisites”. In the configuration tree, right-click on the “Directories” branch and select “Add”. In the window that opens, on the “Basic” tab, set the following properties. Name: MatchingDetailsKB_. Synonym: Matching the details of "KB". On the “Data” tab, set the following properties. Code length: 20. Name length: 150. Code type: Number. Main presentation: In the form of a name. Right-click on “Details” and select “Add”:

In the properties window that opens, set the following properties. Name: TableKB. Synonym: KB table. Type: DirectoryLink.KBTables_. Index: Index. Do not change the remaining properties. Close the properties window. On the “Numbering” tab of the directory, set the following properties. Auto numbering: the checkbox is cleared. Uniqueness control: checked. Series of codes: Throughout the directory. Close the directory window.

1.2.9. Create the “Types of Conditions for KB_” enumeration. In the configuration tree, right-click on the “Enumerations” branch and select “Add”. In the window that opens, on the “Basic” tab, set the following properties. Name: Types of Conditions for KB_. Synonym: Types of conditions for "KB". On the “Data” tab, right-click on the “Values” branch and select “Add”:
You need to add 5 values:- Name: More. Synonym: More - Name: Less. Synonym: Less.- Name: GreaterOrEqual. Synonym: Greater than or equal to. - Name: Less than or Equal. Synonym: Less than or equal to- Name: Equal. Synonym: Equal. Close the enumeration window.

1.2.10. Create an information register “DataAboutObjectsKB_”. In the configuration tree, right-click on the “Information Registers” branch and select “Add”. In the information register window that opens, on the “Basic” tab, set the following properties. Name: DataAboutObjectsKB_. Synonym: Data about objects, information about the cat. uploaded to "KB". Frequency: Non-periodic. Recording mode: Independent. On the “Data” tab, right-click on the “Dimensions” branch and select “Add”:

You need to add 2 dimensions:

Name: Object. Synonym: Object. Type: String. Length: 100. Allowed length: Variable. The "Main selection" flag is set.
Name: UniqueIdentifier. Synonym: Unique identifier. Type: String. Length: 100. Allowed length: Variable. The "Main selection" flag is set.

Right-click on the “Resources” branch and select “Add”. You need to add 1 resource:

Name: Presence Sign. Synonym: Indicator of presence. Type: Boolean.

1.2.11. Create an information register “Checking Remote Objects for KB_”. In the configuration tree, right-click on the “Information Registers” branch and select “Add”. In the information register window that opens, on the “Basic” tab, set the following properties. Name: CheckDeletedObjectsForKB_. Synonym: Attribute for checking deleted objects (for "KB"). Frequency: Non-periodic. Recording mode: Independent.

On the “Data” tab, right-click on the “Dimensions” branch and select “Add”. You need to add 1 dimension:

Name: DateDay. Synonym: Date day. Type: Date. Date composition: Date. The "Main selection" flag is set.

Right-click on the “Resources” branch and select “Add”. You need to add 1 resource:

Name: Sign. Synonym: Sign. Type: Boolean.

Right-click on the “Details” branch and select “Add”. You need to add 1 property:

Name: User. Synonym: User. Type: String. Length: 100. Allowed length: variable.

As a result, the “Data” tab of this information register should look like this:

Close the information register window.

1.2.12. Create an enumeration “Types of Possible Tables_”. In the configuration tree, right-click on the “Enumerations” branch and select “Add”. In the window that opens, on the “Basic” tab, set the following properties. Name: Types of PossibleTables_. Synonym: Types of possible tables. On the “Data” tab, right-click on the “Values” branch and select “Add”. You need to add 4 values: - Directory. Synonym: Directory - Document. Synonym: Document - Register of Information, Synonym: Register of Information - Enumeration, Synonym: Enumeration

1.2.13. Create session parameter "TextDocKB_". In the configuration tree, open the "General" branch, then the "Session Parameters" branch. Right-click and select “Add”:
Set the properties of the session parameter: Name: TextDocKB_, Synonym: Text docKB, Type: String, the "Unlimited length" flag is set.

1.2.14. Create a session parameter “Record OTKB_Changes”. In the configuration tree, open the "General" branch, then the "Session Parameters" branch. Right-click and select “Add”. Set the properties of the session parameter: Name: Record OTKB Changes_, Synonym: Record OTKB Changes, Type: Boolean.

1.2.15. Create session parameter "ObjectKB_". In the configuration tree, open the "General" branch, then the "Session Parameters" branch. Right-click and select “Add”. Set the properties of the session parameter: Name: ObjectKB_, Synonym: Object to b, Type: AnyLink.

1.2.16. Create a session parameter “CharacterPerformedKB_”. In the configuration tree, open the "General" branch, then the "Session Parameters" branch. Right-click and select “Add”. Set the properties of the session parameter: Name: Attribute PostedKB_, Synonym: Attribute posted to b, Type: String, Length: 0, Allowed length: Variable, “Unlimited length” flag is set.

1.2.17. Adjust existing roles. In the configuration tree, open the “General” branch, then the “Roles” branch. For each role, perform the following actions: double-click on the role name, in the window that opens on the right in the configuration tree, select newly created objects (constants, directories and information registers) and set the rights: for constants - read; for reference books - reading, adding, changing; for information registers - reading, changing.

1.4 Add the required lines of code to the managed application module.

Right-click on the configuration name and select “Open Managed Application Module”:

At the beginning of the module, you need to insert text from the Text1.txt file, which is available in the archive with the synchronization module.

Find the “When the System Starts” procedure. To do this, go to the “Text” menu and select “Procedures and functions”:

In the list that opens, select the “When the System Starts” procedure and click the “Go” button:

As a result of this, the cursor is positioned at the beginning of the WhenSystemStart() procedure.

At the beginning of this procedure it is necessary insert text from the Text3.txt file.

At the very end of a regular application module you need insert text from the file Text5.txt.

1.5 Add the necessary lines of code to the general module “General Purpose KB_” In the configuration tree, open the “General” branch, and in it expand the “General Modules” branch:

Right-click on the “Common Modules” branch and select “Add”. Set the properties of the module: Name: General Purpose KB_, Synonym: General Purpose KB, The “Server” flag is set, the “Server Call” flag is set. Then double-click to open the module text and insert text from file Text6.txt

Close the module window.

1.6 Add the necessary lines of code to the general module “General Purpose KB_VS”. In the configuration tree, open the “General” branch, and in it expand the “General Modules” branch. Right-click on the “Common Modules” branch and select “Add”. Set the properties of the module: Name: General Purpose KB_VS, Synonym: General Purpose to b VS, The “Server” flag is set, the “External Connection” flag is set. Then double-click to open the module text and insert text from the file Text7.txt.

1.7 Create event subscriptions.

In the configuration tree, expand the “General” branch, right-click on the “Event Subscriptions” branch and select “Add”:

You need to add 5 event subscriptions:

Name: Changing Directory Details for KB_. Synonym: Changing the details of directories for "KB". Source: DirectoryObject. Event: BeforeRecording. Handler: General Purpose KB_VS.Changing Directory Details_BeforeRecording.
Name: Changing Document Details for KB_. Synonym: Changing document details for "KB". Source: DocumentObject. Event: BeforeRecording. Handler: General Purpose KB_VS.Changing Document Details for KB_BeforeRecording.
Name: Changing Directory Details for KBRecord_. Synonym: Changing directory details for KBRecord. Source: DirectoryObject. Event: OnWrite. Handler: General Purpose KB_VS.Changing Directory Details for KBRecord_WhenWriting.
Name: Changing Document Details for KBRecord_. Synonym: Changing document details for "KB" Record. Source: DocumentObject. Event: OnWrite. Handler: General Purpose KB_VS.Changing Document Details for KBRecord_WhenWriting.
Name: ChangeContentsofInformationRegistersForKB_. Synonym: Changing the contents of information registers for "KB". Source: Information RegisterSet of Records. Event: BeforeRecording. Handler: General Purpose KB_VS.Changing the Contents of Information Registers for KB_BeforeRecording.

Go to the “Configuration” menu and select “Save configuration”. Wait until saving is completed.

1.9 Update the database configuration.

Go to the “Configuration” menu and select “Update database configuration”. When prompted, click the “Accept” button. Wait for the database configuration update to complete.

1.10 Connect universal processing file

Copy the “Communication SettingsSKB83.epf” file to the infobase directory. It is necessary to open universal processing in the user mode of working from the infobase, provided that no other users are currently working with the infobase (when opened, universal processing tries to establish an exclusive mode of working with the database). You can open the processing through the “File - Open” menu, or you can connect it as an external processing.

Working with universal processing

Make an archive copy of the 1C:Enterprise 8.2 information database

Terminate all users from working with the infobase. Go to the information database in the “Configurator” mode. Through the menu “Administration - Upload infobase”, specify the path to the file. Wait for the message “Upload completed successfully.” As a result, the information base will be downloaded to a file with the .dt extension.

Setting up the structure for uploading/downloading information

The structure of uploaded/downloaded information is configured on the “Tables” and “Fields” tabs of universal processing:

On the “Tables” tab, a list of “KB” program tables is compiled that will be used in data exchange. Adding/editing/deleting tables is done using the command panel buttons located above the list. To save the list of tables, you must click the “Save” button located to the right of the list. Attention: to further configure the exchange structure, you must add at least one table to the list.

On the “Fields” tab, you configure the fields of the “1C” information base that will be synchronized:

Adding fields is done using the “Add” button to the right of the list. When you click the button, an additional window appears:

First, you must specify the type of metadata object: Directory, Document, Information Register or Enumeration, and then select a specific object in the “Metadata Object” list. After selecting an object, the “Details” list will be filled in automatically:

In the list of details, you need to check the boxes for those details that will be synchronized. Attention: the standard attribute “Deletion Mark” is marked automatically! The details of the tabular parts are highlighted in the list of names of the tabular part, framed by the symbols “/”:

After defining the list of synchronized fields, you must specify the corresponding “KB” table in the “KB Table” field and click the “Add” button:

The marked details will be added to the “Compliance of details” table. For each field, you must indicate the corresponding field number “KB”.

You can delete unnecessary fields using the “Delete” button to the right of the table.

The list of fields can be sorted by attribute name. To do this, use the “Sort” button to the right of the table.

In cases where it is planned to synchronize the details of the tabular parts of directories or documents, as well as the fields of information register records, for the correct functioning of the upload/download it is necessary to manually add the attribute "UniqueIdentifierKB_" to the structure of the corresponding metadata objects. To simplify things, universal processing will “tell you” where exactly this attribute needs to be added. For this after compiling a list of synchronized fields you need to click the “Report on adding details” button located to the right of the table.

A hint will appear in the message window at the bottom to which metadata objects you need to add the “UniqueIdentifierKB_” attribute.

To add details, you need to close the user mode of working with the infobase and start it in the “Configurator” mode. Then you need to make an archival copy of the information base. (see clause 2.1 of these Instructions)

If the configuration tree window is not open, open it using the menu “Configuration - Open configuration”:

Using the “File - Open” menu, open the universal processing file (Communication SettingsSKB.epf), which is located in the infobase directory:

In the universal processing window, you need to expand the “Table parts” - “Matching details” branch and select the “UniqueIdentifierKB_” attribute:

Next, in the configuration tree (in the left window), you need to find the required metadata object, expand it, expand the “Tabular parts” branch and expand the branch of the corresponding tabular part. Then use the mouse to move the attribute “UniqueIdentifierKB_” from the universal processing window to the required tabular part. It is necessary to “throw” the details not on the name of the tabular part, but on any of its details.

An example of transferring the “UniqueIdentifierKB_” attribute to the “Types of Activities” tabular section of the “Counterparties” directory:

And the result:

An example of transferring the attribute “UniqueIdentifierKB_” to the tabular part “Services” of the document “Sales of Goods and Services”:

And the result:

If you add the “UniqueIdentifierKB_” attribute to the information register, you need to expand the “Information registers” branch in the configuration tree, expand the branch of the corresponding register and expand the branch of its resources. Then use the mouse to move the “UniqIdentifierKB_” attribute from the universal processing window to the “Resources” branch of this information register. You can “throw” the attribute both on the word “Resources” and on any resource of the “Resources” branch. An example of adding the attribute “UniqueIdentifierKB_” to the information register “Advances to Employees”:

And the result:

After adding the “UniqueIdentifierKB_” attribute to the required metadata objects, you must save the configuration through the “Configuration - Save configuration” menu. Then - update the database configuration through the menu “Configuration - Update database configuration”. Then close the Configurator.

Setting up initial export

If you need to upload not all the contents of a particular metadata object, you can set a condition by filling in the columns “Attributes of the type “Date”, “Condition” and “Condition value”. In the “Date type attribute” column, you can select a “Date” type attribute for this metadata object from the list. In the “Condition” column, select the type of condition: Equal to, Greater than, Greater than or equal to, etc. In the “Condition value” column, specify a value of the “Date” type. As a result of this setting, only those objects that meet the specified conditions will be unloaded during the initial export.

To start the initial export, click the “Export” button to the right of the table.

Important: Initial export may take a long time! It is recommended to carry out this step by step, rather than uploading all the data into one transaction.

The path to the directory in which text files with information will be saved is indicated in the “Directory for uploaded text files” field. Attention: all users working with the infobase must have read and write access rights to this directory! To save the path to the directory, click the “Save” button on the right.

The “Upload” flag enables the process of uploading information. If this flag is cleared, all settings made on other universal processing tabs are saved, but information will not be uploaded to text files when users work with the infobase.

Information about deleted marked objects is uploaded to text files daily when the first user logs into the program. Forced downloading of information about such objects can be done using the “Download Now” button.In the “User name for loading” field, you must specify the exact name of the user in whose session information from text files will be downloaded. Attention: this user must have read and write access to this directory! Attention: this user must have full rights in the 1C information base.

In the “File reading frequency” field, you specify the interval in seconds at which the appearance of new files in the download directory will be scanned.

The "Download" flag enables the process of downloading information in the specified user's session. If this flag is cleared, all settings made on other universal processing tabs are saved, but information from text files will not be loaded when the specified user is working with the infobase.

To save the specified download parameters, click the “Save” button on the right.

Other

Synchronization of fields of the "Enumeration" type

To correctly synchronize values of the "Enumeration" type, you must:

On the "Fields" tab, add the appropriate listing and assign it the field number "KB". For enumerations, only one row is added: Value.
Perform an initial export of the corresponding "KB" table. In this case, for each enumeration value, a line of the following type will be unloaded: KB_field_number; Enumeration_value_name; Enumeration_value synonym.

In the future, synchronization will occur by the name of the enumeration value. That is, when unloading from 1C, the name of the enumeration value will be unloaded as a value. When generating files from "KB", you must also specify the name of the enumeration.

Handling invalid files

If the universal processing in the first line of the file from “KB” cannot recognize the 3 required blocks (KB field number, identifier and value), separated by a semicolon, then:

this file is considered incorrect,
subsequent lines of the file are not processed,
a message about an incorrect file is displayed in the message window,
The file extension is renamed to .bad.

If the first line in the file from “KB” is correct, but the rest are not, then the file is processed as usual, incorrect lines are simply skipped.

Important: If you are using the SaaS version of the CRM program "Client Base", then on the server on which 1C is located you need to run the file ClientSync.exe, which is located in the archive with the synchronization module. When starting this program, you must specify the program address, as well as the synchronization password.

Setting up synchronization from the KB side

Primary synchronization

Primary synchronization is necessary for the initial exchange of records between synchronized programs. It is carried out 1 time. Further synchronization occurs only based on events.

To set up primary synchronization, go to "Settings" - "Advanced"

Open the "Sync" section and add a new sync.

Specify a name to indicate synchronization, "Synchronization Mode"specify as "Integration with 1C","Synchronization type" - "Local", specify the folders for downloading and uploading data. An example of the setup is shown in the screenshot below. Also, if necessary, check the box to record a log.

Important: Folders for file synchronization must be created in the upload and download folders. The folder name should be "files".

After making changes, click on the “Save” button. You will be redirected to a menu to select program fields that will be filled in with data from 1C.

We select the table and the fields from it into which the data will go, and indicate in which direction the data synchronization will go - for loading data, for uploading data, or (as in the example in the screenshot) there will be two-way data synchronization. In our example, this will be synchronization information on records in the "My Company" table.

After entering all the fields, click on the “Save” button

Then you need to perform initial synchronization. To do this, go to the synchronization settings and click on the "Primary synchronization" button. The message "Completed" should appear.

In the future, synchronization between programs will occur when:

Changing records in 1C or in KB in the tables selected for synchronization;
Adding entriesin 1C or in KB in the tables selected for synchronization.

Sync files

Additionally, it is worth mentioning about the synchronization files themselves. After the initial synchronization, two files will be created.

The file in the upload folder contains information about:

ID of the field from which the data is taken
ID of the record from which the data was taken
And the data itself

and so on for each record and field in it. Example of an upload file in the screenshot below

The file in the download folder contains:

System value "ID"
Information about ID of a random field in the table into which the data will be loaded. This is necessary for the KB to determine which table the data needs to be loaded into.
Information about ID of the record to which you want to add information.
A unique value that will be added to one of the system fields of the program to compare records from 1C and KB.

Quite often there are situations when an organization uses the “1C: Salary and Personnel Management 8” configuration for settlements with employees, which is when it becomes necessary to upload data on payroll, personal income tax, insurance premiums and other payments into the accounting program.

In the 1C program: ZUP 8 ed. 2.5 data exchange was carried out by uploading a document in XML format; it was also possible to upload payment documents. Then the data had to be loaded into the accounting program database, having previously made certain settings. This can be done on the “Salaries and Personnel” tab by selecting “Download from ZUP ed. 2.5"

To download data, you had to select the file that was generated earlier when downloading from 1C: ZUP.

Data synchronization when using 1C programs: ZUP 8 ed. 3 and 1C: Accounting 8 ed. 3.0 has changed significantly. Now there is no need to upload and download documents into the 1C: Accounting program every time. It is now possible to make certain synchronization settings once and set the time period when it is necessary to perform the exchange. Also, the user can independently start synchronization when necessary, and not according to a schedule.

In BP 3.0, in the Accounting Settings (Section Administration), you must set the following setting.

In the same “Administration” section, select the “Data synchronization settings” item, where you need to check the “Data synchronization” checkbox. The link of the same name becomes immediately available.

Go to 1C: ZUP and check a similar box in the same item on the “Administration” tab. Next, you need to select the program with which synchronization will take place. We make a choice and enter the IB prefix so that we know in which database the document was entered.

Then select the directory through which synchronization will occur.

Here we make the necessary settings. If you need to upload only transactions for accrual of salaries, taxes, contributions, while in accounting, calculations for account 70 are NOT carried out by employee, then set the point “Summary by employee”, in this case the statements will not be uploaded.

The next window shows the data synchronization options. We check if all the data is entered correctly, click “Next”, if something needs to be changed, click “Back”. In our case, everything was entered correctly, go Next.

Now we check the settings on the 1C: Accounting side

These settings must be made once for the first synchronization. They can then be adjusted if necessary.

Now go back to 1C: Salary and HR Management 8 and click on the “Synchronize” button.

To check in the BP, open the document “Reflection of salaries in accounting.”

It will be without postings; for them to appear, you need to check the “Reflected in accounting” checkbox. After checking the box, you will notice that this document is blocked for making changes.

And now we need to block the document on the side of the 1C: Salary and Personnel Management program. For this purpose, in 1C: Accounting, click the “Synchronize” button.

Let’s check the result in 1C: ZUP: go to the “Salary” menu - “Reflection in accounting”. We see that this document is not available for editing and there is an automatic checkbox that cannot be removed.

The programs also automatically configure the synchronization schedule. Here the user can choose the parameters that are convenient for themselves.

Thus, we looked at how synchronization is configured and performed between the programs 1C: ZUP 8 edition 3 and 1C: Accounting 8.

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 level of COM objects). 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.

. What to do if an organization works simultaneously with several configurations that carry out regulated accounting for the organization? In 1C:Enterprise 8, starting with edition 3.0, it became possible to configure automatic synchronization between configurations that can be downloaded at a specified time and with a certain frequency: there is no longer any need to manually duplicate data.

Setting up user rights

When setting up synchronization between the “1C: Accounting 8” and “1C: Salaries and Personnel Management 8” databases, a special role must be given to the rights of the user who will perform the setup. Before you start setting up, you need to check whether your user has access to roles such as “ System administrator" or " " In this case, not surprisingly, a user with the “Full rights” role will not work.

If one of these roles is missing, the user has the flag “ Synchronizing data with other programs" will not be available. You can check and configure roles for your user in the “ Configurator" To do this, go to the menu “ Administration e" in the submenu " Users" On this tab, you must select the user who will configure the synchronization. In the window that opens, you need to go to the “ Other" and check the box next to the role " System administrator" or " Setting up file synchronization" This completes setting up user rights. Press the F5 key to accept the changes and enter the program under the user for whom we changed the roles.

Setting up synchronization

Now let's move on to setting up data synchronization. In the “1C: Salaries and Personnel Management 8” database in the “ Company" go to the tab " Administration" – section "Data synchronization". In the window that opens, set the flag “ Data synchronization" and follow the hyperlink on the right " Setting up data synchronization" In the program window that appears, in the menu, select the program with which you want to set up data exchange, and set the infobase prefix in the window of the same name. For example, in “1C: Salaries and Personnel Management 8” - “ZUP”, and in “1C: Accounting 8” - “BP”.

The Settings Assistant window will open in front of you. Before setting up synchronization, the program recommends that you perform a database backup. This will prevent unnecessary problems and keep your data intact. Next, the program will ask you exactly how you want to make the settings: manually or upload a file with settings made in another program. File upload option " Settings" is used in cases where, for example, in 1C: Accounting 8, we already have a synchronization schedule configured and for the 1C: Salaries and Personnel Management 8 program we want to use the same schedule. We will consider a setting that is performed manually by the user, so we select the item “ Specify settings manually" and click " Further».

In the next window we indicate how we will connect to the program. If the “1C: Accounting 8” program is located on the same computer as “1C: Salary and HR Management 8”, or is located on the same local network, we indicate that we have “ Direct connection to the program on this computer or local network" and indicate the path to the infobase in the field " Information base catalog».

If you do not know the path to the 1C: Accounting 8 database, you can find it as follows. We launch “1C:Enterprise 8” and select in the list the database with which the exchange will take place. At the bottom of the window the path to this database will be indicated, copy it without quotes and paste it into the “ Information base catalog».

If your infobase is located on the 1C:Enterprise 8 server, then you need to specify the server cluster and the name of the infobase. This data can also be found in the program launch window.

Next, you need to specify the user and password (if any) under which we will connect to the 1C: Accounting 8 database. After we have set all the necessary settings, click the “ Check connection" If all settings are made correctly, the program will display the message “ Connection check completed successfully" If the program generates an error and a message appears at the bottom of the screen: “When creating an exchange setting in the second infobase, errors occurred: (GeneralModule.DataExchangeServer.Module(5750)); Data synchronization is prohibited by the administrator. Call MessageText Exception;”, which means that in the settings of “1C: Accounting 8”, with which you are going to exchange data, the “ Data synchronization" To enable this checkbox, use the instructions above described for the 1C: Salaries and Personnel Management 8 program.

A complete list of errors can be found in " Logbook", which can be opened as follows: on the tab " Administration"follow the link" Service", and at the top of the screen we have a link to " Logbook" Go to the tab " Further", and before us a connection check is performed. This check may take up to several minutes, depending on the performance of your PC.

After checking, the data synchronization settings window will appear in the program. In this window, you can check the settings you entered, as well as change the exchange rules. For example, change the organization through which the exchange will take place or exchange data with details per employee. These settings can be changed by clicking on the hyperlink " Change data upload rules"at the bottom of the window.

After completing the setup, the program will prompt “ Synchronize data with “1C: Accounting 8”, ed. 3.0" If necessary, synchronize immediately checkbox “Synchronize data with “1C: Accounting 8”, ed. 3.0" leave it on and press the button " Synchronize" And if we need to configure the exchange schedule, we need to clear this flag and finish the configuration. After these steps, the program will open a window with the settings configured earlier, as well as the ability to configure the schedule.

If you need to set up a schedule, click on the “ Tune" In order for data to be downloaded automatically according to a configured schedule, you must set the flag " Automatically according to schedule" To configure the schedule itself for the infobase, you need to go to the “ Schedule» and configure when and with what frequency synchronization will be performed. Please note that the schedule for uploading and loading data is configured separately in the corresponding line of the tabular section on the setup form.

The first time you synchronize, you must perform data mapping. This is necessary to avoid data duplication. For example, in “1C: Accounting 8” and in “1C: Salaries and Personnel Management 8” there is a reference book “ Individuals", they often store the same data, and by default the system will synchronize data using an internal identifier; it will be unique for each directory element. With such synchronization, two identical individuals will appear in the directory. To avoid such situations, during the first synchronization it is necessary to compare the data and explicitly indicate in the program that Elena Leonidovna Mikhailova in one program and Elena Leonidovna Mikhailova in another are the same employee.

What data is transferred during synchronization

In “1C: Salary and HR Management 8” there are 2 main documents that are transferred during synchronization to “1C: Accounting 8”. This " » and all types of statements. In “1C: Salaries and HR Management 8” there are four of them: “ Statement to the bank», « Statement to the cash register», « Statement of transfers to the account" And " Payout sheet via distributor».

Document " Reflection of salaries in accounting” ends up in the document of the same name in “1C: Accounting 8” and already there, on the basis of the transferred documents, postings are generated.

Statement documents are transferred to “1C: Accounting 8” into one document “ Salary payment slip».

There are also a number of other documents and reference books that are also transferred during synchronization. Such documents include “ Accrual of estimated liabilities», « Salary deposit», « Payment of deposited salary», « Loan documents (agreement, issuance and repayment).” The following types of directories are also synchronized with accounting: “ Organizations», « Individuals», « Counterparties», « Subdivision And " Ways to reflect wages in accounting" Only those directory elements that will be used in synchronization documents will be transferred to 1C:Accounting 8.

If you find an error in the synchronized files in the 1C: Accounting 8 program, then it is recommended to correct the data in the 1C: Salary and Personnel Management 8 database, then the data in 1C: Accounting 8 will change automatically. If you follow this rule, then during synchronization the data from “1C: Salaries and Personnel Management 8” will be given priority and there will be no confusion in the data. You can also configure the data priority yourself, or the program will display a message in conflict situations.

When synchronizing, all settings of the “1C: Accounting 8” database are based on “ Accounting parameters» database "1C: Salaries and personnel management 8".

There is also another factor to consider when transferring data. During synchronization, only individuals are transferred to the 1C:Accounting 8 database. It is not necessary to create employees in “1C: Accounting 8” based on these individuals, since in all accounting documents where employees should be indicated, I will substitute data from the directory “ Individuals».

And finally, let’s point out one more pitfall associated with transfer. Imagine the situation: you have created a document in the “1C: Salaries and Personnel Management 8” database “ Statement..." and during synchronization, uploaded it to 1C: Accounting 8. For some reason, this document was deleted in the 1C:Accounting 8 database. In this case, during resynchronization, this document will not be added again, since during synchronization, the program sees in the correspondence register that this document has already been transferred. In such a situation, there is only one solution: physically delete this statement in “1C: Salary and Personnel Management 8” and create a new one, and then start synchronization. Since the new document is not in the compliance register, it can easily be transferred to the accounting information database.

When synchronizing data, it is necessary to take into account that the details of the organization through which the exchange will take place must be identical.

Data exchange between the 1C ZUP 8.3 program and Accounting 8.3 is necessary to reflect transactions for settlements with employees in accounting. If you keep personnel records and calculate salaries in the 1C ZUP 8.3 program, then read here how to download data from 1C ZUP 8.3 to 1C Accounting 8.3.

With a small number of employees, personnel records and payroll calculations can be carried out in the accounting program 1C 8.3 Accounting. But if your organization has a need for larger-scale and detailed accounting of salaries and personnel, then for this you will need the additional program 1C 8.3 Salaries and personnel management. Keeping records in two programs is not very convenient, but 1C solved this problem. Now the exchange of data between 1C 8.3 databases from ZUP 3.1 to Accounting 3.0 occurs automatically. But for this you need to set up synchronization between 1C 8.3 Accounting and ZUP. How to do this yourself, without involving technical specialists, read in this article. How to set up data exchange between 1C 8.3 databases from ZUP 3.1 to accounting 3.0 in a few steps, see below.

Step 1. Set up synchronization in 1C ZUP 3.1

Go to 1C ZUP 8.3 in the “Administration” section (1) and click on the “Data synchronization” link (2). A window for setting up the exchange will open.

In the window that opens, check the box next to “Data synchronization” (3) and click on the “Data synchronization settings” link (4). The settings window will open.

In the window that opens, click the “Set up data synchronization” button (5) and click on the link “Enterprise accounting, edition 3...” (6). A window will open to continue the setup.

In the new window, select “Specify settings manually” (7) and click the “Next” button (8). A window will open for you to fill in the exchange parameters.

In the window that opens, you need to specify some system exchange parameters. First you need to select a connection option in another program. In our example, this is “Direct connection to a program on this computer...” (9). This method is used if the 1C 8.3 Accounting program is located on the same computer or on the same local network with 1C 8.3 ZUP. Next, you need to specify the connection parameters in another program. In our example, there are two possible options:

On this computer or on a computer on the local network
On the 1C:Enterprise server

In our example, we select the second option (10) and fill in the “Server cluster” (11) and “Infobase name” (12) fields. Read where to get the data for these fields in the next step (Step 2).

Next, select “1C:Enterprise Authentication” (13) and enter the user (14) and password (15) that you use to log into 1C 8.3 Accounting. The data has been entered, now check the connection by clicking on the “Check…” button (16). If the test is successful, after a while the message “Connection test completed successfully” will appear. If something goes wrong, you will see an error message with a brief description of the problem.

In the next step we will tell you where to get the data on the server cluster and database name, and in the third step we will return to setting up synchronization.

Step 2. Where in 1C 8.3 to get data on the cluster and infobase name

When you log into 1C you see the launch menu. In this menu, click once on the database with which you are setting up synchronization, on 1C 8.3 Accounting (1). Next, click the “Change” button (2). The database editing window will open.

In this window you see data on the server cluster (3) and the infobase name (4).

Now let's go back to setting up synchronization.

Step 3. Continue setting up synchronization in 1C ZUP 3.1

In the first step we stopped at checking the connection. If everything went well, click the “Next” button (1). A window will open for further synchronization settings.

In the new window you see rules (2) for uploading data from 1C ZUP to 1C Accounting. To change these settings, click on the “Change” link (3). The exchange rules setting will open.

In this window, you can specify the start date of the exchange (4), select organizations for exchange (5). You can also choose the method for generating transactions in 1C 8.3 Accounting:

“with details by employee” (6);
“summary by employees” (7).

To save the settings, click the “Save and close” button (8). To move on to the next setting, click “Next” (9). A window for further settings will open.

In this window you see the rules (10) for uploading data from 1C Accounting to 1C ZUP. If necessary, you can change them by analogy with the previous setting by clicking on the “Change” link (11). To continue, click the “Next” button (12). A window will open with general information on synchronization settings.

If there are no errors, a window will open with a message about successful data synchronization (15). The program will prompt you to synchronize by default (16). To do this, click the “Next” button (17). A window will open with data matching information.

In the new window you can see directories for which there is unsynchronized data (18). Since you will be synchronizing information from two different information bases - 1C ZUP and 1C Accounting - from the date specified in the settings, it is necessary that certain directories in both databases have the same values. Such reference books include, for example, “Individuals”, “Organizations”, “Methods of reflecting salaries in accounting”. In this window you see directories (18) for which the data does not match. The program will automatically create the missing directory elements in both databases. To do this, click the “Next” button (19). The following window will open to synchronize data.

In the window that opens, the program informs you about the composition of the data that will be sent. To view a report that shows a list of this data, click on the link “Composition report...” (20). To complete the exchange, click “Next” (21). The exchange procedure will start, it will take some time.

Once the data exchange is complete, a window will open indicating that synchronization is complete (22). In this window you can configure the so-called “exchange schedule”, i.e. temporary rules according to which data exchange between two databases will automatically take place. To configure these rules, click the “Configure” button (23). The data synchronization script opens.

In the script window, click on the “Set up routine task schedule” icon (24). The exchange schedule setting will open.

In this setting, you can set at your discretion the time interval at which programs should exchange data. For example, in the “Repeat after” field (25) you can set the number of seconds after which the exchange will be repeated. To save the setting, click “OK” (26).

You have successfully configured synchronization between databases and started exchanging data. You can change exchange settings and control the synchronization process in the “Data Synchronization” window. You can access it through the “Administration” section (27) by clicking on the “Data synchronization” link (28).