SAP ABAP Data Element UPARM_Y_EMB_VW_SAVE_AFTER (Save Embedded View Before Exiting)
Hierarchy
☛
BI_CONT (Software Component) Business Intelligence Content
⤷
BW-BCT-PLA-RAP (Application Component) Retail Assortment Planning
⤷
UPARM (Package) Retail MAP Master Data Maintenance
BI_CONT (Software Component) Business Intelligence Content⤷
BW-BCT-PLA-RAP (Application Component) Retail Assortment Planning⤷
UPARM (Package) Retail MAP Master Data Maintenance
Basic Data
| Data Element | UPARM_Y_EMB_VW_SAVE_AFTER |
| Short Description | Save Embedded View Before Exiting |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | BOOLE | |
| 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 | 10 | Save View |
| Medium | 15 | SaveBeforeExit |
| Long | 23 | Save View Before Exit |
| Heading | 23 | Save View Before Exit |
Documentation
Definition
When checked, this flag displays a dialog box to the user asking to save any modification before exiting the current embedded view. After the save action is completed, all embedded views reload their results from the database to record modifications. If user does not save, modifications are lost and results are not reloaded.
Use
Dependencies
Example
Consider these views embedded in a multi-view: View 1, View 2 and View 3. View 2 and 3 are not related, but they both use InfoObjects of View 1. You do not have to save when navigating from View 2 to View 3. However, you do need to save when exiting View 1 to refresh views 2 and 3.
History
| Last changed by/on | SAP | 20141031 |
| SAP Release Created in | 705 |
