SCN : Document List - Enterprise Asset Management (SAP EAM)

Introduction

In an enterprise, the mapping /structuring of assets (as Functional Locations & Equipments) is generally done as per the process flow. The structure is nothing but the Asset tree, how the assets are installed in the shop-floor. We know this structure is seen through IH01, which we can say the gateway to SAP-Plant maintenance.

Agencies with different expertise are usually involved in the upkeep/maintenance of these assets such as

-Mechanical Maintenance

-Electrical Maintenance

-Instrumentation

-Air Conditioning

All these agencies record their jobs through Notifications and Maintenance Orders on their respective equipments

of this Equipment tree (Structure).

So far we are discussing about the Maintenance Agencies owned by the the Shop.

But there is a situation in Organizations where Centralized Maintenance Agencies exist and they are authorized to access some of these Assets and these Agencies are labelled with different Planner Groups.

The constraint to provide them the IH01 tree, displaying only their Equipments, is that all these equipments have planner groups filled with those of the agencies owned by Shop.

The present topic is about this situation.

Objective

Need to give a Customized IH01 Structure to these Central Service agencies, using a field other than the Planner Group.

(Because the Planner Group field is already consumed by maintenance agencies owned by shop)

How?

Here Comes the idea of using the I_BEGRPAuthorization Object.

That is, uUsing the Authorization Group field in Equipment Master.

Let's see a sample structure shown below.

Now suppose the Equipment to Agency relation in each branch (Pusher) is as under:

Assets	Shop's Own Agncies	Central Agencies
First two equipments	Mechanical	User1
Next two equipments	Electrical	User2
Fifth Equipment	Instrumentation	User3
Sixth Equipment	Airconditioning	User4

As said before the objective is to restrict the display to their respective equipment.

Create Authorization Groups for these Central Agencies in SPRO

Now go to ‘Change Equipment Master’ (IE02) of each of these equipments, give the respective authorization group values and save, as shown below.

Then

Create 4 Roles (One each for these 4 agencies) through PFCG or modify existing Roles as under:

Shown below is the role for AGR1 Mechanical Maintenance Agency

Assign these Roles to the respective Users.

Now when the user1 (Centralised Mechanical services) goes to the Structure (IH01) the following is the tree he will be seeing.

(Only those 2 of his jurisdiction)

Similarly, when the user2 (Centralised Electrical services) goes to the Structure, he will be seeing…

….. So on for other users.

Now an exapmle of the real application of this feature

There is an Enterprise having about 60 shops (departments). The structure here has thousands of functional locations, lakhs of equipments and many hundred Planner groups.

Now there exist a central repair agency which attends major repairs on a certain category of equipments through-out the enterprise. The list of the equipments relevant to this agency, covers only those equipments of a particular planner group of shop, which satisfy certain conditions (e.g., Motors >50KW).

Here comes the use of controlling the structure display though an object other than a planner group.

So all such equipments have been assigned an Authorization Group and a display role was created on this object (I_BEGRP) and assigned to the users of this central agency, to display structure with equipments of their jurisdiction only.

Pictorial depiction of required equipments in the structure.

Important Note:

One Pre-requisite is that AuthorizGroup fields in 100% Equipments need to be in filled condition with some value. If it is not so, then the user will see the Equipments with blank AuthorizGroup field also alongwith Equipments with his own AuthorizGroup values.

Hope this knowledge piece is of relevance to some of the members.

Thank you

Jogeswara Rao K

How maintenance is planned within your company? De-Centralized, Centralized or Partial Centralized?

How is capacity planning performed in your maintenance plants?

Are certain types of maintenance work planned or executed with consideration to the plant sections?

Do you subdivide your maintenance plant in locations to facilitate the maintenance job or for purpose of reporting?

How is maintenance work organized?

How are the maintenance teams / labor resources organized?

How are your technical systems structured?

What types of technical objects do you handle (Types of Equipment and functional location)?

Is the hierarchy for functional locations structured according to spatial, functional or technical viewpoints? Is Real Estate objects are integrated?

How detailed should the functional location hierarchy be (for example, number of levels, installation and dismantling of equipment)?

Do you link documents to functional locations/Equipment?

Do you need to record the performance of functional locations using measuring points and counters?

Do you track warranties/Guaranties?

Are your technical objects classified (Class/Chars) used in you company?

List and describe the different categories of equipment/Functional Location that you maintain.

How many equipment and functional location you manage in your system?

Do you use Object part, Damage, Cause and Activity analysis?

Do you use Fleet Maintenance process?

Do you use Equipment BoMs? Whats the volume of data?

What types of Task List do you use? Whats the volume of data?

Do you use Maintenance Plans (for example Time based or Performance based or both)?

What maintenance type do you do (for example Breakdown, Corrective, Calibration, Refurbishment, Preventive etc.)?

Do you have any third party system integrated with SAP PM?

How do you settle the cost and how you see the cost reports on Equipment and Functional location?

Which reports do you use in SAP PM?

Service order has many date fields which capture the timing of planning and execution. More often than not the name of field does not convey the actual meaning. Via this document I have tried to build a quick reference of Service Order date fields.

Actual Start date: It is the start date of first operation in Order.It does not get filled till we do the first confirmation on the Order. I would like to clarify that the First Operation does not mean the first operation in numerical sequence but the first operation which gets confirmed. The first Actual start date of an Operation flows is also the Actual Start date of the Order. In short this field captured the real start of work (Actualignores scheduling and goes with confirmation off course that is why it is an Actual).

Actual Order Finish date:Similar to Actual start date the Operation finish date is populated as soon as the Operation is confirmed, only difference is in case of Order it is associated with the confirmation of the last operation. .For some reason if we choose not to record the confirmation for the Operation which has confirmation required in configuration and do the TECO, we miss the Actual Order Finish date, because Actual Order Finish date is very closely linked to confirmation of the last operation in time sequence.

Actual Release date:This is the Release date of an Order meaning when the system status of the Order has changed from Created to Release. If the order does not get released due to some issue (attains Release rejected RELR) then the value is not stored.

Available from date/Available to date: I am unable to determine the business logic behind these two fields. While trying to find its usage, I see them used in just one class "CL_EX_ES_MUL_LIST_TZ_CORE_IMPL" which appears to be more of a technical class (handling session programming) instead of having any business logic. I would like peers to comment on these two fields.

Basic Start/Finish Date:These are the most important date field on the Service order, as it contains the input required to initiate the scheduling. These dates are closely linked to Scheduling Type and used in scheduling to determine the start and end of Operations. So the key purpose of these fields to arrive at the schedule for each operation. Operation not having any duration are ignored are ignored in calculation.

Change date:This field stores an Order change date. The description of the field states “Change date for Order Master”. Order Master is AUFK and the field is updated regardless of changes done at AUFK or AFPO, RESB etc. (I have tried these three basic tables). There could be exceptions where this field is not updated despite changes done in IW32 but not to my knowledge.

Note: The label “Change data for Order Master” does not seem the best possible description of the field.

Created on:It is the date on which Order is created.

History from: It is stored on Maintenance Orders which are archived through Order archiving process. It contains the date on which the archiving was executed. This field will get the value after archiving so we can see it populated only on historical orders.

Period (Service Order Selection screen):If we take literal meaning of this field we understand it is a range. This mapping of period to a field in order Header is unclear from field label. This field acts as selection range for all the Orders which has reference date falling in the period specified. It refers to reference date on the Order.I have explained the significance of Reference date later in this document.

[I am sure we could have done better with the naming of this field as “Period” does not signify the business meaning]

Purchase Order Date:This field can contain the PO related date. At times we get the date on which Customer created and sent a PO for repair. This is one of the freely available fields which can be used to store the date if we want to store the information related to PO.As It is not linked to Purchase Order Technically and can store a value independent of Purchase order.

Reference Date:It contains two dates over the life cycle of the Order. If the Order is not completed it contains Order start date but once the Order is complete it store the technical completion date. It is also the date which gets referred in Period field on Order selection screen (T code IW73).

Scheduled Start/Finish date: It is the planned start date of first operation and the value is derived as soon as scheduling is executed. The calculation is primarily dependent on Basic dates, scheduling type and duration.

Note:Whenever an operation is dropped and scheduling is re executed the scheduled date changes.

Though I have not seen the practical usage of each field above, this is my high level understanding of date fields based on experience and search. If you have reached till this line then feel free to provide your feedback on document, I will be more than happy to incorporate any contextual missing information.

Anjan

Equipment Task list Display Report by using SQVI

Hi All,

This is my First Document in the Forum and hope this will be helpful for all.

Purpose:

IA10 and IA17 standard reports are available to display equipment task list, unfortunately this only brings across the information as it would be printed so there is a lot of work to be done in the spreadsheet to get what you want to see. But maybe not impossible! Hope this report will helps Plant Maintenance users to view the maintenance task list details of multiple equipment’s and save into spreadsheet.

The report will be created by using T code SQVI

Used SAP Tables:

1. EQUZ
2. ILOA
3. EQKT
4. IFLOTX
5. EAPL
6. PLKO
7. PLPO
8. PLWP
9. T351X

Step 1:

Enter T Code SQVI

Enter Name of the program for the report in the quick view field and press create button

Now enter the Title for the report and select data source as table join.

Select basis mode and press enter

Step 2:

Press to enter the table name

Step 3:

Again click on table and enter table which should be link to previous table. Example in EQUZ Equipment number it is linked to EQKT equipent number.

We can take n number of tables which should linked to previous entered table.

Enter tables EQKT, EAPL, PLKO, PLPO, PLWP and T351X by following the previous step.

Step 4:

You can delete / edit table connections by selecting the black line and clicking with the right-mouse button.

Select the unwanted connections and delete by clicking the right –mouse button.

Step 5:

Enter 2 more tables ILOA and IFLOTX

Bring ILOA and IFLOTX tables to the starting screen to connect EQUZ table.

Step 6:

Click join condition button on the top of the screen

Now give EQUZ and ILOA table and press enter

The logic:

1. Select EQUNR field from EQUZ table and pass this into EQKT table to get equipment number and description
2. Take EQUNR field from EQKT table and pass this into EAPL table to get the task list details.
3. Take PLNNR field from EAPL table and pass this into PLKO table to get the planner group.
4. Take PLNNR field from PLKO table and pass this into PLPO table to get operation details
5. Take PLNNR & PLNKN fields from PLPO table and pass this into PLWP table to get the required maintenance strategy of task list.
6. Take PAKET & STRAT fields from PLWP table and pass this into T351X table to get the maintenance schedule of operation.
7. Select EQUNR field from EQUZ table and pass this into ILOA table to get functional location. description
8. Select TPLNR field from ILOA table and pass this into IFLOTX table to get functional location description.

After removing the unnecessary links between tables the final links as given below

Table links:

EQUZ-EQUNR-EQKT

EQKT-EQUNR-EAPL

EAPL-PLNNR-PLKO

PLKO-PLNNR-PLPO

PLPO-PLNNR-PLNKN-PLWP

PLWP-PAKET-STRAT-T351X

EQUZ-ILOAN-ILOA

ILOA-TPLNR-IFLOTX

Step 7:

Press back button after connecting the table links

Press to switch between filed names and technical names

Step 8:

Selection fields is for input screen of the report

List fields is for output of the report

Input Fields:

EQUZ-EQUNR (Equipment Number)

PLKO-VAGRP (Planner Group)

PLPO-WERKS (Plant)

Output Fields:

PLPO-WERKS (Plant)

ILOA-TPLNR (Functional Location)

IFLOTX-PLTXT (Functional location Description)

EQKT-EQUNR (Equipment Number)

EQKT-EQKTX (Equipment Description)

PLKO-VAGRP (Planner Group)

PLPO-LTXA1 (Task list Operation Text)

T351X-STRAT (Strategy)

T351X-KTEX1 (Maintenance Package Text)

Select the above input and output fields in the quick viewer screen

Press to switch between filed names and technical names

Select the output fields for the report

Step 9:

Now go to sort fields tab to enter field names to sort

Select to find required field

Click after entering the table and field name

Click to enter sort fields into quick viewer

Sort Fields:

ILOA-TPLNR

EQKT-EQUNR

EQKT-EQKTX

PLPO-WERKS

IFLOTX-PLTXT

Select at the top left side of the screen

Select output headings of the report to change if required, we can change and modify the output length as required

Press Back Button on the screen to save the SQVI report

The SQVI report has been saved, select the line item and press execute to run the report

Input Screen:

Output Screen:

Procedure to create tcode:

Go to system –status on the input screen

Copy the programme name and give it to the ABAPER to create TCODE for the report.

Hope you all will find the Document Helpful.

Thanks & Regards,

Sunil Boya

1.0 Why do we need effective Spare parts planning?

It is a challenge for asset intensive industries to maintain optimum level of spare parts in the inventory. Keeping lower levels of parts than required could mean non availability of parts in time to carry out planned and unplanned maintenance, thereby increasing equipment down time. Reduced availability of equipment can lead to lower production and impacts meeting customer delivery schedules. On the other hand, keeping higher inventory of spare parts means higher inventory carrying cost which will increase overall production cost. Also, industry often experiences the risk of excessive stock of parts in the inventory becoming obsolete over a period of time due to technology and engineering advancements. Either way, it is a challenge for maintenance planners and the MRO stock planners to keep the optimum level of stock on continuous basis.

2.0 Business criticality

Most manufacturing plants and maintenance departments face the challenge of lowering operating cost and improving service levels. Manufacturing systems have become more sophisticated due to demand for agility and flexibility over involving greater capital investments. This has added complexity in maintaining machinery in running condition with minimal impact to production and minimal impact to customer delivery schedules.

Demand unpredictability, part alternatives, high service levels, accurate forecast of part requirement also add to the complexity to the planning for spare parts.

3.0 Key business process requirements

Here are a number of business process requirements that drive spare parts planning:

Ability to plan for parts based on a variety of factors such as criticality, cost, consumption, combination of these factors
Integration of production and operation planning to optimize equipment availability
Optimize spare parts storage with respect to usable life as well as storage space constraints
Ability to dynamically update part availability due to material transfers
Handle shelf life expiry and maximize usable life
Ability to track service levels and parts consumption and to update planning dynamically
Ability to carry out cycle counting based on criticality, parts consumption, parts value, etc.
Use of performance metrics such as overall equipment efficiency (OEE), MTTR, MTTF, unplanned downtime, repair cost, etc.

4.0 SAP ERP functionality to support Spare parts management

SAP ERP supports these key requirements through Plant Maintenance module and integrated functions including inventory, warehouse, procurement, finance and costing. In addition, maintenance scheduling can impact production scheduling. Some of the key functions of SAP that support spare parts planning are described below:
.

4.1 Material Master Setup

Spare parts can be broadly classified as:

Stock Items: Materials for which stock is usually maintained in the store room.
Non-Stock Items: Materials that are usually one time purchases and not maintained as stock in store room.

Requirement for maintenance spare parts are usually generated in the following ways:

Re-Order planning: Store room personnel maintains the minimum and maximum stock levels for most of the MRO items. Procurement process is triggered based on the Re-order level. System creates dependent requirements for all the parts that are subject to requirements planning.
Manual purchase requirements: Purchase requirements are manually created by users as and when the parts are required (during emergency breakdown for example).
Automatic purchase requisitions: System can automatically generate purchase requisitions for non-stock items, if they are used in the work orders.

The table below lists the combination of common MRP parameters used for re-order planning of MRO spares. The combination of MRP type and Lot size keys in conjunction with reorder point, fixed lot, max stock addresses most of the common planning needs for maintenance spare parts.

MRP Type	Lot Size	Reorder Point	Fixed Lot	Max Stock	Effect
V1	HB	X		X	Replenishes to max stock level when below re-order point; allows work order influence
V1	FX	X	X		Replenishes to a fixed quantity when below re-order point; allows work order influence
VB	HB	X		X	Replenishes to max stock level when below re-order point; does not allow work order influence
VB	FX	X	X		Replenishes to a fixed quantity when below re-order point; does not allow work order influence
PD	EX				Orders only per work order requirement. allows work order influence
ND					No planning; will not order

4.2 Integration of PM with Procurement processes

Determination of requirements: Requirements are determined based on MRP planning or manual purchase requirements
Approval process: Once purchase requisitions are approved by authorized personnel, they are converted to purchase orders to carry out the procurement process
Source determination: Potential sources of supply based on past orders and existing long-term purchase agreements. This speeds up the process of creating the requests for quotation (RFQs)
Quotations: Functionality to compare a number of quotations, different pricing and terms, etc.
Purchase order processing: Information from requisition to quotation can be included in a purchase order. Different types of POs include scheduling agreements, contracts etc.
Goods receipt and inventory management: Goods receiving personnel can confirm the receipt of goods simply by entering the PO number. By specifying permissible tolerances, 'over' and 'under', deliveries of ordered goods can be limited.
Invoice verification: Invoices can be verified and accounts payable clerk is notified of quantity and price variances for clearing and payment.

4.3 Integration of PM with Warehouse processes

Managing stock: Stock for materials is updated real-time when goods movement transactions are carried out. Stock overview of the current stock situation of any given material can be obtained. For example, stocks that -
- are located in the warehouse
- have already been ordered, but have not yet been received
- are located in the warehouse, but have already been reserved
- have other statuses like quality inspection
Types of Physical Inventory
- Periodic inventory
- Continuous inventory
- Cycle counting
- Inventory sampling
Cycle counting process
- Cycle counting is a method of physical inventory where inventory is counted at regular intervals within a fiscal year. Cycle counting allows you to count fast moving items more frequently than slow moving items.
- Materials can be grouped together into various cycle counting categories (such as A,B,C,D).

4.4 Core Plant Maintenance processes

Order Management: Work orders in SAP support component planning. Stock items as well as non-stock items can be planned on work orders. Stock items create reservations instantly on saving work orders. Materials are issued to work orders from stock. if parts are not available in stock, system creates purchase requisitions. Purchase requisitions are created immediately on saving work orders for non-stock items. System offers functionality to create planned, unplanned and emergency work orders.

Refurbishment process: Refurbishment Order is a special type of work order that allows repairing of damaged parts in-house or through external vendors. Damaged part is refurbished and then put back in stock for consumption. This process is fully integrated into inventory, costing and MRP functions of SAP.

Serial number management: Spare parts can be tracked individually through serial number management functionality in SAP. Parts can be serialized at the time of material receipts, issue or during stock transfers. Serialization also helps in tracking warranty on parts. vendors can be made accountable for parts that fail prematurely through this functionality.

5.0 Key Metrics

Here are a few key performance indicators that provide analysis on effectiveness of spare parts management:

Equipment efficiency: Percentage of the number of maintenance labor hours spent on an equipment vs equipment operating time.

Maintenance effectiveness: Operating time / (operating time + downtime for maintenance ) as a percentage. Represents equipment availability from maintenance perspective.

Unplanned downtime %: Percentage of time equipment/facilities are not available for production due to maintenance requirements.

Maintenance cost %: Equipment/facility maintenance cost as a percentage of manufacturing controllable costs.

MTTR: Mean time to repair equipment and facilities for a defined unit of measure such as operating hours, number of batch runs, etc.

MTTF: Average interval of time between failures of equipment and facilities for a defined unit of measure such as operating hours, number of batch runs etc.

Hello Folks,

Thought of sharing below logic of getting Maintenance order number from Permit number. Refer attachment for logic and code.

Regards,

Nikhil Kulkarni

PEOL Technologies Pvt Limited, Bangalore India.

Introduction

The way several features including coding in Extras of Infoset takes the work closer to an ABAP development, another function Alias in the Table-join screen also increases the versatility of an Infoset (SQ02) or a Quick View (SQVI)

Objective:

To understand the concept of Alias Tables in Infosets and Quick Views, through a Demo application.

Demo Situation:

We have a task of developing, a report through Infoset or a Quick View, to display Notification details and corresponding Object part and Damage Codes details.

So the ALV we need will have these columns:

Let’s see how we do it.

Obviously the two tables we need are:

VIQMEL - For Notification Details
VIQMFE - For Object Part, Damage Details.

But

In VIQMFE table, we do not have the Code texts (field name kurztext). These fields are shown in Red in the 1^st picture. QPCT is the table we need to join to get this field value. Let’s take this into our join.

Then, What’s the problem ?

As per the join shown above we are getting kurztext (Damage Code Text) for Damage Code (FECOD) only.

What about the kurztext for Object Part Code(oteil).

To get this too, we need to have one more QPCT table into the join. But system does not allow this.

So what do we do?

Here comes the use of the Alias Table.

We now need to create an alias table identical to QPCT (say QPCT1)

Follow the steps shown in the picture.

Now you have the desired table for you. Take this table too into the join.

Remember, system can not propose the right links for the join. You need to know this and Join Manually.

All done regarding the Alias Table.

Now you have your Selection-screen and List fields in QuickView (in case of Infoset make the Query through SQ01).

The Result is:

We find here the desired output with Code Texts also filled.

NOTE:

This is a simple case to demo the Alias tables. This feature has a big advantage during complex works of Infoset / Quick View.

The absence of Extras facility in SQVI, makes this Alias feature more relevant to a Quick View work.

In infoset, this Alias feature can be substituted by Extras Add Table, Add field and Code functionalities.

Hope Infoset / Quick Viewer users find this useful.

The environment of this document is ECC6.0 no EHPs.

Readers might be interested in these posts also:

10 Useful Tips on Infoset Queries

Infoset Queries: Collection of important posts

Thank you

Jogeswara Rao K

ABSTRACT

SAP offers the use of IBIP supported objects from within the LSMW to support data transfer.

This abstract explore the "old" option to run transaction IBIP directly with pre made flat files that matches to the IBIP structures and hierarchy ,the Excel IBIP tool can be usesd as an alternative to LSMW

The Tool includes Demo templates are available to Downloadhere

BENEFITS

Authorizations- if your requirement is provide simple excel based tool for the end user for master data management and LSMW authorization in the PRD system is not an option

Fast and Simple - Use 1 Excel source file also for multi structures ,in the IBIP Tool there is no need to link between the files using key relations between the structures ( Using IDENT1 , IDENT2 etc..) as required by LSMW approach , The Flat file records are written to the flat file based on the location sequence of the structure in the Excel template.

Scheduleruns at night Jobs - by splitting the flat file to several flat files we can use the IBIP program to upload the data in a schedule job which includes also the option to define in advance on which servers the scheduled jobs will be executed for load balancing purpose and also achieve "parallel processing" functionality which speed up data upload , This approach is very helpful when dealing with mass master data update , For exemple if several millions of records can be completed over night (depends on the number of servers in the PRD system ) using this approach .

Exemples for such changes for Functional locations or equipments :

- Mass update class and characteristic

- Mass update of system profile

- Mass update of the Address data ( using structure IBIPBDCD)

Templates examples

Exemple 1 :Create Equipment with user status

Exemple 2 :Create Equipment with class and characteristics

Exemple 3 :General Task list with operation and assignment to maintenance packages

Pre requirement

Microsoft excel 2007- 2013
Macro enabled

STEP A - Prepare template - Select the required structuresand required fields

Selected multi radio button
Select structure IBIPEQUI
Select the required fields from the IBIPEQUI structure
Select structure IBIPSTAT
Select all the fields from this structure IBIPSTAT

1. Open the add in file

2 .Select IE01– Create equipment in the transaction combo box

3. Select the IBIPEQUI structure in the data structure listbox

5. Double click the IBIPSTAT structure which holds the user status data

STEP B - Fill Excel source / template worksheet

STEP C - Generate The Flat File for IBIP Transaction

The flat file will Automatically created ( stored in the temp folder )

Step D - Upload the Flat File to the IBIP transaction

. Select the created file from the flat file selected folder and press in the IBIP transaction

Step E ( Optional ) store the files in the Application server

Another alternative is to store the flat files at the application server which is mostly required when the data migration duration takes
more then several hours and it is required to schedule the run at night (when system load is low) , in this case :

Goto sm51 select the required server

Goto to transaction CG3Z and upload the flat file to the current application server

3.Select the application server which the file was uploaded into and select the Phys. file and press on "Execute"

Step F : Check the Log

Lets Check and confirm that the equipment 10006947 created is created with the "0005" status which as displayed in the excel row 4

We can see the result : the equipment 10006947 was created with user status "0005"

Exemple 2: Equipment creation with class and characteristics

1 Goto transaction IBIP – press the information icon to see Structure hierarchy , So you can know which structures are required to your business scenario

3. Now –with the IBIP Tool Create template using structures IBIPEQUI , IBIPCLAS , IBIPFEAT

(Unhide row 1-2 to view selected structures and fields technical names)

