RF Cookbook - Part I Description - SAP

2y ago
299.06 KB
59 Pages
Last View : 6d ago
Last Download : 2m ago
Upload by : Mia Martinelli

Version: 2.3Release: 1.0Author: SAP DevelopmentRF Cookbook - Part 10-022003–11–172004–01–272.0After evised2008–03–142.3Revised2016-05-02

Contents1Objective . Description of the RF Framework. 5RF Runtime – Framework Interaction Model. 6RF Framework Customizing Overview . 8Sending Messages to Working Resources . 92RF Framework . . 14Important Tables and Structures . 14Important Classes . 14Debugging . akpoints .14Method /SCWM/CL RF BLL SRVC CALL FLOW PROCESS.14Method /SCWM/CL RF BLL SRVC GET STEP FLOW .15Method /SCWM/CL RF BLL SRVC RUN .15Method /SCWM/CL RF BLL SRVC DISPLAY STEP.15Method /SCWM/CL RF BLL SRVC CHECK VERIF PRF.15Breakpoint IDs.153RF Cookbook . Definition . 16Presentation Profile Definition. 16Display Profile Definition . Screens.17Template Screen Title .17Message Handling . Profile Definition . 18Define Logical Transaction . 18Assign Text to Logical Transaction and Other Objects. 19Create Menu Item . 20Assign Text to Menu Item . 20Create Menu Hierarchy Including Submenus and Transactions . 20Define Logical Transaction Steps . 20Define Initial Step for Logical Transaction . 21Define Application Data Containers . 213.12.1Using Tables in the RF Framework .223.13Create Template Screen. 223.13.1Use Custom Template Dynpro .223.14Create Subscreens . 233.14.1 Predefined Screen Groups. Group 1.24 3.24Automatic Page Up / Page Down Implementation .24Field to Field Navigation .25Navigation Between Verification Fields.25Navigation Between Input Fields (No Verification Fields) .25Navigation on a Screen with Input Fields and Verification Fields .26Exiting a Screen Without Saving Data in Internal Structures .26Exiting a Screen and Saving Data in Internal Structures.26Exiting a Screen and Calling the Content Provider .263.15Define Function Code Catalog . 273.15.1Predefined Function Codes in the RF Framework . Text to Function Code . 28Create Services to Support Business Logic . 28Define State Catalogue. 29Map Logical Transaction Step to Subscreen . 29Define Function Code Profile . 303. Status Is Defined for the Template .31Connect Screen Function Codes and RF Framework Function Codes.31Handle More Function Codes Than Available Pushbuttons on a Screen or Step .323.21Define Step Flow . 333. of Initial Screen After Menu Selection .34PAI of Screen and Direct Display of Next Screen .34PAI of Screen and PBO of Next Screen .34Call of Common Screen from Several Screens During Transaction .35Customizable ENTER / Set Next Step Dynamically Using the CP .35Additional Information .363.223.23Set Default Navigation at Transaction End . 37Set Verification Profile . 373.23.1Verification .383.24Presentation Device Catalog . 404Layout . 414.14.2Screen . 41Fields. 414.2.1Field Length.425Programming Information . 435.15.2Posting . 43Exception Handling and Using Shortcuts . 435. .43Exceptions .445.35.45.5Differences . 44Support LIST Functions . 44Display of Text (from Delivery or Hazardous Material) . 45

5.6Methods Available to the Content Provider . 455. into the Framework .45Methods out of the Framework .465.75.85.9Global Variables . 46Display Technical Data on GUI Title of RF UI . 47Hard-Coded Logical Transaction . 496Using the Tools Provided . 516.16.2Menu Manager . 51Screen Manager . ate, Copy, and Delete Display Profiles .52Creating a Display Profile .53Copying a Display Profile .53Guideline for screen conversion .54Deleting a Display Profile .54Editing Screens of a Display Profile .55Screen Maintenance.556.3Wizards . 566. Screen .56Modify Screen .57Error Message Handling in RF Wizard.57

