Acceptance Test
The acceptance test for an ERP Connector module for Microsoft Office Project Server 2003 involves preparing XML files with sample mySAP™ ERP HCM input data for the various test scenarios, running the tests, and analyzing the results. The final test should use live data from mySAP ERP. This topic describes the processes and results of the recommended tests for the human resources (HR) module.
Preparing XML Files for the Test Scenarios
To test scenarios for the HR module, you need to prepare files to use with the Service for Enterprise Data Maintenance (EDM). To help describe the tests, the sample test file names include the following:
- R, which stands for resources.
- S, which stands for organization structure.
- M, which stands for mapping information.
- Number, which indicates how many sets of data the file includes.
The ERP Connector download includes the following sample XML files for the HR module tests:
- 0R_0M_0S.xml Contains empty data elements for resources, organization structure, and mapping information.
- 10R_0M_0S.xml Contains ten new resources.
- 10R_0M_0S_modified.xml Contains the same resources as 10R_0M_0S.xml, but with modified resource information. The mySAP ERP HCM ID is the same as in 10R_0M_0S.xml.
- 5R_0M_0S.xml Contains five new resources.
- 0R_0M_1S.xml Contains an organziation structure.
- 0R_0M_1S_modified.xml Contains a modified organziation structure.
- 0R_10M_0S.xml Contains mapping information for the ten resources in the 10R_0M_0S.xml file, and the organization structures of the 0R_0M_1S.xml and 0R_0M_1S_modified.xml files.
- 10R_10M_1S.xml Contains related and consistent data for ten resources, mapping data for those resources, and one organization structure.
Recommended Tests
The tests recommended for the HR module include a series of resource, organizational structure, and mapping tests using test files and live data.
Resource Tests
Do the following steps to prepare for the tests, and then do the tests in Table 1 in order. Check the intermediate results of each test before proceeding to the next test. Te see the results, you can use Microsoft Office Project Professional 2003 to open the Enterprise Resource Pool and view the custom fields for a resource. For information about the Windows event log, see Using the Event Viewer and Log Files.
- In the HR Module section of the administration page, select Deactivate Resources with mySAP ERP HCM ID.
- Select Activate Resources in Resource Pool.
- Click Write config.
- Use Microsoft Office Project Web Access to delete all resources with an mySAP ERP HCM ID.
Table 1. Resource tests
| Test | Action | Intermediate results |
|---|---|---|
| 1 | Drop the file 0R_0M_0S.xml. | No resources should be created, because there was no resource information. No resources should be deactivated, because there weren't any resources with an mySAP ERP HCM ID in the resource pool. |
| 2 | Drop the file 10R_0M_0S.xml. | Creation: There should be ten new resources in the resource pool. Deactivation: No resource should be deactivated, because there are no resources to deactivate. |
| 3 | Drop the file 5R_0M_0S.xml. | Creation: There should be 5 resources in the resource pool. Deactivation: Ten resources should be deactivated. |
| 4 | Drop 10R_0M_0S.xml again. | There should be five deactivated resources. There should be ten resources activated in the resource pool. |
| 5 | Drop the file 10R_0M_0S_modified.xml | There should be five deactivated resources. There should be ten resources with updated information. |
| 6 | Drop 0R_0M_0S.xml again | There should be fifteen deactivated resources. There should be no resources with an mySAP ERP HCM ID in the resource pool. |
Organization Structure Tests
Do the following steps to prepare for the tests, and then do the tests in Table 2 in order. Check the intermediate results of each test before proceeding to the next test.
- Delete structure information for the enterprise outline code field that you are using for organization structure.
- Use Project Web Access to delete all resources with an mySAP ERP HCM ID.
Table 2. Organization structure tests
| Test | Action | Intermediate results |
|---|---|---|
| 1 | Drop the file 0R_0M_1S.xml. | There should be no resources with an mySAP ERP HCM ID in the resource pool. The outline code field for the organization unit should now contain the structure of the organization. |
| 2 | Drop the file 0R_0M_1S_modified.xml. | There should be no resources with an mySAP ERP HCM ID in the resource pool. The outline code field for the organization unit should now contain the modified structure of the organization. |
| 3 | Drop the file 0R_0M_0S.xml. | There should be no resources with an mySAP ERP HCM ID in the resource pool. The field for the organization unit should still contain the modified organization structure, because the HR module does not delete organization information. |
Resource Mapping Tests
Do the following steps to prepare for the tests, and then do the tests in Table 3 in order. Check the intermediate results of each test before proceeding to the next test.
- In the HR Module section of the administration page, clear Deactivate Resources with mySAP ERP HCM ID, and then click Write config.
- Delete structure information in the enterprise outline code that you are using for organization structure.
- Use Project Web Access to delete all resources with an mySAP ERP HCM ID.
Table 3. Resource mapping tests
| Test | Action | Intermediate results |
|---|---|---|
| 1 | Drop the file 10R_0M_0S.xml. Drop the file 0R_0M_1S.xml. Drop the file 0R_10M_0S.xml. |
Creates the resources for the mapping tests. Creates the organization structure. Applies the resource mapping. There should be ten resources in the resource pool with an mySAP ERP HCM ID. The organization structure should be represented in the enterprise outline code. The ten resources should be mapped to a specific organization unit, and the custom text field for the IsManager flag should be filled. |
| 2 | Drop the file 0R_0M_1S_modified.xml. | There should be no resources with an mySAP ERP HCM ID in the resource pool. There should be a new organization structure in the enterprise outline code. None of the resources should be mapped to an organization unit, because the organization structure values have changed. |
| 3 | Drop 0R_10M_0S.xml again to restore the mapping. | There should be ten resources in the resource pool with an mySAP ERP HCM ID. The organization structure should be represented in the enterprise outline code field. The ten resources should be mapped to an organization unit again. |
Test with Live Data
Do the following steps to prepare for the test with live data. Check the results after mySAP ERP HCM saves an XML file to the drop folder for the Service for EDM on the Project Server computer.
- In the HR Module section of the administration page, select Deactivate Resources with mySAP ERP HCM ID.
- Select Activate Resources in Resource Pool.
- Click Write config.
- Use Project Web Access to delete all resources with an mySAP ERP HCM ID.
- Log on to mySAP ERP HCM.
- In mySAP ERP HCM, execute the export service for human resource data. Configure the service to drop the file in the correct drop folder for your test.
Note It is easier to check the test case success if the resource pool is empty. However, it is not necessary to delete the resources from the Project Server resource pool. You can also vary the administration page settings for activation and deactivation.
Following are the expected results of the live data test:
- The Project Server resource pool should now contain resources from mySAP ERP HCM. Compare the resource pool with the mySAP ERP HCM input data.
- The mySAP ERP HCM organization structure should be represented in the Project Server enterprise outline code.
- The resources with an mySAP ERP HCM ID should be mapped to the correct organization unit, and the custom text field for the IsManager flag should be correctly filled.
- Every resource or mapping that is not part of the Project Server resource pool should be compared with the log file. The log file should include an error that describes why the processing did not work for that resource.
Using the Event Viewer and Log Files
You can set the path for the HR module of ERP Connector log files in the administration page, and you can also set the log level for all ERP Connector modules and the Windows event log name for the Finance Projects and WBS modules. For information on how to set the log file path, log level, and log names, see Using the Administration Page.
To use the Windows event log on the Project Server computer, on the Windows Start menu, click Administrative Tools, and then click Event Viewer. The HR module of ERP Connector logs events in the SAPHRIMPORT node (Figure 1).
.gif)
Figure 1. Windows events from the HR module
In addition to events in the Windows event log, the HR module also saves information in the log files stored in the directory you set in the administration page. For example, if you specify the XML Log Path in the administration page as C:\SAP\Logs\, the HR module saves a log file for each mySAP ERP HCM file drop and includes the date and time of processing in the file name, such as the following:
C:\SAP\Logs\hrmodule_log.08-31-2004.10-52
The Application node of the Event Viewer includes additional information, warning, and error events that you can use to help analyze problems with PDS extensions and the Service for EDM. The Source column of events related to the ERP Connector is labeled Microsoft Project Server Tracing Eventlog Provider. For more information about PDS and EDM errors in the Event Viewer, see Potential Problems in Installing PDS Extensions in the topic Installing the Project Server Components.