SAP ABAP Data Element UPARM_Y_EMB_VW_SAVE_BEFORE (Save Embedded View Before Accessing Current View)
Hierarchy
☛
BI_CONT (Software Component) Business Intelligence Content
⤷ BW-BCT-PLA-RAP (Application Component) Retail Assortment Planning
⤷ UPARM (Package) Retail MAP Master Data Maintenance
⤷ 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_BEFORE |
Short Description | Save Embedded View Before Accessing Current View |
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 Befor |
Medium | 17 | Save Before Enter |
Long | 24 | Save Before Entering Tab |
Heading | 24 | Save Before Entering Tab |
Documentation
Definition
When checked, this flag displays a dialog box to the user asking to save any modification before accessing 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 the results are not reloaded.
Use
Dependencies
Example
Consider these views embedded in a multi-view: View 1, View 2 and View 3. View 1 and 2 are not related, they use different InfoObjects. View 3 uses InfoObjects of View 1 and View 2. You do not need to save when navigating from View 1 to View 2. However, you do need to save before accessing View 3.
History
Last changed by/on | SAP | 20141031 |
SAP Release Created in | 705 |