%& 6$3 %XVLQHVV &RQQHFWRU

%& SAP AG 1999 SAP AG

6$3 %XVLQHVV &RQQHFWRUn n n n

R/3 System Release: Business Connector 3.5 December 2000 Material Number 5004 3623

&RS\ULJKW

&RS\ULJKW 6$3 $* $OO ULJKWV UHVHUYHG

1HLWKHU WKLV WUDLQLQJ PDQXDO QRU DQ\ SDUW WKHUHRI PD\ EH FRSLHG RU UHSURGXFHG LQ DQ\ IRUP RU E\ DQ\ PHDQV RU WUDQVODWHG LQWR DQRWKHU ODQJXDJH ZLWKRXW WKH SULRU FRQVHQW RI 6$3 $* 7KH LQIRUPDWLRQ FRQWDLQHG LQ WKLV GRFXPHQW LV VXEMHFW WR FKDQJH DQG VXSSOHPHQW ZLWKRXW SULRU QRWLFH $OO ULJKWV UHVHUYHG

SAP AG 1999

7UDGHPDUNV Microsoft , Windows , NT , PowerPoint , WinWord , Excel , Project , SQL-Server , Multimedia Viewer , Video for Windows , Internet Explorer , NetShow , and HTML Help are registered trademarks of Microsoft Corporation. n Lotus ScreenCam is a registered trademark of Lotus Development Corporation. n Vivo and VivoActive are registered trademarks of RealNetworks, Inc. n ARIS Toolset is a registered Trademark of IDS Prof. Scheer GmbH, Saarbrcken n Adobe and Acrobat are registered trademarks of Adobe Systems Inc. n TouchSend Index is a registered trademark of TouchSend Corporation. n Visio is a registered trademark of Visio Corporation. n IBM , OS/2 , DB2/6000 and AIX are a registered trademark of IBM Corporation. n Indeo is a registered trademark of Intel Corporation. n Netscape Navigator , and Netscape Communicator are registered trademarks of Netscape Communications, Inc. n OSF/Motif is a registered trademark of Open Software Foundation. n ORACLE is a registered trademark of ORACLE Corporation, California, USA. n INFORMIX -OnLine for SAP is a registered trademark of Informix Software Incorporated. n UNIX and X/Open are registered trademarks of SCO Santa Cruz Operation. n ADABAS is a registered trademark of Software AG n The following are trademarks or registered trademarks of SAP AG; ABAP, InterSAP, RIVA, R/2, R/3, R/3 Retail, SAP (Word), SAPaccess, SAPfile, SAPfind, SAPmail, SAPoffice, SAPscript, SAPtime, SAPtronic, SAP-EDI, SAP EarlyWatch, SAP ArchiveLink, SAP Business Workflow, and ALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names included herein are also trademarks or registered trademarks of SAP AG. n Other products, services, logos, or brand names included herein are trademarks or registered trademarks of their respective owners.n

7KH 6$3 ,QWHJUDWLRQ 0RGHO

SAP AG 2000

n n n

SAPs R/3 System has set new norms for standard software that can be universally implemented. R/3 uses advanced development techniques to achieve comprehensive integration of business administration and data processing. R/3 combines state-of-the-art technology with comprehensive business administration functionality to provide a fully integrated business solution for your company.

CA B) 0 A 9 % @ 8

+5

,6

7 4 653 2

:)

" 1) 0 ( & '% $

'( BH A FGEA D " C( @ F X@ EFWV F $ #"! 0 @SR F A

40

&OLHQW 6HUYHU $%$3 30

#! "

33

5

