Difference between revisions of "V1.5 SP 13.0"

From FPDS-NG
Line 40: Line 40:
 
WSDLs will not be updated to remove DUNS-related tags, but the tags will be disabled from user entry/submission and users must begin using the UEI tag (FPDS: <genericString02>; FAADC: <UEI>) to submit a vendor for transactions.
 
WSDLs will not be updated to remove DUNS-related tags, but the tags will be disabled from user entry/submission and users must begin using the UEI tag (FPDS: <genericString02>; FAADC: <UEI>) to submit a vendor for transactions.
  
−
Both FPDS and FAADC Atom Feeds will be updated so that DUNS values are not sent in DUNS-related tags. All DUNS-related tags will appear as null/empty in the Atom Feeds.</td>
+
Both FPDS and FAADC Atom Feeds will be updated so that DUNS values are not sent in DUNS-related tags. All DUNS-related tags will appear as null/empty in the Atom Feeds.
 +
 
 +
As applicable entity information will only be displayed on FAADC V1.1 Atom Feeds and beyond, the V1.0 Assistance and V1.0 Assistance Deleted Atom Feeds shall be decommissioned following the SP13 deployment schedule.
 +
 
 +
All FPDS and FAADC records finalized on 4/2/2022 or prior that contain a UEI (DUNS) value, shall be appended with a value 'D&B' for the 'Entity Data Source' data element tag. This update shall be made internally, and downstream users who plan to populate this field should append the same value on applicable records within their system.</td>
  
 
<td align="center">Yes</td>
 
<td align="center">Yes</td>
Line 80: Line 84:
 
<td>‘SAM Exception’ label update in FPDS/FAADC
 
<td>‘SAM Exception’ label update in FPDS/FAADC
 
    
 
    
−
<td>After completion of the DUNS to UEI transition, SAM Exception entities will be required to go to SAM to generate a UEI value, for record creation purposes in FPDS. The ‘SAM Exception’ label will be updated to ‘FAR 4.1102 Exception’ on all GUI screens, validation rules, and documentation. Web services and Atom Feed are not impacted.
+
<td>After completion of the DUNS to UEI transition, SAM Exception entities will be required to go to SAM to generate a UEI value, for record creation purposes in FPDS.
 +
 
 +
<ul>
 +
<li>‘SAM Exception’ label will be updated to 'FAR 4.1102 Exception’ for versions 1.1-1.5 in FPDS. Associated help content would be updated. XML tags on web services and the atom feed would not be changed.</li>
 +
<li>‘SAM Exception’ label will be updated to '2 CFR Part 25 Exception’ for versions 1.0-1.1 in FAADC. Associated help content would be updated. XML tags on web services and the atom feed would not be changed.</li>
 +
</ul>
 
</td>
 
</td>
  

Revision as of 23:58, 9 March 2022

Schedule

DescriptionStart Date End Date
Beta DeploymentMarch 11, 2022March 11, 2022
Government Acceptance Testing March 21, 2022March 25, 2022
Production Deployment April 2, 2022April 2, 2022

Document Changes

DocumentationChanges Required
XML SpecificationsNo
Web ServicesYes
Data DictionaryYes
NASA Specific Data DictionaryNo
Use Case SummaryYes
Validation RulesYes
ezSearchYes
Atom FeedsYes
Online HelpYes
User ManualYes

SPR Listing

SPR #Enhancement/ProblemSolutionImpact to Users and Integrators

IAEDEV-60364 / IAEDEV-60365

FPDS and FAADC Phase 3 UEI Enhancements This is the third and final phase of the DUNS to UEI transition for both FPDS and FAADC systems. This will make the UEI element a mandatory field. All instances of the DUNS data element and associated values will be removed and the UEI (SAM) field will be renamed to ‘Unique Entity ID’ (short: ‘UEI’) from both systems, and the (GUI Screens, GUI Services, validation rules, documentation, etc.).

WSDLs will not be updated to remove DUNS-related tags, but the tags will be disabled from user entry/submission and users must begin using the UEI tag (FPDS: <genericString02>; FAADC: <UEI>) to submit a vendor for transactions.

Both FPDS and FAADC Atom Feeds will be updated so that DUNS values are not sent in DUNS-related tags. All DUNS-related tags will appear as null/empty in the Atom Feeds.

As applicable entity information will only be displayed on FAADC V1.1 Atom Feeds and beyond, the V1.0 Assistance and V1.0 Assistance Deleted Atom Feeds shall be decommissioned following the SP13 deployment schedule.

All FPDS and FAADC records finalized on 4/2/2022 or prior that contain a UEI (DUNS) value, shall be appended with a value 'D&B' for the 'Entity Data Source' data element tag. This update shall be made internally, and downstream users who plan to populate this field should append the same value on applicable records within their system.		 Yes

IAEDEV-64036 / IAEDEV-64037

Decommissioning of the D&B API for both FPDS and FAADC systems The Dun & Bradstreet API used to retrieve new SAM Exception entities (previously not found in FPDS/FAADC) will be decommissioned and a new SAM API will be used to retrieve all SAM Exception entity information using a UEI (SAM) value, instead of UEI (DUNS). No

IAEDEV-59966

ezSearch ‘ICD’ tab Search Issues UEI (SAM) values cannot be used to search in the ‘ICD’ tab of ezSearch. The system will be updated to ensure UEI values are indexed and searchable from the ezSearch ‘ICD’ tab. Yes

IAEDEV-62921

‘SAM Exception’ label update in FPDS/FAADC After completion of the DUNS to UEI transition, SAM Exception entities will be required to go to SAM to generate a UEI value, for record creation purposes in FPDS.
  • ‘SAM Exception’ label will be updated to 'FAR 4.1102 Exception’ for versions 1.1-1.5 in FPDS. Associated help content would be updated. XML tags on web services and the atom feed would not be changed.
  • ‘SAM Exception’ label will be updated to '2 CFR Part 25 Exception’ for versions 1.0-1.1 in FAADC. Associated help content would be updated. XML tags on web services and the atom feed would not be changed.
 No

IAEDEV-59967

UEI loading issue on records referencing an IDV There are two issues related to UEI (SAM) on IDVs/Awards with referenced IDVs:
  1. When a record is created from a template (that contains a referenced IDV), the original UEI value remains on the new record after record creation.
  2. UEI does not appear on a record after selecting the referenced IDV through the ellipsis button.
Both defects will be resolved so that UEI is displaying correctly in all scenarios.		 No

IAEDEV-62064

Other Transaction Awards and Other Transaction IDVs can be created with the same PIID There is no validation rule which prevents Other Transaction Awards and Other Transaction IDVs from being created with the same PIID. A validation rule will be implemented to enforce the PIID to be unique between Other Transaction Awards and Other Transaction IDVs. Yes

IAEENH-1018 / IAEDEV-57560

Updated Category 1 IT PSCs Category 1 IT Product Service codes have been updated and will be implemented in FPDS. FPDS PSC Codes Crosswalk will be updated with the new information. Yes

IAEENH-1071 / IAEDEV-64340

IAEPOL DFARS Case 2022-D012, New Qualifying Country - Lithuania Per DFARS case 2022-D012, Lithuania will be added to the list of qualifying countries associated with ‘Country of Product / Service Origin’ validation rule DoD9H03. The validation rule will be updated to the language below:
  • If the "Country of Product / Service Origin" is 'Australia', 'Austria', 'Belgium', 'Canada', 'Czech Republic', 'Denmark', 'Egypt', 'Estonia', 'Germany', 'Finland', 'France', 'Greece', 'Israel', 'Italy', 'Japan', 'Latvia', ‘Lithuania’, 'Luxembourg', 'Netherlands', 'Norway', 'Poland', 'Portugal', 'Slovenia', 'Spain', 'Sweden', 'Switzerland', 'Turkey', or 'United Kingdom of Great Britain and Northern Ireland' the "Place of Manufacture" can only be 'Mfg Outside U.S -Qualifying Country (DOD only)' or 'Not a Manufactured End Product'.
 Yes
Retrieved from "https://fpds.gov/wiki/index.php?title=V1.5_SP_13.0&oldid=4874"