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…
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!
Entering into SAP can be challenging as depending on data volume, it may need multiple resources and the chance of human error should not be taken lightly. Many SAP customers do not want endusers using mass data entry tools such as Mass update transactions, LSMW or CATT Scripting on a regular basis as scripts can be time consuming to create and it may be difficult to train end-users on how to use these tools.
Besides the mass data entry for Sales Orders, Purchase Orders or changing of existing data, the manual entry also requires the users to enter data on multiple screens and analyze multiple fields to make sure they don’t enter the data in a incorrect field. These are just a few examples that you may encounter in your company. We are interested in learning more about what data entry challenges companies have. Please take a few minutes and answer the simple questions of our survey.
Click here to access the Survey.
There are quiet a few companies that want to give end-users access to extract table data via SE16 or SE16N. If you decide to give SE16N, please read our blog that shoes the pitfalls & danger of giving SE16N – In addition, the auditors, security people and basis folks worry about using having transactions such as SQVI, SQ01 etc…. Why is that? For starters, users can access confidential data once they can use SQVI as it is not protecting the data to be extracted by company code or other organizational values. A guideline on how to convert SQVI report into a InfoSet query will be published on this blog.
In addition, SQVI reports, if created poorly, can have a drag on system performance as the endusers never have performance in their minds and run queries over millions of records with inadequate table joins. The same applies to SQ01 – SQ03 transactions. These are a red flag for most of the auditors also if the user is allowed to add custom code on InfoSet level. Security managers usually recommend that SQxx transactions are used in a development environment and the queries mapped to transactions so that these can go through Change Control and given to users via roles in a controlled manner . continue reading…
Even with highly capable BI systems installed and operational at most companies, one of the top challenges reported by SAP end-users is the inability to easily access real-time SAP data in the transactional system. Enabling end-users to easily and securely query and extract transactional SAP data is critical for many purposes beyond BI for corporate performance measurement, including:
SAP Network Blog
Add
Add