Mastering IDoc Business Scenarios with SAP XI

Michal Krawczyk, Michal Kowalczewski

Contents Preface 1
........................................................... 3

Setting Up Conrmation Keys in Material Infotypes ................................

29 29 30 31

IDocs Basics and Elemental Technical Conguration ..............................................

1.1 Creating Connections Between Different Systems ................................. RFC Type Connection ........................... TCP/IP Type Connection ....................... 1.2 1.3 Port Denition ...................................... Partner Prole Maintenance ................. Parameters ............................................ Creating Logical Systems ...................... Customizing .......................................... 1.4 Summary ...............................................
........

Testing the New Settings ......................

5 6 6 8 9 11 11 12 12 14 15 16 17 18 21 22 23 25 25 25 27 28 28

2.3

Logistic Invoice Verication .................. Creating Proper Partner Proles ........... Allocating Company Code, Tax Codes Mapping, and Special Program Parameters ........................................... Testing the New Settings ......................

31 32 33 34 34 35 36 36 37 38 38 39 40 40 41 41 42 42 43

2.4

Processing Inbound Orders in Sales and Distribution ................................... Creating Suitable Partner Proles with Inbound Parameters ............................. Converting External Partner Numbers ............................................... Assigning a Customer to SD Organizational Data .............................. Testing and Debugging Incoming IDoc Sales Orders .................................

Business Scenario Conguration

2.1 Purchase Orders and PO Changes

in the MM Module ............................... Choosing a Proper Application and Procedure ............................................. Creating a New Output Type ............... Access Sequence ................................... Creating a Condition Record ................ Dening a Partner Prole ..................... Fine-Tuning of Messages ...................... Entering the Material Numbers from the Vendors Systems ........................... Testing the Scenario .............................. 2.2 Receiving of Purchase Order Conrmations ....................................... Creating an Appropriate Partner Prole .................................................... Setting Up Conrmation Control in Customizing for Purchasing ..................

2.5

Outbound Order Conrmation ............ Choosing or Creating a New Output Type ...................................................... Choosing a Proper Procedure .............. Creating Entries in Condition Record Tables .................................................... Conguring the Partner Prole ............. Testing the Conguration .....................

2.6

Outbound Delivery .............................. Choosing or Creating Output Types ..... Adding the Output Type to a Proper Procedure ............................................. Maintaining the Condition Records ..... Dening the Partner Prole .................. Testing the Conguration .....................

www.sap-press.com

Contents

2.7

Outbound Invoice ................................ Choosing or Creating Output Types ..... Adding Output Types to a Proper Procedure ............................................. Creating a Condition Table ................... Creating Entries in Partner Proles ....... Testing the Conguration Pick Up with Paper Edits ....................................

43 44 44 45 46 46 47 47 50 51 51 53 53 55 55 56 56 56 59 59 59 61 62 62 64 64 64 66 68 68 69 72 73 73 74

4.7

IDoc Packages and Event-Driven Messages ............................................... Setting Up IDoc Packages ..................... Advanced Scheduling of Message Processing .............................................
76 77 77 77 78 79 80 81 81 83 84 84 84 85 85 86 87 88 89 90 91 92 93 95 97 75 75

4.8

IDoc Tunneling ..................................... Sending IDocs Without the XML Conversion ................................... Setting Up IDoc Tunneling ...................

2.8

Extension of Condition Tables .............. Creating a Condition Table ................... Access Sequence ................................... Output Type ..........................................

4.9

IDoc Acknowledgments ....................... Sending Acknowledgments from an SAP Application System ........................ Sending Acknowledgments from SAP XI ...................................................

2.9

Summary ...............................................
.......................................

IDoc Monitoring
3.1 3.2

4.10

IDoc Serialization .................................. Setting Up Standard IDoc Serialization .......................................... Removing IDocs from the Queues ....... Pseudo IDoc Serialization .....................

