SAP Community - BW SAP HANA Data Warehousing

SQ01 dynamic date and time filters with timestamps

2025-09-24T08:22:03.316000+02:00

Hi,

SAP EWM tables often use timestamps (e.g. /SCWM/ORDIM_C).

Because of that I can't use dynamic date and time filter with SQ01 Queries.

Are there any possibilities to use dynamic date and time filters here?

Best regards

Jonas

How to Change the Subtitle of Created App Variants

2025-09-26T13:32:48.577000+02:00

Is there a way to change the subtitle of created App Variants?
Is the only option to recreate the App Variants and fix the subtitle?

How to call REORG_GENERATE with algorithm ID 14 (Check mode)?

2025-09-29T13:06:40.010000+02:00

Hi SAP Community,

according to https://help.sap.com/docs/SAP_HANA_PLATFORM/6b94445c94ae495c83a19646e7c3fd56/667bfd8f3adc47f8af4c753447e40693.html?locale=en-US the stored procedure REORG_GENERATE for HANA landscape distribution can be called with the algorithm ID 14 to check the current landscape against table placement rules.

I do not understand the optional parameters and their implications:
LEAVE_UNCHANGED_UNTOUCHED | KEEP_VALID | NO_SPLIT

What do they mean?

How would a call exactly look like? Is it for instance like this:

CALL REORG_GENERATE(14, 'LEAVE_UNCHANGED_UNTOUCHED');

And where would I find the results of the checks?

Best regards,

Philipp

Archive PGI issue

2025-10-09T16:03:08.321000+02:00

Is there any alternative ZPGI_REPORT T-code please suggest on this

Road map to get certified

2025-10-16T07:30:18.112000+02:00

Hello, I'm new SAP. I'm looking for information on which courses to take or to start with to get certified. I'm majoring in CS but still have not yet if programming, web dev, or IT I want to pursue. I've never heard of SAP until I was looking for a job the application mention 'knowledge SAP HANA' I believe what it said. Any recommendations will be greatly appreciated.

Replicate data from SAP BW into SAP HANA Cloud

2025-10-17T10:39:45.537000+02:00

Hi Experts,

I have a challenge to get the data from BW into SAP HANA.

Expectation is a real-time replication, which is later using in SAC as a chart.

Now - we did create a BW Query. However, when I try to replciate the query, I get a error. The error happens when I try to start the replication.

Appreciate your inputs on the following:

1. Best way to get data from BW into HANA Cloud View

2. Is it feasible to use BW Query for this purpose

3. If BW data is stored in InfoObjects/DSO/Info Provider etc. - Is it feasible to replicate them directly into HANA.

Regards,

Sharath

Assessment Ran after new journal was posted (assessment was not reversed)

2025-10-22T18:17:00.438000+02:00

Hi,

I posted an journal entry in April and ran assessments. I then realized the entry was incorrect and reversed the journal entry and reposted it. However, I did NOT reverse the Assessments I already ran first. Now, I have balances remaining on secondary cost elements which I cannot post to or clear. To complicate matters, we upgraded to S4/Hana in August, so our IT department doesn't want me to reverse the assessment now under S4 as they are worried it will cause further issues as that was not the version of SAP we had when I posted the entry/assessment back in April. Any ideas on how I can clear these secondary cost elements on a YTD basis?

Thank you!

Not able to find the data source in LBWE

2025-10-24T08:28:15.130000+02:00

Hello Experts,

Not able to find the LO Data sources in LBWE. Could you please find the below screen short and help me.

Regards,

Venkat.

SAP Datasphere - How to handle ERP connection mapping (DIX → QIX) when transporting Replication Flow

2025-11-04T09:15:51.789000+01:00

Hello Experts,

I’m working on a transport scenario for SAP Datasphere using SAP Cloud Transport Management (CTMS) between two BTP subaccounts:

DEV subaccount → contains SAP Datasphere connected to ERP DEV system (connection name: DIX)
QAS subaccount → contains SAP Datasphere connected to ERP QAS system (connection name: QIX)

In the DEV environment, I created a Replication Flow that extracts data from an ABAP CDS View in ERP DEV via the connection DIX.

When I export this Replication Flow from Datasphere DEV (using CTMS), the exported package seems to include the connection reference as well.
However, when I import the same transport package into the Datasphere QAS environment, I’m not sure how Datasphere handles the source connection — because in QAS, the ERP connection should point to QIX (ERP QAS), not DIX (ERP DEV).
My questions:

Does SAP Datasphere automatically detect and remap the connection from DIX → QIX during import?
(I assume no — since Datasphere does not have a logical system mapping concept like SAP BW.)
If not, is there any connection mapping mechanism similar to BDLS (logical system mapping) in SAP BW?
Is it possible to maintain a mapping configuration file (e.g., JSON) for connection replacement during import via CTMS?
What is the best practice for naming and managing ERP connections across DEV / QAS / PROD systems to ensure smooth transports?

Any documentation link or official guidance on connection mapping for Replication Flows in Datasphere would be highly appreciated.

Thank you!

SAP BW filtering with contains pattern

2025-11-17T21:17:03.544000+01:00

Dear collegues !
In SAP BW4/hana in a customer exit I would want to take the value from a variable take everything befure '-' and filter in another variable with * sign around it with the contains pattern.
In another world if my variable hold 23141424-001-A I would like to take the part *23141424* and filter with contains pattern in the another variable.

  Data: W_A_VAR_RANGE like LINE OF  I_T_VAR_RANGE,
      L_S_RANGE like LINE OF C_T_RANGE,
      searchText like W_A_VAR_RANGE-LOW,
      lv_result TYPE string .

CASE I_STEP.

when 1.
when 2.

   if  I_VNAM  =  'AQV_AMATERIAL_EOON'.
     Loop at I_T_VAR_RANGE into W_A_VAR_RANGE  where  VNAM = 'AQV_AMATERIAL_EOOI' and SIGN = 'I' and OPT = 'EQ' .
       SEARCHText = W_A_VAR_RANGE-LOW.
        SHIFT  SEARCHText LEFT DELETING LEADING '0'.

          SPLIT  SEARCHText AT '-' INTO lv_result DATA(lv_rest).
          clear searchtext.
          CONCATENATE '*' lv_result '*' into searchtext.
      W_A_VAR_RANGE-VNAM = 'AQV_AMATERIAL_EOON'.
       W_A_VAR_RANGE-OPT = 'CP'.
       W_A_VAR_RANGE-LOW = searchtext.
        MOVE-CORRESPONDING  W_A_VAR_RANGE to L_S_RANGE.
        append L_S_RANGE to c_t_range.

     endloop.

   endif.
endcase.
  endmethod.

The logic works fine but when I run the query it runs on an error.

As soon as I change the CP in the code to EQ the problem disappear.
Can it be that in customer exits the contains pattern cannot be used for filtering the query ?
If you could use it could you please give me an example code that it works with please ?
I am using customer exit variable with multiple single values, because I will have several values.

Any help taken kindly thank you

SAP Datasphere vs Others (GCP, Azure, etc) - Business Case ??

2025-11-18T12:04:32.731000+01:00

Dear all,

I hope you have a very nice day! Sorry for the long question below. I am trying to set up the context and get some other inputs than what I see at the moment.

I am currently working with a client trying to make his way in the great world of Data. Basically, the situation is that the core processes of a Business Area will run with SAP (target is 1 instance and not 3 as today, ECC for now, but S/4 in the near future), and other specific applications. The implementation of SAP involved the implementation of a BW on HANA system (Yes, I know...not the latest stuff). But instead of feeding the BW through regular datasource extractions, they leveraged an SLT system to be near real time for most of their reports sourcing data from their current various SAP landscape. So, they have "rebuilt" lots of calculation views to support their business users. They also have many front ends (BOBJ, PowerBI, Spotfire, and other specialized applications). The maturity of BI is still, not low, but more oriented on checking consistency, very operational and less strategic than it could be.

So we have : ECCs -> SLT -> HANA DB -> CalcViews -> Composite Providers (for managing authorizations)

They are at a stage of the implementation where the question has been raised to move to SAP Datasphere or to another data manager provider (something like Azure, GCP, Snowflake). The question is raised because they do not have only SAP data, and the overall group (other business areas are in the group) direction is to go to a non SAP landscape for data analytics.

The current exercise is to analyze the options, and choose the most long term viable one: staying with SAP analytics solutions, or moving away. In my current analysis, I am struggling because I don't find any "automatic" ways to convert/migrate the calculation views from BW on HANA directly to SAP Datasphere, provided by SAP.

I have found the HANACV2SQL software, but I would have had expected SAP to support that kind of scenario.

So, my question is : What could be the arguments to keep SAP Datasphere when:

what ever happens, you will need to convert using the same tool at the same costs ?
connectivity to front ends will be subject to reinstallation
row level security needs to be reimplemented
SAP Datasphere restricts "data replication" to other systems if the data is used for other applications.

I have been working in the SAP ecosystem for a long time, and the Analytics strategy has always been hard to implement with SAP. The 0 copy concepts and the sharing capabilities promoted by SAP Datasphere (even the partnerships with Snowflake and GCP) are not clear form my point of view. Even if the client is SAP Centric, you need dedicated resources on the technology, which could lead to higher costs...

Any arguments that you have seen promoting one side more than another ?

Thanks for reading and sharing 😉

Cheers

The Future of SAP: Latest Trends Shaping the Industry in 2025

2025-11-19T16:51:40.110000+01:00

The SAP landscape is evolving rapidly. Here are the trends every aspiring consultant should know about:

1. AI & Machine Learning

AI is embedded in SAP solutions today. Consultants who understand AI-driven automation are highly sought after.

2. Cloud-First Deployments

S/4HANA Cloud is becoming standard. Cloud expertise is now a premium skill.

3. Sustainability & ESG Reporting

Organizations need consultants to help achieve ESG compliance. New specialization = new opportunities.

4. Low-Code/No-Code Solutions

Configuration skills are more valuable than ever. Rapid implementation is the new standard.

5. Cybersecurity & Data Privacy

Security expertise commands top dollar. Every project requires privacy compliance.

6. Real-Time Analytics

Business intelligence consultants are in high demand. Data storytelling is critical.

7. Extended Supply Chain Networks

Supply chain visibility is booming. Consultants here are building thriving careers.

8. Agile Methodologies

Waterfall is out. Agile, iterative approaches are the new normal.

The Bottom Line

The most valuable consultants in 2025 will specialize in these emerging areas. Don't just follow trends—master one and differentiate yourself.

Which trend excites you most? Which area do you want to specialize in? Drop your thoughts in the comments below!

Let's grow together in this dynamic industry. What's your next move? # #SAP #Trends2025 #CareerGrowth #SAPConsulting #AI #CloudComputing #DigitalTransformation

0EMPLOYEE_ATTR & PA0000(CDS View) BW4HANA

2025-12-07T07:13:55.603000+01:00

hello All!

Could anyone assist me? I’m creating a CompositeProvider in Eclipse for BW/4HANA modeling. I need to filter records for Transfer Postings, so I applied the MASSN code Z7 in PA0000 to extract all transfer-posting cases. To retrieve the latest updated information, I’m joining these PERNRs with PA0001, applying the filter ENDDA = 31.12.9999, so I can get the corresponding PERSK and PERSG values for the most current records.

Since the PA0001 data is available through the standard InfoObject 0EMPLOYEE_ATTR, I use that to retrieve PERSG and PERSK. However, for PA0000, I created a custom DataSource with code to extract the required MASSN-based records.

define view ZCDS_PA0000_Z7 as select from pa0000

{

key concat( pernr, begda )as ZCONC_KEY_UNIQUE,

key pernr,

key begda,

// key endda,

massn

}

where

//massn = 'Z4'

//or

massn = 'Z7'

Here is the rephrased version in a clear and professional way:

I mapped the start date (BEGDA) field to the standard InfoObject 0VALIDFROM.
When I run the InfoObject independently, it works fine and returns accurate results.
However, when I combine it with 0EMPLOYEE_ATTR, the output becomes incorrect for the condition ENDDA = 31.12.9999.

Whether I use a left outer join or an inner join, the issue remains the same:

PA0000 gives 199 records (MASSN = Z7)
PA0001 / 0EMPLOYEE_ATTR gives 153 updated records
But in the CompositeProvider, it still shows 199 records instead of 153, even though 0EMPLOYEE_ATTR should return only the updated records.

I am not sure why this mismatch is happening, since 0EMPLOYEE_ATTR is supposed to provide only the latest active record with ENDDA = 31.12.9999.

Can SAP HANA Calculation Views be used in SAP BW on HANA (not BW/4HANA)?

2025-12-12T12:33:38.238000+01:00

Hi everyone,

I will soon start working with a new customer whose system landscape is based on SAP BW on HANA (classic BW 7.x, not BW/4HANA).

In this context, I would like to ask whether the usage of SAP HANA Calculation Views is technically supported in an SAP BW on HANA environment.

In some scenarios, I need the flexibility of SQL to handle complex queries, multiple joins, conditional calculations, and performance-critical logic. In such cases, is it possible to build the model using SAP HANA Calculation Views and then consume them in BW via Open ODS Views or CompositeProviders?