1ObjectiveSAP has developed a new radio frequency (RF) concept.This RF cookbook helps developers to begin working in the RF framework. Itanswers frequently asked questions and helps to avoid common errors. This RFcookbook also provides some useful tips about the standard layout and screenstructure that should be applied in the standard transactions.Initially, the RF framework will be used for development in the ExtendedWarehouse Management (EWM) project. However, the RF framework isapplication-independent and could also be used in other projects or applications.1.1 Architecture Description of the RF FrameworkTransaction /SCWM/RFUI is the starting point for all logical RF transactions inEWM. Logical transactions cannot be started directly from the SAP Easy Accessscreen and no equivalent transaction has been created in SE93.The Easy Enhancement Workbench (EEWB), which can be used for customerenhancements, is integrated into the RF framework. Within the EEWB, usersexecute an RF process and when the modification screen is reached, theenhancement tool is triggered. Users then select the type of enhancement thatthey want to carry out. The appropriate enhancement wizard launches andguides the user through the enhancement process. If the user wants to enhancefields on the user interface, the screen painter is called once the enhancement is

complete so that further adjustments to the screen can be made manually. Thisis part of post processing.1.2 RF Runtime – Framework Interaction ModelThe RF framework architecture consists of three distinct layers:1. Dynpro layer2. Business logic layer3. Content providerThe dynpro layer is concerned with all screen-related data, display profiles,presentation devices, subscreens and templates, and so on.At runtime, the business logic layer receives transactional parameters such asnext step, screen, function code profile, and so on, from the underlyingCustomizing settings.Content provider stores and supplies the relevant data for processing.The following sequence diagram shows how these layers interact.

Object1Dynpro LayerBusiness Logic LayerContent ProviderUserInvoke Transaction()Execute transaction()Set presentation parameters & current logical transaction()Set initial step & function code()Execute Step()Execute FM()Determine next step(){Next step in background}Execute next step()Text ADetermine the following step()Execute Step()Execute FM()Update Stack()Build Function Code Profile()Build Verification Profile()Verify fields status and profiles prior to display()Pass presentation data to template and sub-screen()Execute based on input and function code()Check verification values()Check verification values()Update Stack()A

1.3 RF Framework Customizing OverviewCustomizing for the Radio Frequency (RF) Framework comprises the followingareas:1. User and resource settings2. Interface parameters and communication structures3. Basic building blocks4. Configuration and scenario assignmentsIn Customizing (transaction SPRO), the main Customizing activities for the radiofrequency framework are available under Extended Warehouse Management àMobile Data Entry.The Customizing activity Define Steps in Logical Transaction contains thefollowing submenus:

User and resource settings support the definition of new presentation and personalizationprofiles, which are required to define behavior that varies from standard configuration. Theseprofiles are linked to resource logons, making it possible to define alternative responses (such asdisplaying a user-defined screen instead of the standard screen) for a particular user or usergroup.Interface parameters and communication structures can be defined for data communicationbetween different screens (dynpros). For more information, see the Define ApplicationParameters option.Basic building blocks include the definitions of logical transactions, steps, and function codes.Configuration includes assigning steps to logical transactions and their flow, determiningscreens, assigning function codes, and assigning validations. For more information, see thefollowing sections.You can call some Customizing activities directly using transaction codes, for example,/SCWM/RFMENU for the RF Menu Manager or /SCWM/RFSCR for the RF Screen Manager.You can call Presentation Device Maintenance using transaction /SCWM/PRDVC.1.4 Sending Messages to Working ResourcesYou can send messages to different resources from the EWM Monitor. To do so,proceed as follows:1. Call transaction /SCWM/MON.

2. Enter the warehouse number and the variant of the monitor.3. Expand the Resource Management node and double-click Resource.4. Enter one or more resource names on the selection screen.The resources are displayed on the right side.5. Select the relevant resource names and choose More Methods to sendmessages to the selected resources.

