prop · GS0318 · 2004-09-28 00:00:00 — Table VIII-13: AccountManagement.ValidateAccountUpdate() function This function validates an account update request. If a validation test fails, the account identifier and response code are added to the response list. Account (*) ContactPeople (see Optional People (*) Table VIII-14: ManagementOfAccount.UpdateAccount() function This function updates an account. Update the account details. For each link to be added: If the people existed, update its details if required. If the people did not exist, create the people and link it to the account. For all people to update and that are linked to the account, update their details. Remove the link between the people and the account for the link to be removed (for example, an additional authorised representative is removed). If an installation is linked to the account, update the installation details if required. Update the people details linked to the installation if details have been submitted (by using the same Add, Update and Delete actions). Account (*) ContactPeople (see People) People (*) Not applicable (called as a web service). Table VIII-15: ManagementOfAccount.ValidateAccountClosure() function This function validates an account closure operation. If a validation test fails, the account identifier and response code are added to the response list Account (*) 7111; range 7114 to 7115; 7117; range 7153 to 7156; 7158. Table VIII-16: ManagementOfAccount.CloseAccount() This function closes an account or accounts by setting the end validity date of the account(s) to be closed to the current date. Account (*) Table VIII-17: ManagementOfAccount.ValidateVerifiedEmissionsUpdate() This function validates a verified emissions update. If a validation test fails, the installation identifier and response code are added to the response list. VerifiedEmissions (*) Installations (*) Range 7118 to 7119; range 7152 to 7156; 7159. Table VIII-18: ManagementOfAccount.UpdateVerifiedEmissions Updates the verified emissions for the year and installations in parameter. VerifiedEmissions (*) Installations (*) Preliminary checks for each process The Community independent transaction log shall check the status of a registry for each process concerning an account or verified emissions. If the communication link between the registry and the Community independent transaction log has not been established or is temporarily suspended pursuant to Article 6(3) in respect of the requested process concerning an account or verified emissions, it shall be rejected and the response code 7005 shall be returned. Prior to the communication link between the Community independent transaction log and the UNFCCC independent transaction log being established, the Community independent transaction log shall perform registry version and registry authentication checks, and message viability checks, on each process concerning an account or verified emissions and return the appropriate response codes if a discrepancy is detected, set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC. Thereafter, each registry shall receive such response codes from the UNFCCC independent transaction log. The Community independent transaction log shall perform data integrity checks on each process concerning an account or verified emissions and return response codes in the range 7122 to 7159 if a discrepancy is detected. Secondary checks for each process The Community independent transaction log shall perform secondary checks on each process concerning an account or verified emissions which has passed all of the preliminary The secondary checks, and the adjoining response codes which are returned when a discrepancy is detected, are set out in table VIII-19. Table VIII-19: Secondary Checks Community independent transaction log Range 7101 to 7110 Range 7102 to 7105 Range 7107 to 7108 Range 7114 to 7115 Range 7118 to 7119 Processes concerning transactions with response codes 39.Each process concerning a transaction shall be assigned a process type consisting of an initial process type and a supplementary process type. The initial process type shall describe its category as set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC. The supplementary process type shall describe its category as set out in the provisions of this Regulation, elaborated pursuant to Directive 2003/87/EC. The process types are set out in table IX-1. Requirements for each process The message sequence for processes concerning a transaction, the status of the transaction and the status of the Kyoto units or allowances involved in the transaction during the message sequence, and the components and functions which are utilised during the message sequence, are set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC. Preliminary checks for each process The Community independent transaction log shall check the status of a registry for each process concerning a transaction. If the communication link between the registry and the Community independent transaction log has not been established or is temporarily suspended pursuant to Article 6(3) in respect of the requested process, it shall be rejected and the response codes 7005 or 7006 shall be returned. Prior to the communication link between the Community independent transaction log and the UNFCCC independent transaction log being established, the Community independent transaction log shall perform the following categories of preliminary checks on each process concerning a transaction: (a)registry version and registry authentication checks, (b)message viability, (c)data integrity checks, (d)general transaction checks, and (e)message sequence checks, and return the appropriate response codes if a discrepancy is detected, as set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC. Thereafter, each registry shall receive such response codes from the UNFCCC independent transaction log. Secondary and tertiary checks for each process For each process concerning a transaction which has passed all of the preliminary checks, the Community independent transaction log shall perform the following secondary checks to ascertain whether: (a)the Kyoto units or allowances are held in the transferring account (a discrepancy returns response code 7027); (b)the transferring account exists in the specified registry (a discrepancy returns response code 7021); (c)the acquiring account exists in the specified registry (a discrepancy returns response code 7020); (d)both accounts exist in the same registry for an internal transfer (a discrepancy returns response code 7022); (e)both accounts exist in different registries for an external transfer (a discrepancy returns response code 7023); (f)the transferring account is not blocked pursuant to Article 27 (a discrepancy returns response code 7025). The Community independent transaction log shall perform tertiary checks on each process concerning a transaction which has passed all of the preliminary checks. The tertiary checks, and the adjoining response codes which are returned when a discrepancy is found, are set out in table IX-1. Table IX-1: Tertiary Checks Issue of AAUs and RMUs [not applicable] Conversion of AAUs and External transfer (2008-2012 03-00 Range 7301 to 7302 [not applicable] Range 7358 to 7361 [not applicable] replacement of tCERs and Carry-over of Kyoto units [not applicable] and allowances issued for the Change of expiry date of [not applicable] Range 7406 to 7407 Allowance issue (2005-2007) Range 7201 to 7203 Allowance issue (2008-2012 Range 7201 to 7203 7203Range 7206 to 7208 Range 7210 to 7211 Range 7212 to 7213 External transfer (2005- Range 7304 to 7305 Range 7406 to 7407 Range 7353 to 7356 Retirement (2005-2007) Range 7360 to 7362 (2005 to 2007) Range 7406 to 7407 (2008-2012 onwards) Range 7401 to 7402 Range 7404 to 7407 Reconciliation process with response codes Requirements for each process type 40.Prior to the communication link between the Community independent transaction log and the UNFCCC independent transaction log being established, each registry shall respond to any request made by the Community independent transaction log to submit the following information for a specified time and date: (a)the total number of allowances held in any account type in that registry; (b)the unit identification codes of any allowance held in any account type in that registry; and (c)the transaction log and audit log history of any allowance held in any account type in that registry. (d)the total number of allowances held in any account in that registry; (e)the unit identification codes of any allowance held in any account in that registry; and (f)the transaction log and audit log history of any allowance held in any account in that registry. After the communication link between the Community independent transaction log and the UNFCCC independent transaction log has been established, each registry shall respond to any request made by the UNFCCC independent transaction log to submit the following information for a specified time and date: (a)the total number of allowances, AAUs, RMUs, ERUs, CERs (not tCERs or lCERs), lCERs and tCERs, held in any account type in that registry; (b)the unit identification codes of any allowance, AAU, RMU, ERU, CER (not tCER or lCER), lCER and tCER, held in any account type in that registry; and (c)the transaction log and audit log history of any allowance, AAU, RMU, ERU, CER (not tCER or lCER), lCER and tCER held in any account type in that registry. After the communication link between the Community independent transaction log and the UNFCCC independent transaction log has been established, each registry shall respond to any request by the UNFCCC independent transaction log made on behalf of the Community independent transaction log to submit the following information for a specified time and date: (a)the total number of allowances, AAUs, RMUs, ERUs, CERs (not tCERs or lCERs), lCERs and tCERs held in any account in that registry; (b)the unit identification codes of any allowance, AAU, RMU, ERU, CER (not tCER or lCER), lCER and tCER held in any account in that registry; and (c)the transaction log and audit log history of any allowance, AAU, RMU, ERU, CER (not tCER or lCER), lCER and tCER held in any account in that registry. The message sequence for the reconciliation process, the status of the reconciliation process and the status of the Kyoto units or allowances involved in the reconciliation process during the message sequence, and the components and functions which are utilised during the message sequence, are set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC. Preliminary checks for each process The Community independent transaction log shall check the status of a registry during the reconciliation process. If the communication link between the registry and the Community independent transaction log has not been established or is temporarily suspended pursuant to Article 6(3) in respect of the reconciliation process, it shall be rejected and the response code 7005 shall be returned. Prior to the communication link between the Community independent transaction log and the UNFCCC independent transaction log being established, the Community independent transaction log shall perform registry version and registry authentication checks, message viability checks, and data integrity checks during the reconciliation process and return the appropriate response codes if a discrepancy is detected, as set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC. Thereafter, each registry shall receive such response codes from the UNFCCC independent transaction log. Secondary checks for each process The Community independent transaction log shall perform secondary checks during the reconciliation process, once the preliminary checks have been passed. The secondary checks, and the adjoining response codes which are returned when an inconsistency is detected, are set out in table X-1. Table X-1: Secondary Checks Community independent transaction log Range: 7501 to 7524 If the information held in a registry has been amended in response to a process initiated but not finalised pursuant to Articles 34, 35 and 36, the Central Administrator shall instruct the registry administrator of that registry to reverse that process by amending the information held back to its original state. If the information held in a registry has not been amended in response to a process initiated and finalised pursuant to Articles 34, 35 and 36, the Central Administrator shall instruct the registry administrator of that registry to finalise that process by amending the information held accordingly. Where the reconciliation process has identified an inconsistency, the Central Administrator shall coordinate with the registry administrator or administrators concerned in order to determine the origin of the inconsistency. The Central Administrator shall then, as necessary, either amend the information held in the Community independent transaction log or request the registry administrator or administrators concerned to make specific manual adjustments to the information held in their registry. Administrative processes with response codes 41.The Community independent transaction log shall provide the following administrative processes: (a)Transaction clean-up: all processes under which have been initiated but not yet terminated, completed or cancelled within 24 hours shall be cancelled. Transaction clean-up occurs on an hourly basis. (b)Outstanding units: all allowances which have not been cancelled pursuant to Articles 60 or 61 on or after 1 2008 and on or after 1 in the first year of each subsequent five-year period shall be identified. (c)Process status: a registry administrator may query the status of a process under which has been initiated by that registry administrator. (d)Time synchronisation: upon request, each registry administrator shall provide the system time of its registry in order that the consistency between the system time of a registry and the system time of the Community independent transaction log can be checked and synchronised. Upon request, a registry administrator shall change the system time of its registry in order to ensure time synchronisation. After the communication link between the Community independent transaction log and the UNFCCC independent transaction log has been established, the Community independent transaction log shall only continue to provide the administrative process under paragraph 1(b). Each registry shall be capable of executing correctly the additional administrative processes provided by the UNFCCC independent transaction log, set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC. Requirements for each process The message sequence for administrative processes and the components and functions which are utilised during the message sequence are set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC. Checks for each process If, during the period referred to in paragraph 2, the Community independent transaction log detects a discrepancy under paragraph 1(a) it shall return the appropriate response codes as set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC. If the Community independent transaction log detects a discrepancy under paragraph 1(b) it shall return the response code 7601. During the period referred to in paragraph 2 and where a message is received from a registry under paragraph 1(c) for a process referred to in the Community independent transaction log shall perform the following checks: (a)Status of a registry: if the communication link between the registry and the Community independent transaction log has not been established or is temporarily suspended pursuant to Article 6(3) in respect of the requested process, the message shall be rejected and the response code 7005 shall be returned. (b)Registry version and registry authentication, message viability, and data integrity: if the Community independent transaction log detects a discrepancy, the message shall be rejected and the appropriate response codes shall be returned as set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC. During the period referred to in paragraph 2 and where a message is received from a registry under paragraph 1(d) the Community independent transaction log shall perform the following checks: (a)Status of a registry: if the communication link between the registry and the Community independent transaction log has not been established or is temporarily suspended pursuant to Article 6(3) in respect of the requested process, the message shall be rejected and the response code 7005 shall be returned. (b)Registry version and registry authentication, message viability, data integrity and time synchronisation: if the Community independent transaction log detects a discrepancy, the message shall be rejected and the appropriate response codes shall be returned as set out in the functional and technical specifications for data exchange standards for registry systems under the Kyoto Protocol, elaborated pursuant to Decision 24/CP.8 of the Conference of the Parties to the UNFCCC. List of response codes for all processes 42.The Community independent transaction log shall return response codes as part of each process, where specified in , , and . Each response code shall consist of an integer within the range 7000 to 7999. The meaning of each response code is given in table XII-1. Each registry administrator shall ensure that the meaning of each response code is maintained when displaying information in respect of a process under to the authorised representative who initiated that process. Table XII-1: Community Independent Transaction Log Response Codes The current status of the initiating (or transferring) registry does not permit this process to take place. The current status of the acquiring registry does not permit this process to take place. The specified account identification code does not exist in the The specified account identification code does not exist in the The transferring account and acquiring account must be in the same registry for all transactions except external transfers. The transferring account and acquiring account must be in different registries for external transfers. The transferring account is blocked for all transfers of allowances out of that account, with the exception of the surrender and cancellation and replacement processes pursuant to Articles 52, 53, 60 and 61. One or more units in the serial block are not recognised as being held by the transferring account. The account has already been created. An account must have one and only one account holder. An account must have one and only one primary authorised An account must have one and only one secondary authorised An installation must have one and only one contact person. The installation associated to this account is already associated to The authorised representatives of the account must all be different. The alphanumeric identifier specified for the account is already specified for another account. The account type being created has not been given the correct An operator holding account must have one and only one installation associated with that account. The specified account does not exist, and therefore it is not possible to update or close the account. It is not possible to change the account holder of a person holding The specified account has already been closed therefore it is not possible to close the account. The specified account still holds units and therefore it is not possible to close the account. The installation linked to the specified account is not in compliance therefore it is not possible to close the account. The specified installation does not exist and therefore it is not possible to update the verified emissions table for that installation. The specified year is a future year and therefore it is not possible to update the verified emissions table for that year. The people and their relationship with the account do not exist and therefore it is not possible to update that relationship. The correlation identifier is not in valid format or is out of range. The account alphanumeric identifier is not in valid format or is out of The permit identifier is not in valid format or is out of range. The installation name is not in valid format or is out of range. The installation main activity is not in valid format or is out of range. The installation country is not in valid format or is out of range. The installation postal code is not in valid format or is out of range. The installation city is not in valid format or is out of range. The installation address1 is not in valid format or is out of range. The installation address2 is not in valid format or is out of range. The installation parent company is not in valid format or is out of The installation subsidiary company is not in valid format or is out of The installation EPER identification is not in valid format or is out of The installation latitude is not in valid format or is out of range. The installation longitude is not in valid format or is out of range. The people relationship code is not in valid format or is out of range. The person identifier is not in valid format or is out of range. The people first name is not in valid format or is out of range. The people last name is not in valid format or is out of range. The people country is not in valid format or is out of range. The people postal code is not in valid format or is out of range. The people city is not in valid format or is out of range. The people address1 is not in valid format or is out of range. The people address2 is not in valid format or is out of range. The people phonenumber1 is not in valid format or is out of range. The people phonenumber2 is not in valid format or is out of range. The people fax number is not in valid format or is out of range. The people email is not in valid format or is out of range. The people action is not in valid format or is out of range. The installation verified emission is not in valid format or is out of The from element is not in valid format or is out of range. The to element is not in valid format or is out of range. The major version is not in valid format or is out of range.