Searching for IDocs .............................. IDocs Reprocessing ............................... Inbound Documents ............................ Outbound Documents .........................

3.3 3.4

IDoc Editing .......................................... Summary ...............................................

.......................

4.11

IDoc Bundling ....................................... Multiple IDoc Instances in One Message ........................................

SAP XI in IDoc Scenarios

4.1 4.2

4.12 4.13

Turning Off IDoc Processing Within the Integration Engine .......................... IDoc Message Mappings ...................... Optimizing the IDocs Structure .......... Message Mapping Examples ................ Graphical Message Mapping ................ User-Dened Functions in Graphical Message Mapping ................................. XSLT Message Mapping ........................ Graphical Message Mapping ................ XSLT Mapping .......................................

SAP XI Introduction .............................. Design of SAP XI ................................... IDoc Exchange Basis with the Use of SAP XI ............................................... IDoc Metadata Inside Integration Repository and Integration Engine ....... IDoc Metadata Comparison .................

4.3

Sending IDocs to SAP XI ...................... SAP Application System Conguration ........................................ SAP XI Conguration ............................ Sending IDocs to SAP XITesting Procedure .............................................

4.14

Summary ...............................................
...................................................... ......................................................

5 A

Summary Appendix Index

4.4

Sending IDocs from SAP XI .................. Integration Repository .......................... Integration Directory ............................ Testing Sending IDocs ..........................

.............................................................. 101

4.5 4.6

Monitoring IDocs Inside SAP XI ........... IDoc Control Record ............................ Changing the IDoc Control Records Default Values .......................................

Galileo Press 2007. All rights reserved.

Preface

This book is based on our experiences with IDoc scenarios and the use of SAP NetWeaver Exchange Infrastructure (SAP XI). IDocs still provide one of the most popular interfaces that enable the connection of SAP application systems (SAP R/3, mySAP ERP) to both third-party and other SAP application systems. They can be generated easily from many application transactions and used to generate various documents in SAP application systems, in all possible modules and solutions. With the introduction of SAP XI, it became much easier to use IDocs in the new XML world. SAP XI allows exible integration using IDocs in standard form, with very little conguration needed to create a simple IDoc message ow. Based on our experience, we assert that IDoc integration ows can be very efcient if they are well designed. This book explains both the concepts behind IDocs and how to process IDocs via SAP XI. Readers will gain comprehensive knowledge of all possible scenarios of IDoc ows, as this book covers many real solutions based on our integration project experience. This book is structured as follows:

narios from Material Management (MM) and Sales and Distribution (SD). Chapter 3 details administrator tasks connected with IDoc monitoring, dealing with errors and reprocessing on the SAP side. Chapter 4 is dedicated to the IDoc exchange using SAP XI. We move from standard conguration of IDoc ows through SAP XI to more advanced topics such as IDoc packaging, and IDoc mappings. Chapter 5 provides a short summary of the all the ideas described in the book. Note This book is based on SAP NetWeaver Exchange Infrastructure Service Pack Level 17. Therefore, some options can only be enabled from this particular Service Pack version.

Acknowledgments Michal Krawczyk thanks his family for their never-ending encouragement and inspiration for his work. He also thanks his colleagues from the integration team at BCC for their ideas and support. Theyve developed many integration scenarios together, and these gave him new ideas on how to handle integration more efciently. Michal Kowalczewski thanks his family and friends for their love and support. Both authors also thank their editor, Stefan Proksch at Galileo Press, for his support in preparing this book.

Chapter 1 gives details of preparing the SAP system for an IDoc enabled conguration. It deals with the technical aspects of the conguration, such as connections and ports.

Chapter 2 shows how to congure input and output IDocs in certain business scenarios. Due to capacity restrictions, we focus only on the most common sce-

www.sap-press.com

3 IDoc Monitoring

IDoc monitoring is a very important daily task. The operator has to check the status of incoming and of outgoing IDocs and x any errors. In this chapter, we will present the most common transactions and techniques for monitoring IDoc interfaces in the SAP application system. In Chapter 4, you will also nd out how to monitor IDoc messages from the SAP NetWeaver Exchange Infrastructure.

Creation Date Direction (inbound or outbound) IDoc number Current Status Basic type Logical message Message code Message function Partner port Partner number Partner Type

3.1

Searching for IDocs

To check the IDoc status and view its data, we can use transaction WE02. Let us run that transaction and see how it looks. The selection screen makes it possible to lter IDocs with the most important parameters, including: Figure 3.1 displays the selection screen. On the IDoc view screen, (see Figure 3.2) you can nd all information concerning IDoc data (IDoc segments) and its processing status, at the status-records tree. Dou-

Figure 3.1 WE02IDocs List

www.sap-press.com

53

3 IDoc Monitoring

Figure 3.2 WE02IDoc Detailed View

Figure 3.3 Example of Status View

ble-clicking on the status details opens the status description (see Figure 3.3). The detailed status description is very helpful during IDoc debugging. Sometimes the system can propose links

to the customizing settings maintenanceactivities from transaction SPROthat were not correctly prepared. If you see an error such as Messages from IDoc processing can be found in application log (see Figure 3.4), you have

54 Galileo Press 2007. All rights reserved.

3.2 IDocs Reprocessing

to double-click on the status number and push the Application Log button. It will open the window with nal error messages (see Figure 3.5).

3.2 IDocs Reprocessing

Inbound Documents Some errors in inbound IDoc messages can be repaired by changing the conguration or master data; e.g., when the order cannot be created because of a non-existing customer. In this case, you have to add a new customer and then reprocess the IDoc message. After making changes and determining a potential source of a problem, it is possible to reprocess IDocs by

Figure 3.4 IDoc Status with Comment in the Application Log

transaction BD87. Let us have a look at the details of that process. 1. Open transaction BD87 and select proper time interval; e.g. one day. 2. After execution, the screen presents statistics (see Figure 3.6) showing how many IDocs have been processed successfully and how many have errors. The statistic is presented in a tree view.

Figure 3.5 Displaying the Application Log

WE02 is the basic tool for IDoc monitoring. You should open this transaction a few times a day and check whether all statuses are correct. The next section will explain ways to x errors if they occur.
Figure 3.6 BD87List of Non-Posted IDocs

Figure 3.7 BD87Result of Reprocessing

www.sap-press.com

55

3 IDoc Monitoring

3. IDocs are reprocessed by selecting a group of IDocs represented as a row in a tree, then pressing the Process button. It is only possible to reprocess IDocs that are in red or yellow status. While reprocessing, new statutes are added as shown in Figure 3.7. The gure shows that some IDocs were posted correctly and some of them continued to have errors. In this situation, we have to try to correct the system conguration and than reprocess IDocs one more time. Outbound Documents In some cases, outgoing IDoc messages can also result in errors. Usually the problem occurs while leaving the port (described in Chapter 1). There could be a number of reasons; for example, the receiving system may not be available. 1. Reprocessing of the outbound document, if it was not carried out automatically, can be performed by double-clicking on IDoc entries in tRFC queue (see Figure 3.8).

3.3 IDoc Editing

You can manually change an IDoc and execute it repeatedly, but this should not be done in a production environment because you would modify the original meaning of the message (for example, an amount to pay). To change an existing IDoc, we can use standard transactions WE02 or WE19. In transaction WE02, doubleclick the Page icon near the segment that you want to change (see Figure 3.9) and than choose Data record Display Change from the menu. You then can write values to the segments elds (see Figure 3.10).

Figure 3.9 WE02Segment Icon

The changes are made nal after pressing the Save icon. After this step, a copy of the original IDoc is created with status 70: Original of an IDoc which was edited. The actual IDoc gets status 69: IDoc was edited. We
Figure 3.8 BD87Outgoing Documents

