SAP Stories

 Use transaction code " /SDF/TRCHECK" to find dependencies of transport in SAP

Use below program to updated status from released to modifiable and the target system. *&---------------------------------------------------------------------* *& Report ZTRANPORT_UPDATE *&---------------------------------------------------------------------* *& *&---------------------------------------------------------------------* REPORT  ZTRANPORT_UPDATE .    TABLES :  e070 ,  e070c , e07t .    DATA :  ls_e070   LIKE  e070 ,         ls_e070c  LIKE  e070c ,         ls_e07t   LIKE  e07t .    DATA :  lv_msgtext1  LIKE  sy - msgv3 ,         lv_msgtext2  LIKE  sy - msgv3 ,         lv_msgtext3  LIKE  sy - msgv3 .    CLEAR  ls_e070 .   ...

1. Run report RSGOSCHECK 2. if you find service " J3RF_IMCD" is multi  activated then  3. Go to transaction code:  SGOSM. remove the entry " J3RF_IMCD" Other notes  The modifications from standard Available GOS BAdI implementations If there are customer own entries in table SGOSATTR (like IXOS_XL for instance), check the attachment of the note  1401005  to get more info how to insert non-standard services in table SGOSATTR correctly Some applications (for example sales and distribution) deactivate the object services in standard. This can be activated with user parameter SD_SWU_ACTIVE. For more information, please read the note:  598073  - Message "No service available"

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