workshop business data toolset (bdt)

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

Workshop

Business Data Toolset (BDT)

Carsten KöhlerRalf Irrgang


Contents:

1 Overview2 Development with BDT3 Screen Layout4 Screen Sequences5 Program Logic6 GUI Menu7 Field Grouping8 Search Help9 Change Document Evaluation10 Archiving in the Context of the BDT11 Editing Mode12 Calling Maintenance13 Future Developments


Chapter 1

Overview


Business Data Toolset (BDT):

Definition: Toolset for master data and simple transaction data


Design Targets:

Extensibility

Configurability

Divisibility

Alternative user interfaces

Usability

Quicker development

Generic BDT services


Extensibility

Tables Append/Include structures

Own tables

Screen layout and screen sequence

Program logic Event technique

Field checks

Data retention


Extensibility : Development cycle

CentralData

FI SD

MM

TR-TMIS-IS

IS-BIS-U

DevtPartner1

DevtPartner2

Customer

Without modifications

Developmentspread over various systems

CentralData

FISD

MM

TRIBS

DevtP.

DevtPartner

Customer

DevtP.

SEM

CIBS R

M

Cust.

Cust.


Configurability - Screen Layout

Street/NumberPostcode/CityBAS

SD Delivery districtTransport zone

SAP BPPartnerForm 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

Lindenstrasse 10

69121

Delivery district

1122Transport zone

123456

Heidelberg


ConfigurabilityCustomizing Screen Layout/Sequence

Configuration via Drag&Drop (Visual Basic)

Screen layout and screen sequence

Technique Subscreens

Generation of screen containers


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.


Alternative User Interfaces

DB_UPDATE Function Module

CheckFunction Module

CHECK

WEBSAPGUI

DataRetention

Direct Input

Visual Basic etc.


Usability With Any Object

SAP BP

ApplObject BUPA

BDT

Others ...

ApplObject ????

ApplObject BUPR

SAP BP- Relationships

Bank Account

ApplObject BKK

IS-REContract

ApplObject RECN

ContractAccount

ApplObject FICA

ClaimsCapture

ApplObject ICL


Service

ProcessingTransactions

FieldGrouping

ChangeDocumentEvaluations

Data Transfer

NotesAuthori-zations

Development: Without BDT


ServiceProcessing TA

Fiel

d G

roup

ing

Change D

oc. Eval.

Data Transfer

NotesAuthorizations

Central BDT service Less development work

Quicker Development: With BDT


Generic BDT Services

Direct InputField control (optional, required, hide)Transfer modeTime dependency (interval calculation)Change documents (scheduled change documents)NotesAuthorizationsArchivingDeletion programs


Chapter 2

Development with the BDT


How the Business Data Toolset (BDT) Is Positioned

BDT

SAP Basis (DDIC, Development Environment, ABAP...)

Bank Account(BKKA)

SAPBP Relationships(BUPR)

SAP BP(BUPA)

Contract Account(FICA)

Others......

Application Objects


BDT - Where does Application Development Take Place?

SAP BPApplObj BUPA

Application Objects

Applications

SAPApplication I

SAP Application II Customer

Sub-screenFubauFuMo Sub-

screen

Function Group

Sub-screenFubauFuMo Sub-

screenSub-

screenFubauFuMo Sub-screen

Function Group

Function Group


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


Overview: Development with the BDT

ApplicationsSAP

Application ISAP

Application II Customers

SAP BP(BUPA)

Development

DDIC Development WB BDT Control Tables


BDT/Development: Data Dictionary

...

...

...

Table: ZZ_...

...

...

...Table: BUT000

...

...

...

AppendZZ_...ZZ_...

Development in the DDIC

ApplicationsSAP

Application ISAP

Application II Customers


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


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

ISSTAEvents per application

Events per table

Events per view


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


BDT/Development: DWB - Events per Table

Communication: via Get and

Collect Modules ParticipatingApplication

ParticipatingApplication

OwningApplication

..._GET

..._COLLECT

Call

Data Flow

Data FlowCall


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:

Partner TESTER

Anschrift

Anrede 01VornameNachname

OttoTester

Lindenstraße 10

Name

AnschriftStraße/HausnrPostleitzahl/Ort 69121 Heidelberg

ZZ_...Date of first contactRating of first contact

BUS_PAI

BUS_PBO


Tables: Exercises

Create the APPEND structure ZBUT000 for the table BUT000 with the fields ZZCNT_FIRST Date of the first contact ZZCNTID Rating of the first contact

Create table ZBUTHOBBY with the fields CLIENT Client Key PARTNER Partner number Key HOBBY Hobby Key


Chapter 3

Screen Layout


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


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


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)


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)


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)


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


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)


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


Screen Layout: Procedure

Change Business Partner: Empty screen container for screen B1



Empty screen container for screen B1 Include screen title in screen container

title

Change Business Partner:Address




title Fill 1st view for 1st section


Partner TESTER

Address




title Fill 1st view for 1st section Present title of 2nd section


Name

Partner TESTER

Address




title Fill 1st view for 1st section Present title of 2nd section Fill 1st view for 2nd section


Name

Partner TESTER

Address

Form of addr. 01




title Fill 1st view for 1st section Present title of 2nd section Fill 1st view for 2nd section Fill 2nd view for 2nd section


Name

Partner TESTER

Address

Form of addr. 01

First nameLast name

OttoTester




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


Name

Address

Partner TESTER

Address

Form of addr. 01

First nameLast name

OttoTester




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


Name

Address

Partner TESTER

Address

Form of addr. 01

First nameLast name

OttoTester

Street/numberPostcode/City

Lindenstraße 1069121 Heidelberg




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


Partner TESTER

Address

Form of addr. 01First nameLast name

OttoTester

Street/number Lindenstraße 10

Name

Address

Postcode/City 69121 Heidelberg


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


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


Chapter 4

Screen Sequences


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


Screen Sequences: Overview

Initial Screen Address BankDetailsENTER

Next Screen

Previous Screen

DeletionFlags Bank Data

OtherData

Back BankData

Back

Addl scrn seq. 2

Main screen seq.

LockNextScreen

PreviousScreen

OtherData

Back

Addl scrn seq. 1


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)


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


Chapter 5

Program Logic


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


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


Program Logic: Events (Dialog)

Event table Views Tables Field groups (see field grouping) Field grouping criteria (see field grouping)


Program Logic: Event Table

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


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


Program Logic: Events, Flow

Initial screen

CALL SUBSCREEN

Before Output

CALL SUBSCREEN

After Input

ISSTABeforeCall

Data screen

CALL SUBSCREEN

Before Output

CALL SUBSCREEN

After Input

ISDAT

ISDSTAUTH1

BeforeCall

Save Back Exit Cancel

XCHNG

Change?

Yes

DSAVB

AUTH1DCHCKDTAKEDSAVCDSAVE

No

XCHNG

Change? No

Save?No

Yes

DSAVB


Yes

A

Abbr.

A

XCHNG

Change? No

Save?No

Yes

DSAVB


Yes

A

Abbr.

XCHNG

Change? No

Cancel?

No

Yes

Yes

A

DLVE1DLVE2

Start

End

DTITL

DCUAD DCUAC

FCODE

DTITL

DCUAD DCUAC

FCODE

Screen 1: Events with Dialog, Save Mode


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


Global Memory vs. Current Memory

Current memory table-owning application each table-participating application

Global memory only the table-owning application


Data Administration: Owning ApplicationFu

nctio

n G

roup

DB

DSAVE

DTAKE

ISDAT

Current Memory

new old

GlobalMemory

oldnew


Data Administration: Participating Application

Function Group Owning Application

Function GroupParticipatingApplication

DB

DSAVE

DTAKE

ISDAT

CurrentMemory new old

Global Memory oldnew

DSAVB

ISDST(Get FuMo)

(Collect FuMo)

CurrentMemory new old


Program Logic: Example (Starting Situation)

Table BUT000Owner: SAP BP

Key fields

INCLUDE for SAP BP

APPEND for FI

APPEND for Customer

Table FIBUB1Owner: FI

Key fields

INCLUDE for FI

APPEND for Customer

Applications: SAP BPFinancial Accouting (FI)Customer

Tables:


Program Logic: Example (Read Data)

Applications:Financial Accounting (FI)Customer

Event ISDAT(Read data)

SAP BP


Program Logic: Example (Read data)

Applications: SAP BPFinancial Accounting (FI)Customer

Read BUT000 Event ISDAT(Read data)




Read BUT000 BUT000Event ISDAT(Read data)




Read BUT000

Get BUT000

BUT000Event ISDAT(Read data)




Read BUT000

GET-Funct.modules

Get BUT000

BUT000Event ISDAT(Read data)




Read BUT000

Service-funct. modules

Get BUT000

BUT000

BUT000





Read BUT000


Get BUT000

BUT000

BUT000Read FIBUB1





Read BUT000


Get BUT000

BUT000

FIBUB1BUT000Read FIBUB1





Event ISDST(Distribute data)

Read BUT000


Get BUT000

BUT000






Read BUT000

Get BUT000


Get BUT000

BUT000


BUT000

FIBUB1BUT000






Read BUT000

Get BUT000


Get BUT000

BUT000

FIBUB1

BUT000

BUT000Read FIBUB1

BUT000

FIBUB1BUT000






Read BUT000

Get BUT000 Get FIBUB1


Get BUT000

BUT000

FIBUB1

BUT000

BUT000Read FIBUB1

BUT000

FIBUB1BUT000






Read BUT000



Get BUT000

BUT000

FIBUB1

BUT000

BUT000Read FIBUB1

BUT000

FIBUB1BUT000






Read BUT000



Get BUT000

BUT000

FIBUB1

BUT000 FIBUB1

BUT000Read FIBUB1

BUT000

FIBUB1BUT000




Program Logic: Example (Save data)


Event DSAVB(Collect data)




Transfer BUT000

BUT000

BUT000 FIBUB1


BUT000 FIBUB1




Transfer BUT000


BUT000

BUT000 FIBUB1


BUT000 FIBUB1




Transfer BUT000

Transfer BUT000


BUT000

BUT000 FIBUB1

BUT000 FIBUB1





Transfer BUT000


BUT000

BUT000 FIBUB1

BUT000 FIBUB1


Transfer BUT000




Transfer BUT000

Transfer BUT000


BUT000

BUT000 FIBUB1

BUT000 FIBUB1





Transfer BUT000

Transfer BUT000Transfer FIBUB1


BUT000

BUT000 FIBUB1

BUT000 FIBUB1





Transfer BUT000



BUT000

BUT000 FIBUB1

BUT000 FIBUB1





Event DTAKE(Transfer data)

Transfer BUT000



BUT000

BUT000 FIBUB1

BUT000 FIBUB1





Transfer BUT000

BUT000 in Global Memory



BUT000

BUT000 FIBUB1

BUT000 FIBUB1






Transfer BUT000



FIBUB1 in Global Memory


BUT000

BUT000 FIBUB1

BUT000 FIBUB1






Transfer BUT000




Event DSAVE(Save data)


BUT000

BUT000 FIBUB1

BUT000 FIBUB1






Transfer BUT000




BUT000 in DB


BUT000

BUT000 FIBUB1

BUT000 FIBUB1







Transfer BUT000




BUT000 in DB

FIBUB1 in DB


BUT000

BUT000 FIBUB1

BUT000 FIBUB1





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


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)


Chapter 6

GUI Menu


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


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


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


Function Save Active Create Change Display

Function Delete bank details Active Create Change Display Active Bank details Create Change Display

Function Address overview Active Create Change Display Active Address data Create Change Display Active Addr.data//Main scrn seq. Create Change Display

GUI Menu: Functions (Examples)


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


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


Chapter 7

Field Grouping


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


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_ORG1Name 1


Field Grouping: Field Status Bar

Field status + Required entry . Optional entry * Display - Hide SPACE Not specified

Position in status bar corresponds to field group number (at present: max. 1750 field groups)

Field status bar 1 (200 characters)

+ * . - * 1 3Field group: 2

Field status bar 2 Field status bar 3

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


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


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. 700 First contact: Date 701 First contact: Evaluation 702 Hobbies

Assign field groups to views View ZCUS10 Field groups 700, 701 View ZCUS20 Field 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.


Chapter 8

Search Help


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


Search Helps up to Release 4.5: Assign Elem.Search Help --> Pseudo ID

Search Help BUPA (SAP BP data)

BUPAB Partner acc. to bank detailsBUPAN 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 BUPA BC BUFI B XN BUPA N XV BUSD V X

C Partner acc. to company codeN Partner acc. to name, addressV Partner acc. to sales area


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


Chapter 9

Change Document Evaluations


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


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 CHGD1 Transfer selection values Event CHGD2 Collect change doc. objects with

IDs Event CHGD3 Change doc. Header relevant? Event CHGD4 Change doc. Item relevant?

Call Changes per object instance GUI function BUSA Changes per obj.instance & field GUI function

BUSI Change history Report BUSCHDOC


Chapter 10

Archiving in the Context of the BDT


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


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 Applicationswithout BDT


ARCH1Application-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


Archiving: Programs

BUSOBARCH for archiving data ARCH1 check if data can be archived ARCH2/3 archive header data and dependent data

BUSOBARCH_DELETE for consistent deletion from the completely written archive ARCH4 Interprete archive data and delete on the database

BUSOBARCH_RELOAD for reloading from archives ARCH5 Interpret archive data and check if it can be reloaded ARCH6 Interpret transferred data and write it to the database


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 <Application object> Events

Assign event-> Function modules


Chapter 11

Editing Mode


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


Editing Mode: Save Mode

Event DSAVBCollect data

Event DTAKENote data

Event DSAVCComplete data

Function ‘Save'SAPGP

Event DSAVESave data


Editing Mode: Transfer Mode

ContractContr.no.

Contr.type

Policyholder

Beneficiary

Change

Change

Save

Event DSAVBCollect data

Event DTAKENote data

Event DSAVCComplete data

Function ‘Transfer'

SAPGP

Event DSAVESave data


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!!

DialogDialog Direct InputDirect Input


Edit Mode: Direct Input (Events)

DINP1 Get header data

DINP2 Get data records and note


Edit Mode: Direct Input (Data Transfer)

Entry fileRec.cat. Table Delete flag Data2 BUT000 SPACE 0030001234567...2 BUT020 SPACE 0030001234567...2 BUT021 SPACE 0031122334455...2 BUT0BK SPACE 0030001234567...

BDTData records distribute to applications

SAP BP data2 BUT000 SPACE 0030001234567...2 BUT0BK SPACE 0030001234567...

SAP BP addresses2 BUT020 SPACE 0030001234567...2 BUT021 SPACE 0031122334455...

Function module1 Function module2


Chapter 12

Calling Maintenance


Calling Maintenance: Without Object Part

Transaction BUP2 Report BUPSTART

CALL FUNCTION 'BUP_PARTNER_ MAINTAIN'.

Change BP

Report Partner

Screen selectionAddressPayment trans.

BUPSTART....

Choose BP role

InstallerContract partner

Continue

X


Calling Maintenance: With Object Part

Transaction FPP2 Report RFKKBUPA

CALL FUNCTION 'BUP_PARTNER_ MAINTAIN' TABLES T_RLTYP = GT_RLTYP

Change BP

Report Partner

Screen selectionAddressPayment trans.

RFKKBUPA....

Choose BP role

InstallerContract partner

Continue


Chapter 13

Future Developments


Future Developments:

Mass changes (using logistics tool)

Field defaults

Evaluations (using list tool)

Generate application coding

Relationships between any objects


BDT

workshop business data toolset (bdt)

Documents