I am aware that SAP recommends ADSOs and CompositeProviders for core BW modeling; however, I would really appreciate it if you could provide some clarification on the technical support status, known limitations, and real-life usage of Calculation Views in BW on HANA systems.

An example taken from a BW/4HANA environment

Thank you in advance.

how to rectify the error document splitting: items for clearing 1810/2519000001/2025/001 not found

2025-12-28T11:17:06.447000+01:00

Hi gurus

how to rectify that issue i am posting with F-53 & F-44 through clearing i get the same error get 1810/2519000001/2025/001 not found i checked in document splitting also i think everthing is map but i canot resolve. kindly request guid me how to rectify the issue please.

Standard Table for Listing InfoObjects with Attribute and Text Master Data

2025-12-30T05:47:10.849000+01:00

Is there a standard table that provides a list of all InfoObjects with their attribute and text master data in the system?

Why Trading Firms Running SAP On‑Prem Need SAP Business Data Cloud Now

2026-01-01T21:38:40.372000+01:00

SAP Business Data Cloud (BDC) offers trading organizations a governed, cloud‑based data fabric that unifies on‑premise SAP trading systems (S/4HANA, BW/BW‑PCE) with non‑SAP and OT data to build reusable data products for business consumption, analytics, and AI.[1][2][3][4][5]

***

From siloed trading data to governed data products

Most trading firms run core processes on SAP S/4HANA and BW while capturing key operational technology (OT) and market data in non‑SAP platforms, files, or data lakes.[2][3][6]

Bringing these sources together usually means heavy ETL, point‑to‑point interfaces, and copies of price curves, positions, and risk metrics across BW cubes, SQL marts, and spreadsheets, raising both cost and risk.[2][7][8]

BDC replaces this pattern with a business data fabric where SAP and non‑SAP data remain in place or in low‑cost cloud storage, but are exposed as governed “data products” with shared semantics and lineage.[1][4][8][9]

For trading, this means structured products, positions, P&L, reference data, market curves, and even sensor/OT data can be modeled once and reused by risk, finance, compliance, and commercial teams.[3][4][5]

***

Business benefits for trading organizations

1. End‑to‑end trading insight
- BDC connects S/4HANA trading, BW positions, and non‑SAP feeds (exchanges, brokers, weather, IoT) into unified data products, providing a single, governed view of exposures, margins, and liquidity.[2][3][5]
- Federation and zero‑copy access avoid constant extraction of SAP data into external warehouses, so risk and P&L dashboards and predictive models stay closer to real time.[1][4][8]

2. Faster innovation with analytics and AI
- Predefined SAP‑managed data products shorten the path from SAP trading data to analytics, while native integration with Databricks and other platforms lets quants and data scientists build models on governed data, not ad‑hoc exports.[3][4][10]
- Output from AI/ML models (e.g., price forecasts, risk factors, credit scores) can be shared back as BDC data products and consumed by SAP Analytics Cloud, Insight Apps, or custom apps without rebuilding pipelines.[3][4][1]

3. Better governance and compliance
- A central catalog, ownership model, and lineage in BDC give auditors and regulators transparency into how key trading metrics (VaR, P&L, limits) are built and where they are used.[1][11][12]
- Consistent access control across SAP and non‑SAP domains reduces the proliferation of unmanaged extracts, helping with data protection and trade surveillance requirements.[1][5][8]

***

Cost benefits and TCO impact

For organizations already running S/4 and BW on‑premise, BDC primarily improves TCO through reduced integration, storage, and operations cost while opening room to decommission legacy tooling over time.[2][4][8][13]

- Less ETL and data duplication
- The fabric approach lets you virtualize SAP data and only persist what adds value (e.g., harmonized trading positions with third‑party data), cutting replication volumes and integration tool spend.[1][4][8][14]
- SAP cites substantial TCO savings versus DIY data fabrics because Datasphere/BDC bundles integration, modeling, and governance rather than forcing you to assemble and run multiple components yourself.[8][4][7]

- Optimized use of existing SAP BW and S/4 investments
- Reference architectures show how BW content can be translated into transformation flows and then exposed as BDC data products, allowing reuse instead of rebuild, and enabling gradual reduction of BW infrastructure.[2][3][15]
- Integration with SAP S/4HANA (including private cloud editions) is productized, so trading data can be transferred into BDC with less custom work than typical third‑party stacks.[16][1][5]

