USR01User master record (run-time data) USR02 Logon data USR03 User address data USR04 User master authorizations USR05 User Master Parameter ID USR06 Additional data per user USR07 Object/values of last failed authorization check USR08 Table for user menu entries USR09 Entries for user menus (work areas) USR10 User master authorization profiles USR11 User Master Texts for Profiles (USR10) USR12 User master authorization values
USR13 Short Texts for Authorizations USR14 Surchargeable language versions per user USR15 External User Name USR20 Date of last user master reorganization USR30 Additional Information for User Menu USR40 Table for illegal passwords USR41 User master: Additional data USRCOBJ Object Filters for Exploding Product Structures USRM0 Material Master User Settings: User Screen Reference USRM1 Material Master User Settings: Organizational Levels USRM2 Material Master User Settings: Logical Screens USRMM User settings: material master
Monday, March 16, 2009
SAP Script
Transaction codes SE71
Form painter SE72
Style maintenance SE78
SapScript Graphics Management
SO10 Create standard text module
Form painter SE72
Style maintenance SE78
SapScript Graphics Management
SO10 Create standard text module
Modifying Structures of table containing data
> I need to add a new field to the structure of an existing table which> contains data.Is there any risk of losing the data if the structure is> modified.
A1:
Use append structure and there is no risk.Recently I have extended VEKP (Shipping unit header) this way.Dominik
A2:
I've had experience with this in the past. I've found that as long as youfollow the SAP recommended approach, which is to create an APPEND structure byhitting the "Append Structures..." button when in Table Display / Change,everything should be okay. This also ensures that your custom data is not lostin the event of an upgrade.
A3:
Remeber these alterations when you, or your Basis staff, upgrades your SAP
system(s). There is a phase in the upgrade where the R/3 tool (transaction)SPDD is executed. SPDD compares SAP tables that are being imported/changedin the applied upgrade with the current state of those same tables in theexisting system. When it detects differences (i.e. customer has addedcustom fields to SAP table) it ASKS you what to do. Your choices are to"Return to SAP standard" or to add the custom fields to "appendstructures".
Returning to SAP standard is easy to explain; the custom fields are droppedand the table is "converted". This means the ENTIRE contents of thealtered table is exported to disk, the table is dropped and re-definedaccording to the current SAP standard for that table (including any new
fields that SAP added during the upgrade) and then the data is re-imported.This means two things: the data in the custom fields is lost forever ANDif the table is huge, the upgrade process takes several more hours to allowfor the table conversion.
If you choose to keep your custom fields during the upgrade, R/3 adds themautomatically to an append structure. Any fields that SAP themselves haveadded to the table are appended to the end of the physical table.
Append structures is an SAP R/3 concept. Logically, it looks like you haveall the fields in one table. In reality, any fields that are part of thetable in a the append structure (look in SE11 for append structureinformation for a table) are actually stored in a separate, R/3 maintained
table. When operations occur against a table with append structures,special ABAP/4 auto-generated routines are executed that use additional SQLto go after the custom fields stored elsewhere through append structures.
The benefit here is that when new "custom" fields are added to an SAP tablewith append structures, the base SAP table is not changed. This means noconversion needs to occur during an upgrade. The problem is that now youhave extra overhead, i.e. 2 reads versus 1, updaters may also experiencehits if fields are indexed, for every access to your table.
Bottom line, you can do this, no problem, but there are down-streamramifications that should be considered....
A1:
Use append structure and there is no risk.Recently I have extended VEKP (Shipping unit header) this way.Dominik
A2:
I've had experience with this in the past. I've found that as long as youfollow the SAP recommended approach, which is to create an APPEND structure byhitting the "Append Structures..." button when in Table Display / Change,everything should be okay. This also ensures that your custom data is not lostin the event of an upgrade.
A3:
Remeber these alterations when you, or your Basis staff, upgrades your SAP
system(s). There is a phase in the upgrade where the R/3 tool (transaction)SPDD is executed. SPDD compares SAP tables that are being imported/changedin the applied upgrade with the current state of those same tables in theexisting system. When it detects differences (i.e. customer has addedcustom fields to SAP table) it ASKS you what to do. Your choices are to"Return to SAP standard" or to add the custom fields to "appendstructures".
Returning to SAP standard is easy to explain; the custom fields are droppedand the table is "converted". This means the ENTIRE contents of thealtered table is exported to disk, the table is dropped and re-definedaccording to the current SAP standard for that table (including any new
fields that SAP added during the upgrade) and then the data is re-imported.This means two things: the data in the custom fields is lost forever ANDif the table is huge, the upgrade process takes several more hours to allowfor the table conversion.
If you choose to keep your custom fields during the upgrade, R/3 adds themautomatically to an append structure. Any fields that SAP themselves haveadded to the table are appended to the end of the physical table.
Append structures is an SAP R/3 concept. Logically, it looks like you haveall the fields in one table. In reality, any fields that are part of thetable in a the append structure (look in SE11 for append structureinformation for a table) are actually stored in a separate, R/3 maintained
table. When operations occur against a table with append structures,special ABAP/4 auto-generated routines are executed that use additional SQLto go after the custom fields stored elsewhere through append structures.
The benefit here is that when new "custom" fields are added to an SAP tablewith append structures, the base SAP table is not changed. This means noconversion needs to occur during an upgrade. The problem is that now youhave extra overhead, i.e. 2 reads versus 1, updaters may also experiencehits if fields are indexed, for every access to your table.
Bottom line, you can do this, no problem, but there are down-streamramifications that should be considered....
Thursday, March 5, 2009
SAP Netviewer
SAP NetWeaver is an ambitious vision for improving Information Technology, including the software and hardware that runs the world of business. But SAP NetWeaver is not just a vision: It’s a set of tools and methodologies that can take your company where it needs to go.
Admittedly, SAP NetWeaver is not your normal topic for a For Dummies book. It’s not a hobby such as yoga, sailing, or personal finance. It’s not a word processor or even a programming language. SAP NetWeaver is a super-sized serving of technology and tools made up of products and concepts that are useful to the corporate decision maker and the technologists who work together to solve huge information challenges.
With SAP NetWeaver, you can
Make one portal that gives each user exactly what he needs from all your applications.
Provide a unified view of information from every part of your company and deliver it to employees just when and how they need it.
Knit together into one streamlined interface processes that are distributed in bits across many applications.
And because it is based on the latest technology and approaches to business processes, SAP NetWeaver also increases flexibility and enables change throughout your enterprise.
Admittedly, SAP NetWeaver is not your normal topic for a For Dummies book. It’s not a hobby such as yoga, sailing, or personal finance. It’s not a word processor or even a programming language. SAP NetWeaver is a super-sized serving of technology and tools made up of products and concepts that are useful to the corporate decision maker and the technologists who work together to solve huge information challenges.
With SAP NetWeaver, you can
Make one portal that gives each user exactly what he needs from all your applications.
Provide a unified view of information from every part of your company and deliver it to employees just when and how they need it.
Knit together into one streamlined interface processes that are distributed in bits across many applications.
And because it is based on the latest technology and approaches to business processes, SAP NetWeaver also increases flexibility and enables change throughout your enterprise.
Sunday, March 1, 2009
Characteristics of SAP R/3
- Rich in functionality
- International Orientation
- Tight integration-across functions
- Incorporates 20 years of experience
- Highly configurable
- Highly secure data handling
- seamless handling of database.Accurate order promising
- Minimum data redundancy
- World-wide standerdization
- capitalize on economics of scale e.g purchasing
- Business practices-world wide are incorporated
What is SAP R/3?
It is the third generation set of highly integrated software modules that perform common business function baed on multi-national leading practices.Takes care of any enterprise however diverse it may be in operations, spread over the world geographically.
About Begining
FROM START-UP SOFTWARE VENDOR TO GLOBAL MARKET LEADER
Over the course of three decades, SAP has evolved from a small, regional enterprise into a world-class international company. Today, SAP is the global market leader in collaborative, inter-enterprise business solutions. The company now employs more than 39,300 people, whose commitment and innovative spirit pace our future success.
The 1970s: A Real-Time Vision
In 1972, five former IBM employees — Dietmar Hopp, Hans-Werner Hector, Hasso Plattner, Klaus Tschira, and Claus Wellenreuther — launch a company called Systems, Applications, and Products in Data Processing in Mannheim, Germany. Their vision: to develop standard application software for real-time business processing. One year later, the first financial accounting software is complete, forming the basis for the continuous development of other software components in what later came to be known as the “R/1 system.” “R” stands for real-time data processing. By the end of the decade, intensive examination of SAP’s IBM database and dialog control system leads to the birth of SAP R/2.
The 1980s: Rapid Growth
SAP moves into the company’s first building on Max-Planck-Strasse in an industrial park in Walldorf, near Heidelberg. Our software development area and its 50 terminals are all now under one roof. Fifty of the 100 largest German industrial firms are already SAP customers.The SAP R/2 system attains the high level of stability of the previous generation of programs. Keeping in mind its multinational customers, SAP designs SAP R/2 to handle different languages and currencies. With this and other innovations in SAP R/2, SAP sees rapid growth.By the middle of the decade, SAP founds its first sales organization outside Germany, in Austria. The company makes its first appearance at the CeBIT computer fair in Hanover, Germany. Revenues reach DM 100 million (around $52 million), earlier than expected.In August 1988, SAP GmbH becomes SAP AG. Starting on November 4, 1.2 million shares are listed on the Frankfurt and Stuttgart stock exchanges. Germany’s renowned business journal, manager magazine, names SAP its Company of the Year — a distinction we would receive twice more in the next few years.With the founding of subsidiaries in Denmark, Sweden, Italy, and the United States, SAP’s international expansion takes a leap forward.
The 1990s: A New Approach to Software and Solutions
SAP R/3 is unleashed on the market. The client-server concept, uniform appearance of graphical interfaces, consistent use of relational databases, and the ability to run on computers from different vendors meets with overwhelming approval. With SAP R/3, SAP ushers in a new generation of enterprise software — from mainframe computing to the three-tier architecture of database, application, and user interface. To this day, the client-server architecture is the standard in business software. A growing number of subsidiaries are managed out of Walldorf. The new Sales and Development Center in Walldorf officially opens it doors. It symbolizes the global success of the company. In our twentieth year, our business outside Germany exceeds 50 percent of total sales for the first time.By 1996, the company has earned 1,089 new SAP R/3 customers. At the end of the year, SAP R/3 has been installed in more than 9,000 systems worldwide.SAP celebrates its twenty-fifth anniversary in 1997 and now employs approximately 12,900 people. We continue to strengthen our industry focus and build more and more industry-specific solutions. Henning Kagermann becomes Co-Chairman and CEO of SAP AG with Hasso Plattner. On August 3, 1998, the letters S-A-P appear for the first time on the Big Board at the New York Stock Exchange (NYSE), the largest stock exchange in the world. As the decade draws to a close, Hasso Plattner, Co-Founder, Co-Chairman, and CEO announces the mySAP.com strategy, heralding the beginning of a new direction for the company and our product portfolio. mySAP.com links e-commerce solutions to existing ERP applications, using state-of-the-art Web technology.
The 2000s: Innovation for the New Millennium
With the Internet, the user becomes the focus of software applications. SAP develops SAP Workplace and paves the way for the idea of an enterprise portal and role-specific access to information.Currently, more than 12 million users work each day with SAP solutions. There are now 121,000 installations worldwide, more than 1,500 SAP partners, over 25 industry-specific business solutions, and more than 41,200 customers in 120 countries. SAP is the world’s third-largest independent software vendor.
Subscribe to:
Posts (Atom)
