Configuring in the Integration Directory - Scenario with Multiple Receivers

Scenario with Multiple Receivers

Task 1: Configuring in the Integration Directory

You make settings for routing and mapping the messages in the Integration Directory. This is where the Integration Repository objects created at design time are configured. The following sub-tasks reiterate the individual steps that are required for the configuration of the asynchronous IDoc scenario.

Configure the asynchronous scenario that is described in the business example. The data must only be distributed if the Partner Number Receiver field has the value LS_BIT_##. The field is located in the IDoc control record (segment EDI_DC40) and is called RCVPRN.

1. Log on to the Integration Server. From the menu, start the Integration Builder and log on to the Integration Directory.

2. In the Integration Directory create the business scenario BIT400_##.

3. Create a receiver determination for business scenario

BIT400_##that you just created for the sender business system Travel_Agency_Summer. The outbound interface is described by the IDoc type FLIGHT_SAVEREPLICA.FLIGHT_SAVEREPLICA01.

The receiver of the message is the business system Training. Create a routing condition that ensures that the data is only distributed to the business system Training if the RCVPRN field of the segment EDI_DC40has the value LS_BIT_##.

Continued on next page

63

4. Check the interface determination for the outbound interface FLIGHT_SAVEREPLICA.FLIGHT_SAVEREPLICA01. Is there an interface determination for the sender business system Travel_Agency_Summer and for the receiver business system Training with the inbound interface

FLIGHT_SAVEREPLICA.FLIGHT_SAVEREPLICA01? Is a mapping entered in this interface determination?

5. Check the end point for the business system Training. What end point type is the end point for the inbound interface FLIGHT_SAVEREPLICA.FLIGHT_SAVEREPLICA01? 6. Save your settings and activate your change list.

7. Check the entire configuration by choosing the Refresh icon in the detail view for your business scenario. The system displays a configuration overview. Which entry must be in the configuration overview?

Task 2:

Test your configuration by sending an IDoc from the Travel Agency Summer system. For this purpose, use the program Send Flight Master Data in the initial menu (program name BIT400_REPLICATE_FLIGHTS_IDOC).

1. Log on in client 811 (Travel_Agency_Summer) and start the report BIT400_REPLICATE_FLIGHTS_IDOC. Select a valid flight by using the search help and enter the logical system LS_BIT_##. Start the report by choosing the Execute icon. On the next screen the system displays the IDoc number of the generated IDoc. Choose the IDoc number to display the IDoc. The most important technical information is displayed in the window on the right. What value does the Partner Number field contain? To select the segments in the window on the left, expand the Data Records node. To display detailed information about a segment in the window on the right, double click a segment name. What data is transferred in segment E1BPSFLREP?

2. Once the IDoc has been sent you can display the message in the SAP Adapter Monitor (transaction IDX5) in the Integration Server (client 800). Choose IDoc Monitor and enter today’s date. Choose the Execute icon. Which column contains the IDoc numbers of the source system? Which column contains the number of the XI message that the IDoc adapter created for the IDoc received from the Integration Server? Navigate to the message by double clicking the number and check the receiver determination, interface determination, and technical routing.

Continued on next page

BIT400 Lesson: Logical and Technical Routing

3. How do you know that your message has been successfully processed in the pipeline? Choose the Legend icon.

65 Solution 3: Configuring an Asynchronous Scenario with One Receiver

Task 1: Configuring in the Integration Directory

1. Log on to the Integration Server. From the menu, start the Integration Builder and log on to the Integration Directory.

a) Choose Exchange Infrastructure: Integration Builder→^Start Integration Builder or call transaction SXMB_IFR. Choose

Directory (Configuration). The user name and password are the same as those required to log on to the Integration Server.

2. In the Integration Directory create the business scenario BIT400_##.

a) To create a new business scenario, call the context menu for the Business Scenario node and choose New.... Enter the name of the business scenario and choose Create. You can enter a description on the next screen.

3. Create a receiver determination for business scenario

BIT400_##that you just created for the sender business system Travel_Agency_Summer. The outbound interface is described by the IDoc type FLIGHT_SAVEREPLICA.FLIGHT_SAVEREPLICA01.

The receiver of the message is the business system Training. Create

Continued on next page

BIT400 Lesson: Logical and Technical Routing

a routing condition that ensures that the data is only distributed to the business system Training if the RCVPRN field of the segment EDI_DC40has the value LS_BIT_##.

