Skip to end of metadata
Go to start of metadata

Purpose

This is trouble shooting guideline for all content concerning the data extraction.1597364

Common issues

1 - "Very High" priority is not justified

(BW-BCT-CO-PA) 946549  - 'Very High' priority not justified
(BW-BCT-MM-IV) 2098807 - "Very high" priority is not justified

2 - Important Tables and transactions

 

 

3 - General performance problems

  1. 3.1 Job itself takes a long time

    Please focus on the datasource itself, component should be BW-BCT-XX (search note/incident using the name of the datasource).
    - For the traditional SAPI, the job name is BIREQU_*
    - For the ODP/ODQ framework (job name can be found in TCode.ODQMON): BIREQU_* for Infopackage, ODQR_* for DTP.

    1. Check if there's use-exit in the job log, such as exit_saplrsap_001 / exit_saplrsap_002 / exit_saplrsap_004. If the user-exit takes a long time, then consulting issue.
    2. No user-exit, search note / incident by : datasource name + performance
    3. No note is helpful, please record a ST12 performance trace:
    - If TCode.RSA3 can reproduce the performance issue, then record trace for RSA3 using 'Current mode'
    - If RSA3 cannot, but only the extraction from ERP to BW can reproduce the issue, please record the trace (2469206 - How to collect a trace analysis for delta extraction in the source system) during the extraction -> Aanalyze -> may ask help from DB team.

  2. 3.2 The data transferring takes a long time

    3.2.1 Traditional SAPI

    Job finished quickly, however IDOC transformation is very slow, component might be BC-BW. Please check by the steps below:
    1. Central Note : 597364-FAQ: BW-BCT: Extraction performance in source system. Mainly check: TCode.SMQS -> Max.conn
    2. TCode.SMQS, is there a NONE destination?:
    Note 1250813-SAPLARFC uses all dialog work processes ( suggest note 1403974, suggest register NONE in transaction SMQS)
    Note 1403974-Determining the maximum connections in transaction SMQS(BC-MID-RFC, how to create NONE )
    Reason: The data packages will use RFC Destination with type 3 but the INFO IDocs will use the RFC Destination NONE via TCode.SMQS to transfer the IDocs to BW. Therefore we'd recommend customers to create it.
    3. Both two steps above don't work, please record the ST12 trace in the source system during the extraction.


    3.2.2 ODP scenario

    Check according to the 2 SAP notes:
    2300483-ODQ - performance of ODQDATA_V and ODQTSNLOG
    2520897-ODP package size and data load performance


  3. 3.3 The update in BW side takes a long time

    No matter the Infopackage loads data to PSA or to data target(Cube, DSO) or both simultaneously, so long as the processing time in BW side is long:
    1. Check TCode.SM66/SM50 to find out the which program/function took a long time
    2. Search Note by : the program name + performance / long / hang, there should be notes from BW-WHM-XX.

4 - Data missing during the extraction

  1. 4.1 Check movement type (for 2lis_02/03 datasources)

    Is the movement type of material document statistic relevant:
    Run TCode.OMJJ, see note 827178 -2LIS_03_BF/_UM: Individual documents not extracted
    >>Possible values:
    '' Not relevant
    2 Document evaluations and standard analyses (update)
    3 Standard analyses only (update)

    If the value <> 2 the movement type is not statistic relevant, won't be extracted.

  2. 4.2 For Delta missing

    1. Check Note 2602318 - Queue-based DataSource missed delta records from a particular time range
    2. A reproduce example is required, A reason cannot be determined without specifying a reproducible example.
    See note 978089-LIS/BW-BCT: Reproducible example requested:
    3. If issue cannot be reproduced but happens randomly, please activate log file for delta triggering in R/3 system by Note:
    1760322 - Activate log file for delta extraction, application 02, 03, 04, 08, 11, 12, 13([9])
    Here we would mention:
    "The extraction log is only helpful to find about more about the circumstance of a problematic extraction, however, it usually cannot be used to find out the exact root cause. Therefore we still need ask customer to provide us with a real reproducible example for the issue."

  3. 4.3 For Full missing

  • 4.3.1 Issue can be reproduced in the source system

