Registration

Dear SAP Community Member,
In order to fully benefit from what the SAP Community has to offer, please register at:
http://scn.sap.com
Thank you,
The SAP Community team.
Skip to end of metadata
Go to start of metadata

SAP Screen Personas


 

Tab Merging in Header and Item Detail Screens of VA0* Transactions


SAP SCREEN PERSONAS KNOWLEDGE BASE - by Regina Sheynblat , Sebastian Steinhauer , Kranthi Kumar Muppala

Purpose

This article shows how tab merging can be done in the header and item detail screens of transactions like VA01, VA02 etc. This is not indented as a guide for tab merging in general as it targets a specific case where a tab is shared across multiple screens.

IMPORTANT: This article is only applicable if there is a need to customize the 'Contract Data' tab of the header and item detail screens.

Overview

The header and item detail screens of VA0* transactions are complex in that the program name and screen number vary depending on the highlighted tab. To resolve such variations in a screen, SAP Screen Personas supports screen ID and control ID overwrite rules as described in the [Screen and Control Overwrite Entries] KB article. SAP delivers overwrite rules for these screens and it is possible to customize the header and item detail screens. It is also possible to merge tab contents in both of these screens with one exception - the ‘Contract Data’ tab. The ‘Contract Data’ tab is special as it is shared between the header and item detail screens. This interrupts the tab merging routine and will result in errors or screens in an inconsistent state. In the following sections, a sample flavor will be used as a basis to illustrate the problem and a possible solution.

Target Flavor Design

Let's take an example where the target screen designs for the header and item details screen must look like the screenshots below.

The screen ID overwrite rules currently delivered by SAP make it possible to customize the header details and item details screens as two different screens (4444 and 5555). However, this makes it impossible to design the flavors as illustrated above as the 'Contract Data' tab with program name 'SAPLV45W' and '5555' will always show the customizing made to the item details screen (5555). When the user (or tab merging routine) switches to the 'Contract Data' tab in the header details screen, SAP Screen Personas will apply the changes made to the item details screen. This results in an error in the editor and no further customization can be done on the 'Contract Data' tab.

Here's a screenshot of the current SAP delivered screen ID overwrite rules for the VA01 transaction.

Solution

The following solution is only applicable if there is a requirement to tab merge contents from the 'Contract Data' tab.

Ensure that the following SAP Note is implemented if applicable:

SAP Note: 2255677 - Precedence of Non-SAP Shipped Overwrite Entries over SAP shipped Overwrite Entries

The following new screen ID overwrite rules need to be added:

App IDABAP Program NameOld Screen NumberNew Screen Number
VA01SAPMV45A40025555
VA01SAPMV45A50025555
VA01SAPLV60F40015555

The new entries can be adding in the /PERSONAS/ADMIN transaction -> Maintain Screen ID Overwrite Entries -> Create a new entry

Here's a screenshot of how the new entries will look like.

 

Adding the above rules will make the header and item details screen to have the same ID (screen number 5555). This will make the customizations made to the header data screen to also show up on the item data screen. In order to customize the header and item data screens individually, two flavors are needed. Here are some steps that can be used to switch between the flavors when the header or item data screen is loaded.

  1. FlavorA (flavor with header data customization)
  2. FlavorB (flavor with item data customization)

In FlavorA, create a script with the following contents and assign it to the OnLoad screen event of the item data screen:

OnLoad Script in FlavorA (Item Data Screen)
// Switch to FlavorB when the item data screen loads. 
// The GUID can be seen in the deep link (click on chain link button on the flavor manager)
session.utils.changeFlavor(<GUID of FlavorB>);

In FlavorB, on the overview screen, create an OnLoad script with the following contents:

OnLoad Script in FlavorB (Overview Screen)
// Switch to FlavorA when the overview screen loads. 
// The GUID can be seen in the deep link (click on chain link button on the flavor manager)
session.utils.changeFlavor(<GUID of FlavorA>);

 

Important Considerations

Adding the new screen ID overwrite rules described in the solution section will make any existing customizations to the header and item details to be nullified or inconsistent. All VA01 flavors with changes to the header and item details screens will need to reviewed/re-done after this change.

The screen overwrite conversion report cannot be executed for the transaction if these entries are added.

Similar overwrite entries can be added to VA02 and VA03 transactions if required.

Related Content

Related Search Terms:

SAP Screen Personas, Overwrite Rules, Screen ID Overwrite Rules, VA0*, Tab Merging

Related SAP Notes/KBAs

Screen and Control ID Overwrite Concept in Personas 3.0

SAP Note: 2051455 - SAP Screen Personas 3.0 : Screen and Control Overwrite Entries

SAP Note: 2255677 - Precedence of Non-SAP Shipped Overwrite Entries over SAP shipped Overwrite Entries