can process those IDocs in transaction BD87, just as we did with IDocs not posted successfully due to errors.

2. Select the group of messages of the same message type and press Display tRFC calls. You should see the list of all messages that were not sent. 3. Finally, select the IDocs one by one and choose Execute LUW (F6) from the menu. This action will send IDocs to the external system. By reading this section, you found out how to deal with error situations. For incoming IDocs, this involves a change of the conguration settings or basic data and reprocessing of the IDocs. Sometimes, on the development system, this is insufcient, and you have to manually change the IDoc data to process it correctly. This technique is described in the next section.

3.4 Summary
This chapter explained how to monitor and deal with potential IDoc problems in the SAP application system. In most cases, however it is not the only administrative work that has to be done. IDocs also can cause errors in middleware software such as SAP XI. IDoc monitoring from the XI side will be described in the next chapter.

56 Galileo Press 2007. All rights reserved.

3.4 Summary

Figure 3.10 WE02Editing IDoc

www.sap-press.com

57

4 SAP XI in IDoc Scenarios

This chapter provides you with an overview of the SAP NetWeaver Exchange Infrastructure (SAP XI) as well as the technical steps you need to perform in order to use SAP XI to transfer IDocs.

Both types of activities will be presented in the next sections with regard to IDoc message exchange. Design of SAP XI SAP XI consists of three main parts, as shown in Figure 4.1:

4.1

SAP XI Introduction

Integration Builder Integration Server System Landscape Directory

SAP XI enables you to connect with all systems that support IDoc information exchange. Essentially, SAP XI is a process-integration tool that can integrate one or many business systems. We can distinguish two types of activities supported by the SAP XI:

The Integration Builder serves as the main tool for modeling new integration ows. It consists of the Integration Repository and the Integration Directory. The Integration Repository is used for building all objects that will become relevant for transporting. This includes data types, message interfaces, message mappings, and integration scenarios. You can see the most important repository objects in Figure 4.2.

Cross-system application integration This is responsible for the runtime part of the integration ows, and no user actions are required.

Administration and development This focuses on both the development of the new integration ows and the administration of the existing ones.

Integration Builder

Central Monitoring

Integration Server
Integration Repository Integration Directory Integration Engine Business Process Engine Adapter Engine

System Landscape Directory

Figure 4.1 SAP XI Schema

www.sap-press.com

59

4 SAP XI in IDoc Scenarios

adapters: Services used to communicate with systems

Integration Repository
Business Scenarios Business Processes Mappings Context Objects Message Interfaces External Definitions Software Components

that can use messages structures other than XML messages supported by the SAP XI or that use different protocols to communicate. In the next sections, one of those adaptersthe IDoc adapter and the communication with the use of this adapterwill be discussed in detail. The Integration Server is the SAP XI runtime component responsible for receiving incoming messages and controlling how these messages are forwarded to the receiver systems. It consists of three parts:

Integration Engine The Integration Engine is the runtime environment of the SAP XI.

Business Process Engine The Business Process Engine controls how all the steps of the integration process are dened and executed during runtime.

Figure 4.2 Integration Repository Objects

Adapter Engine The Adapter Engine is used to connect with external systems.

The Integration Directory, on the other hand, is maintained separately for every landscape. What you transport are only routing conditions. The system names can differ from one landscape to another, for instance during transporting from development systems to quality assurance systems. Figure 4.3 highlights the most important Integration Directory objects.

The third part of the SAP XI design is the System Landscape Directory (see Figure 4.4), which is the central location where the information about the whole landscape is maintained. It contains two types of information:

Landscape description The landscape description contains a list of all installed systems in the landscape, both technical systems and business systems.

Integration Directory
Business Scenarios

Component information Component information contains information about products and components of different systems. These are maintained in the Software Catalog.

Business Processes Parties Business Systems/Services Routing Rules Collaboration Agreements Collaboration Profiles

Figure 4.3 Integration Directory Objects

Communication channels are among the objects maintained in the Integration Directory. These are based on

Figure 4.4 System Landscape Directory

60 Galileo Press 2007. All rights reserved.

4.2 IDoc Exchange Basis with the Use of SAP XI

All components of the SAP XI and all the ows that run through it can be centrally monitored by a component called Runtime Workbench (RWB). It consists of several monitors that can be used on IDoc exchange ows from different angles:

synchronously. In most cases other than in IDoc tunneling, which will be discussed later, IDocs inside the Integration Server are transformed into XML messages called IDOC-XML. In a manner of speaking, IDOC-XML is just an XML representation of the IDoc. In Listing 4.1, you can nd an example of the MBGMCR02 IDoc in the XML format. As you can see, it has the same segment names as standard IDoc MBGMCR02.
<?xml version="1.0" encoding="UTF-8"?> <MBGMCR02> <IDOC BEGIN=""> <E1MBGMCR SEGMENT=""> <TESTRUN/> </E1MBGMCR> <E1BP2017_GM_HEAD_01 SEGMENT=""> <PSTNG_DATE>01012010</PSTNG_DATE> <DOC_DATE>01012010</DOC_DATE> <REF_DOC_NO>43234566666</REF_DOC_NO> <BILL_OF_LADING/> <GR_GI_SLIP_NO/> <PR_UNAME/> <HEADER_TXT/> <EXT_WMS/> <REF_DOC_NO_LONG/> <BILL_OF_LADING_LONG/> <BAR_CODE/> </E1BP2017_GM_HEAD_01> <E1BP2017_GM_ITEM_CREATE SEGMENT=""> <MATERIAL/> <PLANT/> <STGE_LOC/> <BATCH/>

Component monitoring Component monitoring allows you to check the status of every component of the SAP XI (Integration Engine, adapters, etc.)

Message monitoring With the message monitoring, you can monitor messages that ow through the Integraiton Engine, in a way similar to using transaction SXMB_MONI

End-to-end monitoring With this monitor, you can check which components were involved in a particular ow

Performance monitoring Performance monitoring allows you to check the speed of different ows, based on many selection and grouping criteria

Index administration This is used to start or stop message indexing (messages can be indexed via the TREX engine)

Alert conguration The alert conguration is used to maintain alerts that later can be called from the integration ows and passed to an email account or a short message service (SMS)

Cache monitoring Cache monitoring lets you monitor the content of the cache currently in use

4.2 IDoc Exchange Basis with the Use of SAP XI

SAP XI enables you to connect with systems that support IDoc information exchange. While only IDocs from SAP systems Release 3.1x or higher are supported, you also can send IDoc messages from an external (third-party) system to the Integration Server, SAP XIs core engine. The Integration Server can communicate with different systems through the IDoc adapter. We can use the IDoc adapter in all integration scenarios as long as message ow is asynchronous and one of the involved systems can process IDocs. IDoc exchange cannot be done

<MOVE_TYPE/> <STCK_TYPE/> <SPEC_STOCK/> </IDOC> </MBGMCR02>

Listing 4.1 MBGMCR02 IDoc in the XML Format

IDoc adapter conguration is different for the inbound channel, when IDocs are being sent to SAP XI, than it is for the outbound channel, when IDocs are being sent from SAP XI. The message exchanges between IDoc sender and IDoc receiver systems are very similar, however.

www.sap-press.com

61

4 SAP XI in IDoc Scenarios

IDoc sender adapter This adapter is used to send messages to the Integration Engine. When you send IDocs to the SAP XI, they are being processed by this service on the Integration Engine unless an IDoc message is included in an exception table (see Section 4.12).

