← Implemented Projects

14 / Integrations

BAS data in external databases and files

Custom import and export routines for agreed data sets including products, customers, sales and other operational information.

MSSQLPostgreSQLData exchangeFiles
Discuss integration with your system ↗

Conceptual illustration. See the interaction diagram for data scope and directions.

The task

BAS ↔ MSSQL / PostgreSQL

External systems need defined accounting data sets and transfer directions.

Interaction diagram

BAS ↔ MSSQL / PostgreSQL

BASComponents and data directions in the described implementation.Data for exportData for exportData forexportAgreed importAgreed importAgreed importConnection and exchangeConnection and exchangeConnectionand exchangeConnection and exchangeConnection and exchangeConnectionand exchangeTable exportTable exportTable exportBASBASBAS1Custom routinesCustom routinesCustom routines2MSSQLMSSQLMSSQL3PostgreSQLPostgreSQLPostgreSQL4File exportFile exportFile export5BASComponents and data directions in the described implementation.Data for export1Agreed import2Connection and exchange3Connection and exchange4Table export5BASBASBAS1Custom routinesCustom routinesCustom routines2MSSQLMSSQLMSSQL3PostgreSQLPostgreSQLPostgreSQL4File exportFile exportFile export5
Selected connectionBAS → Custom routines

Data for export

Architecture

Technical description

Custom routines connect BAS to external databases and file-based outputs. Import and export scenarios are separate, with data and direction specified for each database task.

Data scope

Agreed product, customer, sales, delivery-location and marketplace data. A separate routine prepares tables for file export.

Our implementation

MSSQL and PostgreSQL connections, table preparation and exchange of defined data sets. The diagram does not imply complete database replication or direct editing of internal BAS tables.

Requirements for a new project

Define the source of each entity, mappings and output format. Change data capture, all-table synchronisation and a data warehouse require separate scope.

What we developed

Custom database and file-exchange routines

  1. Developed connections to MSSQL and PostgreSQL.
  2. Implemented exchange of products, customers, sales, delivery locations and marketplace data.
  3. Created table preparation and export workflows, including file-based exchange.

Implementation result

Implementation result

External systems receive agreed accounting data through separately developed import and export workflows.

Discuss your task ↗

Related projects

NEXT STEP

Discuss your task

Describe your current system, task and intended result. We will agree the scope and prepare a proposal.

[email protected] ↗Contact us on Telegram ↗Vyvick Engineering on Telegram ↗
Company and preferred timing — optional

Enquiries and personal data