1.  SAP AG 2000 Workshop: Business Data Toolset 1 (Carsten Köhler, Ralf Irrgang) Workshop Business Data Toolset (BDT) Carsten Köhler Ralf Irrgang

2.  SAP AG 2000 Workshop: Business Data Toolset 2 (Carsten Köhler, Ralf Irrgang) Contents : 1Overview 2Development with BDT 3Screen Layout 4Screen Sequences 5Program Logic 6GUI Menu 7Field Grouping 8Search Help 9Change Document Evaluation 10Archiving in the Context of the BDT 11Editing Mode 12Calling Maintenance 13 Future Developments

3.  SAP AG 2000 Workshop: Business Data Toolset 3 (Carsten Köhler, Ralf Irrgang) Chapter 1 Overview

4.  SAP AG 2000 Workshop: Business Data Toolset 4 (Carsten Köhler, Ralf Irrgang) Business Data Toolset (BDT): Definition: Toolset for master data and simple transaction data

5.  SAP AG 2000 Workshop: Business Data Toolset 5 (Carsten Köhler, Ralf Irrgang) Design Targets: Extensibility Configurability Divisibility Alternative user interfaces Usability Quicker development Generic BDT services

6.  SAP AG 2000 Workshop: Business Data Toolset 6 (Carsten Köhler, Ralf Irrgang) Extensibility Tables Append/Include structures Own tables Screen layout and screen sequence Program logic Event technique Field checks Data retention

7.  SAP AG 2000 Workshop: Business Data Toolset 7 (Carsten Köhler, Ralf Irrgang) Extensibility : Development cycle Central Data FISD MM TR-TM IS-IS IS-BIS-U DevtPartner1 DevtPartner2 Customer Without modifications Development spread over various systems Central Data FI SD MM TR IBS DevtP. DevtPartner Customer DevtP. SEM C IBSR M C u s t. C u s

8.  SAP AG 2000 Workshop: Business Data Toolset 8 (Carsten Köhler, Ralf Irrgang) Configurability - Screen Layout Street/Number Postcode/City BAS SD Delivery district Transport zone SAP BP Partner Form of address First name Last name Change Business Partner: Partner TESTER Address Name Form of address 01 First name Last name Otto Tester Address Street/Number Postcode/City Lindenstrasse10 69121 Delivery district 1122 Transport zone 123456 Heidelberg

9.  SAP AG 2000 Workshop: Business Data Toolset 9 (Carsten Köhler, Ralf Irrgang) Configurability Customizing Screen Layout/Sequence Configuration via Drag&Drop (Visual Basic) Screen layout and screen sequence Technique Subscreens Generation of screen containers

10.  SAP AG 2000 Workshop: Business Data Toolset 10 (Carsten Köhler, Ralf Irrgang) Divisibility Depending on business criteria, objects can be split into parts. These parts can be maintained individually. Choices Each object can be created in one or several object parts. Example: A business partner can assume different BP roles. A range of attributes is assigned to each BP role. Each object can be created in just one object part Each object is always created as one whole part, no divisibility is required. Example: A contract account is always maintained with all attributes.

11.  SAP AG 2000 Workshop: Business Data Toolset 11 (Carsten Köhler, Ralf Irrgang) Alternative User Interfaces DB_UPDATE Function Module Check Function Module CHECK WEB SAPGUI Data Retention Direct Input Visual Basic etc.

12.  SAP AG 2000 Workshop: Business Data Toolset 12 (Carsten Köhler, Ralf Irrgang) Usability With Any Object SAP BP ApplObject BUPA BDT Others... ApplObject ???? ApplObject BUPR SAP BP- Relationships Bank Account ApplObject BKK IS-RE Contract ApplObject RECN Contract Account ApplObject FICA Claims Capture ApplObject ICL

13.  SAP AG 2000 Workshop: Business Data Toolset 13 (Carsten Köhler, Ralf Irrgang) Service Processing Transactions Field Grouping Change Document Evaluations Data Transfer Notes Authori- zations Development: Without BDT

14.  SAP AG 2000 Workshop: Business Data Toolset 14 (Carsten Köhler, Ralf Irrgang) Service Processing TA Field Grouping Change Doc. Eval. Data Transfer Notes Authorizations Central BDT service Less development work Central BDT service Less development work Quicker Development: With BDT

15.  SAP AG 2000 Workshop: Business Data Toolset 15 (Carsten Köhler, Ralf Irrgang) Generic BDT Services Direct Input Field control (optional, required, hide) Transfer mode Time dependency (interval calculation) Change documents (scheduled change documents) Notes Authorizations Archiving Deletion programs

16.  SAP AG 2000 Workshop: Business Data Toolset 16 (Carsten Köhler, Ralf Irrgang) Chapter 2 Development with the BDT

17.  SAP AG 2000 Workshop: Business Data Toolset 17 (Carsten Köhler, Ralf Irrgang) How the Business Data Toolset (BDT) Is Positioned BDT SAP Basis (DDIC, Development Environment, ABAP...) Bank Account (BKKA) SAP BP Relationships (BUPR) SAP BP (BUPA) Contract Account (FICA) Others...... Application Objects

18.  SAP AG 2000 Workshop: Business Data Toolset 18 (Carsten Köhler, Ralf Irrgang) BDT - Where does Application Development Take Place? SAP BP ApplObj BUPA Application Objects Applications SAP Application I SAP Application II Customer Sub- screen Fubau FuMo Sub- screen Function Group Sub- screen Fubau FuMo Sub- screen Fubau FuMo Sub- screen Function Group Function Group