The second method, uploading the metadata before running our integration scenarios, is advisable because we can be sure that the IDoc denitions are the ones that we really want, given that the IDocs metadata is visible right after the import. If the system does not allow exporting the metadata (as is the case with some third-party systems) we can always reference an SAP system to be our metadata repository. In case of problems, we can always have a look at our metadata description with transaction IDX2, which is used to upload or check metadata. In Figure 4.5 we can see an example of the IDocs metadata description uploaded from an SAP system via transaction IDX2. To see the description, you need to double-click on the IDocs name. As you can see, it contains eld descriptions very similar to a standard IDoc description taken from transaction WE60. IDoc Metadata Comparison As of SAP XI 3.0 Service Pack 17, we have a new report called IDX_CHECK_METADATA that enables us to compare a systems current metadata with a reference system. This function can be very useful on the development system, where we often change the structures of the customer IDocs while developing the integration scenario.

IDoc receiver adapter This adapter is used to send messages from the Integration Engine. It is called after all services inside the Integration Engine process the IDOC-XML. The adapter then transforms the IDOC-XML into a standard IDoc format and sends it through the IDoc RFC interface.

IDoc Metadata Inside Integration Repository and Integration Engine In order to process an IDocs in the form of an IDOCXML message, an IDocs metadata must be loaded into the Integration Server so that SAP XIs IDoc adapter can change the native IDoc format into the XML representation. This metadata is just a description of available structures and elds and can be loaded in two ways:

During the runtime Before the actual message ow

Figure 4.5 IDoc Metadata

62

Galileo Press 2007. All rights reserved.

4.2 IDoc Exchange Basis with the Use of SAP XI

Once the metadata is loaded into the system (as described earlier in this section), it is not loaded again during every call. That is why, if there are any changes in the IDocs structure, they would not be reected in the new ow. The new report IDX_CHECK_METADATA now helps to check very quickly if the data needs to be reloaded. You can start the report from transaction SE38. Once the report starts, you need to ll at least two elds (see Figure 4.6):

Figure 4.7 shows that there are three types of statuses that you can see in this report.

Icon with a plus sign When you see this icon, it means that the remote system (the one you want to compare) has more elds that the IDocs metadata loaded to the SAP XI.

Icon with a minus sign When you see this one, it will mean that the IDoc from the remote system has been reduced, and there are more elds in SAP XIs cache.

Port Here, you have to enter the port from transaction IDX1 from which you want to compare the IDocs metadata

Icon with a pencil This icon means that the segment names are the same but the structures are different (offsets, lengths).

Basic Type Fill out the IDocs basic type name

If you see any of those three types of inconsistencies with this report, you can delete the metadata from the specied port directly by pressing the Delete button. The new metadata will be reloaded during the next ow, or you can import it manually as shown earlier in this section. If your SAP XI system version is lower than Service Pack
Figure 4.6 Report IDX_CHECK_METADATA

17, you can always delete the IDocs metadata directly by using transaction IDX2 or by using an older report (IDX_
RESET_METADATA). Keep in mind, though, that those two

If you are using an IDocs extension, you can also put its name in the report (eld Extension). Choosing the Execute button will cause the metadata to be downloaded from the IDoc port and compared with the existing metadata. You can see an example of such comparison in Figure 4.7.

alternative methods will not tell you whether you need to reload, as they do not compare anything. The information from this section should give you the idea of how the IDoc messages look from the SAP XIs perspective. The next section will concentrate on the conguration of the IDoc ows.

Figure 4.7 Metadata Comparison

www.sap-press.com

63

Index

A
ABAP mapping 87 Access sequence 18, 22, 37, 41, 47, 50 ACK_SYSTEM_FAILURE 80 Acknowledgment configuration 68 Adapter Engine 60 Adapter Framework 81 Adapter Specific identifiers 65 Advanced functions 89 ALE audit message 79 ALE logical system 71 Application, Choose 17 Application acknowledgment 78 Application code 17 Application log 55 Apply control record values from payload 73, 74 Assign tax codes 31

D
DESADV 40 Distribution model 79

IDoc receiver adapter 62 IDoc receiver channel 73 IDoc sender adapter 62 IDX_CHECK_METADATA 62 IDX_NOALE 68 IDX_RESET_METADATA 63 IDX_SELECT_IDOCTYP_WITHOUT_IS 85 IDXIDOCINB 85 IDXQUEUE 84 Integration Builder 59 Integration Directory 59, 60, 65, 69 Integration Engine 60 Integration process 75 Integration Repository 59 Integration Server 59, 60 Interface mapping 91 Internal communication 70 INVOIC 43 Invoice 43

E
EDI partners, Configure 35 EOIO 83 Event-driven message processing 75, 76 External definition 84

F
Field catalog 47 File port 9 Flat file 9

G
Graphical message mapping 90, 92

B
BAPI 15 Basic type 63 Batch input 36 Business Landscape 64 Business Process Engine 60 Business service 70 Business system 64, 65

H
Header mapping 71, 74

J
Java mapping 87

I
IDoc Editing 56 Reprocessing 55 IDOC-XML 61 IDOC_INBOUND_IN_QUEUE 82, 83 IDOC_OUTPUT_ORDERS 24 IDoc acknowledgments 78 IDoc adapter 61, 73 IDoc bundling 84, 85 IDoc control record 73 IDoc metadata 62 IDoc ORDER05 97 IDoc packages 76 IDoc port 66

L
Logical system 21, 64

M
Material Info Record 25 Materials Management (MM) 15 Maximum package size 76 Message broker 78 Message Control 15 Metadata 63 Monitor for message packages 76

C
Change list 69 Component monitoring 72 Condition record 21, 42 Condition table 21, 38, 45, 47 Configuration scenario 71 Configuration wizard 70 Confirmation control 28 Confirmation keys 29

www.sap-press.com

101

Index

O
ORDCHG 33 Order confirmation 36 Order response 28, 36 ORDERS 33, 34 ORDERS05 23, 24 ORDRSP 28, 36 Outbound delivery 40, 43 Output type 18, 37, 41, 44, 47, 51

Requirements 38, 41 RFC API 8 RFC connection 64 RFC destination 6, 64, 65, 66 Runtime Workbench 61, 72

TCP/IP connection 6, 8 Technical system 64 Test message 72 Transaction BD87 55 ME21N 16, 17 ME22N 17 ME23N 32 NACE 17 RFC 9 SD08 46 SD09 46 SM59 6 SXI_MONITOR 73 SXMB_ADM 77, 80 SXMB_MONI 72, 73, 75 VA03 17 WE02 53, 56 WE19 56 WE21 9 WE60 9 WEINBQUEUE 83 WEOUTQUEUE 83

S
Sales and Distribution (SD) 15 Sales order 17, 33 SAP_XI_ADMINISTRATOR 66

P
Partner profile 11, 28, 34, 39, 42, 46 Permanent error 81 Port 9, 63 Maintaining 6 Procedure, Choose 17 Procedures 17, 38, 41, 44 Process code 34, 46 Purchase order 16

SAP_XI_CONFIGURATOR 66 SAP R/3 connection 6 SAP Web Application Server 81 Serialization 81, 84 Shared Master Data Tool 15 SLD bridge 64 SOAP payload 77 Software component 68 SXMS_UNPACK_MESSAGES 76 Synchronous communication 78 System acknowledgment 78 System Landscape Directory 59, 60 System number 64

Q
Queue processing 81

X
XML_CONVERSION 77 XPATH expression 75 XSLT editor 90 XSLT functions 91 XSLT mappings 87, 92

R
RBDSTATE 79 Receiver agreement 74 Registered server program 8

T
Take receiver from payload 74 Take sender from payload 74 Target host 64

102 Galileo Press 2007. All rights reserved.