Templates H

Description

Displays the template name. A template is a way to manage data in the form of a particular process, for example, to create a new BOM or to change a material.

Displays target ERP system transaction used in the template recording. A transaction code is not needed if creating a custom template (i.e., if the Type is set to Custom Setup).

Displays the posting type for the template.

Values are:

• BDC Script – The  template is based on the results of a Batch Data Communication (BDC) script recorded in dspCompose
• GUI Script – The template is based on the results of a GUI script recorded using the SAP Logon pad
• Custom Setup – The template is custom and is not created using a recording

If enabled, the template is active. A template must be active to use for requests.

Click to activate or deactivate the template. A template can be activated if:

• It has not been generated.
• Each role assigned to the template is not dependent on another role assigned to the template, or does not have a dependency on another role assigned to the template.

A template cannot be deactivated if active requests exist for the template. A request is considered Active when it is in an active request status.

Click to open the Request page to add, edit and process requests based on the template. This icon is only active if requests that use this template exist.

Click to open the Template (Role) page to add, edit and delete roles assigned to the template.

NOTE: The count on this icon indicates the number of roles assigned to the template. Global roles with the Auto Copy option set on the Roles page are automatically added to a template when it is created. Refer to Add a Global Role for more information.

Click to open the Template (Org Units) page to add, edit and delete Org Units assigned to the template. Org units are optional for templates.

NOTE: The count on this icon indicates the number of Org Units assigned to the template. Refer to Add Org Units to a Template for more information.

Click to open theTemplate (Users)page to add, edit or delete users who have been granted access to the template. The user who created the template is automatically assigned to the template and to all the roles.

NOTE: The count on this icon indicates the number of users granted access to the template. The user who created the template is automatically assigned to the template and to all the template’s roles.

Click to open the Template (External Request Scenario) page to add, edit and delete external request scenarios, including external request scenarios that create Excel-initiated requests.

NOTE: The number on the icon represents the number of external request scenarios that exist for the template.

Click to open the Template (ISA External Request Scenario) page to add, edit or delete an external request scenario that uses data from an ISA report as the basis for a request.

NOTE: This icon does not display if the ISA is not installed and licensed.

Description

Click to activate or deactivate the template. A template can beactivated if:

• It has not been generated.
• Each role assigned to the template is not dependent on another role assigned to the template, or does not have a dependency on another role assigned to the template.

A template cannot be deactivated if active requests exist for the template. A request is considered Active when it is in an >active request status.

Click to open the Request page to add, edit and process requests based on the template. This icon is only active if requests that use this template exist.

Details

Displays the template name. A template is a way to manage data in the form of a particular process, for example, to create a new BOM or to change a material.

Displays target ERP system transaction used in the template recording. A transaction code is not needed if creating a custom template (i.e., if the Type is set to Custom Setup).

Displays the posting type for the template.

Values are:

• BDC Script – The  template is based on the results of a Batch Data Communication (BDC) script recorded in dspCompose
• GUI Script – The template is based on the results of a GUI script recorded using the SAP Logon pad
• Custom Setup – The template is custom and is not created using a recording

Connection

Displays the connection to the target system that was set for the user credentials for this template.

The connection is set on the User Credentials page.

Refer to Establish a Connection to a Target System for more information.

NOTE: If a user adds a request based on this template and does not select a connection ID, the default connection assigned to the Integrate Template is used for the request.

Click to open the User Credentials page to add Login credentials for the current user to track that user’s updates posted to the target system related to requests based on this template.

If enabled, the user name and password have been detected based on the user credentials setting.

If disabled, the credentials have not been detected and must be added for the request to post successfully.

Setup

Displays target ERP system used to record the template. If importing a template from Integrate, set the Type to match the posting type of the template. A Connection must be selected when creating a custom template (i.e., when the Type is set to Custom Setup); however, it does not apply to the template and is ignored.

Click to open theTemplate (Role) page to add, edit and delete roles assigned to the template.

NOTE: The count on this icon indicates the number of roles assigned to the template. Global roles with the Auto Copy option set on the Roles page are automatically added to a template when it is created. Refer to Add a Global Role for more information.

Click to open the Template (Org Units) page to add, edit and delete Org Units assigned to the template. Org units are optional for templates.

NOTE: The count on this icon indicates the number of Org Units assigned to the template. Refer to Add Org Units to a Template for more information.

Click to open the Template (Users) page to add, edit or delete users who have been granted access to the template. The user who created the template is automatically assigned to the template and to all the roles.

NOTE: The count on this icon indicates the number of users granted access to the template. The user who created the template is automatically assigned to the template and to all the template’s roles.

Actions

