Table Maintainance

%&��*HQHUDWH�7DEOH0DLQWHQDQFH�'LDORJ

5HOHDVH �� %

+(/3�%&':

%&8670(

%&��*HQHUDWH�7DEOH�0DLQWHQDQFH�'LDORJ �6$3�$*

� -XQH��

&RS\ULJKW© Copyright 1998 SAP AG. All rights reserved.

No part of this brochure may be reproduced or transmitted in any form or for any purpose withoutthe express permission of SAP AG. The information contained herein may be changed withoutprior notice.

SAP AG further does not warrant the accuracy or completeness of the information, text, graphics,links, or other items contained within these materials. SAP AG shall not be liable for any special,indirect, incidental, or consequential damages, including without limitation, lost revenues or lostprofits, which may result from the use of these materials. The information in this documentation issubject to change without notice and does not represent a commitment on the part of SAP AG forthe future.

Some software products marketed by SAP AG and its distributors contain proprietary softwarecomponents of other software vendors.

Microsoft®, WINDOWS®, NT®, EXCEL® and SQL-Server® are registered trademarks ofMicrosoft 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.

OSF/Motif® is a registered trademark of Open Software Foundation.

ORACLE® is a registered trademark of ORACLE Corporation, California, USA.

INFORMIX®-OnLine IRU�6$3 is a registered trademark of Informix Software Incorporated.

UNIX® and X/Open® are registered trademarks of SCO Santa Cruz Operation.

ADABAS® is a registered trademark of Software AG.

SAP®, R/2®, R/3®, RIVA®, ABAP/4®, SAP ArchiveLink®, SAPaccess®, SAPmail®,SAPoffice®, SAP-EDI®, R/3 Retail®, SAP EarlyWatch®, SAP Business Workflow®, ALE/WEB,Team SAP, BAPI, Management Cockpit are registered or unregistered trademarks of SAPAG.

,FRQV

,FRQ 0HDQLQJ

Caution

Example

Note

�6$3�$* %&��*HQHUDWH�7DEOH�0DLQWHQDQFH�'LDORJ

-XQH��

&RQWHQWV

%&��*HQHUDWH�7DEOH�0DLQWHQDQFH�'LDORJ�� *HQHUDWH�7DEOH�0DLQWHQDQFH�'LDORJ�� &UHDWH�D�PDLQWHQDQFH�GLDORJ��

Initial screen ............................................................................................................................... 9Create maintenance dialog ................................................................................................. 11Delete maintenance dialog.................................................................................................. 12Maintain authorization groups ............................................................................................. 13Maintain authorization group assignments ......................................................................... 14Maintain function groups ..................................................................................................... 15

Environment menu ................................................................................................................... 16Maintain events ................................................................................................................... 18Maintain parameter transaction code.................................................................................. 19

Utilities menu ............................................................................................................................ 200DLQWDLQLQJ�DQG�FKDQJLQJ�DQ�H[LVWLQJ�PDLQWHQDQFH�GLDORJ��

Maintain maintenance dialog.................................................................................................... 23Modify maintenance object....................................................................................................... 24Make Dictionary changes ......................................................................................................... 25

7HFKQLFDO�EDFNJURXQG�� &UHDWH�9LHZ�&OXVWHUV �� 8VH�RI�YLHZ�FOXVWHUV �� 3HUIRUP�YLHZ�FOXVWHU�JHQHUDWLRQ�PDLQWHQDQFH�GLDORJ �� &UHDWH�D�YLHZ�FOXVWHU ��

View cluster names .................................................................................................................. 33Header ...................................................................................................................................... 34

Maintain header entry.......................................................................................................... 35Object structure ........................................................................................................................ 36

Maintain object structure ..................................................................................................... 38Field dependencies .................................................................................................................. 39Activate view cluster ................................................................................................................. 41

0RGLI\�WDEOH�RU�YLHZ�PDLQWHQDQFH�GLDORJV�� Modify maintenance dialogs manually ..................................................................................... 43

7KH�HUURU�ORJ�� 0RGLI\�GHIDXOW�YLHZ�FOXVWHU�PDLQWHQDQFH��

Events....................................................................................................................................... 46Maintain events ................................................................................................................... 48

Event EQ........................................................................................................................ 49Event GR........................................................................................................................ 50Event RE ........................................................................................................................ 51Event SV ........................................................................................................................ 52Event CK ........................................................................................................................ 53Event 01 ......................................................................................................................... 54Event 02 ......................................................................................................................... 55


� -XQH��

Event 03 ......................................................................................................................... 56Event 04 ......................................................................................................................... 57Event 05 ......................................................................................................................... 58Event 06 ......................................................................................................................... 59Event 07 ......................................................................................................................... 60Event 08 ......................................................................................................................... 61Event 09 ......................................................................................................................... 62Event 10 ......................................................................................................................... 63Event 11 ......................................................................................................................... 64Event 12 ......................................................................................................................... 65

9LHZ�FOXVWHU�PDLQWHQDQFH�JOREDO�GDWD�� 0RGLI\�QDYLJDWLRQ�VXEVFUHHQ�WLWOH�DQG�SRVLWLRQ�WH[W�� 'HDFWLYDWH�PHQX�IXQFWLRQV�� &DOO�WKH�YLHZ�FOXVWHU�PDLQWHQDQFH�GLDORJ ��


-XQH��

%&��*HQHUDWH�7DEOH�0DLQWHQDQFH�'LDORJThis document describes the creation of standardized table or view contents maintenancedialogs.

Maintenance dialogs are used mainly in customizing. They can also be used to maintaincustomer table or view contents.

6HH�DOVR�

BC - Extended table maintenance [Ext.]


*HQHUDWH�7DEOH�0DLQWHQDQFH�'LDORJ

� -XQH��

*HQHUDWH�7DEOH�0DLQWHQDQFH�'LDORJ

8VHThe *HQHUDWH�WDEOH�PDLQWHQDQFH�GLDORJ component creates standardized maintenance dialogsfor tables and views. These dialogs can also be used to maintain table or view contents.

,QWHJUDWLRQThe component provides a standardized maintenance interface for many customizing activities. Itis also useful as a customer table or view input tool.

Table or view maintenance dialogs are created in the ABAP/4 Workbench under the menu path'HYHORSPHQW → 2WKHU�WRROV��→�*HQ�WDE�PDLQW�GLDORJ. To maintain table or view contents choose6HUYLFHV → ([W��WDE�PDLQW� at any time.

Maintenance dialogs and data which were created, changed or deleted with the maintenancedialog can be transported into other R/3 Systems.

)XQFWLRQDOLW\The component creates maintenance dialogs which are standardized in their:

• functionality

• interface

• maintenance screen

• navigation

• enhancement options

• maintenance

6HH�DOVR�

Generate table maintenance dialog [Page 7]

Generate table maintenance dialog - Inistial screen [Page 9]

Generate table maintenance dialog - Technical background [Page 26]

Create view clusters [Page 29]


&UHDWH�D�PDLQWHQDQFH�GLDORJ

-XQH��


8VHThis section describes the table or view maintenance dialog creation procedure. Maintenancedialogs can be created for SAP or customer tables or views.

The procedure consists of two steps:

�� 7DEOH�RU�YLHZ�GHILQLWLRQ

if the table or view does not already exist.

�� 0DLQWHQDQFH�GLDORJ�GHILQLWLRQ

7DEOH�RU�YLHZ�GHILQLWLRQ

The table or view is defined in the Dictionary.

• Choose the 0DLQWHQDQFH�YLHZ view type.

• The client field must be included for client-dependent tables or views. The field is notdisplayed in the maintenance dialog.

• The language key need not be included for secondary text tables; the logon languageis automatically entered.

• The key fields must be defined before the function fields. Function fields and keyfields must be kept separate.

• You can assign one of the following maintenance attributes to each field:

− R: The field can only be read by the maintenance dialog.

− S: Only a subset of the data can be maintained for this field.

− H This field is not displayed in the maintenance dialog and is not automaticallyfilled.

− <space>: This field has no individual restrictions.

• You can specify one of the following maintenance statuses for the whole table or viewwith 0DLQWHQDQFH�VWDWXV:

− read only

− read, change, delete and insert (default setting)

− read and change

− read and change (time-dependent views)

The key of time-dependent tables consists of a time-independent and a validityrange part. By choosing UHDG�DQG�FKDQJH��WLPH�GHSHQGHQW�YLHZV� you restrict themaintenance to changing and creating the validity range of H[LVWLQJ keys.

0DLQWHQDQFH�GLDORJ�GHILQLWLRQ

You must specify the following parameters in the maintenance dialog definition:



� -XQH��

• )XQFWLRQ�JURXS The function group in which the table or view maintenance dialogcomponents are generated. This could be a new function group.

• $XWKRUL]DWLRQ�JURXSThe users who are authorized to maintain table or viewcontents.

• 0DLQWHQDQFH�W\SH One or two-step dialog. One-step dialogs only have an overviewscreen containing all fields. In two-step dialogs, the overview screen contains only thekey fields and text fields longer than 20 characters. The detail screen contains allfields.

• 0DLQWHQDQFH�VFUHHQVThe internal number of each maintenance screen. You can getproposals via a search function.

• 5HFRUGLQJ�URXWLQH Copy maintained table or view contents into a transport.

5HVXOWThe maintenance dialog is generated when all values have been input. If no errors occur, thedialog can be used to maintain table or view contents.


,QLWLDO�VFUHHQ

-XQH��

,QLWLDO�VFUHHQ

8VHThe initial screen contains functions for managing the objects required to generate amaintenance dialog.

)XQFWLRQDOLW\Functions:

• (GLW�WDEOH�YLHZ

You can go to display or maintain table, view or maintenance dialog definition, or toauthorization groups and their assignment. You can also delete either the table orview incl. maintenance dialog ('LFWLRQDU\ → 'HOHWH) or individual generated objects(*HQHUDWHG�REMHFWV → 'HOHWH).

• (GLW�IXQFWLRQ�JURXS

Change function group and source text or reset the following group-specificprograms.

− structure-specific PAI modules

− structure-specific data declarations

− structure-specific form routines

− general data declarations

− function group main program

Dialog changes can be lost by resetting the general data declarations and thefunction group main program.

• (GLW�YLHZ�FOXVWHU

Go to the view cluster definition.

• (GLW�YLHZ�YDULDQWV

Create view variants.

• 7HVW�WDEOH�RU�YLHZ

Enter a dialog name and call the dialog.

6HH�DOVR�

Maintain function groups [Page 15]

Maintain maintenance dialog [Page 23]

Change maintenance dialog [Ext.]

Make Dictionary changes [Page 25]

Delete maintenance dialog [Page 12]


,QLWLDO�VFUHHQ

�� -XQH��

Maintain authorization groups [Page 13]

Maintain authorization group assignment [Page 14]


BC - Extended table maintenance [Ext.]


&UHDWH�PDLQWHQDQFH�GLDORJ

-XQH��

&UHDWH�PDLQWHQDQFH�GLDORJTo generate the maintenance dialog for a table or view, proceed as follows:

1. Go to the maintenance transaction initial screen with 7RROV�→�$%$3�:RUNEHQFK�→'HYHORSPHQW�→�2WKHU�WRROV�→�*HQ�WDE�PDLQW�GLDORJ�

2. Enter the name of the table or view.

3. Select *HQHUDWHG�REMHFWV.

4. Choose &UHDWH�&KDQJH.

5. Confirm that you want to create maintenance modules, in the subsequent dialog box.

6. Enter the generation information:

– maintenance module function group

You can put the maintenance modules for several tables or views in one functiongroup.

– authorization group

– maintenance type (one-step, two-step)

– maintenance screen (maintenance type single-level) or maintenance screens(maintenance type two-level) numbers

– recording routine (standard/individally or none)

7. Choose &UHDWH. The system then generates all required components.

When generating the maintenance dialog, the system automatically creates an entry in the tablecontaining the maintenance object description, including an object list. This object list contains alltables used.


'HOHWH�PDLQWHQDQFH�GLDORJ

�� -XQH��

'HOHWH�PDLQWHQDQFH�GLDORJTo delete a generated maintenance dialog from the system, delete the generated elements usingthe maintenance transaction.

Enter the table or view name and select *HQHUDWHG�REMHFWV on the maintenance transaction initialscreen. Choose 'HOHWH. A dialog box appears, in which you can mark the elements you want todelete:

• 0DLQWHQDQFH�PRGXOHV

You can delete function modules independently of the control entry and themaintenance screens.

• (QWU\�LQ�WDEOH�RU�YLHZ�GLUHFWRU\ (control entry)

You can delete the control entry only if you also delete the function modules andmaintenance screens.

• 2YHUYLHZ�VFUHHQ and LQGLYLGXDO�VFUHHQ

You can delete maintenance screens independently of the control entry and thefunction modules.

• 0DLQWHQDQFH�REMHFW�GHVFULSWLRQ

The system deletes all information (header, object list, subobjects, and so on).

• (QWULHV�LQ�(YHQWV�GLUHFWRU\

Events table entries are deleted. The event program code is retained.

• 9DULDQWV

Any existing variants are deleted.

• )XQFWLRQ�JURXSV

The system offers this option only if the function group contains only the functionmodules of the maintenance dialogs you want to delete, that is, if it would be emptyafter deleting the function modules.

You have to delete the following elements separately:

• $XWKRUL]DWLRQ�JURXS�DVVLJQPHQW

(see Maintain authorization group assignment [Page 14])

• 8VHU�LQWHUIDFH, if the function group is not deletedTo delete, proceed as follows:

a) Enter the table or view name in the generation environment and choose(QYLURQPHQW�→�&KDQJH�→�,QWHUIDFH� The dialog box 0DLQWDLQ�XVHU�LQWHUIDFHDVVLJQPHQW appears.

b) Choose 'HOHWH� The system deletes the user interface if the�8VHU�LQWHUIDFH flag isnot set.

If 8VHU�LQWHUIDFH flag is set, another dialog lists the tables or views that use theinterface. Choose 'HOHWH�again to delete the user interface and controlinformation.


0DLQWDLQ�DXWKRUL]DWLRQ�JURXSV

-XQH��

0DLQWDLQ�DXWKRUL]DWLRQ�JURXSVYou can maintain authorization groups for tables and views with the *HQHUDWH�WDEOH�PDLQWHQDQFHGLDORJ maintenance transaction.

An authorization group contains tables and views with the same security requirements.

1. Choose $XWKRUL]DWLRQ�JURXSV and &UHDWH�&KDQJH in the initial screen.

2. Choose 1HZ�HQWULHV. An input area for new entries appears.

3. Enter a name for the authorization group and a descriptive text.

4. Save your input.

To activate the authorization, you must determine an activity for the authorization group in theauthorizaton object.

The system automatically includes the definition of a new authorization group in acorrection only:

• if the authorization group is used, and

• then generation via the &KDQJH or 'HOHWH function, or the client is set toautomatic recording of changes.

Otherwise you must include it yourself using the 7DEOH�YLHZ�→�7UDQVSRUWfunction in the authorization group maintenance screen.


0DLQWDLQ�DXWKRUL]DWLRQ�JURXS�DVVLJQPHQWV

�� -XQH��

0DLQWDLQ�DXWKRUL]DWLRQ�JURXS�DVVLJQPHQWVTables or views are assigned to an authorization group during generation. Using themaintenance transaction you can maintain multiple assignments or delete assignments, if, forexample, you want to combine several views or tables into a new group.

1. Select $VVLJQ�DXWK��JURXS in the maintenance transaction initial screen and choose&UHDWH�&KDQJH. A dialog box appears on which you can enter selection criteria.

2. Mark the criteria (table name, authorization group) according to which to limit themaintenance and choose &RQWLQXH. A dialog box appears in which you can determinethe work area.

3. Enter the selection and choose &RS\�

4. Change the authorization group assigments of the displayed tables and views to yourneeds or choose 1HZ�HQWULHV to create new assignments.

5. Save your input.


0DLQWDLQ�IXQFWLRQ�JURXSV

-XQH��

0DLQWDLQ�IXQFWLRQ�JURXSVChoose (GLW�IXQFWLRQ�JURXSV to go to the function group which contains the function modules ofthe current maintenance dialog. The system offers the following maintenance options:

• )XQFWLRQ�JURXS�WH[W

The short text and the person responsible for the function group is displayed, and youcan change them.

• 6RXUFH�WH[WV

Displays a list of the program parts in the function group that you can change. The listdoes not include generated program parts, since you should not change those. Whenyou select a program part you go to the ABAP/4 Editor initial screen. The programname is copied.

• 5H�JHQHUDWH�JURXS�VSHFLILF�SURJUDPV

Select the program parts you want to edit in a dialog box.

and choose &KDQJH.

If you want to delete the entire function group, enter the name of the group and choose 'HOHWH.


(QYLURQPHQW�PHQX

�� -XQH��

(QYLURQPHQW�PHQX

8VHThe (QYLURQPHQW menu contain application-specific maintenance dialog change functions.


• 0DLQWHQDQFH�VFUHHQV

You go to the Screen Painter where you can modify the generated (overview anddetail) maintenance screens.

• LQWHUIDFH

You can create a dialog-specific interface which can be changed with the MenuPainter.

The maintenance dialogs access the standard table /view maintenance interfacein the function group SVIM. You can define a function group interface by choosing,QWHUIDFH to copy and change the original interface. The message 8VHU�LQWHUIDFHH[LVWV in the 0DLQWDLQ LQWHUIDFH�DVVLJQPHQW�dialog indicates whether an interfacealready exists in the current function group.

• 'LVSOD\�PRGXOH

Displays the definition of the function modules generated by the table/viewmaintenance in the ABAP Workbench Function Builder.

The (view-dependent) function modules VIEWFRAME_�YLHZ�QDPH! andVIEWPROC_�YLHZ�QDPH! are generated for views when a maintenance dialogis generated. The (table-independent) function modulesTABLEFRAME_�IXQFWLRQ�JURXS! and TABELPROC_�IXQFWLRQ�JURXS!are created per function group for tables. These modules must not be changed.

• (YHQWV

To include user routines in the maintenance dialog. For detailed information aboutevents choose ,QIRUPDWLRQ (L pushbutton) on the event maintenance screen

• 9DULDQWV

Create a table/view contents maintenance selection variant.

• 7UDQVDFWLRQ�FRGH

Assign or maintain transaction code to a maintenance dialog.

• 0DLQWHQDQFH�REMHFWV

Generate or change the transport and customizing-relevant additional information fora table or view.


(QYLURQPHQW�PHQX

-XQH��

• 6RXUFH�WH[W

Display function group main program and maintenance dialog top include and userincludes in the ABAP Editor.

• $XWKRUL]DWLRQ�JURXSV

Maintain table/view maintenance authorization groups.

• $VVLJQ�DXWK��JURXS

Assign table/view to an authorization group.

The maintenance authorization of a user is determined by the table maintenanceauthorization in the user master record, which is usually restricted to a user-specific group of maintenance dialogs. The assignment of a dialog to anauthorization group determines which users are authorized to maintain theview/table contents.

6HH�DOVR�

Create maintenance dialog [Page 7]

Maintain events [Page 18]

Maintain transaction code [Page 19]

Maintain authorization groups [Page 13]

Maintain authorization group assignment [Page 14]



0DLQWDLQ�HYHQWV

�� -XQH��

0DLQWDLQ�HYHQWVUse the events to include user FORM routines which modify the flow, or a user interface (event“ST”). Proceed as follows:

1. Choose (QYLURQPHQW�→�(YHQWV.

2. Choose 1HZ�HQWULHV.

3. Press F4 for help on the field in the “Evt” column. The system displays the definedevents.

4. Double-click on the desired line to select an event. The system copies it into the field.

5. Enter the FORM routine name in )RUP�QDPH�3URJUDP�QDPH or, for the event "ST",the user interface program name.

6. Save your input.


0DLQWDLQ�SDUDPHWHU�WUDQVDFWLRQ�FRGH

-XQH��

0DLQWDLQ�SDUDPHWHU�WUDQVDFWLRQ�FRGHYou can create a parameter transaction for your maintenance dialog to call the maintenancedialog from within your program.

1. Choose (QYLURQPHQW�→ 7UDQVDFWLRQ�FRGH�

2. Enter the transaction code and choose &UHDWH. (You can also change or deleteexisting transaction codes on this screen.) A dialog box appears where you can selectthe transaction type.

3. Mark the transaction type 3DUDPHWHU�WUDQVDFWLRQ and choose &RQWLQXH. A dialogbox appears where you can maintain the parameters.

The system provides the following parameters ("X" means that you want to performthe corresponding action):

)LHOG�QDPH 9DOXH $FWLRQ

VIEWNAME Table/View name

UPDATE X or <space> maintain

SHOW X or <space> display

TRANSPORT X or <space> transport

UPDATE_LTD X or <space> maintain subset

SHOW_LTD X or <space> display subset

TRANSP_LTD X or <space> transport subset

TVIMV-VARIANT variant name use variant (only with UPDATE_LTD, SHOW_LTD andTRANSP_LTD)

4. Enter the required values and save your input.

5. Choose ([HFXWH to test the created (or changed) transaction code.


8WLOLWLHV�PHQX

�� -XQH��

8WLOLWLHV�PHQX

8VHThe 8WLOLWLHV menu contains functions which provide additional information about the maintenancedialog and its tables or views.


• 5HTXHVWV��2UJDQL]HU�

You go to the Workbench Organizer.

• 7RWDO�WUDQVSRUW

The total transport transports the complete maintenance dialog:

− authorization group

− authorization group assignment

− control entry

− events

− function groups

− maintenance objects

− variants

• *HW�VFUHHQ�QXPEHUV

Get screen number proposals for the overview and individual screens in thegeneration environment.

• 9LHZ�KLHUDUFK\�VWUXFW�

Graphical view structure display.

• ''�,QIR�V\VWHP

Go to the Dictionary information system.

• 7DEOH�9LHZ�ORJ

Go to log function.

6HH�DOVR�

Create maintenance dialog [Page 7]



0DLQWDLQLQJ�DQG�FKDQJLQJ�DQ�H[LVWLQJ�PDLQWHQDQFH�GLDORJ

-XQH��

0DLQWDLQLQJ�DQG�FKDQJLQJ�DQ�H[LVWLQJ�PDLQWHQDQFHGLDORJ

8VHThere are two possible reasons for changing an existing maintenance dialog:

1. for technical reasons e.g table or view changes (addition or deletion of fields).

2. for application reasons, e.g. additional input data consistency check logic required.Types of changes:

− maintenance screens (layout and flow logic)

− interface

− events in program flow

User program code can only be included via user includes. The includes must be createdmanually in the function group.

Dialog changes must be made such that regeneration does not lose modifications. You can usethe *HQHUDWH�WDEOH�PDLQWHQDQFH�GLDORJ tool to regenerate selectively, i.e. to replace only thenecessary dialog components. If you have changed maintenance screens, the interface or themain program, you should exclude them from the regeneration. Maintenance does not affectevents.

3URFHVV�IORZ

0DLQWHQDQFH

You can control the maintenance dialog change types with the *HQHUDWH�WDEOH�PDLQWHQDQFHGLDORJ tool:

• FKDQJH�PDLQWHQDQFH�W\SH

Change the maintenance type from one-step to two-step or vice versa.

• &UHDWH�PRGXOH

• &UHDWH�PDLQWHQDQFH�VFUHHQ

Reset generated modules or maintenance screens to default values.

• )LHOG�VHF��WDEOH�LQ�VWUXFWXUH

• 5HPRYH�ILHOG�VHF��WDEOH�IURP�VWUXFWXUH

Adjust maintenance dialog when Dictionary structures have changed. Only for views.

• &KDQJH�WH[W�WDEOH�OLQN

Adjust maintenance dialog if you have assigned a table to another text table in theDictionary. Only for tables.

A text table is automatically included in the maintenance dialog if a 7H[W�WDEOH NH\ILHOGV�foreign key relationship is assigned in the Dictionary for the table.


0DLQWDLQLQJ�DQG�FKDQJLQJ�DQ�H[LVWLQJ�PDLQWHQDQFH�GLDORJ

�� -XQH��

• &KDQJHG�VHOHFWLRQ�FRQGLWLRQV

• )LHOG�DWWULEXWH�VXEVHW�FKDQJHG

• )LHOG�DWWULEXWH�UHDG�RQO\�FKDQJHG

• )LHOG�DWWULEXWH�KLGGHQ�FKDQJHG

Adjust maintenance dialog when Dictionary selection conditions or field attributeshave changed.


0DLQWDLQ�PDLQWHQDQFH�GLDORJ

-XQH��

0DLQWDLQ�PDLQWHQDQFH�GLDORJYou can proceed in two ways:

• 1RUPDO

(recommended). The system offers standard situations for selection and executes thecorresponding generation steps. You need no detailed system knowledge and can besure that all required steps are performed.

• ([SHUW�PRGH

You must understand the generation process completely. It is designed for situationsthat are not covered by the standard. You must choose the generation steps yourself.There is a risk of unintentionally deleting maintenance modules or performing thegeneration only incompletely. It is therefore not recommended.

Proceed as follows:

1. Enter the table or view name.

2. Select *HQHUDWHG�REMHFWV.

3. Choose &UHDWH�&KDQJH. You go to the generated objects maintenance screen.

4. Choose &KDQJH. The system displays a screen on which you can choose amongreasons for changes.

5. Mark the corresponding option(s) and choose &RQWLQXH.

If you want to use the expert mode, choose ([SHUW instead of selecting options. Inthe subsequent window, enter the components you want to regenerate.

6. Make the appropriate entries in the dialog box and choose &RQWLQXH.

6HH�DOVR�

Make Dictionary changes [Page 25]


0RGLI\�PDLQWHQDQFH�REMHFW

�� -XQH��

0RGLI\�PDLQWHQDQFH�REMHFWA maintenance object, which automatically contains the table(s) maintained with the dialog, iscreated during generation. The maintenance object entries are significant for transporting thetable/view contents. If user tables have been maintained in a maintenance dialog modification,and they are to be transported, ensure that:

• the tables are manually modified in the maintenance object.

• There are program parts which complete the transport request. (Events [Page 18] 10,11 or 12).

The maintenance object description is changed as follows:

1. Choose 8WLOLWLHV�→�0DLQWHQDQFH�REMHFWV.

2. Press 3RVLWLRQ. A dialog box appears, where you can enter the name of the object onwhich to position.

3. Enter the name of the table or view for which you generated the maintenance dialogand choose &RQWLQXH. The system displays the desired entry in the first line.

4. Mark the entry by clicking on the box at the beginning of the line.

5. Choose 7DEOH�YLHZ�→�2WKHU�YLHZ. A dialog box appears.

6. Position the cursor on 2EMHFW�OLVW and choose &KRRVH. The system displays the objectlist of the selected object.

7. Choose 1HZ�HQWULHV. The system offers additional lines ready for input.

8. Enter the table(s) and save your input.


0DNH�'LFWLRQDU\�FKDQJHV

-XQH��

0DNH�'LFWLRQDU\�FKDQJHVYou can change the Dictionary and the maintenance dialog table/view from the initial screen.

After making changes, you must regenerate the maintenance dialog completelyor partially to activate the changes.

Proceed as follows:

1. Enter the name of the table or view.

2. Mark the option 'LFWLRQDU\ and choose�&UHDWH�&KDQJH.

You go to the Dictionary.

3. Make your changes and save them.

4. Go back and regenerate.

6HH�DOVR�

Maintain maintenance dialog [Page 23]


7HFKQLFDO�EDFNJURXQG

�� -XQH��


0DLQWHQDQFH�GLDORJ�IORZWhen a maintenance dialog is called, the table/view entries are read from the database into aninternal buffer and are then presented on the screen for maintenance. The read range can berestricted.

The use of internal tables means that field content changes do not immediately result in databasechanges. The changes are copied from the internal buffer to the database when saving.

Depending on the recording routine of table or view, delivery class, maintenance objectdescription, and, for client-dependent objects, on the client setting, the system logs the changesin a change task when saving them.

&RPSRQHQWV�RI�D�GLDORJA table maintenance dialog has view/table-specific and independent program components. Theview/table-independent parts are:

• General function modules (lock/unlock all maintainable tables, DDIC analyses, etc.)

• Maintenance dialog control modules and routines

• interface

• Messages

The view/table-specific parts of a maintenance dialog are:

• Function group (main program)

• function modules for processing data and controlling the processing flow

• Code in form of Includes (for data declarations, databank operations, transport)

• Maintenance screens

• Maintenance object description

7UDQVSRUW�FKDQJHV

0DLQWHQDQFH�GLDORJ�FKDQJHV

The generation environment is connected to the transport system, i.e. all maintenance dialoggeneration activities are automatically logged in a change request. Thus, you can transport theentire maintenance dialog into other systems or clients.

7DEOH�9LHZ�FRQWHQWV�FKDQJHV

There are two conditions for the automatic recording and transport of table/view contentschanges:

1. Change authorization for the tables/views

2. Change recording obligation, i.e.the changed table/view entries are recordedautomatically

The changes are only put in a transport request and can be transported if both conditions arefulfilled.



-XQH��

Change authorization and recording obligation are affected by 3 parameters:

1. Client settings

2. Recording routines (maintenance dialog definition)

3. Maintenance object description (maintenance dialog environment)

Dialogs:

• whose tables/views have delivery class L, or

• which have no recording routines and no events 10, 11 and 12,

are not transported and are not considered further.

&KDQJH�DXWKRUL]DWLRQ

Table/view contents with the following settings must not be changed (and are not put in arequest):

1. 3DUDPHWHU 9DOXH

Client no changes allowed

maintenance objects CUSY or CUST

2. 3DUDPHWHU 9DOXH

Client no Repository changes allowed

maintenance objects SYST

3. 3DUDPHWHU 9DOXH

Client no client-independent customizing changes allowed

maintenance objects CUSY

The following combination of settings is a special case:

3DUDPHWHU 9DOXH

Client • no changes allowed

• client role Productive

maintenance objects • current setting

• CUST

Changes are allowed, but they are not transported. This combination of settings is chosen whenchanges are to be made directly in the productive client.

5HFRUGLQJ�REOLJDWLRQ

The following changes must be recorded:



�� -XQH��

• Client-independent tables/view changes.

• Client-dependent tables changes, if the client setting DXWRPDWLF�FKDQJH UHFRUGLQJ�is set.

&DOO�WKH�PDLQWHQDQFH�GLDORJYou can call the generated maintenance dialogs in various ways:

• &DOO�WKH�H[WHQGHG�WDEOH�PDLQWHQDQFH�IURP�WKH�6\VWHP�PHQX��VWDQGDUG�FDOO��

Enter the name of the table or view. Choose 0DLQWDLQ to go to the generatedmaintenance dialog. This call is possible immediately after generation.

• &DOO�D�SDUDPHWHU�WUDQVDFWLRQ (see Transaction code [Page 19]) in the OK code fieldor from within an application

A parameter transaction must be defined before the call. This is useful e.g. if thetable/view and the action (maintain or display) are known.

• &DOO�YLD�JHQHUDWHG�PDLQWHQDQFH�IXQFWLRQ�PRGXOHV

You can use this call, e.g. if a special context-dependent selection is required. Youcan enter the dialog at various levels. Depending on the entry level, you may have toprogram certain activities yourself which are usually performed automatically by tablemaintenance.

The maintenance dialog performs the following activities:

• authorization check

• locks

• get and format Dictionary data

• select, process and save the table contents

• restrict data selection in the subset fields dialog

• dynamically adapt the user interface (menus and functions)

6HH�DOVR�

Extended function library applications - Extended table maintenance [Ext.]


&UHDWH�9LHZ�&OXVWHUV

-XQH��

&UHDWH�9LHZ�&OXVWHUVThis section tells you about the concepts and procedures for creating view clusters.

8VH�RI�YLHZ�FOXVWHUV�>3DJH��@

([HFXWH�YLHZFOXVWHU�JHQHUDWLRQ�PDLQWHQDQFH�GLDORJ�>3DJH��@

&UHDWH�D�YLHZ�FOXVWHU�>3DJH��@

+HDGHU�HQWU\�>3DJH��@

0DLQWDLQ�KHDGHU�HQWU\�>3DJH��@

2EMHFW�VWUXFWXUH�>3DJH��@

0DLQWDLQ�REMHFW�VWUXFWXUH�>3DJH��@

)LHOG�GHSHQGHQFLHV�>3DJH��@

$FWLYDWH�YLHZ�FOXVWHU�>3DJH��@

7DEOH�YLHZ�PDLQWHQDQFH�GLDORJ�FKDQJHV�>3DJH��@

(UURU�ORJ�>3DJH��@

6WDQGDUG�YLHZ�FOXVWHU�PDLQWHQDQFH�FKDQJHV�>3DJH��@

0DQXDO�PDLQWHQDQFH�GLDORJ�FKDQJHV�>3DJH��@

(YHQWV�>3DJH��@

0DLQWDLQ�HYHQWV�>3DJH��@0DLQWDLQ�YLHZ�FOXVWHU�JOREDO�GDWD�>3DJH��@

&KDQJH�QDYLJDWLRQ�VXEVFUHHQ�WLWOH�DQG�SRVLWLRQ�WH[W�>3DJH��@

'HDFWLYDWH�PHQX�IXQFWLRQV�>3DJH��@

&DOO�YLHZ�FOXVWHU�PDLQWHQDQFH�GLDORJ�>3DJH��@


8VH�RI�YLHZ�FOXVWHUV

�� -XQH��

8VH�RI�YLHZ�FOXVWHUVThe view cluster maintenance transaction is a tool for creating maintenance dialogs for complexdata objects. Data objects can be views or tables for which a table maintenance dialog wascreated using the view maintenance. The objects in a view cluster can be connected either viahierarchical relationships (foreign key relation 1:N) or logically, database-independently.

Object maintenance is based on general table maintenance. View cluster maintenance combinesgeneral table maintenance modules into one object. You can navigate among subobjects in thisobject. The system ensures that the consistency of the view cluster is retained when maintaininga view cluster subobject.

The view cluster object data is stored in internal tables and written to the database only when yousave. Changes can be logged by the Workbench Organizer.

You can adapt the standard view cluster maintenance flow logic and the maintenance screens toyour requirements.


3HUIRUP�YLHZ�FOXVWHU�JHQHUDWLRQ�PDLQWHQDQFH�GLDORJ

-XQH��

3HUIRUP�YLHZ�FOXVWHU�JHQHUDWLRQ�PDLQWHQDQFH�GLDORJUse the *HQHUDWH�WDEOH�PDLQWHQDQFH�GLDORJ maintenance transaction to create and maintain aview cluster maintenance dialog. Proceed as follows:

1. Go to the ABAP/4 Development Workbench initial screen.

2. Choose 'HYHORSPHQW�→�2WKHU�WRROV�→�*HQ�WDE�PDLQW�GLDORJ to go to the table or viewmaintenance dialog generation initial screen.

3. Choose (GLW�YLHZ�FOXVWHU.

You go to the view cluster table maintenance dialog generation initial screen.

In the initial screen, you can create new view clusters or display or change existing ones. Youcan also go to the function group maintenance transaction.


&UHDWH�D�YLHZ�FOXVWHU

�� -XQH��

&UHDWH�D�YLHZ�FOXVWHU

3UHSDUDWLRQ�

1. Before creating a view cluster, plan its structure. To do this, you must know exactlyhow the individual objects of the view cluster are interrelated.

2. Make sure that view/table maintenance modules already exist for all objects.

'HILQH�WKH�YLHZ�FOXVWHU�

3. Enter a view cluster name [Page 33].

4. Define the header entry [Page 34]

5. Specify the object structure [Page 36].

6. Define the field dependencies [Page 39] between the view cluster objects.

7. Insert events [Page 46] for your flow logic.

8. Activate view cluster [Page 41]


9LHZ�FOXVWHU�QDPHV

-XQH��

9LHZ�FOXVWHU�QDPHVTo create a new view cluster, you must enter a name. View cluster names are valid throughoutthe system. Make sure that the new name does not already exist, to avoid overwriting an existingview cluster, as follows:

1. Go to the view cluster maintenance initial screen as described in Perform view clustergeneration maintenance dialog [Page 31].

2. Enter the beginning of the desired name, followed by an asterisk (*) in the 9LHZFOXVWHU field and click on the possible entries button (F4).

The system displays all view clusters whose names start like this. Enter a name thatis not in the list in the 9LHZ�FOXVWHU field.

3. Choose &UHDWH�&KDQJH.

You go to the view cluster creation maintenance dialog.


+HDGHU

�� -XQH��

+HDGHUThe maintenance screen for the header entry comprises three groups:

1DYLJDWLRQ�

This group is on all view cluster creation maintenance screens. You can navigate to the othermaintenance screens using this group (see also “complex table maintenance” in Extended tablemaintenance [Ext.]

9LHZ�FOXVWHU�GHILQLWLRQ�PDLQWHQDQFH�

You can maintain technical data (+LHUDUFKLFDO�PDLQWHQDQFH�RSHUDWLRQ�KDQGOLQJ and 5HDG�W\SH)and a short description of the view cluster in this group.

Hierarchical maintenance operation handling:

• 8VH�LQ�KLHUDUFK\��3RSXS�: A dialog box informs you that your object changes affectsuperior or dependent objects. You can either make the same changes to thesuperior objects, ignore the prompt, or cancel the maintenance dialog.

• 8VH�LQ�KLHUDUFK\��PDQGDWRU\�: If changes must be made to superior or dependentobjects due to changes to an object, the system automatically makes them.

• /LPLW�WR�RQH�VWHS: The system executes any operation for the current object only andignores any dependencies.

Read type:

• $OO: All view cluster object data is transferred to the application server.

• 6XE�WUHH: The system transfers only the start object and its dependent objects. Ittransfers data of other objects only as required.

9LHZ�FOXVWHU�GHILQLWLRQ�LQIRUPDWLRQ�

The system displays general information.


0DLQWDLQ�KHDGHU�HQWU\

-XQH��

0DLQWDLQ�KHDGHU�HQWU\This topic tells you how to maintain the header entry for a new view cluster:

1. Go to the view cluster maintenance initial screen.

2. Enter the name of the view cluster you want to create or change and choose&UHDWH�&KDQJH.

3. Enter a description of the view cluster (only when creating a new one)�in the 6KRUWWH[W�field 9LHZ�FOXVWHU�GHILQLWLRQ�PDLQWHQDQFH group.

4. Select the appropriate procedure for your view cluster in the +LHUDUFKLFDO�PDLQWHQDQFHRSHUDWLRQ�KDQGOLQJ subgroup.

5. Specify whether to read all objects or only a subtree to the application server for viewcluster maintenance, in the 5HDG�W\SH subgroup.


2EMHFW�VWUXFWXUH

�� -XQH��

2EMHFW�VWUXFWXUHThe object structure determines the relationships of the view cluster objects on the table/viewlevel. You also define the navigation subscreen structure and the initial view cluster maintenanceobject.

The maintenance screen contains the 1DYLJDWLRQ and 9LHZ�FOXVWHU�GHVFULSWLRQ�PDLQWHQDQFH�VWUXFWXUH�WDEOH� groups and the $FWLYDWH�ILHOG�GHSHQGHQFH pushbutton:

• 1DYLJDWLRQ: This group is on all view cluster creation maintenance screens. You cannavigate to the other maintenance screens (see also “complex table maintenance” inExtended table maintenance [Ext.]).

• 9LHZ�FOXVWHU�GHVFULSWLRQ�PDLQWHQDQFH��VWUXFWXUH�WDEOH�: In this group, enter the objectrelationships in the table and the entry format in the navigation subscreen. The tablehas the following fields:

9LHZ�7DEOH Name of the current object. The green arrow next to the object allows directnavigation to the ABAP/4 Dictionary.

6KRUW�WH[W Context-related text for the current object. The text appears when maintaining thenewly created view cluster as navigation text in the navigation subscreen.

3UHGHFHVV� Name of the directly superior object in the object hierarchy.

If the current object is on the highest hierarchy level (header entry) and thus hasno superior object, enter the same name here as in the 9LHZ�7DEOH field.

'HS This field influences the selection of dependent entries in navigation:

R: the object is a header entry and has no superior object (see 3UHGHFHVVRU)

S: when navigating to the object specified in 9LHZ�7DEOH� you may mark only oneentry in the superior object (predecessor). The system then displays only theentries depending on a superior object.

M: when navigating to the object specified in 9LHZ�7DEOH, you can mark anynumber of entries in the superior object (predecessor).

3RV Enter a value between 1 and 15 for the postion of the object on the navigationsubscreen. You must assign these values consecutively starting from 1.

/HYHO This value between 1 and 15 indicates the level on which the object occurs in theview cluster and thus determines the object description indentation on thenavigation subscreen. A header entry has level 1, a directly dependent objectlevel 2.

,QLWLDO Mark the checkbox for the initial view cluster object.

%DFNJU Mark the checkboxes for those objects that you want to suppress from the viewcluster maintenance. The object is not displayed in the navigation subscreen. Youcannot navigate to these objects.

1�0 Mark this field if the object and its predecessor have an N:M relationship. Thesystem then takes this relationship into account for hierarchical operations (copy,delete, retrieve, transport).

• *HQHUDWH�ILHOG�GHSHQGHQFLHV pushbutton: Use this function to automatically generatethe view cluster objects field dependencies, provided the corresponding foreign keyrelationships for these objects exist in the ABAP/4 Dictionary.


2EMHFW�VWUXFWXUH

-XQH��

Mark the objects for which the field dependencies are to be generated and press thepushbutton. A dialog box confirms generation.


0DLQWDLQ�REMHFW�VWUXFWXUH

�� -XQH��

0DLQWDLQ�REMHFW�VWUXFWXUH1. Go to the header entry maintenance screen.

2. Click on the magnifying glass in the 1DYLJDWLRQ group before the menu item 2EMHFWVWUXFWXUH. You go to the view cluster object structure maintenance screen.

3. Choose 1HZ�HQWULHV to go to new entry creation mode.

4. Maintain a line for each view cluster object in the 9LHZ�FOXVWHU�GHVFULSWLRQPDLQWHQDQFH��VWUXFWXUH�WDEOH� table.

If the current object is a header entry, enter the name of this object aspredecessor and choose dependency type R.

A view cluster can contain up to 15 objects.

5. After entering all objects in the table, mark one object as the initial object by markingthe checkbox in the ,QLWLDO column.

6. If you want to hide some of the view cluster objects from the user, mark the checkboxin the %DFNJU�column for these objects.

7. If the object has an N:M relation to its predecessor, mark the checkbox in the 1�0column.

8. Choose %DFN to leave the 1HZ�HQWULHV mode and return to the object structure.


)LHOG�GHSHQGHQFLHV

-XQH��

)LHOG�GHSHQGHQFLHVThe field dependencies define the relationships between view cluster objects. An object usuallyonly depends on its predecessor.

Each view cluster object must have at least one field dependency.

Field dependencies are maintained in a table. Field dependency maintenance fields:

)LHOG 'HVFULSWLRQ

9LHZ�7DEOH The current object. The green arrow next to the object allows navigation to theABAP/4 Dictionary.

)LHOG Name of the view or table field for which a (foreign key) relationship exists to afield in the predecessor object.

3UHGHFHVV� Object for which a relationship exists to the object specified in 9LHZ�7DEOH.

3UHG��ILHOG Field of the predecessor object to which the relationship exists.

7\SH Field relationship type. This specifies the actions to which the relationshipapplies.

You can define the following types of field dependencies:

• ‘ ‘: The specified fields have a key relationship.

• ‘S’: The field is defined in the ABAP/4 Dictionary as a read-only or subset fieldand is filled in a superior view cluster object.

If the value of the current field is changed in a hierarchically superior object, theview cluster maintenance automatically uses this change.

• ‘C’: This flag tells the system to execute an additional check of a field value of ahierarchically independent field.

The system checks the foreign key for the current contents of the internal viewcluster maintenance tables. This ensures that unsaved view cluster maintenancefield content changes are taken into account.

• ‘I’: Passes a header entry subset field selection condition to another objectwhich is not directly dependent on the header entry.

If foreign key relationships are defined in the ABAP/4 Dictionary, you canautomatically generate the field dependencies of an object to the other viewcluster objects by choosing *HQHUDWH�ILHOG�GHSHQGHQFLHV in the object structuremaintenance screen.

If the field dependence is of type ‘ ‘, the )LHOG and 3UHG��ILHOG fields remain initialfor a header entry.


)LHOG�GHSHQGHQFLHV

�� -XQH��

For dependent objects, you must make an entry for each key field that has a(foreign key) relationship with a predecessor key field.

For each entry in the object structure list, you must make at least one entry oftype ‘ ‘ in the field dependencies list.

If a dependent object contains key fields that are defined as subset fields in theABAP/4 Dictionary but have no relationship with the predecessor, you mustdistinguish between the following cases:

• Enter no field dependencies:

• The value for this field is stored in the ABAP/4 Dictionary or you specify it in auser exit. If no value is specified, the system prompts for it in a dialog boxwhen it first navigates to the object.

If no value is specified, the system prompts for it in a dialog box when it firstnavigates to the object. For hierarchical operations the system considers allentries read in, independently of this value.

• Eentry with initial predecessor for the field dependence:

• The system prompts for the subset field value in a dialog box each time younavigate to the object, unless it is entered at event 09 [Page 62] .

For hierarchical operations, the system uses all dependent entrieswithout considering the subset field, unless you use the events 11 [Page64] and 12 [Page 65].


$FWLYDWH�YLHZ�FOXVWHU

-XQH��

$FWLYDWH�YLHZ�FOXVWHUAfter maintaining the header entry, the object structure, and the field dependencies, you canactivate the view cluster.

1. Go to the view cluster header entry maintenance screen.

2. Choose $FWLYDWH.

The system performs the following actions:

− Save the view cluster definition.

− View cluster definition consistency check. If errors occur, the system displaysthem in an error log [Page 44] and does not activate the view cluster.

− Generate an entry in the maintenance object description.

− Optionally adapt the View maintenance screen [Page 42]. If you confirm theadaptation, the system adds a navigation subscreen to the maintenance screenand makes any necessary modifications. In addition, it deactivates all foreign keychecks on the maintenance screens, since they are performed internally in theview cluster maintenance.

Do not use the automatically modified maintenance dialogs to directly maintainthe corresponding table or view in the extended table maintenance. This maylead to inconsistencies in the database tables. You can only use the maintenancedialog for the view cluster maintenance.


0RGLI\�WDEOH�RU�YLHZ�PDLQWHQDQFH�GLDORJV

�� -XQH��

0RGLI\�WDEOH�RU�YLHZ�PDLQWHQDQFH�GLDORJVYou must adapt the table or view maintenance transactions to the view cluster maintenancefunctionality. This adaptation can be made automatically via the view cluster creationmaintenance transaction.

The system automatically makes the following modifications:

• Include a view cluster maintenance navigation subscreen

• Modify the PROCESS BEFORE OUTPUT (PBO) flow logic

• Modify the PROCESS AFTER INPUT (PAI) flow logic

• Modify the PROCESS ON VALUE-REQUEST flow logic for view cluster possibleentries help

• Deactivate the database level foreign key check for types “ “ and “C” by modifying thescreen field attributes

If you deactivated the foreign key relationships on the screens, you should nolonger use the maintenance dialog to directly maintain the table or view in theextended table maintenance. This may lead to inconsistencies in the databasetables. You can only use the maintenance dialog for the view clustermaintenance.

• After a PAI event input error, non-key fields that have a type “C” dependence onanother field remain ready for input.


0RGLI\�PDLQWHQDQFH�GLDORJV�PDQXDOO\

-XQH��

0RGLI\�PDLQWHQDQFH�GLDORJV�PDQXDOO\If you want to make the modifications by hand, you must make the following changes for all viewcluster view maintenance objects:

1. Deactivate the automatic foreign key check for all key fields listed in the fielddependencies on the view maintenance screens.

2. Deactivate automatic foreign key check for fields with the field dependence “C” thatalso have a foreign key relationship on database level.

3. The system performs an input check in the PAI modules LISTE_UPDATE_LISTE (listscreen) or DETAIL_PAI (detail screen). Make sure that fields with a field dependence“C” are included in the corresponding CHAIN statement.

4. For fields whose entity table is maintained in the view cluster, call the view-cluster-specific possible entries help in the PROCESS ON VALUE-REQUEST flow logic,using the module VCL_HELP_VALUES:

352&(66�21�9$/8(�5(48(67�

��),(/'��YLHZQDPH�ILHOGQDPH!�02'8/(�9&/B+(/3B9$/8(6�

Replace <viewname-fieldname> with the corresponding field names.

If you want to include a navigation subscreen in the view cluster maintenance,you must make the following changes to the flow logic of each view maintenanceelement:

i) Include the 1$9,*$7,21 subscreen in each overview screen.

ii) Include as first statement in the PBO event:

&$//�68%6&5((1�1$9,*$7,21�,1&/8',1*�9,0B6%6&5B352*9,0B6%6&5B'180�

i) Include the following statement in the PAI event directly after the LOOPstatement:

&$//�68%6&5((1�1$9,*$7,21�


7KH�HUURU�ORJ

�� -XQH��

7KH�HUURU�ORJIf view cluster activation errors occur, they are automatically listed in an error log.

The system displays an overview of all activation errors on the initial screen. Choose 'HILQHYLHZ�� for more information.

You can mark an error and choose 'LVSOD\�PHVVDJHV to display priority 1 error messages thatoccurred. Choose 9LHZ��$OO�PHVVDJHV to display all error message, including those of priorities 2and 3�

To see additional information on an error message, mark the error message and choose /RQJWH[W.


0RGLI\�GHIDXOW�YLHZ�FOXVWHU�PDLQWHQDQFH

-XQH��

0RGLI\�GHIDXOW�YLHZ�FOXVWHU�PDLQWHQDQFHYou need modifications whenever the default view clusters do not fulfil individual maintenancetransaction requirements. You can modify either the view maintenance on which the view clustermaintenance is based, or the view cluster maintenance itself.

0RGLI\�WKH�YLHZ�PDLQWHQDQFH�View maintenance modifications:

• Add your own fields to the maintenance screens, including check and processinglogic

• modify the maintenance screen layout

• include additional modules in the maintenance screen flow logic

• include user exits for each view maintenance dialog.

0RGLI\�WKH�YLHZ�FOXVWHU�PDLQWHQDQFH�For the modification of the view cluster maintenance itself, you can change the flow logic usingUser exits [Page 46]. Or, you can change the navigation subscreen title [Page 68] and deactivatefunctions [Page 69] for the maintenance of any objects of the view cluster.


(YHQWV

�� -XQH��

(YHQWVYou can include your own form routines in events to modify the standard flow at predefinedpositions in the flow logic. You must define the form routines in your own module pool (type ‘M’)or subroutine pool (type ‘S’).

You must not define these form routines in a function group.

The module pool or subroutine pool must contain the include LSVCMCOD forglobal data transfer.

The events belong to one of these two groups:

• Supplementary events allow you to include your own flow logic to supplement thestandard flow logic.

• Replacement events allow you to replace parts of the standard flow logic with yourown logic.

The following events exist:

6XSSOHPHQWDU\�HYHQW WULJJHUV�DQ�DFWLRQ

01 [Page 54] after initialising global variables, field symbols, etc.

02 [Page 55] after reading or determining selection conditions

03 [Page 56] immediately before navigating to another object

04 [Page 57] before saving the data in the database

05 [Page 58] after saving the data in the database

06 [Page 59] after locking/unlocking by a function module

07 [Page 60] after leaving the view maintenance module for an object

08 [Page 61] when terminating the processing

09 [Page 62] during navigation, after determining the selections and beforeprocessing a dialog box to query missing subset conditions

10 [Page 63] during navigation, immediately after determining the target object

11 [Page 64] when determining the dependent entries for a hierarchical viewcluster maintenance operation (copy, delete, undo, manualtransport)

12 [Page 65] when determining the superior entries for a hierarchical view clustermaintenance operation

5HSODFHPHQW�HYHQW UHSODFHV�WKH�VWDQGDUG�IORZ�ORJLF�IRU

EQ [Page 49] lock/unlock

GR [Page 50] determine selection conditions

RE [Page 51] read in

SV [Page 52] save data in the database


(YHQWV

-XQH��

CK [Page 53] check values of new or changed entries


0DLQWDLQ�HYHQWV

�� -XQH��

0DLQWDLQ�HYHQWVTo modify the standard flow logic, write your modification as form routines in a module pool orsubroutine pool. To assign them to events, proceed as follows:

1. Go to the view cluster maintenance transaction.

2. Go to the events maintenance screen.

3. Choose 1HZ�HQWULHV.

4. Press the pushbutton &KDQJH after the field )250�5RXWLQHV�PDLQ�SURJUDP. Enter themodule pool or subroutine pool in which you defined the form routines in the dialogbox.

5. Specify the event at which to supplement or replace the flow logic in the )2505RXWLQHV�WR�EH�H[HFXWHG�IURP�9LHZ�FOXVWHU�PDLQWHQDQFH table (YW field.

6. Enter the FORM routine name in the same table in the )250�URXWLQH field.

7. Save your input.

You can go directly to the FORM routines from the view cluster maintenancedialog, by pressing the arrow in the )250�5RXWLQHV�WR�EH�H[HFXWHG�IURP�9LHZFOXVWHU�PDLQWHQDQFH table.


0DLQWDLQ�HYHQWV

-XQH��

(YHQW�(4

8VH�

This event deactivates the standard VIEW_ENQUEUE function module enqueue logic and allowsyou to include your own logic.

The variable VCL_ENQ_ACTION contains the enqueue operation to beperformed:

E: enqueue

D: dequeue

The variable VCL_ACTION contains the selected maintenance operation:

U: change

S: display

T: transport

To change the maintenance operation to be executed, change VCL_ACTION.This may be necessary if you want to access an enqueued object with themaintenance operation &KDQJH. In this case, change VCL_ACTION to S.

Putting SPACE in VCL_ACTION ends the maintenance dialog.


0DLQWDLQ�HYHQWV

�� -XQH��

(YHQW�*5

8VH�

This event suppresses the header entries subset fields selection screen call. This allows you to:

• create dialog screens for the subset fields,

• determine subset fields without user input,

• use the function (QWHU�FRQGLWLRQV� (see “Select by contents” in Extended tablemaintenance [Ext.])

Putting 63$&( in the variable VCL_ACTION ends the maintenance dialog in auser exit. This may be necessary if the user chooses &DQFHO in the selectioncondition entry dialog box.

You must fill the internal table DBA_SELLIST as follows for each header entry:

• For each subset field, enter a value in the internal table DBA_SELLISTVALUE field.

• For selections on fields that are not subset fields, DBA_SELLIST is empty.Include these entries in DBA_SELLIST.

• To pass the header entry selection conditions to the dependent objects, youmust enter the selections for each dependent object in the internal tableDBA_SELLIST.

For each object for which you entered a value for a subset field in DBA_SELLIST,maintain this value also in the internal table DPL_SELLIST.

You must also consider the field dependencies of type I in the user exit.


0DLQWDLQ�HYHQWV

-XQH��

(YHQW�5(

8VH�

You can use your own routine instead of the standard read routine that calls the function moduleVIEW_MAINTENANCE_LOW_LEVEL with the parameter FCODE = ‘READ’.

You must read the data for each view cluster object into the internal table TOTAL.The maintenance of this table is described in Global view cluster maintenancedata [Page 66].

The system calls the object read routine whenever ISREAD is initial in the internaltable VCL_STRUC_TAB. You must set this value to 'X' in the user exit afterreading the data.

To end the maintenance dialog, set 9&/B$.7B9,(:� �63$&( in the user exit.


0DLQWDLQ�HYHQWV

�� -XQH��

(YHQW�69

8VH�

You can use your own data save routine instead of the standard routine that calls the functionmodule VIEW_MAINTENANCE_LOW_LEVEL with the parameter FCODE = ‘SAVE’.

You use the internal table VCL_STRUC_TAB UPD_REQU field to determine thechanged view cluster objects which must be saved. If this field is not initial, theVCL_STRUC_TAB object data have been changed, and must be saved.

To determine the modified entries of an object, use the internal table TOTALACTION field.

After saving the data, you must reset the fields UPD_REQU of the internal tableVCL_STRUC_TAB and ACTION of the internal table TOTAL to their initial values.


0DLQWDLQ�HYHQWV

-XQH��

(YHQW�&.

8VH�

This event deactivates the standard view cluster maintenance new entry creation and changechecks.

You must perform the following standard checks yourself in the user exit:

• When creating or changing an object entry, check the type ’C’ relationshipsmaintained in Field dependencies [Page 39].

• When you create a new entry in a dependent object, check that the entry in thehigher-level object exists, i.e. perform an internal “foreign key check”, even if noforeign key relationship is specified for this object in the ABAP/4 Dictionary. Thisguarantees the consistency of the view cluster.

The entry to be checked is in the global work area VCL_OBJECT_AREA.

In case of an error, send an appropriate message using RAISING INVALID_KEYor RAISING INVALID_VALUE.


(YHQW��

�� -XQH��

(YHQW��

8VH�

This event occurs after the initialization of the the view cluster global variables and field symbols.

At this event, you can:

• initialise additional global data in the user exit main program,

• use the routine VCL_SET_TABLE_ACESS_FOR_OBJ to fill your own field symbolsdefined in the main program, which access view cluster object data and managementtables,

• Deactivate menu functions [Page 69] by calling the function moduleVIEWCLUSTER_SET_EXCL_CUA_FUNCT.

• fill the internal table DBA_SELLIST with values for the subset fields you want to befixed for the view cluster maintenance and to which you want to deny the user accessduring the view cluster maintenance.


(YHQW��

-XQH��

(YHQW��

8VH�

This event occurs after reading or determining the selection conditions.

$W�WKLV�HYHQW��\RX�FDQ�H[HFXWH�WKH�IROORZLQJ�DFWLRQV�

• add other view cluster object selection conditions to the internal table DBA_SELLIST

If you want to include further selection conditions, you must check whether theyaffect dependent objects. If so, you must maintain the selection conditions forthese objects in the internal tables DBA_SELLIST and DPL_SELLIST.


(YHQW��

�� -XQH��

(YHQW��

8VH�

This event occurs immediately before going to another object. You can perform checks and/oractions on the object selected in the navigation and its entries at this event, for example:

• Deactivate menu functions [Page 69]

• perform entry-dependent authorization checks,

• Change the maintenance mode for the target object. The maintenance mode changeapplies to the entire view cluster. If you want to change the mode only for this oneobject, you must reset the maintenance mode at event 07 [Page 60].

To change the maintenance mode, set the global variable VCL_ACTION to:

U: change

S: display

T: transport

The destination object is in the global variables VCL_AKT_VIEW andVCL_NEXT_VIEW.

The source object is in the internal variable VCL_LAST_VIEW.

To end the maintenance, set VCL_AKT_VIEW back to its initial value in the userexit.

You can prevent navigatation to the target object in the user exit with thesestatements:

9&/B1(;7B9,(:� �9&/B/$67B9,(:�

9&/B$.7B9,(:� �9&/B/$67B9,(:�

&/($5�9&/B)81&7,21�


(YHQW��

-XQH��

(YHQW��

8VH�

This event occurs immediately before saving modified data in the database. You can performapplication-specific consistency checks. To prevent the system storing the data, set the variableVCL_STOP to ‘X’.

Event SV [Page 52] explains which flags tell you which objects and which entriesin these objects have been modified.


(YHQW��

�� -XQH��

(YHQW��

8VH�

This event occurs immediately after saving data changes in the database. You can:

• modify other tables that depend on the modified objects and are not contained in theview cluster definition,

• create view cluster maintenance logs.


(YHQW��

-XQH��

(YHQW��

8VH�

This event occurs after each enqueue/dequeue. You can enqueue or dequeue other objects thatare not contained in the view cluster definition, but which you maintain yourself in the viewcluster.

See event EQ [Page 49] for the global variables you need.


(YHQW��

�� -XQH��

(YHQW��

8VH�

This event occurs immediately after leaving a view maintenance module. You can:

• reset modifications of the maintenance mode made in event 03 [Page 56].

• perform final object maintenance activities.

The variables VCL_AKT_VIEW and VCL_NEXT_VIEW contain the name of theobject whose maintenance was left.

The variable VCL_FUNCTION contains the operation which left the viewmaintenance module.

If it was a navigation operation, the selected target object is not yet inVCL_NEXT_VIEW.


(YHQW��

-XQH��

(YHQW��

8VH�

This event occurs at the end of processing. You can reset the variables which you defined in theuser exit main program and you can start any activities that follow the object processing


(YHQW��

�� -XQH��

(YHQW��

8VH�

If selection criteria are missing for the navigation into an object, the system displays a dialog boxfor entry of the missing selections. This event occurs immediately after event 09. You can enterany selection conditions that cannot be derived from field dependencies in the internal tableDPL_SELLIST.

The global variables are filled as described in event 03 [Page 56].


(YHQW��

-XQH��

(YHQW��

8VH�

This event occurs during navigation, immediately after determining the target object. You can, forexample, forbid navigation to certain objects.

If the selected navigation is not allowed, you must perform the following actions:

9&/B1(;7B9,(:� �9&/B/$67B9,(:�

&/($5�9&/B)81&7,21�


(YHQW��

�� -XQH��

(YHQW��

8VH�

This event occurs when determining the dependent entries for hierarchical view clusteroperations (such as delete).

At this event, you can specify selection conditions for subset fields that cannot be derived fromfield dependencies in the view cluster. Proceed as follows:

• Specify an entry with empty predecessor field in the field dependence 6XEVHW field.

• Pass the desired subset field value in the user exit global variableVCL_REDUCTION_AREA.

VCL_REDUCTION_AREA is a work area so you must put the value in the correctposition.

• The global variable VCL_OBJECT_AREA contains the entry in the superior object, forwhich you determine the dependnent entries.

If you specify no user exit at event 11 for a view cluster object with such a subsetfield, the system considers all dependent entries, independent of the value of thesubset field.


(YHQW��

-XQH��

(YHQW��

8VH�

This event occurs when determining the superior entries for hierarchical view cluster operations(such as delete).

You can specify selection conditions for subset fields in superior objects which cannot be derivedfrom the next object in the view cluster field dependency definition. Proceed as follows:

• Specify an entry with empty 2EMHFW field in the field dependency�6XEVHW field.

• Pass the desired value for the subset field in the global variableVCL_REDUCTION_AREA. The system uses this value in the calculation of thesuperior entries.

VCL_REDUCTION_AREA is a work area so you must put the value in the correctposition.

• The global variable VCL_OBJECT_AREA contains the entry in the dependent objectfor which you determine the superior entry.

If you specify no user exit at event 12 for a view cluster object with such a subsetfield, the system considers all superior entries, independent of the value of thesubset field.


9LHZ�FOXVWHU�PDLQWHQDQFH�JOREDO�GDWD

�� -XQH��

9LHZ�FOXVWHU�PDLQWHQDQFH�JOREDO�GDWDUser exit data is stored in a COMMON area which is declared in the COMMON part of theLSVCMCOD include. The user exit FORM routine module pool or subroutine pool must containthis include program.

View cluster maintenance system accesses the following internal tables for each object:

7DEOH FRQWDLQV

HEADER object ABAP/4 Dictionary header entry

NAMTAB ABAP/4 Dictionary object field information

DBA_SELLIST object read database access selection conditions

DPL_SELLIST selection conditions for displaying part of a work area

TOTAL data table with all object data read, added or changed

EXTRACT object data display work table, which contains only those table lines from theinternal table TOTAL that the user selected

For each object, these tables are accessed by calling the FORM routineVCL_SET_TABLE_ACESS_FOR_OBJ in the LSVCMCOD include. You must pass the objectname as parameter for the FORM routine. The system fills the global field symbols with thecontents of the internal tables for the object specified as parameter:

JOREDO�ILHOG�V\PERO FRQWDLQV

<VCL_HEADER> HEADER

<VCL_NAMTAB> NAMTAB

<DBA_SELLIST> DBA_SELLIST

<VCL_DPL_SELLIST> DPL_SELLIST

<VCL_TOTAL> TOTAL

<VCL_EXTRACT> EXTRACT

The folowing global data exist for the view cluster maintenance:

JOREDO�YDULDEOH FRQWDLQV

VCL_FUNCTION function code from the view maintenance

VCL_ACTION maintenance action: S: display; U: change; T: transport

VCL_ENQ_ACTION enqueue action: E: enqueue; D: dequeue

VCL_AKT_VIEW current object

VCL_LAST_VIEW previously processed object

VCL_NEXT_VIEW navigation target object

VCL_CORR_NUMBER request number for change request

VCL_STRUC_TAB view cluster object structure


9LHZ�FOXVWHU�PDLQWHQDQFH�JOREDO�GDWD

-XQH��

VCL_SUBSET_TAB field dependency table

VCL_REDUCTION_AREA table work area of the dependent/superior object (for events 11and 12)

VCL_OBJECT_AREA table work area for the object for which the system founddependent/superior entries at the events 11 and 12

VCL_LAST_CURSOR_IX current cursor position of the current object

VCL_STOP cancel flag in event 04 (cancel at VCL_STOP = ‘X’)


0RGLI\�QDYLJDWLRQ�VXEVFUHHQ�WLWOH�DQG�SRVLWLRQ�WH[W

�� -XQH��

0RGLI\�QDYLJDWLRQ�VXEVFUHHQ�WLWOH�DQG�SRVLWLRQ�WH[WThe navigation subscreen title and position text are set by the view cluster maintenancetransaction to 1DYLJDWLRQ by default. You can modify the title using the function moduleVIEWCLUSTER_SET_SUBSCREEN_TITL.

1. Create a FORM routine that calls the function module VIEWCLUSTER_SET_SUBSCREEN_TITL.

2. Pass the the navigation subscreen title and position text as export parameters to yourFORM routine.

3. Enter the FORM routine at event 01 [Page 54].

Modification of the navigation subscreen title:

&$//�)81&7,21�9,(:�&/867(5B6(7B68%6&5((1B7,7/

��(;3257,1*

��68%6&5((1B7,7/(� �1HZ�WLWOH

��326,7,21B7(;7�� (QWU\

��(;&(37,216

��27+(56��


'HDFWLYDWH�PHQX�IXQFWLRQV

-XQH��

'HDFWLYDWH�PHQX�IXQFWLRQVYou can deactivate menu functions in a view cluster object maintenance screen by calling thefunction module VIEWCLUSTER_SET_EXCL_CUA_FUNCT in a user exit FORM routine, e.g. atview cluster maintenance event 01 [Page 54].

1. Enter the function codes of the functions you want to deactivate in an internal table ofthe structure VIMEXCLFUN.

2. Pass the name of the object and the corresponding internal table that contains thefunctions to deactivate to the function module VIEWCLUSTER_SET_EXCL_CUA_FUNCT.

&$//�)81&7,21�9,(:�&/867(5B6(7B(;&/B&8$B)81&7

��(;3257,1*

��2%-(&7�� REMHFW�QDPH!

��7$%/(6

��(;&/B&8$B)81&7�� LQWHUQDO�WDEOH!

��(;&(37,216

��2%-(&7B127B)281'��

��9,(:�&/867(5B127B$&7,9(� ��

��27+(56��

Any functions you deactivated in a previous call are automatically re-activated,unless you include them again in the internal table that contains the functions todeactivate.


&DOO�WKH�YLHZ�FOXVWHU�PDLQWHQDQFH�GLDORJ

�� -XQH��

&DOO�WKH�YLHZ�FOXVWHU�PDLQWHQDQFH�GLDORJYou can call the generated maintenance dialogs in different ways:

• Enter the name of the view cluster in the SM34 view cluster maintenance transaction.Choose 0DLQWDLQ to go to the generated maintenance dialog.

• Call a parameter transaction (see transaction codes) in the command field or fromwithin an application. You go to the extended table maintenance with the specifiedparameters. Choose 0DLQWDLQ to go to the generated, possibly changed, maintenancedialog.

• Call the function module VIEW CLUSTER_MAINTENANCE_CALL:

&$//�)81&7,21�9,(:�&/867(5B0$,17(1$1&(B&$//

��(;3257,1*

��9,(:&/867(5B1$0(��

��67$57B2%-(&7��

��0$,17(1$1&(B$&7,21��

��5($'B.,1'��

��6+2:B6(/(&7,21B32383��

��&255B180%(5��

��12B:$51,1*B)25B&/,(17,1'(3��

��7$%/(6

��'%$B6(//,67��

��'%$B6(//,67B&/867(5��

��(;&/B&8$B)81&7B$//B2%-(&76��

��(;&/B&8$B)81&7B&/867(5��

��(;&(37,216

��&/,(17B5()(5(1&(��

��)25(,*1B/2&.��

��9,(:�&/867(5B127B)281'��

��9,(:�&/867(5B,6B,1&216,67(17��

��0,66,1*B*(1(5$7('B)81&7,21��

��12B83'B$87+��

��12B6+2:B$87+��

��2%-(&7B127B)281'��

��12B79',5B(175<��

��12B&/,(17,1'(3B$87+��

��,19$/,'B$&7,21��

��6$9,1*B&255(&7,21B)$,/('��


&DOO�WKH�YLHZ�FOXVWHU�PDLQWHQDQFH�GLDORJ

-XQH��

��6<67(0B)$,/85(��

��81.12:1B),(/'B,1B'%$B6(//,67� ��

��0,66,1*B&255B180%(5��

��27+(56��

With this call, you must pass the following parameters to the function module:

3DUDPHWHU FRQWDLQV

VIEW CLUSTER_NAME view cluster name

START_OBJECT initial object for the view cluster maintenance(optional)

MAINTANANCE_ACTION the action to be performed: display (S), maintain (U),transport (T)

READ_KIND Read type: (optional)

‘ ‘: read all view cluster objects

‘T’: read, starting at the header entry, only for onebranch of the hierarchy

SHOW_SELECTION_POPUP whether to display the dialog box for enteringselection conditions (optional)

CORR_NUMBER correction number for changes made (optional)

NO_WARNING_FOR_CLIENTINDEP whether to suppress the warning. The table is client-independent (optional)

DBA_SELLIST the selection conditions for the initial object (optional)

DBA_SELLIST_CLUSTER the selection conditions for any view cluster objects(optional)

EXCL_CUA_FUNCT_ALL_OBJECTS table of all GUI functions you want to deactivate forall view cluster objects (optional)

EXCL_CUA_FUNCT_CLUSTER table with all GUI functions you want to deactivate forany view cluster objects (optional)

For more information on export parameters, see the function module documentation.

Table Maintainance

Documents

Transcript of Table Maintainance