a) To create a new receiver determination, choose Business Scenario→BIT400_## →Receiver Determination and call the context menu. Next, choose New.... Select the sender business system Travel_Agency_Summer and the interface FLIGHT_SAVEREPLICA.FLIGHT_SAVEREPLICA01from input help and choose Create. You can enter a description on the next screen.

b) In the table for receivers and routing conditions, from the input help for the Receiver field, choose the business system Training.

Hint: To display the input help icon, click on the Receiver field.

c) In the table for receivers and routing conditions, navigate to the condition editor from the input help for the Condition field.

Hint: To display the input help icon, click on the Condition field.

To add a condition, choose the Insert Expression icon. Select the type Field Value and from the input help for segment EDI_DC40, select the field RCVPRN. Close the window with the IDoc structure by choosing OK. In the Value field enter LS_BIT_##. Close the conditions editor by choosing ’OK’.

Continued on next page

67

business system Training with the inbound interface

FLIGHT_SAVEREPLICA.FLIGHT_SAVEREPLICA01? Is a mapping entered in this interface determination?

a) The interface determinations are located under Interface Determination for Outbound Interface→

FLIGHT_SAVEREPLICA.FLIGHTSAVEREPLICA01. Double click to navigate to the detail view. The system displays a table with all the sender business systems for which this outbound interface is configured. One or more receiver interfaces may be assigned to each trio of values comprising the sender business system, outbound interface, and namespace. The receiver interfaces are also identified by a trio of values (receiver business system, inbound interface, and namespace).

b) There is an interface determination for the sender business system Travel_Agency_Summer and for the receiver business system Training with the inbound interface

FLIGHT_SAVEREPLICA.FLIGHTSAVEREPLICA01. Double click to navigate to the detail view. No mapping has been entered because the inbound and outbound interfaces are identical.

5. Check the end point for the business system Training. What end point type is the end point for the inbound interface FLIGHT_SAVEREPLICA.FLIGHT_SAVEREPLICA01? a) To find the end points, choose Receiver System End

Points. The end point for the inbound interface

FLIGHT_SAVEREPLICA.FLIGHTSAVEREPLICA01is of type

’IDoc Adapter’.

6. Save your settings and activate your change list.

a) Check whether you have any windows open in change mode.

Save your settings and close the window. Next, choose the Change Lists tab page. The Changed Objects node contains all objects that have been changed. You can activate these objects by calling the context menu and choosing Activate. If you want to activate all objects, call the context menu for the Changed Objects node. However, if you want to activate individual objects, call the context menu for the object in question.

Continued on next page

BIT400 Lesson: Logical and Technical Routing

a) The system must find the inbound interface FLIGHT_SAVEREPLICA.FLIGHTSAVEREPLICA01 from the sender business system

Travel_Agency_Summer with the outbound

inter-face FLIGHT_SAVEREPLICA.FLIGHTSAVEREPLICA01 and an end point of type IDoc adapter for the receiver business system Training.

Task 2:

a) To start the ABAP report BIT400_REPLICATE_FLIGHTS_IDOC, choose Send Flight Master Data on the initial screen. Enter the corresponding data and start the report by choosing the Execute icon. On the next screen the system displays the number of the generated IDoc.

b) Choose the IDoc number to display the IDoc. The window on the right has a frame with the title Technical Quick Info. The Partner Number field should contain the entry LS_BIT_##.

c) The segment E1BPSFLREP is located under Data

Records→^E1SFL_SAVE→E1BPSFLREP. Click the segment name. The system displays the values for the AIRLINEID, CONNECTID, FLIGHTDATE, PRICE, CURR, CURR_ISO, and PLANETYPE fields in the window on the right.

Continued on next page

69

a) Choose Exchange Infrastructure: Monitoring→SAP Adapter - Monitoring or call transaction IDX5 to navigate to the SAP Adapter Monitor.

b) The IDoc number is in the Reference Number column. Select the line that contains your IDoc number.

c) The number of the XI message is in the Message ID column.

Double click the number in the selected line to navigate to the detail view for your message.

d) Look at the slides for receiver determination, interface determinaiton, and technical routing.

3. How do you know that your message has been successfully processed in the pipeline? Choose the Legend icon.

a) The monitor uses a series of icons to indicate whether a message was processed sucessfully or not. The various kinds of errors are also represented by corresponding icons. To display a list of the icons and their descriptions, choose the Legend icon.

BIT400 Lesson: Logical and Technical Routing

Exercise 4: Configuring an Asynchronous

In document Bit400 en Col34 Fv Part a4 (Page 71-79)