Contact us
  1. Home
  2. DevOps
  3. SAP programs

The SE38 toolbox: standard SAP programs that fix everyday problems

32 standard programs that key users and consultants keep reaching for: what each one does, how to run it safely, what you get back, and what changed in SAP S/4HANA. Every program links to its sources, SAP’s own documentation first.

  • Finance
  • Bank statement
  • Assets
  • Output and IDocs
  • Audit
  • Brazil

By · Updated

SA38 · Run a programPage demo

Try:RFBNUM00NRFEBKA96RSVTPROTJ_1BNFE_CF_STATUS_UPDATE

> waiting for a program name

The catalogue below follows what you type here.

A look-alike of SA38 that searches this page. It is not connected to any SAP system.

Read a program name before you run it

The first letters of the programs on this page cluster by area. Treat it as a pattern you notice, not an official naming rule: once you see it, an unknown name stops looking random.

  • SAPF4 programsFinance programsSAPF124 · SAPF190 · SAPF020 · SAPF019
  • RFEB2 programsBank statementRFEBKA96 · RFEBKA00
  • RF4 programsFinance reportsRFBNUM00N · RFVBER00 · RFDABL00 · RFBIBL00
  • RG1 programValidations and substitutionsRGUGBR00
  • RA5 programsAsset AccountingRAAFAR00 · RAJABS00 · RAJAWE00 · RAPOST2000 · RAGITT_ALV01
  • RV2 programsSales and deliveryRVKRED77 · RVV50R10C
  • RM1 programMaterialsRMMMPERI
  • RBD2 programsALE and IDocsRBDAPP01 · RBDMANI2
  • RS9 programsBasis and cross-applicationRSNAST00 · RSEOUT00 · RSBDCSUB · RSCONN01 · RSTXPDFT4 · RSTXSCRP · RSVTPROT · RS_ABAP_SOURCE_SCAN · RSPFPAR
  • J_1B2 programsBrazilJ_1BNFE_CF_STATUS_UPDATE · J_1BLB*

Before the first run

How to run any program safely

Five habits that make SE38 and SA38 a tool instead of a risk. The steps are in the order you meet them.

Step 1 of 5

Use SA38 to run, leave SE38 to developers

SA38 only runs executable programs; you also reach it through the menu System › Services › Reporting. SE38 is the ABAP Editor, the developer’s entry point to the source code, attributes and variants.

System › Services › Reporting (SA38)Example
Program
RFBNUM00N
Action
Execute

Why it matters. A key user who runs programs doesn’t need the editor, and keeping the two apart keeps the roles clean.

Sources: Running programs directly (SA38) · Opening programs in the ABAP Editor (SE38)

Step 2 of 5

Read the program documentation first

Executable programs can carry their own documentation. On the SE38 initial screen, Documentation is one of the subobjects you can display. Read it before the first run, especially for programs that change or delete data.

SE38 · initial screenExample
Program
SAPF019
Subobjects
Documentation
Mode
Display

Why it matters. The documentation is where a program’s options, prerequisites and warnings are explained.

Sources: Opening programs in the ABAP Editor (SE38) · The ABAP Editor initial screen and its subobjects

Step 3 of 5

Save a variant, and protect it

A variant stores your selections. Protect variant stops other users from changing it, Only for background processing keeps it out of dialog runs, and fields can be hidden. Dates can be calculated at run time, and values can come from table TVARVC.

Variant attributesExample
Variant
MONTH_END
Protect variant
Yes
Only background
Yes
Posting date
Dynamic date: current month

Why it matters. A nightly job with dynamic dates and TVARVC values never needs editing, and a protected variant can’t be changed by accident.

Sources: Variant attributes · Variable values in variants

Step 4 of 5

Run long jobs in the background

Executable programs can run as background jobs. Scheduling one needs the action BTCSUBMIT in S_PROGRAM, and where a program offers a test run, use it first.

Background jobExample
Job name
Z_FI_GAP_CHECK
Program
RFBNUM00N
Variant
MONTH_END
Start
Immediately

Why it matters. Long runs in dialog can hit time limits and block your session; a job runs on its own and leaves a log.

Sources: Running programs directly (SA38) · Authorization object S_PROGRAM

Step 5 of 5

Give it a transaction and an authorization group

SE93 creates a report transaction that starts the program with a preset variant and its own authorization check. Assign the program to an authorization group: S_PROGRAM then checks the group (P_GROUP) and the action (P_ACTION: SUBMIT, BTCSUBMIT or VARIANT). RSCSAUTH assigns groups to programs without modifying them.

Authorization object S_PROGRAMExample
P_GROUP
ZFI_REP (example)
P_ACTION
SUBMIT, VARIANT

Why it matters. SAP’s documentation says S_PROGRAM does not restrict a program without an authorization group: any user can start it.

Sources: Report transactions (SE93) · Authorization object S_PROGRAM · Program authorization groups and RSCSAUTH

For key users and consultants

What happened? Start from the problem

Pick the situation closest to yours. You get the program, the order of the steps and what to watch out for.

