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:

1. VIQMEL  - For Notification Details
2. 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

Purpose of this document is to share SAP PM - FICO integration insights. There are multiple integration points between SAP PM & FICO.

Topics covered in this document. All basic configuration settings are mentioned in this document and other integration points are mentioned in brief.

• EAM - MM Integration
• EAM - MM - FICO Integration
• EAM - FICO Integration

Note : PM - FICO integration using PS module is not covered in this document.

EAM - MM Integration Points :

• Non-Stock Materials  : To create a PR directly from a Work order.
• Material Reservations : For Stock materials to be reserved against a Work order
• Bill Of material : for setting up BOM for Functional location & Equipment
• Material Availability check : Material availability check number should be available in material master record ( MRP 3 View)
• Serial Number profile for Material & Auto generation of Equipment with default equipment category maintained in Serial number profile.

EAM - MM - FICO  Integration Points :

• PR creation from Work Order - Accounting data for a external procurement ,Service maser record etc.
• Material master record for batch managed material
• Material Valuation class & Valuation type for Refurbishment process
• Goods issuance : Moving average price for a material during goods issuance.

EAM -  FICO  Integration Points :

• Activity Based costing for calculations of Labor cost for a Work Order
• Work Order settlement - Settlement Profile
• Cost Analysis reporting

Basic Configurations required for EAM-FICO Integration

(Note - In this document, one to one mapping for Company code & Plant is considered)

Pre-requisites :  1) Assign controlling area to company code

2) Maintain Number ranges for controlling

1) Define Cost component Structure :

SPRO Path : Controlling - Product Cost Controlling - Product Cost Planning - Basic Settings for Material Costing - Define Cost Component Structure.

Description : Cost component structure determines how the results of material costing are updated. The cost component structure groups the costs for each material according to cost component (such as material costs, internal activities, external activities, and overhead). If the material is used in the production of another material.

2) Maintain Costing variants :

SPRO Path : Plant Maintenance and Customer Service - Maintenance and Service Processing - Maintenance and Service Orders - Functions and Settings for Order Types - Costing Data for Maintenance and Service Orders - Maintain Costing Variants

Description : The costing variant determines how costing is carried out. All Cost estimates are created & Saved with reference to costing variant only. Please refer to F1 help for detailed explanation.

3) Define Valuation Variants :

Path : Plant Maintenance and Customer Service -  Maintenance and Service Processing - Maintenance and Service Orders -  Functions and Settings for Order Types - Costing Data for Maintenance and Service Orders - Define Valuation Variants

Description :  Assign valuation variant to Plant for material and plant level valuation purposes.You use the Valuation Variant to specify the following things.

• Which prices are used to valuate the material components
• Which prices are used to valuate the internal activities and business processes
• Which plan version is used
• Which prices are used to valuate external processing of an assembly or operation
• Which costing sheet is used to calculate overhead

4) Assign Costing Parameters to result analysis key

Path : Plant Maintenance and Customer Service - Maintenance and Service Orders - Functions and Setting for Order Types - Costing Data for Maintenance and Service Orders - Assign Costing Parameters and Results Analysis Keys

Description : In this Step, you assign Costing variant to Plant - Order type combination as shown below.

5) Maintain Value Categories :

Path : Plant Maintenance and Customer Service  - Maintenance and Service Processing - Basic Settings - Settings for Display of Costs - Maintain Value Categories.

Description : Value categories are nothing but an interval of cost elements with respect to your controlling area. You define these value categories to display grouped cost into an Work order.

6) Assign value categories :

Path : Plant Maintenance and Customer Service - Maintenance and Service Processing - Basic Settings - Settings for Display of Costs - Assign Cost Elements to Value Categories

Description : Here you assign cost elements to your value categories created in above steps as shown below.

7) Define version for Cost elements for orders

Path : Plant Maintenance and Customer Service - Maintenance and Service Processing - Basic Settings - Settings for Display of Costs - Define Version for Cost Estimates for Orders

8) Define Default values for Value categories :

Path : Plant Maintenance and Customer Service - Maintenance and Service Processing - Basic Settings - Settings for Display of Costs - Define Default Values for Value Categories

Example : Labor cost, Material cost etc.

9) Define currency for Maintenance statistics :

Path : Plant Maintenance and Customer Service >Information Systems for Plant Maintenance and Customer Service --> Define Currency for Maintenance Statistics

Description :  In this step, you can define in which currency plant maintenance statistical data is managed. The following points are to be considered when defining the currency for the maintenance statistics.

• The currency chosen applies to the entire client.
• All of the fields in Plant Maintenance that are currency-dependent and are used for statistical data are translated automatically into the currency for statistics.
• The date with which the exchange rate is calculated is field-related and determined by the system, and cannot be changed. The equipment acquisition date is taken as a basis for translating the acquisition value and the posting date of the individual order documents is taken as a basis for translating the value fields of a maintenance order.

10) Maintain Cost key figures :

Path : Plant Maintenance and Customer Service >Information Systems for Plant Maintenance and Customer Service --> Assign Value Categories to Maintenance Cost Key Figures

Note : In this section, you can allocate value categories to PM cost key figures predefined by SAP.   The value category generally groups several cost element accounts together.

11) Maintain Settlement Profile :

Path : Plant Maintenance and Customer Service - Maintenance and Service Processing - Basic Settings - General Order Settlement -Maintain Settlement Profiles.

Note : If you want to settle the costs each time to just one cost center or just one G/L account, you need a settlement profile. As you cannot maintain the settlement parameters during settlement to a receiver, you must save the settlement profile in the order type.

In Settlement profile you have options to define criteria for settlement receiver, Default object type for settlement etc.

12) Maintain Allocation Structure :

Path : Plant Maintenance and Customer Service -> Maintenance and Service Processing -> Basic Settings -> General Order Settlement -> Maintain Allocation Structure

Description :  During settlement, costs incurred under the primary and secondary Cost elements by a sender are allocated to one or more receivers. When you settle by cost element, you settle using the appropriate original cost element. An Allocation Structure comprises one or several settlement assignments.

An assignment shows which costs (origin: cost element groups from debit cost elements) are to be settled to which receiver type (for example, cost center, order, and so on). You have two alternatives in settlement assignment:

• You assign the debit cost element groups to a settlement cost element.
• You settle by cost element - that is, the debit cost element is the settlement cost element.
• This is a good idea, for example, if the required capital spending for an asset you are building yourself is to be monitored. These costs are settled by cost element to an inventory account in Asset Accounting at the end of the year, or when the measure is complete.

13) Automatic Settlement Rule assignment :

Path : Plant Maintenance and Customer Service - Maintenance and Service Processing - Maintenance and Service Orders - Functions and Settings for Order Types - Settlement Rule : Define Time and Creation of Distribution Rule.

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

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.

Overview

The SAP serial number functionality allows managing serialized stock keeping. SAP Serial number

management is mainly focuses on Inventory tracking before and after sales. It is a precise approach than

batch management. Batches are defined as subset of material in stock. Serial number is a number that you

give to individual item of material in addition to the material number, in order to differentiate between this

individual piece and all other items of the material. Always the material number and serial number

combination is unique in system. The SAP serial number component contributes in following business area.

1. Inventory management

2. Production orders

3. Repetitive manufacturing

4. Quality Management

5. Sales orders

6. Plant Maintenance

Serial Number Profile

Serial numbers profile defines the conditions and operations for assigning serial numbers to materials. It is

plant level definition in material master work scheduling view. Serial number profiles are defined in

customization at

Plant Maintenance and customer service>Master data in Plant Maintenance and customer service

>Technical Object>Serial Number management>Define Serial Number profiles.

As shown in screenshot for profile is assigned with business procedures which defines the serial numbers

are required or can be assigned or assigned automatically. Each procedure represents the business areas.

Apart from the standard profile customized profiles can be mapped in system as per requirement.

Serial Number Masters

Serial numbers can be auto generated or created manually; the length of single number is limited to 18

characters. SAP supports both numeric and alphanumeric serial numbers. Serial number master record

