Exchange interfaces
Data migration
Data migration makes it possible to import data held in a CSV file into the software. The migration can also be carried out in XML format, or through an ETL calling the REST services or web services natively available in beCPG.
WEB/REST services
As standard, beCPG offers an HTTP REST service called the Remote API, which makes it possible to:
- import the data of an entity in XML format,
- export the data of an entity in XML format according to criteria (e.g. I want every product that is validated and effective on the date DD/MM/YYYY).
This REST service is used to build interfaces with third-party software such as an ERP. An entity means a product, a customer, a supplier, a project, and so on, together with all of its information, and this dynamically, without any development. The exchange interface can therefore be handled by a third-party tool whose role is to:
- drive the exchanges,
- transform the flows (transformation rules on value lists, for instance),
- handle the errors.
This third-party tool talks to the Remote API to import and export beCPG data. Two approaches are possible:
- the customer already owns a third-party tool able to build the interface,
- the customer wants beCPG to set up a third-party tool to build the interface.
Beyond that, every API of the application is reachable through REST services:
- CRUD operations — Create/Read/Update/Delete
- formulation
- document generation
- retrieval of versions and technical data sheets
- and so on.
CSV connector
A CSV connector exports data through CSV files. It lets you configure the data to export, and transformation rules can be set up in a "Mapping". It is also possible to develop a specific connector to take particular business rules into account and to send the data in a specific format.
GDSN interface
The data entered in the PLM can automatically feed a GDSN catalogue, for example the Equadis software.
Salsify interface
The Salsify SupplierXM platform (formerly Alkemics) can be fed by a connector.