3750350 - Replication flows fail or hang at initial load partitioning with read_next_package error for SLT sources - SAP Datasphere

• Replication flows from an ABAP-based source via SLT to the target remain in status “Initial Load Partitioning (Retrying)” or fail during initial load.
• Error message: “Transferring initial data failed due to the following error: An exception was raised / API method IF_DHRDB_API_CONSUMER~READ_NEXT_PACKAGE failed; see the following messages for details: / Error by reading next package / Cannot read new entries from buffer table / The data object could not be created: The type does not exist.”

• SAP Datasphere

1. Create a Replication Flow.
2. Select the connection.
3. Choose the SLT system and a Mass Transfer ID.
4. Add the required source tables and map targets.
5. Deploy the Replication Flow.
6. Run the Replication Flow and observe that initial load fails or remains in “Initial Load Partitioning (Retrying)”.

Using SLT table more than 4 times (Mass Transfer IDs)

See 2325312 - Maximum of 4 configurations are permitted for a single source - SLT - SAP for Me

• Refer to: 3507856 - SAP Datasphere - ABAP Integration - Retention drops RDB table without read access
• Refer to: 3016862 - Note Analyzers with separated scenarios for ABAP-based Migration and Replication Technology
• Refer to: 3561074 - How should the note analyzer be used for SLT source, central, and target systems?
• Refer to: How to check relevant note corrections in On-premise ABAP-based systems for Data Flows and Replication Flows
• Refer to: Replication Flow for ABAP Tables from On-Premise to SAP Datasphere with SLT

replication flow, initial load partitioning retrying, read_next_package, IF_DHRDB_API_CONSUMER, cannot read new entries from buffer table, data object type does not exist, abap integration, slt, mass transfer id, abap source, initial load failure, datasphere replication, buffering table, replication error, slt notes , KBA , DS-DI-RF , Replication Flow Runtime , Problem