4.Upload the Flat File to the IBIP transaction

5. Let’s Check and see that the equipment created 200860 was created with the required class and characteristics per the data in
the excel rows 4 -6

Exemple 3: Functional Location assign class and update characteristics values

Introduction

Agencies with different expertise are usually involved in the upkeep/maintenance of these assets such as

-Mechanical Maintenance

-Electrical Maintenance

-Instrumentation

-Air Conditioning

All these agencies record their jobs through Notifications and Maintenance Orders on their respective equipments

of this Equipment tree (Structure).

So far we are discussing about the Maintenance Agencies owned by the the Shop.

The constraint to provide them the IH01 tree, displaying only their Equipments, is that all these equipments have planner groups filled with those of the agencies owned by Shop.

The present topic is about this situation.

Objective

Need to give a Customized IH01 Structure to these Central Service agencies, using a field other than the Planner Group.

(Because the Planner Group field is already consumed by maintenance agencies owned by shop)

How?

Here Comes the idea of using the I_BEGRPAuthorization Object.

That is, uUsing the Authorization Group field in Equipment Master.

Let's see a sample structure shown below.

Now suppose the Equipment to Agency relation in each branch (Pusher) is as under:

Assets	Shop's Own Agncies	Central Agencies
First two equipments	Mechanical	User1
Next two equipments	Electrical	User2
Fifth Equipment	Instrumentation	User3
Sixth Equipment	Airconditioning	User4

As said before the objective is to restrict the display to their respective equipment.

Create Authorization Groups for these Central Agencies in SPRO

Now go to ‘Change Equipment Master’ (IE02) of each of these equipments, give the respective authorization group values and save, as shown below.

Then

Create 4 Roles (One each for these 4 agencies) through PFCG or modify existing Roles as under:

Shown below is the role for AGR1 Mechanical Maintenance Agency

Assign these Roles to the respective Users.

Now when the user1 (Centralised Mechanical services) goes to the Structure (IH01) the following is the tree he will be seeing.

(Only those 2 of his jurisdiction)

Similarly, when the user2 (Centralised Electrical services) goes to the Structure, he will be seeing…

….. So on for other users.

Now an exapmle of the real application of this feature

There is an Enterprise having about 60 shops (departments). The structure here has thousands of functional locations, lakhs of equipments and many hundred Planner groups.

Here comes the use of controlling the structure display though an object other than a planner group.

Pictorial depiction of required equipments in the structure.

Important Note:

Hope this knowledge piece is of relevance to some of the members.

Thank you

Jogeswara Rao K

Introduction

Many of us are aware that Breakdowns leading to Production losses draw attention of Senior Management as well as QMS audit people. Very frequently asked question by these authorities is What is the Root Cause? Also Many of us know about a very common and effective approach to reach at this Root Cause is through the method of asking Why 5 times. (5-Why method). It is said that by receiving answer to the 5th Why on the Breakdown reason, we would be arriving at the Root Cause. (It is quite possible that we arrive at Root Cause well before answering the 5th Why.)

Objective

We are discussing in this document about an idea implemented to map this process of Root Cause Analysis, making use of Catalogs & Codes. We will be able to show to the Authorities, the Root Cause Analysis done on vital breakdowns.

Here we see how to go about it

Preparation

Make few Code-Groups and Codes as under through Tcode QS41 (and Transport to other clients)

Root Cause Analysis

For demonstration, we have taken a simple case of EME vehicle not starting, on which we had already created a Malfunction Notification. See this Graphic to understand the 5-Why Analysis.

Now let's do it in the system with the help of the codes created above. Go to the Catalogs & Codes Tab of this Notification, give the Object part and Damage details and enter the Causes Tab page. See the picture how we used the above codes to perform 5-Why analysis .

So theRoot Cause we have Arrived at is Training not Given. Note: If needed, you can write long-texts against each code-Text.

Now Go to Activities tab and record this way:

Here too Long texts can be used.

All done.

Now we can show the Authorities, the Analysis we do on vital Breakdowns.

Further, to show it in an impressive Lay-out, and system generated PDF formats, we can go for a Smartform as I opted for (shown below)

I need not explain the picture above, it is self-explanatory. This Samrtform was integrated to custom reports of Breakdown Analysis When clicked on a CAPA cell against a Notification, system presents you the above screen.

Note:

The coding part (QS41), will be customized by Readers as per their situation. Bottom line is how we map the 5-Why process using the SAP objects. Hope this share will be useful to members.

Thank you

KJogeswaraRao

Introduction:

After the exposure to many standard ALV reports for masterdata , it is seen that the clients or end-users expect similar reports for Catalog-Profiles, Code Groups and Codes, so that it will be easier to search for such available profiles which suit to their requirements and they can make use of the same, saving lot of time, effort and data duplication.

For big organizations, comprising of several units where SAP-PM is adopted, this requirement is very common.

We do not have such ready report/s provided by SAP. At the same time, SAP has given good tools for Functional persons to generate reports on their own.

These are Quick viewer, and Infoset Queries.Present article is based on Infoset Query.

Let's see what we are going to achieve in this article:

A report with selection screen like this

will generate a report like this: (list of all profiles related to 'Motors')

DO you find it is relevant and useful to you? Then here is how to make it !

Step 1. Create an Infoset as follows

- Create an infoset (Say 'CATCODES') using 'SQ02' Tcode. opting for Table-Join in the initial screen.

- In the Join page Insert these tables as shown ( select left-outer-join for QPGR and QPCD tables join)

- Click Back,

- Select the required fields from tables (left) to the Field Groups in the right. (Drag & Drop) as shown here.

In order to arrange the Calatogs in the sort order of B, C, 5, 2, A in the ALV screen, a user defined field 'SORT' is being created in the following section.

For this click on the 'Extras' tab on the application toolbar to have Extras window on the right.

Click on the 'New' icon and create 'Additional Field' named 'SORT'

The specification of field 'SORT' while creating

Now, keep cursor on the 'SORT' field (Red Boxed area) and click on the 'CODE' icon (Green box), and write the following code.

Save the code,

Making of 'Selection screen' of the report

Go to 'Selections' tab (next to 'Extras' tab) and create the select-option.

Here we are creating the 2 selection fields shown in the 1st image of this document. i.e., Catalog Profile' and 'Created By'.

For this click on 'New' icon in this tab and create two selection fields 'CATPROF' and 'CRTDBY' one after one as shown here.

Now the 'Selections' tab will look like this.

Save and Generate the Infoset.

This completes the job in Infoset creation (SQ02).

Come to initial screen of SQ02 and assign this infoset to your usergroup. (User group is created through SQ03)

Step 2. Create Infoset-Query through SQ01 as follows.

Create a Query (say 'CATCODES') using the infoset made above 'CATCODES'.

Click 'Next' arrow

Select all the 3 tables appearing here used in Infoset and click next.

Select the fields required for display in ALV.

Click on Basic List button and arrive at the following screen.

(If this screen does not appear go to 'Settings' menu, check the 'Graphical Menu Painter' option in the 'Settings' option)

The red box list shows the Field selections you need to appear in the output.

For column coloring you have to drag & Drop colors from tool box to the corresponding field as shown by the Red arrow on the right.

That's all. Now You save the query and return to the initial screen. Execute and test.

To have a Tcode for the program you've just generated

In the SQ01 screen

to get this result.

Copy this string (Report name), Run SE93 in Development Client and create a Z-Tcode with desired name using the above program name.

Transport the request to Production.

Now the report you've made is operated using the Tcode you've created.

To my end-users, this report was very much sought and proved very useful by them. They can now easily search the profiles available in the system (made by users in other shops) for their similar equipments. This report has got many such uses.

The making of this report here has been demonstrated using 'Standard Client 'option in the SQ02 (Environment --> Query Areas), so that no transport needs to be done during creation or modifications. However as explained, the Z-Tcode has to be created in Workbench Dev Client, once.

Also, it is aimed through this document, the beginners in the Infoset query area to be benefited without referring to other detailed documents on SQ03, SQ02, SQ01.

Hoping it is useful to many.

-Jogeswara Rao K

Introduction :

Equipment & Tools Management ( previously knows as Construction Equipment Management until release 4.6C2) For ETM component minimum EHP4 + DIMP switch framework is required.

Why do we need ETM ( Equipment & Tools Management) ?

To perform the consolidated planning, processing, settlement, evaluation of resources.

Where does ETM is applicable & mostly useful?

Self performing construction companies.

What are the benefits of using ETM?

Improved availability and tracking of equipment
Manage the increasing administrative workload
Reduce handling and administration cost
Introduce most flexible prices and account determination
Optimize equipment utilization
Improve the visibility of profitability, TCO and return on asset and equipment

What are Key Process of ETM?

Time-based Equipment Process
Time-based Equipment Process including 3rd Party Rental Equipment
Performance Based Equipment Process
Non-Consumable Material Process
Consumable Material Process

Business Functions required to be activated in your system

First of all you need to activate business function DIMP_SDUD using transaction SFW5. Once you activate , a background job SFW_ACTIVATE_SF0X will start. Once your background job is over, an ETM node wil be available in your IMG path under Logistics general node.

Configurations steps :

Pre-requisites Org structure components : Controlling Area, Company code, Sales Organization, Distribution channel, Division & Plant should already be available.

Basic Settings :

1) Consolidated Mapping Category and Settlement Dates

Menu Path : Logistics - General - Equipment and Tools Management (ETM) - Basic Settings - Consolidated Mapping Category and Settlement Dates

2) Sales Area per Company Code/Business Area/Plant

You need to perform cross-company operations & settlement settings here based on your business requirement. No settings are required here if you use internal activity settlement.

Menu Path : Logistics - General - Equipment and Tools Management (ETM) - Basic Settings - Sales Area per Company Code/Business Area/Plant

Master Data:

1) Maintain Equipment Category View and Processing

Menu Path : Logistics - General - Equipment and Tools Management (ETM) - Master Data - Equipment - Maintain Equipment Category View and Processing

2) Define Equipment Types ( Technical object types)

Menu Path : Logistics - General - Equipment and Tools Management (ETM) - Master Data - Equipment - Define Equipment Types

3) Proposal for Each Equipment Type

Pre-requiste : You need to maintain an entry of Owner & Administrators in the table J_3GV_EIVE.

Menu Path : Logistics - General - Equipment and Tools Management (ETM) - Master Data - Equipment - Proposal for Each Equipment Type

Note, your settings in above screen should vary based on your business requirement

4) Allowed Material Types

Menu Path : Logistics - General - Equipment and Tools Management (ETM) - Master Data - Materials- Allowed Material Types

4) Maintain Recipient Types

Menu Path : Logistics - General - Equipment and Tools Management (ETM) - Master Data - Recipient - Maintain Recipient Types

5) Determine Planning Areas

Menu Path : Logistics - General - Equipment and Tools Management (ETM) - Master Data - Recipient - Determine Planning Areas

This basic configuration may vary according to usability & scope of requirement. Will focus more light on ETM Functions & Operations in Part 2 of this ETM document.

Thanks & Regards,

Amol

Introduction

One of the very frequently asked questions in this space, is about the subject matter, i.e., How can I add Custom fields to a Notification? A documentation on this subject would be helpful to the forum for ready reference.

Objective

This documentation is intended to enable the readers to create the Custom fields in different tabs of Maintenance Notification, update the Noyification Master data Table and also display these fields in IW28 / IW29 output.

Let's see how it is done.

Part1

Create Custom fields in the Notification Table

The table of our context is QMEL. We need to append our Z-fields to this through the include structure namely CI_QMEL.

The process of creating any custom field starts with creating a Data Element with desired Type and Length or with desired Domain name and with the Field Labels we want to have for the Customer fields. For our Demo, we have created Two Data Elements, namely :

Z_DELAY - Type DEC Len 3 Dec 1 and Field Label ‘Delay(H)’
Z_REASON - Domain TXT40 and Field Label ‘Reason for Delay’)

Now let us create our Customer fields.

Run Tcode SE11 --> give value QMEL in the Database Table field --> Click on Display. Scroll-down to find include tableCI_QMEL. Double click on this, Go to Change mode and Add Two new fields of our interest as shown in the picture and Activate.

As seen in the picture, we have created Two Customer-Fields namely ZZDELAY and ZZREASON. It is essential for all Customer fields used in Enhancement purposes to be prefixed with ZZ.

Part2

Enhancement and Screen-Exit

1, Create an Enhancement Project say ZPMNOT using Tcode CMOD.

2. Assign Enhancement QQMA0001 to this project .

3. Click on Components in the picture above to reach this screen.

4. Activate by clicking on the Activate Icon (shown in picture above)

Now the screen is like this.

As we see here, there are several screen-exits (27) and Two Function-Exits namely EXIT_SAPMIWO0_008 and EXIT_SAPMIWO0_009 in this enhancement.

Double Click on this screen number to create a Sub-Screen for holding our Custom Fields. You’ll get this pop-up. Press Enter and Continue.

You’re in the screen below, where you’ll give a Description, Select the Subscreen Radio button, Save and Activate.

Click on Layout Arrow in the Application Toolbar of (See the picture above) to reach the Screen-Painter pop-up window, where we will be creating :

A Box to hold our Z-fields
Text Fields to for Z-field labels
Input Fields for Z-fields

The input fields should be referred to the Dictionary fields we have just created. (QMEL-ZZDELAY and QMEL-ZZREASON) as shown above.

Activate the screen-painter.

Part3

Codes to be given in Function-Exits

Go to the following screen

Double click on the Function-Exit EXIT_SAPMIWO0_008 and

put the following code in the include ZXQQMU07 .

*---------------------------------------------------------------------------------------------

TABLES: QMEL.

MOVE-CORRESPONDING I_VIQMEL TO QMEL.

*---------------------------------------------------------------------------------------------

Similarly put the following code in the include ZXQQMU08 of the Function-Exit EXIT_SAPMIWO0_009.

*---------------------------------------------------------------------------------------------

E_VIQMEL-ZZDELAY = QMEL-ZZDELAY.

E_VIQMEL-ZZREASON = QMEL-ZZREASON.
*---------------------------------------------------------------------------------------------

Part4

SPRO setting to be done

Navigate to the Overview of Notification Type in SPRO.

Select your Notification Type (Here we are doing it in M2) and Enter the Screen Structure for Extended view

Give the following settings in the Malfunction Tab (the tab where we want to have our custom fields)

Please note that the custom screen should be the last i.e., below all standard screen areas of the Tab. The reason for this can be understood in this discussion. ---> Blank Screen coming in Tcode IW21 after our custom screen area

Almost Done

Let’s see the effect of work done so far.

Create a Maintenance Notification (IW21). You will see the following addition of subscreen area in the Malfunction Start/End Tab.

Enhancement has been added here by the system, in which our Custom fields appear with their labels and the input fields.

Now let’s add some values in these fields and Save the Notification.

Run IW22, open the Notification and verify whether the values are updated to table or not. If they are appearing as you have entered and saved, this means the QMEL table has been updated with these values when Notification was saved.

Part5

Let's have these Custom fields in the Notification list reports namely the ALV of Tcode IW28/29 (QM10/QM11 in case of Quality Notifications)

So far we have succeeded in creating our Custom fields and updating the values to the Notification Master data. Next natural requirement of a user would be to have these fields in IW28/29 ALV screen. For this purpose we, need to create an Append Structure in the Structure RIHQMEL_LIST (RQMQMEL1 in case of QM10/QM11 reports), as shown in the picture below. The Tcode is SE11 again for this task. Here we have created an Append Structure named ZDLAY and in this structure we have added both the Custom fields.

Now let's create few more Notifications, with custom fields filled with some values. Now run IW28 with selection parameters to display these Notifications we created. Click on the icon shown , You'd find the Custom fields in the Column-set list, Bring them to Displayed list on the Right hand side.

Related SAP Note: 370191 (Image of the note is attached herewith for the benefit of the members who can not access OSS)

Part6

Now if you go to IW23 of any of these Notifications, unlike all other greyed-out fields, the Custom fields will be seen Editable. Though there is no provision to Save the edits here, you’d definitely like to have these fields too in Greyed-out mode.

For this we need to write a small code in the PBO (Process Before Output) module of the screen 0103 we have created. Double click on the Screen number 0103 of the enhancement,

Un-comment line MODULE STATUS_103. and D’Click on the STATUS_0103 of the PBO module. Insert the following code between the MODULE, END MODULE lines like this.

------------------------------------------------------------------------------------------------------------------------

