Questions and Answers

You set the rules in the source system: date ranges, company codes, business objects or org structures. SLaiCE then moves only that data to one or more target systems, under SAP’s standard business and security controls. Everything starts and runs from the source system.

It uses the security you’ve already set up in your SAP landscape: SAP authentication, authorisations and standard encryption. Nothing new to configure there.

SLaiCE doesn’t scan or classify data itself. It works with the SAP or third-party discovery and classification tools you already use, and follows the classifications and masking policies they set.

SLaiCE is SAP-approved for SAP ECC, SAP S/4HANA on-premise and SAP S/4HANA Private Cloud. If you have your own custom-code standards, we work with your technical team so SLaiCE passes your SAP ATC checks without critical findings. The patented core logic can’t be changed, but we’ll explain any limits and agree a workaround with you.

Yes. Each use case runs under its own profile, so a test-system refresh never gets in the way of your company-mandate or migration set-up. A test profile could be master data only, the last few years, or a single region or country.

Usually, nothing needs restarting. Depending on what went wrong, SLaiCE picks up where it stopped, a bit like resuming a paused download.

Standard control reports compare record counts in the source and target systems. If your auditors ask for more, extra reports can be built case by case, when mutually agreed.

SLaiCE runs on SAP tools, so you can switch on SAP’s standard alerting and monitoring.

For ongoing use cases like the company mandate (data residency), SLaiCE comes with an annual maintenance subscription. SAP releases updates every quarter; we hear about them in advance and ship fixes like any other SAP-approved add-on, and you choose when to apply them. New modules or add-ons in your system may need a few consulting hours to set up.

SLaiCE keeps the required data for your Indian entities in a live SAP system on servers in India, updated daily, with audit logs. That supports what the Companies Act and Income-tax Rule 46(8) ask for.

Usually not. The mandate expects records to be available in the same form they were entered in the original system, with audit logs. Exports to Excel, PDF or other files don’t meet that, and auditors can reject them.

DART pulls archived data into flat files for audits, and it isn’t available once you move from SAP ECC to SAP S/4HANA. SLaiCE works on live data and keeps it in a local SAP system.

In-house tools often load the production system and miss later corrections, like a journal entry fixed two months after posting. They usually need rewriting for new add-ons, and again when you move to SAP S/4HANA, and they give a small team wide access to financial data. SLaiCE runs in the background and handles all of this.

Usually not, as long as that system (including SAP S/4HANA Public or Private Cloud) is hosted in an Indian data centre. You still need daily backups, audit trails, audit logs and database logs set up and kept properly, because they aren’t on by default. Our people can guide your team, and SAP where it’s relevant.

It depends on your SAP version. On SAP ECC, the India system is a non-productive instance, so you don’t need extra licences. On SAP S/4HANA (RISE) it depends on your SAP contract: some customers run a read-only system in an SAP data centre in India, or use an India-based disaster-recovery system as the target to save on infrastructure.

Yes. We set up daily backups in a secure location with your infrastructure provider, including audit logs, audit trails and database redo logs, plus an automatic email with each backup’s start, finish and status. Our technical team can walk you through restoring to a specific past date.

Yes. It can keep the relevant SAP change history, including CDHDR and CDPOS records, so past changes are there for audit, compliance and statutory needs within the agreed scope.

Yes. We work with infrastructure partners who give SLaiCE customers special pricing. We can bring them into our scope as a managed service, or introduce you to them directly.

The biggest hurdle is how much data sits in SAP ECC. SLaiCE moves only the data you choose, say a specific period, which can cut a typical ~16–18 month migration to ~6–8 months.

SLaiCE keeps copying the selected data from your SAP ECC production system to an intermediate shell system that stays in sync. On the agreed date the copying stops, and the shell is converted to SAP S/4HANA with SAP’s own tools. If business events move the date, you just re-plan; nothing has to start over.

Yes. You can set filters on several fields across your SAP application, and SLaiCE knows the parent-child links between tables, so documents stay consistent.

Yes. It can move the relevant change history along with the business data, so the audit trail survives in SAP S/4HANA or in a carved-out business, within the agreed organisational, document or time scope.

Yes. With SLaiCE already installed, you can build a lean, read-only SAP ECC system for legal and audit needs. You can also load selected test data into new SAP S/4HANA development and quality systems for custom-code work and user training.

Yes. SLaiCE fully supports carving out CO documents with cross-company assignments.

Our team works alongside your SAP teams through the migration. Once it’s done, SLaiCE is removed from your landscape, unless you’d like to keep it for other use cases.