1. Traditional SAPI
Check using TCode.RSA3 -> Use the selection condition which's the same with Infopackage
2. ODP
Check using SE38 -> RODPS_REPL_TEST > Use the selection condition which's the same with Infopackage/DTP. To debug RODPS_REPL_TEST, see note 1580242.

  • 4.3.2 Issue only can be reproduced by running Infopackage/DTP from the target system (BW, BODS, Byd...)

Necessary to check: Does the background user have enough authorization -> see note 150315
[Notice]: profile SAP_ALL and SAP_NEW are not enough authorization to background users.
If profile is OK →
1. Traditional SAPI
Debug infopackage from BW side (Note 177577)

2. ODP
Debug DTP (simulation mode) from BW side, call stack is as below:

7   FUNCTION RODPS_REPL_ODP_GET_DETAIL SAPLRODPS_REPL(<----jump to source)
27 FORM         ODP_GET_DETAIL SAPLRSDS_ODP
26 FUNCTION RSDS_ODP_DETAILS_GET SAPLRSDS_ODP(after CASE get_communication_channel( i_logsys ) )
25 METHOD    RODPS_REPL_ODP_GET_DETAIL CL_RSDS_ACCESS_ODP============CP
24 METHOD    cl_rsds_access_odp=>extract CL_RSDS_ACCESS_ODP============CP >> (Access_ODP/EXTRACT1~19)
                CALL METHOD cl_rsds_access_odp=>rodps_repl_odp_open -->METHOD / OPEN (CL_RODPS_REPLICATION)
                CALL METHOD cl_rsds_access_odp=>rodps_repl_odp_fetch_xml >> jump to source: RODPS_REPL_SOURCE_FETCH_XML
                                                                                                                           >> FETCH >> _get_tid_full & _get_tid_delta
23 METHOD _GET_ODP CL_RSDS_X_CMD=================CP ( CALL METHOD p_r_ds->get_method -> L_R_ATTR_OBJ-PT_FIELDMAP holds DS name)
22 METHOD _GET_REMOTE CL_RSDS_X_CMD=================CP
21 METHOD IF_RSBK_CMD_X~GET_DATAPACKAGE CL_RSDS_X_CMD=================CP CL_RSDS_X_CMD=================CM002
20 METHOD IF_RSBK_CMD_X~GET_DATAPACKAGE_GENERAL CL_RSBK_CMD_X=================CP CL_RSBK_CMD_X=================CM00S
19 METHOD PROCESS_REQUEST CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM00Q 191
18 METHOD IF_RSBATCH_EXECUTE~EXECUTE CL_RSBK_PROCESS===============CP CL_RSBK_PROCESS===============CM002 13

 

4.4 Notes for repairing data in BW in case of missing data

See SAP Note 1773830 - Records missing in BW
"Correcting data!
- For a small set, follow note 739863 - Repairing data in BW  / 1340294-Reposting of missing data to delta queue
- For the large data volume, delta reinitialization
- In case of the Logistic datasource, 2LIS_nn_xx, before the 'full repair' or 'reinitialization', setup table will be filled firstly.

