An example of an object conversion rule. An example of an object conversion rule If the terms of the transaction simply change
Migrating data between different configurations is not a trivial task. As always, there are several solutions, but not all of them are optimal. Let’s try to understand the nuances of data transfer and choose a universal strategy for resolving such issues.
The problem of data migration (we are talking purely about 1C company products) from one solution to another did not arise yesterday. The 1C company understands perfectly well what difficulties developers face when creating migrations, so it tries in every possible way to help with tools.
During the development of the platform, the company introduced a number of universal tools, as well as technologies that simplify data transfer. They are built into all standard solutions and the problem of migrations between identical configurations has generally been resolved. The victory is once again confirmed by the close integration of standard solutions.
With migrations between non-standard solutions, the situation is somewhat more complicated. A wide selection of technologies allows developers to independently choose the optimal way to solve a problem from their point of view.
Let's look at some of them:
- exchange via text files;
- use of exchange plans;
- etc.
Each of them has its own pros and cons. To summarize, the main disadvantage will be its verbosity. Independent implementation of migration algorithms is fraught with significant time costs, as well as a long debugging process. I don’t even want to talk about further support for such decisions.
The complexity and high cost of support prompted the 1C company to create a universal solution. Technologies that make it possible to simplify the development and support of migrations as much as possible. As a result, the idea was implemented in the form of a separate configuration – “Data Conversion”.
Data conversion - standard solution, independent configuration. Any user with an “ITS:Prof” subscription can download this package completely free of charge from the user support site or the ITS disk. Installation is performed in a standard way - like all other standard solutions from 1C.
Now a little about the advantages of the solution. Let's start with the most important thing - versatility. The solution is not tailored to specific platform configurations/versions. It works equally well with both standard and custom configurations. Developers have a universal technology and a standardized approach to creating new migrations. The versatility of the solution allows you to prepare migrations even for platforms other than 1C:Enterprise.
The second big plus is visual aids. Simple migrations are created without programming. Yes, yes, without a single line of code! For this alone, it’s worth spending time learning the technology once, and then using invaluable skills repeatedly.
The third advantage I would note is the absence of restrictions on data distribution. The developer himself chooses the method of delivering data to the receiver configuration. There are two options available out of the box: uploading to an xml file and direct connection to the infobase (COM/OLE).
Studying architecture
We already know that data conversion can work wonders, but it is not yet entirely clear what the technical advantages are. The first thing you need to understand is that any data migration (conversion) is based on exchange rules. Exchange rules are a regular xml file describing the structure into which data from the information security will be uploaded. The service processing that uploads/downloads data analyzes the exchange rules and performs the upload based on them. During loading, the reverse process occurs.
The “CD” configuration is a kind of visual constructor with the help of which the developer creates exchange rules. It does not know how to download data. Additional external service processing included in the CD distribution package is responsible for this. There are several of them (XX in the file name is the platform version number):
- MDXXExp.epf- processing allows you to upload a description of the infobase structure to an xml file. The structure description is loaded into the CD for further analysis and creation of exchange rules.
- V8ExchanXX.epf- uploads/downloads data from the information base in accordance with the exchange rules. In most typical configurations, processing is present out of the box (see the “Service” menu item). Processing is universal and is not tied to any specific configurations/rules.
Okay, now, based on all of the above, let’s define the stages of developing a new conversion:
- Definition of the task. It is necessary to clearly understand what data needs to be transferred (from which configuration objects) and, most importantly, where to transfer it.
- Preparation of descriptions of configuration structures (Source/Sink) for subsequent loading into the CD. The problem is solved by service processing MDXXExp.epf.
- Loading prepared descriptions of structures into information security.
- Creating exchange rules using a visual CD tool.
- Performing upload/download according to the created data conversion rules using V8ExchanXX.epf processing.
- Debugging exchange rules (if necessary).
The simplest conversion
For the demonstration we will need two deployed configurations. I decided to go with the option: “Trade Management” 10th edition and a small home-written solution. The task will be to transfer data from the standard “UT” configuration. For brevity, let’s call the self-written solution “Sink”, and the trade management “Source”. Let's start solving the problem by transferring elements from the “Nomenclature” directory.
First of all, let's take a look at the data conversion scheme and re-read the list of actions that need to be done. Then we launch the “Source” configuration and open the MD82Exp.epf service processing in it.
The processing interface does not have an abundance of settings. The user only needs to indicate the types of metadata objects that will not be included in the structure description. In most cases, these settings do not need to be changed, because There is no particular point in unloading movements using accumulation registers (as an example).
It is more correct to form the movement while holding documents in the receiver. All movements will be made by the document itself after the transfer. The second argument in defense of the default settings is the reduction in file size with uploading.
Some documents (especially in standard configurations) generate movements across multiple registers. Unloading all this stuff will make the resulting XML file too large. This may complicate subsequent transportation and loading into the receiver base. The larger the data file, the more RAM will be required to process it. During my practice, I had the opportunity to encounter indecently large upload files. Such files completely refused to be parsed using standard tools.
So, we leave all the default settings and upload the configuration description to a file. We repeat a similar procedure for the second base.
Open the CD and select in the main menu “Directories” -> “Configurations”. The directory stores descriptions of the structures of all configurations that can be used to create conversions. We load the configuration description once, and then we can use it multiple times to create different conversions.
In the directory window, click the button “ Add” and in the window that appears, select the file describing the configuration. Check the “Load into a new configuration” checkbox and click on the “Load” button. We perform similar actions with the description of the structure of the second configuration.
Now you are ready to create exchange rules. In the main CD menu, select “Directories” -> “Conversions”. Add a new element. In the window for creating a new conversion, you need to specify: the source configuration (select UT) and the destination configuration (select “Receiver”). Next, open the “Advanced” tab and fill in the following fields:
- exchange rules file name - the created exchange rules will be saved under this name. You can change the file name at any time, but it is best to set it now. This will save time in the future. I named the rules for the demo example: “rules-ut-to-priemnik.xml”.
- name - the name of the conversion. The name can be absolutely anything, I limited myself to “Demo. UT to Receiver.”
That’s it, click “Ok”. Immediately a window appears in front of us asking us to create all the rules automatically. Agreeing to such a tempting offer will give the master a command to automatically analyze the description of the selected configurations and independently generate exchange rules.
Let’s dot the “i’s” right away. The wizard will not be able to generate anything serious. However, this possibility should not be discounted. If it is necessary to establish an exchange between identical configurations, then the services of a specialist will be very useful. For our example, manual mode is preferable.
Let’s take a closer look at the “Exchange Rules Settings” window. The interface may seem a little confusing - a large number of tabs crammed with controls. In fact, everything is not so difficult; you begin to get used to this madness after a few hours of working with the application.
At this stage, we are interested in two tabs: “Object conversion rules” and “Data upload rules”. At first, we must configure the matching rules, i.e. compare objects of two configurations. On the second, determine possible objects that will be available to the user for uploading.
In the second half of the “Object Conversion Rules” tab there is an additional panel with two tabs: “Property Conversion” and “ Converting values" The first will select the properties (details) of the selected object, and the second is necessary for working with predefined values (for example, predefined directory elements or enumeration elements).
Great, now let's create conversion rules for directories. You can perform this action in two ways: use the Object Synchronization Wizard (the “” button) or add correspondence for each object manually.
To save space, we will use the first option. In the wizard window, uncheck the group “ Documentation” (we are only interested in directories) and expand the group “ Directories" We carefully scroll through the list and look at the names of reference books that can be compared.
In my case, there are three such directories: Nomenclature, Organizations and Warehouses. There is also a directory called Clients, which serves the same purpose as “ Counterparties"from configuration" UT" True, the master could not compare them due to their different names.
We can fix this problem ourselves. We find in the window “ Object Matches» reference book « Clients", and in the "Source" column select the "Counterparties" directory. Then check the box in the “Type” column and click the “Ok” button.
The Object Synchronization Wizard will offer to automatically create rules for converting properties of all selected objects. The properties will be compared by name and for our demonstration this will be quite sufficient, we agree. The next question will be a proposal to create upload rules. Let's agree to it too.
The basis for the exchange rules is ready. We selected the objects for synchronization, and the rules for converting properties and uploading rules were created automatically. Let’s save the exchange rules to a file, then open the IB “Source” (in my case it’s UT) and launch service processing in it V8Exchan82.epf.
First of all, in the processing window, select the exchange rules we created. We answer the question of loading rules in the affirmative. Processing will analyze the exchange rules and build a tree of objects of the same name available for uploading. For this tree, we can set up all sorts of selections or exchange nodes, by changing which we need to select data. We want to download absolutely all the data, so there is no need to install filters.
After completing the process of uploading data to a file, go to IB “ Receiver" We also open processing in it V8Exchan82.epf, only this time we go to the “Data Loading” tab. Select the data file and click the “Download” button. That's it, the data has been successfully transferred.
Real world problems
The first demo could be misleading. Everything looks quite simple and logical. Actually this is not true. In real work, problems arise that are difficult or completely impossible to solve using visual means alone (without programming).
In order not to be disappointed with the technology, I prepared several real-life problems. You will definitely come across them at work. They don’t look so trivial and make you look at data conversion from a new angle. Carefully consider the presented examples, and feel free to use them as snippets when solving real problems.
Task No. 1. Fill in the missing details
Suppose we need to transfer the directory “ Counterparties" The receiver has a similar “Clients” directory for this purpose. It is completely suitable for data storage, but it has props “ Organization”, which allows you to separate counterparties by belonging to the organization. By default, all counterparties must belong to the current organization (this can be obtained from the constant of the same name).
There are several solutions to the problem. We will consider the option of filling out the details “ Organization“right in the database” Receiver”, i.e. at the time of data loading. The current organization is stored in a constant, therefore, there are no barriers to obtaining this value. Let’s open the object conversion rule (hereinafter referred to as PKO) “ Clients” (double click on the object) and in the rules setup wizard, go to the “Event Handlers” section. In the list of handlers we will find “ After downloading”.
Let's describe the code for obtaining the current organization and then assigning it to the details. At the time the “After loading” handler is triggered, the object will be fully formed, but not yet written to the database. Nobody forbids us to change it at our discretion:
If NOT Object.ThisGroup Then Object.Organization = Constants.CurrentOrganization.Get(); endIf;
Before filling out the details " Organization"It is necessary to check the value of the attribute " This group" For the reference book " Clients"The hierarchical feature is set, so checking for the group is necessary. Fill in any details in a similar way. Be sure to read the help for other handler options " AfterLoading" For example, among them there is the parameter “ Refusal" If you assign it the value “True”, then the object will not be written to the database. Thus, it becomes possible to limit the objects that can be written at the time of loading.
Task No. 2. Details for the information register
In the directory “ Counterparties"UT configurations, details available" Buyer" And " Provider" Both details are of type “ Boolean” and are used to determine the type of counterparty. In IB “ Receiver”, at the directory “ Clients“There are no similar details, but there is a register of information” Types of Clients" It performs a similar function and can store multiple attributes for one client. Our task is to transfer the values of the details into separate entries in the information register.
Unfortunately, visual means alone cannot cope here either. Let’s start small, create a new software for the information register “ Types of Clients" Do not cite anything as a source. Avoid automatically creating upload rules.
The next step is to create the upload rules. Go to the appropriate tab and click the “ Add" In the window for adding upload rules, fill in:
- Sampling method. Change to “Arbitrary algorithm”;
- Conversion rule. Select the information register “Types of Clients”;
- Code (name) of the rule. Write it down as “Unloading Client Types”;
Now you need to write code to select data for uploading. The parameter “ Data Sampling" We can place a collection with a prepared data set in it. Parameter " Data Sampling” can take on various values - query result, selection, collections of values, etc. We initialize it as a table of values with two columns: client and client type.
Below is the code for the event handler “ Before processing" It initializes the parameter “ Data Sampling” followed by filling in data from the directory “ Counterparties" Here you should pay attention to filling out the column “ Client Type" In “UT” our attributes are of the “Boolean” type, and the recipient is an enumeration.
At this stage, we cannot convert them to the required type (it is not in the UT), so for now we will leave them in the form of strings. You don’t have to do this, but I immediately want to show how to cast to a missing type in the source.
DataFetch = New ValueTable(); DataSelection.Columns.Add("Client"); DataSelection.Columns.Add("ClientType"); SelectingDataFromDirectory = Directories.Accounts.Select(); While SelectingDataFromDirectory.Next() Loop If SelectingDataFromDirectory.ThisGroup Then Continue; endIf; If Data Selection From Directory.Buyer Then NewRow = Data Selection.Add(); NewRow.Client = DataFetchFromDirectory.Link; NewRow.ClientType = "Customer"; endIf; If DataFetchFromDirectory.Supplier Then NewRow = DataFetch.Add(); NewRow.Client = DataFetchFromDirectory.Link; NewString.ClientType = "Supplier"; endIf; EndCycle;
Let’s save the data upload rule and return to the “ tab Object conversion rules" Let's add for the information register “ Types of Clients” property conversion rules: client and client type. We’ll leave the source empty, and in the “Before unloading” event handler we’ll write:
//For the “Client” property Value = Source.Client; //For the property “ClientType” If Source.Client = "Buyer" Then Expression = "Enumerations.ClientTypes.Buyer" ElseIf Source.Client = "Supplier" Then Expression = "Enumerations.ClientTypes.Supplier"; endIf;
In the listing, the details are filled in based on the selected data sample. We simply pass the client as a link, and write the client type in the parameter “ Expression" The data of this parameter will be interpreted in the receiver, and when executed, the prop will be filled with the correct value from the enumeration.
That's it, the exchange rules are ready. The considered example turned out to be quite universal. A similar approach is often used when migrating data from configurations created on the 7.7 platform. A striking example of this is the transfer of periodic details.
Task No. 3. Tricks with table parts
Often you come across tasks that require posting rows from one table section into several. For example, in the initial configuration, services and goods are registered in one tabular part, and in the receiver, the storage of these entities is divided. Again, the problem cannot be solved by visual means. Here it is convenient to take the solution of the second problem as a basis.
We make a rule for unloading data, specify an arbitrary algorithm, and in the “Before unloading” handler we write a request to obtain data from the tabular part.
To save space, I will not provide the code (you can always refer to the sources) of the request - there is nothing unusual in it. We sort through the resulting selection, and place the sorted results in the already familiar parameter “ Data Sampling" It is again convenient to use a table of values as a collection:
DataFetch = New ValueTable(); //There will be another table part here Data Selection.Columns.Add(“Products”); //Here there will also be a tabular part Data Selection.Columns.Add(“Services”); SelectionData.Columns.Add(“Link”);
Task No. 4. Transferring data to an operation
If an organization uses several accounting systems, then sooner or later there will be a need to migrate data with the subsequent generation of transactions.
In the configuration “ BP“there is a universal document” Operation” and it is ideal for forming more wires. There’s just one problem - the document is made cunningly, and the data cannot be transferred into it so easily.
You will find an example of such a conversion in the source code for the article. The amount of code turned out to be quite large, so there is no point in publishing it in conjunction with the article. Let me just say that uploading again uses an arbitrary algorithm in the rules for uploading data.
Task No. 5. Data synchronization across multiple details
We've already looked at several examples, but we still haven't talked about synchronizing objects during migration. Let's imagine that we need to transfer counterparties and some of them are probably in the receiver database. How to transfer data and prevent duplicates from appearing? In this regard, CD offers several ways to synchronize transferred objects.
The first one is by unique identifier. Many objects have a unique identifier that guarantees uniqueness within a table. For example, in the directory “ Counterparties” there cannot be two elements with the same identifiers. CD makes calculations for this and for all created PCOs, a search by identifier is immediately enabled by default. During the creation of the PCO, you should have paid attention to the image of a magnifying glass next to the name of the object.
Synchronizing using a unique identifier is a reliable method, but it is not always appropriate. When merging directories “ Counterparties” (from several different systems) it will not help much.
In such cases, it is more correct to synchronize objects according to several criteria. It is more correct to search for counterparties by INN, KPP, Name or split the search into several stages.
Data conversion does not limit the developer in defining the search criteria. Let's look at an abstract example. Suppose we need to synchronize directories “ Counterparties” from different information bases. Let’s prepare the PKO and in the object conversion rules settings, check the “ Continue searching search fields if the receiver object is not found by identifier" With this action, we immediately defined two search criteria - by a unique identifier and custom fields.
We have the right to choose the fields ourselves. By checking TIN, KPP, and Name, we will immediately indicate several search criteria. Comfortable? Quite, but again this is not enough. What if we want to change the search criteria? For example, first we search for the TIN+KPP combination, and if we don’t find anything, then we start trying our luck with the name.
Such an algorithm is quite capable of being implemented. In the event handler “ Search fields” we can specify up to 10 search criteria and for each of them define its own composition of search fields:
If SearchOptionNumber = 1 then SearchPropertyNameString = “TIN, KPP”; OtherwiseIfSearchOptionNumber = 2 ThenSearchPropertyNameString = “Name”; endIf;
There are always several solutions
Any task has several solutions, and transferring data between different configurations is no exception. Each developer has the right to choose his own solution path, but if you constantly have to develop complex data migrations, then I strongly recommend paying attention to the “”. You may have to invest resources (time) in training at first, but they will more than pay off on the first more or less serious project.
In my opinion, the 1C company unfairly ignores the topic of using data conversion. During the entire existence of the technology, only one book was published on it: “1C: Enterprise 8. Data conversion: exchange between application solutions.” The book is quite old (2008), but it is still advisable to familiarize yourself with it.
Knowledge of platforms is still necessary
"is a universal tool, but if you plan to use it to create data migrations from configurations developed for the 1C:Enterprise 7.7 platform, then you will have to spend time becoming familiar with the built-in language. The syntax and ideology of the language are very different, so you will have to spend time learning. Otherwise the principle remains the same.
The purpose of this exchange rule is to transfer balances on mutual settlements from BP 2 to UT11.
Step-by-step creation of an exchange rule using the "Data Conversion" configuration (metadata must be loaded):
1) Create a rule for uploading an object; for this, go to the “Rules for uploading data” tab, click add. In the window that appears, select the sample object; this will be a self-accounting register. We change the sampling method to an arbitrary algorithm.
2) Let’s move on to writing the code itself because There is no self-accounting register in the UT, so we must convert it. First, we need a query that, according to our parameters, will return balances for mutual settlements. In the "Before processing" event handler we write the following request:
QueryText = "SELECT
| Self-supporting Balances.Account,
| Self-supportingRemainings.Subconto1 AS Subconto1,
| ISNULL(SUM(Self-AccountingRemaining.AmountRemainingDt),0) AS AmountRemainingDt,
| ISNULL(SUM(Self-accountingRemains.AmountRemainingCt),0) AS AmountRemainingCt,
| MAXIMUM(Cost Accounting Balances.Subaccount2.Date) AS Date of SettlementDocument,
| MAXIMUM(Self-Accounting Balances.Subaccount2.Number) AS Accounting Document Number
|FROM
| Accounting Register. Self-supporting. Balances (&OnDate, Account = &account,) AS Self-supporting Balances
|WHERE
<>&group and
| Self-supporting Balances. Sub-account 1. Parent<>&group1
|GROUP BY
| Self-supporting Balances.Account,
| Self-supporting Balances. Sub-account 1,
| Self-supportingRemains.Subconto2
|ORDER BY
| Subconto1
|AUTO ORDER";
My task was to limit the groups of counterparties for which mutual settlements are uploaded.
We determine the values of the variables that will be used in the future.
OnDate = date("20130101");
TD = CurrentDate();
group = Directories.Counterparties.FindByName("Buyers");
group1 = Directories. Counterparties. Find By Name("Returns from INDIVIDUALS");
We create a table that we will later pass to the value conversion rule.
TZ = New ValueTable();
TK.Columns.Add("Counterparty");
TK.Columns.Add("Amount");
TK.Columns.Add("AmountREGLE");
TK.Columns.Add("CalculationDocument");
TK.Columns.Add("Settlement Document Date");
TK.Columns.Add("Settlement Document Number");
TK.Columns.Add("Partner");
TK.Columns.Add("Currency of Mutual Settlement");
TK.Columns.Add("Payment Date");
We set the parameters, call the request, fill out the table and call the conversion rule.
request = new Request(RequestText);
request.SetParameter("group", group); request.SetParameter("group1",group1);
request.SetParameter("OnDate",OnDate);
request.SetParameter("Account", Charts of Accounts. Self-accounting. Calculations with Other Suppliers and Contractors);//76.05
Fetch = request.Run().Select();
TK.clear();
While Select.Next() Loop
if Sample.SumRemainingCT = 0 or Sample.SumRemainingCT = "" then
continue;
endif;
if Sample.AmountRemainderCT< 0тогда
report(""+Sample.Subconto1+" negative value "+Sample.SumRemainingCT);
endif;
LineTZ = TZ.Add();
Line TK.Counterparty = Selection.Subconto1;
LineTZ.sum = Selection.SumRemainingCT;//Selection.SumRemainingCT;
LineTZ.sumRegl = Sampling.SumRemainingCT;//Sampling.SumRemainingCT;
Line TK.Calculation Document Date = Selection.Calculation Document Date;
Line TK.Calculation Document Number = Selection.Calculation Document Number;
LineTZ.PaymentDate = TD;
EndCycle;
OutData = New Structure;
OutgoingData.Insert("Date", CurrentDate());
OutgoingData.Insert("CalculationsWithPartners", TK);
OutgoingData.Insert("Operation Type", "Balances of Debt to Suppliers");
OutgoingData.Insert("Comment", "Generated on account credit 76.05");
report("76.05 CREDIT start");
UploadByRule(, OutgoingData, "Input of Balances for Mutual Settlement_7605Credit");
We similarly perform the same operation for the remaining necessary accounts (their description, as well as the ready-made rule, is in the attachment).
3) Let’s move on to creating object conversion rules; to do this, open the “Object Conversion Rules” tab. Let's add a new rule there with the name "Input Balances By Mutual Settlement_7605Credit", leave the source object empty, set the receiver object to the document "Enter Balances", and on the settings tab remove the flag "Search the receiver object by the internal identifier of the source object".
In the "Before loading" event handler we will write the following code:
Generate NewNumberOrCodeIfNotSpecified = true;
In the "After loading" event handler we will write:
execute(algorithms.AfterLoadInputRemainings);
it will execute an algorithm with the following content:
currency = Constants.RegulatedAccountingCurrency.Get();
object.Owner = SessionParameters.CurrentUser;
object.organization=parameters.organization;
for each page from object.calculationspartners loop
Page.SettlementDocument = Directories.Counterparty Agreements.empty link();
PageCurrencySettlements = currency;
if ValueFilled(page.counterparty.partner) then
p.partner = p.counterparty.partner;
otherwise
partners = Directories.Partners.FindByName(page.counterparty.Name);
if the desk<>Undefined and desks<>Directories.Partners.emptylink() then
p.partner = desk;
object2.Partner = desk;
object2.Write();
otherwise
execute(algorithms.AddPartner);
endif;
endif;
end of cycle;
This algorithm will be executed on the receiver side (BP). In addition to transferring balances for mutual settlements, there is the task of transferring counterparties, but the UT uses partners, so after generating the document, we check whether all counterparties and partners are in the receiver database; if for some reason they are not there, then we add them.
Adding contractors will implement the conversion rule for the “Counterparties” directory; you can create it in the same way as the previous rule, but allow the system to compare the necessary fields.
An algorithm was created for partners that is executed on the receiver side.
In order to execute the algorithm on the receiver side, you need to check the “Used when loading” flag in the upper right corner of the algorithm window (when editing it).
Below is the code for the "Add Partner" algorithm:
nPartner = Directories.Partners.CreateItem();
nPartner.Name = page.counterparty.name;
nPartner.Comment = "Created when loading from BP";
nPartner.NameFull = page.counterparty.NameFull;
nPartner.Supplier = ?(find(page.counterparty.AdditionalInformation,"Supplier")>0,true,false);
nPartner.Client = ?(find(page.counterparty.AdditionalInformation,"Client")>0,true,false);
OtherRelations = ?(find(page.counterparty.AdditionalInformation,"Other")>0,true,false);
npartner.Write();
p.partner = npartner.link;
counterparty = Directories.Counterparties.FindByName(page.counterparty.Name);
object2 = counterparty.GetObject();
object2.Partner = npartner.link;
object2.Write();
Let's go back to the object conversion rule. Now we need to establish correspondence between the source and destination fields; this could have been done immediately before writing the code. In order to compare fields, in the lower tabular part there is a button for calling the “Properties Synchronization” wizard. In this wizard, we can either map the fields or leave them both without a source and without a destination. In our case, we leave all fields and PMs without a source.
After the required fields have been selected in the lower TC, for each field we set a flag in the “Get from incoming data” column. This flag indicates that the system will look for this field in the incoming data. It is important that the field name matches the name in the incoming data, otherwise a message will be displayed stating that the field was not found.
The text does not describe all the nuances of the process.
Currently, the transition from 1C:Enterprise 7.7 to 8.3 (similar to 8.2) has become a headache for accountants. Preferably as quickly as possible and without errors. If you are a 1C:Accounting programmer and you need to convert these documents from the seventh version to the eighth, then this article is for you.
Take just a few steps and your data transfer problems will be solved. Read this instruction to the end, and you will see how to do this. First, you must prepare a workplace on your computer for the necessary manipulations. Firstly, your hard drive must be at least 100 GB. This is necessary because the transfer of balances is multi-level. And you will need to work with several 7.7 configurations.
If you need a quick and high-quality transition from 1C Accounting 7.7 to 1C 8.3, contact us! Our average turnkey cost is 6,600 rubles.
Transferring data from 1C 7.7 to 1C 8.3 accounting 3.0
So, before working with transferring data to version 1C 8.3, you need to prepare this data in version 7.7. To do this you must do the following. Let’s say you have a working database “Accounting for an Enterprise” on your computer, which your accountants work with. Using Export77 processing, upload all the necessary documents to a text file and from that moment on, never return to the main working database. Your further manipulations will occur with other configurations.
Install the latest Release 1C:Enterprise 7.7 into the new directory. (the package includes a standard empty version (without data) and a demo version). We will work with the standard version. Now run this database and, using Import 77 processing, load data from your main database from a text file.
When converting data, some documents may not be processed. It's not scary. The trick is that you can easily fix this after the transfer, since in the standard database you work with the main standard chart of accounts. Therefore, no matter how sophisticated the subaccounts are, it is easy to fix this in your working database in about 3 hours by going into each unposted document and changing the accounts that you have in your configuration in the account fields.
Naturally, before the transfer, you first bring the chart of accounts of the standard configuration into line with the chart of accounts of your main working base. The options are purely individual depending on the specifics of your organization. Having done this work, you receive a standard configuration filled with data from your working database.
Now we need to do another data transfer. To do this, install the standard zero configuration again in a new directory. And transfer the data there from the standard configuration with your data. As a result, you will get an ideal version 7 database, ready for transfer to version 8.2.
The fact is that data is transferred directly to the eighth version exclusively from the “untouched” standard version 7.7. And now you have just such a configuration. But now it is not empty, but with your work data.
All! We launch 1C:Enterprise 8.2. Select “Data transfer from version 7.7.” and enjoy how the program itself transfers data from your processed 7.7., transfers documents and displays a comparative table of the balance sheet of versions 7.7 and 8.3.
Of course, there will not be a 100% result. But at 70-80 percent you will get a match. And then your work will be done only in version 8.3.
Possible inaccuracies are easily corrected. It's another 3-4 hours. You go to the document journal and either adjust accounts or fields (for example, “Agreement” or “Main cash desk”). It depends on the degree of difference between your 7.7 base. from standard. As a result of all these actions, your working configuration of version 8.3 will be able to produce accounting data through the balance sheet in an ideal form.
After the transition, it will be useful for you to learn how to work in the new program. For this purpose, we have prepared a section Training 1C Accounting 8.3.
By the way! If you need modification of 1C programs, you can contact us!
Transferring a 1C 7.7 database to 8.3, how to do it?
Many standard (and some industry-specific) eight-core solutions already have either built-in transfer tools from 7.7 or in the form of additional files in the template installation directory.
If you transfer it yourself, then on the ITS disk (as well as in many places on the Internet - Google can help) there is a “Loading from a spreadsheet document” processing, which allows you to load arbitrary tabular data into directories/documents/registers. With a sufficiently high level of qualification, you can use combat artillery - a special configuration “Data Conversion 2” (not to be confused with 3.).
Can you tell me why this error occurs? In the documentation for 1C, everything is written too confusingly - after all, you have to receive a salary, so it’s impossible to understand their manuscripts at all, war and peace are easier than their tutorials on operating their far from complex system.
Maxim Kravchenko, well, everything is written in Russian :)
In my experience, the most common reasons may be the following:
1) The wrong path is specified in the exchange settings with 7.7. There are either just typos here or the path to the wrong directory is specified. Or the local path on your computer is specified, but the exchange takes place on the side of the enterprise 1C server and this server naturally does not see anything along your path (a common problem).
2) On the side of the computer that is trying to communicate with 7.7 (local or server) there is no fully installed 7.7 platform. Those. there is no registered COM object, and the 7.7 base has traditionally been connected using a directory with a hacked platform that does not need a key or any system data.
3) There are no access rights to the directory with the 7.7 base (especially important when working on a server, where the rphost worker process runs under a service user, and the 7.7 base directory is open to specific people).
Maxim Kravchenko, why not through IRC or chats on the people’s “damn little streets”? 🙂
No, I won’t step on the same rake again. I already gave one ungrateful person my Skype and he sat on his neck.
If you have general questions the answers to which might help others, ask. Let's do a good deed together. No secret negotiations.
P.S. So that people do not lose the desire to give answers on this resource, it would be nice to mark solutions or click the “like” button on the most adequate answers, even if they did not directly help.
Maxim Kravchenko, FAQ is impossible since pure 7.7 does not exist in nature. There is a whole palette of standard/industry solutions, there are different versions of the same specific configuration, but none of this set covers the needs of companies out of the box, and all 7.7 sold were completed for years after installation. Taking into account the fact that mass sales of 7.7 stopped more than ten years ago, there might be nothing left of the standard functionality in your particular database.
It’s one thing if you take the standard transfer mechanisms, which I wrote about in my answer, and transfer it, understanding that the responsibility for the mistakes is on you and you will put the “girls” to correct all the inconsistencies. It’s quite another thing to hire a specialist for money. You need to describe all reference books for transfer, the amount of information to transfer (articles, barcodes, TIN, etc.), where to get the missing information, and so on. I'm not ready to take on your project right now. I suggest registering this task on freelancer sites and holding a tender between them.
Transfer rules 1s 8
Transferring data from programs “1C: Accounting 8 rev.2.0” to “1C: Accounting 8 rev.3.0”
Designed primarily for modified configurations 1C:Accounting 8 edition 2.0(possible names on the Internet BP 2.0 or BP 8.2) as a basis for developing original rules for transferring to the configuration 1C:Accounting 8 edition 3.0(possible names on the Internet BP 3.0 or BP 8.3), of course also suitable for transferring data between standard configurations.
Possible strategies for migrating from edition 2.0 to 3.0 can be found here.
Transition from 1C:Accounting 8 edition 2.0 on 1C:Accounting 8 edition 3.0 It is recommended to perform at the beginning of a new period (year, quarter, month) after completion of routine operations of the previous period.
Data transfer is carried out using universal processing that downloads data from the information base 1C:Accounting 8 edition 2.0 to a file in XML format. The resulting file is uploaded to the information database 1C:Accounting 8 edition 3.0 using universal data loading processing.
The following files are required to transfer data:
ACC20_30.xml - data conversion rules.
From the information base BP 2.0 V BP 3.0 transferred:
information on current balances on accounting accounts of the information base “1C: Accounting 8 rev. 2.0” as of the date of conversion of the information base
information base documents BP 2.0 for the selected period
necessary reference information from the information base “1C: Accounting 8 edition 2.0”
— data from the 1C information base BP 8.2 uploaded to a separate file (data file);
— the resulting file is uploaded to the 1C information database BP 8.3.
No installation is required, since processing built into standard configurations is used, in 1C:Accounting 8 edition 2.0 And 1C:Accounting 8 edition 3.0.
(Read below about the possibility of using specialized processing)
In a programme 1C:Accounting 8 edition 2.0 you need to open processing (menu: Service — Other data exchanges), select the folder in which the transfer rules are located (see Fig. 1) and download the exchange rules. I recommend loading exchange rules forcibly every time, even if they are automatically loaded when processing starts. To do this, you need to either reselect the rules file or click the button Re-read the exchange rules. You do not need to include all transfer rules. Only those necessary to transfer balances and/or documents should be used. All reference books are transferred via links, as needed, i.e. only those involved in balances and documents. This ensures that there is no “garbage” in the new information base.
If you need to unload balances at the end of the year, for example at the end of the day 12/31/2014, i.e. It would be more correct to say at the beginning of 2015, then the unloading period should be 01/01/2015 - XX.XX.XXXX. Documents for entering balances into BP 3.0 will be dated 12/31/2014. From 01/01/2015 to BP 3.0 you need to create documents reflecting current transactions. If you only need leftovers, then you need to enable rules for downloading data from the section Incoming balances(see Fig. 1). Rules for downloading data from a section Documentation in this case it should be disabled (see Fig. 3). The upload period, for example, 01/01/2015 - 01/31/2015 means that documents from January 2015 will be transferred. Rules for downloading data from a section Documentation in this case must be included.
Rice. 1 . Processing for data upload
First of all, we recommend transferring the organization’s accounting policies (directory Organizations transferred via links). When transferring data, you can additionally set parameters (see Fig. 2). To return to default values, you must reload the exchange rules.
Fig.2 Setting parameters
Parameter Ignore VAT batch register determines first of all whether it will be filled in BP 3.0 when entering balances Inventory table Data on invoices received. It also affects how the subconto will be filled in Parties: according to BOO or by the remainder of the register VAT on purchased assets.
Setting this parameter allows you to manage the unloading of balances for organizations using simplified tax system. When accounting is running, if the register data does not match Expenses under the simplified tax system It may be more useful for the accounting register to unload the balances according to accounting data only, without taking into account the register simplified tax system, which can add a lot of errors. In this case, in the documents for entering initial balances in BP 3.0 requisites Reflection in the simplified tax system And Flow Status are filled with default values.
When setting the parameter to Yes simultaneously with the documents, sets of registers associated with these documents will be transferred. Otherwise, the contents of the documents are transferred, and to receive movements, the documents must be entered into the database BP 3.0 after the transfer. You must understand that not all movements of documents existing in BP 8.3, there are correspondences in BP 8.2. Therefore, even if you choose the option of transferring documents with movements, for some types of documents you may need to post in order to create all the necessary sets of registers.
Fig.3 List of documents that are transferred to BP 3.0
The list of directories and registers of information for transfer is presented in Fig. 4. If anyone is interested in expanding this list, please contact the author. There are rules for transferring objects for many directories. This is understandable, because a variety of reference books are present in many documents and, accordingly, are downloaded via links. It’s not difficult to create unloading rules from them; you can do it yourself. The rule for unloading a directory is needed if there is a desire to transfer the entire directory, and not just links.
Rice. 4 List of directories and registers of information for transfer
Features of transferring balances on accounts 76.AB and 76.VA
When set to Yes parameter Correct misgrading in settlements with counterparties errors made in accounting can be corrected. What regrading is is clear from Fig. 5.1: for the counterparty the balance is zero, but for the second subconto the amounts are not zero. Such balances will not be carried over.
Fig.5.1 Re-grading in residues
If set to Yes parameter Messages in detail, then during uploading explanatory messages will be displayed (see Fig. 5.2).
Fig. 5.2 Messages in case of misgrading in balances
Features of transferring balances on inventory accounts
The algorithm for correcting errors such as misgrading in residuals works in a similar way. Inventory. This algorithm works when setting the parameter Correct misgrading of inventory balances in meaning Yes. An example is shown in Figure 5.3. Accounting for account 10.03 is carried out by item, warehouse and batch. Remaining by item Gasoline AI-92 on warehouse No. 4 equals zero, but if you expand the balances by batch, there will be a lot of them. The algebraic sum of the balances by batch is equal to zero, this is re-grading. Such balances should not be transferred, because this is an obvious mistake. They will not be transferred if the parameter is set.
Fig. 5.3 Re-grading in residues Inventory in the source database BP 2.0
Things are worse with the balances warehouse No. 6. The remainder is non-zero, so the misgrading correction algorithm will not work, the remainder will be transferred. Let's look at how they will be transferred. Sum -155,29 will not be included in the transfer, because such a remainder is in BP 3.0 it is impossible to enter, it is impossible to enter a zero quantity and a non-zero amount, the document for entering balances will not be posted, so we do not upload it. As a result, in BP 3.0 the remaining two amounts will fall (see Fig. 5.4). The rest was transferred as if with an error. In fact, of course, there is no transfer error here, but there are accounting errors.
Fig.5.4 Result of transfer to BP 3.0
Whether or not to use the described algorithm for correcting misgrading is up to the user to decide. You just need to remember that balances with a zero amount are never transferred. According to the author, this is the most correct behavior, at least it allows you to enter a document for entering balances and begin reconciliation. To more quickly search for positions of discrepancies between balances BP 2.0 And BP 3.0 Based on the results of the transfer, it can be recommended to select such problematic positions in the source by setting up the balance sheet accordingly. How to do this, see Fig. 5.5.
Fig.5.5 Selection of positions with zero quantity
After unloading is completed you need to run the program 1C:Accounting 8 edition 3.0. Loading, both initially and during repeated data transfers or additional transfers, should be performed using standard processing Universal data exchange in XML format(see Fig. 8.1). You can open it through the menu: All functions - Processing - Universal data exchange in XML format. If there is no item on the menu All functions, then you need to go to Service -Parameters and check the box Show command All functions.
After loading the data into the 1C:Accounting 8 rev.3.0 database, it is necessary to enter documents for entering initial balances to obtain all the necessary movements. You can use processing Group transfer of documents(see Fig. 8.2) or post documents in the journal (menu: All functions - Documents - Entering balances). If documents were transferred without movement (parameter Upload document movements set to value No), then in order to receive transactions and entries in registers, it is necessary to post documents.
Data conversion technique.
Conversion, if necessary, can be performed in several stages, for example, first reference books, then documents for entering balances, then other documents. Re-transfer of information is possible. Between transfers, you should not make corrections to the transferred data in 1C:Accounting 8 edition 3.0, otherwise these fixes may be lost during repeated transfers.
Balances are transferred through documents Entering initial balances.
More details on the methodology for entering balances can be found in the article on the ITS website of the 1C company.
Important! Before entering opening balances, accounting policy parameters must be set. The organization's accounting policy parameters are read on the date following the date the balances are entered. For example, if the date for entering balances is December 31, 2013, then the accounting policy parameters established as of January 1, 2014 are taken into account. This allows you to take into account the parameters of the current accounting policy (for example: if in 2013 the organization applied a simplified taxation system, and since 2014 . switched to the general system - then when entering balances as of December 31, 2013, the accounting policy parameters of 2014 will be taken into account). That is why, as stated above, we first of all recommend transferring the organization’s accounting policies.
Important! If you decide to start working in 1C:Accounting 8 edition 3.0 before the remnants have been transferred there, it is necessary first before starting work in 1C:Accounting 8 edition 3.0 transfer directories. Otherwise, errors may occur when transferring balances to a non-empty database.
Important: It is possible to solve the synchronization problem when loading into a non-empty database - object matching.
How to work with specialized data transfer processing.
Processing is used only in mode File. Processing Transfer_Data_from_BP20_to_BP30.epf should be launched in the infobase where the data is transferred, i.e. V 1C Enterprise Accounting ed.3.0. In the first window (see Fig. 9) you should specify the option for loading data from the infobase on the 1C:Enterprise platform:
Load data directly from the infobase
Fig.9 Start window for data transfer processing
In the next window (see Fig. 10) you need to configure the transfer:
- When the length of service is interrupted after dismissal Since January 1, 2007, a slightly different procedure has been in force for determining the continuity of a citizen’s work experience. Before this, if 3 weeks did not pass when moving from one place of work to another, then the length of service was not interrupted. Since 2007 […]
- ANKO Tambov Center for Forensic Expertise and Research, ANO ANKO Tambov Center for Forensic Expertise and Research, ANO is registered at Tambov, Rabochaya St., 37, office 40, 392008. DIRECTOR of the organization AUTONOMOUS NON-PROFIT ORGANIZATION TAMBOV CENTER FOR JUDICIAL […]
- Order on the working time schedule Sample order on the working time schedule On the working time schedule In accordance with Articles 100, 103, 104, 73 of the Labor Code of the Russian Federation and the Internal Labor Regulations of PJSC "Organization", in order to optimally operate the enterprise and increase […]
- In Central City Hospital No. 20 of Yekaterinburg, where the chief doctor was fired, an acting company has been appointed | Sverdlovsk region | Ural Federal District Alena Tunis was appointed acting chief physician of the central city hospital No. 20 of Yekaterinburg. As the correspondent reports [...]
- Ohm's law for parallel Home Remember physics: 7th grade 8th grade 9th grade 10-11th grade videos on physics multimedia 7th grade. multimedia 8th grade multimedia 9th grade multimedia 10-11 grades. astronomy tests grade 7 8th grade tests 9th grade tests demonstration tables of the Unified State Exam [...]
- Law of the RSFSR “On competition and restriction of monopolistic activities in commodity markets” of March 22, 1991 N 948-1 (as amended by the Laws of the Russian Federation dated 06.24.1992 N 3119-1, dated 07.15.1992 N 3310-1; Federal Laws dated 25.05. 1995 N 83-ФЗ, dated 05/06/1998 N 70-ФЗ, dated 01/02/2000 N 3-ФЗ, dated […]
Select an infobase from the list (the list is the same as when starting the application 1C Enterprise).
Specify user name and password
Specify what information should be transferred
Additionally, you can check the data in the source for the correctness of the transfer
When transferring directories, data will be transferred from directories of the selected infobase, for which there are upload rules. In this case, the directories are transferred entirely. If the checkbox is not checked, but any other transfer option is selected, then the directories will also be transferred, but only to the extent necessary to fill in the data in the transferred transactions and documents. When transferring data, you can transfer reference books, documents and balances to the beginning of the year. Transfer options can be selected in any combination. When transferring balances, data on account balances as of January 1 of the selected year will be transferred according to the rules indicated in Fig. 1. In 1C: Accounting 8, documents “Entering initial balances” will be created for December 31 of the year preceding the selected one.
Fig.10 Transfer parameters window
If the option to check data is selected, then before loading such a check will be performed and the result of the check will be displayed on the screen (see Fig. 11). If errors are found during the verification process, the transfer process will be paused to allow errors to be corrected. If you need to upload and download data despite errors, uncheck Check data before downloading or click Continue. The list of check rules is constantly updated.
Fig. 11 Result of data verification before loading
During the process of transferring data from the source to the receiver, a picture will be updated on the screen that indicates the current stage: connecting to the infobase, uploading data, loading data, etc. In addition, more detailed information is displayed below in the form of a line, for example, “Data upload: Documents (3 /3)”. Once the data has been downloaded, the process of posting the downloaded documents and then checking the downloaded data starts. If errors occurred during document processing or data verification, messages about this will appear in the message window upon completion. Error messages can also be viewed in a separate window by clicking on the hyperlink Error Information(see Fig. 12).
Fig.12 Indication of data transfer process
A fragment of the table containing error records is shown in Fig. 13. First, the table displays messages about errors that occurred when posting documents, then errors during verification. Checking the downloaded data consists of comparing the balance sheets generated on the date the balances were entered at the source and destination. If the balance on any account does not match, a record is created about this. By double-clicking on an entry in the error table, you can open the problematic document for correction and manual editing. The same can be done in the message window.
Fig. 13 Fragment of a table containing error records
After making corrections in the destination database, it does not make sense to transfer the same information from the source database again, because when transferring again, this data will again be recorded with errors. Therefore, try to make corrections at the source, not at the receiver, or not repeat the transmission of the same information. For example, after transferring initial balances and correcting all documents for entering initial balances in the receiver, do not set the flag for further transfers Balances at the beginning of the year.
Updates are free for 6 months after purchase. After the free update period ends, you can receive updates on a paid basis (see price below). At the same time, if you purchased several software products, as part of sets or separately, then you have the right to count on a discount. You can learn more about the discount system.
The rules are created using technology Data conversions: Easy to edit.
Completely open, there are no licensing restrictions other than a ban on replication.
File TransferDemo20_30.xml is an download from the database obtained by transferring the BP 2.0 demo database, distributed by 1C, to the BP 3.0 database. Create an empty BP database 3.0.44.94, either from a 1C template or using the 1Cv8.cf configuration file. Set in the accounting parameters to Setting up a chart of accounts inventory accounting by warehouses and batches. Download the demo database file TransferDemo20_30.xml using processing Universal data exchange in XML format. The demo database shows the transfer of balances as of 01/01/2009 and documents for the period from 01/01/2009 to 12/31/2009.
The rules are regularly updated for new releases, suitable for BP releases 2.0.64.23 and later. There is no need to search and select the desired version of the transfer rules; they are suitable for any SOURCE release in the specified range. If you need rules for earlier releases, please contact the author. The RECEIVER release must be exactly like that as per the rules.
08/29/2018 Unloading of balances by section has been allocated as a separate rule Credits and loans(accounts 66, 67), previously it was part of Other accounting accounts
08/20/2018 Update to 2.0.66.59 and 3.0.64.48
06/03/2018 Added transfer of documents Reflection of salaries in regulated accounting
05/18/2018 Update to 2.0.66.54 and 3.0.61.37
02/23/2018 Update to 2.0.66.48 and 3.0.58.41
01/18/2018 Update to 2.0.66.46 and 3.0.57.17
12/22/2017 Update to 2.0.66.42 and 3.0.56.22
11/03/2017 Update to 2.0.66.37 and 3.0.53.38
09/26/2017 Update to 2.0.66.37 and 3.0.52.35
06/14/2017 Update to 2.0.66.29 and 3.0.50.18
05/05/2017 Update to 2.0.66.25 and 3.0.49.27
04/04/2017 - added the creation of invoices received when in BP 2.0 there is only a number and date. You need to set the parameter Convert invoices(create new ones if the source contains only the number and date)
02/06/2017 Update to BP 3.0.47.23
01/26/2017 Added transfer of documents Reflection of VAT accrual And Reflection of VAT for deduction
01/11/2017 Update to BP 2.0.66.8 and BP 3.0.46.16. Case transfer excluded NDSpoOSiNMA. In earlier versions, where it is included in the configuration, it will not be transferred.
12/14/2016 Update to BP 3.0.44.203
12/07/2016 Added transfer of documents Debt adjustment
12/01/2016 Added parameter Do not take into account the register Expenses under the simplified tax system, which allows you to manage the unloading of balances for organizations using the simplified tax system
11/21/2016 Added downloading of the directory Users a separate rule with the creation of information security users in the receiver (details here). Added transfer of balances across RS Employees of organizations(personnel data). When transferring balances on accounts 76.AB and 76.BA, it is possible to check and correct the misgrading in the second subaccount.
11/08/2016 The list of documents has been expanded.
10/28/2016 Added transfer of documents. A transfer demo has been added, this is the result of transferring the BP 2.0 demo database.
10.26.2016 Fixed creation of empty documents for entering balances when there are account balances 10.07
09.09.2016 Update to BP 3.0.44.102
03.23.2016 Improved transfer of data on invoices received (when transferring inventory balances)
01/11/2016 Added transfer of contact information of individuals, citizenship, passport data, information about disability, statuses of individuals. Added rules for transferring bank accounts and item accounting accounts.
12/23/2015 Update to BP 3.0.43.29. Added transfer of contact information of counterparties and their contact persons.
12/14/2015 Rules for BP 3.0.42 were created
The package includes: transfer rules "ACC20_30" and processing Transfer_Data_from_BP20_to_BP30. If your organization does not have a full-time programmer to carry out the work, we are ready to offer the services of our specialist (the programmer will connect to your computer via the Internet using a special program for remote work and perform the necessary work). If possible, provide a working base "1C: Accounting 8 edition 2.0", we can transfer the data ourselves and transfer the file “ 1C:Accounting 8 edition 3.0» with transferred balances. The cost of this service is not included in the total cost of the package.
Important. Not all documents are transferred (for compatibility with older BP 2.0 releases). Before purchasing, carefully read the list in Fig. 3.
Transferring data from the programs “1C: Accounting 7.7” and “1C: USN 7.7” to “1C: Accounting 8”
A few words about how data is transferred from a standard configuration “ Accounting", edition 4.5 for 1C:Enterprise 7.7 or configuration "" (hereinafter referred to as Source Configurations) into a standard configuration " Enterprise accounting", edition 3.0 for 1C:Enterprise 8 (version 3.0.52), hereinafter referred to as “Receiver configuration”.
IMPORTANT! Data transfer is possible from the configuration Accounting edition 4.5 for 1C:Enterprise 7.7 versions 7.70.569 and later or from the configuration " Simplified taxation system, ed. 1.3» versions 7.70.219 and higher.
It is recommended to switch from the source Configuration to the destination Configuration at the beginning of a new period (year, quarter, month) after completing the regulatory operations of the previous period.
Data transfer is carried out using specialized processing that downloads data from the source Configuration information base into a file in XML format. The resulting file is loaded into the recipient Configuration infobase using universal data loading processing.
ACC_ACC8 .ert - external processing of uploading data to an external file from the configuration " Accounting, Rev. 4.5»;
USN_ACC8 .ert - external processing of uploading data to an external file from the configuration " Simplified taxation system, ed. 1.3»;
ACC_ACC8 .xml - data conversion rules.
USN_ACC8 .xml - data conversion rules.
The following are transferred from the Source Configuration infobase to the Recipient Configuration:
— information on current balances in the accounting accounts of the Source Configuration information base as of the date of conversion of the information base;
— current documents with a date greater than the date of conversion of the information base.
The conversion is carried out in two stages:
— data from the Source Configuration information base is uploaded to a separate file (data file);
— the received file is loaded into the information base of the recipient Configuration.
To install data migration processing, you must use the setup.exe installation program. After starting the program (if the number of 1C:Enterprise infobases is large, then after some time) a dialog box will appear in which you need to mark those infobases where data transfer processing will be installed. The window looks like in Fig. 1. If the number of information bases is more than seven, then use the “up” and “down” buttons to navigate. If several information bases are selected, then the “path” line reflects the location of only the last selected base. This information is of an auxiliary nature and is used optionally for additional control on the part of the user over the result of the installation program; do not pay special attention to it, the program itself will determine where the information bases you have chosen are installed.
Fig.1 Window for selecting infobases during installation
Additionally, you can specify the folder in which data transfer processing will also be installed; to do this, use the folder selection window (by clicking the button with three dots). The full path for the selected folder will be reflected in the selection line. After clicking on the “install” button, the necessary files will be installed in the selected infobases and (or) in the selected folder. After completion, you can click the “details” button and see a detailed installation log, which files were written into which folders. As a result, the selected folder should have something like the following picture, see Fig. 2.
Fig.2 Files installed in the selected folder
To subdirectory ExtForms processing and transfer rules are established. Please note that upload processing ACC_ACC8.ert and data upload rules replace standard processing and rules. If you want to keep the standard transition mechanism, install the new processing in a separate directory and not in the infobase.
The installation process is described in more detail using the example of installing the report " Express check of accounting for the configuration “1C: Accounting 7.7”«.
In a programme " 1C: Accounting 7.7"You need to open processing from additional options" Transition to 1C:Accounting 8, ed. 3.0“, select the folder in which the transfer rules are located (see Fig. 3) and download the exchange rules. You do not need to include all transfer rules. Only use those that are necessary, for example for transferring residues, or residues and documents. For example, in the directories group, not a single rule can be included, because all directories are transferred via links, as needed, i.e. only those that are involved either in balances or in documents. This ensures that there is no “garbage” in the new information base. Documents also do not need to be included all. For example, if some documents are not in your database, or you do not want to transfer them, you do not need to enable this rule.
Fig.3. Processing for data upload
I recommend setting the data file name to “C:\v77_v8\Exp77_80.xml”, this is the folder that is often used by default in the program “ 1C: Accounting 8" when downloading data from programs on the platform " 1C:Enterprise 7.7". If necessary, set the parameters on the " Options«.
During the process of downloading data from the configuration " Accounting 7.7"Various errors may occur. The transfer rules presented here differ from the standard ones in that at the data upload stage they search for typical errors. Let's consider those about which messages are displayed.
Zero quantity and non-zero amount of inventory items. Entering the balance in the receiving Configuration in such a way that the quantity of material is equal to zero, and the cost estimate of the material is not equal to zero, is impossible, and it is also pointless, because this is an error. Therefore, when transferring balances, such positions (with a zero quantity) will not be included in the balance entry documents. Consequently, if errors are not corrected before data transfer, then the amounts in the source and destination of the data when transferring balances will not match, which will cause additional reconciliation difficulties. Therefore, in the process of downloading data from the configuration " Accounting 7.7» messages about encountered errors are displayed (see Fig. 4). Additionally, to find errors, we can recommend using the “Express check of accounting maintenance” processing, namely the rule “Absence of a non-zero amount when there is a zero quantity for materials.”
Fig.4.1 Messages about encountered errors
Non-zero balance for subaccount of the second (third) level, while the balance at the first (second) level is zero. This is a fairly common situation of erroneous record keeping. A typical example is shown in Figure 4.2. This condition arises as a result of “re-grading” in analytical accounting. For example, an agreement is indicated in the cash flow documents, but there is no agreement in the capitalization documents, or vice versa, or there are agreements but they are different. In all these cases, there is a non-zero balance under the contracts, despite the fact that the balance under the counterparty is equal to zero. A similar picture can arise in the accounting of materials and nomenclature (when total accounting by storage location is included): re-grading between warehouses, especially if the warehouses are financially responsible persons.
Fig. 4.2 Example of errors in accounting
It is clear that this is a mistake, and it is clear that it makes no sense to carry over such balances. In order to exclude the transfer of this kind of balances, there is a parameter “Do not unload balances if there is a zero balance at the upper level.” If this parameter is set to one, then during upload the messages shown in Fig. 4.3 (compare with Fig. 4.2), and balances for such positions will not be unloaded. You can use different combinations of this parameter with the rules for transferring different residues. If you transfer not all balances at once, but by accounting sections, then you can transfer balances from different accounting sections with different parameter values.
Fig.4.3. Error messages
Empty contract values or foreign contracts. The problem is similar to that described above, the reason is the same - misgrading in analytical accounting for contracts (see Fig. 4.4). But the balance for the counterparty is not zero, so the verification rule described above will not work. When transferring data, an error will occur when posting the document for entering balances, because an empty contract value is not allowed.
Fig.4.4 Report showing error
To eliminate such errors before transfer, error messages are issued at the data upload stage (see Fig. 4.5). The same figure shows that another error was encountered: the contract does not correspond to the counterparty, i.e. the owner of the contract is another counterparty. Such errors are often found in modified, i.e. non-standard configurations or in databases created long ago, when even in standard configurations there was not a sufficiently strict check for compliance of contracts when filling out documents.
Fig.4.5 Accounting error messages
Checking for empty values of contracts and other people's contracts is carried out if the parameter " is set to one Check contracts for empty values and compliance with the counterparty". Additionally, to find errors, we can recommend using the “Express check of accounting maintenance” processing, namely the rules “Absence of empty analytics for contracts” and “Compliance of counterparties and contracts.”
There are other error checks, for more information please contact us (contacts at the bottom of the page).
We will show how you can transfer data in parts, rather than entirely, using the example of uploading documents of a separate type or even individual copies of documents of a selected type. Let’s mark only one data upload rule “ Payment order"(see Fig. 5). This will allow you to upload documents only like " Payment order". If, with these parameters, you click on the “ Unload", then all documents of the type " Payment order", located in the time interval with " start date" By " expiration date". Click the button " Install PVD", after that the inscription " Selection of data for Payment order«.
Fig.5 How to set a rule for uploading data of a certain type
Next, click the “Add condition” button, you will be able to select a selection attribute (see Fig. 6.1), most often it is “ CurrentDocument“, which allows you to select a separate document from the list of documents of this type. You can, using other selection details, obtain a selection by group of documents, for example, select documents by date. In all cases, documents are selected within the time interval specified by the parameters " start date" And " expiration date«.
Fig.6.1 How to select a single document
Important! "1C"), which in some configurations does not allow the selection of documents when uploading according to the selection details. This is due to the fact that in the standard rules the selection of documents is carried out by a request without specifying a period. Such requests do not always work.
In a similar way, you can upload directories, not the entire directory, but by selecting according to some details. First, select the desired data upload rule, then successively press the buttons “ Install PVD" And " Add condition". For example, Fig. 6.2 shows how you can unload only those employees with whom at the time of transition from the program " 1C: Simplified taxation system, ed. 1.3" on " 1C: Enterprise Accounting, edition 3.0"(or, as users often say, the transition from accounting 7.7 to 3.0) labor relations have been established.
Fig.6.2 How to select a group of directory elements
Important! An error in the standard rules has been corrected in the proposed rules for data transfer (from the company "1C"), which leads to incorrect selection of directory elements when unloading using periodic directory details, i.e. those that have different values set for different dates. This is due to the fact that in standard rules the selection of directory elements is carried out by a query without specifying a period.
Selection based on the periodic details of the directory is made on the date of the parameter “ expiration date«.
You can use a combination of data upload and selection rules. Rules for which selections have been set will be marked as "[SELECTION]". In order to see or edit the selection of a specific data upload rule, you need to double-click on this rule in the list of rules or, having selected it, click the button " Install PVD«.
Important! If the upload of objects turns out to be empty or incomplete, you need to check whether the synchronization mode is set with 1C: Accounting 8. If this is the case, then only objects changed after the transfer will be uploaded (Directory.Synchronous Accounting Parameters stores the Position of the Last Uploaded Document parameter, which is checked during upload by the CheckFor Upload Possibility function) . Full operation in synchronization mode becomes impossible. The synchronization mode is checked after loading the exchange rules. If the mode is installed, a warning window will be generated (see Fig. 6.5) and you will be asked to disable the synchronization mode.
Rice. 6.5 Synchronization mode warning window
Additional differences from standard rules
Fixed an error in transferring PT&U with old receipt types: if in the documents Receipt of Goods and Services the receipt type is equal to 2 (outdated value) and there is no supplier invoice, an erroneous conversion of this document in BP 3.0 into a return document from the buyer occurs.
An error has been fixed when transferring manual operations that have a subaccount of Division to the PROF version of BP. Such an operation is not recorded in the BP; an error occurs: “The Division field must be empty.” This is due to the fact that the rules are designed to work with CORP versions, however, in PROF, the DivisionDt and DivisionKt dimensions of the accounting register must be empty.
Fixed a bug that led to duplication of directory groups Treaties and, as a consequence, to duplication of elements of this directory (since the search during loading is carried out taking into account the parent). This is illustrated in Figure 6.6.
Fig.6.6 Result of directory transfer Treaties standard rules
Here in the column Parent(directory group) with name 2015 There are two different directory groups with the same name (there is only one group in the source), therefore the contracts are duplicated.
Fixed an error in transferring bank documents when transferring money from one current account to another. IN BP 3.0 in this case a document is created Debiting from current account with the type of operation Transfer to another account of the organization, which is not carried out due to the fact that the details are not filled in Recipient's account. In addition, the details are filled in incorrectly. Account And Debit account. This will show up if they are different, for example 55 and 51, then they need to be swapped. Fixed error not filling in details Type of obligation in tax transfer documents. All of the above applies to release 3.0.43.215.
Props are transferred main contract directory Counterparties.
The rule for downloading the directory has been changed Nomenclature, now the method of data selection is standard sampling, which allows you to select elements of the directory by details (in the standard rules of the simplified tax system 7.7 - BP 3.0 this is not possible). When transferring a directory Nomenclature, are transferred and Item prices via links, i.e. prices of only transferred items of the nomenclature. To enable this feature, you need to set the parameter value to one Upload prices when unloading items.
An error has been fixed in the standard rules “STS 7.7 - BP 3.0” when transferring balances for settlements with counterparties: the type of agreement was always set to Other. Now - depending on the type of balance, according to the accounting section " Calculations with suppliers and contractors"contract type = " With supplier", according to the accounting section " Calculations with buyers and customers"contract type = " With buyer", in other cases, contract type = " Other«.
An error has been fixed in the standard rules “USN 7.7 - BP 3.0” when transferring balances for settlements with counterparties: the amount of mutual settlements was recorded in two details of the document for entering initial balances Sum And AmountKt. Because of this, the entry document for opening balances was not posted.
CheckWith the buyer"(in the standard rules " Other"). The value of the attribute " is set Payment State“, this is important for correctly selecting an invoice for payment to the buyer in bank payment documents in the Recipient Configuration.
When transferring documents of the form " Payment order» the contract type is set to the value « With the supplier"(in the standard rules " Other«).
An error has been fixed in the standard rules “USN 7.7 - BP 3.0” when transferring storage locations: the attribute “ is not filled in Warehouse type«.
Added parameter " Exchange with regulatory authorities included": if its value is 1, then the prop Type of Exchange with Control Authorities directory element " Organizations" is set to " ExchangeIn Universal Format", otherwise in " ExchangeDisabled"as in the standard rules. This is important for repeated (regular) transfers, so as not to spoil the EDI setup.
The search rule for downloaded items for the directory " has been changed Counterparties": first the search is performed by TIN And checkpoint(if these values are filled in), then only by TIN and finally by Name. In all three cases, the search involves the group attribute (ThisGroup) and the group itself (Parent). This is important for repeated (regular) transfers, so as not to create duplicates for counterparties with names changed AFTER loading.
When transferring counterparties, fill in the details CountryRegistration meaning "Russia". This is necessary so that after loading the directory of counterparties into the program "1C Accounting 8" I didn’t have to manually fill out the required details CountryRegistration. If it is not filled in, then in the form of a directory element " Counterparties» details will be available « Tax number" And " Reg. number", and the details " TIN" And " checkpoint" will be hidden.
A data upload rule for transferring the “Employees” directory has been added to the transfer rules “USN 7.7 - BP 3.0” (in the standard rules, only the directory of individuals is transferred).
In the transfer rules “USN 7.7 - BP 3.0”, the transfer rule for the information register Current Tariff Rate of Employees has been corrected.
Features of transferring payment orders for tax payments
For payment orders with transaction type Tax transfer Additional details must be filled in: KBK - budget classification code, compiler status, etc. The structures of these details are in Bukh 7.7 (USN 7.7) and in BP 3.0 do not match. In particular in BP 3.0 Some of these details are included in a separate directory, a link to which is contained in the payment order. Directory Types of taxes and payments to the budget contains a number of supplied elements that appear in the information base, for example, when editing an accounting policy. When transferring data, these elements will also appear when loading the accounting policy. When uploading and downloading payment orders, a directory element Types of taxes and payments to the budget searched using the KBK for substitution into the details of the payment order Tax. Therefore, it is recommended that after transferring the accounting policies, you check whether all the necessary taxes appear in the directory and, if necessary, supplement them. When comparing (synchronizing) KBK in payment orders, the source and receiver do not take into account the four KBK categories, categories 14-17, income subtype code: tax, penalty, fine, etc. In the directory Types of taxes and payments to the budget these bits are filled with zeros. When adding new elements to the directory, digits 14-17 should also be filled with zeros.
Transfer of large information databases.
First of all, when transferring large infobases, the process of downloading data can take a very long time. This happens if there is a large number of balances in one accounting section, for example, balances of goods. To reduce upload time, you can use the technique of splitting one document " Entering initial balances" for a few. If you set the parameter value " Number of lines in the balance entry document» different from zero (see Fig. 6.3), then uploading data into one document will be limited to the specified value. This can very significantly (several times) reduce the unloading time.
Fig.6.3 Setting parameters when transferring data with a document size limitation " Entering initial balances»
Note: the parameter value limits the number of transaction table rows uploaded into one document " Entering initial balances", rather than specifying the number of lines of the document itself. Therefore, the number of document lines will differ from the parameter value; this is not an error. When splitting a document " Entering initial balances” for several documents, a postfix will be added to the comment of each document at the end of the line: “-1”, “-2”, etc.
IMPORTANT! The described algorithm for splitting one document " Entering initial balances"several is used only to reduce the time of data uploading; all documents are uploaded into one file, i.e. Data transfer occurs in one step, comments (postfixes) are generated automatically, only one parameter is specified. But this technique does not solve the problem of lack of memory, which will be discussed below.
When migrating large infobases, a problem with running out of RAM may arise: when you try to unload, the program will end with a corresponding error message or without a message. Trying to replace your computer with a more powerful one is useless. In this case, you should upload the data in parts, breaking it into portions. This requires transfer rules that support the specified mode. Let's look at how to unload. Firstly, data transfer should be performed using only one upload rule (see Fig. 6.4). If the transfer is impossible according to one rule, then we divide it into parts, indicating the initial and final portion numbers. Each portion will contain information for a given number of first-level analytics values, for example, product balances, i.e. the specified number of account balance values “41”. Knowing the total amount of analytics for the account, it is easy to calculate the number of servings. How much data is transferred without problems at a time (into one piece of information) needs to be determined experimentally; as a rule, when uploading account balances, transfer problems appear when the number of balances is several thousand or more. Although, to save time for uploading data, we can recommend splitting it into parts, even if it is possible to upload all the balances in the accounting section at one time. The upload time depends on the size of the data portion, not proportionally, not linearly. Therefore, by dividing, for example, ten thousand product balances into ten parts of a thousand, you can reduce the unloading time by several times. If we are transferring the first portion, the number of the initial portion may not be indicated; if the last portion is transferred, then the number of the final portion may not be indicated.
IMPORTANT! When transferring data in parts, it is necessary to specify a postfix in the parameters, which is involved in the formation of the document comment “ Entering initial balances" When changing the portion range numbers, you must not forget to change the postfix, otherwise, when loading into the recipient Configuration, documents with the same comments (postfixes) will be overwritten. The name of the data file is not particularly important. You can use sequential transfer tactics: unload - load, unload - load, etc. In this case, the data file name does not need to be changed. You can choose a tactic: first unload everything, then load everything. In the latter case, the name of the data file will have to be changed each time it is uploaded. One more example. If the number of balances in the accounting section (for example, goods) is, say, 10,000, we divide it into parts of a thousand, then we get 10 portions. Each part must have a unique postfix: "-1", "-2", "-3", "-4". If we unload all remaining goods and then load everything, then the data files must also be unique, for example: “41_1”, “41_2”, “41_3”, “41_4”. The parameters “Portion number start” and “Portion number end” should take the following values: 0, 1000; 1001, 2000; 2001, 3000; 3001, 4000.
Data and important documents collected over years of hard work should not be lost just because a newer platform or 1C configuration has been released. To prevent this from happening, it is possible to transfer data.
Data transfer is one of the most critical parts of the transition from one configuration to another.
In order for the data to be transferred safe and sound, you need to entrust this work to professionals. Our team will complete all the work efficiently and on time.
Transfer stages
Data transfer consists of 5 stages. We tried to describe them as detailed and clear as possible.
Why is our data transfer better?
Typical data transfer cost
Maintenance of a new program
After all data has been transferred, you may need to maintain your program. We are ready to provide it to you!
Transition to 1C 8.2
Learn more about other stages of transition from one platform to another. License upgrade, configuration, training, support. Our specialists are ready to provide you with all the help you need!
Why are we better?
Order transfer
our team
Why is our 1C transfer better?
Before transferring 1C 8.2 directories and your other data, our specialists will tell you in detail about all stages of the work. By entrusting your database to us, you always know what is being done, in what order, and how much you pay for each stage of work.
Before proceeding directly to the transfer of 1C 7.7 to 1C 8.2, our specialists will conduct an in-depth analysis of your database. There is a high probability that the new version of 1C already has all the improvements that you needed. In any case, we will recommend what else you may need for comfortable work.
Before the most important stage of transfer, our specialists always carry out a trial transfer of 1C databases in order to identify possible errors, repetitions and data losses. But even after the transfer itself, we will definitely check everything for even greater confidence in its quality.
The work is considered completed only after you make sure that the transfer of 1C 8 directories and other data was carried out correctly and you are satisfied with the result. We don't abandon our clients!
Stage 1. General analysis of the source database
What work is being done:
For what:
After performing a general analysis of the source database, confirmation can be obtained that the data can be transferred using standard means; in this case, the further cost of the transfer service is determined according to the standard transfer price list, depending on the configuration.
If a correct standard transfer is not possible, then a proposal is prepared with the cost of work to finalize the configurations, exchange rules and non-standard transfer.
Price: 2,000 rub.
Stage 2. Preparation of technical documentation for non-standard transfer
What work is being done:
non-standard transfer procedures (if necessary).
For what:
If the specified set of technical documentation is not available, non-standard transfers between 1C configurations are carried out only on an hourly basis. In this case, it is impossible to accurately guarantee the cost and duration of the work in advance. However, in this case, some savings in time and costs for preparing a set of documentation are possible.
Price: To be determined based on the results of a general analysis of the source database.
Stage 3. Finalization of the receiver configuration
What work is being done:
For what:
updates by a service engineer.
Stage 4. Finalization of transfer rules
What work is being done:
For what:
Ensures correct transfer of data that is not transferred by standard exchange rules;
Modification of the transfer rules may also be required if the accounting in the source database was carried out incorrectly from the point of view of the methodology of the standard solution, although the source configuration may not have contained modifications.
Price: based on a set of technical documentation.
Stage 5. Data transfer
What work is being done:
For what:
You receive a ready-to-use new database with your current balances.
The transfer is carried out using transfer rules developed by 1C, with the use of modifications made specifically for the Customer. The composition of the transferred data may differ for different versions of configurations; our specialists will advise you on possible
transfer features.
