A live connection that already feeds analytic stories is not automatically a planning connection. In SAP Analytics Cloud, planning models have a narrower connectivity matrix than analytic models. Write-back, versions, data actions, allocations and currency conversion only exist on the paths SAP actually supports. The usual failure is not a missing mapping. It is trying to plan on a connection type that was never allowed to write.
Cipher implements SAP Analytics Cloud, including planning models. We do not implement or resell the ERP underneath. The ERP remains a source. This article is the requirements, the two valid paths, and the checks that matter when Publish still does nothing.
What are SAC planning model connectivity requirements?
SAC planning model connectivity requirements are the license, the model type, and the connection type. You need a planning license, a model created as planning from the start, and either an import connection into native SAC planning or a live BPC connection on an input-ready query. A BI-only tenant cannot create planning models.
Those three gates fail independently. Passing one does not pass the others. A Planning Professional user still cannot put native data actions on a live CDS view. An import connection still cannot write back if the model was created as analytic. A live BPC connection still cannot be created if nobody on the tenant holds a Planning Professional license.
The environment, stated as requirements
This is not one customer tenant. It is the stack that has to be true before any of the numbered steps below will work. License features below follow SAP Help for SAP Analytics Cloud 2023.20, "Features by License Type for Planning Models." Check your own wave against current Help if a later quarterly release has moved a cell.
| Layer | What has to be true |
|---|---|
| SAC license | Planning standard or professional. BI-only users can view planning models and work on private versions. They cannot create planning models, run data actions, or establish a BPC connection. |
| BPC connection | At least one Planning Professional user is required to create the connection from SAC to BPC. That is a license gate, not a missing menu. |
| Model type | Created as a planning model from the start. Converting an analytic live model later does not give you native SAC planning on that live connection. |
| Native SAC planning | Import (acquired) data. Versions, data actions, allocations and native currency conversion store plan data in SAC. |
| Live write-back | BPC embedded on SAP BW or SAP BW/4HANA, with an input-ready query. Plan data writes back through the BPC planning engine, not into SAC. |
| BW version | Live connectivity depends on the BW support package. Confirm against SAP Note 2715030. Usage restrictions: SAP Note 2788384. BPC runtime license: SAP Note 3150518. |
| On-premise live | InA services enabled, HTTPS, and either CORS for a direct connection or SAP BTP Cloud Connector for a tunnel. |
If a row above is not true, skip the how-to and fix that row. The steps will reproduce the same greyed-out control you already have.
Why can't I create a SAC planning model on a live connection?
Most live connections in SAP Analytics Cloud are read-only. Native SAC planning stores versions, data actions and currency conversion inside SAC, which requires imported data. Live planning exists, but it uses the source system's planning engine, usually BPC embedded on BW or BW/4HANA. A live CDS view that already feeds an analytic story is not a planning model.
That is the question the existing data acquisition vs live connection article does not answer. Import versus live is the first fork. Planning versus analytic is the second. You can choose live and still have no path to write-back.
The same confusion shows up as "SAC Planning live data connection to S/4" and "can I create a planning model on a CDS view." For native SAC planning features, the answer on a live S/4 CDS view is no. Live write-back is a BPC-embedded architecture, not a property of every SAP live connection.
What is the difference between an analytic model and a planning model in SAC?
An analytic model in SAP Analytics Cloud is read-only analysis. A planning model adds write-back: versions, data entry, data actions, allocations and currency conversion. Analytic models can use many live connections. Planning models cannot. Native SAC planning features run on imported data. Live write-back uses a BPC embedded model, not a converted analytic model.
| What you need | Analytic model | Native SAC planning (import) | Live BPC planning |
|---|---|---|---|
| Live BW, HANA, S/4, Universe, SQL | Yes, as a live analytic model | No. Import the data instead | No. Those connectors are not BPC live |
| Data entry and public versions | No | Yes, stored in SAC | Yes, stored in BW/BPC |
| Data actions, allocations, native currency conversion | No | Yes | No. Use BPC planning sequences and the BW currency model |
| Write-back to the source | No | Only if you add a separate export | Yes, through the input-ready query |
| License to create the model or BPC connection | BI can create analytic models | Planning professional to create planning models | Planning professional to establish the BPC connection |
Keep the two model types out of one story unless you have a documented reason. Blending a live analytic model with an imported planning model is how numbers stop agreeing in the monthly review.
How do you connect SAP BW to a SAC planning model?
To connect SAP BW to a SAC planning model for write-back, expose an input-ready query through BPC embedded, create a live SAP BPC connection in SAC, and build a live data model on that query. Data writes back through the BPC engine. At least one Planning Professional license is required to create that connection.
This is also the path for SAP BW/4HANA. Pointing a standard SAP BW live connection at a CompositeProvider gives you an analytic model. It does not give you planning.
On the BW / BPC side
- Confirm BPC embedded is in the landscape, not only BW reporting. Without BPC, there is no live write-back path into SAC planning.
- Build or reuse a HANA CompositeProvider, an aggregation level, and an input-ready query. The query must contain a measure. A display query will not accept data entry from SAC.
- In BPC, create the environment and the model that expose that query.
- Enable InA on the ABAP front end. Live SAC connectivity talks InA, not RFC.
- Choose the network path: CORS on the BW system for a direct connection, or SAP BTP Cloud Connector for a tunnel if users are outside the corporate network.
- Confirm the BW support package against SAP Note 2715030 before you debug SAC. A down-level BW stack fails with SAC errors that name the tenant, not the support package.
In SAP Analytics Cloud
- Confirm a Planning Professional user exists. That user creates the connection. Standard planning users can then enter data and run planning sequences on it.
- Go to Connections, expand Connect to Live Data, and choose SAP BPC. Enter host, HTTPS port, client, and the authentication method (user and password, or SAML SSO if trust is already in place).
- Create a live data model. System type is SAP BPC. Select the connection, the BPC environment, the BPC model, and the input-ready query. One SAC model is one query. A second query is a second model.
- If the source has Actuals, Budget, Plan or Forecast in a version column, map that column to version categories before you save.
- Build the story on a table, not a chart. Data entry in live BPC planning is a table. Planning sequences are added as BPC Planning Sequence triggers, not as SAC data actions.
The gotcha: each SAC model is one query. Teams that built one analytic live model on a wide CompositeProvider expect one planning model to do the same job. It will not. You split the input-ready queries, then you split the SAC models.
How do you build a native SAC planning model on imported data?
Create a planning model from the start, not by converting an analytic model later. Use an import connection, map a Version dimension, and keep write-back inside SAP Analytics Cloud. Data actions, allocations and native currency conversion need this path. Schedule the import so actuals stay current. Export separately if the source also needs the plan.
Use this path when you want SAC to be the planning engine: driver-based models, allocations, value driver trees, native currency conversion, and a calendar of planning tasks. The financial forecasting software problem is usually this one. Actuals come from ERP or BW. The plan lives in SAC. The two have to be reconciled on purpose.
- Confirm the tenant has planning licenses, not only BI. Creating a planning model is a Planning Professional action on the 2023.20 license matrix.
- Create an import connection to the source (SAP BW, S/4, file, or another supported acquired source). This is data acquisition, not live.
- In the Modeler, create a new planning model from that acquired data. Do not start from a live data model and hope to switch it later.
- Map Account, Time, and Version. Planning without a Version dimension is how actuals and plan overwrite each other.
- If you need currency conversion, create the currency conversion table against this planning model. That table does not exist on analytic models.
- Build data actions for copies, allocations and driver calculations. These run in SAC, on the imported data.
- Schedule the import so actuals refresh. Plan versions stay in SAC. They are not live against the ERP.
- If BW or S/4 also needs the approved plan, add an export. Write-back is not implied by the import connection.
The gotcha: import feels like a downgrade if the analytic dashboards are already live. It is the price of native SAC planning. Mixing a live analytic model and an imported planning model in the same story without a documented join is how forecast and actuals disagree by a day, a filter, or a currency.
A later path, seamless planning with SAP Datasphere, stores the planning model outside the SAC tenant. It is real, and it is not this walkthrough. Do not treat a Datasphere live view as a substitute for the BPC or import steps above unless that architecture was designed on purpose.
Why is currency conversion missing in my SAC model?
Currency conversion in SAP Analytics Cloud is a planning-model feature. Analytic models have no currency conversion table. Creating or editing that table needs a planning standard or professional license. If the model is analytic, or the user is BI-only, the option is missing for those reasons, not because the rate file failed to load.
BI users can view converted values in reports. They cannot create or edit the table. If the model is a live BPC model, currency conversion belongs in BW, not in a SAC currency table. Looking for the SAC table on a BPC live model is the wrong engine.
What do you check when the SAC planning connection still fails?
Check the license first, then the model type, then the connection type. BI-only users cannot create planning models. Analytic live models cannot take native data actions. BPC live needs InA, CORS or a Cloud Connector tunnel, and an input-ready query. If those three match and publish still does nothing, the user can simulate but cannot publish.
- License. Can this user create a planning model at all? If Create Planning Model is missing, it is not a connection problem. Check Planning Professional versus standard versus BI. The BPC connection itself needs at least one Professional user on the tenant.
- Model type. Open the model. If it is analytic, stop. You will not get native data actions or a currency conversion table by adding a live connection to it.
- Connection type. SAP BW live, SAP HANA live, S/4 live and Universe live are analytic paths. SAP BPC live is the write-back path. Import is the native SAC planning path. Pick one. Do not stack them on the same model.
- Query. For BPC live, the source must be input-ready. A reporting query explains a model that opens and then rejects every save.
- Network. Direct connections fail on CORS and HTTPS. Tunnel connections fail on Cloud Connector trust and the "allow live data to leave my network" switch. Test with a trivial analytic live model on the same host before you debug planning.
- Publish versus simulate. On BPC live, a BI user can simulate and cannot publish back to BPC. A standard planning user can enter data and run planning sequences. If Publish is dead and simulation works, look at the license before you rebuild the query.
- BW version. If SAC errors mention the tenant and BW is down-level, read SAP Note 2715030 before you open an incident on the SAC side.
If it still fails after those seven, the next move is not another connection type. It is to write down the license, the model type, the connection type, the BW support package, and the exact control that is greyed out, then treat it as a stack problem. Cipher's SAC work is this stack: the model, the connection, and the planning process that has to survive both.
The other direction, getting data out of SAC into HANA, is a different pipeline. That walkthrough is extracting SAP Analytics Cloud data to HANA with Smart Data Integration. For the warehouse sitting under many of these live connections, see SAP BW.