Background Job created but transactions not created.

Cocept of Bacth input Sessions and Back ground jobs.

First we try to understand concept of batch input programs in SAP.
To create any transaction record thru ABAP SAP has provided Batch input Technique.
Again there are two techinques to create batch input programs.
1. Call transaction
2. Sessions

You need to send all required data in bacth input tables (Structure BDCDATA) then use

1. Call transaction method: In this method program directly calls specified SAP transaction code and creates corresponding records. There will not be any sessions. The error messages can be captured by programming using BDCMSGCOLL structure.

This call transaction program can be created as Background Job. So when the job is ran then you see log in SM37, and the job might be finished. But actually the record got errored out. So make sure you program creats error log file.

2. Session method: In this method program puts all related data in sessions and need to be released and processed.
Once session is created, go to SM35 and release and process the session.
Normally in production system Basis people run a program(RSBDCSUB) as background which setup to be run in automatically every 5 mts or 10 mts, this program picks all unprocessed sessions, release and runs those sessions.

So this session program also created as background Job. So once the background job is ran make sure check the background job log in SM37 and also check the session log in SM35. If both are fine then program executed scucessfully.

Comments

Popular posts from this blog

Add additional fields in VA05 report

Totals table for ACDOCA in S/4 HANA - ACDOCT

FAGLL03 / FBL1N / FBL3N / FBL5N not showing custom fields