Organisation Structure - CS and PM
-
Upload
swame-kumar -
Category
Documents
-
view
221 -
download
0
Transcript of Organisation Structure - CS and PM
-
7/29/2019 Organisation Structure - CS and PM
1/9
1: Organisation Structure
1.1 Maintain Maintenance Planning Plant
1.2 Assign Maintain Maintenance Planning Plant to Maintenance Plant
2 Part-2: Global Settings
3 Part-3: Baseline Settings
3.1 Master Data Settings
3.1.1 Define User Status
3.1.2 Create Authorization Keys for User Status Authorizations
3.1.3 Define Currency for Maintenance statistics
3.1.4 Define Permit categories
3.1.5 Define Measuring Point categories
3.1.6 Create Number Range for Measuring Points
3.1.7 Create Number Range for Measuring documents
3.1.8 Define Warranty Types
3.1.9 Define number range for Warranty Types
3.1.10 Maintain Transaction Start Default Values for Sample Warranties
3.1.11 Define Warranty counters
3.1.12 Define object information keys3.1.13 Define Types of Technical Objects
3.1.14 Define Plant-sections
3.1.15 Define Planner Group
3.1.16 Define ABC Indicators
3.1.17 Define Authorization Group
3.1.18 Set View profile for Technical objects
3.1.19 Create Structure Indicator for Reference Locations / Functional Locations
3.1.20 Define Category of Functional Location
3.1.21 Maintain Equipment Category
3.1.22 Define additional business views for Equipment categories
3.1.23 Define number ranges
3.1.24 Usage history update
3.1.25 Define history related fields
3.1.26 Define installation at Functional Location
3.1.27 Define Media for Object Links
3.1.28 Define Number Ranges for Object Links
3.1.29 Define Serial Number Profile
3.1.30 Define default Equipment categories for Serial Numbers
3.2 Maintenance Plans, Work centres and Task Lists
3.2.1 Set Maintenance Plan Categories
3.2.2 Define Number Ranges for Maintenance Plan
3.2.3 Define Number Ranges for Maintenance Items
3.2.4 Define Sort fields for Maintenance Plan3.2.5 Define Employees responsible for Work centres
3.2.6 Configure Planner Group
3.2.7 Define Number ranges for General Maintenance Task List
3.2.8 Define Number ranges for Equipment Task List
3.2.9 Define Number ranges for Task list for Functional Location
3.2.10 Define profiles with default Values
3.3 Maintenance Processing
3.3.1 Overview of Notification Type
3.3.2 Define Notification Types
3.3.3 Set Field Selection for Notifications
3.3.4 Define Number ranges
3.3.5 Define Transaction Start Values3.3.6 Assign Notification Types to Order Types
-
7/29/2019 Organisation Structure - CS and PM
2/9
3.3.7 Maintain Catalog
3.3.8 Define Catalog Profile
3.3.9 Define Partner Determination Procedure and Partner Function
3.3.10 Define Priorities
3.3.11 Define Shop floor Papers, Forms and Output Programs
3.3.12 Define Operational Effects
3.3.13 Configure Order Types
3.3.14 Configure Number Ranges
3.3.15 Assign Order Types to Maintenance Plants
3.3.16 Assign Inspection Types to Maintenance/Service Order Types
3.3.17 Define Default Value for Planning Indicator for Each Order Type
3.3.18 Create Default Value Profiles for External Procurement
3.3.19 Create Default Value Profiles for General Order Data
3.3.20 Default Values for Task List Data and Profile Assignments
3.3.21 Settlement Rule: Define Time and Distribution Rule
3.3.22 Define Proposed Reference Time for Technical Completion
3.3.23 Define Default Order Types for Maintenance Items
3.3.24 Define Notification and order Integration3.3.25 Maintain Control Keys
3.3.26 Maintain Default Values for Control Keys for Order Types
3.3.27 Define Maintenance Activity Types
3.3.28 Assign Valid Maintenance Activity Types to Maintenance Order Types
3.3.29 Default Values for Maintenance Activity of each order type
3.3.30 Assign Costing Parameters and Results Analysis Keys
3.3.31 Define Change Docs, Collective Purc. Req. Indicator, Operation No. Interval
3.3.32 Define Documentation for Goods Movements for the Order
3.3.33 Define Scope of Check
3.3.34 Define Checking Control
3.3.35 Define Default Values for Component Item Categories
3.3.36 Activate Default Value for Current Date as Basic Date
3.3.37 User Status for Orders
3.3.38 Create Authorization Keys for User Status Authorizations
3.3.39 Define Default Values for Units for Operation
3.3.40 Partner Determination Procedures -> Equipment Category
3.3.41 Partner Determination -> Notification Type
3.3.42 Partner Determination ->Assign to Order Type
3.3.43 Set Scheduling Parameter
3.3.44 Assign Default Values for Settlement Areas to Order Types
3.3.45 Object Information -> Define Object Information
3.3.46 Object Information -> Assign Object Info Keys to Order Type
3.3.47 Completion Confirmation ->Confirmation Parameter3.3.48 Completion Confirmation -> Define Causes for Variances
3.3.49 Completion Confirmation -> Define Execution Time for Confirmation Processes
3.4 Information Systems for Plant Maintenance
3.4.1 Assign Value Categories to Maintenance Cost Key Figures
3.4.2 Configure Measurement Document Update- See more at:http://www.sapebooks.com/b/is-utility-plant-maintenance-and-customer-service-configuration-
document.html#sthash.M8aWbEja.dpuf
http://www.sapebooks.com/b/is-utility-plant-maintenance-and-customer-service-configuration-document.html#sthash.M8aWbEja.dpufhttp://www.sapebooks.com/b/is-utility-plant-maintenance-and-customer-service-configuration-document.html#sthash.M8aWbEja.dpufhttp://www.sapebooks.com/b/is-utility-plant-maintenance-and-customer-service-configuration-document.html#sthash.M8aWbEja.dpufhttp://www.sapebooks.com/b/is-utility-plant-maintenance-and-customer-service-configuration-document.html#sthash.M8aWbEja.dpufhttp://www.sapebooks.com/b/is-utility-plant-maintenance-and-customer-service-configuration-document.html#sthash.M8aWbEja.dpufhttp://www.sapebooks.com/b/is-utility-plant-maintenance-and-customer-service-configuration-document.html#sthash.M8aWbEja.dpuf -
7/29/2019 Organisation Structure - CS and PM
3/9
-
7/29/2019 Organisation Structure - CS and PM
4/9
IW59 Display Service Notifications: Selection of Notification
IW64 Change Notification List of Activities
IW65 Display Notification List of Activities
IW66 Change Notification List of Tasks
IW67 Display Notification List of Tasks
IW68 Change Notification List of Items
IW69 Display Notification List of Items
IA07 Display General Task List
IA03 Display Equipment Task List
IA13 Display Functional Location Task List
IR03 Display Work Centre
KO88 Settle Order (Single)
ME21 Create Purchase Order (pre R4.6)
ME21N Create Purchase Order (R4.6 onwards)
IP41 Create Single Cycle Plan (R4 onwards)
IE02 Change Equipment
IE01 Create Equipment
IE03 Display Equipment
IE05 Equipment List Editing - Change
IE08 Equipment List Editing - Display
QS42 Display Catalog
ML81 Create Service Entry Sheet
MM03 Display Material
CS03 Display Material BOM
IH01 Display Functional Location Structure
MB11 Goods Movement
MB31 Goods Receipt
IW8W Goods Receipt for Refurbishment (R4 onwards)
IP02 Change Maintenance Plan
-
7/29/2019 Organisation Structure - CS and PM
5/9
IP03 Display Maintenance Plan
IP10 Schedule Maintenance Plan
IP30 Deadline Monitoring
IP11 Change Maintenance Strategy
IP12 Display Maintenance Strategy
IP19 Maintenance Scheduling Overview Graphic
IP24 Maintenance Scheduling Overview List
IQ03 Display Serial Numbers
IP42 Create Strategy Maintenance Plan (from R4 onwards)
IL02 Change Functional Location
IL01 Create Functional Location
IL03 Display Functional Location
IL05 Functional Location List Editing - Change
IL06 Functional Location List Editing - Display
IA11 Create Functional LocationTask Lists
IA12 Change Functional Location Task List
IL02 Change Functional Location
IA05 Create General Task List
IA06 Change General Task List
IA01 Create Equpment Task List
IA02 Change Equipment Task List
IE03 Display Equipment
IR01 Create Work Centre
IR02 Change Work Centre
CA85 Replace Work Centre
IP13 Strategy Package Sequence
IP14 Strategy Package Sequence
IP04 Create Maintenance Item
IP05 Change Maintenance Item
-
7/29/2019 Organisation Structure - CS and PM
6/9
IP06 Display Maintenance Item
IP17 Maintenance Item List Editing - Change
IP18 Maintenance Item List Editing - Display
IP02 Change Maintenance Plan
IP03 Display Maintenance Plan
IP15 Maintenance Plan List Editing - Change
IP16 Maintenance Plan List Editing - Display
IK11 Create Measurement Documents
IK12 Change Measurement Documents
IK13 Display Measurement Documents
IK22 Measurement Documents List Editing - Create
IK21 Measurement Documents List Editing - Create
IK22 Measurement Documents List Editing - Create
IK18 Measurement Documents List Editing - Change
IK17 Measurement Documents List Editing - Display
IK41 Measurement Documents List Editing - Display Archive
IQ01 Create Serial Numbers
IQ02 Change Serial numbers
IQ04 Serial Numbers List Editing - Create
IQ08 Serial Numbers List Editing - Change
IQ09 Serial Numbers List Editing - Display
IK01 Create Measurment Point
IK02 Change Measurement Point
Ik03 Display Measurement Point
IK08 Measurement Point List Editing - Change
Ik07 Measurement Point List Editing Display
-
7/29/2019 Organisation Structure - CS and PM
7/9
Hun,
Provides support for the complete Service processing lifecycle from Service Quotation creation to Billing. A
service order is created if the customer has to be billed for services like utility usage, no. of pages printed (using
counters etc). Service Order processing includes integrated validation of service contract price agreements and
warranty entitlements.
The cycle is :
Business Scenario Service quotation and service order management
A. Make inquiry Customer contacts and requests for quotation
B. Create and communicate quotation service rep. creates a quotation and sends it to the customer
C. Accept the quotation
D. Convert quotation into service order and release the order
E. Create and optimize assignments - The Resource Planner assigns any field service tasks to one or more of
his Field Service Representatives
F. Execute assignment, perform confirmation - The Field Service Representative performs the service
assignment at the customer site and performs confirmation for the work done, materials used and so on
G. Approve confirmation, assign costs - The Service Manager checks and approves the confirmation data and
decides which costs should be billed to the customer
H. Bill customer, perform analyses - The Service Manager triggers billing of the customer and performs
analyses of the complete service order processing cycle
Where as a repair order would be created when a customer finds a defect in say a product and the requests for a
repair of replacement.
The cycle is:
The business scenario
1. Enter repair request
The customer calls the service organization to request a repair. The agent enters the repair request. The system
checks whether a warranty exists.
2. Send in defective product
The customer sends in the product using the given return material authorization number.
3. Plan repair steps
A service representative performs the technical analysis and enters the inspection result (causes, tasks, etc.). He
decides what action should be taken based on the inspection result.
4. Create service quotation
The system calculates the price for the planned repair and required spare parts, according to the price
agreements in the service contract, and the warranty costs. The agent generates a service quotation.
5. Perform confirmation
The customer accepts the quotation. The service representative repairs the product and confirms his working
times and materials used. He also documents the inspection results.
6. Return repaired product
The service representative returns the repaired product to the customer.
-
7/29/2019 Organisation Structure - CS and PM
8/9
7. Create invoice
The service representative triggers customer billing, based on the confirmed time and spare parts used, and in
accordance with existing warranties and specific price agreements.
8. Analyze defect reasons
Using predefined queries and reports, the service manager analyzes the most important defect reasons.
Refer to CR700 - Service for details info.
Regards,
Julius
Work/Service Order
Definition
R/3 document containing processing data that can be transferred from the R/3 Maintenance andService Management (MSM) system to Computer-aided Scheduling & Dispatch (CSD/MF) software.
Use
A work order may contain multiple operations, which in turn can contain multiple sub-operations. Awork/service order can make reference to a business partner (customer), and one or more technicalobjects (for example, work locations, equipment). Work orders and work operations may havedependencies with one another, as well as external constraints such as permits. Tools, materialand/or qualifications can be defined in the work/service order as requirements for the work.
Normally, work information provided by SAP is translated as 1 "job" per work order operation.However, for administrative expediency, the CSD system may dispatch a single "summary" of jobsinstead of multiple operations in the work order. Under these circumstances, work completiontransactions would normally only be generated for those work requests that were dispatched.
The CSD system may support functionality that permits feedback for jobs to be done to a "standing"
work order that is not dispatched but used purely as a cost collector for a specific type of work.
Structure
The following types of work/service order data can be transferred from the R/3 System using theIORDER01IDoc:
Order header data Permit data
Technical object data (functional locations and equipment including measuring points)
Partner data (ship-to party, sold-to party, service-at customer)
Operation data (sub-operation, splits, material, PRTs, requirements, relationships)
Notification reference data
https://help.sap.com/saphelp_nw04/helpdata/en/f2/660b378350c976e10000009b38f839/content.htmhttps://help.sap.com/saphelp_nw04/helpdata/en/f2/660b378350c976e10000009b38f839/content.htmhttps://help.sap.com/saphelp_nw04/helpdata/en/f2/660b378350c976e10000009b38f839/content.htmhttps://help.sap.com/saphelp_nw04/helpdata/en/c2/090b374e4e7c64e10000009b38f839/frameset.htmhttps://help.sap.com/saphelp_nw04/helpdata/en/f2/660b378350c976e10000009b38f839/content.htm -
7/29/2019 Organisation Structure - CS and PM
9/9
The IORD transaction performs the extraction of the work/service order data to build IDocs.
Integration
The selection criteria for the IDoc requires the entry of auser statuscode to be used to identify that
the order has been transferred to and is now 'owned' by the CSD system. Data can only be extractedfor the order if the user status code exists in the user status profile defined for the order.
https://help.sap.com/saphelp_nw04/helpdata/en/1e/0a0b374e4e7c64e10000009b38f839/content.htmhttps://help.sap.com/saphelp_nw04/helpdata/en/1e/0a0b374e4e7c64e10000009b38f839/content.htmhttps://help.sap.com/saphelp_nw04/helpdata/en/1e/0a0b374e4e7c64e10000009b38f839/content.htmhttps://help.sap.com/saphelp_nw04/helpdata/en/1e/0a0b374e4e7c64e10000009b38f839/content.htm