An auditor asks about missing document numbers

Programs

Steps

  1. Run RFBNUM00N for the company code and fiscal year.
  2. Run RFVBER00 for the same period and match its update terminations to the gaps.
  3. For gaps that remain, check whether the number range is buffered.

What you end up with

An explanation for each missing number.

Watch out. A gap does not mean a deleted document: a terminated update also uses up a number. Run RFVBER00 soon, as older terminations may no longer show.

Source: Update termination leaves a document number gap (KBA 2062732)

A bank statement was imported twice

Programs

Steps

  1. Note the documents the wrong statement posted and reverse them.
  2. Run RFEBKA96 with application 0001 and delete only the wrong statement.
  3. Import the correct file again with FF.5.

What you end up with

Clean bank data storage and a statement you can import again.

Watch out. Deleting the statement does not reverse its postings.

Source: Bank statement closing activities (RFEBKA96)

Open items that net to zero keep piling up

Programs

Steps

  1. Check the clearing criteria set for the account type.
  2. Run F.13 for a single account first and check the clearings.
  3. Widen the selection, or schedule it as a job.

What you end up with

Open items cleared automatically, group by group.

Watch out. Groups only clear when their balance is exactly zero.

Source: Automatic clearing

Validations or substitutions misbehave after an upgrade

Programs

Steps

  1. Read the long text of message GB 206 if it appears.
  2. Run RGUGBR00 in each client that uses them, with all generation options.
  3. Post a test document again.

What you end up with

Regenerated validation and substitution code.

Watch out. The long text of message GB 206 asks for it in every client that uses validations, substitutions or rules, not only in the one where you saw the error.

Source: Message GB 206: programs should be regenerated

Output didn’t go out

Programs

Steps

  1. Check the dispatch time and the processing log of the output.
  2. Make sure an RSNAST00 job runs with a variant that covers it.
  3. If the document uses SAP S/4HANA output control instead of NAST, look there instead.

What you end up with

The waiting output is processed.

Watch out. Message VN033 means no outputs were processed; one cause is the dispatch time.

Source: RSNAST00 message VN033 (KBA 1464879)

IDocs are stuck

Programs

Steps

  1. Open the status monitor for ALE messages and group the IDocs by status.
  2. Status 30 (outbound): RSEOUT00. Status 64 (inbound): RBDAPP01.
  3. Status 51: fix the cause first, then reprocess with RBDMANI2.

What you end up with

IDocs moving again, each status handled by its own program.

Watch out. Statuses 30 and 64 are waiting states, not errors.

Source: Technical errors in the ALE service layer

E-mails sit in SOST

Programs

Steps

  1. Check the SAPconnect send jobs in SCOT.
  2. Schedule a send job (RSCONN01) for the address type if none runs.
  3. Status 672 while the job runs? See KBA 3769464.

What you end up with

Queued mails leave the system on a schedule.

Watch out. Mail that is queued instead of sent at once waits until a send job runs.

Source: Scheduling the SAPconnect send process

I need a report as a PDF

Programs

Steps

  1. Send the report to the spool and note the spool request number.
  2. Run RSTXPDFT4 with that number.
  3. Choose where to save the file.

What you end up with

A PDF that looks like the printout.

Watch out. For very long ABAP lists it is slow.

Source: Converting spool requests to PDF

Who changed this configuration table?

Programs

Steps

  1. Check rec/client in RSPFPAR to confirm logging is on.
  2. Evaluate the logs for the table in SCU3.
  3. No log? The table wasn’t being logged at the time.

What you end up with

The user, date and entries behind a change.

Watch out. Logging also needs the “Log data changes” flag on the table itself.

Source: SCU3: how to enable table logging (KBA 2437986)

We need a clean test company code

Programs

Steps

  1. Run OBR1 to delete the company code’s transaction data.
  2. If SAPF019 has never run in this system, start SAPF047 first.
  3. Run SAPF019 as a test, then for real.

What you end up with

A company code with no postings and no test master data.

Watch out. Test clients only. OBR1 can delete the CO data of the whole controlling area.

Source: Deleting master data

Credit exposure looks wrong (ECC)

Programs

Steps

  1. Run RVKRED88 to simulate the reorganization.
  2. Plan a window with no sales activity.
  3. Run RVKRED77 with the smallest selection that fixes the problem.

What you end up with

Corrected credit exposure in classic credit management.

Watch out. SAP S/4HANA uses SAP Credit Management instead.

Source: Reports for credit management

An NF-e is stuck “in process”

Programs

Steps

  1. Check the access key on the SEFAZ site.
  2. Run J_1BNFE_CF_STATUS_UPDATE for the company code and business place.
  3. If it returns message J_1BNFE_CF 040, follow KBA 2941021.

What you end up with

The NF-e status in J1BNFE refreshed from the cloud service.

Watch out. After SAP Note 3586432 the job can fail with message J_1BNFE_CF 041 (KBA 3668616).

Source: NF-e status update from the cloud (KBA 2941021)

