BC417_EN_Col62_FV_Part_A4 - BAPI Devlopment for SAP Components.pdf - BC417-BAPI_Development_for_Accessing_SAP_Components - Ryjufka

BC417

BAPI Development for Accessing

SAP Components

Date

Training Center

Instructors

Education Website

Participant Handbook

Course Version: 62

Course Duration: 3 Day(s)

Material Number: 50084607

An SAP course - use it to learn, reference it for work

No part of this publication may be reproduced or transmitted in any form or for any purpose

without the express permission of SAP AG. The information contained herein may be changed

without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software

components of other software vendors.

Trademarks

Microsoft§, WINDOWS§, NT§, EXCEL§, Word§, PowerPoint§ and SQL Server§ are

registered trademarks of Microsoft Corporation.

IBM§, DB2§, OS/2§, DB2/6000§, Parallel Sysplex§, MVS/ESA§, RS/6000§, AIX§,

S/390§, AS/400§, OS/390§, and OS/400§ are registered trademarks of IBM Corporation.

ORACLE§ is a registered trademark of ORACLE Corporation.

INFORMIX§-OnLine for SAP and INFORMIX§ Dynamic ServerTM are registered

trademarks of Informix Software Incorporated.

UNIX§, X/Open§, OSF/1§, and Motif§ are registered trademarks of the Open Group.

Citrix§, the Citrix logo, ICA§, Program Neighborhood§, MetaFrame§, WinFrame§,

VideoFrame§, MultiWin§ and other Citrix product names referenced herein are trademarks

of Citrix Systems, Inc.

HTML, DHTML, XML, XHTML are trademarks or registered trademarks of W3C§, World

Wide Web Consortium, Massachusetts Institute of Technology.

JAVA§ is a registered trademark of Sun Microsystems, Inc.

JAVASCRIPT§ is a registered trademark of Sun Microsystems, Inc., used under license for

technology invented and implemented by Netscape.

SAP, SAP Logo, R/2, RIVA, R/3, SAP ArchiveLink, SAP Business Workflow, WebFlow, SAP

EarlyWatch, BAPI, SAPPHIRE, Management Cockpit, mySAP.com Logo and mySAP.com

are trademarks or registered trademarks of SAP AG in Germany and in several other countries

all over the world. All other products mentioned are trademarks or registered trademarks of

their respective companies.

Disclaimer

THESE MATERIALS ARE PROVIDED BY SAP ON AN "AS IS" BASIS, AND SAP EXPRESSLY

DISCLAIMS ANY AND ALL WARRANTIES, EXPRESS OR APPLIED, INCLUDING

WITHOUT LIMITATION WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A

PARTICULAR PURPOSE, WITH RESPECT TO THESE MATERIALS AND THE SERVICE,

INFORMATION, TEXT, GRAPHICS, LINKS, OR ANY OTHER MATERIALS AND PRODUCTS

CONTAINED HEREIN. IN NO EVENT SHALL SAP BE LIABLE FOR ANY DIRECT,

INDIRECT, SPECIAL, INCIDENTAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES OF ANY

KIND WHATSOEVER, INCLUDING WITHOUT LIMITATION LOST REVENUES OR LOST

PROFITS, WHICH MAY RESULT FROM THE USE OF THESE MATERIALS OR INCLUDED

SOFTWARE COMPONENTS.

g2008114101614

About This Handbook

This handbook is intended to complement the instructor-led presentation of this

course, and serve as a source of reference. It is not suitable for self-study.

Typographic Conventions

American English is the standard used in this handbook. The following

typographic conventions are also used.

Type Style

Description

Example text

Words or characters that appear on the screen. These

include field names, screen titles, pushbuttons as well

as menu names, paths, and options.

Also used for cross-references to other documentation

both internal (in this documentation) and external (in

other locations, such as SAPNet).

Example text

Emphasized words or phrases in body text, titles of

graphics, and tables

EXAMPLE TEXT

Names of elements in the system. These include

report names, program names, transaction codes, table

names, and individual key words of a programming

language, when surrounded by body text, for example

SELECT and INCLUDE.

Screen output. This includes file and directory names

and their paths, messages, names of variables and

parameters, and passages of the source text of a

program.

Example text

Exact user entry. These are words and characters that

you enter in the system exactly as they appear in the

documentation.

Example text

Variable user entry. Pointed brackets indicate that you

replace these words and characters with appropriate

entries.

iii

2008/Q1

About This Handbook

BC417

Icons in Body Text

The following icons are used in this handbook.

Icon

Meaning

For more information, tips, or background

Note or further explanation of previous point

Exception or caution

Procedures

Indicates that the item is displayed in the instructor's

presentation.

2008/Q1

Contents

CourseOverview......................................................... vii

CourseGoals...........................................................vii

CourseObjectives .....................................................vii

Unit 1: BAPI Fundamentals. .............................................1

BAPI Concepts andUsage ............................................2

BAPI Transaction Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Unit 2: Finding and using SAP suppliedBAPIs................... 25

Finding anSAPdevelopedBAPI.................................... 26

CallingSAPBAPIs fromABAP. .................................... 33

Unit 3: Creating customer specific BAPIs ......................... 47

The Business Scenario. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Tools andNamingConventions..................................... 57

Creating anRFCBusiness Scenario............................... 77

Structural Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Special Considerations............................................... 98

Creating RFC-Enabled Function Modules . . . . . . . . . . . . . . . . . . . . . . . .104

Testing an RFC enabled Function Module. . . . . . . . . . . . . . . . . . . . . . . .124

BusinessObject Repository ........................................131

BusinessObjects ....................................................139

Business Object Components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .151

Logical Unit ofWork .................................................167

Authorizations ........................................................179

Locking................................................................186

Update Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203

Unit 4: BAPIs andRFCs...............................................249

External ABAPCall ..................................................250

WebServices.........................................................267

Unit 5: Enhancement of SAP suppliedBAPIs....................291

Planning aBADI in aBAPI .........................................292

Implementing a BADI of a BAPI. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304

Redefining a method in the BOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .315

Unit 6: BAPIs Using ALE & IDOCs..................................325

ALEand IDOCs ALEBasicConcepts.............................326

2008/Q1

BC417_EN_Col62_FV_Part_A4 - BAPI Devlopment for SAP Components.pdf

Plik z chomika:

Inne pliki z tego folderu:

Inne foldery tego chomika: