Scribd
Upload
7 views3 pages

SAP PM Module T-Codes Overview

The document discusses the evolution and definitions of wikis, highlighting their use in education and enterprise settings for collaborative software. It also touches on the technical aspects of wiki implementations, including version control and edit histories. Additionally, it briefly covers programming concepts such as inheritance, polymorphism, encapsulation, and abstraction, as well as the SAP Plant Maintenance module and its transaction codes.

Uploaded by

putluruneeraj
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
7 views3 pages

SAP PM Module T-Codes Overview

The document discusses the evolution and definitions of wikis, highlighting their use in education and enterprise settings for collaborative software. It also touches on the technical aspects of wiki implementations, including version control and edit histories. Additionally, it briefly covers programming concepts such as inheritance, polymorphism, encapsulation, and abstraction, as well as the SAP Plant Maintenance module and its transaction codes.

Uploaded by

putluruneeraj
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

and some schools and universities use wikis to enhance group

learning. On March 15, 2007, the word wiki was listed in the
online Oxford English Dictionary.[22]

Alternative definitions
In the late 1990s and early 2000s, the word "wiki" was used to refer to
both user-editable websites and the software that powers them, and
the latter definition is still occasionally in use. [1]

By 2014, Ward Cunningham's thinking on the nature of wikis had


evolved, leading him to write[23] that the word "wiki" should not be
used to refer to a single website, but rather to a mass of user-editable
pages or sites so that a single website is not "a wiki" but "an instance
of wiki". In this concept of wiki federation, in which the same content
can be hosted and edited in more than one location in a manner
similar to distributed version control, the idea of a single discrete "wiki"
no longer made sense.[24]

Implementations
See also: List of wiki software
The software which powers a wiki may be implemented as a series
of scripts which operate an existing web server, a
standalone application server that runs on one or more web servers, or
in the case of personal wikis, run as a standalone application on a
single computer. Some wikis use flat file databases to store page
content, while others use a relational databaseIL02
hile wiki engines have traditionally offered source says his goals were
to link together people's experiences to create a new literature to
document programming patterns, and to harness people's natural
desire to talk and tell stories with a technology that would feel
comfortable to those not used to "authoring". [20]

Wikipedia became the most famous wiki site[clarification needed],


launched in January 2001 and entering the top ten most popular
websites in 2007. In the early 2000s, wikis were increasingly adopted
in enterprise as collaborative software. Common uses included project
communication, intranets, and documentation, initially for technical
users. Some companies use wikis as their collaborative software and
as a replacement for static intranets, Some wiki implementations keep
a record of changes made to wiki pages, and may store every version
of the page permanently. This allows authors to revert a page to an
older version to rectify a mistake, or counteract a malicious or
inappropriate edit to its content.[13]
These stores are typically presented for each page in a list, called a
"log" or "edit history", available from the page via a link in the
interface. The list displays metadata for each revision to the page,
such as the time and date of when it was stored, and the name of the
person who created it, alongside a link to view that specific revision.
A diff (short for "difference") feature may be available, which highlights
the changes between any two revisions.

Edit summaries
"Edit summary" redirects here. For the Wikipedia help page,
see Help:Edit summary.

W2.3 Inheritance
Inheritance is a mechanism that allows one class to acquire the attributes and methods of
another class. In ABAP, a class can inherit from another class using the 'INHERITING FROM'
keyword. This promotes code reuse and enhances modularity.

2.4 Polymorphism
Polymorphism allows objects of different classes to be treated as objects of a common
superclass. This is achieved through method overriding, where a method in a subclass has
the same name as a method in the superclass, but with different behavior.

2.5 Encapsulation
Encapsulation is the concept of bundling data and methods that operate on that data within
a single unit (class). It restricts direct access to some of the object's components, which
helps to protect the integrity of the data. In ABAP, encapsulation is achieved by defining
attributes as private or protected.

2.6 Abstraction

Abstraction is the process of hiding the implementation details and


showing only the essential features of an object. This allows the user to
focus on high-level operations withouSAP PM Module T-Codes
The SAP Plant Maintenance (PM) module is an essential component of the SAP ERP system.
It helps organizations manage maintenance activities, including inspection, preventive
maintenance, and repairs. Below is a list of common T-Codes (Transaction Codes) used in
the SAP PM module.

T-Code Description
IW21 Create Maintenance Notification
IW22 Change Maintenance Notification
IW23 Display Maintenance Notification
IW31 Create Maintenance Order
IW32 Change Maintenance Order
IW33 Display Maintenance Order
IL01 Create Functional Location

Common questions

Powered by AI

The 'diff' feature highlights changes between two revisions, allowing users to see exactly what has been modified, which improves transparency and accountability. The 'edit history' maintains a record of all changes, including metadata like the date and editor's identity, enabling easy reversion to previous states in case of errors or vandalism .

Polymorphism allows objects from different classes to be treated as objects of a common superclass. This is achieved through method overriding, where subclasses modify the behavior of inherited methods. Polymorphism enhances flexibility and maintainability in code, as it allows developers to use the same interface for different underlying forms, leading to cleaner and more efficient code management .

Using flat file databases for wikis can simplify the implementation by reducing complexity in setup and operation, making them suitable for smaller or personal-oriented wikis. In contrast, relational databases offer more robust data handling capabilities, improved query efficiency, and scalability, which are essential for larger and enterprise-level wikis that require complex data manipulation and retrieval .

Inheritance improves code modularity by allowing new classes to derive properties and behavior from existing ones, promoting reusability and logical organization of code. As new requirements emerge, developers can extend existing code rather than rewriting it, which enhances the maintainability and scalability of the system. It supports a hierarchical classification of data models which is essential for large-scale software development .

Cunningham's philosophy of wiki federation extends beyond individual user-editable websites by emphasizing a network of interconnected, editable spaces. This approach breaks down silos, fostering a collective body of knowledge where content can propagate and evolve across different platforms. The relationship is thus a shift from isolated content creation to a dynamic, distributed system enhancing community-driven expansion and redundancy .

Wikipedia stands as a significant case study due to its successful implementation of wiki technology on a massive scale, becoming one of the most visited websites globally by 2007. It illustrates the scalability and community-based knowledge curation potential of wikis. Wikipedia's model emphasizes the viability of wikis in harnessing collective intelligence for large-scale knowledge management .

Wikis offer several advantages over traditional intranets in enterprise settings, including improved collaboration by allowing multiple users to edit content in real-time and maintain a log of changes. They also enhance communication by providing a dynamic platform for project documentation and knowledge sharing, adaptable to the needs of technical and non-technical users alike .

Encapsulation contributes to data integrity by bundling data and the methods that operate on it within a single unit, or class. It restricts direct access to the object’s components by defining attributes as private or protected, thereby safeguarding against unauthorized or unintended modifications. This enhances the security and integrity of the data .

Ward Cunningham's conceptualization of 'wiki' evolved from referring to a single user-editable website or the software behind it, to a broader concept called wiki federation. He suggested that 'wiki' should refer to a network of user-editable pages distributed across different locations similar to distributed version control. This implies that the modern understanding of wikis involves interconnected sites rather than standalone ones, promoting broader collaboration and data sharing .

Wiki software in educational institutions enhances group learning by allowing students to collaboratively create and edit content. This fosters peer-to-peer learning, critical thinking, and a more active engagement with the material. Wikis can also serve as platforms for students to undertake research projects collaboratively, providing them with skills in digital collaboration and information management .

You might also like