SAP PM Overview

ORGANIZATION STRUCTURE (SPRO)

Step - 1

Company - Company Code - (FICO)

Plant - Plant Code - (FICO)

Planning Plant - (FICO)

a. Centralized Plant - ( Have dedicated Planning Plant ) ex: for 3 Plant have 1 Single Planning Plant

b. De-Centralized Plant - ( Plant it self Planning ) ex: Each plant planning for it Self

c. Partially Centralized Plant - ( It has some actions from Centralized & Some from It Self)

Work Center

MASTERDATA - 

WORK CENTER/FLOC/EQUPMENT/BOM/CLASS/CHAR/CATALOGUE/CODE GROUP/CODES/MEASURING POINTS/MEASURING DOC/TASK LIST/MAINTENANCE STRATAGIES/MAINTENANCE PLANS/PERMITS

TRASACTIONAL DATA -

BUSINESS PROCESS - 

CORRECTIVE

BREAKDOWN

PREVENTIVE

QUALITY

REFERBUSHMENT

INVESTMENT

PREDECTIVE

SHUTDOWN

PLANS/WORK ORDERS/NOTIFICATIONS.

REPORTS - ASAP/LSMW/FS PREPARATIONS

Comments

Post a Comment

Popular posts from this blog

Interview Questions - CAPGEMINI

How many years of experience do you have & relevant.  Whichever processes you have worked? Previous experiences? Support project which ever process you have worked? can you tell me about SAP PM org structure in hierarchal way? Can you tell me about SAP PM Master Data? What are all the transactional data's you prepared? - Notification/Work order While creating maintenance plan - Scheduling indicators are there what are the types - Fact. Calendar / Time / Key Date in the same page as 8th point there is a tick mark what was that & what it refers to (what was the use of it)??   - Completion requirements In equipment master we mention catalogue profile from where you create?? - SPRO In equipment master we assign the catalogue profile. when we create the Notification, we will select the Code groups /  Codes. is there any specific report (Standard report) there from which we can get the detail whatever notification by codes/code groups. Have you ever worked on RICEFW -  while crea
Read more

IDoc - #IDOCSetup

Image
 Steps involved in IDoc set-up  Setting up Inbound/outbound IDocs for system interfaces between systems can reduce the processing time of documents considerably. IDoc interfaces allows to transfer data in faster and safer way. During order to cash cycle we come across multiple IDocs for data transfer. Few logical messages that can be used are mentioned below. #ORDERS: We receive this as inbound IDoc which will have all the header and line item details required for order creation. Processing this IDoc is capable of order creation in SAP system. This way we get the order created without any manual intervention which reduces risk of human error at order creation level. Same Logical message type IDoc when generated for purchase order, it can be used to send the purchase order to vendor. Using EDI IDoc for purchase orders over traditionally used email/ telephone medium can reduce the overall purchasing time for the business and helps to maintain accuracy of data. #ORDRSP: This can be used a
Read more