COMMIT inside a BADI Implementation

Commit work in BADI Implementation is not advisable as it can lead to process inconsistencies.

• COMMIT WORK will end the Logical Unit of Work (LUW) and a new LUW will begin.

• COMMIT WORK will clear/refresh the buffers.

Debugging a Background Job

• In the Job Overview transaction SM37, select the job that has finished and enter jdbg in the command field. The Debugger will start. It will simulate the exact scenario with the same selection screen values, and the system variable SY-BATCH will be set to X (abap_true).

Differences between the Classic and the New ABAP Debugger

• The new ABAP Debugger is executed in its own external mode, while the application which is being debugged (debuggee) uses a different mode. This is two tier architecture that is the new debugger is displayed in its own GUI window. The debuggee is inactive while the debugger is active and vice versa that is debugger remains available in inactive mode when the program displays its final output. The debugger does not close while the application which is being debugged is still alive.

SAP Gateway Client /IWFND/GW_CLIENT Transaction Error - User no longer logged on

When trying to execute transaction /IWFND/GW_CLIENT or any other transactions in /IWFND/ namespace, many users get an error message 'User no longer logged on'.

It is believed that this problem is in older SAP GUI versions but as you can see in the image above, the error is there even in GUI version 760.

Solution

Append Structure and Include Structure

• Append structures are used for enhancements that are not included in the standard. 

• An append structure is a structure that is assigned exactly to one table or structure. 

• There can be more than one append structure for a table or structure.

• An Include structure can be assigned to many tables.

• On adding fields to an include structure, all tables/structures, which contain that include structure, will be updated.

Question Marks '?????' in Menu Bar instead of Menu Names

If the menu bar displayed in your custom report or in any other sap screen is like the image above, try deleting the language specific run time objects (Load).

To delete language specific run time objects execute the report RSLANG20.This resets the language buffers and reloads them from the database.

To access certain information more quickly, the SAP System optimizes the information in database tables and internal buffers.
This information must be deleted after a language import or supplementation.The language transport tools delete the language load automatically after completing an import or supplementation action. However, database locks may prevent the load from being deleted. This report enables you to delete the load manually in this case.
This report does not cause errors in the system and can be restarted at any time. However, you may experience a short drop in performance after starting the report.

Use the check boxes to select which load types you want to delete.
To delete a language-specific load, you must enter a target language. You also have the option of deleting the load for all languages installed in the system.

For more information, you can check the source code of the program or see SAP Note 110910.

Change Description of Transport Request

Description of an unreleased transport request can be changed in the following steps :

• Go to transaction SE10
• Select the request whose description needs to be changed and click on display or just double click on the tr number.
• Now on the new screen click on change (Ctrl + F1).
• Click on Properties Tab on the same screen.
• The description of the tr can be seen in editable mode.
• Change it as desired and click on Save button (Ctrl + S).

Please comment on the post if you find it useful, it will only take 2 seconds and will cost you nothing.