ATT J20_P24 Technical Debt.xlsx

XLSX spreadsheet 26 KB Posted

Attached to
MCSC PDSS Support Services
Solicitation number
M6785424R7603
Issued by

About this file

This document is an Excel file that details technical debt and long-term corrective actions to eliminate production scripts (PROD24) in the GCSS-MC system. The file identifies 30 change requests that address various data quality and operational issues, such as resolving NIIN/SN/CG/Locator locks, automating PO/SO clean-up, addressing MRP workflow errors, and replacing temporary data fix scripts. Each change request provides a description of the issue, the proposed long-term solution, the impacted functionality, priority, severity, and status. The Excel file does not contain any information about a specific federal contract opportunity. It appears to be an internal document focused on technical debt and system enhancements for the GCSS-MC logistics platform.

View the file

Other files

File Type Posted
ATT J21_QA Matrix.xlsx XLSX spreadsheet
ATT J01 TO 01 PWS.pdf PDF
ATT J07 PPQ 060724.docx DOCX document
ATT J19 GCSS-MC RCA.pdf PDF
Conformed_24R760303 _070824.pdf PDF
ATT J02 Price Workbook.xlsx XLSX spreadsheet
ATT J16 GCSS-MC ECP DD1692-1.pdf PDF
ATT J21_QA Matrix.xlsx XLSX spreadsheet
ATT J05 QASP.pdf PDF
ATT J14 GCSS-MC CM Plan FY24.pdf PDF
AMD 02_24R7603_120724.pdf PDF
Conformed_24R7603_120724.pdf PDF
PDSS RFP AMEND 01 CONFORM 24R7603 20240515.pdf PDF
PDSS RFP AMEND 01 24R7603 20240515.pdf PDF
Show all 14

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Tech Debt (PROD24 CRs in SBM)

