Blogs

ISSUE 1: JOB CANCELS WITH A TABLESPACE OR MEMORY ERROR

The Problem:

The DART extraction job (FTW0) cancels, and the job log in SM37 shows a database error related to tablespace limits or a memory error like a short dump (e.g., TSV_TNEW_PAGE_ALLOC_FAILED).

The Cause: DART reads a massive amount of data. If you are extracting a full fiscal year for a large company code, the program can consume significant system resources. The selection may be too large for a single run.

The Fix: Break down your DART run into smaller pieces. Instead of running for the entire fiscal year at once, run it for smaller date ranges, for example, on a quarterly or even monthly basis. This reduces the memory and processing load of each individual job.

ISSUE 2: EXTRACT LOG SHOWS "0 RECORDS EXTRACTED"

The Problem:

The DART job finishes successfully (green light in FTWL), but when you view the log details, it shows "0 records extracted" for key segments like TXW_FI_HD.

The Cause: This almost always means your selection criteria in the variant for FTW0 were too restrictive or incorrect. Common causes include:

• An incorrect Fiscal Year or Company Code was entered.
• The date range specified does not contain any posted documents.
• The Data View selected in the variant was not configured correctly or does not contain the required data segments.

The Fix: Carefully review the variant used for the DART run. Double-check every parameter against the data you expect to exist in the system. Start with a very broad selection (e.g., a wider date range) in a test system to confirm data is being selected, then narrow it down.

ISSUE 3: AUTHORIZATION ERRORS FOR THE BACKGROUND USER

The Problem:

The job fails, and the job log indicates that the user who ran the job (often a system or background user) is missing authorizations for specific tables.

The Cause: DART needs to read data from a wide variety of tables across different modules (FI, CO, SD, MM). The user executing the job needs the appropriate display authorizations (S_TABU_DIS) for all tables included in the selected Data Segments.

The Fix: Work with your Security team. Run a security trace (ST01 or STAUTHTRACE) on the background user while executing the DART run in a test environment. The trace will pinpoint exactly which authorization objects and values are missing. Add these missing authorizations to the background user's role.