Table EKBEH contains aggregated Po history datra. Sometimes , for eample in scheduling agreement, there are huge Po history (GR and iR document) and thus it cause performance issue during posting of new invoice etc. Then for performance improvement, PO history can be aggregated using txn ME87 and thus reducing the number of entries in PO history table (EKBE).
Please see inforation in note 311089 "Performance problems because of long PO history" how this help in improving performance.
Note : 311089
星期五, 五月 20, 2011
星期四, 五月 19, 2011
CPUDT BLDAT BUDAT difference
Entry Date CPUDT - Entry date is the date when the doc is entered
Document Date BLDAT - User Specified Document Date
Posting Date BUDAT - Posting date also specified by the user
Document Date BLDAT - User Specified Document Date
Posting Date BUDAT - Posting date also specified by the user
星期一, 五月 16, 2011
Add storage location to existing material
Link
Use MM01 Tcode to extend the material to storage location level.
Use MMSC to add more storage location to the material.
If the number of materials are more than Use LSMW tool to extend the storage locations.
At any point of time you can extend the material to the storage location.
Use MM01 Tcode to extend the material to storage location level.
Use MMSC to add more storage location to the material.
If the number of materials are more than Use LSMW tool to extend the storage locations.
At any point of time you can extend the material to the storage location.
ABAP Tip-How to Debug Pop-up window
Via SAPshortcut you can create a system-independent debugger shortcut.
Solution 1:
To do this click on the Windows desktop and display the context menu (right mouse button). Select New->SAP Shortcut. Call the file Debugger.sap. Call 'Edit' with the right mouse button on the newly created file. A processing dialog of the SAPshortcut is displayed. Leave the fields empty, change the fields 'Type' and 'Command'.
Set the type to 'System command' and set the command to '/H'.
Close the dialog. The debugger shortcut is now defined. You can drag and drop it on the corresponding SAPGui dialog box. This way the debugger is activated, and it is accessed with the next user interaction.
Solution 2:
Generate a new text file. Edit it with any ASCII editor. Insert the following contents:
------------ 8< cut >8 -----------------
[Function]
Command=/H
Title=Debugger
Type=SystemCommand
-------------8< cut >8 -----------------
Save the file and rename it as 'Debugger.sap'.
This way the shortcut is defined. You can now drag and drop it to the SAPGui in order to activate the debugger.
Solution 1:
To do this click on the Windows desktop and display the context menu (right mouse button). Select New->SAP Shortcut. Call the file Debugger.sap. Call 'Edit' with the right mouse button on the newly created file. A processing dialog of the SAPshortcut is displayed. Leave the fields empty, change the fields 'Type' and 'Command'.
Set the type to 'System command' and set the command to '/H'.
Close the dialog. The debugger shortcut is now defined. You can drag and drop it on the corresponding SAPGui dialog box. This way the debugger is activated, and it is accessed with the next user interaction.
Solution 2:
Generate a new text file. Edit it with any ASCII editor. Insert the following contents:
------------ 8< cut >8 -----------------
[Function]
Command=/H
Title=Debugger
Type=SystemCommand
-------------8< cut >8 -----------------
Save the file and rename it as 'Debugger.sap'.
This way the shortcut is defined. You can now drag and drop it to the SAPGui in order to activate the debugger.
The okcode field is deactivated when a modal window (the technical name of popup windows) is displayed, so it seems impossible to enter the debugger (using /H okcode).
In common dialogs, the okcode field is available:
But it is not available in modal windows (we see it but we can't enter anything in it):
The solution is to create on the frontend a SAPGUI shortcut (file with extension .SAP), of type System Command and command /H, and drag and drop it from Windows desktop to the SAP modal window. The creation of SAPGUI shortcuts is explained here: SAPGUI shortcuts.
Run tcode without authorisation
If you are not authorised to run a particular SAP transaction you can still execute it via the use of the debugger. Obvioulsy care needs to be taken that you know what you are doing with the transaction in question, but there are many instances when this method can not only be useful but a life saver. Plus I believe any changes made during debugging are, or at least can be recorded in a log somewhere. The process for getting past the debug authority is as follows:
Step 1 - Insert debug breakpoint
Within Function module 'AUTH_CHECK_TCODE' insert a break-point the ABAP code line 'if sy-subrc = 0.', straight after the call 'AUTH_CHECK_TCODE' id 'TCODE' field tcode command.
Step 2 - Execute your desired SAP transaction code
Execute your tcode and SAP should go into debugging mode and stop at your break point. If it doesn't type /h into the command line field(where you enter transactions) and press enter, then try executing your transaction code again. If it stops at a point which is not where you inserted the breakpoint in step 1 keep pressing F8 until it gets to it!
Step 3 - Change SY-SUBRC value
When the code reaches the 'if sy-subrc = 0' statement, sy-subrc should have a value not equal to 0 if you are not authorised for this transaction. Change this to 0 using the usual method relevant to your system (i.e. by clicking on the change pencil icon, change value and press enter). When value is changed press F8 to continue the SAP program on its way.
Step 1 - Insert debug breakpoint
Within Function module 'AUTH_CHECK_TCODE' insert a break-point the ABAP code line 'if sy-subrc = 0.', straight after the call 'AUTH_CHECK_TCODE' id 'TCODE' field tcode command.
Step 2 - Execute your desired SAP transaction code
Execute your tcode and SAP should go into debugging mode and stop at your break point. If it doesn't type /h into the command line field(where you enter transactions) and press enter, then try executing your transaction code again. If it stops at a point which is not where you inserted the breakpoint in step 1 keep pressing F8 until it gets to it!
Step 3 - Change SY-SUBRC value
When the code reaches the 'if sy-subrc = 0' statement, sy-subrc should have a value not equal to 0 if you are not authorised for this transaction. Change this to 0 using the usual method relevant to your system (i.e. by clicking on the change pencil icon, change value and press enter). When value is changed press F8 to continue the SAP program on its way.
星期四, 五月 05, 2011
SNOTE
Link
Implementing an OSS note via SAP note assistant
The table below outlines the simple steps required to implement an OSS note using SAP note assistant (SNOTE).
Implementing an OSS note via SAP note assistant
The table below outlines the simple steps required to implement an OSS note using SAP note assistant (SNOTE).
| Step | Icon | Description |
| 1 |  or  | Download note (differnt icon depending on your version of SAP) |
| 2 |  | Set process status to in process |
| 3 |  | Read note instructions |
| 4 |  | Implement note (popup will appear allowing you to read note) |
| 5 |  | View implementation log, add comments of your own |
| 6 |  | Set status to Complete |