PL

AMAA

Custom code for S/4HANA

Custom ABAP analysis ahead of an ECC to S/4HANA conversion. It finds what will not carry over, and writes the technical documentation nobody kept.

In production
The challenge

SAP ends mainstream maintenance for ECC in 2027, with paid extension to 2030. The hardest part of a conversion is neither the database nor the infrastructure — it is custom code: hundreds or thousands of undocumented objects, written by people who left years ago. Manual compatibility assessment takes weeks and still misses things.

How it works
  1. Integration layer

    A secure connection to the ECC system over VPN or Direct Connect. Nothing gets installed on the SAP side.

  2. Code analyzer

    The engine assesses object compatibility with S/4HANA against SAP’s simplification database and known conversion patterns.

  3. AI documentation

    An Amazon Bedrock module documents function modules, reports, enhancements and user exits. The project stops being a black box.

  4. Recommendations

    Every object comes back with a decision: carry over, adapt, or retire.

What it runs on
  • Bedrock
  • Lambda
  • Step Functions
  • S3
  • RDS
  • Cognito
  • Amplify