Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
AP-MD-BP (Application Component) SAP Business Partner⤷
BUPA (Package) SAP Business Partner
Basic Data
| Data Element | BU_VARTP |
| Short Description | BDT: Screen Sequence Category |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BU_VARTP | |
| Data Type | CHAR | Character String |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 6 | |
| Value Table | TBZ3L |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | ||
| Default Component name | ||
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | ScrSeqCat |
| Medium | 15 | Scrn.seq.cat. |
| Long | 20 | Screen sequence cat. |
| Heading | 4 | Cat |
Documentation
Definition
A screen sequence category is a level in a maintenance transaction at which a screen sequence is presented. Multiple screen sequences can be assigned to a screen sequence category, and one of the screen sequences is selected as being the standard for this screen sequence category.
After the initial screen, BDT Classic automatically calls the main screen sequence category. The application programmer is then able to call other screen sequences that may be required, for example, because of GUI functions.
When working with the BDT, you should always call a screen sequence category, and never a screen sequence. The reason for this is that customers can change screen sequences by drag & drop using the Visual Configuration Tool. These customer screen sequences are saved as a separate screen sequence with an own ID, and assigned to the same screen sequence category. When the screen sequence category is called, the BDT automatically ensures that the customer screen sequence is displayed, if such a screen sequence exists.
You can call a screen sequence category by
- entering the screen sequence category in a GUI function
- calling function module BUS_SCREEN_CALL and transferring the screen sequence category.
Example
The screen sequence categories in SAP Business Partner include
- main screen sequence category
- address overview
- address details
Several screen sequences are assigned to the main screen sequence category, because the screen sequence can vary with each BP role. You have the option of defining a screen sequence for each BP role (the BDT term for this is object part).
Conversely, only one screen sequence with one screen is assigned to the other two screen sequence categories. The address overview screen sequence category is called as soon as you select the GUI function bearing the same name. The screen sequence category is stored in this GUI function.
History
| Last changed by/on | SAP | 20010216 |
| SAP Release Created in |