6. Enter the message text in the dialog box and choose Send Message.If the resource is logged on to the RF application, the message isdisplayed.You can deactivate the function for sending and processing RF resourcemessages by calling transaction /SCWM/ RSCMSG DEACT. Alternatively,choose the following on the SAP Easy Access screen:

Activate or deactivate the function for sending messages to resources atwarehouse level by selecting or clearing the checkbox in the Deactivate column.By default, messages can be sent, meaning that the checkbox is not selected.

Note:1. If you deactivate the function for sending messages for the warehouse,you cannot send messages to the resource in the monitor. The messagereceipt process is also deactivated in the RF framework. If you attempt tosend a message to the resource in the monitor, the system displays anerror message.2. When you change the Deactivate field in the Customizing settings, youmust restart the monitor and log in again for the change to be applied tothe resource.

2RF Framework2.1 StructureThe RF framework is developed in package /SCWM/RF FRAMEWORK.2.2 Important Tables and StructuresTable/SCWM/TAPPL CAT/SCWM/TDPRF CAT/SCWM/TFCOD CAT/SCWM/TFCOD PRF/SCWM/TMENU CAT/SCWM/TMENU HIER/SCWM/TOBJ TXT/SCWM/TPARAM CAT/SCWM/TPRDV CAT/SCWM/TPRES CAT/SCWM/TPRSN PRF/SCWM/TSTAT CAT/SCWM/TSTEP CAT/SCWM/TSTEP FLOW/SCWM/TSTEP SCR/SCWM/TTRNS CAT/SCWM/TTRNS NAV/SCWM/TVALID PRF/SCWM/TVLID CATDescriptionApplication, for example, WMEDisplay profileFunction code catalogFunction code profileMenu catalogMenu hierarchyObject textData containerPresentation devicePresentation profilePersonalization profileState catalogStepsStep flowMapping of foreground steps tosubscreenLogical transactionsNavigation at end of logicaltransactionVerification and validation profileVerification and validation objects2.3 Important ClassesClass/SCWM/CL RF BLL DB/SCWM/CL RF BLL SRVCDescriptionPresentation data accessRF Business Logic Layer2.4 Debugging2.4.1Breakpoints2.4.1.1 Method /SCWM/CL RF BLL SRVC CALL FLOW PROCESSThis method calls the function modules defined in /SCWM/TSTEP FLOW. Method /SCWM/CL RF BLL SRVC GET STEP FLOWThis method reads table /SCWM/TSTEP FLOW with the actual step data todetermine the next step. Method /SCWM/CL RF BLL SRVC RUNThis method is called using transaction /SCWM/RFUI. It contains the loop inwhich the steps and screens are called or processed. Method /SCWM/CL RF BLL SRVC DISPLAY STEPThis method calls the screens once the verification field check has been called. Method /SCWM/CL RF BLL SRVC CHECK VERIF PRFThis method checks the verification fields that have been completed against thecorresponding data fields. If a barcode function module is set in the verificationprofile (/SCWM/TVALID PRF field FMODUL TRNSL), this function module iscalled. If a verification function module is set in the verification profile(/SCWM/TVALID PRF field FMODUL VERIF), this function module is called. Formore information about the verification process, see Verification.2.4.2Breakpoint IDsIn the RF framework, we have implemented the following breakpoint IDs:· /SCWM/RF FRAMEWORK· /SCWM/RF FRAME STEP· /SCWM/RF FRAME VERIFYou can activate the breakpoint IDs in transaction SAAB.

3RF Cookbook3.1 Application DefinitionAn application is the highest organizational level in the RF framework. Atapplication level, you define the start transaction. In the standard SAP system,the start transaction is /SCWM/RFUI.The application for the Warehouse Management Engine (WME) is 01.In addition, you can define a function module to control the verification fields froman application-relevant point of view. This means that all verification fields in anRF transaction are ready for input. This function module enables you todeactivate verification fields in a process-specific manner. The function moduleused for EWM is /SCWM/RF WME SET VERIFICATION.To maintain application data, call transaction SM30 and enter view/SCWM/V TAPPL CAT (for more information, see SAP Note 938314). The datais stored in table /SCWM/TAPPL CAT.3.2 Presentation Profile DefinitionThe presentation profile (together with the personalization profile) is used tosupport different menu structures for different users. The presentation profile isassigned to the application.The presentation profile for the standard transaction is ****.You can maintain the presentation profile by choosing Define PresentationProfiles. The records are stored in table /SCWM/TPRES CAT.3.3 Display Profile DefinitionThe display profile is used to support different devices and their different screencharacteristics. We provide one display profile.The display profile for standard transaction is **.For the display profile, you specify the height and width of your total screen(8x40), as well as the template program (/SCWM/SAPLRF TMPL) and screens(0001 and 0002 for messages). You also define the following at profile level:· Length of the pushbuttons (8)· Number of pushbuttons (4)· Length of menu items (20)· How error messages are displayed (0 display on a separate screen)· Where error messages are displayed

You can use the three parameters BEEP INFO, BEEP WARN, and BEEP ERR tomaintain the number of beeps processed by the device when a message isdisplayed. This works only if the device supports the beep function.A display profile record can be created in transaction /SCWM/RFSCR (or inCustomizing). The data is stored in table /SCWM/TDPRF CAT.3.3.1Template ScreensThe standard SAP system is shipped with two templates, both of which have thesize 8x40 and contain seven lines for the subscreen.Dynpro 0001 with one line (last line) for four pushbuttons and an input field forkeyless navigation and exceptions.Dynpro 0002 with only the message field on the last line (used only for messageprocessing). The corresponding function group is /SCWM/RF TMPL. Template Screen TitleNo GUI title is shipped for SCM 5.0 or SCM 5.1. The title SAP appears on the RFscreens. As of SCM 5.1, you can customize the GUI title for your templatescreens. The RF screen manager enables you to specify a function group andGUI title when you create a new display profile or copy an existing one. Forexisting display profiles, you can maintain view /SCWM/V DPRF C directly withtransaction SM30.3.3.2Message HandlingField MSG VIEW in table /SCWM/TDPRF CAT is used to control how themessages are processed.An entry of 0 means that the message is displayed on a separate screen. This isscreen 0002 in function group /SCWM/RF SSCR.An entry of 1 means that the message is displayed on the last line of the samescreen or on the last line of the next screen. The template screen and thetemplate program in which the message is processed must be specified in table/SCWM/TDRPF CAT. In the standard SAP system, the template screen is 0002 intemplate program /SCWM/SAPLRF TMPL (function group /SCWM/RF TMPL).If you want to use your own template dynpro, the message line field must refer tofield /SCWM/S RF SCRELM-MSGTX.The messages are defined at package level and assigned at function group level.As a result, there are two message classes. The standard message class in

