SAP Job Market
SAP job market is currently in a state of flux just like any other IT job. Where there used to be 10 jobs there are 4 or may be 5. Post recession, the reasons are obvious – Lack of budgets, postponing new implementations, general market slump etc.
However, all is not lost yet. There are still jobs. And more are going to come up as the economy slowly takes roots again and boomtown comes along. continue reading…
Ever wondered what the error codes mean when analyzing your AIS or trace logs? Here are some hints and how users or administrators should react to the messages:
1 Incorrect logon data (client, user name, password)
User: check the logon data entered (enter data again)
Admin: check the logon data for the service users, for example in the ITS service file
(usually wrong client) or in the RFC destinations
(usually wrong password)
continue reading…
To create custom transaction, it is suggested that you define the naming convention as simple as possible to make sure that users will remember the transaction and do not have to second guess. If a user needs a custom transaction to browse table MARA, you can either call the transaction ZSE16_MARA or simply ZMARA. continue reading…
White-collar crime is the fastest growing type of crime in North America, and co-workers and disgruntled employees have many motivations to cause damages or increase their wealth. Especially in the current economy it is every company’s responsibility to keep honest employees honest by preventing opportunities and temptation! The first thing intruders do before taking any illegal action is to get access to another colleague’s user profile for extended access so that the other person will be blamed. Below we will point out how easy this unfortunately is…
We know about one company that lost over $60 Million in a 4 year period. A director used one of his employee’s user profiles and passwords to commit the fraud in the SAP financial system. When the fraud was discovered, this employee spent half a year in jail for a crime that she did not commit. Eventually, her boss was arrested for stealing her password and committing the fraud. continue reading…
I am sure that your data governance is up do date and you are happy with your eCATT and LSMW scripts, or even happy that you saved some money to hire some interns or temps to enter data in your system. But why doing it the better & more cost effective way if you have money to burn? Just kidding!
bioLock is the first and only certified biometric 
No matter security on table editing. When in transaction SE16N use the command &SAP_EDIT in the command field in SAP and off you go: edit table content directly. This works if you have debug with changes access for object S_DEVELOP, but S_TABU_DIS is ignored as well as the system settings regarding changes. If you use this function for transaction, master data or other tables that cannot be changed with SM30, you can cause quiet some damage. So, use with caution and this is NOT a Best Practice by all means, but to educate you on a little documented feature:
Step 1: Use transaction SE16N or transaction N (yes, there is a transaction called just ‘N’) and enter a table of your choice, for example SKA1 G/L Account Master (Chart of Accounts)
2) In the command field enter ‘&SAP_EDIT’ and press enter. The maintenance indicator in SE16N will switch on.
3) Limit the search of your data or execute for all values and you will see, that the table entries can be edited:
If you limit the users access not to have access to S_DEVELOP with change activities for object type DEBUG, this function will not be possible (tested on ECC5)
If you want to allow this function, you can audit who changed data via SE16N by browsing the following tables;
SE16N_CD_KEY : Change Documents – Header
SE16N_CD_DATA : Change Documents – Data
You can also run report RKSE16N_CD via SE38 (or create a custom transaction for it for ease of use).
SAP Network Blog
Add
Add