Acceptance Tests

  • Article

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.

Acceptance testing a plug-in component for the ERP Connector Solution Starter for Microsoft Office Project Server 2007 involves preparing XML files with sample input data for the various test scenarios, running the tests, and analyzing the results. The final set of tests before installing ERP Connector on a production system should use live data from mySAP™ ERP.

This topic describes the processes and results of the recommended tests for the SapHRPlugIn component, as an example. This topic includes the following sections:

  • XML Files for the Test Scenarios

  • Recommended Tests

    • Resource Tests

    • Organization Structure Tests

    • Resource Mapping Tests

    • Testing with Live Data

    • Using the Event Viewer

XML Files for the Test Scenarios

To perform the tests for SapHRPlugIn that are described in Test Scenarios, you must prepare XML request files for the ERP Connector drop folder on Project Server. To help describe the tests, the sample test files installed with the ERP Connector Solution Starter include a combination of resource, organization structure, and mapping data. The sample test file names include the following:

  • R, which stands for resource data.

  • M, which stands for mapping data.

  • S, which stands for organization structure data.

  • One or more numbers that indicate how many sets of each kind of data the file includes.

The ERPConnector\tests\HR subdirectory in the Project 2007 SDK download includes the following sample XML files for the SapHRPlugIn 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 PERNO element (for the SAP Resource ID custom field) is the same as in 10R_0M_0S.xml.

5R_0M_0S.xml    Contains five new resources.

0R_0M_1S.xml    Contains an organization structure.

0R_0M_1S_modified.xml    Contains a modified organization structure.

0R_10M_0S.xml    Contains mapping information for the ten resources in the 10R_0M_0S.xml file, and includes 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.

In addition, there are three files that contain incorrect data or XML structure that is not valid for SapHRPlugIn requests.

The tests recommended for SapHRPlugIn include a series of resource, organization structure, and mapping tests using XML test files and live data.

Resource Tests

Use Procedure 1 to prepare for the resource tests, and then perform the tests in Table 1 in the order that they are listed. Check the intermediate results of each test before proceeding to the next test. To see the results, you can use either Project Web Access or Microsoft Office Project Professional 2007 to open the enterprise resource pool and view the custom fields for a resource.

For information about configuration, see Configuring the ERP Connector. For information about the Windows event log, see Using the Event Viewer.

Procedure 1. To prepare for resource tests

  1. In the SapHRPlugIn.config file, set Deactivate·Resources to true (the default).

  2. Set Activate·Resources to true (the default).

  3. Delete all resources that have a SAP Resource ID custom field.

    1. In Project Professional, open the enterprise global template, view the Resource Sheet, and then insert columns for the resource custom fields specified in the SapHRPlugIn.config file. For example, add the columns SAP Resource ID, SAP Organisation Unit ID, and SAP Manager Flag. Save and close the enterprise global template, and then restart Project Professional.

    2. Open the enterprise resource pool, and check whether the resources have a SAP Resource ID custom field.

    3. In Project Web Access, click Server Settings, and then click Delete Enterprise Objects.

    4. On the Delete Enterprise Objects page, click Resources and Users, select the resources you want to delete from the enterprise resource pool, and then click Delete.

Table 1. Resource tests

Test

Action

Intermediate Results

1

Drop the file 0R_0M_0S.xml.

No resource should be created, because there is no resource information.

No resource should be deactivated, because there is no resource with an SAP Resource ID custom field in the enterprise resource pool.

2

Drop the file 10R_0M_0S.xml.

There should be ten new resources in the enterprise resource pool, and each should have an SAP Resource ID custom field.

No resource should be deactivated, because there are no resources to deactivate.

3

Drop the file 5R_0M_0S.xml.

There should be five new resources in the enterprise resource pool, and each should have an SAP Resource ID custom field.

The ten resources created in Test 2 should be deactivated.

4

Drop 10R_0M_0S.xml again.

The five resources created in Test 3 should be deactivated.

The ten resources created in Test 2 should be activated.

5

Drop the file 10R_0M_0S_modified.xml

The ten resources created in Test 2 should have updated information.

6

Drop 0R_0M_0S.xml again

All fifteen of the resources created in Test 2 and Test 3 should be deactivated.

Organization Structure Tests

Use Procedure 2 to prepare for the organization structure tests, and then perform the tests in Table 2 in the order that they are listed. Check the intermediate results of each test before proceeding to the next test.

Procedure 2. To prepare for organization structure tests

  1. Delete the structure information for the lookup table that you are using for organization structure. To do this, you can delete the lookup table and then create it again by using the Connector Tool:

    1. In Project Web Access, click Server Settings, and then click Enterprise Custom Field Definition.

    2. Delete any custom fields that use the SAP Organisation Units lookup table.

    3. Delete the SAP Organisation Units lookup table.

    4. On the Project Server computer, run ConnectorTool.exe with no arguments. It creates the empty lookup table and the custom fields specified in the SapHRPlugIn.config file.

  2. Use Project Web Access to delete all resources that have an SAP Resource ID custom field.

