SAP Batch Input Session Checklist
Batch input is still used for data loads and one-off corrections because it drives the real transaction screens. It is also fragile, so a structured checklist from recording to reconciliation saves reruns and bad data.
0 of 31 items complete
5 critical items still open - these are the highest-risk gaps.
Prepare
Record and build
Validate before loading
Run
Verify and close
Items marked critical can cause bad data or a failed cut-over if skipped. Batch input depends on screen layout, so re-test after any support package or customizing change. Newer releases favor BAPIs, standard migration cockpit objects and APIs where they exist.
Planning a big SAP data load?
Ask for a light review of your load plan and where automated pre-checks could reduce reruns.
Optional. The tool and every export work without this. No spam.
How to use the checklist
Work through the groups in order and tick items as you finish them. Use the critical items as a stop sign: if one is open, hold the load. Export the completed list to PDF and keep it with the cut-over documentation as evidence that the session was prepared and verified.
Session versus call transaction
A batch input session is stored in SM35 and processed later, which gives a log and a restart option. CALL TRANSACTION runs immediately in the program and returns messages directly. Sessions suit large and auditable loads, while call transaction suits quick synchronous updates. Both depend on stable screens.
- Session method: stored, logged, restartable in SM35
- Call transaction: immediate, messages returned to the program
- Background processing avoids terminal timeouts
- Error-only mode helps you fix problem records quickly
Alternatives to consider first
Check for a BAPI, a released API, an IDoc inbound process or the migration cockpit before you record screens. They are more stable across releases and give clearer messages. Batch input is a sensible fallback for objects without such an interface, but needs more regression testing.
Common mistakes
Recording with the developer's user formats and running with another user's, loading before master data exists, using a recording that includes a one-off popup, and running a very large session in one piece are frequent. Always reconcile the count with the source file.
Frequently Asked Questions
What is a batch input session in SAP?
It is a stored set of screen inputs for a transaction, created from a recording or program and processed later in SM35. The system replays the entries as if a user typed them and writes a log for each transaction.
How do I process a session in the background?
In SM35, select the session and choose Process, then pick the background option, or schedule the report RSBDCSUB in SM36. Background processing avoids dialog timeouts and runs without displaying screens.
Why do records fail in a batch input run?
Usual causes are unexpected popups, differences in user date or decimal format, missing master data, locked objects, and screens that changed after a support package. Run in error-only mode to see where each record stops.
Is batch input still recommended?
Only when no BAPI, API, IDoc or migration cockpit object exists for the task. It depends on screen layouts, so it needs regression tests after upgrades. Where an interface exists, prefer it for stability and clearer errors.
If you are planning a large SAP data load, Netray can help you build a validation layer that checks source files before they are posted, with your team approving the run.
Related Tools
SAP RFC Destination Setup Checklist (SM59)
Work through every step of creating and securing an RFC destination in SM59, from connection type to authorization and testing.
SAPSAP IDoc Status Codes Reference
Look up any IDoc status code, see whether it is inbound or outbound, whether it is an error, and which transaction to use to fix it.
SAPSAP IDoc Message Types Reference (ORDERS, DESADV, INVOIC, MATMAS, DEBMAS)
Searchable list of common SAP IDoc message types with the basic IDoc type, business meaning and the X12 or EDIFACT message they usually map to.
SAPSAP OData Service URL Builder
Generate a correct SAP Gateway OData V2 request URL with query options, test it in a browser or REST client, then reuse it in your code.
More SAP tools
See all- SAP Sales Document Types Reference
- SAP Pricing Procedure Design Worksheet
- SAP Item Category Determination Reference
- SAP Delivery Block Reasons Template
- SAP Credit Management Checklist
- SAP Output Determination Checklist
- SAP Billing Types Reference
- SAP Incompletion Log Checklist
- SAP SD Tables Reference (VBAK, VBAP, LIKP, VBRK and More)
Keep exploring
Free tools
- ABAP Background Job Runtime and Batch Window CalculatorEstimate batch job duration from record volume, per-record time, commit frequency and parallel processing, and test it against your batch window.
- SAP Background Job Capacity CalculatorEstimate batch window utilisation, elapsed time and how many background work processes you need to finish nightly jobs.
- SAP Kernel Upgrade ChecklistA checklist for planning, staging, replacing and verifying an SAP kernel update, with backup and rollback steps called out.
ERP fixes and how-tos
- Batch Report in SAP PP: Where-Used and Traceability TcodesWhich SAP batch reports show where a batch came from and went to? MB56, MSC3N, BMBC, MB51 and tables MCH1, MCHA, MCHB for production traceability.
- Fix SAP Business One Service Layer 'Invalid session' (code 301)Fix 'Invalid session or session already timed out' in the SAP Business One Service Layer: B1SESSION and ROUTEID cookies, timeout, relogin and pooling.
- IFS Cloud Background Job Stuck in Posted or ExecutingIFS background jobs stuck in Posted or Executing? See how to check batch queues, find the error text, requeue or cancel jobs, and avoid duplicate runs safely.
AI on your ERP
- AI for SAP S/4HANA in Food and Beverage: Batch Traceability, Shelf Life and Recall ReadinessAI on SAP S/4HANA for food and beverage: batch traceability, shelf life, recalls and allergen data answered from live records, on-prem and read-only.
- AI for SAP S/4HANA in Pharmaceuticals: Read-Only, GxP-Aware Answers From Batch and Quality DataAI on SAP S/4HANA for pharma manufacturers: batch records, QM lots and deviations, read-only and GxP-aware, running on your own validated infrastructure.