ECC6, S / 4 Hana 1909.......

BI / BW, SCM, SRM, SNC, PI

SAP ECC 6---Oracle database
SAP S / 4 HANA(SAP Own database)....PM module remains same in S / 4 HANA and ECC6 version....
SAP PM module also called as EAM--Enterprise asset management
***********************************************************************************************************************************************************************
SAP PM course:
1. Introduction--1
2. Master data--12
3. Notification & Orders-10
4. Reports-2
5. Configuration--3-4 and Technical part-2
6. Interview preparation and real time examples, Roles & responsibalities-2
30 to Hrs

ERP Software’s:
1. SAP------>You here
2. Oracle--->
3. JD Edwards-->
4. People soft
5. Baan
6. Maximo
7. Tally

System applications Products

SAP is ERP software owned by "SAP AG" Company--JSW / ToyoTA / Hundai / Philips / Apple / Samsung / PEPSI / ITC / BOSCH / TATA Steel etc--
50 cr licence(Clint)(number of users)-->ACcenture-450 Cr / Infosys-400 / TCS--500, Wipro-570 service providers / Vendors--

SAP Functional Modules:

1. PM-Plant maintenance(also called as EAM)
2. PP--Production Planning
3. QM-Quality Management
4. SD--Marketing
5. FICO-Finance & Controlling
6. MM-Material management ....................etc

Finance(FICO)--MBA / CA / BCom
Sales and distribution- MBA-Marketing
HR-ENG / MBA-HR
MM--Material Management--general
PM Module---Mechanical / Electrical / industry
1--10
1---15
1--5

PM / PP / QM--Manufacturing
MM / WM / eWM / Logistics
SD / etc

We are
1. Functional Consultant----PM, MM, FICO, PP, QM, WM, SD etc---
2. Technical Consultant(ABAPer / BASIS / Security)---ABAP Programmers(Coding people)--CS / IS / MCA people---1000 people
3. Techno Functional

1. Implementation---Oracle--scratch / green field---New SAP Software’s---PM Module--100%---Accenture---Vijanagar plant---

2. Rollouts Project---Dolvi, Us Plant, Salem, Tarapur -- 25cr -- Capgemini
3. Support Projects--
4. Upgrade projects

ASAP Methodology:
Delivery manager--

1. Project Manager---Project Manager--PM

2. Program Manager----ABAP---Coding people--CS / IS people
3. Release manager---

1. Project Planning-----
2. Blue print---
3. Configuration, test and -->Clint

SAP PM(Plant maintenance or EAM) Module:

One of SAP PM module used for the maintenance of the assets(machines)

Types Maintenance process:

1. Corrective Miantenance → small repairs → No major Production loss → Machine running--10%
2. Breakdown Maintenance → Un planned-production loss → Major problem / damage → Machine is on off condition → 5%
3. Preventive Maintenance (planned scheduled maintenance) → Time based-1M, 6m, 1Yr and performance 1000Km, 5000Km et → 60% →
planned maintenance
4. Refurbishment (Re-conditioning)
5. Calibration maintenance (Q-measuring equipment) → Weigh Bridge, CT Scan Machine, MRI Scan Machine
6. Capital / investment process

***********************************************************************************************************************************************************************
Centralised Maintenance → Bangalore Plant maintenance team (planning), Chennai Plant, Hyd Plant----1%

1
 1. One planning plant can be assigned to diff Maintenance Plant Vijayanagar Plant(Planning Plant), Tarapur, Salem
2. 2.de-centralised maintenance → Bangalore Plant Maintenance Team, Chennai Plant (Own Maintenance Team), Hyderabad Plant(Own
Maintenance Team)
3. Vijayanagar Plant, Tarapur, Salem → 99%

Planning plant same as maintenance plant

***********************************************************************************************************************************************************************
Types data:
1. Organisational data--Plant, Planner group, plant section, sort field, object type etc--------Configuration (T code-SPRO)
2. Master data---Work centre, Equipment, FL, class, Char, Catelog, task list etc-One time creation---(Mass upload LSMW)-->
3. Transactional data--Notifications, Miantenance orders, MP

SAP PM Organisation structure:

1. Company code-->
2. Planning plant---->
3. Maintenance plant--->
4. Planner group---->
5. Work centre
***********************************************************************************************************************************************************************
WORK CENTRE:
(IR01 / IR02 / IR03 / CR05) -Group of maintenance people who are responsible for carrying out maintenance activities...
It can be Electrical, Mechanical, Instrumentation etc.,

capacity calculation--SAP008
Scheduling---Sap004
BE-Maintenance Engineers-1
Diploma-Mountainous Supervisors-1
ITI- Mechanical Technicians-100
HRMS Integration—
*****************************************************************************************************************************************************************
1. FUNCTIONAL LOCATION:
(IL01 / IL02 / IL03 / IH06 / IH01) → Logical place / area / dept / production line where equipment installed and dismantled
It’s an Technical object, Its hierarchical representation of organisation

a. Company → TATA Steel ltd company → TATASL23 → TOYOTA → Toyota Company

b. Plant → Jamshedpur plant → TATASL23-JPP → TOYOTA-BALR→Bangalore plant
c. Dept → SMS 1 dept → TATASL23-JPP-SMS1 → TOYOTA-BALR-ASMBL1 → Assembly area
d. Sub Dept → Utility area → TATASL23-JPP-SMS1-UT → TOYOTA-BALR-ASMBL1-ENG → Engine dept
e. sub area → Pump section → TATASL23-JPP-SMS1-UT-PS → TOYOTA-BALR-ASMBL1-ENG-PI → Piston area

Equipment → → Compressor, Lathe, Pump, Motor, DG etc

Advisable 5th Level → 6th level max (not beyond) → 6th
Structure indicator: (one time activity) → Config
Mask → 40 Character and hierarchy

X---Alphabetical / Numerical
A---Alphabetical
N---Numerical

Reference Functional location(il11 / il12 / il13)---Il04 to Copy

U1, U2, U3, U4....100 utility dept
Master / Template FL
Alternative label: New naming for functional location change mode----You need to activate alternate label indicator in customisation
K1 Plant
*****************************************************************************************************************************************************************
2. EQUIPMENT (MACHINE):
IE01 / IE02 / IE03...report - IE06 / IH08
Technical object where we execute maintenance work and it will be installed / dismantled to FL.
lathe, Turbine, compressor, pump, motor, bike, car, bus, weigh bridge etc

Category:
1) M → Machine → 90% → lathe, compressor, pump, motor, DG, Turbine
2) P → PRT → Production resource tool - 5% → FORK Lift, Cranes, Hydra → belongs Production dept → Will never install to FL-----
PRT data should be entered--
3) F → Fleet / vehicle → Vehicle(bus, ship, truck, car, bike) → Truck 1000KM, 3M → engine, driver, type vehicle, KM reading, Chassis
no chassis, vehicle number.
4) Q → Measuring / testing Equipment / Lab equipment → 5% → Calibration order → Ex-Weigh bridge, MRI, CT Scanning machine

Under Location tab → Work Centre(PP) → M category → To prevent production activities if the equipment is under the maintenance →
capacity planning(CM25 T code)

Superior Equipment → Lathe → Sub equipment → Motor / cooling unit

Attach document / image

Serialisation (IQ01 / IQ02 / IQ03 / IQ09) : Integration MM Module

One material → motor → 100 qty → winding(external repair → which motor sent for repair-to track?) → Serial number → will link to equipment
100 equipment’s
Serial no can be created manually or automatically → Serial no mainly used in refurbishment process
Material → Serial number profile should be assigned (plant data / storage 2) view
*****************************************************************************************************************************************************************

2
4. BOM: Bill of Material (Spare Parts / individual parts of the equipment)
→ One time creation → we can use it forever

1) Equipment BOM (IB01 / IB02 / IB03) → Lathe: Shaft, carriage, spindle, coolant, gear box, motor etc.,
a. Created wrf. to the EQ no Bike; tyre, lights. engine, chain, seat cover, indicators, fuel tank, spark plug etc
b. WT-Motor, gearbox, shaft, coupling, bearing etc
c. Turbine; Bearings, lob oil, RTD, Impeller, Controlling system, DC systems, shaft etc

2) Assembly(Material BOM)(CS01 / CS02 / CS03) → Gear Box: Shaft, gears, housing etc. → 25% → CS01 / 02 / 03,
a. Created with reference to the Material no Motor; winding, casing, wiring, shaft, coupling, fan guard, o ring, brake
b. Engine: Crank shaft, sealings, o ring, shaft, bearing

3) FL BOM(IB11 / IB12 / IB13) → Ac, exhaust Fans, doors, lights, sealing fan, ventilator, water filter etc → 5% → IB11 / 12 / 13
a. Effective way of planning work order / task list, to reduce the time. But creation is one time activity once equipment is
purchased from OEM companies.

*****************************************************************************************************************************************************************
5. Class and characteristic:

Class: Cl02
Group characteristic
colour--
Power--
Fuel--Petrol, deiesl

Characteristic: CT04
Specifications / attributes / technical details of the Technical object (equipment or FL)

Voltage → 110 v, 220 Volts, 440 V

power → 20 hp, 50Hp, 100 HP
colour → white, red, blue, grey
Fuel type → petrol, diesel
Type → Single, double stage, multi stage
Frequency → 50 Hz, 60 Hz
RpM → 1000, 2000, 3000
Pressure → 110MP
Current →
Temperature →
Characteristic will be assigned to class, then class will be assigned to equipment master
*****************************************************************************************************************************************************************
Standard Permits (IPMD): Hot work permit, safety permits, confined entry permits, work at hight
IPMD-once permit is created then have to link with Equipment
To issue / approve the permit-IPM2(safety manager or person trained on safety (maintenance manager / shift in charge))
There is another Advance permit called as WCM-Work clearance management (only used in heavy industries like Aerospace, nuclear
power plant etc)

*****************************************************************************************************************************************************************
6. Catelog (configurable master data-SPRO) - node transaction QS41
Set of codes and code group which will be used in notification to get maintenance history

Catelog type: BC52A

• B → Object part → which part? → Shaft, bearing, gear box, motor, engine, MCCB, winding etc
• C → Damage → what happened? → Bent, Broken, Crack, Melt, damage, leak
• 5 → Cause → why it is happened? → Poor material quality, operator fault, current fluctuation, overload, poor maintenance etc
• 2 → Task → what you have to do? → repair, remove, clean, replace, stop etc
• A → Activity → what you have done? → Repaired, cleaned, removed, replaced, stopped, scrapped etc

Will create Catelog in qs41..will assign in to the Catelog profile.....

After Catelog profile will be assign to equipment master or notification config

Why Catelog are used?

a) User friendly to select codes / code group in the notification instead of entering long text
b) Equipment Maintenance history(damage reports for root cause analysis, why-why analysis etc)----
c) To standardise the maintenance process

Buy 1 motor from → Kirloskar BHEL local company → 1 year

0 1 8

Code group → codes

*****************************************************************************************************************************************************************
7. Measuring Point (IK01 / 02 / 03 / REPORT - IK07):
Critical equipment’s point / place where you take the reading on daily basis (Only once will be created) →
To monitor healthy condition of the equipment in order to avoid the breakdown

A shift---8 hr, 50 degree

B shift---8 Hr, 52 degree
C shift---8 Hr, 90 degree

Running hrs(1000Hrs), diesel consumption (1000 litres), Temperature(45-55 degree), pressure, out / in flow rate, RPM, Voltage, KM, Speed,
etc

3
 1) Non counter based MP (range-condition based) → Temperature (degree), pressure, rpm(1000) -constant reading(won't increases on
daily basis)---->Notification will be triggered for Corrective maintenance
User exit-IMRC0001
Corrective maintenance / condition → Corrective notification / mail
Valuation Condition based measuring points:
You can link code group to measuring points when you take the reading you can enter codes also.

2) Counter based MP...Running (usage hours)..Diesel consumption, KM → Daily reading increases...8hrs + 8Hrs + 4Hrs=20hrs →
21(41hrs) → 20(61)Hrs → 8640hrs / annually → 720Hrs in month → 2nd + 3rd

Preventive maintenance (PM Order)

Compressor → 1. Machine hours usage, 2. Inlet Temperature, 3. Out let temperature, 4 inlet air pressure, 5 outlet air pressure, 6 RPM, 7
Current, 8 Voltage etc

Reading entry / Measuring document(IK11 / 12 / 13 / 17) → Collective reading entry (IK22)

IMRC0001 → User exit

*****************************************************************************************************************************************************************
Revision: OIOB is T code → Shut down maintenance → Painting, Foundation work, electrical wiring etc

Will define when the shutdown starts and ends → Revision will be assigned to shutdown order in header data, basic start / finish date and time
will be copied from REVESI

