In the area of Enterprise Asset Management SAP just recently kicked off a new customer connection cycle on February 2nd.
The project workspace is now active for collection of improvement requirements until April 16th, 2016
Find more information and additional links here:
Dear Friends,
As the title indicates this is about Checks while creating Measuring Documents and hence about a user-exit namely the very useful IMRC0004 . I felt an immediate need to record and preserve the solutions for various types of checks discussed so far, because it has been realized today that 3 times in last half year, I started by suggesting solutions through user-exit IMRC0001 for these queries and corrected myself in the end by giving final solution through IMRC0004. Also, being such an useful exit, this IMRC0004 is very less talked about exit.
Now few lines about the difference in using the above referred two exits for these checks.
IMRC0001
I always remembered this exit as the one which triggers at the Saving of a MPt or MDoc as the description starts so. 'MeasPoint/MeasDoc: Exit before update (after COMMIT WORK)'. All such requirements about checks while creating Measuring documents, look work well with this exit but there is an issue caused by this part of the exit description i.e, 'after COMMIT WORK'.
What happens is, our code successfully prevents the MDoc from getting saved if the conditions are not met, but it interrupts the COMMIT WORK. So after preventing the MDoc when the system takes us to IK11 initial screen, if we continue by hitting Enter or by clicking on Back key etc, it would result in a short dump, because the code interrupted the COMMIT WORK. (We can avoid this short dump by coming out of the screen by using some tcode in the command bar).
So that is a clear limitation for using this exit for such purposes.
IMRC0004
The description here says: 'Measure.doc.:Exit according to stndrd checks for new mes.doc' . So far this description failed to trigger in my mind at right time in using for MDoc checks. But not here onwards because this event of blog creation will have its punch in the mind and would not let me forget again.
The basic difference in triggering of these exits is, the former triggers at the time of Saving the MDoc and the later namely our subject exit, triggers instantly at the time of entering values in the IK11 screen.
------------------------------------------------------------------------------------------------------------------------------------------------
Now, I am listing below some typical requirements of Checks while creating MDocs and the Codes to be written in the include ZXMRCU04 of the exit IMRC0004 .
------------------------------------------------------------------------------------------------------------------------------------------------
Case1
To prevent users from entering readings in the 'Counter reading' field of the Measuring document (of a counter obviously).
The code
As mentioned earlier all these codes being discussed are needed to be put in include ZXMRCU04.
IF sy-tcode = 'IK11' AND impt_data-indct = 'X' AND imrg_ins-idiff IS INITIAL.
MESSAGE: 'Reading in ''Counter reading'' field is not allowed. Please enter your reading in the ''Difference'' field.' TYPE 'E'.
ENDIF.
This code first checks whether the tcode is IK11, then checks whether the Measuring document is for a Counter and then checks whether the field Counter reading entered as difference(IDIFF) is empty. If this field is empty, then it understands that the Reading is entered in the Counter reading field and throws the following error in the status bar of IK11 screen.
------------------------------------------------------------------------------------------------------------------------------------------------
Case2
To prevent users from entering readings in the 'Difference' field of the Measuring document for 'M' category of the MPts.
The code
IF sy-tcode = 'IK11' AND impt_data-mptyp = 'M' AND impt_data-indct = 'X' AND imrg_ins-idiff IS NOTINITIAL.
MESSAGE: 'Reading in ''Difference'' field is not allowed. Please enter your reading in the ''Counter reading'' field.' TYPE 'E'.
ENDIF.
This throws an error in the status bar the moment someone enters a reading in the Difference field and hits Enter (for 'M' category of measuring points)
------------------------------------------------------------------------------------------------------------------------------------------------
Case3
To prevent creating of a MDoc of a particular MPt, in case the difference between previous reading and current reading is more than a value say 20,000.
The code
DATA: l_readg TYPE imrg-readg,
l_point TYPE imrg-point,
l_prvrdg TYPE imrg-readg,
l_diff TYPE imrg-readg.
CLEAR: l_readg, l_point, l_prvrdg, l_diff."wains
l_point = imrg_ins-point.
l_readg = imrg_ins-readg * 1000.
SELECT SINGLE readg FROM imrg INTO l_prvrdg WHERE point = imrg_ins-point.
l_diff = l_readg - l_prvrdg.
IF l_diff < 0.
l_diff = - l_diff.
ENDIF.
IF l_point = '000000000500' AND l_diff > '20000'.
MESSAGE: 'The difference between consecutive readings is more than ''20000''' TYPE 'E'DISPLAY LIKE 'I'.
ENDIF.
This throws the following error popup
------------------------------------------------------------------------------------------------------------------------------------------------
Case4
To restrict users from entering values below or above certain limit if particular ValCode is chosen.
The code
IF imrg_ins-codgr = 'DEDR' AND imrg_ins-vlcod = '0010' AND imrg_ins-cancl <> 'X'.
IF imrg_ins-readg < 3.
MESSAGE: 'Incorrect Reading, For the selected ValCode reading can not be less than ''3''' TYPE 'E'.
ENDIF.
ENDIF.
Here is the IK11 screen with the values and the error in the status bar.
------------------------------------------------------------------------------------------------------------------------------------------------
Case5
To prevent users from entering same Counter reading as the last MDoc.
The code
IF impt_data-indct = 'X' AND imrg_ins-cancl <> 'X'.
DATA: old_readg TYPE imrg-cntrr.
SELECT SINGLE MAX( cntrr ) FROM imrg INTO old_readg WHERE point = impt_data-point.
IF imrg_ins-cntrr = old_readg.
MESSAGE: 'Counter reading equal to previous reading not accepted' TYPE 'E'.
ENDIF.
ENDIF.
In this case system throws this Standard warning message first in the status bar:
Upon continuing by pressing Enter key, an error triggers in the status bar preventing MDoc creation, which is as a result of above code.
------------------------------------------------------------------------------------------------------------------------------------------------
So, like these there can be many cases. But the different code samples discussed here, have the potential to address all such requirements by suitably using.
------------------------------------------------------------------------------------------------------------------------------------------------
Notes
------------------------------------------------------------------------------------------------------------------------------------------------
Hope the forum especially EAM space will be benefited through this knowledge sharing.
Thank you.
KJogeswaraRao
User experience is one of the main challenge most companies face to improve adoption of SAP EAM by maintenance technicians. Award wining Fiori concepts could help in crossing this hurdles. (Refer this link to know more about Red Dot Design Award http://news.sap.com/sap-fiori-2-0/)
SAP is now offering a training course to learn these concepts so that you can quickly implement these new concept in your organization. Above all it is free training and does not need any technical background. Most people who are participating in EAM SCN space are able to participate in this community based learning and stand a chance to win an iPAD. For more information please have look at link given below.
https://open.sap.com/courses/fiux2
Regards
Hemant
In a very short time we have received 150 improvement request for our customer connection project for SAP PM.
Details of some of these requests would be discussed by originator of the request during speaker’s corner sessions.
Register and join first speaker corner session to know more about the request so that you can subscribe for request that are relevant for you.
Link to register this event is given below..
To access this link you need a S-user that you use for creating support message. You need to register yourself on influence portal with your S-user ID.
Regards
Hemant
Reporting is one the important features in SAP. SAP has built lot of standard reports in order to solve the basic benefits of the customers to avoid custom developments.
In reality due to complex business processes we tend to build custom reports for customers but in case of any issues, we tend to compare the standard SAP report with custom build report, to confirm whether the values are populated correctly from the tables or there are any selection issues and list goes on.
In this blog, I would like to share a special transaction provided by SAP to identify the list of Standard Reports available for each module.
Are you aware SAP has provided a transaction SAP1? If no, then below is for your information.
Whenever we login into SAP, SAP Easy Access or User Menu will be displayed. To check the reports first we should know the transaction or navigate the structure in the respective module.
Now Go to Transaction SAP1 in transaction code area and Press Enter
It opens a screen SAP Easy Access – Report Selection
If we drill down Plant Maintenance – Management of Technical Objects
This will list out the transaction based on Technical Objects.
As an additional example, if we want to see PR / PO reports available in MM Structure.
Drilling down Materials Management – Purchasing – Purchase Requisition / Purchase Order
To return back to SAP Easy Access Menu, Click the highlighted below
Similarly, you will be able to get all reporting transactions in one place. This transaction will reduce the dependency towards other module consultant or raising SCN thread to identify reports.
More you explore,
More you learn &
More you will use SAP
The SAP-Centric EAM Conference is North America’s most comprehensive event designed specifically for the SAP enterprise asset management (EAM) community.
Join us in Denver on March 7–10 to learn how the SAP extended supply chain portfolio incorporating enabling technologies like the cloud, business networks, and the Internet of Things, are delivering unprecedented value for EAM professionals.
Don’t miss this unique opportunity to:
Continue the conversation and meet with SAP experts at our demo kiosks and see how SAP solutions are improving EAM performance for:
The complete agenda can be found here.
We are looking forward to seeing you there!
The SAP Asset Data Quality rapid-deployment solution has now been merged with theSAP Information Steward rapid-deployment solution V3.420 which apart from the EAM (SAP PM) master data objects, covers materials, supplier and customer master data.
The solution gives customers the ability to assess, validate and continuously monitor the quality of their asset master data, with information visualization and governance capability. With SAP's industry-leading data quality management tool Information Steward, and predefined content, this solution lays a solid foundation for a comprehensive Enterprise Asset Management (EAM) solution.
The scope of the solution includes processes for creating or changing business and validation rules, identifying corresponding data quality issues, and ongoing analysis of historical data with continuous insight for SAP ERP.
Key domains include:
Access the SAP Information Steward rapid-deployment solution from the SAP Service Marketplace.
Don't miss two upcoming webinars on SAP Management of Change and on SAP’s Environment Management application and register today.
DATE: Thursday, March 10, 2016, Time: 11:00am EST / 8:00am PST / 5:00pm CET
As the list of stakeholders requesting environmental and sustainability data grows, corporations are challenged with the need to have an accurate, transparent and auditable business process to produce this data. Deploying a global business process to calculate and report your emissions data not only requires the ability to collect operations data in a timely manner, but also requires the ability to estimate/calculate the same data with accuracy and consistency. SAP’s Environment Management application gives customers the ability to collect, calculate and report their emissions data with a global, transparent and auditable business process. This webcast will give you a solution overview and a live demo of the new Emissions Management functionality supported by the SAP Environment Management application. Register Now.
Implementing Management of Change procedures that work
DATE: Wednesday, March 16, 2016, Time: 11:00am EST / 8:00am PST / 5:00pm CET
Companies running Process Safety Management are mandated to have a formal Management of Change (MoC) approach in place, but since regulations are not prescriptive, companies often rely on various disparate procedures including forms being passed around on paper or via email. On the other hand, it has become abundantly clear, that a good MoC system yields great benefits, not only in terms of preventing process industry disasters, but also by eliminating disruptions of any kind that can lead to quality problems, or other commercial losses. In this webinar, we will present how SAP Management of Change makes it easy for users to handle change requests and all associated activities. Companies can set up automatic processes that fit their organization and eliminate ambiguities and tedious tasks for all involved parties. You will also learn about the latest Feature Pack of SAP Management of Change that has been built to significantly reduce the implementation effort and increase the flexibility of the solution even further. Register Now.
If you missed the past webinars of the SAP EAM Webcast Series, you still have the chance to watch a replay of these sessions.
We are looking forward to seeing you online!
Within this blog i intend to make you aware of the fact that setting user status on operation level has never been as easy as in Web User Interface.
In the Web User Interface of EAM you are able:
This is possible and as well documented in the Innovation Discovery
1) Client : It is the highest hierarchical unit in the SAP system. All areas of an organization that are to be integrated into SAP, should be included under one client.
2) Controlling area : An organization unit within a company used to represent a closed system for cost accounting purpose.A controlling area may include single or multiple company codes that may use different currencies. These company codes must use the same operative chart of accounts. All internal allocations refer exclusively to objects in the same controlling area.
3) Company Code :It is the smallest organizational unit of Financial Accounting for which a complete self-contained set of accounts can be drawn up for purposes of external reporting. This includes recording of all relevant transactions and generating all supporting documents required for financial statements.
4) Maintenance Plant :A Maintenance Plant is an organizational unit within Logistics, serving to subdivide an enterprise according to procurement, maintenance, and materials planning.
5) Maintenance planning plant :Maintenance planning plant is a logical location where the maintenance activities on technical objects are planned. The Maintenance Planner Groups who plan and monitor the maintenance activities are defined at the maintenance planning plants. Maintenance planning plants determine if the maintenance planning is centralized, decentralized or partially centralized.
If maintenance is centralized, then there would be one Maintenance Planning Plant for all the Maintenance Plants. if it is decentralized, then there would be a Maintenance Planning Plant for each Maintenance Plant. if it is partially decentralized, then there would be Maintenance Planning Plants, looking after a few Maintenance Plants each.
Business Process & master data Impacts :
a) Material Planning based on maintenance task lists and maintenance orders
b) Management and scheduling of maintenance plans
c) Creation of maintenance notifications
d) Performance of maintenance orders
e) Location-wise analyses on different performance parameters like costs, downtime's, breakdowns etc. are possible at the Planning Plant level.
f) Definition of technical objects, maintenance task lists etc.
6) Locations : Location is a place in a maintenance plant at which a technical object is physically located. It allows a plant to be classified according to spatial or situation criteria.
Locations are used for informative assignment only. We can only use Locations as a match code or as parameter criteria in reporting.
7) Plant section : Plant sections are processing units/ production areas within a maintenance plant. These are subdivision of maintenance plants. Machines or sets of machines that are represented in the system as pieces of equipment or functional locations are installed in plant sections.
We can indicate the place for which a maintenance task was requested with the plant section. We also, can establish a contact person for Plant Maintenance using the plant section. Plant sections are assigned to Maintenance plants.
8) Maintenance planner groups : A group of employees responsible for planning and processing maintenance tasks in a plant. Planner groups or Maintenance Planner groups must be defined separately for each planning plant. Depending on the size and structure of your company, a maintenance planning group may be an individual department (for central work preparation), a group of Technician or a workshop.
9) Work Center : Work Center is an organizational unit that defines where and when an operation must be performed. The Work Center has an available capacity. The activities performed at or by the Work Center are evaluated by charge rates, which are determined by Cost Centers and Activity types. Centers and Activity types are defined and detailed in Finance & Controlling Module. Work Centers can be: Machines, People, Production lines or Groups of craftsmen.
Thanks for reading through. Please visit http://sapeambook.blogspot.in/
Here is a list of cut-over tasks that should be considered during go-live.
Please contribute:
Technical Object is a generic term for,
1) A component in a technical system on which a maintenance task is performed (functional location).
2) A physical object that is maintained as an autonomous unit (equipment).
In Other words, Technical Object is nothing but an object which requires Maintenance. In Plant maintenance basically there are two main types of Technical Objects.
Technical objects are maintained in the SAP System in separate master records. If you want to represent part of a technical system as a technical object, you can:
a) Manage individual data.
b) Perform breakdown, prepared, or planned maintenance tasks.
c) Record maintenance tasks that have been performed.
d) Collect and evaluate technical data over long periods of time.
e) Track the costs of maintenance tasks.
f) Track which piece of equipment was installed when at which functional location.
1) Functional Location :
The business object functional location is an organizational unit within Logistics, which structures the maintenance objects of a company according to functional, process-related or spatial criteria. A functional location represents the object at which a maintenance task is to be performed. A functional location represents system area at which an object can be installed. The objects that can be installed at functional locations are called Equipment.
You create a functional location in following cases,
a) When you have to perform maintenance task on a particular part of your complete technical system and record the same.
b) When you have to track the maintenance history of a particular technical object.
c) When you want to represent a major equipment which consist of many small equipment.
d) When you have to monitor Maintenance Cost.
1.1) Functional Location Category : An indicator that let you differentiate functional locations according to how they are used. Each location category required in the system is described using parameters. The number of functional location categories in a system depends on the number of parameter constellations required
1.2) Structure Indicator for Functional Locations : Numbering of functional Locations will be based on the structure indicator. The Structure Indicator defines the format of the code used to describe the Functional Location hierarchy. The Structure Indicator determines the edit mask and the number of the hierarchy levels when you create functional location structures. The edit mask defines:
a) the total length of the functional location number.
b) the lengths of the individual blocks of the functional location number.
c) the characters allowed.
Structure Indicator | ABC |
Description | Structure Indicator |
Edit Mask | XXXX-XXX-XXX-XXXXX-XXXX-XXXX-XXXX-XXXX |
Hierarchy Level | 1 2 3 4 5 6 7 8 |
2) Equipment :
Equipment is a representation of every important and expensive individual component of a machinery such as Pump, Engine, Motor, Tire etc.
The business object "Equipment" is an individual, physical object that is to be maintained
independently. It can be installed in a technical system or part of a technical system. We can manage all types of objects as pieces of equipment. Equipment can also be managed as "assets" in Asset Management.
All types of device as pieces of equipment (for example, production utilities, transportation utilities,test equipment, production resources/tools, buildings, PCs) can be identified as Equipment.
Each piece of equipment is a separate master record and an individual maintenance history can be set for each one. The system manages the master records for pieces of equipment at client level. This means that their numbers are valid for the entire corporate group.
This will facilitate,
a) Defining breakdown / Preventative maintenance tasks.
b) Measuring specific parameters.
c) Classification data.
d) Collection, evaluation, retrieval of data including cost of maintenance, history and usage.
e) Spare parts planning.
2.1) Equipment Categories : An indicator used to differentiate pieces of equipment according to its characteristic & usage. In SAP, Equipment categories control the number assignment of Equipment. There are two possible options when you are creating a piece of equipment:
a) Internal number assignment
The numbering shall be internal (SAP generated internal number) and is limited to 18 characters.
b) External number assignment
You can enter your own equipment number as per the configured number ranges in the SPRO settings.
2.2) Technical Object Type : It is the sub-division of the equipment category, which allows a more detailed description. This allows, grouping of pieces of equipment that have the same use. These object types can be alphanumeric.
3) Bill Of Material :
Bill of material is a term used for spare parts which are to be replaced but no history is to be maintained. There are different types of BOM - Production BOM, Maintenance BOM, Costing BOM, Construction BOM. etc. These types of BOM are used for different purpose based on Enterprise business requirement.
In Plant Maintenance, we use Maintenance BOM which is devided into three subcateogires such as
Functional Location BOM, Equipment BOM and Material BOM.
Other than Functional location, Equipment and Bill of Material, there following important master data items in SAP PM module.
1)Task list : List of maintenance task to be performed by a technician to maintain a particular technical object.
Maintenance Task Lists describe a sequence of individual maintenance activities which must be performed repeatedly within a company. These are the master data for Preventative Maintenance Process. There are three types of maintenance task lists that can be distinguished from one another using indicators:
Equipment Task List
Equipment task lists have a specific link to a piece of equipment. Using equipment task lists,
you can centrally define and manage maintenance tasks for your pieces of equipment.
Functional Location Task List
A functional location task list is assigned to a specific functional location. Using a functional
location task list, you can centrally define and manage maintenance tasks for your functional
location.
General Maintenance Task List
General maintenance task lists are task lists that are used for general maintenance tasks.
They do not refer to a specific technical object. Using general maintenance task lists, you can define and manage sequences of maintenance tasks centrally, and use them for
maintenance planning.
2)Measuring Points : Measuring points are physical and/or logical locations ( of a technical object) at which a particular condition is described − for example, the temperature, pressure etc. You can enter measurement readings for each object to be maintained.
3)Measuring Counters : These are resources that enable you to represent the wear and tear of an technical object or the consumption or reduction in its useful life. E.g. Running hours of a machine, Mileage indicator of a vehicle. You can enter measurement or counter readings for each object to be maintained.
Other items like maintenance plans, measurement documents we will cover in Maintenance planning process page.
4) Catalog profile/Code groups /codes : Catalog Profile is a combination of code groups from several catalogs. Catalog is a compilation of code groups with related contents.
Code Groups consists of data on problems, damages, causes and Corrective action to be taken or taken is recorded in the system
Codes are the means with which this data is managed in the Plant Maintenance (PM) application components. There is a corresponding code for each set of findings. The codes are grouped together in code groups according to particular characteristics.
5) Warranties : Warranties define the scope of the services that a company performs at a technical object in the event of damage or problems. You can assign warranties to pieces of equipment, functional locations, or serial numbers. When warranty is assigned to a technical object, The system can automatically check when processing a maintenance notification/ order.
6) Classification of Technical Objects : Classification consists of Class and Characteristics. Its basic function is as a repository for all the characteristics the objects can have. These characteristics can then be used to group similar objects together in classes. Classification system is used to maintain technical parameters (as characteristics) of a technical object and to group similar objects in a class. Characteristics will have values for the relevant object. Classification helps in identifying similar objects quickly & easily
Thanks & Best Regards,
Amol Khairnar
SAP EAM - SAP Enterprise Asset Management, SAP Plant Maintenance
SAP EAM team in collaboration with SAP User Experience and Design team is pleased to invite you to the SAP Fiori Customer Co-Innovation Forum Q1/2016. During this forum, various SAP tam would showcase new Fiori Apps developed and released SAP.
SAP EAM team would be presenting the first transactional app to create maintenance request during this virtual event. Customer Co-innovation forum, provides a unique experience of viewing features of new app and provide expert advice to the team about how you would see new app can be further improved. The event has been planned with two time slots so that everyone from SAP eco-system across the globe can participate, learn about new functional enhancements and provide their valuable insights.
Use following link to register for this event.
https://experience.sap.com/participate/fiori-q1-2016-customer-co-innovation-forum/
Even as an experienced SAP GUI User the following happens quite often:
this is quite frustrating for the end user and leads to the fact that the people do not like how the system is reacting . Observations tell us that User spend up to 30 % of the time with searching the right Equipments, Functional Location, Task List ...
Within the new EAM Web User Interface we have tackled this issue and we found a solution which suits the purpose of the value help much better.
Now you are able to:
This is possible now for the following Objects within EAM:
You find this new feature inInnovation Discovery under the Innovation
here you find:
we hope this suits the users needs much better.
To achieve better return on investment for any equipment, important components of costs along with equipment availability needs to be analyzed and corrective measures needs to be prepared.
For example, a plant may measure types of work (preventive, predictive, failure and modifications), labor and materials to identify important gaps in their maintenace capability. Let us assume that such analysis will provide information that 10% of the work is predictive, 40% is preventive, 30% is unexpected failure and approximately 20% of the PM is short closed each month. Although at high level this may look OK, but there could be huge overlap between preventive and predictive maintenance. Such unintended overlap increases costs and it occurs because of various activities like Preventive Maintenance and Predictive Maintenance are not planned in a unified system.
Most plants can build their PM programs over long period of time. Creation of PMs are done because they are hopped to reduce failure. Over time, these Preventive maintenance plans will grow to include inspections. Plants may observe some high visibility incidence that may require additional PM. The frequency will be set and the PM applied to every piece of equipment that is similar to the one that failed. It is natural that if machine failed, the boss is unhappy, and PM makes the boss less unhappy. Over time, the number of PMs Increases to the point that many aren’t being completed; even with an extensive PM program, there are still failures that can’t be eliminated.
With PM program getting stabilized with addtional failures, plant would begin additionally a PdM program by monitoring a few pieces of highly critical equipment with vibration analysis (where there usually is some success). In most cases these New PdM program also brings in additional benefits and leads to increase that success, the program would grow. If the organization has a lot of support corporately for implementation of PdM, they would typically apply the technology to 50% of their known assets and use all available technologies. To determine how many assets to monitor, the plant should determine how many technologists it can support and then buy the equipment needed to perform the work.
Conclusion: A well planned maintenance strategy needs mix of Preventive and Predictive methodology. Planning these strategy should be clearly documented along with what benefits it would bring in. Maintenance strategies are compiled and corresponding benefits are noted, it can be used along with current performance to identify possible future improvements in the area derive higher utilization of assets..
Dear SCN users,
I have been active on SCN since last one month and I have observed many open threads where experts have given their answers which are correct and helpful but users did not bother to close these threads.
I would like to highlight few benefits of closing threads on time.
1) If you close threads on time, beginners can learn form these threads. Most of beginners they do refer "answered" posts on SCN.
2) if yous issue is not resolved even after multiple experts suggestions, that particular issue can be identified as entity of Continuous improvement and can be logged to influence.sap.com for future development & Patches.SAP Customer Influence: Enterprise Home
3) Updating your thread regularly improves collaboration between all SAP consulting experts across globe and Idea exchange takes place fruitfully.
Likewise there are many helpful returns of being active and careful about your discussion threads.
As a member of this SCN community, I would like to request everyone to follow the SCN rules of engagement properly.
Best Regards,
Amol
Reporting is one the important features in SAP. SAP has built lot of standard reports in order to solve the basic benefits of the customers to avoid custom developments.
In reality due to complex business processes we tend to build custom reports for customers but in case of any issues, we tend to compare the standard SAP report with custom build report, to confirm whether the values are populated correctly from the tables or there are any selection issues and list goes on.
In this blog, I would like to share a special transaction provided by SAP to identify the list of Standard Reports available for each module.
Are you aware SAP has provided a transaction SAP1? If no, then below is for your information.
Whenever we login into SAP, SAP Easy Access or User Menu will be displayed. To check the reports first we should know the transaction or navigate the structure in the respective module.
Now Go to Transaction SAP1 in transaction code area and Press Enter
It opens a screen SAP Easy Access – Report Selection
If we drill down Plant Maintenance – Management of Technical Objects
This will list out the transaction based on Technical Objects.
As an additional example, if we want to see PR / PO reports available in MM Structure.
Drilling down Materials Management – Purchasing – Purchase Requisition / Purchase Order
To return back to SAP Easy Access Menu, Click the highlighted below
Similarly, you will be able to get all reporting transactions in one place. This transaction will reduce the dependency towards other module consultant or raising SCN thread to identify reports.
More you explore,
More you learn &
More you will use SAP
The SAP-Centric EAM Conference is North America’s most comprehensive event designed specifically for the SAP enterprise asset management (EAM) community.
Join us in Denver on March 7–10 to learn how the SAP extended supply chain portfolio incorporating enabling technologies like the cloud, business networks, and the Internet of Things, are delivering unprecedented value for EAM professionals.
Don’t miss this unique opportunity to:
Continue the conversation and meet with SAP experts at our demo kiosks and see how SAP solutions are improving EAM performance for:
The complete agenda can be found here.
We are looking forward to seeing you there!
Dear All,
I have come across one of the good requirement posted on influence.sap.com. ( ID: D10681).
Extend the field code to 8 digits.
Using the Catalog - Code groups in QS41 and QS42, the field code is not supporting that many scada systems sends out alarm codes contaning more than 4 digits.
Extending the code field will support the use of interfaces from external systems creating notificaitons in SAP PM. Then there is no need for creating conversion rules to get the interfaces to work.
Requested release*
SAP ERP 6.0 EhP7
Describe current pain points and obstacles
Conversion rules is need for getting the interfaces from external systems to work when catalog - code groups are used in SAP to reflect the alarm codes send from external systems into SAP.
You can follow this request on the link mentioned below.
https://influence.sap.com/D10681
Regards,
Amol Khairnar
In a very short time we have received 150 improvement request for our customer connection project for SAP PM.
Details of some of these requests would be discussed by originator of the request during speaker’s corner sessions.
Register and join first speaker corner session to know more about the request so that you can subscribe for request that are relevant for you.
Link to register this event is given below..
To access this link you need a S-user that you use for creating support message. You need to register yourself on influence portal with your S-user ID.
Regards
Hemant
