Skip to content

System Requirements

Comprehensive guide to SAP system requirements and compatibility for abap2xlsx.

Minimum System Requirements

SAP NetWeaver Version Support

SAP VersionSupport StatusInstallation MethodNotes
SAP NetWeaver 7.31+✅ Fully SupportedabapGit (recommended)Optimal performance and features
SAP NetWeaver 7.02-7.30⚠️ Limited SupportabapGit or SAPLinkMay require additional configuration
SAP NetWeaver < 7.02⚠️ Legacy SupportSAPLink onlydocs/SAPLink-installation.md:1-2
SAP NetWeaver 6.20⚠️ Special CaseManual modifications requiredRequires code patches

Technical Prerequisites

Core System Requirements

  • Unicode System: Recommended for proper character encoding
  • HTTPS Support: Required for abapGit GitHub connectivity
  • Memory: Minimum 100MB free for installation, more for large file processing
  • Developer Access: Package creation and modification rights

Required Function Modules

The following SAP function modules must be available:

abap
" Test system compatibility
REPORT ztest_system_compatibility.

START-OF-SELECTION.
  " Test required function modules
  CALL FUNCTION 'TRINT_SPLIT_FILE_AND_PATH'
    EXPORTING
      full_name = '/test/path/file.txt'
    IMPORTING
      stripped_name = DATA(lv_name)
      file_path = DATA(lv_path).
  
  WRITE: / 'TRINT_SPLIT_FILE_AND_PATH: Available'.
  
  " Test class availability
  DATA: lo_test TYPE REF TO cl_abap_zip.
  TRY.
      CREATE OBJECT lo_test.
      WRITE: / 'CL_ABAP_ZIP: Available'.
    CATCH cx_sy_create_object_error.
      WRITE: / 'CL_ABAP_ZIP: Not available - may need workarounds'.
  ENDTRY.

SAP Notes Requirements

Essential SAP Notes

Based on the FAQ documentation docs/FAQ.md:13-23, these SAP notes are required:

Document Processing Notes

  • SAP Note 1151257: Converting document content

    • Purpose: Enables proper Excel file generation with correct encoding
    • Impact: Without this note, Excel files may be corrupted or unreadable
    • Systems: All SAP systems using abap2xlsx
  • SAP Note 1151258: Error when sending Excel attachments

    • Purpose: Fixes email integration issues with Excel files
    • Impact: Email sending may fail when attaching Excel files
    • Systems: Systems using email functionality with Excel attachments

ABAP Language Support

  • SAP Note 1385713: SUBMIT parameter of type STRING
    • Purpose: Allows STRING parameters in SUBMIT statements
    • Impact: Demo programs may fail with runtime error DB036
    • Systems: All systems running abap2xlsx demo programs

Verification Script

abap
" Verify SAP notes implementation
REPORT zverify_sap_notes.

DATA: lv_test_string TYPE string VALUE 'test'.

START-OF-SELECTION.
  " Test Note 1385713 - STRING parameter support
  TRY.
      SUBMIT rsdemo01 WITH p_string = lv_test_string AND RETURN.
      WRITE: / 'Note 1385713: Implemented correctly'.
    CATCH cx_sy_submit_error.
      WRITE: / 'Note 1385713: May need implementation'.
  ENDTRY.
  
  " Test Note 1151257/1151258 - Document conversion
  DATA: lo_conv TYPE REF TO cl_bcs_convert.
  TRY.
      CREATE OBJECT lo_conv.
      WRITE: / 'Notes 1151257/1151258: Classes available'.
    CATCH cx_sy_create_object_error.
      WRITE: / 'Notes 1151257/1151258: Need implementation'.
  ENDTRY.

Version Compatibility Matrix

abap2xlsx Version Support

docs/FAQ.md:3-5 indicates that version tracking was introduced in version 7.0.1:

abap2xlsx VersionSAP NetWeaverKey FeaturesInstallation Notes
7.16.0 (Current)7.31+Full feature set, performance optimizationsRecommended version
7.15.07.31+Enhanced conditional formattingStable release
7.0.1+7.02+Version tracking introducedFirst versions with version detection
< 7.0.16.20+Legacy versionsNo automatic version detection

Feature Compatibility

FeatureSAP 7.31+SAP 7.02-7.30SAP < 7.02Notes
Basic Excel GenerationCore functionality
Excel Reading⚠️May need modifications
Large File SupportMemory limitations
Chart Generation⚠️Limited chart types
Conditional Formatting⚠️Basic support only
Template Processing⚠️May require workarounds

Performance Considerations

Memory Requirements

