Hierarchy
SAP_BW (Software Component) SAP Business Warehouse⤷
BW-PLA-BPS (Application Component) Business Planning and Simulation⤷
UPWB (Package) Graphic Builder for Planning Applications with BSP
Basic Data
| Data Element | UPWB_Y_PREVDYN |
| Short Description | Ind: Dynamic Preview |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOOLEAN | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
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 | 0 | |
| Medium | 0 | |
| Long | 40 | Quick Preview w/o Generating BSP-App |
| Heading | 0 |
Documentation
Definition
Determines that in the preview, the application is presented so that it corresponds to the current definition of the Web interface. This also applies when no BSP application was yet generated for the interface, or the generated version is obsolete.
The advantage of this setting is that the generation, which often takes a long time, no longer applies. However, if the BSP application should be transported then a generation must take place.
If the Web interface is finally completed, then you must generate the BSP application again.
Technically, the existing BSP application uses SEM_UPWB, which works similar to an interpreter and generates the HTML page from the internal XML display of the respective Web interface. Thus, the BSP application must also have an HTTP entry and be activated (transaction SICF).
Use
Dependencies
Example
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in | 3.1B |
