{"text_format":"2","workbook":"xlsx","n_sheets":1,"sheets":["ManualActionsForApp10"],"not_rendered":{"charts":0,"images":1,"macros":0,"external_links":0,"defined_names":1,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"run_cost":"one","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":"ManualActionsForApp10","index":0,"n_rows":185,"n_cols":16,"rows_kept":185,"cut":false,"hidden":false,"merged":[[2,3,4,3],[2,4,4,4],[2,5,4,5],[2,6,4,6],[2,7,4,7],[2,8,4,8],[2,0,4,0],[2,1,4,1],[2,2,4,2],[6,14,16,14],[6,15,16,15],[6,4,16,4],[6,5,16,5],[6,6,16,6],[6,7,16,7],[6,8,16,8],[6,10,16,10],[2,14,4,14],[2,9,4,9],[2,10,4,10],[2,11,4,11],[2,12,4,12],[2,13,4,13],[6,0,16,0],[6,1,16,1],[6,2,16,2],[6,3,16,3],[23,10,34,10],[23,12,34,12],[23,13,34,13],[6,11,16,11],[6,12,16,12],[6,13,16,13],[17,0,22,0],[17,1,22,1],[17,2,22,2],[17,3,22,3],[17,4,22,4],[17,5,22,5],[23,6,34,6],[23,7,34,7],[17,14,22,14],[39,10,50,10],[39,12,50,12],[39,13,50,13],[39,14,50,14],[17,15,22,15],[23,0,34,0],[23,1,34,1],[23,2,34,2],[23,3,34,3],[23,4,34,4],[23,5,34,5],[17,7,22,7],[17,8,22,8],[17,9,22,9],[17,10,22,10],[17,12,22,12],[17,13,22,13],[23,14,34,14],[23,15,34,15],[23,8,34,8],[39,0,50,0],[39,1,50,1],[39,2,50,2],[35,0,37,0],[35,1,37,1],[35,2,37,2],[35,3,37,3],[35,4,37,4],[35,5,37,5],[39,15,50,15],[39,8,50,8],[35,8,37,8],[35,10,37,10],[35,12,37,12],[35,13,37,13],[35,14,37,14],[35,15,37,15],[39,3,50,3],[39,4,50,4],[39,5,50,5],[39,6,50,6],[39,7,50,7],[35,7,37,7],[58,13,64,13],[58,14,64,14],[58,15,64,15],[65,0,68,0],[65,1,68,1],[65,2,68,2],[65,3,68,3],[65,4,68,4],[58,4,64,4],[58,7,64,7],[58,8,64,8],[58,9,64,9],[58,10,64,10],[58,12,64,12],[58,0,64,0],[58,1,64,1],[58,2,64,2],[58,3,64,3],[65,12,68,12],[65,13,68,13],[65,14,68,14],[65,15,68,15],[65,10,68,10],[74,0,77,0],[74,1,77,1],[74,2,77,2],[74,3,77,3],[65,5,68,5],[65,6,68,6],[65,7,68,7],[65,8,68,8],[65,9,68,9],[74,10,77,10],[74,12,77,12],[74,13,77,13],[74,14,77,14],[74,15,77,15],[74,9,77,9],[78,0,81,0],[78,1,81,1],[78,2,81,2],[74,4,77,4],[74,5,77,5],[74,6,77,6],[74,7,77,7],[74,8,77,8],[78,10,81,10],[78,11,81,11],[78,12,81,12],[78,13,81,13],[78,14,81,14],[78,15,81,15],[78,3,81,3],[78,4,81,4],[78,6,81,6],[78,7,81,7],[78,8,81,8],[78,9,81,9],[85,10,89,10],[85,12,89,12],[85,13,89,13],[85,14,89,14],[85,15,89,15],[91,0,96,0],[91,1,96,1],[91,2,96,2],[85,4,89,4],[85,5,89,5],[85,6,89,6],[85,7,89,7],[85,8,89,8],[85,9,89,9],[85,0,89,0],[85,1,89,1],[85,2,89,2],[85,3,89,3],[91,9,96,9],[91,10,96,10],[91,12,96,12],[91,13,96,13],[91,14,96,14],[91,15,96,15],[91,3,96,3],[91,4,96,4],[91,5,96,5],[91,6,96,6],[91,7,96,7],[91,8,96,8],[97,0,103,0],[97,1,103,1],[97,2,103,2],[104,12,114,12],[104,13,114,13],[104,14,114,14],[104,15,114,15],[104,3,114,3],[104,4,114,4],[104,5,114,5],[104,6,114,6],[97,3,103,3],[97,4,103,4],[97,5,103,5],[97,6,103,6],[97,7,103,7],[104,7,114,7],[104,8,114,8],[97,9,103,9],[97,10,103,10],[97,12,103,12],[97,13,103,13],[97,14,103,14],[97,8,103,8],[115,0,117,0],[115,1,117,1],[115,2,117,2],[115,9,117,9],[115,10,117,10],[104,0,114,0],[104,1,114,1],[104,2,114,2],[104,9,114,9],[104,10,114,10],[115,12,117,12],[115,13,117,13],[115,14,117,14],[115,15,117,15],[115,3,117,3],[115,4,117,4],[115,5,117,5],[115,6,117,6],[115,7,117,7],[115,8,117,8],[118,11,122,11],[118,12,122,12],[118,13,122,13],[118,14,122,14],[118,15,122,15],[123,0,124,0],[123,1,124,1],[123,2,124,2],[118,4,122,4],[118,5,122,5],[118,7,122,7],[118,8,122,8],[118,9,122,9],[118,10,122,10],[118,0,122,0],[118,1,122,1],[118,2,122,2],[118,3,122,3],[123,9,124,9],[123,10,124,10],[123,12,124,12],[123,13,124,13],[125,15,129,15],[125,3,129,3],[125,4,129,4],[125,5,129,5],[125,7,129,7],[125,8,129,8],[125,9,129,9],[123,14,124,14],[123,15,124,15],[123,3,124,3],[123,4,124,4],[123,5,124,5],[123,6,124,6],[123,7,124,7],[123,8,124,8],[125,10,129,10],[125,11,129,11],[125,12,129,12],[125,0,129,0],[125,1,129,1],[125,2,129,2],[125,13,129,13],[125,14,129,14],[131,0,132,0],[131,1,132,1],[131,2,132,2],[131,3,132,3],[131,10,132,10],[131,12,132,12],[131,13,132,13],[131,14,132,14],[131,4,132,4],[131,5,132,5],[131,6,132,6],[131,7,132,7],[131,8,132,8],[131,9,132,9],[133,15,139,15],[133,4,139,4],[133,5,139,5],[133,6,139,6],[133,7,139,7],[133,8,139,8],[133,9,139,9],[131,15,132,15],[133,10,139,10],[133,12,139,12],[133,13,139,13],[133,0,139,0],[133,1,139,1],[133,2,139,2],[133,3,139,3],[141,1,144,1],[141,2,144,2],[141,3,144,3],[141,4,144,4],[141,14,144,14],[133,14,139,14],[141,15,144,15],[141,9,144,9],[141,10,144,10],[141,12,144,12],[141,13,144,13],[146,14,150,14],[146,15,150,15],[146,9,150,9],[146,10,150,10],[146,12,150,12],[146,13,150,13],[146,0,150,0],[146,1,150,1],[146,2,150,2],[146,3,150,3],[146,4,150,4],[146,5,150,5],[141,7,144,7],[141,8,144,8],[141,0,144,0],[141,5,144,5],[141,6,144,6],[146,7,150,7],[146,8,150,8],[151,10,159,10],[151,12,159,12],[151,13,159,13],[151,14,159,14],[151,15,159,15],[160,0,162,0],[160,1,162,1],[160,2,162,2],[151,4,159,4],[151,5,159,5],[151,6,159,6],[151,7,159,7],[151,8,159,8],[151,9,159,9],[151,0,159,0],[151,1,159,1],[151,2,159,2],[151,3,159,3],[160,10,162,10],[160,12,162,12],[160,13,162,13],[160,14,162,14],[163,4,165,4],[163,5,165,5],[163,6,165,6],[163,7,165,7],[163,8,165,8],[160,15,162,15],[163,0,165,0],[163,1,165,1],[163,2,165,2],[160,4,162,4],[160,5,162,5],[160,6,162,6],[160,7,162,7],[160,8,162,8],[160,9,162,9],[163,10,165,10],[163,12,165,12],[163,13,165,13],[163,14,165,14],[163,15,165,15],[163,9,165,9],[166,3,167,3],[166,4,167,4],[166,5,167,5],[166,6,167,6],[166,7,167,7],[166,8,167,8],[166,0,167,0],[166,1,167,1],[166,2,167,2],[172,13,173,13],[172,14,173,14],[172,15,173,15],[172,9,173,9],[172,10,173,10],[172,4,173,4],[166,9,167,9],[166,10,167,10],[166,12,167,12],[166,13,167,13],[166,14,167,14],[166,15,167,15],[172,6,173,6],[172,7,173,7],[172,8,173,8],[168,12,171,12],[168,13,171,13],[168,14,171,14],[168,15,171,15],[168,9,171,9],[168,10,171,10],[172,12,173,12],[172,0,173,0],[172,1,173,1],[172,2,173,2],[172,3,173,3],[168,4,171,4],[168,6,171,6],[168,7,171,7],[168,8,171,8],[168,0,171,0],[168,1,171,1],[168,2,171,2],[168,3,171,3],[174,8,184,8],[174,9,184,9],[174,10,184,10],[174,12,184,12],[174,13,184,13],[174,14,184,14],[174,15,184,15],[174,0,184,0],[174,1,184,1],[174,2,184,2],[174,3,184,3],[174,4,184,4],[174,5,184,5],[174,6,184,6],[174,7,184,7]]}
["Component ","APP9 \nUpgrade","APP10 \nUpgrade","Installation Step","Mandatory Action","Activity Description","Functional Conditions for Execution","Technical Dependencies","Consequences  \n(of not executing)","Script Name","Script requires\nuser input ","Steps","Functional Assistance\nRequired ","Parallel \nExecution","Estimated\nDuration ","Additional Information"]
["ACCRUL","All","All","Pre - Immediate","Yes","Update vouchers in hold tables to General Ledger","None","None","Inconsistent data in the General Ledger. This will affect Balances as well.","N/A","N/A","Before upgrading Accrul, make sure that all vouchers in hold table are updated to the General Ledger.","Yes","N/A",null,"Vouchers based on a voucher type for which Store Originalis selected, will still be available in the hold table after update to the General Ledger."]
["BACLI","All","All","Post - Immediate","Yes","Upgrade all IFS Business Reporter Reports using Upgrade Utility.","A new function named IFS() was introduced in the Office 365 version of Microsoft Excel 2016 from the February 2016 update. This function conflicts with a IFS Business Reporter specific function with the same name. Since there is one common version of IFS Business Reporter supporting all versions of Microsoft Excel, it was necessary to modify IFS Business Reporter as of Update 3 of IFS Applications 9. The modification means that all existing IFS Business Reporter reports have to be updated to be compatible with IFS Business Reporter version 3.2.8 and higher.","None","Reports will not work.","IFS Business Reporter Report Upgrade Utility","Yes","Use the tool named IFS Business Reporter Report Upgrade Utility.\n\nThe IFS Business Reporter Report Upgrade Utility handles upgrade of IFS Business Reporter reports according to the following:\n1. Reports saved on disk\n2. Automatic retrieval, upgrade and replacement of:\n             1. Saved and Published reports\n             2. Reports available in the Info Services report archive\n             3. Reports saved in Budget Process component (Budget Template and Archived Budget Templates).\n             4. Reports in the IFS Business Reporter specific Export Archive","No","N/A","Short","The tool does not handle automatic upgrade of IFS Business Reporter reports added as document revisions in Document Management. This must be handled manually."]
[]
[{"$nulls":15},"More about how to handle upgrade of IFS Business Reporter reports is described in a special section dealing with the The IFS Business Reporter Report Upgrade Utility."]
["BACLI","All","All","Post - Immediate","Yes","All IFS Business Reporter reports have to be modified.\nThis action is necessary due to refactoring of IFS Business Reporter and the new rendering option for the BR Execution Server based on OpenXML SDK.\nUse a local computer:\n- Install the latest version of IFS Business Reporter (BR)\n- Use BR to do a bulk download of all published and saved reports.\n- Use BR to do a bulk republish/resave of all downloaded reports. The republishing/resaving will make sure that compression and sorting of data sets is handled correctly.","Necessary action for customers using IFS Business Reporter, upgrading from before IFS Applications 10 Update 7 to Update 7 or later.\nRepublishing/resaving will ensure that compression of data sets is enabled and that data sets are sorted propely.","None","\tIt must be made sure that all reports are using data set compression and that data sets are sorted propely to ensure correct rendering of IFS Business Reporter reports.","N/A","N/A","On a local computer\n1. Install the latest version of IFS Business Reporter  (BR) on a local computer\n2. Use BR to perform a bulk download of all saved and published reports\n3. Perform a bulk republish/resave of all downloaded reports to make sure that compression of data sets is enabled and that data sets are sorted correctly.","No","N/A","Medium","Refer to the IFS Business Reporter Desiger's Guide for more information"]
["CRM","N/A","N/A","Post - Anytime","No","These scripts are used to import required FNDMIG jobs to migrate data entered by old \"IFS Sales & Marketing\" solution into \"IFS Applications\" (ENTERP and CRM). ","If you want to migrate data entered by old “IFS Sales & Marketing” solution into \"IFS Applications\" (ENTERP and CRM)","No","Not available the data entered by old “IFS Sales & Marketing” solution into \"IFS Applications\" (ENTERP and CRM)","1. POST_CRM_App9_ImportCRMAccountMigrationJobs.sql - ","No","Detail information/steps about the CRM migration jobs can be found here.","No","Yes","Cannot Predict"]
[{"$nulls":9},"Import required FNDMIG jobs used to migrate Account information "]
[{"$nulls":9},"2. POST_CRM_App9_ImportCRMContactMigrationJobs.sql - "]
[{"$nulls":9},"Import required FNDMIG jobs used to migrate Contact information"]
[{"$nulls":9},"3. POST_CRM_App9_ImportCRMActvityMigrationJobs.sql - "]
[{"$nulls":9},"Import required FNDMIG jobs used to migrate Activity information "]
[{"$nulls":9},"4. POST_CRM_App9_ImportCRMOpportunityMigrationJobs.sql - Import FNDMIG jobs used to migrate Opportunity information "]
[{"$nulls":9},"5. POST_CRM_App9_ImportCRMLeadMigrationJobs.sql - "]
[{"$nulls":9},"Import required FNDMIG jobs used to migrate Lead information "]
[{"$nulls":9},"6. POST_CRM_App9_ImportCRMCustomMigrationJobs.sql - "]
[{"$nulls":9},"Import required FNDMIG jobs used to migrate Custom objects"]
["DOCMAN","N/A","N/A","Post - Immediate","No","Fix Etrage association XML file references with no checked in date","Fix Etrage association XML file references with no checked in date to improve download performance.","None",null,"POST_DOCMAN_App8_CleanupCheckedInDateForEtrageFiles.sql","No","This script will look for and fix Etrage association XML file references with no checked in date. If an ORIGINAL file reference exists on the same document revision, its date will be used. If no ORIGINAL file reference exists it will be listed.","No","No","Short","Info 1: If a large number of information is spooled, there is a probability that the limit of the serveroutput (1,000,000) is reached and the file will end in an error. To remedy this you will have to retry the script (before each run back up any previously generated log files). This script is re-runnable."]
[]
[{"$nulls":6},"Only applicable if there is a CAD integration"]
[{"$nulls":11},"To execute the script:"]
[{"$nulls":11},"1. Locate the script and change the log file path to a preferred location (see Info 1)."]
[{"$nulls":11},"2. Execute the script as IFS Application Owner."]
["DOCMAN","N/A","N/A","Post - Immediate","Yes","List Doc Access Lines for removal where Person ID is set to  asterisk (*)","None","Upgrade should be completed. No invalid objects should exist in database.","Incorrect/unwanted access levels for relevant documents are granted to all users.","POST_DOCMAN_App8_ConditionallyDisplayDocAccessLines.sql","Yes","The script will identify","Yes","No","Short"]
[{"$nulls":9},"Generates a report that contains a list of Access Lines for removal.",null,"All the document access lines for users with person id *"]
[{"$nulls":11},"(asterisk)"]
[{"$nulls":11},"And then the access lines where * has edit access without the intention of the creator of the revision/sheet."]
[]
[{"$nulls":11},"A report is generated in the specified location (default c:\\accesslines_88317.html). Someone has to then decide whether the access line should be deleted or not."]
[]
[{"$nulls":11},"To execute the script:"]
[{"$nulls":11},"1. Make sure the Upgrade is completed with ZERO invalid objects."]
[{"$nulls":11},"2. If required, locate the script and change the location to where the report should be generated (fileName) "]
[{"$nulls":11},"3. Execute the script as IFS Application Owner."]
[{"$nulls":11},"4. Go through the generated report (accesslines_88317.html) and manually delete the records as needed."]
["DOCMAN","RTM - UPD1","N/A","Post - Immediate","No","List Person Group records where Person ID with asterisk (*) is included","Only applicable if a person with the Person ID * (asterisk) has been added to Person Group. ","Upgrade should be completed. No invalid objects should exist in database.","Users can approve a step of the Document Approval Process even if they do not belong to the group of the approval step. This issue occurs if the person * (Person ID is asterisk) is in the group.","POST_DOCMAN_App8_ListStarPersonGroups.sql","No","To execute the script:","Yes","No","Cannot Predict","Info 1: If a large number of information is spooled, there is a probability that the limit of the serveroutput (1,000,000) is reached and the file will end in an error. To remedy this you will have to retry the script (before each run back up any previously generated log files). This script is re-runnable."]
[{"$nulls":9},"Lists person groups for modification.",null,"1. Execute the script as IFS Application Owner."]
[{"$nulls":6},"Starting from IFS Applications 8 SP2 adding a person with Person ID * (asterisk) is not allowed.",{"$nulls":4},"2. Carefully go through the generated log file (group_id_with_Star_Person.log) and manually modify the records as needed (see Info 1)."]
["DOCMAN","N/A","N/A","Post - Immediate","Yes","Set Date Connected values for all document connection records (doc_reference_object records) where Date Connected field is empty",null,"None",null,"POST_DOCMAN_App8_RepairDateConnectedInDocRefObjects.sql","No","Execute the script as IFS Application Owner.","No","No","Cannot Predict"]
["DOCMAN","RTM - UPD5","N/A","Post - Immediate","No","Repair Key Ref of missing Voucher Type","Some of the object connections done prior to IFS Applications 75 SP3 thorough the windows Query Voucher Detail or Query Voucher Detail – GL were created with wrong KeyRef values where the keyref value could sometimes be missing the value of the VOUCHER_TYPE of the Voucher or the GL Voucher to which the object is connected. The purpose of this manual script is to handle those missing entries.",null,null,"POST_DOCMAN_App9_RepairKeyRefOfMissingVoucherType.sql",null,"This script writes all the object connections whose keyrefs are erroneous. i.e. the keyrefs that do not have Accounting_Year and Voucher_Type. Since its not possible to find the missing voucher type based on the available data (i.e. Company, Voucher_no and row_no) those erroneous keyrefs are inserted to a table called MISSING_VOU_DOC_CONN_TEMP_TABand the user will have to find the missing voucher_types manually.","Yes","No","Cannot Predict"]
[{"$nulls":9},"This script writes all the object connections whose keyrefs are erroneous. i.e. the keyrefs that do not have Accounting_Year and Voucher_Type."]
[{"$nulls":11},"This table contains columns for"]
[{"$nulls":11},"1. The type of object connection missing."]
[{"$nulls":11},"2. The lu_name for which the object is connected."]
[{"$nulls":11},"3. The company fetched from the keyref"]
[{"$nulls":11},"4. The voucher_no fetched from the keyref"]
[{"$nulls":11},"5. The row_no fetched from the keyref"]
[{"$nulls":11},"6. The voucher_type into which the user must enter the missing voucher_type manually"]
[{"$nulls":11},"After running this script once, it will fetch all the erroneous records and insert them into MISSING_VOU_DOC_CONN_TEMP_TAB"]
[{"$nulls":11},"Then the user must fill in the voucher_type column with the correct voucher type by searching in the database or the application to find the correct voucher or voucher row to which the object should be attached. After that the user must run this script again to fix those object connections."]
[{"$nulls":11},"User may run this script multiple times until all the connections are fixed. After all the connections are fixed MISSING_VOU_DOC_CONN_TEMP_TAB will be dropped by this script."]
["DOCMAN","RTM - UPD3","N/A","Post - Immediate","No","Update DOCMAN tables with new keys for OSHA LUs","Only if OSHA component is installed.","Only if OSHA component is installed.","Database will contain incorrect document reference values.","POST_DOCMAN_App9_RepairKeyRefOfOshaLUs.sql","No","Execute the script as IFS Application Owner.","No","Yes","Short"]
["DOCMAN","RTM - UPD3","N/A","Post - Immediate","No","Update DOCMAN tables with new keys for PERSON LUs","Only if PERSON component is installed.","Only if PERSON component is installed.","Database will contain incorrect document reference values.","POST_DOCMAN_App9_RepairKeyRefOfPersonLUs.sql","No","Execute the script as IFS Application Owner.","No","Yes","Short"]
["DOCMAN","RTM - UPD3","N/A","Post - Immediate","No","Update DOCMAN tables with new keys for PRJREP LUs","Only if PRJREP component is installed.","Only if PRJREP component is installed.","Database will contain incorrect document reference values.","POST_DOCMAN_App9_RepairKeyRefOfPrjrepLUs.sql","No","Execute the script as IFS Application Owner.","No","Yes","Short"]
["DOCMAN","RTM - UPD3","N/A","Post - Immediate","No","Update DOCMAN tables with new keys for STRACO LUs","Only if STRACO component is installed.","Only if STRACO component is installed.","Database will contain incorrect document reference values.","POST_DOCMAN_App9_RepairKeyRefOfStracoLUs.sql","No","Execute the script as IFS Application Owner.","No","Yes","Short"]
["DOCMAN","RTM - UPD3","N/A","Post - Immediate","No","Update DOCMAN tables with new keys for TRNADM LUs","Only if TRNADM component is installed.","Only if TRNADM component is installed.","Database will contain incorrect document reference values.","POST_DOCMAN_App9_RepairKeyRefOfTrnadmLUs.sql","No","Execute the script as IFS Application Owner.","No","Yes","Short"]
["ENTERP","All","All","Post - Anytime","No","Update existing Companies","It is recommended to perform an update of existing companies after an upgrade. The reason for this is to facilitate addition of new basic data that is required for new functionality.","None","New basic data will not be available in existing companies.","N/A","N/A","Updated using command Update Company in Application Base Setup / Enterprise / Company / Company page. More information around Company Template can be found in the Development Guide.","Yes","N/A","Cannot Predict","Updating an existing company actually means that new basic data is added to a Logical Unit. It does not mean that existing basic data is modified."]
["ENTERP","RTM - UPD10","RTM - UPD1","Post - Anytime","Yes","The Personal Data Management system is designed to help customers comply with personal data protection regulations. The purpose of this system is to remove or anonymize any personal data for which there is no valid legal basis for processing. Due to a few missing configuration entries in the Personal Data Management system, some personal address details could avoid anonymization despite the data clean-up.\nThe script shows the list of persons for whom there is a risk that their detailed personal address has not been successfully anonymized by the data cleanup procedure. In addition, if the RUN_CLEANUP is set to YES, the script will not only show the list of affected persons but also refresh the last update of data processing purposes and trigger a relevant cleanup action.","This script is only applicable if the Personal Data Management system is being used and the Detailed Address setting has been used in the Address Setup per Country page. Otherwise there is no need to run the script, unless the Data Protection Officer wants to ensure that there the is no unauthorized personal address information stored in the system.","LCS Patch 141382 installed.","If the script is not executed by the customer who is legally obligated (e.g. by GDPR) to dispose of personal data, there is a risk that the unauthorized details of person’s personal address will remain in the system violating the law.","POST_Enterp_App9_PersonDetailedAddressCleanup.sql","Yes","To execute the script:\n1. Locate the script and change the log file path to a preferred location. \n2. Set RUN_CLEANUP to one of the following values:\n-'YES' - if you want to report inconsistency in personal address detailed and run the cleanup\n- 'NO' - if you want to report inconsistency in personal address detailed and do not want to run the cleanup\n\nExecute the script as Application User with sufficient access rights.","Yes","N/A","Cannot Predict"]
[{"$nulls":5},"2. Change the data of the column Cash Flow type in Manual Cash Flow - Single and Manual Cash Flow - Repetitive pages to a manually defined cash flow type",{"$nulls":5},"2. Change all cash flow sources under this category to 'MANUAL' which is IFS system defined manual cash flow source."]
[{"$nulls":6},"If the Source column in Manual Cash Flow - Single and Manual Cash Flow - Repetitive pages having the values ('CUSTOMER ORDER','PURCHASE ORDER','PAYMENT') OR Cash Flow type having the following values",{"$nulls":4},"3. Define a new cash flow type under system defined 'MANUAL' source and change all cash flow types of these entries to newly created cash flow type."]
[{"$nulls":6},"('IFS_CUSINV','IFS_CUSTORD','IFS_CUSONA','IFS_SUPINV','IFS_PURORD',"]
[{"$nulls":6},"'IFS_SUPONA','IFS_FINPAY','IFS_FXFORWARD','IFS_FX','IFS_VAT',"]
[{"$nulls":6},"'IFS_OTHER_PAYMENTS','IFS_SALARIES','IFS_TAXES','IFS_CUSBOE',"]
[{"$nulls":6},"'IFS_SUPBOE','IFS_CUSCHK','IFS_SUPCHK','IFS_BADDEBT','IFS_CUSVAL')"]
[]
[{"$nulls":11},"2. Select the Analysis Id and select the command Analysis Details Cash Flow Source."]
[{"$nulls":11},"3. Select desired Cash Flow Source Ids to Order Cash Flow Analysis Snapshot."]
[{"$nulls":11},"4. Check Include in Cash Flow Analysis check box for selected entries and save."]
[{"$nulls":11},"5. Execute Update Analysis Online or Update Analysis in Background commands in Analysis Details Cash Flow Source page."]
["FNDBAS","N/A","N/A","Post - Anytime","No","Clean Language_Sys_Tab by deleting Centura Client (SO) and Rich Web Client (RWC) attributes.","This is only applicatble if the Centura Client has been used","None","Obsolete data in Language_Sys_Tab","POST_FNDBAS_APP8_Clean_LanguageSysTab.sql","No",null,"No","Yes","Short"]
["FNDBAS","N/A","N/A","Post - Anytime","No","This script will delete all old Centura profile values in all user profiles.","This is only applicatble if the Centura Client has been used","None","Old Centura profile values in all user profiles","POST_FNDBAS_APP8_DeleteCenturaProfileValues.sql","No","Consider migrating Saved Queries to Saved Searches using Migrate Saved Queries window in IFS Enterprise Explorer before executing this script.","No","Yes","Short"]
["FNDBAS","N/A","N/A","Post - Anytime","No","This script will delete old Database Alert Log Categories: 'IFS Sessions', 'Sessions' and 'Intrusions'.","If there is no need to keep the old records, Alert Log Categories: 'IFS Sessions', 'Sessions' and 'Intrusions'.","None","Old Database Alert Log Categories: 'IFS Sessions', 'Sessions' and 'Intrusions'.","POST_FNDBAS_APP9_RemoveOldServerLogs.sql","No",null,"No","Yes","Short"]
["FNDBAS","RTM Only","N/A","Post - Anytime","No","This script will delete Event Actions which uses the following obsolete action types:‘SMS_Message','Shell Command'.","If action trypes: SMS Message and Shell Command are used","None","Obsolete action types:‘SMS_Message','Shell Command'.","POST_FNDBAS_APP9_RemoveOldEventActions.sql","No",null,"No","Yes","Short"]
["FNDBAS","N/A","N/A","Post - Anytime","No","This script will change module name values with 'Temporary Description' and ' name' to correct values.","Translated name values for modules shown as 'Temporary Description'","None","Module name values with 'Temporary Description' and ' name' to correct values.","POST_FNDBAS_FixModuleBasicDataTranslations.sql","No",null,"No","Yes","Short"]
["FNDBAS","N/A","N/A","Pre - Anytime","Yes","This script provides a list of Oracle Users in the database that are not connected with the Fnd User of the same name. These Oracle Users will be connected with their respective Fnd Users during the upgrade.","To find Oracle users in the database who are not connected with the Fnd User of the same name.","None","Oracle Users who are not connected with the Fnd User of the same name will be connected with their respective Fnd Users during the upgrade.","PRE_FNDBAS_App9_ListUnconnectedOracleUsers.sql","No","If a particular Oracle User in this list should not be connected with the respective Fnd User you have three options:","No","Yes","Short"]
[{"$nulls":11},"1. Delete the Oracle Account but keep the Fnd User: A fresh Oracle Account will then be created during the upgrade."]
[{"$nulls":11},"2. Delete the Fnd User but keep the Oracle Account: The Oracle Account will not be affected by the upgrade."]
[{"$nulls":11},"3. Delete both"]
["FNDBAS","N/A","N/A","Post - Immediate","No","This will move obsolete personal messages into tasks.","This is only applicatble if obsolete personal messages exist","None","Personal messages related to users will be not shown","POST_FNDBAS_APP9_MovePersonalMessages.sql","No",null,"No","Yes","Short"]
[{"$nulls":5},"Note:"]
[{"$nulls":5},"- Event actions rules for personal messages are not migrated, only already processed messages are. "]
[{"$nulls":5},"- Messages with the obsolete persons will be deleted."]
["FNDBAS","N/A","N/A","Pre - Anytime","No","This will update rowkey columns with data. Follow this linkfor more details.","Please follow this link","Please follow this link","Please follow this link","PRE_FNDBAS_UpdateRowkeyColumns.sql","No","Please follow this link","No","No"]
["FNDMIG","N/A","N/A","Post - Anytime","No","The Quick_Report_OUT Procedure is obsolete. It is recommended to use the built in Import/Export functionality in Quick Report. This script will remove all data related to any FNDMIG Quick Report Out Job.","This is only applicatble if FNDMIG Quick Report Out is used.","None","Obsolete data related to FNDMIG Quick Report Out Job.","POST_FNDMIG_APP9_RemoveProcQuickReportOut.sql","No",null,"No","Yes","Short"]
["FNDMIG","N/A","N/A","Post - Anytime","No","Corrects the execution plan on scheduled migration jobs which had an invalid date time format.","Applicable only if the Customer has a local which uses “.” instead of “:” as time separators (i.e time is displayed as 12.00 instead of 12:00).","None","Incorrect time formats. This can cause issues when populating the Scheduled Database Task window in Solution Manager.","POST_FNDMIG_App9_Repair_Currupted_Schedules.sql","No","After executing the script review and re-enable scheduled task listed in ChangedSchedulesLog.log.","No","Yes","Short"]
[{"$nulls":11},"2. Calculate the current difference in parallel currency in the Balance Sheet by comparing asset accounts with liability accounts."]
[{"$nulls":11},"3. Deduct the Income Statement difference from the Balance Sheet difference. The remaining amount should correspond to the total debit/credit difference in parallel currency for all accounts."]
[{"$nulls":11},"4. Using a new Asset or Liability account (depending on the sign of the difference), post the difference in parallel currency only in a manual voucher. Counter post the amount to a new account of logical account type Statistics."]
[{"$nulls":11},"5. Update the General Ledger"]
[{"$nulls":11},"The total balance in parallel currency for all accounts except the statistical account should now be zero, i.e. debit and credit balance should be equal. Also, The difference between all assets and liability accounts should be equal to the difference between all revenue and cost accounts, but with different sign (= current profit/loss)."]
["INTLED","All","All","Pre - Immediate","Yes","Update vouchers in Internal Ledger hold table to Internal Ledger","None","None","Inconsistent data in the Internal Ledger. This will affect Balances as well.","N/A","N/A","Before upgrading Intled make sure that all vouchers in the Internal Ledger hold tables are updated to the Internal Ledger.","Yes","N/A","Cannot Predict"]
[{"$nulls":11},"1. Calculate the current difference in parallel currency in the Income Statement by comparing revenue accounts with cost accounts (= current profit/loss)"]
[{"$nulls":11},"2. Calculate the current difference in parallel currency in the Balance Sheet by comparing asset accounts with liability accounts."]
[{"$nulls":11},"3. Deduct the Income Statement difference from the Balance Sheet difference. The remaining amount should correspond to the total debit/credit difference in parallel currency for all accounts."]
[{"$nulls":11},"4. Using a new Asset or Liability account (depending on the sign of the difference), post the difference in parallel currency only in a manual voucher. Counter post the amount to a new account of logical account type Statistics."]
[{"$nulls":11},"5. Update the Internal Ledger"]
[{"$nulls":11},"The total balance in parallel currency for all accounts except the statistical account should now be zero, i.e. debit and credit balance should be equal. Also, The difference between all assets and liability accounts should be equal to the difference between all revenue and cost accounts, but with different sign (= current profit/loss)."]
["ORDER","N/A","N/A","Pre - Immediate","Yes","For future reference, extract information of return material authorization lines where the parts have been reported as arrived but have not yet been moved to inventory or scrapped.","Only applicable if backup is needed for return material authorization lines where the parts have been reported as arrived but have not yet been moved to inventory or scrapped to be able to physically identify such quantity.","None","There can be physically received quantity that exists in unknown locations, that have not been moved to inventory locations or scrapped, and such quantity will not be possible to identify after the upgrade.","N/A","N/A","In order to backup of such Return Martial Authorization lines, it is advisable to run the below advanced query before the upgrade.","No","Yes","Short","Before APP9, for inventory parts it was possible to receive quantity without moving to inventory or performing scrap. This means the particular quantity had physically arrived, but had not yet been moved to inventory or scrapped. If such quantity has arrived then the Total Qty Received field on the RMA line had been updated but the Returned Inv Qty and Scrapped Qty had not been updated since no quantity had been moved to inventory or scrapped physically. "]
[{"$nulls":11},"1. Connect all sites to gather all the RMA data that is expected by running this advanced query.",null,null,null,"After upgrade the Total Qty Received will be equal to Returned Inv Qty + Scrapped Qty. Therefore any quantity that had arrived but had not yet been moved to inventory or scrapped will not be shown in the Total Qty Received field. "]
[{"$nulls":11},"2. Go to the Return Material Authorization Lines window, (IFS Enterprise Explorer address= ifsapf:tbwReturnMaterialOverview). Use Search, Advanced, SQL and use the following text to populate data. ",null,null,null,"The extracted information will be used for reference purpose to know if there is any discrepancy of quantity arrived but have not yet been moved to inventory or scrapped so such discrepancy should be physically identified. "]
[{"$nulls":15},"If the RMA line is customer order connected, then the returned quantity on customer order line has to be manually set on the customer_order_line_tab to be equal to Total Qty Received field value of all the connected RMA lines."]
[{"$nulls":11},"(NVL(QTY_RECEIVED,0) * CONV_FACTOR / INVERTED_CONV_FACTOR) > NVL(QTY_RETURNED_INV, 0) + NVL(QTY_SCRAPPED, 0) "]
[{"$nulls":11},"AND PART_NO IS NOT NULL"]
[{"$nulls":11},"3. After populating, data can be exported for future reference."]
["ORDER","All","N/A","Post - Immediate","Yes","The post script POST_Order_ConvertOrderQuotationProspect.sql creates “Prospect” type customers with customer related detail entered in prospect Sales Quotations. The address detail entered in the ‘Customer Address’ of the Sales window will be transferred as delivery and document addresses of the new prospect customers for valid addresses. After the upgrade, the table quote_prospect_customer_1410 will have two columns invalid_del_addr_upg and invalid_doc_addr_upp with the value ‘TRUE’, for addresses that were NOT transferred because they were invalid as per the ‘Address Setup per Country’ window.","Before Application 9, Prospect sales quotations were created without a customer. The address detail of the customer was saved in QUOTE_PROSPECT_CUSTOMER_TAB and before App8, these addresses were not validated against \"Address Setup per Country\" entries per country. With this script, when upgrade to Application 9, a customer of Prospect category is created and connected to the sales quotation. When customer addresses are created with old data, address validation errors are fired if a particular country need validation as per Address Setup per Country window, but old sales quotation has invalid address data.","None","A prospect with an incomplete address will not have the address created after the upgrade. The address needs to be entered again if the intention is to use it.","N/A","N/A","1. After the upgrade, the table quote_prospect_customer_1410 will have two columns invalid_del_addr_upg and invalid_doc_addr_upg with values ‘TRUE’ or ‘FALSE’. Therefore, the customers created without the address detail from prospect sales quotations can be quarried  with the following SQL statement: ","Yes","Yes","Short","This enhancement is done in LCS Bug 136492."]
[{"$nulls":11},"SELECT q.customer_no, q.quotation_no, 'Delivery Address' error_occured_in, p.del_name name, p.del_country_code country_code, p.del_address1 address1, p.del_address2 address2, p.del_zip_code zip_code, p.del_city city, p.del_county county, p.del_state state "]
[{"$nulls":11},"  FROM order_quotation_tab q, quote_prospect_customer_1410 p "]
[{"$nulls":11},"WHERE p.invalid_del_addr_upg = 'TRUE' "]
[{"$nulls":11},"  AND p.quotation_no = q.quotation_no "]
[{"$nulls":11},"UNION "]
[{"$nulls":11},"SELECT q.customer_no, q.quotation_no, 'Document Address' error_occured_in, p.doc_name name, p.doc_country_code country_code, p.doc_address1 address1, p.doc_address2 address2, p.doc_zip_code zip_code, p.doc_city city, p.doc_county county, p.doc_state state "]
[{"$nulls":11},"  FROM order_quotation_tab q, quote_prospect_customer_1410 p "]
[{"$nulls":11},"WHERE p.invalid_doc_addr_upg = 'TRUE' "]
[{"$nulls":11},"  AND p.quotation_no = q.quotation_no;"]
[{"$nulls":11},"2. The results from this query for the quotation address data that are invalid must be inspected and decide what action is needed. i.e. Either to enter addresses for a newly created prospect customers (fetched in customer_no column), with the old data fetched in rest of the columns, or ignore if any address data is no more required."]
["PAYLED","All","All","Pre - Immediate","Yes","Check whether all the necessary payment related transactions are completed",null,"None","Inconsistency in Payment data and might cause installation errors during the Upgrade","N/A","N/A","Before upgrading Payled please make sure that all reminder proposals, external payments and mixed payments are fully processed.","Yes","No","Cannot Predict"]
[]
[]
["PCMSTD","All","N/A","Pre - Anytime","No","Update existing Material and/or Tool Facility lines that are not connected to an Operation","Upgrading to IFS Applications 10 requires all Material and Tool Facility lines to be connected to an operation in Standard Job. This is because Material and Tool Facility (as a Resource) will always be created under a Work List in IFS Applications 10. ","None","Upgrade will create an extra Work List line to connect all unconnected Material and Tool Facility records.","N/A","N/A","Query for the relevant records and perform the necessary data updates.","No","No","Cannot Predict"]
[]
[{"$nulls":6},"In case there are unconnected Material and Tool Facility lines, the upgrade will create an extra Work List line to connect all those Material and Tool Facility records. Exception; if there is only one Work List available, then the upgrade will connect all Material and Tool Facility to that Work List. "]
[]
[{"$nulls":6},"If this is not what you want and you need all Material and Tool Facility to be connected to a specific Work List then you need to connect all Material and Tool Facility to an operation line before the upgrade."]
["PCMSTD","All","N/A","Post - Immediate","Yes","Update Resource Group Column if NULL values are found","There may be records created without a resource group in Task Template/Work List/Resources tab. You are advised to update the Resource Group column if null values are found.","None","If records are not updated, errors will be raised when a PM or WO is generated using these task templates.","POST_PCMSTD_App10_TaskTempResourceDemandsWithoutGroup.sql","No","Use the SQL query provided in the script to find such task templates that require modification.","No","Yes","Short"]
[{"$nulls":11},"Note: The script is for querying purposes only and does not modify data."]
["PM","All","N/A","Pre - Anytime","No","Update existing Material and/or Tool Facility lines that are not connected to an Operation","Upgrading to IFS Applications 10 requires all Material and Tool Facility lines to be connected to an operation in PM Action. This is because Material and Tool Facility (as a Resource) will always be created under a Work List in IFS Applications 10. ","None","Upgrade will create an extra Work List line to connect all unconnected Material and Tool Facility records.","N/A","N/A","Query for the relevant records and perform the necessary data updates.","No","No","Cannot Predict"]
[]
[{"$nulls":6},"In case there are unconnected Material and Tool Facility lines, the upgrade will create an extra Work List line to connect all those Material and Tool Facility records. Exception; if there is only one Work List available, then the upgrade will connect all Material and Tool Facility to that Work List. "]
[]
[{"$nulls":6},"If this is not what you want and you need all Material and Tool Facility to be connected to a specific Work List then you need to connect all Material and Tool Facility to an operation line before the upgrade."]
["PM","All","All","Post - Immediate","No","Update Planned Start, Finish dates and Earlier Start Finish dates in PM Maintenance Plan.","Issue: After the upgrade some PM Actions Maintenance Plan does not have a value in Planned Start/Planned Finish/Earliest Start/Latest Finish dates. As a result work orders will be generated without planned start and finish dates from these PM actions.\nThis script will update Planned Start, Finish dates and Earlier Start Finish dates in PM Maintenance Plan.\nScript will also update the 'Date To' date in PM Action Calendar Operation and in Activities.\nScript can be run for a given site, several given sites or for all sites.",null,"As a result work orders will be generated without planned start and finish dates from these PM actions.","POST_PM_App10_UpdatePmCalendarPlanDates.sql","Yes","Execute the script as IFS Application Owner.\nIf you wish to run this script for a single site, enter the desired site and press ENTER.\nIf you want run this script ONLY for a set of sites please enter the desired sites seperated by a '^' sign on the prompt and press ENTER.\nIf you wish to run this script for ALL sites, enter '%' AND press ENTER.","Yes",null,"Cannot Predict","If you wish to run this script for ALL sites, enter '%' AND press ENTER."]
["PM","All","N/A","Post - Immediate","Yes","Update Resource Group Column if NULL values are found","There may be records created without a resource group in PM Action/Work List/Resources tab. You are advised to update the Resource Group column if null values are found.",null,"If records are not updated, errors will be raised when a WO is generated using these PM actions.","POST_PM_App10_PMResourceDemandsWithoutGroup.sql",null,"Use the SQL query provided in the script to find such task templates that require modification."]
[{"$nulls":11},"Note: The script is for querying purposes only and does not modify data."]
["PROJ","N/A","N/A","Post - Immediate","No","Generate spreading for all activities which do not have spreading for its resource planning lines","If customer need resource spreading information to be shown for activities after upgrade, this should be run",null,"Resource spreading information will not be shown after upgrade","POST_Proj_App9_GenerateActivityResourceSpreading.sql","Yes","Since this might take a long time to complete, Oracle parallel execution is used within the script to speedup execution. Hence to obtain the full benefits of parallel execution and to allow the script to complete in a timely fashion this should be deployed in the following manner:","Yes","N/A","Long"]
[]
[{"$nulls":11},"1. Before deploying, the job_queue_processes system parameter should be set to 25. This can be achieved through the following steps"]
[{"$nulls":11},"2. Obtain the current value of this parameter by executing \"select value from v$parameter where name = 'job_queue_processes';\" statement and note the result."]
[{"$nulls":11},"3. If it is less than 25, execute \"alter system set job_queue_processes = 25;\" and change it to 25."]
[{"$nulls":11},"4. Deploy the script using the Application Owner user."]
[{"$nulls":11},"5. Once the script is finished executing, reset the job_queue_processes parameter to the original value by executing \"alter system set job_queue_processes = <original value>;\"."]
[]
["PRJREP","All","N/A","Post - Immediate","No","Regenerate posting for project transactions if posting setup or cost element is changed.","When the posting setup is changed manually for PRJIT% and if we need to get the planned revenue through new cost elements.",null,"It will keep existing preliminary postings & planned cost as it is and not reflecting new posting changes","Post_Prjrep_App9_RecreatePostings.sql","Yes","1. Execute this script as IFS Application Owner.","Yes","Yes","Long"]
[{"$nulls":11},"2. If the user wants to include closed projects, enter TRUE"]
[{"$nulls":11},"3. If the user wants to include closed activities enter TRUE"]
[]
["PRJREP","All","N/A","Pre - Immediate","Yes","Replace Posting types PRJI2,PRJI4 with new values. In APP10 this was changed to if taxable PRJI1 and PRJI2(multi company) and if not taxable PRJI3 and PRJI4(multi company)",null,null,"If not run, for new project transactions, there will error recorded in the system","PRE_PRJREP_APP10_UpdateProjectPostingTypes.sql","No","1. Execute this script as IFS Application Owner.","Yes","No","Short"]
["PRJREP","All","N/A","Post - Immediate","No","Regenerate the preliminary revenue postings of project transaction and invoicing plan according to the latest posting setup and cost element setup and tax regime.","Can be run in fallowing scenarios","This will initiate a background job","It will keep existing preliminary postings & planned revenue as it is and not reflecting new posting changes","Post_Prjrep_App10_UpdateProjectRevenuePostings.sql","Yes","1. Execute this script as IFS Application Owner.","Yes","Yes","Long"]
[{"$nulls":6},"If the posting setup is changed manually for PRJI1,PRJ2 and if we need to get the planned revenue through new cost elements.",{"$nulls":4},"2. Enter connection object type PTR or IP. default is both types."]
[{"$nulls":6},"In application 10, the functionality of the tax regime has been changed. As a result of this posting type of the preliminary postings can be changed. If we need to regenerate the postings and fetch the planned revenue according to the tax regime modifications then this need to be executed.",{"$nulls":4},"3. if the user wants to include closed projects, enter TRUE"]
[]
[]
["PURCH","RTM-UPD1","N/A","Pre - Anytime","Yes","Delivery Patterns and Customer Order Route (if ORDER component is installed) will be obsolete from App9-UPD1 onwards and existing records in Delivery Patterns and Customer Order Route will be copied toDelivery Route (which will be newly introduced to the system from App9-UPD1).   ","Only applicable for customers who uses both Delivery Patterns and Customer Order Route","Only applicable if ORDER component is installed.","If user fail to do so Delivery Pattern IDs that are similar to Route IDs in Customer Order Route will not be copied to Delivery Route.","N/A","N/A","1. Appowner or a user who has permission to access the below windows should be logged on to the application.","Yes","Yes","Short","After App9-UPD1, Delivery Route will be used as the delivery pattern and customer order route in respective areas in the application. When we do the copying, we might have delivery pattern IDs that are similar to route IDs in customer order routes. This would create problems when both data ends up in the same location (Delivery Route) after the upgrade. In order to facilitate copying those data to Delivery Route, new patterns will have to be manually created using different IDs. Then only the dissimilar patterns to the customer order routes will be copied to the Delivery Route using an AUTO post script in PURCH module (POST_Purch_CopyDeliveryPatternToDeliveryRoute.sql)."]
[{"$nulls":11},"2. Use below statement in Search, Advanced, SQL of the Procurement Basic Data (ifsapf:frmPurBasic)-> Delivery Patterns (frmDeliveryPattern) tab."]
[{"$nulls":11},"(DELIVERY_PATTERN_ID in (select ROUTE_ID from &AO.CUSTOMER_ORDER_ROUTE))"]
[]
[{"$nulls":11},"Or below query can be used in the database instead."]
[{"$nulls":11},"SELECT  *"]
[{"$nulls":11},"FROM   purch_delivery_pattern_tab "]
[{"$nulls":11},"WHERE  (delivery_pattern_id IN (SELECT route_id FROM customer_order_route_tab));"]
[{"$nulls":11},"3. Users will get records, comprising of Delivery Pattern IDs that are similar to existing Route IDs in the Customer Order Route. Then, users can duplicate the patterns with different IDs and update the delivery pattern in the Supplier for Purchase Part window with the new entry accordingly."]
["RCEIPT","All","N/A","Pre - Immediate and","Yes","The structure of the Dispatch Advice message (DESADV) has been changed in APP10. If the message is already sent before the upgrade but not received yet, such a message will not be possible to receive after the upgrade to APP10.  ","Only applicable if you have Dispatch Advice messages (DESADV) in the queue that are sent but still not received through the Connectivity before the upgrade.","None","Will have to re-send such DESADV messages after the upgrade.","N/A","N/A","1. Check whether there exists any Dispatch Advice messages (DESADV) that has been sent already; but, still not received.","Yes","Yes","Short"]
[null,null,null,"Post - Immediate",{"$nulls":7},"2. Process (Send & Receive) such messages through Connectivity \"before\" the upgrade"]
[{"$nulls":11},"3. Or otherwise, re-send such messages \"after\" the upgrade"]
["SHPMNT","All","N/A","Pre - Immediate preferrably and","Yes","The structure of the Dispatch Advice message (DESADV) has been changed in APP10. If the message is already sent before the upgrade but not received yet, such a message will not be possible to receive after the upgrade to APP10.  ","Only applicable if you have Dispatch Advice messages (DESADV) in the queue that are sent but still not received through the Connectivity before the upgrade.","None","Will have to re-send such DESADV messages after the upgrade.","N/A","N/A","1. Check whether there exists any Dispatch Advice messages (DESADV) that has been sent already; but, still not received.","Yes","Yes","Short"]
[null,null,null,"Post - Immediate",{"$nulls":7},"2. Process (Send & Receive) such messages through Connectivity \"before\" the upgrade"]
[{"$nulls":11},"3. Or otherwise, re-send such messages \"after\" the upgrade"]
["TAXLED","All","All","Pre - Immediate","Yes","Check whether all the tax transactions are fetched before the Upgrade.",null,"None","Inconsistent data in Tax Ledger","N/A","N/A","1. Make sure all the tax transactions are updated to GL","Yes","N/A","Cannot Predict"]
[{"$nulls":11},"2. Run Fetch Tax ledger"]
["TIMREP","All","All","Post-Anytime","No","The script should be used to bulk recalculate Time and Attendance results after change of \"RESULTS IN 10 DEC\" property in System Definitions/Object Properties window.","The script should be used after change of configuration of \"RESULTS IN 10 DEC\" property in System Definitions/Object Properties window. The change of the configuration is not done automatically in any situation (especially it is not done during upgrade). It could be done only manually by end user.","None","The days which are not recalculated will remain with number of decimals as the configuration used before the change and there will be difference between number of decimal places in the results between results created before and after change of the configuration.","POST_Timrep_App10_RecalculateTimeAndAttendance.sql","Yes","1. Decide if script execution is needed.","Yes","No","Cannot Predict"]
[{"$nulls":5},"The change of configuration will affect only results calculated after that change. Previously calculated results need to be recalculated using this script or via IFS Applications with the recalculate option for the required days. ",{"$nulls":5},"2. Enter parameters inside the script. They are descibed in the script."]
[{"$nulls":5},"The script will recalculate the previously entered results except the ones with day status Authorized, Transferred and Manual (Calc Status field in Time Card Day window) and these days need to be corrected manually.",{"$nulls":5},"3. Execute the script as application owner (IFSAPP) via e.g. sqlplus."]
[{"$nulls":11},"4.  Correct manually via IFS Applications results with day status Authorized, Transferred and Manual (Calc Status field in Time Card Day window). They are not corrected by the script.  "]
["TRVEXP","N/A","Yes","Post - Immediate","Yes","In App9 it was possible to modify the \"deductible %\" for the tax code in expense_code_tax_lines_tab in SALES TAX companies, which led to an inconsistency between the \"dedcutible %\" in expense_code_tax_lines_tab and statutory_fee_tab. This script will list such tax codes with different \"deductible %\".",null,"None","Inconsistency between the \"dedcutible %\" in expense_code_tax_lines_tab and statutory_fee_tab.","POST_Trvexp_App10_TaxCodesWithDifferentDeductible.sql","No","1.  Execute the script as application owner (IFSAPP) via e.g. sqlplus.","Yes","No","Cannot Predict"]
[{"$nulls":5},"An Application Consultant should analyze and address all discrepancies reported by the script.",{"$nulls":5},"2.  An Application Consultant should analyze and address all discrepancies reported by the script."]
["WO","All","N/A","Pre - Immediate","Yes","Create and transfer all Css Transactions before upgrading to IFS Applications 10","Only applicable if your company/companies are using IFS Service Management and Cost of Sold Services functionality to carry out a financial analysis on Costs vs. Sales in IFS/General Ledger.","None","During upgrade to IFS Applications 10, only Css Postings that are transferred to finance will be upgraded to the new Task framework. So failing to transfer all Css Postings before the upgrade will result in Css records not been upgraded to the new Task Framework.","N/A","N/A","1. Navigate to Create CSS Postings window.","Yes","No","Cannot Predict"]
[{"$nulls":11},"2. Generate CSS Transactions for all sites."]
[{"$nulls":11},"3. Navigate to Transfer CSS Transactions window."]
[{"$nulls":11},"4. Transfer CSS Transactions to Finance for all sites."]
[{"$nulls":11},"Note: In order to create CSS postings: "]
[{"$nulls":11},"-Vouchers should be created for the relevant work order posting line (Booking Status of the WO posting line = Transferred, and the transaction has a voucher number) "]
[{"$nulls":11},"-The CSS Type of the work order posting line should be Not Posted or Partly Posted. "]
[{"$nulls":11},"-The work order posting line should be transferred to IFS/Customer Order and; "]
[{"$nulls":11},"-The status of the customer order should be Delivered or above OR the status of the work order posting line should be set to Not Invoiceable and the work order completed. "]
[]
[{"$nulls":11},"Once created, the CSS postings can be viewed in CSS Postings Analysis. Next step is to transfer them to IFS/Accounting Rules before further transferring them to IFS/General Ledger."]