error on changeNotice Notice Subtype 4 #508

rengit62 · 2023-06-06T13:58:59Z

rengit62
Jun 6, 2023

Hi Labs !
I tried to make my first change notice on subtype 4, the notice is CVS valid but when I submit it I got the error :
A notice with the same id and version id already exists.

As it is my first change notice I surely made an error but from the message I cannot understand which error , here the notice :

<?xml version="1.0" encoding="UTF-8"?>
<PriorInformationNotice xmlns="urn:oasis:names:specification:ubl:schema:xsd:PriorInformationNotice-2" xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2" xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2" xmlns:efac="http://data.europa.eu/p27/eforms-ubl-extension-aggregate-components/1" xmlns:efbc="http://data.europa.eu/p27/eforms-ubl-extension-basic-components/1" xmlns:efext="http://data.europa.eu/p27/eforms-ubl-extensions/1" xmlns:ext="urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2">
	<ext:UBLExtensions>
		<ext:UBLExtension>
			<ext:ExtensionContent>
				<efext:EformsExtension>
					<efac:Changes>
						<efbc:ChangedNoticeIdentifier>eeecf7d8-843a-4294-b7e8-4835e2161386-05</efbc:ChangedNoticeIdentifier>
						<efac:Change>
							<efbc:ProcurementDocumentsChangeDate>2023-06-22+02:00</efbc:ProcurementDocumentsChangeDate>
						</efac:Change>
						<efac:ChangeReason>
							<cbc:ReasonCode listName="change-corrig-justification">cor-buy</cbc:ReasonCode>
							<efbc:ReasonDescription languageID="ENG">HO UNA OTTIMA RAGIONE DI CAMBIARE</efbc:ReasonDescription>
						</efac:ChangeReason>
					</efac:Changes>
					<efac:NoticeSubType>
						<cbc:SubTypeCode listName="notice-subtype">4</cbc:SubTypeCode>
					</efac:NoticeSubType>
					<efac:Organizations>
						<efac:Organization>
							<efbc:GroupLeadIndicator>true</efbc:GroupLeadIndicator>
							<efac:Company>
								<cac:PartyIdentification>
									<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
								</cac:PartyIdentification>
								<cac:PartyName>
									<cbc:Name languageID="ENG">Buyer organization</cbc:Name>
								</cac:PartyName>
								<cac:PostalAddress>
									<cbc:Department>Reparto racchette da tennis</cbc:Department>
									<cbc:CityName>COMO</cbc:CityName>
									<cac:Country>
										<cbc:IdentificationCode listName="country">AUT</cbc:IdentificationCode>
									</cac:Country>
								</cac:PostalAddress>
								<cac:PartyLegalEntity>
									<cbc:CompanyID>1</cbc:CompanyID>
								</cac:PartyLegalEntity>
								<cac:Contact>
									<cbc:Telephone>051333</cbc:Telephone>
									<cbc:ElectronicMail>[email protected]</cbc:ElectronicMail>
								</cac:Contact>
							</efac:Company>
							<efac:TouchPoint>
								<cac:PartyIdentification>
									<cbc:ID schemeName="touchpoint">TPO-0001</cbc:ID>
								</cac:PartyIdentification>
							</efac:TouchPoint>
						</efac:Organization>
					</efac:Organizations>
				</efext:EformsExtension>
			</ext:ExtensionContent>
		</ext:UBLExtension>
	</ext:UBLExtensions>
	<cbc:UBLVersionID>2.3</cbc:UBLVersionID>
	<cbc:CustomizationID>eforms-sdk-1.7</cbc:CustomizationID>
	<cbc:ID schemeName="notice-id">eeecf7d8-843a-4294-b7e8-4835e2161386</cbc:ID>
	<cbc:IssueDate>2023-06-06+02:00</cbc:IssueDate>
	<cbc:IssueTime>03:36:33+02:00</cbc:IssueTime>
	<cbc:VersionID>05</cbc:VersionID>
	<cbc:PlannedDate>2023-06-22+02:00</cbc:PlannedDate>
	<cbc:RegulatoryDomain>31985R2137</cbc:RegulatoryDomain>
	<cbc:NoticeTypeCode listName="planning">pin-only</cbc:NoticeTypeCode>
	<cbc:NoticeLanguageCode listName="language">ENG</cbc:NoticeLanguageCode>
	<cac:ContractingParty>
		<cbc:BuyerProfileURI>http://buyer1.iu</cbc:BuyerProfileURI>
		<cac:ContractingPartyType>
			<cbc:PartyTypeCode listName="buyer-legal-type">body-pl-cga</cbc:PartyTypeCode>
		</cac:ContractingPartyType>
		<cac:ContractingActivity>
			<cbc:ActivityTypeCode listName="authority-activity">env-pro</cbc:ActivityTypeCode>
		</cac:ContractingActivity>
		<cac:Party>
			<cac:PartyIdentification>
				<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
			</cac:PartyIdentification>
		</cac:Party>
	</cac:ContractingParty>
	<cac:ProcurementProject>
		<cbc:Name languageID="ENG">PROC_TITLE</cbc:Name>
		<cbc:Description languageID="ENG">PROC-DESC</cbc:Description>
		<cbc:ProcurementTypeCode listName="contract-nature">supplies</cbc:ProcurementTypeCode>
		<cbc:Note languageID="ENG">IN SU LA VETTA DELLA TORRE ANTICA</cbc:Note>
		<cac:RequestedTenderTotal>
			<cbc:EstimatedOverallContractAmount currencyID="EUR">100</cbc:EstimatedOverallContractAmount>
		</cac:RequestedTenderTotal>
		<cac:MainCommodityClassification>
			<cbc:ItemClassificationCode listName="cpv">03110000</cbc:ItemClassificationCode>
		</cac:MainCommodityClassification>
		<cac:AdditionalCommodityClassification>
			<cbc:ItemClassificationCode listName="cpv">03114200</cbc:ItemClassificationCode>
		</cac:AdditionalCommodityClassification>
		<cac:RealizedLocation>
			<cbc:Description languageID="ENG">Chi ha qualcosa in contrario, lo dica subito o taccia per sempre</cbc:Description>
			<cac:Address>
				<cbc:CityName>Vertemate con Minoprio</cbc:CityName>
				<cbc:PostalZone>40121</cbc:PostalZone>
				<cbc:CountrySubentityCode listName="nuts">AL014</cbc:CountrySubentityCode>
				<cbc:Region>anyw-cou</cbc:Region>
				<cac:Country>
					<cbc:IdentificationCode listName="country">BEL</cbc:IdentificationCode>
				</cac:Country>
			</cac:Address>
		</cac:RealizedLocation>
	</cac:ProcurementProject>
	<cac:ProcurementProjectLot>
		<cbc:ID schemeName="Part">PAR-0001</cbc:ID>
		<cac:TenderingTerms>
			<cac:FiscalLegislationDocumentReference>
				<cbc:ID>TAX_ID</cbc:ID>
				<cac:IssuerParty>
					<cac:PartyIdentification>
						<cbc:ID schemeName="touchpoint">TPO-0001</cbc:ID>
					</cac:PartyIdentification>
				</cac:IssuerParty>
			</cac:FiscalLegislationDocumentReference>
			<cac:EnvironmentalLegislationDocumentReference>
				<cbc:ID>ENV_ID</cbc:ID>
				<cac:Attachment>
					<cac:ExternalReference>
						<cbc:URI>http://env.df</cbc:URI>
					</cac:ExternalReference>
				</cac:Attachment>
				<cac:IssuerParty>
					<cac:PartyIdentification>
						<cbc:ID schemeName="organization">ORG-0001</cbc:ID>
					</cac:PartyIdentification>
				</cac:IssuerParty>
			</cac:EnvironmentalLegislationDocumentReference>
			<cac:CallForTendersDocumentReference>
				<cbc:ID>PROCUREMENT_DOCUMENTS_ID</cbc:ID>
				<cbc:DocumentType>restricted-document</cbc:DocumentType>
				<cac:Attachment>
					<cac:ExternalReference>
						<cbc:URI>http://localhost.er</cbc:URI>
					</cac:ExternalReference>
				</cac:Attachment>
			</cac:CallForTendersDocumentReference>
			<cac:TendererQualificationRequest>
				<cac:SpecificTendererRequirement>
					<cbc:TendererRequirementTypeCode listName="reserved-procurement">none</cbc:TendererRequirementTypeCode>
				</cac:SpecificTendererRequirement>
			</cac:TendererQualificationRequest>
			<cac:TenderEvaluationParty>
				<cac:PartyIdentification>
					<cbc:ID schemeName="touchpoint">TPO-0001</cbc:ID>
				</cac:PartyIdentification>
			</cac:TenderEvaluationParty>
			<cac:AppealTerms>
				<cac:AppealReceiverParty>
					<cac:PartyIdentification>
						<cbc:ID schemeName="touchpoint">TPO-0001</cbc:ID>
					</cac:PartyIdentification>
				</cac:AppealReceiverParty>
			</cac:AppealTerms>
		</cac:TenderingTerms>
		<cac:TenderingProcess>
			<cbc:GovernmentAgreementConstraintIndicator>true</cbc:GovernmentAgreementConstraintIndicator>
			<cac:ContractingSystem>
				<cbc:ContractingSystemTypeCode listName="framework-agreement">fa-mix</cbc:ContractingSystemTypeCode>
			</cac:ContractingSystem>
		</cac:TenderingProcess>
		<cac:ProcurementProject>
			<cbc:ID>PART_FERDI_IDENTIFIER</cbc:ID>
			<cbc:Name languageID="ENG">PART TITLE</cbc:Name>
			<cbc:Description languageID="ENG">PART-DESC</cbc:Description>
			<cbc:ProcurementTypeCode listName="contract-nature">supplies</cbc:ProcurementTypeCode>
			<cbc:Note languageID="ENG">Ma perche' tutte queste domande ?</cbc:Note>
			<cac:MainCommodityClassification>
				<cbc:ItemClassificationCode listName="cpv">03000000</cbc:ItemClassificationCode>
			</cac:MainCommodityClassification>
		</cac:ProcurementProject>
	</cac:ProcurementProjectLot>
