• home
  • What we do
  • Who We Are
    • About Us
    • Leadership
  • Careers
  • Newsroom
  • More
    • home
    • What we do
    • Who We Are
      • About Us
      • Leadership
    • Careers
    • Newsroom
  • home
  • What we do
  • Who We Are
    • About Us
    • Leadership
  • Careers
  • Newsroom

Problem Statement

A problem statement in an SAP Archival project is crucial. It provides clear focus, aligns stakeholders, guides resource allocation, directs solution development, and establishes success metrics, ensuring the project addresses the core issues efficiently and effectively. 


User Perspective -

  • Slow Archive Data Retrieval.
  • No response when searching the fields Without an Archive server index.
  • It's cumbersome to search the archive using a transaction code that differs from the usual one.

Admin Perspective-

  • Possibility of Human error during archiving.
  • Archive server indexing required increased software as well as hardware management.
  • File loss and change issues.

High Cost 

Solution Strategy

ANALYSIS & REQUIREMENT DEFINITION

 

In an SAP archival project, defining requirements is crucial for delineating the project’s scope, ensuring compliance, managing costs, tailoring the solution to specific business needs, allocating resources efficiently, setting performance benchmarks, mitigating risks, facilitating user acceptance, enhancing operational efficiency, and planning for future scalability.

Implementation Model

We did archiving utilizing SARA to meet the requirements and the retrieval speed was increased substantially. 

Process in flowchart

The Data that was archived using the standard method was transformed into compressed data and merged with the new archive data. This allowed for quick searches on SAP interface without any additional software development.

We do not just state the benefits reaped by the client via qualitative descriptions but also quantify their gains.


Data Extraction after Go-Live

  1. Using a Data Dictionary, a kind of catalogue of the tables and fields contained in the SAP® system, we specified the necessary data for request. This “list“ of data was customized to meet requirements by filtering tables and their content to get exactly the data needed for auditing purposes. For instance, data was filtered by selecting a specific period or company code. 
  2. We were also able to define joins for the tables selected to combine the data required for your auditing purposes beforehand. 
  3. Additionally, we could provide the data as per the format specified by them.
  4. We used SmartExporter which enabled us to extract exactly the data from SAP® they required for their analyses. At the same time the extracted data could be used in other auditing software like Microsoft® Excel where they can be edited and analyzed immediately after extraction.
  5. To protect sensitive data, we used components with specific transactions which enable SAP® administrators to define Data Privacy profiles using the specific transaction and assign them to users or roles. This way using pseudonymization or anonymization data are encrypted on the SAP® system even before extraction and the SAP® administrator has full control of the implementation. 
  6. Using the asynchronous export, we were able to specify the exact time when the data transfer was to be done. This enabled us to schedule the extraction of data to off-peak hours to reduce the workload of the system. Depending on their objectives and the data volume, we could select the suitable method of data extraction. 

Copyright © 2024 Avoquado - All Rights Reserved.


Software Services by CURIOUSNSMART Private Limited 


This website uses cookies.

We use cookies to analyze website traffic and optimize your website experience. By accepting our use of cookies, your data will be aggregated with all other user data.

Accept