19.  SAP AG 2000 Workshop: Business Data Toolset 19 (Carsten Köhler, Ralf Irrgang) Applications Applications are assigned to application objects The following can be applications SAP component Development partner Customer Separate function group per application Decoupling Communication with the BDT via event modules Communication between applications with GET modules

20.  SAP AG 2000 Workshop: Business Data Toolset 20 (Carsten Köhler, Ralf Irrgang) Overview: Development with the BDT Applications SAP Application I SAP Application II Customers SAP BP (BUPA) Development DDICDevelopment WBBDT Control Tables

21.  SAP AG 2000 Workshop: Business Data Toolset 21 (Carsten Köhler, Ralf Irrgang) BDT/Development: Data Dictionary... Table: ZZ_...... Table: BUT000... Append ZZ_...  Development in the DDIC Applications SAP Application I SAP Application II Customers

22.  SAP AG 2000 Workshop: Business Data Toolset 22 (Carsten Köhler, Ralf Irrgang) Tables Existing tables can be extended by INCLUDES APPENDS New tables can be created and integrated into the maintenance For each table there is an owning application several participating applications

23.  SAP AG 2000 Workshop: Business Data Toolset 23 (Carsten Köhler, Ralf Irrgang) BDT/Development: Development Workbench Function Group 0010 First Contact Dynpros PBO Module PAI Module... PAI... PBO Function Modules Program logic......_PAI_....._PBO_....._PBC_..... Collect GET... ISDST ISDAT ISSTA Events per application Events per table Events per view

24.  SAP AG 2000 Workshop: Business Data Toolset 24 (Carsten Köhler, Ralf Irrgang) BDT/Development: DWB - Events per Application ISSTA  Initialization ISDAT  Read data from DB ISDST  Distribute data to participating applications FCODE  Edit own function code XCHNG  Check whether data changed DCHCK  Check before saving DSAVB  Collect data with owning application DTAKE  Note data in global memory DSAVC  Complete data (get internal number) DSAVE  Save data in DB DLVE1  Initialize current memory DLVE2  Initialize global memory ISSTA ISDAT ISDST FCODE XCHNG DCHCK DSAVB DSAVC DSAVE DLVE1 DLVE2 DTAKE

25.  SAP AG 2000 Workshop: Business Data Toolset 25 (Carsten Köhler, Ralf Irrgang) BDT/Development: DWB - Events per Table Communication: via Get and Collect Modules Participating Application Participating Application Owning Application..._GET..._COLLECT Call Data Flow Call

26.  SAP AG 2000 Workshop: Business Data Toolset 26 (Carsten Köhler, Ralf Irrgang) BDT/Development: DWB - Events per View Create subscreen with Screen Painter Activate screen type: “subscreen” Create layout Flow logic  PBO module  call  PAI module  call Events - create function modules per view Create FuMo “before the screen call“ Create FuMo “before output” Create FuMo “after input” Geschäftspartner ändern: PartnerTESTER Anschrift Anrede01 Vorname Nachname Otto Tester Lindenstraße10 Name Anschrift Straße/Hausnr Postleitzahl/Ort 69121 Heidelberg ZZ_... Date of first contact Rating of first contact BUS_PAI BUS_PBO

27.  SAP AG 2000 Workshop: Business Data Toolset 27 (Carsten Köhler, Ralf Irrgang) Tables: Exercises Create the APPEND structure ZBUT000 for the table BUT000 with the fields ZZCNT_FIRSTDate of the first contact ZZCNTID Rating of the first contact Create table ZBUTHOBBY with the fields CLIENT ClientKey PARTNERPartner numberKey HOBBYHobbyKey

28.  SAP AG 2000 Workshop: Business Data Toolset 28 (Carsten Köhler, Ralf Irrgang) Chapter 3 Screen Layout

29.  SAP AG 2000 Workshop: Business Data Toolset 29 (Carsten Köhler, Ralf Irrgang) Screen Layout: Targets Extensions and changes to screens are possible Add other fields  in new frames  in existing frames Assign fields differently, even between screens Merge screens No changes to Development Workbench objects of BDT of other applications

30.  SAP AG 2000 Workshop: Business Data Toolset 30 (Carsten Köhler, Ralf Irrgang) Screen Layout: Screen->Section->View Change Partner: Address View 1 View 2 View 3 View 4 View 5 View 6 View 7 View 8 Section 1 Section 2 Section 3 Screen 1 A screen contains one or several sections A section contains one or several views A view is presented by a subscreen

31.  SAP AG 2000 Workshop: Business Data Toolset 31 (Carsten Köhler, Ralf Irrgang) Screen Layout: View (Definition) Properties are summarized in a view if they belong together from a content point of view are tested together View = Subscreen View belongs to an application Assignment view --> field groups (field grouping) Multiple usage of views in object parts is possible (Example: BP roles)

32.  SAP AG 2000 Workshop: Business Data Toolset 32 (Carsten Köhler, Ralf Irrgang) Screen Layout: View (Attributes) Event function module Before output (PBO): Display explanatory texts,... After entry (PAI): Field checks,... Before screen call (PBC): Sort table, begin display with first entry Only display view if the application of the view is active the view is assigned to the maintaining object part/s Processing logic of subscreen Call function module BUS_PBO in PBO (field grouping, messages) Call function module BUS_PAI in PAI (determine cursor position)

33.  SAP AG 2000 Workshop: Business Data Toolset 33 (Carsten Köhler, Ralf Irrgang) Screen Layout: View (Further Checks) Owning application of view Carry out checks in a function module Define name of function modules in the attributes of a view All other applications Carry out checks in an own function module Add name of function module under "Further checks" Important note: Output all error messages via message handler (function module BUS_MESSAGE_STORE)

34.  SAP AG 2000 Workshop: Business Data Toolset 34 (Carsten Köhler, Ralf Irrgang) Screen Layout: Section Assignment section --> views Sequence of views by way of position numbers Frame around a section (exception: header data) Frame title for each section

35.  SAP AG 2000 Workshop: Business Data Toolset 35 (Carsten Köhler, Ralf Irrgang) Screen Layout: Screen Assignment Screen --> Sections Sequence of sections by way of position numbers Presentation as normal screen (full screen) modal dialog box (popup) Screen title for each screen External screens (not created with BDT)

36.  SAP AG 2000 Workshop: Business Data Toolset 36 (Carsten Köhler, Ralf Irrgang) Screen Layout: Screen Containers Consist of subscreen areas and frames (section frames) Assignment screen --> screen container When the screen layout is saved, the system automatically looks for a matching screen container generates a new screen container, if required Transport: Determination of the screen container is conducted during import of data (AFTER_IMP-Method) Restriction: Only subscreens among themselves

37.  SAP AG 2000 Workshop: Business Data Toolset 37 (Carsten Köhler, Ralf Irrgang) Screen Layout: Procedure Change Business Partner: Empty screen container for screen B1

38.  SAP AG 2000 Workshop: Business Data Toolset 38 (Carsten Köhler, Ralf Irrgang) Screen Layout: Procedure Empty screen container for screen B1 Include screen title in screen container title Change Business Partner:Address

39.  SAP AG 2000 Workshop: Business Data Toolset 39 (Carsten Köhler, Ralf Irrgang) Screen Layout: Procedure Empty screen container for screen B1 Include screen title in screen container title Fill 1st view for 1st section Change Business Partner: PartnerTESTER Address

40.  SAP AG 2000 Workshop: Business Data Toolset 40 (Carsten Köhler, Ralf Irrgang) Screen Layout: Procedure Empty screen container for screen B1 Include screen title in screen container title Fill 1st view for 1st section Present title of 2nd section Change Business Partner: Name PartnerTESTER Address

41.  SAP AG 2000 Workshop: Business Data Toolset 41 (Carsten Köhler, Ralf Irrgang) Screen Layout: Procedure Empty screen container for screen B1 Include screen title in screen container title Fill 1st view for 1st section Present title of 2nd section Fill 1st view for 2nd section Change Business Partner: Name PartnerTESTER Address Form of addr.01

42.  SAP AG 2000 Workshop: Business Data Toolset 42 (Carsten Köhler, Ralf Irrgang) Screen Layout: Procedure Empty screen container for screen B1 Include screen title in screen container title Fill 1st view for 1st section Present title of 2nd section Fill 1st view for 2nd section Fill 2nd view for 2nd section Change Business Partner: Name PartnerTESTER Address Form of addr.01 First name Last name Otto Tester

43.  SAP AG 2000 Workshop: Business Data Toolset 43 (Carsten Köhler, Ralf Irrgang) Screen Layout: Procedure Empty screen container for screen B1 Include screen title in screen container title Fill 1st view for 1st section Present title of 2nd section Fill 1st view for 2nd section Fill 2nd view for 2nd section Present title of 3rd section Change Business Partner: Name Address PartnerTESTER Address Form of addr.01 First name Last name Otto Tester

44.  SAP AG 2000 Workshop: Business Data Toolset 44 (Carsten Köhler, Ralf Irrgang) Screen Layout: Procedure Empty screen container for screen B1 Include screen title in screen container title Fill 1st view for 1st section Present title of 2nd section Fill 1st view for 2nd section Fill 2nd view for 2nd section Present title of 3rd section Fill 1st view for 3rd section Change Business Partner: Name Address PartnerTESTER Address Form of addr.01 First name Last name Otto Tester Street/number Postcode/City Lindenstraße10 69121 Heidelberg

45.  SAP AG 2000 Workshop: Business Data Toolset 45 (Carsten Köhler, Ralf Irrgang) Screen Layout: Procedure Empty screen container for screen B1 Include screen title in screen container title Fill 1st view for 1st section Present title of 2nd section Fill 1st view for 2nd section Fill 2nd view for 2nd section Present title of 3rd section Fill 1st view for 3rd section Compress screen Change Business Partner: PartnerTESTER Address Form of addr.01 First name Last name Otto Tester Street/numberLindenstraße10 Name Address Postcode/City69121 Heidelberg

46.  SAP AG 2000 Workshop: Business Data Toolset 46 (Carsten Köhler, Ralf Irrgang) Screen Layout: Exercise 1 Within your function group create two screens (screen category = subscreen!) and incorporate these into the dialog. Screen 0010  Include fields of APPEND structure ZBUT000  Create function modules Before output and After entry  Create view ZCUS10  Create section ZCUS10  Include section ZCUS10 in screen BUP500 Screen 0020  Include fields of table ZBUTHOBBY (Hobbies)  Create function module Before screen call  Create view ZCUS20  Create section ZCUS20  Include section ZCUS20 in screen BUP500

47.  SAP AG 2000 Workshop: Business Data Toolset 47 (Carsten Köhler, Ralf Irrgang) Screen Layout: Exercise 2 Within your function gorup, create a function module, that checks that the last name of a person contains at least one vowel. Include this funtion module as a further check in view BUP300. Create function module Z_ZCUS_BUPA_PAI_BUP300 Include function module as further check for view BUP300

48.  SAP AG 2000 Workshop: Business Data Toolset 48 (Carsten Köhler, Ralf Irrgang) Chapter 4 Screen Sequences

49.  SAP AG 2000 Workshop: Business Data Toolset 49 (Carsten Köhler, Ralf Irrgang) Screen Sequences: Targets Screen sequences at any level Individual additional screens Extend screen sequences to include new screens Integrate screens not created with BDT Change sequence of screens within a screen sequence Navigation between screen sequences/screens with BDT Tabstrips Divisibility: optimum screen sequence for each object part

50.  SAP AG 2000 Workshop: Business Data Toolset 50 (Carsten Köhler, Ralf Irrgang) Screen Sequences: Overview Initial ScreenAddress Bank Details ENTER Next Screen Previous Screen Deletion Flags Bank Data Other Data Back Bank Data Back Addl scrn seq. 2 Main screen seq. Lock Next Screen Previous Screen Other Data Back Addl scrn seq. 1

51.  SAP AG 2000 Workshop: Business Data Toolset 51 (Carsten Köhler, Ralf Irrgang) Screen Sequences: Definition Screen sequence category Levels at which a screen sequence is required Assignment screen sequence category --> screen sequences Screen sequence Sequence of screens by way of position numbers Main screen sequence: Assignment object part --> screen sequence Standard screen sequence Any screens possible  BDT screens  External screens (by calling a function module)

52.  SAP AG 2000 Workshop: Business Data Toolset 52 (Carsten Köhler, Ralf Irrgang) Screen Sequences: Other Screen Sequences Jump from a screen of another screen sequence Realization: Alternatives Define screen sequence category when defining GUI function Call function module BUS_SCREEN_CALL at event FCODE Navigation options Menu (edit, extras, environment) Freely positionable push buttons

53.  SAP AG 2000 Workshop: Business Data Toolset 53 (Carsten Köhler, Ralf Irrgang) Chapter 5 Program Logic

54.  SAP AG 2000 Workshop: Business Data Toolset 54 (Carsten Köhler, Ralf Irrgang) Program Logic: Targets Use program logic for Dialog maintenance via the standard user interface Dialog maintenance via an external user interface (in R/3 or a non-R/3 system) Maintenance without dialog (direct input or function modules) Decouple program logic from the user interface Foreign key checks not at the user interface Data category checks not at the user interface Extensions without changes to Development Workbench objects of BDT of other applications

55.  SAP AG 2000 Workshop: Business Data Toolset 55 (Carsten Köhler, Ralf Irrgang) Program Logic: Event Technique Communication Between BDT and applications Between applications Defined events Within maintenance dialog With different generic BDT services Assignment event --> event function module Define name in control tables Dynamic call via BDT Sequence of event function modules by way of position numbers

56.  SAP AG 2000 Workshop: Business Data Toolset 56 (Carsten Köhler, Ralf Irrgang) Program Logic: Events (Dialog) Event table Views Tables Field groups (see field grouping) Field grouping criteria (see field grouping)

57.  SAP AG 2000 Workshop: Business Data Toolset 57 (Carsten Köhler, Ralf Irrgang) Program Logic: Event Table ISSTAInitialization ISDATRead data from DB ISDSTDistribute data to participating applications FCODE Edit own function code XCHNG Check whether data changed DCHCK Check before saving DSAVB Collect data with owning application DTAKENote data in global memory DSAVC Complete data (get internal number) DSAVESave data in DB

58.  SAP AG 2000 Workshop: Business Data Toolset 58 (Carsten Köhler, Ralf Irrgang) Program Logic: Views Before Call (PBC) Begin with first data record (table control) Sort data records (table control) Before Output (PBO) Read tables for explanatory texts After Entry (PAI) Field checks

59.  SAP AG 2000 Workshop: Business Data Toolset 59 (Carsten Köhler, Ralf Irrgang) Program Logic: Events, Flow

60.  SAP AG 2000 Workshop: Business Data Toolset 60 (Carsten Köhler, Ralf Irrgang) Program Logic: Tables (Service Function Modules) Communication between applications Distribute data (Event ISDAT or ISDST) Data from owning application to participating application Creator: owning application Table BUT000: BUP_BUPA_BUT000_GET Collect data (Event DSAVB) Data from participating application to owning application Creator: owning application Table BUT000: BUP_BUPA_BUT000_COLLECT

61.  SAP AG 2000 Workshop: Business Data Toolset 61 (Carsten Köhler, Ralf Irrgang) Global Memory vs. Current Memory Current memory table-owning application each table-participating application Global memory only the table-owning application

62.  SAP AG 2000 Workshop: Business Data Toolset 62 (Carsten Köhler, Ralf Irrgang) Data Administration: Owning Application Function Group DB DSAVE DTAKE ISDAT Current Memory newold Global Memory oldnew

63.  SAP AG 2000 Workshop: Business Data Toolset 63 (Carsten Köhler, Ralf Irrgang) Data Administration: Participating Application Function Group Owning Application Function Group Participating Application DB DSAVE DTAKE ISDAT Current Memory newold Global Memory oldnew DSAVB ISDST (Get FuMo) (Collect FuMo) Current Memory newold

64.  SAP AG 2000 Workshop: Business Data Toolset 64 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Starting Situation) Table BUT000 Owner: SAP BP Key fields INCLUDE for SAP BP APPEND for FI APPEND for Customer Table FIBUB1 Owner: FI Key fields INCLUDE for FI APPEND for Customer Applications : SAP BP Financial Accouting (FI) Customer Tables :

65.  SAP AG 2000 Workshop: Business Data Toolset 65 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read Data) Applications : Financial Accounting (FI) Customer Event ISDAT (Read data) SAP BP

66.  SAP AG 2000 Workshop: Business Data Toolset 66 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000Event ISDAT (Read data)

67.  SAP AG 2000 Workshop: Business Data Toolset 67 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 BUT000 Event ISDAT (Read data)

68.  SAP AG 2000 Workshop: Business Data Toolset 68 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 Get BUT000 BUT000 Event ISDAT (Read data)

69.  SAP AG 2000 Workshop: Business Data Toolset 69 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 GET- Funct.modules Get BUT000 BUT000 Event ISDAT (Read data)

70.  SAP AG 2000 Workshop: Business Data Toolset 70 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 Service- funct. modules Get BUT000 BUT000 Event ISDAT (Read data)

71.  SAP AG 2000 Workshop: Business Data Toolset 71 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 Service- funct. modules Get BUT000 BUT000 Read FIBUB1 Event ISDAT (Read data)

72.  SAP AG 2000 Workshop: Business Data Toolset 72 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 Service- funct. modules Get BUT000 BUT000 FIBUB1BUT000 Read FIBUB1 Event ISDAT (Read data)

73.  SAP AG 2000 Workshop: Business Data Toolset 73 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Event ISDST (Distribute data) Read BUT000 Service- funct. modules Get BUT000 BUT000 FIBUB1BUT000 Read FIBUB1 Event ISDAT (Read data)

74.  SAP AG 2000 Workshop: Business Data Toolset 74 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 Get BUT000 Service- funct. modules Get BUT000 BUT000 FIBUB1BUT000 Read FIBUB1 BUT000 FIBUB1BUT000 Event ISDAT (Read data) Event ISDST (Distribute data)

75.  SAP AG 2000 Workshop: Business Data Toolset 75 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 Get BUT000 Service- funct. modules Get BUT000 BUT000 FIBUB1BUT000 Read FIBUB1 BUT000 FIBUB1BUT000 Event ISDAT (Read data) Event ISDST (Distribute data)

76.  SAP AG 2000 Workshop: Business Data Toolset 76 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 Get BUT000 Service- funct. modules Get BUT000 BUT000 FIBUB1 BUT000 Read FIBUB1 BUT000 FIBUB1BUT000 Event ISDAT (Read data) Event ISDST (Distribute data)

77.  SAP AG 2000 Workshop: Business Data Toolset 77 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 Get BUT000 Get FIBUB1 Service- funct. modules Get BUT000 BUT000 FIBUB1 BUT000 Read FIBUB1 BUT000 FIBUB1BUT000 Event ISDAT (Read data) Event ISDST (Distribute data)

78.  SAP AG 2000 Workshop: Business Data Toolset 78 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 Get BUT000 Get FIBUB1 Service- funct. modules Get BUT000 BUT000 FIBUB1 BUT000 Read FIBUB1 BUT000 FIBUB1BUT000 Event ISDAT (Read data) Event ISDST (Distribute data)

79.  SAP AG 2000 Workshop: Business Data Toolset 79 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Read data) Applications : SAP BP Financial Accounting (FI) Customer Read BUT000 Get BUT000 Get FIBUB1 Service- funct. modules Get BUT000 BUT000 FIBUB1 BUT000FIBUB1 BUT000 Read FIBUB1 BUT000 FIBUB1BUT000 Event ISDAT (Read data) Event ISDST (Distribute data)

80.  SAP AG 2000 Workshop: Business Data Toolset 80 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Event DSAVB (Collect data)

81.  SAP AG 2000 Workshop: Business Data Toolset 81 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 BUT000 FIBUB1 Event DSAVB (Collect data) BUT000FIBUB1

82.  SAP AG 2000 Workshop: Business Data Toolset 82 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 Service- funct. modules BUT000 FIBUB1 Event DSAVB (Collect data) BUT000FIBUB1

83.  SAP AG 2000 Workshop: Business Data Toolset 83 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 Service- funct. modules BUT000 FIBUB1 Event DSAVB (Collect data) BUT000FIBUB1

84.  SAP AG 2000 Workshop: Business Data Toolset 84 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data)

85.  SAP AG 2000 Workshop: Business Data Toolset 85 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data) Transfer BUT000

86.  SAP AG 2000 Workshop: Business Data Toolset 86 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data)

87.  SAP AG 2000 Workshop: Business Data Toolset 87 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 Transfer FIBUB1 Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data)

88.  SAP AG 2000 Workshop: Business Data Toolset 88 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 Transfer FIBUB1 Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data)

89.  SAP AG 2000 Workshop: Business Data Toolset 89 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 Transfer FIBUB1 Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data)

90.  SAP AG 2000 Workshop: Business Data Toolset 90 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Event DTAKE (Transfer data) Transfer BUT000 Transfer FIBUB1 Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data)

91.  SAP AG 2000 Workshop: Business Data Toolset 91 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 BUT000 in Global Memory Transfer BUT000 Transfer FIBUB1 Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data) Event DTAKE (Transfer data)

92.  SAP AG 2000 Workshop: Business Data Toolset 92 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 BUT000 in Global Memory Transfer BUT000 Transfer FIBUB1 FIBUB1 in Global Memory Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data) Event DTAKE (Transfer data)

93.  SAP AG 2000 Workshop: Business Data Toolset 93 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 BUT000 in Global Memory Transfer BUT000 Transfer FIBUB1 FIBUB1 in Global Memory Event DSAVE (Save data) Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data) Event DTAKE (Transfer data)

94.  SAP AG 2000 Workshop: Business Data Toolset 94 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 BUT000 in Global Memory Transfer BUT000 Transfer FIBUB1 FIBUB1 in Global Memory BUT000 in DB Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data) Event DTAKE (Transfer data) Event DSAVE (Save data)

95.  SAP AG 2000 Workshop: Business Data Toolset 95 (Carsten Köhler, Ralf Irrgang) Program Logic: Example (Save data) Applications : SAP BP Financial Accounting (FI) Customer Transfer BUT000 BUT000 in Global Memory Transfer BUT000 Transfer FIBUB1 FIBUB1 in Global Memory BUT000 in DB FIBUB1 in DB Service- funct. modules BUT000 FIBUB1 BUT000FIBUB1 Event DSAVB (Collect data) Event DTAKE (Transfer data) Event DSAVE (Save data)

96.  SAP AG 2000 Workshop: Business Data Toolset 96 (Carsten Köhler, Ralf Irrgang) Program Logic: Exercise 1 Create the program logic for maintenance of the two fields in table BUT000 (first contact). Event ISSTA: Query controlling parameters in the BDT and note (example: activity category) Event ISDAT: Get data in table BUT000 from the owning application and note in the current memory (not until ISDST because of Exercise 2!) Event XCHNG: Check if there are any changes to the fields for the first contact Event DSAVB: Return data from the current memory for table BUT000 with the changes in the fields for the first contact to the owning application Event DLVE1: Initialize current memory for table BUT000

97.  SAP AG 2000 Workshop: Business Data Toolset 97 (Carsten Köhler, Ralf Irrgang) Program Logic: Exercise 2 Create the program logic for maintenance of table ZBUTHOBBY (Hobbies). Event ISSTA: Already created in Exercise 1 Event ISDAT: Read data from the database or from the global memory Event XCHNG: Check if there any changes Event DTAKE: Transfer data from the current memory to the global memory Event DSAVC: Complete data in the global memory (create with internal number assignment) Event DSAVE: Write data from global memory to database Event DLVE1: Initialize current memory Event DLVE2: Initialize global memory View ZCUS20  Before Call (PBC)

98.  SAP AG 2000 Workshop: Business Data Toolset 98 (Carsten Köhler, Ralf Irrgang) Chapter 6 GUI Menu

99.  SAP AG 2000 Workshop: Business Data Toolset 99 (Carsten Köhler, Ralf Irrgang) GUI Menu: Targets Own menu with standard functions for each appl. object Add additional functions Activate/deactivate functions per activity per view per screen sequence category on basis of additional program logic Link menu function freely positional push button Extensions to GUI Menu without changes to Development Workbench objects of BDT of other applications

100.  SAP AG 2000 Workshop: Business Data Toolset 100 (Carsten Köhler, Ralf Irrgang) Contained in standard menu Activate/deactivate in system tables per activity per activity / view per activity /view/screen sequence category GUI Menu: Standard Functions Lowest priority Highest priority

101.  SAP AG 2000 Workshop: Business Data Toolset 101 (Carsten Köhler, Ralf Irrgang) Can be included in the standard menu Can be reached via the function "Additional functions" in every menu Presentation in an additional dialog box Activate/deactivate in system tables per activity per activity/view per activity/view/screen sequence category GUI Menu: Additional Functions Lowest priority Highest priority

102.  SAP AG 2000 Workshop: Business Data Toolset 102 (Carsten Köhler, Ralf Irrgang) Function Save Active Create ChangeDisplay Function Delete bank details Active CreateChange Display Active Bank detailsCreateChangeDisplay Function Address overview Active CreateChange Display Active Address data CreateChangeDisplay Active Addr.data//Main scrn seq.Create ChangeDisplay GUI Menu: Functions (Examples)

103.  SAP AG 2000 Workshop: Business Data Toolset 103 (Carsten Köhler, Ralf Irrgang) GUI Menu: Events DCUAD (Determine GUI status) Standard menu with GUI status is in the application function group of the application owning the application object Application can set the desired GUI status DCUAC (Change GUI status) Programmed activation/deactivation of GUI functions  Function 'Delete bank' is inactive if field group 'Bank details' is either hidden or just displayed  Scroll functions only active with large number of entries

104.  SAP AG 2000 Workshop: Business Data Toolset 104 (Carsten Köhler, Ralf Irrgang) GUI Menu: Exercise 1 Make it possible to delete hobbies during maintenance. Do this using an own GUI function. Create additional function ZCUS_HOBBY_DELE  Assign function to the Edit menu  Function may only be active if activity category is Create or Change, and not Display hobbies (View ZCUS20) are on the current screen Event FCODE: Create program logic for handling the deletion function

105.  SAP AG 2000 Workshop: Business Data Toolset 105 (Carsten Köhler, Ralf Irrgang) Chapter 7 Field Grouping

106.  SAP AG 2000 Workshop: Business Data Toolset 106 (Carsten Köhler, Ralf Irrgang) Field Grouping: Targets Field status Required entry Optional entry Display Hide Determine field status of related fields together Different field grouping criteria Field grouping criteria of applications can be added (Examples in GP: Company code through FI, sales organization through SD) Programmed field grouping

107.  SAP AG 2000 Workshop: Business Data Toolset 107 (Carsten Köhler, Ralf Irrgang) Field Grouping: Field Groups Group fields into field groups if they belong together logically are displayed/hidden together Field grouping per field group Function module for programmed field grouping Assignment view --> field groups Assignment field group --> screen fields SORT 1 SORT 2 Field Groups Search terms Fields NAME_ORG1 Name 1

108.  SAP AG 2000 Workshop: Business Data Toolset 108 (Carsten Köhler, Ralf Irrgang) Field Grouping: Field Status Bar Field status + Required entry. Optional entry * Display - Hide SPACENot specified Position in status bar corresponds to field group number (at present: max. 1750 field groups) Field status bar 1 (200 characters) + *. - * 13 Field group: 2 Field status bar 2Field status bar 3.........

109.  SAP AG 2000 Workshop: Business Data Toolset 109 (Carsten Köhler, Ralf Irrgang) Field Grouping: Add Criterion Create table (such as TB103) Create view (such as V_TB103) and generate maintenance dialog Include maintenance user interface for field status in view Function 'Field Grouping' (using SAPLBUS2) Function module BUS_FMOD_CUSTOMIZING Enter criterion in control table Create function module for reading field status bar and define name in control table

110.  SAP AG 2000 Workshop: Business Data Toolset 110 (Carsten Köhler, Ralf Irrgang) Field Grouping: Exercise 1 Link views ZCUS10 and ZCUS20 to the field grouping. Create field groups for data on first contact and hobbies, and assign the fields in the subscreens.  700First contact: Date  701First contact: Evaluation  702Hobbies Assign field groups to views  View ZCUS10Field groups 700, 701  View ZCUS20Field group 702 Hide the GUI function "Delete hobby" if the fields of the field group are not ready for input (event DUAC) Test the field grouping by hiding the fields for the BP role Test role.

111.  SAP AG 2000 Workshop: Business Data Toolset 111 (Carsten Köhler, Ralf Irrgang) Chapter 8 Search Help

112.  SAP AG 2000 Workshop: Business Data Toolset 112 (Carsten Köhler, Ralf Irrgang) Search Help: Targets Each application can add elementary search helps Activate/deactivate elementary search helps Direct selection possible via '=...' Extensions without change to Development Workbench objects of BDT of other applications

113.  SAP AG 2000 Workshop: Business Data Toolset 113 (Carsten Köhler, Ralf Irrgang) Search Helps up to Release 4.5: Assign Elem.Search Help --> Pseudo ID Search Help BUPA (SAP BP data) BUPAB Partner acc. to bank details BUPAN Partner acc. to name, address Tables: BUT000, BUT010, ADRC Search Help BUFI (FI) BUFIB Partner acc. to company code Tables: BUT000, BUT010, ADRC, FIBUB1 Search Help BUSD (SD) BUSDV Partner acc. to sales area Tables: BUT000, BUT010, ADRC, SDBUVV Pseudo-ID Search help El SH Active? ID Name/Description Define all elementary search helps in BDT control table Inactive elementary search helps do not appear B BUPAB C BUFI B X N BUPAN X V BUSDV X C Partner acc. to company code N Partner acc. to name, address V Partner acc. to sales area

114.  SAP AG 2000 Workshop: Business Data Toolset 114 (Carsten Köhler, Ralf Irrgang) Search Helps as from Release 4.6: APPEND-Search Helps Search help of a different application can be extended via the dictionary without changing the original search help Maintenance Transaction SE11 Function Goto --> APPEND search helps BDT control table is no longer required

115.  SAP AG 2000 Workshop: Business Data Toolset 115 (Carsten Köhler, Ralf Irrgang) Chapter 9 Change Document Evaluations

116.  SAP AG 2000 Workshop: Business Data Toolset 116 (Carsten Köhler, Ralf Irrgang) Change Document Evaluation: Targets Generic BDT service Evaluation variants In dialog  Changes per object instance (such as partner changes)  Changes per object instance and field (field changes) As a report  Change history (over several instances) Divisibility Add new tables Add additional fields to existing tables No changes to Development Workbench objects of BDT of other applications

117.  SAP AG 2000 Workshop: Business Data Toolset 117 (Carsten Köhler, Ralf Irrgang) Change Document Evaluation: Realization Write change documents Change document object per application (if own table exists!) Write change documents in event DSAVE Evaluate change documents Events  Event CHGD1Transfer selection values  Event CHGD2Collect change doc. objects with IDs  Event CHGD3Change doc. Header relevant?  Event CHGD4Change doc. Item relevant? Call  Changes per object instanceGUI function BUSA  Changes per obj.instance & fieldGUI function BUSI  Change historyReport BUSCHDOC

118.  SAP AG 2000 Workshop: Business Data Toolset 118 (Carsten Köhler, Ralf Irrgang) Chapter 10 Archiving in the Context of the BDT

119.  SAP AG 2000 Workshop: Business Data Toolset 119 (Carsten Köhler, Ralf Irrgang) Archiving in the Context of the BDT Standard SAP Archiving Archiving object Use of the ADK FuMo Archiving administration with transaction SARA Service programs in the BDT Program logic in reports Processing of the application data by event function modules

120.  SAP AG 2000 Workshop: Business Data Toolset 120 (Carsten Köhler, Ralf Irrgang) Archiving: Program Run in the BDT Enter data Check data Sort data Create archive Write archive Close archive Log Enter data ARCH1 Sort data Create archive ARCH2/3 Close archive Log Check data Write archive with BDT Applications without BDT

121.  SAP AG 2000 Workshop: Business Data Toolset 121 (Carsten Köhler, Ralf Irrgang) ARCH1 Application-specific ARCH2.. *------ Write data to the archive ---------------------------------- call function 'ARCHIVE_PUT_RECORD‘ exporting archive_handle = p_archive_handle record = lt_but000 record_flags = et_chart-del_flag record_structure = 'BUT000'. Endfunction. Archiving: Event Function Modules Only call of a ADK FuMo

122.  SAP AG 2000 Workshop: Business Data Toolset 122 (Carsten Köhler, Ralf Irrgang) Archiving: Programs BUSOBARCH for archiving data ARCH1check if data can be archived ARCH2/3archive header data and dependent data BUSOBARCH_DELETE for consistent deletion from the completely written archive ARCH4Interprete archive data and delete on the database BUSOBARCH_RELOAD for reloading from archives ARCH5Interpret archive data and check if it can be reloaded ARCH6Interpret transferred data and write it to the database

123.  SAP AG 2000 Workshop: Business Data Toolset 123 (Carsten Köhler, Ralf Irrgang) Archiving: Procedure Create archiving object Transaction AOBJ Register archiving object in the BDT BDT task level menu  General control  Application objects Create event function modules and register in the BDT BDT task level menu  Control  Events  Assign event-> Function modules

124.  SAP AG 2000 Workshop: Business Data Toolset 124 (Carsten Köhler, Ralf Irrgang) Chapter 11 Editing Mode

125.  SAP AG 2000 Workshop: Business Data Toolset 125 (Carsten Köhler, Ralf Irrgang) Editing Mode: Targets Save mode Changes to a BP are saved before leaving maintenance or discarded Transfer mode Example:  Contract calls BP maintenance  BP data is noted  The BP data is not saved until the contract is saved Realization for all data including address data Direct Input: Enable mass insert/update

126.  SAP AG 2000 Workshop: Business Data Toolset 126 (Carsten Köhler, Ralf Irrgang) Editing Mode: Save Mode Event DSAVB Collect data Event DTAKE Note data Event DSAVC Complete data Function ‘Save' SAP GP Event DSAVE Save data

127.  SAP AG 2000 Workshop: Business Data Toolset 127 (Carsten Köhler, Ralf Irrgang) Editing Mode: Transfer Mode Contract Contr.no. Contr.type Policyholder Beneficiary Change Save Event DSAVB Collect data Event DTAKE Note data Event DSAVC Complete data Function ‘Transfer' SAP GP Event DSAVE Save data

128.  SAP AG 2000 Workshop: Business Data Toolset 128 (Carsten Köhler, Ralf Irrgang) Edit Mode: Direct Input (Flow) Initial Screen: Entries Initial Screen: PAI Event ISDAT (Read data) Event ISDST (Distribute data) Data screen: Entries Data screen: PAI Event DSAVB (Collect data) Event DTAKE (Transfer data) Event DSAVE (Save data) Initial Screen: Data from file Initial Screen PAI Event ISDAT (Read data) Event ISDST (Distribute data) Data screen: Data from file Data screen PAI Event DSAVB (Collect data) Event DTAKE (Transfer data) Event DSAVE (Save data) Important: Mass insert/update!! Dialog Direct Input

129.  SAP AG 2000 Workshop: Business Data Toolset 129 (Carsten Köhler, Ralf Irrgang) Edit Mode: Direct Input (Events) DINP1Get header data DINP2Get data records and note

130.  SAP AG 2000 Workshop: Business Data Toolset 130 (Carsten Köhler, Ralf Irrgang) Edit Mode: Direct Input (Data Transfer) Entry file Rec.cat. Table Delete flag Data 2 BUT000 SPACE 0030001234567... 2 BUT020 SPACE 0030001234567... 2 BUT021 SPACE 0031122334455... 2 BUT0BK SPACE 0030001234567... BDT Data records distribute to applications SAP BP data 2 BUT000 SPACE 0030001234567... 2 BUT0BK SPACE 0030001234567... SAP BP addresses 2 BUT020 SPACE 0030001234567... 2 BUT021 SPACE 0031122334455... Function module1 Function module2

131.  SAP AG 2000 Workshop: Business Data Toolset 131 (Carsten Köhler, Ralf Irrgang) Chapter 12 Calling Maintenance

132.  SAP AG 2000 Workshop: Business Data Toolset 132 (Carsten Köhler, Ralf Irrgang) Calling Maintenance: Without Object Part Transaction BUP2Report BUPSTART CALL FUNCTION 'BUP_PARTNER_ MAINTAIN'. Change BP Report Partner Screen selection Address Payment trans. BUPSTART........ Choose BP role Installer Contract partner Continue X

133.  SAP AG 2000 Workshop: Business Data Toolset 133 (Carsten Köhler, Ralf Irrgang) Calling Maintenance: With Object Part Transaction FPP2Report RFKKBUPA CALL FUNCTION 'BUP_PARTNER_ MAINTAIN' TABLES T_RLTYP = GT_RLTYP Change BP Report Partner Screen selection Address Payment trans. RFKKBUPA........ Choose BP role Installer Contract partner Continue

134.  SAP AG 2000 Workshop: Business Data Toolset 134 (Carsten Köhler, Ralf Irrgang) Chapter 13 Future Developments

135.  SAP AG 2000 Workshop: Business Data Toolset 135 (Carsten Köhler, Ralf Irrgang) Future Developments: Mass changes (using logistics tool) Field defaults Evaluations (using list tool) Generate application coding Relationships between any objects

136.  SAP AG 2000 Workshop: Business Data Toolset 136 (Carsten Köhler, Ralf Irrgang) BDT