SAP Stories

For T-code: FBL1N/FBL3N/FBL5N Execute the report RFPOSXEXTEND with T-code: SE38 in your system. Table T021S and structure RFPOSXEXT are able to synchronize. For T-code: FAGLL03Call T-code: SE37, enter the function module ITEM_STRUC_EXTENSION and execute it with the following parameters: BASIC_STRUCNAME FAGLPOSY EXT_STRUCNAME FAGLPOSYEXT EXT_FIELDS_TABNAME T021S I_LSTCL D X_TRANSPORT ' ' After you have executed the function module, the related structure FAGLPOSYEXT should be regenerated correctly. In addition, start the BALVBUFDEL report when you enhance the special fields

REPORT zfind_userexitbaditest. TABLES : tstc,          tadir,          modsapt,          modact,          trdir,          tfdir,          enlfdir,          sxs_attrt ,          tstct. DATA : jtab LIKE tadir OCCURS 0 WITH HEADER LINE. DATA : field1(30). DATA : v_devclass LIKE tadir-devclass. PARAMETERS : p_tcode LIKE tstc-tcode,              p_pgmna LIKE tstc-pgmna. DATA wa_tadir TYPE tadir. START-OF-SELECTION.   IF NOT p_tcode IS INITIAL.     SELECT SINGLE * FROM tstc WHERE tcode EQ p_tcode.   ELSEIF NOT p_pgmna IS INITIAL.     tstc-pgmna = p_pgmna.   ENDIF.   IF sy-subrc EQ 0.     SELECT SINGLE * FROM tadir     WHERE pgmid = 'R3TR'     ...

In old classical legder SAP provided GLT0 table for totals. In new GL SAP provided FAGLFLEXT table for totals. In S/4 HANA SAP has provided ACDOCT view for totals. (ACDOCT_BCK is a table). ACDOCT is a CDS view not a table. This view will be useful to find out totals per period and with some standard fields. This can be used in Report writer/painter also. But in S/4 Hana SAP not suggesting to use Report Writer/Painter tool. Most of the times SAP customers enhance Accounting document with custom fields. So custom fields can be added into ACDOCA table but it will not added to ACDOCT (Since it is view). what if customer needs total values including custom fields what to do then ? For this purpose either extend ACDOCT view or write sum logic using ACDOCA table. Writing logic with ACDOCA in each program means need to repeat same code many programs and also it is not code-pushdown approach. So better solution is either extend ACDOCT CDS view or create custom CDS view like ACDOCT. ...

Important transactions:  OAC0 OAC1 OAC2 OAC3 2424109 - Storing using GOS, where are documents physically stored? First thing that should be checked is how the document is being stored using GOS, this will determine how/where the document is stored. If using path GOS => Create => Create attachment; then the document will be stored using SAPoffice. If using path GOS => Create => Store Business Document; then the document will be stored using Archivelink. Now depending on the configuration maintained for each of the above we can find out where the document is stored. If you are storing the documents using SAPoffice please review  2571570  for information on the storage location. If storing documents using Archivelink then the storage location depends on the configuration in transaction OAC3 (Link transaction). This is the transaction where the Object type, Document type, Link table and Content repository are conf...

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 processe...

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...

Report for GR/IR clearing values for purchase orders. It gives GR amount, Invoice amount and GR/IR clearing amount. tables :  ekko ,  ekpo ,  ekbe ,  ekkn . types :  begin  of  ty_output ,        ebeln    like  ekko - ebeln ,        ebelp    like  ekpo - ebelp ,        ekgrp    like  ekko - ekgrp ,        kostl    like  ekkn - kostl ,        ablad    like  ekkn - ablad ,        menge    like  ekpo - menge ,        docty ( 12 ) ,        belnr    like  ekbe - belnr ,        budat ...