Use CaseMinimum RAMRecommended RAMNotes
Basic Reports100MB200MBSmall datasets (< 10,000 rows)
Large Reports500MB1GBMedium datasets (10,000-100,000 rows)
Huge Files1GB2GB+Large datasets (> 100,000 rows)
Multiple Users+200MB per user+500MB per userConcurrent processing

System Resources

abap
" Check system resources
REPORT zcheck_system_resources.

START-OF-SELECTION.
  " Check available memory
  CALL FUNCTION 'SYSTEM_MEMORY_INFO'
    IMPORTING
      memory_available = DATA(lv_memory).
  
  WRITE: / 'Available Memory:', lv_memory, 'bytes'.
  
  IF lv_memory < 100000000.  " Less than 100MB
    WRITE: / 'WARNING: Low memory may affect performance'.
  ENDIF.
  
  " Check system load
  CALL FUNCTION 'TH_SERVER_LIST'
    TABLES
      list = DATA(lt_servers).
  
  WRITE: / 'Active Servers:', lines( lt_servers ).

Installation Prerequisites

Development Environment

Required Transactions

  • SE80: ABAP Workbench (for manual installation)
  • SE11: ABAP Dictionary (for data type verification)
  • SM30: Table maintenance (for configuration)
  • ZABAPGIT: abapGit (for modern installation)

Package Requirements

  • Package Creation Rights: Ability to create development packages
  • Transport Management: Access to transport system (for productive installations)
  • Object Modification: Rights to create classes, interfaces, and programs

Network Requirements

For abapGit Installation

  • HTTPS Access: Connection to https://github.com
  • SSL Certificates: Valid certificates for GitHub API
  • Proxy Configuration: If behind corporate firewall
  • File System Access: Ability to download and upload nugget files
  • Local Storage: Temporary space for nugget files

Compatibility Testing

Pre-Installation Check

abap
" Comprehensive system compatibility check
REPORT zsystem_compatibility_check.

DATA: lv_version TYPE string,
      lv_unicode TYPE c,
      lv_release TYPE string.

START-OF-SELECTION.
  " Check SAP release
  CALL FUNCTION 'SYSTEM_GET_INFO'
    IMPORTING
      release = lv_release.
  
  WRITE: / 'SAP Release:', lv_release.
  
  " Check Unicode support
  CALL FUNCTION 'SYSTEM_GET_UNICODE'
    IMPORTING
      unicode = lv_unicode.
  
  IF lv_unicode = 'X'.
    WRITE: / 'Unicode: Supported'.
  ELSE.
    WRITE: / 'Unicode: Not supported - may cause issues'.
  ENDIF.
  
  " Check ABAP version
  DATA(lv_abap_release) = sy-saprl.
  WRITE: / 'ABAP Release:', lv_abap_release.
  
  " Recommendations based on release
  CASE lv_abap_release.
    WHEN '731' OR '740' OR '750' OR '751' OR '752' OR '753' OR '754' OR '755' OR '756' OR '757'.
      WRITE: / 'Recommendation: Use abapGit installation'.
    WHEN '702' OR '710' OR '711' OR '720' OR '730'.
      WRITE: / 'Recommendation: abapGit preferred, SAPLink as fallback'.
    WHEN OTHERS.
      WRITE: / 'Recommendation: Use SAPLink installation only'.
  ENDCASE.

Post-Installation Verification

After installation, verify system compatibility:

  1. Run Demo Checker: Execute ZDEMO_EXCEL_CHECKER
  2. Test Basic Functionality: Create simple Excel file
  3. Check Version: docs/FAQ.md:5 - Verify VERSION attribute in ZCL_EXCEL class
  4. Memory Test: Process sample data to check memory usage

Troubleshooting Compatibility Issues

Common Compatibility Problems

Older SAP Versions

  • Missing Classes: Some utility classes may not exist
  • Syntax Differences: Newer ABAP syntax may not be supported
  • Memory Limitations: Older systems may have stricter memory limits

Unicode Issues

  • Character Encoding: Non-Unicode systems may have encoding problems
  • Special Characters: International characters may not display correctly

Performance Issues

  • Memory Constraints: Insufficient memory for large files
  • CPU Limitations: Older hardware may struggle with complex operations

Getting Help

If you encounter compatibility issues:

  1. Check System Requirements: Verify your system meets minimum requirements
  2. Review SAP Notes: Ensure all required notes are implemented
  3. Test Incrementally: Start with simple examples before complex scenarios
  4. Community Support: Post questions on SAP Community with system details

Next Steps

After verifying system compatibility:

  1. Proceed with Installation: Follow the Installation Guide
  2. Start with Quick Start: Try the Quick Start Examples
  3. Explore Core Features: Review Basic Usage Guide