32 programs

The catalogue

Every program with its area, its status in SAP ERP (ECC) and SAP S/4HANA, and what it does to your data. Open a program to see how to run it, what you get, a documented tip and the sources.

  • RFBNUM00NFind gaps in FI document numbersNot confirmedRead-only

    Finance

    Lists the numbers missing from the FI document number sequence, so you can explain each gap before an auditor asks.

    How to run it
    SA38 → RFBNUM00N. Enter the company code and fiscal year, and narrow the run by number range or document type if needed.
    What you get
    A list of the document numbers that were never used.
    ECC
    Available Available. SAP’s knowledge base on document number gaps names it (KBA 1828201).
    S/4HANA
    Not confirmed Not confirmed in SAP’s documentation for SAP S/4HANA. SAP documents the Audit Journal app instead, whose report Check Gaps in Document Numbers does the same job (S/4HANA Finance 1605).

    Tip. A gap is not always a missing posting. When an update terminates after the number was drawn, the number is lost and nothing reaches BKPF or BSEG. SAP documents this for SAP ERP and SAP S/4HANA (KBA 2062732).

    Watch out. Number range buffering can also leave gaps and make numbers jump (KBA 1843002). Check it before you chase a gap.

    Sources

  • RFVBER00List FI update terminationsAvailableRead-only

    Finance

    Shows the FI postings that ended in an update termination, which is where many document number gaps come from.

    How to run it
    SA38 → RFVBER00, or transaction S_ALR_87101004. Select the period you are checking.
    What you get
    The FI update terminations for the period you select.
    ECC
    Available Available (KBA 3764467).
    S/4HANA
    Available Available: SAP’s KBA on S_ALR_87101004 covers SAP S/4HANA and S/4HANA Cloud Private Edition (KBA 3764467). In Fiori, the Audit Journal app has a Display Update Terminations report.

    Tip. Use it together with RFBNUM00N for the same period: SAP lists both programs under the same knowledge base topic on number gaps (KBA 1828201), and you match the terminations to the gaps.

    Watch out. SAP’s KBA on this report covers terminations that no longer show for an older date range, and its keywords point to how long update records are kept (KBA 3764467). Run it soon after the period you are checking.

    Sources

  • SAPF124Clear open items automatically (F.13)AvailableChanges data

    Finance

    Groups the open items of customer, vendor or G/L accounts by your clearing criteria and clears each group whose balance is zero.

    How to run it
    Transaction F.13, or SA38 → SAPF124 with a variant. The clearing criteria are set per account type in configuration: a standard set plus up to five extra fields.
    What you get
    Clearing documents for the groups that balance to zero.
    ECC
    Available Available: SAP Help describes automatic clearing, and KBA 2914798 names F.13 and SAPF124.
    S/4HANA
    Available Available: SAP KBAs cover F.13 and SAPF124 in SAP S/4HANA (KBA 2914798). In S/4HANA Cloud Public Edition you schedule it with the Schedule General Ledger Jobs app, job template SAP_FIN_GL_AUTO_CLR (KBA 3761737).

    Tip. If you add Assignment as a clearing criterion, remember that on G/L accounts the sort key in the account master fills it. A well-chosen sort key then does much of the matching for you (SAP Learning).

    Watch out. In a production run, the variant option that takes the clearing date from the most recent document (XAUGDT) can stop with error FG018 (KBA 2914798).

    Sources

  • RGUGBR00Regenerate validations and substitutionsAvailableRegenerates code

    Finance

    Regenerates the code behind FI validations, substitutions and rules, the logic you maintain in GGB0, GGB1, OB28 and OBBH.

    How to run it
    SA38 → RGUGBR00 in each client that uses validations, substitutions or rules. Select the generation options for rules, validations, substitutions, sets and their usage.
    What you get
    The generated programs are rebuilt, and the error that asked for regeneration goes away.
    ECC
    Available Available: named in SAP KBAs on validations and substitutions (KBA 1582327).
    S/4HANA
    Available Named in an SAP KBA that covers SAP S/4HANA and S/4HANA Finance (KBA 2503724).

    Tip. You don’t have to guess when to run it. SAP’s message GB 206 says the programs should be regenerated, and its long text, which you can read in your own system, names RGUGBR00 for after an upgrade.

    Sources

  • RFDABL00Show who changed customer master dataNot confirmedRead-only

    Finance

    Lists the changes made to customer master records across many customers at once: what changed, when and by whom.

    How to run it
    SA38 → RFDABL00. Select by customer, change date, user and field group, and choose general, company code or sales area data.
    What you get
    Usually one line per change. Fields that need an extra key, such as bank details, get a second line.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Not confirmed The program itself is not confirmed for SAP S/4HANA in SAP’s documentation. SAP Learning describes the Display Changes to Customers app for the same job, with old and new values.

    Tip. Tick the option for technical field names and each change also shows the field name behind it, which helps when you hand the case to IT.

    Sources

  • RFBIBL00Post FI documents from a fileAvailableChanges data

    Finance

    Transfers FI documents from a file built with the BBKPF and BBSEG structures, by batch input, call transaction or direct input.

    How to run it
    SA38 → RFBIBL00. Point it at the file and choose the processing mode.
    What you get
    Posted documents, or, with batch input, a session to process.
    ECC
    Available Available: SAP Help lists it as the transfer program for accounting documents.
    S/4HANA
    Available Still in use: SAP KBAs about it cover SAP S/4HANA and S/4HANA Finance (KBA 3769491).

    Tip. In direct input mode, automatic tax calculation (BBKPF-XMWST) is not allowed and stops with message RW308 (KBA 2545516).

    Watch out. Direct input does not honour the G/L account setting “Post automatically only” (KBA 2590652). Check the accounts in your file before the run.

    Sources

  • SAPF190Compare FI totals with documentsNot confirmedRead-only

    Finance

    Checks that the transaction figures of customer, vendor and G/L accounts agree with the documents and with the index tables.

    How to run it
    SA38 → SAPF190. Enter the company code, fiscal year and periods, and choose which comparisons to run.
    What you get
    Differences by area. In a healthy system there are none.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Not confirmed Not confirmed for SAP S/4HANA. The related index check RFINDEX_NACC is no longer available there and ends with message SFIN_FI004 (KBA 2642923). Before a conversion, SAP’s finance data quality check runs FIN_CORR_RECONCILE on the ECC system (SAP, 2022).

    Tip. It belongs to the monthly close: SAP Help lists the comparative analysis as a month-end closing step.

    Sources

  • SAPF020Delete a test company code’s postings (OBR1)AvailableDeletes data

    Finance

    Resets the transaction data of a company code in a test client, so the next test cycle starts with clean figures.

    How to run it
    Transaction OBR1, which runs SAPF020.
    What you get
    The company code’s transaction data is deleted.
    ECC
    Available Available (KBA 1895961).
    S/4HANA
    Available Available: SAP KBAs about OBR1 cover SAP S/4HANA (KBA 2539538; KBA 2788050 lists releases up to 1809). In S/4HANA Cloud, KBA 2927181 describes the same error F7148 in the Schedule Accounting Data Corrections app.

    Tip. Error F7148 means postings exist in Controlling for the company code; KBA 2788050 explains the cases.

    Watch out. Aimed at one company code, it can still delete the CO data of the whole controlling area (KBA 1895961). Keep it to test clients.

    Sources

  • SAPF019Delete master data in a test systemChangedDeletes data

    Finance

    Physically deletes G/L account, customer and vendor master data, for example to clean a test system before go-live.

    How to run it
    SA38 → SAPF019 (for G/L accounts also transaction OBR2). Choose general data, company code data or both, decide whether deletion flags count, and run a test first. SAP recommends a background job.
    What you get
    The test run changes nothing; the update run removes the master records.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Changed G/L accounts: OBR2 and SAPF019 are covered for SAP S/4HANA (KBA 2811096). Customers and vendors are business partners there, and SAP documents a separate deletion route through business partner archiving (KBAs 2491026, 3787397).

    Tip. On the very first run, start SAPF047 to build the link information. Accounts that still have transaction figures can’t be deleted, so remove those with SAPF020 first (SAP Help).

    Watch out. SAP says to use it only in the test phase, while the company code is not yet flagged as productive.

    Sources

  • RFEBKA96Delete an imported bank statementNot confirmedDeletes data

    Bank statement

    Removes imported bank statements from the bank data storage, so a wrong or test file can be imported again.

    How to run it
    SA38 → RFEBKA96. Enter application 0001, select the statements in the list, choose Delete statements and confirm.
    What you get
    The number of deleted records. Documents already posted from the statement stay.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Not confirmed Not confirmed in SAP’s documentation for SAP S/4HANA. Test it in your release before you rely on it.

    Tip. Imported statements sit in table FEBKO (KBA 2945545), so you can look up the right statement there before deleting.

    Watch out. Deleting a statement does not reverse the documents it posted. Reverse those separately.

    Sources

  • RFEBKA00Import bank statements (FF.5)AvailableChanges data

    Bank statement

    Imports an electronic bank statement file into the bank data storage, where SAP enriches it and starts the postings.

    How to run it
    Transaction FF.5, or SA38 → RFEBKA00. Choose the format, the files and whether to post right away.
    What you get
    Statements in the bank data storage and the postings they trigger.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Available Available: SAP S/4HANA KBAs cover RFEBKA00 and FF.5, all versions (KBAs 2877257, 2907264).

    Tip. To test your configuration, RFEBKATX creates open items and matching Multicash statement files that you then import with RFEBKA00 (SAP Help).

    Watch out. In the background the file must be readable on the application server, or the run stops with error FB002 (KBA 2907264). Error FB773 points to an external transaction code missing from configuration (KBA 2877257).

    Sources

  • RAAFAR00Recalculate asset depreciation (AFAR)AvailableChanges data

    Assets

    Recalculates planned depreciation after a change in the depreciation settings. It does not post anything.

    How to run it
    Transaction AFAR, or SA38 → RAAFAR00. Use the test mode first to compare the values.
    What you get
    Recalculated planned values. Posting them is the job of the depreciation run.
    ECC
    Available Available: SAP KBAs name AFAR and RAAFAR00 (KBA 2032820).
    S/4HANA
    Available Available: SAP KBAs about AFAR and RAAFAR00 cover SAP S/4HANA (KBAs 2919009, 2032820).

    Tip. A production run cannot be limited to a company code, depreciation area or asset: the program stops with “Selection not allowed in production run” (KBAs 2446387, 2919009).

    Sources

  • RAJABS00Close the fiscal year in Asset Accounting (AJAB)AvailableChanges data

    Assets

    Checks that depreciation is fully posted and the assets are complete, then closes the fiscal year for asset postings.

    How to run it
    Transaction AJAB, or SA38 → RAJABS00.
    What you get
    The last closed fiscal year is recorded, so no more asset postings reach it.
    ECC
    Available Available (KBA 2816495).
    S/4HANA
    Available Available: SAP KBAs about AJAB and RAJABS00 cover SAP S/4HANA and Private Cloud Edition (KBA 3782864).

    Tip. A closed year can be reopened with transaction OAAR when a correction is needed (KBA 2816495).

    Sources

  • RAJAWE00Open the new year in Asset Accounting (AJRW)ChangedChanges data

    Assets

    Opens the new fiscal year for assets and carries forward their cumulative values.

    How to run it
    Transaction AJRW, or SA38 → RAJAWE00.
    What you get
    Each asset gets its values for the new fiscal year.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Changed SAP’s KBA on this step names AJRW for ECC and the balance carryforward FAGLGVTR for SAP S/4HANA (KBA 2584908). Some S/4HANA KBAs still mention AJRW, so check your release.

    Sources

  • RAPOST2000Post depreciation (AFAB)ChangedChanges data

    Assets

    The depreciation posting run: it posts planned depreciation to the general ledger with collective documents.

    How to run it
    Transaction AFAB. Check the test run and its list before the update run.
    What you get
    Depreciation documents and a list of the run.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Changed AFAB is still there, and SAP KBAs also mention AFABN. KBA 2996678 names RAPOST2000 as the AFAB program in SAP S/4HANA, while KBA 3498548 lists both RAPOST2000 and FAA_DEPRECIATION_POST; SAP PRESS (2020) ties the background job to FAA_DEPRECIATION_POST.

    Tip. A repeat run posts only the differences, and a restart run continues after an abnormal end, so a period is not posted twice (SAP Help).

    Watch out. Don’t run it for a future period (KBA 2870963).

    Sources

  • RAGITT_ALV01Asset history sheet (AR02)AvailableRead-only

    Assets

    Shows how acquisition cost and depreciation moved over the year, from the opening to the closing balance, grouped by history sheet version.

    How to run it
    Transaction AR02, or SA38 → RAGITT_ALV01. Enter the company code, report date and history sheet version.
    What you get
    An ALV list of the asset values, from opening to closing balance.
    ECC
    Available Available (KBA 2459182).
    S/4HANA
    Available Available, together with the Fiori apps Asset History Sheet (F1615) and Asset Balances (F1617) (KBA 3049624).

    Tip. Revaluation values are missing when the revaluation transaction types are not assigned to a history sheet group in AO84 (KBA 2857119).

    Watch out. A report date earlier than the legacy data transfer date leaves assets out, with message AB064 (KBA 1700142).

    Sources

  • RMMMPERIClose the materials period (MMPV)AvailableChanges data

    Logistics

    Moves the open posting period for materials forward by closing the previous one.

    How to run it
    Transaction MMPV, or SA38 → RMMMPERI. MMPI (program RMMMINIT) initializes periods, which is a different job.
    What you get
    The new period is open for goods movements.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Available Available in SAP S/4HANA (KBA 2042164). In S/4HANA Cloud Public Edition the Close Periods app does it; since release 2602 the check-only options are obsolete, and choosing them only closes the period (KBA 3755912).

    Tip. After the period change you can post to the new current period and to the previous one; older periods are closed (SAP Help, SAPinsider).

    Watch out. With the Material Ledger active, closing a future period by mistake can’t be reversed with MMPI (KBA 2042164).

    Sources

  • RVKRED77Rebuild SD credit exposureReplacedChanges data

    Logistics

    Reorganizes the open order, delivery and billing values behind classic SD credit management, for example after update errors.

    How to run it
    SA38 → RVKRED88 first, which simulates the reorganization, then RVKRED77. RVKRED09 rechecks released documents once their release has expired.
    What you get
    Corrected credit exposure values.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Replaced Classic credit management (FI-AR-CR) is not available in SAP S/4HANA. Its successor is SAP Credit Management, FIN-FSCM-CR (SAP Learning, SAP Note 2270544).

    Tip. SAP Help lists RVKRED88 as the simulation of the credit data reorganization: run it first to see the result before RVKRED77 changes anything.

    Watch out. RVKRED77 locks sales documents while it runs, so plan a window with no sales activity (SAP Community, 2016).

    Sources

  • RVV50R10CDelivery due list in batch (VL10C)AvailableChanges data

    Logistics

    The program behind VL10C, which creates outbound deliveries from the delivery due list. People run it in batch from SE38 or as a job.

    How to run it
    SA38 → RVV50R10C with a variant, in the background or as a scheduled job.
    What you get
    Outbound deliveries and a log.
    ECC
    Available Available (KBA 2427912).
    S/4HANA
    Available KBA 2427912 covers SAP S/4HANA, all versions.

    Tip. Started from SE38 in batch, it can call the VL10 program you used last in the same session instead (KBA 2427912). Check which program the job really ran.

    Watch out. SAP documents a background VL10 run that created no deliveries although the function code profile was set (KBA 2297715).

    Sources

  • RSNAST00Send waiting output (NAST)ChangedChanges data

    Output and IDocs

    Processes output records, such as print, e-mail or EDI, that wait for a scheduled send instead of going out when the document is saved.

    How to run it
    Schedule it as a background job with a variant. In live systems it is normally scheduled for output with dispatch time 1 (SAP Help).
    What you get
    The output is processed and a log is written.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Changed Still used where an application runs on NAST. SAP (May 2023): NAST is in maintenance mode with no plans to deprecate it; existing applications default to NAST in SAP S/4HANA and Private Cloud, new ones mainly use SAP S/4HANA output control, and the public cloud uses output control only.

    Tip. If the log says no outputs were processed (message VN033), check the output’s dispatch time: SAP’s KBA shows this case with dispatch time 2 (KBA 1464879).

    Sources

  • RSEOUT00Send outbound IDocs waiting in status 30AvailableChanges data

    Output and IDocs

    Sends outbound IDocs that were created but held back, the usual case when the partner profile collects IDocs (output mode 4).

    How to run it
    Schedule it as a periodic job, or start it from the ALE menu.
    What you get
    The IDocs leave status 30 and are passed on to the receiving system.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Available Supported: SAP’s KBA lists it for Web AS for SAP S/4HANA, all versions (KBA 3314649).

    Tip. Status 30 is a waiting state, not an error (SAP Help).

    Watch out. Its selection “Maximum number of IDocs” can be ignored, so every IDoc in status 30 goes out (KBA 3314649).

    Sources

  • RBDAPP01Process inbound IDocs waiting in status 64AvailableChanges data

    Output and IDocs

    Hands received IDocs to the application when the partner profile says to process them later instead of immediately.

    How to run it
    Schedule it as a periodic job, or start it from the ALE menu.
    What you get
    IDocs move from status 64 to posted (53) or to an error status.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Available Supported for SAP S/4HANA (KBA 2038054).

    Tip. Status 64 is a waiting state, not an error (SAP Help).

    Watch out. SAP documents cases where some IDocs stay in status 64 even after the run (KBA 2038054).

    Sources

  • RBDMANI2Reprocess inbound IDocs in error (status 51)AvailableChanges data

    Output and IDocs

    Runs inbound IDocs that failed in the application again, once the cause, such as missing master data, is fixed.

    How to run it
    SA38 → RBDMANI2, usually as a job. For a few IDocs, reprocess them in the status monitor instead.
    What you get
    Corrected IDocs post; the others stay in error.
    ECC
    Available Available (KBA 2338156).
    S/4HANA
    Available Supported in current releases (KBA 2338156).

    Tip. The status monitor for ALE messages groups IDocs by status. Start there to read the error before you reprocess (SAP Help).

    Watch out. SAP documents jobs that skip some status 51 IDocs (KBA 2338156).

    Sources

  • RSBDCSUBRun batch input sessions in the backgroundNot confirmedChanges data

    Output and IDocs

    Finds batch input sessions that haven’t run yet and processes them in the background, so nobody has to start them in SM35.

    How to run it
    Schedule it as a periodic job, with a variant that selects only the sessions you expect.
    What you get
    Processed sessions, with their logs in SM35.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Not confirmed Not confirmed in SAP’s documentation for SAP S/4HANA.

    Tip. Deleting a session only marks its log for deletion. RSBDCREO reorganizes the log file and frees the space (SAP Help).

    Sources

  • RSCONN01Push out e-mails waiting in SOSTNot confirmedChanges data

    Output and IDocs

    The SAPconnect send process: it passes queued e-mails and faxes to the external systems. SAP Help says to schedule it periodically.

    How to run it
    In SCOT, Send Jobs: schedule a job for the address type you need.
    What you get
    The queued messages are sent.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Not confirmed Not confirmed in SAP’s documentation for SAP S/4HANA.

    Tip. SCOT offers a send job per address type, such as fax or internet mail, with SAP’s template variant already chosen (SAP Help).

    Watch out. If mails stay in SOST with status 672 while the job runs, see KBA 3769464.

    Sources

  • RSTXPDFT4Turn a spool request into a PDFNot confirmedRead-only

    Output and IDocs

    Converts a spool request into a PDF file that looks like the printed output.

    How to run it
    SA38 → RSTXPDFT4. Enter the spool request number and where to save the file.
    What you get
    A PDF file in the folder you chose.
    ECC
    Available Available (SAP Help).
    S/4HANA
    Not confirmed Not confirmed in SAP’s documentation for SAP S/4HANA.

    Tip. Real bar codes come out only from Smart Forms that use the newer bar code technology; other bar codes are simulated (SAP Help).

    Watch out. It is slow for long ABAP lists, so it is not meant for mass printing (SAP Help).

    Sources

  • RSTXSCRPExport or import SAPscript formsAvailableChanges data

    Output and IDocs

    Moves SAPscript forms and styles to or from a file, outside the normal transport route.

    How to run it
    SA38 → RSTXSCRP. Choose export or import and the objects.
    What you get
    A file with the objects, or the objects imported from one.
    ECC
    Available Available (KBA 2172623).
    S/4HANA
    Available KBA 2172623 covers SAP ERP, SAP NetWeaver and SAP S/4HANA, all versions.

    Tip. Only objects whose language is in the system’s language vector are moved (SAP Help).

    Watch out. Forms and styles travel with normal transports, so keep this program for special cases (SAP Help).

    Sources

  • RSVTPROTSee who changed a customizing table (SCU3)AvailableRead-only

    Tools and audit

    Evaluates table change logs: which entries were changed, by whom and when.

    How to run it
    Transaction SCU3, or SA38 → RSVTPROT. Select the table and the period.
    What you get
    A list of the logged changes.
    ECC
    Available Available (KBA 2437986).
    S/4HANA
    Available Covered for SAP NetWeaver, SAP S/4HANA and ABAP Platform (KBA 2437986).

    Tip. Logging needs the profile parameter rec/client and the “Log data changes” flag on the table. New installations and conversions to SAP S/4HANA 2021 have table logging switched on by default (SAP Learning, SAP Note 3093760).

    Watch out. It only shows changes to tables that were being logged when the change happened.

    Sources

  • RS_ABAP_SOURCE_SCANSearch the ABAP source codeAvailableRead-only

    Tools and audit

    Searches programs for a string, such as a table, field or function module, so you find every custom program that uses it.

    How to run it
    SA38 → RS_ABAP_SOURCE_SCAN. Enter the search string and narrow the run by program name or package.
    What you get
    A hit list with the programs and lines where the string appears.
    ECC
    Available Available (KBA 2764076).
    S/4HANA
    Available Named in an SAP KBA that covers SAP S/4HANA (KBA 2764076).

    Tip. Before you change a field of a custom table, search for it here to list every Z program that reads it. Transaction CODE_SCANNER does a similar search.

    Watch out. SAP documents cases where CODE_SCANNER returns incomplete results (KBA 2764076).

    Sources

  • RSPFPARCheck the profile parametersAvailableRead-only

    Tools and audit

    Lists the instance’s profile parameters with the system default, the current value and a short description.

    How to run it
    Transaction RSPFPAR, or SA38 → RSPFPAR. Filter by parameter name.
    What you get
    A filterable list of parameters and their values.
    ECC
    Available Available (SAP Learning).
    S/4HANA
    Available Described by SAP Learning for SAP S/4HANA and SAP Business Suite.

    Tip. Filter on rec/client to see at once whether table logging is on in this system.

    Sources

  • J_1BNFE_CF_STATUS_UPDATERefresh NF-e status from the cloud (DRC)AvailableChanges data

    Brazil

    Updates the status of NF-e sent through SAP Document and Reporting Compliance, for documents stuck as “in process” in the NF-e monitor J1BNFE.

    How to run it
    SA38 → J_1BNFE_CF_STATUS_UPDATE for the company code and business place, or as a background job.
    What you get
    The NF-e status in J1BNFE is updated.
    ECC
    Available Available: KBA 2941021 covers SAP ERP 6.0.
    S/4HANA
    Available KBA 2941021 covers SAP S/4HANA and S/4HANA Cloud Private Edition.

    Tip. If the run returns message J_1BNFE_CF 040 for an NF-e that stays “in process” and whose access key is not on the SEFAZ site, SAP covers the case in KBA 2941021.

    Watch out. After SAP Note 3586432 the job can fail with message J_1BNFE_CF 041 (KBA 3668616).

    Sources

  • J_1BLB*Brazilian legal booksNot confirmedRead-only

    Brazil

    The classic legal book reports for Brazil, such as Legal Book Models 1, 2, 7, 8, 9, 12 and 51.

    How to run it
    Through their J1B_LB transactions, such as J1B_LB01 or J1B_LB07N, or with SA38.
    What you get
    The legal book for the selected period.
    ECC
    Out of maintenance SAP has put these reports out of maintenance for SAP ERP 6.0 because the legislation behind them is outdated (KBA 2475189).
    S/4HANA
    Not confirmed Not confirmed in SAP’s documentation for SAP S/4HANA.

    Watch out. Know this before you rely on them: SAP no longer maintains them (KBA 2475189).

    Sources

Release check

From ECC to SAP S/4HANA: what happened to them

Most programs on this page still run in SAP S/4HANA on-premise. These are the ones where the job moved, changed shape or gained a Fiori app.

Production check

Danger zone: check the client before you press Execute

The same program can be routine in a sandbox and a disaster in production. Switch the client and see how the advice changes.

ProgramWhat it does to dataIn a test clientIn a production client
SAPF019Deletes master dataFine Fine in the test phase. Run the test mode first.Don’t SAP says to use it only in the test phase. Delete customer master data: test phase only
SAPF020Deletes a company code’s postingsCareful Fine, but it can delete the CO data of the whole controlling area.Don’t Keep it to test clients. OBR1 and controlling data (KBA 1895961)
RFEBKA96Deletes imported bank statementsFine Fine for importing test files again.Careful Only for a wrong file, after you reverse what it posted. Bank statement closing activities (RFEBKA96)
RVKRED77Rebuilds credit exposureFine Fine. Compare with RVKRED88 first.Careful Plan a window: it locks sales documents while it runs. RVKRED77/RVKRED07 with limited system downtime
RMMMPERICloses the materials periodFine Fine.Careful Check the period twice: with the Material Ledger, a future period can’t be undone. MMPV future period with Material Ledger active (KBA 2042164)
RAAFAR00Recalculates depreciationFine Fine, with the test mode first.Careful A production run covers everything: it can’t be restricted. AFAR: selection not allowed in production run (KBA 2446387)
RFBIBL00Posts documents from a fileFine Fine for load tests.Careful Real postings. Direct input skips the “Post automatically only” setting. RFBIBL00 direct input and “Post automatically only” (KBA 2590652)

