Professional Documents
Culture Documents
Products
Products Industries
Industries Support
Support Training
Training Community
Community Developer
Developer Partner
Partner
About
About
Home / Community / Blogs + Actions
Yong Zhao
more by this author
share
0 share tweet share
Follow RSS
Overview
SAP SD provides very dynamic approach to determine the sales document
screen sequence. The user interface picks up di erent sub-screens to work
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 1/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
In this example, the screen sequence group “LL” is de ned for sales
document type “LZ”, and the overview screen function code is de ned as
“UER2”.
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 2/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 3/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 4/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
Now let’s see how function code controls screen sequence in detail.
T185F
What kind of function is triggered in the screen will be de ned 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:
In the same table, the second column de nes transaction types. There are
following transaction types available:
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 5/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
In our example, the default overview screen function code “UER2” was
de ned in the sales document type. The relevant entry can be found in the
table “T185F”:
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 6/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
T185
This table is used to de ne 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 de ned below:
The screen sequence group “LL” which was speci ed in the sales document
type is de ned here. Double click the item to check the detail:
Settings in the detail view represents that the current function and screen
group are “USR2” and “A0”. The next location is de ned as:
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 7/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
T185V
This table is used to de ne the technical detail, such as screen number.
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:
Here eld “Panel” was de ned in table T185 according to previous step, and
main screen number “4001” is de ned here.
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 8/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
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:
And sub-screen “4419” represents item overview tab which was set by
default on screen group “USR2”:
TAXITABS
This table is used to de ne tabs in the table control of sales document.
Based on unknown reason, the program ID for table control de nition is
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 9/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
“SAPMV45A”:
In the table, there are many function codes de ned to represent di erent
tabs in the table control:
The screen group de nes tab control. For example, “U0” represents
overview table control.
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 10/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
There are following tabs (function codes) with their sequence de ned in
this table:
The column number de nes 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 rst 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:
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 11/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
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 group will be used to determine the table control tabs and their
function codes:
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 12/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
PAI
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 number of main screen will be determined via screen sequence
control in following module:
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 13/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
FUNCTION_EXECUTE
SCREEN_SEQUENCE_CONTROL
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 14/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
Step 1
Initialize the main screen and deactivate all unnecessary function codes.
The rst form is used to determine the text (e.g. title) based on transaction
group (e.g. order, inquiry, agreement, etc.)
The second one will lter out those unnecessary function codes.
Step 2
Following function modules are triggered to build up table control on the
main screen by default:
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 15/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
Alert Moderator
7 Comments
You must be Logged on to comment or reply to a post.
Michelle Crapo
Great Blog – I’ve changed the screen sequence before. For me – it didn’t work out.
There are just so many dependencies. Perhaps I’ll be able to do that in the future on
higher levels of SAP.
Michelle
Thanks Michelle!
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 16/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
You are right. When I was debugging SD application, there were so many
enhancement points and exits which introduced very complex
dependency. I had to open Google translator to translate comments
from Germany to English. Indeed, it was painful, but worthwhile.
Best regards,
Yong
Paul Hardy
However I have found the e ort involved in “wrapping” sales order creation in your
own Z code (be it DYNPPRO in the GUI or more recently UI5), and then calling a
BAPI, is far less than battling with the standard SAP code. And it is a battle.
The greatest irony, is that SAP decided to write ME21N in all object orientated code,
and they missed the point totally, the point being that well written OO code should be
easier to understand, so ME21N is far more di cult to debug than VA01.
In any event the problem with standard SAP screens is that they had to be all things
to all people, which is why there were so many tabs all lled with hundreds of elds,
and each company only need about six elds.
So it does not matter what order those screens appear in, it is still agony. That is why
you need some sort of wrapper to radically simplify matters for any given
organisation.
Cheersy Cheers
Paul
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 17/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
Hi Paul,
I was curious about how screen sequence group setting was working in
the sales document type con guration, so I started to investigate screen
sequence controls.
best regards,
Yong
Ged Hurst
Hi Ged,
Yes. You are correct. I think modify T185 series table is not
recommended. This is why there is no o cial document available about
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 18/19
8/14/2018 Sales Document Screen Sequence Control | SAP Blogs
best regards,
Yong
G Lakshmipathi
https://blogs.sap.com/2018/01/12/sales-document-screen-sequence-control/ 19/19