</PriorInformationNotice>

Looking at the sample change-cn_24_void.xml I tried changing the tag :
efbc:ChangedNoticeIdentifiereeecf7d8-843a-4294-b7e8-4835e2161386-05</efbc:ChangedNoticeIdentifier>
with :
efbc:ChangedNoticeIdentifierf42be27e-09cf-4f0e-a745-63ec689631e6-01</efbc:ChangedNoticeIdentifier>

but the result was the same
I am using sdk 1.7
Thanks and Regards
Renato

Answered by bertrand-lorentz

Jun 7, 2023

As indicated in https://docs.ted.europa.eu/eforms/latest/schema/change-notice.html, a change notice is a new notice, so it must have its own identifier.
This is currently enforce by the eNotices2 application, which is why the notice is considered valid by CVS, but you got the error when trying to submit.

So you should probably change the identifier in the following line to a new UUID:
<cbc:ID schemeName="notice-id">eeecf7d8-843a-4294-b7e8-4835e2161386</cbc:ID>

View full answer

bertrand-lorentz · 2023-06-07T08:54:35Z

bertrand-lorentz
Jun 7, 2023
Maintainer

As indicated in https://docs.ted.europa.eu/eforms/latest/schema/change-notice.html, a change notice is a new notice, so it must have its own identifier.
This is currently enforce by the eNotices2 application, which is why the notice is considered valid by CVS, but you got the error when trying to submit.

So you should probably change the identifier in the following line to a new UUID:
<cbc:ID schemeName="notice-id">eeecf7d8-843a-4294-b7e8-4835e2161386</cbc:ID>

1 reply

rengit62 Jun 8, 2023
Author

OK done and submitted ! thanks
now a simple question ( I think )
BT-140-notice and BT-758-notice are both "readOnly" : true
It is 'wanted' or it is an error ? I mean if BT-140-notice is readonly (for example) an user cannot choose the reason code.
Ciao !
Renato

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

error on changeNotice Notice Subtype 4 #508

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 1 comment 1 reply

{{title}}

{{title}}

Select a reply

error on changeNotice Notice Subtype 4 #508

rengit62 Jun 6, 2023

Replies: 1 comment · 1 reply

bertrand-lorentz Jun 7, 2023 Maintainer

rengit62 Jun 8, 2023 Author

rengit62
Jun 6, 2023

Replies: 1 comment 1 reply

bertrand-lorentz
Jun 7, 2023
Maintainer

rengit62 Jun 8, 2023
Author