Difference between revisions of "V1.4 SP 19.0"

From FPDS-NG
Line 45: Line 45:
  
 
<b>The Contracting Agency on the Modification cannot be different than the Contracting Agency on the ‘Transfer Action’ document.</b>
 
<b>The Contracting Agency on the Modification cannot be different than the Contracting Agency on the ‘Transfer Action’ document.</b>
 +
 +
3. Requirements 1 and 2 apply to all Award and IDV types.
  
 
</td>
 
</td>

Revision as of 09:51, 20 February 2013

Schedule

DescriptionStart Date End Date
BETA Installation Friday March 15, 2013Friday March 15, 2013
Functional Qualification Testing Monday March 18, 2013Friday March 22, 2013
Installation in ProductionFriday March 29, 2013Friday March 29, 2013

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesNo
Data Dictionary No
NASA Specific Data DictionaryNo
Use Case SummaryNo
Validation RulesNo
ReportingNo
Online HelpNo
Computer-Based TrainingNo
User ManualNo

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators
FPDSHD-72999 Civilian and DoD users can successfully create modifications to contracts when the base belongs to another agency without a Transfer Action. 1. On a record without a “Transfer Action”, for operations ‘create’, ‘update’, ‘isComplete’, ‘approve’, ‘correct’:

FPDS-NG shall restrict users from creating a Modification when “Contracting Office Agency ID” of the Base record does not match “Contracting Office Agency ID” of the Modification being created, except when “Reason for Modification” is ‘Transfer Action’.

The following new Validation Rule shall fire:

The Contracting Agency on the Modification cannot be different than the Contracting Agency on the Base document unless “Reason for Modification” is ‘Transfer Action’.

2. On a record with a “Transfer Action”, for operations ‘create’, ‘update’, ‘isComplete’, ‘approve’, ‘correct’:

FPDS-NG shall restrict users from creating a Modification when “Contracting Office Agency ID” of the “Transfer Action” Modification does not match “Contracting Office Agency ID” of the Modification being created.

The following new Validation Rule shall fire:

The Contracting Agency on the Modification cannot be different than the Contracting Agency on the ‘Transfer Action’ document.

3. Requirements 1 and 2 apply to all Award and IDV types.

No
FPDSHD-113057 Users cannot correct the New Base after a Transfer Action if there are existing mods after it. In Progress No
FPDSHD-113670 The user is reporting data accuracy issue when correcting base contracts that have Rerepresentation modifications. In progress No
FPDSIRB-173 The values for the "National Interest Action" (NIA) and "Local Area Set Aside" (LASA) are defaulted as "Select One" on error records. 1. FPDS-NG shall retain the user provided values for NIA and LASA on the base errored out documents.

2. FPDS-NG shall retain the user provided values for NIA and the propagated value of LASA on the modification errored out documents.

3. The following documents shall be addressed: 

   Purchase Order
   Delivery/Task Order
   Definitive Contract
   BPA Call
   FSS
   GWAC
   BOA
   BPA Call 
   IDC

4. The resolution applies the FPDS-NG actions - Create and Update.

No
FPDSHD-84802 The user reported a conflict between the posted requirement state and the behavior of the Referenced IDV Modification Number on the Other Transaction documents. In progress No
FPDSHD-108437 Modifications to the Other Transaction Order, Agreement and IDV are validating the PSC code although it propagates from the base. 1. FPDS-NG shall not validate the PSC code on the modifications for the following documents: 
   Other Transaction IDV
   Other Transaction Order
   Other Transaction Agreement

2. The resolution applies to the FPDS-NG actions - Create, Update and Correct.

No
FPDSHD-91657 The Place of Performance Zip Code is retained when the Place of Performance Country Code is corrected from USA to a foreign country. In progress No
Retrieved from "https://fpds.gov/wiki/index.php?title=V1.4_SP_19.0&oldid=4297"