Ale

SAP AG 1999

%&$/(7HFKQRORJ\

%&%&$/(7HFKQRORJ\$/(7HFKQRORJ\

n R/3 System

n Release 4.6n June 2000n Material Number 5003 8179

SAP AG 1999

&RS\ULJKW6$3$*$OOULJKWVUHVHUYHG1HLWKHUWKLVWUDLQLQJPDQXDOQRUDQ\SDUWWKHUHRIPD\EHFRSLHGRUUHSURGXFHGLQDQ\IRUPRUE\DQ\PHDQVRUWUDQVODWHGLQWRDQRWKHUODQJXDJHZLWKRXWWKHSULRUFRQVHQWRI6$3$*7KHLQIRUPDWLRQFRQWDLQHGLQWKLVGRFXPHQWLVVXEMHFWWRFKDQJHDQGVXSSOHPHQWZLWKRXWSULRUQRWLFH$OOULJKWVUHVHUYHG

&RS\ULJKW

7UDGHPDUNVn 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, Saarbrckenn 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 AGn The following are trademarks or registered trademarks of SAP AG; ABAP/4, 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, andALE/WEB. The SAP logo and all other SAP products, services, logos, or brand names includedherein are also trademarks or registered trademarks of SAP AG.

n Other products, services, logos, or brand names included herein are trademarks or registeredtrademarks of their respective owners.

SAP AG 1999

$/(7HFKQRORJ\&RXUVH(QYLURQPHQW

IntegrationTechnologies forBusiness Solutions

3 days

/HYHO /HYHO

Business Framework:Overview

2 days

Data Transfer

5 days

Programming withBAPIs in Visual Basic

5 days

Programming withBAPIs in C++

5 days

Application LinkEnabling (ALE)

3 days

EDI Interface

4 days

"!$#%

&

')("!$*+*-, .(

/!%!021#43$!(

Interface Programmingin ABAP

54

2 days

Programming withBAPIs in JAVA

6

5 days

SAP IDoc Interface(Development)

1 daySAP IDoc Interface(Standard)

2 days

SAP AG 1999

l 5HTXLUHGn 6$36$32YHUYLHZn .QRZOHGJHRI56\VWHP

l 5HFRPPHQGHGn &$%XVLQHVV)UDPHZRUN2YHUYLHZn %&,QWHJUDWLRQ7HFKQRORJLHVIRU%XVLQHVV6ROXWLRQV

&RXUVH3UHUHTXLVLWHV

SAP AG 1999

l 3DUWLFLSDQWV7 0HPEHUVRI$/(SURMHFWWHDPV7 5FRQVXOWDQWVLQ%DVLVDQGLQWKHDSSOLFDWLRQV7 $SSOLFDWLRQVSHFLDOLVWV

l 'XUDWLRQGD\V

7DUJHW*URXS

SAP AG BC619 1-1

SAP AG 1999

&RXUVH2YHUYLHZ

l &RXUVH*RDOl &RXUVH2EMHFWLYHVl 2YHUYLHZRI&RQWHQWV

&RQWHQWV

SAP AG BC619 1-2

SAP AG 1999

&RXUVH2YHUYLHZ'LDJUDP

&RXUVH2YHUYLHZ

$/(&RPSRQHQWV,'RF6HUYLFHV

6\VWHP6HFXULW\7LSVDQG7ULFNV

7RROV

3HUIRUPDQFH

$GPLQLVWUDWLRQ(QKDQFHPHQWV

6SHFLDO)XQFWLRQV

%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV&RPPXQLFDWLRQDQG1HWZRUNV

,QIRUPDWLRQ6RXUFHV

SAP AG BC619 1-3

SAP AG 1999

&RXUVHJRDO

7KLVFRXUVHl ([SODLQVKRZ5EXVLQHVVREMHFWVDUHGLVWULEXWHG

XVLQJ$SSOLFDWLRQ/LQN(QDEOLQJl 3URYLGHVDQLQWURGXFWLRQWRFRPPXQLFDWLRQ

WHFKQRORJ\l 'HVFULEHV$/(IXQFWLRQVDQGWRROVl 3URYLGHVWLSVIRULPSOHPHQWDWLRQDGPLQLVWUDWLRQ

PRGLILFDWLRQDQGFXVWRPHUVRZQGHYHORSPHQWV

SAP AG BC619 1-4

SAP AG 1999

l (YDOXDWHWKHDGYDQWDJHVDQGGLVDGYDQWDJHVRIGLVWULEXWHGEXVLQHVVSURFHVVHV

l 8QGHUVWDQGWKHSULQFLSOHVRIFRPPXQLFDWLRQWHFKQRORJ\

l ,PSOHPHQW$/(FRPSRQHQWVDQGGHVFULEHWKHLUIXQFWLRQV

l &RQILJXUHWKHGLVWULEXWLRQRIEXVLQHVVSURFHVVHVEDVHGRQ$/(

l $GPLQLVWUDWHDQGPRQLWRU$/(IXQFWLRQV

$WWKHFRQFOXVLRQRIWKHFRXUVH\RXZLOOEHDEOHWR

&RXUVH2EMHFWLYHV

SAP AG BC619 1-5

SAP AG 1999

2YHUYLHZRI&RQWHQWV

Unit 7 7RROVUnit 8 $GPLQLVWUDWLRQUnit 9 (QKDQFHPHQWVUnit 10 3HUIRUPDQFHUnit 11 6\VWHP6HFXULW\Unit 12 7LSVDQG7ULFNVUnit 13 ,QIRUPDWLRQ6RXUFHV

Unit 1 &RXUVH2YHUYLHZUnit 2 %XVLQHVV3URFHVVHV

DQG%XVLQHVV2EMHFWVUnit 3 &RPPXQLFDWLRQDQG

1HWZRUNVUnit 4 $/(&RPSRQHQWVUnit 5 ,'RF6HUYLFHVUnit 6 6SHFLDO)XQFWLRQV

3UHIDFH

$SSHQGL[

SAP AG BC619 2-1

SAP AG 1999

l %XVLQHVV3URFHVVHVLQ&RPSDQLHVl 'LVWULEXWHG%XVLQHVV3URFHVVHVl 6$35%XVLQHVV2EMHFWVl ,'RFVDQG0HVVDJH7\SHVl %$3,Vl $/(,QWHJUDWLRQ7HFKQRORJ\l $/(%XVLQHVV3URFHVVHV

&RQWHQWV

%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV

SAP AG BC619 2-2

SAP AG 1999

l 8QGHUVWDQGWKHUHODWLRQVKLSEHWZHHQEXVLQHVVSURFHVVHVDQGEXVLQHVVGDWDREMHFWV

l ,GHQWLI\WKHDGYDQWDJHVDQGGLVDGYDQWDJHVRIGLVWULEXWLQJEXVLQHVVSURFHVVHV

l 8QGHUVWDQG,'RFVPHVVDJHVW\SHVDQG%$3,Vl 8QGHUVWDQGWKHSXUSRVHRI$/(

$WWKHFRQFOXVLRQRIWKLVXQLW\RXZLOOEHDEOHWR

%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV8QLW2EMHFWLYHV

SAP AG BC619 2-3

SAP AG 1999


&RXUVH2YHUYLHZ



7RROV

3HUIRUPDQFH


6SHFLDO)XQFWLRQV


,QIRUPDWLRQ6RXUFHV

SAP AG BC619 2-4

SAP AG 1999

l %XVLQHVVSURFHVVHVWDVNVDQGZRUNVWHSVl 5EXVLQHVVREMHFWVDUHXVHGIRUVWUXFWXULQJEXVLQHVVGDWDl :RUNIORZVXSSRUWVEXVLQHVVSURFHVVHVl $QLQWHJUDWHG(536\VWHPVXFKDV6$35DXWRPDWLFDOO\IXOILOV

WKHUHTXLUHPHQWVIRUVKDUHGGDWDDFFHVVDQGDZRUNIORZFRQWUROOHGSURFHVV

%XVLQHVV3URFHVVHVLQWKH&RPSDQ\

%XVLQHVVSURFHVVHVEXVLQHVVREMHFWVDQG:RUNIORZn In all companies business processes consist of a sequence of work steps in which individual tasks are

completed.n When the individual tasks are processed, usually existing data is accessed or new business data is

created, for example, customer addresses, bank details, purchase orders. The person processing thedata must have authorization to access shared data.

n In R/3 Systems business data is structured in business objects.n The processing of business processes must be supported by appropriate workflow functions. The

processor of the subsequent task must be notified and if there is an error situation, the correct worksteps must be started.

n An integrated ERP System such as SAP R/3 automatically fulfils the requirements for shared dataaccess and a workflow controlled process.

SAP AG BC619 2-5

SAP AG 1999

Regional installation Country-wide installation local system business objects

'LVWULEXWHG%XVLQHVV3URFHVVHV

'LVWULEXWHG%XVLQHVV3URFHVVHVn For various reasons it is practical to decentralize business applications for ensuring simultaneous

data consistency.n You must ensure that the distributed applications can access shared data. The semantics of this data

must be synchronized - updated data must be available in each business environment.n To be able to distribute business processes application data must also be distributed. Business

objects are used to distribute this data.

SAP AG BC619 2-6

SAP AG 1999

'LVWULEXWHGDSSOLFDWLRQVDULVHGXHWR

l 7KHJOREDOL]DWLRQRIPDUNHWVl &RPSDQ\ZLGHEXVLQHVVSURFHVVHVl ,QGHSHQGHQWDQGDXWRQRPRXVEXVLQHVVXQLWV

5HDVRQVIRU'LVWULEXWHG$SSOLFDWLRQV,

n The increasing globalization of markets has led to the increasing separation of organizational units.Work steps need to be carried out locally but also be part of a distributed business process.

n When enterprises are bought or sold business fields must be quickly integrated or deleted.n Business processes are not restricted to one enterprise only. More and more customers and suppliers

are being included in business processes. In the Internet age business processes are taking placebetween companies. A process confined to company boundaries is therefore now unusual.

n Autonomous units (e.g. local production plants, sales units) in an enterprise do not want to bedependent on a centrally administered system. There may be several reasons for this: When structuring a process, flexibility and individuality is very important. The technical infrastructure for communicating with a central system is not sufficiently developed

in all regions for enterprises that operate globally. Release strategies can be independent and individual.

SAP AG BC619 2-7

SAP AG 1999


l $YDLODELOLW\UHTXLUHPHQWV[8SJUDGHl 'DWDSURWHFWLRQl ,QGXVWU\ODQJXDJHDQGFRXQWU\YHUVLRQVl 7LPH]RQHVl &RPPXQLFDWLRQZLWKQRQ6$3V\VWHPV

5HDVRQVIRU'LVWULEXWHG$SSOLFDWLRQV,,

n Systems that map core processes in logistics (production, plant maintenance, warehouse managementsystem, shipping) have to be available 24 hours every day. The costs of such a high level of systemavailability should be kept limited to systems providing this core functionality.

n Special requirements for data protection can be better fulfilled on a separate system (personnelmanagement, public orders in the armament industry).

n In certain circumstances different SAP industry solutions, languages and country versions cannot beimplemented on one single R/3 System.

n For processes that extend over several time zones, the difficulties of working in different time zonesmust be dealt with (employees working at different times).

n Specialized external applications have to handle important tasks in the processes, for example, timerecording, production planning systems)

SAP AG BC619 2-8

SAP AG 1999


l /RDGGLVWULEXWLRQl P\6$3FRPFRPSRQHQWV1HZ'LPHQVLRQ$SSOLFDWLRQVl )DLOXUHULVNVl 8VHRIH[LVWLQJV\VWHPV

5HDVRQVIRU'LVWULEXWHG$SSOLFDWLRQV,,,

n Limited system resources (in particular the DB server) make it necessary to distribute the workloadacross several systems. Keep in mind that the primary function of ALE is not in handlingperformance bottle necks. With efficient distribution ALE scenarios can reduce the system load inoperative systems (e.g. consolidating nested application data for reporting).

n mySAP.com components (New Dimension applications) are to be used.n System failure should be minimized. System failures caused by errors or upgrades do not effect all

business components.n The implementation strategy provides for a heterogeneous system environment and non-SAP or

legacy systems are still to be used.

SAP AG BC619 2-9

SAP AG 1999

l 5LVDQLQWHJUDWHGEXVLQHVVDSSOLFDWLRQVRIWZDUH7KLVLQWHJUDWLRQHQDEOHV $SSOLFDWLRQPDVWHUGDWDWREHVKDUHG 7RPRGHOSURFHVVHVDVRQHXQLWDQGWRFRQWURODOOWKHLU

GHSHQGHQFLHVFHQWUDOO\ 7RXSGDWHDQGPRQLWRUTXDQWLW\DQGYDOXHIORZV

V\QFKURQRXVO\

:KDW'LVWLQJXLVKHVDQ,QWHJUDWHG(536\VWHP"

n This high level of integration often cannot be sustained when applications are distributed.Implementation and operating costs also increase considerably in distributed system environments .

SAP AG BC619 2-10

SAP AG 1999

l 'RHVWKHIXQFWLRQVFRSHRIWKHLQGLYLGXDODSSOLFDWLRQVPHHWP\UHTXLUHPHQWV" +RZFRPSOH[DQGFRQVLVWHQWDUHGLVWULEXWHGV\VWHPV"

l $UHWKHSDUWLFLSDWLQJGHSDUWPHQWVSUHSDUHGWRVXSSRUWWKHUHTXLUHGKDUPRQL]DWLRQDQGVWDQGDUGL]DWLRQDWDOOEXVLQHVVDQGWHFKQLFDOOHYHOV" *OREDOYHUVXVORFDOVWDQGDUGV )UHHVSDFHRIWKHGHFHQWUDOL]HGRUJDQL]DWLRQDOXQLWV

l +RZKLJKDUHWKHRSHUDWLQJFRVWVRIDGLVWULEXWHGHQYLURQPHQW" +DUGZDUHDQGVRIWZDUH $GGLWLRQDOHPSOR\HHV 7UDLQLQJFRVWV

4XHVWLRQV

SAP AG BC619 2-11

SAP AG 1999

l ,GHQWLI\WKHEXVLQHVVSURFHVVl ,GHQWLI\WKHUHDVRQVl $QDO\]HWKHRUJDQL]DWLRQDOVWUXFWXUHRIWKHFRPSDQ\l ,GHQWLI\WKHEXVLQHVVREMHFWV

2UJDQL]DWLRQDO3UHUHTXLVLWHV

Analysis of the company organizational structure Identify the organizational units

Global organizational units: business areas, company codes- Sales organizations and plants

Identify the technical infrastructure- System environment and capacities

Identify the business objects These are often predefined by the scenario or the technology.

Do business objects have to be created or modified?

SAP AG BC619 2-12

SAP AG 1999

%XVLQHVV%XVLQHVV2EMHNW2EMHNW

l $EXVLQHVVREMHFW ,VWKHWHFKQLFDOUHSUHVHQWDWLRQRIDEXVLQHVVREMHFWLQWKHUHDOZRUOG

IRUH[DPSOHDSXUFKDVHRUGHU (QFDSVXODWHVEXVLQHVVORJLF (QDEOHVDFFHVVRQO\YLDGHILQHGLQWHUIDFHV%$3,V +LGHVLQWHUQDOGHWDLOVVRWKDWWKHLPSOHPHQWDWLRQLVLQGHSHQGHQW

IURPWKHH[WHUQDOHQYLURQPHQW ,VVWRUHGDQGPDQDJHGLQWKH%XVLQHVV2EMHFW5HSRVLWRU\%25

6$35%XVLQHVV2EMHFWV

6$35%XVLQHVV2EMHFWVn Definition:

Technical representation of a real world business object:- Customer, vendor, business partner, G/L account

- Purchase order, purchase requisition

- Material, class

n Business processes are modeled using a business object flow.n Encapsulates business logic

Enables access only via defined interfaces (BAPIs, IDoc updating function modules). Complexdata structures are assigned to a business object: message type, business APIs.

Hides internal details so that the implementation can be changed externally.n Stored and managed in the Business Object Repository (BOR).

SAP AG BC619 2-13

SAP AG 1999

%XVLQHVVREMHFWFRUH

Internal structureSpecialization

Consistency requirements(object- related)

Business rules(related toenvironment)

,QWHUIDFH$FFHVVYLD,QWHJULW\

Represntative "is part of"

"is a"

Events

Attributes

ABAP (RFC)

COM/DCOM

CORBAMethods(BAPIs)

IDocs

6WUXFWXUHRI%XVLQHVV2EMHFWV

6WUXFWXUHRI6$35%XVLQHVV2EMHFWVSo that SAP business objects can be encapsulated, they are created as entities with different layers.n At the heart of an SAP business object is the core that contains the object data.n The second layer is the integrity layer and represents the business logic of the object. It includes the

business rules to ensure consistent embedding in the environment and the constraints for values andapplications that can refer to the business object. .

n The third layer - the interface layer describes the implementation and structure of the SAP businessobject and defines the object interface to the external environment.

n The fourth layer of a business object is the access layer. This layer defines the technologies that canbe used for the external access to the object data e.g. COM/DCOM (Component ObjectModel/Distributed Component Object Model).

SAP AG BC619 2-14

SAP AG 1999

l $FFRXQWLQJ $FFRXQWV &KDUWVRI

DFFRXQWV

l 6DOHVDQG'LVWULEXWLRQ 6DOHVRUJDQL]DWLRQ &XVWRPHUHQTXLU\ 6DOHVRUGHU

l &RQWUROOLQJ &RVWDFFRXQWLQJDUHD &RVWW\SH 5HFRQFLOLDWLRQOHGJHU

l 0DWHULDOV0DQDJHPHQW 3XUFKDVLQJRUJDQL]DWLRQ 3XUFKDVHUHTXLVLWLRQ 3XUFKDVHRUGHU )UDPHZRUNRUGHU

([DPSOHVRI%XVLQHVV2EMHFWV

n Each business object belongs to a specific object class depending on its characteristics and its type.These object classes are called object types. For example, all the employees of a company belong tothe object type employee.

SAP AG BC619 2-15

SAP AG 1999

l &ROOHFWLRQRIDOOEXVLQHVVREMHFWV%2

%XVLQHVV:RUNIORZ

$UFKLYH/LQN

$FFHVVLQWHUIDFHV

0RGHOLQJ

%2%2

%2%2

%2%2

%2%2%2%2

%2%2

%2%2%2%2%2%2

%2%2

%25

%XVLQHVV2EMHFW5HSRVLWRU\%25

n All business objects are defined in the Business Object Repository (BOR) within SAP.n The BOR contains two categories of object types:

Business object types Interface types

n BOR objects are processed by the Business Object Builder. The path in the SAP menu is 7RROV$%$3:RUNEHQFK'HYHORSPHQW%XVLQHVV2EMHFW%XLOGHU.

SAP AG BC619 2-16

SAP AG 1999

%XVLQHVV2EMHFW5HSRVLWRU\%URZVHU

n The BOR Browser is called from the Business Object Builder. Choose the pushbutton %XVLQHVV2EMHFW5HSRVLWRU\ and then display all the object types.

SAP AG BC619 2-17

SAP AG 1999

:KDW$UH$3,V"

'HILQLWLRQ$Q$SSOLFDWLRQ3URJUDPPLQJ,QWHUIDFH$3,GHVFULEHVKRZRQHSURJUDPFDQJHWDQRWKHUSURJUDPWRFDUU\RXWDVHUYLFH7KHVHUYLFHPD\DFFHVVGDWDRUH[HFXWHDVSHFLILFIXQFWLRQ

SAP AG BC619 2-18

SAP AG 1999

l 5)&HQDEOHGIXQFWLRQPRGXOHVl %DWFKLQSXWHQDEOHGWUDQVDFWLRQVl $SSOLFDWLRQLQWHUIDFHVIRU,'RFVl %XVLQHVV$SSOLFDWLRQ3URJUDPPLQJ,QWHUIDFHV%$3,V

$YDLODEOHDVRI5$ &DOOHGV\QFKURQRXVO\YLD5)& &DOOHGDV\QFKURQRXVO\YLD$/(LQWHUIDFH

3URJUDPPLQJ,QWHUIDFHIRU%XVLQHVV2EMHFWV

SAP AG BC619 2-19

SAP AG 1999

l $Q,'RFLVDFRQWDLQHUIRUWKHGDWDRIDEXVLQHVVREMHFWRUWHFKQLFDO5REMHFW

l (DFK,'RFKDVDPHVVDJHW\SH7KLVLQGLFDWHVWKHW\SHRIEXVLQHVVREMHFWRUWKHEXVLQHVVIXQFWLRQRIWKHGDWD

l 0HVVDJHW\SHVKDYHSURFHVVLQJUXOHVLQWKHUHFHLYLQJV\VWHPl $Q,'RFFRQWDLQVWKHGDWDLQDVHJPHQWKLHUDUFK\7KH,'RFW\SH

GHVFULEHVWKHWHFKQLFDOVWUXFWXUHRIWKH,'RFl ,'RFW\SHVKDYHYHUVLRQV

,'RFV

n Technical R/3 objects for IDocs with a message type exist, for example, audit data (ALEAUD) anddistribution group (CONDA2)

n An IDoc has different characteristics: database table, text, HTML file, XML datastream, RFC callparameters.

SAP AG BC619 2-20

SAP AG 1999

! #"$% '&()"*+ ,).-../.*) ,-

- #*.*"0),+-*)1))'"123 4)

+5! #"6! )7989):,) 9"); \3],^C_']a b

\c'de+f5g\E^E_]h

b

\

SAP AG BC619 2-21

SAP AG 1999

([DPSOHRIDQ,'RF7\SH0$70$6

n An example of an IDoc type is MATMAS03

Short description: master material Release 4.6A First predecessor MATMAS01 Predecessor MATMAS02

n As well as IDoc types R/3 uses IDoc basic types. IDoc types are called IDoc basic types if they canbe used as the basis for enhancements.

SAP AG BC619 2-22

SAP AG 1999

6DOHV&XVWRPHU

2UGHU0HVVDJHW\SH25'(56,'RFW\SH25'(56$

25'(56'25'(56$

25'(56$

2UGHUFRQILUPDWLRQ0HVVDJHW\SH25'563,'RFW\SH25'(56[

'HOLYHU\0HVVDJHW\SH'(6$'9,'RFW\SH'(6$'9$

'(/95

SAP AG BC619 2-23

SAP AG 1999

%$3,Vl $UHPHWKRGVRIEXVLQHVVREMHFWVl $UHPDQDJHGLQWKH%XVLQHVV2EMHFW5HSRVLWRU\l $UHVWDEOHDQGUHOHDVHLQGHSHQGHQWl +DYHDQRSHQLQWHUIDFH

l $SSOLFDWLRQVVXSSRUWPDLQWHQDQFHDQGIXUWKHUGHYHORSPHQWWKURXJKFKDQJHPDQDJHPHQW

%XVLQHVV$SSOLFDWLRQ3URJUDPPLQJ,QWHUIDFHV

n Change Management

Compatible changes are parameter extensions With incompatible changes new BAPIs must be created: Object.Create -> Object.Create1

SAP AG BC619 2-24

SAP AG 1999

:K\8VH%$3,V"

%$3,Vl $UHXVHGWRVHSDUDWH5FRPSRQHQWVDQGWKHLUUHVSRQVLELOLWLHVl $UHWKHEDVLVRIGLVWULEXWHG$/(EXVLQHVVSURFHVVHVWKDWXVHERWK

V\QFKURQRXVDQGDV\QFKURQRXVFRPPXQLFDWLRQl 2SHQXSWKH56\VWHPWRGHVNWRSDSSOLFDWLRQVLQ&9LVXDO%DVLFDQG

-DYDl +DYHDOLQNWRWKHREMHFWPRGHO&20'&20l 6XSSRUWWKH5,QWHUQHWFRQQHFWLRQXVLQJWKH6$3%XVLQHVV&RQQHFWRUl 3URYLGHDVLPSOHSURJUDPPLQJPRGHOIRUFXVWRPHUVDQGSDUWQHUVRZQ

GHYHORSPHQWV

SAP AG BC619 2-25

SAP AG 1999

l *HW/LVWGets a list of key fields of objects that meet specific selection criteria (search function)

l *HW'HWDLO, *HW6WDWXVGets details (attributes) of an object with a fully specified key

l &UHDWH &UHDWH0XOWLSOHGenerates instances of R/3 business objects

l 5HSOLFDWH6DYH5HSOLFD6DYH5HSOLFD0XOWLSOHUsed to replicate ALE data

l &KDQJH&KDQJH0XOWLSOHChanges instances of R/3 business objects

l 'HOHWH([LVWHQFH&KHFNDeletes instances and checks for the existence of instances in R/3

l &KHFN3RVWUsed in accounting for checking and posting

7\SLFDO0HWKRGV

n The ALE interface for asynchronous BAPI calls supports only write BAPIs with no user dialog.

SAP AG BC619 2-26

SAP AG 1999

'HVNWRSDSSOLFDWLRQV 5)&DFFHVV

%XVLQHVV2EMHFW5HSRVLWRU\ )XQFWLRQ/LEUDU\

5DSSOLFDWLRQVHUYHU

%XVLQHVV%XVLQHVVREMHFWREMHFW

$/(LQWHUIDFH

$FFHVVLQJ%$3,V

l 'HVNWRSDSSOLFDWLRQVv 9LVXDO%DVLFv &v &20'&20

&RQQHFWRUv -DYD

l 5)&DFFHVVv 5v 1RQ6$3

V\VWHPVl $/(LQWHUIDFH

IRUDV\QFKURQRXV%$3,FDOO

wCx`yz{}| ~Iy~QIx`

#w3Cy`` `

wCx`yz{}| ~Iy~QIx`

#w3Cy`` `

wCx`yz{}| ~Iy~QIx`

#w3Cy`` `

n BAPIs are defined as methods of SAP business objects in the Business Object Repository (BOR) andimplemented as function modules in R/3.

n Object-oriented access:Object-oriented access to BAPIs in the BOR can be implemented using various programmingplatforms, e.g. Windows NT, Win9x, DCOM/COM

n RFC access:You can execute direct RFC calls to the function module that forms the basis of the BAPI, eitherusing ABAP or from external development platforms, e.g. by using RFC Class Libraries of C/C++.

SAP AG BC619 2-27

SAP AG 1999

%$3,VLQWKH%XVLQHVV2EMHFW%URZVHU

n Example: business object BUS2012 - purchase order

SAP AG BC619 2-28

SAP AG 1999

%$3,([SORUHU

BAPI Explorer (transaction BAPI)

SAP AG BC619 2-29

SAP AG 1999

33SURGSODQQLQJ ,QYHQWRU\PDQDJHPHQW

6DOHVVKLSSLQJDQGELOOLQJLQWHUQDO

3XUFKDVLQJORFDO 303ODQW0DLQWHQDQFH

623ORFDO

$FFRXQWLQJ &RQWUROOLQJFHQWUDO 623FHQWUDO ,QIRUPDWLRQV\VWHPV

,QYHQWRU\ 3XUFKDVLQJ 6DOHV

3XUFKDVLQJFHQWUDO 5HIHUHQFHV\VWHPIRUPDVWHUDQGFRQWUROGDWD

6HPDQWLF6\QFKURQL]DWLRQ

6DOHVVKLSSLQJDQGELOOLQJ

3XUFKDVLQJRIWUDGLQJJRRGV

,QYHQWRU\PDQDJHPHQW

&RQWUROOLQJORFDO

$/(,QWHJUDWLRQ7HFKQRORJ\

n ALE was originally used to distribute business processes by forwarding the required data andtriggering a workflow in the external system.

n The focus was on a companys internal distribution scenarios: department-to-departmentn Using the stable IDoc interface ALE enables business processes that go beyond company

boundaries: business-to-business.n ALE is independent of the communication layer and can implement business processes over the

Internet.

SAP AG BC619 2-30

SAP AG 1999

3XUSRVHRI$/(

l 6XSSRUWVGDWDFRQVLVWHQF\DQGGDWDDYDLODELOLW\LQGLVWULEXWHGEXVLQHVVSURFHVVHV

l 3URYLGHVDQLQIUDVWUXFWXUHIRUFRXSOLQJV\VWHPVORRVHO\WKURXJKDV\QFKURQRXVPHVVDJLQJXVLQJ,'RFVRUFRXSOLQJV\VWHPVQDUURZO\WKURXJKV\QFKURQRXV%$3,FDOOV

l (QDEOHVGLVWULEXWLRQEHWZHHQV\VWHPVZLWKGLIIHUHQWUHOHDVHYHUVLRQV

l (QDEOHV5WRFRPPXQLFDWHZLWKQRQ6$3V\VWHPVDQG5l 3URYLGHVIXQFWLRQVIRUDGPLQLVWUDWLRQPRQLWRULQJDQG

GHYHORSPHQWl 3UHGHILQHG$/(EXVLQHVVSURFHVVHVFRYHULPSRUWDQWEXVLQHVV

IXQFWLRQV/LEUDU\RI$/(%XVLQHVV3URFHVVHV

SAP AG BC619 2-31

SAP AG 1999

$/(%XVLQHVV3URFHVVHV

l 'LVWULEXWLRQRIPDVWHUGDWD

l 'LVWULEXWLRQRIWUDQVDFWLRQGDWD

n ALE business processes distribute master data and transaction data.n There are no technical differences between the two data types.n Master data is stable over the long term: Changes seldom have to be communicated straight away. Master data must be able to be processed in mass. When master data is created, changed or deleted, ALE master data scenarios do not immediately

create the IDoc, - they create the IDoc later when the change pointers are processed.

SAP AG BC619 2-32

SAP AG 1999

,QERXQGIXQFWLRQPRGXOHIRU,'RF,QERXQGIXQFWLRQPRGXOHIRU,'RF %$3,%$3,

$SSOLFDWLRQ$SSOLFDWLRQ

z~I

NyzC`~IyE~IxII

zC

SAP AG BC619 2-33

SAP AG 1999

l 8QGHUVWDQGWKHUHODWLRQVKLSEHWZHHQEXVLQHVVSURFHVVHVDQGEXVLQHVVGDWDREMHFWV

l ,GHQWLI\WKHDGYDQWDJHVDQGGLVDGYDQWDJHVRIGLVWULEXWLQJEXVLQHVVSURFHVVHV

l 8QGHUVWDQG,'RFVPHVVDJHVW\SHVDQG%$3,Vl 8QGHUVWDQGWKHSXUSRVHRI$/(

SAP AG BC619 2-34

([HUFLVHV

8QLW%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV7RSLF,QWHUIDFH$GYLVHU

At the conclusion of these exercises, you will be able to: Define the structure of the "Interface Adviser" Define the content of the "Interface Adviser"

You would like to gain an overview of the existing SAP integrationscenarios and the available technologies for your interface planning phase.

1-1 Log on to SAPNet with the user ID and password given to you by your instructor:http://sapnet.sap.com/int-adviser

1-1-1 Work through the section Introduction.

1-2 Become familiar with the structure of the "Interface Adviser".

1-2-1 Where is the core scenario "Sales and Distribution processing stand alone"?

1-2-2 How many variants are described in detail?

1-2-3 Which master data is distributed in variant 4?

1-3 Which Basis technology requirements are stated for communication with the R/3System 3.11 via RFC for external platforms?

SAP AG BC619 2-35

8QLW%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV7RSLF7KH.QRZOHGJH3RRORIWKH%XVLQHVV)UDPHZRUN

At the conclusion of these exercises, you will be able to: Define the structure of the Knowledge Pool of the Business

Frameworkn Define the content of the Knowledge Pool of the Business Framework

You would like to gain an overview of the existing SAP integrationscenarios and the available technologies for your interface planningphase.

2-1 Log on to SAPNet with the user ID and password given to you by your instructor:http://sapnet.sap.com/ibf

2-1-1 Work through the section Introduction. What are the five most importantmodules of the Business Framework?

2-2 Become familiar with the structure of the Knowledge Pool of the BusinessFramework.

2-2-1 Work through the section 'Technology'.

2-2-2 Which scenario types are available?

SAP AG BC619 2-36

8QLW%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV7RSLF%XVLQHVV2EMHFW5HSRVLWRU\

At the conclusion of this exercise, you will be able to:n Navigate through the application hierarchy of the business objects in

the Business Object Repository.

You would like to know where you can find business objects in the R/3System and where you can call up information on their attributes,interfaces and so on.

1-1 Open the Business Object Repository Browser for all object types in order todisplay existing objects in the R/3 System.

1-1-1 Expand the hierarchy node of any hierarchy.

1-1-2 What do the colors of the objects and the STOP indicator signify?1-1-3 Display details of the business object sales order (BUS2032).

1-2 Use the Business Object Builder to disclose the object behind the technical nameBUS1001.

1-2-1 Which is the key field for this object ?

SAP AG BC619 2-37

8QLW%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV7RSLF%XVLQHVV$SSOLFDWLRQ3URJUDPPLQJ,QWHUIDFH

At the conclusion of this exercise, you will be able to:n Find BAPIs directly in the R/3 System and to define the connection

between the definition in the BOR and the actual implementation ofthe function module.

You would like to know where you can find the external parameters forbusiness objects in the R/3 System and where you can call up furtherdetails on their parameters.

2-1 Use the BAPI Explorer in order to display business objects with BAPIs.

2-1-1 What is the significance of the different symbols?

2-1-2 Which business objects in the application Project System have BAPIs?2-1-3 Which key field is defined for the business object Network ?2-1-4 Which BAPIs does the business object Network provide ?

2-2 Display the documentation for the business object Network.2-2-1 Display the documentation for the BAPI Getlist.

2-2-2 Which function module is implemented by the BAPI GetList of Network?

2-3 Use the alphabetical display in order to display further information on the businessobject Applicant.2-3-1 Which instance-independent method is defined for this business object?

SAP AG BC619 2-38

8QLW%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV7RSLF2SHQ%$3,1HWZRUN

At the conclusion of this exercise, you will be able to:n Find further information and products concerning development

support for BAPIs in SAPNet.

You would like to know how you can start to develop external access,and what support SAP provides for this.

3-1 Visit the Open BAPI Network in SAPNet. Log on using either your own user dataor the user data given to you by your instructor.

3-1-1 Open the BAPI section.

3-1-2 Open the COM section.

3-1-3 Open the Java section.

SAP AG BC619 2-39

6ROXWLRQV

8QLW%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV7RSLF,QWHUIDFH$GYLVHU

1-1 SAPNet access to http://sapnet.sap.com/int-adviser.Use your SAPNet user ID and password.1-1-1 Select ,QWURGXFWLRQ

Read me Basics How to use

1-2 The interface consists of four sections:1.) Data transfer2.) Scenarios3.) Objects4.) Technology

1-2-1 You can find the core scenario "Sales and Distribution processing standalone" under

6FHQDULRV&RUHSURFHVVHV6DOHVDQG'LVWULEXWLRQ1-2-2 Seven different variants are explained in detail for this core process.

1) No availability check is available in R/32) Availability check performed in R/3 against the inventory at delivery3) Availability check performed in R/3 against the inventory at delivery planned outflows from sales orders from R/3 to the external system4) Scheduling the sales orders in the external system5) Scheduling the sales orders against quotas6) Availability check in R/3 against planning7) ATP checks in R/3 against reservations

1-2-3 9DULDQW0DVWHUGDWDMaterial and client master data have to be distributed.

1-3 Return to the homepage of the Interface Adviser and select WHFKQRORJ\. In thesection Interfaces there is a link to the availability checklist of the basictechnologies.

)LHOGQDPH 9DOXHV55HOHDVH ,&RPPXQLFDWLRQZLWK56\VWHPV5)&V 6HOHFW

SAP AG BC619 2-40

8QLW,QWHJUDWLRQ7HFKQRORJLHVIRU%XVLQHVV6ROXWLRQV7RSLF7KH.QRZOHGJH3RRORIWKH%XVLQHVV)UDPHZRUN

1-1 SAPNet access to http://sapnet.sap.com/ibf.Use your SAPNet user ID and your SAPNet password or Walldorf/training.

6HOHFW2YHUYLHZ2-2 Select .QRZOHGJH3RRO

Methodology Scenarios Technology Interface Adviser Data Transfer Adviser

6HOHFW7HFKQRORJ\2-2-2 Select 6FHQDULRV

Frontend/Internet Scenarios ALE Scenarios Customer Scenarios Complementary Scenarios

SAP AG BC619 2-41

6ROXWLRQV

8QLW%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV7RSLF%XVLQHVV2EMHFW5HSRVLWRU\

1-1 7RROV %XVLQHVV)UDPHZRUN%$3,GHYHORSPHQW%XVLQHVV2EMHFW%XLOGHU6:2Button: %XVLQHVV2EMHFW5HSRVLWRU\6:2

1-1-1 Expand the node under any application (for example Real EstateManagement, Sales and Distribution) and expand the subnodes.

1-1-2 8WLOLWLHV /HJHQGVSTOP indicator: obsolete (please do not use this object type any more)

1-1-3 The SalesOrder (BUS2032) is located in the hierarchy under Sales andDistribution Sales.Display the details of the business object SalesOrder by double clicking onit.

$OWHUQDWLYHURXWHWRWKHVROXWLRQLQ7RROV$%$3:RUNEHQFK'HYHORSPHQW%XVLQHVV2EMHFW%XLOGHU

1-3 Enter %86 => the text material is displayedDisplay the details of the business object Material by double clicking on it.The MatNr (material number) is displayed as the key field.

SAP AG BC619 2-42

8QLW%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV7RSLF%XVLQHVV$SSOLFDWLRQ3URJUDPPLQJ,QWHUIDFH

2-1 7RROV%XVLQHVV)UDPHZRUN%$3,([SORUHUSelect the tab multi-level in left-hand section of the screen.

*RWR'LVSOD\OHJHQG2-1-2 Expand the node project system.

You will see three business objects: ProjectDefinition, Network andWorkBreakdownStruct.

2-1-3 Expand the node Network.Only the key field Number : Network Plan Number is defined for thisbusiness object.

2-1-4 The business object Network provides five BAPIs: ExistenceCheck,Getdetail, Getinfo, Getlist and Maintain.

2-2 Select the node Network in the left-hand section of the screen and press the tabDocumentation in the right-hand section of the screen.

2-2-1 Repeat this step for the BAPI Getlist. Select the node Getlist in the left-hand section of the screen and press the tab Documentation in the right-hand section of the screen.

2-2-2 Select the node Getlist in the left-hand section of the screen and press thetab Detail in the right-hand section of the screen. This BAPI isimplemented via the function module BAPI_NETWORK_GETLIST.

2-3 Select the tab Alphabetical in the left-hand section of the screen.

2-3-1 Only one instance-independent method is defined for the business objectApplicant:CreateFromData.

SAP AG BC619 2-43

8QLW%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV7RSLF2SHQ%$3,1HWZRUN

KWWSVDSQHWVDSFRPEDSL3-1-1 Become familiar with the BAPI concept, check which BAPIs are available,

or become a member. You can also find up to date BAPI information in thesection BAPI.

3-1-2 The COM section contains information and software relating to COM-basedtechnologies, utilities and documentation, as well as links to SAP partnersites on which you can find more information and software relating toCOM-based subjects.

3-1-3 You can find SAP products and partner products for both Java and BAPIs inthe Java section.

SAP AG BC619 3-1

SAP AG 1999

l &RPSXWHU1HWZRUNVl 1HWZRUN6HUYLFHVDQG3URWRFROVl 6$3)XQFWLRQVIRU1HWZRUN&RQQHFWLRQV

&RQWHQWV

&RPPXQLFDWLRQDQG1HWZRUNV

SAP AG BC619 3-2

SAP AG 1999

l :K\FRPSXWHUQHWZRUNVDUHXVHGl +RZV\VWHPVFRPPXQLFDWHZLWKHDFKRWKHUl :KLFK,QWHUQHWVHUYLFHVDQGSURWRFROVDUH

LPSRUWDQWl :KLFKIXQFWLRQVDQGSURGXFWV6$3SURYLGHVIRU

QHWZRUNFRPPXQLFDWLRQ

$WWKHFRQFOXVLRQRIWKLVXQLW\RXZLOOEHDEOHWRXQGHUVWDQG

&RPPXQLFDWLRQDQG1HWZRUNV8QLW2EMHFWLYHV

SAP AG BC619 3-3

SAP AG 1999


&RXUVH2YHUYLHZ



7RROV

3HUIRUPDQFH


6SHFLDO)XQFWLRQV

&RPPXQLFDWLRQDQG1HWZRUNV

,QIRUPDWLRQ6RXUFHV

%XVLQHVV3URFHVVHVDQG%XVLQHVV2EMHFWV

SAP AG BC619 3-4

SAP AG 1999

7HFKQLFDO5HDVRQV

l 5HVRXUFHVKDULQJl 5HOLDELOLW\DQGDVVXUDQFHDJDLQVW

EUHDNGRZQl +DUGZDUHFRVWVl 6FDOLQJRISURFHVVLQJSHUIRUPDQFHl &RPPXQLFDWLRQ

5HDVRQVIRU1HWZRUNLQJ&RPSXWHUV

5HDVRQVIRUQHWZRUNLQJn Computer networks are the technical prerequisite for implementing distributed business processes.

The purpose of computer networks are to:

Share data, equipment and system performance over long distances Guarantee high reliability and availability by providing hardware replacement capacity Reduce costs since small computers have a considerably higher cost/performance relation than

large computers.

Hardware performance can be scaled up (adjustment to the demand for computer power) byadding more computers to the network.

Provides communication across the globe.n All the above reasons bring considerable savings in costs.n. The reasons are similar to the business

and technical reasons for distributing business processes.

SAP AG BC619 3-5

SAP AG 1999

7&3,3

l 7UDQVPLVVLRQ&RQWURO3URWRFRO,QWHUQHW3URWRFRO 6XSSRUWVWKHFRPPXQLFDWLRQRIDSSOLFDWLRQVLQDQHWZRUNHG

HQYLURQPHQWl &RPELQDWLRQRIWZRSURWRFROVRIOD\HUVDQGLQ26,

UHIHUHQFHPRGHOIRUQHWZRUNV,36WDFN ,3VHQGVGDWDLQSDFNHWV 7&3DVVXUHVGDWDLQWHJULW\IUDJPHQWDWLRQVHTXHQFHDYRLGDQFH

RIGDWDORVV

n A 1978 protocol from the US Defense Ministry established this as the communications standard.n TCP/IP communicates data using data packets. As data packets can reach the receiver via any route,

this protocol is relatively insensitive to a route failure, provided there are alternative routes.

SAP AG BC619 3-6

SAP AG 1999

,QWHUQHW3URWRFRO,3

l ,QWHUQHW3URWRFRO,3 5HVSRQVLEOHIRUURXWLQJGDWDEHWZHHQVHQGHUDQGUHFHLYHU ,3VHQGVGDWDLQSDFNHWV&RQWDLQVLQIRUPDWLRQDERXWWKH

IUDJPHQWDWLRQDQGUHVWRUDWLRQRIGDWD ,3URXWHUVFDQVXSSUHVVGDWDSDFNHWVLIV\VWHPLVRYHUORDGHGDQG

UHGXFHWKHWUDQVPLVVLRQIUHTXHQF\ 0LVVLQJSDFNHWVDUHUHVHQWZLWKUHWUDQVPLWUHTXHVWV

SAP AG BC619 3-7

SAP AG 1999

l $GGUHVVIRUPDW ELWOHQJWK )RXUGHFLPDOGLJLWVEHWZHHQ 'RWWHGGHFLPDOIRUPDW 'LYLGHGLQWRQHWZRUNDGGUHVVHVDQGKRVWDGGUHVVHV

l 6SHFLDODGGUHVVHV ORFDOQHWZRUNURXWHU ORFDOFRPSXWHU EURDGFDVWWRDOOFRPSXWHUVLQWKHORFDO

QHWZRUNl 'RPDLQ1DPH6\VWHP

+LGHVWKHWHFKQLFDODGGUHVVEHKLQGDUHDGDEOHQDPH

,3$GGUHVVHV

,3$GGUHVVn All network layer protocols have a specific address format. The 32 bit IP addresses of the TCP/IP

protocol have the form "199.12.1.1". This format is also called GRWWHGGHFLPDO. Each of its four partscorresponds to a decimal number between 0-255 and represents 8 bits.

n Part of the IP address identifies the network, the remaining part the individual computer or hostwithin the network.

n The part of the address that identifies the host can be defined by a subnetwork mask.

SAP AG BC619 3-8

SAP AG 1999

,3$GGUHVV&ODVVHV

l $GGUHVVFODVVHV $ELWQHWZRUNELWKRVWIRUDWRWDORIFRPSXWHUV

WR $ELWQHWZRUNELWKRVWVIRUWRWDORIFRPSXWHUV

WR $ELWQHWZRUNELWKRVWVIRUWRWDORIFRPSXWHUV

WR 'DQG(PXOWLFDVWDQGH[SHULPHQWDOXVDJH

,3$GGUHVV&ODVVHVn As the whole IP address is only 32 bits long and networks have different numbers of computers,

several address classes are created. Address classes assign different numbers of bits to the networkcomponent and the host component of the IP address.

SAP AG BC619 3-9

SAP AG 1999

7UDQVPLVVLRQ&RQWURO3URWRFRO7&3

l 7UDQVPLVVLRQ&RQWURO3URWRFRO7&3 5HOLDEOHVWUHDPVHUYLFHJXDUDQWHHVHUURUIUHHFRPPXQLFDWLRQ

EHWZHHQSURJUDPVZLWKQRGDWDORVVQRUGXSOLFDWLRQDQGZLWKGDWDLQFRUUHFWVHTXHQFH

7KHGDWDLVUHFHLYHGE\WKHSURJUDPDVDVWUHDPRIE\WHV7KHUHDOSDFNHWSDFNHWVL]HDQGSDFNHWVHTXHQFHUHPDLQVKLGGHQ

7&3XVHVDELWSRUWQXPEHUWRLGHQWLI\WKHSURFHVVRQWKHUHFHLYLQJFRPSXWHUWKDWZLOOSURFHVVWKHGDWDSDFNHW

n Protocol of the communication-oriented transport layer (layer 4). Attached to the packet-orientedInternet protocol (IP).

SAP AG BC619 3-10

SAP AG 1999

7&33RUWV

l 7&3XVHVDELWSRUWQXPEHUWRLGHQWLI\WKHSURFHVVRQWKHUHFHLYLQJFRPSXWHUWKDWZLOOSURFHVVWKHGDWDSDFNHW3RUWQXPEHUVXQGHUDUHDVVLJQHGWRVSHFLILHGVHUYLFHVLQ5HTXHVWIRU&RPPHQWV5)&VDQGDUHFDOOHGZHOONQRZQSRUWV3RUWVXQGHUVKRXOGRQO\EHXVHGE\V\VWHPSURFHVVHVURRWXVHUXQGHU81,;

l 6HUYLFH 3RUW 3URWRFRO3LQJHFKR 7&3)73GDWD 7&3)73FRQWURO 7&3WHOQHW 7&36073 7&3KWWS 7&3SRS 7&3

7&33RUWVn TCP uses a 16 bit port number to identify the process on the receiving computer that will process the

data packet. Port numbers below 512 are assigned to specified services in Request for Comments(RFCs) and are called "well known ports". Ports under 1024 should only be used by systemprocesses (root user under UNIX).

SAP AG BC619 3-11

SAP AG 1999

5,QWHUIDFHV

l &RPPXQLFDWLRQOD\HUSURWRFROVXVHGLQ5 ',$*6$3*8,SURWRFRO 5)&

w ,'RFGLVSDWFKw 6\QFKURQRXV%$3,FDOO

)73)LOH7UDQVIHU3URWRFROw (',ILOHLQWHUIDFHw %DWFK,QSXW

6073w (',,QWHUQHWLQWHUIDFHHPDLORXWER[w 6$32IILFH

5,QWHUIDFHVSAP provides a range of programming interfaces to integrate external applications into the SAP System. With these interfacesyou can write client/server applications that communicate with SAP Systems. Your external application can function either asthe client or as the server to the SAP System (sometimes even as both).

',$*With the GUI interface to R/3 you can write a client program that accesses the datastream exchanged between the R/3application server and its SAPgui.With the GUI interface your external client program can provide an alternative interface to the standard SAPgui. This caneither be a graphical or non graphical interface (e.g. language controlled or Web-based).Programming using the GUI interface also enables your client program to monitor or record a user dialog with SAPguiimages.

5)&The protocol of the SAP Remote Function Call (RFC) enables you to call ABAP function modules from externalapplications. An external application that uses the RFC interface, can function as a server or as a client to an SAP System.Calling an RFC function in an SAP System from an external program is the same in principle as calling an RFC functionfrom another SAP System (from ABAP).

%$3,SAP business objects provide an object-oriented view of SAP data structures and functions. The Business API (BAPI) isan interface through which you can call the methods of these SAP business objects.

,'RFThe interface Intermediate Document (IDoc) is an SAP standard format for exchanging data between SAP Systems orbetween an SAP-System and an external application. An IDoc defines an SAP standard data container (template) forsending or receiving data from an SAP System.

)LOHLQWHUIDFH (FTP) (', (IDoc) %DWFK,QSXW batch input interface enables you to input data into R/3 using R/3 transactions.

SAP AG BC619 3-12

SAP AG 1999

l $/(XVHV5%DVLVIXQFWLRQVIRUDV\QFKURQRXVFRPPXQLFDWLRQXVLQJ,'RFV

l 7KH%DVLVIXQFWLRQVFDUU\RXWWKHIROORZLQJWDVNV :ULWH,'RFVWRWKHGDWDEDVH &KHFNV\QWD[RI,'RFW\SH &RPPXQLFDWHORZOHYHOZLWKRXWSXWGHYLFHVDQG5SRUWW\SHV

,'RF&RPPXQLFDWLRQ

SAP AG BC619 3-13

SAP AG 1999

3DUWQHU3URILOHV

l 3DUWQHUSURILOHVFRQWUROWKHFRPPXQLFDWLRQRIDV\QFKURQRXV,'RFVLQRXWERXQGSURFHVVLQJDQGLQERXQGSURFHVVLQJ

l 'LIIHUHQWSDUWQHUW\SHVDUHXVHGLQ,'RFRXWERXQGSURFHVVLQJHJORJLFDOV\VWHPFXVWRPHUYHQGRU

l 7KHSDUWQHUW\SHIRU$/(FRPPXQLFDWLRQVLVWKHORJLFDOV\VWHP/6

l 3DUWQHUSURILOHVDUHFOLHQWGHSHQGHQW

n Partner profiles are client-dependentn Partner profiles with the partner type logical system only exist for systems to which the current client

sends messages or from which the current client receives messages.

SAP AG BC619 3-14

SAP AG 1999

'HILQLQJ3DUWQHU3URILOHV

SAP AG BC619 3-15

SAP AG 1999

l 5SRUWVGHILQHWKHGHYLFHLQWHUIDFHDQGLWVWHFKQLFDOSDUDPHWHUVIRU,'RFRXWERXQGSURFHVVLQJ

l 7KHSRUWW\SHGHILQHVWKHRXWSXWPHGLXP 7UDQVDFWLRQDO5)&IRU$/(EXVLQHVVSURFHVVHV )LOH &3,&FRQQHFWLRQWR5 ,QWHUQHWHPDLODWWDFKPHQWLQ0,0(IRUPDW $%$3366SURJUDPPLQJLQWHUIDFHIXQFWLRQPRGXOH ;0/;0/ILOHIRUPDW

53RUWV

l 5SRUWVGHILQHWKHGHYLFHLQWHUIDFHDQGLWVWHFKQLFDOSDUDPHWHUVIRU,'RFRXWERXQGSURFHVVLQJ

l 7KHSRUWW\SHGHILQHVWKHRXWSXWPHGLXP 7UDQVDFWLRQDO5)&IRU$/(EXVLQHVVSURFHVVHV )LOH &3,&FRQQHFWLRQWR5 ,QWHUQHWHPDLODWWDFKPHQWLQ0,0(IRUPDW $%$33663URJUDPPLQJLQWHUIDFHIXQFWLRQPRGXOH ;0/;0/ILOHIRUPDW

SAP AG BC619 3-16

SAP AG 1999

'HILQLQJWKH53RUWV

3DUDPHWHUVIRU53RUWVn Version:

If you want to communicate using IDocs with SAP Systems of earlier Releases (2.1 to 3.1) or withexternal systems (e.g. EDI sub-systems), you have to specify the release version in the portdescription in your system. Then the correct IDoc record types can be sent in outbound processing.

n You use the port version to set the release version of the system you want to communicate with. Thismeans:

Version 2: Releases 3.0/3.1 and R/2 System. As each R/2 System is connected to the R/3 Systemvia the port type "CPI-C" and in turn each CPI-C port is connected to an R/2 System, Version 2 ispredefined for this port type and cannot be set in the port description.

Version 3: Releases 4.X (default value)n Two problems may arise with R/2 Systems as well as with earlier R/3 Releases: You are using long names for message types, IDoc types or segments. Earlier releases only

support name lengths up to:

- 6 characters (message type)- 8 characters (IDoc type: Basis type or extension)- 7 characters (segment)

You are using enhancements that you defined for Release 4.X. Earlier releases (3.0, 3.1) identifythese enhanced IDoc types internally using other fields or they do not support enhancements at all(R/3 Releases 2.1, 2.2 and R/2 Systems).

SAP AG BC619 3-17

SAP AG 1999

5)&'HVWLQDWLRQV

l 7KH5)&GHVWLQDWLRQFRQWDLQVWKHDFFHVVVHWWLQJVIRUWKHWDUJHWV\VWHPRID5HPRWH)XQFWLRQ&DOO

l &RQQHFWLRQW\SHVIRU5)&GHVWLQDWLRQV 5FRQQHFWLRQV 5FRQQHFWLRQVXVHGE\$/( ,QWHUQDOFRQQHFWLRQV /RJLFDOGHVWLQDWLRQV 7&3,3FRQQHFWLRQVIRU%XVLQHVV&RQQHFWRU &RQQHFWLRQVXVLQJ$%$3GULYHUV

n R/2 connections

Entries of type 2 specify R/2 Systems. If you create an entry of type 2, you only have to specify thehost name; all communication information is already saved in the background information table ofthe SAP gateway host. If you want you can specify logon details.

n R/3 connectionsEntries of type 3 specify R/3 Systems. If you create an entry of type 3, you have to specify the hostname and the communication service. If you want you can specify logon details. As of R/3 Release3.0 you can choose to specify a load adjustment.

n Internal connectionsEntries of type 1 specify R/3 Systems that are connected to the same database as the current system.These entries are predefined and cannot be changed. The entry names correspond to the names in theSAP message server (transaction SM51).

SAP AG BC619 3-18

SAP AG 1999

0DLQWDLQLQJ5)&'HVWLQDWLRQV

n Logical destinations Instead of specifying a system connection, entries of type L refer to a physical destination. A type

L destination can refer to further type L destinations. A type L entry uses information from thereference entry and adds its own information to this. The reference entry usually contains hostinformation while the type L entry contains the logon information. You can also enter a specificuser name, password, logon language or client.

A type L entry can refer to other entries of type L.

n TCP/IP connections Destinations of type T are connections to external programs which the RFC Library uses to receive

RFCs. The activation type can either be start or registration. If you choose start you have to enter the host name and the path name of the program you want to

start.

If you choose registration, you have to enter a registered RFC program. With an SAP gatewayyou can register an RFC server program under this ID and then wait for RFC calls from other SAPSystems.

n ABAP drivers Entries of type X specify systems in which device drivers have been especially installed in ABAP.

If you create an entry of type X, you have to specify the host name and the ABAP device driver.

SAP AG BC619 3-19

SAP AG 1999

$/(&RPPXQLFDWLRQ6HWWLQJV

l 3DUWQHUSURILOHVSRUWVDQG5)&GHVWLQDWLRQVDUHLQGHSHQGHQWRIHDFKRWKHU

l 7RDYRLGLQFRQVLVWHQFLHV$/(HQDEOHVSDUWQHUSURILOHVDQGSRUWVIRUH[LVWLQJ5)&GHVWLQDWLRQVDQGFRQQHFWLRQVWREHJHQHUDWHGLQWKHGLVWULEXWLRQPRGHO

l )RUHDFKORJLFDOV\VWHPDQ5)&GHVWLQDWLRQRIWKHVDPHQDPHLQXSSHUFDVHPXVWEHGHILQHG

l 7KHVWDQGDUGVHWWLQJVFDQEHFKDQJHGODWHU

n With automatic generation you can change default settings for parameters of partner profiles and R/3ports. These settings include: The person responsible for post processing if errors occur. The version of the communication interface

IDoc packet size and output mode Inbound processing mode

SAP AG BC619 3-20

SAP AG 1999

SAP AG BC619 3-21

([HUFLVHV

8QLW&RPPXQLFDWLRQDQG1HWZRUNV7RSLF&RPPXQLFDWLRQ3DUDPHWHUV

At the conclusion of these exercises, you will be able to: Find the physical definitions that are necessary for communication

between different systems.

You would like to set up communication between R/3 systems.

1. &KHFN the assignment of clients 810 and 811 to the logical system names SALES andPRODUCTION.

Client 810:_______________

Client 811:_______________

5)&GHVWLQDWLRQOn the system 6$/(6Use the implementation guide (IMG) to view the RFC destination for the system SALES.

Target computer: _______________

User: _______________

3RUWVOn the system 6$/(6Use the implementation guide (IMG) to view the port for the system SALES.

Port: _______________

SAP AG BC619 3-22

3DUWQHU3URILOHVOn the S$/(6system: Generate a partner profile for the logical system 68%6

SAP AG BC619 3-23

6ROXWLRQV

8QLW&RPPXQLFDWLRQDQG1HWZRUNV7RSLF&RPPXQLFDWLRQ3DUDPHWHUV

([HUFLVH FKHFNDVVLJQPHQWUse the Implementation Guide (IMG):

Tools Accelerated SAP Customizing Project ManagementSAP ReferenceIMG

Start the setup of the logical systems:

Basis Components Distribution (ALE) Sending and Receiving Systems LogicalSystems Assign Client to Logical System

Double click on the corresponding client number:

Client 810: SALES

Client 811: PRODUCTION

([HUFLVH5)&GHVWLQDWLRQStart the maintenance of the RFC destination:

Basis Components Distribution (ALE) Sending and Receiving Systems Systemsin Network Define Target Systems for RFC Calls

Select5FRQQHFWLRQVDouble click on the destination ,'(6B6DOHV.The WDUJHWFRPSXWHU and the XVHU are displayed on the screen.

([HUFLVH3RUWVStart the maintenance of ports in the IMG:

BBasis Components Distribution (ALE) Sending and Receiving Systems Systems in Network Asynchronous Processing Assigning Ports Define Port

Select 7UDQVDFWLRQDO5)&.The QXPEHU of the Port 6DOHVV\VWHP is displayed.

SAP AG BC619 3-24

([HUFLVHSDUWQHUSURILOHV

Start the maintenance of partner profiles in the IMG:

Basis Components Distribution (ALE) Modeling and Implementing BusinessProcesses Partner Profiles and Time of Processing Maintain Partner ProfileManually

Generate the partner profile SUBSYS_## :

Partner number: SUBSYS_##

Partner type: LS

Postprocessing of permitted users:

Type US

ID

6DYH the entries.

Setting the outbound partner profile

Under RXWERXQGSDUDPHWHU click the 1HZ(QWULHV button.

Message type: MATMAS

Receiver port: Converter

Output mode: Transfer IDOC immediately

IDOC type: MATMAS01

SAP AG BC619 3-25


Type US

ID

6DYH the entries.

Setting the inbound partner profile

Press )EDFN. Under LQERXQGSDUDPHWHU click the 1HZ(QWULHV button.

Message type: MATFET

Processing: Trigger immediately

Process code MATF


Type US

ID

6DYH the entries.

SAP AG BC619 4-1

SAP AG 1999

l 2YHUYLHZRI$/(&RPSRQHQWVl 'LVWULEXWLRQ0RGHOl $SSOLFDWLRQ,QWHUIDFHIRU,'RFVl $SSOLFDWLRQ,QWHUIDFHIRU$V\QFKURQRXV%$3,Vl 6KDUHG0DVWHU'DWD7RRO60'7RROl 7RROVLQ$/((QYLURQPHQW

&RQWHQWV

$/(&RPSRQHQWV

SAP AG BC619 4-2

SAP AG 1999

l 1DPHWKH$/(FRPSRQHQWVDQGLGHQWLI\WKHLUIXQFWLRQV

$WWKHFRQFOXVLRQRIWKLVXQLW\RXZLOOEHDEOHWR

$/(&RPSRQHQWV8QLW2EMHFWLYHV

SAP AG BC619 4-3

SAP AG 1999


&RXUVH2YHUYLHZ



7RROV

3HUIRUPDQFH


6SHFLDO)XQFWLRQV


,QIRUPDWLRQ6RXUFHV

SAP AG BC619 4-4

SAP AG 1999

3ULQFLSOHVRI$/(

l 5HSOLFDWLRQRIEXVLQHVVREMHFWVIRUVXSSRUWLQJGLVWULEXWHGEXVLQHVVSURFHVVHV

l 'DWDLVUHSUHVHQWHGWKHVDPHLQDOOSDUWLFLSDWLQJ56\VWHPV

l 6XSSRUWVDV\QFKURQRXVDQGV\QFKURQRXVFRPPXQLFDWLRQ

l 5HOHDVHLQGHSHQGHQW

SAP AG BC619 4-5

SAP AG 1999

$/(

'LVWULEXWLRQ0RGHO'LVWULEXWLRQ0RGHO7RROV7RROV

$SSOLFDWLRQLQWHUIDFHIRUDV\QFKURQRXV%$3,FDOOV$SSOLFDWLRQLQWHUIDFHIRUDV\QFKURQRXV%$3,FDOOV

6KDUHG0DVWHU'DWD7RRO


2YHUYLHZRI$/(&RPSRQHQWV

$SSOLFDWLRQ,QWHUIDFHIRU,'RFV$SSOLFDWLRQ,QWHUIDFHIRU,'RFV

SAP AG BC619 4-6

SAP AG 1999

$/(

'LVWULEXWLRQ0RGHO

'LVWULEXWLRQ0RGHO'LVWULEXWLRQ0RGHO

$SSOLFDWLRQ,QWHUIDFHIRU,'RFV$SSOLFDWLRQ,QWHUIDFHIRU,'RFV

7RROV7RROV




!" #!

$%&'

(

)&

*#&+, !## !

$ -& &(

n The distribution model describes the flow of business objects between logical systems. SAP, non-SAP or other input/output functions can be hidden behind the logical systems.

n In the distribution model conditions can be defined for a data flow. These "filter" conditions are usedfor:

Receiver determination Data filtering

Specifying dependencies between message types and/or BAPIsn The distribution model is used by ALE outbound processing, receiver determination, APIs and

applications.

SAP AG BC619 4-7

SAP AG 1999

l 7KHGLVWULEXWLRQPRGHOKDVDWUHHVWUXFWXUHZLWKWKHIROORZLQJOHYHOV

. 9LHZRIWKHGLVWULEXWLRQPRGHO. /RJLFDOVHQGLQJV\VWHPV. /RJLFDOUHFHLYLQJV\VWHPV. 0HVVDJHVPHVVDJHW\SHVRU%$3,V. &RQGLWLRQVIRUGDWDILOWHULQJDQGUHFHLYHUGHWHUPLQDWLRQ

l $FRQQHFWLRQLVHVWDEOLVKHGE\DVVLJQLQJPHVVDJHW\SHVRU%$3,VWRWZRORJLFDOV\VWHPV

l 'LVWULEXWLRQPRGHOYLHZVDUHXVHGWRJURXSWRJHWKHUGLVWULEXWLRQVFHQDULRV

6WUXFWXUHRI'LVWULEXWLRQ0RGHO

n The distribution model is client-dependent and may contain one or more views.n The individual views of the distribution model have their own maintenance system that may be

different from the logical system of the client.

SAP AG BC619 4-8

SAP AG 1999

0DLQWHQDQFHRI'LVWULEXWLRQ0RGHO

l 'LVWULEXWLRQPRGHOPDLQWHQDQFHLVDIXQFWLRQRI$/(&XVWRPL]LQJl ,PSRUWDQWIXQFWLRQV

. &UHDWLQJFKDQJLQJDQGGHOHWLQJYLHZVV\VWHPVPHVVDJHVDQGFRQGLWLRQVIRUUHFHLYHUGHWHUPLQDWLRQDQGGDWDILOWHULQJ

. 0RGHOLQJFRPSOHWH$/(EXVLQHVVSURFHVVHVXVLQJWHPSODWHV

. 'LVWULEXWLQJWKHPRGHOWRSDUWLFLSDWLQJ56\VWHPV. 9DULRXVGLVSOD\RSWLRQV

w 'LVSOD\ILOWHUVH[SDQGLQJDQGFROODSVLQJZKROHQRGHV

l 5HFRPPHQGDWLRQ0RGHOLQJWKHGLVWULEXWLRQPRGHOFHQWUDOO\DQGGLVWULEXWLQJWKHUHOHYDQWYLHZV

. $XWRPDWLFJHQHUDWLRQRISDUWQHUSURILOHV

n Maintenance of the distribution model $SSOLFDWLRQ/LQN(QDEOLQJ0RGHOLQJDQGLPSOHPHQWLQJEXVLQHVVSURFHVVHV0DLQWDLQGLVWULEXWLRQPRGHO

SAP AG BC619 4-9

SAP AG 1999

/RJLFDO6\VWHPV

l 0HVVDJHVLQ$/(IORZEHWZHHQORJLFDOV\VWHPVl /RJLFDOV\VWHPVDUHGHILQHGFURVVFOLHQWLQ5l 3UHFLVHO\RQHORJLFDOV\VWHPLVDVVLJQHGWRRQHFOLHQW:KHQ

PHVVDJHVDUHSRVWHGWKLVORJLFDOV\VWHPLVWUDQVIHUUHGLQWRDSSOLFDWLRQGRFXPHQWV

l &$87,21:+(15(1$0,1*7+(/2*,&$/6

SAP AG BC619 4-10

SAP AG 1999

3DUWQHU3URILOHV

l 3DUWQHUSURILOHVFRQWUROWKHSURFHVVLQJRILQERXQGDQGRXWERXQG,'RFV

l 7KH\FDQEHJHQHUDWHGLQWKHPDLQWHQDQFHWUDQVDFWLRQIRUWKHGLVWULEXWLRQPRGHO

l ,PSRUWDQWSDUDPHWHUV. 7KHVL]HRI,'RFSDFNHWVSHU5)&FDOO. 7KHVL]HRI,'RFSDFNHWVIRUSURFHVVLQJ. 2XWSXWDQGSURFHVVLQJPRGHFROOHFWRUSURFHVVLPPHGLDWHO\

n Partner profiles are client-dependent.n Partner profiles with the partner type logical system only exist for systems which the current client

sends messages to or receives messages from.n For this reason when the partner profiles are generated, ALE only considers connections that contain

the logical system of the current client.

SAP AG BC619 4-11

SAP AG 1999

&RQGLWLRQDO'LVWULEXWLRQ)LOWHUV

l )LOWHUVFDQEHGHILQHGLQWKHGLVWULEXWLRQPRGHOWRVHWFRQGLWLRQVIRUWKHGLVSDWFKDQGSURFHVVLQJRIRXWERXQGPHVVDJHV

l ,'RFVDQG%$3,VKDYHGLIIHUHQWILOWHUIXQFWLRQVl ,'RFVXVHFRQGLWLRQVIRU

/ )LOWHULQJVHJPHQWV/ 'HSHQGHQFLHVRIPHVVDJHW\SHVDQG%$3,V/ 'LVWULEXWLQJFODVVLILHGPDVWHUGDWD

l %$3,VXVHFRQGLWLRQVIRU/ 5HFHLYHUGHWHUPLQDWLRQ/ 'DWDILOWHULQJRIWDEOHSDUDPHWHUVIRU%$3,VWKDWZHUHFDOOHGDV\QFKURQRXVO\

SAP AG BC619 4-12

SAP AG 1999

'DWD)LOWHULQJIRU0HVVDJH7\SHV

l 6HJPHQWILOWHULQJ. ,IWKHPHVVDJHW\SHDOORZVWKH,'RFVHJPHQWVRIPHVVDJHW\SHVFDQ

EHILOWHUHG. $OOWKHVHJPHQWVDUHVXSSUHVVHGWKDWGRQRWFRQWDLQWKHYDOXH

VSHFLILHGLQWKHGLVWULEXWLRQPRGHOl 'HSHQGHQFLHV

. &RQGLWLRQVIRUGHSHQGHQFLHVFDQEHVHWIURPWKHGLVWULEXWLRQRIRWKHUPHVVDJHW\SHV

l &ODVVLILFDWLRQ. 7KHGLVWULEXWLRQFDQEHPDGHGHSHQGHQWRQWKHPDVWHUGDWDREMHFW

EHORQJLQJWRDFODVVUHOHYDQWIRUGLVWULEXWLRQ

n Segment filtering

If the filter condition for an optional segment is not satisfied, only this segment will be removedand the IDoc sent.

If the filter condition for a mandatory segment is not satisfied, either:- The higher-level optional segment is removed and the IDoc is sent- All the higher-level mandatory segments and any existing optional segments are removed in

sequence If the header segment is also removed in this process, the IDoc is not sent.

SAP AG BC619 4-13

SAP AG 1999

5HFHLYHU'HWHUPLQDWLRQZLWK%$3,V

l :KHWKHUWKHDSSOLFDWLRQILQGVDUHFHLYHUIRUDV\QFKURQRXVRUIRUDQDV\QFKURQRXV%$3,FDOOFDQEHFRQWUROOHGE\. 9DOXHILOWHUV. 'HSHQGHQFLHVRIPHVVDJHW\SHVDQG%$3,V

n Receivers are determined for BAPIs using APIs that ALE provides for the application. Theapplication receives a list of:

Logical systems in the case of an asynchronous BAPI call

RFC destinations in the case of a synchronous BAPI call

SAP AG BC619 4-14

SAP AG 1999

'DWD)LOWHULQJZLWK$V\QFKURQRXVO\&DOOHG%$3,V

l %$3,WDEOHSDUDPHWHUVFDQEHILOWHUHGSURYLGHGWKDWWKH%$3,KDVSURYLGHGIRUWKLV

l $OOWKHOLQHVDUHVXSSUHVVHGWKDWGRQRWFRQWDLQWKHYDOXHVSHFLILHGLQWKHGLVWULEXWLRQPRGHO

SAP AG BC619 4-15

SAP AG 1999

)LOWHU*URXSV

l )LOWHUFRQGLWLRQVDUHRUJDQL]HGLQWRILOWHUJURXSVl )LOWHUJURXSVDUHFUHDWHGLQWKHGLVWULEXWLRQPRGHOIRUUHFHLYHU

GHWHUPLQDWLRQDQGGDWDILOWHULQJl $Q\QXPEHURIILOWHUJURXSVFDQEHFUHDWHGIRURQHFRQQHFWLRQl )LOWHUJURXSVDUHOLQNHGWRJHWKHUE\WKHORJLFDORSHUDWLRQ25l 7KHILOWHUFRQGLWLRQVRIDILOWHUJURXSDUHOLQNHGWRJHWKHUE\WKH

ORJLFDORSHUDWRU$1'

SAP AG BC619 4-16

SAP AG 1999

'HPR

SAP AG BC619 4-17

SAP AG 1999

$/(

Distribution ModelDistribution Model

ToolsTools

Application interface forasynchronous BAPI callsApplication interface for

asynchronous BAPI calls

Shared MasterData Tool


$SSOLFDWLRQ,QWHUIDFHIRU,'RFV

$SSOLFDWLRQ,QWHUIDFHIRU,'RFV$SSOLFDWLRQ,QWHUIDFHIRU,'RFV0214365871%98:

;4?4?@9BA

0C14365B7198:

;D?4?@98A

E 9%58719B:

;D??@98A

E 95871%98:

;%?4?@98A

F%GHGI JKGL

M%GN GLO'I PQN I RP-M%QN Q

S I T N GL&I PU

VWX"T I HYI NZGUO-GPN

S I T N GL&I PU

[ RP"JKGL&Z\I RP-R S UT R]QT

RL&UQPI ^QN I RPQT_PI N Z

M%QN Q'H\RP"J`GLZ\I RP

aGLZ\I RP-HYbQPUG

F*GH\GI JKGL

M*GN GL&O'I PQN I RP-M*QN Q

S I T N GL&I PU

V#WX"T I HYI NZGUOGPN

S I T N GL&I PU

[ RP"JKGL&Z\I RPR S UT R]QT


M*QN QHRP"J`GLZ\I RP

aGL&Z\I RP-HYbQPUG

a#GL&ZI RP'H\bQPUG

c GUO-GPN S I T N GL&I PUdQN Q

[ RP"J`GL&ZI RP'R S UT R]QT


a#GL&ZI RPH\bQPUG

c GUOGPN S I T N GL&I PU-dQN Q

[ RP#J`GL&ZI RP'R S UT R]QT

RLUQPI ^QN I RPQT_PI N Z

n The task of the ,'RFDSSOLFDWLRQLQWHUIDFHV is to process outbound and inbound IDocs based onmessage types. There is a close relationship between outbound processing and the distributionmodel. The application interfaces for IDocs provide special services for processing messages: Data filtering

Segment filtering Conversion of global organizational units Data conversion in IDoc fields Version change (with Customer Exit ALE0001 FB=EXIT_SAPLBD11_001) Serialization using business objects

n Not all services are provided in both outbound processing and inbound processing. The same appliesto the interface for asynchronous BAPI calls.

SAP AG BC619 4-18

SAP AG 1999

2XWERXQGSURFHVVLQJIRU,'RFV

l 7KHDSSOLFDWLRQSURJUDPGHWHUPLQHVZLWK$3,VRI$/(ZKHWKHUWKHEXVLQHVVREMHFWLVWRGLVWULEXWHG

l 7KHDSSOLFDWLRQSURJUDPILOOVWKHGDWDVWUXFWXUHVIRUWKH,'RFFRQWUROUHFRUGDQGWKH,'RFGDWDUHFRUG7KHGDWDLVWUDQVIHUUHGWRWKHIXQFWLRQPRGXOH0$67(5B,'2&B',675,%87(

l )RUHDFKSRWHQWLDOUHFHLYHU0$67(5B,'2&B',675,%87(FUHDWHVDVHSDUDWHWHPSRUDU\,'RFSURFHVVHVWKH,'RFGDWDLQ,'RFVHUYLFHVDQGLIUHTXLUHGFUHDWHVDQ,'RFIRUHDFKUHFHLYHULQWKHGDWDEDVH

l 7KH,'RFVDUHWUDQVIHUUHGLQWKHFRPPXQLFDWLRQOD\HU7KLVIRUZDUGVWKH,'RFVWRWKHSDUWQHUV\VWHPV

SAP AG BC619 4-19

SAP AG 1999

)ORZ'LDJUDP,'RF2XWERXQG3URFHVVLQJ

$SSOLFDWLRQ &RPPXQLFDWLRQegfihjlknm8opoq4r4q#s tDq#o

uqv+q#o`wxsyz{v(sm8y

)LOO,'RFVWUXFWXUHVDQGIRUZDUGWR$/(

|lo`s(vs&y{}x~&sy4jvm

z%p~&sr#zvsm8ym8\q4r8v&j

fomr4qjjh&mrjzBr4rmBo\u8syB}

v+mzoYvypq#opomBks~q

efh jlkm{or"oq#zBvsy{}hgmrj

$/(

oYq"zBvsyB}xh&mrj

,'RF6HUYLFHV$*&'& & !"

# #!& & !"

!B( #!#"#D#4 !"

$*&-!B( #!

D( #!D!DD

gq4r4q#s(tq#o,q4v+q"o`wsy%z{vsm8y

'HWHUPLQHUHFHLYHUVLIUHTXLUHG

SAP AG BC619 4-20

SAP AG 1999

)ORZ'LDJUDP,'RF,QERXQG3URFHVVLQJ

$SSOLFDWLRQ &RPPXQLFDWLRQ

z4~~4z%p~sr#z{vsm8yk+8yr8vsm8y

wmu8~q

|oKs(vqhgmr2v+mu8z{vzzDjq

)XQFWLRQPRGXOH

$/(

,'RF6HUYLFHV# #!& & !"

!B( #!#"#D#4 !"

$*&-!B( #!

D( #!D!DD

h&,m%rjoq4r4qDstq4u

tszv'

SAP AG BC619 4-21

SAP AG 1999

$/(


ToolsTools

Application Interface for IDocsApplication Interface for IDocs




$SSOLFDWLRQ,QWHUIDFHIRU$V\QFKURQRXV%$3,V

ipE E& 7=

7143K58719B:

;D??%@&98A

pE E& 7%=

713`5871%98:

;4??@&9BA

QL(QO-GN GL#O-QYXXDI PU

M%QN Q S I T N GLI PU

c GUO-GPN S I T N GL&I PU

"I GT d-HYRP#JKGL&Z\I RP

M%GYXDGPdGPH\I GZ

c

GLI QT I ^QN I RP,_\ZI PU-%

BQLQO-GN GL"O'Q\XX"I PU

MQN Q S I T N GL&I PU

c GUO-GPN S I T N GL&I PU

"I GT d'H\RPJ`GLZYI RP

MGKXDGPdGPHYI GZ

c

GL&I QT I ^QN I RP-_ZI PU'*

iE E& 7=

@&9587i198:

;D??%@&98A

ppE nE& 7=

@&9%58719B:

;D?8?@&98A

QLQO-GN GL"O'Q\XXDI PU

BQLQOGN GLOQ\XX"I PU

SAP AG BC619 4-22

SAP AG 1999

$SSOLFDWLRQ,QWHUIDFHIRU$V\QFKURQRXV%$3,V

l 2XWERXQGSURFHVVLQJIRUDV\QFKURQRXV%$3,FDOOVLVVLPLODUWR,'RFSURFHVVLQJ

l ,QDQLQWHULPVWHSWKH$/(LQWHUIDFHFRQYHUWVWKH%$3,SDUDPHWHUVLQWRDQ,'RFZLWKWKHDSSURSULDWHVHJPHQWVWUXFWXUHDQGPHVVDJHW\SH

l )RUWKH$/(XVHUVWKHXVDJHRID%$3,LVWUDQVSDUHQWDQGHTXLYDOHQWWRFODVVLFDOPHVVDJHW\SHV

SAP AG BC619 4-23

SAP AG 1999

)ORZ'LDJUDP$V\QFKURQRXV%$3,2XWERXQG3URFHVVLQJ

egfihjlknm8opoq4r4q#s tDq#o

uqv+q#o`wxsyz{v(sm8y

h&,m%r,pomr4qj4jBsyB}B

pz4ovyq"o%poYmBk s~(q

efh jlkm{or"oq#zBvsy{}hgmrj

$SSOLFDWLRQ &RPPXQLFDWLRQ$/(

)RUZDUG%$3,SDUDPHWHUVWR$/(

'HWHUPLQHUHFHLYHUVLIUHTXLUHG

egsyiv+q#oYkz{r4q2k m8o

z"j8yr"%o\m8ym%4jefhBr#z4~~

oYq"zBvsyB}xh&mrj

|lo`s(vs&y{}x~&sy4jvm

z%p~&sr#zvsm8ym8\q4r8v&j

$/(VHUYLFHV{#&+ !#& #!

$%-

&( !#

$%!B( #!

"(#!D!D4

# #!

SAP AG BC619 4-24

SAP AG 1999

)ORZ'LDJUDP$V\QFKURQRXV%$3,,QERXQG3URFHVVLQJ

$/( &RPPXQLFDWLRQ$SSOLFDWLRQ

%$3,

$/(6HUYLFHV#4 "!

!#

!B( !""&D#"

!"

$% !B( #!

#( #!D!DD

#! !D8 !4

#6K

h,mrjo\qr4q#s(t4quxt"szv

|lo`s(vqhm%rCv+mu{zBvz4%z"j%q

m8ypt4q#ov8hm%rz4yur#z4~~

)efh

SAP AG BC619 4-25

SAP AG 1999

$/( 6KDUHG0DVWHU'DWD7RRO



-QPQUGO-GPNR S

OQZN GL"dQN Q-H\bQPUGZ

'QPQUGO-GPNR S

O-QZN GLDdQN Q'HYbQPUGZ

ToolsTools




6KDUHG0DVWHU'DWD7RRO60'7RRO

n The 6KDUHG0DVWHU'DWD60'7RRO is used for distributing changes to master data It is connectedto the R/3 Engineering Change Management and logs master data changes relevant for distribution

SAP AG BC619 4-26

SAP AG 1999

:KDWLVWKH60'7RRO"

l 7KH60'WRROLVDQLQGHSHQGHQW$/(FRPSRQHQWWKDWHQDEOHVWKHDSSOLFDWLRQWRVHQGPDVWHUGDWDFKDQJHV

l 7KHVHLQFOXGHFKDQJHVWRH[LVWLQJPDVWHUGDWDQHZO\FUHDWHGPDVWHUGDWDDQGGHOHWLRQV

l 7KH60'7RROLVFRQQHFWHGWRWKH5(QJLQHHULQJ&KDQJH0DQDJHPHQWDQGORJVPDVWHUGDWDFKDQJHVUHOHYDQWIRUGLVWULEXWLRQLQFKDQJHSRLQWHUV

l &KDQJHSRLQWHUVFDQEHSURFHVVHGDQGWKHFKDQJHVGLVWULEXWHG

SAP AG BC619 4-27

SAP AG 1999

7HUPV8VHGLQ60'(QYLURQPHQW

l &KDQJHGRFXPHQW. 5FKDQJHVHUYLFHREMHFW

l &KDQJHSRLQWHUV. /RJVFKDQJHVWRPDVWHUGDWDREMHFWVUHOHYDQWIRUGLVWULEXWLRQ

. :ULWHPXVWEHDFWLYDWHGJHQHUDOO\DQGIRUVSHFLILFPHVVDJHW\SHV

l 3URFHVVLQJFKDQJHSRLQWHUV

n Processing change pointers

n Change pointers can be processed manually in ALE Administration or in the background by callingprogram RBDMIDOC. You can restrict processing to a specified message type. Change pointers canalso be processed for extended or reduced message types

n If a change pointer exists for the message type, program RBDMIDOC calls an application functionmodule that creates an IDoc following the rules of master data replication and forwards it to the ALEapplication interface for IDocs.

SAP AG BC619 4-28

SAP AG 1999

$/(

7RROV7RROVDistribution ModelDistribution Model






7RROV

V,_dI N

*V,i_dI N

cD PHYbLRPI ^QN I RPR S

[ _ZN ROI ^I PU'dQN Q

c" PH\bLRPI ^QN I RP-R S

[ _ZN ROI ^I PU-dQN Q

FGd_H\N I RP'R S

OGZZQUG'N XDGZ

F*Gd_H\N I RP-R S

O-GZZQUG-N XDGZ

MRHiL(GH\RJ`GL

M%RHpLGH\RJ`GL

[ RP"J`GL&ZI RP-R S T RUI HQT

Z ZN GOPQO'GZ

[ RP"J`GLZI RP'R S T RUI H\QT

Z ZN GOPQO'GZ

n The ALE tool box contains separate programs for monitoring, modeling and error handling. ALE Audit Synchronization of Customizing data Reduction of message types IDoc recovery following database crash Conversion of logical system names

SAP AG BC619 4-29

SAP AG 1999

Application &Application &



;;*

@ =D436@ 79 E( 7=

@943+>

<

=D>

713`5871%98:

;;

@ =4D36@ 79 E 7%=

@&943+>

l

7143`5B7198:

IDoc dataAsynchronous

;;

@=DD36@ 79 E 7=

@93+>

@&95B7198:

;%;

@ =4436@ 79 E 7=

@943>

<

=D>l

@9%5871%98:

ApplicationApplicationBAPI

'LVWULEXWLRQ0RGHO'LVWULEXWLRQ0RGHO

ToolsTools

,QERXQGIXQFWLRQPRGXOHV

0DVWHUGDWDRXWERXQG)0V

Call BAPI

Synchronous

&RPPXQLFDWLRQOD\HU&RPPXQLFDWLRQOD\HU

,QWHJUDWLQJ$/(&RPSRQHQWVLQWR5

E 7=

>

D?

{98:?

;

>={@

198=43n@ 794?

E( 7=

>

D?

98:?

;

>=B@

19B="36@ 7p94?

E 943>

7

7

={@

198="36@ 794?

E 7=

)>

D?

{98:?

;

>=B@

198=D36@ 794?

E 943+>

<

=4>

7

Documents

Ale