Upload
himanshu
View
231
Download
5
Embed Size (px)
DESCRIPTION
flight order integration scenario configuration and master data and process flow
Citation preview
ContentsInitial Data Set Up...........................................................................................................................4Step 1 – CC04 – Set-Up Aircraft as-Maintained Structure.............................................................4Step 2 – IH01 - Check the master equipment having the USER data filled properly in Additional data 1 tab..........................................................................................................................................8Step 3 – /AXONX/LTPG_MASTER- Maintain Master data Table for using LTPG functionality.......................................................................................................................................................12Step 4 – CJ20N – Create Project...................................................................................................14Step 5 – CJ20N - Release Project/WBS........................................................................................16Step 6 – /AXONXAPP/WBSDET – Maintain WBS determination table with appropriate WBS, FLOC & Valid from date record...................................................................................................26Step 7 - /ISDFPS/LMFL01- Create Actual and Seasonal Flight Record and it should Trigger LTPG, Create One revision and Notification & Order..................................................................29Step 8 – WPS1 – Check Created Revision....................................................................................31Step 9 – /AXONX/FLTMNT - Check seasonal and Actual Flight record....................................33Flight Updates...............................................................................................................................35Step 10 – /ISDFPS/LMFL02- Update flight details - (Time change)...........................................35Step 11 – WPS1 – Check Updated Flight......................................................................................36Step 12 – WPS1 – Check Updated Revision.................................................................................39Step 13 – /ISDFPS/LMFL02 – Update flight details - (Date Change)..........................................40Step 14 – /AXONX/FLTMNT - Check updated Flight Status......................................................43Step 15 – WPS1 – Check Updated Revision.................................................................................45Flight Updates...............................................................................................................................47Step 16 – /ISDFPS/LMFL02 –Divert Flight (Station Change).....................................................47Step 17 – /AXONX/FLTMNT - Check updated Flight Status......................................................49Step 18 – WPS1 – Check Updated Revision.................................................................................52Step 19 – /ISDFPS/LMFL02 – Update flight details - Aircraft change........................................54Step 20 – /AXONX/FLTMNT - Check updated Flight Status......................................................55Step 21 – WPS1 – Check Updated Revision.................................................................................57Step 22 – /ISDFPS/LMFL02 – Create Connecting flights............................................................59.......................................................................................................................................................59Step 23 – /AXONX/FLTMNT - Check updated Flight Status......................................................60Step 24 – WPS1 – Check Updated Revision.................................................................................61
Step 25 – /ISDFPS/LMFL02 – Update connecting flight details - Divert Flight (Station Change).......................................................................................................................................................63Step 26 – /AXONX/FLTMNT - Check updated Flight Status......................................................64Step 27– WPS1 – Check Updated Revision..................................................................................66Step 28 – /ISDFPS/LMFL02- Update connecting flight details - (Time change).........................68Step 29 – /AXONX/FLTMNT - Check updated Flight.................................................................69Step 30 – WPS1 – Check Updated Revision.................................................................................71Step 31 – /ISDFPS/LMFL02 – Update connecting flight details - (Date Change).......................73Step 32 – /AXONX/FLTMNT - Check updated Flight Status......................................................74Step 33 – WPS1 – Check Updated Revision.................................................................................76Planning Finalisation....................................................................................................................78Step 34 – WPS1 – View Existing Revisions - generated from LTPG...........................................78Step 35 – WPS1 - Release Revision..............................................................................................80Step 36 – WPS1 - Generate Orders...............................................................................................87Step 37 - IW33 - Check work order WBS and Settlement rule.....................................................89Step 38 – IW38 - Release Work Orders........................................................................................93Step 39 – /AXONX/MPW - View Data......................................................................................100
Initial Data Set Up
Step 1 – CC04 – Set-Up Aircraft as-Maintained Structure
P u r p o s e
Use this procedure to set up complex asset As-Maintained structure.
Trigger
Perform this procedure when you change, update, or modify complex asset during maintenance or modification procedures.
When you need to create a new functional location with its structure, you can copy from the existing one in order to reduce the incomplete data.
Prerequisites
As Allowed structure.Documentation; EO, SB/AD, etc.
Menu Path
Logistics > Plant Maintenance > Management of Technical Objects > Environment > Product Structure
Transaction Code
CC04
Helpful Hints
This functionality is related to transaction code IL01, IL02 (Create / Change Functional Location).
P r o c e d u r e
1. From the main SAP screen, follow the menu path:
Logistics > Plant Maintenance > Management of Technical Objects > Environment > Product Structureor use the transaction code CC04
Click or press [ENTER]
Note 1:An existing functional location structure will be used as the basis of this process. The copied structure will then be modified to reflect the new aircraft
Note 2:It is best to copy a complete structure in one go and therefore a top level functional location should be entered at this point. You should choose a structure which is very similar to the new one to minimize the amount of future rework. It is recommended that the structure chosen is the newest aircraft of the same type as being created.
2. Product Structure Browser: Initial Screen
Click on the
Enter the functional location that you wish to copy.
Search Help is available to find the correct functional location by press F4 or icon.
Press [ENTER] or click button to continue
3. Product Structure Browser: Validity Date nn.nn.nnnnClick on the first line of the structure (this will be the line starting with the inputted functional location)
Using the context menu (right mouse click whilst holding the mouse over the highlighted line)
Select the ‘Copy Subhierarchy’ menu option.
NoteEnsure that the two ‘copy from template’ radio buttons are selected and all the ’sub-objects to be copied’ selection boxes are selected
4. Pop up: Create Functional Location HierarchyEnter the new Functional Location name in the functional location field in the New Functional Location screen area.
Click to copy the functional location
Click to copy the functional location
6. Product Structure Browser: Initial Screen
Press and enter the new top level function location name in the Functional location box
Press [ENTER] or click button to continue
7. Product Structure Browser: Validity Date nn.nn.nnnnClick on the first line of the structure (this will be the line starting with the inputted functional location)
Using the context menu (right mouse click whilst holding the mouse over the highlighted line) select the ‘change’ menu option.
Change the following fields:
Description Model Number
Click on the Partners icon on the main icon bar and then enter
Sold-to Party (= aircraft operator)
Click on to move back to the main functional location detail screen
Click on the tab
Tail number into Sort Field
Step 2 – IH01 - Check the master equipment having the USER data filled properly in Additional data 1 tab
P u r p o s eThis User data in the Equipment helps to pick the correct entries in LTPG_MASTER table to create Revision and notification creation based on flight schedule updates
Trigger
This user data helps in generating flights
Prerequisites
Aircraft Type, Sub type, Fleet type
Menu Path
Logistics > Plant Maintenance > Management of Technical Objects > Functional location > Structural Display
Transaction Code
IH01
Helpful Hints
NIL
P r o c e d u r e1. Use the Transaction code to access the Structural display
R e s u l t Checked the entries in User data
Step 3 – /AXONX/LTPG_MASTER- Maintain Master data Table for using LTPG functionality
P u r p o s eThis is a master table to maintain settings for Revision and notification creation based on flight schedule updates
Trigger
Planning and Slot Creation
Prerequisites
Revision Type
Menu Path
NIL
Transaction Code
/AXONX/LTPG_MASTER
Helpful Hints
NIL
P r o c e d u r e1. Use the Transaction code to access the Table
2. Maintain the Entries for Revision Type and Duration of Revision etc.3. Maintain the task list and Notification type to be generated
Save the transaction
R e s u l t Master table has been updated
Step 4 – CJ20N – Create Project
P u r p o s eUse this procedure to create a new project
Trigger
New Project will be created
Menu Path
Logistics>Project System>Project>Project Builder
Transaction Code
CJ20N
Helpful Hints
NIL
P r o c e d u r e1. Use the Transaction path menu or Transaction code to create Project
2. Click on this to create new project
3. Enter the following details:-Project definition – Aircraft Routine check
4. Project has been created
R e s u l tNew Project has been created.
Step 5 – CJ20N - Release Project/WBS
P u r p o s e
Use this procedure to approve or release project. The WBS Element together with its Network Activities are created automatically by the system when the engine/complex asset repair work scope is set up in the Sales Order. The following steps show how to release the project so that repair work can begin
Trigger
Perform this procedure when approve or release project.
Prerequisites
Notification and sales order are readyMaster data; standard network, standard project definition, material service, and variant configuration are set up.
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Project System > Project > Project Builder
P r o c e d u r e
1. Start the transaction using the menu path or transaction code.
SAP Easy Access
2. Click CJ20N - Project Builder tree item .
3. Double-click CJ20N - Project Builder tree item .
Field R/O/C Description
Project Definition R
Example:Enter the Project created during induction workscope
6.Click Open button .
Project Builder: Project 11934
7.Click button .
8. Click Edit main menu .
9.Click Edit Status Release Ctrl+F2 menu item .
Milestone Function
10.Click Continue button .
Transfer parameters from superior network to subnetwork
11.
Click control .
12.Click Continue button .
Transfer parameters from superior network to subnetwork
15.Click Continue button .
Create Relationship for Subnetwork
16.Click Yes button .
Information
17.Click Continue button .
18. You can view “Status was set” message at the status bar
.
19. As required, complete/review the following fields:
Field R/O/C Description
System Status R
Example:REL
20.Click button .
Project Builder
21. Project 11934 is being changed message at status bar can be viewed.
R e s u l t
You have approved or released project.
Step 6 – /AXONXAPP/WBSDET – Maintain WBS determination table with appropriate WBS, FLOC & Valid from date record
P u r p o s eUse this procedure to Maintain WBS determination table with Functional location and Valid from date record.
Trigger
Project System integration to Work Orders
Prerequisites
Functional location must exist
Menu Path
NIL
Transaction Code
/AXONXAPP/WBSDET
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code to open the master table
2. Click on this button
3. Enter the following details :-Plant – X003Revision Type – A1Valid from – 01.01.2015Functional location – AC101Notification type – A1WBS Element – 11934
4. Click on this to save the values
R e s u l tData has been maintained successfully.
Step 7 - /ISDFPS/LMFL01- Create Actual and Seasonal Flight Record and it should Trigger LTPG, Create One revision and Notification & Order
P u r p o s eUse this step to generate Actual record.
Pre-requisites
Functional location, Master Equipment
In cluster table ‘/AXONFLT/CU17’ against order and plant, flight integration method should be set to ‘Create Flight Header/Flight Schedule/Revision and Notification’ and flight integration should be enabling.
Transaction Code
/ISDFPS/LMFL01
P r o c e d u r e1. Access the transaction using the Transaction code
2. Maintain the time and dates for flight
3. After save, it should generate the Order.
R e s u l tRecord updated successfully.
Step 8 – WPS1 – Check Created Revision
P u r p o s eUse this procedure to review the created revision.
Trigger
Revision gets created.
Menu Path
NIL
Transaction Code
WPS1
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code to open the revision
2. Click on this to select revision3. Enter the functional location and Plant to open the revision
Changes have been reflected in the revision.R e s u l t
Revision has been created.
Step 9 – /AXONX/FLTMNT - Check seasonal and Actual Flight record
P u r p o s eUse this step to Check Actual and Seasonal record.
Pre-requisites
Record should exist
Transaction Code
/AXONX/FLTMNT
P r o c e d u r e1. Access the transaction using the Transaction code
/AXONX/FLTMNT
2. Seasonal flight record should get updated
Flight Updates
Step 10 – /ISDFPS/LMFL02- Update flight details - (Time change)
P u r p o s eUse this step to change Flight time
Trigger
Flight Record
Prerequisites
Actual Flight Record
Menu Path
NIL
Transaction Code
/ISDFPS/LMFL02
P r o c e d u r e1. Execute the transaction and change time to:
Field Estimated TimeTake off Time 09:00:00Landing Time 15:00:00
Update takeoff and landing time, and save,
R e s u l tFlights have been updated.
Step 11 – /AXONX/FLTMNT – Check Updated Flight
P u r p o s eUse this procedure to review the changes incorporated in the existing Flight.
Trigger
Flight gets updated.
Prerequisites
Flight must exist.
Menu Path
NIL
Transaction Code
/AXONX/FLTMNT
P r o c e d u r e1. Use transaction code to open the Flight
2. Execute the tcode and check the updated time.3. Seasonal record should get updated.
And Actual record should get updated
Changes have been reflected in the Flight.R e s u l t
Flights have been updated.
Step 12 – WPS1 – Check Updated Revision
P u r p o s eUse this procedure to review the changes incorporated in the existing revision.
Trigger
Revision gets updated.
Prerequisites
Revision must exist.
Menu Path
NIL
Transaction Code
WPS1
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code to open the revision
2. Click on this to select revision3. Enter the functional location and Plant to open the revision
Changes have been reflected in the revision.R e s u l t
Revision has been updated.
Step 13 – /ISDFPS/LMFL02 – Update flight details - (Date Change)
P u r p o s eUse this step to change Flight Date.
Trigger
Flight Record
Prerequisites
Actual Flight Record
Menu Path
NIL
Transaction Code
/ISDFPS/LMFL02
Helpful Hints
NIL
P r o c e d u r e
1. Start the transaction using the menu path or transaction code./ISDFPS/LMFL02
2. As required, change the following fields:
Field R/O/C Description
Takeoff date R
Example:02.03.2015
Land. date R
Example:02.03.2015
R e s u l tChanges have been updated successfully.
Step 15 – WPS1 – Check Updated Revision
P u r p o s eUse this Procedure to check the updated revision
Trigger
Revision gets updated
Prerequisites
Revision must exist
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Plant Maintenance > Maintenance Processing > Maintenance Event Builder > Maintenance Event Builder
Transaction Code
WPS1
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code or menu path to open the transaction
2. Click on this to select revision
3. Enter the functional location number and click on this to execute
Revision for previous date i.e. 01.03.2015 should get delete and new revision should get create for 02.03.2015
R e s u l tRevision has been successfully updated.
Flight Updates
Step 16 – /ISDFPS/LMFL02 –Divert Flight (Station Change)
P u r p o s eUse this step to divert the Flight
Trigger
Flight Record
Prerequisites
Actual Flight Record
Menu Path
NIL
Transaction Code
/ISDFPS/LMFL02
Helpful Hints
NIL
P r o c e d u r e
1. As required, change the following fields:
Field R/O/C Description
Landing Station R
Example:SIN
To R
Example:AMS
And save the transaction.
R e s u l tChanges have been updated successfully.
Step 17 – /AXONX/FLTMNT - Check updated Flight StatusCheck seasonal flight
Check actual flight
Previous flight of KUL-SIN should get delete and new record should create for KUL-AMS
Step 18 – WPS1 – Check Updated Revision
P u r p o s eUse this Procedure to check the updated revision
Trigger
Revision gets updated
Prerequisites
Revision must exist
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Plant Maintenance > Maintenance Processing > Maintenance Event Builder > Maintenance Event Builder
Transaction Code
WPS1
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code or menu path to open the transaction
2. Click on this to select revision
3. Enter the functional location number and click on this to execute
Revision date and time has been updated after diversion of flight.Previous flight (1065) should get delete and new revision (1066) of flight get created.
R e s u l tRevision has been successfully updated after diversion of flight.
Step 19 – /ISDFPS/LMFL02 – Update flight details - Aircraft change
P u r p o s eUse this Step to Change the Aircraft and update Flight Details
Trigger
Change Flight data
Prerequisites
Actual Flight Data
Menu Path
NIL
Transaction Code
/ ISDFPS/LMFL02
Helpful Hints
NIL
P r o c e d u r e
1. Start the transaction using the menu path or transaction code.
R e s u l tChanges have been updated successfully.
Step 20 – /AXONX/FLTMNT - Check updated Flight Status
Seasonal and Actual flight should get updated successfully, with new floc
Step 21 – WPS1 – Check Updated Revision
P u r p o s eUse this procedure to check the updated Revision.
Trigger
Revision has been updated
Prerequisites
Revision must exist
Menu Path
Logistics > Plant Maintenance > Maintenance Processing > Maintenance Event Builder > Maintenance Event Builder
Transaction Code
WPS1
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code or menu path to open the transaction
2. Click on this to select revisionOld revision should get delete and new revision should be created on same flight key.
R e s u l tRevision has been successfully updated.
Step 22 – /ISDFPS/LMFL02 – Create Connecting flights
P u r p o s eUse this Step to create connecting flights
Trigger
Seasonal Flight Record, Revision, Notification, Order
Prerequisites
Functional Location, Equipment, Seasonal Record
Menu Path
NIL
Transaction Code
/ISDFPS/LMFL02
P r o c e d u r e1. Create legs for flight order,
Click on and save the tcode.
R e s u l tRecords saved successfully.
Step 23 – /AXONX/FLTMNT - Check updated Flight Status
Main flight (KUL-AMS) should get delete and the new connecting flight (KUL-LHR and LHR-SIN) should get create for both seasonal and actual.
R e s u l tFlight Record has been successfully updated.
Step 24 – WPS1 – Check Updated Revision
P u r p o s eUse this Procedure to check the updated revision
Trigger
Revision gets updated
Prerequisites
Revision must exist
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Plant Maintenance > Maintenance Processing > Maintenance Event Builder > Maintenance Event Builder
Transaction Code
WPS1
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code or menu path to open the transaction
2. Click on this to select revisionRevision should get DLT for KUL-SIN and new revision should be created for connecting flights.
R e s u l tRevision has been successfully updated.
Step 25 – /ISDFPS/LMFL02 – Update connecting flight details - Divert Flight (Station Change)
P u r p o s eUse this step to divert the Flight
Trigger
Flight Record
Prerequisites
Actual Flight Record
Menu Path
NIL
Transaction Code
/ISDFPS/LMFL02
Helpful Hints
NIL
P r o c e d u r e
1. As required, change the following fields:
Field R/O/C Description
Landing Station R
Example:LHR
Field R/O/C Description
To R
Example:LAX
` `
Click on and save the tcode.
R e s u l tChanges have been updated successfully.
Step 26 – /AXONX/FLTMNT - Check updated Flight StatusSeasonal flight should get update as:
Step 27– WPS1 – Check Updated Revision
P u r p o s eUse this Procedure to check the updated revision
Trigger
Revision gets updated
Prerequisites
Revision must exist
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Plant Maintenance > Maintenance Processing > Maintenance Event Builder > Maintenance Event Builder
Transaction Code
WPS1
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code or menu path to open the transaction
R e s u l tRevision has been successfully updated.
Step 28 – /ISDFPS/LMFL02- Update connecting flight details - (Time change)
P u r p o s eUse this step to change Flight time
Trigger
Flight Record
Prerequisites
Actual Flight Record
Menu Path
NIL
Transaction Code
/ISDFPS/LMFL02
P r o c e d u r e1. Execute the transaction and change time to:
Field Estimated TimeLanding Time 12:45:00Takeoff Time 13:30:00
Update takeoff and landing time, and save,
Step 29 – /AXONX/FLTMNT - Check updated Flight
P u r p o s eUse this Step to check updated Flight Details
Trigger
Check updated Flight data
Prerequisites
Actual Flight Data
Menu Path
NIL
Transaction Code
/AXONX/FLTMNT
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code to open the Flight
Seasonal record should get update as:
Actual record should update as:
R e s u l tChanges have been updated successfully.
Step 30 – WPS1 – Check Updated Revision
P u r p o s eUse this procedure to review the changes incorporated in the existing revision.
Trigger
Revision gets updated.
Prerequisites
Revision must exist.
Menu Path
NIL
Transaction Code
WPS1
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code to open the revision
2. Click on this to select revision3. Enter the functional location and Plant to open the revision
Revision gets updated with the new time
R e s u l tRevision has been updated.
Step 31 – /ISDFPS/LMFL02 – Update connecting flight details - (Date Change)
P u r p o s eUse this step to change Flight Date.
Trigger
Flight Record
Prerequisites
Actual Flight Record
Menu Path
NIL
Transaction Code
/ISDFPS/LMFL02
Helpful Hints
NIL
P r o c e d u r e
1. Start the transaction using the menu path or transaction code./ISDFPS/LMFL02
2. As required, change the following fields:
Field R/O/C Description
Takeoff date R
Example:02.03.2015
Field R/O/C Description
Land. date R
Example:03.03.2015
Changed date of LAX-SIN
And save the transaction.
R e s u l tChanges have been updated successfully.
Step 32 – /AXONX/FLTMNT - Check updated Flight StatusCheck seasonal and actual flight
Old flight should get delete and new flight should be created.
R e s u l tChanges have been updated successfully.
Step 33 – WPS1 – Check Updated Revision
P u r p o s eUse this Procedure to check the updated revision
Trigger
Revision gets updated
Prerequisites
Revision must exist
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Plant Maintenance > Maintenance Processing > Maintenance Event Builder > Maintenance Event Builder
Transaction Code
WPS1
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code or menu path to open the transaction
2. Click on this to select revision
3. Enter the functional location number and click on this to executeRevision for previous date i.e. 02.03.2015 should get delete and new revision should get create for 03.03.2015
R e s u l tRevision has been successfully updated.
Planning Finalisation
Step 34 – WPS1 – View Existing Revisions - generated from LTPG
P u r p o s eUse this Procedure to check the updated revision
Trigger NJU7
Revision gets updated
Prerequisites
Revision must exist
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Plant Maintenance > Maintenance Processing > Maintenance Event Builder > Maintenance Event Builder
Transaction Code
WPS1
Helpful Hints
NIL
P r o c e d u r e1. Use transaction code or menu path to open the transaction
2. Click on this to select revision
3. Revision date and time has been updated after diversion of flight
R e s u l tRevision has been successfully updated.
Step 35 – WPS1 - Release Revision
P u r p o s e
Use this procedure to release revision. This Step denotes the handover between planning and production and should be undertaken when the work package is complete from a planning perspective.
Trigger
Perform this procedure when releasing revision.
Prerequisites
Revision is set up
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Plant Maintenance > Maintenance Processing > Maintenance Event Builder > Maintenance Event Builder
Transaction Code
WPS1
Helpful Hints
Nil
P r o c e d u r e
1. Start the transaction using the menu path or transaction code.
SAP Easy Access
2. Click WPS1 - Maintenance Event Builder tree item .
3. Double-click WPS1 - Maintenance Event Builder tree item .
Revision Selection
6. As required, complete/review the following fields:
Field R/O/C Description
Revision Number R
Example:Enter the Revision created in earlier step
Maintenance Event Builder
7. Select the revision 1068 (QF 121 20150302) tree item .
8.Click button .
Maintenance Event Builder
11.Click button .
R e s u l t
You have released revision.
Step 36 – WPS1 – Check Existing Orders
P u r p o s e
Use this procedure to generate orders for the notifications packaged to the Revision. The guide describes how to perform PM-PS assignment of orders that were generated as well.
Trigger
This procedure is triggered when orders have to be generated and assigned to PM-PS to capture costs to the Project
Prerequisites
Revision/maintenance slot or operative network created Notifications packaged to the revision
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Plant Maintenance > Maintenance Processing > Maintenance Event Builder > Maintenance Event Builder
Transaction Code
WPS1
Helpful Hints
Nil
P r o c e d u r e
1. From the main SAP screen, follow the menu path:
Logistics > Plant Maintenance > Maintenance Processing > Maintenance Event Builder > Maintenance Event Builderor use the transaction code WPS1
Click or press [ENTER]
2. Maintenance Event Builder
click on button in revision area to search for revisions.
3. Revision Selection
Enter the following selection data:
Maintenance Planning Plant
Revision Number
OR
Functional Location
OR
WBS Element
Network
Click on button to execute.
4. Maintenance Event Builder
5. Maintenance Event Builder
R e s u l t
You have generated orders.
Step 37 - IW33 - Check work order WBS and Settlement rule
P u r p o s e
Use this procedure to check the WBS element and settlement rule.
Trigger
Perform this procedure to check work for WBS element and Settlement rule
Prerequisites
Work order must exist.
WBS element must exist.
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Plant Maintenance > Maintenance Processing > Order > Display Order
Transaction Code
IW33
Helpful Hints
Nil
P r o c e d u r e
1. Start the transaction using the menu path or transaction code.
SAP Easy Access
2. Click on IW33 to display the order
3. Now click on this button to check the Settlement
4. Go to Location Tab page and check the WBS element will be copied
R e s u l t
WBS Element and settlement rule has been successfully copied.
Step 38 – IW38 - Release Work Orders
P u r p o s e
Use this procedure to update and release mass work orders. Before the actual maintenance process starts, work orders need to be updated and released.
Trigger
Perform this procedure when updating and releasing work orders.
Prerequisites
Build orders are created.
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Plant Maintenance > Maintenance Processing > Orders > Order List > Change
Transaction Code
IW38
Helpful Hints
Orders that generated in the previous step
P r o c e d u r e
1. Start the transaction using the menu path or transaction code.
SAP Easy Access
2. Click IW38 - Change tree item .
Change PM Orders: Selection of Orders
4. As required, complete/review the following fields:
Field R/O/C Description
WBS Element Order Header
R
Example:11934
16.Click button .
R e s u l t
You have changed and released maintenance orders.
Step 39 – /AXONX/MPW - View Data
P u r p o s e
Use this procedure to check Asset data, Flight data, Capacity data and etc.
Trigger
Perform this procedure too check load on MPW.
Prerequisites
Flight, revision should exist.
Menu Path
Use the following menu path(s) to begin this transaction:
Logistics > Plant Maintenance > Maintenance Processing > Orders > Order List > Change
Transaction Code
/AXONX/MPW
Selection Screen: