The screen number of main screen will be determined via screen sequence control in following module: The screen sequence control information is determined in the PAI module of screen 101, which is the initial screen for sales document creation. The screen group will be used to determine the table control tabs and their function codes: The screen groups are hard coded in the form “TAXI_SCREEN_GROUPS_INIT” For example, the table T180 is used to store the screen sequence default value by transaction code. In step 1 the transaction VA01, system will prepare some default value based on transaction code. In the PBO of initial screen the default values are prepared: Technical Detail Screen Number Determination PBO 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”). DEFINE SCREENIE CODEThe function code “UER1” and “UER2” which were assigned in the sales document type will put the default active tab. The column number defines sequence of overview tab. There are following tabs (function codes) with their sequence defined in this table: For example, “U0” represents overview table control. In the table, there are many function codes defined to represent different tabs in the table control: Based on unknown reason, the program ID for table control definition is “SAPMV45A”: This table is used to define tabs in the table control of sales document. To be precise, the sub-screen “4021” represents overview header:Īnd sub-screen “4419” represents item overview tab which was set by default on screen group “USR2”: In the detail view, it is very clear that main screen “4001” has two sub-screens in tab control. Here field “Panel” was defined in table T185 according to previous step, and main screen number “4001” is defined here. This table is used to define the technical detail, such as screen number.īy using the program ID, screen group “U0”, and panel “ERFI” which were determined in the previous step to locate the entry in this table: Subsequent panel: ERFI – this will be used in the next step.Subsequent screen group: U0 (TAXI_TABSTRIP_OVERVIEW).Settings in the detail view represents that the current function and screen group are “USR2” and “A0”. Double click the item to check the detail: The screen sequence group “LL” which was specified in the sales document type is defined here. So in the table T185, the next screen of initial screen is defined below: For example, from the initial screen of sales document, the current screen group is “A0”, and the function code is “UER2”. This table is used to define the paths between current location and next location. Settings in table T185F will be used to control what information is required in table T185. The relevant entry can be found in the table “T185F”: In our example, the default overview screen function code “UER2” was defined in the sales document type. There are following transaction types available: In the same table, the second column defines transaction types. So the ENTER will be registered as a function code in table T185F: For example, generally we will press button ENTER to navigate from initial screen of sales document to the main screen. What kind of function is triggered in the screen will be defined in the table T185F. Now let’s see how function code controls screen sequence in detail. So the program ID “SAPMV45B” will be used to control screen sequence determination: In program logic, the program ID of sequence control is routed to “SAPMV45B” when transaction triggers to the main page of sales document. It is not so difficult to find screen number of VA01 and the relevant program name: This can be done by checking technical detail of any SD transaction (e.g.T-code VA01). Here we need to find out what program ID should be used on this transaction. The transaction code “VFBS” is used to control the screen determination for sales document. How are those settings functioning in controlling user interface can be found several tables which are defined in transaction code “VFBS”. 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”. Sales Document Typeįirst of all, the screen sequence group as well as overview screen function code are defined in the sales document type: Let’s go to system to explore how screen sequence control works. The various user interface components are controlled by the function codes which are defined in the screen sequence group. The user interface picks up different sub-screens to work with different business processes. SAP SD provides very dynamic approach to determine the sales document screen sequence.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |