Toolkit for SAP consultants

Log and monitor messages for your application The Application Log is a tool for collecting messages, saving, reading, and deleting logs in the database and displaying logs. These messages are not to be output individually (with the ABAP commands MESSAGE and Raise), they are to be collected and displayed later as a log. Message attributes Message type - this parameter determines the color of the icon when viewing the log Importance level - records are automatically divided into categories based on this attribute Sorting criterion - a word of three characters, a sign for grouping and sorting messages Detail level - a number from 1 to 9 inclusive, can participate in filters Additional information - an arbitrary set of parameters and a link to a function module or procedure for displaying it. Can be used, for example, to attach the HTTP header of the server response to a data transfer error message, or to invoke a transaction with parameters  Functions Logs are displayed using function

via File interface (Dateischnittstelle) via Remote Function Call (RFC)  Business Application Programming Interface (BAPI) Application Link Enabling (ALE) IDocs SOAP OData ABAP channels  bgRFC Programming Information (22.09.2021) 1793313 - ALE: IDoc inbound processing using bgRFC as standard 2183108 - t/qRFC processing: general performance verifications via File interface (Dateischnittstelle) Call-Transaction-Program Methods of the global class CL_GUI_FRONTEND_SERVICES are available for files on presentation servers. Batch-Input Direct Input via Remote Function Call (RFC) is the SAP interface technology allowing to call a  function in another system or internally Authorizations for RFC Monitoring und Troubleshooting Monitoring the output queue:  SMQ1 for monitoring the outgoing queues  Use transaction SBGRFCMON to track how your bgRFC inbound bgRFC monitor calls are processed. RFC Destinations Connection type 3: The target system is an SAP system Connection type T:

TVARVC Seat leaf How to display documentation? There are a few options to struct and simplify the maintenance of customer-project-function-specific customizing. This own customizing can then be called from your custom programs, user-exits, and enhancement points. Managing these custom tables becomes increasingly difficult over time.   Therefore, it should be a decision at the beginning of the project on how to struct and organize these data.  Here is the list of possibilities we can apply in our developments:  Own customizing in SPRO - Document customizing  Use T-code S_IMG_EXTENSION - IMG maintenance(note: when using the S_IMG_EXTENSION option SAP puts your entries aside and we can re-merge them after the upgrade) Enhance structure> Create Enhancement ID, Enhance the structure Add a note Add an activity Customizing activity ID Assign the object using one of the allowed types: View cluster, Logical transport object, Table (with text table), Individual transaction object, Vi