--- title: "Processing \"Warehouse Topology Generation\" (DataProcessors.ГенерацияТопологииСклада)" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-23 canonical: https://buhgpt.kz/suraqtar/obrabotka-generaciya-topologii-sklada-dataprocessors-gene-en source: BuhGPT --- # Processing "Warehouse Topology Generation" (DataProcessors.ГенерацияТопологииСклада) > **TL;DR:** 1. Identification Parameter Value Object type Data processor (DataProcessor) Name WarehouseTopologyGeneration Full name DataProcessors.WarehouseTopologyGeneration ( Обработка.ГенерацияТопологииСклада ) Synonym "Warehouse Topology Generation" Configuration Trade Management for --- 1. Identification Parameter Value Object type Data processor (DataProcessor) Name WarehouseTopologyGeneration Full name DataProcessors.WarehouseTopologyGeneration (Обработка.ГенерацияТопологииСклада) Synonym "Warehouse Topology Generation" Configuration Trade Management for Kazakhstan, ed. 3.4.5.21 Subsystem Service subsystems Navigation link e1cib/list/Обработка.ГенерацияТопологииСклада Purpose Mass (batch) creation and population of the address topology of an order-based warehouse: work areas, rooms (zones), rows, racks, tiers and storage bins according to specified generation parameters Object class. This is a service (utility) data processor. It is not a document, is not posted, and does not generate accounting entries. Its purpose is to quickly deploy the hierarchy of warehouse address storage so that hundreds of bins do not need to be created manually. The result of its work is records in the catalogs and information registers of the "Warehouse" subsystem (address/order-based storage). Where to find it in 1C. The "Service subsystems" section → "Warehouse Topology Generation". If the data processor is not present in the command interface, use the direct navigation link e1cib/list/Обработка.ГенерацияТопологииСклада (File → Open by link / "Go to link" field). 2. Attributes and tabular sections The exact composition of attributes is version-specific and is not disclosed in the attached evidence. Below is the typical set of fields for UT/KA address topology generation data processors; verify the actual set in Designer (Attributes/Tabular sections of the data processor). 2.1. Form attributes (header / generation parameters) Attribute Type Purpose Warehouse CatalogRef.Warehouses Target warehouse (order-based, with address storage) for which the topology is generated Room / WorkArea CatalogRef.WarehouseRooms Room (storage zone) within which the bin grid is created AddressPrefix / Template String Template for generating the bin's code and name (e.g., A-{Row}-{Rack}-{Tier} → A-01-05-03) NumberOfRows Number Number of aisles/rows NumberOfRacks (sections per row) Number Number of racks (sections) in one row NumberOfTiers (shelves) Number Number of tiers (levels) vertically NumberOfBinsPerSection Number Number of positions by depth/width of a section PickingPlacementType Enumeration Scope of application of the bin: picking, placement, universal VolumeUnitOfMeasure / Dimensions Reference/Number Bin restrictions by volume/weight/dimensions (if weight-and-dimension accounting is maintained) ClearExisting Boolean Flag for pre-clearing previously generated topology 2.2. Tabular section "GenerationParameters" (result preview) Column Type Purpose Code String Bin code generated according to the template Name String Readable name (address) of the bin Row / Rack / Tier / Position Number Bin coordinates in the topology Room CatalogRef.WarehouseRooms Parent room Create Boolean Flag to include the row in the batch write The tabular section is used as a preview buffer: the user generates the list of bins "in memory", reviews it, clears the flags for unwanted rows, and only then starts writing to the information base. 3. Forms Form Purpose Form (main data processor form) Single working form: input of generation parameters, "Generate" button (fill the preview) and "Write/Create bins" button (batch object write), result preview table SettingsForm (optional) Advanced settings for the coding template, numbering rules, and weight-and-dimension restrictions If only one form is present in a particular delivery, all the logic (parameters + preview + write) is concentrated in it. 4. Key module procedures The attached evidence does not provide the source BSL code (paths path:line), so below is a typical set of handlers for a data processor of this purpose. Verify the names against the form module / object module of the specific delivery. Procedure/function Location What it does OnOpenAtServer / OnOpen Form module Initializes default values (address template, unit of measure), substitutes the warehouse from context Generate(Command) Form module, &AtClient Preview button handler: calls the server procedure that populates the table GenerateAtServer() Form module, &AtServer Uses nested loops over rows/racks/tiers/positions to build preview rows, generating code and name according to the template GenerateBinCode(Parameters) Form module / common module Builds the code according to the template, pads numbers with leading zeros, checks uniqueness CreateBins(Command) → CreateBinsAtServer() Form module Batch-creates Catalog.WarehouseBins objects (and, if needed, WarehouseRooms), writes the address storage registers within a transaction CheckFilling() Form/object module Validates the correctness of parameters (warehouse with address storage, positive quantities, non-empty template) ClearTopology() Form/object module Optional deletion/marking for deletion of previously created bins of the specified room Standard "DataProcessor"-type handlers that may be present: FillingProcessing, ExternalDataProcessorInfo() (for the variant of a pluggable external BSP data processor with the type "Object filling"/"Additional processing"). 5. Written objects and movements The data processor does not perform posting and does not generate accounting entries — it is not a document. It modifies the catalog and register structure of the warehouse: Write object What is written Catalog.WarehouseBins (Warehouse bins) New items — generated bins with code, name (address), coordinates, usage type Catalog.WarehouseRooms If needed — created rooms/work areas Information registers of address storage (e.g. ItemPlacementByBins, bin weight-and-dimension restrictions) Applicability flags for bins for picking/placement, volume/weight restrictions Impact on accounting (indirect). The generated topology is used by subsequent order-based and warehouse documents (goods receipt order, goods expense order, picking, placement, bin-to-bin movement). It is these documents, not this data processor, that generate movements in item accounting. For context — typical Kazakhstan accounts affected by warehouse item operations via documents (not by this data processor): Account Purpose 1330 Goods (warehouse item accounting) 1210 Short-term receivables from customers 1030 Cash on current bank accounts 3310 Short-term payables to suppliers 3130 VAT payable (Kazakhstan VAT rate 2026 — 16%) 6010 Sales revenue 7010 Cost of sales Kazakhstan numerical standards for 2026 (for reference when configuring related functionality): MCI = 4,325 ₸, minimum wage = 85,000 ₸; VAT 16%; individual income tax 10% (up to 8,500 MCI of annual income) / 15% above that; standard individual income tax deduction — 30 MCI per month, but no more than 360 MCI per year; mandatory pension contributions 10% (base cap 50 minimum wages), employer's mandatory pension contributions 3.5%, mandatory social health insurance contributions (employee) 2%, mandatory social health insurance contributions (employer) 3%, social contributions 5%, social tax 6%. Kazakhstan electronic documents: ESF (electronic invoice, ESF IS), SNT (goods consignment note). Currency — tenge (₸). These standards do not directly apply to this topology generation data processor. 6. Related objects and entering on the basis of Relation Object Role Context source Catalog.Warehouses Target warehouse (must have the order-based/address storage flag) Result Catalog.WarehouseBins Main object created Result Catalog.WarehouseRooms Storage zones/rooms Topology consumers Order-based documents: GoodsReceiptOrder, GoodsExpenseOrder, ItemPicking, ItemPlacement, ItemMovement Use the created bins as storage/operation addresses Entering on the basis of. As a service data processor, the object does not participate in the "Enter on the basis of" mechanism (it is neither a basis nor a result of entering on the basis of) and is not registered in document filter criteria. 7. Extension points - Configuration extension — the procedures GenerateAtServer() and CreateBinsAtServer() can be overridden/extended for non-standard address coding rules or additional filling of bin attributes. - Coding template — extract code generation into a separate function/parameter to support a corporate addressing standard without modifying the generation loop. - External BSP data processor — when delivered as an additional/external data processor, the function ExternalDataProcessorInfo() is implemented; connected via "Additional reports and data processors". - Event subscriptions — when batch-writing bins, take into account subscriptions to BeforeWrite/OnWrite of the WarehouseBins catalog; for large volumes, write within a transaction in batches. - Access rights restriction (RLS) — access to the data processor and the created bins is governed by the roles of the "Warehouse" subsystem. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_