Control of inventory in systems 1C
By this article, the author would like to raise the issue of the weak points of the typical 1C “SCP, UT, Complex” systems, methods of eliminating them, and determine the interest of the audience in the problem as a whole.
The first of these addresses the issue of “control of commodity balances”.
How the system controls the excess residue.
In the terminology of 1C, there are two types of conducting documents Operational and Non- operational implementation.
The operational mode of conducting means that the fact of a business transaction is recorded at the current time and the non- operational mode means that the business operation is reflected in the past, even a second ago from the current time.
I will not reveal the big secret that, in the ideology of typical configurations of 1C programs, it is not considered necessary to check the goods in non- operational mode.
I will not be given right now in the reasons for the lack of full-fledged mechanisms for controlling residues in early versions of systems, I will only note the fact that controlling residues only in operational mode is not very suitable for real workflow. Often documents are made as they are received and usually backdating.
How it works.
In my article, as a basic configuration, I will consider the SCP (management of a manufacturing enterprise) since it contains the largest number of subsystems. The presented method is also suitable for other 1C systems in which there is a register of “Free residuals”.
The system contains demo data and the “Free balances” control mechanism is enabled.
It is a little about the register Free Remains .
This register appeared in the SCP not so long ago and its appearance is due to the need to consolidate data on commodity balances in one place; it also separated commodity balances from the party registers due to the strategic promotion of RUAZ (extended cost analytics) where the lots were not used.
In the further development of the entire control of commodity balances is based on it.
')
But back in our problem. Having conducted several documents in the past period with a deliberately inflated amount, it can be found that the system does not respond to exceedances.
Let's see what really happens.
For all system documents in the posting module, there is a processing residue control block. Usually it looks like this:
All is well. Control seems to be there. But falling into the implementation ( F12 key). We see all that is written above. The system only controls the operating balance.
The system without control skips most of the documents that were acquired in the past period. It would be logical to report data errors at the time of its occurrence, when the operator has a primary document on his hands, and not at the time of closing the month, when documents in the archive and to find out the truth is not possible.
Every time starting a completely different project, the first thing that had to close this particular gap in the control of residues. Only this one action can significantly improve the quality of system data and its usefulness in general.
We supplement the non-operational processing.
Now for the good news.
There is no need to refine anything. All improvements are reduced to 4 lines.
1. Block the exit from the procedure if the conduct is not operational.
2. Add a parameter to the request that determines which date we want to receive the balances.
3. Additionally, we pass this parameter to the request.
We are checking.
Let's form a document in the past period and make sure that the system blocks its implementation when the excess balance is exceeded. Additionally, we use the report "Analysis of the availability of goods in warehouses."
Findings.
This article covers one of the methods for improving typical 1C systems. It is told about the methods of holding documents and their features. It is shown how a few strokes can significantly improve the quality of system data.
Thanks for attention.
PS The solution proposed by the author is characterized by simplicity and accessibility, but does not claim to be 100 percent guaranteed as in the following articles.
The first of these addresses the issue of “control of commodity balances”.
How the system controls the excess residue.
In the terminology of 1C, there are two types of conducting documents Operational and Non- operational implementation.
The operational mode of conducting means that the fact of a business transaction is recorded at the current time and the non- operational mode means that the business operation is reflected in the past, even a second ago from the current time.
I will not reveal the big secret that, in the ideology of typical configurations of 1C programs, it is not considered necessary to check the goods in non- operational mode.
I will not be given right now in the reasons for the lack of full-fledged mechanisms for controlling residues in early versions of systems, I will only note the fact that controlling residues only in operational mode is not very suitable for real workflow. Often documents are made as they are received and usually backdating.
How it works.
In my article, as a basic configuration, I will consider the SCP (management of a manufacturing enterprise) since it contains the largest number of subsystems. The presented method is also suitable for other 1C systems in which there is a register of “Free residuals”.
The system contains demo data and the “Free balances” control mechanism is enabled.
It is a little about the register Free Remains .
This register appeared in the SCP not so long ago and its appearance is due to the need to consolidate data on commodity balances in one place; it also separated commodity balances from the party registers due to the strategic promotion of RUAZ (extended cost analytics) where the lots were not used.
In the further development of the entire control of commodity balances is based on it.
')
But back in our problem. Having conducted several documents in the past period with a deliberately inflated amount, it can be found that the system does not respond to exceedances.
Let's see what really happens.
For all system documents in the posting module, there is a processing residue control block. Usually it looks like this:
All is well. Control seems to be there. But falling into the implementation ( F12 key). We see all that is written above. The system only controls the operating balance.
The system without control skips most of the documents that were acquired in the past period. It would be logical to report data errors at the time of its occurrence, when the operator has a primary document on his hands, and not at the time of closing the month, when documents in the archive and to find out the truth is not possible.
Every time starting a completely different project, the first thing that had to close this particular gap in the control of residues. Only this one action can significantly improve the quality of system data and its usefulness in general.
We supplement the non-operational processing.
Now for the good news.
There is no need to refine anything. All improvements are reduced to 4 lines.
1. Block the exit from the procedure if the conduct is not operational.
// <> . // ; //; 2. Add a parameter to the request that determines which date we want to receive the balances.
| ..(&, 3. Additionally, we pass this parameter to the request.
.("", ?(=.,(), (..(),.))); We are checking.
Let's form a document in the past period and make sure that the system blocks its implementation when the excess balance is exceeded. Additionally, we use the report "Analysis of the availability of goods in warehouses."
Findings.
This article covers one of the methods for improving typical 1C systems. It is told about the methods of holding documents and their features. It is shown how a few strokes can significantly improve the quality of system data.
Thanks for attention.
PS The solution proposed by the author is characterized by simplicity and accessibility, but does not claim to be 100 percent guaranteed as in the following articles.
Source: https://habr.com/ru/post/174673/
All Articles