📋

Description

Error 1299, ERR_SQLSCRIPT_NO_DATA_FOUND, indicates that a database query or SQLScript procedure executed within SAP S/4HANA did not return any records, even though data was expected. This typically occurs when reports, transactions, or custom applications attempt to retrieve information that either does not exist or does not match the specified selection criteria.

💬

Error Message

ERR_SQLSCRIPT_NO_DATA_FOUND

🔍

Known Causes

4 known causes

⚠️

Incorrect Selection Criteria

The filters or parameters used in the report, transaction, or query are too restrictive or do not correspond to any existing data in the system.

⚠️

Missing Master/Transactional Data

The expected master data or transactional records have not been created in SAP S/4HANA or are missing for the specific parameters used in the data retrieval.

⚠️

Archived or Deleted Data

The data that the system is attempting to retrieve may have been moved to an archive, purged, or permanently deleted from the active database tables.

⚠️

Flawed Custom Logic

Custom SQLScript, ABAP code, or a view definition contains a logical error that causes it to incorrectly filter or fail to retrieve existing data from the database.

🛠️

Solutions

3 solutions available

1. Verify Data Existence in Target Table easy

Confirm that the data expected by the SQLScript actually exists in the database table.

1

Identify the specific SQLScript or report that is generating the error. This might involve checking transaction logs, application error messages, or debugger output.

text

2

Determine the target table(s) and the filtering conditions (WHERE clause) used within the SQLScript to retrieve data.

text

3

Execute a direct SQL query against the identified table(s) using the same filtering conditions to check for the presence of data. Replace `your_table_name` and `your_condition` with actual values.

SELECT COUNT(*) FROM your_table_name WHERE your_condition;

4

If the count is zero, the 'NO_DATA_FOUND' error is expected. Investigate why the data is missing. This could be due to incorrect input parameters, data corruption, or a logic error in a preceding process that should have populated the table.

text

2. Adjust SQLScript Logic for Empty Result Sets medium

Modify the SQLScript to gracefully handle scenarios where no data is found.

1

Locate the SQLScript that is failing. This could be a stored procedure, a table function, or an inline SQL statement used within an ABAP program or other S/4HANA component.

text

2

Wrap the data retrieval part of the SQLScript in a structure that checks for the existence of data before proceeding. A common pattern is to use a `CURSOR` and check its state or to use a `SELECT INTO` statement within an exception handler.

BEGIN
  DECLARE v_count INT;
  SELECT COUNT(*) INTO v_count FROM your_table_name WHERE your_condition;

  IF v_count = 0 THEN
    -- Handle the case where no data is found, e.g., return an empty result set or a specific indicator.
    -- Example: RETURN ''; -- Or return a specific structure with default values
    RETURN ROW ''; -- Example for returning an empty row
  ELSE
    -- Proceed with data retrieval and return the data
    RETURN SELECT * FROM your_table_name WHERE your_condition;
  END IF;
END;

3

Alternatively, for `SELECT INTO` statements that might fail, use an exception handler. This is particularly useful if the SQLScript is expecting exactly one row.

BEGIN
  DECLARE v_column1 VARCHAR(100);
  DECLARE v_column2 INT;

  BEGIN
    -- Attempt to select data into variables
    SELECT column1, column2 INTO v_column1, v_column2 FROM your_table_name WHERE your_condition;
    -- Process the retrieved data...
  EXCEPTION
    WHEN NO_DATA_FOUND THEN
      -- Handle the absence of data. This could involve setting default values or raising a different, more informative error.
      -- Example: v_column1 := 'N/A'; v_column2 := 0;
      RAISE EXCEPTION TYPE cx_sy_open_sql_db MESSAGE 'Specific data not found for the given criteria.' WITH TEXT = 'Error 1299: No data found.';
  END;
END;

4

Test the modified SQLScript thoroughly with various input parameters, including those that are known to produce no data, to ensure it behaves as expected.

text

3. Review and Correct Input Parameters medium

Ensure that the parameters passed to the SQLScript are accurate and will yield data.

1

Identify the source of the SQLScript call. This could be an ABAP program, a Fiori application, a BAPI, or another interface.

text

2

Examine the input parameters being supplied to the SQLScript. Pay close attention to date ranges, selection criteria, and key fields.

text

3

Compare the provided input parameters against the expected data in the relevant database tables. For example, if the SQLScript is expecting sales orders for a specific date, verify that sales orders actually exist for that date in the sales order tables.

text

4

If the input parameters are incorrect or too restrictive, correct them. This might involve adjusting date formats, widening search criteria, or ensuring that the correct primary keys are used.

text

5

Re-execute the process or transaction that triggered the SQLScript with the corrected input parameters to verify the error is resolved.

text

🔗

Related Errors

5 related errors

SAP S/4HANA Error 1299: SQLScript Data Retrieval Failure