1 / 11

ERP I1, Session 7

ERP I1, Session 7. dynpro. SAP GUI. SAP has many GUI solutions: Lists (ALV) dynpro ( Dyn amic Pro gram) Business Server Pages Web dynpro More?. dynpro. A dynpro consists of Numbered screens A navigation structure between the screens Data to display on the screens

samira
Download Presentation

ERP I1, Session 7

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ERP I1, Session 7 dynpro

  2. SAP GUI • SAP has many GUI solutions: • Lists (ALV) • dynpro (Dynamic Program) • Business Server Pages • Web dynpro • More?

  3. dynpro • A dynpro consists of • Numbered screens • A navigation structure between the screens • Data to display on the screens • Functionality for the screens • Menus, toolbars, and titles for the screens • More... • All this is grouped in a function group

  4. Screen navigation structure • All screens are linked to a 'next' screen. • Example: Registering on a homepage 100 200 300 400 Enter login information Enter personal information Fill stupid questionnaire Confirm 210 Enter extra information

  5. Screen navigation • Navigation to next screen when • Button clicked • Menu item selected • keyboard shortcut pressed • Checkbox toggled (sometimes) • Radio button selected (sometimes) • The default next screen is the screen itself.

  6. More on navigation • Navigation to screen 0 terminates dynpro • Navigation happens after some code is run • Override navigation: • SET SCREEN <screen-no> • Override and navigate now: • LEAVE TO SCREEN <screen-no> • Navigate and then return to here: • CALL SCREEN <screen-no>

  7. Dynpro flow logic

  8. PBO & PAI configuration PBO PROCESS BEFORE OUTPUT. MODULEread_data.   MODULE set_status. PROCESS AFTER INPUT.   MODULE exit_admin AT EXIT-COMMAND.   MODULE process_action. PAI

  9. Function codes • A function code is the name of the action that caused navigation • Function codes are written to OK_CODE. • OK_CODE can be renamed, but it's the conventional name. • You can react to the action in the PAI section. • OK_CODE has type sy-ucomm. • OK_CODE is a field (see next slide)

  10. Fields & Dictionary structures • Fields • Data objects (variables) • Public in the entire function group • Declared like normal data objects • Dictionary structures • Fields with structured type • Has same name as type • Used to represent data on screens • Declared with keyword 'TABLES'

  11. Recap • A dynamic program is a number of screens with a navigation structure • Each screen defines what happens before output (PBO) and after input (PAI) • The action that caused the navigation is saved in OK_CODE • Data for the entire dynpro is stored in fields and/or dictionary structures

More Related