Test Scenarios
This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This page may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist.
To test the ERP Connector Solution Starter for Microsoft Office Project Server 2007, you should design test scenarios for each plug-in component to ensure that the plug-in performs correctly. Test scenarios describe the essential behavior of a component. You should perform the tests on a test installation of Project Server to allow you to make modifications to the enterprise resource pool and project data without impacting critical systems.
The scenarios described in this topic use SapHRPlugIn as an example. Before starting tests, do the following:
Install the ERP Connector with SapHRPlugIn and other required components. For information, see Installing the ERP Connector on Project Server.
Initialize and configure the ERP Connector with the necessary lookup tables and custom fields required by SapHRPlugIn. For information, see Configuring the ERP Connector.
If enterprise resources specified in the test files already exist in Project Server, ensure that the resources are not checked out.
A test can include more than one operation, so the final result can differ from the expected result from one test scenario to another. For example, if a resource is activated, it is also updated.
In general, the SapHRPlugIn component performs operations in the following order:
Processing Resources
Activating Resources
Updating Resources
Creating Resources
Deactivating Resources
Processing an Organization Structure
Processing Mapping Information
Processing Resources
To maintain resources in Project Server, SapHRPlugIn must be able to create, update, activate, and deactivate enterprise resources. The tests for each process include three scenarios.
Activating Resources
Scenario 1 SapHRPlugIn determines which resources in the enterprise resource pool are deactivated. If the XML request from mySAP™ ERP Human Capital Management (HCM) includes one or more resources that are in the set of deactivated resources, SapHRPlugIn activates those resources. Following are the requirements for Scenario 1:
The enterprise resource pool contains deactivated resources.
The XML request file includes at least one resource.
SapHRPlugIn is configured to activate resources. The Activate·Resources attribute in the SapHRPlugIn.config file is true (the default value).
Scenario 2 If the resource pool contains no deactivated resources, SapHRPlugIn should not activate any resources. Following are the requirements for Scenario 2:
The enterprise resource pool does not contain deactivated resources.
The XML request file includes at least one resource.
SapHRPlugIn is configured to deactivate resources. The Deactivate·Resources attribute in the SapHRPlugIn.config file is true (the default value).
Scenario 3 SapHRPlugIn should not activate any resources when it is not configured to do so. Following are the requirements for Scenario 3:
The enterprise resource pool contains deactivated resources.
The XML request file includes at least one resource that matches one of the deactivated resources in Project Server.
SapHRPlugIn is configured to not activate resources. The Activate·Resources attribute in the SapHRPlugIn.config file is false.
Updating Resources
Scenario 1 If the enterprise resource pool is empty, SapHRPlugIn should not update any resource. Following are the requirements for Scenario 1:
The enterprise resource pool is empty.
The XML request file includes at least one resource.
Scenario 2 SapHRPlugIn must determine which resources are already contained in the enterprise resource pool. SapHRPlugIn should update each of those resources with data from mySAP ERP HCM. Following are the requirements for Scenario 2:
The enterprise resource pool contains one or more resources.
The XML request file includes at least one resource.
Scenario 3 SapHRPlugIn should not update any resource when the XML request file does not include any resources. Following are the requirements for Scenario 3:
The enterprise resource pool either contains or does not contain resources.
The XML request file does not include any resources.
Creating Resources
Scenario 1 SapHRPlugIn should create exactly the same number of resources as the XML request file includes, except where the data is incorrect. SapHRPlugIn must log an error message for each resource that contains data that is not valid. Following are the requirements for Scenario 1:
The enterprise resource pool is empty.
The XML request file includes at least one resource.
Scenario 2 SapHRPlugIn should determine which resources are already included in the enterprise resource pool. If the XML request file includes a resource that is not part of the resource pool, SapHRPlugIn must create it. SapHRPlugIn must log an error message for each resource that contains data that is not valid. Following are the requirements for Scenario 2:
The enterprise resource pool contains one or more resources.
The XML request file includes at least one resource.
Scenario 3 SapHRPlugIn should not create a resource when the XML request file does not include a resource. Following are the requirements for Scenario 3:
The enterprise resource pool either contains or does not contain resources.
The XML request file does not include any resources.
Deactivating Resources
Scenario 1 If the XML request file does not contain any resources, SapHRPlugIn should determine which resources in the enterprise resource pool have the SAP Resource ID resource enterprise custom field, and then deactivate all of those resources. When the process is complete, there should be no active resources with an SAP Resource ID custom field remaining.
.gif "Note") Note |
|---|
When resources that contain an SAP Resource ID are deactivated, they still contain the SAP Resource ID. |
Following are the requirements for Scenario 1:
The enterprise resource pool contains one or more resources.
The XML request file does not includes any resources.
SapHRPlugIn is configured to deactivate resources. The Deactivate·Resources attribute in the SapHRPlugIn.config file is true.
Scenario 2 If the XML request file contains resources, SapHRPlugIn should determine which resources in the enterprise resource pool have an SAP Resource ID custom field, and then deactivate those resources that the XML request file does not include. Following are the requirements for Scenario 2:
The enterprise resource pool contains one or more resources.
The XML request file includes one or more resources.
SapHRPlugIn is configured to deactivate resources. The Deactivate·Resources attribute in the SapHRPlugIn.config file is true.
Scenario 3 If SapHRPlugIn is configured so that it does not deactivate resources, it should not deactivate resources in the enterprise resource pool. Following are the requirements for Scenario 3:
The enterprise resource pool either contains or does not contain resources.
The XML request file does not include any resources.
SapHRPlugIn is configured to not deactivate resources. The Deactivate·Resources attribute in the SapHRPlugIn.config file is false.
Processing an Organization Structure
If the SapHRPlugIn component receives an organization structure, it creates or updates the lookup table structure for the specified enterprise custom field in Project Server. SapHRPlugIn always overwrites the organization structure in Project Server with the current organization structure of the mySAP ERP HCM system. SapHRPlugIn does not support incremental updates of the organization structure.
Scenario 1 SapHRPlugIn updates the lookup table structure for the specified organization structure custom field in Project Server. The organization structure change causes all resources in the enterprise resource pool that have an SAP Resource ID custom field to lose any mapping to the organization structure. Following are the requirements for Scenario 1:
The enterprise resource pool contains one or more resources.
The XML request file includes an organization structure.
Scenario 2 SapHRPlugIn creates a new lookup table structure for the specified enterprise custom field in Project Server. Following are the requirements for Scenario 2:
The enterprise resource pool is empty.
The XML request file includes an organization structure.
Scenario 3 SapHRPlugIn does not change the lookup table structure of the specified enterprise custom field in Project Server when it does not receive any information about an organization structure. Following are the requirements for Scenario 3:
The enterprise resource pool either contains or does not contain resources.
The XML request file does not include an organization structure.
Processing Mapping Information
If the SapHRPlugIn component receives resource mapping information, it applies the mapping data to resources in the enterprise resource pool that have an SAP Resource ID custom field.
Scenario 1 When it receives resource mapping information, SapHRPlugIn should determine which of the mapped resources are in the enterprise resource pool and also have an SAP Resource ID custom field. SapHRPlugIn should then update the mapping information for all of those resources. Following are the requirements for Scenario 1:
The enterprise resource pool contains one or more resources.
The XML request file includes resource mapping information.
Scenario 2 If the XML request file does not include resource mapping information, SapHRPlugIn should not change any resource mapping information. Following are the requirements for Scenario 2:
The enterprise resource pool contains one or more resources.
The XML request file does not include resource mapping information.
Scenario 3 SapHRPlugIn does not apply mapping to resources in the enterprise resource pool if they have no SAP Resource ID custom field. Following are the requirements for Scenario 3:
The enterprise resource pool contains no resources with an SAP Resource ID custom field.
The XML request file includes resource mapping information.