Neler Yeni
Hos Geldiniz,

SAPOfis Türkiye üzerinde yer alan içeriklere erişim sağlayabilmek, projelerinizde karşılaştığınız sorunlara birlikte çözüm üretebilmek adına üye olunuz. Unutmayalım ki, bilgi paylaşıldıkça değer kazanır.

  • Bu site çerezler kullanır. Bu siteyi kullanmaya devam ederek çerez kullanımımızı kabul etmiş olursunuz. Daha fazla bilgi edin.

SAP BLOG Sales Document Screen Sequence Control

SAP Blog

Kayıtlı Üye
Katılım
22 Ara 2017
Mesajlar
193
Beğeniler
0
Puanları
6
#1
Overview


SAP SD provides very dynamic approach to determine the sales document screen sequence. The user interface picks up different sub-screens to work with different business processes. The various user interface components are controlled by the function codes which are defined in the screen sequence group.

Let’s go to system to explore how screen sequence control works.

Sales Document Type


First of all, the screen sequence group as well as overview screen function code are defined in the sales document type:

so_type.jpg

In this example, the screen sequence group “LL” is defined for sales document type “LZ”, and the overview screen function code is defined as “UER2”.

How are those settings functioning in controlling user interface can be found several tables which are defined in transaction code “VFBS”.

Screen Sequence Control


The transaction code “VFBS” is used to control the screen determination for sales document.

tcode_VFBS.jpg

Here we need to find out what program ID should be used on this transaction. This can be done by checking technical detail of any SD transaction (e.g.T-code VA01). It is not so difficult to find screen number of VA01 and the relevant program name:

techincal_info_va01.jpg

In program logic, the program ID of sequence control is routed to “SAPMV45B” when transaction triggers to the main page of sales document.

program_screen_101.jpg

So the program ID “SAPMV45B” will be used to control screen sequence determination:

VFBS_init.jpg

Now let’s see how function code controls screen sequence in detail.

T185F


What kind of function is triggered in the screen will be defined in the table T185F. For example, generally we will press button ENTER to navigate from initial screen of sales document to the main screen. So the ENTER will be registered as a function code in table T185F:

t185f_overview.jpg

In the same table, the second column defines transaction types. There are following transaction types available:

transaction_types.jpg

In our example, the default overview screen function code “UER2” was defined in the sales document type. The relevant entry can be found in the table “T185F”:

t185f_uer2.jpg

Settings in table T185F will be used to control what information is required in table T185.

T185


This table is used to define the paths between current location and next location. For example, from the initial screen of sales document, the current screen group is “A0”, and the function code is “UER2”.

So in the table T185, the next screen of initial screen is defined below:

t185_overview.jpg

The screen sequence group “LL” which was specified in the sales document type is defined here. Double click the item to check the detail:

t185_detail_1.jpg

Settings in the detail view represents that the current function and screen group are “USR2” and “A0”. The next location is defined as:

  • Subsequent screen group: U0 (TAXI_TABSTRIP_OVERVIEW)
  • Subsequent panel: ERFI – this will be used in the next step
  • Function code: ENT1
T185V


This table is used to define the technical detail, such as screen number.

t185v.jpg

By using the program ID, screen group “U0”, and panel “ERFI” which were determined in the previous step to locate the entry in this table:

t185v_overview.jpg

Here field “Panel” was defined in table T185 according to previous step, and main screen number “4001” is defined here.

Double click the item to go to detail:

t185v_detail.jpg

In the detail view, it is very clear that main screen “4001” has two sub-screens in tab control. To be precise, the sub-screen “4021” represents overview header:

screen_4021.png

And sub-screen “4419” represents item overview tab which was set by default on screen group “USR2”:

screen_4419.png

TAXITABS


This table is used to define tabs in the table control of sales document. Based on unknown reason, the program ID for table control definition is “SAPMV45A”:

taxitabs.jpg

In the table, there are many function codes defined to represent different tabs in the table control:

tab_control.jpg

The screen group defines tab control. For example, “U0” represents overview table control.

There are following tabs (function codes) with their sequence defined in this table:

tab_sequence.jpg

The column number defines sequence of overview tab. The function code “UER1” and “UER2” which were assigned in the sales document type will put the default active tab. For example, the first tab “Sales” is set as default tab if creating sales order (document type “OR”) and the tab “Item overview” is set as default tab when creating scheduling agreement (document type “LZ”).

Technical Detail

Screen Number Determination

PBO


In the PBO of initial screen the default values are prepared:

101_pbo.jpg

In step 1 the transaction VA01, system will prepare some default value based on transaction code. For example, the table T180 is used to store the screen sequence default value by transaction code.

The screen groups are hard coded in the form “TAXI_SCREEN_GROUPS_INIT”

screen_group_init.jpg

The screen group will be used to determine the table control tabs and their function codes:

screen_group_hardcode.jpg

PAI


The screen sequence control information is determined in the PAI module of screen 101, which is the initial screen for sales document creation.

101_pai.jpg

The screen number of main screen will be determined via screen sequence control in following module:

101_fcode.jpg

In above modules, following function modules are called:

  • FUNCTION_EXECUTE
  • SCREEN_SEQUENCE_CONTROL

pai_screen_control.jpg

Tab Control Determination


The tabs of the tab control are determined in the PBO of main screen of sales document. For example, assume the main screen of sales document is 4001. In its PBO there are following steps:

tab_control_steps.jpg

Step 1


Initialize the main screen and deactivate all unnecessary function codes.

step1.jpg

The first form is used to determine the text (e.g. title) based on transaction group (e.g. order, inquiry, agreement, etc.)

The second one will filter out those unnecessary function codes.

Step 2


Following function modules are triggered to build up table control on the main screen by default:

  • TAXI_CREATE_CAPTIONS: determine the captions on each tab
  • TAXI_INITIALIZE_CARRIERSCREEN: hide unmarked tabs
  • GET_HANDLE_SD_TAB_CUST_H: handle the custom tab settings for sales document header
  • GET_HANDLE_SD_TAB_CUST_I: handle the custom tab settings for sales document item
  • TAXI_ACTIVATE_TAB: it is used to determine the default active tab by function code
Step 3 and Step 4


Call header sub-screen and call body sub-screen.



More investigation will be shared later.

Okumaya devam et...
 

Benzer Konular