package /SCWM/CORE RF EN is /SCWM/RF EN and in package/SCWM/CORE RF DE it is /SCWM/RF DE.If you display the messages on the bottom line, you can easily display themessage on the separate screen using function code FULLMS. To do so, define afunction key (with or without a corresponding pushbutton) and assign the functioncode FULLMS to it. If this function code is triggered, the actual message isdisplayed on message screen 0002. Function code FULLMS is always to beimplemented, although it does not have to be shown in the toolbar. For moreinformation about the function code and function code definitions, see DefineFunction Code Catalog.The framework automatically retrieves all error messages of type E from thecontent provider's function modules. However, it may still be necessary to displaymessages while continuing with the coding in the function module and the stepflow. In this case, you send a message with message type S or I. Note that thistype of message cannot be retrieved due to the technical restrictions of theframework. In this case, you must use method/SCWM/CL RF BLL SRVC MESSAGE. This method registers the message inthe framework and the message is displayed when the screen next changes.Note that only one message can be displayed. If you send more messages, onlythe last message is displayed3.4 Personalization Profile DefinitionYou use the personalization profile to empower customers to change thestandard SAP system. Thanks to the personalization profile, you can supportdifferent user groups working in different menus and, therefore, differentprocesses.The personalization profile for standard transactions is **.You define the main menu entry for the personalization profile.You can maintain the personalization profile in Customizing by choosing DefinePersonalization Profile. The data is stored in table /SCWM/TPRSN PRF.3.5 Define Logical TransactionA logical transaction encapsulates the processed action from beginning to end. Itcould involve screen changes and multiple postings including COMMIT WORK.Logical transactions have no corresponding entries in transaction SE93 and canbe called only from the RF menu or the RF logon step. A logical transaction canalso be called using method /SCWM/CL RF BLL SRVC START LTRANS (forexample, from another logical transaction).

The authority check on object /SCWM/RFLT is also carried out in method/SCWM/CL RF BLL SRVC START LTRANS.For the logical transaction, you define an initial step (see below) or an SAPtransaction. You can also define a step that is processed during recovery.The following naming convention for the first 2 characters should be considered:Initials ProcessAHAdhoc movementsINInquiriesIVPhysical inventoryPAPackingPIPickingPTPutawayQMQuality managementRFRF frameworkRSResource managementSHShipping and loadingSPSpreadingULUnloadingWKIndependent of work process, for example, system-guidedThe reserved logical transaction is RFMAIN. This is the default logical transactionthat is called when you start the RF framework with transaction /SCWM/RFUI.The initial step of RFMAIN is MENU.Logical transactions are stored in table /SCWM/TTRNS CAT.3.6 Assign Text to Logical Transaction and Other ObjectsFor several objects, you can add texts for translation. These texts are storedimplicitly using different Customizing settings for the RF framework.Note that in the case of function codes, the function key (such as F2) is addedautomatically if you assign the function key to the function code in field FNKEY oftable /SCWM/TFCOD PRF. As a result, the remaining available space for the textis less than specified in /SCWM/TDPRF CAT.The length of the fields is defined in the display profile.

3.7 Create Menu ItemYou can define your own menus in transaction /SCWM/RFMENU.You create your menu items for the main menu and then for the submenus.The menu items are stored in table /SCWM/TMENU CAT.3.8 Assign Text to Menu ItemYou assign text to menu items in transaction /SCWM/RFMENU. In the case ofmenu items, the appropriate number is added and so it is not necessary to addthe sequence number. The data is stored in table /SCWM/TOBJ TXT. The lengthof the menu items is defined in the display profile.3.9 Create MenuTransactionsHierarchyIncludingSubmenusandYou create the menu hierarchy in transaction /SCWM/RFMENU.Within the hierarchy, you define whether a logical transaction is triggered (fieldLTRANS) or whether the user jumps to a submenu (field LMENU).We deliver a default menu that contains application 01, presentation profile ****,and personalization profile **. These entries can be maintained only in an SAPsystem. In a customer system, these entries are locked for changes.Note that the standard menu is maintained by a central team.The menu hierarchy is stored in table /SCWM/TMENU HIER.3.10 Define Logical Transaction StepsAny logical transaction consists of at least one step. If possible, steps defined forother logical transactions can be reused. Steps can be executed in thebackground or in the foreground. Each foreground step has a correspondingphysical screen. Steps in the background can be combined.The following naming convention for the first two characters must be considered:Initials ProcessAHAdhoc movementsINInquiriesIVPhysical inventoryPAPacking