OIOB → based on revision will get the shutdown order list(iw39), you can analyse maintenance cost for that shutdown period
*****************************************************************************************************************************************************************
Preventive Maintenance PM03 (planned order, scheduled maintenance) → IP11
If we do the proper preventive maintenance then less breakdown will be there....

Maintenance Strategy(IP11 / IP12):

Strategy defines cycle, package will be assigned to the task list operations and hierarchies
→ Task list or Maintenance plan

a) Time based strategy → 1M :lubrication / greasing, 3M: oil change, 6m:clean / Changing the filter, 1Y-bearing change

b) Performance based strategy → 1000Km, lubrication / greasing, 3000KM:oil change, 6000KM:clean / Changing the filter, 10000KM-
tyres change 1000Hr, lubrication / greasing, 3000Hr:oil change, 6000hr:clean / Changing the filter, 9000hr-Bearing change

c) Hierarchy

d) Strategy will be created in each system...Not master data or configuration data...cut over activity

*****************************************************************************************************************************************************************

8. Task list (Set or group operations(maintenance activities)):

To standardise the maintenance process, not to miss any, Reduce time During creation / Planning of the work order

One time creation

• Forever you can use
• Assigned in the maintenance plan (for preventive maintenance)
• Directly you can assign to the maintenance order

1) Equipment task list (50%) → IA01 / 02 / 03 / 09 → Lathe-Gear box, these are created with reference of equipment
a. Compressor → 1. Check the sensors, 2. remove shaft, 3. remove chocked filter, 4, fit new filter, 5. take a train run and
handover to operation CNC Lathe machine- remove spindle, remove carriage, check the spindle alignment

2) General TL (Ia05 / 06 / 07 / 09) (40%) → Bike, Car, Lathe machine, compressor, pump-------cleaning, lubrication / greasing, painting,
tightening of bolts

3) FL Task list (ia11 / 12 / 13 / 09) (10%) → change the ac, remove door, change fan. Change the water filter

*****************************************************************************************************************************************************************
Maintenance Plan:
Transactional data---> we create the plan, we schedule it, will generate maintenance call (maintenance order / Notification)
we never Preventive maintenance order (PM03) create manually(iw31) → automatic generation / trigger
Orders / notification / inspections--Maintenance plan category (mainly always will create maintenance orders)

Types of maintenance plans:

1) Single cycle plan (IP01 / IP41 / 02 / 03 / IP16 / IP19 / IP24) → 1M, 1000Hr

Simple plan
Time based---->Period-->monthly
counter based--->Based Measuring doc reading--->1000 Hr
Scheduling indicator:
Time---Exact 30 days
Time key days---exact key date--example every month 1st
Time-Factory calendar
cycle modification factor--30 days---by default always 1
1,5---45 days
0,5---15 days

Completion requirement check box--->If you complete previous order(call) then only you system will generate next order

4
 Call Horizon-Used in single cycle / strategy plan to call(generate) the order in advance 50%, 75%, 90%, 100%. So that mainteance team
will get the sufficient time preparation for maintenance work.
Based on call horizon % call date will be calculated once the plan scheduled. If you give 100%, call date is same as plan date, ideally we
use 90%

****************************************

2) Strategy plan (IP01 / IP42 / 02 / 03 / 1P16 / IP24) → Strategy(ip11)-

If multiple operations in task list, we can call the specific operations for particular cycle based on package assignment TL
................This is not possible in the single cycle plan (all task list operation will get copied to order)

Complex type maintenance

--->Time based----------->1M:Greasing 3m; oil change 6m:Changing the filter, 1Y-change bearing
--->counter based-------->1000Hr-lubrication / greasing, 3000Hr:oil change, 6000hr:clean / Change filter, 9000hr-Bearing change

Scheduling indicator:
Time---Exact 30 days
Time key days---exact key date--example every month 1st
Time-Factory calendar
cycle modification factor --30 days---by default always 1
1,5---45 days
0,5---15 days

Completion requirement check box--->If you complete previous order(call) then only you system will generate next order

Call Horizon-Used in single cycle / strategy plan to call(generate) the order in advance 50%, 75%, 90%, 100%. So that maintenance team
will get the sufficient time preparation for maintenance work.
Based on call horizon % call date will be calculated once the plan scheduled. If you give 100%, call date is same as plan date, ideally we
use 90%

3) Multiple counter plan → IP01 / IP43 / 02 / 03 / 1P16 / IP24 → Cycle set → to create cycle set t code IP11z
This plan rarely used.....
Name itself says we can combine multiple counters(measuring point).........
There are some rare equipment’s created with multiple counters...
1 eq will have 2 counters → ex like diesel generator or diesel pumps for diesel consumption in litre → 1 counter for machine running hours
in HUR → 1 counter we can also create multiple counter plan to combine time + Counter

Difference between strategy and multiple counter plan:

1) Strategy plan created with ref of strategy, MCP created with reference of cycle set
2) In strategy plan we cant combine counter + TIME, But MCP we can combine
3) In strategy plan there is call horizon, But in MCP lead float days will use
4) In strategy plan no or / AND link, but in MCP OR / AND link is there
5) Shift factors and time indicator not exist in MCP

*****************************************************************************************************************************************************************
Strategy and single cycle plan:

Shift factor for Late completion:

0% (blank)------
1st Jan is plan date----4th Jan(completion)---->4 days late

Even completed 4 days late there is no impact on the next pLANNED DATE(cycle)---> WILL BE ON 1st feb

100%:
1st Jan plan date------>COMPLETED JAN 4th---4 days late
Next cycle plan date is 4th Feb--------->There is impact on next cycle---->entire cycle will get shifted based on the late days

Shift factor for Early completion:

0% or Blank
1st Jan--Planned date

Dec 26th.....4 days early / advance......

next plan date is on Feb 1st...

100%:
1st Jan--Planned date

Dec 26th.....4 days early / advance....

next plan date is on Jan 26

***********

Cycle modification factor (by default will use 1)

30 days---1
30 + 15---1,5
15-----0.5

***************************
assigning multiple equipment’s in maintenance plan;

Object List:
1. Only one Order will be generated for one header / main maintenance item → Object list will be included in orders object tab
2. No costing possible under object list level (only possible for header level item)..

5
 3. You can’t assign different task list for equipment’s

Multiple maintenance item:

1. Multiple orders will be generated each item with assign different task list assignment possible
2. Costing possible under each maintenance item / equipment level

If you don’t want to generate the order then you can inactivate / delete maintenance plan → Ex-equipment is no more useful

