Purpose
This is trouble shooting guideline for all content concerning the data extraction.
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
(BW-BCT-MM-PUR) 3153996 - "Very high" priority is not justified for BW-PUR issues and LIS
2 - Important Tables and transactions
3 - General performance problems
3.1 Job itself takes a long time (probably BW-BCT*)
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' (see this demo)
- 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 -> Analyze -> may ask help from DB team.3.2 The data transferring takes a long time (probably BC-BW*)
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
When creating the secondary index, please use name starts with Z, e.g. Z1.
2520897-ODP package size and data load performance3.3 The update in BW side takes a long time (probably BW-WHM*)
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
4.1 Check movement type (for 2LIS_02/03 DataSource)
Is the movement type of material document statistic relevant:
If the value <> 2 the movement type is not statistic relevant, won't be extracted.
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)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 the application log in source system accordingly:
For Logistic DataSource: 1760322 - Activate log file for delta extraction, application 02, 03, 04, 08, 11, 12, 13
For FI-GL/EC-PCA DataSource: 1479732 - Use of log for FI-GL, FI-SL, and EC-PCA extractors
For CO-OM DataSource: 1370386 - Activating LOG table for error analysis of CO delta queue
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."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
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 ;
Log can be checked by TCode. NPRT ;
Setup table can be filled by the following transactions:Application (description) TCode Program DataSource Component 02-Purchasing OLI3BW RMCENEUA 2LIS_02_ITM/HDR/ACC/SCL BW-BCT-MM-PUR 03-Inventory(Stock Initialization) MCNB RMCBINIT_BW 2LIS_03_BX BW-BCT-MM-IM 03-Inventory(Material Movements) OLI1BW RMCBNEUA 2LIS_03_BF BW-BCT-MM-IM 03-Inventory(Revaluation) OLIZBW RMCBNERP 2LIS_03_UM BW-BCT-MM-IM 04-Shop Floor Information OLI4BW RMCFNEUA 2LIS_04_P_MATNR/2LIS_04_P_COMP/2LIS_04_P_ARBPL BW-BCT-PP-LIS 04-SF(Repetitive Manufacturing) OLIFBW RMCFNEUD 2LIS_04* BW-BCT-PP-PP 05-Quality Management OLIQBW RMCQNEBW 2LIS_05_Q0NOTIF/2LIS_05_QE1/2LIS_05_QE2 BW-BCT-QM 06-Invoice Verification OLI6BW RMCENEUR 2LIS_06_INV BW-BCT-MM-IV 08-LES Transportation VTBW VTRBWVIFBW 2LIS_08TRTLP BW-BCT-LE-TRA 08-LES Shipment Cost VIFBW VTRBWVIFBW 2LIS_08TRFKZ BW-BCT-LE-TRA 11-SD Sales Orders OLI7BW RMCVNEUA 2LIS_11_VA*/2LIS_11_VC* BW-BCT-SD-SLS 12-SU shipping OLI8BW RMCVNEUL 2LIS_12* BW-BCT-LE-SHP 13-SD Billing OLI9BW RMCVNEUF 2LIS_13* BW-BCT-SD-BIL 17-Plant Maintenance OLIIBW RMCINEBW 2LIS_17* BW-BCT-PM 18-Customer Service Management OLISBW RMCSNEBW 2LIS_18* BW-BCT-CS 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 and page:
How collective run works - SAP NetWeaver Business Warehouse - Support Wiki
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)
5.3 TCode & Source tables for LIS*
The TCodes here are used for reproducing delta missing issue.
DataSource TCodes Source tables 2LIS_02* ME21N, ME22N, ME23N EKKO,EKPO,EKET,EKBE 2LIS_03* MIGO, MIRO MSEG,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, VA03 VBAK,VBPA,VBKD,VBUP 2LIS_12* VL03N LIKP,LIPS,VBUP(rejection staus - ABSTA),VBUK,VBPA,VBFA 2LIS_13* VF01, VF02, VF03 VBRK,VBRP,KONV( V_KONV_CDS in S/4HANA ) 2LIS_17* IW33, IW32 QMFE,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
Also see page: EXIT_SAPLRSAP_001 and EXIT_SAPLEINS_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 BW-BCT-LE-SHP, 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.0 Central note about the delta logic
1012874-FAQ extractors 0FI_AP_* 0FI_AR_* 0FI_GL_* (except 0FI_GL_10, 0FI_GL_11, 0FI_GL_12, 0FI_GL_14)
BWFI_AEDAT , for 0FI_*_4 / 0fi_gl_14; (FUNCTION BWFIP_WRITE_AEDAT_POINTER)
BWFI_AEDA2 , for 0FI_*_6 / 0FI_*_7; (FUNCTION BWFI2P_WRITE_AEDA2_POINTER )
BWFI_AEDA3 , for 0FI_AR_8, 0FI_AR_9, 0FI_AR_10 (FUNCITON BWFI3P_WRITE_AEDA3_POINTER)
Common functions: FBW4_WRITE_CHANGE_QUEUE
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)
0FI_GL_6 extracts data from GLT0 which is a table in ECC but a view in S/4. It does not make sense to use 0FI_GL_6 in S/4 as New G/L is activated by default in S/4. You should be using datasources that extract New G/L totals and not classic one's. So please use 0FI_ACDOCA_20 which extracts totals from ACDOCA table. You could also 0FI_GL_12. You can refer to this note 2302508 for usage of 0FI_GL_12 in S/4.
Please go through both notes & check which will suit your requirement:
2341038 - Usage of datasources 0FI_ACDOCA_10 and 0FI_ACDOCA_20 in sFIN / S4HANA
2302508 - Usage of datasources 0FI_GL_10, 0FI_GL_14 in sFIN / S4HANA
(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
0FI_ACDOCA_10 -> Delta : PUSH (ROOSOURCE-DELTA = AIMD) -> After-Images with Deletion Flag Via Delta Queue (e.g. BtB) (PUSH)
0FI_ACDOCA_20 -> Delta : PULL (ROOSOURCE-DELTA = ADDD)
You can take a look at table ROOSOURCE to check for a DataSource which type of delta is associated to.
And then, in table RODELTAM, you can find the delta procedures and related properties. See delta type
###DELTA ###
For 0FI_ACDOCA_10, 0FI_ACDOCA_20, 0FI_GL_12 (or copies of them like e.g. 3FI_ACDOCA_10, 3FI_ACDOCA_20, 3FI_GL_xx_TT with delta mode 'AIMD' or 'ADDD'),
main functions:
>> FINS_ACDOCA_BW_UPD_DELTA_QUEUE / in FUGR FIS_ACDOCA_BIW
-- Calls RSC1_TRFC_QUEUE_WRITE to write DELTA queue
-- V1 update. Need Enable "Update Process" in debugger. Only by this, the breakpoint will be captured when posting the FI document.
>> G_BIW_WRITE_DELTA_ACDOCA_COMP / in FUGR GBIWDELTA_47
For 0FI_GL_10 (or generated 3FI_GL_xx_TT with delta mode AIED) or 0FI_GL_61
Data mismatch after delta extraction: issue often occurs due to parallel extraction with SAPI and ODP channel. It's the known problem and please read the implement the 2 notes below:
2508594 - FI-GL: Wrong BI data when using the ODQ delta extraction for 0FI_GL_10 or 0FI_GL_61
2831211 - 0FI_GL_10, 0FI_GL_61: Incorrect data extraction when using ODP delta extraction
Moreover, it is essential that:
- Both extraction channels are using the same field list. This can be achieved by settings the field property of non used fields to 'A' in RSA2.
- The remaining potential key fields match with key property in overwriting DSO in BW or ADSO in BW4. Make sure, you use the same key structures in both targets.
In principle, you can trigger SAPI & ODP extraction load at the same time, but it is not recommended, since it may lead to doubled extracted data, which is not necessary. Better to trigger them in sequence, when the other one has finished. Note, both delta queues are filled by both channels.
6.2 0FI_AP/AR_* DataSources
0FI_AP_4 BSIK BSAK
0FI_AR_4 BSID BSAD
delta will be protocoled 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
0FI_AP_30 - AIM, delta queue, push
6.3 0FI_*_6/7 DataSources
0FI_GL_* reads table GLT0 GLFUNCT
0FI_AP_* LFC1 LFC3
0FI_AR_* KNC1 KNC3
Delta will be protocoled 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 interval of loaded data
6.4 Global Settings for data extraction in table BWOM_SETTINGS
e.g. safety interval for data load
parameters:
BWFILOWLIM
BWFISAFETY
BWFIOVERLA
BWFITIMBOR
7 - BADI and User-Exits of extractors in R/3
7.0 Call sequence: BADI → BTE exit → Customer Exit(exit_saplrsap_001~004)
SAPLRSAP / LRSAPF06
FORM / CALL_DATA_CUSTOMER_FUNCTION
* Begin BADI <--------------------------------------------¹
* (only available for releases >= 6.20)
*-------------------------------------------*
PERFORM DATA_TRANSFORM IN PROGRAM RSAYBADI
...
* Call BTE-Exit <--------------------------------------------²
CALL FUNCTION BW_BTE_CALL_BW204010_E
...
* Call Customer-Exit <--------------------------------------------³
DESCRIBE TABLE P_T_DATA LINES L_LINES.
CALL CUSTOMER-FUNCTION '001' *-- EXIT_SAPLRSAP_001
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
In 6 METHOD, ALL Implementations in BADI RSU5_SAPI_BADI (including standard and Z*) will be looped. The implementation which contains the current datasource will be called finally. You can run transaction SE18 to check the BADI and its implementation.
7.2 BTE-Exit
BTE (Business Transaction Events ) is one of the enhancement technique available in SAP that can be used by SAP, third party vendor(partner) and customer.
The corresponding BTE for a transaction can be found using the function module BF_FUNCTIONS_FIND.
https://answers.sap.com/questions/10396951/use-of-bte.html
7.3 Customer-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'.
To know what CDS views have been released for data extraction, please check the online help.
If the standard CDS view is not extraction enabled, even appending the Annotation 'dataExtraction: { enabled: true }' won't work. As a workaround:
- For S/4HANA on-premise, you could create your own CDS view using the Annotation 'dataExtraction: { enabled: true }'
- 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.
--> You can find all the CDS views which're released for Data Extraction followed by this link: Discover CDS View Based Extractors from SAP S/4HANA Cloud - For both on-premise & Cloud, customer could report incident under the corresponding application component (rather than BC-BW-ODP) 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.
For more details about the Delta handling, please go through the blogs:
CDS based data extraction – Part I Overview
CDS based data extraction – Part II Delta Handling
9.4 The MAPPING between the release of S/4HANA and the S4CORE
Note 2236608 - Support Package levels of SAP S/4HANA ON-PREMISE installations/upgrades
SAP S/4HANA ON-PREMISE 1511 <--> S4CORE 100
SAP S/4HANA 1610 <--> S4CORE 101
SAP S/4HANA 1709 <--> S4CORE 102
SAP S/4HANA 1809 <--> S4CORE 103
SAP S/4HANA 1909 <--> S4CORE 104
SAP S/4HANA 2020 <--> S4CORE 105
SAP S/4HANA 2021 <--> S4CORE 106
10. Integration between BW and C4C/ByD
10.1 Component
Most of the issues are connection / basis / interface related errors. That’s something (e.g. configuration) between C4C and BW.
Technical errors where the connection check already does not work are not related to ODP. The technical connection is set up with transaction SOAMANAGER, which is not ODP. Also with other sporadic technical errors it’s usually other components.
For HTTP and SOAP connection issues, please try the following to judge the component:
- In the classic loading with RFC-connection, we have BC-MID-RFC and BC-BW/BC-BW-ODP.
- If something fails sporadically with the connection, we have the technical components BC-MID-RFC, BC-CST-GW or BC-NET.
- Transferring this to C4C and HTTP-connection, the business content component would be AP-RC-ANA. They are also familiar how to setup a connection and know some limitations (Internal KBA 2423752), but probably also don’t know all the causes for SOAP-errors and how to analyze them.
- For SOAP-connection or webservice errors, the technical component might be BC-ESI-WS-ABA or BC-NET.
10.2 Common issues
For supplement...
11. Generic Datasource
11.1 Lower limit & Upper limit
Note 2116914 - Safety interval of BW DataSource
And more details:
Delta Intervals / Safety Intervals - SAP NetWeaver Business Warehouse - Support Wiki