User Exit - SAP WM

Use
User exits offer you the option of enhancing the existing functions according to your personal requirements.
Features
The following user exits are available:

  • User Exit Screens
  • Verification with User Exit
  • Sorting Using the User Exit
  • Printing Using the User Exit
  • Deactivating Function Codes with the User Exit

User Exit Screens
Use
The RF solution supports the two screen formats (8x40/16x20) that are offered by most manufacturers of RF devices. The user exit function enables you to display other fields, according to your particular requirements, and also to implement other screen formats.

Features
Fields
You can add fields that are available through standard transactions to the existing screens. Currently, these fields can only be used for display purposes. Also, you can eliminate fields, which are part of the RF solution, from the display.

Changing the Screen Format
The RF transactions use logical screen numbers. User exit screens are built upon existing screens, but have a separate ID (physical screen number). This physical screen number is assigned to a logical screen and then implemented for users who are assigned to the same user exit class. User exit screens are maintained in a separate user screen library. The templates have been defined as part of the RF screen management environment in order to help the user with the development and logic of the specific screens. These screens are called "dummy" screens.

Changing the Screen Layout on Runtime
To change the screen layout on runtime, use the following screen layout modules:

  • MODULE DISABLE_PB
  • MODULE SPECIAL_FIELD_OUTPUT
  • MODULE SET_CURSOR

Screen Selection in RF
The screens in the radio frequency transactions are divided into two main groups: Source information screens and destination information screens. In each group, the screens are chosen dynamically, according to transfer order properties, such as activity and storage unit management.

For example, if the transfer order does not contain a storage unit number because the material will be put away into a non-storage unit-managed storage type, source information screen number 212 appears. If the material will be put away into a storage unit-managed storage type, screen number 202 appears as the source information screen and 302 as the destination information screen. Special screens exist for the confirmation of transfer orders with bulk storage types, because the actual storage unit number must be scanned.

Screen numbers for the different activities and properties

Screen numbers for the different activities and properties

Defining a Screen
Use
You can either create a new screen or copy an existing one.
Procedure

  1. To create a new screen, enter the program SAPLXLRF or SAPLXLHU in the screen painter. To find out which program you have to enter, do the following:
    • In the screen painter, enter the program SAPLLMOB and the dummy screen number 1xxx. The Flow Logic of the dummy screen contains a call for the customer-subscreen in which the respective program (SAPLXLRF or SAPLXLHU) is included.
  2. To copy a screen, proceed as follows:
    • Enter the program SAPLLMOB and a screen number.
    • Choose Element List and delete the last field, the "OK_CODE".
    • Choose Subscreen in the tab page Attributes in Screen type.
    • Save your data entries under the relevant development class in the customer's namespace.

Assigning a Screen

  1. In Customizing for Mobile Data Entry in Logistics Execution, create a new table record under Define Screen Management.This record assigns the new user screen to a logical screen for this user exit version within a program module.
  2. Use the CMOD transaction to create a project for this screen. SAP recommends that you start the project name with one of the letters X, Y, or Z, followed by four digits that represent the screen number used.
  3. Insert a descriptive text after you have created the project.
  4. Choose Continue. A dialog box appears.
  5. Choose Local Object and save your entries.
  6. Choose Enhancement. A new screen appears. Enter the enhancement name MWMRFxxx and save your entries. Make sure that you include for xxx the last three digits of the logical screen number.
  7. Activate the project using the transaction CMOD.
  8. In the screen painter, enter the program SAPLLMOB and the dummy screen number 1xxx. From the Flow Logic tab of the dummy screen, call up the module DATA_TO_EXIT0xxx, open the customer function, and go to Include. Do the same for the module DATA_FROM_EXIT0xxx.
  9. Enter the data that is entered into the screen through the function (watch out for the import parameters). You need to execute the same step for the structure of the data that returns from the screen through the function (watch out for the export parameters).
  10. Here you can add up to four verification fields by filling in the table O_VERIFICATION_ERRORS (internal table). You can define up to four fields on the screen that you can check any way you wish. If an error occurs during the check, you should update this internal table with the appropriate field name. The function reports a known error message: "Error in field verification"..

