{"text_format":"1","workbook":"xlsx","n_sheets":5,"sheets":["Release Information","Product Fixes","Product Enhancements","Impacted Objects","Schema Changes"],"not_rendered":{"charts":0,"images":3,"macros":1,"external_links":1,"defined_names":11,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Release Information","index":0,"n_rows":54,"n_cols":3,"rows_kept":54,"cut":false,"hidden":false,"merged":[[10,2,10,3],[4,1,4,3],[5,2,5,3],[6,2,6,3],[8,2,8,3],[9,2,9,3],[7,2,7,3],[26,1,26,3],[39,2,39,3],[36,1,36,3],[41,2,41,3],[38,1,38,3],[40,2,40,3],[35,1,35,3],[31,1,31,3],[32,1,32,3],[29,1,29,3],[28,1,28,3],[53,1,55,3],[42,2,42,3],[43,2,43,3],[46,1,46,3],[47,2,47,3],[52,1,52,3],[44,2,44,3],[48,2,48,3],[50,2,50,3],[22,2,22,3],[23,2,23,3],[25,1,25,3],[11,2,11,3],[12,2,12,3],[18,1,18,3],[21,2,21,3],[16,2,16,3],[14,1,14,3],[15,2,15,3],[19,2,19,3],[20,2,20,3]]}
[]
[]
[]
[]
[null,"Release Details"]
[null,"Solution Name","Ramco Aviation Solution "]
[null,"Release Initiated By ","Ramco Aviation Product Team"]
[null,"Shipment To","Release 5.8"]
[null,"Solution Release","Release 5.8"]
[null,"Base Release Number","EAR5.8.8.0"]
[null,"Last Released BASE HRMS CU ","HCM_Magna1.1.16"]
[null,"Release Type","Regular Shipment"]
[null,"Update Effected on","WEB, APP and RM Layer"]
[]
[null,"System Requirements"]
[null,"Hardware","As per recommended COTS"]
[null,"Software","As per recommended COTS"]
[]
[null,"Shipment Details"]
[null,"Published SFTP Details ","Refere Release Mail"]
[null,"Shipment Size","25 MB"]
[null,"No. of Packages",1]
[null,"Expected System Downtime*","00:30 Hrs"]
[null,"Release Date/Time","01 Nov 2019 20:00 Hrs"]
[]
[null,"Prerequisites"]
[null,"1) Successful deployment of the release EAR5.8.7.1\n2) Release package EAR5.8.8.0 should be deployed only using the deployment tool (Release Version : D5.5.0.9 or more)"]
[]
[null,"Installation Sequence"]
[null,"Not Applicable"]
[]
[null,"Installation Instructions"]
[null,"(1) Download the Product Release version mentioned above in \"Base Release Number\" field.\n\n(2) Download the latest \"ICMS_release_hdr.sql\" from the above SFTP under folder \"/BAVN-58FS-Common/Regular/<RespectiveRelease>\" , Place the  file in specified local path as specified in Ramco Deployer User Guide.\n\n(3) Deploy the Release Package mentioned above in \"Base Release Number\" field using the deployment tool(version - D5.5.0.9). Refer the Ramco Deployer User Guide.\n\n(4) Please refer Configuration & Settings Section for Manual Deployment or Post Installation Steps if applicable.\n"]
[]
[]
[null,"Configuration & Settings "]
[null,"Not Applicable"]
[]
[null,"Other Details:"]
[null,"Distribution Information"]
[null,"Distributed To","Release 5.8"]
[null,"Copy To","Sam Jacob, Anuradha R, Mangai K, Shanthi Krishna, Off-shore Project Leads,  On-site Support Personnel "]
[null,"Support Contact Person","Vinoth Kumar K"]
[null,"Support Contact Person Mail ID","vinothkumark@rsi.ramco.com"]
[null,"Support Contact Hours","09:00 Hrs to 19:30 Hrs"]
[]
[null,"Authoring Details"]
[null,"Prepared By ","Vinoth Kumar K"]
[null,"Prepared Date/ Time","01 Nov 2019 18:00 Hrs"]
[null,"Reviewed By","QA Team"]
[null,"Reviewed Date/ Time","01 Nov 2019 19:00 Hrs"]
[]
[null,"*Notes:"]
[null,"1. All Time  should be read in Indian Standard Time (IST) in 24 hour format. \n2. Shipment  will be available in the published SFTP site for 5 Days from the date of release. \n3. Please report installation errors, if any, log a ticket in rTrack.\n4. Expected system down-time mentioned is tentative and it may vary according to the system configuration."]

{"sheet":"Product Fixes","index":1,"n_rows":198,"n_cols":10,"rows_kept":198,"cut":false,"hidden":false,"merged":[]}
[]
["Key","Component/s","Summary","Sequence and error encountered","Root Cause \nCategory","Root Cause Remarks","Resulted In Data \nCorruption/ Resolution","Follow-up Issue Id","What was Fixed?","Test and Verification Details"]
["AHFG-19461","Work reporting hub>Parts Hub","When checking the parts availability you are unable to identify the UOM. Once the part is requested the UOM is populated leading to the incorrect amount regularly being ordered","In parts hub when checking part availability the screen displays the QTY available but not the UOM. This means tradespeople are unsure how much to order as they do not know what it unit of measure it comes in.","Primary Defect","UOM is not fetching in multi line on clicking check part availability in Parts hub","No - No",null,"Logic handled to fetch UOM in multi line on clicking check part availability in Parts hub","Data: \n1. Launch Parts Hub for the package VP000113-2019 \n2. Check the part availability for the part 0-0440-4-0011:36361 \n3. The quantity and UOM are shown correctly \n\nEnvironment: FS ST"]
["AHFG-18954","Work Monitoring and Control","Panasonic Performance Report","Panasonic Performance Report \n\nRead the mail conversation for more details.","Secondary Defect","Performance tunning needs to be handled to resolve the issue","No - No",null,"Performance Tunning handled to resolve the issue. \n:with sqltmp is replaced by temp table.","Verified the fix and it is working fine. \nPerformance issue has been resolved on confirm estimates \nGo to Estimates screen \nEstimate parts and resources against the tasks \nSelect multiple tasks and confirm the estimates and Performance issue should not be there. \nPerformance issue has been resolved on confirmation of estimates."]
["AHFG-18894","Work Monitoring and Control","Work Estimates screen-Performance very slow","Work Estimates screen-Performance very slow","Secondary Defect","performance tunning needs to be handled to resolve the issue","No - No",null,"key columns not used and the same has been handled.","Performance issue has been resolved on search of parts in parts requirement tab. \nPerformance tuning handled to rectify the issue."]
["AHFG-18944","Work Monitoring and Control","Deadlocks in WMC","objectname=AVNAPPDB_TEMPDB.dbo.wmc_wohld_hold_val_In_temp indexname=wmc_wohld_hold_val_In_temp_IDX - Deadlock in this table occured on 24/09 \n","Primary Defect","Performance issue observed when concurrent users closes the package from WMC","No - No",null,"Identified the blocking process and fine tuned the queries to have better performance","Post deployment of fixes, with 3 users tried closing task from WMC page. System processed the data without any deadlocks"]
["AHFG-18745","Work Monitoring and Control","Discrepancy shows in different status in WMC screen and AME hub or AME screen. Lee is trying to close as it is showing as completed in WMC page","Discrepancy shows in different status in WMC screen and AME hub or AME screen. Lee is trying to close it as it is showing as completed in WMC page \n\nIn AME hub screen discrepancy LP-001054-2019/2 is showing as under resolution whereas in WMC screen it is showing as completed","Primary Defect","Incorrect validation is getting fired when trying to close the discrepancy from WMC against package1 which was deferrred with out corrective action and added to new package.","Yes - Only Fix Provided",null,"Logic modified to skip the validation when trying to close the discrepancy from WMC against package1 which was deferrred with out corrective action and added to new package.","Data: \n1. Launch the package VP011279-2019 in AME Hub and create a discrepancy \n2. Defer the discrepancy \n3. Close the discrepancy in Manage Work Assignments and Reporting \n4. Create and defer a discrepancy for the aircraft JS-1819 and add the discrepancy to a new package \n5. Close the discrepancy in the first package \n\nEnvironment: FS ST"]
["AHFG-18878","Work Monitoring and Control","On search in WMC, if search results contain Facility work orders, system displayed error and not grouped under work center","On search in WMC, if search results contain Facility work orders, system displayed error and not grouped under work center","Primary Defect","on generation of XML double quotes not handled properly FOR Part number","No - No",null,"Part number with double quotes handled now while generating XML","Data: \n1. Launch Manage Work Assignments and Reporting \n2. Search for facility work orders \n3. The search results are shown without errors \n\nEnvironment: FS ST"]
["AHFG-18744","Work Monitoring and Control","Performance issue while updating the timesheet status","Deadlocks occurred on the below statement: \n\n\"UPDATE A \nSET mtsua_timeshtstatus = tlgea_tmsht_status \nFROM cmn_mtsua_timshet_upd_auth_tmp A \nJOIN flog_tlgea_emp_actuals_dtl WITH (NOLOCK) \nON mtsua_guid = '2' \nAND mtsua_ouinstance = tlgea_slfsrc_ouinstance \n--AND mtsua_doctype = 'AME' /*deadlock issues for AHFG-3496*/ \nAND mtsua_docno = tlgea_techlog_no \nAND mtsua_trackid = tlgea_task_track_id \nAND mtsua_taskno = tlgea_task_no \nAND mtsua_empno = tlgea_emp_no \nAND mtsua_bookingid = tlgea_booking_id \n--AND mtsua_modeflag = 'U' /*deadlock issues for AHFG-3496*/ \nWHERE mtsua_guid = '2' \n--AND tlgea_booking_id IS NOT NULL /*deadlock issues for AHFG-3496*/ \n--AND ISNULL(mtsua_timeshtstatus,'FR') NOT IN ('CN','RJT') /*deadlock issues for AHFG-3496*/ \nAND ISNULL(mtsua_timeshtstatus,'FR') IN ('FR','CF','AU') \nAND mtsua_doctype = 'AME' \nAND mtsua_modeflag = 'U' \" \n","Primary Defect","Performance issue while updating the time sheet status.","No - No",null,"Performance issue while updating the time sheet status.","After deploying the fixes, took a timesheet which is pending for authorization and tried authorization from multiple sessions. System authorized the timesheet successfully"]
["AHFG-18987","Work Monitoring and Control","Search criteria in Manage work assignment and reporting doesn't work properly when clock is on for on user and authorized without end date and time","Search criteria in Manage work assignment and reporting doesn't work properly when clock is on for on user and authorized without end date and time. \n\nSame Records gets repeated on every search. \n\nplease update the end clock with 1 min so that it doesn't appear anymore","Primary Defect","Due to incorrect logic, System is fetching the records in multiline which are not falling under selected date criteria","Yes - Only Fix Provided",null,"Fix has been provided to fetch the records in multiline which should have date range between selected date criteria","Data: \n1. Launch Manage Work Assignments and Reporting for the aircraft 1000 \n2. Search with the desired planned start date and end date \n3. The search results that fit the search criteria are shown \n\nEnvironment: FS ST"]
["AHFG-19005","Work Monitoring and Control","System lists duplicate lines in Part Estimates tab for Task and Part # combination. While recording Part Estimates, system displays error","System lists duplicate lines in Part Estimates tab for Task and Part # combination. While recording Part Estimates, system displays error \"Unable to proces row # \"17\".Part # \"R6HG738YB\" and its attributes are duplicated. Please enter a different part # or change attributes\" \n\nSWO#: 10000811 & 10000624","Primary Defect","Validation trigerred due to the incorrect logic,Warranty specified as Null and No but due to incorrect logic system considered both as same and validation trigerred,It should not display an error message when warranty is selected as NO and blank.","No - No",null,"Validation trigerred due to the incorrect logic,Warranty specified as Null and No against 17th and 18th lines but due to incorrect logic system considered both as same and validation trigerred,It should not display an error message when warranty is selected as NO and blank. \nLogic modified for warranty Null and No- validation will not be displayed when warrannty is selected differently","1)Selected the lines and on hit save validation error message is not trigerred. \n2)Modified the warranty for both the lines as NO and validation trigerred \n3)Estimated another task with the same details and selected the warranty as No for both the lines and on save validation trigerred \nVerified the fix for the same data as mentioned in the actuals and fix is working fine. \nFST"]
["AHFG-18795","Work Center","While trying to search for an employee in Workcenter->View Employee Information screen, system is listing search result when searched with Employee # but not listing when searched with Employee Name","While trying to search for an employee in Workcenter->View Employee Information screen, system is listing search result when searched with Employee # but not listing when searched with Employee Name","Primary Defect","Found that extra space exists after the last name","No - No",null,"Found that extra space exists after the last name.Trim function handled in the employee name # search to ignore the space","Data: \n1. Launch Maintain Employee Information \n2. Search for employee name with *nal* \n3. The search results are shown correctly \n4. Launch View Employee Information \n5. Search for employee name with *nal* \n6. The search results are shown correctly \n\nEnvironment: FS ST"]
["AHFG-19363","Time Tracking","Attendance rounds to nearest minute today within system. Customer needs to stop the rounding all together and let the clock in and out time be real time.","Customer needs to have the rounding stop and let the system to use real time not round to nearest minute.","Primary Defect","Rounding off for both clockin and clockout needs to be removed to show the actual real time","No - No",null,"Rounding off for both clockin and clockout was removed to show the actual real time.","Env: FS ST \nFor Top Aces, all the Time Tracking parameters of rounding off [common-ars], provision was given to enter a value '0'. On doing so, exact In-Time and Out-Time entry can be displayed. \n\nThis changes is handled only for Top Aces and nothing affects the product."]
["AHFG-18741","Time Tracking","Cannot see the entries in the Process Timesheet Accounting. There is data records for the Timesheets that have been entered but nothing","Authorized Timesheet Records then went to Process Timesheet Accounting and no drop downs are available screen in blank","Primary Defect","This is the first instance of time sheet processing, Logic was facilitating only if previous process period exists. Logic being modified to support loading of FB,Year,Period","No - No",null,"This is the first instance of time sheet processing, Logic was facilitating only if previous process period exists. Logic being modified to support loading of FB,Year,Period","Env: http://bavnwarcnv04/Extui/extui/vwrt/LaunchPanel.htm \n\nFinancial Year: FY18 \nFiancial Period: MAR18 \n\n1) For initial processing in ‘Process Timesheet Accounting’ screen there is a logic failure on loading the combo. Currently, it was corrected. \n2) Firstly, timesheet accounting can happen only once in month (31st May_see the first screenshot). \n3) Created a numbering type ‘TA’ and mapped against Timesheet Accounting transaction. \n4) Again created a numbering type ‘TE’ and mapped against Timesheet Entry transaction. \n5) Now on process of timesheet accounting a new voucher with fresh status will be displayed \n6) Authorize it and respecting accounting information will be displayed in the Acc. Info tab. \n\nVery Important Note: Rates are defined only for the skill code ‘01’. Rates needs to be defined for other skill codes as-well. Please check."]
["AHFG-19321","Technical Records","Against ACSA-575, Icon is not displayed in 'Fleet Overview' screen, also Chinese task description is not supported","Icon is not displayed in 'Fleet Overview' screen, also Chinese task description is not supported","Primary Defect","Backend image location path did not have the icon logo for the Condition column in Fleet Overview screen. Conversion failure while showing the description in the Next Due Tab.","No - No",null,"The image icon has been copied to the location to which the backend logic is referring to in the fleet hub code. \n\nUploaded the image/logo used to the common path for the user to upload.","Tested and verified in FS server \n1. Configuration Management > Technical Records > Fleet Overview \n2. Checked that logos are available in the Condition column \n3. Checked that the descriptions of the tasks in Next Due Tab did not show any junk values."]
["AHFG-18995","Technical Records","Ramco fleet overview is showing incorrect data in the hours remaining field of deferred items.","Ramco fleet overview is showing incorrect data in the hours remaining field of deferred items. \nInstead of showing how many hours are remaining until action must be taken, it is showing total aircraft hours when the item will be due.","Primary Defect","For the Discrepancy Task,Where the triggering parameter of Discrepancy is Usage based, system was showing the threshold value in remaining value column instead of showing the remaining value in Fleet Overview screen.","No - No",null,"Now logic has been changed and system showing the remaining value correctly.","Tested and verified in FS server \n1. Configuration Mgmt. > Technical Record > Fleet Overview \n2. For an aircraft reg# checked the records in Deferred Items \n3. For a Deferral# checked its corresponding Rem. Value \n4. Discrepancy Mgmt > Discrepancy processing > View discrepancy \n5. Kept the Record Status as 'Deferred' and searched on the basis of the aircraft reg# \n6. Searched for the Discrepancy and checked its \"Rem. Days/FH/FC' \nthe system showed the correct Rem. Value in Fleet overview screen."]
["AHFG-19521","Tech records hub","Aircraft Status displaying as \"U\" for the aircraft record 6789, even though aircraft status value is blank in Update status & Condition for Aircraft Records","Aircraft Status displaying as \"U\" for the aircraft record 6789, even though aircraft status value is blank in Update status & Condition for Aircraft Records. Both the value should match","Secondary Defect","Aircraft Status was hard allocated to a given value.","No - No",null,"If the Aircraft Status was saved blank, it was automatically viewed as 'U' which was hard allocated . The input aircraft status was rightly mapped","Data: \n1. Create a new aircraft OUHG with aircraft status \n2. Aircraft status is shown in Edit Aircraft Record \n3. If a blank value is saved then aircraft status is shown as blank \n\nEnvironment: FS ST"]
["AHFG-19454","Supplier Order Based Invoice","Freight Charge added in Order Based Invoice Accounted twice","Freight Charge added in Order Based Invoice Accounted twice","Secondary Defect","The reported issue occurred as the system logic to process account postings for Freight Charge has been handled twice for the line level Charage/Discount added.","No - No",null,"The reported issue has been fixed by modifying the system logic to process account postings for Freight Charge only once added in line level.","Server: FS-ST \n1. Created an Order Based Invoice SI-001254-2019 and added Freight Charges to the invoice at line level. \n2. Saved and authorized the invoice and verified that the account postings for Freight Charges has gone correctly without any double posting."]
["AHFG-18758","Supplier Order Based Invoice","i can not create maintain invoice because the currency not match with account code","when i trying to create SPO from maintain invoice it comes to this message: Account code not defined for the Usage Id \"GSE/TOOLS SERVICE\" and Currency Code \"USD\" combination. Please define the same to proceed. Account code retrieval failed.)","Secondary Defect","When create Invoice for NOGR Purchase Order having Order level add to stock TCD in foreign currency, system expects PO accounting usage should be mapped with Transaction currency account code instead of checking for the base account definition.","No - No",null,"The reported issue has been fixed by modifying the system logic to retrieve account code based on transaction currency and if definition not available for the same, system will look for the base currency definition.","Server: FS - ST \n1. Created an Adhoc PO with NO GR Option and also added TCD at PO level which is Add to stock. PO-001639-2019 \n2. Retrieved the PO and created Supplier Order Based Invoice. SI-001257-2019 \n3. The Invoice was authorized without any error. \n4. Verified the posting for the Accounting usage and it has posted taking the conversion rate even though the PO and Invoice is in foreign currency. \n"]
["AHFG-19578","Supplier Order Based Invoice","Get details taking more time in Maintain Invoice","Metnioned query has taken long time and caused delay in other processes \n\n[AVNAPPDB].[dbo].[GI_Intg_Poinv_Fetch_Sp] \n\nwith gr_qty_tmp ( acc_guid, acc_ouid, acc_grno, acc_grlineno, acc_acceptedqty, acc_rejectedqty, acc_quarqty , acc_pendingqty, acc_accpamt ,acc_date )--Added:IUCH-1388 as ( select @guid, itm_ouid, itm_grno, itm_grlineno, sum(isnull(ac.giac_accp_qty,0)), sum(isnull(srl.gisld_visu_rej_qty,0)+isnull(srl.gisld_totinsp_rej_qty,0)+isnull(tmp.itm_rejectedqty,0)), sum(isnull(ac.giac_quar_qty,0)), sum(isnull(ac.giac_pend_insp_qty,0)), sum(isnull(ac.giac_acct_amt,0)) ,max(convert(date ,giac_accp_date))--,103))--Added:IUCH-1388 --->AHBE-7658 from gi_intg_poinv_process_tmp tmp with(nolock), gi_gisld_srl_lot_dtl srl with(nolock), gi_giac_accp_info ac with(nolock) where tmp.guid = @guid and ac.giac_rcpt_no = tmp.itm_grno and ac.giac_rcpt_no = srl.gisld_rcpt_no and ac.giac_rcpt_line_no = tmp.itm_grlineno and ac.giac_rcpt_line_no = srl.gisld_rcpt_lineno and ac.giac_srllot_lineno = srl.gisld_srllot_lineno and ac.giac_rcpt_type = tmp.itm_grtype and ac.giac_rcvd_partno = tmp.itm_itemcode and ac.giac_accp_linestatus = 'A' --Added: Priyadharsini.R / AAIC-2993 / 27 June 2012 and ac.giac_rcpt_ou = tmp.itm_ouid and ac.giac_rcpt_ou = srl.gisld_rcpt_ou group by itm_ouid,itm_grno,itm_grlineno ) update tmp set tmp.itm_quarnqty = gr.acc_quarqty, tmp.itm_acceptedqty = gr.acc_acceptedqty, tmp.itm_rejectedqty = gr.acc_rejectedqty, tmp.itm_invamt = gr.acc_accpamt, tmp.itm_invqty = gr.acc_acceptedqty - isnull(tmp.itm_invoicedqty,0), tmp.itm_pendinginsp = gr.acc_pendingqty ,tmp.itm_grdate = acc_date--Added:IUCH-1388 from gi_intg_poinv_process_tmp tmp, gr_qty_tmp gr where tmp.guid = @guid and tmp.guid = gr.acc_guid and tmp.itm_grno = gr.acc_grno and tmp.itm_grlineno = gr.acc_grlineno and tmp.itm_ouid = gr.acc_ouid and tmp.itm_exptype <> 'RC'","Primary Defect","Performance Issue in Maintain Invoice Get details logic","No - No",null,"Tuning done to modify the code, such that permanent temp tables are introduced to use the appropriate index.","Tested & verified in AMP server and ensured Get details logic is working fine."]
["AHFG-19165","Supplier Order Based Invoice","System does not validating for Tax addition in case of Automatch Failed invoices and force matched","System does not validating for Tax addition in case of Automatch Failed invoices and force matched. \nsimulated for both Expense off variance accounting and Supplier receivable variance accounting","New Scenario","The reported issue occurred as the system validation for VAT addition has not been handled in Match Invoice screen.","No - No",null,"The reported issue has been resolved by handled the validation for VAT addition check in Match Invoice screen on click of Match button.","Server: FS-ST \n1. Created an Order based invoice SI-001256-2019 without adding any tax to it and saved it in Auto Match Failed Status. \n2. Retrieve the invoice in Match Invoice screen and matched it without any error. \n3. Since the validation for VAT addition is customer specific, it has been handled through backend set option and cannot be tested in base server."]
["AHFG-19228","Supplier Order Based Invoice","Unable to invoice PO # PO2014872","System is trying to validate the account usage mapping with the header FB mapping in invoice screen which is meant for the credit account and not for the debit postings for the account usage selected. \n\nThe PO has FB # L018-NJSP, against which the usage id PREPAYMENTS - IT has been correctly mapped \n\nHowever system is expecting the same mapping for invoice FB L008-JSPL which is incorrect \n\n","New Scenario","The reported issue occurred as the system validation for accounting usage provided in the multiline of Maintain invoice page check is based on the Invoice Finance book instead of Purchase order's Expense to Finance Book.","No - No",null,"The reported issue has been fixed by modifying the system validation for accounting usage in Maintain invoice page based on the Purchase order's Expense to Finance Book if provided else validate for Invoice Finance Book.","Server: FS - ST \n1. Created an Adhoc PO with a different \"Expense To\" FB and selected an accounting usage which is defined only in the Expense To FB. PO-001640-2019 \n2. Received the Goods and verified the posting for Inter FB accounting. GIGPO-000977112019 \n3. Created an Order Based Invoice in the Purchasing FB SI-001258-2019 and authorized it without any error."]
["AHFG-18525","Supplier Inquiry","Unable to change the due date for an authorized invoice","Unable to change the due date for an authorized invoice, though the setoption to Allow modification of Due date/Discount date for Authorized Supplier Documents is set as Yes in Finance Setup > OU Parameter Setup > Set Finance Process Parameters","Secondary Defect","When Payment schedule screen enhanced for due date change after the document authorization, logic has not been handled properly on enter of \"Payment Term\" field. Due to which reported error occurred.","No - No",null,"The system logic has been handled properly on enter of \"Payment Term\" field from Payment schedule screen for due date change after the document authorization.","Tested and verified in the following manner, \n> For a particular Supplier #, through AP INQUIRY screen selected an Authorized Order Based invoice for amending the Pay term. \n> Amended the Payterm along with Modification of due date which system computed on click of Enter after the new Pay term and ensured the same is saved successfully. \n> In Supplier Regular Pay batch ensured the Due date of the Order invoice is fetched with the Due date amended as in step 2. \n> Likewise, for a particular Supplier #, through AP HUB screen selected an Authorized Order Based invoice for amending the Pay term. \n> Amended the Payterm along with Modification of due date which system computed on click of Enter after the new Pay term and ensured the same is saved successfully. \n> In Supplier Regular Pay batch ensured the Due date of the Order invoice is fetched with the Due date amended as in step 5. \n\nServer - FS Server"]
["AHFG-19518","Sundry Payment","Provide Analysis Code. Context : Component-SNP, OU-HeligoOU, BU-HCPLBU, FB-HCPFB, DocNo-PYT-000041-19, TranType-PM_SPV & ActCode-420079 & CostCenter-HELIGO-GEN. Fianance Postings Failed at line# 0.","while creating sundry payment voucher for bank charges by applying cgst and sgst on saved getting issue mention in the summary. \nrefer the enclosed screen shot","Secondary Defect","As rounding off method is not defined for the Tax Code and Tax Variant, system rounded offal the total Taxable income up to 4 digits during calculation. Due to this a difference of $-.01 is coming b/w Total DR & CR amounts","No - No",null,"System logic has been handled to round off the Tax Amount to 2 decimals when there is no definition for rounding off in the specify tax attributes.","Server: FS ST \n1. Created a Sundry Payment Voucher SPV-000609-2019 for bank charges and added CGST and SGST to it. \n2. Authorized the voucher without any error regarding analysis code. \n3. Verified the account posting."]
["AHFG-19444","Stock Transfer","Error when editing Stock Tranfer","Error when editing Stock Transfer Part # 101-01175","Primary Defect","System wrongly validating the stock is not available in the particular warehouse/zone/bin combination due to preferred condition not selected in stock transfer","No - No",null,"Logic has been modified , system correctly check the available quantity in particular warehouse/zone/bin combination","Data: \n1. Launch Edit Inter Warehouse Stock Transfer for ST-001209-2019 \n2. Edit the stock transfer \n3. The changes are saved successfully \n\nEnvironment: FS ST"]
["AHFG-19369","Stock Transfer","System allowed to create multiple transfer document for the same part – serial /lot combination","System allowed to create multiple transfer document for the same part – serial /lot combination in a concurrent scenario.","Primary Defect","System allowed to create multiple transfer document for the same part – serial /lot combination in a concurrent scenario. Validation not exist in the routine which is being called for authorization process.","No - No",null,"Validation has been introduced to check enough available qty is available in stock in the authorization process.","Launch the Manage Intra warehouse stock transfer . \nStock Management->Stock Transfer->Manage Intra Warehouse Stock Transfer \nCreated the part # 01-0309-00:41364 SN# aa1478965 ware house 0123 ST-001304-2019 , \nFetch the record for creation for the same part – serial with multiple login. \nHit the Create and Authorize Transfer, \ngot the success message for \"dmuser\" and Error validation message for another login user. \nFix working fine \n\" Validation appears when try to do the same part – serial /lot combination transaction in other user\" \n"]
["AHFG-19122","Stock Transfer","System allowed to shortclose the Stock transfer even though issue was confirmed","System allowed to shortclose the Stock transfer even though issue was confirmed. Need a consistency error to stop this.","Primary Defect","During stock transfer issue confirmation , system failed to update the transfer status as closed,. due to which system allowed to short close the transfer document","No - No",null,"preventive validation has been introduced during short close of stock transfer document to restrict the short close if all the parts are issued","Data: \n1. Launch a stock transfer which is in authorized status \n2. Confirm the stock transfer issue for the stock transfer \n3. Short close the stock transfer \n4. An error is correctly shown \n\nEnvironment: FS ST"]
["AHFG-18981","Stock Status Conversion","Seems like De-allocation failed after cancellation of Stock Conversion SCV0002982","Issue 1: Seems like De-allocation failed after cancellation of Stock Conversion SCV0002982 \n\nIssue 2: Similar issue reported for RD-NB2112-01, SN LS0016. Serial found allocated for a cancelled SVC0003332 \n\n","Primary Defect","The de-allocation has not happened for Cancelled Stock Conversion documents. The parts are still allocated to the same stock conversion Doc (Cancelled)","No - No",null,"Validation added as a preventive actions to check if part is having stock correction as last updated document even when the document is cancelled. \n","Data: \n1. Cancel the stock conversion SSC-000606-2019 \n2. The part is deallocated successfully \n\nEnvironment: FS ST"]
["AHFG-19027","Stock Maintenance","For standard cost valuation parts with differential standard cost -part reference change results in incorrect stock value","For standard cost valuation parts with differential standard cost -part reference change results in incorrect stock value. \n* Consider parts P1 and P2 with valuation method as standard cost valuation. \n* Standard cost of P1 =0 stnadard cost of P2 = 10. \n*Through part reference change when part # P1 is changed to part # P2, iTs results in incorrect stock valuation. \n\nThis causes the mismatch between reporting \ntable and Stock. \n","Primary Defect","Part reference change has been done for the parts which are having different std. cost (old part with zero cost and new part has value). System copies the cost (zero cost) to the new part from the old part. Post the PSC","No - No",null,"Validation introduced to restrict the “Part Reference Change” and “Part and Serial Reference Change” for the standard cost part if the exiting part and the modified part has different standard cost.","Data: \n1. This has to be taken up as a change request in the product \n2. Data patch has been provided for the corrupted records in Panasonic environment \n\nEnvironment: FS ST"]
["AHFG-18992","Stock Maintenance","No finance posting for Automated Stock Correction on approval of cycle count results","The following set options are enabled. \nGenerate Stock Correction for discrepant stock in Authorized status? is set to Yes. If data gets refreshed, please configure set options as per screenshot. \n\nCreated a cycle count plan and cycle count sheet for Warehouse # DRW, \nGenerated positive and negative discrepancy for around 188 lines. \nConfirmed Cycle Count Sheet. \nAuthorised Cycle Count Results. \n\nOn Authorisation of Cycle Count results, system generated a stock correction in Authorised status. \n\nThe part value has increased / decreased because of the discrepancy but there was no GL posting for the stock correction, Ideally, this should have gone to \"Stock Take\" Account Usage and \"Darwin\" costing usage based on Set Options. \n\nTake for Ex; Part # 13066; Lot # ALOT-136975-2019 \nThis Lot # was previously 4 Qty with total value of 126.81. \n\nIn Cycle Count, count Qty was recorded as 1. \nIn Stock Correction # generated on approval of Cycle count results, the correction qty is shown as -3 but value is blank. \n\nIn the stock inquiry, the total value has gone down from 126.81 to 31.70 \n\nIn the GL Postings, for Stock Correction #, there is no posting at all. \n\nThis defect need to be resolved at the earliest. \n","Primary Defect","The computation of correction value not handled based on the correction qty and the system value. Due to which postings not triggered.","No - No",null,"Logic handled to compute the correction value based on the system value, system quantity and the correction value.","Data: \n1. Set option Generate Stock Correction for discrepant stock in Authorized status? is set to Yes \n2. Create a cycle count plan and cycle count sheet \n3. Create a positive and negative discrepancy \n4. Confirm and authorize Cycle Count Sheet and Cycle Count Results \n5. Stock correction is generated in Authorized status \n6. The part value has increased/decreased because of the discrepancy and the GL postings were found against the Stock Correction \n\nEnvironment: E5S ST"]
["AHFG-18766","Stock Maintenance","Reason for Qty mismatch does not flow from Cycle count result to Stock correction document.","Reason for Qty mismatch does not flow from Cycle count result to Stock correction document.","Primary Defect","Reason for Qty mismatch” provided for none controlled parts weren’t getting updated in stock correction tables","No - No",null,"Logic has been corrected to persist the “Reason for Qty mismatch” provided for none controlled parts in stock correction.","Tested in FS server \n\n1. Create CC Plan # CCP-000219-2019 , authorize it and prepare CC sheet# CS-000164-2019 . \n2. Enter count result and keep one row as difference in qty to make negative stock correction. Select the reason for Qty mismatch \n3. Enter the recount result, system will default that one row with same information given in Count Result screen, save and confirm the recount result without making any changes in Recount screen., \n4. Authorize the result and verify that in stock correction document system is defaulting the reason as \" Part data change\" & \" FE91\" , \"MS70\" \n\nViewed the stock correction \"SC-000872-2019\". \nEdited the Stock correction \"Reason for Qty mismatch properly flow from Cycle count result to Stock correction document.\" \n\n"]
["AHFG-18874","Stock Maintenance","System not allowing to Inactivate the record in Part Certificate screen","System not allowing to Inactivate the record in Part Certificate screen \n\nSystem display success message, but refresh the record in Active status itself \n\nPart #: RD-FJ7884-01 \nSerial #: G584466","Primary Defect","System pick wrong serial due to considering the lot value as ##'","No - No",null,"Logic has been handle to not consider the blank value in mange part certificate screen","Data: \n1. Launch Maintain Part Certificates for 0-0440-4-0011:36361 \n2. Inactivate the certificate details for the part \n3. The rows are inactivated successfully \n\nEnvironment: E5S ST"]
["AHFG-18832","Stock Maintenance","Unable to confirm retrun","While confirming the Return #: MRT0035105, system displayed error: \n\nThe conversion of the nvarchar value \"20231539006\" overflowed an int column. \n\nSaw that 20231539006 is part of Mfr Serial # and Serial #. The actual value is AA20231539006","Primary Defect","part restriction function should be called only if the value exist in the table AC_ACAPR_ADPART_REST_DET ,else it is not behaving correctlty","No - No",null,"part restriction function should be called only if there is a value in table AC_ACAPR_ADPART_REST_DET.else it is not behaving correctlty. So if exists condition was added","Data: \n1. Launch Maintenance Return for MRT-004512-2019 \n2. Confirm the return \n3. The return is confirmed successfully \n\nEnvironment: FS ST"]
["AHFG-16375","Stock Maintenance","Unable to open PO / MR","Click on View Purchase Order / View Material Request \n\nGets error message","Primary Defect","Sub -pub is not properly handled for serial and lot control from parent(hub )screen to child screen","No - No",null,"Sub -pub is not properly handled for serial and lot control from parent(hub )screen to child screen .Two hidden controls, one for lot # and the other for serial # is passed from the parent screen.","Tested in FS server \n\nScreens:- \n1.Procurement Management;>Purchase Order->Select Purchase Order . \n2. Stock Management;>Material Request->Select Material Request \n\nAble to view PO and MR . \n\nFix working fine \n\n\n"]
["AHFG-19256","Stock Maintenance","When a Lot controlled Part with 0 qty is added directly in the count results screen and authorized for a Positive stock correction, mismatch Lot # details observed in Inquire stock and Part Serial history screen","When a Lot controlled Part with 0 qty is added directly in the count results screen and authorized for a Positive stock correction, mismatch Lot # details observed in Inquire stock and Part Serial history screen","Primary Defect","When a Lot controlled Part with 0 qty is added directly in the count results screen and authorized for a Positive stock correction, mismatch Lot # details observed in Inquire stock and Part Serial history screen","No - No",null,"Logic has been modified to show the new Lot # in stock correction if lot added manually in the count results","Data: \n1. Launch Enter Cycle Count Results \n2. Add a lot controlled part with 0 quantity \n3. Authorize the Cycle Count Results \n4. The new lot number is shown correctly in Stock Correction \n\nEnvironment: FS ST"]
["AHBG-33113","Stock Issue","Unable to Confirm Exchange issue due to the mentioned error(AHFG-16730)","Created Exchange Purchase Order \nAuthorized the PO \nlaunched create exchange issue screen \nprovided the purchase order and clicked on search \nChanged the issue warehouse to 0123 \nCreated exchange Issue \nUnable to confirm issue \n\"Unable to process the document # : \"EIS-000035-2019\". External owned Stock Status should have trading partner information.(Input values : Stock Status : Supplier , Trading Partner Type : SUP & Trading Partner # : NULL.) Unable to process the document # : \"EIS-000035-2019\". External owned Stock Status should have trading partner information.(Input values : Stock Status : Supplier , Trading Partner Type : SUP & Trading Partner # : NULL.) \n\"","Secondary Defect","owningagency value is not updated properly for exchange issue lot control part.","No - No",null,"Owningagency value is updated properly for exchange issue lot control part.","Verified in bavnwarcnv04/extui \nconfirmed the exchange issue # EIS-000035-2019."]
["AHFG-19378","Stock Issue","Performance issue in Record Shipping Note screen. While executing search, system took long time and got blank error message","Performance issue in Record Shipping Note screen. While executing search, system took long time and got blank error message. \n\nHappened on 21-Oct-2019 6:00 AM to 7:00 AM","Primary Defect","System displays error while executing search in record shipping note due to the temp table updation and invalid key column joins.","No - No",null,"Logic has been modified on the updation of temp tables with key column joins and logic to fetch the records based on the search criteria.","Tested in FS Server \nScenario:- \n1. Picked up SWO#and added tasks \n2. Estimated and did confirm estimates, system generated Quote and approved Quote \n3.Signed off all tasks and completed the SWO \n4. Closed the SWO and returned LRU \n5. Searched for CO# in Record Shipping Note screen, did Record Shipment system processed it without any error \n\nscenario: \n\nCreated Recoerd shipping note # RSN-001102-2019 \n\n1. Stock transfer issue # STI-002996-2019 and AST-001819-2019 \n\n2. Recorded the shipping note 3 RSN-001102-2019 \n\nworking fine without any performance issue. \n"]
["AHFG-19172","Stock Issue","RO is listing under pending Issue due even though the part is issue confirmed and awaiting for RR","RO is listing under pending Issue due even though the part is issue confirmed and awaiting for RR","Primary Defect","RO listed under the pending issue even after the Issue is confirmed due to the invalid join logic handled with piece part table.","No - No",null,"Fetch logic has been modified to display records based on the issue confirmation logic.","Tested In FS Server, \n\n. Launch the Inventory operations hub and select the storage Location as \"ware house and location 0123\" \n2. Launch the Issue and returns tab and click -SV on the tree. RO will not be showing up anymore. \n\n3. Launch the external receiving tab and click 0123 repair receipt #ROR-000457-2019 / ROR-000458-2019 /ROR-000446-2019 ( to be confirmed)on the tree. \n\nFix working fine."]
["AHFG-18943","Stock Issue","When a lot controlled part is transferred from one location to the other location, system is not copying the certificate information","When a lot controlled part is transferred from one location to the other location, system is not copying the certificate information","Primary Defect","System failed to fetch the certificate details when doing stock transfer.","No - No",null,"Logic has added to fetch certificate information from inventory for the stock transfer receipts.","Tested in FS server \n\nCreated Stock Transfer of Serviceable parts (Lot Controlled) for following parts form 0123 to YULES warehouse: \nWarehouse # Part # Available Qty Condition Value Lot # Mfr. Lot # \n\nB) After Stock Transfer receipt # ST-001301-2019 , following new Lot # is created for the respective Part #00000584:D2269 lOT # LOT-009662-2019 \n\nC) Verify the Certificate information displayed for new Lot # in new warehouse in following screens: \n- Inquire Stock Availability (Part Name Plate screen) \n- Maintain Certificates screen \n\nResult: \nSystem displayed the Certificate details for old and new Lot # successfully in Part Name Plate and Maintain Certificates screen."]
["AHFG-19478","Stock Demand Mgmt.","MMD printed against stock transfer issue raised automatically as per demand management has incorrect information","When MMD was generated for STI-004608-2019 noticed all lines have the same part number as requested part number. This is wrong as each line has a different part number in request.","Primary Defect","system wrongly showing the request part number due to line matching failed","No - No",null,"Logic has been modified to fetch the requested part number in ST","Tested in FS server \n\n1.Created stock transfer issue# STI-002992-2019 with one part #0-0050845-1:5N982 and generated MMD report \nMMD report generated without any mismatch of columns or incorrect \ninformation \n\n2.Created Stock transfer issue with multiple parts, MMD report working fine. \n\nFix reviewed."]
["AHFG-19103","Smartcard","While scanning the Barcode (Start clock) error is coming","While scanning the Barcode (Start clock) error is coming","Primary Defect","Logic for enabling user access to confirm issue using Smart Operations is wrongly handled in Start clock bar code scanning","Yes - Only Fix Provided",null,"Logic has been corrected as confirm issue for enabling user access to confirm issue using Smart Operations. also this validation should not fire on when scanning the start clock barcode","Data: \n1. Launch Manage Work Actions \n2. Enter the code for start clock for the task NST-049574-2019 \n3. The clock is started successfully \n\nEnvironment: FS ST"]
["AHFG-18776","Shop Work Order","Issue part is not showing to part consumption details","Issue part is not showing to part consumption details","Secondary Defect","Part Details tab doesnt retrieved due to incorrect Logic,Logic has to be corrected","No - No",null,"mat type populated as \"RG\" from part details tab in estimation screen \nLogic Has been corrected","Launch the Part details tab and verified the issued parts displayed against the task. \nFix is working fine."]
["AHFG-19043","Shop Work Order","Clock on & Clock out Issue due to Non Availability of station code ( manage work assignment and reporting)","\" Station Code Not populated\"","Primary Defect","While booking timesheet for workorders from WMC screen, station code is not stamping","No - No",null,"While booking timesheet for workorders from WMC screen, station code stamping as expected.","Data: \n1. Launch Manage Work Assignments and Reporting for the work order CWO-009563-2019 \n2. Book the timesheet for an employee \n3. The timesheet is recorded successfully with the station code"]
["AHFG-18918","Shop Work Order","Deadlock in SWO_Revwrk_Exection_Tmp on 20/09","Deadlock in SWO_Revwrk_Exection_Tmp on 20/09","Primary Defect","Performance issue when concurrent users perform search from \"review work execution\" screen","No - No",null,"Identified the process which consumes more time and fine tuned the queries","Data: \n1. Launch Review Work Execution in 2 sessions \n2. Enter the search criteria and click 'Search' in the 2 sessions \n3. The search results are shown without errors \n\nEnvironment: FS ST"]
["AHFG-18847","Shop Work Order","Deadlocks in shop transactions","Deadlocks in these tables \n\nobjectname=AvnAppDB.dbo.swo_swoassoc_main_core_dtl","Primary Defect","Performance tuning not handled. Key column was not referred in a main table update","No - No",null,"Code is corrected in the following three SP's in order to refer the proper key columns in the main table update blocks","Data: \n1. Launch plan work order and create a make work order \n2. Associate required serials in Split/associate cores and release the work order \n3. Complete the work order \n4. Return the parts and close the work order \n\nEnvironment: FS ST"]
["AHFG-18931","Shop Work Order","Deadlocks in shop transactions","objectname=AvnAppDB.dbo.swo_swoprt_part_details - 19 locks \n","Primary Defect","Performance issue observed when short-closing a work order","No - No",null,"Identified the blocking statements and fine tuned the process to avoid deadlocks","Data: \n1. Launch Plan Work Order for CWO-009450-2019 \n2. Short close all the tasks and short close the work order \n3. The work order is short closed without performance errors \n\nEnvironment: FS ST"]
["AHFG-19533","Shop Work Order","Deadlocks objectname=AVNAPPDB.dbo.swo_swotsk_shop_wo_task_dtl pagelock","13-11-2019 objectname=AVNAPPDB.dbo.swo_swotsk_shop_wo_task_dtl pagelock 41 \n","Primary Defect","Performance issue in Plan work order screen","Yes - Only Fix Provided",null,"Performance fix provided to improve the processing time in submission clicks.","Post deploying the fix from Air India UAT server and verified with following sequence \n1, Launch Plan work order screen \n2. Fetch the Any work order and add the new nonstandard task and release the task to execution."]
["AHFG-19390","Shop Work Order","Not able to close the work order, due component location discripency","User not able to close the work order, same item is reflecting in inventory as well as in work order. \n\nMain core has been issued and system not allowing to create the MRN as well. \n\nCase1: \nCWO- 328937-19; \nPart# 398-21 and serial# IA222 ---- combination in work order but \nactual after PSN not combination is Part# 398-21 and serial# R16 \n\ncase2: \nwork order CWO-358607-19; Part# 2040029-104 ; Serial# aau9086 \n\n","Primary Defect","system allowed to change the new serial in part serial change activity which is already exist in system. System failed to validate due to internal new seral is matching for existance check","No - No",null,"Validation logic has been modified to check the existence of serial based on new Manufacturer serial and existing part number","Data: \n1. Launch Part Serial change screen for the part 0-0440-4-0011:36361 \n2. Change the manufacturer serial number to a number which is in a work order \n3. An error message is shown \n\nEnvironment: FS ST"]
["AHFG-6648","Shop Work Order","View Work Holds link does not work in some Work Orders","In some Work Orders I try to click in link \"View Work Holds\" in Review Work Execution screen and the system does not bring the information (latest example I have faced this problem is in CWO-002796-2017). It usually works fine for all work orders but there are some special cases in which it fails. In this cases, I cannot know how much time the Work Order has been held from here.","Primary Defect","As some work order # against customer name is join with special character like double quot. so system doesn't fetch the detail in view work hold link screen","No - No",null,"Issue has been fixed. Now would you see details in \"view work hold link screen\", whether given information with special character( double quot), system fetch the detail.","Data: \n1. Change the customer name for 400007 to Customer 8\" \n2. Launch Record Shop Execution Details for CWO-009357-2018 \n3. Record work hold \n4. Launch View Work orders and launch View work holds \n5. The screen is launched successfully \n\nEnvironment: FS ST"]
["AHFG-19302","Shop Work Order","script error occurs while removing a component","on removing a component the script error occurs \n\nWO-000775","Primary Defect","Process guid not updated properly while creating shop work order for Lot controlled part","No - No",null,"Logic handled to update process guid while creating shop work order for Lot controlled part","Data: \n1. Launch RSED for the work order CWO-009429-2019 \n2. Remove the part 0-0440-4-0011:36361 \n3. The part is removed successfully \n\nEnvironment: FS ST"]
["AHFG-19328","SERVICE SALE QUOTATION","START DATE DOESN'T APPEAR ON CO WHEN WE QUOTE","We are having some problems because when we go to quote a CO we can't because the Start Date is blank and the system shows an error. We have to go to the CO and modify it including the start date. At the Customer Goods Receipt the Start date appears, so we don't know where is the problem. \n\nCould you, please take a look on this matter and let us know something about it? \n\nBest regards, \nMarina","Secondary Defect","System mandates 'TAT start date' in Sale Quote if Promised delivery date is manually provided by Customer in CO. When the PDD is directly entered by user, it is not necessary to specify the start date in CO / Quote.","No - No",null,"Validation mandated the specification of TAT start date on existence of PDD in Sale Quote has been relaxed.","Scenario: \n1) Launched Manage Sale Quotation screen for the above mentioned CO. \n2) Clicked Save Main info button under ref. Info tab without specifying start date in the TAT section. \n3) Details got saved and system didn't mandate start date."]
["AHFG-18719","Service Sale Billing","E5S to FS regularization(billing)",null,"Secondary Defect","E5S to FS regularization","No - No",null,"E5S to FS regularization","E5S to FS regularization"]
["AHFG-19366","Service Sale Billing","Invoice value is incorrect for CO-000364-2019","Invoice value is incorrect for CO-000364-2019. \neven though invoice basis is set as Quote and Quote value is 22023 but system prints the invoice value as 16990","Secondary Defect","For the Prequote based release basic Value is not derived correctly,Logic has to be corrected.","No - No",null,"For the Prequote based release basic Value is not derived correctly,Logic has to be corrected. \nLogic handled and value displayed correctly.","Verified the fix and fix is working fine. \nRequest to cancel the already generated release and generate a new release. \nValue will get displayed correctly. \nPlease find the comments for more information and steps."]
["AHFG-18991","Service Sale Billing","On click of the link Process monthly invoice contract and revision is not stamping properly and on compute system displayed an invalid error",null,"Secondary Defect","alidation for object effectivity has to be relaxed to fetch and release the monthly bill","No - No",null,"Logic has been corrected by relaxing the validation against the object effectivity others","Verified the fix and it is working fine. \nAble to compute the charges and generate the release \nFST \n"]
["AHFG-19204","Service Sale Billing","Ref : APHE-1559 - Final Price of the task is not getting properly updated if the Invoice release generated based on Pre-quote","1) Generated CO based on Pre-quote and info of pre-quote has been copied to direct quote. \n2) Completed Execution document, closed SWO and generated Invoice release. \n3) Details in the Direct Quote info has been copied to Invoice release. \n4) Processed Invoice Release. \n5) Generated Invoice and printed the same. Report is not getting printed. \n\nRoot Cause: On Generation of Invoice release based on quote, Final price is not getting updated properly against the tasks where as the report is getting printed only if the final price is available against atleast one of the task in Invoice release","Secondary Defect","When the Invoice release is generated automatically, Final price of the task copied from Direct Quote is not computed properly. Because of this, Invoice report is not getting generated.","No - No",null,"Changes have been done in the event of auto invoice release generation to compute the final value of the tasks copied from Direct Quote section of Sale Quote.","Scenario: \n1) Generated Invoice release for the above mentioned CO. \n2) Value of the task copied from direct quote is displayed properly. \n3) Confirmed and Processed invoice release. \n4) Generated Customer Service Invoice and printed Invoice report. \n5) Report has been generated successfully."]
["AHFG-19227","Service Sale Billing","The TCD amount is getting changed in the CO T/C/D tab on saving the data in resources tab.","The TCD amount is getting changed in the CO T/C/D tab on saving the data in resources tab.","Secondary Defect","The logic is not build on flat base TCD amount to save the value in the table on amending the amount other than the one which is in TCD master.","No - No",null,"The logic is build on flat base TCD amount to save the value in the table on amending the amount other than the one which is in TCD master. On save of resource tab also the flat TCD amount is not getting vanished.","Env: http://bavnwarcnv04/Extui/extui/vwrt/LaunchPanel.htm \n\nData: CO-009153-2019"]
["AHFG-19414","Service Sale Billing","To ship the inconsistent data of DHM alert mail on Project cost rpt , Invoice report , Pricing summary","To ship the inconsistent data of DHM alert mail on Project cost rpt , Invoice report , Pricing summary","Secondary Defect","project specific logic has been implemented and provided fix.","No - No",null,"Old records moved to inconsistent table and same being removed in alert mail","Project Specific fix has been implemented. \nJust launch the Project cost report,Invoice report."]
["AHFG-19147","Service Sale Billing","Duplicates lines for A/C in Process Monthly Invoice Release","Duplicates lines for A/C in Process Monthly Invoice Release. \nContract #: MSA-DAL-01 \n","Primary Defect","Duplication of values happened due to incorrect logic for price disposition splitup at category level and the same is not available in the front end screen,LOGIC has to be modified in the backend.","No - No",null,"Price disposition has been split up at category level at back end logic but the category is not visible in screen hence seemed to be duplicated. \nLogic has been modified.","Verified the fix and it is working fine. \nFor the month of September milestone generated a release and validated the values and it is showing the correct values and no line is duplicated. \nGenerated Release and invoice"]
["AHFG-18420","Service Sale Billing","Pricing Summary Consistency Alert","Pricing Summary Consistency Alert","Primary Defect","Alert mail to compare pricing summary and release value is incorporated.","No - No",null,"This is project specific alert.","Env: http://BAVNWARCNV04/Extui \n\nThis is project specific alert."]
["AHFG-19159","Service Sale Billing","The recent created/generated record should fetch in first line of the multi-line on search.","The recent created/generated record should fetch in first line of the multi-line on search. \n\nIt is expected to happen in Manage Invoice Release screen.","Primary Defect","This change was done as a project specific for Jet East and there is no impact in base env.","No - No",null,"This change was done as a project specific for Jet East and there is no impact in base env.","Env: http://bavnwarcnv04/Extui/extui/vwrt/LaunchPanel.htm \n\nThis change was done as a project specific for Jet East and there is no impact in base env."]
["AHFG-18750","Service Sale Billing","Unable to process invoice for CO-000091-2019 system gives an error as Account code has not been defined for usage SER-MAT in Finance Book PHABPFB","Unable to process invoice for CO-000091-2019 system gives an error as Account code has not been defined for usage SER-MAT in Finance Book PHABPFB","Primary Defect","If the Invoice release is created for the Exchange Order based CO on actual basis, system failed to retrieve Accound definition for material","No - No",null,"Changes have been in order to retrieve the account code for Exchange order based CO on generation of Exchange invoice, if the invoicing basis is Actuals. \n","Scenario: \n1) Launched Manage Invoice Release Screen and generated Invoice release for the above mentioned CO on actual basis. \n2) Confirmed and Processed invoice release. \n3) Generated Invoice and account code has been generated successfully \nhttp://bavnwarcnv04/extui/extui/vwrt/LaunchPanel.htm"]
["AHFG-19192","SERVICE QUOTATION","QUOTATION","Quotation CO-002780-2017 / 3 is wrong calculated. System shows 1.726,21€ and the total is 2.071,21€","Secondary Defect","On providing the FP-labour price manually against T&M task, Fixed total price is not calculated properly. Hence it is not added in Quote value..","No - No",null,"Changes have been done in order to calculate the Fixed price properly when the same is entered manually by user against T&M tasks","Scenario: \n1) Launched Manage Sale Quote for the above mentioned CO. \n2) Entered Fp-labour price manually against task. \n3) Fixed price has been calculated properly and entered price added to quote value."]
["AHFG-19134","Sales Setup","Trying to create a new PPL by copying existing PPL, in which slab definitions are not getting copied.","Trying to create a new PPL by copying existing PPL, in which slab definitions are not getting copied.","Secondary Defect","Slab definitions is not getting copied from existing PPL to new PPL . This is because, insert logic was not handled for slab detail.","No - No",null,"Slab definitions logic was handled to copy the slab definitions from existing PPL to new PPL .","Existing PPL: QA \nNew PPL: 2 \nCopied the slab definitions correctly \nfst"]
["AHFG-18252","Sales Quotation","Contract Modification happened (unit moved from T&M to FPO), so user revised the Customer Order with new Contract Revision. Later to this when user revise the Customer Quotation, system did not pick SWO-Task line in Ref info tab","Pre Requisites: \nPart #: RD-KA5622-01 was moved from Part Group # T&M to SRT 1.75. This happened after the Quotation is generated \n1. Pick up CO#: CO0012882 in Customer order screen and create a new revision \n2. Checked the Contract and Part Effectivity column, system listed GTA-GENERAL-01 and PE-017 \n3. Clear the Contract field and do evaluate contract once again, system displayed Contract # as GTA-GEneral-01 and Effectivity code as PE-001 \n4. Save and Confirm the CO# \n5. Go to Quotation screen and search for CO#: CO0012882, system displayed status as Contract Re-assigned \n6. Did Revise Quotation and Get Revision, system did not picked up SWO-Task \n7. Checked the Pricing Basis in Quotation, system displayed Fixed price by Object","Secondary Defect","If the New revision of CO is created and Contract re-assigned, contract re-assignment is not happening properly. Also system is not allowing Contract Reassignment if Part Effectivity alone is changed","No - No",null,"1) Changes have been done in the Customer Order to recognise the Contract Re-assignment action properly on evaluation of Contract. \n\n2) Validation which was restricting the re-assignment of contract if part effectivity is modified in the Contract has been relaxed.","Scenario: \n1) Created new revision of the above CO. \n2) Evaluated contract and new revision of contract got assigned. \n3) Confirmed CO. \n4) Launched Manage Sale Quotation and quote of the respective CO change to Contract Re-assigned status. \n5) Created new revision of Quote and SWO-task has been picked."]
["AHFG-19377","Sales Quotation","Long running statement in Stock - SP: SQO_RSQ_Sp_SrchSearcRspO","Long running statement in Stock - SP: SQO_RSQ_Sp_SrchSearcRspO \n\nStatement attached in comments","Primary Defect","Performance tunning needs to be handled on search of Sale Quote","No - No",null,"Non clustered index used for temp tables for the missing index column","Env: FS \n\nThis changes is handled only for project and nothing affects the product."]
["AHFG-19523","Sale Contract","Not able to choose the \"Pricing Basis\", system defaults back to \"All\"","Service Sale Contract - Invoicing & Payment --> Chosen Pricing Basis as \"TM\" \n\nNot able to choose the \"Pricing Basis\", system defaults back to \"All\"","Secondary Defect","Unable to choose the respective pricing basis against each service sale type.Logic has to be corrected","No - No",null,"Invoice pricing basis Code was loaded instead of description during tab click , hence the value wasnt defaulted","Verified the fix and it is working fine. \nProvided the pricing basis and saved successfully. \nAPROAME"]
["AHFG-19133","Sale Contract","Validations are incorrectly during save in Task-Billing Element Mapping activity.","Contract #: MSA-VAU-01 \nThere are 4 tasks available in the multiline. See attached. \nTask available in 2nd line was inactivated in Task Master. \n\n1) When clicking on save, system validates with following - 'Unable to process row # \"2\". Please enter a valid Task no.' \nSystem should inform that the task is inactive instead of stating its invalid. \n2) Selected the task in Line 2 and changed the status to Inactive. Clicked on Save. System validates with following - 'Unable to process row # \"2\". Please enter a valid Task no.' \nSystem should ideally allow to inactivate the line. \n3) Removed the line 2 which has the inactive task and clicked on save. System validates with following - 'Unable to process row # \"1\". Please enter a valid Task no.' \nThis is an incorrect message. System should allow to inactivate the line. Now there is no option to remove/inactive this line. As well as not allowing to modify any data or add data in this screen. \n4) I can modify the task in an existing line and system will allow to save it. It retains the created by for that line. It is a invalid behaviour as it will lose control on the data and we wont know the history of it. We should not allow to update the task # if its already available. If required user should be allowed to inactivate the line and create new lines.","Secondary Defect","New validations needs be added along with amendments in existing validations.","No - No",null,"New Validations was added. \nExisting validations was amended for specific scenarios [Explained in Test & Verification details section]","\n1) When clicking on save, system validates with following - 'Unable to process row # \"2\". Please enter a valid Task no. \n\nNew Validation Added: Unable to process row# “2”. The task in row “2” is inactive in task master. Please change the status as ‘Inactive’ and Save. \n\n2) Selected the task in Line 2 and changed the status to Inactive. Clicked on Save. System validates with following - 'Unable to process row # \"2\". Please enter a valid Task no.' \n\nActions taken: Above validation was relaxed. If a task is inactive in taskmaster, provision will be given in Task-Billing Element Mapping screen to change the status to inactive. \n\nTo be discussed: If a task which is in-progress in execution and then if a task is changed to inactive in task master, how it needs to be handled? \n\n3) Removed the line 2 which has the inactive task and clicked on save. System validates with following - 'Unable to process row # \"1\". Please enter a valid Task no.' \n\nNew Validation: Deletion is not allowed. Please change the status as inactive and save. \nActions Taken: Addition is happening without any error. \n\nNote: The new validation will throw on deleting the inactive task aswell. \n\n4) System is allowing modify the task, customer#, contract# in an existing line and its getting saved. \n\nActions taken: Amending the task#, customer#, contract# in the existing line should be restricted. If needed user can change the status as inactive and proceed. New task can be added only in a separate line. \n\nNew Validation: Modification is not allowed in row “2“. Please inactive and add a new line."]
["AHBG-35129","Sale Contract","Regularization (E5D) : SALE CONTRACT CHANGES","Regularization agaisnt the case : AHBG-30658","Primary Defect","Observed that the capping front end changes agaisnt the case : AHBG-30658 are not available in E5D ST.","No - No",null,"Regularization (E5D) : SALE CONTRACT CHANGES \nObserved that the capping front end changes agaisnt the case : AHBG-30658 are not available in E5D ST. \nRegularized the same .","Regularization (E5D) : SALE CONTRACT CHANGES \nObserved that the capping front end changes agaisnt the case : AHBG-30658 are not available in E5D ST. \n"]
["AHFG-19033","Sale Contract","Manage Sales Contract - Part Eff Tab - Covers Alternates Not Working","Manage Sales Contract - Part Eff Tab - Covers Alternates Not Working. \nPFA the scenario provided by Customer.","Primary Defect","The logic is not properly handled to fetch the eligible contract on receiving alternative parts. And its mainly caused when a block is commented for panasonic against APPI-1100.","No - No",null,"Logic has been handled to insert based on alternative parts and match flag is considered for contract evaluation. Now, the eligible contract will be pegged and if more contract exist, a proper message will be thrown by listing all the possible contract.","1) Created a new contract 'Testing' and gave a part '0-25031-8E:2D671' by mentioning 'Covers Alternatives' as Yes. \n2) Received an alternative part '0-25031-7898' and generated a CGR# 'GI-011982-2019 \n3) Clicked evaluate contract and a message thrown saying, Multiple contract exist and it listed all the possible contract. It includes contract 'TNMCONTRACT as well. \n4) Gave 'TNMCONTRACT' under contract column and clicked evaluate contract. No error was thrown and finally saved successfully. \nhttp://bavnwarcnv04/extui/extui/vwrt/LaunchPanel.htm"]
["AHFG-18988","Sale Contract","Repl. Type disappears on click of Save in Mat caps defn. tab Contract : ATR-RDSR-1143/17",null,"Primary Defect","During save refresh instead of replacement code, replacement description has been passed ,coding logic corrected.","No - No",null,"Logic was corrected inorder to save the replacement type in ‘Mat Pricing Caps’ tab.","Defined Material capping in the mentioned contract. \nWhile defining provided the replacement type and clicked save, the data got saved successfully. \nFST"]
["AHFG-18853","Sale Contract","The repair process code is not getting saved in the contract screen. And also, inactive repair process codes are seen in the dropdown.","The repair process code is not getting saved in the contract screen. And also, inactive repair process codes are seen in the dropdown.","Primary Defect","Repair process description is loaded in combo of TAT-Parts of Sale Contract screen.","No - No",null,"Combo logic was amended and currently Repair Process Code will be loaded in TAT-Parts, CO, SWO and CGR screen.","Repair Process code is loading in the screen. \nVerified the fix"]
["AHFG-19464","Request For Quotation","Error while creating a quotation based PO","While creating quotation based PO below mention error occurs. \n\nQUOT-010841-2019","Primary Defect","Quotation effectivity check hadled based on the supplier offer date plus price held firm time","No - No",null,"Logic modified to validate the quotation effectivity based on the effective tp date","Tested in FS Server \n\nScreen:- \nProcurement Management->Purchase Order->Select Quotation \n1.Created Quotation based PO # QUO-000124-2017 confirmed and authorized. \n\nScreen 2:- \nProcurement Management->Purchase Order->Create Purchase Order \n\n1. Created The PO # against quotation. \n\nFix working fine on the effective date issue. \n\n\n"]
["AHFG-19038","Reports - Receivables Management","Charge Amount and subtotal is displayed wrongly in Invoice Report","1) Generated Customer Service Invoice report for the CO having multiple Charges. \n2)Charge Amount and subtotal is displayed wrongly in Invoice Report","Secondary Defect","Charge amount is not displayed properly if more than 1 charge is available in the Invoice release","No - No",null,"Changes have been done in the report in order to compute the charge amount properly irrespective of the no of charges added in the report","Scenario: \n1) Launched Customer Service Invoice report for the invoice. \n2) Charge amount and subtotal have been displayed properly. \nhttp://bavnwarcnv04/extui/extui/vwrt/LaunchPanel.htm \nCI-000453-2019"]
["AHFG-18890","Reports - Receivables Management","Charge amount is wrongly printed in the Invoice print","Generated Invoice report for the Invoice # 'CI-002382-2019' and Charge amount is wrongly printed in the report. Instead of 218.21 Euro, 181.84 Euro has been printed","Secondary Defect","If additional charge is available in Invoice release, basic charge amount alone is printed in the report and markup of the respective charge is not considered while printing the charge in report","No - No",null,"Changes have been done in the Invoice report in order to consider the Final Price computed against additional charge which is the sum of basic charge amount and markup provided against additional charge in Invoice release.","Added the charge in the invoice release \nand on print charge displayed according to the specification. \nScenario: \nGenerated Invoice Report for the Invoice and additional charge printed properly. \nCI-000453-2019 \nhttp://bavnwarcnv04/extui/extui/vwrt/LaunchPanel.htm"]
["AHFG-18752","Reports - Receivables Management","Invoice report is not getting generated for the Invoice # 'CI-002188-2019'","1) Launched Print Invoice screen and selected Invoice type as Customer Service Invoice. \n2) Launched Report for the Invoice # 'CI-002188-2019'. \n3) Report is not getting generated for the same.","Secondary Defect","No logic was handled to fetch a report for a Work Order when RO is generated within SWO.","No - No",null,"Now logic was handled to fetch a report for a Work Order when RO is generated within SWO. \n\n'SWO' doc type condition has been checked in external service data insertion and it has been removed now.","1) Launched Print Invoice screen and selected Invoice type as Customer Service Invoice. \n2) Launched Report for the Invoice # CI-000454-2019. \n3) Report is getting generated for the same. Attached the report in this RTrack."]
["AHFG-19326","Reports - Receivables Management","Alert mail to track inconsistent records b/w CO profitability report and customer project cost report","Alert mail to track inconsistent records b/w CO profitability report and customer project cost report","Primary Defect","Consistency b/w CO profitability report & Customer Project Cost Report is required","No - No",null,"Alert mail has been configured to display exception records which are having cost mismatch b/w CO profitability & Customer Project Cost Report.","Env: FS \n\nProject specific alert mail was configured for Patria and no changes in product."]
["AHFG-19340","Reports - Receivables Management","Billing Customer and address should be referred from Customer Service Invoice and printed in the report. Currently billing address is referred from Invoice release.","Bill to address is printed in Invoice report by referring the 'Bill to' address available in the Invoice release. \n\nRequirement is to refer the 'Bill to Customer' from Customer Service Invoice and default bill to ID of the respective customer should be referred from Customer Sales Point information and the same should be printed in the report.","Primary Defect","The default 'Bill to Address' from the customer master under 'Customer Sales Point Information' needs to be printed in the invoice report when 'Bill to Customer' is amended during the invoicing.","No - No",null,"The default 'Bill to Address' from the customer master under 'Customer Sales Point Information' is getting printed in the invoice report when 'Bill to Customer' is amended during the invoicing.",") In edit invoice screen changed 'Bill to Customer' \n2) Ensure the default bill to customer is getting printed in the report or not. \n3) Since for this particular customer, there were 5 different address available, tried to default the second once and launched the invoice report. The exact address defined in the second line got printed."]
["AHFG-19329","Reports - Receivables Management","Consistency check b/w Invoice release and Comprehensive Invoice report at entity level viz., Task, Material, Resource, External Repair etc.,","Consistency check b/w Invoice release and Comprehensive Invoice report at entity level viz., Task, Material, Resource, External Repair etc.,","Primary Defect","Consistency check b/w Invoice release and Comprehensive Invoice report at entity level viz., Task, Material, Resource, External Repair etc.,","No - No",null,"Alert mail has been configured to track the mismatch records which are having the difference in price b/w Invoice report & Invoice release at each entity level viz., Fixed Price, Material Price, Labour Price etc.,","Env: FS \n\nProject specific alert mail was configured for Patria and no changes in product."]
["AHFG-19000","Reports - Payables Management","Differences in Supplier Ageing Report with Trial Balance as of 30-September-2019","Differences in Supplier Ageing Report with Trial Balance as of 30-September-2019","Secondary Defect","As the supplier Deposit voucher retrieval failed in Supplier Ageing Analysis report, reported mismatch occurred. Also transaction balance has not been properly accounted for the Order based Invoices causing Revalued balance differences.","Yes - Data Update & Fix Provided",null,"Supplier Ageing Analysis report has been fixed to retrieve the supplier Deposit voucher properly. Transaction Account balance has been corrected for problematic Order based Invoices as on October 1st and therefore, Revalued balance as on the October Month end can be tallied.","> Extracted the following reports as on 30th September 2019 \n- Trial Balance \n- Supplier Ageing Report \n> Observed no mismatch exist between the same. \n\nServer - FS Server"]
["AHFG-18845","Reports - Management Accounting","the account description for some of the accounts on the budget vs actual report is different than their description on the chart of accounts","the account description for some of the accounts on the budget vs actual report is different than their description on the chart of accounts. \nthe following account numbers (6101,6102,6104,6107,7516) have incorrect description. \ncan you please cross-check all the accounts on the report, and reconcile it with the chart of accounts. \n","Primary Defect","Incorrect account description is getting fetched in the report","No - No",null,"Account description is fetched from Chart of Accounts table.","Tested and verified after the fix, that the account code description is matching with the description fetched in the Report."]
["AHFG-19078","Reports - Book Keeping","Amount is incorrect in GSTR reports","Amount is incorrect in GSTR reports","Primary Defect","Instead of tran amount ,item amount has been shown for all the supplier transactions","No - No",null,"Tran amount has been shown under the amount column from the master tables .","Verified in FS-ST server"]
["AHFG-19278","Reports - Book Keeping","Report on Tax Transaction -Data error","Report on Tax Transaction -Data error","Primary Defect","The reported issue occurred as the system could not process the customer codes in Tax Transaction reports, created with 18 characters length. As per current report definition it can hold only till the length of 16 characters.","No - No",null,"The reported issue has been resolved by modifying the report logic to process the customer codes in Tax Transaction reports, created with 18 characters length.","Tested and verified in the following manner, \n> Launched Book Keeping > EDK Reports Book Keeping > Reports on Tax Transactions. \n> On filling all the mandatory fields and on the click of 'View Transaction Details/ View Account Details', observed that system executed the process and the report got generated accordingly. \n\nServer - FS Server"]
["AHFG-16320","Repair Order","Actual receipt date is blank in view repair order","Actual receipt date is blank in view repair order","Primary Defect","Actual receipt date is blank in view repair order","No - No",null,"Logic handled to fetch the actual receipt date as show the latest date of PGR. \n","Tested in FS server, \n\n1.Created the RO's #AFRO-003132-2019 / OBCRO-000077-2018 moved to authorized status. \n2. Searched the RO# actual receipt date( updated properly). \n3. Checked the PGR date matching with actual receipt date. \n\nFix working fine. \n\n"]
["AHFG-18989","Repair Order","Error message when editing a repair order","Error message when editing a repair order after doing the release for shipping","Primary Defect","Error message has not been handled in the sp","No - No",null,"error message has been handled in the sp","Data: \n1. Launch Edit Repair Order for REP-000705-2019 \n2. Edit the repair order \n3. The changes are saved successfully \n\nEnvironment: E5S ST"]
["AHFG-18942","Repair Order","Supplier parts and warranty details - drop down in confirm desrepancy report is not getting saved in repair order management business process//RAD034192-19 & RAD033442-19","Dear Ramco, \nPlease see screen shot , the below array of activity , dropdown in \"confirm descrepancy reported\" is not getting saved and automatically return to first level after saving. \nRepair order management ->Reapir order -> Manage repair quote-> Tab-Supplier parts and warranty details -> supplier findings->confirm descrepaccy reported -> dropdown return automatically after saving. \nPlease do needfull to authorise the order RAD034192-19 pending for RGR action at A320 recipt section. \nThe same desrepancy is also observed in RAD033442-19 \nThanks","Primary Defect","the below array of activity , dropdown in \"confirm descrepancy reported\" is not getting saved and automatically return to first level after saving.","No - No",null,"Logic handled to update the confirm discrepancy reported properly","Tested in FS Server. \n\nRepair Order Management->Repair Order->Manage Repair Quote \nAfter deploying the fix \nDoc# AFRO-000001-2011 \nconfirm discrepancy reported updated properly. \n\nSupplier par warranty details get update successfully with comments . \n\nFix working fine"]
["AHBG-35961","Reliability Analysis","Ability to configure the user defined rules for removal assessment parameters(NFF rules & LTR rules)","Ability to configure the user defined rules for removal assessment parameters(NFF rules & LTR rules)","Primary Defect","Ability to configure the user defined rules for removal assessment parameters(NFF rules & LTR rules)","No - No",null,"Ability to configure the user defined rules for removal assessment parameters(NFF rules & LTR rules)","Ability to configure the user defined rules for removal assessment parameters(NFF rules & LTR rules)"]
["AHFG-18486","Quality Audit","Record is not saving in Corrective and preventive action screen and data is vanish after record action and Setup option also defined","Record is not saving in Corrective and preventive action screen and data is vanix after record action \n","Secondary Defect","In Recommendations/Observations details tab page, does not fetch those Recommendations records which have their 'Recom./Observ Status' as \"Actioned\".","Yes - Only Fix Provided",null,"Fix given to fetch 'Recom./Observ Status' as \"Actioned\" or pending status.","Post deploying the fix from GMR UAT server and verified with following sequences. \n1. Launch for Corrective and preventive action screen \n2. Search for Pending action items \n3. Select Recommendations/Observations details tab page and enter the required details \n4. Save pending action."]
["AHFG-18321","Purchase Order","FB is getting duplicated in Expense to drop down.","FB is getting duplicated in Expense to combo.","Primary Defect","System displays duplicate entry of the data in the Expense to combo option.","No - No",null,"Logic has been modified to fetch the records accordingly","Tested in FS server and checked in LFN Enthronement too. \n\nScreen:- \nProcurement Management->Purchase Order->Create Purchase Order. \nCreated Adhoc PO, Expense to drop down with finance book populated without duplicate value. \nFix working fine. \n"]
["AHFG-18953","Purchase Order","Search not working in View Purchase Order screen for particular scenarios","1. Search Combination of Supplier Name and PO Total Value does not return results, even though documents exist within the set criteria \n\n2. When more than 40 characters entered in Supplier Name Search, no results are fetched, even though documents exist \neg. \"ZANCOTT KNIGHT FACILITIES MANAGEMENT PTY LTD\" \n","Primary Defect","system did not fetch records when searched with supplier name and PO value","No - No",null,"Logic has been handled to fetch records based on the search criteria.","Tested in FS Server \n\nScreen :- \nProcurement Management->Purchase Order->Select Purchase Order. \nIn search criteria , searched against the supplier name and supplier description, \n\nFetching the data against the description \nFix working fine. \n\n"]
["AHFG-19084","Purchase Order","a previously created PSO and PO needed an update in quantity of 2 items, it only got updated in PSO but no in PO, PO can not be amended","PSO-013710-2019 Y 19P02655 \na previously created PSO and PO needed an update in quantity of 2 items, it only got updated in PSO but no in PO, PO can not be amended","Primary Defect","When the Quantity is getting reduced for multiple parts in PSO , then the processing records for PO amendment was limited to 1.","No - No",null,"When the Quantity is getting reduced for multiple parts in PSO , then the processing records for PO amendment was limited to 1. \n\nLogic handled to consider all the affected lines for PO amendment from PSO.","Data: \n1. Create and confirm a Part Sale Order for 3 parts with 10 quantities each \n2. Create a purchase order for the part sale order \n3. Amend the Part Sale Order by reducing the quantity and confirm the part sale order \n4. Check for the reduced quantity in the MR and PO \n\nEnvironment: FS ST"]
["AHBG-35947","Pool Management","Deployment error during E5D to FS merger","Deployment error during E5D to FS merger","Secondary Defect","Force Reviewed for Shipment","No - No",null,"Force Reviewed for Shipment","Force Reviewed for Shipment"]
["AHFG-19550","Physical Inventory and Cycle Count","Error message for Stock Ownership should come while confirming the Cycle Count result and not while approving cycle count results","Error message for Stock Ownership should come while confirming the Cycle Count result and not while approving cycle count results. \n\nWhen the entered Lot # - Mfr. Lot # is entered in the cycle count result is entered in Owned Stock Status but in Ramco history, the Lot # - Mfr. Lot # combination exists in customer ownership, this validation should come while confirming the count results.","Primary Defect","When a new serial-lot is getting added during count results which is already known to the system , then system fails to validate whether the serial -lot belongs to the correct stock status has been selected.","No - No",null,"Validation added to ensure the part - serial /lot stock status ownership combination is valid if the new rows is getting added during count results process.","Tested in UAT Server FS ST server. \n\n1. Created the cycle count plan # and authorize. \n2.Added the new row with serial /lot stock in count results. \n\n\"Error message for Stock Ownership while confirming the Cycle Count result\" \n\nSystem validates to check the stock status ownership combination along with trading partner. \n\nfix working fine. \n\n"]
["AHFG-19207","Physical Inventory and Cycle Count","Even though recount is set as required, cycle count is updated as counted on enter cycle count results instead of Pending recount","Even though recount is set as required, cycle count is updated as counted on enter cycle count results instead of Pending recount","Primary Defect","cycle count is updated as counted on enter cycle count results instead of Pending recount due to system failed to check tolerance value","No - No",null,"Logic has been corrected to check the tolerance value greater than equal to system quantity","Data: \n1. Launch Enter Cycle Count Results \n2. Authorize the results \n3. Cycle count is updated as pending recount \n\nEnvironment: FS ST"]
["AHFG-19124","Physical Inventory & Cycle Count","Stock Correction document does not bring the cost for new lines added in cycle count result","(*Make sure that the Set Option for Generate Stock Correction for discrepant stock in Authorized status? is set to Yes and a default Account and Costing Usage is defined in SIPP) \n\nAdd a new line and the Lot # and Mfr. Lot #. Enter count Qty. \nClick on Record and Confirm Result. \n\nOn Authorisation of Cycle Count Result, system creates a Positive Stock Correction in Authorised status but the correction value for this new line is taken as 0. \n\nHistorically for the Part # - Lot # combination, there is a cost in the system and when stock correction is generated, this new line should come with the cost that is previously available in system. \n\nNote: When the stock correction is manually authorised by changing the Set Option for Generate Stock Correction for discrepant stock in Authorized status? to No, system brings the value in Stock Correction.","Primary Defect","When a new line is added, i.e. a Line is newly added with a Part # - Lot # - Mfr. Lot # whose history already exists, then system brings the same at zero cost","No - No",null,"Logic handled to compute the cost from stock a Part # - Lot # - Mfr. Lot # whose history already exists, Also derive the standard cost as correction value when new manufacturer serial / new manufacturer lot brought through cycle count","Data: \n1. Add new line to cycle count results and authorize it \n2. Cost is computed correctly for the part \n\nEnvironment: FS ST"]
["AHFG-15983","Physical Inventory & Cycle Count","Unable to authorise results because of allocated stock","In the Cycle Count Results, create a discrepancy for one of the part which is allocated. Like in this case, the Serial # for Part SMA2150-1 is allocated. (Check screenshot from Inquire stock availability) \n\nDuring the Authorisation of count result, we are getting an error message that Part cannot be allocated. We have enabled the option that Stock Correction should be generated in Authorised status. \n\nThe message is valid but the relevance of getting this message is too late. At this stage, we cannot change the count Qty (because status of count sheet is \"counted\" and we cannot authorise Count Results based on this error. \n\nCan we get this error message while confirming results instead of Authorising results. \nDuring the confirmation of results, if the discrepant stock is allocated (or making the allocation to be cancelled), then this error should be displayed.","Primary Defect","Logic not available to de-allocate the hard allocate quantity in auto stock correction during count results authorization","No - No",null,"Logic handled to de-allocate the hard allocated quantity in auto stock correction during count results authorization","Data: \n1. Take the part 0-0440-4-0011:36361 which has allocated quantity \n2. Create a cycle count results for the part and a discrepancy with count quantity as zero \n3. Authorize the cycle count results \n4. The cycle count results is authorized successfully without errors \n\nEnvironment: FS ST"]
["AHFG-18915","Part Sale Order","AMP PRODUCTION SALE ORDERS IN UNDER PROCESSING","AMP PRODUCTION SALE ORDERS IN UNDER PROCESSING","Secondary Defect","System is expecting to decrease the qty of all the lines in the multi-line and not allowing to approve the PSO when qty is decreased only for a single line out of many.","No - No",null,"Logic has been changed in a way that, on confirmation only respective lines for which qty was decreased will be considered for short closure","Created new revision for an approved PSO and the quantity of the parts has been decreased for specific lines. \n• On confirmation system is looking for change in all the lines of the PSO. \n• Logic has been changed in a way that, on confirmation only respective lines for which qty was decreased will be considered for short closure. \n• Moreover, the PSO will go to approved status once demon scheduler runs \nhttp://bavnwarcnv04/extui/extui/vwrt/LaunchPanel.htm \nACPR-000475-19"]
["AHFG-19007","Part Sale Order","AMP PRODUCTION SALE ORDERS IN UNDER PROCESSING",null,"Secondary Defect","System is expecting to decrease the qty of all the lines in the multi-line and not allowing to approve the PSO when qty is decreased only for a single line out of many.","No - No",null,"Logic has been changed in a way that, on confirmation only respective lines for which qty was decreased will be considered for short closure.","Created new revision for an approved PSO and the quantity of the parts has been decreased for specific lines. \n• On confirmation system is looking for change in all the lines of the PSO. \n• Logic has been changed in a way that, on confirmation only respective lines for which qty was decreased will be considered for short closure. \n• Moreover, the PSO will go to approved status once demon scheduler runs \nFST"]
["AHFG-19245","Part Sale Order","Getting error while processing sale orders","Getting error while processing sale orders \n\nMails attached for reference. \nPPSO-010889-2019","Secondary Defect","Validation has to be handled on revision of a part sale order when the line level status is getting changed.system should not allow to change the line level status","No - No",null,"Validation handled at the line level status getting changed. \nSystem should not allow the line level status from ordered to pending so to trap the sequence we added a validation message.","Verified the fix and it is working fine. \nValidation handled on change of line status"]
["AHFG-18964","Part Sale Order","Would like to change the part sale order PSO-000612-2019 It hasalready been shipped and invoiced, but with wrong discount.Wrong discount 961,93Right discount 62,54","Would like to change the part sale order PSO-000612-2019 It hasalready been shipped and invoiced, but with wrong discount.Wrong discount 961,93Right discount 62,54 \n\nInvoice CI-PS-000436-2019 is also deleted","Secondary Defect","f the Part Sale Invoice is deleted from the Entry Screen of Manage Pack slip / Bill Back Invoice, New Invoice is not getting auto generated","No - No",null,"Changes have been done to recreate the part sale invoice even if the invoice is deleted from the entry screen of Packslip / bill back invoice screen. \nIssue existed in modifying the Discount amount also has been fixed. On Modification of TCD amount, system was not able to identify the taxable amount due to which error was thrown. Changes have been done in order to make the system identify the Taxable amount properly on TCD amount modification.","Able to modify the discount amount and regnerate the sale invoice. \nFix is working fine \nFST"]
["AHFG-18759","Part Sale Order","all orders in AMP-PANAMA are stuck in under processing status","all orders in AMP-PANAMA are stuck in under processing status","Secondary Defect","No validation was handled when user tries to replace the part for approved [MR generated] PSO.","No - No",null,"Currently, new validation was handled so that when user tries to replace the part for approved [MR generated] PSO , system will restrict.","Currently, new validation was handled so that when user tries to replace the part for approved [MR generated] PSO , system will restrict. \nACPR-000476-19"]
["AHFG-18956","MRO Warranty","System displaying ## for Serial Controlled Parts in MRO Part Warranty screen","System displaying ## for Serial Controlled Parts in MRO Part Warranty screen. \n\nPlease handle logic to display Blank for Lot # in MRO Part Warranty screen \n\nData: \npart RD-AC1160-13, SN G119347","Primary Defect","System displayed value of lot as ## when searching for the serial controlled part in MRO part warranty screen.","No - No",null,"Logic has been modified to replace null in the place of ## to fetch in the search criteria on MRO part warranty screen.","Tested in FS server \n\nScreen: Warranty Management->MRO Warranty->Manage Parts under MRO Warranty. \nWhen the serial number is different than Mfr serial, system validates properly as below ( Panasonic). \n\nUnable to process row # \"1\". Please enter a valid Mfr. Serial # for the Part-Serial # combination. \n\nFix working fine."]
["AHBG-36092","Mechanic Anywhere","The required process parameter of the feature \"AHBG-24092 Ability to display Tasks in a different color based on Alert Date\" is not available for testing the feature","The required process parameter of the feature \"AHBG-24092 Ability to display Tasks in a different color based on Alert Date\" is not available for testing the feature. \nDisplay Block Task in “AMBER” colour when the Base Task reaches Alert Date/Value?”, \n“Reference Date for Overdue and Alert calculation with respect to the Current Date” and \n“Show a Task as Overdue if Planned Start Date is greater than Schedule Date”","Secondary Defect","Define process entities code is missed","No - No",null,"DSTCA,DSTO,DSTOA , this code has been added into common object","Fixed and verified"]
["AHFG-19301","Mechanic Anywhere","Level code is not fetching in sequence order","On click of Help on configuration, Level code is not fetching in sequence order","Primary Defect","Due to incorrect logic, System is not fetching the configuration items in a sequence of level code","Yes - Only Fix Provided",null,"Fix has been provided to fetch the configuration items in a sequence of level code on click of Help on PositionCode in MechAnyWhere","Tested the Issue in Mechanic anywhere FS ST environment \n\n1. Validated the Sequence of the configuration items from the Help Icon of the Configuration. The Configurations are getting arranged and displayed properly as per the Expectation."]
["AHFG-19152","Mechanic Anywhere","Mech Anywhere MR Remarks not showing in MR screen.","add part and remarks and create mr \ncheck snap shot","Primary Defect","System failed to populate entered remarks while click on Add Parts and Create MR","Yes - Only Fix Provided",null,"Fix has been provided to save the Entered Remarks while click on Add Parts & Create MR","Data: \n1. Launch a package for the aircraft 101 in Mechanic Anywhere \n2. Select a discrepancy and create a part request \n3. Enter remarks \n4. Launch View Material Request in desktop for the material request \n5. The remarks are shown correctly \n\nEnvironment: FS ST"]
["AHFG-18796","Material Request","system allowing to create and edit material request document with different customer stock status with one trading number","system allowing to create and edit material request document with different customer stock status with one trading number","Primary Defect","system allowing to create and edit material request document with different customer stock status with one trading number","No - No",null,"validation has been handled not to select different stock status with one trading partner details in the create and edit material request document","Data: \n1. Create a material request MR-004047-2018 with a trading partner and a customer stock status \n2. In Edit Material Request change the customer stock status to a stock status that is not valid for the trading partner \n3. An error is shown \n\nEnvironment: FS ST"]
["AHFG-19308","Maintain Sundry Payment","Relaxing the validation of taxable amount","Right now we cannot enter taxable amount higher than line amount \nthe validation should be removed.","Secondary Defect","User has requested to relax the validation for modifying the taxable amount more than the Line value in case of Grossing up GST.","No - No",null,"Validation has been relaxed as per request, wherein modification of Taxable Amount in TCD screen more than the Line value shall now be permitted.","Server: FS-ST \n1. Created a Sundry Payment Voucher SPV-000608-2019 \n2. Added Tax to the voucher and modified the taxable amount to be higher than the line value. \n3. On click of compute, system computed the Tax Value based on the modified Taxable Amount \n4. Authorized the Sundry Payment Voucher and verified the postings."]
["AHFG-19125","Loan Order","Not able to raise Loan order","On Clicking Create Loan order in Create Loan order screen, \nsystem displays following error message. \n\n\"Loan for\" is \"Self\" \n\nUnable to process. Aircraft Reg # entered is not owned by \"Trading Partner #\" entered. Please enter valid Aircraft Reg #.","Primary Defect","System validated during creation of Loan order when aircraft reg# is not null.","No - No",null,"logic has been modified such that system will validate when loan for option is for customer and when A/c Reg # is not null.","Data: \n1. Launch Create Loan Order \n2. Create a loan order for the part 0-0440-4-0011:36361 \n3. The loan order is created successfully \n\nEnvironment: FS ST"]
["AHFG-18979","Loan Order","While confirm the loan order issue Error is showing","While confirm the loan order issue Error is showing","Primary Defect","system not allowing to confirm the loan order issue document when the Loan type is exchange","No - No",null,"Logic handled properly to allow the confirm the loan order issue document when the Loan type is exchange","Data: \n1. Launch Confirm Issue \n2. Search for an exchange type loan order \n3. Confirm the issue \n4. The loan order issue is confirmed successfully \n\nEnvironment: E5S ST"]
["AHBG-36048","LineAnywhere","LAW - E5D - FS Merging regularization","E5D - FS Merging regularization","Secondary Defect","E5D - FS Merging regularization","No - No",null,"E5D - FS Merging regularization","Latest Object regualrized"]
["AHFG-18800","Line Anywhere","Root Cause fix : APPA-3153 Violation of PRIMARY KEY constraint 'PK_Dp_DpDef_Disc_Deferral_Dtl'. Cannot insert duplicate key in object 'dbo.DP_DPDEF_DISC_DEFERRAL_DTL'. The duplicate key value is (MRP0004929, 2). The statement has been terminated.","Station : SYD Package #: LP006053193 Error : Violation of PRIMARY KEY constraint 'PK_Dp_DpDef_Disc_Deferral_Dtl'. Cannot insert duplicate key in object 'dbo.DP_DPDEF_DISC_DEFERRAL_DTL'. The duplicate key value is (MRP0004929, 2). The statement has been terminated.","Secondary Defect","MR # is not stamped against the deferred discrepancy if the same aircraft is refine loaded again without clearing the device.","No - No",null,"MR # is not stamped against the deferred discrepancy if the same aircraft is refine loaded again without clearing the device. Code logic modified to take the MR # from Main DP table and stamp it in Staging DP table during transfer.","Applied the fix in FS ST and verified. Deferral reason got updated correctly. \nPackage # \nVP011057-2019 \nVP011087-2019 \nVP011118-2019 \nDiscrepancy # \nCDP-040482-2019"]
["AHFG-18671","Line Anywhere","AME LP005221860 (N718AN) error \"CR022013601 * A/C Level # and A/C Position # entered are not valid for the Aircraft Reg # N718AN.* A/C Level # is invalid. Please enter valid A/C Level #.* A/C Position # is invalid. Please enter valid A/C Position #.\"","Checked the data and following is the observation \nCR #: CR022013601 \nRemoved part/serial # is available on position IFE-CS3 in aircraft configuration. But in the package summary report it is showing as IFE-CS2 \n\nCR #: CR022013602 \nRemoved part/serial # is available on position IFE-CS2 in aircraft configuration. But in the package summary report it is showing as blank. \n\nCR of object type component is generated without a position code against it. Seems like data got corrupted during transfer.","Primary Defect","Unable to simulate the issue reported. Not sure that user has modified the CR details in Transfer pop-up screen. To identify the problem, log table will be added to capture the CR data transferred from Offline.","No - No",null,"Unable to simulate the issue reported. Not sure that user has modified the CR details in Transfer pop-up screen. To identify the problem, log table has been added to capture the CR data transferred from Offline.","Base Server : FS ST. \n\n1. Pre-Load The Station \n2. Refine Load the Aircraft #. \n3. Created package \n4. Created Task / DP \n5. Performed CR against the Task \n6. Transferred the Package successfully \n7. Verified the Log table - Data Inserted succesfully. \n\nResult: Every CR Transaction will recorded in this \"lmech_flog_tlgcr_tech_log_cr_dtl_log\" Log Table."]
["AHFG-19021","Line Anywhere","APPA-3316-Root Cause and Fix: Violation of PRIMARY KEY constraint 'Flog_TLgMn_Tech_Log_Hdr_PK'. Cannot insert duplicate key in object 'dbo.FLOG_TLGMN_TECH_LOG_HDR'.","Able to validate the processed packages in transfer package screen","Primary Defect","The Primary Key error is coming due to the completed status package was validated and processed again. Data Patch to be provided to correct the corrupted data.","No - No",null,"To avoid the process records for validate/process again, have introduced additional validation by referring the status from stage queue table. And update of validation and pending status also restricted for the completed/processed records by adding additional where clause.","Tried to validate the processed/pending/short closed packages, its not allowed to processed. its throwing error as \"Unable to process row # %d. Package # \"%s\" is already in Pending/ Processed/ Short Closed status.\". \n\nTried to validate the error packages, its validated successfully."]
["AHFG-19151","Line Anywhere","Data missing in View Resource Consumption screen.","Package #: AD005099571 \nTwo tasks are available in View Work & Sign-off Information screen but only one task is available in View Resource Consumption screen.","Primary Defect","Task's base model is B787-8 and Aircraft's model is B737-800. Even though task is effective on B737-800, system failed to retrieve the data. It is incorrectly comparing the aircraft's model with base model","No - No",null,"Task's Model effectivity has been considered while fetching the data","Data: \n1. Open a package for the aircraft 101 and add tasks which have base model as A320 but are effective to 101's model \n2. Complete and close the tasks \n3. The View Resource and Sign off information show all the tasks \n\nEnvironment: FS ST"]
["AHFG-18862","Line Anywhere","Kill State error during Line Anywhere pre-load","While doing pre-load the app threw the following error : \n\nCannot continue the execution because the session is in the kill state.A severe error occurred on the current command. The results, if any, should be discarded.","Primary Defect","Needs to change the data type from INT to BIGINT of below column in the mentioned table. Table: LMech_Data_Load_File Column: LM_DL_uniqueid bigint","No - No",null,"Data type changed from INT to BIGINT of below column in the mentioned table. \nTable: LMech_Data_Load_File \nColumn: LM_DL_uniqueid bigint","Change of data type from int to big int working without any issues in site servers and base servers."]
["AHFG-18819","Line Anywhere","Mod # dropped off for Serial #: G590021 removed from the aircraft via LAW","Mod # dropped off for Serial #: G590021 removed from the aircraft via LAW \n\nIn CR, the Mod out is 2. In Record Part Serial Mod details, there is no entry. \nSaw that Return is in Confirmed status.","Primary Defect","MOD# given for the CR's recorded with Serial Type - Existing in LAW is not getting updated in SMN during transfer of package into Online. This should happen if there were no MOD defintion already exists for that Part - Serial in Online","No - No",null,"MOD# given for the CR's recorded with Serial Type - Existing in LAW is not getting updated in SMN during transfer of package into Online. This should happen if there were no MOD defintion already exists for that Part - Serial in Online. Code logic modified accordingly.","Verified in FS ST with the below steps \n1.Preload device \n2.Refine load an aircraft \n3.Create a package \n4.Add a task \n5.Enter a Part - Serial in Removal Section. Part - Serial should be there in the Configuration of aircraft \n6.Enter the MOD#(s) \n7.Save the CR \n8.Confirm the CR \n9.Complete the task \n10.Transfer the package \n11. Check the MOD # in SMN once the package is processed. \n------------------------------- \nData : \nPAckage : VP011314-2019 \nCR # :REPL-092651-2019 \nPart # :0506252:P9784 \nSerial # :51184-13 \nMOD # : 1"]
["AHFG-19320","Line Anywhere","Packages which are completed are not getting closed by the scheduler.","There are 17 packages in production server which are older than a day in completed status but not taken up for closure by the scheduler. Request to analyse why the packages are not getting closed automatically and provide patch to close it.","Primary Defect","Packages which are completed are not getting closed by the scheduler due to 1. package status is updated as NULL 2. Some cancelled packages transferred 3.Completed packages are picked by closure scheduler but not successfully closed the packages.","No - No",null,"PFB Fix Details, \n1. Fix Provided for changing the package status as “Planned” if package having work units in Deferred and Cancelled / only Deferred / only Cancelled. \n2. Fix Provided for the validation to restrict the validate and transfer for cancelled packages from iPad.","Test Sequence:- \nScenario-1 \nCreated a package and added task. Cancelled that task. \nVerified if the package still retains 'Planned' status. \n\nScenario-2 \nCreated a package and added task. Deferred that task. \nVerified if the package still retains 'Planned' status. \n\nScenario-3 \nCreated a package and added 2 tasks. Deferred one task and Cancelled the other task. \nVerified if the package still retains 'Planned' status. \nNow Cancelled the package \n\nScenario-4 \nCreated a package and added 3 tasks. Deferred one task, Cancelled the other task and Completed the other task. \nVerified if the package still retains 'Planned' status after the 2nd task is cancelled. After the final task is completed, verify if the package goes to 'Completed' status. \n\nNow validate all the 4 packages. System should validate for the 1st three packages \"Unable to process. Validate cannot be performed for work Package \"%s\" in \"Planned/ In-Progress/ Cancelled\" Status.\" \nVerify if the last package if transferred to online successfully"]
["AHFG-18594","Inventory Operations Hub","String or binary data would be truncated. The statement has been terminated error is thrown on click of STI.","String or binary data would be truncated. The statement has been terminated error is thrown on click of STI.","Primary Defect","data size is not matching with schema table","No - No",null,"table schema has been increased","Data: \n1. Launch Inventory Operations Hub \n2. Launch Transfers and select the stock transfer issue 789900953887 \n3. No error is shown \n4. Confirm the issue successfully \n\nEnvironment: E5S ST"]
["AHFG-19176","Integration","Invoice mismatch between Ramco screen vs stag table. Refer CSI0000206","CSI0000206 in Ramco shows value as 15114.18. whereas the stage table has the total as 15094.77","Primary Defect","Decimal value of actual usage is not considered on usage release. Logic has to be corrected.","No - No",null,"Decimal value of actual usage is not considered on usage release. \nColumn datatype has been modified. \nLogic has been corrected","Fix has been verified and it is working fine. \nSelected the milestone and generated the release and the value is displayed. \nGenerated the invoice and verified. \nFST \nCI-000456-2019"]
["AHFG-19202","General Issues","Mech Anywhere-Elog Page issues","Bug 11: Date and Time format is displayed wrongly \nBug 12: Smart Search is not working correctly. \n\nWhen user enters ‘D’ character in Aircraft Reg # field, system fetches values which are not starting with D in smart search look up \n\nWhen user enters ‘D-‘character in Aircraft Reg # field, system fetches no records found in smart search look up. \nBug 13: Date and Time Field in header (Near station) is showing only Date value \nBug 14: Date and Time in Manage Package Cluster is showing wrong values. \nBug 15: FH value is displayed wrongly in Mech anywhere \n\nBug 16: From Station smart search is not working. \nUser tries to enter ‘F’ in From station, but system shows no records in Smart Search filter look up. \n\nIf same tried from To station, system correctly fetches data in smart search. \n\nBug 17: Date and Time format selection in Arrival and Departure is wrong. \nBut on saving system correctly saves the data. \n\nBug 18: Arrival Date and Time cannot be lesser than Departure Date and Time. \n","Primary Defect","Logic was not handled to fetch the FH value in Decimal format in MechAnyWhere","Yes - Only Fix Provided",null,"Fix has been provided to fetch the FH value in Decimal format in ELog page in MechAnyWhere","Data: \n1. Launch a package for the aircraft 101 in Mechanic Anywhere \n2. The FH value is equal to the FH value in the desktop \n\nEnvironment: FS ST"]
["AHFG-17796","flyanywhere","Synonyms incorrect for the previous Hot-Fix objects","Synonyms incorrect for the previous Hot-Fix objects","Primary Defect","EFB database is not considered for the synonyms creation","No - No",null,"EFB database is considered for the synonyms creation","verified in FS"]
["AHFG-19246","Flight Sheet","Modified No of passengers in parameter infor but billing head got disappeared in Main info tab","Modified No of passengers in parameter infor but billing head got disappeared in Main info tab \nFS-000002-19","Secondary Defect","Line# mismtach ,Logic has to be corrected","No - No",null,"@linenumber is not handled correctly in join condition,which has been fixed here. \nLogic has been corrected","Verified the fix and it is working fine. \nBilling head doesn't vanish on specification of parameter value. \nfst \nFS-000171-2013"]
["AHBG-35391","Flight Log","Ability to configure the user defined rules for removal assessment parameters(NFF rules & LTR rules)","Ability to configure the user defined rules for removal assessment parameters(NFF rules & LTR rules)","Primary Defect","Ability to configure the user defined rules for removal assessment parameters(NFF rules & LTR rules)","No - No",null,"Ability to configure the user defined rules for removal assessment parameters(NFF rules & LTR rules)","Ability to configure the user defined rules for removal assessment parameters(NFF rules & LTR rules)"]
["AHBG-35934","Flight Log","E5D to FS merger deleted objects Checkin","FS","Primary Defect","Merger Impacted Objects","No - No",null,"BasFltLog","Merger Impacted Objects"]
["AHFG-19515","Flight Invoice Release","Getting an string or binary data error while trying to generate the flight invoice release.","Getting an string or binary data error while trying to generate the flight invoice release.","Primary Defect","The character length needs to be increased inorder to overcome string or binary data error.","No - No",null,"Length increased to overcome string or binary data error while generating the flight invoice release.","Env: http://bavnwarcnv04/Extui/ \n\nGenerated flight invoice release and no error was thrown."]
["AHFG-18940","Flight Contract","Provision to non-mandate A/C reg # if A/C Model # is duplicated across lines with same effective period in Flight Contract","Background: \n\nIn 4X, GHC has defined same A/C models defined in multiple lines within same effectivity and different rates were given for each line. \n\nFor Example, GHC have committed to customer that 18 Aw139 aircrafts would be provided and each will be defined in single line with different effectivity and rates. With this kind of definition, GHC have an advantage of fly any aircraft against a line and charge accordingly. \n\nDuring JL creation, GHC will manually provide the line # for contract evaluation. \n\nHence provision is required to non-mandate A/C reg # if A/C Model # is duplicated across lines with same effective period in Flight Contract \n\nNote : This should be handled as project specific fucntionality for GHC","Secondary Defect","Provision is required to allow duplicate definition in Flight Contract - A/C Coverage across line","No - No",null,"Validation restricting the duplicate A/C coverage definition has been relaxed in Flight Contract. \n\nThis fix has been done specifically for GHC alone. \n\nNote : Due to this fix, Line # should be manually provided during contract evaluation for flight sheet creation. System could not evaluate contract automatically as duplicate definition allowed in flight contract.","Scenario: \n1) Defined A/C model in multiple lines. \n2) Provided different rate definition for each line. \n3) Generated journey log and Flight sheet for an Aircraft belongs to respective model \n4) On generation of Invoice release, proper rate has been fetched."]
["AHFG-18932","Finance Book Processing","During Confirm Return, Finance postings failed - Posting Parameters Invalid Unable to process. Return# \"MRT0022475\" not confirmed since finance posting failure error is thrown","During Confirm Return, Finance postings failed - Posting Parameters Invalid Unable to process. Return# \"MRT0022475\" not confirmed since finance posting failure error is thrown","Primary Defect","Unconfirmed return table not getting inserted in few scenario from AME","No - No",null,"Log table introduced to track the scenario and fix the RCA. \n","Ensured Unconfirmed return detail table is getting inserted during AME closure and return confirmation happened successfully without any error."]
["AHFG-19359","Finance Book Processing","VAB Supplier suspense Service report performance issue","VAB Supplier suspense Service report performance issue","Primary Defect","The reported issue occurred due to report executing for long time for supplier suspense service report due to which index script added to avoid the performance issue","No - No",null,"Due to performance issue in supplier suspense service view account balance report, Index added for view account balance table and Non clustered index added for related company summary table.","> Verified that on click of 'Export', system executed the process and the report got extracted accordingly. \n\n\nServer - FS Server"]
["AHFG-18821","Engineering Reports","Engineering Document Compliance Status Report - filters are not working, selected the document type EAD but the report is generating with all the document type.","Engineering Document Compliance Status Report - filters are not working, selected the document type EAD but the report is generating with all the document type.","Primary Defect","Report logic was not handled for source,source document type,Engineering schedule types and task no.","No - No",null,"Report logic for the search filters have been fixed.","Tested and verified in FS server \n\n1. In Engineering Order Compliance Report, \n2.Searched on the basis of Source Doc. Type and Source in MCR attributes. \n3.Searched on the basis of Engineering Schedule type \n4.Searched on the basis of Task# in Addl. Search On \n\nWhen generated EO Compliance Report, system showed only those items based on the Search given."]
["AHFG-18684","Engineering Order","Blank search does not work in Manage Eng. Document",null,"Primary Defect","Blank search did not work in Manage Eng. Document because EO search value in back end was declared as \"null\"","No - No",null,"As per the requirements of the customer, the query was changed. Now the blank search works when searched for an EO","Tested and verified in FS server \n1. In manage EO screen, gave a blank search. \nSystem retrieved all EO. \n2. In manage EO screen, searched a specific EO# \nsystem only retrieved that EO#"]
["AHFG-19042","DW Reports","Even though date filter From Date / Time and To Date / Time is given as 01 Sept. 2019 to 30 Sept 2019, system retrieves very old data as well.","Even though date filter From Date / Time and To Date / Time is given as 01 Sept. 2019 to 30 Sept 2019, system retrieves very old data as well. date search criteria is not working properly in Timesheet report","Secondary Defect","Due to technical issue with date filter, date provided in the search criteria is not properly recognised by the system due to timesheet data is fetched wrongly.","No - No",null,"\nReport Configuration was corrected for Date Field. \n\nChanges have been done in the timesheet report to eliminate the technical issue with date filter. \n\nNow the date provided in the search criteria has been recognised by the system properly.","Scenario: \n\n1) Launched Timesheet report for the month of sep-2019. \n2) Data has been fetched properly."]
["AHFG-18746","Deployment Process","404 error in load balancer","404 error in load balancer. Please clear the incorrect file links. Refer the attachment for the list.","Primary Defect","404 Error - Failed to load resource as the required deliverables were missing.","No - No",null,"All the missing deliverables were added to load the web content.","Front End Deliverables(empty files) added for the 404 load balancer error. \nTesting not required."]
["AHFG-19446","DCube","Unable to generate component maintenance due report dcube","Unable to generate component maintenance due report dcube","Primary Defect","Due to the datatype mismatch system throwing sql error.","No - No",null,"Now data type has been changed.","Tested and verified in FS server \nComponent Maintenance > Reports-Component maintenance > Comp maintenance Due report \n1. Generated Component maintenance Due report for a component. System generated the report successfully. \n2. Confirg. Mgmt > Aircraft > Reinitialize and Update parameter values \n3. gave the same component number and updated in Since New value and gave Update Option as 'New' \n4. Generated component maintenance due report again. Report was generated with the newly updated values."]
["AHFG-19411","Customer Service Quote","TERMS OF PAYMENT DON'T APPEAR IN QUOTES OR PROFORMA INVOICE","Although Terms of payment are stablished in the customer information (in commercial information - pay terms) those terms don't appear in quotes nor in proforma invoice. \n\nBest regards, \nMarina","Secondary Defect","Logic has to be handled to fetch the defined PayTerm in the report","No - No",null,"Logic has been handled to fetch payterm in the quotation report.","PayTerm is displayed in the report. \nVerified the fix and it is working fine."]
["AHFG-18718","Customer Service Order","regularise E5s-FS csb_order_level_wrapping_price - (ABTI-6291 , ABTI-6837)",null,"Secondary Defect","regularise E5s-FS","No - No",null,"regularise E5s-FS","Regularise E5s-FS"]
["AHFG-19140","Customer Service Order","User created one CO CO-000353-2019 and system has created 2 Visit package, one for SE-JPN and one for N849YB.","User created one CO CO-000353-2019 and system has created 2 Visit package, one for SE-JPN and one for N849YB. \n\nVP-000604-2019 \nVP-000605-2019 \n\nwhat should we do now?","Primary Defect","System is allowing to change the Aircraft status to Active though manufacturing Serial of the Aircraft is already available in the system.","Yes - Only Fix Provided",null,"Fix has been provided to validate while launching Edit Aircraft Record for the Aircraft (for which Change Aircraft Recorded and it is in Fresh & Initiated status) \n","Data: \n1. Launch Change Aircraft Registration number and change 102 to 102-AAA \n2. Launch Edit Aircraft Record for 102-AAA \n3. The error \"Aircraft Reg. # \"102-AAA\" has been created because of Aircraft Reg. # change action. Modification of this record is disallowed\" is shown \n\nEnvironment: FS ST"]
["AHFG-18924","Customer Service Invoice","Once again CI-000310-2019 Invoice sum , tax and total is wrong","Once again CI-000310-2019 Invoice sum , tax and total is wrong. \n","Primary Defect","When more than one CO is available in the Invoice, Charges are printed multiple times against each CO","No - No",null,"Issue mentioned in the rtrack is already resolved. As soon as the Invoice is shown as exception during inconsistency tracking, data update has been provided to resolve the issue and root cause also has been fixed. \n\nAs part of this rtrack, duplication of additional charges has been fixed. If more than one co is available and if the charges are defined against one particular CO, then the charges would be printed only below the respective CO.","Scenario: \n1) Have generated above mentioned Customer Service Invoice by combining 2 COs. \n2) Added additional charges and discounts against both COs. \n3) On printing the Invoice, Charges and Discounts displayed properly against respective COs."]
["AHFG-18753","Customer Service Invoice","we are not finding invoices for CO-000250-2019 and CO-000251-2019 from View invoice or Authorize invoice.","we are not finding invoices for CO-000250-2019 and CO-000251-2019 from View invoice or Authorize invoice. \n\nhowever we found the invoice from process invoice screenView invoice link","Primary Defect","If the Customer Order is not having any WO or Repair Order document associated to it, system is not fetching the Invoice in Edit/Authorize/View Invoice screen. As the Exec. doc # is shown in Invoice screen and the reported COs doesn't have the same.","No - No",null,"Irrespective of whether the Customer Order is having the Exec. doc # ornot, system will always fetch the Invoices generated against CO in Edit/Authorize/View Invoice screen. \nIf the Exec. doc # is available against CO then the same would be displayed in the Invoice screen or else the Exec. doc # will be left blank.","Scenario: \n1) Launched Edit/view/Authorize Customer Service Invoice screen. \n2) Provided above CO # as ref. doc # and clicked search. \n3) Exchange Invoice created against the respective CO has been displayed. \nhttp://bavnwarcnv04/extui/extui/vwrt/LaunchPanel.htm"]
["AHFG-18952","Customer Receipt","System is automatically taking bank charges while creating receipt","System is automatically taking bank charges while creating receipt","Secondary Defect","The Reported issue occurred due to With holding tax initialization failure because of this system taking default value and deriving the cost.","No - No",null,"On creation of customer receipt with reference of no debit document, System is considering charge amount incorrectly due to which charge amount showing incorrectly in Header level information. With holding tax initialization failure because of this system taking default value and deriving the cost. Hence the logic has been handled to derive correctly.","Server: FS-ST \n1. Created a Customer Receipt without any reference document CR-000702-2019 \n2. Verified that the Charge Amount was displayed as \"0\" in the header \n3. Authorized the Receipt and verified the account postings. There was no additional accounting for any charge,"]
["AHFG-19573","Customer Order Management","execution release push not happening for defferred and incomplete task","execution release push not happening for defferred and incomplete task","Secondary Defect","Deferred tasks should not have the releasepush and incomplete task will have the release push.Logic has to be modified","No - No",null,"Provided fix that deferred tasks will not have the release push and incomplete tasks will have the release push. \nLogic has been modified","Verified the fix. \nDeferred tasks will not have the release push and incomplete tasks will have the release push."]
["AHFG-19495","Customer Order","Validations added in Customer Order due to Sale Order data issues - Please regularize",null,"Secondary Defect","Manage Customer Order --> Shipping Terms and Billing Terms validations regularization.","No - No",null,"Manage Customer Order --> Shipping Terms and Billing Terms validations regularized.","Project related validation handled. \nNon Destructive cycle has been carried out and successfully generated CO"]
["AHFG-19205","Customer Order","Deadlocks","14/10/2019 objectname=AvnAppDB.dbo.cso_exec_commercial_info 24 \n\n17/10/2019 objectname=AVNAPPDB_TEMPDB.dbo.csb_queue_lookup_tmp indexname=csb_queue_lookup_tmp_cidx 12 \n\n","Primary Defect","Due to high volume, Performance issue exists on creation of Work Order / addition of Task in Customer Order based Work Orders","No - No",null,"Performance tuning has been done in order to improve the performance during WO creation and Task addition","Env: FS Forward Line. \n\nOnly positive scenario was tested. \nScenario: \n1) Have opened 3 work orders in parallel and added NST tasks. \n2) Performance issue / deadlock didn't occur."]
["AHFG-19574","Customer Order","Primary Work Center \"(null)\" does not exist, which is an invalid error message","Primary Work Center \"(null)\" does not exist, which is an invalid error message \nFirstly, the message should be Primary Work Center not entered. \nSecond, as Execution Facility is selected as external, the Work Center is not required to fill.","Primary Defect","It is resolved","No - No",null,"The Primary Work center is not required after fixed, So the error is not coming","The Primary Work center is not required after fixed, So the error is not coming"]
["AHFG-18875","Customer Order","Ref: APHE-1557 - If more than one A/C is having same MSN #, on approval of CO, AME document is getting generated for all A/C having the MSN specified in Customer Order","1) Generated CO against Aircraft by providing A/C Reg # as 'SE-JPN'. \n2) A/C MSN specified in CO is available for 2 Aircrafts. \n3) On approval of CO, Package got generated for both aircrafts","Primary Defect","If same MSN is available for more than one Aircraft, Package is generated for each A/C reg # on CO approval. During AME generation, A/C MSN alone is referred from CO.","No - No",null,"1) If the A/C Reg # is specified in the CO, then the package will get generated only for the respective A/C reg #. \n\n2) If the A/C MSN alone is specified in the CO, then A/C reg # for the MSN will be derived from Aircraft Master and Package will get generated for respective aircraft.","Scenario: \n1) Launched Manage Customer order screen. \n2) Provided A/C reg # as Se-JPN and evaluated Contract. \n3) Confirmed CO and Package got generated only for respective A/C reg # specified in the CO. \nFSST"]
["AHFG-19520","Customer Direct Invoice","Aviation Project -GHC 5x - AMCAGHX-1809 PACKSLIP ALREADY INVOICED BUT SHOWING AS PENDING IN FINANCE BOOK",null,"Secondary Defect","During Invoice part sale customer suspense knock-off entries are not happened","No - No",null,"Validation added for below scenarios: \n1) Non-happening of Part sale customer suspense knock-off entries during Invoice. \n2) Pack slip# is not cleared from Part sale customer suspense account even after happening of Knock-off entries during Invoice.","Tested and verified by creating Packslip invoice, knock-off entries happened during Invoice and cleared from Part sale customer suspense account."]
["AHFG-19050","Customer Direct Invoice","TCD has been modelled as flat but when entering TCD amount , on click of save system is not capturing modified values","TCD has been modelled as flat but when entering TCD amount , on click of save system is not capturing modified values \nIN-20/113","Secondary Defect","If TCD amount is modified for flat TCD, system is not recognising the modified TCD amount and always considers the amount provided initially during TCD addition","No - No",null,"Changes have been done in order to consider the TCD amount provided by user during modification of TCD Amount","Scenario: \n1) Launched edit misc. invoice screen for the invoice. \n2) Clicked TCD link and modified the Discount Amount. \n3) TCD amount has been modified and Invoice amount also adjusted accordingly. \nMIN-000904-2018 FST"]
["AHFG-19343","Customer Direct Invoice","UNABLE TO AUTHORIZE INVOICE INV000152-19","STRING OR BINARY DATA WOULD BE TRUNCATED. THE STATEMENT HAS BEEN TERMINATED. (INV000152-19)","Primary Defect","Due to Length of UOM errror has been displayed,Length of UOM has to be increased","No - No",null,"Due to Length of UOM errror has been displayed,Length of UOM has to be increased","Env: http://bavnwarcnv04/Extui/extui/vwrt/LaunchPanel.htm \nCustomer Direct Invoice# FINV-000027-2019 \n\n\nTried to authorized the CDI and it got authorized successfully. Only positive scenario was tested."]
["AHFG-19041","Customer Debit Credit Note","Unable to reverse the Credit Note Error is coming.","Unable to reverse the Credit Note Error is coming. \n\nCredit note : CCN9/000151/1019. \n\nPlease find the screenshot for your reference.","Secondary Defect","Customer Code holding Variable is defined with 16 Char length whereas it should be 18. Due to 16 length, Customer code was not formed properly and truncated to 16 characters.","No - No",null,"Length of the variable has been modified to 18 Characters.","> Verified that on provision of the Customer Debit/Credit Note # and on the click of 'Reverse' in Reverse Debit/Credit Note screen, observed that system processed the task accordingly. \n\nServer - FS Server"]
["AHFG-19019","Customer Balance Adjustment","Customer Prepayment Invoice does report correctly","Created a prepayment Invoice for AUD 196.23 Adjusted AUD 42.47 against an invoice Balance Unadjusted Value is 153.76 Customer Ledger, Ageing & Inquiry doesn't consider the prepayment invoice and showing a due balance of 42.47","Secondary Defect","The reported issue occurred as the Customer Prepay account adjusted information not properly updated against the customer prepayment Invoice. As a result system bring the same document again and again in Adjustment screen.","Yes - Only Fix Provided",null,"The reported issue has been fixed by modifying the system logic to update properly Customer Prepay accounts adjusted information against the customer prepayment Invoice. Hence, the same document will not come again for Adjustments.","Server: FS-ST \n1. Created a Customer Prepayment Voucher CPI-000115-2019 \n2. Created a Customer Receipt CPI-000115-2019 and adjusted the Prepayment Voucher \n3. Created a Misc Invoice and authorized it MIN-000982-2019 \n4. In the Customer Balance Adjustment screen, retrieved the Misc Invoice and Prepayment Voucher and adjusted both. \n5. Launched Customer Ledger, Ageing and verified that the Prepayment Voucher did not have any outstanding balance."]
["AHBG-34076","Customer","User Defined field spelling is incorrect.","User Defined field spelling is incorrect.","Secondary Defect","User Defined field spelling is incorrect.","No - No",null,"Spelling corrected in the UI","Verified"]
["AHFG-19613","Customer","Unable to launch Collaborate from Customer Master","Edit Customer Record --> Collaborate \n\nUnable to launch Collaborate from Customer Master","Secondary Defect","File has not been loaded,Template File has to be changed","No - No",null,"Template file has been changed","Verified the fix \nAble to launch the collaborate. \nFST"]
["AHBG-35364","Customer","Effectivity to provided as 24 and the modified to 25 in the header and deleted in the ML - ML is saved but header is not saved","Effectivity to provided as 24 and the modified to 25 in the header and deleted in the ML - ML is saved but header is not saved","Primary Defect","Updation of the effective to was not handled at the header level.","No - No",null,"when the effective to value is updated , same has been saved and refreshed.","Force reviewed for shipment"]
["AHBG-35379","Customer","Error/Success message specified in the RCN is different from the actual message","Error/Success message specified in the RCN is different from the actual message \n\nActual msg: \n\nPart Sale List # of Rev # \"11\" is already existing in 'Fresh' status. Please activate the same to create further revisions. \n\nRCN: \n\nPart Sale List# of Rev# '%%' is already existing in 'Fresh' status. Please activate the Rev # '%%' to create further revisions. \n","Primary Defect","Error Description was corrected as mentioned in the FID Document","No - No",null,"Error Description was corrected as mentioned in the FID Document as \n'Part Sale List# of Rev# '%%' is already existing in 'Fresh' status. Please activate the Rev # '%%' to create further revisions.","Verified"]
["AHBG-35083","Customer","In the Scrap rate column it does not allowing to save the value less 100","In the Scrap rate column it does not allowing to save the value less 100 value enter is that 99.9999","Primary Defect","The BT for scrap rate changed. The precision for the column is set as 0.","No - No",null,"The BT for scrap rate changed.","The issue is forced review for shipment"]
["AHBG-35343","Customer","On confirm customer is vanishing","On confirm customer is vanishing","Primary Defect","Customer NO. is not outed while refreshing the screen on confirm","No - No",null,"Customer No + customer Name is concatenated and outed while refreshing the screen on confirm","Verified"]
["AHBG-33874","Customer","Trn-Bsg-R59-COM1-SP27-QPA-Ability to define the QPA for Customer's Fleet at Customer Master","Trn-Bsg-R59-COM1-SP27-QPA-Ability to define the QPA for Customer's Fleet at Customer Master","Primary Defect","Trn-Bsg-R59-COM1-SP27-QPA-Ability to define the QPA for Customer's Fleet at Customer Master","No - No",null,"Trn-Bsg-R59-COM1-SP27-QPA-Ability to define the QPA for Customer's Fleet at Customer Master","Force reviewed for shipment"]
["AHBG-35258","Customer","data not saved in part list","data not saved in part list","Primary Defect","Modeflags not handled correctly","No - No",null,"Modeflags not handled correctly. This was corrected","Verified in E5DST"]
["AHFG-19516","Customer","\"The delivery Point is set. However, in line level, the dropdown selected is not able to be saved\"","Unable to process Row # \"1\". Delivery Point \"HKG- Terminal 1 - Gate 1\" is invalid. Please enter a valid Delivery Point","Primary Defect","validation handled wrongly","No - No",null,"validation handled wrongly","FS ST"]
["AHFG-19485","Customer","No option for \"Status\" Dropdown","no result","Primary Defect","fixed","No - No",null,"the status is available now","verified"]
["AHBG-35077","Customer","Part Description and Mean shop processing Time is not displayed","Part Description and Mean shop processing Time is not displayed Manage customer specific RSPL","New Scenario","Part Description and Mean shop processing Time is not displayed","No - No",null,"Part description should be fetched from part master.","Verified"]
["AHBG-35079","Customer","Inconsistency in displaying the RSPL Rev. #","Inconsistency in displaying the Revision no - make some changes click save button the status change to fresh and click confirm the status change to active status and view the RSPL Rev. #","New Data Condition","Order by clause not used properly","No - No",null,"Order by clause not used properly","Verified"]
["AHBG-35084","Customer","Invalid error is throwned while enter alphabetical character in the Numeric column","Invalid error is throwned while enter alphabetical character in the Numeric column","New Data Condition","Change in datatype for the control","No - No",null,"Change in datatype for the control","Verified"]
["AHFG-19402","Create Purchase Request","System validated to select the select the customer as \"Group Company\" even the custmoer was set as Group Company during Purchase Request creation with Purchase For as \"Customer\"","System validated to select the select the customer as \"Group Company\" even the custmoer was set as Group Company during Purchase Request creation with Purchase For as \"Customer\" \n\n1) Open MR listed in Plan Material. \n2) Selected that MR and clicked Create Purchase Request link. \n3) System default all the details. \n4) Selected the Purchase For as \"Customer\" and provided Cutsomer # \n\nOn click on Create Purchase Request, System validated \"Unable to process. Trading Partner # is not a group company. PR Expense Type can be \"Capital\" only if the Pur. For Trading Partner is a Group Company and if the CAPEX PO on behalf of Dest. Company is set as \"Allowed\".\" \nthough the customer # CUAMO-000012-F is Group companty and the Set option set.","Primary Defect","Logic for validating whether the trading partner related to group company is not handled based on source and destination company","No - No",null,"Logic for validating whether the trading partner related to group company is has been corrected based on source and destination company.","Data: \n1. Open MR MR-004760-2019 listed in Plan Material \n2. Selected that MR and clicked Create Purchase Request link \n3. System default all the details \n4. Selected the Purchase For as \"Customer\" and provide Cutsomer # \n5. Create the purchase request \n6. The purchase request is created successfully \n\nEnvironment: FS ST"]
["AHFG-18963","Cost Centre Rule Definition","Search function is not working in View / Delete Sale Defn. screen","Search function is not working in View / Delete Sale Defn. screen. Even though definition is available, system doesn't fetch anything.","Secondary Defect","In View / Delete CCRD screens, logic is not available to load the \"Company\" value, hence system failed to fetch all the definition in View and Delete CCRD","No - No",null,"Logic has been modified to fetch the \"Company\" value in the corresponding drop down","> Launched the View / Delete Sale Definition screen \n> On the click of 'Search', observed that system retrieved all the earlier definitions that has been made in accordance with the Search criteria. \n\nServer - FS Server"]
["AHFG-19353","Cost Centre Rule Definition","Not able to confirm stock issue if CCRD sales definition is on Stock status","Not able to confirm general issue for part sales if CCRD sales definition is on Stock status","New Data Condition","Stock status for the part sale ccrd was not updated on confirm stock issue","No - No",null,"Fix has been provided to update the respective stock status to fetch the CCRD on confirm stock issue.","\nTested and verified by confirming the mentioned Issue document. \n\nTest Server: https://amptest01.ramcouat.com/RVW/extui"]
["AHFG-17963","Configuration","Able to create same Non-Seat Identifier in Manage Cabin Layout. In LAW, the LOPA wont launch and it gives error - Duplicate Seat.","Able to create same Non-Seat Identifier in Manage Cabin Layout. In LAW, the LOPA wont launch and it gives error - Duplicate Seat. \n\nThere should be a validation to prevent duplication of the non-seat identifier in Manage Cabin Layout screen.","Primary Defect","Seq# and starting & Ending duplicate validation is not available across deck level.","No - No",null,"Seq# and starting & Ending duplicate validation introduced across deck level.","preload and refine load A/C: A6-APA \nBelow issues observed after package creation. \n1) Discrepancy - Cabin position is getting duplicated after it is selected in LOPA. Issue is also occurring when cabin position # edit icon is clicked. \n2)Task - During selection of equipment category in e-sign off page, the list is displaying cabin position #’s instead of equipment category. \n3) Component replacement - Same issue mentioned above happens when opening the Mod # column in CR screen."]
["AHBG-35816","Configuration","In tab click , the syntax error coming in tech records hub.","In tab click , the syntax error coming in tech records hub.","Primary Defect","In tab click , the syntax error coming in tech records hub.","No - No",null,"In tab click , the syntax error coming in tech records hub.","In tab click , the syntax error coming in tech records hub."]
["AHFG-19311","Compliance Tracking and Control","System Shows incorrect NSD in IMPUC,","System Shows incorrect NSD in IMPUC, this is because during Approval of STE ( Rejected and confirming again) system updating the STE reference in AMP for already closed escalation. \nNote : Two escalated tasks are already closed and Two tasks are still open in this STE","Primary Defect","System showed incorrect value of NSD for a complied task whose STE was reversed and confirmed again.","No - No",null,"Logic was handled to ignore the previous complied value when the STE against the task was reversed and approved.","Tested and verified in FS server \n\n1. Took a task which was already complied. \n2. Created an STE for the task and confirmed it from Planning board \n3. In Approve Escalations screen, Rejected the STE \n4. Went to Inquire short term escalation screen and edited the same STE and confirmed again. \n5. Approved the STE \nIn IMPUC screen, the NSV value was updated according to the latest STE approved for that task. \n"]
["AHFG-19479","Asset Planning","System is mandating the Sub Analysis Code while creating Assets Proposal","System is mandating the Sub Analysis Code while creating Assets Proposal & there is no mapping of Analysis and Sub analysis code","Primary Defect","Sub analysis code error, Sub-Analysis code mandatory was handled as per the mapping available.","No - No",null,"Sub-Analysis code mandatory was handled as per the mapping available.","Verified in HAECO environment."]
["AHFG-18882","Asset Disposal","Unable to do asset class transfer - Getting error Book Value goes below salvage value","Unable to do asset class transfer - Getting error Book Value goes below salvage value \n\nAsset # FA000874","Secondary Defect","The reported issue occurred as the system validated whether book value goes below salvage cost when performing Asset Class transfer but actually it should not be validated as always whole Asset cost will get transferred on Transfer Asset.","No - No",null,"The reported issue has been fixed by relaxing the system validation to check whether book value goes below salvage cost when performing Asset Class transfer.","Tested and Verified in the following manner \n> Created an Asset Class Transfer from 'Land' to 'Rotables' \n> Observed that on the click of 'Preview Depreciation', system executed the process accordingly. \n> And on the click of 'Confirm Transfer', New Asset number for the respective new Asset Class got created accordingly. \n>Verified that the above sequence is working fine \n\nServer - FS Server"]
["AHFG-19013","Asset Depreciation Processing","System doesnt validate if the header FB provided which creating the Dep JV is same as asset FB, hence leading to mismatch of balance between GL - Sch of FA and Asset Details Report","System doesnt validate if the header FB provided while creating the Dep JV is same as asset FB, hence leading to mismatch of balance between GL - Sch of FA and Asset Details Report","Secondary Defect","The reported issue occurred as the validation to check the Finance Book selected is the correct one for the selected Assets has not been handled in Create Depreciation Adjustment screen.","Yes - Only Fix Provided",null,"The reported issue has been resolved by adding validation to check the Finance Book selected is the correct one for the selected Assets in Create Depreciation Adjustment screen. In such scenario system will provide error message as \"Asset No. XXX and Tag No. Y was not Active for selected Finance Book - ZZZ\" on click of Create button.","Server: FS-ST \n1. Created a new asset IT-ITEQP-6 in the Finance Book \"AVEOS\" \n2. Processed depreciation for that asset. \n3. Tried to create a depreciation adjustment for that asset by selecting the FB as \"1\" in the create depreciation adjustment screen. \n4. Error popped up stating that the Asset # and Tag# does not belong to the selected FB, please modify. \n5. Selected the correct FB \"AVEOS\" and created the depreciation adjustment DAJ-000032-2019. \n6. The adjustment was created successfully without any error. Verified the account posting."]
["AHFG-19319","AP Statutory Extension","On Click of search documents are not getting retrieved","On Click of search documents are not getting retrieved","Primary Defect","Indian TDS tax type was not included","No - No",null,"Indian TDS tax type has been included.","Verified that on the click of 'Search', system retrieves all the invoices. \n\n\nServer - FS Server"]
["AHFG-18899","AMMEND PURF","UNABLE TO RECTIFY RETURN ADDRESS","NOT LETTING AMMEND PO , error message \"Unable to process row # 1 as Warehouse # \"AI-BOM-S01\" is not valid. Please enter a valid Warehouse # \nbut wont allow to change warehouse# to B-BOM-S050. \n\nIf EDIT TERMS AND CONDITIONS pressed, error message \" Unable to proceed as GR is under processing for this Purchase Order\" appears. \n\nhowever both the pgr-095627-18 and pgr-095904-18 for AIB00273318 are complete.","Primary Defect","System validated while clicking on Edit terms and conditions when amending the purchase order.","No - No",null,"Fix provided to modify the logic in order to check the status of the GR.","Tested in Air India training UAT and FS server, \n\nSelected the PO# Amend Purchase order #PO-000567-2017. \n-> Clicked on Edit terms and conditions \n-> System allowed to modify the RMA address without any error. \n\nFix working fine."]
["AHFG-18738","AME Hub","Work Reporting Hub : While trying to add tasks from due list in AME hub previous completed task adding automatically","We are creating outstation TECHLOGS in the system. So, after every completion of TECHLOG, selecting CREATE option in the AME Hub for the next TECHLOG Creation. Now when we try to add a due task while creating the package, the previously completed Task in previous TECHLOG is appearing automatically.","Primary Defect","while creating package in work reporting hub and added task from due list and again created package from hub and while adding task from due list previously added task added along with the current task","No - No",null,"Issue has been fixed by applying appropriate deletion of the task entry","Data: \n1. Launch Aircraft Work Reporting Hub \n2. Create a package for the aircraft 101 and add a task from due list \n3. Create a new package for the aircraft 101 and add a task from due list \n4. Only the selected task is added to the package \n\nEnvironment: FS ST"]
["AHFG-18947","Aircraft Maintenance Program","Deadlocks","objectname=AVNAPPDB.dbo.MP_CMPHIS_WUS_CMPL_HISTORY --84 locks \n\nobjectname=AVNAPPDB.dbo.MP_CMPHIS_WUS_CMPL_HISTORY indexname=MP_CMPHIS_WUS_CMPL_HISTORY_NCINDEX \n\n","Primary Defect","Deadlocks issue","No - No",null,"Update logic has been modified to avoid Deadlock issues","Tested and verified in FS server \n\n1. In IMPUC screen, updated the schedules for a task \nComplied the task \nsystem took much lesser time duration to update compliance/schedules \n\n2. In Record AME screen, performed Bulk Sign off for a package \nSystem showed increase in performance"]
["AHFG-19186","Aircraft Maintenance Program","Even after the AME closure tasks are still in completed status and due to which finance closure postings has not been happened","Even after the AME closure tasks are still in completed status and due to which finance closure postings has not been happened","Primary Defect","When a Single package is opened in different screens in different browsers, Actions at individual screens where not validating the package status in other browser. Due to this Package closed from one browser screen could be modfied in another browser","No - No",null,"Validation has been added to check the package status.","Data: \n1. Launch a Package for the aircraft 101 which was in \"Completed\" status in AME in Chrome \n2. Launch the package in Explorer and launch Sign Off Sub Tasks screen \n3. Select the Value \"yes\" from the drop down for \"Change status of task to Completed \" \n4. Close the package from Chrome \n5. Now from Explorer click Sign Off \n6. An error message is shown \n\nEnvironment: FS ST"]
["AHFG-19135","Aircraft Maintenance Program","UNable to approve amp","confrim amp","Primary Defect","If the task is in Initiate schedule relation ship and NSV/NSD has been computed based on Parent task LPV/LPD , when we change the NSD/NSV manually for child task through IMPUC then system automatically updated the parent task's LPV as LPV for the task.","No - No",null,"Auto LPV/LPD updation logic for tasks in Post compliance relationship in the program on modification of the schedules in the program has been corrected to get the correct LPV/LPD value","Tested and Verified in FS ST server \n1. Created a two task with Parent - Child initiate relationship \n2. Complied the parent task and system calculated the childs NSV \n3. On modifying the child NSV the LPV for the child remains blank if there is no previous LPV value already present and the system has retained the same LPV value of the child if there is a LPV value which is already exist for the child."]
["AHFG-18717","Aircraft Maintenance Planning","AFTER PRESSING RADIO BUTTON FOR UTILIZATION REPORT-AIRCRAFT SUMMARY NO REPORT IS COMING SUMMERY","SAME AS ABOVE","Primary Defect","System did not generate the report because of a performance issue","No - No",null,"Logic at back end was fixed so as to generate the report","Tested and verified in FS server \nConfiguration Mgmt. > Additional Reports Configuration Mgmt > Generate Utilization report \n\n1. Generated utilization report for an aircraft model# \nSystem generated the report successfully."]
["AHBG-36084","Aircraft Maintenance Planning","E5D to FS merger impacted objects","E5D to FS merger","Primary Defect","Merger Impacted Objects","No - No",null,"Merger Impacted Objects","Merger Impacted Objects"]
["AHFG-18749","Aircraft Maintenance Planning","In task part requirement screen when a part is added and click \"Edit Part\" getting the message \" The record \"TSI-717-12-0004\" has been modified by another user. Please refresh the page and submit\"","1.select ED task with rev# from planning board and go the plan material screen. \n2.selected edit part \nerror message.","Primary Defect","Timestamp validation was incorrect at backend. Due to this error message was shown.","No - No",null,"Timestamp validation has been corrected.","Tested and verified in FS server \n1. Aircraft maintenance planning > Plan Material > Edit Part Requirement for task \n2. Went to Planning board \n3. In task part requirement screen and clicked on \"Edit Parts\" \nsystem did not show any error message"]
["AHFG-18588","Aircraft Maintenance Planning","Why a wild card search for 717 BR715's bring a result of 146 P/plants ?","serach for component removal task and expected to see only 717 aircrafts, but system is showing other aircrafts as well. \nCheck snapshot.","Primary Defect","Search filter failed when searching for specific maintenance item types.","No - No",null,"Logic has been fixed so as to fetch the correct details when given specific searches.","Tested and verified in FS server \n1. Maintenance Planning > Aircraft Maintenance Planning > Plan Aircraft Maintenance \n2. Searched for specific aircraft and Maintenance Item type \n3. Checked for any extra data that was fetched. system retrieved only those data which were given in the search."]
["AHFG-18971","Aircraft Maintenance Planning","performance issue on oct 4 2019","system is taking more time when fetching from the planning board","Primary Defect","System is taking more time when fetching from the planning board and it was fixed.","No - No",null,"Objects were tuned and verified for increasing performance","Tested and verified in FS server \n1. Launched Planning board and searched for an aircraft reg# and gave an all search for tasks \nSystem fetched the records faster than before."]
["AHFG-18779","Aircraft Maintenance Planning","Daily Planning Report:Specific tasks are not showing its remaining time.","Snapshot","New Data Condition","There was no logic to show the remaining values for Position Tracked on-wing tasks in Daily Planning Report","No - No",null,"New logic has been implemented to show the remaining values for Position Tracked on-wing tasks in Daily Planning Report.","Tested and verified in FS server \n1. Generated Daily Planning report under the given filter conditions. \nSystem displayed the records and the tasks showed the Remaining values. \nPlanning Element: Sub fleet \nPlanning element info: 111 \ntask# VP-001173-2017/1 \nPackage# VP-001494-2018"]
["AHFG-19581","Aircraft Maintenance Execution","Could not assign workcenter to newly created fresh package","Could not assign workcenter to newly created fresh package","Secondary Defect","Force Reviewed for Shipment","Yes - Only Fix Provided",null,"Force Reviewed for Shipment","Force Reviewed for Shipment"]
["AHFG-19203","Aircraft Maintenance Execution","Performance issue in Component replacement confirmation","Performance issue in Component replacement confirmation","Secondary Defect","Performance tuning not handled not handled in Confirm CR","Yes - Only Fix Provided",null,"Performance fix provided to improve the processing time in submission clicks","Data: \n1. Launch AME for aircraft 1133 \n2. Perform a component replacement for the part 0-0440-4-0011:36361 \n3. No performance errors occur \n\nEnvironment: FS ST"]
["AHFG-18820","Aircraft Maintenance Execution","When creating package or for any transaction for the package type ETRN the system is throwing Error","When creating package or for any transaction for the package type ETRN the system is throwing Error. \nGeneral Exception during OUT Data Binding of PS - 1 BR - 1Conversion failed when converting the varchar value '\"\"1\"\" for \"\"Yes\"\"\"' to data type int.","Secondary Defect","System did not validated if user entered incorrect Permitted values in define process entity","Yes - Only Fix Provided",null,"System should validated if user entered the incorrect permitted value in define process entity screen","Data: \n1. Launch the define process entity screen \n2. select the Entity type as \"Package type\" and Choose package type as \"Transit\" \n3. Save the define process entity screen. \n4. System properly validated if existing any value is incorrect \n\nEnvironment: FS ST"]
["AHFG-19189","Aircraft Maintenance Execution","UNABLE TO CLAIM TASK IN AME TECHLOG","IN SYSTEM PT 1 TASK & PT 2 TASK ARE DEFINED THROUGH EO & TASK RELATIONSHIP IS DEFINED. \nOn completion of Part1 task it should initiate the schedule for Part2 task. (Task relationship defined in \"initiate schedule\") \n\nBUT WHEN TRYING TO CLAIM PART1 TASK ERROR MESSAGE APPEARING.","Primary Defect","During compliance of Parent task, system failed to retain value of NSV for child task, the tasks are in Initiate schedule relationship","No - No",null,"Logic has been corrected to retain the old NSV/NSD and verified.","Tested and verified in FS server \n\n1. Aircraft/Shop Work Management > Work reporting Hub > Aircraft Work reporting hub \n2. In a package, added a parent task which has an Initiate schedule relationship with child task \n3. Saved the package \n4. Clicked the task record and clicked on Complete \n\nsystem completed the task."]
["AHFG-19371","Aircraft Maintenance","Task NST-003088-2019 was added in VP-000554-2019 but it is missing in AME hub","1. Task NST-003088-2019 was added in VP-000554-2019 but it is missing in AME hub but it is showing in Parts Hub","Primary Defect","System incorrectly stamping the doc type as discrepancy while adding cancelled non standard task to package.","Yes - Only Fix Provided",null,"Fix has been provided to stamp the doc type as Task while adding cancelled task to package","Data: \n1. Create a non standard task in a Line Package for the aircraft 101 \n2. Cancel the task \n3. Launch the package VP-000465-2013 and add the cancelled task to the package \n4. The task is added and is visible in AME Hub \n\nEnvironment: FS ST"]
["AHFG-19243","Aircraft Maintenance","Unable to Close the task system gives an error as \"  Unable to process. Some of the discrepancies are in ‘Under Resolution’ or ‘Pending Deferral’ status or in ‘Deferred status for Log card packages’.\"","Unable to Close the task system gives an error as \" Unable to process. Some of the discrepancies are in ‘Under Resolution’ or ‘Pending Deferral’ status or in ‘Deferred status for Log card packages’.\"","Primary Defect","System incorrectly validating while closing the package from WMC which is due to discrepancy is in under resolution in another package(Deferred from old package) though it was closed from package","Yes - Only Fix Provided",null,"Fix has been provided to close the package though discrepancy is in under resolution in other package since it is already closed at source package","Data: \n1. Launch the package VP-010855-2018 in Manage Work Assignments and Reporting for the aircraft 101 \n2. Close the package \n3. The package is closed successfully \n\nEnvironment: FS ST"]
["AHFG-18978","Aircraft Maintenance","cmn_offlineapp_ame_dp_processing_sp Checkin FS ST for testing View Deferral History","cmn_offlineapp_ame_dp_processing_sp Checkin FS ST for testing View Deferral History - APPA-3196","Primary Defect","Deferral history table push is not happening from LineAnywhere. Insert to be handled during package transfer to Online.","No - No",null,"Deferral history table push is not happening from LineAnywhere. Insert handled during package transfer to Online.","FS ST \nPackage # :VP013544-2019 \nDiscrepancy # : CDP-045714 \n\n1.Create a package \n2. Create discrepancy \n3. Deferred it \n4. Checked in View Discrepancy Information -> View Discrepancy Deferral History of desktop \n5. Details are updated correctly"]
["AHFG-18660","Aircraft execution Hub","Aircraft VTANA - Created Package in Hub for TC Package Type. Selected the task and clicked complete button. Primary violation key error is popping up","Aircraft VTANA - Created Package in Hub for TC Package Type. Selected the task and clicked complete button. Primary violation key error is popping up","Primary Defect","Primary key error due to existing user actions not cleared from the Work reporting hub","Yes - Only Fix Provided",null,"Logic handled to clear the existing actions from the Work reporting hub","Data: \n1. Launch the work reporting hub screen \n2, Create the Package For Aircraft 101 and Work center # 185-20 then Click Create Package \n3. Change the Planned Started date and end date then Save \n4. Select the Task From Multiline and Click complete button \n5. Able to change the Task Status without any error \n\nEnvironment: FS ST"]
["AHBG-36088","Aircraft Execution Hub","Objects is overwritten for E5D Merger to FS","Objects is overwritten for E5D Merger to FS","Primary Defect","Objects is overwritten for E5D Merger to FS","No - No",null,"Objects is overwritten for E5D Merger to FS","Verified in FS ST Simulation server"]
["AHFG-19298","Aircraft Execution Hub","UNable to cancel three packages ( ALINE-000828-2018, ALINE-000118-2018,ADEF-015879)","System throws log leaf validation error. \n\n1. Select the package and click cancel","Primary Defect","System allowed to modify logitem # from maintain discrepancy info screen(Discrepancy dtl table log item # modified (new), but in snag still old log item # available), because back end set option table not having entry.","Yes - Data Update & Fix Provided",null,"System allowed to modify log item # from maintain discrepancy info screen,and log item # is in sync in back end tables.","Data: \n1. Create a new line package with a discrepancy \n2. Change the log item number for the discrepancy \n3. Cancel the discrepancy \n4. Cancel the package \n\nEnvironment: FS ST"]
["AHFG-19612","Aircraft","During check out a new entry is being created with a new record id instead of updating the existing entry.","During check out a new entry is being created with a new record id instead of updating the existing entry.","Secondary Defect","Logic has to be changed","No - No",null,"Top 1 logic has been changed \nNew entry has not been created.","During check out a new entry has not been created. \nRecord time sheet for multiple employees and check the apportioning logic. \nNon destructive cycle has been carried out by booking the time sheet against the employees."]
["AHBG-35067","Aircraft","Part type and Part planning group are not loading in drop down","While entering the information for Part type and Part planning group","Primary Defect","This issue now working. It is addressed as part of the case AHBG-35162. Reason : FE - Deployment Issue","No - No",null,"This issue now working. It is addressed as part of the case AHBG-35162. \nReason : FE - Deployment Issue","Tested"]
["AHFG-19502","Aircraft","System allows to confirm the Maintenance Issue even though the restriction is applied on Part #Serial # from Manage Part Restriction screen","1. Define Process Parameter for Stock Restriction Code \n2. Update the restriction for Part # and Serial # in Manage Part Restriction Screen. \n3. Create a MR from Log Card using work reporting hub. \n4. Confirm the Issue for the same Serial # as selected in step 2","Primary Defect","During conform issue system fails to validate due to insurrecting matching for the transaction type (instead of issue type reference document type is matched)","No - No",null,"The parameter has been corrected to pass the issue type for the routine which has the restriction logic","Data: \n1. Launch Manage Part Restriction and restrict the part 0-0440-4-0011:36361 \n2. Create a material request for the part from a package and confirm the issue \n3. An error message is successfully shown \n\nEnvironment: FS ST"]
["AHFG-19608","Aircraft","Data Truncation",null,"New Data Condition","The input parameter of the Store Procedure was the issue, as it was accepting only 5 characters.","No - No",null,"The input parameter of the SP was changed to accept 40 characters","Tested and Verrified in FS-UT"]
["AHFG-18798","Accounts Payable Hub","Performance issue in Review process scanned invoices / notes","Performance issue in Review process scanned invoices / notes \n\nCurrently it takes 32 Seconds just to launch the screen in production","Secondary Defect","Non clustered and clustered index were are not provided for the tables","No - No",null,"Non clustered and clustered index has been provided for all the key columns of the tables","Tested and Verified in cobham dev server"]
["AHFG-19242","DW Reports","Timesheet Report fetches only Authorized hours, it should fetch all hours including confirmed and fresh","Timesheet Report fetches only Authorized hours, it should fetch all hours including confirmed and fresh.","Secondary Defect","Provision is required to display all time records in timesheet report irrespective of the status of the record","No - No",null,"Changes have been done in the report in order to show all time records irrespective of the status of the time record.\nStatus of the time record is concatenated and shown in the field 'Time type'.","Scenario: \n1) Launched timesheet report for the period of October 2019. \n2) All time records booked in the respective period has been fetched in that report. \n3) Status of the time record has been displayed in Time type field."]

{"sheet":"Product Enhancements","index":2,"n_rows":21,"n_cols":9,"rows_kept":21,"cut":false,"hidden":false,"merged":[]}
[]
["Key","Component/s","Summary","Test and Verification Details","Enhancement Notification Document#","Behavior Change","Enhancement notification \nrequired","Remarks","Applicable for 2.0"]
["AHBG-35403","Stock Management Reports","SLX Report does not have a projected date visible","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","EN is not applicable. Behavioral Changes Updated","Filters used in entry screen has been added in report header in first page. \nValues of input filters used in Shelf Life Report entry screen will display in report output.","NA",null,"NA"]
["AHBG-31082","Part Administration","Ability to manage Recommended Spare Parts List at Model/Part Level","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Manage Recommended Spare Parts List-AHBG-31082.pdf",null,"Yes","Based on  the  Recommended  Spare  Parts  List  (RSPL) provided  by  OEM,  the  inventory  float  (indicating the  quantity  of  parts  to  be  maintained  to  support  an  aircraft),  gets  computed.  Business  need  is  to  define  and  maintain the Recommended Spare Parts List for a given Aircraft Model. Also this enhancement provides the ability to define  and  maintain  the  Aircraft  Models  for  which  a  Part  serves  as  the  spare,  along  with  additional  RSPL  Information.  The RSPL  information  can  vary  over  time,  hence a  provision  to  track  the  changes  is also enabled by providing Revision #s at A/C Model # level. This will be used in Float Management, which is planned beyond EAR 5.8.9","NO"]
["APSE-257","Component Maintenance Planning","Ability to define and manage the 'Part Technical Data Requirements' master data and its version for tracking during receipt","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to define and manage the Part Technical data requirements-APSE-257.pdf",null,"Yes","A new screen was developed to capture part technical data requirements for a part that needs to be verified while receiving a part into the system. The downstream impact of this feature will be a part of 5.8.9","No"]
["APSE-246; APSE-247 ","Reliability Analysis","Ability to define Fleet for aircraft's / aircraft group and map same aircraft to multiple fleets","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to setup Reliability Fleet with Aircraft mapping and report selection-APSE-246 APSE-427.pdf",null,"Yes","An Advanced Fleet setup has been enabled to run Component reliability analysis. The reliability run & reports based on this fleet setup will be part of EAR 5.8.9 release.","No"]
["APSE-12","Supplier","Ability to manage Supplier Repair Contracts","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to manage Supplier Repair Contracts-APSE-12.pdf",null,"Yes","Manage  Supplier  Service  Contract  is  added  in  the  Supplier  business  component.  This  activity  provides  an  extensive  framework  record/capture  all  the  key  entities  applicable  for  a  Supplier  Contract  agreed  for  repair of the parts. The Supplier Repair Contract will be used to identify the default Repair Cost of the Parts that are sent  for  repair  to  the  vendor.  The  screen  provides  different  tabs  to  capture basic  contract  details,  fixed/monthly  pricing details, covered workscope, exclusions, TAT details, Billing details, etc.","NO"]
["APSE-11","Pool Management","Ability to define and manage a Pool","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to define and manage Pool-APSE-11.pdf",null,"Yes","Typically, Pool definition comprises of the Parts supported from the Pool (Mostly Model specific Spare Parts), Customers who benefit from the Pool (Beneficiaries) and Stocking Locations (Warehouses), in addition to the other information,  like  the  Payment  Terms.  Pooling is  attractive  for  new  aircraft,  when  fleet  size  is  small,  reliability  is unknown, OEM parts are expensive and used parts are unavailable. This enhancement provides the ability to define and maintain a Pool with all the key information. The Downstream impact of Pool Management will be released in the EAR 5.8.9","NO"]
["APSE-48","Maintenance Change Request","Ability to capture the key attributes of the Eng. Doc (Mandatory and Reliability Impact) in the MCR and identify the EO initiated by customer","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to capture key attributes of Eng Doc in MCR and identify EO-APSE-48.pdf",null,"Yes","Fields added to MCR to capture if an SB/AD/SIL is mandatory and if it has any reliability impact. The EO can contractually be an inclusion/exclusion depending on the above new attributes and this contract defn. & the subsequent evaluation will be handled in EAR 5.8.9 release.","Yes"]
["AHBG-32209","Asset Planning","Definition of Asset Proposal with Analysis Code","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Definition of Asset Proposal with Analysis Code-AHBG-32209.pdf",null,"Yes","Analysis Code is introduced in Asset Acquisition Proposal and the same is mandatory if CIM Interaction between Asset Planning and Account Based Budget Components. Introduction of Analysis Code in Asset Record is planned in the subsequent releases EAR 5.8.9.\n","Yes"]
["AHBG-31819","Asset Planning","Ability to enable Asset Proposal Rule Definition","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to enable Asset Proposal Rule Definition-AHBG-31819.pdf",null,"Yes","Proposal Rule Definition is introduced to automate defaulting of Proposal in Purchase Order based on PO and Part Parameters. \nHowever in this release only the Rule Definition Master is enabled. The PO related changes of defaulting the proposal are planned in subsequent release: EAR 5.8.9","Yes"]
["AHBG-31754","Customer","Provision to maintain the Station, Delivery Point, Freight Forwarder in the Address details of the customer","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Maintain Station Delivery Point Freight Forwarder in address details of customer-AHBG-31754.pdf",null,"Yes","Additional Fields have been provided to maintain the applicable station, Delivery point(final Destination) and Freight Forwarder details against the customer address. This details are currently maintained in the customer master only. The defaulting of the same in transactions like Customer Request, Customer Order, Part Sale Order based on the Address ID selected are planned in the subsequent release : EAR 5.8.9","Yes"]
["AHBG-32465","Logistics Common Master","Ability to define Delivery Point and have Delivery Point-Station mapping established","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to define Delivery Point and establish Delivery Point-Station mapping-AHBG-32465.pdf",null,"Yes","Delivery  Point  indicates the final  point  of  destination  in  the  requesting  station  where  the  part  #  requested  by  the  customer will be delivered. Business need is to maintain the Delivery Points   available in different stations in Ramco Aviation application and establish Delivery Point-Station mapping. The usage of this Delivery point will be to identify the end shipment delivery point, which will be available in EAR 5.8.9","Yes"]
["AHBG-31699","Procurement management","Ability to map buyer group to Supplier/Customers","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to map Buyer Group to Suppliers and Customers-AHBG-31699.pdf",null,"Yes","Business  need  is  to  map  Buyer  Group  to  specific suppliers/customers  which is the main attributes  of  a  transaction  document,  thus  establishing  control  over  processing  of  the  documents.  Currently  this  screen facilitates Buyer Group mapping only in Repair Orders. This will be used in Repair Order Hub, which is planned in beyond EAR 5.8.9","Yes"]
["APSE-64","Maintenance Change Request","Ability to capture the part effectivity with PN range, MOD range, Manf. Date range, Repair date range in MCR","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to capture Advanced Part Effectivity in MCR-APSE-64.pdf",null,"Yes","A new featuer called advanced part effectivity is introduced where many new criteria can be specified to fetch a part. The down stream impact of this will be available in 5.8.9","Yes"]
["APSE-340","Component Maintenance Program","Ability to manage the component program based on Schedule adjustments","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to manage Schedules of Part and Components for multiple combinations-APSE-59.pdf",null,"Yes","A new screen has been introduced to manage program schedules at an Operator level. The schedule adjustments  to Aircraft / Component programs based on operator level definitions will be enabled as part of EAR 5.8.9.","Yes"]
["APSE-274","Part Administration","Ability to define the new Part Group for the Inventory Planning Purpose and identify the same in Planning Info and Alternate Info","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to define Part Planning Group and additional part Information-APSE-274.pdf",null,"Yes","The ability to define a   new Part Group for the Inventory Planning Purpose and identify the same in Planning Information and Alternate Information with some additional information. Also, a new screen is provided to define and view the additional information for a Part #. This will be used in Float Management, which is planned beyond EAR 5.8.9","Yes"]
["APSE-40","Sale Contract","Ability to set Service Type against a service sale contract","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","EN is not applicable. Behavioral Changes Updated","A new column 'Service Type' has been added in the contract main info. of the sale contract to specify the type of the service that is agreed as per that respective contract. \nThis control displays the values \"Blank\", \"Repair\" and \"Exchange\" \nIf this field is left as blank then the contract definition is irrespective of service or exchange. i.,e the Sale contract is applicable for both the repair and exchange services against the parts covered. \nIf this field in the contract is set as \"Repair\" , it means that only repair services are allowed against this contract and this contract will be evaluated only against the Customer Orders for repair. \nIf this field in the contract is set as \"Exchange\" , it means that only Part exchanges are allowed against this contract and this contract will be evaluated only against the Customer Orders for exchange. \n","No","A new entity  called 'Service Type' has been introduced in the Sale Contract to define whether the Contract covers only 'Repair' Services or only 'Exchange' services.\nBased on this, the downstream impact - i.e.., Identification of applicable contract based on the Request for (Repair/Exchange) in Customer Request to auto setup 'Customer Order' or the evaluation of the contract for repair and Exchange CO are planned in subsequent release: EAR 5.8.9","Yes"]
["APSE-39","Customer","Ability to manage the list of parts for sales covered under the monthly fixed price model as part of customer master","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to manage list of parts for sales covered under monthly fixed Price model-APSE-39.pdf",null,"Yes","Part Sale List at customer level enables the definition of the list of parts agreed for 'Sale'. Provision is also given to set the pricing basis based on which the part covered under the part sale list will be charged to the customer.\nHowever the downstream impact of evaluation of the Parts requested in the RFQ/Part Sale Order based on the part sale list and billing as per T&M basis or FPM will be planned in the subsequent release: EAR 5.8.9 ","Yes"]
["APSE-26","Customer","Trn-Bsg-R59-COM1-SP27-QPA-Ability to define the QPA for Customer's Fleet at Customer Master","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","Trn-Bsg-Enh Note-Ability to define QPA for Customer Fleet at Customer Master-APSE-26.pdf",null,"Yes","Maintain Customer RSPL screen is introduced to maintain the QPA(Quantity per Aircraft) for the customer fleet at Aircraft Model level or Aircraft Reg# level.\nThe RSPL(recommended spare part list) maintained in the Aircraft configuration for each A/C model can be modified for QPA & other details and maintained at each customer level.\nThe computation of float and material replenishment based on the agreed QPA at customer level will be downstream impact planned in the subsequent release EAR 5.8.9","Yes"]
["AHFG-19166","Reports - Fixed Assets Management","The report to fetch In Expiry Date and Useful Life in Asset Detail report","Test Scenario and Test Cases are available in the Enterprise Tester - Will be provided on Request basis","EN is not applicable. Behavioral Changes Updated","Report level changes made in the Fixed Asset Detail report with two additional columns as listed below:\n1. Expiry date of the Asset # / Tag #.\n2. Useful life of the Asset # / Tag #.\n\nBehavior change is the report retrieving two additional columns as listed above, and during the Fixed Asset Detail report generation - system will retrieve additional two columns in addition to the existing data at each Asset # / Tag # level","NA","Expiry date and useful life are added as new columns in the report.","Yes"]

{"sheet":"Impacted Objects","index":3,"n_rows":1181,"n_cols":4,"rows_kept":1181,"cut":false,"hidden":false,"merged":[[0,0,0,3]]}
[]
["Key","Component Name / BPC Name","Object Type","Object Name"]
["AHBG-28805","Engineering Change Management/BasMD","BRO","BASMD.dll"]
["AHBG-28805","Engineering Change Management/BasMD","BRO","BASMD.Resources.dll"]
["AHBG-28805","Engineering Change Management/BasMD","BRO","BASMD.zip"]
["AHBG-28805","Engineering Change Management/BasMD","DepMetaData","BASMD_DepMetaData.sql"]
["AHBG-28805","Engineering Change Management/BasMD","DepMetaData","BASMD_depmetadata_Language.sql"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO","mdaddmdoc.dll"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO","mdmodmdoc.dll"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO","mdrevmdoc.dll"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO","mdvwmdoc.dll"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdaddmdoc_mdaddmdocmain.htm"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","MDAddMDoc_MDAddMDocMain.xml"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdaddmdoc_mdaddmdocmain_user.js"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocacadl.htm"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","MDModMDoc_MDModMDocAcAdl.xml"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocacadl_user.js"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdoccompadl.htm"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","MDModMDoc_MDModMDocCompAdl.xml"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdoccompadl_user.js"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocmain.htm"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","MDModMDoc_MDModMDocMain.xml"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocmain_user.js"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocprtefadl.htm"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","MDModMDoc_MDModMDocPrtEfAdl.xml"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocprtefadl_user.js"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdrevmdoc_mdrevmdocmain.htm"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","MdRevMDoc_MdRevMDocMain.xml"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdrevmdoc_mdrevmdocmain_user.js"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocacinq.htm"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","MdVwMDoc_MdVwMDocAcInq.xml"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocacinq_user.js"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdoccompinq.htm"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","MdVwMDoc_MdVwMDocCompInq.xml"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdoccompinq_user.js"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocinq.htm"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","MdVwMDoc_MdVwMDocInq.xml"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocinq_user.js"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocprtefinq.htm"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","MdVwMDoc_MDVwMDocPrtEfInq.xml"]
["AHBG-28805","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocprtefinq_user.js"]
["AHBG-28805","Engineering Change Management/BasMD","Metadata","05-R59-MX2-BasMD-Alter-MetaData-AHBG-28805.SQL"]
["AHBG-28805","Engineering Change Management/BasMD","StateXML","MDAddMDoc_MDAddMDocMain.xml"]
["AHBG-28805","Engineering Change Management/BasMD","StateXML","MDModMDoc_MDModMDocAcAdl.xml"]
["AHBG-28805","Engineering Change Management/BasMD","StateXML","MDModMDoc_MDModMDocCompAdl.xml"]
["AHBG-28805","Engineering Change Management/BasMD","StateXML","MDModMDoc_MDModMDocMain.xml"]
["AHBG-28805","Engineering Change Management/BasMD","StateXML","MDModMDoc_MDModMDocPrtEfAdl.xml"]
["AHBG-28805","Engineering Change Management/BasMD","StateXML","MdRevMDoc_MdRevMDocMain.xml"]
["AHBG-28805","Engineering Change Management/BasMD","StateXML","MdVwMDoc_MdVwMDocAcInq.xml"]
["AHBG-28805","Engineering Change Management/BasMD","StateXML","MdVwMDoc_MdVwMDocCompInq.xml"]
["AHBG-28805","Engineering Change Management/BasMD","StateXML","MdVwMDoc_MdVwMDocInq.xml"]
["AHBG-28805","Engineering Change Management/BasMD","StateXML","MdVwMDoc_MDVwMDocPrtEfInq.xml"]
["AHBG-28805","Engineering Change Management/BasMD","Stored Procedure","RvMcr18T.sql"]
["AHBG-28805","Engineering Change Management/BasMD","Table","04-R59-01-BasMD-Table-0001.sql"]
["AHBG-28805","Maintenance SetUp/BASCm","Metadata","11-R59-MX2-Altermetadata-BASCm-AHBG-28805.SQL"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","AdMcr17T.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","AdMcr19T.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","AdMcr20T.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","AdMcr22T.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","AdMcr23C.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","AdMcr24C.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","Md_AddMcr_EffDtBasis_ini_sp.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","Md_AddMcr_EffDTUI_sp.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","Md_AddMcr_RefDtBasis_ini_sp.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","Md_ModDoc_EffDTUI_sp.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","Md_RevMcr_EffDTUI_sp.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","Md_VwDoc_CmpEff_Fth2_sp.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","Md_VwDoc_PrtEfFth2_sp.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod26F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod27F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod29S.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod30S.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod32F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod41F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod42F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod44T.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod47F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod48F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod50T.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod61F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod62F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdMod64T.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdVw01F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdVw02F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","MdVw13F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","RvMcr05F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","RvMcr06F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","RvMcr10T.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","RvMcr19T.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","RvMcr23S.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","VwMcr20F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","VwMcr21F.sql"]
["AHBG-30900","Engineering Change Management/BasMD","Stored Procedure","VwMcr50F.sql"]
["AHBG-31082","Configuration Management/BasAircraft","BRO","BASAIRCRAFT.dll"]
["AHBG-31082","Configuration Management/BasAircraft","BRO","BASAIRCRAFT.Resources.dll"]
["AHBG-31082","Configuration Management/BasAircraft","BRO","BasAircraft.Zip"]
["AHBG-31082","Configuration Management/BasAircraft","BRO","basaircraft_bulk.dll"]
["AHBG-31082","Configuration Management/BasAircraft","DepMetaData","BASAircraft_DepMetaData.sql"]
["AHBG-31082","Configuration Management/BasAircraft","DepMetaData","BASAircraft_depmetadata_Language.sql"]
["AHBG-31082","Configuration Management/BasAircraft","EXTJS-JSON","managerspl_managerspl.json"]
["AHBG-31082","Configuration Management/BasAircraft","ILBO","acmodmodel.dll"]
["AHBG-31082","Configuration Management/BasAircraft","ILBO","managerspl.dll"]
["AHBG-31082","Configuration Management/BasAircraft","ILBO-EXTJS","Acmodmodel_acmodmodelent.htm"]
["AHBG-31082","Configuration Management/BasAircraft","ILBO-EXTJS","Acmodmodel_acmodmodelent_user.js"]
["AHBG-31082","Configuration Management/BasAircraft","ILBO-EXTJS","Managerspl_managerspl.htm"]
["AHBG-31082","Configuration Management/BasAircraft","ILBO-EXTJS","Managerspl_managerspl_user.js"]
["AHBG-31082","Configuration Management/BasAircraft","Metadata","03-AHBG-31082-MAT1-BasAircraft_RSPL_AltertMetadata-01.sql"]
["AHBG-31082","Configuration Management/BasAircraft","StateXML","ManageRSPL_ManageRSPL.xml"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_BFE_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Essentcode_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_HdrSave_sp.sql"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_MltSave_Met_Sp.sql"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_MSPTUOM_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_OnEnter_Part_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_PgLnch_sp.sql"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Prtclss_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Prtplangrp_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Prttype_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Pwrpltprt_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Revision_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Save_IS_Met.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Soudoc_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Status_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_UDD1_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_UDD2_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_UDD3_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_UDD4_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_UDD5_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Unit_Init_sp.SQL"]
["AHBG-31082","Configuration Management/BasAircraft","Table","01 MAT1_AHBG-31082_Basaircraft_RSPL_CreateTable.sql"]
["AHBG-31082","Configuration Management/BasAircraft","Table","01_MAT1_AHBG-31082_BasAircraft_RSPL_CreateTmptable.sql"]
["AHBG-31082","Configuration Management/BasAircraft","Table","02_AHBG_31082_BasAircraft_RSPL_CreateSynonym.sql"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO","prtaddmaininfo.dll"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO","prtaddqkinfo.dll"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO","prtmodmaininfo.dll"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO","prtvwallinfo.dll"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtaddmaininfo_prtaddmainmain.htm"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtaddmaininfo_prtaddmainmain_user.js"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtaddqkinfo_prtaddqkinfomain.htm"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtaddqkinfo_prtaddqkinfomain_user.js"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtmodmaininfo_prtmodmaininfomain.htm"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtmodmaininfo_prtmodmaininfomain_user.js"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtvwallinfo_prtvwallinfomain.htm"]
["AHBG-31082","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtvwallinfo_prtvwallinfomain_user.js"]
["AHBG-31082","Inventory Setup/BasPartAdmn","Metadata","03-AHBG-31082-MAT1-BasPartAdmn_RSPL_AltertMetadata-01.sql"]
["AHBG-31699","Procurement Management/BasBuyerGroup","BRO","BASBUYERGROUP.dll"]
["AHBG-31699","Procurement Management/BasBuyerGroup","BRO","BASBUYERGROUP.Resources.dll"]
["AHBG-31699","Procurement Management/BasBuyerGroup","BRO","Basbuyergroup.zip"]
["AHBG-31699","Procurement Management/BasBuyerGroup","DepMetaData","BasBuyerGroup_DepMetaData.sql"]
["AHBG-31699","Procurement Management/BasBuyerGroup","DepMetaData","BasBuyerGroup_depmetadata_Language.sql"]
["AHBG-31699","Procurement Management/BasBuyerGroup","EXTJS-JSON","buyeraddbuyer_buyeraddbuyermain.json"]
["AHBG-31699","Procurement Management/BasBuyerGroup","EXTJS-JSON","buyermntbuyer_buyermntbuyermain.json"]
["AHBG-31699","Procurement Management/BasBuyerGroup","EXTJS-JSON","buyermntbuyer_trading.json"]
["AHBG-31699","Procurement Management/BasBuyerGroup","EXTJS-JSON","buyervwbuyer_buyervwbuyerinq.json"]
["AHBG-31699","Procurement Management/BasBuyerGroup","ILBO","buyeraddbuyer.dll"]
["AHBG-31699","Procurement Management/BasBuyerGroup","ILBO","buyermntbuyer.dll"]
["AHBG-31699","Procurement Management/BasBuyerGroup","ILBO","buyervwbuyer.dll"]
["AHBG-31699","Procurement Management/BasBuyerGroup","ILBO-EXTJS","Buyeraddbuyer_buyeraddbuyermain.htm"]
["AHBG-31699","Procurement Management/BasBuyerGroup","ILBO-EXTJS","Buyeraddbuyer_buyeraddbuyermain_user.js"]
["AHBG-31699","Procurement Management/BasBuyerGroup","ILBO-EXTJS","Buyermntbuyer_buyermntbuyermain.htm"]
["AHBG-31699","Procurement Management/BasBuyerGroup","ILBO-EXTJS","Buyermntbuyer_buyermntbuyermain_user.js"]
["AHBG-31699","Procurement Management/BasBuyerGroup","ILBO-EXTJS","Buyermntbuyer_trading.htm"]
["AHBG-31699","Procurement Management/BasBuyerGroup","ILBO-EXTJS","Buyermntbuyer_trading_user.js"]
["AHBG-31699","Procurement Management/BasBuyerGroup","ILBO-EXTJS","Buyervwbuyer_buyervwbuyerinq.htm"]
["AHBG-31699","Procurement Management/BasBuyerGroup","ILBO-EXTJS","Buyervwbuyer_buyervwbuyerinq_user.js"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Metadata","01-R59-MAT1-AHBG-31699-BasBuyerGroup-AlterMetadata.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","StateXML","BuyerMntBuyer_trading.xml"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Stored Procedure","ADDBG01F.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Stored Procedure","BGP_TRDPART_ORDCLS_INIT_SP.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Stored Procedure","BGP_TRDPRT_ DOCTY_INIT_SP.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Stored Procedure","BGP_TRDPRT_ DOCTYML_INIT_SP.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Stored Procedure","BGP_TRDPRT_HDRCHK_SP.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Stored Procedure","BGP_TRDPRT_HDRSAVE_SP.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Stored Procedure","BGP_TRDPRT_MLTSAVE_SP.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Stored Procedure","BGP_TRDPRT_PAGELAUN_HDR_SP.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Stored Procedure","BGP_TRDPRT_PAGELAUN_MLT_SP.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Stored Procedure","MNTBG02F.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Stored Procedure","VWBG08F.SQL"]
["AHBG-31699","Procurement Management/BasBuyerGroup","Table","01_MAT1_AHBG-31699_BasBuyerGroup_CreateTable.SQL"]
["AHBG-31754","Sales Management/BasCu","EXTJS-JSON","cusmodcus_cusmodcusent.json"]
["AHBG-31754","Sales Management/BasCu","ILBO","cusmodcus.dll"]
["AHBG-31754","Sales Management/BasCu","ILBO-EXTJS","Cusmodcus_cusmodcusent.htm"]
["AHBG-31754","Sales Management/BasCu","ILBO-EXTJS","Cusmodcus_cusmodcusent_user.js"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","CrCuMn09F.Sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","CrCuMn12S.Sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","CrCuMn13F.Sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","CrCuMn14F.Sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","Cu_CrCumn_Sp_IniHdr_Caragncy.sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","Cu_CrCumn_Sp_IniHdr_delpt.sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","Cu_CrCumn_Sp_IniML_Caragncy.sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","Cu_CrCumn_Sp_IniML_DelPt.sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","cu_mdcumn_sp_iniHdr_caragncy.sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","cu_mdcumn_sp_iniHdr_delpt.sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","cu_mdcumn_sp_iniMl_caragncy.sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","cu_mdcumn_sp_iniMl_delpt.sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","MdCuMn07F.Sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","MdCuMn08F.Sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","MdCuMn09S.SQL"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","MdCuMn10S.SQL"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","MdCuMn11S.SQL"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","MdCuMn12F.SQL"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","MdCuMn13F.SQL"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","VwCuMn01F.Sql"]
["AHBG-31754","Sales Management/BasCu","Stored Procedure","VwCuMn02F.Sql"]
["AHBG-31754","Sales Management/BasCu","Table","04-R59-01-BasCu-Table-0007-Tmp.sql"]
["AHBG-31754","Sales Management/BasCu","Table","04-R59-01-BasCu-Table-0007.sql"]
["AHBG-31819","Finance Setup/OPS","Stored Procedure","OPSmains5SpAuto_SSetOptspO.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","BRO","APLAN.dll"]
["AHBG-31819","Fixed Asset Management/APLAN","BRO","APLAN.Resources.dll"]
["AHBG-31819","Fixed Asset Management/APLAN","BRO","APLAN.zip"]
["AHBG-31819","Fixed Asset Management/APLAN","DepMetaData","APLAN_depmetadata.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","EXTJS-JSON","mainapruledefinition_maintainassetpropsllruledeftn.json"]
["AHBG-31819","Fixed Asset Management/APLAN","ILBO","mainapruledefinition.dll"]
["AHBG-31819","Fixed Asset Management/APLAN","ILBO-EXTJS","Mainapruledefinition_maintainassetpropsllruledeftn.htm"]
["AHBG-31819","Fixed Asset Management/APLAN","ILBO-EXTJS","Mainapruledefinition_maintainassetpropsllruledeftn_user.js"]
["AHBG-31819","Fixed Asset Management/APLAN","Index","07-R59-01-APLAN-Index-0001-Tmp.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Index","07-R59-01-APLAN-Index-0001.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Metadata","09-R59-01-APLAN-Metadata-0001.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpfetHdrFet.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpfetPropoa.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitCompan.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitCompon.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitDocume.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitDocumn.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitDocumt.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitDocumy.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitHidd15.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitHidd16.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitHidd17.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitHidd18.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitHiddee.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitHiddeR.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitPartCa.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitPartCl.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitPartGr.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitPartTy.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitPrimar.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitPropol.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitPurcha.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitRefere.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitSearcb.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpinitSearch.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpSave1HdrChk.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpSave1HdrRef.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpSave1HdrSav.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpSave1Propoa.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpSave1PropoaspO.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpSearc1PropoaspO.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpSearchHdrRef.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","APLmain28SpSearchSearcb.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Stored Procedure","cmn_aplan_proposal_get_sp.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Table","03-R59-01-APLAN-Table-0001-Tmp.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Table","03-R59-01-APLAN-Table-0001.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Table","04-R59-01-APLAN-Table-0003-Tmp.sql"]
["AHBG-31819","Fixed Asset Management/APLAN","Table","05-R59-01-APLAN-Synonymn-0001-Tmp.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","BRO","APLAN.dll"]
["AHBG-32209","Fixed Asset Management/APLAN","BRO","APLAN.Resources.dll"]
["AHBG-32209","Fixed Asset Management/APLAN","BRO","APLAN.zip"]
["AHBG-32209","Fixed Asset Management/APLAN","EXTJS-JSON","aplanaddapro_aplanaddacpromain.json"]
["AHBG-32209","Fixed Asset Management/APLAN","EXTJS-JSON","aplanaddapro_aplanaddaproent.json"]
["AHBG-32209","Fixed Asset Management/APLAN","EXTJS-JSON","aplanamapro_aplanamacpromain.json"]
["AHBG-32209","Fixed Asset Management/APLAN","EXTJS-JSON","aplanamapro_aplanamaproent.json"]
["AHBG-32209","Fixed Asset Management/APLAN","EXTJS-JSON","aplanauapro_aplanauacpromain.json"]
["AHBG-32209","Fixed Asset Management/APLAN","EXTJS-JSON","aplanauapro_aplanauaproent.json"]
["AHBG-32209","Fixed Asset Management/APLAN","EXTJS-JSON","aplanmodapro_aplanmodacpromain.json"]
["AHBG-32209","Fixed Asset Management/APLAN","EXTJS-JSON","aplanmodapro_aplanmodaproent.json"]
["AHBG-32209","Fixed Asset Management/APLAN","EXTJS-JSON","aplanvwapro_aplanvwacpromain.json"]
["AHBG-32209","Fixed Asset Management/APLAN","EXTJS-JSON","aplanvwapro_aplanvwaproent.json"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO","aplanaddapro.dll"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO","aplanamapro.dll"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO","aplanauapro.dll"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO","aplanmodapro.dll"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO","aplanvwapro.dll"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanaddapro_aplanaddacpromain.htm"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanaddapro_aplanaddacpromain_user.js"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanaddapro_aplanaddaproent.htm"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanaddapro_aplanaddaproent_user.js"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanamapro_aplanamacpromain.htm"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanamapro_aplanamacpromain_user.js"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanamapro_aplanamaproent.htm"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanamapro_aplanamaproent_user.js"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanauapro_aplanauacpromain.htm"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanauapro_aplanauacpromain_user.js"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanauapro_aplanauaproent.htm"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanauapro_aplanauaproent_user.js"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanmodapro_aplanmodacpromain.htm"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanmodapro_aplanmodacpromain_user.js"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanmodapro_aplanmodaproent.htm"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanmodapro_aplanmodaproent_user.js"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanvwapro_aplanvwacpromain.htm"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanvwapro_aplanvwacpromain_user.js"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanvwapro_aplanvwaproent.htm"]
["AHBG-32209","Fixed Asset Management/APLAN","ILBO-EXTJS","Aplanvwapro_aplanvwaproent_user.js"]
["AHBG-32209","Fixed Asset Management/APLAN","Metadata","09-R59-02-APLAN-Metadata-0040.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanacpmspcptminf_common.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanacpmsphdsav_common.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanacpmspminf_common.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspamdhdchk.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspamdhdsav.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspamdhref.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspamdminf.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspamdminfout.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspcpthdchk.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspcpthdsav.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspcpthref.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspcptminf.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspcptminfout.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspfethdfet.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanamacpmspfetminf.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanAmAcPMSpInitUD.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanauacpmspauhdchk.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanauacpmspauhdsav.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanauacpmspauhref.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanauacpmspauminf.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanauacpmspauminfout.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanauacpmspcptminf.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanauacpmspcptminfout.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanauacpmspfethdfet.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanauacpmspfetminf.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplancracpmspcpthdchk.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplancracpmspcpthdsav.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplancracpmspcpthref.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplancracpmspcptminf.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplancracpmspcptminfout.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplancracpmspcrauhdchk.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplancracpmspcrauhdsav.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplancracpmspcrauhref.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplancracpmspcrauminf.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplancracpmspcrauminfout.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplancracpmspfethdfet.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanCrBRMSpInitUD.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanedacpmspdelphdsav.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanedacpmspdelphref.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanedacpmspedauhdchk.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanedacpmspedauhdsav.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanedacpmspedauhref.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanedacpmspedauminf.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanedacpmspedauminfout.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","AplanVwAcPMSpFetHdFet.SQL"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","AplanVwAcPMSpFetMInf.SQL"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanvwacpmsphdrrefreshout.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanvwacpmspsavehdchk.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanvwacpmspsavehdsav.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanvwacpmspsaveminf.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Stored Procedure","aplanvwacpmspsaveminfout.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Table","04-R59-01-APLAN-Table-0002-Tmp.sql"]
["AHBG-32209","Fixed Asset Management/APLAN","Table","04-R59-01-APLAN-Table-0002.sql"]
["AHBG-32465","Procurement Management/BasLogCM","BRO","BASLOGCM.dll"]
["AHBG-32465","Procurement Management/BasLogCM","BRO","BASLOGCM.Resources.dll"]
["AHBG-32465","Procurement Management/BasLogCM","BRO","BasLogcm.zip"]
["AHBG-32465","Procurement Management/BasLogCM","EXTJS-JSON","mngquickcode_managequickcodes.json"]
["AHBG-32465","Procurement Management/BasLogCM","ILBO","mngquickcode.dll"]
["AHBG-32465","Procurement Management/BasLogCM","ILBO-EXTJS","Mngquickcode_managequickcodes.htm"]
["AHBG-32465","Procurement Management/BasLogCM","ILBO-EXTJS","Mngquickcode_managequickcodes_user.js"]
["AHBG-32465","Procurement Management/BasLogCM","Metadata","05-R58-MAT2-BasLogCM-Metadata-AHBG-32465.Sql"]
["AHBG-32465","Procurement Management/BasLogCM","StateXML","MngQuickCode_ManageQuickCodes.xml"]
["AHBG-32465","Procurement Management/BasLogCM","Stored Procedure","LCMLQckCdSpBtnSavMlQkCd.sql"]
["AHBG-32465","Procurement Management/BasLogCM","Stored Procedure","LCMLQckCdSpinitQkCdTy.SQL"]
["AHBG-32465","Procurement Management/BasLogCM","Stored Procedure","LCMLQckCdSpQkCdTy_StatespO.SQL"]
["AHBG-32465","Procurement Management/BasLogCM","Stored Procedure","LCMLQckCdSpQkCdTyMlQkCdspO.SQL"]
["AHBG-32465","Procurement Management/BasLogCM","Stored Procedure","LCMLQckCdSpQkCdTyQkCdMn.SQL"]
["AHBG-32465","Procurement Management/BasLogCM","Stored Procedure","LCMLQckCdSpQkCdTyRfDSTy.sql"]
["AHBG-32465","Procurement Management/BasLogCM","Stored Procedure","LCMLQckCdSpQkCdTyRfDTyp.SQL"]
["AHBG-32465","Procurement Management/BasLogCM","Table","03-R58-MAT2-BasLogCM-AlterTable-AHBG-32465.Sql"]
["AHBG-32886","Engineering Change Management/BasMD","BRO","BASMD.dll"]
["AHBG-32886","Engineering Change Management/BasMD","BRO","BASMD.Resources.dll"]
["AHBG-32886","Engineering Change Management/BasMD","BRO","BASMD.zip"]
["AHBG-32886","Engineering Change Management/BasMD","DepMetaData","BASMD_DepMetaData.sql"]
["AHBG-32886","Engineering Change Management/BasMD","DepMetaData","BASMD_depmetadata_Language.sql"]
["AHBG-32886","Engineering Change Management/BasMD","EXTJS-JSON","mdaddmdoc_mdaddmdocmain.json"]
["AHBG-32886","Engineering Change Management/BasMD","EXTJS-JSON","mdmodmdoc_mdmodmdocadvparteff.json"]
["AHBG-32886","Engineering Change Management/BasMD","EXTJS-JSON","mdmodmdoc_mdmodmdocent.json"]
["AHBG-32886","Engineering Change Management/BasMD","EXTJS-JSON","mdmodmdoc_mdmodmdocmain.json"]
["AHBG-32886","Engineering Change Management/BasMD","EXTJS-JSON","mdrevmdoc_mdrevmdocent.json"]
["AHBG-32886","Engineering Change Management/BasMD","EXTJS-JSON","mdrevmdoc_mdrevmdocmain.json"]
["AHBG-32886","Engineering Change Management/BasMD","EXTJS-JSON","mdvwmdoc_mdvwmdocent.json"]
["AHBG-32886","Engineering Change Management/BasMD","EXTJS-JSON","mdvwmdoc_mdvwmdocinq.json"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO","mdaddmdoc.dll"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO","mdmodmdoc.dll"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO","mdrevmdoc.dll"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO","mdvwmdoc.dll"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdaddmdoc_mdaddmdocmain.htm"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdaddmdoc_mdaddmdocmain_user.js"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocent.htm"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocent_user.js"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocmain.htm"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocmain_user.js"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdrevmdoc_mdrevmdocent.htm"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdrevmdoc_mdrevmdocent_user.js"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdrevmdoc_mdrevmdocmain.htm"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdrevmdoc_mdrevmdocmain_user.js"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocent.htm"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocent_user.js"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocinq.htm"]
["AHBG-32886","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocinq_user.js"]
["AHBG-32886","Engineering Change Management/BasMD","Metadata","05-R59-MX2-BasMD-Alter-MetaData-AHBG-32886.SQL"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","AdMcr13F.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","AdMcr19T.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","AdMcr22T.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","Md_AddMcr_IniMand_Sp.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","Md_AddMcr_IniRelia_Sp.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","Md_ModDoc_AddSrchIni_Sp.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","Md_ModDoc_AddSrchUI_Sp.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","MdMod06T.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","MdMod26F.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","MdMod29S.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","MdMod32F.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","RvMcr04T.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","RvMcr05F.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","RvMcr18T.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","RvMcr23S.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","VwMcr19T.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Stored Procedure","VwMcr20F.sql"]
["AHBG-32886","Engineering Change Management/BasMD","Table","04-R59-01-BasMD-Table-0005.sql"]
["AHBG-33513","Configuration Management/BasAircraft","BRO","BASAIRCRAFT.dll"]
["AHBG-33513","Configuration Management/BasAircraft","BRO","BASAIRCRAFT.Resources.dll"]
["AHBG-33513","Configuration Management/BasAircraft","BRO","BasAircraft.Zip"]
["AHBG-33513","Configuration Management/BasAircraft","EXTJS-JSON","acaddacinfo_acaddacmnmod.json"]
["AHBG-33513","Configuration Management/BasAircraft","EXTJS-JSON","acmodacinfo_acmodacmn.json"]
["AHBG-33513","Configuration Management/BasAircraft","EXTJS-JSON","acvwacinfo_acvwacvw.json"]
["AHBG-33513","Configuration Management/BasAircraft","ILBO","acaddacinfo.dll"]
["AHBG-33513","Configuration Management/BasAircraft","ILBO","acmodacinfo.dll"]
["AHBG-33513","Configuration Management/BasAircraft","ILBO","acvwacinfo.dll"]
["AHBG-33513","Configuration Management/BasAircraft","ILBO-EXTJS","Acaddacinfo_acaddacmnmod.htm"]
["AHBG-33513","Configuration Management/BasAircraft","ILBO-EXTJS","Acaddacinfo_acaddacmnmod_user.js"]
["AHBG-33513","Configuration Management/BasAircraft","ILBO-EXTJS","Acmodacinfo_acmodacmn.htm"]
["AHBG-33513","Configuration Management/BasAircraft","ILBO-EXTJS","Acmodacinfo_acmodacmn_user.js"]
["AHBG-33513","Configuration Management/BasAircraft","ILBO-EXTJS","Acvwacinfo_acvwacvw.htm"]
["AHBG-33513","Configuration Management/BasAircraft","ILBO-EXTJS","Acvwacinfo_acvwacvw_user.js"]
["AHBG-33513","Configuration Management/BasAircraft","Stored Procedure","AAcIn10F.sql"]
["AHBG-33513","Configuration Management/BasAircraft","Stored Procedure","AAcIn12S.sql"]
["AHBG-33513","Configuration Management/BasAircraft","Stored Procedure","AAcIn14S.sql"]
["AHBG-33513","Configuration Management/BasAircraft","Stored Procedure","ModAc16F.sql"]
["AHBG-33513","Configuration Management/BasAircraft","Stored Procedure","ModAc18S.sql"]
["AHBG-33513","Configuration Management/BasAircraft","Stored Procedure","VwInf06F.sql"]
["AHBG-33513","Configuration Management/BasAircraft","Table","04-R59-01-BasAircraft-Table-AHBG-33513.sql"]
["AHBG-33513","Configuration Management/BasAircraft","View","06-R58-MX2- BasAircraft-AlterView-AHBG-33513.Sql"]
["AHBG-33721","Engineering Change Management/BasMD","BRO","BASMD.dll"]
["AHBG-33721","Engineering Change Management/BasMD","BRO","BASMD.Resources.dll"]
["AHBG-33721","Engineering Change Management/BasMD","BRO","BASMD.zip"]
["AHBG-33721","Engineering Change Management/BasMD","DepMetaData","BASMD_DepMetaData.sql"]
["AHBG-33721","Engineering Change Management/BasMD","DepMetaData","BASMD_depmetadata_Language.sql"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO","mdaddmdoc.dll"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO","mdmodmdoc.dll"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO","mdrevmdoc.dll"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO","mdvwmdoc.dll"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO-EXTJS","Mdaddmdoc_mdaddmdocmain.htm"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO-EXTJS","Mdaddmdoc_mdaddmdocmain_user.js"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocadvparteff.htm"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocadvparteff_user.js"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocmain.htm"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO-EXTJS","Mdmodmdoc_mdmodmdocmain_user.js"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO-EXTJS","Mdrevmdoc_mdrevmdocmain.htm"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO-EXTJS","Mdrevmdoc_mdrevmdocmain_user.js"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocinq.htm"]
["AHBG-33721","Engineering Change Management/BasMD","ILBO-EXTJS","Mdvwmdoc_mdvwmdocinq_user.js"]
["AHBG-33721","Engineering Change Management/BasMD","Metadata","05-R59-MX2-BasMD-Alter-MetaData-AHBG-33721.SQL"]
["AHBG-33721","Engineering Change Management/BasMD","StateXML","MDAddMDoc_MDAddMDocMain.xml"]
["AHBG-33721","Engineering Change Management/BasMD","StateXML","MDModMDoc_MDModMDocAdvPartEff.xml"]
["AHBG-33721","Engineering Change Management/BasMD","StateXML","MDModMDoc_MDModMDocMain.xml"]
["AHBG-33721","Engineering Change Management/BasMD","StateXML","MdRevMDoc_MdRevMDocMain.xml"]
["AHBG-33721","Engineering Change Management/BasMD","StateXML","MdVwMDoc_MdVwMDocInq.xml"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","AdMcr13F.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","Md_AddMcr_EffDTUI_sp.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","Md_ModDoc_AdvPrtEfFth1_Sp.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","Md_ModDoc_AdvPrtEfFth2_Sp.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","Md_ModDoc_AdvPrtEfHChk_Sp.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","Md_ModDoc_AdvPrtEfHSav_Sp.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","Md_ModDoc_AdvPrtEfMSav_Sp.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","Md_ModDoc_EffDTUI_sp.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","Md_ModDoc_RestrCodIni_Sp.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","Md_ModDoc_RestrIni_Sp.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","Md_RevMcr_EffDTUI_sp.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","MdMod26F.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","RvMcr05F.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Stored Procedure","VwMcr20F.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Table","03-R59-01-BasMD-Table-0001-Tmp.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Table","03-R59-01-BasMD-Table-0001.sql"]
["AHBG-33721","Engineering Change Management/BasMD","Table","05-R59-01-BasMD-Synonymn-0001.sql"]
["AHBG-33721","Maintenance SetUp/BASCm","Metadata","05-R59-MX2-BasCM-ALTERMETADATA-AHBG-33721.sql"]
["AHBG-33874","Sales Management/BasCu","BRO","BasCu.zip"]
["AHBG-34076","Sales Management/BasCu","EXTJS-JSON","mancussprspl_mancussprspl.json"]
["AHBG-34076","Sales Management/BasCu","ILBO-EXTJS","Mancussprspl_mancussprspl.htm"]
["AHBG-34076","Sales Management/BasCu","ILBO-EXTJS","Mancussprspl_mancussprspl_user.js"]
["AHBG-34169","Engineering Change Management/BasMD","Table","04-R59-01-BasMD-Table-0001.sql"]
["AHBG-35067","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Prtplangrp_Init_sp.SQL"]
["AHBG-35067","Configuration Management/BasAircraft","Stored Procedure","AC_RSPL_Prttype_Init_sp.SQL"]
["AHBG-35077","Sales Management/BasCu","BRO","BasCu.dll"]
["AHBG-35077","Sales Management/BasCu","BRO","BasCu.Resources.dll"]
["AHBG-35077","Sales Management/BasCu","BRO","BasCu.zip"]
["AHBG-35077","Sales Management/BasCu","ILBO","mancussprspl.dll"]
["AHBG-35077","Sales Management/BasCu","Stored Procedure","CUSmain45SpConfirHdrChk.sql"]
["AHBG-35077","Sales Management/BasCu","Stored Procedure","CUSmain45SpConfirSpareP.sql"]
["AHBG-35077","Sales Management/BasCu","Stored Procedure","CUSmain45SpfetSpareP.sql"]
["AHBG-35077","Sales Management/BasCu","Stored Procedure","CUSmain45SpSave1HdrChk.sql"]
["AHBG-35077","Sales Management/BasCu","Stored Procedure","CUSmain45SpSave1SpareP.sql"]
["AHBG-35077","Sales Management/BasCu","Table","04-R59-01-BasCu-Table-0009-Tmp.sql"]
["AHBG-35077","Sales Management/BasCu","Table","04-R59-01-BasCu-Table-0009.sql"]
["AHBG-35079","Sales Management/BasCu","Stored Procedure","CUSmain45SpinitRSPLRe.sql"]
["AHBG-35080","Sales Management/BasCu","Stored Procedure","CUSmain45SpinitRSPLRe.sql"]
["AHBG-35082","Sales Management/BasCu","Stored Procedure","CUSmain45SpSave1HdrSav.sql"]
["AHBG-35083","Sales Management/BasCu","BRO","BasCu.dll"]
["AHBG-35083","Sales Management/BasCu","BRO","BasCu.Resources.dll"]
["AHBG-35083","Sales Management/BasCu","BRO","BasCu.zip"]
["AHBG-35083","Sales Management/BasCu","EXTJS-JSON","Mancussprspl_mancussprspl_user.js"]
["AHBG-35083","Sales Management/BasCu","ILBO","mancussprspl.dll"]
["AHBG-35083","Sales Management/BasCu","ILBO-EXTJS","Mancussprspl_mancussprspl.htm"]
["AHBG-35083","Sales Management/BasCu","ILBO-EXTJS","mancussprspl_mancussprspl.json"]
["AHBG-35084","Sales Management/BasCu","BRO","BasCu.dll"]
["AHBG-35084","Sales Management/BasCu","BRO","BasCu.Resources.dll"]
["AHBG-35084","Sales Management/BasCu","BRO","BasCu.zip"]
["AHBG-35084","Sales Management/BasCu","EXTJS-JSON","mancussprspl_mancussprspl.json"]
["AHBG-35084","Sales Management/BasCu","ILBO","mancussprspl.dll"]
["AHBG-35084","Sales Management/BasCu","ILBO-EXTJS","Mancussprspl_mancussprspl.htm"]
["AHBG-35084","Sales Management/BasCu","ILBO-EXTJS","Mancussprspl_mancussprspl_user.js"]
["AHBG-35084","Sales Management/BasCu","Stored Procedure","CUS_rsplsp_mlt_validation.sql"]
["AHBG-35091","Sales Management/BasCu","Stored Procedure","CUS_rsplsp_mlt_validation.sql"]
["AHBG-35092","Sales Management/BasCu","Stored Procedure","CUSmain45SpfetSpareP.sql"]
["AHBG-35092","Sales Management/BasCu","Stored Procedure","CUSmain45SpSave1HdrChk.sql"]
["AHBG-35092","Sales Management/BasCu","Stored Procedure","CUSmain45SpSave1SpareP.sql"]
["AHBG-35092","Sales Management/BasCu","Stored Procedure","CUSmain45SpSave1SparePspO.sql"]
["AHBG-35129","Sales Management/BasCu","Stored Procedure","CUSmain36SpSetProProces.sql"]
["AHBG-35129","Sales Management/BasCu","Stored Procedure","MdCuMn09S.SQL"]
["ahbg-35129","Sales Management/SaleContract","ILBO-EXTJS","Scaddsc_conmodconpriinvdet.htm"]
["ahbg-35129","Sales Management/SaleContract","ILBO-EXTJS","Scaddsc_conmodconpriinvdet_user.js"]
["AHBG-35171","Sales Management/BasCu","Stored Procedure","MdCuMn09S.SQL"]
["AHBG-35204","Sales Management/BasCu","Stored Procedure","MdCuMn10S.SQL"]
["ahbg-35258","Sales Management/BasCu","BRO","BasCu.dll"]
["ahbg-35258","Sales Management/BasCu","BRO","BasCu.Resources.dll"]
["ahbg-35258","Sales Management/BasCu","BRO","BasCu.zip"]
["ahbg-35258","Sales Management/BasCu","ILBO","cussysmod.dll"]
["ahbg-35258","Sales Management/BasCu","Stored Procedure","CrCuMn11S.Sql"]
["ahbg-35258","Sales Management/BasCu","Stored Procedure","CUSmain46SpsaveHdrChk.sql"]
["ahbg-35258","Sales Management/BasCu","Stored Procedure","MdCuMn08F.Sql"]
["AHBG-35258","Sales Management/BasCu","Stored Procedure","VwCuMn01F.Sql"]
["AHBG-35299","Maintenance SetUp/BASCm","Metadata","06_R59_COM1_BASCm_AHBG_31756_Metadata.sql"]
["AHBG-35299","Sales Management/SaleContract","Metadata","06_R59_COM1_SaleContract_APSE_40_Metadata.sql"]
["AHBG-35299","Sales Management/SaleContract","Stored Procedure","SC_MSC_PtEff_CMN_Validation.sql"]
["AHBG-35299","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpInit_homestock.sql"]
["AHBG-35299","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpPartEfPartEDspO.sql"]
["AHBG-35299","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpPD_SvHChk.sql"]
["AHBG-35299","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpPD_SvPartED.sql"]
["AHBG-35299","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpPD_SvPartEDspO.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","EdBank07T.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Actiontask_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Addcategry_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Addinfo_Hdr_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Addinfo_Hdrchk_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Addinfo_Save_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Aplicblty_Init_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Attribute_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_cntrct_billng_ele_ini_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Category_Init_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Con_Hdrchk_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_ConSaveTsk_Met.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Coveralt_Init_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Crncy_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Exclusion_hdFet_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Exclusion_mltFet_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Exclusion_Save_Met_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Exclusn_Hdrchk_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_cntrct_fixprce_hdfet_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_cntrct_fixprce_hdrchk_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_cntrct_fixprce_mltfet_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Fixprce_Sub_Met_Sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Fpfor_Init_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Go_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Maintype_Init_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_cntrct_Mnprcdtl_hdfet_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Monthlyprice_Sub_Sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_ObjEff_Init_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Payment_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_PgLnch_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Prcngbas_Init_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Prefcarrier_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Pricemulti_Init_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Priority_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_PrtClass_Init_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_PrtCtgry_Init_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Prtdtl_Hdr_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Prtgrp_Init_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Prtrefcde_Init_SP.SQL"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_repclsific_Init_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Repcode_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Revtype_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Save_CntExp_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Save_Mmet_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Save_Success_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Shipbill_Hdrchk_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_ShipBill_Save_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_ShipBill_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Shipcost_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Shipmethod_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_taskcatog_Init_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_tasktyp_Init_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_TATdtl_Hdrchk_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_TATdtl_Save_Met_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_TATdtl_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_TATend_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_TATstrt_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_udd1_Init_Sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_udd2_Init_Sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_udd3_Init_Sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Units_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Usrstatus_Init_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_WrkDtl_Hdrchk_Met_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Wrksave_mmet_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Wrkscp_Hdr_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_Wrkscp_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_Cntrct_wrkscrefcd_Init_sp.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_MtSpLc_Ini_mltUDBD1_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_MtSpLc_Ini_mltUDBD2_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_MtSpLc_Ini_mltUDBD3_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_MtSpLc_Ini_mltUDBD4_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Stored Procedure","Sup_MtSpLc_Ini_mltUDBD5_SP.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Table","03-R58-MAT2-BasSupplier-AlterTable-AHBG-32942.sql"]
["AHBG-35325","Procurement Management/BasSupplier","Table","03-R58-MAT2-BasSupplier-AlterTmpTable-AHBG-32942.sql"]
["AHBG-35343","Sales Management/BasCu","Stored Procedure","CUSmain46SpConfrmHdrRef.sql"]
["AHBG-35343","Sales Management/BasCu","Stored Procedure","CUSmain46Spps_noHdrRef.sql"]
["AHBG-35343","Sales Management/BasCu","Stored Procedure","CUSmain46Spps_noPrd_mlspO.sql"]
["AHBG-35343","Sales Management/BasCu","Stored Procedure","CUSmain46SpsavePrd_ml.sql"]
["AHBG-35364","Sales Management/BasCu","Stored Procedure","CUSmain46SpsaveHdrChk.sql"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","AuCmp03T.SQL"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","Cmp_AuCmpM_Sp_Ini_MnOpr.sql"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","Cmp_MnCmEn_Sp_Ini_MnOpr.sql"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmDT03F.SQL"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmDt05T.SQL"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmDt07S.SQL"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmDt09S.SQL"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmDT10S.SQL"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmp06T.sql"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmp07T.sql"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmp21S.SQL"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmUs02F.SQL"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmUs04T.SQL"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmUs08S.SQL"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnCmUs09S.SQL"]
["AHBG-35372","Component Maintenance/BasCMP","Stored Procedure","MnRWu06S.SQL"]
["AHBG-35379","Sales Management/BasCu","Stored Procedure","CUSmain46Spps_noHdrRef.sql"]
["AHBG-35379","Sales Management/BasCu","Stored Procedure","CUSmain46SpsaveHdrSav.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_CUS_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_Fet_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_INSP_Sav_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_INSP_VwML_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_INSPEntIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_INSPMandIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_INSPReqtypeIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_INSPStatusIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_PartCatIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_PrtTypIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_PV_Sav_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_PV_VwML_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_PVParameterIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_PVSinNewMdIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_PVSinOverMdIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_PVSinRepMdIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_PVSinShopVisMdIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_PVStatusIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_RADI_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_Sav_Hdr_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_Sav_HdrChk_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_SrchOnIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_StatusIni_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_Sv_SP.sql"]
["AHBG-35387","Inventory Setup/BasPartAdmn","Stored Procedure","PRT_MPT_View_Hdr_SP.sql"]
["AHBG-35391","Reliability Management/BasRS","BRO","BASRS.dll"]
["AHBG-35391","Reliability Management/BasRS","BRO","BASRS.Resources.dll"]
["AHBG-35391","Reliability Management/BasRS","BRO","BasRS.zip"]
["AHBG-35391","Reliability Management/BasRS","EXTJS-JSON","rsmngrelalrtdef_mngrelalrtdef.json"]
["AHBG-35391","Reliability Management/BasRS","ILBO","rsmngrelalrtdef.dll"]
["AHBG-35391","Reliability Management/BasRS","ILBO-EXTJS","Rsmngrelalrtdef_defrul.htm"]
["AHBG-35391","Reliability Management/BasRS","ILBO-EXTJS","Rsmngrelalrtdef_defrul_user.js"]
["AHBG-35391","Reliability Management/BasRS","ILBO-EXTJS","Rsmngrelalrtdef_defrulurr.htm"]
["AHBG-35391","Reliability Management/BasRS","ILBO-EXTJS","Rsmngrelalrtdef_defrulurr_user.js"]
["AHBG-35391","Reliability Management/BasRS","ILBO-EXTJS","Rsmngrelalrtdef_mngrelalrtdef.htm"]
["AHBG-35391","Reliability Management/BasRS","ILBO-EXTJS","Rsmngrelalrtdef_mngrelalrtdef_user.js"]
["AHBG-35391","Reliability Management/BasRS","Metadata","04-AHBG-35391-MX2-BasRS-Metadata-01.Sql"]
["AHBG-35391","Reliability Management/BasRS","Metadata","04-AHBG-35391-MX2-BasRS-Metadata-02.Sql"]
["AHBG-35391","Reliability Management/BasRS","Stored Procedure","RL_MRAD_alertrulesfor_Ini_sp.sql"]
["AHBG-35391","Reliability Management/BasRS","Stored Procedure","RL_MRAD_Fetch_SP.sql"]
["AHBG-35391","Reliability Management/BasRS","Stored Procedure","RL_MRAD_Rule_save_Hdrsp.sql"]
["AHBG-35391","Reliability Management/BasRS","Stored Procedure","RL_MRAD_Rule_save_MltSP.sql"]
["AHBG-35391","Reliability Management/BasRS","Stored Procedure","RL_MRAD_Rule_SaveSucMsg_Sp.sql"]
["AHBG-35391","Reliability Management/BasRS","Stored Procedure","RL_MRAD_Save_SP.sql"]
["AHBG-35391","Reliability Management/BasRS","Stored Procedure","RL_MRAD_SevLev_Ini_sp.sql"]
["AHBG-35391","Reliability Management/BasRS","Stored Procedure","RL_MRAD_VwDet_Sp.sql"]
["AHBG-35391","Reliability Management/BasRS","Stored Procedure","RS_DefRules_Fetch_Sp.sql"]
["AHBG-35391","Reliability Management/BasRS","Stored Procedure","RS_DefRules_save_sp.sql"]
["AHBG-35391","Reliability Management/BasRS","Stored Procedure","RS_MRAD_AlertruleUI_Sp.sql"]
["AHBG-35391","Reliability Management/BasRS","Table","02-AHBG-35391-MX2-BasRS-CreateTable-01.Sql"]
["AHBG-35391","Reliability Management/BasRS","Table","02-AHBG-35391-MX2-BasRS-CreateTableTmp-01.Sql"]
["AHBG-35391","Reliability Management/BasRS","Table","05-AHBG-35391-MX2-BasRS-Synonymn-0001.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Ben_Mainsave_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Cmn_Onenter_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_His_mv_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Info_Context_sp.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_Benml_met_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_PrtEx_met_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_PtDlml_met_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_Sc_met_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_Wh_met_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_BenMl_sp.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_Hdr_sp.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_PrtDtlMl_sp.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_PrtEx_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Prtno_Onenter_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_PtDl_Mainsave_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_PtEx_Mainsave_SP.sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Table","02-R58-MAT2-BasPoolMgmt-APSE-11-CreateTable-1.Sql"]
["AHBG-35402","Inventory Setup/BASPoolMgmt","Table","02-R58-MAT2-BasPoolMgmt-APSE-11-CreateTmpTable-2.sql"]
["AHBG-35406","Reliability Management/BasRS","DepMetaData","BasRS_DepMetaData.sql"]
["AHBG-35406","Reliability Management/BasRS","Stored Procedure","RS_Fleet_ACEff_SaveSucMsg_Sp.sql"]
["AHBG-35406","Reliability Management/BasRS","Stored Procedure","RS_Fleet_PrtEff_SaveSuMsg_Sp.sql"]
["AHBG-35406","Reliability Management/BasRS","Stored Procedure","RS_Fleet_View_AcEff_Sp.sql"]
["APSE-11","Inventory Setup/BasPartAdmn","Stored Procedure","AdPgp05S.Sql"]
["APSE-11","Inventory Setup/BasPartAdmn","Stored Procedure","MdPrt09S.Sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","BRO","BASPoolMgmt.dll"]
["APSE-11","Inventory Setup/BASPoolMgmt","BRO","BASPoolMgmt.Resources.dll"]
["APSE-11","Inventory Setup/BASPoolMgmt","BRO","BASPoolMgmt.zip"]
["APSE-11","Inventory Setup/BASPoolMgmt","DepMetaData","BASPoolMgmt_depmetadata.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","DepMetaData","BASPoolMgmt_depmetadata_Language.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","EXTJS-JSON","maintainpoolinfo_mnt_poolnew.json"]
["APSE-11","Inventory Setup/BASPoolMgmt","EXTJS-JSON","maintainpoolinfo_mnt_poolnew_template.json"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO","maintainpoolinfo.dll"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_core_rtn_rules.htm"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_core_rtn_rules_user.js"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_loctn_coverage.htm"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_loctn_coverage_user.js"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_mantn_service_levels.htm"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_mantn_service_levels_user.js"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_mnt_pool_demand_warehouse.htm"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_mnt_pool_demand_warehouse_user.js"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","maintainpoolinfo_mnt_poolnew.css"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_mnt_poolnew.htm"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_mnt_poolnew_user.js"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_mtn_pool_info.htm"]
["APSE-11","Inventory Setup/BASPoolMgmt","ILBO-EXTJS","Maintainpoolinfo_mtn_pool_info_user.js"]
["APSE-11","Inventory Setup/BASPoolMgmt","Index","07-R58-MAT2-BASPoolMgmt-APSE-11-Index-1.Sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Metadata","04-R58-MAT2-BASPoolmgmt-APSE-11-Metadata-1.Sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Metadata","04-R58-MAT2-BASPoolMgmt-APSE-11-Metadata-2.Sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","StateXML","MaintainPoolInfo_Mnt_PoolNew.xml"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Cmn_Save_Sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Cmn_Validations_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Ben_Mainsave_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Benprteff_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Benusrdef1_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Benusrdef2_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Category_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Cmn_Onenter_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Customerno_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Excprteff_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Hdr_Sav_SP.SQL"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_His_mv_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Info_Context_sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_Benml_met_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_Cntexp_Sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_Hdr_Sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_HdrChk_Sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_PrtEx_met_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_PtDlml_met_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_Sc_met_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_Save_Wh_met_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_BenMl_sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_Cntexp_sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_Hdr_sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_PrtDtlMl_sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_PrtEx_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_Sc_sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_TileMl_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_IS_VwDet_Wh_sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Onenter_Rev_Init_sp.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Parttype_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Prtclassi_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_PrtExcusrdef1_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_PrtExcusrdef2_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Prtgrp_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Prtlist_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Prtno_Onenter_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Prtplngrp_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Prtsalety_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Prtusrdef1_init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Prtusrdef2_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_PtDl_Mainsave_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_PtEx_Mainsave_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Sc_Mainsave_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_State_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Statusrdef1_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Statusrdef2_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Succ_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Usrstatus_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Wh_Mainsave_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Whmpusrdef1_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Stored Procedure","Pool_Mng_Whmpusrdef2_Init_SP.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Table","02-R58-MAT2-BasPoolMgmt-APSE-11-CreateTable-1.Sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Table","02-R58-MAT2-BasPoolMgmt-APSE-11-CreateTmpTable-2.sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Table","02-R58-MAT2-BASPoolMgmt-APSE-11-Synonymn-1.Sql"]
["APSE-11","Inventory Setup/BASPoolMgmt","Table","03-R58-MAT2-BASPoolMgmt-APSE-11-AlterTable-1.Sql"]
["APSE-11","Inventory Setup/BasStockAdmn","Stored Procedure","CrQCd01I.Sql"]
["APSE-11","Inventory Setup/BasStockAdmn","Stored Procedure","EdQCd01I.Sql"]
["APSE-12","Procurement Management/BasSupplier","BRO","BASSUPPLIER.dll"]
["APSE-12","Procurement Management/BasSupplier","BRO","BASSUPPLIER.Resources.dll"]
["APSE-12","Procurement Management/BasSupplier","BRO","BasSupplier.zip"]
["APSE-12","Procurement Management/BasSupplier","DepMetaData","BasSupplier_DepMetaData.sql"]
["APSE-12","Procurement Management/BasSupplier","DepMetaData","BasSupplier_depmetadata_Language.sql"]
["APSE-12","Procurement Management/BasSupplier","EXTJS-JSON","mngsupsrcntr_copyfrom_msc.json"]
["APSE-12","Procurement Management/BasSupplier","EXTJS-JSON","mngsupsrcntr_mngsupsrcrtmain.css"]
["APSE-12","Procurement Management/BasSupplier","EXTJS-JSON","mngsupsrcntr_mngsupsrcrtmain.json"]
["APSE-12","Procurement Management/BasSupplier","EXTJS-JSON","mngsupsrcntr_mngsupsrcrtmain_template.json"]
["APSE-12","Procurement Management/BasSupplier","ILBO","mngsupsrcntr.dll"]
["APSE-12","Procurement Management/BasSupplier","Metadata","01-MAT1-APSE-12_ManageSupContract_MetaData.SQL"]
["APSE-12","Procurement Management/BasSupplier","Table","01_MAT1_APSE-12_BasSupplier_Suppliercontract_CreateTable.SQL"]
["APSE-12","Procurement Management/BasSupplier","Table","01_MAT1_APSE-12_BasSupplier_Suppliercontract_CreateTmpTable.SQL"]
["APSE-12","Procurement Management/BasSupplier","Table","02_MAT1_APSE-12_BasSupplier_Suppliercontract_CreateSynonym.SQL"]
["APSE-12","Procurement Management/BasSupplier","Table","03_MAT1_APSE-12_BasSupplier_Suppliercontract_CreateHistable.SQL"]
["APSE-246","Configuration Management/BasAircraft","Stored Procedure","MdGrp10S.sql"]
["APSE-246","Configuration Management/BasAircraft","Table","04-R59-02-BasAircraft-Table-0001.sql"]
["APSE-246","Reliability Management/BASRA","Metadata","04_R59_MX2_BasRA_AlterMetadata.sql"]
["APSE-246","Reliability Management/BASRA","Stored Procedure","Ra_qccodes_HFet_Sp.sql"]
["APSE-246","Reliability Management/BASRA","Stored Procedure","Ra_qccodes_qctype_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","BRO","BASRS.dll"]
["APSE-246","Reliability Management/BasRS","BRO","BASRS.Resources.dll"]
["APSE-246","Reliability Management/BasRS","BRO","BasRS.zip"]
["APSE-246","Reliability Management/BasRS","DepMetaData","BasRS_DepMetaData.sql"]
["APSE-246","Reliability Management/BasRS","DepMetaData","BasRS_depmetadata_Language.sql"]
["APSE-246","Reliability Management/BasRS","EXTJS-JSON","rsmngfltdef_edtrelprts.json"]
["APSE-246","Reliability Management/BasRS","EXTJS-JSON","rsmngfltdef_rsmngfltdefui.json"]
["APSE-246","Reliability Management/BasRS","ILBO","rsmngfltdef.dll"]
["APSE-246","Reliability Management/BasRS","ILBO-EXTJS","Rsmngfltdef_edtrelprts.htm"]
["APSE-246","Reliability Management/BasRS","ILBO-EXTJS","Rsmngfltdef_edtrelprts_user.js"]
["APSE-246","Reliability Management/BasRS","ILBO-EXTJS","Rsmngfltdef_rsmngfltdefui.htm"]
["APSE-246","Reliability Management/BasRS","ILBO-EXTJS","Rsmngfltdef_rsmngfltdefui_user.js"]
["APSE-246","Reliability Management/BasRS","Index","07-R59-02-BasRS-Index_tmp.sql"]
["APSE-246","Reliability Management/BasRS","Metadata","04_R59_MX2_BasRS_AlterMetadata.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_EditPrtGrp_Param_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_EditPrtGrp_PartGrp_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_ACEff_SaveHdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_ACEff_SaveMlt_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_ACEff_SaveSucMsg_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_PrtEff_PtMgrp_Init_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_PrtEff_SaveHdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_PrtEff_SaveMlt_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_PrtEff_SaveSuMsg_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_Rpt_SaveHdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_Rpt_SaveMlt_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_Rpt_SaveSucMsg_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_Save_hdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_Save_SucMsg_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_View_AcEff_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_View_Hdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_View_PrtEff_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_View_Prtmgrp_Init_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Fleet_View_RelAppl_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_AcGroup_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_AcGroup_Onclk_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_Appli_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_AppliMlt_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_Create_Fleet_hdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_Edit_Fleet_Hdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_EditPartGrp_Fet_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_EditPartGrp_Get_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_EditPartGrp_Save_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_Fetch_hdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_FltCat_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_FltType_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_Get_hdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_OwnAgency_Onclk_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_Ownership_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_PartGrp_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_PrtEffDRMlt_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_PrtEffPrtGrpMlt_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_Save_AC_Eff_Hdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_Save_PrtEff_Hdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_Save_Rpt_Appl_Hdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_Status_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_MFD_Usersts_Ini_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Part_PartGrp_Save_Hdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Part_PartGrp_Save_Mlt_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Part_PartGrp_Save_SucMg_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Part_PartGrp_View_Hdr_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Stored Procedure","RS_Part_PartGrp_View_Mlt_Sp.sql"]
["APSE-246","Reliability Management/BasRS","Table","04-R59-02-BasRS-Table-0001.sql"]
["APSE-246","Reliability Management/BasRS","Table","04-R59-02-BasRS-Table_tmp-0001.sql"]
["APSE-246","Reliability Management/BasRS","Table","04-R59-03-BasRS-Table-0001.sql"]
["APSE-246","Reliability Management/BasRS","Table","04-R59-03-BasRS-Table_tmp-0001.sql"]
["APSE-246","Reliability Management/BasRS","Table","05-R59-01-BasRS-Synonymn.sql"]
["APSE-246","Reliability Management/BasRS","Table","05-R59-02-BasRS-Synonymn.sql"]
["APSE-246","Reliability Management/BasRS","Table","07-R59-01-BasRS-Index.sql"]
["APSE-246","Reliability Management/BasRS","Table","07-R59-01-BasRS-Index_tmp.sql"]
["APSE-257","Inventory Setup/BasPartAdmn","BRO","BASPARTADMN.dll"]
["APSE-257","Inventory Setup/BasPartAdmn","BRO","BASPARTADMN.Resources.dll"]
["APSE-257","Inventory Setup/BasPartAdmn","BRO","BasPartadmn.zip"]
["APSE-257","Inventory Setup/BasPartAdmn","DepMetaData","BasPartAdmn_DepMetaData.sql"]
["APSE-257","Inventory Setup/BasPartAdmn","DepMetaData","BasPartAdmn_depmetadata_Language.sql"]
["APSE-257","Inventory Setup/BasPartAdmn","EXTJS-JSON","mngprttecdtreq_mngprttecdtreq.json"]
["APSE-257","Inventory Setup/BasPartAdmn","ILBO","mngprttecdtreq.dll"]
["APSE-257","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Mngprttecdtreq_mngprttecdtreq.htm"]
["APSE-257","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Mngprttecdtreq_mngprttecdtreq_user.js"]
["APSE-257","Inventory Setup/BasPartAdmn","Metadata","04-R59-MX2-APSE-257-Metadata-01.Sql"]
["APSE-257","Inventory Setup/BasPartAdmn","StateXML","MngPrtTecDtReq_MngPrtTecDtReq.xml"]
["APSE-257","Inventory Setup/BasPartAdmn","Table","02-APSE-257-MX2-BasPartAdmn-CreateTable-01.Sql"]
["APSE-257","Inventory Setup/BasPartAdmn","Table","02-APSE-257-MX2-BasPartAdmn-CreateTableTmp-01.Sql"]
["APSE-257","Inventory Setup/BasPartAdmn","Table","05-APSE-257-MX2-BasPartAdmn-Synonymn-0001.sql"]
["APSE-26","Sales Management/BasCu","BRO","BasCu.dll"]
["APSE-26","Sales Management/BasCu","BRO","BasCu.Resources.dll"]
["APSE-26","Sales Management/BasCu","BRO","BasCu.zip"]
["APSE-26","Sales Management/BasCu","DepMetaData","BasCu_depmetadata.sql"]
["APSE-26","Sales Management/BasCu","EXTJS-JSON","cusaddcus_cusaddcusmain.json"]
["APSE-26","Sales Management/BasCu","EXTJS-JSON","cussysmod_cussysmodmain.json"]
["APSE-26","Sales Management/BasCu","EXTJS-JSON","cusvwcus_cusvwcusmain.json"]
["APSE-26","Sales Management/BasCu","EXTJS-JSON","mancussprspl_mancussprspl.json"]
["APSE-26","Sales Management/BasCu","ILBO","cusaddcus.dll"]
["APSE-26","Sales Management/BasCu","ILBO","cussysmod.dll"]
["APSE-26","Sales Management/BasCu","ILBO","cusvwcus.dll"]
["APSE-26","Sales Management/BasCu","ILBO","mancussprspl.dll"]
["APSE-26","Sales Management/BasCu","ILBO-EXTJS","Cusaddcus_cusaddcusmain.htm"]
["APSE-26","Sales Management/BasCu","ILBO-EXTJS","Cusaddcus_cusaddcusmain_user.js"]
["APSE-26","Sales Management/BasCu","ILBO-EXTJS","Cussysmod_cussysmodmain.htm"]
["APSE-26","Sales Management/BasCu","ILBO-EXTJS","Cussysmod_cussysmodmain_user.js"]
["APSE-26","Sales Management/BasCu","ILBO-EXTJS","Cusvwcus_cusvwcusmain.htm"]
["APSE-26","Sales Management/BasCu","ILBO-EXTJS","Cusvwcus_cusvwcusmain_user.js"]
["APSE-26","Sales Management/BasCu","ILBO-EXTJS","Mancussprspl_mancussprspl.htm"]
["APSE-26","Sales Management/BasCu","ILBO-EXTJS","Mancussprspl_mancussprspl_user.js"]
["APSE-26","Sales Management/BasCu","Index","07-R59-01-BasCu-Index-0004-Tmp.sql"]
["APSE-26","Sales Management/BasCu","Index","07-R59-01-BasCu-Index-0004.sql"]
["APSE-26","Sales Management/BasCu","Index","07-R59-01-BasCu-Index-0005.sql"]
["APSE-26","Sales Management/BasCu","Metadata","07_R59_Com1_BAVN_APSE-26_ALTERMETADATA.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUS_rsplSp_Hdr_validation.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUS_rsplsp_mlt_validation.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpAC_ModHdrRef.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpAC_ModSparePspO.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpConfirHdrChk.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpConfirHdrRef.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpConfirHdrSav.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpConfirSpareP.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpConfirSparePspO.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpfetHdrFet.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpfetSpareP.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpinitBFE_ML.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpinitRSPLRe.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpinitStatus.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpSave1HdrChk.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpSave1HdrRef.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpSave1HdrSav.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpSave1SpareP.sql"]
["APSE-26","Sales Management/BasCu","Stored Procedure","CUSmain45SpSave1SparePspO.sql"]
["APSE-26","Sales Management/BasCu","Table","03-R59-01-BasCu-Table-0005-Tmp.sql"]
["APSE-26","Sales Management/BasCu","Table","03-R59-01-BasCu-Table-0005.sql"]
["APSE-26","Sales Management/BasCu","Table","03-R59-01-BasCu-Table-0006.sql"]
["APSE-26","Sales Management/BasCu","Table","05-R59-01-BASCU-Synonymn-0001-Tmp.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","BRO","BASPARTADMN.dll"]
["APSE-274","Inventory Setup/BasPartAdmn","BRO","BASPARTADMN.Resources.dll"]
["APSE-274","Inventory Setup/BasPartAdmn","BRO","BasPartadmn.zip"]
["APSE-274","Inventory Setup/BasPartAdmn","BRO","baspartadmn_bulk.dll"]
["APSE-274","Inventory Setup/BasPartAdmn","DepMetaData","BasPartAdmn_DepMetaData.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","DepMetaData","BasPartAdmn_depmetadata_Language.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","EXTJS-JSON","prtaddmaininfo_prtaddmainmain.json"]
["APSE-274","Inventory Setup/BasPartAdmn","EXTJS-JSON","prtaddqkinfo_prtaddqkinfomain.json"]
["APSE-274","Inventory Setup/BasPartAdmn","EXTJS-JSON","prtmntapinfo_prtmntapinfomain.json"]
["APSE-274","Inventory Setup/BasPartAdmn","EXTJS-JSON","prtmntbasicinfo_mngaddinf_part.json"]
["APSE-274","Inventory Setup/BasPartAdmn","EXTJS-JSON","prtmntbasicinfo_prtmntbasicaddlpla.json"]
["APSE-274","Inventory Setup/BasPartAdmn","EXTJS-JSON","prtmodmaininfo_prtmodmaininfomain.json"]
["APSE-274","Inventory Setup/BasPartAdmn","EXTJS-JSON","prtvwallinfo_prtvwallinfomain.json"]
["APSE-274","Inventory Setup/BasPartAdmn","EXTJS-JSON","prtvwallinfo_prtvwallinfoplan.json"]
["APSE-274","Inventory Setup/BasPartAdmn","EXTJS-JSON","prtvwapinfo_prtvwapinfomain.json"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO","prtaddmaininfo.dll"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO","prtaddqkinfo.dll"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO","prthlppart.dll"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO","prtmntapinfo.dll"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO","prtmntbasicinfo.dll"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO","prtmodmaininfo.dll"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO","prtvwallinfo.dll"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO","prtvwapinfo.dll"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtaddmaininfo_prtaddmainmain.htm"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtaddmaininfo_prtaddmainmain_user.js"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtaddqkinfo_prtaddqkinfomain.htm"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtaddqkinfo_prtaddqkinfomain_user.js"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtmntapinfo_prtmntapinfomain.htm"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtmntapinfo_prtmntapinfomain_user.js"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtmntbasicinfo_mngaddinf_part.htm"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtmntbasicinfo_mngaddinf_part_user.js"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtmntbasicinfo_prtmntbasicaddlpla.htm"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtmntbasicinfo_prtmntbasicaddlpla_user.js"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtmodmaininfo_prtmodmaininfomain.htm"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtmodmaininfo_prtmodmaininfomain_user.js"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtvwallinfo_prtvwallinfomain.htm"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtvwallinfo_prtvwallinfomain_user.js"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtvwallinfo_prtvwallinfoplan.htm"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtvwallinfo_prtvwallinfoplan_user.js"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtvwapinfo_prtvwapinfomain.htm"]
["APSE-274","Inventory Setup/BasPartAdmn","ILBO-EXTJS","Prtvwapinfo_prtvwapinfomain_user.js"]
["APSE-274","Inventory Setup/BasPartAdmn","Index","03-R59-MAT2-BasPartAdmn-Index-APSE-274.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Metadata","05-R58-MAT2-BASPARTADMN-Metadata-APSE-274.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","StateXML","PrtMntAPInfo_PrtMntAPInfoMain.xml"]
["APSE-274","Inventory Setup/BasPartAdmn","StateXML","PrtMntBasicinfo_MngAddInf_Part.xml"]
["APSE-274","Inventory Setup/BasPartAdmn","StateXML","PrtMntBasicinfo_PrtMntBasicaddlPla.xml"]
["APSE-274","Inventory Setup/BasPartAdmn","StateXML","PrtVwAllinfo_PrtVwAllinfoPlan.xml"]
["APSE-274","Inventory Setup/BasPartAdmn","StateXML","PrtVwAPInfo_PrtVwAPInfoMain.xml"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","AdMGc04F.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","AdPgp05S.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","AsPGr02F.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","AsPGr04S.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","AsPGr07F.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","MdPrt09S.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Plng13F.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Plng14S.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Plng15F.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_MntAp_Main_M1Fet_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_MntAp_Main_M1Sub_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_MntAp_Main_R1Trn_Sp.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_MntAp_Main_R2Trn_Sp.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_Pln_Main_AddInf_Att_Ini_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_Pln_Main_AddInf_Cat_Ini_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_Plng_Main_AddInfo_AttUI_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_Plng_Main_AddInfo_CatUI_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_Plng_Main_AddInfo_HFet_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_Plng_Main_AddInfo_HSav_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_Plng_Main_AddInfo_MFet_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_Plng_Main_AddInfo_Mlt1_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_Plng_Main_AddInfo_MSav_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_Plng_Main_PrtPlnGrp_Ini_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","Prt_Pvap_Main_COND_MFet_Sp.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","PrtAp05F.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","PrtAp06F.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","PrtAp08S.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","PrtPlng_MainAddInfo_Attdes_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","PrtPlng_MainAddInfo_Catdes_SP.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","QKCD01I.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","VwAlt04F.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","VwAlt05F.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","VwPrt07F.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Stored Procedure","VwPrt23I.Sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Table","03-R59-MAT2-BasPartAdmn-alterTable-AHBG-35162.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Table","03-R59-MAT2-BasPartAdmn-Altertable-APSE-274.sql"]
["APSE-274","Inventory Setup/BasPartAdmn","Table","03-R59-MAT2-BasPartAdmn-CreateTable-APSE-274.sql"]
["APSE-340","Component Maintenance/BasCMP","BRO","BASCMP.dll"]
["APSE-340","Component Maintenance/BasCMP","BRO","BASCMP.Resources.dll"]
["APSE-340","Component Maintenance/BasCMP","BRO","BasCMP.zip"]
["APSE-340","Component Maintenance/BasCMP","DepMetaData","BasCMP_DepMetaData.sql"]
["APSE-340","Component Maintenance/BasCMP","DepMetaData","BasCMP_depmetadata_Language.sql"]
["APSE-340","Component Maintenance/BasCMP","EXTJS-JSON","cmpmntoptset_cmpmntoptsetmain.json"]
["APSE-340","Component Maintenance/BasCMP","EXTJS-JSON","cmpmntpossch_cmpmntposschdtadl.json"]
["APSE-340","Component Maintenance/BasCMP","EXTJS-JSON","cmpmntpossch_cmpmntposscheffadl.json"]
["APSE-340","Component Maintenance/BasCMP","EXTJS-JSON","cmpmntpossch_cmpmntposschuseadl.json"]
["APSE-340","Component Maintenance/BasCMP","EXTJS-JSON","cmpprtcmpschadj_mngprtcomschadj_.json"]
["APSE-340","Component Maintenance/BasCMP","ILBO","cmpmntpossch.dll"]
["APSE-340","Component Maintenance/BasCMP","ILBO","cmpprtcmpschadj.dll"]
["APSE-340","Component Maintenance/BasCMP","ILBO-EXTJS","Cmpmntoptset_cmpmntoptsetmain.htm"]
["APSE-340","Component Maintenance/BasCMP","ILBO-EXTJS","Cmpmntoptset_cmpmntoptsetmain_user.js"]
["APSE-340","Component Maintenance/BasCMP","ILBO-EXTJS","Cmpmntpossch_cmpmntposschdtadl.htm"]
["APSE-340","Component Maintenance/BasCMP","ILBO-EXTJS","Cmpmntpossch_cmpmntposschdtadl_user.js"]
["APSE-340","Component Maintenance/BasCMP","ILBO-EXTJS","Cmpmntpossch_cmpmntposscheffadl.htm"]
["APSE-340","Component Maintenance/BasCMP","ILBO-EXTJS","Cmpmntpossch_cmpmntposscheffadl_user.js"]
["APSE-340","Component Maintenance/BasCMP","ILBO-EXTJS","Cmpmntpossch_cmpmntposschuseadl.htm"]
["APSE-340","Component Maintenance/BasCMP","ILBO-EXTJS","Cmpmntpossch_cmpmntposschuseadl_user.js"]
["APSE-340","Component Maintenance/BasCMP","ILBO-EXTJS","Cmpprtcmpschadj_mngprtcomschadj_.htm"]
["APSE-340","Component Maintenance/BasCMP","ILBO-EXTJS","Cmpprtcmpschadj_mngprtcomschadj__user.js"]
["APSE-340","Component Maintenance/BasCMP","Metadata","04-APSE-340-MX2-BasCMP-Metadata-01.sql"]
["APSE-340","Component Maintenance/BasCMP","StateXML","CMPMntPosSch_CMPMntPosSchDtAdl.xml"]
["APSE-340","Component Maintenance/BasCMP","StateXML","CMPMntPosSch_CMPMntPosSchEffAdl.xml"]
["APSE-340","Component Maintenance/BasCMP","StateXML","CMPMntPosSch_CMPMntPosSchUseAdl.xml"]
["APSE-340","Component Maintenance/BasCMP","StateXML","CMPPrtCmpSchAdj_MngPrtComSchAdj_.xml"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","cmp_schadj_adj_combo_sp.sql"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_Adjat_Int_Sp.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_bt_Sp.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_bwhdr_Sp.sql"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_Cnfcls_Int_Sp.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_Cnfcls_IntMl_Sp.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_Oprtr_Int_Sp.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_Oprtr_IntMl_Sp.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_Save_Hdr_Sp.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_Save_Hdrchk_Sp .sql"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_Save_Ml_Sp.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_Sts_Int_Sp.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_View_hdr_Sp.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","CMP_SchAdj_View_Ml_Sp.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnArEf01F.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnArEf01T.sql"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnArEf02F.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnArEf02T.sql"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnArEf03T.sql"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnArEf04T.sql"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnArEf05T.sql"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsDt04F.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsDt05F.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsDt06T.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsDt07T.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsDt08S.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsDt09S.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsDt10S.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsDt11S.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsDt12S.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsUs03F.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsUs04F.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsUs05T.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsUs06T.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsUs07S.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsUs08S.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsUs09S.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsUs10S.SQL"]
["APSE-340","Component Maintenance/BasCMP","Stored Procedure","MnPsUs11S.SQL"]
["APSE-340","Component Maintenance/BasCMP","Table","02-APSE-340-MX2-BasCMP-CreateTable-01.Sql"]
["APSE-340","Component Maintenance/BasCMP","Table","02-APSE-340-MX2-BasCMP-CreateTable-02.sql"]
["APSE-340","Component Maintenance/BasCMP","Table","02-APSE-340-MX2-BasCMP-CreateTableTmp-01.Sql"]
["APSE-340","Component Maintenance/BasCMP","Table","03-R58-MX2-BasCMP-AlterTable-01.sql"]
["APSE-340","Component Maintenance/BasCMP","Table","03-R58-MX2-BasCMP-AlterTableTmp-01.sql"]
["APSE-340","Component Maintenance/BasCMP","Table","05-APSE-340-MX2-BasCRM-Synonymn-0001.sql"]
["APSE-340","Configuration Management/BasConfig","Stored Procedure","cihlp02I.sql"]
["apse-39","Sales Management/BasCu","BRO","BasCu.dll"]
["APSE-39","Sales Management/BasCu","BRO","BasCu.Resources.dll"]
["apse-39","Sales Management/BasCu","BRO","BasCu.zip"]
["apse-39","Sales Management/BasCu","DepMetaData","BasCu_depmetadata.sql"]
["apse-39","Sales Management/BasCu","EXTJS-JSON","cusaddcus_cusaddcusmain.json"]
["APSE-39","Sales Management/BasCu","EXTJS-JSON","cusaddcus_mancusprtsallist.json"]
["apse-39","Sales Management/BasCu","ILBO","cusaddcus.dll"]
["apse-39","Sales Management/BasCu","ILBO","cussysmod.dll"]
["APSE-39","Sales Management/BasCu","ILBO-EXTJS","Cusaddcus_cusaddcusmain.htm"]
["apse-39","Sales Management/BasCu","ILBO-EXTJS","Cusaddcus_cusaddcusmain_user.js"]
["apse-39","Sales Management/BasCu","ILBO-EXTJS","Cusaddcus_mancusprtsallist.htm"]
["APSE-39","Sales Management/BasCu","ILBO-EXTJS","Cusaddcus_mancusprtsallist_user.js"]
["APSE-39","Sales Management/BasCu","Index","07-R59-01-BasCu-Index-0005-Tmp.sql"]
["APSE-39","Sales Management/BasCu","Stored Procedure","cu_partsallst_mlval_sp.sql"]
["APSE-39","Sales Management/BasCu","Stored Procedure","CUSmain46SpConfrmHdrRef.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46SpConfrmHdrSav.sql"]
["APSE-39","Sales Management/BasCu","Stored Procedure","CUSmain46SpfetHdrFet.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46SpfetPrd_ml.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46Spinitpr_grp.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46Spinitpribas.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46Spinitps_typ.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46Spinitr_acgr.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46SpinitStatus.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46Spinitstksts.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46Spinitudef_1.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46Spps_noHdrRef.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46Spps_noPrd_mlspO.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46SpsaveHdrChk.sql"]
["APSE-39","Sales Management/BasCu","Stored Procedure","CUSmain46SpsaveHdrRef.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46SpsaveHdrSav.sql"]
["APSE-39","Sales Management/BasCu","Stored Procedure","CUSmain46SpsavePrd_ml.sql"]
["apse-39","Sales Management/BasCu","Stored Procedure","CUSmain46SpsavePrd_mlspO.sql"]
["APSE-39","Sales Management/BasCu","Table","03-R59-01-BasCu-Table-0006-Tmp.sql"]
["APSE-39","Sales Management/BasCu","Table","03-R59-01-BasCu-Table-0008.sql"]
["APSE-39","Sales Management/BasCu","Table","05-R59-01-BasCu-Synonymn-0003.sql"]
["APSE-40","Sales Management/BasCu","Stored Procedure","CUSmain36SpSetProProces.sql"]
["APSE-40","Sales Management/SaleContract","BRO","SaleContract.dll"]
["APSE-40","Sales Management/SaleContract","BRO","SaleContract.Resources.dll"]
["APSE-40","Sales Management/SaleContract","BRO","SaleContract.zip"]
["APSE-40","Sales Management/SaleContract","DepMetaData","SaleContract_depmetadata.sql"]
["APSE-40","Sales Management/SaleContract","EXTJS-JSON","scaddsc_scaddscmain.json"]
["APSE-40","Sales Management/SaleContract","ILBO","scaddsc.dll"]
["APSE-40","Sales Management/SaleContract","ILBO-EXTJS","Scaddsc_scaddscmain.htm"]
["APSE-40","Sales Management/SaleContract","ILBO-EXTJS","Scaddsc_scaddscmain_user.js"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","contract_efft_out_sp.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","contract_efft_process_sp.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","contract_efft_ser_sp.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","Pri_info_common_validation.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","sal_cnt_cmn_cpy_cnt_sp.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_PtEff_CMN_Validation.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpCD_CopyHRef.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpCD_CopyHSav.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpCD_SvHRef.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpCD_SvHSav.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpConfirHRef.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpConfirHSav.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpfetHFet.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpGoHRef.sql"]
["apse-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpInit_HdrServType.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpInit_sertype.sql"]
["APSE-40","Sales Management/SaleContract","Stored Procedure","SC_MSC_SpPartEfPartEDspO.sql"]
["APSE-40","Sales Management/SaleContract","Table","04-R59-01-Salecontract-AlterTable-0002.sql"]
["apse-40","Sales Management/SaleContract","Table","04-R59-01-SaleContract-Table-0027.sql"]
["apse-40","Sales Management/SaleContract","Table","04-R59-01-SaleContract-Table-0030.sql"]
["APSE-40","Sales Management/SaleContract","Table","04-R59-01-SaleContract-Table-0031.sql"]
["apse-40","Sales Management/SaleContract","Table","04-R59-01-SaleContract-Table-0036-Tmp.sql"]
["apse-40","Sales Management/SaleContract","Table","04-R59-01-SaleContract-Table-0041-Tmp.sql"]
["APSE-40","Sales Management/SaleContract","Table","04-R59-01-SaleContract-Table-0042-Tmp.sql"]
["APSE-40","Service Sales Management/CustSerOrder","Stored Procedure","cso_cmn_cofetch_sp.sql"]
["APSE-40","Service Sales Management/CustSerOrder","Stored Procedure","cso_cmn_efft_sp.sql"]
["APSE-40","Service Sales Management/CustSerOrder","Stored Procedure","cso_co_match_sp.sql"]
["APSE-40","Service Sales Management/CustSerOrder","Stored Procedure","CSO_MCO_SpEvaluaHdrChk.sql"]
["APSE-40","Service Sales Management/CustSerOrder","Stored Procedure","CSO_MCO_SpEvaluaPartdt.sql"]
["APSE-40","Service Sales Management/CustSerOrder","Stored Procedure","CSO_MCO_SpODSavHdrChk.sql"]

{"sheet":"Schema Changes","index":4,"n_rows":2,"n_cols":6,"rows_kept":2,"cut":false,"hidden":false,"merged":[]}
[]
["Database Name","Table Name","Modified Event","Column Added","Columns  Modified","Columns Dropped"]