PIPickingPTPutawayQMQuality managementRFRF frameworkRSResource managementSHShipping and loadingSPSpreadingULUnloadingWKIndependent of work process, for example, system-guidedReserved steps are RFLOGN, RFMENU, RFLIST, and RFMSG.Steps are stored in table /SCWM/TSTEP CAT.3.11 Define Initial Step for Logical TransactionThe initial step is stored in the logical transaction data in the ISTEP field of table/SCWM/TTRNS CAT.3.12 Define Application Data ContainersApplication data containers transmit data between the steps and from theprogram (content provider) to the screens. Data containers can be structures ortables. These structures or table types must be defined beforehand in the datadictionary.The same data dictionary structure or table type can be defined only once withinan application, for example, function modules, dynpro with structure, or

SAP has developed a new radio frequency (RF) concept. This RF cookbook helps developers to begin working in the RF framework. It answers frequently asked questions and helps to avoid common errors. This RF cookbook also provides some useful tips about the standard layout and screen structure that should be applied in the standard transactions.File Size: 299KBPage Count: 59Explore further[PDF] SAP EWM RF Cookbook - Free Download PDFdlscrib.comEWM RF Cookbook SAP blog of John Kristensenjksap.wordpress.comRF Cookbook - Part I Description - SAP Communityarchive.sap.comRF Cookbook - Part I Descriptiondocshare01.docshare.tipsSAP EWM RF Framework - SlideSharewww.slideshare.netRecommended to you based on what's popular Feedback

Related Documents:

Texts of Wow Rosh Hashana II 5780 - Congregation Shearith Israel, Atlanta Georgia Wow ׳ג ׳א:׳א תישארב (א) ׃ץרֶָֽאָּהָּ תאֵֵ֥וְּ םִימִַׁ֖שַָּה תאֵֵ֥ םיקִִ֑לֹאֱ ארָָּ֣ Îָּ תישִִׁ֖ארֵ Îְּ(ב) חַורְָּ֣ו ם

Active Filter Cookbook, CMOS Cookbook, TTL Cook book, RTL Cookbook (out of print), TVT Cookbook, Cheap Video Cookbook, Son of Cheap Video, The Hex adecimal Chronicles, The Incredible Secret M

Naked Persian Turkey Burgers The Skinnytaste Cookbook Perfect Poultry 156 6 6 6 Orecchiette with Sausage, Baby Kale, and Bell Pepper The Skinnytaste Cookbook Perfect Poultry 181 11 11 4. RECIPE COOKBOOK CHAPTER PG SP Roasted Poblanos Rellenos with Chicken The Skinnytaste Cookbook Perfect Poultry 173 7 10 5

How To Cook (use this Arduino cookbook) What Is This Cookbook? This Arduino circuits and programming instruction guide is organized into a "cookbook" style layout. The cookbook illustrates how to create and write various arduino based circuits and programs. These instructions are organized into "Recipes" or instruction guides that can be

cookbook. Eternal gratitude is expressed to all who have contributed to this educational cookbook to include urologists, dietitians and staff. A sincere thank you is extended to the seven celebrity chefs who so graciously shared recipes for use in Living Healthy Cookbook with Information about Urologic Cancers. Nutrition and Cancer

Explain: Cookbook vs. Inquiry We gave you a mystery card and the card’s content should have either the characteristics of a cookbook lesson or an inquiry lesson. Our room will be divided in half. The left side of room will be cookbook, and the right side of the room will be inquiry. Your task is to determine which side of

rudimental cookbook method to my madness 3.2 rudimental lynch, mike rudimental cookbook odyssey ii 3.2 rudimental freytag, edward rudimental cookbook pratfalls 3.2 rudimental whitlock, jon rudimental cookbook tuo kaerf 3.2 concert unknown #32 3.05 concert unknown #47 3.05 .

The book has evolved as the textbook for a course taught to a mostly undergraduate audience over a number of years in the Department of Linguistics at UCLA. The course meets in lecture for four hours per week, with a one hour problem-solving session, during a ten-week term. The ideal audience for this book is a student who has studied some linguistics before (and thus has some idea of what .