Posts

Showing posts from October, 2016

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 sessi

Material relevant tables

MARA - Material Master: General data MAKT - Material Master: Description MARM - Material Master: Unit of Measure MAPE - Material master: Export control file MARC - Material master: Plant data MARD - Material master: Storage location MAST - Material link to BOM MBEW - Material valuation MLGN u2013 Material Master: WM Inventory MLGT u2013 Material Master: WM Inventory type MDIP - Material: MRP profiles (field contents) MKOP - Consignment price segment (old versions of SAP) EBEW - Valuation of sales order stock QBEW - Valuation of project stock MVER u2013 Material Master: Consumption <Plant> DVER u2013 Material Master: Consumption <MRP Area> MVKE u2013 Material Master: Sales <Sales Org, Distr Ch> MLAN - Material Master: Tax indicator MARC - Material Master: Plant data MAPR u2013 Material Master: Forecast MARD u2013 Material Master: Storage Location MCH1 u2013 Material Master: X Plant Batches MCHA u2013 Material Master: Batche