# SAP Batch Input Session Checklist > Source: https://netray.co/tools/sap-batch-input-session-checklist > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Step-by-step checklist for recording, building, running and verifying a batch input session in SM35, with notes on errors and background processing. ## Category sap ## Erp SAP ECC / S/4HANA ## Audience - SAP ABAP developer - SAP data migration consultant - SAP functional consultant ## Tool **Kind:** checklist **Groups:** #### Prepare **Items:** **Text:** Confirm batch input is the right method; check for a BAPI, IDoc, LSMW or standard migration object first **Critical:** true Document the transaction, object and number of records in scope Get the source file layout approved with the business owner **Text:** Confirm the executing user has authorization for the transaction and for SM35 **Critical:** true Check the screen sequence is stable in this release, since patches can change screens Agree the cut-over window and the rollback or correction approach #### Record and build **Items:** Record the transaction in SHDB with realistic data, including the save step Remove screen elements with fixed values and replace changing ones with variables Check the cursor position, OK codes and function keys, such as ENTER or /11 for save Handle screens that appear only conditionally, such as warnings or popups **Text:** Mind the user decimal and date formats in the profile of the executing user **Critical:** true Generate the program from the recording, or transfer it to your own program Use a clear session name that contains object, wave and date #### Validate before loading **Items:** Check source data for mandatory fields, lengths and leading zeros Validate master data references such as plant, material, vendor and company code Run a small test of 5 to 10 records in a test client Run a representative set in foreground mode (display all screens) and compare results Process in error-only display mode to see exactly where a record stops Verify created documents in the target transaction, not only the session log #### Run **Items:** **Text:** Lock or notify users of the target data where concurrent changes are likely **Critical:** true Choose the processing mode: foreground, errors only or background Schedule large sessions in background so a terminal timeout cannot stop them Run in several parallel sessions only if the object has no number range or lock contention Keep sessions to a manageable size so a failure does not block the whole load Record start and end times and counts for the cut-over log #### Verify and close **Items:** Review the session log in SM35 and list all transactions in error **Text:** Correct the source data and reprocess only the failed records **Critical:** true Reconcile counts and totals against the source file Have the business owner sign off a sample Delete or archive processed sessions according to policy Document lessons learned and keep the recording and program under version control **Scoring Note:** 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. ## Content **Intro:** 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. **Sections:** #### How to use the checklist **Body:** 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 **Body:** 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. **Bullets:** - 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 **Body:** 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 **Body:** 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. **Cta:** 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. **Faq:** #### What is a batch input session in SAP? **Answer:** 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? **Answer:** 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? **Answer:** 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? **Answer:** 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. ## Search terms sap batch input checklist, sm35 batch input session, shdb recording tips, sap batch input error handling, sap batch input background run, sap bdc call transaction vs session, sap batch input data migration, sm35 process session in background --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json