Abhinav Jain
Independent Researcher, Pennsylvania, USA

Published : 2 Documents Claim Missing Document
Claim Missing Document
Check
Articles

Found 2 Documents
Search

From Custom Code Inventory to Clean Core: CORE-Fit—A Portfolio-Level Methodology for Rationalizing ERP Extensions in SAP S/4HANA Abhinav Jain
The Eastasouth Journal of Information System and Computer Science Vol. 3 No. 01 (2025): The Eastasouth Journal of Information System and Computer Science (ESISCS)
Publisher : Eastasouth Institute

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.58812/esiscs.v3i01.1245

Abstract

Enterprise resource planning (ERP) modernization increasingly requires organizations to reconcile two competing objectives: preserving business-specific capabilities and reducing the lifecycle burden created by tightly coupled custom code. Clean Core addresses this tension through fit-to-standard processes, governed extensibility, stable interfaces, and deliberate placement of capabilities inside or outside the transactional ERP core. This paper introduces CORE-Fit (Customization Optimization, Rationalization, and Extensibility Fit), a design-science methodology proposed in this study for rationalizing inherited ERP customizations into five disposition paths: retire or standardize, key-user extension, on-stack developer extension, side-by-side extension, or governed exception and remediation. The underlying principles and related SAP approaches to custom-code rationalization and extension design were already established; CORE-Fit does not claim novelty for retirement, fit-to-standard, or extension technology selection as individual concepts. Its contribution is the specific six-stage portfolio-level decision artifact that integrates business-need validation, standard-fit analysis, transaction and data proximity, lifecycle independence, integration and economic/operational fit, and governance into five explicit disposition outcomes. CORE-Fit is evaluated using an anonymized customer-system assessment of 121 RICEF objects. The resulting disposition comprised 22 objects (18.2%) retired or standardized, 11 (9.1%) classified as key-user extensions, 73 (60.3%) as on-stack developer extensions, 15 (12.4%) as side-by-side extensions, and none as governed exceptions. The results illustrate that Clean Core rationalization need not equate to aggressive externalization: in this portfolio, most surviving requirements remained close to the transactional core through governed developer extensibility. The study presents a case-evaluated methodology for applying these criteria consistently across a legacy customization portfolio.
The Role of SAP Business Technology Platform in the Intelligent Enterprise: Developing and Applying an Intelligent Enterprise Capability Framework Abhinav Jain
The Eastasouth Journal of Information System and Computer Science Vol. 1 No. 02 (2023): The Eastasouth Journal of Information System and Computer Science (ESISCS)
Publisher : Eastasouth Institute

Show Abstract | Download Original | Original Source | Check in Google Scholar | DOI: 10.58812/esiscs.v1i02.1288

Abstract

The rapid digitalization of enterprises has increased organizational dependence on cloud applications, distributed data, application programming interfaces, automation, and artificial intelligence. The COVID-19 pandemic accelerated this transition but also intensified a persistent architectural problem: digital capabilities frequently become fragmented when introduced as independent technologies. The challenge facing enterprises today is therefore shifting from digital adoption toward the integration and coordination of digital capabilities. This study examines SAP Business Technology Platform (SAP BTP) as an architectural foundation for the Intelligent Enterprise. Drawing on research in digital transformation, enterprise architecture, and digital-platform ecosystems, the paper proposes the Intelligent Enterprise Capability Framework (IECF). The framework evaluates five enterprise capabilities: Connectivity, Adaptability, Context, Execution, and Intelligence. To make the framework evaluative rather than purely descriptive, each capability is assessed using three predefined criteria: implementation maturity, breadth of deployment, and strength of documented outcome evidence. The framework is applied to three evidence sets: an SAP-sponsored IDC study of nine SAP BTP customers, Maersk's documented BTP implementation, and Hitachi High-Tech's side-by-side extensibility program. The resulting overall IECF scores are 3.93 for the IDC sample, 3.67 for Maersk, and 3.73 for Hitachi High-Tech on a five-point scale. All three exceed the study's exploratory threshold of 3.5 for meaningful demonstrated platform value, producing an aggregate score of 3.78. The analysis further shows that platform value is realized through different capability profiles: IDC demonstrates stronger Context and Execution outcomes, Maersk demonstrates strong cross-system Connectivity and capability coordination, while Hitachi High-Tech demonstrates particularly strong Adaptability and ERP-core decoupling. The study contributes a capability-centric method for evaluating enterprise technology platforms and argues that an Intelligent Enterprise should be understood not as the implementation of an individual technology but as an architectural capability created when systems, data, applications, automation, and intelligence operate together.