IDOC Integration Enhancements for ERP Canvas

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 2 min. de leitura
  • THIS IS AN EXPRIMENTAL TEST TOPIC CREATED BY AI AND NOT EDITED OR REVIEWED - IT SHOULD NEVER BE MADE PUBLIC! This concept topic outlines the key requirements and features for enhancing ERP Canvas to support IDOC-based integrations with SAP.

    The following enhancements are designed to improve the IDOC integration capabilities within ERP Canvas, making it more robust and user-friendly for SAP integrations.

    IDOC Creation and Management

    • Enable the creation of IDOCs in the underlying SAP system.
    • Enhance the Monitor to include IDOC information with reference to the Async Queue.
    • Implement a new Async Queue specifically for IDOCs.

    UI Components

    • Create a table component to display segment fields, with mandatory fields checked by default.
    • Allow users to select all fields at once using a checkbox.
    • Display the hierarchy of IDOC segments and their fields in a tabular format.
    • Provide options to select and display segment fields.
    • Ensure the ability to sort fields in the list view based on fieldPosition.
    • Include a UI component to display IDoc segments in a tab view with search functionality.
    • Allow users to remove saved segments and fields.

    Model Manager

    • Enable the Model Manager to map input/output to IDOC segments.
    • Validate the user's ability to create and save the payload structure required for IDOC operations.
    • Ensure that the payload contains all mandatory and optional segments added in the model.
    • Support the creation and validation of payload structures for IDoc operations.

    Monitoring and Status Tracking

    • Display the IDOC retrieval status on the ribbon of the system_details page with color-coded indicators: grey for not started, blue for retrieving started or indexing data, green for completed, and red for error indexing/retrieving.
    • Show IDOC transaction logs in read-only mode with appropriate field restrictions via messages.

    Partner Profiles

    • Display a comprehensive list of all existing outbound configurations for IDoc extractions on the Partner profile page, including Configuration Name/ID, Target System, IDoc Type, Creation Date, and Last Modified Date.
    • Ensure the Partner profiles tab appears on the system details page, showing relevant partner information.
    • Provide a Partner refetch button on the system page with a functioning REST endpoint and appropriate alerts.

    End-to-End Testing

    • Validate the user's ability to create and configure the payload structure required for IDoc via the Model Manager.
    • Confirm that the system returns an IOC number for both create and update operations when 'Use ERP data' is called.
    • Verify that saved segments and fields are displayed correctly in the UI.
    • Ensure the tree structure updates appropriately after deletion of segments or fields.\\
    UI Component Description
    Table Component Displays segment fields with mandatory fields checked by default.
    Checkbox Allows users to select all fields at once.
    Tabular Format Shows the hierarchy of IDOC segments and their fields.
    Options for Selection Provides options to select and display segment fields.
    Sorting Enables sorting fields in the list view based on fieldPosition.
    Tab View with Search Includes a UI component to display IDoc segments in a tab view with search functionality.
    Remove Saved Segments and Fields Allows users to remove saved segments and fields.
    Ribbon on system_details Page Displays IDOC retrieval status with color-coded indicators.
    Transaction Logs Shows IDOC transaction logs in read-only mode with field restrictions.
    Partner Profile Page Lists all existing outbound configurations for IDoc extractions.
    Partner Profiles Tab Appears on the system details page, showing relevant partner information.
    Partner Refetch Button Provides a button on the system page with a functioning REST endpoint and appropriate alerts.