- Hybrid rather than “big bang”
- A hybrid data strategy lets you keep mission‑critical trading execution close to S/4HANA on‑premise while using BDC for analytics, reporting, and AI, limiting initial migration risk and smoothing spend over time.[17][6][18][13]
- Over the medium term, running analytics in BDC instead of parallel on‑premise warehouses and external BI stacks can shrink infrastructure and license footprints, reducing duplicated costs common in hybrid estates.[2][4][13]

***

Pros and cons of moving trading data to BDC

Pros
- Unified SAP + non‑SAP trading view with shared business semantics.[2][1][5][4]
- Stronger data products for risk, treasury, and front‑office teams, increasing trust and reuse.[3][11][12]
- Cloud‑scale analytics and AI on governed data instead of extracts.[4][10][19]
- Strategic roadmap for BW customers beyond classic on‑premise warehousing.[1][2][15]
Cons / risks
- Potential license and platform overlap if BW, external warehouses, and BDC all run without a decommissioning plan.[7][15][13]
- Need for new skills around data products, cloud security, and governance operating models.[4][20][18]
- Stronger dependence on cloud and vendor roadmaps, which must be balanced with latency, sovereignty, and regulatory constraints in some trading jurisdictions.[6][17][21]

***

#SAPBDC #BusinessDataCloud #SAP #S4HANA #SAPBW #TradingAnalytics #DataProducts #DataFabric #HybridCloud #SAPDatasphere #SAPAnalyticsCloud #FinancialMarkets #RiskManagement #DataStrategy #CloudMigration

Sap is oil and Gas

2026-01-14T10:18:07.994000+01:00

do anybody have materials or guides related to sap is oil and gas

Information request

2026-01-14T13:12:02.811000+01:00

We are planning an upgrade of our SAP BW NetWeaver 7.5 system which is currently running on SAP HANA 1.0 SPS12.
Our system landscape is as follows:

• SAP BW 7.5 Application Server running on Windows

• SAP HANA Database running on Linux
While running SAP Maintenance Planner for this system, the target database recommended is SAP HANA Database 2.0 SPS08 (Revision 89) for Linux.
We would like to confirm the following points from SAP:
Whether SAP HANA 2.0 SPS08 Rev. 89 is the correct and supported target version for BW NetWeaver 7.5 when upgrading from HANA 1.0 SPS12.
Whether the mixed OS landscape (Application Server on Windows and HANA Database on Linux) is fully supported for this upgrade scenario.
Whether the upgrade path using SUM with DMO (Database Migration Option) from HANA 1.0 to HANA 2.0 is the recommended and supported approach for this system.
Kindly confirm that the target selected by Maintenance Planner (HANA 2.0 SPS08 Rev. 89 on Linux) is the correct upgrade path for our BW 7.5 system so that we may proceed accordingly.
Your confirmation will help us finalize our upgrade plan.

Our BW system is running with SAP Kernel 7.49. Please confirm that Kernel 7.49 is fully supported for BW 7.5 on SAP HANA 2.0 SPS08, and that there is no conflict between PAM and the relevant SAP Notes for this kernel level.

Guidance Needed – Repartitioning HANA Table /BIC/FZIM_C12

2026-01-29T02:49:59.552000+01:00

We would like your guidance regarding repartitioning one of our large tables in SAP CAR on PERSON_NAME. The table /BIC/FZ*** is currently split into 4 partitions, and we are seeing that partition ID 4 contains approximately 1.7 billion records and is rapidly approaching the 2 billion record limit in PERSON_NAME. Due to this, we are considering repartitioning the table, however we are not sure what the correct partitioning strategy should be.

At present, the table is partitioned using two layers: Round-Robin as the first layer and Range partitioning as the second layer based on the column KEY_*** (ranges 0,1,2). The data distribution appears to be highly skewed, with most records in partition 4 and significantly fewer in the other partitions (partition 1 being the smallest), so we are unsure whether the partitioning was originally done correctly and whether this strategy is appropriate for this table going forward.

We have reviewed SAP Notes such as DIGITS (BW-related) and DIGITS (general PERSON_NAME partitioning recommendations), and we are looking for a recommendation similar to the table-specific guidance mentioned in Question 27 of SAP Note DIGITS where the partition method and column are clearly defined for specific tables.

Could you please advise whether there are any table-specific recommendations for how /BIC/FZ*** should be partitioned, and what partition method and key column(s) would be best to avoid future growth issues?

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.