Validations definitions Validations categories are not mutually exclusive (i.e., several categories can apply to a single validation). A validation can apply to multiple categories, such as a specific form version, an activity code and/or an FOA specific flag at the same time. As an example, validation 018.3.2 agency Provide error if this value for any budget year is > 50K for R03 or budget year is >200K for R21 on the Modular budget applies to the following categories: Form version - V1.2 Agency - NIH FOA Specific flag - project_cost_exception_flag = Y Activity code – Include R03, R21 Categories: Form Version Validations Validations can vary by version level of an individual form within a form package. The form version number column lists – applicability of rule to all Included Versions and above. Example: Form version Incl: 2.0 means the rule is applicable to form versions 2.0 and above. Form version Excl: 1.2 means the rule is applicable to form version 1.1 Mandatory Validations Validations required for eRA systems to successfully process applications and map them to the eRA database (i.e., IMPAC II). – Apply to NIH and all Agencies using eRA systems to process grant applications. Examples: The FOA must exist in the eRA database (000.19) DUNS on SF424 R&R cover form must exist in the eRA database. (001.8.1) Agency Specific Validations Validations that are modifiable at the Agency level. Agency is determined by a parameter associated with the FOA. The – Agency parameter will be exposed in the Submission Agency Data Service in a future enhancement. Examples:
Validations definitions Validations categories are not mutually exclusive (i.e., several categories can apply to a single validation). A validation can apply to multiple categories, such as a specific form version, an activity code and/or an FOA specific flag at the same time. As an example, validation 018.3.2 agency Provide error if this value for any budget year is > 50K for R03 or budget year is >200K for R21 on the Modular budget applies to the following categories: Form version - V1.2 Agency - NIH FOA Specific flag - project_cost_exception_flag = Y Activity code – Include R03, R21 Categories: Form Version Validations – Validations can vary by version level of an individual form within a form package. The form version number column lists applicability of rule to all Included Versions and above. Example: Form version Incl: 2.0 means the rule is applicable to form versions 2.0 and above. Form version Excl: 1.2 means the rule is applicable to form version 1.1 Mandatory Validations – Validations required for eRA systems to successfully process applications and map them to the eRA database (i.e., IMPAC II). Apply to NIH and all Agencies using eRA systems to process grant applications. Examples: The FOA must exist in the eRA database (000.19) DUNS on SF424 R&R cover form must exist in the eRA database. (001.8.1) Agency Specific Validations – Validations that are modifiable at the Agency level. Agency is determined by a parameter associated with the FOA. The Agency parameter will be exposed in the Submission Agency Data Service in a future enhancement. Examples: