TAW12 Workbench Fundamentals Part 2

Card Set Information

Author:
jaegli
ID:
285218
Filename:
TAW12 Workbench Fundamentals Part 2
Updated:
2014-10-08 16:23:03
Tags:
TAW12 Workbench Fundamentals Part WORKBENCH FUNDAMENTALS
Folders:

Description:
Workbench Fundamentals Part 2
Show Answers:

Home > Flashcards > Print Preview

The flashcards below were created by user jaegli on FreezingBlue Flashcards. What would you like to do?


  1. 3 categories of data types in the dictionary
    • Data element
    • Structure
    • Table type
  2. 6 ABAP Dictionary services that support program development
    • Input helps (F4): Using search help
    • Field help (F1): Using documentation of data element
    • Input check: Ensure data consistency with foreign key relations
    • Locks: Using Lock objects
    • Data buffering: Using buffering in technical table settings
    • Logging: Enable logging in technical table settings
  3. Settings of a domain
    • Format: Data type and length
    • Output Characteristics: Length, case-sensitivity, etc.
  4. 6 Types of structure components
    • Data element
    • Integrated types
    • Table types
    • Definition of tables/views
    • other structure types
    • Object references (Ref to)
  5. 3 types of structures
    • Flat: All components are simply typed with data elements/integrated types
    • Nested: At least one component is typed as structure
    • Deep: At least one component is typed as table
  6. 3 Basic objects for defining data in the Dictionary
    • Table
    • Domain
    • Data element
  7. 2 ways to use a transparent table
    • Access data through OPEN or native SQL
    • Use it as structure type
  8. 4 Characteristics of including structures using the .INCLUDE syntax
    • Avoid redundant structure definitions
    • Tables cannot be included in other tables
    • Includes can contain other includes
    • Foreign keys of Include-structure are passed to the including table
  9. 4 Important data classes for tables
    • Master data: much data, seldom modified
    • Transaction data: much data, frequently modified
    • Organizational data: less data, seldom modified
    • System data: Necessary system data, for example programs
  10. 4 Technical settings of transparent tables
    • Data class: Master data, customizing, etc.
    • Size category: Expected size (from 0 to 8)
    • Buffering: Kind of buffering
    • Logging: Log changes
  11. 3 Advantages of pooled and cluster tables
    • Fewer tables and fields
    • Data compression
    • Encrypted data storage
  12. 4 Disadvantages of pooled and cluster tables
    • Limitations on database functions
    • No table appends
    • Selection limited to key fields (Cluster)
    • Longer keys than necessary (Pooled)
  13. 4 Consideration points when creating an index
    • Should be as small as possible
    • Only use significant and frequently queried fields
    • As more frequent data is changed, the less indexes should be used
    • As disjunct as possible
  14. 2 Types of indexes
    • Primary: Unique, as it consists of all key fields
    • Secondary: Unique or Non-Unique with frequently queried fields
  15. 3 Main characteristics of Indexes
    • 3-character ID
    • ID 0 reserved for primary index
    • Customer-index for SAP-tables possible
  16. 3 types of table buffering
    • Full: When accessed, all records are buffered
    • Generic:¬†When accessed, records with same left-justified key are buffered
    • Single-record: Only accessed record is buffered
  17. 2 Characteristics of Buffer-Synchronization
    • Synchronizes buffers between several application servers
    • Low network load
    • Obsolete entries between moments of synchronization
  18. 6 Decision points for table buffering type
    • Small tables (<1000 records): Full
    • Many key accesses: Generic
    • Many SELECT SINGLE accesses: Single-record
    • Table size < 32 KB: Full
    • Many read only accesses: No buffering
    • Many accesses to non existing entries: Full
  19. 5 Characteristics of a foreign key
    • Links two tables
    • Primary key of the linked table
    • Linked table is called check table or referenced table
    • Foreign key field to be cheched is the Check Field
    • Checked during screen input and value help
  20. 4 Settings for foreign key fields
    • Not specified: No info about key kind given
    • No key fields/Candidates: Fields do not identify the foreign key table
    • Key fields/Candidates: Fields identify the foreign key table
    • Key fields of a text table: Foreign key table contains country specific texts
  21. 5 ABAP Dictionary runtime objects
    • data element
    • table type
    • view
    • structure
    • table
  22. 3 ways of adjusting a database table and situation they are used by the system
    • Delete and Create: No data stored
    • ALTER TABLE: Data is stored
    • Converting: When ALTER TABLE fails
  23. 7 steps of table conversion
    • 1: Table is locked
    • 2: Old Table is renamed with prefix QCM
    • 3: New table is created with prefix QCM8
    • 4: Data is moved from QCM to QCM8
    • 5: QCM Table is deleted
    • 6: QCM8 Table is renamed to actual table name. Indexes are created and dependent objects activated
    • 7: Lock is removed
  24. 2 Problems that can occur while table conversion
    • Overflow of tablespace
    • Duplicate keys when key was shortened
  25. 4 Restrictions for append structures
    • Not for pooled and cluster tables
    • Tables containing long field (LRAW, LCHR) cannot be extended
    • Fields have to be in the customer namespace with ZZ or YY
    • Can only be assigned to one table
  26. 5 Enhancement categories of SAP standard tables
    • 1 - Not classified: No category
    • 2 - Not enhanceable: Cannot be enhanced
    • 3 - Enhanceable and character-like: All components must be char-like
    • 4 - Enhanceable and character-like or numerical: No deep data types
    • 5 - Freely extentable: Data type is optional
  27. 2 ways of enhancing SAP standard structures and tables
    • Customizing Includes
    • Append Structures
  28. 2 Types of Joins and the corresponding view type
    • Inner Join - Database View: Entries which are included in all view tables
    • Outer Join - Maintenance View: All entries are selected
  29. 5 Steps to create a maintenance view
    • Copy tables: Primary table and linked tables
    • Copy View fields: Views to be displayed
    • Selection Conditions: Restrictions for data records
    • Maintenance status: Maintenance status of the view
    • Activate: Activate the object
  30. 5 Fields to maintain when creating maintenance dialog
    • Function group: Function group where the dynpros are created in
    • Authorization group: Define which users are authorized
    • Maintenance type: 1 or 2 steps
    • Maintenance screens: Number of the generated dynpros
    • Recording routine: Specify how values can be transported
  31. 2 Advantages of View clusters
    • Navigation: Navigate between dialogs
    • Consistency: Ensure consistency accross dependent tables
  32. 3 Ways to attach a search help to dictionary objects
    • Assign to a field of structure or table
    • Check table of check fields
    • Assign to a data element
  33. 3 presentation forms for a input help
    • Listbox
    • Control (amodal)
    • Dialog box (modal)
  34. 3 Characteristics of an Append Search Help
    • Collective search help assigned to another collective search help
    • Improve component separation
    • Hide elementary search helps
  35. 4 Characteristics of Search help exits
    • Function module with standardized interface
    • Existing modules with prefix F4UT_
    • Should only be used in exceptional cases
    • Makes input helps more difficult to maintain
  36. 3 possible default values for search help parameters
    • Literals
    • System fields
    • GET parameters
  37. 4 Event blocks of a selection screen
    • INITIALIZATION: preassign default values
    • AT SELECTION-SCREEN OUTPUT: Before screen is displayed again
    • AT SELECTION-SCREEN: After screen is displayed
    • START-OF-SELECTION: Select data
  38. 4 Design elements for a selection screen
    • BLOCKS: Group logically dependent screen elements
    • LINES: Place elements in one output line
    • Additional Screens: Further selection screens to be called
    • Tabstrips: Selection Screen for each tabstrip
  39. 3 Components to define when creting a selection screen with tabstrips
    • Subscreen area
    • Individual tab titles
    • Selection screens as subscreens for individual tab titles
  40. 4 Additional events for AT SELECTION-SCREEN
    • ON BLOCK: Check input of all block elements
    • ON END OF <seltab>: PAI event
    • ON HELP-REQUEST: when F1 info is requested for a field
    • ON VALUE-REQUEST: when F4 help is requested for a field
  41. 6 ABAP program types
    • Complete (Executable)
    • Type 1: Executable Program
    • Type M: Module Pool
    • Incomplete (Non-executable)
    • Type F: Function Group
    • Type J: Interface Pool
    • Type K: Class Pool
    • Type I: Include Program
  42. 4 Components of a screen
    • screen masks
    • attributes
    • elements
    • flow logic (No ABAP Code!)
  43. 2 types of software logic processors
    • ABAP processor: controls the program flow
    • DYNP processor: controls flow logic of screens
  44. 4 Elements of a GUI status
    • Menu bar: functions to be processed by the program
    • Standard toolbar: same on every SAP screen
    • Application toolbar: frequently used functions of the program
    • Function key settings: Assign functions to function keys
  45. 4 Types of key settings in a GUI title
    • Screen
    • Dialog box
    • List
    • List in a dialog box
  46. 6 Types of error dialog messages
    • A - Termination: Processing terminates
    • X - EXIT: Short dump
    • E - Error: Processing stops, entries can be corrected
    • W - Warning: Processing stops, entries can be corrected
    • I - Information: Continue by confirming
    • S - Success: Displayed on status bar
  47. 2 Functions to be performed with subscreens
    • Display group of objects from the main screen
    • Display or hide extra fields on the main screen
  48. 4 Scenarios where subscreens can be used
    • Screen enhancements
    • Within other screen objects
    • Modification assistant
    • Web transactions
  49. 5 Restrictions that apply for subscreens
    • CALL SUBSCREEN not allowed in Loops and Chains
    • No OK-Code field
    • Object names must be unique accross all screens
    • No module with AT EXIT-COMMAND addition
    • No usage of SET TITLEBAR, SET PF-STATUS, SET SCREEN OR LEAVE SCREEN
  50. 3 Restrictions for tabstrips
    • The screen surrounding the tabstrip must remain constant
    • Useless for processes with a certain order
    • Changes in one tab can not affect other tabs dynamically

What would you like to do?

Home > Flashcards > Print Preview