Click to launch the local target ERP system environment where script recording for the template occurs. The Record icon is only available if creating a GUI Script or a BDC Script template. When the Record icon is clicked, if an Integrate Template ID is set, dspCompose™ overrides the Template ID with the recording. Because this Integrate template may also be used in Integrate, take special care when re-recording (and thus modifying) a template that has been imported from Integrate.

NOTE: This option does not display if the template is active.

Click to generate the template when a template recording is complete. dspCompose™ imports the recording for the template into Integrate for posting and creates all the necessary data entry pages in dspCompose™. A template cannot be activated until it is generated. The Record icon is only available if creating a GUI Script or a BDC Script template.

NOTE: This option does not display if the template is active.

Click to generate the custom template. This icon only displays if creating a custom template (i.e., when the Type is set to Custom Setup).

Description

Template Settings

Displays name of team to which the template is assigned.

Click to open theTemplate (Post Message Tables)page to add, edit and delete tables that store posting feedback.

Click to open the Template (Request Retention) page to edit how long a request with a specific status is retained before it is archived.

Click to open theTemplate (Objects) page to add, edit and delete tables, stored procedures and views that are automatically created in the cMass_Data database when a template is generated.

Click to open the Template (Events) page to configure events that trigger rules to run for the template.

External Request Creation

Click to open the Template (External Request Scenario) page to add, edit and delete external request scenarios, including external request scenarios that create Excel-initiated requests.

NOTE: The number on the icon represents the number of external request scenarios that exist for the template.

Posting

This field is not used.

Displays name of Integrate template used as the dspCompose™ template recording.

Displays the ID for the process generated by Integrate and used to post request data to the target ERP system. Click the link to view the Process in Integrate.

Displays name of GUI or BDC script (i.e., recording) used in the template.

Description

Validation

If enabled, dspCompose™ validates the values entered on the data entry pages of the request that have a list or a combo box. When the user clicks the Validate button on theRequest (Roles)page, dspCompose™ ensures that the values that have been entered or selected on the data entry pages are contained in the list boxes assigned to the data entry pages. Records that fail this validation fail with a severity of Error. The default for this setting is set on theParameterspage.

If enabled, dspCompose™ validates that all required fields on data entry pages of the request contain values. Records with blank required fields fail with a severity of Error. dspCompose™ runs the validation when the user clicks the Validate button on the Request (Roles) page. The default for this setting is set on the Parameters page.

If enabled, dspCompose™ validates that the values selected on data entry pages of the request for a check box are the values in the table corresponding to the proper check box format set on the column property. Records that fail this validation fail with a severity of Error. dspCompose™ runs the validation when the user clicks the Validate button on the Request (Roles) page. The default for this setting is set on the Parameters page.

If enabled, dspCompose™ rejects data entry records that fail a validation whose severity meets or exceeds the Force Reject Severity. These records cannot be approved by the Review role and are automatically rejected and sent back to the Data role for correction.  If no Force Reject Severity is set, all data entry records can be rejected or approved by Review role users. The default for this setting is set on the Parameters page.

Displays value that represents actions that may be performed on Org Unit Values when a request is created. Values are:

• OrgUnit Values Available For Assignment – All of the individual Org Unit values possible for the request are available for assignment to the request, but no assignments are assigned by default.
• User Assignments, Defaulted Change Allowed – All of the individual Org Unit assignments available to the user creating the request are assigned to the request by default, but may be unassigned.
• User Assignments Defaulted, No Change Allowed – All of the individual Org Unit assignments available to the user are assigned to the request and cannot be unassigned. If this option is selected, the Select All, Unselect All, and Reset Defaults button do not display on the Request (Org Unit Assignments) page.

The default value is configured on theParameterspage.

If enabled, Org Unit values presented at the request level are based on the requester’s Org Unit assignments. If disabled, Org Unit values presented at the request level are based on all users’ Org Unit assignments from users assigned to the template.

Archive Settings

Displays data source that contains the Template Archive Page ID.

Displays page ID automatically set for a template when the template is processed and when roles are configured. If non-custom review roles are used, the Template Archive Page ID is set to the system-generated page.

Click to open theTemplate (Archive Settings)page to add, edit and delete custom archive tables. When a request is archived, the data is selected out of the active table(s) and written to the archive table(s). Data is only inserted into the custom archive tables; deletes and updates are not performed.

Maintenance

Click to update all system-generated objects based on changes made to the data entry page for the template.

NOTE: This icon is only available while in Developer Mode.

NOTE: This icon does not display for custom templates (i.e., when the Type is set to Custom Setup).

Reset

Click to reset the status to Procedure Completed. This icon is only active while in Developer Mode.

Developer

If enabled, a user can make changes to an active template with active requests. If disabled, no changes can be made to an active template with active requests.

Click to delete all requests that currently use this template so that the template can be deleted. In order to delete a template, all requests for the template must first be deleted.