--- title: "Catalog \"Warehouses\" (Catalogs.Warehouses) — Technical Description" country: KZ lang: en author: Сапа Т.И. (https://buhgpt.kz/authors/sapa-ti) date: 2026-09-07 canonical: https://buhgpt.kz/suraqtar/spravochnik-sklady-catalogs-sklady-tehnicheskoe-opisanie-en source: BuhGPT --- # Catalog "Warehouses" (Catalogs.Warehouses) — Technical Description > **TL;DR:** 1. Identification Parameter Value Object Type Catalog Name Warehouses Full Name Catalog.Warehouses ( Catalogs.Warehouses ) Synonym Warehouses (storage locations) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Hierarchy Hierarchical (groups and items) Wh --- 1. Identification Parameter Value Object Type Catalog Name Warehouses Full Name Catalog.Warehouses (Catalogs.Warehouses) Synonym Warehouses (storage locations) Configuration Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 Hierarchy Hierarchical (groups and items) Where to find Section "Nomenclature and Warehouse" → "Warehouses" Navigation Link e1cib/list/Catalog.Warehouses Purpose. The catalog maintains a classifier of storage locations for the organization's material assets. It is used in all documents for receipt, transfer, sale, and write-off of goods, materials, and finished products. It supports a hierarchical structure, a mechanism for additional attributes (subsystem "Property Management"), and user-specific default settings. The catalog is critical for warehouse accounting: the system automatically manages the functional option "Use multiple warehouses" depending on the number of catalog items — if there is more than one warehouse, the "Warehouse" field becomes available in documents and reports. 2. Attributes of Headers and Table Parts 2.1 Header Attributes Name Type Mandatory Purpose Name String Mandatory (standard attribute) Name of the warehouse (storage location). Code String/Number Auto-numbering Unique code of the catalog item. Parent CatalogReference.Warehouses Not checked Owner group in the warehouse hierarchy. ResponsiblePerson CatalogReference (individual/employee) Not checked Materially responsible person for the warehouse; substituted in documents and printed forms. Prefix String Not checked Document numbering prefix for documents created for this warehouse; automatically substituted in the numbers of invoices and acts when the warehouse is selected. Comment String Not checked Arbitrary explanation for the warehouse (address, area of responsibility, storage features), visible to users. 2.2 Table Parts AdditionalAttributes Purpose: storage of additional user attributes for the warehouse, configurable through the "Property Management" subsystem. Name Type Purpose Property PlanTypesOfCharacteristics.AdditionalAttributesAndInformation Reference to the definition of the additional attribute (type, name, format). Value Arbitrary Actual value of the additional attribute for this warehouse (type depends on the property settings). TextString String Text representation of the value for display in the interface (for complex types). 3. Forms Form Purpose ElementForm Main form for editing the warehouse item. Fields: Parent, Name, ResponsiblePerson, Code, Prefix, Comment, "History" button (view object versions). GroupForm Form for editing the group of warehouses. Fields: Parent, Name, Code. ListForm List of warehouses with support for bulk attribute modification (button "ModifySelected"). SelectForm Modal window for selecting a warehouse to fill in document attributes. SelectGroupForm Select group of warehouses (used in report and processing settings). 4. Key Procedures of Modules The attached evidence does not include the program code (BSL) of the modules — below are the typical handlers characteristic of a catalog of this type in a BSP-compatible configuration. Exact signatures and the presence of handlers require verification in the specific build 3.0.74.2. Object Module (Catalog.Warehouses.ObjectModule): - FillProcessing(FillData, FillText, StandardProcessing) — filling in default values upon creation. - BeforeSaving(Refusal) — data validity control before saving. - OnSaving(Refusal) — updating the functional option "Use multiple warehouses": when a second item appears, the option is enabled. - BeforeDeleting(Refusal) — checking the warehouse usage in documents; if necessary, disabling the functional option. Form Modules: - ElementForm.OnCreateOnServer — setting field visibility, connecting the additional attributes mechanism (PropertyManagement), initializing the versioning subsystem (button "History"). - ElementForm.OnReadOnServer / AfterSavingOnServer — updating additional attributes. - ListForm.ModifySelected — calling the bulk attribute modification processing. - SelectForm.SelectionProcessing — returning the selected warehouse to the calling document. 5. Posting and Movements The "Warehouses" catalog does not independently generate postings and movements in registers — it is an object of normative reference information. It serves as analytics (subaccount/dimension) in movements that generate goods movement documents. Typical participation of the warehouse in accounting logic (chart of accounts of the RK, VAT rate 16%, currency — tenge ₸): Receipt of material assets to the warehouse (document "Receipt of Goods and Services"): Dr Cr Content 1330 "Goods" 3310 "Accounts Payable" Receipt of goods into the warehouse (analytics: warehouse, nomenclature) 1420 "VAT to be Reimbursed" 3310 Incoming VAT 16% Sale from the warehouse (document "Sale of Goods and Services"): Dr Cr Content 1210 "Short-term Accounts Receivable" 6010 "Revenue from Sales" Revenue 1210 3130 "VAT Payable" VAT 16% from sales 7010 "Cost of Goods Sold" 1330 "Goods" Write-off of the cost of goods from the warehouse Payment from the customer: Dr 1030 "Cash in Current Accounts" — Cr 1210. Registers where the warehouse is a dimension: - GoodsInWarehouses (accumulation register, balances) — quantitative and monetary accounting of balances by warehouse and nomenclature. - Accounting registers (postings for accounts 1330 and others) — warehouse as a subaccount for inventory accounts. Electronic documents of the RK. The warehouse participates in the formation of electronic invoices (ESF) and accompanying invoices for goods (SNT) as a place of shipment/receipt during the posting of sale and transfer documents. 6. Related Objects and Input Based On Documents using the "Warehouse" attribute as analytics: - Receipt of Goods and Services - Sale of Goods and Services - Transfer of Goods (sending warehouse / receiving warehouse) - Receipt / Write-off of Goods - Inventory of Goods - Production Reports for the Shift, Requirement-Invoice Related Objects: - PlanTypesOfCharacteristics.AdditionalAttributesAndInformation — definitions of additional attributes. - Register of personal settings — "Main Warehouse" of the user. - Catalogs "Organizations", "Nomenclature", individuals/employees (responsible person). Input Based On. For the "Warehouses" catalog, typical input based on is usually not provided — the warehouse is selected as an attribute in documents, rather than serving as the basis for their creation. 7. Extension Points - Additional attributes and information — extending the composition of warehouse attributes without changing the configuration (subsystem "Property Management"). - Configuration extensions (adapters) — adding attributes, changing forms, connecting handlers without removing from support. - Event subscriptions (BeforeSaving, OnSaving) — integration and synchronization with external systems (WMS, data exchange). - Additional processing/reports (BSP) — contextual commands on list and element forms. - Functional option "Use multiple warehouses" — control point for document and report behavior depending on the number of warehouses. --- _BuhGPT — ИИ-помощник для бухгалтеров Казахстана: https://buhgpt.kz_