5 - Logistic Cockpit 2LIS* Datasources

  1. 5.1 Setup table

    For full extraction, the datasources read data from the setup table, such as: MC02M_0ACCSETUP, MC02M_0CGRSETUP. Name convention: SE16 -> *SETUP -> F4:

    Setup table can be deleted by TCode.LBWG. Then fill them using the following transactions:

    Application (description)TCodeProgramDataSourceComponent
    02-PurchasingOLI3BWRMCENEUA2LIS_02_ITM/HDR/ACC/SCL BW-BCT-MM-PUR
    03-Inventory(Stock Initialization)MCNBRMCBINIT_BW2LIS_03_BXBW-BCT-MM-IM
    03-Inventory(Material Movements)OLI1BWRMCBNEUA2LIS_03_BFBW-BCT-MM-IM
    03-Inventory(Revaluation)OLIZBWRMCBNERP2LIS_03_UMBW-BCT-MM-IM
    04-Shop Floor InformationOLI4BWRMCFNEUA2LIS_04_P_MATNR/2LIS_04_P_COMP/2LIS_04_P_ARBPLBW-BCT-PP-LIS
    04-SF(Repetitive Manufacturing)OLIFBWRMCFNEUD2LIS_04*BW-BCT-PP-PP
    05-Quality ManagementOLIQBWRMCQNEBW2LIS_05_Q0NOTIF/2LIS_05_QE1/2LIS_05_QE2BW-BCT-QM
    06-Invoice VerificationOLI6BWRMCENEUR2LIS_06_INVBW-BCT-MM-IV
    08-LES TransportationVTBWVTRBWVIFBW2LIS_08TRTLPBW-BCT-LE-TRA
    08-LES Shipment CostVIFBWVTRBWVIFBW2LIS_08TRFKZBW-BCT-LE-TRA
    11-SD Sales OrdersOLI7BWRMCVNEUA2LIS_11_VA*/2LIS_11_VC*BW-BCT-SD-SLS
    12-SU shippingOLI8BWRMCVNEUL2LIS_12*BW-BCT-LE-SHP
    13-SD BillingOLI9BWRMCVNEUF2LIS_13*BW-BCT-SD-BIL
    17-Plant MaintenanceOLIIBWRMCINEBW2LIS_17*BW-BCT-PM
    18-Customer Service ManagementOLISBWRMCSNEBW2LIS_18*BW-BCT-CS
  2. 5.2 Management: Logistics Cockpit - transaction LBWE

    1.Check the datasource status -> update mode (a.Direct delta / b.Unserialized V3 Update / c.Queued Delta) and maintain the Extract Structures
    For the update mode a&b, a collective run job (program is RMBWV3xx, xx - application number) is needed, see FAQ note 1779063.
    If data cannot be pushed to BW, also please check the same note.
    2. Activate datasource ( check table ROOSOURCE to see if VERSION A exists)
    3. Enhance the data structure for Datasource
    Central note: 1779063-Frequently Asked Questions (FAQ) about LO Data Extraction: Customizing Cockpit (transaction LBWE)

  3. 5.3 TCode & Source tables for LIS*

    The TCodes here are used for reproducing delta missing issue.

    DatasourceTCodesSource tables
    2LIS_02*ME21N, ME22N, ME23NEKKO,EKPO,EKET,EKBE
    2LIS_03*MIGO, MIROMSEG,MKPF
    2LIS_04*CO11, CO11N, CO14 ...AFKO,AFPO,AUFK,AFRU
    2LIS_05* QMEL,QMFE,QMIH,QAMR,QASR,QAPP,QAMR,QASV
    2LIS_06* RBKP,RBCO,RBEX,RSEG
    2LIS_08* VFKK,VFKP,VFSI,VTTK,VTTP
    2LIS_11*VA01, VA02, VA03VBAK,VBPA,VBKD,VBUP
    2LIS_12*VL03NLIKP,VBUP(rejection staus - ABSTA),VBUK,LIPS,VBPA,VBFA 
    2LIS_13*VF01, VF02, VF03VBRK,VBRP,KONV( V_KONV_CDS in S/4HANA )
    2LIS_17*IW33QMFE,QMUR,QMMA,QMSM

    The following user-exits would be called when running the transactions above:

    > For 2LIS_02*, Note 2715864:  FM EXIT_SAPLEINS_001, EXIT_SAPLRSAP_001
    > For 2LIS_12*, Note 415716: include MV50AFZ1,MV50AFZZ
    > For 2LIS_13*, Note 42250: EXIT_SAPLMCS1_002,EXIT_SAPLMCS5_002, ZXMCVU04, EXIT_SAPLMCS6_002, ZXMCVU06
    > For shipping datasource 2LIS_*, Note 901992 - Goods issue posted without being updated in BW:
    Affected DataSources: 2LIS_12_VCHDR, 2LIS_12_VCITM, 2LIS_12_VCSCL, 2LIS_11_V_ITM, 2LIS_11_V_SCL, 2LIS_11_V_SSL, 2LIS_03_BF
    FORM USEREXIT_SAVE_DOCUMENT in the include MV50AFZ1.

