- Electronic contracting
- Integration
Remember the discontinuity of the PSCP backward compatibility web services: end date 29/07/2024
On 22/05/2024, a new version of the services was added to the Public Procurement Services Platform and eLicita services that incorporates changes and new functionalities. At the end of this post you can find the new version document detailing all the additions.
The main of these is that the new fields detailed below are added to the forms of the Publications Manager, with the aim of preparing the integration functionality of this tool with the Public Register of Contracts, which is planned to be implemented during the summer of 2024 and from then on, those publications that contain all the required mandatory data can be sent automatically 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
- Tenders/Awarded companies/Contracting companies – Municipality
- Offers – Not open
- Tenders/Awarded companies/Contracting companies – Third sector
- Tenders/Awarded companies/Contracting companies – UTE – Company name
- Offers/Awarded companies/Contracting companies – UTE – Country
- Tenders/Awarded companies/Contracting companies – UTE – Municipality
- Extension – Identifier of the extension
- Extension – Has several types of VAT
- Extension – VAT percentage
- Extension – Amount awarded with VAT
- Extension – Identifier of the extension
- Modification – Identifier of the modification
- 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 existing field rules required for RPC integration:
- 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 the third-party file 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 the RPC in an unattended 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 be taken into account by entities that have developed integration with the RPC from their recruitment file managers.
Initially, the new integration services with the RPC, from the PSCP, and the existing RPC web services, for third-party hiring managers, will coexist. However, these directly integrated applications will receive a -1 error for those contracts that try to pass and have already been sent by the PSCP previously,
This error -1 may contain one of the messages below, which the integrators must take into account to interpret correctly in order to be able to keep the registration number in the RPC of the contracts that have already been sent, and give these messages as valid 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.
Check the details of these and other new features in the version at version 3.6 news document