Color Key:
Long Term corrective action to eliminate a PROD24 script (TECHNICAL DEBT)
New PROD24 script to resolve detected data issue or error
Other (26199 creates Logging ISO expected Audit requirement, 20706 is actually a one-time data-fix vice a PROD24)
PriorityItem IdSubmit DateTitleDescriptionDev TeamPrioritySeverityStateFunctionalityTarget Environment
1CR0268013/5/23 8:19LT to resolve P-24 script NIIN/SN/CG/Locator locksLong Term (LT), permanent Corrective Action to resolve root issue currently addressed with PROD24 script created via CR023966; "As LogCom continually updates the NIIN/Serial Cost Group (PurpCode / CondCode) and moves NIIN/Serial around in Inventory Location, random errors are accumulating and increasing the frequency of NIIN/SN/CG/Locator locks, preventing further transactions. Create a PROD24 script to update/adjust locked / frozen NIIN/SN/CG/Locator combinations, and delete associated Pending Transactions." This is the code, package, program permanent corrective action to eliminate or alleviate the need for the data correction script.(None)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogInventory Management(None)
2CR0267993/5/23 8:18LT to resolve P-24 script Prod24 Script for XXMCPOSO Query and RetryLong Term (LT), permanent Corrective Action to resolve root issue currently addressed with PROD24 script created via CR023963; "Look for XXMCPOSO (Create a Sales Order from the Purchase Order - E-111) and produce a list of records that need attention to be given to Functional Tier 3, which usually require a Close PO and a COR. Script will also attempt a retry." This is the code, package, program permanent corrective action to eliminate or alleviate the need for the data correction script.(None)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogFinance(None)
3CR0267973/5/23 8:17LT to resolve P-24 script PO/SO Clean up Script CorrectionLong Term (LT), permanent Corrective Action to resolve root issue currently addressed with PROD24 script created via CR015924A defect that was missed during the course of development and testing was discovered upon the application of this script to Production. The clean up script improperly evaluates MRP transactions and attempts to close out associated PO's and SO's. As a result, the script in its current state is unusable and must be updated to properly evaluate MRP transactions." This is the code, package, program permanent corrective action to eliminate or alleviate the need for the data correction script.(None)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogFinance(None)
4CR0267953/5/23 8:17LT to resolve P-24 script XXMCFT_ - Anything ShippedLong Term (LT), permanent Corrective Action to resolve root issue currently addressed with PROD24 script created via CR023962; "MRP Records (XXMCFTE or XXMCFTA) stuck in Workflow on the step "Anything Shipped?" require a simple Retry to get moving again. We average about (5) per day." This is the code, package, program permanent corrective action to eliminate or alleviate the need for the data correction script.(None)(None)(None)CR VerificationWorkflow(None)
5CR0267933/5/23 8:16LT to resolve P-24 script POAPPRV - Unable to ReserveLong Term (LT), permanent Corrective Action to resolve root issue currently addressed with PROD24 script created via CR023964; "Script will look for PO Approvals that have a Response of Unable to Reserve and resubmits them." This is the code, package, program permanent corrective action to eliminate or alleviate the need for the data correction script.(None)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogFinance(None)
6CR0267913/5/23 8:14LT to resolve P-24 script Incomplete RequisitionsLong Term (LT), permanent Corrective Action to resolve root issue currently addressed with PROD24 script created via CR023965; "Script that detects Purchase Orders not created but the Requisition was created and Approved with the Launch CREATEPO also completed. User gets an intermittent issue where the CREATEPO does not detect the Requisition Line when it launches, but it is available later." This is the code, package, program permanent corrective action to eliminate or alleviate the need for the data correction script.(None)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogFinance(None)
7CR0267893/5/23 8:12LT to resolve P-24 script to generate 900 Responses to PO after outageLong Term (LT), permanent Corrective Action to resolve root issue currently addressed with PROD24 script created via CR025560; "Script which can be used identify PO Changes in the POAPPRV Workflow waiting to Receive a Response from DAI. These usually occur during planned/unplanned outages. Using the CUSRO of the script, a list would be generated of all qualified PO Changes. That list will be cross referenced with DAI to determine which were Approved (Response 900) thru the Product Owner. The script would then have the list, provided by the PO, of SDN’s added to the CURSOR to move these Workflow along to completion and execute any and all steps as if the Response of Approved was received. With a result of the Workflow being completed, and no longer showing as in flight/in process." This is the code, package, program permanent corrective action to eliminate or alleviate the need for the data correction script.(None)2. Adverse Effect Without WorkaroundS2 - Moderate to Minor ImpactCR VerificationWorkflow(None)
8CR02539710/14/22 17:24Workflow Fails to Find Source of SupplyAbout 200 times per year, OEOH Workflow errors at Activity Steps 'EXECUTE X-125', 'FIND_SOS'. Add function or activity step such that, when it fails at 'FIND_SOS', initiat a Retry at that step to continue. When complete, inactivate TA-105 PROD24 section 3.64.Functional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogWorkflow(None)
9CR02539410/14/22 17:21Completely Retire/Expire MI Items Not in RelationshipAbout 3,000 times each year, MI items have their relationship to the PEI as expired, but the MI item is not fully expired or retired. Add trigger or functionality to 1) validate all relationships are to Retired PEIs and 2) Retire or Expire the MI. When complete, inactivate TA-105 PROD24 section 3.26.Functional Team (1)4. InconvenienceS3 - Minor to No ImpactProduct BacklogInstall Base(None)
10CR0237174/1/22 15:21Retire MIs with no active, valid RelationshipsModification Instructions (MI's) are active and valid in GCSS-MC with no Relationship; Create a trigger on the Relationship Table, when an MI has no active, valid Relationships - Retire the MI.
When there is an IB Instance retired which has a MI Relationship, providing that is the only Relationship active and valid for that MI, the MI should automatically be retired at the same time. There is a 'on demand' PROD24 script to effect this retirement - this CR will render that PROD24 script (3.26) as no longer required.(None)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactCR VerificationInstall Base(None)
11CR0170235/16/19 20:01Long term solution to replace the script in PROD - AE1BM_SUPER_SCRIPT_no_I125.sqNeed a long term solution to replace this script - CODE NAME: AE1BM_SUPER_SCRIPT_no_I125.sql. DATA ISSUE PURPOSE: BM Trailer Reprocess. EXECUTION FREQUENCY: Daily. RCA / LONG TERM RESOLUTION: . IN PROD24: Y. PROACTIVE/ REACTIVE: . Description / Comments: This script reprocesses a redlined AE1/BM trailer.Interfaces Team3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc Mgmt(None)
12CR0170195/16/19 19:58Long term solution to replace the script in PROD - REPROC_BA.sqlNeed a long term solution to replace this script - CODE NAME: REPROC_BA.sql. DATA ISSUE PURPOSE: BA Trailer Reprocess for ZBE Will Build Failure. EXECUTION FREQUENCY: As Needed. RCA / LONG TERM RESOLUTION: . IN PROD24: Y. PROACTIVE/ REACTIVE: . Description / Comments: This script reprocesses a redlined BA trailer where a ZBE DIC was not created for a will build document.Functional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc Mgmt(None)
13CR0170055/16/19 19:49Long term solution to replace the script in PROD - PO_FIX.sqlNeed a long term solution to replace this script - CODE NAME: PO_FIX.sql. DATA ISSUE PURPOSE: PO Lines Script. EXECUTION FREQUENCY: Daily. RCA / LONG TERM RESOLUTION: . IN PROD24: Y. PROACTIVE/ REACTIVE: . Description / Comments: This script finds all PO Lines with a NULL in the SIGNAL_CODE field, and adds it and the SUPPADD from the Document Header record.Functional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc MgmtPSS & PROD
14CR0169875/16/19 19:33Long term solution to replace the script in PROD - XXMC_WSH_SerialNumbers.sqlNeed a long term soltion to replace this script - CODE NAME: XXMC_WSH_SerialNumbers.sql. DATA ISSUE PURPOSE: Add Missing Serail Numbers to the MTL_SERAIL_NUMBERS_TEMP Table. EXECUTION FREQUENCY: As Needed. RCA / LONG TERM RESOLUTION: . IN PROD24: Y. PROACTIVE/ REACTIVE: . Description / Comments: This change finds instances where there an existing WSH_DELIVERY_DETAILS record’s TRANSACTION_ID points to a Serial Number(s) in the MTL_SERIAL_NUMBERS table and there is not matching SERAIL_NUMBER(s) on the MTL_SERIAL_NUMBERS_TEMP table. It then adds the Serial Number(s) missing.Functional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc Mgmt(None)
15CR0169835/16/19 19:30Long term solution to replace the script in PROD - QUERY_AND_FIX_NSN_ORDERED (DONeed a long term soltion to replace this script - CODE NAME: QUERY_AND_FIX_NSN_ORDERED (DOC MGMT). DATA ISSUE PURPOSE: NSN's with alphanumeric characters examples below:

4720 01 187 6911 SX

5120 01 313 6937 ED

5310 01 457 3292 SX

Causing Doc Mgmt Issues. Update these to the FSC||NIIN based on the NIIN if found in the PLM Attributes Table, removing the last 2 digits.

EXECUTION FREQUENCY: AS NEEDED - Weekly. RCA / LONG TERM RESOLUTION: Haven't been able to isolate where they are coming from. IN PROD24: YES. PROACTIVE/ REACTIVE: BOTH. STATIC: NFunctional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc Mgmt(None)
16CR0169775/16/19 19:27Long term solution to replace the script in PROD - A_TO_C_MISSING_PARTY_ID_FIXNeed a long term soltion to replace this script - CODE NAME: A_TO_C_MISSING_PARTY_ID_FIX. DATA ISSUE PURPOSE: RICE PROVIDED - Purpose Code Xfer A > C issue. Typically Non Serialized IB Instances. EXECUTION FREQUENCY: AS NEEDED. RCA / LONG TERM RESOLUTION: RICE Issue. IN PROD24: YES. PROACTIVE/ REACTIVE: REACTIVE. STATIC: NFunctional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc MgmtDEV, CM, PSS & PROD
17CR0169755/16/19 19:25Long term solution to replace the script in PROD - UPDATE_INSTANCE_OWNER_TO_ACCTNeed a long term soltion to replace this script - CODE NAME: UPDATE_INSTANCE_OWNER_TO_ACCT. DATA ISSUE PURPOSE: Data fix script for Install Base where IB Instance has been corrupted. EXECUTION FREQUENCY: AS NEEDED. RCA / LONG TERM RESOLUTION: Haven't been able to isolate what is causing the issue. IN PROD24: YES. PROACTIVE/ REACTIVE: REACTIVE. STATIC: NFunctional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc MgmtDEV, CM, PSS & PROD
18CR0169735/16/19 19:24Long term solution to replace the script in PROD - UPDATE_INSTANCE_OWNER_TO_INVNeed a long term soltion to replace this script - CODE NAME: UPDATE_INSTANCE_OWNER_TO_INV. DATA ISSUE PURPOSE: Data fix script for Out Of Sync situations between Inventory and IB; also corrupt IB Instances. EXECUTION FREQUENCY: AS NEEDED. RCA / LONG TERM RESOLUTION: Haven't been able to isolate what is causing the issue. Inventory to IB Updates still an Issue. IN PROD24: YES. PROACTIVE/ REACTIVE: REACTIVE. STATIC: NFunctional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc MgmtDEV, CM, PSS & PROD
19CR0169715/16/19 19:23Long term solution to replace the script in PROD - SUBMIT_1538131_1Need a long term soltion to replace this script - CODE NAME: SUBMIT_1538131_1. DATA ISSUE PURPOSE: Oracle Data Fix Script for all NON Serialized IB Interface Errors. EXECUTION FREQUENCY: AS NEEDED. RCA / LONG TERM RESOLUTION: Oracle Issue, Inventory Txn's and updating Install Base IN PROD24: YES. PROACTIVE/ REACTIVE: REACTIVE. STATIC: YFunctional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc MgmtDEV, CM, PSS & PROD
20CR0169555/16/19 19:11Long term solution to replace the script in PROD - Modify LKH.sqlNeed a long term solution to replace this script running PROD - CODE NAME: Modify LKH.sql. DATA ISSUE PURPOSE: Modify LKH value in Document Management Trailer (Note: Executing this script may impact how other fields display in Document Management.). EXECUTION FREQUENCY: AS NEEDED. RCA / LONG TERM RESOLUTION: N/AIN PROD24: YES. PROACTIVE/ REACTIVE: BOTH.Functional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc MgmtDEV, CM, PSS & PROD
21CR0169495/16/19 19:05Long term solution to replace the script in PROD - Update Rev Flag.sqlNeed a long term solution to replace this script running PROD - CODE NAME: Update Rev Flag.sql. DATA ISSUE PURPOSE: Modify Review Flag for a specific trailer in Document Management. (Note: Use of this script may cause changes to how other fields display when the targeted SDN is queried within Document Management.). EXECUTION FREQUENCY: AS NEEDED. RCA / LONG TERM RESOLUTION: N/AIN PROD24: YES. PROACTIVE/ REACTIVE: BOTH.Functional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc MgmtDEV, CM, PSS & PROD
22CR0169455/16/19 18:58Long term solution to replace the script in PROD - Insert_missing_BA_AS1.sqlNeed a long term solution to replace this script running PROD - CODE NAME: Insert_missing_BA_AS1.sql. DATA ISSUE PURPOSE: Produce missing AS1's / AE1-BA's, when Shipping Transaction indicates that a line has been interfaced, but the corresponding trailers have failed to post in Document Management.. EXECUTION FREQUENCY: AS NEEDED. RCA / LONG TERM RESOLUTION: N/A - Need Matt to confirm the scope (if any) of work being performed towards a long term resolution.IN PROD24: YES. PROACTIVE/ REACTIVE: BOTH.Functional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc MgmtDEV, CM, PSS & PROD
23CR0169435/16/19 18:56Long term solution to replace the script in PROD - REPROC.sql"Need a long term solution to replace this script running PROD - CODE NAME: REPROC.sql. DATA ISSUE PURPOSE: Prepare errorered or partially processed Document Management trailers for reprocessing. [Note: The current version in the Prod 24 is outdated and is no longer in use. This has been replaced by a similar script that fulfills the same role conceptually, but allows for: (1) reprocessing of errored/failed trailers outside of status 'BM' and (2) utilizes current best practice by targeting an individual trailer for reprocessing based on Document History ID, rather than all trailers for an entire SDN.]. EXECUTION FREQUENCY: AS NEEDED. RCA / LONG TERM RESOLUTION: N/A
CR016153IN PROD24: YES. PROACTIVE/ REACTIVE: BOTH. "Functional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc MgmtDEV, CM, PSS & PROD
24CR0169415/16/19 18:55Long term solution to replace the script in PROD - COR_ITSM.sqlNeed a long term solution to replace this script running PROD - CODE NAME: COR_ITSM.sql. DATA ISSUE PURPOSE: Insert COR into Document Management to close out transactions where cancellation / receipt entry will not be possible.. EXECUTION FREQUENCY: AS NEEDED. RCA / LONG TERM RESOLUTION: N/AIN PROD24: YES. PROACTIVE/ REACTIVE: BOTH.Functional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc MgmtDEV, CM, PSS & PROD
25CR0169335/16/19 18:26Long term solution to replace the script in PROD - 02.2017 - Unlock Update.sqlNeed a long term solution to replace this script running in PROD - CODE NAME: 02.2017 - Unlock Update.sql. DATA ISSUE PURPOSE: Unlocks redline trailer in Document Management. EXECUTION FREQUENCY: AS NEEDED. RCA / LONG TERM RESOLUTION: Possible future modifications to "redline" logic. IN PROD24: YES. PROACTIVE/ REACTIVE: BOTH.Functional Team (1)3. Adverse Effect With WorkaroundS2 - Moderate to Minor ImpactProduct BacklogDoc MgmtDEV, CM, PSS & PROD
26CR0203731/4/21 9:26Sales Order / Shipping Transaction Status DiscrepancyCancelled Sales Order lines are incorrectly reflecting as Backordered when queried from Shipping Transactions form. If user attempts to launch pick release from Shipping Transactions form, a move order will not be generated. Inaccurate statuses create confusion for users querying records to perform Pick/Pack/Ship process. Reported SDN's have been removed from the unit's DASF via multiple avenues. There are no specific steps to replicate the status mismatch. No manual actions can be performed in the application to resolve the issue. No Prod24 script exists for addressing confirmed cases.Functional Team (1)2. Adverse Effect Without WorkaroundS3 - Minor to No ImpactProduct BacklogDoc MgmtDEV, CM, PSS & PROD
27CR02024211/25/20 11:48Data Script for E-175 errorsAn enhanced data script is needed to address E-175 errors. Flexibility is needed to address a wide range of errors affecting purpose code transfers A>C / C>A, as well as assignment and custody transactions. Prod24 script 3.48 can be used as a template to process errored transactions. Data script should have the ability to be ran on a single Instance Id, batch name, batch id, etc.Cross Product Team2. Adverse Effect Without WorkaroundS1 - Major ImpactAwaiting Sprint AssignmentInstall BaseDEV, CM, PSS & PROD
28CR0312634/22/24 9:24Update PROD24 Script 3.87: MRP_SUPPLY_SDN and DOC UpdatePROD24 script 3.87 flips D6T receipt from Transaction Type MRP (M) to Supply (S). Update script to remove following condition as it is not required:

AND X.mrp_qty < X.mrp_rec

Since the D6T does not belong to MRP, this condition is not required to move the trailer to supply. Upon update of 3.87 script, updates to GCSS-MC TA.105_PROD24 document is required.

(None)2. Adverse Effect Without WorkaroundS2 - Moderate to Minor ImpactProduct BacklogPerformance/Optimization(None)
29CR0261991/6/23 8:45PROD24 Logging and OBIEE Dashboarda) Update / Enhance PROD24 scripts to include logging

(this will be accomplished by GOC-SI)

COLUMN_NAME DATA_TYPE NULLABLE DATA_DEFAULT COMMENTS

GOC_LOG_ID NUMBER NOT NULL SEQUENCE

SOURCE_TABLE_NAME VARCHAR2(25) NOT NULL

SOURCE_TABLE_UNIQUE_ID NUMBER NOT NULL

PROD24_SCRIPT_NUMBER VARCHAR2(5) NOT NULL --ex. 3.01 REQUESTED_BY VARCHAR2(30) --Name of person requesting, like SME/FE or T3-SI Daily

ADDITIONAL_UK_1 VARCAHR2(100)

ADDITIONAL_UK_2 VARCAHR2(100)

ADDITIONAL_UK_3 VARCAHR2(100)

ADDITIONAL_UK_4 VARCAHR2(100)

ACTION_DESCRIPTION VARCAHR2(100) NOT NULL --ex. Pulled from LOV based on PROD24 Script Number

COMMENT VARCAHR2(2000)

ACTION_BY NUMBER NOT NULL FOREIGN KEY to FND_USER_ID

ACTION_DATE DATE NOT NULL

--Supporting ID's when they can be added for optimal logging

SDN VARCHAR2(14) NOT NULL DEFAULT 'N/A'

REQ_LINE_ID NUMBER FOREIGN KEY to PO_REQUISITION_LINES_ALL PO_LINE_ID NUMBER FOREIGN KEY to PO_LINES_ALL OE_LINE_ID NUMBER FOREIGN KEY to OE_ORDER_LINES_ALL UMX_USER_ID NUMBER FOREIGN KEY to FND_USER_ID IB_INSTANCE_ID NUMBER FOREIGN KEY to CSI_ITEM_INSTANCES

b) Create OBIEE Dashboard for 'Data Maintenance Script Execution', tie, link or otherwise reference for Audit use to enable Auditing to be able to look up if data has been updated by execution of an authorized PROD24 script, what authority granted the execution, what was updated, when, where, and why.

GOC-SI will draft the creation of the table structure and supporting elements with generic documentation in the PROD24 GOC-SI will update all active PROD24 scripts to add a INSERT where we output the line information

GOC-SI will draft the test plan and coordinate test/migration efforts (just like all other PROD24 products)(None)4. InconvenienceS3 - Minor to No ImpactProduct BacklogData QualityDEV, CM, PSS & PROD
30CR0207062/22/21 13:04PROD24 to remove Obsolete TAMCN from CategoriesData in the TAMCN, Model, and ID value sets is not currently accurate, valid and maintained, and requires development of a one-time programmatic or executable solution to update based on input from authoritative data sources.
Functional Team (1)2. Adverse Effect Without WorkaroundS2 - Moderate to Minor ImpactAwaiting Sprint AssignmentData QualityDEV, CM, PSS & PROD

File details come from the government source that posted it. Updated .