How to Use the Custom Report Maintenance Feature

Contents of this Topic: ShowHide

Using the Custom Report Maintenance Interface

Importing a Custom Report from the Custom Reports Database into the SEOM Program File on the Current Workstation

1. Click the [Reports] radio button.

2. For the purpose of illustrating this process, the [All] radio button is selected in the left-hand section of the screen synonymous with the Microsoft Access Form object or graphical user interface (GUI). Notice that there is no report named Custom Credit Slip in the list box on the left-hand side of the screen, as shown below:

3. Click on the name of that report in the list box on the right-hand section of the screen to select to "left-click" the mouse on an object, usually a row in a table, in the context of Monsoon OMS documentation it.

4. Click [Import] and the report will now appear in the list box on the left-hand section of the screen (Reports available in your copy of SEOM).

If there had already been a report with the name Custom Credit Slip in the program file The MS Access database that contains the Monsoon OMS application code. This database does not contain the user's order information, which is housed in the Store Data File. The program file name begins with SEOrdMan* and has the extension of .mdb. (left-hand list box), the program would prompt the user as to whether it should rename or replace the file before proceeding with the import. That dialog is described in more detail in the following sections.   

Exporting a Custom Report from a SEOM Program File to the Custom Reports Database (Custom Report.mdb)

Adding a non-standard or modified report to the Custom Reports database is the opposite of the process that was described in the previous example. Let's assume that we have made a change to the Custom Credit Slip report that was just imported into the program file of the current workstation. In order for all of the other workstations in the configuration to use the updated report, it needs to be exported to the Custom Reports database. Once that has been done, the report can be imported from the Custom Reports database into the program file on each workstation, as described in the previous example. Now let's review the process to export a report from a program file to the Custom Reports database:

1. Select the report to be exported from the list in the left-hand section of the screen. For this example we will use the report, Custom Credit Slip.

2. Click the [Export] button and if a report by that name does not exist, the report will be immediately copied to the Custom Reports database and will be displayed in the list box on the right-hand side of the screen. If, however,  there is already a report in the Custom Reports database with the same name, the program will prompt the user how it should proceed:

1. • Yes - Rename the report that is already in the Custom Reports database by appending "Backup x" to the end of the name; where x is a numeral that indicates the number of times the same report has been exported using this option one of the possible attributes of a product; for example, blue is an option for the color attribute of a product.  

   • No - Replace the report that is in the Custom Reports database with the copy that is coming from the program file; the name of the report will remain the same and no backup copy will be made by the program

   • Cancel - abandon the action of copying the report to the Custom Reports database

3. Click the action button of choice. For this example we will select Yes, to demonstrate the naming convention used by the program:

4. Notice that Custom Credit Slip Backup 1 has been added to the list box on the right hand side of the screen and there is also a report with the original name, Custom Credit Slip. The former is the report as it previously existed in the Custom Reports database prior to the export function and the latter is the report in the form as it came from the program file of the current workstation. Be sure that the report is exported to the Custom Reports database from the workstation that was used to make the changes to the report.

5. If other workstations should begin using this updated copy of the report, refer back to the previous section that describes how to import a custom report and repeat those steps on each workstation.

Deleting a Report through the Custom Report Maintenance Feature

1. Select the report to be deleted in the appropriate side of the screen:

1. • Left-hand side of the screen represents the reports that are in the program file of the current workstation

   • Right-hand side of the screen represent the reports that are in the Custom Reports database

2. Click the [Delete] button associated with the location of the given report (left or right hand side of the screen).

3. The program will prompt the user for confirmation before deleting the report.

Renaming a Report through the Custom Report Maintenance Feature

1. Select the report to be renamed in the appropriate side of the screen:

1. • Left-hand side of the screen represents the reports that are in the program file of the current workstation

   • Right-hand side of the screen represent the reports that are in the Custom Reports database

2. Click the [Rename] button associated with the location of the given report.

3. The program will open a dialog box where the user can change the name of the report. Click [OK] to make the change or [Cancel] to abandon making the change.

Re-importing a Report through the Custom Report Maintenance Feature

Using the Re-Import button on the left-hand side of the screen basically accomplishes the same thing that the Import button on the right-hand side of the screen does. A copy of the selected report will be pulled from the Custom Reports database and placed it in the program file of the current workstation.

1. Select the report to be re-imported in the left-hand side of the screen.

2. The program will prompt the user how to proceed:

1. • Yes - Rename the report that is already in the program file by appending "Backup x" to the end of the name; where x is a numeral that indicates the number of times the same report has been exported using this option.  

   • No - Replace the report that is in the program file with the copy that is coming from the Custom Reports database; the name of the report will remain the same and no backup copy will be made by the program

   • Cancel - abandon the action of copying the report to the program file

3. To demonstrate the naming convention that the program will use, we will choose option [Yes].

4. The program will append "Backup x" to the name of the report, where "x" is a numeral that indicates the number of times that a report of this name has been re-imported. A message box will display the new name of the original report:

5. Notice that both the original report name, Custom Credit Slip Backup1 is still listed, and there is now a report by the name of Custom Credit Slip Backup 1 Backup 1. The former is the report that was just copied from the Custom Reports database and the latter is the report as it existed in the program file prior to the Re-Import process.

6. Click [OK] to end the dialog.

Import a Custom Report from an External Source (Browse button)

If the user has contracted a third party to create a custom report (and/or other components), chances are that they will distribute those objects to the user in an "external" file or database. "External" is defined as a file that did not come as part of the SEOM application.

In order for SEOM to access those components, they must be imported into the Custom Reports database or the program file. The Custom Report Maintenance screen provides the means to accomplish that goal.

This example refers to importing reports, but the same instructions apply to importing other object types, such as tables, queries, or modules. To import those other object types, select the appropriate radio button at the very top of the screen before beginning the following process:

1. Click the [Browse] button and navigate to the location of the external file that contains the custom components and open it.

2. The contents of the external file will then be displayed in the list box on the right-hand side of the screen, according to the object type that is selected at the very top of the screen (Reports, Tables, Queries, Modules or Forms user interface through which users are able to interact with the program. The terms "form" and "screen" are used interchangeably throughout the documentation.).

3. At that time, two other action buttons will become visible at the bottom of the right-hand list box:

   • Copy to Cust. Reports

   • Reopen Cust Rept mdb

4. Do one or both of the following:

   1. Select a component from the list in the right-hand window and click [Import] to copy the component directly to the program file on the current workstation.

   2. Select a component from the list in the right-hand window and click [Copy to Cust. Reports] to copy the component directly to the custom reports database

5. Click [Reopen Cust Rept mdb] when all desired custom components have been retrieved from the external file. The list box in the right-hand side of the screen will once again reflect the contents of the Custom Reports database.  

6. To propagate the newly imported custom components to other workstations in the configuration, refer to the instructions earlier in this article that describe the process of importing a custom report. Repeat those directions for each component type on all workstations.

Additional Information

Created: 5/2/12

Revised:

Published: 04/13/16