Scribd
Upload
5 views

History

The document outlines the functionalities of a work scheduling and cost tracking system for maintenance activities, including resource allocation and cost monitoring. It discusses methods and attributes in ABAP for managing equipment and maintenance plans, as well as integration with other SAP modules. Additionally, it addresses the trust and security aspects of wikis, including user roles, content control, and the reliability of publicly editable content.

Uploaded by

putluruneeraj
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
5 views

History

The document outlines the functionalities of a work scheduling and cost tracking system for maintenance activities, including resource allocation and cost monitoring. It discusses methods and attributes in ABAP for managing equipment and maintenance plans, as well as integration with other SAP modules. Additionally, it addresses the trust and security aspects of wikis, including user roles, content control, and the reliability of publicly editable content.

Uploaded by

putluruneeraj
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Change

Functional
Ay Documentation Location

1. Introduction- **Work Scheduling**:


Plan and allocate resources, labor, and
materials for maintenance activities.
- **Cost Tracking and Settlement**:
Monitor costs related to maintenance
tasks, including Concept Documentation
cation development and maintenance.

2.3 Tables
Tabl

2.2 Data Elements


Data elements define the semantic meaning of a table field or a structure
component. They

installation, operation, and maintenance of equipment at specific locations.

subroutine ___. intenral subroutine and external subroutine

- **Equipment and Functional Locations**: Track and manage the

wherein a term in natural language could be wrapped


in special characters to turn it into a link without
modifying it. The concept was given the name in its
first implementation, in UseModWiki in February 2001.
[16] In that implementation, link terms were wrapped in
a double set of square brackets, for
example [[Kingdom offer full text search of all stored
content.
Navigation between wikis
Visualization of the collaborative work in the German
wiki project Mathe für Nicht-Freaks
"WikiNode" redirects here. For the app for the Apple
iPad, see WikiNodes.
Some wiki communities have established navigational
networks between each other using a system
called WikiNodes. A WikiNode is a page on a wiki which
describes and links to other, related wikis. Some wikis
operate a structure of neighbors and delegates,
wherein ,[25] as indexed database access is faster on
large wikis, particularly for searching.

editing to users, in recent years some implementations


have added a rich text editing mode. This is usually
implemented, using JavaScript, as an interface which
translates formatting instructions chosen from
a toolbar into the corresponding wiki markup or HTML.
This is generated and submitted to the
server transparently, shielding users from the
technical detail of markup editing and making it easier
for them to change the content of pages. An example
of such an interface is the VisualEditor in MediaWiki,
the wiki engine used by Wikipedia. WYSIWYG editors
may not provide all the features available in wiki
markup, and some users prefer not to use them, so a
source editor will often be available simultaneously.

Version history

3. Methods and Attributes in


ABAP
3.1 Methods

IL03 Display
Functional
Location
IE01 Create
Equipment
IE02 Change
Equipment
IE03 Display
Equipment
IP01 Create
Maintenance
Plan
IP02 Change
Maintenance
Plan
IP03 Display
Maintenance
Plan
IP10 Schedule
Maintenance
Plan
labor, materials, and services, and settle these costs to the appropriate cost objects.

3. Integration with Other SAP Modules


Hosting
See also: Comparison of wiki hosting services
Wikis can also be created on wiki hosting services (also known
as wiki farms), where the server-side software is implemented by
the wiki farm owner, and may do so at no charge in exchange
for advertisements being displayed on the wiki's pages. Some
hosting services offer private, password-protected wikis
requiring authentication to access. Free wiki farms generally contain
advertising on every page.

Trust and security


Access control
The four basic types of users who participate in wikis are readers,
authors, wiki administrators and system administrators. System
administrators are responsible for the installation and maintenance
of the wiki engine and the container web server. Wiki administrators
maintain content and, through having elevated privileges, are
granted additional functions (including, for example, preventing
edits to pages, deleting pages, changing users' access rights, or
blocking them from editing).[26]

Controlling changes
"Recent changes" redirects here. For the Wikipedia help page,
see Help:Recent changes. For the recent changes page itself,
see Special:RecentChanges.

History comparison reports highlight the


changes between two revisions of a page.
Wikis are generally designed with a soft security philosophy in which
it is easy to correct mistakes or harmful changes, rather than
attempting to prevent them from happening in the first place. This
allows them to be very open while providing a means to verify the
validity of recent additions to the body of pages. Most wikis offer
a recent changes page which shows recent edits, or a list of edits
made within a given time frame.[27] Some wikis can filter the list to
remove edits flagged by users as "minor" and automated edits.
[28] The version history feature allows harmful changes to be
reverted quickly and easily.[13]

Some wiki engines provide additional content control,


allowing remote monitoring and management of a page or set of
pages to maintain quality. A person willing to maintain pages will be
alerted of modifications to them, allowing them to verify the validity
of new editions quickly.[29] Such a feature is often called a watchlist.

Some wikis also implement patrolled revisions, in which editors with


the requisite credentials can mark edits as being legitimate.
A flagged revisions system can prevent edits from going live until
they have been reviewed.[30]

Wikis may allow any person on the web to edit their content without
having to register an account on the site first (anonymous editing),
or require registration as a condition of participation. [31] On
implementations where an administrator is able to restrict editing of
a page or group of pages to a specific group of users, they may
have the option to prevent anonymous editing while allowing it for
registered users.[32]

Trustworthiness and reliability of content


Critics of publicly editable wikis argue that they could be easily
tampered with by malicious individuals, or even by well-meaning
but unskilled users who introduce errors into the content.
Proponents maintain that these issues will be caught and rectified
by a wiki's community of users.[2][17] High editorial standards in
medicine and health sciences articles, in which users typically use
peer-reviewed journals or university textbooks as sources, have led
to the idea of expert-moderated wikis.[33] Wiki implementations
retaining and allowing access to specific versions of articles has
been useful to the scientific community, by allowing expert peer
reviewers to provide links to trusted version of articles which they
have analyzed.[34]

You might also like