Test yourself

Which program would you run?

Six situations from real projects. Pick an answer to see why.

  1. An auditor found a missing FI document number. Which pair helps you explain it?

    Right.Not quite. RFBNUM00N and RFVBER00. RFBNUM00N lists the gaps, and RFVBER00 lists the update terminations you can match against them.

  2. Outbound IDocs sit in status 30. What do you run?

    Right.Not quite. RSEOUT00. RSEOUT00 sends IDocs held back in status 30. RBDAPP01 is for inbound status 64, and RBDMANI2 for inbound status 51.

  3. A test bank statement must be imported again. Which program removes the imported copy?

    Right.Not quite. RFEBKA96. RFEBKA96 removes the statement from the bank data storage. Anything it posted needs its own reversal.

  4. In SAP S/4HANA, what took over from classic credit management and RVKRED77?

    Right.Not quite. SAP Credit Management (FIN-FSCM-CR). Classic credit management is not available in SAP S/4HANA; SAP Credit Management is its successor.

  5. Someone changed a customizing table yesterday. Where do you look?

    Right.Not quite. SCU3 (RSVTPROT). Table change logs, provided rec/client and the table’s logging flag were on. RFDABL00 covers customer master data.

  6. Which program does SAP say to use only in the test phase?

    Right.Not quite. SAPF019. SAP’s documentation says SAPF019 is for the test phase only. The other two only read.