Table 2. Organization stucture tests

Test

Action

Intermediate Results

1

Drop the file 0R_0M_1S.xml.

There should be no resource with an SAP Resource ID custom field in the resource pool.

The SAP Organisation Units lookup table should contain the structure of the organization.

2

Drop the file 0R_0M_1S_modified.xml.

There should be no resource with an SAP Resource ID custom field in the enterprise resource pool.

The SAP Organisation Units lookup table should contain the modified structure of the organization.

3

Drop the file 0R_0M_0S.xml.

There should be no resource with an SAP Resource ID custom field in the enterprise resource pool.

The SAP Organisation Units lookup table should still contain the modified organization structure, because SapHRPlugIn does not delete organization information.

Resource Mapping Tests

Use Procedure 3 to prepare for the resource mapping tests, and then perform the tests in Table 3 in the order that they are listed. Check the intermediate results of each test before proceeding to the next test.

Procedure 3. To prepare for resource mapping tests

  1. In the SapHRPlugIn.config file, set Deactivate·Resources to false.

  2. Delete the structure information for the lookup table that you are using for organization structure, as in Procedure 2, Step 1.

  3. Delete all resources that have a SAP Resource ID custom field.

Table 3. Resource mapping tests

Test

Action

Intermediate Results

1

a. Drop the file 10R_0M_0S.xml.

b. Drop the file 0R_0M_1S.xml

c. Drop the file 0R_10M_0S.xml.

a. Creates the resources for the mapping tests.

b. Creates the organization structure.

c. Applies the resource mapping.

There should be ten resources in the enterprise resource pool, and each should have an SAP Resource ID custom field.

The organization structure should be represented in the SAP Organisation Units lookup table.

The ten resources should be mapped to a specific organization unit, and the SAP Manager Flag custom field should be set.

2

Drop the file 0R_0M_1S_modified.xml.

There should be a new organization structure in the SAP Organisation Units lookup table.

If you are using Project Professional to view the organization unit in the Resource Sheet, remove and then add the SAP Organisation Units column again in the enterprise global template (Procedure 1, Step 3.a).

NoteNote
When you delete and add a custom field or change a lookup table structure, you must reset the field in the enterprise global template to show the modified structure.

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 enterprise resource pool, and each with the same SAP Resource ID custom field.

The modified organization structure should be represented in the SAP Organisation Units lookup table.

The ten resources should be activated and mapped to the modified organization unit (see Figure 1).

Figure 1. Results of mapping resources to the modified organization structure

Results of mapping resources to the organization

Testing with Live Data

Use Procedure 4 to prepare for the live data test. Check the results after mySAP ERP Human Capital Management (HCM) saves an XML request file to the drop folder on the Project Server computer.

Procedure 3. To prepare for testing with live data

  1. In the SapHRPlugIn.config file, set Deactivate·Resources to true.

  2. Set Activate·Resources to true.

  3. Use Project Web Access to delete all resources that have an SAP Resource ID custom field.

  4. Log on to the mySAP ERP system.

  5. In mySAP ERP HCM, configure the export service for human resource data to drop the file in the correct drop folder for your test, and then execute the export service.

Note

It is easier to check the test case results if the enterprise resource pool is empty. However, it is not necessary to delete the resources from the enterprise resource pool on Project Server. You can also vary the SapHRPlugIn.config file settings for resource activation and deactivation.

Following are the expected results of the live data test:

  • The enterprise resource pool should contain resources from the mySAP ERP HCR system. Compare the enterprise resource pool on Project Server with the input data.

  • The organization structure should be represented in the SAP Organisation Units lookup table in Project Server.

  • The resources that have an SAP Resource ID custom field should be mapped to the correct organization unit, and the SAP Manager Flag custom field should be correctly filled.

  • You should compare every resource or mapping that is not part of the Project Server enterprise resource pool with the event log. If the resource is not updated as expected, the event log should include a warning or an error that describes why the processing failed for that resource.

Using the Event Viewer

You can individually configure the Windows event log name and set the log level for the ERP Connector application and plug-in components. For more information, see Configuring the ERP Connector.

Note

If you change a log name in one of the configuration files, you must restart the Event Viewer to see the new log name. For an example, see Figure 1 in Additional Tests.

To use the Windows event log on the Project Server computer, on the Windows Start menu, click Administrative Tools, and then click Event Viewer. In Figure 2, the default node for ERP Connector in the Event Viewer is SAPMSP.

Figure 2. Windows events in the default node for ERP Connector

Windows events in the node for ERP Connector

The Application node of the Event Viewer includes additional information events, warning events, and error events that you can use to help analyze problems.

See Also

Concepts

Installing the ERP Connector on Project Server

Configuring the ERP Connector

Test Scenarios

Additional Tests