Hierarchy
⤷ LE-TRM (Application Component) Task & Resource Management
⤷ LMBP (Package) Mobile Presentation
IMG Activity
ID | SIMG_LMBP003 | Define Control Screen Layout |
Transaction Code | S_DTR_07000025 | S_DTR_07000025 |
Created on | 20010211 | |
Customizing Attributes | SIMG_LMBP003 | Define Function Code and Verification Profiles |
Customizing Activity | SIMG_LMBP003 | Define Function Code and Verification Profiles |
Document
Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
Document Name | SIMG_LMBP003 |
Use
In this IMG activity, you can personalize the control screen layout by doing any of the following:
- Mapping your own user-defined processes to activities
- Defining your own function code profiles
- Defining your own pushbutton text
- Defining your own verification profiles
You may want to map external processes to activities if you want greater flexibility when defining function code profiles and verification profiles.
If you map a specific process to a specific activity and then define function code/verification profiles for the specific process, the profiles will apply to all screens related to tasks of the specific activity type.
Requirements
- If you want to enable bar code scanning, you have configured the settings for the use of bar codes in the following Mobile Data Entry IMG activities:
- You have already defined personalization profiles in IMG activity Personalize User Data.
Standard settings
Standard external process-activity mapping, function code profiles and pushbutton texts are provided with the standard system.
Recommendation
Activities
Mapping External Process to Activities
- Choose Define External Process.
- Enter the site number.
- In the Act field, enter the identifier for an activity defined in the activity catalog (IMG activity General Settings for TRM).
- Choose the process to which you want to map the activity.
Defining New Function Code Profiles
- Choose Define Function Code Profile.
- Enter the site number.
- In the relevant fields, enter the transaction step, internal process, personalization and process for which you are defining the function code profile.
- In the Function Code field, choose the function code of the transaction step for which you are defining a profile.
- In the Pushbutton field, assign a pushbutton to the function code.
- In the Func.Key field, assign a function key to the function code.
- If you want a message to be displayed at the particular transaction step, do the following:
- In the Message Class field, enter the message class.
- If you want to display a query message, enter the message number in the Query Msg field.
- If you want to display a confirmation message, enter the message number in the Conf.Msg field.
- If you want to disable the function code and prevent the pushbutton from appearing at the transaction step, select Dis.F.Code.
Personalizing Pushbutton Texts
- Choose Define Pushbutton Text.
- In the Lang. field, enter the language identifier.
- Enter the site number.
- For each function code, enter the length of the pushbutton text and the text to be displayed on the corresponding pushbutton.
Defining New Verification Profiles
- Choose Define Verification Profiles.
- Enter the site number.
- In the relevant fields, enter the transaction step, personalization and process for which you are defining the verification profile.
- In the Verification field field, enter the verification field.
- In the Verified field field, enter the field to be verified.
- In the Methd field, choose a bar code transaction method.
- If you want to disable the verification field, select Disable.
Further notes
Example
Example 1: Define a verification profile involving the verification of a destination handling unit
Prepare your function group for creating your sub-screens
- Choose transaction SE80.
- Display package LMBP.
- Open the sub-tree of function groups.
- Choose function group LMOP.
- Right-click and choose Copy.
- Enter the name of function group ZTS2 and enter the necessary parameters.
- After you copy the function group, copy the following function modules:
- LMOP_SUBSCREEN_DATA_SET to ZTS2_SUBSCREEN_DATA_SET
- LMOP_OK_CODE_SET to ZTS2_OK_CODE_SET
- LMOP_PARAMS_SET to ZTS2_PARAMS_SET
- Choose transaction SE37.
- Display an object (e.g function module LTS1_SUBSCREEN_DATA_SET).
- Activate the object.
- Repeat steps 9 -10 for each object relevant to the new function group.
Paint the verification field on the Source screen
- Choose transaction SE51
- Enter program name SAPLZTS2 and screen number 3110.
- Select the sub-object Layout and choose Change.
- Prepare a place for the new verification field. You can do this in a number of ways. For example, you could decrease the length of the handling unit titles, changing their modification property from 2 to 1 and move handling unit fields to the left.
- Place the cursor on the desired position and choose Edit -> Create Element -> Input/Output field.
- Enter the following element attributes:
- Name: RLMBP-BRCD3
- Groups (3): 002
- DefLg: 100
- VisLgth: 1
- Select the following checkboxes:
- Scrollbl
- Frm Dict (Modific.)
- Input field
- Invisible
- Choose Transfer and activate the sub-screen.
Define the verification profile
- In this IMG activity, choose Define Verification Profiles.
- For your site, add a new record with the following values:
Step Personal. Process Verif. fld Verified f Meth
Source 02 Any process RLMBP-BRCD3 LMBP_MOVE-HUNMD Default
Define the physical screen
- Go back and choose Presentation Management -> Define Display Profiles and Physical Screens -> Physical Screen.
- For your site, add a new record with the following values:
Step D. prof. Seq. screen no. Progr. name Screen number
Source ** 1 SAPLZTS2 3110
- If you choose System-Guided Pick and Pack from the RF menu, the Destination HU field is displayed and open for user input. HU verification is eliminated and changed by the validation of the input handling unit number. The verification field is not displayed.
- If you choose to put away a full pallet, the Destination HU field is displayed but closed for user input. The verification field is displayed and open for user input.
- If you choose to put away a mixed pallet, the Destination HU field and verification fields are not displayed.
Example 2: Define function code profiles so that you receive confirmation messages at the source and destination steps, you receive a warning message when choosing Skip at the source step, and the Back pushbutton does not appear at the destination step
- Using transaction SE91, create message class ZTST with two messages:
- 001 - Task confirmed
- 002 - This task is not suitable
- In this IMG activity, choose Define Function Code Profile.
- For your site, add the following records. Each record should also have:
- Int proc: Def. process
- Personal.: 02
- Process: Any process
Step Function code Pushbutton Func. Key Mess Class Query msg Conf msg Dis FCode
Source Save Pushbutton 1 Function key 1 ZTST 001
Destination Save Pushbutton 1 Function key 1 ZTST 001
Source Skip task Pushbutton 12 Function key 5 ZTST 002
Destination Go back Pushbutton 3 Function key 3 x
Business Attributes
ASAP Roadmap ID | 203 | Establish Master Data |
Mandatory / Optional | 1 | Mandatory activity |
Critical / Non-Critical | 1 | Critical |
Country-Dependency | A | Valid for all countries |
Assigned Application Components
Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
---|---|---|---|---|
SIMG | SIMG_LMBP003 | 0 | AL00000041 | Task & Resource Management |
Maintenance Objects
Maintenance object type | C | Customizing Object |
Assigned objects | ||||||
---|---|---|---|---|---|---|
Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
V_LEXTP | V - View | SM30 | Define External Process | |||
V_LFCPR | V - View | SM30 | Define Function Code Profile | |||
V_LFCTX | V - View | SM30 | Define Pushbutton Text | |||
V_LIVPR | V - View | SM30 | Define Verification Profiles |
History
Last changed by/on | SAP | 20020425 |
SAP Release Created in | 46C |