Testing in a Single Client From Two Different SAP Systems

Use

This is the most realistic test situation. It requires transport of the development objects that belong to the enhancement. You therefore have to release the development request before testing.

Prerequisites

• You are developing the enhancements in a development system, in client^NNN.

• You have implemented and activated the enhancements. A logical system name is assigned to the clients^NNNand^MMM. You want to send the IDocs from the client^NNNto the client^MMM. In the following procedures, the development system is called^DEV, and the logical system names are^DEVCLNTNNNand^DEVCLNTMMM.

• The application Customizing settings have been made so you can test the scenario being enhanced. This includes all the settings for the sending system in client^NNN, and all the settings for the receiving system in client^MMM.

• A partner with these Customizing settings exists in the partner profile.

Procedure

1. In the development system, create a destination that leads to client^MMM. 2. In client^NNN, set up a port of type tRFC that references the RFC

destination from step 1.

3. Maintain the distribution model in client^NNN. Enter the logical system

DEVCLNTNNNas the sending system, and the logical system^DEVCLNTMMMas the target system.

4. In client^NNN, set up the outbound partner profile. Select the partner and partner type determined by the application. If the IDoc is generated using message control, you also need to consider the message control settings. For the same partner, also maintain outbound parameters for the message type^SYNCHwith the same RFC destination.

the control record of the IDoc in the status monitor. On the Partner tab page, you can find the information in the Sender Information group box. Note the partner, partner type, and partner role.

6. Use transaction WE42 in client^MMMto check whether the inbound process codes are available. If not, use Transport Customizing or Compare Customizing with the view cluster VED_TMSG1.

Figure 65: Sender: Partner Profile (Outbound)

For an enhancement of an IDoc type to be used in a distribution scenario, the following prerequisites must be met:

• The enhancement for the IDoc has been created. Additional segments are permitted.

• The IDoc type is assigned to a message type.

• In addition to the basic type, the enhancement is also entered in the partner profile.

• At runtime, the master IDoc is enhanced by additional segments.

• At runtime, the name of the enhancement is entered in the^CIMTYP field of the IDoc.

Exercise 8: Testing the Enhancement

Exercise Objectives

After completing this exercise, you will be able to:

• Test the enhancement you have created in the previous exercises.

Business Example

A scenario for ordering materials has been deliberately simplified for this exercise. Some of the functions from the standard scenario have been omitted. You want to create the order for another SAP system. For the outbound order, the message type^ORDLGT is available with an outbound function module for message control. For the incoming order, an inbound function module for the message type^ORDLGTis available. In this scenario, the two fields of the purchase order header, ^INCO1and^INCO2, are not transferred. You want to enhance the scenario by adding these fields. You have finished implementing the enhancement and now want to test the scenario.

Task

Check whether all the required settings have been made for the enhancement. Then create an order, and check whether the generated IDocs have been processed without errors in inbound processing and outbound processing.

1. Using transaction WE82, check whether your enhancement^ZEXTEN##

has been assigned to the message type^ORDLGT, the basic type^ORDLGT01, and Release^4.6C. If it has not, make these assignments.

2. Make the appropriate change in the outbound partner profile for the partner^T-BIL##by entering the enhancement.

3. Test the scenario using the CATT from the exercise in Unit 3: Use the CATT to create an order.

Choose System→ Services → CATT → Record (= transaction SCEM. ).

Enter the test caseYBIT350_ME21_##, and execute it. Use transaction BD87 to check whether the outbound and inbound IDocs now contain

the fields and .

Solution 8: Testing the Enhancement

Task

Check whether all the required settings have been made for the enhancement. Then create an order, and check whether the generated IDocs have been processed without errors in inbound processing and outbound processing.

1. Using transaction WE82, check whether your enhancement^ZEXTEN##

has been assigned to the message type^ORDLGT, the basic type^ORDLGT01, and Release^4.6C. If it has not, make these assignments.

a) Follow the procedure Creating an Enhancement for an IDoc Type in the lesson Defining an Enhancement for an IDoc Type.

2. Make the appropriate change in the outbound partner profile for the partner^T-BIL##by entering the enhancement.

a) In transaction WE20: Change the outbound parameter for^ORDLGT. Enter your enhancement^ZEXTEN##.

3. Test the scenario using the CATT from the exercise in Unit 3: Use the CATT to create an order.

Choose System→ Services → CATT → Record (= transaction SCEM. ).

Enter the test caseYBIT350_ME21_##, and execute it. Use transaction BD87 to check whether the outbound and inbound IDocs now contain the fields^INCO1and^INCO2.

a) Select your IDoc(s) using the partner^T-BIL##. Display the data records of the outbound IDoc and the inbound IDoc. Check whether your segment^Z1INCO##is attached beneath the segment

E1HEAD, and whether the fields^INCO1and^INCO2are included and filled.

Lesson Summary

You should now be able to:

• Test an enhanced scenario

• List what you need to check when transporting into the quality system landscape