HOW TO ENHANCE SAP RF SCREENS | ABAP SCREEN ...
https://www.google.com/search?q=ewm+rf+screen&sca_esv=575557852&sxsrf=AM9HkKlrnkqFdPZY72IIEyeEJ_AUNirOw%3A1697960038414&source=hp&ei=ZtA0Zd34Fsi54EPjcGU4AY&iflsig=AO6bgOgAAAAAZTTedvVanBvg8_61hjNr8-x1gXgQ16W&oq=EWM+RF&gs_lp=Egdnd3Mtd2l6IgZFV00gUkYqAggGMgQQIxgnMggQABjLARiABDIIEAAYywEYgA
QyCBAAGMsBGIAEMggQABjLARiABDIIEAAYywEYgAQyCBAAGMsBGIAEMggQABjLARiABDIIEAAYywEYgAQy
CBAAGMsBGIAESLtYUABYph5wAHgAkAEAmAFCoAHmAqoBATa4AQHIAQD4AQHCAgsQLhiABBixAxiDAcIC
ERAuGIAEGLEDGIMBGMcBGNEDwgILEAAYigUYsQMYgwHCAgUQABiABMICCBAAGIAEGLEDwgIOEC4YywE
YgAQYxwEY0QM&sclient=gws-wiz#fpstate=ive&vld=cid:601ba289,vid:9hBmW0GQVEM,st:0
Enhancement of RF Screens – LMOB
51124,094
There are various links in SCN, which guide us on the use of RF programming and the steps to follow
while developing a custom program. But what if a standard screen from LMOB function group needs to
be modified??
Here is the complete steps, which can be referred to add the customer fields to standard RF screen
belongs to LMOB function group.

Get the Actual Screen Number based on Logical Screen Number in SPRO -> Logistic Execution ->
Mobile Data Entry -> Define Screen Management

For Example, to enhance the RF screen of Pick and Pack (LM45 Transaction) the Logical Screen for
Pick and Pack is ‘0650’. In the Define Screen Management (defined above) the actual screen number
in Narrow Format (16X20) is ‘2650’ and Large Format(8X40) is ‘0650’

In the LMOB function group for every logical screen a dummy screen is available which contains the
screen exit. The dummy screens can be identified as ‘1(logical screen). So for logical screen ‘650’ the
dummy screen is ‘1650’.
The program mentioned in the green color is nothing but the user screen i.e the screen which has to be
created in that program as a subscreen.

Now copy the narrow format screen ‘2650’ in the program ‘SAPLXLHU’ as custom screen ‘9650’
(Follow the naming standards of custom screen number 9(logical screen)).

In the function group XLHU, screen 9650 gets created. Now remove the OK_CODE from ‘Element list’
tab and screen type is changed to ‘Subscreen’

Add the additional fields in the screen layout and populate those fields in PBO or get the values in PAI
after a certain user action by capturing the SY-UCOMM.

Now the subscreen ‘9650’ has to be embedded in the dummy screen 1650. To do this create a CMOD
project and assign the enhancement component MWMRF650
Note: The enhancement component can be identified by using the F4 help in SMOD transaction. Use the
package name as search criteria

Activate the CMOD project. The screen exit 1650 gets implemented.

Now the custom screen ‘9650’ is configured in the Screen Management (SPRO) for the narrow format
(16X20)

To run the RF transactions, the user must have a screen format configured in the LRFMD transaction.
Note: The Variant in the Screen Management and in the LRFMD transaction should be same.

Run the transaction LM45

If the user doesn’t want the additional fields then remove the variant in LRFMD transaction

Now run the transaction LM45
FollowLikeRSS Feed
Alert Moderator
Assigned Tags

ABAP Development
Similar Blog Posts

Simulation of ITSMobile Applications from Chrome browser
By Suman PradhanFeb 06, 2020

How To Add Batch Verification To WM Mobil Screen With Enter Definition
By Beyhan MEYRALIAug 30, 2022

Using Custom Display Profile for SAP EWM RF screens
By Vishal KumarOct 31, 2022
Related Questions

Add a custom transaction in function group LMOB
By Ankit MahatoNov 26, 2019

Add 2 custom screens to RF tcode lm06- GI Picking
By Swarnadeepta PadhiFeb 19, 2020

Add batch verification field on RF Screen(LM06)
By Former MemberJan 09, 2014
5 Comments
You must be Logged on to comment or reply to a post.
Alejandro Bindi
January 21, 2016 at 3:16 pm
Thank you very much for this!!
I have to modify the standard LM45 as well so this post is invaluable, there's not much info around
about this process, even the SAP help I've found is not detailed at all.
I just have one question, I see the fields you added are ready for input (as I need), but the SAP help
says "You can add fields that are available through standard transactions to the existing screens.
Currently, these fields can only be used for display purposes.".
Can you confirm there's no problem in adding custom editable fields?
Again, many thanks!
 Like 0
 Share
Rakshith Gore
Blog Post Author
January 21, 2016 at 4:11 pm
Basically, when you implement the exits and do the configuration like setting the variant to '1' in
screen management for your screen means you have defined a customer screen, not a standard
one.
So you can add the custom editable fields in your screen, there wont be any problems.
 Like 0
 Share
Alejandro Bindi
January 21, 2016 at 5:20 pm
Excellent. I will try this approach.
Thanks!
 Like 0
 Share