|
This window appears when you select Maintain Scenarios from the Scenario Maintenance menu |
Purpose |
This window lists 'scenarios' that already exist. It enables you to define, amend and delete scenarios. These define a combination of style, content, data folder and file name to be used when invoking import or export in Global 3000. For exports, scenarios can also define a program and template folder, and when relevant program parameters. |
Search sequences |
You can press <F6> to change the search sequence. The following search sequences are available: § Startpoint. |
|
§ Scenario code. |
|
§ Scenario description. |
Move through list |
You can move through the list using the cursor and <Page Up> and <Page Down> keys in the standard way. |
Add |
To add a new scenario, move the cursor to the line below the last entry in the list. Alternatively you can press <F5> to insert an entry into the list, or <F4> to go into 'Add' mode. The prompts are described in detail below. |
Note |
To avoid the need for operator input, do not set up more than one scenario for startpoints used for EDI spooler imports. |
Amend |
To amend an existing scenario, move the cursor to the required scenario and press <Return>. The prompts are described in detail below. |
Delete |
To delete an unwanted scenario, move the cursor to the required scenario and press <F7>. You are asked to confirm the deletion. |
The prompts are:
Startpoint |
The process in Global 3000 for which the scenario is to be used. Press <F1> to list the available startpoints. When you enter a valid code, its description is displayed. |
Note |
Generally, the first five characters of the startpoint code are taken from the program code the startpoint is in. When multiple startpoints are available in a single program, a suffix is added to the program code; for example when two startpoints are available, one for imports and the other for exports, the program codes are suffixed with I or E respectively. The first two characters of the program code indicate the module the program is in; for example, DL indicates a Debtors Ledger program, CS indicates a Project Ledger program, ED indicates an EDI program, etc. |
Further information |
For further information on startpoints, see Maintain Contents - Terminology. |
Scenario |
Up to eight characters uniquely identifying the export scenario. |
Description |
Up to 30 characters describing the scenario. |
Contents |
Enter the code of the contents lists for the scenario. Press <F1> to browse contents lists set up for the selected startpoint. When you enter a valid code, its description is displayed. |
Further information |
For further information on contents lists, see Setting Up a Contents List. |
Type |
(Display only.) This can either be import or export and shows whether the startpoint is used for data import or data export. |
Style |
Enter the code of the style for the scenario. Press <F1> for a pop-up enquiry. When you enter a valid code, its description is displayed. |
Further information |
For further information on styles, see Maintain Styles Window. |
Data folder |
Enter the code of the data folder for the scenario. Press <F1> to list data folders which are valid for your operator id Þ Select Data Folder Window. |
|
When you enter a valid code, its description is displayed. |
Further information |
For further information on data folders, see Data Folders and Data Paths - Introduction. |
File name |
For exports to (or imports from) the host system, enter a filename of up to 20 characters identifying the file to (or from) which information is to be transferred. |
|
For Global exports (or imports), enter a file name of up to eight characters identifying the GSM file to (or from) which information is to be transferred. |
Note |
If a file extension is defined in the style, it is automatically displayed and you do not need to enter it. |
Template folder |
(Exports to open system only.) If you want to use a template when you invoke a program in the host system after the export has successfully completed, enter the code of the template folder here. Leave this blank if you do not want to use a template. |
|
Press <F1> to > to list template folders which are valid for your operator id Þ Select Template Folder Window. |
Note |
If you want to use a template, you must also specify the template in the 'Parameters' prompt below. |
Program folder |
(Exports to open system only.) If you want to invoke a program in the host system after the export has successfully completed, enter the code of the program folder here. Leave this blank if you do not want to invoke a program. |
|
Press <F1> to > to list program folders which are valid for your operator id Þ Select Program Folder Window. |
Further information |
For further information on program folders, see Program Folders and Program Paths - Introduction. |
Parameters |
(Only if you entered a program folder above.) If you want to pass parameters to the host system when the specified program is invoked, enter them here; for example you could specify the name of the exported file to be loaded into a spreadsheet, the template to be used, a macro to be run, etc. |
|
You can use the following abbreviations: § %DP. To indicate the data path specified in the Data Path. |
|
§ %FN. To indicate the file name specified at the file name prompt above. |
|
§ %EX. To indicate the file extension defined for the style. |
|
§ %TP. To indicate the path specified in the Template Path. |
Example |
You would enter '%DP%FN%EX %TP\statement.doc' to indicate the file created by the data export process, and a template called 'statement.doc' in the path specified in the Template Path. |
Prompt |
(Y/N.) If you enter Y, you can enter or amend scenario details at the point of import or export. If you enter N, at the point of export you are only prompted for scenario details which are missing or invalid. |
Note |
To avoid the need for operator input, set this prompt to N on scenarios used for EDI spooler exports and imports. |
On completion |
Þ Next line in the window. |
On exit |