6 - FI datasources

6.1 0FI_GL_* datasources

(OldGL)
0FI_GL_1 / 0FI_GL_6-> total -> table: GLT0 (not released in ODP, see note 2232584)
0FI_GL_4 -> 'General Ledger: Line Items with Delta Extraction' -> read table BKPF, then BSEG (released in ODP 2232584)

(NewGL)
0FI_GL_10 -> total -> table: FAGLFLEXT (General Ledger: Totals)
0FI_GL_14 -> Line Items -> table: open cursor from FAGLFLEXA (General Ledger: Actual Line Items), Then BSEG (FB03)
0FI_GL_40 -> Line Items -> G/L Accounts
3FI_GL_xx_TT -> total -> table: FAGLFLEXT

(S/4HANA)
0FI_ACDOCA_10/20 -> table ACDOCA

6.2 0FI_AP/AR_* datasources

0FI_AP_4 BSIK BSAK
0FI_AR_4 BSID BSAD

delta will be protokolled in table:
'Recording Changed Line Items' in BWFI_AEDAT
fields:
BUKRS
BELNR
GJAHR
AEDAT date
AETIM time
When a delta dataset has been selected successfully, the SAP R/3 system logs two time stamps that define a selection interval for a DataSource in table BWOM2_TIMEST

6.3  0FI_*_6/7 datasources

0FI_GL_* reads table GLT0 GLFUNCT
0FI_AP_* LFC1 LFC3
0FI_AR_* KNC1 KNC3

Delta will be protokolled in table:
'Recording Changed Transaction Figures' in table BWFI_AEDA2

fields: TABNAME/KONTO/BUKRS/GJAHR/AEDAT date/AETIM time

The extractors can use this log table and the time stamp procedures described below to determine a delta dataset of changed transaction figures in Financial Accounting.

Time Stamp Method
When a delta dataset has been selected successfully, the SAP R/3 system logs two time stamps that define a selection interval for a DataSource in table BWOM2_TIMEST

fields:
OLTPSOURCE
AEDAT date
AETIM time
TS_LOW -from
TS_HIGH -till time intervall of loaded data

6.4  Global Settings for data extraction in table BWOM_SETTINGS
e.g. safety intevall for data load

parameters:
BWFILOWLIM
BWFISAFETY
BWFIOVERLA
BWFITIMBOR

7 - BADI and User-Exits of extractors in R/3

BADI will be called firstly and then exit_saplrsap_001/002/003/004

7.1  Call stack of BADI

 

6 METHOD IF_EX_RSU5_SAPI_BADI~DATA_TRANSFORM CL_EX_RSU5_SAPI_BADI==========CP CL_EX_RSU5_SAPI_BADI==========CM001
5 FORM      DATA_TRANSFORM                                              RSAYBADI                                                     RSU5BADI
4 FORM      CALL_DATA_CUSTOMER_FUNCTION                SAPLRSAP                                                     LRSAPF06
3 FORM      PROCESS_DATA_PACKAGE                               GP4D66FAYKOSARBBW5MBSLUTVR9       GP4D66FAYKOSARBBW5MBSLUTVR9

7.2 User-exit 

Function module, can be displayed by SE37 ->
EXIT_SAPLRSAP_001: for Transaction data ( REPS LRSAPF06 >> FORM CALL_DATA_CUSTOMER_FUNCTION )
EXIT_SAPLRSAP_002: for Attributes ( REPS LRSAPF06 >> FORM CALL_MSD_CUSTOMER_FUNCTION )
EXIT_SAPLRSAP_003: for Texts ( REPS LRSAPF06 >> FORM CALL_TEXT_CUSTOMER_FUNCTION )
EXIT_SAPLRSAP_004: for Hierarchies ( REPS LRSAPF06 >> FORM CALL_HIER_CUSTOMER_FUNCTION )

