SAP ABAP IMG Activity CA-NCSCR (Define Screen Templates)

Hierarchy

☛ BBPCRM (Software Component) BBPCRM
   ⤷ CRM (Application Component) Customer Relationship Management
     ⤷ CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages
       ⤷ QI (Package) QM IMG and area menu

IMG Activity

ID	CA-NCSCR	Define Screen Templates
Transaction Code	S_ALR_87100674	(empty)
Created on	19991117
Customizing Attributes	CA-NCSCR	Screen Templates for Claim
Customizing Activity	CA-NCSCR	Screen Templates for Claim

Document

Document Class	SIMG	Hypertext: Object Class - Class to which a document belongs.
Document Name	CA-NCSCR

In this step, you structure the screens you want to use for your notifications.

Requirements

The notification types have already been defined.

Standard settings

Recommendation

Copy the standard settings.

Activities

A Define Screen Areas
You can assign the groups of information contained in the notifications to particular tabstrips and screen areas, and as a result flexibly structure your screen templates. You complete the following tasks in separate views:

1. Define screen areas for the notification header
   Here, you can assign up to 5 of your own screen areas in addition to a screen area based on the origin.
2. Define screen templates for the simplified view
   You can select up to 5 screen areas for the simplified notification transactions. Assign the required screen areas.
3. Define screen templates for the extended view
   For the extended notification transactions, you can define tabstrips and assign screen areas to each tabstrip.
   First, copy the settings from client 000. Make sure that the standard settings for the screen templates are suitable for the notification information and functions required by your company. Optimize the settings for the tabstrips and screen areas. Proceed as follows:
1. Review the tabstrips and screen areas and the fields they contain.
   To do this, you need an example notification for each notification origin, in which you can check the screen areas.
2. Assign the required screen areas to the tabstrips that are available and give these tabstrips suitable names.
   Note: The tabstrip 10\TAB* is at header level, the tabstrip 20\TAB* at item level in the notification.
   Tip: Check the results of the settings immediately in a parallel session using an example notification.
4. Hide the fields you do not require.
   To do this, refer to the section Environment/ Tools / System Modification / Adapt Field Selection.

Note: If you have not defined any screen areas before you create a notification for the relevant notification type, the system searches for a notification type in the standard client 000 with the same notification origin, and uses its screen area settings.
You can also copy this standard setting for the relevant notification type manually into the current client (transaction OIMN).

B Define Initial Screens
You can have the system offer additional creation screens when you access the notification functions, by assigning appropriate function modules and initial screens. The system contains examples of these. You can find a list of these initial screens if you call up the text reference that has been defined for the word initial screens, or use the F1 help (not input help) in the table.

1. Identify for which notification origins and notification types this is necessary. Use the examples that are available or your own program. Note: Structure RQM01 (SE12) contains all fields that can be copied into the notifications in this way.
2. Hide the fields you do not require. Refer to the method in the section Environment / Tools / System Modification / Adapt Field Selection.

C Format Long Texts
You can control the formatting of long texts on the notification screen. If required, the system can:

• Add log lines automatically
• Protect texts from being changed

  For more information, see the online documentation for the relevant view.

  Identify whether you require such functions for specific notification types.

Further notes

Business Attributes

ASAP Roadmap ID	261	Define Screen Control
Mandatory / Optional	2	Optional 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	CA-NCSCR	0	ALR0077563	Claim 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
VC_TQSCR	C - View cluster	SM34	0000000000	☐	☐	Define Screen Areas and Tabs
IMGDUMMY	D - Dummy object	OIMN		☐	☐	Copy Screen Areas from the Standard System
V_TQ80_E	V - View	SM30		☐	☐	Define Initial Screens
V_TQ80_L	V - View	SM30		☐	☐	Format Notification Long Text
SFAC	T - Individual transaction object	OCLM2		☐	☐	Field Selection: General Screens in Claim
SFAC	T - Individual transaction object	OQM2		☐	☐	Field Selection: Initial Screens
SFAC	T - Individual transaction object	OQM3		☐	☐	Field Selection: Reference Object Screens
SFAC	T - Individual transaction object	OQM4		☐	☐	Field Selection: Partner Screens

History

Last changed by/on	SAP	20051005
SAP Release Created in