Use of the User Exit

  • In the screen management for Customizing, you should enter a new entry with a physical screen number that is assigned to a logical screen number.
  • In the screen format variant, enter a number other than 0. This means that you have defined a separate screen.
  • At the same time, the administrator should enter a definition in the separate data table stating that the user is assigned to a screen format variant (user exit).
  • During logon, the user should enter his or her own screen format variant.

Verification with User Exit
Use
The radio frequency solution supports four types of verification: Storage bin, storage unit number, material, and quantity. To be able to verify other fields, the system also provides a general verification entry. You can use this verification to meet individual requirements, such as verification of batches.

Procedure

  1. Create a new screen.
  2. In the screen painter, enter the program SAPLLMOB and one of the dummy screen numbers 1xxx.
  3. Enter the module DATA_FROM_EXIT0xxx on the Flow Logic tab of the dummy screen, open the customer function, and access the Include.
  4. Here you can enter up to four verification fields by filling in the table O_VERIFICATION_ERRORS (internal table). You can define up to four fields on the screen that you can program according to your specific requirements.
  5. If an error is found in the verification checks, the system requires the user to update this internal table with the field names. The following error message appears: "Error in field verification" (which the user updated in the internal table).

Sorting Using the User Exit
Use
System-guided transfer order processing in the RF solution supports two different sort possibilities for the transfer orders:

  1. Sorting without defining a user exit
  2. Sorting by different sort criteria with the help of a user exit

Both options can be used in the following transactions, but we strongly recommend that you implement the user exit only in the interleaving transactions. In the other system-guided transactions, the sorting defined in the user exit is not reflected properly in the RF monitor

  • Putaway system-guided: LM04 (Report: RLMOB005)
  • Picking system-guided: LM07 (RLMOB008)
  • Pick and Pack system-guided: LM45 (RLMOB045)
  • Posting change: LM11 (RLMOB010)
  • Interleaving system-guided: LM57 (RLMOB005, RLMOB008)
  • Interleaving by storage unit: LM56 (RLMOB001, RLMOB008)

Procedure: Sorting Without a User Exit
In the system-guided RF transactions, if you do not define a user exit, the system selects your transfer orders by priority and then by creation date and time.

Procedure: Sorting by Different Sort Criteria with the Help of a
User Exit
Use the user exit function EXIT_SAPLLMOB_061:

  1. If you use this function for interleaving, the following parameters will be imported:
    • Last storage bin
    • Queue
    • Activity

To use the user exit, use the enhancement name MWMRFSSG. As an additional selection criterion, you want the system to select a transfer order for picking with a source storage bin close to the destination storage bin of the transfer order for putaway executed before.

If you do not define your own user exit in this function, the system selects the transfer order for picking only according to the queue assignment and the standard sorting mentioned above.

  1. If you use this function for any other system-guided transaction, only the parameter for the activity will be imported. The function returns the transfer order number.

Printing Using the User Exit
Use
The radio frequency solution supports the printing of different label types, for example, shipping labels and handling unit labels. You can use the print pushbuttons in the respective transaction by creating your own user exit function module, which is called from the LE_MOB_PRINT function module.

Prerequisites
To indicate that you created your own user exit in order to print labels, change the status field in the function LE_MOB_PRINT.

Procedure

  1. Choose the function LE_MOB_PRINT.
  2. Change the status field as mentioned above. If the user exit is not activated, you receive an error message upon using the print pushbuttons.
  3. Two parameters, the ok_code and the parameter of the object to be printed, will be passed to the user exit function. The ok_code defines which pushbutton has been selected and the second parameter contains the object ID.

Deactivating Function Codes with the User Exit
Use
Using this user exit EXIT_SAPLLMOB_222, you can deactivate function codes in the delivery header screen.
Procedure
To deactivate individual function codes, activate the user exit using the enhancement name MWMRFCOD and clear the output parameter O_ENABLED.
Result
The respective button still appears on the delivery header screen, but it is deactivated.

Adding Function Keys to Screens
Use
You can add function keys to the user exit screens of the following screens:

Adding Function Keys to Screens

Procedure
On those screens you have the option to use one more function key. In the respective user exit screen, you can display the pushbutton and assign to it the function code USRF in the GUI status, which corresponds to the function key Shift+F1. Define the functionality of the function key in the user exit function EXIT_SAPLLMOB_077.


All rights reserved © 2018 Wisdom IT Services India Pvt. Ltd DMCA.com Protection Status

SAP WM Topics