Part IV: Post-Installation
Chapter 12: Log in the First Time
Use the following steps to verify and test your Epicor 9.05 application upgrades the first time you log in.
Note If you are a new customer, you only complete the Set Up System Agent for Printing steps. All other
steps can be ignored.
12.1 Import Posting (Booking) Rules for Extended Rules
Use these steps to import your posting rules if you use Extended Rules. If you only use standard rules, this step has already been automatically completed for you when you converted your data.
1. Open the Epicor 9.05 application.
2. Select Financial Management > General Ledger >Setup > GL Transaction Type. 3. From the Actions menu, select Import ACT Type.
4. Click the Input File Name button. Navigate to the Extended posting rules folder. For example, go to the
following:
• Extended rules: \\<servername>\Epicor905\server\PostingRules\Extended
5. Select one or more .XML files. You can select multiple files by pressing the Shift key while you highlight
the files. Click Open to select the highlighted files.
6. Select the Import All check box to specify that you want to import all the selected XML files. To specify
individual XML files instead, you can select the Selected check box for each file.
7. If this is not the first time you are importing posting rule files, you can select the Replace All check box to
replace your existing revision with the same name. To specify to replace individual XML files instead, you can select the Replace Existing check box for each file.
8. Select the Change All Revision Statuses To Active check box if you want to change the revision from a
draft to active for all transaction types being imported. To specify to activate individual XML files instead, you can select the Activate check box for each file.
9. Select the Import into all companies check box if you want to import the posting rules into each company. Note Newly created revisions are automatically set to Active in the current company only. In other
companies, you need to update the status manually. In order to make changes, your User Id must have access to the company.
10. Click OK to begin the import.
11. You may be prompted with the Book Mapping dialog. Select the book identifier you previously defined
from the Map Book selection list. If you want to map the selected book identifier to all transaction types, select the Use for all transaction types check box. Click OK.
Note To copy the rules from one book to another, you can use GL Transaction Type Maintenance.
You create a revision, and then copy both the header and detail rules one at a time into a new book. Then activate the revision.
12.2 Review Blocked Standard Posting Rules (if any)
Use the following steps to review any standard posting rules that were not updated during the conversion. If you were not prompted with an Information message during the conversion, you can skip this step.
1. Get the screen capture of the Information message that you took during the conversion process. 2. Select Financial Management > General Ledger > Setup > GL Transaction Type.
3. Search and select a transaction type that is listed on the Information message.
4. In the Tree View area, select a revision. From the Actions menu, select Change Log Menu. Review the list
of revisions that were added and blocked during the last conversion process.
5. If a Revision you want is listed as Blocked, you can change it to Active. To do this:
a. Click on the Revision to select it.
b. From the Status drop-down list, select Active. c. Click Save from the standard toolbar.
6. Repeat the above step for each Revision listed on the Information message.
Note If you have multiple companies, the Information message may list the same blocked transaction
type for each company. You must review the blocked posting rules for each company where you have access.
12.3 Set Up System Agent for Printing (First Time Login)
Use the following steps to set up the System Agent for your system to enable printing.
1. Review the paths you specified during the server software installation for the following locations:
• Destination Location
• Print Folder Destination Location • Server Share Location
2. Launch your Epicor 9.05 application.
3. Navigate to System Management > Utilities > System Agent. 4. Click Agent ID to search for the system agent identifier.
5. The identifiers are listed. Select SystemTaskAgent. Click OK.
Examples Description
Directory
c:\Program Files\Epicor
Software\EpicorData/usr/epicor/epicordata specifies the local path on the server to
the print directory Server File
\\<servername>\EpicorData specifies the unc path to the print
directory Client File
\\<servername>\Epicor905\Server specifies the unc path to the server
directory Client Program
12.4 Maintain Your Customizations and Personalizations
Use the following steps to verify and maintain your customizations and personalizations. Note that the Customization / Personalization Maintenance program attempts to automatically correct any problems that it encounters during the verification process.
The verification process checks that each customization includes the following: a valid customization script, valid custom properties, valid control keys, valid controls that are located on the form and properly docked, and user-defined controls are added to the form. It also deletes customization properties that are no longer applied, and cleans up the grid layout to remove obsolete fields.
1. Launch your Epicor 9.05 application.
2. Navigate to System Management > Utilities > Customization Maintenance. 3. Click the Search icon (binoculars) from the tool bar.
4. Select Customization as the Type and All as the Status.
5. Click Search. The customizations are displayed. Click Select All and then click OK to select all. 6. Click on the Actions menu.
7. Select the Verify All command.
8. You are warned that this process may take several minutes. Click Yes.
9. The verification process reviews the selected personalizations and customizations. When complete, you are
returned to the Customization/Personalization Maintenance window.
10. Select a customization/personalization you want to review.
11. Click the Warnings tab to review any elements that were not validated. Usually warnings are caused by
properties stored in the customization data that cannot be applied. Common warnings that you might see include:
a. Cannot locate control on form. The key used for the customization is no longer on the form. This could result from a renamed control or changed EpiGuid.
b. Could not set the property. No code exists that sets this property. c. EpiBinding is not valid. Identifies the database field that should be used. d. Invalid Parent Type. Custom control was added to an invalid parent.
12. Use the Run, Modify, and Show Custom Data features from the Actions menu to correct the warnings. 13. After fixing a warning, select the row and click Remove Selected Item.
14. Click the Errors tab to review error messages generated by the selected program. Usually errors are caused
by problems with the customization script.
15. Use the Run, Modify, and Show Custom Data features from the Actions menu to correct the errors. 16. After fixing the errors, from the Actions menus, select Verify Customization.
17. Click the Detail tab to verify that the customization has passed validation. If it is valid, the current
manufacturing version is Valid For and Pass is the Status.
18. Repeat these instructions and select Personalization as the Type to verify and maintain your personalizations,
if necessary.
12.5 Test Business Activity Query (BAQ) Calculations
During the Epicor 9.05 installation, unused obsolete fields are automatically deleted. Obsolete fields that are used in calculations within BAQ are not deleted, but calculations with obsolete fields no longer work.
1. Review your calculations within any BAQs you want to continue using after upgrading your system. 2. Launch the online help system.
3. Review the Schema Change topic to see which fields have been changed or removed. 4. Change each BAQ calculation so that it uses current fields.
After you upgrade, your BAQ reports should work since your fields are valid.
12.6 Test Business Activity Manager (BAM) Upgrades
If you use any global alerts that activate procedure (.p) programs, use these steps to compile these programs using the newly installed Progress 10.2A.
1. Review each BAM event that has a procedure program on your system. Verify that it still has a valid business
reason for being upgraded to the next version.
2. Add Comments within your procedure program, explaining your changes. 3. Save each BAM event, including the procedure files, in an archive location. 4. Move these BAM events and their procedure files to a new location.
5. If any Epicor 9.05 schema changes affect the procedure program, update the .p program to reflect the new
schema.
6. Compile each procedure program using Progress 10.2A. 7. Test each procedure program for issues.
12.7 Update and Test Business Process Management (BPM) Directives
Use these instructions to update your outdated BPM directives after upgrading and to identify any that need special attention due to schema changes or other factors.
Note You must use these steps to properly upgrade your BPM directives. You can not just copy the BPM
directives in the Epicor905\BPM\bo directory to another directory. You also cannot keep the BPM directives in the current folder, they must be properly upgraded to a new location.
1. Navigate to System Management > Business Process Management > General Operations > Directive Update.
2. From the Actions menu, select Recompile All Outdated Directives. As the directives are converted and
re-compiled, an hour glass is displayed.
3. Upon completion, the compile results are displayed. Any Method Directives that failed to compile after the
conversion are listed.
4. Navigate to System Management > Business Process Management > Setup > Method Search. 5. Use the Method Directives program to search for any Outdated Directives.
6. Open an outdated directive.
7. Click on the Actions menu and select Validate Method.
8. If a directive is outdated, the Pre-Processing, Base Processing and/or Post Processing sheets display the
Outdated icon on each directive's Detail sheet. Research how to update each outdated directive to make it compatible with Epicor 9.05. This may involve updating your custom 4GL code to reflect the new schema.
9. Repeat these steps for all the outdated directives that you find.
12.8 Test Custom Code Programs
Use these steps to test any custom code programs that were created and updated for you by the Epicor Custom Solutions Group.
1. Test your custom code programs.
2. Contact the Epicor Custom Solutions Group if you need other custom code upgraded. Note that the Epicor
Custom Solutions Group requires time to review, estimate, schedule, and complete the custom solution for you.
12.9 Test System and Repeat Installation
Based on your installation process, you are at one of the following points:
• If you completed the Epicor 9.05 installation in a test environment, you are now ready to test the installed Epicor 9.05 application in that environment. After your testing is complete, you must repeat the entire installation in your production environment.
• If you completed the Epicor 9.05 installation in your production environment, you are now ready to use the installed Epicor 9.05 application in that environment.