Pick an answer on each card.Your score: right out of answered, 6 questions in all.

Frequently asked questions

What is the difference between SE38 and SA38?

SE38 is the ABAP Editor, the developer’s entry point to a program’s source, attributes, variants and documentation. SA38 only runs executable programs; you also reach it through System › Services › Reporting. For running the programs on this page, SA38 is all a key user needs.

Can a key user run these programs?

Yes, if the role allows it. Starting SA38 needs the transaction in the role, and the authorization object S_PROGRAM checks the program’s authorization group. SAP’s documentation adds a detail that surprises many: S_PROGRAM does not restrict a program that has no authorization group, so any user can start it. Give your custom reports a group.

How do I run a program every night?

Save a variant, then schedule a background job in SM36 with the program and that variant. If the variant takes dates or values from table TVARVC, or calculates dates at run time, the job stays current without anyone editing it.

Do these programs exist in SAP S/4HANA Cloud Public Edition?

We found no SAP statement that lists SE38 or SA38 for customers there. Customers work through Fiori apps, and developer extensions are built with the ABAP Development Tools in the SAP S/4HANA Cloud ABAP Environment. Several jobs on this page have an app instead: automatic clearing runs as a job template in Schedule General Ledger Jobs, and the materials period is closed with the Close Periods app.

Why can’t I find a program in my system?

Some were replaced in SAP S/4HANA (the ECC vs S/4HANA section shows which), and some belong to a country version, like the J_1B programs for Brazil. The catalogue marks each program’s status, and “Not confirmed” means we found no SAP source either way, so test it in your release.

References

Checked in October 2026. SAP Help pages for older releases are cited where SAP’s current pages describe the same function. Knowledge base articles open in full with an SAP for Me login.