MODULE STATUS_0103 OUTPUT.

IF SY-TCODE = 'IW23'.

LOOP AT SCREEN.

SCREEN-INPUT = '0'.

MODIFY SCREEN.

ENDLOOP.

ENDIF.

ENDMODULE.

-------------------------------------------------------------------------------------------------------------------------

Lastly Rememebr to
Activate the Function GroupXQQM from Tcode SE80. Right click on the Function Group and click on the Activate option

...... and thus we reach to the end of this knowledge sharing Documentation.

Note

1. As this is largely a Technical job, it is recommended to be developed through an experienced ABAPer, especially Part1 which involves Activating the Standard table QMEL.

2. The Environment of Author is ECC 6.0 with no EHPs, hence the document applicability.

Expecting this document too would be of use to many members from mainly from EAM and QM spaces.

*Author's other Posts

Thank you

KJogeswaraRao

Business scenario :

While working with globalization concept in SAP EAM, it so happens that multiple plants are being served by single planning plant. Maintenance planner work in different timezone. In such cases it is required to have time zone functionality active for your system.

System time zone : Time zone which is application for a client. STZAC is the transaction where you can change system time zone. It is not at all advised to change this time zone as it takes effect across the client.

User Time zone : This is defined for a user in SU01 OR SU3 in Personal time zone under Default tab.

How does SAP system determines objects Time zone ?

Please refer below link for system behavior on determination of time zone for objects in SAP e.g. Notification/Work Order.

Determination of an Object's Time Zone - Time Zones (BC-SRV-TIM) - SAP Library

EAM Specific Behavior while working in Different Time zones without activation of Time zone functionality.

Even if you maintain your user time zone in SU3, system will fetch client level time zone in following cases.

System behavior when you update personal time zone. Log off & Login.

Create Notification - personal time zone will reflect on notification reference time, malfunction start time etc. After creation if you check administrator data, you will see creation time in system time zone settings. But action log will be with reference to system time zone.

Create Order - Same as above. When you do TECO, pop-up for confirmation will have reference time as per your system time zone. Action log is with reference to system time zone.

Create confirmation - confirmation dates & time will be referring system time zone.

Measuring document - creation date & time will be referring to System time zone.

Solution

In order to overcome, we need to activate LOG_EAM_TZS_1 business function. You can get more information about this on below link.

Enterprise Asset Management: Time Zone Support - Business Functions (SAP Enhancement Package 4 for SAP ERP 6.0) - SAP Li…

Activating business function LOG_EAM_TZS_1

1) When you activate this business function, a background job SFW_ACTIVATE_SF0X will be started.

2) Once background job is finished, you need to go to following configuration path to activate time zones.

Plant Maintenance and Customer Service - Maintenance and Service Processing - Basic Settings - Activate Time Zone Support for Application Areas

3) Once your settings are maintained, you can check Notification, work order, measuring documents, order confirmation transactions. You will observe following changes.

On transaction screens, you will find a button activated for Time zones as shown in below image.

If you click on Button highlighted in above screen, You will get following screen.

On above screen you can see different time zones.

Personal Time zone - Its default picking up from SU3 settings.

Reference time zone - Its a time zone which will be valid for the transaction that you are going to process. IF you are creating a breakdown notification for a plant which falls under different time zone ( e.g. UTC-2).

Session time zone : Same as above, but only difference is this time zone is valid for full session ( from login to Logoff)

Reference time zone = Personal time zone If session time zone is not maintained.

System Behavior after activation

Notification & Order - User time zone settings will be reflected. Except action log. But if you check administrative data, you will see creation time referring to user time zone from SU3.

Order TECO pop-up - Here reference time will according to User time zone. ( My user time zone is UTC- 5& system time zone is UTC+8)

Time confirmation - According to user time zone

Measuring document - according to user time zone.

All action logs & Change documents will be still referring to System time zone only.

Please refer Time Zone Support - Measuring Points and Counters (CS-IB-MC / PM-EQM-SF-MPC) - SAP Library for functions which are not supported by Time zone business functions

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Best Regards,

Amol Khairnar

Hi All,

I got this opportunity to share to an recent query on "How to make field optional"

In location tab of PM work order ,we have field selection for settlement order as shown below and which has to be made optional.

In above screen settlement order field has to be made optional

Step-1

Using OIAZ, go to field selection screen as shown below

Step-2

click on influencing button

Step-3

select order type and click on display

select input R.button and than save.

Step-4

Go to location tab in work order as shown below

In above image , you can see settlement field optional.

Regards,

PS R

This document was generated from the following discussion: How to make a field optional ?

Why do we need Work clearance management?

Maintenance crews generally work in hazardous environment ( E.g. High voltage, radiation exposure). There are some work related illness which requires special health and safety measures. SAP WCM enables you t control and monitor these activities. This means you are able to ensure safe and secure working conditions for maintenance crew, observe environmental regulations and guarantee technical system availability.

WCM Terminologies

WCA - Work Clearance Application
WCD - Work Clearance Documents
WAP - Work Approval
WA - Other Work Applications ( Additional)

1) Work approvalis an Object in WCM which can have WCA linked to it. other Work applications (WA) including Hot work Approvals, Chemical environment approvals, Hazardous Gas approvals etc. Work approval links PM Maintenance Orders to WCA and other applications in an Enhanced WCM scenario. In a standard scenario, it is the WCA which links PM Order to WCD’s.

2) Work Clearance application (WCA) is a WCM Object which represents a Safety certificate in particular for Lockout/Tagout. It is used to control maintenance processing and groups together Operational WCD’s. A Work clearance Application can be assigned to several Operational WCD’s and vice versa.. In the Enhanced model (as configured), a WCA is used to control communication between work approvals and Operational WCD’s.

Work applications are additional specific work related certificates. For example Hot work application, Hazardous Chemical/Gas/Particulate work certificate etc. The Hot work application, for instance, is to protect a maintenance personnel from a hot working environment before entering the actual maintenance site.

3) Operational WCDis a WCM Object that is responsible for executing the Operational cycle. It would consist of 3 key phases namely Tagging phase, Temporary Untagging phase (To test when work has been done before making a system fully operational) and Untagging phase. In WCD we define Lockout/Tagout operations for Technical Objects which need to be isolated temporarily from Technical system.

Operational WCD should be assigned to WCA and its status will affect the status of WCA. Here the status of WCD will be transferred to the linked WCA. For example, once the Tagging operation is finished, the Tagged status will be assigned to WCD and transferred to WCA.

WCM Models & Process Flow

Process flow for Standard model, PM Order is linked to WCM Objects as below:

Work Order >> WCA >> WCD (Work Clearance documents- Linked to WCA)

Process flow for Enhanced model, PM Order is linked to WCM Objects as below:

Work Order >> WAP (Work Approval) >> WCA & WA >> WCD (Work Clearance documents- Linked to WCA)

In following document we will get into step by step process for Standard Model followed by Enhanced model.

Thanks

Amol

Foreword:

The Original post was relevant non-EHP version of ECC6.0,
Users in EHP environment, should read the Notes by the author at the end of this post dated 10/06/2016.

Introduction:

The environment in which the present subject is being discussed is that, where Large Machine installations like Furnaces, Cranes etc have been mapped as Functional Locations and the Equipments hierarchy follows under them.

The author, in the past had posted a document on the subject matter Equipment Availability - Concept & Issues. As defined in this document the usual method of deriving Equipment Availability through MTBR, MTTR parameters is by the formula:

Everything was OK until we see the Equipments in isolation. It did not take longer for the Audit persons to reach the Logic that in an Enterprise Structure, if an Equipment undergoes breakdown, the Functional Location also goes inoperative. M2 Notifications are recorded on the Equipments but its effect impacts the hierarchy, finally affecting the bigger machine i.e., the Functional Location in our case.

The Audit demand was that the Equipment Availability figures be made available at the Functional Locations level, even when no direct M2 notifications are created on them.

Naturally, we approached OSS. The recommendation was in the form of implementing an SAP note namely 1074845, but with conditions like no further software support would be provided in relation to this. This is relevant to Functional Location-Equipment Hierarchy only, not to Equipment-Equipment Hierarchy. Meaning that, the MTTR, MTBR vales will be collected to Functional Locations only, but not to Superior-Ord Equipments.

Objective:

So the objective of this document is to compute Nodal Equipment Availability on Functional Locations as explained above.

Let’s see how we do it !

Readers might by now have understood that by implementing the said SAP note, SAP will be providing the collective MTTR, MTBR values on the Functional Locations. Using these values our requirement of Calculating the Availability values can be easily done through formula given above.

Step1 (Implement the SAP note)

Steps suggested in SAP note 1074845 were implemented by BASIS people.

Important: The nodal MTTR, MTBR computation effect in the report MCJC would be seen with a condition that atleast One M2 Notification is created directly on this Functional Location. (This was the pre-requisite SAP informed us). Also we saw this. Until no M2 Notification is created on the immediate F/Locn, the MCJC report was coming blank inspite of several M2 Notifications exist on the hierarchy Equipments under this F/Locn. The moment we created one M2 Notification on the Big machine (F/Locn), the MCJC report showed the computed figures of hierarchical MTTR, MTBR values..

Step2 (Cross-check the impact of SAP note)

We manually checked the correctness of the collective values of MTTR, MTBR on the Functional Location through MCJC, by deriving from the individual Equipment values of MCJB. We confirmed that the things are accurate.

Note:

Here I want to share one information with the readers. Few might be wondering that this requirement can be well addressed by a simple development. Even I too tried this. Such development would be very complex because, taking care of Breakdown Duration Overlaps of Equipments under a Functional Location would be very complicated and so a less reliable code would be an outcome if developed locally. The same thing comes from Standard through this SAP-note in an accurate way.

Step3 (If required increase update frequency of S070 info-structure)

While testing we realized that the info-structure S070 (responsible for MCJC report) updates monthly (OMOS setting). So, to suit our requirement, we developed a simple program to update S070 (Calling Tcodes OLPM and OLIX in the code) and scheduled it to run daily (Initially we were updating 12Hrly but later modified for Daily updating).

Step4 (Develop a program to compute the Equipment Availability)

A simple program using table S070 (for periodical MTBR and MTTR values of the Functional Location) has been developed which calculates the Equipment Availability (in our case the Functional Location) using the formula given in the beginning.

Selection-screen

ALV Output

Note:

This is to reiterate that SAP did not give any solutions to compute similar calculations on SuperiorOrd Equipments in relation to the sub-equipments. Also, these collective computations are valid on the immediate Functional Locations above the Equipment hierarchy. So starting with the Equipments which need these collective MTTR/MTBR computations, we had to modify our structures to suit the present situation .

(Hoping that Readers will be able to distinguish the use of word Equipment in this article, sometimes it meant as an SAP object and at other it has general Equipment meaning)

...and I feel here too it is important for me to mention the version of my system where all these exercises were to be done. It is ECC6.0 no EHPs.

Hope members find this article useful.

10/06/2016:

The above was posted on the basis of ECC6.0 EHP0 version.
When we upgraded to EHP7, we saw the effect of the Note discussed above disappeared and the story repeats. We reported an incident to OSS.
SAP gave us a solution through a Note relevant to present version. The note is: 2327193
We applied this note and restored the Hierarchical MTTR / MTBR values on the F/Locans as discussed in the post above.

10/06/2016:

My recent post on related topic: Rebuild PM Infostructures (LIS)

Thank you

KJogeswaraRao

Introduction

The first usual improvisation requirement in self-made Infoset Queries by beginners, is often the requirement of calling other reports from ALV output, just the same way we do in Standard reports. In ABAP-coded Z Report Programs, there are several techniques of achieving this by syntax like Call Transaction,Submit etc.

The very objective of this documentation is to achieve the same. This topic was briefly discussed in the document 10 Useful Tips on Infoset Queries. But, when the author experienced few exceptions in the technique suggested there and found a solution subsequently, he got the idea of having an exclusive document on this topic.

This document has assumption that readers have working knowledge in developing Infoset Queries.

Here we Start

We have seen earlier, that for enabling Report Calling from the ALV output of an Infoset Query, we need to do these steps in SQ01.

Note: If your Report Assignment option is found disabled, then the reason and setting to restore is here: How to make 'Report assignment' available in 'SQ01'

Click here on then on then select TR (Transaction Code) or RT (Report Program),

When we select TR we need to put only the Transition code.

Example:

IE03 if our ALV lines are having Equipment field and we want Equipment Master display upon clicking on the ALV row.

If we have a Maintenance Order Number in the ALV, and we want to have Display Order Screen upon clicking on this row, then we give the Tcode IW33 here.

2. In the other case, when we want to call List Reports like IW37 , then we need to select RT in the Report type, where we need to give the

Program name (in this case RIAFVC20) in the Report field and the variant name.

So far, it looked very much OK, until I found recently that few field names like EQUNR, MATNR, DOKNR etc, do not exhibit the desired behaviour.

Few cases where this call report was not working are discussed here.

In one of my Queries, I have Material number (MATNR) in the ALV output, for which I used Report Type TR with Tcode MM03, for the purpose of Material Master Display. What happened here, was no Material number was passing to the MM03 initial screen, so the display interrupted, In another case, the first attempt display was coming, but the next attempt on different material line in the ALV, the material master display of the first attempt was repeating. Broadly there is a technical problem in passing the Material number.

Another such case was with the Tcode CV03N (Display of DMS Document) , where the DOKNR, DOKAR field values were not passing to the CV03N initial screen.

Here is the solution I worked-out, using the QUReport Type of Report Assignment

We are taking the MM03 case

As mentioned above, the report Type QU (Query), in the Report Assignment came to rescue.

This option has 3 fields.

First field (User Group): You know, your User Group.

Second field (Query): We need to develop a simple query for this field.

Third field (Variant): Optional.

So, what required was that a simple Infoset query using MARA table (Material Master) to be created.

And this Query name, was given in the field 2 above.

Let’s see the steps of creating the simple Query for Report Assignment purpose.

SQ02

We are Creating an Infoset (I named it MM03) with Direct read of table option.

This is because, we use only one table.

Select this default option, and Continue.

With this the Key field MATNR is added to the Field Group folder in the Infoset.

And in the Infoset Code Section, give the following code

Generate Infoset and do not forget to assign it to your User Group.

SQ01

Create a Query (Say MM03) using the above Infoset.

Note:

This query name is going to be used in the Report Assignment.

Go to Basic list screen and Tick the MATNR field in the List fields column.

Save the Query.

Testing.

Here we are examining, the behaviour of 3 cases of Report Assignment) in the ALV output of an Infoset Query.

We know that when multiple Call report assignments are there in the query, then the options appear as a menu as shown above, upon clicking on a row.

Here the first option in the menu namely Display PM Order, is that where I used report type TR and given Tcode IW33,
Second one, namely Report Assignment MM03 is through Report Type QU with Query field value MM03 (created as explained above)
Third one was the option which was malfunctioning i.e., Report Type TR and Tcode MM03

Now when tested, the first option with TR report-typeworks satisfactorily, without any problem, passing the Order number (AUFNR) correctly everytime.

The third option, again with report type TR works erratically, unable to pass material number (MATNR) correctly.

The second option is our solution to the erratic behaviour of MM03 through TR report type. i.e., through QU report type. This works very correctly like the first case.

In the case of Display Equipment (IE03) , the above method would work, with the following code in SQ02.

PARAMETERS:
EQUNR LIKE EQUI-EQUNR.
SET PARAMETER ID 'EQN' FIELD EQUNR.
CALL TRANSACTION 'IE03' AND SKIP FIRST SCREEN.
EXIT.

So that is about the Problems and the Solutions

As referred in the beginning, another parameter which gave trouble in calling reports through report-type TR was, DOKNR (DMS document number).

I have solved this issue too in a similar manner. The transaction called was CV03N. The code used in the Infoset is given below.

Note

See the Syntax used PARAMETER ID in the syntax used in both the cases above.

The Parameter Id used in MM03 case was, MAT, and in the CV03N case was CV1 and CV2.

MAT is the Parameter Id for field MATNR, CV1 is for DOKNR and CV2 is for DOKAR.

This parameter-id is the key factor for any Call report to function properly.

Where do we get this?

For example for MATNR, place cursor in MATNR field of any screen, and press F1 on key-board. The pop-up has this value.

Similarly for any other field.

That’s everything I think, about this document.

The author hopes that this document also will be useful to the members, the way the other documents by the author, in the series of Infoset-queries.

Thank you

Jogeswara Rao K