can be created directly prior to business transaction, this would appropriate to have serial numbers already

in system so these can be assigned during business process. Serial numbers can be created individually

(IQ01) or several at the time (IQ04), depending on transaction chosen.

Serial number masters contents following information

 Status information: System status of gives idea about current status and availability of serial

number. User status also used for precise control over serial number movement.

 Stock information: This shows the plant and storage location of material, also the stock type of

material like unrestricted, quality or blocked stock.

 Serial number history: The history tells about the past business process with serial number.

Serial numbers are also categorized on broader level like Machine, Customer equipment etc. These

categories mainly serve the reporting purpose.

Working with Serial Numbers

Inventory Management

It is possible to characterize good movement with serial number. It does not matter in which application the

movement trigger. Serial numbers can be assigned to the goods movement like Goods receipts (For

purchase order or production order-101), Good issue (to sales order - 601), Stock transfer (311), stock

transfer orders (541) and cutover movements (561) provided that the usage of MMSL procedure should be

03 in serial number profile.

The following information is recorded for the serial number for each goods movement:

1. Plant and storage location

2.Batch

3.Valuation type

4.Stock type

5.Special stock indicator

6.Sales order number and order item

7.Account number of the vendor or customer

8.Work breakdown structure element

Status of serial number governs the movement of serialised stock. Some time it is necessary to change

status manually, in this case it is advisable to create customise user status with all optional entries.

Discrete Manufacturing - Production Orders

Serial numbers can be assigned to individual piece of header material while creating or releasing the

production order. In this case the numbers are referred to production order. At the time of GR numbers are

transferred to product of order in documented goods movement. The prerequisite is the PPAU (Serial

numbers in PP order) and PPRL (PP order release) procedures should present in serial number profile with

usage 03. These assigned numbers prints on shop floor printing paper in bar codes.

For production orders, component level serial numbers management is also possible As-built in

configuration for serialised assembly (COIB). The COIB screen can be maintained in CO11n via ‘single

screen entry of confirmation’ (OPK0). This type of business scenario observed in assembly processing

where components are maintained with serialization e.g. Compressor with serial number in refrigerator

assembly.

In case of confirmation reversal serial number status changes back to AVLB form ESTO.

Repetitive Manufacturing

Like production orders the serial number are not maintained to orders. The serial numbers are created prior

to backflush (MFBF) with IQ01 or IQ04. The documented goods movement posted along with serial number

at the backflush posting. Also in case of backflush reversal system reveres the status from AVLB to ESTO.

Quality Management

SAP quality management component supports the serial number processing. All goods movement in quality

management supports the serialization processing with QMSL procedure in serial number profile. Also it is

necessary to have serial number processing check in inspection type in quality view of material master. If

this check is not available then lot will be generated without serial number.

During inspection lot processing, you can:

 Enter results for original values with reference to serial numbers

 Enter errors with reference to serial numbers

 Make a usage decision and perform inventory postings with reference to serial numbers

At the time of quality processing the serial number status shows ESTO (In stock) and stock type 02 (In

qual. Inspection).

Sales and Distribution

Serial numbers can be assigned to sales orders, deliveries and return deliveries. Sales is major part where

considerable good movement occurs. Sale order delivery made for serialized stock with 601 movement,

also the return deliveries with or without reference to sale order made by 651 movements. If multiple depots

are available system then it is easy to track the moving inventory with serialization procedure. The

procedures SDAU, SDLS, SDCC, SDRE, and SDCR are related to Sales and distribution in serial number

profile.

Plant Maintenance

In plant maintenance serialization procedure is mainly used for the equipment management and

processing. Serial number data tab on equipment screen is made available through screen selection in

configuration. On same screen material and serial number field is located. Material assignment is

mandatory before serial number assignment to equipment.

Serialization procedure is necessary for dismantling of faulty equipment as transferring to warehouse. If

equipment parts are managed with serial numbers then it can be tracked in refurbishment process.

Serialization enables the inventory management of piece of equipment.

Conclusion

Serial number management is effective way of inventory monitoring and tracking. It is advisable to use in

sectors like consumer electronics, automobiles, and assembly units. Apart from inventory it is also useful in

after sales customer services where warranty plays important role.

Best regards,

Sameer

What is Fleet Objects in SAP PM ?

In SAP System commercial vehicles, buses, trains, trucks, loading vehicles (pay loader, excavator, dump trucks) cranes, machinery, ships, airplanes and helicopters and so on treated as a Fleet Object and maintain by Fleet Management System.

Fleet objects are similar as an Equipment with vehicle-specific additional data, which is displayed in the system on two additional tab pages. Here you can specify important fleet data such as the license plate number, load volume, consumption data, fuel card number, engine data, or fuel type and so on directly in the equipment master record.

We can  use the fleet object as a reference object for Maintenance Notification, Maintenance Order or Service Tasks.We can also perform maintenance planning date of the next scheduled service dependent on the distance counter (for example, the odometer), the time counter (for example, the time meter), or any other fleet counter.

T Code  Create: IE31

Configuration Path:

Plant Maintenance and Customer Service > Master Data in Plant Maintenance and Customer Service > Technical Objects > Settings for Fleet Management

> Assign View Profile and Equipment Categories to Fleet Object Types

Select any Object Type (have to create before) and set here as a fleet.

Save

Definition of default equipment category

Click New Entries

Save

> Define Consumable Types

> Define Usage Types for Fleet Objects

> Define Engine Types for Fleet Objects

> Make Settings for Units of Measurement for Monitoring of Consumption

> Define Special Measurement Positions for Fleet Objects

> Define Calculation Method for Fleet Consumption Values

> Set Field Selection for Specific Fields in Fleet Management

I have shown you what elements are involve in Fleet Management. Will try to update more on this later.

Good Luck

Regards,

Sameer

Introduction:

Requirement to have Additional User-Fields in various Tabs of Equipment, Functional Location or Fleet Masters is very common. Though there is a hassle-free way of having the Z-fields through Class and Characteristic way, it has got its own limitations like unable to become a part of Standard reports.

In this article, the User-Exit way of having these custom fields has been elaborated.  Enhancement ITOB0001 has been demonstrated here. The process will be same for ITOB0003 (Fleet Master).

While trying to achieve this by joining the information pieces available in the forum and outside, the author spent sufficient time to achieve all requirements related to this.

Objective:

At the end of this article we will be able to:

1. Create our own fields in the Equipment, Functional Location or Fleet Masters
2. Input values and save these values to the related Database Tables
3. Edit these values through Tcodes IE02, IL02.
4. Will have these fields in standard reports like IH08, IH06, IE37.

Here we go (ABAP Workbench)

Step 1 (Preparation of EQUI Table)

Let’s suppose we are intending to have 40char long  field, named PO Number into the Equipment Master.

1^st step is to create this Z-field into the include table of EQUI table.

For this run Tcode SE11, Give value CI_EQUI and Go to Change mode. Add a Z-field  in this table say ZZITO_PONO

with component type TXT40 (for 40char long field). Activate table.

Note:

Here I want to share a vital information with the readers. i.e., as long as I tried this task with field names like ZZPONO etc, it never worked. And there consumed lot of time.  Then at some place I read about the SAP note 594757, which states that without a prefix ZZITO_  to theCustom fields, this task would not be successful.

Next,  we need to add this field ZZITO_PONO, also to the include table CI_EQUI _U  with component type IIND (Char1). Do it in the same way as above (through SE11). Activate table.

With this we completed adding our Z-field to the database table EQUI  (through its include tables)

Step 2 (Enhancement – Create Sub-Screen)

Create a project ZPMEQUIPthrough Tcode CMOD and assign the Enhancement ITOB0001.

Now Run Tcode SMOD with value ITOB0001 and click on Test button.

See here, we have 2 Function-exits and 5 Screen exits. Let’s select the first Screen, namely 1000 .  Double click on this and Create a Sub-Screen through the steps there on.

Now Click on Layout Arrow above to go to Screen Painter and Create your Fields here. In our case we are creating One field.

As shown in the picture , drag the 'T' icon to the screen are to create a Text field and name tis field as 'PO Number'.

Similarly drag the icon below to create an Input/Output field and Give the Dictionary address to the Input field i.e., EQUI-ZZITO_PONO .

(I hope you recall that this is the field we have created in EQUI table in the step1)

Step3 ( Enhancement – Give Codes in Function Exits)

We  have 2 function Exits, namely

EXIT_SAPLITO0_001

EXIT_SAPLITO0_002

The first Exit imports the Z-field values from the EQUI table to the Equipment Master

The second one exports Z-field values from the Equipment Master to the EQUI table.

Now the codes to be written in the Exits. 

Write following code in the include (ZXTOBU01) of function-exit EXIT_SAPLITO0_001.

TABLES: EQUI.
E_SUBSCREEN_NUMBER = '1000'.
I_OBJECT_TYPE = '02' .
I_ACTIVITY_TYPE = '3' .
EQUI-ZZITO_PONO = I_DATA_EQUI-ZZITO_PONO.

Write following code in the include (ZXTOBU02) of function-exit EXIT_SAPLITO0_002

E_UPDATE_DATA_EQ-ZZITO_PONO = EQUI-ZZITO_PONO.
E_UPDATE_FLAGS_EQ-ZZITO_PONO = 'X'.

Step 4 (SPRO  Preparation)

• Navigate to this section of SPRO.

• Select Screen Group (Equipment) on the right (Profile Standard) and D’Click on the Activity and layout of views on the Right.

• Give value 150 in the line of desired Tab page of Equipment Master.

• Assign this profile (in this case Standard) to the intended Equipment Category, through this setting.

After this SPRO setting, you will be able to see your Z-Field at the bottom of the Organization Tab page  of that particular Equipment Category. Verify by running IE02 / IE03 transactions.

Try by inputting a value, Save and rerun IE02 and verify your value is stored or not.

In fact, the part of Step3 above ( coding in the Exits ) did not work as long as I did not come across the above referred SAP note. After using the prefix ZZITO_ to the Z-field these codes started working. values inserting.

Almost done

Now if you go to IE03, unlike all other greyed-out fields, your Z-field will be seen Editable. Though there is no provision to save the edits here, you’d definitely like to have this too in Greyed-out mode.

For this we need to write a small code in the PBO (Process Before Output) module of the screen 1000 we have created.

Double click on the Screen number 1000 of the enhancement, (you are in the Flow Logic Tab) ,

D’Click on the STATUS_1000 of the PBO module. and insert this code between the MODULE, END MODULE lines like this

MODULE STATUS_1000 OUTPUT.
IF SY-TCODE = 'IE03'.
LOOP AT SCREEN.
SCREEN-INPUT = '0'.
MODIFY SCREEN.
ENDLOOP.
ENDIF.
ENDMODULE. 

Related discussion:

Configure field selection for equipment user-fields

Lastly Do not Forget to

Activate the Function Group  XTOB  from  Tcode SE80.  Right click on the Function Group and click on the Activate option

Now the Last Step.

Step 5 (Have this Z-field in the Standard Report , in this case IE05, IH08)

To have our Z-field in IH08 output, first we need to know the structure of this report output.

For this click on any cell in the ALV screen and press F1 key.

Here click on the Technical Information icon. The resulting pop-up will show you the Structure against field name Table. Here the Structure is RIHEQUI_LIST .

Now through SE11 go to the above Structure, Click on an Append Structure on the Application toolbar and Create an Append structure having this field. Activate table.

Now Run IH08 and see in the output list in the Column Set (thelist not displayed). You should find this field PO Number.

Often you do not find this. It is time to clear ALV buffer through program BALVBUFDEL.

For this run Tcode SE38 give the above program and hit Execute.

Now run IH08 again and verify, your field is there.

Note:

This work is with a larger objective in mind to avoid re-inventing the wheel after sometime and at the same time providing the Total Solution about this task at one place.  This work involves Appending structures and Activation of Tables, which should be done by experienced ABPAers only.

Also this work can be extended to Functional Location Masters with the same enhancement used above and to the Fleet Masters with enhancement ITOB0003.

..and I feel it is important to mention the version I experienced all these and documented, it is ECC6.0 no EHPs.

Hope members find this useful.

Thank you

Jogeswara Rao K

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:

1. VIQMEL  - For Notification Details
2. 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

There are situations for which we want to reflect some changes in a PM order to the assigned PM notification. When we create the order and then a PM notification the equipment, if entered, is also created as reference object in the notification.

This is the standard behavior when we are creating the documents. It appears some cases for which we also need to maintain some fields synchronized between these two documents. That's the case when we change the equipment in the order and want to have the same equipment updated in the assigned notification.

From a search in customizing we can find some related feature in the "Set up Synchronization of work center in Order/Notification", which is an entry in the PM customizing node "System Enhancements and Data Transfer". This is the possibility to get a synchronization between the two documents but just for when we change the work center.

To make it available to other fields we can use the Enhancement (type "Customer Exit") IWO10009 that is called when we save the PM order, after creating a project in CMOD The example I've done using CMOD transaction is attached to this document as a picture .

Note I've done this just as an example so it has some limitations. The program can be used just as a start base and more ABAP code should be added according to the following limitations.

Limitations

• Only synchronizes the equipment
• Only from PM order to the assigned notification
• Not error handling is done, should be added
• Code should be added because some fields should need to change when the equipment changes: Planner Group", "Main Work Center"
• Need to be adapted to run with other transactions not only IW32.

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

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:

Requirement to have Additional User-Fields in various Tabs of Equipment, Functional Location or Fleet Masters is very common. Though there is a hassle-free way of having the Z-fields through Class and Characteristic way, it has got its own limitations like unable to become a part of Standard reports.

In this article, the User-Exit way of having these custom fields has been elaborated.  Enhancement ITOB0001 has been demonstrated here. The process will be same for ITOB0003 (Fleet Master).

While trying to achieve this by joining the information pieces available in the forum and outside, the author spent sufficient time to achieve all requirements related to this.

Objective:

At the end of this article we will be able to:

1. Create our own fields in the Equipment, Functional Location or Fleet Masters
2. Input values and save these values to the related Database Tables
3. Edit these values through Tcodes IE02, IL02.
4. Will have these fields in standard reports like IH08, IH06, IE37.

Here we go (ABAP Workbench)

Step 1 (Preparation of EQUI Table)

Let’s suppose we are intending to have 40char long  field, named PO Number into the Equipment Master.

1^st step is to create this Z-field into the include table of EQUI table.

For this run Tcode SE11, Give value CI_EQUI and Go to Change mode. Add a Z-field  in this table say ZZITO_PONO

with component type TXT40 (for 40char long field). Activate table.

Note:

Here I want to share a vital information with the readers. i.e., as long as I tried this task with field names like ZZPONO etc, it never worked. And there consumed lot of time.  Then at some place I read about the SAP note 594757, which states that without a prefix ZZITO_  to theCustom fields, this task would not be successful.

Next,  we need to add this field ZZITO_PONO, also to the include table CI_EQUI _U  with component type IIND (Char1). Do it in the same way as above (through SE11). Activate table.

With this we completed adding our Z-field to the database table EQUI  (through its include tables)

Step 2 (Enhancement – Create Sub-Screen)

Create a project ZPMEQUIPthrough Tcode CMOD and assign the Enhancement ITOB0001.

Now Run Tcode SMOD with value ITOB0001 and click on Test button.

See here, we have 2 Function-exits and 5 Screen exits. Let’s select the first Screen, namely 1000 .  Double click on this and Create a Sub-Screen through the steps there on.

Now Click on Layout Arrow above to go to Screen Painter and Create your Fields here. In our case we are creating One field.

As shown in the picture , drag the 'T' icon to the screen are to create a Text field and name tis field as 'PO Number'.

Similarly drag the icon below to create an Input/Output field and Give the Dictionary address to the Input field i.e., EQUI-ZZITO_PONO .

(I hope you recall that this is the field we have created in EQUI table in the step1)

Step3 ( Enhancement – Give Codes in Function Exits)

We  have 2 function Exits, namely

EXIT_SAPLITO0_001

EXIT_SAPLITO0_002

The first Exit imports the Z-field values from the EQUI table to the Equipment Master

The second one exports Z-field values from the Equipment Master to the EQUI table.

Now the codes to be written in the Exits. 

Write following code in the include (ZXTOBU01) of function-exit EXIT_SAPLITO0_001.

TABLES: EQUI.
E_SUBSCREEN_NUMBER = '1000'.
I_OBJECT_TYPE = '02' .
I_ACTIVITY_TYPE = '3' .
EQUI-ZZITO_PONO = I_DATA_EQUI-ZZITO_PONO.

Write following code in the include (ZXTOBU02) of function-exit EXIT_SAPLITO0_002

E_UPDATE_DATA_EQ-ZZITO_PONO = EQUI-ZZITO_PONO.
E_UPDATE_FLAGS_EQ-ZZITO_PONO = 'X'.

Step 4 (SPRO  Preparation)

• Navigate to this section of SPRO.

• Select Screen Group (Equipment) on the right (Profile Standard) and D’Click on the Activity and layout of views on the Right.

• Give value 150 in the line of desired Tab page of Equipment Master.

• Assign this profile (in this case Standard) to the intended Equipment Category, through this setting.

After this SPRO setting, you will be able to see your Z-Field at the bottom of the Organization Tab page  of that particular Equipment Category. Verify by running IE02 / IE03 transactions.

Try by inputting a value, Save and rerun IE02 and verify your value is stored or not.

In fact, the part of Step3 above ( coding in the Exits ) did not work as long as I did not come across the above referred SAP note. After using the prefix ZZITO_ to the Z-field these codes started working. values inserting.

Almost done

Now if you go to IE03, unlike all other greyed-out fields, your Z-field will be seen Editable. Though there is no provision to save the edits here, you’d definitely like to have this too in Greyed-out mode.

For this we need to write a small code in the PBO (Process Before Output) module of the screen 1000 we have created.

Double click on the Screen number 1000 of the enhancement, (you are in the Flow Logic Tab) ,

D’Click on the STATUS_1000 of the PBO module. and insert this code between the MODULE, END MODULE lines like this

MODULE STATUS_1000 OUTPUT.
IF SY-TCODE = 'IE03'.
LOOP AT SCREEN.
SCREEN-INPUT = '0'.
MODIFY SCREEN.
ENDLOOP.
ENDIF.
ENDMODULE. 

Related discussion:

Configure field selection for equipment user-fields

Lastly Do not Forget to

Activate the Function Group  XTOB  from  Tcode SE80.  Right click on the Function Group and click on the Activate option

Now the Last Step.

Step 5 (Have this Z-field in the Standard Report , in this case IE05, IH08)

To have our Z-field in IH08 output, first we need to know the structure of this report output.

For this click on any cell in the ALV screen and press F1 key.

Here click on the Technical Information icon. The resulting pop-up will show you the Structure against field name Table. Here the Structure is RIHEQUI_LIST .

Now through SE11 go to the above Structure, Click on an Append Structure on the Application toolbar and Create an Append structure having this field. Activate table.

Now Run IH08 and see in the output list in the Column Set (thelist not displayed). You should find this field PO Number.

Often you do not find this. It is time to clear ALV buffer through program BALVBUFDEL.

For this run Tcode SE38 give the above program and hit Execute.

Now run IH08 again and verify, your field is there.

Note:

This work is with a larger objective in mind to avoid re-inventing the wheel after sometime and at the same time providing the Total Solution about this task at one place.  This work involves Appending structures and Activation of Tables, which should be done by experienced ABPAers only.

Also this work can be extended to Functional Location Masters with the same enhancement used above and to the Fleet Masters with enhancement ITOB0003.

..and I feel it is important to mention the version I experienced all these and documented, it is ECC6.0 no EHPs.

Hope members find this useful.

Thank you

Jogeswara Rao K

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:

1. VIQMEL  - For Notification Details
2. 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