1. Identification of the object
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | VirtualWarehousesOfCounterparty |
| Full Name | Catalog.VirtualWarehousesOfCounterparty |
| Synonym | not set (—) |
| Configuration | Accounting for Kazakhstan, ed. 3.0.74.2 |
| Country of Accounting | Republic of Kazakhstan, currency — tenge (₸) |
| Navigation Link | e1cib/list/Catalog.VirtualWarehousesOfCounterparty |
Purpose. The catalog stores a list of virtual (remote) warehouses owned by the counterparties of the organization. It is used in logistics and trade scenarios of electronic document flow in Kazakhstan: when issuing electronic invoices (ESF) and accompanying invoices (SNT), it is necessary to specify the counterparty's warehouse identified in its external system. Each virtual warehouse receives a unique numerical identifier (id), under which it is known in the counterparty's external system, ensuring correct API integration and matching of warehouses during data exchange.
Where to find in 1C: section “Sales” → “Virtual Warehouses of Counterparties”; or through the command “Update Virtual Warehouses” in the data retrieval wizard. Direct navigation — via the link e1cib/list/Catalog.VirtualWarehousesOfCounterparty.
2. Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| Name (standard) | String | Mandatory | The name of the virtual warehouse, displayed in lists and selection forms. Standard attribute of the catalog. |
| Counterparty | CatalogReference.Counterparties | Mandatory (ShowError) |
The counterparty-owner of the virtual warehouse. The record cannot be saved without filling this field — control at the level of filling verification. |
| WarehouseIdentifier | Number (xs:decimal) |
Optional (DontCheck) |
Unique numerical identifier (id) of the warehouse in the counterparty's external system. Key for matching during API integration and exchange of ESF/SNT. |
| Address | String (xs:string) |
Optional (DontCheck) |
Physical address of the counterparty's warehouse. Informational field, used for display in documents and printed forms. |
| Status | EnumerationReference | Optional (DontCheck) |
Status of the warehouse's activity (e.g., “Active” / “Blocked”). Affects the ability to select the warehouse in documents: blocked warehouses are filtered out. |
2.2 Table Parts
There are no table parts. All data is stored in header attributes — the catalog is flat, one record = one virtual warehouse of one counterparty.
3. Forms
| Form | Role | Composition/features |
|---|---|---|
| ListForm | Main form for the list of warehouses | ~41 control elements. Contains commands for working with the data retrieval wizard and setting the main warehouse. |
| ElementForm ⭐ | Creation/editing of a single warehouse | ~27 elements. Input fields: Name, Address, Counterparty, WarehouseIdentifier. Key form for manual maintenance. |
| SelectionForm | Selecting a warehouse from the list | ~37 elements. Supports filtering by Status and Counterparty, contains a command to call the wizard. Invoked from documents when selecting the counterparty's warehouse. |
4. Key Procedures of Modules
The application BSL code in evidence is not attached, so below is a typical set of handlers for a catalog of this purpose (integration). Specific lines/names are clarified according to the configurator of this assembly.
Object Module (FillingVerificationProcessing)
- Control of the mandatory attribute Counterparty (
ShowError): if the counterparty is not filled, the record is rejected with a message to the user. - Attributes
Address,WarehouseIdentifier,Statusare excluded from verification (DontCheck).
Object Module (BeforeSaving)
- Normalization/checking the uniqueness of
WarehouseIdentifierin the context of the counterparty (to prevent the same externalidfrom being duplicated during exchange).
Element Form Module
OnCreationOnServer— initial setup of field availability and setting the default status.- Handlers for changing
Counterparty— resetting filtering and clearing/recalculating dependent fields.
List/Selection Form Module
- Command “Update Virtual Warehouses” — launching the data retrieval wizard: calling the counterparty's API, loading the list of warehouses and their identifiers, creating/updating catalog elements.
- Command for setting the main warehouse — marking the warehouse to be used by default in documents.
- Setting filters for the selection form by
StatusandCounterparty.
Requires verification (version-specific): the exact protocol/address of the data retrieval wizard's API and the algorithm for deduplicating warehouses may differ between assemblies 3.0.7x.
5. Posting and Movements
The catalog is not posted and does not independently generate movements in registers and accounting entries — it is normative-reference information (NRI). Records create/change movements only indirectly, as analytics in documents where the counterparty's warehouse is specified.
Data from the catalog is used in sales/purchase documents and electronic document flow (ESF/SNT). When posting such documents, standard movements for the RK are formed (accounts — according to the typical chart of accounts of the RK, VAT rate 16%):
Example: sale of goods with issuance of ESF (tenge)
| Dr | Cr | Content |
|---|---|---|
| 1210 | 6010 | Reflected receivables from the buyer and income from sales (excluding VAT) |
| 1210 | 3130 | VAT on sales, 16% (to be paid) |
| 7010 | 1330 | Cost of goods sold written off |
Example: receipt/payment (tenge)
| Dr | Cr | Content |
|---|---|---|
| 1330 | 3310 | Receipt of goods, payables to the supplier |
| 3310 | 1030 | Payment to the supplier from the current account |
The virtual warehouse of the counterparty acts as analytics/attribute of the electronic document (SNT/ESF) and is included in the XML export to the ESF IS by its WarehouseIdentifier; it does not affect the composition of entries.
6. Related Objects and Input Based On
- Catalog.Counterparties — owner of the virtual warehouse (attribute
Counterparty). - Documents ESF and SNT — consumers of the catalog: the counterparty's warehouse is specified when issuing electronic documents and is transmitted to external systems by
WarehouseIdentifier. - Data Retrieval Wizard (“Update Virtual Warehouses”) — source of automatic filling of the catalog through the counterparty's API.
- Enumeration of statuses — source of values for the
Statusattribute.
Input Based On. As a source for input based on, the catalog is generally not used. Filling is performed manually (ElementForm) or automatically through the data retrieval wizard/API exchange.
7. Extension Points
- Configuration Extension: adding attributes (e.g., region code, warehouse type, validity period), adding custom commands in ListForm/SelectionForm, overriding
FillingVerificationProcessingandBeforeSavingthrough extension handlers. - Event Subscriptions:
BeforeSaving/OnSavingof the catalog — for logging changes or cascading synchronization with an external system. - Integration: refinement of the data retrieval wizard for a specific counterparty API; matching external
idduring loading; deduplication by the pair “Counterparty + WarehouseIdentifier.” - Filters for selection forms: programmatic addition of filters (by region, main warehouse indicator) for selection in ESF/SNT documents.
- Additional attributes and information (BSP mechanism) — if it is necessary to expand the card without changing the configuration.