05/11/2015:

A tip in this context of Report Assignment.

Recently I made 3 ALV reports using Query for Equipment, Functional Location and Material BOMs . And then I was trying to use Report Assignment in the SQ01 of Equipment BOM. i.e., I was trying to call ALV report of Material BOM, when we click on the Component material field of Equipment BOM ALV. My issue was it was not taking to that report. I analyzed the reason to be:The BOM Component field (IDNRK) does not have a ParameterId on which the Report Assignment function depends.

What I did:

I created a user field MATNR in the Infoset Query by giving data type MARA-MATNR which has a Parameter Id MAT, and then equated that to BOM component (IDNRK) field. Means I gave code in the Code area of this user-field MATNR as: MATNR = STPO-IDNRK.

Then I took this user-field to SQ01 and then to List fields (ALV). Now I thought that the ALV has PID, and the Report Assignment would work. But it was not working. Then I realized the reason to be that as long as IDNRK field is there in ALV it would not work. I removed the IDNRK field from ALV. I already have the values of BOM component material values in my user-field MATNR. But then I had to remove the text field also associated with IDNRK field from the ALV. Now it worked. Now it is taking me to the Material BOM report assigned in the Report assignment when I click on any ALV line of the Equipment BOM, when that material has got a BOM of it own.

But I lost the Component Description field which I had to remove alongwith IDNRK field from the ALV. So what I did was I created another user-field MAKTX in SQ02 and in its code retrieved the Description field from MAKT table. ( Select single maktx from makt into maktx where matnr = stpo-idnrk.). Now I took this MAKTX field also to SQ01 and then to List. So I got back the lost fields also and finally made the Report assignment to work.

Again with a view not to lose this information by memory erosion and for the benefit oft he forum I'm preserving here.

Regards

KJogeswaraRao

Introduction

As soon as I'm done with my step-by-step reply to a discussion on the subject matter recently, I realized that this long reply comprising of several Screen-captures possesses the characteristics of a Document. So I thought of converting it into a Document, so that members will be benefited from this frequently asked query.

Topic dealt here is for IP30 (program RSITRA20), but this method is valid for other programs too for background scheduling.

Here we see, how to do:

Step1. Create IP30 Variant.

- Run IP30,

- Give your Plan (here it is ABC123 ) in the Maintenance Plan field (Do not forget this step)

- Click Save Button and in the resulting screen give the Variant name,

- Optional:- Tick Only for Background Processing and Save again.

So we have just created a Variant named TEST for IP30 .

Note:

This variant will not be available for changes in IP30 Tcode, because 'Only for Background Processing' has been ticked.

For changes of this Variant, you need to Run SE38, give RISTRA20 in Program field, select Variants radio button, and then click on Display,

ClickF4 help in Variant field and click Change.

Step2. Create Background Job - Run Tcode SM36

Give Job Name and click Start Condition (See Picture)

A pop-up is displayed.

Follow the steps 1 to 7 given in Picture .

(Here it is assumed that you want the RISTRA20 program to run at midnights of everyday)

Click SAVE again

You will be given a pop-up.

Enter ABAP Program Name (Here it is RISTRA20) and the Variant (we know it is TEST), and SAVE.

(Steps 1,2,3 in the above picture)

You will be here:

Do not do anything, Click Back arrow and

SAVE

All Done

Now to see the schedule -

Run SM37 and Execute. (Give Current Date as FROM date and Date after 2 days as TO Date)

Execute to see a screen like this, where your Job is seen scheduled to be run at Midnight of Every Day. (According to the settings in picture 3 above)

During Scheduling, the Status changes from Released to Active andafter Scheduling it turns to Finished.

Hope members will be benefited by this post.

Thank you

Jogeswara Rao K

This document was generated from the discussion: Job Scheduling and activate for Maintenance Plans and modified to be a Document for general relevance.

Transaction Variant

Prepared By: Eslam Hosny

In This Document we will learn the concept & how to create Transaction and Screen Variants to change screen layouts.

And how to assign those transactions and screens variants to:

A Standard Transaction
A group of users
A new transaction

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Transaction Variants can simplify transaction runs as they allow you to:

Pre assign values to fields
Hide and change the 'ready for input' status of fields
Hide menu functions
Hide entire screens

A Transaction Variant is made up of a series of screen variants.

Screen variant contains field values and attributes for exactly one screen.

Transaction Code -> SHD0

The above Three Tabs in the T Code SHD0:

Transaction Variants – > Create Transaction Variants and assign Screen Variants
Screen Variants – > Create Screen Variants.
Standard Variants -> Used to assign Transaction Variants to standard transaction

Create and assign Variant Groups to specifics users

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Creating Transaction Variant from a Transaction (Transaction Variant TAB)

You can create the Screen Variant first (Screen Variant TAB)and then create Transaction Variant (Transaction Variant TAB)
Or create both at the same time (Transaction Variant TAB) -> Preferred

Our Below Example will be on T Code IW31 (Create Maintenance Order)

Once You Pressed Create, The System Will Call The T Code IW31
Fill all the required fields & Any Field you Want Then Press Enter

Once You Pressed Enter, The System Will Call A Configuration Screen That Represents The T Code IW31 In Forms Of Screens with its own Fields

W.Content: set the value you entered as default
Output Only: Dimmed
Invisible
Required: Mandatory

In Our Example

Then

Press Enter If you want to change the another available screen In The T Code IW31
Press Exit & Save If You Finished

Result -> Transaction Variant Created With Its Screen Variants

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Then You Can Test Your Transaction Variant

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Using the Transaction Variant You Have Created

Assign it to The Standard Transaction
Assign it to a group of users
Assign it to a new transaction (Variant Transaction)

1- Assign The Transaction Variant To The Standard Transaction (Standard Variants TAB)

If you assign the Transaction Variant to transaction IW31 the changes will affect all the users that use the transaction.

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

2- Assign The Transaction Variant To A Group Of Users (Standard Variants TAB)

Here We Create a Group (Variant Group)

A Transaction Variant Generated Automatic Once You Create The Variant Group
Then Assign Users To The Variant Group
Set Proposal : To Active The Variant To The user

Then Go To Transaction Variants TAB & Put The Transaction Variant Generated in the previous step With The group & Create it as normal transaction variant or Assign the Screen Variants to it

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

3- Assign The Variant To A New Transaction (Variant Transaction)

You Have Two Options:

A- In T Code SHD0, Then From Go To Menu -> Create Variant Transaction

B- From T Code SE93

We Will Work From T Code SE93

Then Save

You Can Now Use Your T Code

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Note:

You cannot activate more than one transaction variant to a standard transaction, only one

For example:

If you created two transaction variant from T Code MM01, and you need to assign the two variant to the standard T Code (MM01) -> You cannot, only one can be assigned

If you created two transaction variants for example from T code MM01, and you assigned one to the T Code MM01 & the other to a user(s)

So all the users will work with first (assigned to the T Code MM01) & The User(s) will work with the variant that is assigned to

You can assign to a group (User(s)) more than one variant -> but the these variants must be from different T Codes

-------------------------------------------------------------------------------------------------------------------------------------------

20/06/2016 by Jogeswara Rao Kavala

One more useful link on this subject:

Transaction Variant and Screen Variants by Kleyson Rios

-------------------------------------------------------------------------------------------------------------------------------------------------------------

IH01 Structure Customizing beyond I_INGRP Authorization Object

Introduction

Basic Questions that helps in PM implementation estimation

A glossary of dates fields on Service Order.

Equipment Task list Display Report by using SQVI

Spare Parts Management in SAP Plant Maintenance

Getting Maintenance order Number from Permit number

Alias Tables in Infosets and QuickViews

Excel IBIP Tool - Easy upload PM master data

IH01 Structure Customizing beyond I_INGRP Authorization Object

Introduction

Root Cause Analysis through 5-Whys

ALV Report on Catalog Profile and Catalogs & Codes - (Infoset way)

ETM Part 1 - Basic Settings & Master data Configuration

User-Fields in QM and PM/CS Notifications : Screen-Exit QQMA0001

FAQ : Working with different time zones in SAP EAM

How to make a field optional ?

WCM -Business Models & Process flow

Hierarchical Equipment Availability Calculations (on Functional Locations)

Calling Reports from an Infoset Query

Background Job Scheduling for IP30 (RISTRA20)

Transaction Variant