The Public Procurement Services Platform incorporates new fields to prepare for integration with the Public Contract Register
Share
This post is over 1 year old. Content may not be up to date.
On 22/05/2024, the following services were added to the Public Procurement Services Platform: eLicita a new version of the services that incorporates changes and new functionalities. At the end of this publication you can find the version's new features document with details of all the additions.
The main one is that the new fields detailed below are added to the Publication Manager forms, with the aim of preparing the functionality of integrating this tool with the Public Contracts Registry, which is planned to be implemented during the summer of 2024 and from which, those publications that contain all the necessary mandatory data, can be automatically sent to the RPC.
New fields and validations:
Type of supplies
BIM methodology (not mandatory for the local scope of the service)
Price review
Country of origin of the product
Linguistic clause
Ethics clause
Studies and opinions (not mandatory for the local scope of the service)
Social technical prescriptions
Environmental technical prescriptions
Unit price
Main CPV / secondary CPVs
Offers/Awarded companies/Contracting companies – Country
Other action execution – Identifier other action execution
Other performance execution – Identifier other contractual performance
Settlement – Contract evaluation report (not mandatory for the local scope of the service)
New rules for existing fields required for integration with RPC:
Mandatory field of Extension - Amount awarded
Mandatory field of Extension – VAT adjudication amount
Obligation of the Extension field – Extension start date
Compulsory field of Extension – Extension end date
Mandatory field Liquidation - Final price
Mandatory field Liquidation – Resolution date
It is not possible to overlap two extensions based on the start/end date of execution
The execution actions "Modification", "Extension" and "Other execution actions" must have a unique identifier
Settlement: The date of receipt must be less than or equal to the settlement date
Fields will initially be included in this release on a non-mandatory basis, to give time to third-party case managers who integrate with the PSCP, to make the necessary adaptations to add these fields to their applications, until, become mandatory in order to allow the transfer of data to RPC in a careless manner, to the next version 3.7, which is expected to be implemented during the summer of 2024.
These changes and the new integration will impact the current integration web services available for both tools, detailed below:
Aspects to take into account for entities that have developed integration with the PSCP from their recruitment file managers:
Integrators should take into account the integration document published in the post below that already adds these new fields and the detail of those that will have to be reported mandatorily.
Aspects to take into account for entities that have developed integration with the RPC from their hiring file managers.
Initially, the new integration services will coexist with the RPC, from the PSCP, and the web services of the RPC already existing, for third-party contracting managers. However, these directly integrated applications will receive a -1 error for those contracts that attempt to pass and have already been sent by the PSCP previously,
This error -1 may contain one of the messages below, which integrators must take into account to interpret correctly in order to keep the registration number in the RPC of the contracts that are already sent, and give these messages as vàlids from your system.
Contract Answer:
"There is a contract with the same file number, the existing registration number is (…)"
"A contract cannot be modified through the JCCA."
"A contract validated by the JCCA cannot be modified."
Settlement Response:
"The data of a settlement sent to the JCCA cannot be updated."
"The data of a settlement validated by the JCCA cannot be updated.
