PrintFiling Validation Rules
The following validation rules are verified when a user validates a Filing prior to submitting the Filing to FERC.
| Rule ID | Description | Type | Message |
|---|---|---|---|
| A001 | Attachments that are provided must include a file name | Fail | The file name for FERC Attachment "<Attachment.Description>" is missing. |
| A003 | Required, non-waivable attachments must be provided. | Fail | The content for FERC Attachment "<Attachment.Description>" is missing. |
| A004 | Required, waivable attachments must either be provided or a waiver requested | Fail | The content for FERC Attachment "<Attachment.Description>" is missing. |
| A005 | Attachment content cannot be larger than 50MB | Fail | The content for FERC Attachment "<Attachment.Description>" is too large. |
| A006 | Required, waivable attachments cannot be both provided AND waiver requested | Fail | The content for FERC Attachment "<Attachment.Description>" has been provided and waiver is also being requested. This is ambiguous. |
| A007 | Filing Validation Rule: Attachment Security Level is active on Filing Date | Fail | The security level selected for FERC Attachment "<FERCAttachment.Description>" is not valid for filing date <filingDate.Value.ToShortDateString()>. |
| A008 | Filing Validation Rule: Attachment content type is active on Filing Date | Fail | The content type (<file extension>) of FERC Attachment "<FERCAttachment.Description>" is not valid for filing date <filingDate.Value.ToShortDateString()>. |
| A009 | Transmittal letter attachments must be named "Transmittal Letter". | Fail | FERC Attachment "<Attachment.Description>" is an attachment of type "<Attachment.AttachmentReferenceCode.Description>". You must submit it with a Description of "Transmittal Letter". |
| A010 | FERC Attachment Filename cannot be longer than 60 characters | Fail | The file name "<Attachment.AttachmentFileName>" that belongs to FERC Attachment "<Attachment.Description>" is longer than the 60 character maximum. |
| A011 | FERC Attachment Description cannot be longer than 80 characters | Fail | FERC Attachment "<Attachment.Description>" has a description that is longer than the 80 character maximum. |
| A012 | Within a Filing, the combination of attachment file name and attachment security level must be unique. | Fail | There is more than one FERC Attachment with file name "<Attachment.AttachmentFileName>" and security level "<Attachment.SecurityLevel.Description>" in this Filing. The combination of file name and security level must be unique within a Filing. |
| A013 | For every attachment in a Filing that is provided with a non-Public security level a version must also be provided with a Public security level. | Fail | When FERC Attachment "<Attachment.AttachmentReferenceCode.Description>" is provided with a security level of "<Attachment.SecurityLevel.Description>", a Public version of the attachment must also be provided. |
| A014 | FERC Attachments must have an associated AttachmentContentType | Fail | The content type (<file extension>) of FERC Attachment "<FERCAttachment.Description>" is not valid. |
| A015 | "FERC Attachment Filename cannot contain any of the following characters: ? / * \ " ' > < | Fail | The file name "<Attachment.AttachmentFileName>" that belongs to FERC Attachment "<Attachment.Description>" contains one or more invalid characters. |
| C001 | Verify that the Company's FERC Id matches the expected FERC-established format. | Fail | The FERC Id for <Company.Name> is in the wrong format. It must start with an upper case "C" and be followed by six digits. For example, C001234. |
| F001 | A filing is typically in Draft status when XML is generated. | Warning | The status of this filing indicates that it has already been filed with FERC. Generating the XML now is out of the ordinary. |
| F002 | The FERC Response for every FTRV in a Filing is typically Draft when XML is generated. | Warning | This filing contains n Filed Tariff Record Versions with a FERC Response that indicates that they have already been filed with FERC. Generating the XML now is out of the ordinary. |
| F003 | Some Filing validations are date effective. Therefore, Filing.FERCFilingDate is required. | Fail | The Filing cannot be validated because the Date Filed has not been provided. |
| F004 | Make sure the filing type selected for the Filing is "in effect". | Fail | Invalid Filing Type. You must create a new filing with a valid Filing Type, move the Tariff Record Versions over to it, and recreate the FERC Attachments. |
| F005 | Within a Tariff Database, there can be only one Filing filed where the Filing Type is "New" or "Refiled". | Fail | Invalid Filing Type - a "new" or "refiled" type of filing has already been filed with FERC. You must create a different filing with a valid Filing Type, move the Tariff Record Versions over to it, and recreate the FERC Attachments. |
| F006 | Within a Tariff Database, a Filing of any non-New and non-Refiled type cannot be filed until one has been filed where the Filing Type is "New" or "Refiled". | Fail | Invalid Filing Type - a "new" or "refiled" type of filing must be filed with FERC before you can file this Filing. You must create a different filing with a "new" or "refiled" Filing Type, move the Tariff Record Versions over to it, and recreate the FERC Attachments. |
| F007 | When making an Amendment filing, Filing.AssociatedFilingId is required. | Fail | When making an Amendment filing, you must specify the filing with which your filing is associated. |
| F008 | When making an Amendment filing, the associated Filing must have a status of "Filed". | Fail | When making an Amendment filing, the associated filing must have a status of "Filed" thus indicating that FERC has not yet acted upon it. |
| F009 | When making a Motion filing, Filing.AssociatedFilingId is required. | Fail | When making a Motion filing, you must specify the filing with which your filing is associated. |
| F010 | When making a Motion filing, the associated Filing must have a status of "Filed" or "Complete". | Fail | When making a Motion filing, the associated filing must have a status of "Filed" or "Complete" thus indicating that it is on file with FERC. |
| F011 | Tariff Database Title is required | Fail | The Tariff Database Title is missing. |
| F012 | Tariff Database Title cannot be longer than 100 characters | Fail | Tariff Database Title is longer than the 100 character maximum. |
| F013 | Filing Title is required | Fail | The Filing Title is missing. |
| F014 | Filing Title cannot be longer than 80 characters | Fail | Filing Title is longer than the 80 character maximum. |
| F015 | Filing Validation Email address is required | Fail | The Filing Validation Email address is missing. |
| F016 | Every attachment must include a description | Fail | One or more FERC Attachments are missing a Description. |
| F017 | Schema v1 requires that there is at least one attachment | Fail | FERC's eTariff XML schema requires that there be at least one FERC Attachment. |
| F018 | When making a Withdrawal filing, Filing.AssociatedFilingId is required. | Fail | When making a Withdrawal filing, you must specify the filing with which your filing is associated. |
| F019 | When making a Withdrawal filing, the associated Filing must have a status of "Filed". | Fail | When making an Withdrawal filing, the associated filing must have a status of "Filed" thus indicating that FERC has not yet acted upon it. |
| F021 | If the type of filing rules stipulate that a suspense motion response is required, then the question must be answered | Fail | You must specify for FERC whether or not suspended Tariff Record Versions should be made effective automatically after a suspension period. |
| F022 | If the type of filing rules stipulate that a filing fee is required, then a Payment Confirmation Code must be provided for the Filing | Fail | A payment confirmation code is required for this filing. |
| F023 | When making a Report filing, Filing.AssociatedFilingId is required. | Fail | When making a Report filing, you must specify the filing with which your filing is associated. |
| F024 | When making a Compliance filing, the associated Filing is optional, but if specified, the associated Filing cannot have a "Draft" status. | Fail | When making a Compliance filing, the associated filing, "<AssociatedFiling.DisplayName>" in this case, cannot have a status of "Draft" as this indicates that the associated filing has not been filed with FERC. |
| F025 | When making a Compliance filing, the associated Filing is optional, but if specified, the associated Filing should not have a "Draft" or "Filed" status. | Warning | When making a Compliance filing, the associated filing, "<AssociatedFiling.DisplayName>" in this case, should have a status of "Complete" as this indicates that FERC has acted on the associated filing. |
| F026 | Withdrawal Filing must contain zero FTRVs. | Fail | A withdrawal filing must not contain any Tariff Record Versions. |
| F027 | When making a Withdrawal filing, the associated Filing cannot be a withdrawal-type filing | Fail | When making a Withdrawal filing, the associated filing cannot itself be a Withdrawal filing. |
| F028 | Warn user if a Motion filing contains any FTRVs that relate to a TRV where content is present. | Warning | You cannot propose textual or content changes to a tariff within the context of a Motion filing. If this filing contains textual or content changes, they will not be sent to FERC in the XML. |
| F029 | Filing.AssociatedFilingId is unexpected when making NEW, REFILED, NORMAL, and CANCEL type filings. | Warning | When making a Normal, New, Refiled, or Cancel type of filing, an Associated Filing is not typically sent to FERC. You have associated this Filing with the Filing "<Filing.AssociatedFiling.DisplayName>". Please use caution in your submission of this Filing. |
| F030 | It is invalid for an amendment filing to have a compliance filing as its associated filing. | Fail | You have associated this amendment filing with compliance-type filing "<Filing.AssociatedFiling.DisplayName>". Amendment filings cannot amend compliance filings. |
| F032 | Option Codes must be provided in complete sets. This is straightforward for change type CHANGE. For change type NEW, FTRVs may appear in some option sets and not others, so NEW is omitted from this validation. For change type CANCEL, a TR could be cancelled in one change set and untouched in another, so CANCEL is omitted from this validation. Change types WITHDRAW and PRO FORMA is not subject to option set restrictions. | Fail | Option sets must be complete. If a filing includes an Option B, then every Tariff Record in Option A must also be in Option B. The same is true of Options C, D, and so on. This Filing violates this rule in that Option "<optionCode>" is incomplete. |
| F034 | Standard withdrawal filing warning. | Warning | This is a withdrawal type filing that has been setup to withdraw Filing "<Filing.AssociatedFiling.DisplayName>" in its entirety. Proceed with caution as submitting this filing to FERC could withdraw more than you had intended. |
| F035 | Optional attachments have not been provided. | Warning | Depending on the details of your filing, FERC may require the following attachments but none of them have been included in this filing: [list of optional attachments that are missing from the filing]. This could be completely normal or may indicate that you have left something out of your filing. |
| F036 | When making a Withdrawal filing, the associated Filing cannot be an amendment-type filing | Fail | When making a Withdrawal filing, the associated filing cannot itself be an Amendment filing. You must withdraw the original filing that is being amended. |
| F037 | For oil companies, a warning must be issued if an index rate change is being submitted and a derivation of ceiling level attachment has not been provided | Warning | It appears that you have chosen to file an index rate change. Please make sure you include (either as an attachment or within your Transmittal Letter) the required information regarding derivation of the ceiling level. (18 CFR § 342.3(b)) |
| F038 | For oil companies, a warning must be issued if a cost-of-service rate change is being submitted and a cost of service summary attachment has not been provided | Warning | It appears that you have chosen to file a cost-of-service rate change. Such a filing requires a showing that there is a "substantial divergence" between actual costs and the rate resulting from application of the index such that the carrier would not be able to "charge a just and reasonable rate." The filing must include cost, revenue, and throughput data as required by part 346. (18 CFR § 342.4(a)) |
| F039 | For oil companies, a warning must be issued if a settlement rate change is being submitted and a verified statement has not been provided | Warning | It appears that you have chosen to file a settlement rate change. Please make sure that you attach the required verified statement by the carrier that the proposed rate change has been agreed to by all current shippers. (18 CFR § 342.4(c)) |
| F040 | Verify that the Filing's payment confirmation coe matches the expected FERC-established format. | Fail | The payment confirmation code for Filing "<Filing.DisplayName>" is in the wrong format. It must start with eight digits, followed by a hyphen, followed by four more digits. For example, 12345678-1234. |
| F041 | It is invalid for an amendment filing to have a refiled filing as its associated filing. | Fail | You have associated this amendment filing with refiled-type filing "<Filing.AssociatedFiling.DisplayName>". Amendment filings cannot amend refiled filings. |
| F042 | A Filing cannot be associated with itself. | Fail | Filing "<Filing.DisplayName>" is associated with itself. |
| F043 | Filing Validation Email address cannot be longer than 100 characters | Fail | Filing Validation Email is longer than the 100 character maximum. |
| F044 | When making a Compliance filing, the associated Filing is optional. If one is not specified, warn the user that the Filing will be assigned a unique docket. | Warning | This compliance Filing is not associated with an earlier eTariff Filing. Therefore, FERC will assign it a unique docket number. |
| F045 | New, Refiled, Normal, Amendment, and Motion type filings must include at least one FTRV. | Fail | When making a Normal, New, Refiled, Amendment, or Motion type of filing, the Filing must contain one or more FTRVs. This Filing does not have any FTRVs. |
| F046 | Validate FTRV Proposed Effective Dates for "New" And "Refiled" type of Filing | Fail | When filing a New or Refiled type of filing, you must include at least one FTRV with a proposed effective date (even if you do not yet know the date you wish to propose). It is acceptable to FERC if the date of the filing submittal is used. |
| F047 | A CANCEL type Filing must have one and only one FTRV | Fail | A Cancel type Filing must include exactly one FTRV. This Filing has <Filing.FTRV.Count> FTRVs. |
| F048 | A CANCEL type Filing must have an FTRV of Record Change Type CHANGE | Fail | The FTRV in a Cancel type Filing must have a Record Change Type of "Change". This Filing's FTRV has a Record Change Type of "<Filing.FTRV.RCT.Description>". |
| F049 | Warn if the Effective Date of a CANCEL type Filing falls prior to any other FTRV.EffectiveDate in the TDB | Warning | The Effective Date of this Cancel type Filing is expected to be later than all other FTRVs in the Tariff Database. There is at least one other FTRV that falls later than <Filing.FTRV.EffectiveDate>. |
| F050 | Within a TDB with an Approved CANCEL type Filing, only Compliance type Filings are allowed and all Effective Dates within must fall on or prior to the date on which the TDB was cancelled. | Fail | Within a cancelled Tariff Database, only Compliance type Filings are allowed and all Effective Dates within must fall on or prior to the Tariff Database cancellation date. |
| R001 | Make sure Record Change Types of "New" are appropriate. | Fail | A Filed Tariff Record Version cannot be sent to FERC with Record Change Type of "New" because the Tariff Record was previously filed with FERC. |
| R002 | Make sure Record Change Types of "Change" are appropriate. | Fail | A Filed Tariff Record Version cannot be sent to FERC with Record Change Type of "Change" because the Tariff Record has not been previously filed with FERC. |
| R003 | Make sure Record Change Types of "Cancel" are appropriate. | Fail | You cannot cancel Tariff Record "<TR.DisplayName>" because it has already been cancelled in the Filing "<Filing.DisplayName>". |
| R005 | Validate Record Change Type for "New" And "Refiled" type of Filing | Fail | "Change", "Withdraw", and "Cancel" are not a valid Change Types for this filing. |
| R008 | FTRV ProposedEffectiveDate is required | Warning | The proposed effective date for Filed Tariff Record Version "<FTRV.DisplayName>" is missing. Filing this way sends FERC the message that you don't yet know the desired effective date. If this is not what you intended, you should enter a proposed effective date. Proceed with caution. |
| R009 | FTRV Effective Priority Order must be unique among Filed FTRVs under the same TR with the same effective date. | Fail | Regarding "<FTRV.DisplayName>": There is more than one version of this Tariff Record filed with an effective date of FTRV.ProposedEffectiveDate. In the event that FERC approves these, a unique priority must be assigned to each. |
| R057 | FTRV Effective Priority Order must be unique among FTRVs in a Filing under the same TR with the same Option Code. | Fail | FTRV "<FTRVx.DisplayName>" is not the only representation of Tariff Record "<FTRVx.TRV.TR.DisplayName>" in this Filing within Option "<FTRVx.TRV.OptionCode>". All such FTRVs must have unique Effective Priority values. |
| R010 | Validate Record Change Type for "Motion" type of Filing | Fail | "Change" is the only valid Change Type for this filing. |
| R011 | The Version value filed for a TRV must be unique. | Fail | Tariff Record Version "<FTRVx.TRV.DisplayName>" must be filed with a unique Version value. Version <FTRVx.TRV.Version> has been filed before or exists more than once within this Filing. |
| R012 | FTRVs in a Motion Filing can only propose a different effective date for FTRVs that are Suspended. | Fail | Filed Tariff Record Version "<FTRV.DisplayName>" is invalid in this filing because Tariff Record Version "<TRV.DisplayName>" isn't suspended in an earlier filing. |
| R013 | FTRVs in a Motion Filing must have an AssociatedFTRVId that points to a suspended FTRV from an earlier filing under the same TRV. | Fail | Filed Tariff Record Version "<FTRV.DisplayName>" must be associated with Tariff Record Version "<TRV.DisplayName>" which has been suspended in an earlier filing. |
| R017 | Withdraw FTRVs must have an FTRV.AssociatedFTRVId that points to an FTRV with an FTRVR of Pending or Suspended and belongs to the same TRV in an earlier Filing (use Filing.FERCFilingDate). | Fail | Filed Tariff Record Version "<FTRV.DisplayName>" must be associated with a Pending or Suspended Filed Tariff Record Version from an earlier filing. |
| R018 | Within non-Cancel type Filings, verify that Tariff Record binary content is present for non-section-based Tariffs and non-hierarchy-enforced, section-based Tariffs. Also omit Amendment-type Filings that have a Cancel-type Filing at the end of their amendment chain. | Fail | Tariff Record Version "<TRV.DisplayName>" has no content. |
| R019 | Within non-Cancel type Filings, verify that Tariff Record plain text content is present for non-section-based Tariffs and non-hierarchy-enforced, section-based Tariffs. Also omit Amendment-type Filings that have a Cancel-type Filing at the end of their amendment chain. | Fail | Tariff Record Version "<TRV.DisplayName>" has no plain text content. |
| R020 | Make sure a cancellation is not done for Tariff Records that have never been filed with FERC. | Fail | You cannot cancel Tariff Record "<TR.DisplayName>" because it has not been filed with FERC. |
| R021 | Verify that a section number / collation value being filed appears to be unique. | Warning | Tariff Record Version "<FTRV.TRV.DisplayName>" has been assigned a section number that is already in use by "<collision TRV.DisplayName>". Due to the complexity of this validation rule, this is noted as a warning. Please use caution in your submission of this Tariff Record Version. |
| R022 | Verify that a Tariff Record Version isn't being filed under a Tariff Record that has been cancelled. | Fail | Filed Tariff Record Version "<FTRV.DisplayName>" is invalid in this filing because Tariff Record "<TR.DisplayName>" has been cancelled in Filing "<Filing.DisplayName>". |
| R023 | For oil companies, a warning must be issued if any FTRV in the filing proposes an effective date less than 31 days from the FERC filing date. | Warning | Tariff Record Version "<FTRV.TRV.DisplayName>" has a proposed effective date that does not meet the Commission's standard notice period filing requirements in 18 CFR § 341.2(b). Make sure your filing materials meet the requirements for special permission for tariff publications issued on short notice. (18 CFR § 341.14(a)) |
| R024 | Within non-Cancel type Filings, TRV effective date should not fall prior to Filing Date. | Warning | You are requesting an effective date (<FTRV.ProposedEffectiveDate>) for Filed Tariff Record Version "<FTRV.DisplayName>" that falls prior to the Filing Date (<FTRV.Filing.FERCFilingDate>). |
| R025 | Verify that a TR isn't being cancelled more than once in a Filing. | Fail | Tariff Record "<TR.DisplayName>" is being cancelled more than once in this filing. |
| R026 | For Whole Document TRs, the FTRV TariffRecordContentType must match the content type of the associated TRV DBF, except in the case of withdrawals for which this is normal and expected. | Fail | The content for Tariff Record Version "<TRV.DisplayName>" was uploaded in <RTF/PDF> format. The "File as:" selection for Filed Tariff Record Version "<FTRV.DisplayName>" must match. |
| R027 | Validate that a TRV is filed only once with record change type "NEW" or "CHANGE" or "CANCEL", unless being subsequently filed in a MOTION filing. Omit WITHDRAWN FTRVs as, logically, these have not been filed. | Warning | Tariff Record Version "<TRV.DisplayName>" was previously filed in Filing "<secondary FTRV.Filing.DisplayName>" Generally, once a Tariff Record Version has been filed, submitting further changes would be done using a different Tariff Record Version that belongs to Tariff Record "<TRV.TR.DisplayName>". |
| R028 | It is out of the ordinary and may be incorrect to file a TRV in PDF format it is was most recently filed in RTF format. | Warning | Filed Tariff Record Version "<FTRV.DisplayName>" was recently filed in RTF format and you are proposing to file it in this filing in PDF format. Generally speaking, FERC encourages the filing of RTFs and discourages the filing of PDFs. Changing from RTF to PDF may raise eyebrows at FERC and could cause this part of your filing to be rejected. |
| R029 | Option Codes must be filed in consecutive alphabetic sequence. | Fail | Tariff Record Version "<FTRV.TRV.DisplayName>" has an Option Code "<FTRV.TRV.OptionCode>" but a Tariff Record Version belonging to the same Tariff Record Version is not present in this Filing with an Option Code "<FTRV.TRV.OptionCode minus 1 letter>". |
| R030 | Report Filings can only contain FTRVs with record change type of PRO FORMA | Fail | This type of filing can only include Filed Tariff Record Versions with Record Change Type of "Pro Forma". Filed Tariff Record Version "<FTRV.DisplayName>" has a Record Change Type of "<FTRV.RCT.Description>". |
| R031 | Record change type Pro Forma is not a true tariff proposal. As such, it is not subject to Option Set restrictions. | Warning | Pro Forma submissions are not true tariff proposals. It is not necessary to submit them first as an Option A, then as an Option B, etc. As FERC considers Option A to be the "primary" option, the safe play is to submit Pro Forma tariff records with an Option other than A. |
| R032 | Root TR must be filed with FERC when filing a non-root TR in a non-hierarchy enabled TDB or a non-root, sheet-based TR in a hierarchy enabled TDB. | Fail | Tariff Record Version "<FTRV.TRV.DisplayName> is part of Tariff "<TRV.TR.Tariff.Title>", however, the Tariff Record that represents this Tariff has not been filed with FERC and is not represented in this Filing. |
| R033 | Parent TR must be filed with FERC when filing a non-root, section-based TR in a hierarchy enabled TDB. | Fail | Tariff Record Version "<FTRV.TRV.DisplayName> is a child of Tariff Record "<TRV.TR.parentTR.DisplayName>", however, this Tariff Record has not been filed with FERC and is not represented in this Filing. |
| R034 | Tariff Record Version binary data cannot be larger than 10MB | Fail | The content for Tariff Record Version "<FTRV.TRV.DisplayName>" is too large. |
| R035 | For oil companies, a warning must be issued if any TRV in the filing contains the string "342.2(a)" | Warning | It appears that you have chosen to file initial rates justified by filing cost, revenue, and throughput data for Tariff Record Version "<FTRV.TRV.DisplayName>". Please make sure you attach the supporting data required by part 346. (18 CFR § 342.2(a)) |
| R036 | For oil companies, a warning must be issued if any TRV in the filing contains the string "342.2(b)" and it is a non-Embargo Filing | Warning | It appears that you have chosen to file initial rates supported by a sworn affidavit that the rate is agreed to by at least one non-affiliated person for Tariff Record Version "<FTRV.TRV.DisplayName>". Please make sure you attach the required affidavit. (18 CFR § 342.2(b)) |
| R037 | For oil companies, a warning must be issued if any TRV in the filing contains the string "342.4(b)" | Warning | It appears that you have chosen to file a market-based rate change for Tariff Record Version "<FTRV.TRV.DisplayName>". The title page of the tariff must include the specific Commission order pursuant to which the tariff is issued. (18 CFR § 342.4(b)) |
| R038 | For oil companies, an error must be issued if any FTRV in the filing proposes an effective date greater than 60 days from the FERC filing date. | Fail | Tariff Record Version "<FTRV.TRV.DisplayName>" is proposed to be effective more than 60 days after the filing date. Tariffs must be filed 60 or fewer days before the Effective date. (18 CFR § 341.2(b)) |
| R039 | Tariff Record Version plain text cannot be larger than 10MB. | Fail | The plain text content for Tariff Record Version "<TRV.DisplayName>" is too large. |
| R040 | FTRVs that have an AssociatedFTRVId cannot be associated with an FTRV that was rejected. | Fail | Filed Tariff Record Version "<FTRV.DisplayName>" is associated with Filed Tariff Record Version "<FTRV.AssociatedFTRV.DisplayName>", which was rejected in an earlier filing. |
| R041 | Verify that Tariff Record plain text content is non-blank. | Warning | The plain text content of Tariff Record Version "<TRV.DisplayName>" contains no printable characters. This can happen if the document consists of nothing more than an image, such as a map. This condition may result in a FERC warning or error when the filing is submitted. |
| R042 | Verify that FTRVs that are associated with other FTRVs have a common TR. | Fail | Filed Tariff Record Version (FTRV) "<FTRV.DisplayName>" is associated with another FTRV, namely "<FTRV.AssociatedFTRV.DisplayName>". These FTRVs belong to different Tariff Records. There are no known circumstances under which this is an appropriate association. |
| R043 | Validate Associated FTRV Id for "New" And "Refiled" type of Filing | Fail | Filed Tariff Record Version "<FTRV.DisplayName>" is associated with another Filed Tariff Record Version, but this is not valid for this type of filing. |
| R044 | The combination of a TRV's Description and Title should be unique across TRs within a TDB. | Warning | Generally, the combination of a Tariff Record Version's Description and Title must uniquely identify the record being filed. This Filing contains Tariff Record Version "<FTRV.TRV.DisplayName>", which could be confused with "<TRVx.DisplayName>". Submitting the Filing as is might result in a FERC rejection or instructive order to update the Description or Title to better distinguish these records. |
| R045 | Warn user if FTRVs that have an AssociatedFTRVId are associated with an FTRV that is pending, except in the case of withdrawals for which this is normal and expected. | Warning | Filed Tariff Record Version (FTRV) "<FTRV.DisplayName>" is associated with another FTRV whose FERC Response is "Pending". If the associated record has a status of "Pending" at FERC, submitting this Filing will cause the associated record's status in the eTariff Viewer to become OBE (overtaken by events). Proceed with caution as this may not be what you intend. |
| R046 | An FTRV in a non-oil industry Filing does not have an AssociatedFTRVId and there exists a Pending FTRV under the same TR. | Warning | Filed Tariff Record Version (FTRV) "<FTRV.DisplayName>" is not associated with another FTRV, yet one or more "Pending" FTRVs exist. If you intend to submit this FTRV as a replacement for one of the pending FTRVs, then you must associate this FTRV with the one you wish to replace. |
| R047 | In a section-based Tariff in a hierarchy-enabled Tariff Database an FTRV is associated with another FTRV under a Tariff Record that has children. | Warning | [1] Filed Tariff Record Version (FTRV) "<FTRV.DisplayName>" is associated with another FTRV. [2] Tariff Record "<FTRV.AssociatedTR.DisplayName>" has child Tariff Records. Submitting this Filing will cause the associated record to become moot and its status in the eTariff Viewer to become OBE (overtaken by events). This automatic update in FERC's software cascades to child Tariff Records also pending at FERC from earlier Filings. Under certain circumstances, this causes the child records to disappear...as if they hadn't been filed. Proceed with caution! |
| R048 | An FTRV cannot be associated with itself. | Fail | Filed Tariff Record Version "<FTRV.DisplayName>" is associated with itself. |
| R049 | For hierarchy-enforced, section-based Tariffs, issue warning if Tariff Record binary content is not present. NOTE that this validation is a variation of R018 and, as a result, is quite similar. Also omit Amendment-type Filings that have a Cancel-type Filing at the end of their amendment chain. | Warning | Tariff Record Version "<TRV.DisplayName>" has no content, which is OK if it is merely a placeholder parent of child sections. |
| R050 | For hierarchy-enforced, section-based Tariffs, issue warning if Tariff Record plain text content is not present. NOTE that this validation is a variation of R019 and, as a result, is quite similar. Also omit Amendment-type Filings that have a Cancel-type Filing at the end of their amendment chain. | Warning | Tariff Record Version "<TRV.DisplayName>" has no plain text content, which is OK if it is merely a placeholder parent of child sections. |
| R051 | [Tariff Cancel] An FTRV with Record Change Type CANCEL and a FERC Response of DRAFT must be a TRV-level FTRV and have an associated TRV. | Fail | Filed Tariff Record Version "<FTRV.DisplayName>" is a request to cancel Tariff Record "<FTRV.TR.DisplayName>". This FTRV must have an associated TRV, but it doesn't. To resolve this issue, delete the FTRV and recreate it by cancelling the Tariff again. |
| R052 | [Tariff Record Cancel] An FTRV with Record Change Type CANCEL and a FERC Response of DRAFT must be a TRV-level FTRV and have an associated TRV. | Fail | Filed Tariff Record Version "<FTRV.DisplayName>" is a request to cancel Tariff Record "<FTRV.TR.DisplayName>". This FTRV must have an associated TRV, but it doesn't. To resolve this issue, delete the FTRV and recreate it by cancelling the Tariff Record again. |
| R053 | Within a TDB with a Draft CANCEL type Filing, issue a warning if the Effective Date of an FTRV with Record Change Type of NEW, CHANGE, CANCEL, or PRO FORMA falls after the TDB cancellation. | Warning | Filed Tariff Record Version "<ThisFiling.FTRV.DisplayName>" has an Effective Date (<ThisFiling.FTRV.EffectiveDate>) that falls after the date on which this Tariff Database may be cancelled by Filing "<Fn.DisplayName>". |
| R054 | "Within a TDB with a Pending CANCEL type Filing, issue a validation failure if the Effective Date of an FTRV with Record Change Type of NEW, CHANGE, CANCEL, or PRO FORMA falls after the TDB cancellation. The one exception to this rule is an Amendment type Filing that is associated with the Pending CANCEL type Filing." | Fail | Filed Tariff Record Version "<ThisFiling.FTRV.DisplayName>" has an Effective Date (<ThisFiling.FTRV.EffectiveDate>) that falls after the date on which this Tariff Database is proposed to be cancelled by Filing "<Fn.DisplayName>". |
| R055 | For oil companies, all FTRVs with lower TRV.Version values must have EffectiveDates that fall on or prior to FTRV.EffectiveDate | Warning | Tariff Record Version "<FTRVx.TRV.DisplayName>" has a Version greater than FTRV "<TRVz.FTRV.DisplayName>", but its Effective Date falls prior. This scenario is non-standard for the oil industry. Proceed with caution. |
| R056 | Within Cancel type Filings, TRV effective date should not fall prior to Filing Date. | Fail | You cannot request an effective date (<FTRV.ProposedEffectiveDate>) for this Cancel type Filing that falls prior to its Filing Date (<FTRV.Filing.FERCFilingDate>). |
| S001 | Within a Filing, there can be no more than 200 FERC Attachments in any given Security Level. | Fail | You may supply no more than 200 FERC Attachments with the same Security Level. Within this Filing there are <n> FERC Attachments with Security Level "<security level>". |
| T001 | TRV Option Code is required for every TRV in the Filing | Fail | Option Code is missing from Tariff Record Version "<TRV.DisplayName>". |
| T002 | TRV Title is required on root Tariff Records. | Fail | Title is missing from Tariff Record Version "<TRV.DisplayName>". |
| T003 | TRV Description is required. | Fail | Description is missing from Tariff Record Version "<TRV.DisplayName>". |
| T004 | TRV-level FTRVs must include a version number. | Fail | Version is missing from Tariff Record Version "<TRV.DisplayName>". |
| T005 | TRV Title cannot be longer than 60 characters | Fail | The Title of Tariff Record Version "<TRV.DisplayName>" is longer than the 60 character maximum. |
| T006 | TRV Description cannot be longer than 25 characters | Fail | The Description of Tariff Record Version "<TRV.DisplayName>" is longer than the 25 character maximum. |
| T007 | TRV Version cannot be longer than 10 characters | Fail | The Version of Tariff Record Version "<TRV.DisplayName>" is longer than the 10 character maximum. |
| T008 | TRV NarrativeName cannot be longer than 254 characters | Fail | The Narrative Name of Tariff Record Version "<TRV.DisplayName>" is longer than the 254 character maximum. |
| T011 | Last TRV Processing attempt failed | Fail | TRV content processing for Tariff Record Version "<TRV.DisplayName>" failed in its last attempt and because of that it may contain incomplete or inaccurate information in its content, header, or footer. |
| T012 | TRV has unprocessed item in queue | Fail | TRV content processing is pending for Tariff Record Version "<TRV.DisplayName>" and because of that it may contain incomplete or inaccurate information in its content, header, or footer. |
| X002 | Optional attachments that are provided must include content | Fail | FERC Attachment "<AttachmentReferenceCode.Description>" has no content. |
| X003 | Optional attachments that are provided must include a file name | Fail | FERC Attachment "<AttachmentReferenceCode.Description>" is included in this filing but a file name has not been provided. |
| X004 | For some Attachments, FERC specifies a mandatory security level. For such attachments that are included in the filing, make sure that at least one is provided with the mandatory security level. | Fail | FERC Attachment "<Attachment.Description>" is an attachment of type "<Attachment.AttachmentReferenceCode.Description>". In order to include this type of attachment in your Filing, a FERC Attachment must be provided with security level "<Attachment.AttachmentReferenceCode.RequiredSecurityLevel.Description>". |
| Z002 | A Tariff Record (via its FTRV) can be present no more than once in an Option Set. | Warning | A Tariff Record should appear only once within an option set. Tariff Record "<TR.DisplayName>" is included within Option "<FTRV.TRV.OptionCode>" more than once. You appear to be working around a Commission restriction that would require multiple Filings to be submitted. WARNING: Any subsequent Filing in which an FTRV level association is made referring back to Tariff Record "<TR.DisplayName>" and Option "<FTRV.TRV.OptionCode>" in this Filing must include all FTRVs under the Tariff Record and Option. |