See note 1997720-SAPI BADI for 7.x HIER DataSource
> In case of ODP scenario <-----
2684463-FAQ: User-Exit/BAdI in data loads from ODP SAPI source systems
2684535-SAP exits of datasource enhancement are not executed in ODP loads from SAPI-source systems if ODP BAdI is implemented

Set break-point at line "case i_datasource.", check how the content of internal table c_t_data is changed.

8 - Primary / New features in the BW/4HANA 1.0 & 2.0 (BW-BCT-GEN)

8.1 Central Notes

The compability of BI_CONT/BI_CONT_XT in the BW system: 2500202 - S4TWL - BW Extractors in SAP S/4HANA[21]
2400585-Collective Note: SAP BW/4HANA Content 1.0 (BW4CONT 100 & BW4CONTB 100)
2785525-Collective Note: SAP BW/4HANA Content 2.0 (BW4CONT 200 & BW4CONTB 200)

8.2 FAQ Note

2785514-FAQ: SAP BW/4HANA Content (BW4CONT & BW4CONTB)

8.3 About the delivered objects

2395613 - SAP BW/4HANA Content - Additional information on delivered InfoObjects[23]

2395579 - SAP BW/4HANA Content - Additional information on delivered variables[24]
2397520 - SAP BW/4HANA Content - Differences to SAP HANA optimized BI Content delivered with BI CONT 7.57[25]

8.4 Online help

9 - Extractors in S/4HANA

9.1 How to find the relevant note

Search note by Title: SAP S/4HANA Restriction

9.2 Special issue about long length of Material number (Chat 40)

Search note by Title: material number S/4HANA, e.g.
(CA-FLE-MAT)2233100 - SAP S/4HANA: Material Number Field Length Extension: Restriction Note
(CA-FLE-MAT)2232362 - SAP S/4HANA: Material Number Field Length Extension in LIS: Restriction Note
(BW-BCT-MM-BW)2422224 - SAP S/4HANA Long Material number integration with SAP BW / SAP BW/4HANA

9.3 CDS views for extraction: dataExtraction: { enabled: true }

Only when there's the following highlight Annotation, the CDS view can be used for data extraction:
@Analytics: { dataCategory: #DIMENSION,     dataExtraction: { enabled: true } }

You could refer to 'How to display the CDS definition'.

If the standard CDS view is not extraction enabled, even appending the Annotation 'dataExtraction: { enabled: true }' won't work. As a workaround:

  1. For S/4HANA on-premise, you could create your own CDS view using the Annotation 'dataExtraction: { enabled: true }'
  2. For S/4HANA Cloud, custom CDS view extraction enable is NOT SUPPORTED at this moment.  Please see note 2724648-SAP S/4HANA Cloud 1902: Release Restriction Note:
    "Data Extraction: it is currently not allowed to use CDS views carrying the "@Analytics.dataExtraction.enabled:true" annotation for data extraction to SAP Business Warehouse and SAP BW/4HANA in a production system. Please see SAP Note 2674373 for more details."
    If customer requests a new functionality – to release some CDS views for data extraction, the usual procedure is the influence channel. This's your direct channel to our product management and they are the ones to decide which CDS views are to be enabled for extraction with priority. Maybe you'd prefer to report an incident under CA-GTF-EI (S/4HANA Extensibility and Integration), but they'll still suggest you the same channel.
  3. For both on-premise & Cloud, customer could report incident under the corresponding application component of the requested CDS view to ask for a similar CDS which's extraction enabled. E.g. I_GLAccountLineItemSemTag is not extraction enabled, then please report an incident under FI-GL-IS for an alternative extraction-enabled CDS view.

 

“Modeling – Enterprise Data Warehouse Layer – DataSource”, NetWeaver platform 7.3. Published on SAP Help

“Search and Operational Analytics – Operational Data Provisioning”, NetWeaver platform 7.3. Published on SAP Help

Operational Data Provisioning Published on SAP Help

Operational Data Provisioning - Troubleshooting

  • No labels