*********************************************************************************************************************************
Maintenance plan Scheduling:

Need to schedule the maintenance plans in order to generate the maintenance order(call) every day mid night automatically.

IP10--Manual / single plan scheduling (only one plan can be scheduled and we use if manual intervention required)---Rare 1%
can be used for restart maintenance plan, skip call / manual calls / to change the plan date

Ip30-Automatic / mass scheduling + Deadline monitoring + Batch job input / background scheduling-----Every Sunday / every mid night
/ 15 days / monthly--99%
(IP30 will be run with batch job, batch job will select the maintenance plans based variant, will the program, if maintenance plan call date
matches to the batch job running date system will generate order automatically)

Sensitive transaction, usually users are not authorised to use this..IP30 always run by batch job ID

Batch Job SM36 / Sm37(Basis Team)-One time activity

Variant-IP30 DEADLINE_MON35----------------DEADLINE_MON56
Program name RISTRA20 for IP30
Frequency every day mid night / Every Sunday / 15 days / monthly-

Sort field
Stop creation of orders:

1. Inactivate the maintenance plan(deactivate it), so that all the next sxheduled calls are locked and wont create further orders
2. If based on sort field the remove the sort field in the maintenance plan to exclude from shceduling
3. Modify the variant
4. Stop the batch job

************************************************************************************************************************************************************************
Notification (IW21 / 22 / 23, report IW28 / IW29):--->
First step for the maintenance order → Transaction data → To notify the maintenance team for any issue / malfunction in Equipment / FL

1) M1→ Corrective / general / maintenance request→ low priority→ No major production loss / machine running:
oil leakage, vibration / abnormal noise fix → Anyone(end users across plant) can create→ 90%→ Pm01 / corrective order

2) M2→ Breakdown / down time / Malfunction report→ High priority→ Production loss / machine not running: gearbox failure, shaft cut etc→
5%→ Pm02 / Breakdown order-B / D indicator(duration) → MTTR / MTBR→ Operator / Production supervisor

3) M3→ Activity report--1%

Notification purpose:
a) Just for notify the person / maintenance
b) Maintenance history (Catelog) damage reports, why-why analysis, Breakdown history(MTTR + MTBR)
c) No cost
d) Maintenance orders can created (Visa / Versa)

************************************************************************************************************************************************************************
Maintenance order / Business process / work Order--IW31 / 32 / 33 / Iw39 / IW38 / IW40 report → Transaction data

Maintenance Order types → Standard

1) PM01-Corrective / general Miantenance order → Immediate order:

Pm01-Corrective order → M1(anybody can raised) → PM01 → low priority → no major production loss →

2) PM02-Breakdown maintenance order (Down time) → unplanned order - M2(operator) / Pm02 → High priority → production loss → malfunction
start / end date / time (breakdown duration, B / D check → MTTR / MTBF reports

3) PM03-Preventive maintenance order (scheduled maintenance) → 75%

Planned maintenance → Automatically triggered → Strategy → task list → Maintenance plan → scheduling----preventive maintenance Orders
are created Preventive maintenance orders are never generated from notification or manually created(iw31) → less breakdown if proper PM

Time based → Daily, Weekly, monthly, 3M, 6M, 1Y

Performance based → 1000Hr, 3000Hr

4) PM04-Refurbishmnent Order

5) PM05-Order inclusive of notification → shutdown order or PM01 / Pm02 / Pm03 → 99% → Notification-all steps same

6) PM06-Calibration order →

7) PM07-Investment / Capital order → 95%

6
***********************************************************************************************************************************************************************

Steps:
1) Planning → labour planning + Materials planning + external service---planned cost generated → Release→Will take the Print (shop paper)--
MIGO goods issued for the order(261 goods movement posted) → actual material cost

2) Execution: Physically do the maintenance →

confirmation(iw41):

3) Order Confirmation--Actual hours / time posting...Manual(iw41) or Mass confirmation (IW42) → actual labour cost will be generated → CNF or
PCNF status
Manual (Iw41)
Mass confirmation (Iw42)
Mile stone confirmation--> PP module will use

4) Completion: Will take trail run --->will handover equipment to the operation team
a) overhead cost (Kgi2)----actual over head cost generated
b) Technical completion--TECO--Maintenance team responsibility—

5) Settlement (KO88):
a) Settlement (Finance task) → manually K088 or (month end)---order actual cost will be '0' nullified
b) Business completion → CLSD

************************************************************************************************************************************************************************
Planned order:

PM03 → Preventive maintenance order → Planned order--Automatically triggered → Strategy → task list → Maintenance plan → scheduling →
Orders are created
• Never will create from the notification or directly
• Time based → Daily, Weekly, monthly, 3M, 6M, 1Y
• Performance based-1000Hr, 3000Hr*
• Pre-planned maintenance order → Everything will be planned in the task list (labours / materials etc) → less planning

Costing: →
a) Categories → estimated, Planned, actual
b) Labor cost → Link between the work centre activity and WC cost centre (KP26 T code) → Finance team labour rate for the month /
yearly(100Rs / Hour)-
c) Overhead cost → Indirect cost( like management cost etc) → Automatically comes from costing sheet
d) Material cost → Material master → Accounting view → Valuation / Standard price etc-
e) Service cost →

************************************************************************************************************************************************************************
Settlement rule: Finance integration topic
• The process settling the cost between sender and receiver. we maintain the settlement rule in order
• Maintenance WC CC-->sender
• Equipment Cost centre(Production)---receiver

Types of settlement:
1) Full settlement → 100 operations are completed in January, If you completed all the maintenance work → 100% → Full
2) Periodic settlement → Completed 50 operations, January(50%) → Completed 50 operations, February(50%)

Create settlement rule in order:

Manual / automatic (rule → configuration)
We can cost to the following settlement receivers:

Cost Centre → 75% → Equipment CC

Cost centre → Pm01,Pm02,Pm03,Pm06

GL account

Material → Refurbishment order(PM04)

Asset → (Investment order-pm07) → Capitalise

WBS element → Project

Superior Order →

Settlement(KO88):

Settlement (Finance task) → manually K088 or month end Batch job → Finance team (month end) → order actual cost will be '0' nullified

************************************************************************************************************************************************************************
Confirmation: Mainly to enter actual hours
Actual labour cost will be generated
partial confirmation---PCNF status----only few operations or if you don’t click on final confirmation indicator

Full confirmation---CNF--All the operations are confirmed with final confirmation indicator.

Manual confirmation-->iw41
Mass confirmation:(Iw42)

7
Milestone confirmation: If you confirm one operation, all the subsequent operation will confirmed automatically (Control key should have millstone
confirmation indicator,

************************************************************************************************************************************************************************
Superior order(iw36)--- mass maintenance:--->Sub order(electrical / mechanical / instrumentation work)
Standing order--> One order will be open for long time---> each month will do some part of maintenance(25%)--->
Sub operation:
************************************************************************************************************************************************************************
Operation Control key topic---Applicable for all the order types

Standard operation control keys;

1) PM01 / Internal---Always Internal--No Purchase requisition(PR)---we do the confirmation
2) PM02 / External---1000 Rs----Sub contract process
3) PM03 / External Services---Service entry sheet

Usually we standard. However, we can configure new control key also in SPRO

Integration with MM module.

PR Generation(external process)--PM02 or PM0

PM02: External Man power supply or Sub contract process-->-

PR(sub contract item category-L)--->Convert to PO(Me21n)---->Goods receipt against to PO(Migo--101 + 543)Actual external cost will be
generated---->(MIRO) payment to the contractor--->TECO---->settlement--->Business completion

PM03 Control key(external service): You don’t send equipment outside of the plant premise, will external company to do the service for plant itself
PR(service PR item category-D)-->Convert PR to PO--->SES(service entry sheet(ML81N)--Actual external service cost will generated---(MIRO)
payment to the contractor----->TECO---->settlement--->Business completion

External Material procurement: Non stock process

Component--N(Non stock)
PR-->Conevrt to PO--->Goods reciept againest PO(MigO-101)---Actual material external cost will generated--MIRO-consume aginest maintenace
order

Goods movements types:

261--Goods issue to order / consuming components for the order ( + Quantity---261 movement)
262--Goods issue to order reversal(-ve Quanity---262 movement)
101--Goods receipt against PO / Iw8w(Internal refurbishment)

************************************************************************************************************************************************************************
PM04-Refurbishment order:
Re-conditioning of damaged component / material

Breakdown down order-

NEW-Fitted to Equipment
Repair-REQ / Damaged--Send back to store(262 MVT)

PM04-Refurbishment Order---(MM Integration)

will critical components(material)---Gearbox / motor / engine............costly items / repairable items.......not all the components
Maintenance Cost saving to organisation

Lathe Machine-
Main Equipment--Spindle, carriage, motor, guard, gear box, shaft

Motor: winding, Case, foundation setup, shaft, electrical wiring, brake etc
gear box: Gears, shaft, oil ring, connector, etc

1. Internal refurbishment--Internally repaired within the plant premise

2. External refurbishment---outside of the plant (external vendor will do repair work)

Perquisite:

Refurbishment order will be created for material

1) Will be created by IW81 / iw32 / iw33
2) Material should be Split valuated → This will be maintained by MM Team →
a. One material can have different valuation
b. C1-New-10000eur
c. C2-Repaired (Refurbished) → 4000eur
d. C3-Repair-REQ(Damaged) → (Zero value)
3) Cost settled to the Material (moving average price updated) → Will assign different material settlement profile in Refurbishment order
configuration

Repairing gearbox:

Material → zero + shaft (20) + bearing (30)=50

Labour → 100
Service cost → 10

Total Refurbished cost is---250

1) Total refurbishment cost-250 → (1PC)
2) Total refurbishment cost-300 → (2PC)
3) Total refurbishment cost-400 → (3PC)

8
 4) Total refurbishment cost-350 → (4PC)

Moving average price for material is= (250 + 300 + 400 + 350) / 4 =313.55
5th New refurbished order cost- 200

New moving average price(250 + 300 + 400 + 350 + 200) / 5= 300

Average price of all refurbished (repaired) materials

External refurbishment(Sub contract process-PM02):

Will repair the damaged material outside of the plant (external vendor will do repair work)

1. Refurbishment order iw81

2. enter Pm02 control key in operation, click on sub contract indicator, select material provision indicator as “rework material", upon order
save there will be Sub contract PR will be generated with item category L
4. Convert sub contract PR in to SUBCON PO
5. MIGO-Send damaged motor(material) to vendor(541 mVt) → Transfer stock from plant to vendor--here serial no will be useful
6. Vendor repair the material and will return back
7. MIGO-GR against PO(101 + 543) as repaired(refurbished) valuation, so actual external cost will generated and stock will update, MIRO / Invoice
will be posted for the vendor
8. Complete the order(TECO-->settlement run-->business completion))

************************************************************************************************************************************************************************
Calibration / inspection Order (PM06): IW31 / 32 / 33 / 38 / 39 → QM module integration

Planned maintenance...Can be created directly(iw31) or from the calibration plan.

1. Equipment category should be Q(Testing equipment / lab equipment / measuring equipment) → weigh bridge, MRI scanning machine, CT scan

2. MIC-Master Inspection characteristics(QM master data); QS21 / 22 / 23--(Weight_2)

a) Quantitative--10Kg, 100mtr, 1000rpm
b) Qualitative--Ex- colour(white, black, green) or Condition

3. Task list(QM data should be maintained--300 equipment-inspection point)--Assign MIC to task list operations

Qa01--Inspection lot manual creation

qa02--change
Qa03--display

Result recording for inspection lot(inspection type 14): T code-qa32

Qa32-results recording and usage decision for IL

Usage decision(UD):

************************************************************************************************************************************************************************
PM07 Investment(Capital order)----10%

Cost settlement will be on Asset or WBS element

Purchase and Installation and commissioning of the new lathe machine

kO22-BUDGET ASSIGNMENT

****************************

General topic questions: may ask in interview

--->There will be always one pR / reseravtion will be there for order.

---->settlement possible even if order is in released status. Usually will do after TECO

---->Its possible to reverse TECO, business completion. But not possible to reverse Released status.

----->Business completion is possible only if the order settled.

Once order TECO'ed

1. All resrvations will get deleted
2. If any open PR, will set to delettion flag automatically

Mass order release / TECO possible in IW38 transaction.

Mass equipment change also possible in IH08.

************************************************************************************************************************************************************************
Reports:
Business users(clint / managers / engineers)

CR05, IL05,IH08, IW29 / 28, IW38 / iw39, IK09, Ik17, IW47, IP24, Ip16, Ip19, iA09------------------->SAP standard reports

PMIS report:

T code MCI1 to MCI8

9
2. MTTR & MTBR---Are available for breakdown
MTTR: Mean Time to repair
Day 1---5 hrs
Day 2---4 hrs
Day 3---3 Hrs

MTTR for 3 days----(5 + 4 + 3) / 3= 4 Hrs

MTBR: Mean time between repairs

1st B / d =--9am
2nd B / D----1Pm
3rd B / D----3 PM

4 Hrs
2 hrs

MTBR= (4 + 2) / 2=3 Hrs

T code-MCJC / MCJB

Custom reports(Z reports)--->project / company specific--->not available globally---->ABAPER develop the reports with Z tcode--->To develop we
need to give the FS / Logic

************************************************************************************************************************************************************************
System status---automatically driven by system based on function, user dont have any control.

Order system status:

1) Created(CRTD)
2) Released(REL)
3) MIGO-(GMPS)
4) Technically completed-(TeCO)
5) Full confirmation-(CNF),Partial confirmation-(PCNF)
6) Business completion-(CLSD)
7) MANC,MACM
8) DLF
9) LKD
10) DLV(refurbishment order-IW8w)
11) ILAS(calibration) order
12) BUDG- Budgeted
13) AUC- Asset under construction

Notification system status:

1) OSNO-outstanding notification
2) NOPR-notification in progress
3) NOCO- Notification completed
4) Order assigned-ORAS
5) OSTS-out standing task
6) ATCO-All task completed
7) DLFL

Equipment system status:

Available-AVLB
Installed to FL-INST
Assigned to superior equipment-ASEQ
ESTO- Equipment in store / warehouse
DLFL

User status:
user / clint can manually change the status according requirement
Will create separate user status profile and it will be assigned to notification, order, equipment in the configuration

************************************************************************************************************************************************************************
Work order scheduling types:
1) Forward → will use this always
2) backward
3) Current date
4) Forward in time
5) Backward in time

************************************************************************************************************************************************************************
Configuration / Customisation / Back-end settings → SPRO
• Only consultants will be having knowledge → whenever we do the configuration Transport request (Customisation TR will get generated)
• If any dev / enhancement ABAPER will create the WORKBENCH TR
• Configuration will be done in development system...Golden clint.... D-100...SPRO will not be authorised in quality and production system

Config →
1) Master data configuration
2) Notification config → If we need new notification type apart from standard M1, M2, M3---Not plant dependent
3) Order config → Standard order types are PM01, PM02, PM03, Pm04, PM06, PM07----Apart for these we can configure new order type as
per clint requirement like shutdown order type

EH6K900670 → TR

10
Corrective order config: 99% steps are same for other order configurations also.

1) Indicator / Order Type → Pm01 Corrective(immediate), Pm02 B / D(un planned), Pm03 Preventive(Planned),

2) Refurbishment config: additional steps →

a) Order type is different and settlement profile is material
b) Refurbishment order indicator
c) Goods movement indicator for refurbishment

3) Calibration order config; additional step is →

a) Inspection type 14 should assigned and order type PM06
b) Order indicator for Calibration (planned)

4) Investment order config: additional step is →

a) order type is pm07, Settlement profile is different(asset / WBS) and assignment of budget profile
b) 2 indicator for investment order
c) Assign the investment profile

************************************************************************************************************************************************************************
2nd level Training:
PM module Integration with other Modules (cross modules):

1. Fico----Cost centre, Gl accounts, assets, KP26(activity type and cost centres), settlement profiles, settlement rule, order settlement part, material
master accounting view
order config--costing sheet, valuation variant, costing variant, estimated, actual cost, planned cost, service cost, budget, investment profile
etc

2. HR-----work centre HRMS integration---Position, person, profile we can assign / link the employees

3. PP-----Eq master under Location tab(PP Work centre)---to block the production if the equipment under maintenance.....PP people they will run
capacity planning that can see maintenance order, so that they don’t create production order

4. MM-----Serial number(refurbishment)-----1. serial number profile--Material master will assign it in plant data / stor 2 tab---Manually or
automatically...
material no, reservation no, refurbishment order (split valuation part), Material settlement profile, MIGo, PM02 / PM03, PR-->PO, SES,
material cost, non stock process

5. QM-----Calibration; Inspection lot, task list QM data--300 inspection point, MIC, result recording , UD, Inspection type 14

************************************************************************************************************************************************************************
LSMW- T code used to mass upload / change / create of the master data
S / 4 HANA--LTMC(migration cockpit)

Types:
1. Standard / direct input
2. Batch input / screen recording → Famous one, normally all will use this
3. BAPI / BADI

14 steps--
1) To mass create / change upload mass data.
2) Sequence for master data upload:
3) All configurations must exist (like Plant, planner group, sort field, plant section, person responsible etc)

50% master data in quality server

100% Upload in production server

1. Work Centre → 50
2. Function Location → 250
3. Equipment → 6000
4. BOM → 7000
5. Task list → Very difficult to load Standard LSMW----->BDC Programme / Custom program → 600
6. Measuring point → 100
7. Maintained plan → 1500

watch LSMW video, in interview they may ask at lest few important steps.....instal bb flash back pro application to watch
************************************************************************************************************************************************************************
Technical part:
T code: SE16N is to see the table / field data
Table names:
1) Equipment master table → EQUI
2) Work centre → CRHD
3) Order master data → AUFK
4) Order header data → IFIH
5) Maintenance plan → MPLA
6) Functional location → IFLOT
7) Confirmation → AFRU
8) Task list → PLKO
9) Notification → VIQMEL
10) Measuring point → IMPTT

Only functional consultants will have the knowledge

GAP Document → We need to write FS for GAP documents according to clint / project requirement for RICEF

11
ABAPER will write program and we will test

Example 1- By using user exit

If the measuring document reading goes out of the limit:

By using exit IMRC0001 ABAPER will write the programme to trigger the mail if the goes out of the limit
when i click on the save user exit will be active and it will trigger mail alert.
in the programme he will write the logic this:

Whenever ik11 measuring doc created, check the reading from IMRG table by passing MDOCM check READG value if the goeas out the limit
(go to IPMTT table, pass POINT measuring point check the value for MRMIN and MRMAX)

Example 2- By using save exit

For IWO10009
Check CAUFVD-EQUNR is blank AND CAUFVD-TPLNR is blank.
If both are blank, then display error message “Fill in Equipment or Functional location” and it should not allow saving of the order.

For QQMA0014
Check VIQMEL-EQUNR is blank AND VIQMEL-TPLNR is blank.
If both are blank, then display message “Fill in Equipment or Functional location" and it should not allow saving of the notification.

WARNING----Don’t yourself say worked on enhancement / RICEF.....Unless he asked...In case if he asked remember few easy enhancement above
and explain
Say in our project pure functionality and didn’t get chance to work on!!!!!!!!!!!!!!!!!!!!!!!!!

************************************************************************************************************************************************************************
Real time work:

PM Functional consultant--
1) Implementation---Oracle--scratch / green field---New SAP Softwares---PM Module--100%--ECC6
2) Rollouts Project---Same set of configurations like order config etc will be extended to the new plant
3) Support Projects--Handling ticket----S / 4 HANA 2021
4) Migration / Upgrade projects

1) ASAP Methodology---SAPR3 ECC6, S4HANA 2021 (PM / PP / SD / MM / FICO / PS etc)---SAP PM module is same in ECC6 and S /
4HANA
2) Agile methodology---
3) Activation methodology

ASAP Methodology (Implementation project)

1) Project planning----100 team members------>Key Users / Core team members(15 key users)-Kick off meeting(Project launch meeting)--
2) AS-is document---To-be documents--explain SAP--->business requirement-->GAP document(whatever not possible in standard SAP)---
>Blue print(BPD / PPD / BPML) sign off--signed Clint / Vendor
3) Design + Build phase(standard config + Development)-----Development Clint / system--->(golden clint D-100)-Only config
4) TR -->Q-200---Quality / Testing(Only transaction)--Functional unit test(FUT)--System Integration test(SIT)----Finance cost, material
posting, settlement, PR / PO--->(end user / key user KT + 75% master data LSMW to quality system)---->User acceptance test-UAT(clint
key user / core team)---approved-->>
5) TR-->Cut over activities, TR sequence (P-500)---Production system (will load 100% master data)---clint key users / end users--Golive----
(1 month Hyper care support---after care support)
6) Go Live---->Hyper care Support

Landscape;
Development golden system / clint--D 100->>Purely development--->Only SPRO(configuration) like master data / notification / order type config
Development Unit test system------D 110--->To move we use SCC1 t code copying Configuration from D100 to D110----Once TR copied to the D110
so you can unit test(basic test like order creating / notify creating or not)

TR will be moved from development to quality by BASIS consultant D100-->Q200

Quality / Testing system--->Q 200---->Can't use SPRO--->Only should do testing(creation master data, order, notification)-->FUT / SIT / UAT
Functional consultant will do the basic Functional unit test(FUT)--basic, master data / transactional data etc
In quality system we do the system integration test(SIT)----With different team FICO,MM, PP etc
In quality system clint will do the user acceptance test (UAT)---This will be done by clint core team / key users with actual roles---Will give test
scripts and will load 50% master data

TR will be moved from quality to production by BASIS consultant D100--Q200-->P500---Will be done BASIS----->But We need to TR give
sequence---Like first master data then notification then order configuration
In production system P-500 functional consultants will not be having authorisation for SPRO, any data creation......

Project cut over activities;

1) Creation maintenance strategy
2) Transport request movement to production(configuration)
3) Number range configuration--------------Directly in the production or quality or development---->or you can create TR and save number range
config and move across QA--PROD
4) Master data load / mass upload--100% real master data
5) Variant creation, Activation of batch job
6) Will end user training (KT)--->Before UAT

Regression test

*******************************************************************************************************
Special Fire fighter access will be given for one day or one week for cut over activities for functional consultants with approval
We shouldn’t miss use that only have to be used for like strategy creation, variant creation, master data load etc not for any other activities

12
*******************************************************************************************************
As a Functional consultant:
1) AS-IS document → how the business doing the maintenance
2) To-Be document → How you are going to Map in SAP
3) GAP document → Functional specification (ABAP Logic) → ABAPER development(Technical specification)
4) Blue print document → Mutual clint / vendor
5) User manuals →
6) Test scripts → Will give to the clint user

Read all documents how they are written

***********************************************************************************************************************
Two types of TR-Transport request;
Customisation TR (Customizing request) → Functional consultant will use this for any configuration (SPRO)
Work Bench TR / Request------->ABAPER will use that

Transport movement: taken care by BASIS consultant

Development (only config-SPRO, no transaction)-TR generated (import the TR by BASIS) ->Quality (testing only transaction, no dev)--
>Production(no spro) only key users allowed.

Basis consultant--His job is to move TR, create batch jobs, any performance issue, SAP installation etc. He will take care

************************************************************************************************************
Security consultant---His role prepare the role matrix--->based on role matrix he will give t code access to user--> We need to give functional
support for role matrix

In case of any authorisation issue will ask the user to send su53 screen shot and will sent to security team

1. Maintenance technician role---->Only iw21 / iw22 / iw23 / iw29 / 1w28

2. Miantenance engineer role------>iw21 / iw22 / iw23 / iw29 / 1w282, iw31, iw32, iw33, iw41 reports etc
3. Maintenance planner role------->Maintenance plans like IP01. ip02, ip03, ip10 etc
4. Maintenance master data maintenance---->all master data creation t code
5. Maintenance manager---> All above t codes + order approval like iw32, Budget allocation ko22, all the sensitive transactions

SU01 or SUIM we can see which role allocated---->within those roles there will be transactions assigned inside

Refer role matrix you will get idea

************************************************************************************************
PM Support tickets(support project experience):

Role is to resolve SAP production tickets as per Service level agreement (SLA days). There will be priority for each tickets
P1--Very High Tickets-------1 day (example number range exhausted)
P2--Medium priority Ticket---3 days
P3--low priority ticket------10 days

Supporting tools like SNOW or IT SOLMAN or REMEDY……You can say anyone

There will be different types of tickets like INCIDENT, SERVICE REQUST(SR), CHANGE request.

You can say monthly around 10 incidents and 10 request approx..

********************************************
Incidents: Something not working in the production system as designed is called as incident.

Example:
Issue / Incident- 1-->INC632643
When user the confirm maintenance operation, labour cost not calculating. User will raise incident in ticketing tool, mentioning like details like, order
number screen shot and his contacts / mail etc
Incident will be assigned to you by manager or Team lead. As a pm consultant should start looking in to the issue and speak user
regarding if details are not clear. After checking issue there is no activity price maintained in KP26 by finance team, that’s the root cause!!!!!!!!!!.
Once price maintained then user will get the labour cost in order. And you can confirm with the end user and close the incident.

Issue / Incident- 2--->INC632644

When user try to create notification or order he is unable to create it. User will raise very high priority incident mentioning details in ticket.
After it will be assigned to you. Then you find out there is number range exhausted / consumed. So as functional consultant have to configure the
new number range. Then close the tickets

