1. Identification
| Parameter | Value |
|---|---|
| Object type | Catalog |
| Name | ВозвратТоваровМеждуОрганизациямиПрисоединенныеФайлы |
| Full name | Справочник.ВозвратТоваровМеждуОрганизациямиПрисоединенныеФайлы |
| Synonym | "Attached files (Return of goods between organizations)" |
| Configuration | Trade Management for Kazakhstan, edition 3.4 (3.4.5.21) |
| BSP subsystem | "File management" (Attached files) |
| Owner(s) | Документ.ВозвратТоваровМеждуОрганизациями |
| Hierarchy | No (flat list of files) |
Purpose. The catalog stores files attached to the "Return of goods between organizations" document: scans of return acts, invoices, claims, printed forms of ESF/SNT, attachments from electronic document workflow, etc. Each catalog item is a separate attached file (metadata + binary data or a reference to a storage volume) logically linked to a specific owner document. This is a service object: the user does not work with it directly, but through the "Attached files" command in the return document form.
Where to find: e1cib/list/Справочник.ВозвратТоваровМеждуОрганизациямиПрисоединенныеФайлы
(in standard workflow the list is opened from the owner document form, not from the main menu).
2. Header attributes and tabular sections
The structure is standard for BSP attached files. Below is the purpose of the fields.
Header attributes
| Attribute | Type | Purpose |
|---|---|---|
Наименование (Code/Description) |
String | File name without extension |
ВладелецФайла |
ДокументСсылка.ВозвратТоваровМеждуОрганизациями |
Reference to the document the file is attached to |
Расширение |
String | File extension (pdf, xml, jpg, docx…) |
Размер |
Number | File size in bytes |
Автор |
СправочникСсылка.Пользователи |
User who added the file |
ДатаСоздания |
Date | Moment the file was attached in the database |
УниверсальнаяДатаМодификации |
Date | Date of last modification (UTC) |
ТипХранилищаФайла |
Enumeration | Where the data is stored: "In the infobase" or "In volumes on disk" |
ХранилищеФайла |
ValueStorage | Binary file data (when stored in the infobase) |
Том |
СправочникСсылка.ТомаХраненияФайлов |
Storage volume (when stored on disk) |
ПутьКФайлуВТоме |
String | Relative path within the volume |
ТекстовоеХранилище |
ValueStorage | Extracted text for full-text search |
СтатусИзвлеченияТекста |
Enumeration | Not extracted / Extracted / Extraction error |
Зашифрован |
Boolean | Flag indicating content encryption |
ПодписанЭП |
Boolean | Flag indicating presence of an electronic signature |
РедактируетПользователь |
СправочникСсылка.Пользователи |
Who has "checked out" the file for editing (lock/capture) |
ПометкаУдаления |
Boolean | Standard deletion mark |
Tabular sections
| Tabular section | Key columns | Purpose |
|---|---|---|
ЭлектронныеПодписи |
Signature (ValueStorage), Certificate, IssuedTo, SignatureDate, Comment | Stores electronic signatures attached to the file |
ЗашифрованныеДанные (encryption certificates) |
Representation, Thumbprint, Certificate | Certificates used to encrypt the file |
The exact composition of BSP metadata attributes may differ slightly between releases — when making modifications, check against the configurator of the specific 3.4.5.21 build. This is the only truly version-specific point.
3. Forms
| Form | Purpose |
|---|---|
ФормаЭлемента |
Attached file card: name, author, size, dates, "View", "Edit", "Save as…" buttons, working with electronic signatures |
ФормаСписка |
List of owner's files (used inside the common "Attached files" form) |
Common form ПрисоединенныеФайлы (BSP) |
Main working form: list of the return document's files with commands to add, upload, download, sign, and print |
The user scenario is built on the common BSP form "ПрисоединенныеФайлы", which is parameterized by the owner (the return document) and operates on top of this catalog.
4. Key module procedures
No separate BSL code is included in the evidence, so below are the standard handlers for this type of object (implemented via calls to the BSP "File management" library):
Manager module / BSP common modules:
РаботаСФайламиСлужебный.ДобавитьФайл(...)— creates a new catalog item, writes binary data to the infobase or volume.РаботаСФайлами.ЗанятьФайл / ОсвободитьФайл(...)— checks out a file for editing (sets/clearsРедактируетПользователь).ОбновитьВерсию / ОбновитьДанныеФайла(...)— replaces content on re-upload.ПрисоединенныеФайлы.ПрисоединенныеФайлыВладельца(Владелец)— retrieves the list of files for a document.
Object module:
ПередЗаписью— checks whether the file is checked out, updatesУниверсальнаяДатаМодификации, synchronizes theЗашифрован/ПодписанЭПflags.ПередУдалением— deletes binary data from the volume when stored "on disk".ОбработкаЗаполнения— setsАвтор,ДатаСоздания,ВладелецФайлаon creation.
Form module:
- Commands
View,Edit,Finish editing,Save as,Sign,Encrypt/Decrypt— wrappers over the client proceduresРаботаСФайламиКлиент.
5. Posting and movements
The catalog is not posted and does not generate register movements — it is a subordinate storage catalog with no posting mode or transaction tabular section. Registers and transactions are generated by the owner document ВозвратТоваровМеждуОрганизациями; attached files merely accompany it as attachments (scans, ESF/SNT XML).
For context — what the owner document does under standard logic (Kazakhstan chart of accounts, VAT rate 16%, currency — tenge ₸):
Registers (management/operational accounting):
ТоварыОрганизаций,СвободныеОстатки— goods movement between organizations;СебестоимостьТоваров— cost adjustment for returned items;РасчетыМеждуОрганизациями— settlements between own legal entities;НДСПродажи/НДСПокупки— VAT accounting at a rate of 16%.
Journal entries (standard Kazakhstan chart of accounts):
| Operation | Debit | Credit |
|---|---|---|
| Recording returned goods | 1330 (goods) | 3310 (payables to supplier-organization) |
| VAT on return (16%) | 1420 / reversal 3130 | 3310 |
| Settlements between organizations | 1210 / 3310 | 3310 / 1210 |
| Reversal of income/cost on sales return | 6010 (income), 7010 (cost) — reversing entries | 1210 / 1330 |
| Payment/offset in cash | 3310 | 1030 (current accounts) |
VAT example. For a return in the amount of 1,000,000 ₸ (excluding VAT), the VAT amount at 16% = 160,000 ₸, total document amount = 1,160,000 ₸. On the ESF side, a corrected/additional invoice is generated in the ESF information system; when goods are moved, an SNT is issued.
6. Related objects and entry based on
- Owner:
Документ.ВозвратТоваровМеждуОрганизациями— the only source of items. - Similar attached files catalogs of other documents (sales, receipts, transfers) — same BSP mechanics.
Справочник.Пользователи— file authors and lockers.Справочник.ТомаХраненияФайлов— volumes when stored "on disk".- Information register
ДвоичныеДанныеФайлов/ВерсииФайлов(depending on the storage scheme) — binary data. - Electronic documents: ESF XML (ESF information system) and SNT, received/generated for the owner document, are often stored precisely as attached files.
Entry based on: not applicable for the attached files catalog. Items are created only via the "Attached files" command from the return document form (add/upload/scan).
7. Extension points
- Configuration extension: adding handlers to the item/list form module and to the common form
ПрисоединенныеФайлы(e.g., automatic classification of attachments by extension). - BSP programming interfaces:
РаботаСФайлами,РаботаСФайламиКлиент,ПрисоединенныеФайлы— standard API for adding/reading files without working directly with the catalog. - Additional attributes and information ("Properties" subsystem) — if needed, to mark the attachment type (act, claim, ESF, SNT).
- Access restriction (RLS): permissions are inherited from the owner document — when customizing access restrictions, configure them by owner.
- Event subscriptions
ПередЗаписью/ПередУдалениемof the object — for logging or integration with an external document archive.
