Best data update approach

I am currently trying to decide on the best architecture approach for the synchronisation of data between a CRM system and SAP. The CRM system is already built and will be producing files as part of nightly batch containing updates that are required for synchronisation to SAP. Examples of these updates are:
- New Customers
- Updates to existing customer information (e.g. date of birth)
- Regional Structure Updates
and so on.
We do not have a middleware platform, nor can we process the updates asynchronously throughout the day using messages, so we must use a batch approach where the CRM creates a file containing the changes and then we load and update SAP each night.
My questions is should we get the CRM system to format the changes as IDOCs or just create a custom flat file containing the changes?
- If we use IDOCs I assume I can then reuse standard SAP functionality to make the updates to the SAP DB (and I assume that they would be able to tell the different between a create and an update). However the downside is that will be extra complexity in creating correctly formatted IDOC in the CRM system. A follow on question would be - Am I correct in assuming that a single IDOC can contain updates for many different records (e.g. in the case of the batch to update customer information would I need an IDOC for each update or just 1 mega IDOC?
- If we use a flat file format then we will need to create a custom ABAP program to read in the file and call the appreciate methods to either locate and update records or create new ones.
Any guidance would be good, particularly on the relative advantages of using IDOCs over flat files for this type of batch processing.

Hi Richard,
Welcome to SDN.
I would suggest to use IDoc for interface between SAP and CRM (vice versa).
IDoc technology has excellent error handling and capability to reprocess the error case by case.
It has also good error analysis and testing tool.
Regards,
Ferry Lianto

Similar Messages

Excelsisu Best Data Connectivity Approach: BI Services & Live Office?

Hi guys,
I the next months we have planned to develop several Excelsius dashboards based on existing web intelligence queries. After carefully reading all documentation we have concluded that for this purpose the most suitable approaches for data connectivity are:
- Use BI Services (Qaaws method)
- Use Live Office
Leaving apart license considerations (we have Live Office licenses) we are internally discussing about which should be the choosen method to develop all dashboards.
Both seems to fullfill basic requirements: security restrictions, access to special data (totals, orders by)
Question is: what is your opinion about? Considering the future release of SP4 do you know which method best fit future migrations?

Hi,
You have three options currently. QaaWS, BI Services and Live Office.
In BI4.0 QaaWS is effectively replaced by the query pane in Xcelsius, which lets you connect an Xcelsius model directly to a universe.
In BI4.0, you can also create BI Services from the web client, you no longer need to use the Webi Rich Client.
Read this for an overview and comparison of the three. http://blog.davidg.com.au/2011/04/live-office-vs-qaaws-vs-bi-services.html
Having just migrated a dashboard with 44 connections from Live Office to BI Services, I can tell you that BI Services are much faster, and easier to work with.
Hope that helps.

Confuse on PR & PO data migration approach new to MM module

Hi All,
I'm pretty confuse with the PO data migration approach when it comes to PO is GR or partial GR or GR&IR. I'm hoping that someone can enlighten me. i understand that we typically don't migrate PO when it is GR & IR, FI team usually will bring over to the new system as an vendor open item in AP. How about the PR or PO which have gone through or half release strategy? What is the follow up process? I have created a criteria table below. How Could someone point me in the right direction? Thanks in advance.
PR
Criteria
Data migration required
Notes
Open and Released
Y
Open and not Released
Y
Flag for Deletion
N
Flag for Block
Y
PO
Criteria
Data migration required
Notes
Open and Released
Y
Open and not Released
Y
GR but no IR
GR & IR
N
AP will bring over as open item
Flag for Deletion
N
Flag for Block
Y
Partial
Y
For partial GR to recreate PO only with missing GR quantity
Regards,
John

Hi John,
The approach that i have followed recently is that we have considered PO as the base document and converted other documents based on the PO condition. This means you first need to see if the PO is to be converted or not. Then you can proceed to convert the related documents like PR, Agreement, Info record, Source list, etc.
Also open qty for PO should be considered for Material and Service line items both.
Once a GR/SES is created, it gets updated in the PO history table EKBE with its related transaction/event type.i.e. EKBE-VGABE = 1 for GR and 9 for SES. Quantity and value also gets updated in case of material and services. You can compare this consumed quantities with PO quantity.
Please see below from SCN and let me know if you need more info on PR or PO conversion.
Purchase Requisition Conversion Strategy
Thanks,
Akash

Last Data Update in Visual Composer and Web App Designer

Hello,
We want to show the last data update in query result and we used 2
differents ways to do it: throught Web Application Designer (SP 12) and
Visual Composer (SP 10).
In query result of Web Application Designer, the last data update came
in GMT0 and in visual composer came ok (GMT - 3, that's our time zone).
This value (ROLLUPTIME) is taken out of the RSMDATASTATE table and this is used in SAPLRSMDATASTATE program, that is called by Web App Designer.
Why does the difference exist between: Web App Designer and Visual Composer for last data update?
So, I need more information how the Visual Composer brings the correct value (in our time zone) and Web App Designer in GMT0.
Best Regards,
Pablo Moraes

Hi Mario,
Yes, i used the same user and the same query to access the information. But, how can i check the mapping from my VC user to the BI user?
Regards,
Pablo Moraes

Data migration approach for Scheduling Agreements

Gurus,
Can anyone provide guidance on the data migration approach for Scheduling Agreements? How can we migrate the open delivery schedules and the respective cumulative quantities? The document type being used is "LZ".
Can correction deliveries (Doc type - LFKO) be used update the initial cumulative quantities?
Any help in this regard is higly appreciated.
Regards,
Gajendra

Hi Zenith
You might find useful information here: IS-U data export (extraction) for EMIGALL.
I've done numerous IS-U migrations in the last 10+ years, but never one from IS-U to IS-U.
One main questions to start with: Are the two systems on the same release level?
If they are not and it would be too much effort to get them onto the same release level I would think creating your own extract programs and using the Migration workbench (EMIGALL) is the way to go.
If they are on the same level, there might possible other ways to do it, dependent on the differences between the two systems (mainly around customising). Assuming there are significant differences - otherwise why would you bother migrating? - there's the high probability that using EMIGALL is the way to go as well.
Yep
Jürgen

Dynamical Call of ALV - No data update

Hi,
I tried to use use the ALV dynamically. With dynamically I mean that I that I have diffrent data structures, depending what was selected by the user. The first call of the program is always correct. The data is displayed correctly. But when the data structure is changing, the ALV display is not updated. For a better understanding I post a extract of my coding:
1. Creation of Container
CREATE OBJECT g_custom_container
 EXPORTING
 container_name = 'PARENT_CONT'
 EXCEPTIONS
 cntl_error = 1
 cntl_system_error = 2
 create_error = 3
 lifetime_error = 4
 lifetime_dynpro_dynpro_link = 5.
IF sy-subrc <> 0.
 ASSERT 1 = 2.
ENDIF.
2.Creation of splitter container
CREATE OBJECT splitter
 EXPORTING
 parent = g_custom_container
 rows = 2
 columns = 2
 EXCEPTIONS
 cntl_error = 1
 cntl_system_error = 2
 OTHERS = 3.
IF sy-subrc <> 0.
 ASSERT 1 = 2.
ENDIF.
container_2 = splitter->get_container(
 row = 1
 column = 2 ).
3.Dynamic Creation of alv object
CREATE OBJECT go_grid
 EXPORTING
 i_parent = container_2.
4. Get Fieldcatalogue
CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
 EXPORTING
 i_structure_name = lv_structure_name
 CHANGING
 ct_fieldcat = lt_fieldcat
 EXCEPTIONS
 inconsistent_interface = 1
 program_error = 2
 OTHERS = 3.
IF sy-subrc <> 0.
 ASSERT 1 = 2.
ENDIF.
5. Set table for first display
CALL METHOD go_grid->set_table_for_first_display
* EXPORTING
* i_structure_name = lv_structure_name
 CHANGING
 it_fieldcatalog = lt_fieldcat
 it_outtab = <lt_out_data>.
CALL METHOD ls_alv_ref-alv_ref->refresh_table_display.
CALL METHOD cl_gui_cfw=>flush.
Perhaps someone could help.....
Best Regards, Edgar

Hello Edgar
The following sample report ZUS_SDN_TWO_ALV_GRIDS_8 shows how to solve your problem. Please note that for the sake of simplicity I replaced the tree containing the structure names with an ALV list. However, the switch between the different structures is triggered by the DOUBLE_CLICK event.
I like to add that the integration of the first displayed ALV list (DD02L) into GT_OUTTAB is not really elegant. In addition, with $TMP I marked a problematic part of the coding with respect to your requirement to have the right layout for each displayed ALV list:
If you have a fixed assignment of tabname -> 4-digit handle then it is ok. I my sample report the layouts only work if you select the tabnames in the very same order.
Before showing the entire coding I describe crucial parts of the coding:
[code]TYPES: BEGIN OF ty_s_outtab.
TYPES: tabname TYPE tabname.
TYPES: layout TYPE lvc_s_layo.
TYPES: variant TYPE disvariant.
TYPES: fcat TYPE lvc_t_fcat.
TYPES: data TYPE REF TO data.
TYPES: END OF ty_s_outtab.[/code]
Every time a new structure is selected the corresponding ALV data are stored as new record in GT_OUTTAB which is of line type TY_S_OUTTAB.
[code] READ TABLE gt_outtab INTO gs_outtab INDEX 2.
ASSIGN gs_outtab-fcat TO <gt_fcat>.
ASSIGN gs_outtab-data->* TO <gt_outtab>.[/code]
Since the ALV list data and the fieldcatalog are fully dynamic I use global field-symbols for these data.
[code]&----
*& Module STATUS_0100 OUTPUT
 text
MODULE status_0100 OUTPUT.
SET PF-STATUS 'STATUS_0100'. " contains push button "DETAIL"
SET TITLEBAR 'xxx'.
CALL METHOD go_grid2->set_table_for_first_display
 EXPORTING
 i_structure_name = gs_outtab-tabname
 is_layout = gs_outtab-layout
 is_variant = gs_outtab-variant
 i_save = 'A'
 CHANGING
 it_outtab = <gt_outtab>
 it_fieldcatalog = <gt_fcat>
 EXCEPTIONS
 OTHERS = 4.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDMODULE. " STATUS_0100 OUTPUT[/code]
The second ALV list which displays the table records is always newly displayed in the PBO module.
In the event handler method HANDLE_DOUBLE_CLICK we need to do two things:
- store the current fieldcatalog back to GT_OUTTAB
- store the name of the new selected table/structure -> trigger PAI
In routine HANDLE_DB_CLICK we create a new entry for GT_OUTTAB if it does not yet exist. Next we select this entry and display it again as second ALV list.
[code]
*& Report ZUS_SDN_TWO_ALV_GRIDS_8
*& Description: Display two ALV lists in splitter container (left/right)
*& Left ALV list contains DB table names,
*& right ALV list displays entries of selected DB table
*& SDN thread: Dynamical Call of ALV - No data update
*& Link: https:||Dynamical Call of ALV - No data update
*& Screen '0100' contains no elements.
*& ok_code -> assigned to GD_OKCODE
*& Flow logic:
PROCESS BEFORE OUTPUT.
 MODULE STATUS_0100.
PROCESS AFTER INPUT.
 MODULE USER_COMMAND_0100.
REPORT zus_sdn_two_alv_grids_8.
TYPE-POOLS: abap.
DATA:
gd_repid TYPE syst-repid,
gd_okcode TYPE ui_func,
go_docking TYPE REF TO cl_gui_docking_container,
go_splitter TYPE REF TO cl_gui_splitter_container,
go_cell_left TYPE REF TO cl_gui_container,
go_cell_right TYPE REF TO cl_gui_container,
go_grid1 TYPE REF TO cl_gui_alv_grid,
go_grid2 TYPE REF TO cl_gui_alv_grid,
gs_layout TYPE lvc_s_layo.
TYPES: BEGIN OF ty_s_outtab.
TYPES: tabname TYPE tabname.
TYPES: layout TYPE lvc_s_layo.
TYPES: variant TYPE disvariant.
TYPES: fcat TYPE lvc_t_fcat.
TYPES: data TYPE REF TO data.
TYPES: END OF ty_s_outtab.
TYPES: ty_t_outtab TYPE STANDARD TABLE OF ty_s_outtab
 WITH DEFAULT KEY.
DATA:
gt_dd02l TYPE STANDARD TABLE OF dd02l,
gs_outtab TYPE ty_s_outtab,
gt_outtab TYPE ty_t_outtab.
FIELD-SYMBOLS:
<gt_fcat> TYPE lvc_t_fcat,
<gt_outtab> TYPE table.
 CLASS lcl_eventhandler DEFINITION
CLASS lcl_eventhandler DEFINITION.
PUBLIC SECTION.
 CLASS-DATA:
 md_tabname_selected TYPE tabname READ-ONLY.
 CLASS-METHODS:
 handle_double_click FOR EVENT double_click OF cl_gui_alv_grid
 IMPORTING
 e_row
 e_column
 es_row_no
 sender.
ENDCLASS. "lcl_eventhandler DEFINITION
 CLASS lcl_eventhandler IMPLEMENTATION
CLASS lcl_eventhandler IMPLEMENTATION.
METHOD handle_double_click.
define local data
 DATA:
 ls_dd02l TYPE dd02l,
 ls_outtab TYPE ty_s_outtab.
 CHECK ( sender = go_grid1 ).
 READ TABLE gt_dd02l INTO ls_dd02l INDEX e_row-index.
 " Store data of currently displayed ALV list (except for DD02L)
 IF ( md_tabname_selected = space ).
 ELSE.
 READ TABLE gt_outtab INTO ls_outtab
 WITH KEY tabname = md_tabname_selected. " old
 CALL METHOD go_grid2->get_frontend_fieldcatalog
 IMPORTING
 et_fieldcatalog = ls_outtab-fcat.
 MODIFY gt_outtab FROM ls_outtab INDEX syst-tabix.
 ENDIF.
 md_tabname_selected = ls_dd02l-tabname. " new selected DB table
Triggers PAI of the dynpro with the specified ok-code
 cl_gui_cfw=>set_new_ok_code( 'HANDLE_DB_CLICK' ). " not 4.6c
 CALL METHOD cl_gui_cfw=>set_new_ok_code
 EXPORTING
 new_code = 'HANDLE_DB_CLICK'
 IMPORTING
 RC =
ENDMETHOD. "handle_double_click
ENDCLASS. "lcl_eventhandler IMPLEMENTATION
START-OF-SELECTION.
gd_repid = syst-repid.
SELECT * FROM dd02l INTO TABLE gt_dd02l
 WHERE tabname LIKE 'KN%1' OR
 tabname LIKE 'LF%1' OR
 tabname LIKE 'VB%' OR
 tabname LIKE 'MAR%' OR
 tabname LIKE 'E07%'
 AND tabclass = 'TRANSP'. " transparent table
SORT gt_dd02l BY tabname.
PERFORM init_controls.
PERFORM add_first_table.
Set event handler
SET HANDLER:
 lcl_eventhandler=>handle_double_click FOR go_grid1.
READ TABLE gt_outtab INTO gs_outtab INDEX 1.
Display data
CALL METHOD go_grid1->set_table_for_first_display
 EXPORTING
 i_structure_name = gs_outtab-tabname
 is_layout = gs_outtab-layout
 CHANGING
 it_outtab = gt_dd02l
 EXCEPTIONS
 OTHERS = 4.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE gt_outtab INTO gs_outtab INDEX 2.
ASSIGN gs_outtab-fcat TO <gt_fcat>.
ASSIGN gs_outtab-data->* TO <gt_outtab>.
NOTE: method called in PBO module
CALL METHOD go_grid2->set_table_for_first_display
 EXPORTING
 i_structure_name = gs_outtab-tabname
 is_layout = gs_outtab-layout
 is_variant = gs_outtab-variant
 i_save = 'A'
 CHANGING
 it_outtab = <gt_outtab>
 it_fieldcatalog = <gt_fcat>
 EXCEPTIONS
 OTHERS = 4.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Link the docking container to the target dynpro
CALL METHOD go_docking->link
 EXPORTING
 repid = gd_repid
 dynnr = '0100'
 CONTAINER =
 EXCEPTIONS
 OTHERS = 4.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
NOTE: dynpro does not contain any elements
CALL SCREEN '0100'.
Flow logic of dynpro (does not contain any dynpro elements):
*PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
*PROCESS AFTER INPUT.
MODULE USER_COMMAND_0100.
END-OF-SELECTION.
*& Module STATUS_0100 OUTPUT
 text
MODULE status_0100 OUTPUT.
SET PF-STATUS 'STATUS_0100'. " contains push button "DETAIL"
SET TITLEBAR 'xxx'.
CALL METHOD go_grid2->set_table_for_first_display
 EXPORTING
 i_structure_name = gs_outtab-tabname
 is_layout = gs_outtab-layout
 is_variant = gs_outtab-variant
 i_save = 'A'
 CHANGING
 it_outtab = <gt_outtab>
 it_fieldcatalog = <gt_fcat>
 EXCEPTIONS
 OTHERS = 4.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDMODULE. " STATUS_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT
 text
MODULE user_command_0100 INPUT.
CASE gd_okcode.
 WHEN 'BACK' OR
 'END' OR
 'CANC'.
 SET SCREEN 0. LEAVE SCREEN.
User has pushed button "Display Details"
 WHEN 'HANDLE_DB_CLICK'.
 PERFORM handle_db_click.
 WHEN OTHERS.
ENDCASE.
CLEAR: gd_okcode.
ENDMODULE. " USER_COMMAND_0100 INPUT
*& Form HANDLE_DB_CLICK
 text
--> p1 text
<-- p2 text
FORM handle_db_click.
define local data
DATA:
 ld_handle(4) TYPE n,
 ls_outtab TYPE ty_s_outtab.
READ TABLE gt_outtab INTO ls_outtab
 WITH KEY tabname = lcl_eventhandler=>md_tabname_selected.
IF ( syst-subrc NE 0 ).
 CLEAR: ls_outtab.
 ls_outtab-tabname = lcl_eventhandler=>md_tabname_selected.
 CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
 EXPORTING
 I_BUFFER_ACTIVE =
 i_structure_name = ls_outtab-tabname
 I_CLIENT_NEVER_DISPLAY = 'X'
 I_BYPASSING_BUFFER =
 I_INTERNAL_TABNAME =
 CHANGING
 ct_fieldcat = ls_outtab-fcat
 EXCEPTIONS
 inconsistent_interface = 1
 program_error = 2
 OTHERS = 3.
 IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
 ENDIF.
 CREATE DATA ls_outtab-data TYPE TABLE OF (ls_outtab-tabname).
 ASSIGN ls_outtab-data->* TO <gt_outtab>.
 SELECT * FROM (ls_outtab-tabname) UP TO 50 ROWS
 INTO TABLE <gt_outtab>.
 ls_outtab-layout-no_toolbar = abap_false.
 ls_outtab-layout-zebra = abap_true.
 ls_outtab-layout-smalltitle = abap_true.
 CONCATENATE ls_outtab-tabname ':'
 INTO ls_outtab-layout-grid_title.
 CONCATENATE ls_outtab-layout-grid_title 'Table Records'
 INTO ls_outtab-layout-grid_title
 SEPARATED BY space.
 ls_outtab-variant-report = gd_repid.
 DESCRIBE TABLE gt_outtab.
 ld_handle = syst-tfill + 1.
 WRITE ld_handle TO ls_outtab-variant-handle. " $TMP: Problem!!!
 APPEND ls_outtab TO gt_outtab.
ENDIF.
" NOTE: read into GLOBAL variable gs_outtab !!!!
READ TABLE gt_outtab INTO gs_outtab
 WITH KEY tabname = lcl_eventhandler=>md_tabname_selected.
ASSIGN gs_outtab-fcat TO <gt_fcat>.
ASSIGN gs_outtab-data->* TO <gt_outtab>.
ENDFORM. " HANDLE_DB_CLICK
*& Form INIT_CONTROLS
 text
--> p1 text
<-- p2 text
FORM init_controls .
Create docking container
CREATE OBJECT go_docking
 EXPORTING
 parent = cl_gui_container=>screen0
 ratio = 90
 EXCEPTIONS
 OTHERS = 6.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL METHOD go_docking->set_extension
 EXPORTING
 extension = 99999 " full-size screen
 EXCEPTIONS
 cntl_error = 1
 OTHERS = 2.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Create splitter container
CREATE OBJECT go_splitter
 EXPORTING
 parent = go_docking
 rows = 1
 columns = 2
 NO_AUTODEF_PROGID_DYNNR =
 NAME =
 EXCEPTIONS
 cntl_error = 1
 cntl_system_error = 2
 OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Get cell container
CALL METHOD go_splitter->get_container
 EXPORTING
 row = 1
 column = 1
 RECEIVING
 container = go_cell_left.
CALL METHOD go_splitter->get_container
 EXPORTING
 row = 1
 column = 2
 RECEIVING
 container = go_cell_right.
CALL METHOD go_splitter->set_column_mode
 EXPORTING
 mode = cl_gui_splitter_container=>mode_relative
 IMPORTING
 RESULT =
 EXCEPTIONS
 cntl_error = 1
 cntl_system_error = 2
 OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL METHOD go_splitter->set_column_width
 EXPORTING
 id = 1
 width = 25
 IMPORTING
 RESULT =
 EXCEPTIONS
 cntl_error = 1
 cntl_system_error = 2
 OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL METHOD go_splitter->set_column_sash
 EXPORTING
 id = 1
 type = cl_gui_splitter_container=>type_movable
 value = cl_gui_splitter_container=>false
 IMPORTING
 RESULT =
 EXCEPTIONS
 cntl_error = 1
 cntl_system_error = 2
 OTHERS = 3.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
Create ALV grids
CREATE OBJECT go_grid1
 EXPORTING
 i_parent = go_cell_left
 EXCEPTIONS
 OTHERS = 5.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CREATE OBJECT go_grid2
 EXPORTING
 i_parent = go_cell_right
 EXCEPTIONS
 OTHERS = 5.
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
ENDFORM. " INIT_CONTROLS
*& Form ADD_FIRST_TABLE
 text
--> p1 text
<-- p2 text
FORM add_first_table .
define local data
DATA:
 ls_outtab TYPE ty_s_outtab.
ls_outtab-tabname = 'DD02L'.
CALL FUNCTION 'LVC_FIELDCATALOG_MERGE'
EXPORTING
I_BUFFER_ACTIVE =
 i_structure_name = ls_outtab-tabname
I_CLIENT_NEVER_DISPLAY = 'X'
I_BYPASSING_BUFFER =
I_INTERNAL_TABNAME =
CHANGING
 ct_fieldcat = ls_outtab-fcat
EXCEPTIONS
 inconsistent_interface = 1
 program_error = 2
 OTHERS = 3.
IF sy-subrc <> 0.
*MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
GET REFERENCE OF gt_dd02l INTO ls_outtab-data.
ls_outtab-layout-no_toolbar = abap_false.
ls_outtab-layout-zebra = abap_true.
ls_outtab-layout-smalltitle = abap_true.
CONCATENATE ls_outtab-tabname ':'
 INTO ls_outtab-layout-grid_title.
CONCATENATE ls_outtab-layout-grid_title 'Table Records'
 INTO ls_outtab-layout-grid_title
 SEPARATED BY space.
ls_outtab-variant-report = gd_repid.
ls_outtab-variant-handle = '0002'.
INSERT ls_outtab INTO gt_outtab INDEX 1.
ls_outtab-layout-no_toolbar = abap_true.
ls_outtab-layout-zebra = abap_true.
ls_outtab-layout-smalltitle = abap_true.
ls_outtab-layout-grid_title = 'DB Tables'.
ls_outtab-variant-report = gd_repid.
ls_outtab-variant-handle = '0001'.
DELETE ls_outtab-fcat WHERE ( fieldname NE 'TABNAME' ).
INSERT ls_outtab INTO gt_outtab INDEX 1.
ENDFORM. " ADD_FIRST_TABLE[/code]
Regards,
Uwe

What are different Data archival approaches available in SharePoint 2013?

I want to know what are the different Data archival approaches available in SharePoint 2013 apart from Record Management?

Record center is the best template available for data archival.
You can also use IRM for Data Archiving
Also I would suggest you to use BLOB stoage which will reduce addional burden on SQL server:
http://blogs.technet.com/b/wbaer/archive/2012/11/12/introduction-to-shredded-storage-in-sharepoint-2013.aspx

Last data update

Hi,
How I can find the last data update information(date and time) of multiprovider in BW?
Kindly help on this.
Regards
Mukul Singhal

Let me explain how the "last data update" works.
If the query is based on one cube or DSO, it is the time of the last request upload.
If the query is based on a multiprovider, like the example given ealier,
assume there are three cubes in multiprovider :
Last update of cube1 is 11/17/2008
Last update of cube2 is 11/19/2008
Last udpate of cube3 is 11/20/2008.
The "last data update" will be the earliest day of the "last data update"s of all partproviders, i.e.11/17/2008.
Because the meaning of "last data update" is that, data (of all partproviders) has been already updated until this time.
Now we assume there are three cubes like this in multiprovider :
Last update of cube1 is 11/17/2008
Last update of cube2 is 11/19/2008
Cube3 is empty. It has never been loaded with any request.
Then the "last data update" will be empty. Because until no time has all partproviders been updated. This is the design of the system.
Regards,
Patricia

Unable to run bapis for project status update and date update together

Hi Experts,
I have a requirement to update the dates and status of a project WBS at level 4. I am trying to do update the CJ02 Transaction using standard BAPI available. I need to do both Date update and status update in the same LOOP PASS i am using the below mention bapi. when i am doing so i am getting an error Project 'A._____' has been currently processed by ID i.e. my id.
I have tried putting a wait for 2 seconds in the code but its still not working. please find the order below in which i am calling the bapi.
Loop at itab.
if date_changed = 'X'.
 CALL FUNCTION 'BAPI_PROJECT_MAINTAIN'
 READ TABLE it_error WITH KEY message_type = c_e.
 IF sy-subrc <> 0.
Commit
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = c_x
 IMPORTING
 return = s_ret.
 endif.
endif.
if Status_change = 'X'.
 CALL FUNCTION 'BAPI_PS_INITIALIZATION' .
 CALL FUNCTION 'BAPI_BUS2054_SET_STATUS'
 READ TABLE t_result WITH KEY message_type = c_e.
 IF sy-subrc NE 0.
 CALL FUNCTION 'BAPI_PS_PRECOMMIT'
 TABLES
 et_return = t_ret.
 CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
 EXPORTING
 wait = c_x
 IMPORTING
 return = s_ret.
 ENDIF.
endif.
 WAIT UP TO 4 SECONDS.
endloop.

Try to use
SET UPDATE TASK LOCAL.
before each BAPI call.
Did you try to debug through your code, leaving sufficient time between BAPI calls? If it does work like that, then the above statement might help.

When the apple review team review our app,they point out that our app uses a background mode but does not include functionality that requires that mode to run persistently.but in fact,when the app in background ,the app need data update to make the

when the apple review team review our app，they point out that our app uses a background mode but does not include functionality that requires that mode to run persistently。but in fact，when the app in background ，the app need data update to make the function of trajectory replay come ture。in fact， we have added function when the app is in background mode。we have point out the point to them by email。but they still have question on the background mode，we are confused，does anyone can help me，i still don't know why do review team can't find the data update when the app is in background and how do i modify the app，or what is the really problem they refered，do i misunderstand them？
the blow is the content of the review team email：
We found that your app uses a background mode but does not include functionality that requires that mode to run persistently. This behavior is not in compliance with the App Store Review Guidelines.
We noticed your app declares support for location in the UIBackgroundModes key in your Info.plist but does not include features that require persistent location.
It would be appropriate to add features that require persistent use of real-time location updates while the app is in the background or remove the "location" setting from the UIBackgroundModes key. If your application does not require persistent, real-time location updates, we recommend using the significant-change location service or the region monitoring location service.
For more information on these options, please see the "Starting the Significant-Change Location Service" and "Monitoring Shape-Based Regions" sections in the Location Awareness Programming Guide.
If you choose to add features that use the Location Background Mode, please include the following battery use disclaimer in your Application Description:
"Continued use of GPS running in the background can dramatically decrease battery life."
Additionally, at your earliest opportunity, please review the following question/s and provide as detailed information as you can in response. The more information you can provide upfront, the sooner we can complete your review.
We are unable to access the app in use in "http://www.wayding.com/waydingweb/article/12/139". Please provide us a valid demo video to show your app in use.
For discrete code-level questions, you may wish to consult with Apple Developer Technical Support. When the DTS engineer follows up with you, please be ready to provide:
- complete details of your rejection issue(s)
- screenshots
- steps to reproduce the issue(s)
- symbolicated crash logs - if your issue results in a crash log
If you have difficulty reproducing a reported issue, please try testing the workflow as described in <https://developer.apple.com/library/ios/qa/qa1764/>Technical Q&A QA1764: How to reproduce a crash or bug that only App Review or users are seeing.

Unfortunately, these forums here are all user to user; you might try the developer forums or get in touch with the team that you are working with.

Help! Best data recovery software?

Help!
Accidentally put some important photos in the Trash Can, and emptied it.
Best data recovery program = ?
Thanks!

Click here and pick a product. Don't write anything else to the drive until the files are recovered or you choose not to recover them.
(105730)

Cann't install up to date update Lion 10.7 cancel during install error: damaged by download but it's download without errors 1,34 GB. What can I do has anyone a solution to solve this issue?

cann't install up to date update Lion 10.7 cancel during install error: damaged by download but it's download without errors 1,34 GB. What can I do has anyone a solution to solve this issue?

I wish I fully understood your post, but perhaps you should try re-downloading. Are you trying to download the 10.7.3 update? If so, then try downloading OS X Lion Update 10.7.3 (Client Combo).

Reconciliation and data verification approaches for data in sap r/3 and bw

Hi
Cam anybody suggest what are the different reconciliation and data verification approaches to assure that BW and R/3 source data are in sync.
Thanks in advance.
Regards,
Nisha.

Hi
What you can do is, go to R/3 transaction RSA3 and run the extractor, it gives you the number of records extracted and then go to BW Monitor to check the number of records in the PSA.
if it's the same, there you go.
there is an HOW-TO Document on service market place "Reconcile Data Between SAP Source Systems and SAP BW".
Check this document as well which is very helpful.
There is another HOW-TO document "Validate infocube data by comparing it with PSA Data". this is also a good document.
Hope it helps.
Hari Immadi
http://immadi.com
SEM BW Analyst

How to hide the Last date Update in the Excution of a report

Dear All,
When we execute a query in EP, the Out Result will contain the following Options
1) Save As
2) Open
3) Export Excel
4) Information
5 ) Comments
6) Filters
7) Settings
8) Last data update
Can anyone plese tell me how to give the authorisation in BI for the above options.so that we can give restrictions for some users.
hope everything is crear.
Please give me the hint atleast

You also have to test the value:
REPORT ztest MESSAGE-ID 00.
DATA: BEGIN OF itab OCCURS 0,
        f1 TYPE i,
        f2 TYPE i,
        f3 TYPE i,
        f4 TYPE i,
      END OF itab.
DATA: sel_field(20),
      value TYPE i.
DO 5 TIMES.
itab-f1 = sy-index.
itab-f2 = sy-index + 10.
itab-f3 = sy-index + 20.
itab-f4 = sy-index + 30.
APPEND itab.
ENDDO.
LOOP AT itab.
WRITE: /001 itab-f1, itab-f2, itab-f3, itab-f4.
HIDE itab.
CLEAR itab.
ENDLOOP.
AT LINE-SELECTION.
CLEAR: sel_field,
         value.
GET CURSOR FIELD sel_field.
IF sy-subrc = 0.
    CASE sel_field.
      WHEN 'ITAB-F1'.
        value = itab-f1.
      WHEN 'ITAB-F2'.
        value = itab-f2.
      WHEN 'ITAB-F3'.
        value = itab-f3.
      WHEN 'ITAB-F4'.
        value = itab-f4.
    ENDCASE.
    MESSAGE s001 WITH 'Value of' sel_field 'is' value.
ELSE.
    MESSAGE s001 WITH 'Invalid field selected'.
ENDIF.
Rob

Automatic date update in Pages for iPad

I want the date (date feild?) in a Pages for iPad letter template to update automatically (using the system date, like other word process application) but cannot see how to do this. This automatic date update appears to work in the Pages for iPad templates examples. i.e open a letter template and the date field shows the correct date, do the same with the same template 24 hours later and the date is shown correctly accordingly. I believe feature is achieved in the Mac version of Pages by setting up a date field. I would like to do the same with Pages iPad. Any ideas how this can be achieved?

We cannot speculate about future Apple products. We know no more about this than you do at this time.
You can suggest it to Apple at Apple Feedback.

Best data update approach

Similar Messages

Maybe you are looking for