Issue / Incident- 3
User will raise incident saying unable to do MIGO or confirmation mentioning details in ticket.
After it will be assigned to you, when you check the order you come to know that order still in Created status! You can guide the user to release the
order then he can work on that. These kinds of tickets are raised by user due to lack of knowledge

Issue / Incident- 4
User will raise the incident current month order has not generated from the maintenance plan.
When you check the plan, there is completion indicator is active in the maintenance plan and previous order is not closed. So you can guide the
user to complete the previous order or to remove the completion requirement check box.

Like this you to note down many incidents and can explain in interview.

************************************
Service request:SR384723945
User will raise tickets requesting some help. These are not incidents!!!!!!!!!!!

13
 1) Like additional master data creation / upload request, creation of new equipment, FL, maintenance pan, measuring point, characteristic,
permits etc.
2) Maintenance plan update.
Ex- If user don’t want to generate order for few cycle / months / calls ask help to in ip10 or manually to release or inclusion of new
maintenance plans in batch job variant or to change the call horizon etc.
3) Inactivate or set deletion flag for maintenance pan not to trigger further orders.
4) Mass update / close of orders (iw38 can be used to update any field in mass)
5) Creation of new planner group, plant section, employee responsible, sort field, warranty popup etc(These are to be done in SPRO in
development system after testing quality will move to production )

***********************************
Change request (CR):CHG3034028
User will raise CR for asking new functionalities.
These are to be done in SPRO in development system, Transport request (TR) will be created.
after testing quality will move to production. Actually, any configuration change is CR.

1) New user status profile configuration

2) New tabs / new screen in notifications / equipment screen etc
3) Standard Fields selection (optional, mandatory, hide etc)
4) Asking new notification type
5) New order type configuration (ex- Initially they were not using calibration, after few years they start this maintenance process)

*************************************************************************************************************************************************************
Difference between S / 4 HANA 2020 and ECC6
Just say you worked on both ECC6 and s / 4 HANA 1909 or 2020 version...in S / 4 HANA PM module is same. No major changes....but other
modules like changes FICO, SD, MM changed lot

In case if they asked what are the main difference tell below:
1) S / 4 HANA IP30H (updated version of IP30) transition is there where as in ECC6 only IP30
IP30H we can also do mass schedule maintenance plan based on equipment, functional location, work centre
where as in ECC6 only based maintenance plan, category, strategy, sort field
2) ECC6 only we can print order shop paper after release → but s / 4 HANA even in created status also we can print
3) Less tables in s / 4 Hana and more tables in ECC6
4) More fiori apps in s / 4 HANA and many advance feature, but in ECC6 limited compatibility
5) Performance is better in s / 4 HANA but in ECC6 low performance
6) SAP uses own database in s / 4 HANA.........Ecc6 its oracle database

Just say worked on s / 4 HANA and ECC6 also.

*******************************************************************************************************
RICEF → Learnt based on clint / project requirement → These are only available for particular project / company / clint
Avoid questions on RICEF, just say didn’t get chance to work major RICEF. In our project everything is standard functionality, That’s why looking
opportunity!!!!!!!!!!!!!!!!! in case if they asked given few info below

1) R-Reports
• A SAP report is an executable program that reads data from the database and generates output based on the filter criteria selected by the
end user. It is like display of data based on some selection.
• Standard SAP reports → IW39, IW28, IK09, IH08 etc
• Custom reports → developed by your organization → There is custom / Z transaction (Z T Code)
• When the standard SAP reports does not meet the client or business requirement, we have to develop custom reports with the help of
ABAP team.
• For this we need to understand what is the selection screen, what output they want like what data they want to display on the screen once
the report is executed

2) I-Interface
• In some organizations some of the business processes like Planning , Quality Management functions are executed or maintained in
external systems (Non SAP systems).
• For example for Planning they use third party systems like M2, ADS and for Quality they use LIMS..We need to send the data from SAP
to those Non SAP systems and receive the data from them back to SAP system..
• normally IDocs are used for this data transfers..
• Functional consultant need to give the details what data needs to be transferred or what data to be received, what are fields mapping etc
to the ABAP team…

3) C-Conversion
• Means data load by LSMW, BDC, LTMC etc

4) E-enhancement
• Enhancements are the means by which we add our own / modify existing functionality to SAP’s standard business applications.
• Some requirements from the client cannot be met with Standard SAP. That time we need to go for enhancements.
• Normally enhancements are done through user exits, customer exits, BADI’s...Need to google to find these
• Refer FS document for more information

5) F-Forms
• Forms are nothing but printouts taken from SAP. like Process order print, Inspection lot Certificate of analysis (COA).
• Standard SAP comes with pre configured layout and design of the forms. but these standard forms will not meet customer requirements.
• during this time we need to develop custom forms in coordination with ABAP team.
• or this we need to give the functional specification to the ABAP team with the details like what is the form layout, what data needs to be
printed, from which tables and fields data needs to be fetched for printing the data…based on this ABAP team develop the custom
forms…

For more info on RICEF Refer Google / You tube for more information...Very difficult to explain RICEF topic in class and should be learn based on
project / Realtime
For more information refer below link:

14
https: / / blogs.sap.com / 2014 / 05 / 20 / ricefws-in-sap-projects-and-role-of-functional-consultant

**********************************************************************
USE SE38 / SE37 t codes to run

BAPI-
BAPI is Business Application Programming Interface and has the role as communication platform for developing applications,
e.g. booking material documents from flat files, see more in trx BAPI.

BADI-
Business Add-Ins (BAdIs) are the basis for enhancements where BAdI methods in object plug-ins can be called from ABAP programs.
The calling program controls which BAdI implementations are used by specifying filter values.

User exit-
A point in an SAP program where a customer's own program can be called.
In contrast to customer exits, user exits allow developers to access and modify program components.
There will be customer exit, save exit et

******************************************************************
Interview tips:

Instal Naukri, LinkedIn apps in mobile and start apply.

Say ok for all location even contract job and any companies...at least you get interview experience!!!!!!!!!!!!!!!!

1. Try to explain what you know like master data, notification, order etc........
2. Mention one implementation and say currently working as PM support consultant
3. Don’t mention any other details in CV other than SAP. Mentioning maintenance domain experience is added advantage
4. avoid questions on RICEF, Project experience. Try to explain more on what you learnt in the course.........Consume more time here by explainig
end to end
5. All the documents i have given, you need to refer

15