Validation of completeness Sample Clauses

Validation of completeness. It details the new process on reporting rowcount in entity type delivery. Updated the hyperlinks to the webpage of DNB that contains the AnaCredit information.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Validation of completeness. The metadata checksum file is part of the files to be submitted. For each entity type, the required type of checksum is listed. For now, only, a logical row count is requested for each entity type that is logically part of the reporting requirement. The entity types that are part of the reference data do not require a rowcount. All entity types whose rowcount is to be reported is marked with a rowcount reporting indicator value set to “entity type with reported rowcount”. This rowcount 12 Sending in a new AnaCredit data exchange for the same obligation (reporting ID, reporting reference date, data delivery code) while the status of the previous delivery is Received, will result in a validation error of the newly submitted data exchange. 13 In time, these signalling rules are meant to be changed to ‘blocking’. 14 These are signalling rules that require data outside the scope of the data delivery set. indicates the number of instances of an entity type that is appropriate to this entity type in accordance with the logical data model. Please note that this concerns the entity types in the logical data model where the attribute ‘reporting reference date’ is part of the primary key, and not only those entity types in the physical data deliveries. The logical data model also requires a row count and checksum for those entity types that do not have a corresponding .csv file to be delivered. 2.7.6.1 Example of a check on a physical delivery
Sample 1Sample 2Sample 3See All (4)
Validation of completeness. The metadata checksum file is part of the files to be submitted. For each entity type, the required type of checksum is listed. For now, only, a logical row count is requested for each entity type that is logically part of the reporting requirement. The entity types that are part of the reference data do not require a rowcount. All entity types whose rowcount is to be reported is marked with a rowcount reporting indicator value set to “entity type with reported rowcount”12. This rowcount indicates the number of instances of an entity type that is appropriate to this entity type in accordance with the logical data model. Please note that this concerns the entity types in the logical data model where the attribute ‘reporting reference date’ is part of the primary key, and not only those entity types in the physical data deliveries. The logical data model also requires a row count and checksum for those entity types that do not have a corresponding .csv file to be delivered. 2.6.6.1 Example of a check on a physical delivery E.g. the reporting agent must report on exactly 100,000 instruments. The instrument.csv file contains 100,000 rows, excluding the header. The row count for the logical entity is 100,000. The entity type delivery lists a row count of 100,000 for the "instrument" entity type. DNB checks that 100000 = 100000 and accepts the delivery. 2.6.6.2 Example of a check on a logical delivery The entity type "instrument not past due" does not have its own specific features or relations, and therefore does not require physical delivery. However, the logical checksum of all not past due instruments must be delivered. For example, the reporting agent must report on exactly 100,000 instruments (with 100,000 financial data), 10,000 of which are instrument past due and 90,000 are instrument not past due (100,000-10,000). These files must be reported: 1. instrument.csv with 100,000 records 2. financial_data.csv with 100,000 records 3. instrument_past_due.csv with 10,000 records These records must be reported in the entity type delivery: Instrument 100,000 financial data 100,000 instrument past due 10,000 instrument not past due 90,000 DNB checks that instrument.csv contains 100,000 rows, that financial_data.csv contains 100,000 rows, that instrument_past_due contains 10,000 rows and that 90,000 rows in instrument.csv logically consist of instruments not past due. 12 The rowcount reporting indicator for the entity types can be found in the ‘RRE business terms’,...
Sample 1Sample 2See All (4)
Validation of completeness. The metadata checksum file is part of the files to be submitted. For each entity type, the required type of checksum is listed. For now, no checksum is requested, only, a logical row count is requested for each entity type. This count indicates the number of instances of an entity type that is appropriate to this entity type in accordance with the logical data model. Please note that this concerns the entities in the logical data model and not only those in the physical data deliveries: the logical data model also requires a row count and checksum for those entity types that do not have a corresponding .csv file to be delivered. 2.6.6.1 Example of a check on a physical delivery E.g. the bank must deliver exactly 100,000 bank accounts. The bank_account.csv file contains 100,000 rows. The row count for the logical entity is 100,000. The entity type delivery lists a row count of 100,000 for the "bank account" entity type. DNB checks that 100000 = 100000 and accepts the delivery. 2.6.6.2 Example of a check on a logical delivery The entity types "non blocked bank account" and “blocked bank account” do not have their own specific features, and therefore do not require physical delivery. However, the logical checksum and/or rowcount of “non blocked bank account” and “blocked bank account” must be delivered. For example, the bank must deliver exactly 100,000 bank accounts, 1,500 of which are blocked bank accounts and 98,500 are non blocked bank accounts (100,000-1,500). Only one file must be reported: 1. bank_account.csv with 100,000 records Altough, three records must be reported in the entity type delivery: Bank account 100,000 Blocked bank account 1,500 Non blocked bank account 98,500 DNB checks if bank_account.csv contains 100,000 rows and if 1,500 rows and 98,500 rows in bank_account.csv logically consist of respectively blocked bank accounts and non blocked bank accounts. An example of the entity_type_delivery content can be found in Apendix C. 2.6.6.3 Check on primary key The LDM has entity types that allow DNB to ask for checks on combinations of attributes. This mechanism is primarily meant to check the integrity of primary keys of the entity types in the logical data model. Currently, no checks of these types are foreseen, since DNB will rely instead on the hashing of the csv files themselves, in combination of the checks on the referential integrity as specified in the logical data model. This entails that the file attribute_combination_delivery.csv mus...
Sample 1Sample 2Sample 3
Validation of completeness. ‌ The metadata checksum file is part of the files to be submitted. For each entity type, the required type of checksum is listed. For now, no checksum is requested, only, a logical row count is requested for each entity type. This count indicates the number of instances of an entity type that is appropriate for this entity type in accordance with the logical data model. Please note that this concerns all entities in the logical data model including reference data and entity types like “entity type delivery” and not only those in the physical data deliveries: the logical data model also requires a row count and checksum for those entity types that do not have a corresponding .csv file to be delivered. 2.6.6.1 Example of a check on a physical delivery
Sample 1Sample 2
Validation of completeness. ‌ The metadata checksum file is part of the files to be submitted. For each entity type, the required type of checksum is listed. For now, no checksum is requested, only, a logical row count is 12 Sending in a new AnaCredit data exchange for the same obligation (reporting ID, reporting reference date, data delivery code) while the status of the previous delivery is Received, will result in a validation error of the newly submitted data exchange. 13 In time, these signalling rules are meant to be changed to ‘blocking’. 14 These are signalling rules that require data outside the scope of the data delivery set. requested for each entity type. This count indicates the number of instances of an entity type that is appropriate to this entity type in accordance with the logical data model. Please note that this concerns the entities in the logical data model and not only those in the physical data deliveries: the logical data model also requires a row count and checksum for those entity types that do not have a corresponding .csv file to be delivered. 2.7.6.1 Example of a check on a physical delivery
Sample 1
Validation of completeness. ‌ The metadata checksum file is part of the files to be submitted. For each entity type, the required type of checksum is listed. For now, no checksum is requested, only, a logical row count is requested for each entity type. This count indicates the number of instances of an entity type that is appropriate to this entity type in accordance with the logical data model.
Sample 1
AutoNDA by SimpleDocs

Related to Validation of completeness

  • Completeness This Grant Contract is complete and contains the entire understanding between the parties relating to the subject matter contained herein, including all the terms and conditions of the parties’ agreement. This Grant Contract supersedes any and all prior understandings, representations, negotiations, and agreements between the parties relating hereto, whether written or oral.

  • Certification of Compliance The Recipient shall complete and submit the following Notice of Completion and, if applicable, Engineer’s Certification of Compliance to the Department upon completion of the construction phase of the Project.

  • Effect of Completion This agreement shall, as to any of its provisions remaining to be performed or capable of having or taking effect following Completion, remain in full force and effect notwithstanding Completion.

  • Response/Compliance with Audit or Inspection Findings A. Grantee must act to ensure its and its Subcontractors’ compliance with all corrections necessary to address any finding of noncompliance with any law, regulation, audit requirement, or generally accepted accounting principle, or any other deficiency identified in any audit, review, inspection or investigation of the Grant Agreement and the services and Deliverables provided. Any such correction will be at Grantee’s or its Subcontractor's sole expense. Whether Xxxxxxx's action corrects the noncompliance shall be solely the decision of the System Agency. B. As part of the services, Grantee must provide to HHS upon request a copy of those portions of Grantee's and its Subcontractors' internal audit reports relating to the services and Deliverables provided to the State under the Grant Agreement. C. Grantee shall include the requirement to provide to System Agency (and any of its duly authorized federal, state, or local authorities) internal audit reports related to this Grant Agreement in any Subcontract it awards. Upon request by System Agency, Grantee shall enforce this requirement against its Subcontractor. Further, Grantee shall include in any Subcontract it awards a requirement that all Subcontractor Subcontracts must also include these provisions.

  • Declaration of Compliance Within 90 Days of the HSP’s fiscal year-end, the Board will issue a Compliance Declaration declaring that the HSP has complied with the terms of this Agreement. The form of the declaration is set out in Schedule F and may be amended by the Funder from time to time through the term of this Agreement.

  • Inspection; Compliance with Law Lessor, Lessor's agents, employees, contractors and designated representatives, and the holders of any mortgages, deeds of trust or ground leases on the Premises ("Lenders") shall have the right to enter the Premises at any time in the case of an emergency, and otherwise at reasonable times, for the purpose of inspecting the condition of the Premises and for verifying compliance by Lessee with this Lease and all Applicable Requirements (as defined in Paragraph 6.3), and Lessor shall be entitled to employ experts and/or consultants in connection therewith to advise Lessor with respect to Lessee's activities, including but not limited to Lessee's installation, operation, use, monitoring, maintenance, or removal of any Hazardous Substance on or from the Premises. The costs and expenses of any such inspections shall be paid by the party requesting same, unless a Default or Breach of this Lease by Lessee or a violation of Applicable Requirements or a contamination, caused or materially contributed to by Lessee, is found to exist or to be imminent, or unless the inspection is requested or ordered by a governmental authority as the result of any such existing or imminent violation or contamination. In such case, Lessee shall upon request reimburse Lessor or Lessor's Lender, as the case may be, for the costs and expenses of such inspections.

  • EFFECT OF COMPLIANCE Compliance with and fulfillment of this Agreement shall be deemed to resolve all issues raised in the NOV.

  • Representations Complete None of the representations or warranties made by the Company herein or in any Schedule hereto, including the Company Disclosure Schedule, or in any certificate furnished by the Company pursuant to this Agreement, when all such documents are read together in their entirety, contains or will contain upon the consummation of the Offer any untrue statement of a material fact, or omits or will omit upon the consummation of the Offer to state any material fact necessary in order to make the statements contained herein or therein, in the light of the circumstances under which made, not misleading.

  • Inspection and Verification The Collateral Agent and such Persons as the Collateral Agent may reasonably designate shall have the right, subject to compliance with Section 5.09 of the Credit Agreement, to inspect the Collateral, all records related thereto (and to make extracts and copies from such records) and the premises upon which any of the Collateral is located, to discuss the Grantors' affairs with the officers of the Grantors and their independent accountants and to verify under reasonable procedures the validity, amount, quality, quantity, value, condition and status of, or any other matter relating to, the Collateral, including, in the case of Accounts or Collateral in the possession of any third person, by contacting Account Debtors or the third person possessing such Collateral for the purpose of making such a verification; provided, however, that representatives of the Grantors shall be entitled to -------- ------- participate in such discussions. The Collateral Agent shall have the absolute right to share any information it gains from such inspection or verification with any Secured Party.

  • DECLARATION OF COMPLIANCE WITH APPLICABLE STANDARDS 1. Does the Work report experiments involving human subjects? [ ] YES [ ] NO  If Yes, were the reported experiments in accordance with the ethical standards of the committee responsible for human experimentation (institutional and national), and with the Helsinki Declaration of 1975, as revised in 2013 (xxxx://xxxxxx.xxx.xxx/ecodes/node/3931 )? [ ] YES [ ] NO (If Yes, the Assignor must submit a copy of the approval and consent-to-disclose form to Xxxxxxx Science Publishers by fax or email.) Please state whether Ethical Approval was given, by whom and the relevant Judgement’s reference number. (If No, the Assignor must mention an institutional or regional guideline.) 2. Does the Work report experiments involving animals? [ ] YES [ ] NO  If Yes, were the reported experiments in accordance with the standards set forth in one of below national guidelines and regulations: o The US National Research Council's "Guide for the Care and Use of Laboratory Animals," o The US Public Health Service's "Policy on Humane Care and Use of Laboratory Animals," and "Guide for the Care and Use of Laboratory Animals." o UK : the Animals (Scientific Procedures) Act 1986 Amendment Regulations (SI 2012/3039). [ ] YES [ ] NO 6 [v.122016] Conflicts of interest arise when authors, reviewers, or editors have interests (such as financial or personal interests) that are not made clear and that may influence their judgment on the content of their work. Authors and editors who submit work for publication with Xxxxxxx Science are required to disclose and acknowledge all forms of financial support relating to the work to be published, all commercial or financial involvement that might present an appearance of a conflict of interest in respect of the work, and all agreements relating to sponsorship of any research upon which the work is based. Are there any actual, or potential, conflicts of interest? [ ] YES [ ] NO If Yes, details of the actual or potential conflicts of interest must be set-out in the spaces provided below. Does Assignor require assistance in having the English grammar and style of the Work checked and improved by Xxxxxxx Science? [ ] YES [ ] NO If Yes, Xxxxxxx Science will provide a quote in respect of the same.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!