Академический Документы
Профессиональный Документы
Культура Документы
We will use the same nodes in third tab so both the nodes MAIN_INFO &
DETAIL_INFO should be of 1:N cardinality.
Save and activate the component controller.
Map the component controller context node to View Context node.
Insert UI Element TABSTRIP to ROOTEUIELEMENTCONTAINER with
MatrixLayout for the concern of alignments.
Insert Tabs
As we want more than one input fields, insert GROUP UI ELEMENT passing
through Insert Content.
We have taken context node in view and the same attributes we will use in
first tab. So we can use option for binding as Create Container Form.
For binding of context node to second tab with personal details, do the same
as we followed steps above
For third screen, data should come from first two tabs, so third screen must
be in display format.
To take fields from first two tabs, we need event handler action. To
incorporate this, insert UI Element Button on first and second tabs, with the
following code.
Use code wizard to call the context node main_info
DATA : lo_nd_main_info TYPE REF TO if_wd_context_node,
lo_el_main_info TYPE REF TO if_wd_context_element,
ls_main_info TYPE wd_this->element_main_info,
lt_main_info TYPE wd_this->elements_main_info.
lo_el_main_info->get_static_attributes(
IMPORTING
static_attributes = ls_main_info ).
lo_el_main_info->get_static_attributes(
IMPORTING
static_attributes = ls_main_info ).
*
lo_nd_main_info->bind_table( lt_main_info ).
endif.
Call the context node Detail_Info and bind the inputs to Internal table.
* Node : DETAIL_INFO
DATA : lo_nd_detail_info TYPE REF TO if_wd_context_node,
lo_el_detail_info TYPE REF TO if_wd_context_element,
ls_detail_info
TYPE
wd_this->element_detail_info,
lt_detail_info
TYPE
wd_this->elements_detail_info.
* Object Reference to context node DETAIL_INFO