@ @E F $ A 9 ( E $ " `! F 6 Y! F

00

EA U ( ( @ F ( T F

CAEQ 66 P I F #C B)

6'

),

&2

$0

36

%XVLQHVV ,QWHJUDWLRQ 7HFKQRORJLHV ,,/HYHO 3 days Application Link Enabling (ALE) Technology

/HYHO Vpweca f v b

3 days

4 days

Business Integration Technology

EDI Interface

5 days R/3 Interface and BAPI Programming in C++ SAP AG 1999

5 days Programming with BAPIs in JAVA

%!U BUh6y

v s f i xeb

5 days Programming with BAPIs in Visual Basic

2 days Communication Interfaces in ABAP

g r b 1pSGca

Data Transfer

dhcca s r b

2 days Building Enterprise Solutions with SAP Components

5 days

g e wwwfBdhG

2 days SAP IDoc Interface Technology

1 day SAP IDoc Interface Development

p s v b Uheca

d p s Vwxieb

d s b hveca

g s f hhtieb

u f i hshteb

g f d b hecad g p i hVqeb

&RXUVH 3UHUHTXLVLWHV

l (VVHQWLDO

l 6$3 6$3 2YHUYLHZ

l %DVLF WHFKQLFDO NQRZOHGJH RI 6$3 6\VWHP l 5HFRPPHQGHG l %DVLF NQRZOHGJH RI ,QWHUQHW 7HFKQRORJ\

l %& %XVLQHVV ,QWHJUDWLRQ 7HFKQRORJ\

l :RUNLQJ .QRZOHGJH RI ([WHQVLEOH 0DUNXS /DQJXDJH ;0/ l :RUNLQJ NQRZOHGJH RI +70/ DQG +773 l %DVLF NQRZOHGJH RI ,QWHUPHGLDWH 'RFXPHQWV ,'2&V

SAP AG 1999

7DUJHW *URXSl $XGLHQFHn n n n

7HFKQLFDO 3URMHFW 0DQDJHUV

l 'XUDWLRQ GD\V

6\VWHP $UFKLWHFWXUH 0DQDJHU ZLWK IRFXV RQ WHFKQLFDO LQWHJUDWLRQ LVVXHV

&RQVXOWDQWV IURP %XVLQHVV )UDPHZRUN ,PSOHPHQWDWLRQ 3DUWQHUV

6$3 %DVLV &URVV $SSOLFDWLRQ &RQVXOWDQWV

&RXUVH 2YHUYLHZ

&RQWHQWVl &RXUVH *RDOV l &RXUVH 2EMHFWLYHV l &RXUVH &RQWHQW l &RXUVH 2YHUYLHZ 'LDJUDP l 0DLQ %XVLQHVV 6FHQDULR

SAP AG 1999

SAP AG

BC635

1-1

&RXUVH *RDOV

l 'HVFULEH 6$3 %XVLQHVV &RQQHFWRU DUFKLWHFWXUH l ,QVWDOO FRQILJXUH DQG DGPLQLVWUDWH WKH 6$3

7KLV FRXUVH ZLOO SUHSDUH \RX WR

DQG LQWHJUDWLRQ WHFKQRORJLHV

l 'HVFULEH KRZ WKH 6$3 %XVLQHVV &RQQHFWRU XVHV

%XVLQHVV &RQQHFWRU IRU GLIIHUHQW VFHQDULRV ;0/

SAP AG 1999

SAP AG

BC635

1-2

&RXUVH 2EMHFWLYHV

$W WKH FRQFOXVLRQ RI WKLV FRXUVH \RX ZLOO EH DEOH WRl ,GHQWLI\ VLWXDWLRQV ZKHUH WKH 6$3 %& LV DQ l ,QVWDOO FRQILJXUH DQG DGPLQLVWUDWH WKH 6$3

DSSURSULDWH VROXWLRQ

%XVLQHVV &RQQHFWRU

SAP AG 1999

SAP AG

BC635

1-3

&RXUVH &RQWHQW

3UHIDFH Unit 1 Unit 2 Unit 3 Unit 4 Unit 5 &RXUVH 2YHUYLHZ 7KH 6$3 %& *HWWLQJ 6WDUWHG ;0/ %DVLFV Unit 6 Unit 7 Unit 8 Unit 9 6$3 WR QRQ6$3 &RPPXQLFDWLRQ

6$3 %& $UFKLWHFWXUH

0DQDJLQJ WKH 6$3 %& 6$3 %& DQG P\6$3 &RQFOXVLRQ

([HUFLVHV 6ROXWLRQV

6$3 WR 6$3 &RPPXQLFDWLRQ

SAP AG 1999

SAP AG

BC635

1-4

&RXUVH 2YHUYLHZ 'LDJUDP &RXUVH 2YHUYLHZ 'LDJUDP &RXUVH 2YHUYLHZ7KH 6$3 %& *HWWLQJ 6WDUWHG 6$3 %& $UFKLWHFWXUH ;0/ %DVLFV 6$3 WR 1RQ6$3 &RPPXQLFDWLRQ

0DQDJLQJ WKH 6$3 %&6$3 %& DQG P\6$3&RQFOXVLRQ

6$3 WR 6$3 &RPPXQLFDWLRQ SAP AG 1999

SAP AG

BC635

1-5

0DLQ %XVLQHVV 6FHQDULR

l ,QWHJUDWLRQ RI 6$3 DQG QRQ6$3 FRPSRQHQWV XVLQJ

WKH 6$3 %XVLQHVV &RQQHFWRU

SAP AG 1999

n

The SAP Business Framework is an integrated, open, component-based product architecture that encompasses SAP R/3 enterprise applications and third-party products and technologies.

SAP AG

BC635

1-6

gt UBRss UBR B#5T 5VVwTT w A A Br U #r 5UT 5

REEFR F q q v v q q GEETG S5T T h h q q SEFGG T T Y Y T SF F5 F #

q q StTT (S 0 b (G S b G

$ $ %##"#! ) 3 & 2 & 756($54'$ (( ) $ 1

stRs !!0w w q q A A BR B b #a 0 baRVRiF F q q 5# UX UX q q q q f f #66ESVPPRRXX ia a Y Y v v5 # v# vF U U#T T r ( X edQQccBDTTRRBBX BD EV( UX UX F r

tss UBR UBR B#5 UT UT B#T T y y Br B #r 5 H

q q 00T4tgbvv (!!`b`XX b q q u w 0F 0x ( wFT bu

st UBRs UBR #r5T T q q SEVT T h h B #5 G 0T T F F# Br Gq q tg`RR 5SSssg6bRR 0S%tgBb Bb p p b T 5X X P ST S % bT ` P bTFX deQc6TTRRBBX 8G G q q ViFRR F I I F b q b# SEPPP P q F FVVaPP a B B

GSEFG F0STgTg``b b q q VRR iF F I I B 0w S BwFX BWdicg8G G q q QQFRR F I I F b X B R R Tq T b # bb qPP

$ @ (5(8 (

X BdWiiTRRBX gg#G G q q QiFRR F I F Tb # F b EEFRR F q q SE5X X f f I v v a a5w w

) 9 $ @ 756@#85 0!('# &$ ) $

G0F FeBB dVRR EP P #p p G q 0 q#

X BdWiiTRRBX gTg BG BG h h F b F bf Tg6ERRT VT T f

F T b b0( ` ` F X decQTRRBBX 860a(G WBBG WEEX X Y Y F a F

F(X WWVVUTRRBBX UT U068SEQQFPPRRTT F I I F( 0 U

G 0 BD H 0F FBEEDB CA A G B

SAP AG SAP AG 1999

6$3 %XVLQHVV 7HFKQRORJ\ 0DS (GLWLRQ

BC635

1-7

7KH 6$3 %& *HWWLQJ VWDUWHG &RQWHQWVl 6\VWHP UHTXLUHPHQWV l ,QVWDOODWLRQ RI 6$3 %&

SAP AG 1999

SAP AG

BC635

2-1

7KH 6$3 %& *HWWLQJ VWDUWHG 8QLW 2EMHFWLYHV

$W WKH FRQFOXVLRQ RI WKLV XQLW \RX ZLOO EH DEOH WR l 'HVFULEH WKH 6$3 %XVLQHVV &RQQHFWRU l ,QVWDOO DQG UXQ WKH 6$3 %XVLQHVV &RQQHFWRU

SAP AG 1999

SAP AG

BC635

2-2

7KH 6$3 %& *HWWLQJ VWDUWHG &RXUVH 2YHUYLHZ 'LDJUDP&RXUVH 2YHUYLHZ7KH 6$3 %& *HWWLQJ 6WDUWHG 6$3 %& $UFKLWHFWXUH ;0/ %DVLFV 6$3 WR 1RQ6$3 &RPPXQLFDWLRQ

0DQDJLQJ WKH 6$3 %&6$3 %& DQG P\6$3&RQFOXVLRQ

6$3 WR 6$3 &RPPXQLFDWLRQ SAP AG 1999

SAP AG

BC635

2-3

7KH 6$3 %& *HWWLQJ VWDUWHG %XVLQHVV 6FHQDULR

l SAP BC). 2-4-2 Choose the package Default, specify the remote server according to exercise 2-3 and specify which existing service you want to call in the remote server (e.g. service ERRNLQJOLVW in interface ,)B ). Save your inputs. Now the connection between the two SAP systems via your business connector is set. 2-5 Test the connection between the two SAP systems via SAP BC 2-5-1 Logon to the second SAP system and navigate to the function builder (transaction SE37). 2-5-2 Enter BAPI_SBOOK_GETLIST and choose single test 2-5-3 Enter the destination to your SAP BC (defined in exercise 2-2) and the data you previously used for this BAPI. If the data are different in your two SAP systems, the result of a local call and the call with destination SAP BC will be different.

SAP AG

BC635

5-55

6ROXWLRQV8QLW 6$3 WR 6$3 FRPPXQLFDWLRQ 7RSLF &RQILJXUH D VHUYLFH LQ 6$3 %& WR UHDFK D %$3, LQ D 6$3 V\VWHP

1-1

Logon to your SAP BC 1-1-1 Start the SAP Business Connector. You can open a command prompt window and execute the command \sapbc\server\bin\server.bat log none or you create a shortcut to server.bat, setting the option log none in the properties of the shortcut. A command window opens where you can view the initialization process. Don t close the command window because this will shut down the SAP BC server as well! 1-1-2 Start up a Web browser via the shortcut in the windows startmenu. Type the URL http://localhost:5555 into the address field. Instead of ORFDOKRVW you can also enter the domain or IP address of your computer. To connect your local SAP Business Connector, log on with (user/password): Administrator/manage. These are the initial parameters. Make sure you use the correct upper and lower case letters. Unit 8: Managing the SAP BC will show you how to change the password. The start page of the SAP Business Connectors appears with the Performance Statistics. (tab page Statistics). You can navigate around in the SAP BC using Menus, Tab pages, and Buttons.

1-2

Configure your SAP BC as an RFC Client to a SAP system 1-2-1 Choose 6$3 from the navigation panel of your SAP BC. Choose the 6$3 6HUYHUV tab. Initially, there is no SAP Server listed. Choose $GG 6HUYHU. Complete the following fields with the values from an SAP server configured in SAP GUI. (Leave all other fields with their default values.)

SAP AG

BC635

5-56

1DPH

,Q WKH ILHOG

6SHFLI\ An alias for the SAP server. This is the name by which the server will be known to SAP BC developers, clients and partners. The SAP router string. Only needed if there is a firewall between the SAP server and SAP BC. Your SAP user name. Your SAP password. The three-digit SAP client number. The SAP language code. If connecting to a Release 3.x system, this is one character. For Release 4.x , it is two characters. The IP address or host name of the SAP system. The two-digit SAP system number (00-99).

6$3 5RXWHU 6WULQJ 8VHU

3DVVZRUG &OLHQW

/DQJXDJH $SSOLFDWLRQ 6HUYHU

6\VWHP 1XPEHU

Choose 6DYH to commit these changes to the SAP Business Connector. Information to application server, system number and SAP router string: Start up your SAP logon. Select the required SAP System from the list (if necessary, add it to the list via *URXSV). To look up the system number and the SAP router string: Select 3URSHUWLHV via the right mouse button. To look up the application server: Select 6HUYHU. In the next dialog box select *HQHUDWH /LVW. All the application servers for the selected SAP System are listed. 1-2-2 Testing the Connection: Use the following procedure to verify that the SAP BC can successfully connect to the SAP server that you have defined. Choose 7HVW &RQQHFWLRQ on the 6$3 6HUYHUV tab page after you have defined an SAP Server. If the SAP Business Connector can successfully connect to the specified SAP Server, it will display connection information. If you receive an error message, verify that your SAP server configuration information is correct. 1-3 Testing a BAPI call from SAP Business Connector 1-3-1 Before you start the BAPI call from the SAP Business Connector, first test the function in your SAP System. Choose 7RROV $%$3 :RUNEHQFK 'HYHORSPHQW )XQFWLRQ %XLOGHU (Transaction SE37). Enter BAPI_SFLIGHT_GETLIST in field )XQFWLRQ PRGXOH. Choose )XQFWLRQ PRGXOH 7HVW 6LQJOH WHVW. The values are listed in the exercise. Choose ([HFXWH. 1-3-2 In SAP BC: In order to call a BAPI from SAP BC you first need to make its interface known to the SAP Business Connector. Choose 6$3 from the SAP Business Connector navigation panel. Choose the 5)& /RRNXS tab. Choose the SAP System from the drop down list you have defined in the last exercise. Enter BAPI_SFLIGHT_GETLIST in section )XQFWLRQ E\ 1DPH in field )XQFWLRQ 1DPH. Choose /RRNXS. Then you can test the function by choosing the button test function. Use the same values as described in the exercise. SAP AG BC635 5-57

1-3-3 After this test, choose the BAPI_SBOOK_GETLIST and make an RFC lookup. Test the BAPI with the values you noted. 1-4 Define an outbound map as service in your SAP BC 1-4-1 Make an RFC Lookup for BAPI_SBOOK_GETLIST. 1-4-2 Define a new map as a service using the link ('HILQH QHZ PDS) in the line SAP BC -> SAP.Note: It is also possible to lookup the function by typing it in section )XQFWLRQ 6HDUFK in field )XQFWLRQ 1DPH. In the following list select the function %$3,B6%22.B*(7/,67 and follow link 'HILQH 1HZ 0DS.All services are organized in packages and interfaces. Packages contain interfaces and services with related functionality like the SAP or the mySAP.com package. For this exercise enter ,)B (## as your group number) in field 1HZ ,QWHUIDFH, Enter ERRNLQJOLVW in field 1HZ 6HUYLFH. Choose 'HIDXOW in field 3DFNDJH. Choose 6DYH. You have now created a new service in SAP Business Connector to call a specific function module on your SAP system. Now you can find the service in the Service Menu and test it. The parameters must not contain any blank spaces. 1-5 Test this service from SAP BC 1-5-1 Choose 6HUYLFHV from the SAP BC navigation panel. Follow the link of interface ,) . You will get a list of services defined in the interface ,) . Select the checkmark in the column 7HVW for the service ERRNLQJOLVW. A screen appears showing the BAPIs interface as an HTML form. Enter the values you noted for the fields AIRLINECARRIER, CONNECTIONNUMBER and DATEOFFLIGHT. Choose 7HVW ZLWK LQSXWV. If there is no example data available in your selected SAP System, a message will be displayed that no data was found. The BAPI %$3,B6%22.B*(7/,67 was successfully called, but no data exists in your SAP System. If the BAPI %$3,B 6%22. B*(7/,67 could not be called, an error message is displayed. In this case you should check your input values. 1-6 Call this service from a browser 1-6-1 The installed service ERRNLQJOLVW can be called via the Internet by its URL. The required URL must be structured like: http://:/invoke//3DUDPHWHU 0HDQLQJ Name or IP address of the SAP Business Connector computer on which the service is installed. Port number The default port number is 5555. Interface name Service name

KRVW

SRUW LQWHUIDFH VHUYLFH

SAP AG

BC635

5-58

Call the service ERRNLQJOLVW by URL with the parameters from the last exercise. In the address field of the Web browser enter the URL, which could look like this: http://localhost:5555/invoke/IF_##/bookinglist?AIRL INECARRIER=LH&CONNECTIONNUMBER=0400&DATEOFFLIGHT=20 00-08-06 The Web page that is loaded displays the same result values as the BAPI test that you carried out in the last test using the button 7HVW ZLWK LQSXWV. The difference with calling the service via the Internet is that the Business Connector functions are not available. The menu and tab pages are not displayed. Note: The primary use of the SAP Business Connector is not in dialog processing via an interface. In a real-world scenario you are more likely to submit this call from within an application rather than entering its URL in the browser. In this case the selection data would either come from some database or be entered in an HTML user interface. However, the first steps to create and test a service will be the same as in this exercise.1-7 Optionally: create a template in SAP BC to modify the result of calls from a browser client. Execute the steps listed in the exercise.

SAP AG

BC635

5-59

6ROXWLRQV8QLW 6$3 WR 6$3 FRPPXQLFDWLRQ 7RSLF &UHDWH LQERXQG PDS DV VHUYLFH LQ 6$3 %&

2-1

Configure an RFC listener in SAP BC 2-1-1 Define the SAP system you are awaiting calls from:

Choose 6$3 from the SAP Business Connector navigation panel and choose the 6$3 6HUYHUV tab. Set up your SAP test system as another SAP server in the SAP Business Connector. (see exercise 2: Defining an SAP Server in SAP BC).

2-1-2 In the list of installed SAP servers, in the row /LVWHQHU the number of configured RFC listeners is shown as a link (in this case as ). To configure an RFC listener, follow this link for your SAP test system.2-1-3 Choose $GG /LVWHQHU. Enter or choose the following parameters: 1XPEHU RI 7KUHDGV *DWHZD\ +RVW (QDEOHG 3URJUDP ,' BC_##_ID 1

*DWHZD\ 6HUYLFH sapgw 5)& 7UDFH Yes Off

Note: The parameter 3URJUDP ,' must be unique. In the fields *DWHZD\ KRVW and *DWHZD\ VHUYLFH enter the parameters of the selected SAP test system. The required values are usually suggested by the system. Choose 6DYH. Click the red ball in column 6WDUWHG" to start the Listener The ball turns green. If an error occurs, the ball will turn yellow. Click the yellow ball to receive an error message. Error messages at this stage typically indicate a problem with listener configuration.

2-2

Configure an RFC destination in your SAP system 2-2-1 The steps described below are to be carried out in the SAP System. &KRRVH 7RROV $GPLQLVWUDWLRQ 'HVWLQDWLRQV WUDQVDFWLRQ 60 $GPLQLVWUDWLRQ 1HWZRUN

5)&

2-2-2 Choose &UHDWH. Enter %&B B'(67 in field 5)& GHVWLQDWLRQ as a name for the new RFC destination. Enter T in field &RQQHFWLRQ W\SH (destination type TCP/IP). Enter SAP Business Connector for group ## in section 'HVFULSWLRQ. Choose 6DYH. SAP AG BC635 5-60

2-2-3 Choose Registration as Activation Type. Enter %&B B,' in field Program ID. Choose Save. Choose Destination *DWHZD\ RSWLRQV (QWHU in field Gateway host. Enter sapgw in field Gateway service. Note: The parameters Program ID, Gateway host and Gateway service must have the same names as the parameters selected in the SAP Business Connector from exercise 2-1-3. 2-2-4 Choose 2.. and choose 7HVW FRQQHFWLRQ. 2-3 Define a remote server in SAP BC using your own business connector. 2-3-1 Choose 6HWWLQJV from the SAP Business Connector navigation panel. Choose the 5HPRWH 6HUYHUV tab. 2-3-2 Add a remote server by adding the data of your business connector. Enter the following parameters (leave all other fields at their default values): $OLDV +RVW 1DPH RU ,3 $GGUHVV 3RUW 1XPEHU 8VHU 1DPH 3DVVZRUG 5555 Administrator manage REMOTE_BC_## localhost

Choose $GG and then 2..

Note: you can alternate this by specifying the SAP BC of the group next to you if you know the host name, the port, the password and the name of the interface and service. 2-4 Define an outbound map as service in SAP BC 2-4-1 In order to receive a BAPI call you first need to make its interface known to the SAP Business Connector by creating a map of type 6$3 WR 6%&. Choose 6$3 from the SAP Business Connector navigation panel. Choose the 5)& /RRNXS tab. Choose the SAP test system from the drop down list that you have defined in exercise 2-1-1. Enter BAPI_SBOOK_GETLIST in section )XQFWLRQ E\ 1DPH in field )XQFWLRQ 1DPH. Choose /RRNXS. For map type 6$3 FDOOLQJ 6$3 %& follow link 'HILQH 1HZ 0DS2-4-2 Choose 'HIDXOW in field 3DFNDJH. Choose 5(027(B%&B in field 6HUYHU $OLDV. Enter IF_## in field ,QWHUIDFH. Enter bookinglist in field 6HUYLFH)ORZ. Choose 6DYH.

SAP AG

BC635

5-61

2-5

Test the connection between the two SAP systems via SAP BC 2-5-1 Logon to the second SAP system and navigate to the function builder (transaction SE37). 2-5-2 Enter BAPI_SBOOK_GETLIST and choose single test 2-5-3 Enter the destination to your SAP BC (defined in exercise 2-2) and the data you previously used for this BAPI. If the data are different in your two SAP systems, the result of a local call and the call with destination SAP BC will be different.

SAP AG

BC635

5-62

6$3 WR QRQ6$3 &RPPXQLFDWLRQ &RQWHQWVl &RQQHFWLQJ QRQ6$3 V\VWHPV ZLWK 6$3 V\VWHPV l ,PSOHPHQWLQJ VHUYLFHV RQ 6$3 %& l 0DSSLQJ ;0/ GRFXPHQWV l %XLOGLQJ )ORZV ZLWK WKH 6$3 %& 'HYHORSHU

SAP AG 1999

SAP AG

BC635

6-1

6$3 WR QRQ6$3 &RPPXQLFDWLRQ 8QLW 2EMHFWLYHV$W WKH FRQFOXVLRQ RI WKLV XQLW \RX ZLOO EH DEOH WR l 6HQG ;0/ GRFXPHQWV IURP D FOLHQW WR 6$3 %& l 3RVW ;0/ GRFXPHQWV ZLWK 6$3 %& WR DQ ;0/ VHUYHU l &UHDWH )ORZV ZLWK WKH 6$3 %& 'HYHORSHU l 0DS LQFRPLQJ ;0/ GRFXPHQWV WR 6$3 ,QWHUIDFHV

SAP AG 1999

SAP AG

BC635

6-2

6$3 WR QRQ6$3 &RPPXQLFDWLRQ&RXUVH 2YHUYLHZ 'LDJUDP&RXUVH 2YHUYLHZ7KH 6$3 %& *HWWLQJ 6WDUWHG 6$3 %& $UFKLWHFWXUH ;0/ %DVLFV 6$3 WR 1RQ6$3 &RPPXQLFDWLRQ

0DQDJLQJ WKH 6$3 %&6$3 %& DQG P\6$3&RQFOXVLRQ

6$3 WR 6$3 &RPPXQLFDWLRQ SAP AG 1999

SAP AG

BC635

6-3

6$3 WR QRQ6$3 FRPPXQLFDWLRQ %XVLQHVV 6FHQDULRl $ QRQ6$3 V\VWHP RIIHUV LQIRUPDWLRQ LQ D SURSULHWDU\ IRUPDW 7R JHW WKH LQIRUPDWLRQ LQWR WKH 6$3 V\VWHP GDWD PDSSLQJ DQG WUDQVIRUPDWLRQ LV QHFHVVDU\

l $V D SURMHFW WHDP PHPEHU \RX DUH UHVSRQVLEOH WR SHUIRUP WKLV ZRUN LQ WKH 6$3 %XVLQHVV &RQQHFWRU GHYHORSHU

SAP AG 1999

SAP AG

BC635

6-4

6$3 6\VWHP WR QRQ6$3 6\VWHP &RPPXQLFDWLRQ 2YHUYLHZ

6$3 WR QRQ6$3 &RPPXQLFDWLRQ 2YHUYLHZ SAP BC as XML server SAP BC as XML client Processing and mapping Java classes

SAP AG 1999

SAP AG

BC635

6-5

6FHQDULRV ZLWK ;0/

,QWHUQHW:HE $SSOLF DWLRQV

) , 5 ( : $ / /

;0/ +773

) , 5 ( : $ / /

6$3 6\VWHP

SAP AG 1999

n n

Scenarios with XML There are two main scenarios using XML via BC in the context of SAP to non-SAP communication: SAP communicating with an XML web application SAP communicating with a non-SAP backend system using an XML interface

n

Technically those two scenarios are exactly the same. They are both using HTTP as the transport protocol and XML documents are used to exchange information. Therefore its not necessary to know what kind of system your communication partner is using. You only have to agree which XML dialect is to be used for the communication, everything else is transparent for you.

SAP AG

BC635

6-6

([DPSOH VFHQDULR FUHDWH RUGHU

6$3;0/

%&

6$3 V\VWHP5)&25'(56,'RF

SAP AG 1999

n n

Example scenario: an external java application is used to send an xml document to the SAP system which shall create an IDoc of type ORDERS.

SAP AG

BC635

6-7

;0/ WR 6$3 VFHQDULR XVLQJ 6$3 %&

6$3 %&5)&$ ! S "# T

SAP AG 1999

n n n

The role of BC in XML scenarios The Business Connectors tasks for XML scenarios with SAP systems can be divided in three parts: Decode the incoming and encode the outgoing XML document: This is either done automatically or the necessary services are already provided by the Business Connector, so that you can work on a more abstract level with the document. Process a document using logic on the Business Connector, if necessary do some mappings that the document can be processed by the SAP system: This logic has to be provided by you, as this is application level in which you need to know about the semantics of a document.

n

n n

decode incoming and encode outgoing RFC containers: This is always done automatically if a BAPI is invoked in a SAP system or if an IDoc is sent to one. The SAP BC Developer is the tool to configure, set and develop the flows the SAP BC server is working with

SAP AG

9 75 I I RQPPPB HBC635

;0/

6$3 V\VWHP

U

& ( D B 5 9 GFE7C0 A( @ !

9864322)'% 75 3 1 0 ( & "#

$

6-8

7KH 6$3 %& 'HYHORSHU6HUYLFH %URZVHU 3DQH 6HUYLFH (GLWRU 3DQH 6HUYLFH (OHPHQW 3DQH

SAP AG 1999

n n

The SAP BC Developer The SAP BC Developer is an environment for creating and testing SAP BC services; it is also used for accessing SAP BC services, and code-harnesses for server side Integration Modules. The code generated for integration modules provides a stub class suitable for registering new SAP BC services with the SAP BC. The Service Browser, which lets you open packages and view the structure of interfaces and services; the Editor pane, which lists the flow operations of a chosen service; and the Element pane, which for a selected element in the Editor pane shows properties, pipeline information, and in the case of a query, variables.

n

Service Element Tabs (pipeline, properties, variables)

SAP AG

BC635

6-9

6$3 6\VWHP WR QRQ6$3 6\VWHP &RPPXQLFDWLRQ 2YHUYLHZ

6$3 WR QRQ6$3 &RPPXQLFDWLRQ Overview 6$3 %& DV ;0/ VHUYHU SAP BC as XML client Processing and mapping Java classes

SAP AG 1999

SAP AG

BC635

6-10

1HFHVVDU\ VWHSV IRU FUHDWLQJ ;0/ VFHQDULRV

,GHQWLI\ GDWD LQ WKH ;0/ GRFXPHQW ,GHQWLI\ %$3, RU ,'2& ZKLFK FDQ EH XVHG

8VH WKH 6$3 %& 'HYHORSHU WR GR QHFHVVDU\ PDSSLQJV IURP WKH ;0/ VWUXFWXUHV WR WKH %$3, RU ,'2& LQWHUIDFHV SAP AG 1999

SURYLGH VRPH SURFHVVLQJ ORJLFV

n n n n

When preparing a non-SAP SAP scenario you have to go through a few steps: Identify data in the XML document: The document contains a set of tags, and some of those tags are representing the data you want to process. Identify a BAPI or an IDoc, with which you can execute the scenario Use the SAP BC Developer to provide the processing logic and to do necessary mappings from the XML structures to the BAPI/IDoc interface. This is necessary as the structures of the XML document and the BAPI/IDoc might not fit to each other.

SAP AG

BC635

6-11

3DVVLQJ DQ ;0/ 'RFXPHQW WR D 6$3 %& 6HUYLFH

3RVVLEOH ZD\V IRU SDVVLQJ l 0DNH DQ +773 SRVW RI DQ DUELWUDU\ ;0/ GRFXPHQW WR D VHUYLFH ZLWK FRQWHQW W\SH WH[W[PO l 3DVV WKH HQWLUH ;0/ GRFXPHQW DV D VWULQJ LQ D YDULDEOH QDPHG [POGDWD ZKHQ \RX LQYRNH WKH VHUYLFH l 6HQG WKH ;0/ GRFXPHQW WR WKH 6$3 %& XVLQJ WKH )LOH 7UDQVIHU 3URWRFRO )73

SAP AG 1999

n n

Ways to pass an XML document to a service There are three ways to pass an XML document to a SAP BC service: You can pass the entire XML document as a string in a variable named $xmldata when you invoke the service. HTTP post an arbitrary XML document to a service with content type text/xml You can send the XML document to the SAP BC using the File Transfer Protocol (FTP)

n

When the SAP BC receives an XML document via one of these methods, it automatically transforms (parses) the XML into a document object, which can be used by any SAP BC service that takes a node as input (e.g., queryDocument, documentToRecord). You can further HTTP post documents to any service using RFC-XML or IDoc-XML provided that it is indeed formatted according to SAPs specification. The content type has to be set accordingly (application/x-sap.rfc or application/x-sap.idoc)

n

SAP AG

BC635

6-12

3DVVLQJ DQ ;0/ 'RFXPHQW WR D 6$3 %& 6HUYLFH IURP D :HE %URZVHU

6$3 %& KRVW

,QWHUIDFH QDPH 6HUYLFH QDPH "!

KWWSZZZKRWKGHLQYRNHVIOLJKWJHW)OLJKW'DWH" [POGDWD "[PO YHUVLRQ

7KH LQYRNH NH\ZRUG

7KH [POGDWD YDULDEOH QDPH 7KH ;0/ GRFXPHQW

SAP AG 1999

n n n n n

Passing an XML Document to a SAP BC service from a web browser To submit an XML document to a SAP BC service from a Web browser, create a browser application that: Generates an XML document Submits the XML document to the SAP BC services URL as the value of a variable called $xmldata. The variable name $xmldata has special meaning to the SAP BC - the server assumes that the value of this variable is an XML document. When the SAP BC receives a request to invoke a service, and that request includes an input variable named $xmldata, the server automatically parses the content of that variable (the XML document) before passing it as input to the requested service. This diagram shows the URL you would use to submit an XML document to a service called Purch:ShipNotice on a SAP BC Integration Sever called www.rubicon.com. (For the purposes of illustration, this example uses the GET method to pass the XML data to the server; however, in practice you would more likely use the POST method.) This method is equivalent to posting an XML document with content type text/xml to the server.

n

n

SAP AG

BC635

6-13

3DVVLQJ DQ ;0/ 'RFXPHQW WR D 6$3 %& 6HUYLFH 8VLQJ )73

7R XVH WKLV PHWKRG l 7KH ;0/ GRFXPHQW PXVW EH FRQWDLQHG LQ D ILOH WKDW KDV D ILOH H[WHQVLRQ RI [PO l 7KH 6$3 %& VHUYLFH WR ZKLFK \RX ZDQW WR SDVV WKH GRFXPHQW PXVW WDNH D QRGH DV LQSXW

SAP AG 1999

n n

Passing an XML Document to a SAP BC Service Using FTP The SAP BC can also pass an XML document to a SAP BC that it receives on its FTP listening port. By default the FTP listener is assigned to port 8021. However, this assignment is configurable, so you should check with your SAP BC server administrator to see which port is used for FTP communications on your SAP BC. When the SAP BC receives an XML document on its FTP listening port, it automatically parses the document and passes it as input to the service in the directory where the file was FTPed. To use this method: The XML document must be contained in a file that has a file extension of xml. The SAP BC service to which you want to pass the document must take a node as input. This method is equivalent to posting an XML document with content type text/xml to the server.

n

SAP AG

BC635

6-14

6$3 6\VWHP WR QRQ6$3 6\VWHP &RPPXQLFDWLRQ 2YHUYLHZ

6$3 WR QRQ6$3 &RPPXQLFDWLRQ Overview SAP BC as XML server 6$3 %& DV ;0/ FOLHQW Processing and mapping Java classes

SAP AG 1999

SAP AG

BC635

6-15

1HFHVVDU\ VWHSV IRU FUHDWLQJ ;0/ FOLHQW VFHQDULRV

6HQG WKH ;0/ GRFXPHQW

8VH WKH 6$3 %& 'HYHORSHU WR GR QHFHVVDU\ PDSSLQJV IURP WKH %$3, RU ,'2& GDWD WR ;0/ VWUXFWXUHVVn n n

SURYLGH VRPH SURFHVVLQJ ORJLFV

SAP AG 1999

When preparing a non-SAP SAP scenario you have to go through a few steps: Use the SAP BC Developer to provide the processing logic and to do necessary mappings from the BAPI/IDOC data to the XML structures. Send the XML document

SAP AG

BC635

6-16

7KH 6$3 %& DV DQ ;0/ FOLHQW ,URXWLQJ UXOHsender receiver transport url processing

hugo catalog XML http://..

message type orders

7KH URXWLQJ UXOH ZLWK ;0/ WUDQVSRUW DXWRPDWLFDOO\ l FUHDWHV ,'RF;0/ IRU ,'RFV DQG 5)&;0/ IRU %$3,V l +773SRVWV 6$3;0/ GRFXPHQWV WR WKH 85/

SAP AG 1999

n n

The Business Connector as an XML client (1) There are two recommended ways for acting as an XML client with the Business Connector: 1) Use the routing mechanisms of BC and choose the transport XML. This transport executes an HTTP post to the specified URL. If the pipeline contains an IDOC the XML transport automatically creates IDOC XML, if a BAPI representation is found there an RFC XML document is generated.

SAP AG

BC635

6-17

7KH 6$3 %& DV DQ ;0/ FOLHQW

3URYLGH \RXU 3URYLGH \RXU RZQ VHUYLFH RZQ VHUYLFH

FUHDWH WKH ;0/ GRFXPHQW FUHDWH WKH ;0/ GRFXPHQW XVLQJ VWDQGDUG VHUYLFHV XVLQJ VWDQGDUG VHUYLFHV

XVH SXEFOLHQWKWWS WR SRVW WKH XVH SXEFOLHQWKWWS WR SRVW WKH GRFXPHQW WR DQ ;0/ VHUYHU GRFXPHQW WR DQ ;0/ VHUYHU DSSOLFDWLRQ DSSOLFDWLRQ

SAP AG 1999

n

The Business Connector as an XML client (2) 2) Provide your own service using the pub.client:http service (located in WmPublic) to post an XML document to an XML server. In this case the document has to be created before, for example by using the standard services provided by Business Connector for that.

SAP AG

BC635

6-18

6$3 6\VWHP WR QRQ6$3 6\VWHP &RPPXQLFDWLRQ 2YHUYLHZ

6$3 WR QRQ6$3 &RPPXQLFDWLRQ Overview SAP BC as XML server SAP BC as XML client 3URFHVVLQJ DQG PDSSLQJ Java classes

SAP AG 1999

SAP AG

BC635

6-19

3URFHVVLQJ ORJLF DQG PDSSLQJ

6$3 %&$ ! S6-20

l %XLOG -DYD RU )ORZ VHUYLFHV ZLWK WKH 'HYHORSHUl ,PSOHPHQW VHUYLFHV LQ -DYD && RU 9% SAP AG 1999

n n

Processing logic and mapping When you need some additional processing logic in the Business Connector or if a mapping has to be applied to the data youll have to create your own services. You could either use the tool delivered with the Business Connector, the SAP BC Developer, for creating Java and/or Flow services or you implement your services in your favorite programming language and include it in the Business Connector using JNI Libraries (C++, VB) or if you are using Java, your class has to follow some rules.

SAP AG

BC635

"# T

U

AFERC0 5AP( @ & ( D 7 B 9 9 75 I I FPPB H !

98P322PW% 75 3 1 0 ( & "#

$

;0/

5)&

6$3 V\VWHP

6WUXFWXUH RI 6HUYLFHV

3DFNDJHV&RQWDLQ LQWHUIDFHVZKLFK FRQWDLQ VHUYLFHVVXFK DV,QYRFDWLRQVV SAP AG 1999

6HUYLFH VSHFLILFDWLRQVV

:HE WDSVV

-DYD VHUYLFHVV

n

As a refresher, remember that packages contain interfaces, which contain more interfaces and different types of services.

SAP AG

BC635

6-21

&UHDWLQJ D 6HUYLFH%HIRUH \RX FDQ FUHDWH D VHUYLFH \RX QHHG WR NQRZ :KDW SDFNDJH ZLOO WKLV VHUYLFH EH SXEOLVKHG LQ" :KDW LQWHUIDFH ZLOO WKLV VHUYLFH UHVLGH LQ" :KDW LV WKH DQWLFLSDWHG LQSXW DQG H[SHFWHG RXWSXW IRU WKLV VHUYLFH"

SAP AG 1999

n n n n n

Creating a service Creating Java services with the SAP BC Developer is easy, since the Developer does most of the work for you. Before you can create a service you need to know a few items. What package will this service be published in? What interface will this service reside in? What is the anticipated input and expected output for this service?

SAP AG

BC635

6-22

:KDW LV WKH 3LSHOLQH" )ORZ 6HUYLFHV,192.( VIOLJKWJHW)OLJKW'DWH

$,5/,1(&$55,(5/+

3LSHOLQH 9DOXHV

&211(&7,21180%(5

,192.( VIOLJKWVIOLJKW*HW'HWDLO ,192.( VIOLJKWVIOLJKW*HW'HWDLO,192.( VIOLJKWJHW)UHH6HDWV ,192.( VIOLJKWERRN)UHH6HDWV

SAP AG 1999

n n n

What is the Pipeline? The pipeline is the general term used to refer to the data structure in which input and output values are maintained for a flow service. It allows services in the flow to share data. The pipeline starts with the input to the flow service and collects inputs and outputs from subsequent services in the flow. When a service in the flow executes, it has access to all data in the pipeline at that point.

SAP AG

BC635

6-23

:KDW LV WKH 3LSHOLQH" )ORZ 6HUYLFHVd c a Y eb`8XBC635

$,5/,1(&$55,(5/+

3LSHOLQH 9DOXHV

,192.( VIOLJKWJHW)OLJKW'DWH

&211(&7,21180%(5c a ` bRRcba f

'$7(2))/,*+7

,192.( VIOLJKWVIOLJKW*HW'HWDLO ,192.( VIOLJKWVIOLJKW*HW'HWDLO,192.( VIOLJKWJHW)UHH6HDWV ,192.( VIOLJKWERRN)UHH6HDWV

SAP AG 1999

n

For example, the service sflight:getFlightDate receives the inputs AIRLINECARRIER and CONNECTIONNUMBER and returns the next date of this flight in DATEOFFLIGHT. In this service actually BAPI_SBOOK_GETLIST is called.

SAP AG

6-24

:KDW LV WKH 3LSHOLQH" )ORZ 6HUYLFHV,192.( VIOLJKWJHW)OLJKW'DWHdhPYgX c a `BC635

$,5/,1(&$55,(5/+

3LSHOLQH 9DOXHV

&211(&7,21180%(5'$7(2))/,*+7)/,*+7'$7$5(&25'!5(78515(&25'!

,192.( VIOLJKWVIOLJKW*HW'HWDLO ,192.( VIOLJKWVIOLJKW*HW'HWDLO,192.( VIOLJKWJHW)UHH6HDWV ,192.( VIOLJKWERRN)UHH6HDWV

SAP AG 1999

n

The values AIRLINECARRIER, CONNECTIONNUMBER and DATEOFFLIGHT are available to another service, sflight:sflightGetDetail, which uses those values to get the details of this flight in FLIGHTDATA, which is returned by BAPI_SFLIGHT_GETDETAIL All of these values are now available to future services that may need them - for example, sflight:bookFreeSeats may use the airline carrier, the connection number and the date of flight to perform booking of all free seats.

n

SAP AG

d c a ` c 2bRRba f

6-25

7HVWLQJ ;0/ VHUYLFHV

l 7HVW6HQG ;0/ )LOH l /RDG'RFXPHQW l +773 VXEPLVVLRQ IRUPl mu RRPu PR2wf2kGR6RAb6PRPgufs hPGRywq4w G i r u d p r u d u j q i d h h h h w e q x d d w x q x u s s q P'RRGywvterPPpi SAP AG 1999

n n n

How can I post arbitrary XML to a service from the Developer? There are ways on the server for an XML document to be received, parsed, put into the pipeline as "node" and then have a service called. To simulate this behavior from Developer, you can use the Test/Send XML File... menu item. You are prompted for whether you want Trace or Step mode and then you select a file. Developer uses Flow incremental invoke to pass a special parameter in the pipeline containing the XML from the file. On the server side, this parameter is detected, the string is parsed and a new pipeline is created with the parsed document as "node". At this point, the remainder of the Trace or Step is the same as if you had done a regular Trace/Step. Note, that this only works for Flows and that you cant kick off a regular "Run" starting with an XML file.

n n

SAP AG

BC635

6-26

)ORZ &RQWURO /DQJXDJH

l $OORZV JUDSKLFDO SURJUDPPLQJ LQ 6$3 %& l ,QWHJUDWHV PXOWLSOH VHUYLFHV LQWR D VLQJOH VHUYLFH l 'HILQHV KRZ GDWD IORZV DPRQJ WKH VHUYLFHV

SAP AG 1999

n n

Flow Control Language Flow services integrate multiple services -- IM services and other flow services -- into a single service. A flow service defines how data flows among the services and manages the flow of data. Flows are programmed graphically, so you dont have to code to build new services!

SAP AG

BC635

6-27

)HDWXUHV RI )ORZ 6HUYLFHV

l 5HWU\ VHUYLFHV WKDW IDLO l 'HILQH D VHW RI DOWHUQDWLYH VHUYLFHV VKRXOG DQ\ RQH VHUYLFH IDLO l 3ODFH WLPHRXWV RQ WKH GXUDWLRQ RI RSHUDWLRQV l 6HOHFW VHUYLFHV EDVHG RQ GDWD YDOXHV l 3HUIRUP D VHTXHQFH RI RSHUDWLRQV RQFH IRU HDFK YDOXH LQ D VHW RI YDOXHV l 7UDQVIRUP GDWD IURP RQH UHSUHVHQWDWLRQ WR DQRWKHU

SAP AG 1999

n n

Features of Flow services Flow services can be used to define a service chain, retry services that fail, define a set of alternative services should any one service fail, place timeouts on the duration of operations, select services based on data values, perform a sequence of operations once for each value in a set of values, or transform data from one representation to another.

SAP AG

BC635

6-28

6WHSV LQ %XLOGLQJ D )ORZ 6HUYLFH

&UHDWH D QHZ VHUYLFH ,QVHUW IORZ RSHUDWLRQV 6SHFLI\ WKH VLJQDWXUH RI WKH VHUYLFH 0DS SLSHOLQH GDWD 6SHFLI\ UXQWLPH SDUDPHWHUV )RUPDW RXWSXW

SAP AG 1999

n n n n n n n

Steps in building a Flow service Create a new service on the SAP BC. During this stage, you create the new service on the SAP BC where you will do your development and testing. Insert flow operations into the new service. During this stage, you specify the work that you want the service to perform by adding flow operations to the service. Specify the signature of the service. During this stage, you define the services inputs and outputs. Map pipeline data. During this stage, you route input and output values between services that are invoked in the flow. Specify the run-time parameters. During this stage, you assign parameters that configure the run-time environment for this service. Format Output. This may be an output template for an HTML or XML document, or a flow that pushes the data to a connected database. NOTE: Not all flows use all six steps -- for example, there may be no user inputs in a particular search.

n

SAP AG

BC635

6-29

)ORZ 2SHUDWLRQV

l ,QYRNH H[HFXWHV D VHUYLFH l %UDQFK RSHUDWHV EDVHG RQ D SLSHOLQH YDOXH l /RRS H[HFXWHV RSHUDWLRQV RQFH IRU HDFK HOHPHQW LQ DQ DUUD\ l 5HSHDW H[HFXWHV RSHUDWLRQV D VSHFLILHG QXPEHU RI WLPHV l 6HTXHQFH JURXSV VHWV RI RSHUDWLRQV l 0DS IRU HGLWLQJ 3LSHOLQH HJ DGGLQJGURSSLQJ YDULDEOHV

SAP AG 1999

n n n

What is a Flow Operation? A flow service contains flow operations. A flow operation is a basic unit of work (expressed in the SAP BC flow language) that the SAP BC interprets and executes at run time. Looks like Invoke can do LoadDocument, QueryDocument, CreateRegions, DocumentToRecord, RecordToDocument, COM Services, and Remote Invoke. You can also use an invocation to run another service, for example, a Java Service. Each flow operation has properties, may have a link to the pipeline, and in the case of Queries, has variables. You can move things up and down or delete them with the other keys. As we go through this course, you will have the opportunity to use each service, all of those possible operations are explained on the following slides. Common properties of those operations: Label: (Optional) Specifies a name for this instance of an operation. By default, the name is the operation [+ something specific]. Because the Developer displays the instance name in the flow editor, a flow can be more understandable if you specify instance names that are meaningful to you. Timeout: Specifies the number of milliseconds that the server waits for the operation to complete before raising an exception. If you do not want to set a timeout period, set Timeout to zero (0).

n n n n n

n

SAP AG

BC635

6-30

)ORZ RSHUDWLRQV ,QYRNH

l ,QYRNHV D SUHYLRXVO\ EXLOW VHUYLFH l $OORZV VHUYLFH FKDLQLQJ IRU FRPSOH[ IORZV l /HYHUDJHV PRGXODULW\ LQ GHVLJQ

SAP AG 1999

n n n n n n n n n

INVOKE The INVOKE flow operation invokes another service. You can use it to invoke any type of SAP BC service, including another flow service. The INVOKE operation has the following special properties. Service: (Required) Specifies the fully-qualified name of the service to invoke. Conditions that will cause an INVOKE operation to fail The INVOKE flow operation does not complete before the timeout period expires. The service that is invoked fails. The specified service does not exist. The specified service is disabled.

SAP AG

BC635

6-31

)ORZ RSHUDWLRQV %UDQFK

LI WKH YDOXH RI FKRLFH LV C1DPHC LI WKH YDOXH RI FKRLFH LV C1DPHC 1DPH RI WKH VZLWFK ILHOG LV FKRLFH

1DPH1DPH

LI WKH YDOXH RI FKRLFH LV C1DPH1C 2WKHUZLVH

1DPH1 1DPH1

SAP AG 1999

n n

BRANCH The BRANCH flow operation selects and executes a child operation based on the value of a specified field (referred to as the switch field) in the pipeline. You specify the switch field in the Switch property of the BRANCH operation. The BRANCH flow operation executes the child operation that has the same name as the value of the Switch property. You may leave one child operation unnamed (which is represented by an asterisk). If you leave a child operation unnamed and the value of the Switch property does not match any of the named child operations, the BRANCH flow operation executes the unnamed child operation. The BRANCH operation has the following special properties. Switch: (Required) Specifies the name of the field in the pipeline that the BRANCH operation uses as the switch field to select the child operation to execute. Conditions that will cause a BRANCH operation to fail: The switch field is not in the pipeline. The matching child operation fails. The BRANCH flow operation does not complete before the timeout period expires.

n n n n n n

SAP AG

BC635

6-32

)ORZ RSHUDWLRQV /RRS

1R,QSXW LV DQ DUUD\ 0RUH LQSXW DUUD\ PHPEHUV"