1 2 3 8 Previous Next

Enterprise Asset Management (SAP EAM)

114 Posts

          On July 30th, 2014 Scott Allen with Denbury Resources presented an ASUG EAM Community Webcast titled “BOM Creation Where to Begin. Lose the Panic! It’s Easy”. This webcast was part three of our four part webcast series recapping the SAP Centric EAM 2014 (http://www.sap-centric-eam.com/eam) conference that was held in Austin, Texas in February. This presentation really meant a lot to me because, as Scott mentioned in his webcast, my presentation on Bills of Material at the 2012 SAP EAM Centric conference inspired Scott to create this presentation. Scott presentation was the number one ranked presentation at this year’s conference.

            I met Scott at the 2012 SAP Centric EAM conference. I gave my presentation on Bill of Materials (BOM). My employer Fairfax Water had implemented SAP in 2009 and we made the mistake of not having BOM’s created when we went live. I explained to the audience that this was a huge mistake and not to make same that mistake. Scott’s employer, Denbury Resources was implementing SAP Plant Maintenance (PM) and Materials Management (MM) and was about to make the same mistake.

Pic 1.jpg

 

 

          Scott decided that Denbury was not going to make thismistake. Scott came back from that conference and told his implementer, Vesta
Partners, that they need to create BOM’s. Scott tirelessly worked with Vesta’s Greg Manley to create over BOMs for over forty thousand pieces of equipment and Functional Locations.  Scott and his team contacted vendors and got the material information they needed to build their BOMs. They even traded doughnuts for spreadsheets of the information they needed. The vendors, of course, complied because they wanted Denbury Resources business.

 

Pic 2.jpg

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

          The creation of BOMs allowed Denbury’s SAP implementation of Plant Maintenance (PM) to be a success. Scott explained in his webcast that
before SAP planners averaged 45 minutes planning a work order. Now Denbury’s planners are planning jobs in four to five minutes. That the power of BOMs.
Having all the part information you need in front of you can maximize the system. As a former planner who did not have this information at his fingertips, I am almost envious of the information planners can have if SAP PM is set up correctly.

 

Pic 3.jpg

 

 

          I think Scott summed it up best with this quote from SAP Centric EAM 2014 conference:

 

 

Realistic expectations are key to the successful execution of a bill of materials data strategy. Efficient planning of time and resources from both PM & MM is critical to achieve those expectations on a tight implementation schedule”  - Scott Allen, Denbury Resources

 

    

Here is a link for ASUG Members to Scott’s presentation and
webcast recording:

 

 

ASUG.com - Events

 

 

 

 

          Our next webcast for ASUG EAM Community members will held on September 9, 2014 12pm-1pm EST. This webcasts is part one of four in our next
webcast series “SAP Mobile Enterprise Asset Management (EAM) - Today, Roadmapand Futures”.

 

 

Registration Link:

 

 

ASUG.com - Events

 

 

 

The entire overview for the four part SAP Mobile EAM Webcast series can be located here:

 

 

ASUG.com - Special Interest Groups - Plant Maintenance

 

 

Jeff Smith

 

 

ASUG Plant Maintenance
SIG Program Chair

During the recent development cycle SAP addressed the topic of Simplification in Enterprise Asset Management.

 

The focus of the Simplification project was on enhancing the Web user interface with new and rich functionality as well as using the newest features of the underlying Web Dynpro ABAP technology. In this project different areas were addressed. These improvements enable maintenance planners and workers to use the EAM Web user interface to do their jobs more efficiently.

 

This series of blogs wanted to cover some of these enhancements and explain what is possible now in Enterprise Asset Management via the Web user interface.

 

All these topics are bundled in the EhP7 Business Function “LOG_EAM_SIMPLICITY_3” and do not require any additional license on top of the existing enterprise foundation license.


You can find details on the different new capabilities based on the simplification project in my Blogs listed below. In addition to the details I also wrote on the Rapid Deployment Solution (RDS) to implement a jump start version of Enterprise Asset Management to cover the main processes of Maintenance Operations (see: The fast lane to EAM). On top of this you can find a blog on the possibility to create very fast a test environment for EAM in the cloud to test out or verify new EAM functionality.

 

Here you will find more information on the recent simplification topics:

 

Blogs

 

Additional information

 

Here you will find more general information on Enterprise Asset Management:

 

You will have the opportunity to discuss all relevant EAM topics with the SAP experts during the International SAP Conference on Asset Management in Amsterdam (Netherlands) on October 7th and 8th 2014 - find details here!

During the recent development cycle SAP addressed the topic of Simplification in Enterprise Asset Management. The focus of the Simplification project was on enhancing the Web user interface with new and rich functionality as well as using the newest features of the underlying Web Dynpro ABAP technology. In this project different areas were addressed. These improvements enable maintenance planners and workers to use the EAM Web user interface to do their jobs more efficiently.

 

This series will cover some of them and explain what is now new in EAM. All these topics are bundled in the EhP7 Business Function  "LOG_EAM_SIMPLICITY_3” and do not require any additional license on top of the existing enterprise foundation license.

 

New features in the Web user interface for the Maintenance Work Order

 

The user can create and edit long texts directly in the operation data and in the operation details.

 

You can create orders using a template (reference order). When you create a new order by copying an existing order, you can specify whether you want to copy the relationships, settlement rules, linked documents, and order descriptions as well. In addition to that, you can create order operations by copying existing operations.

 

Up to now, some of the system statuses that you were able to set in the SAP GUI transactions for orders could only be displayed on the SAP Web UI for Plant Maintenance. This new feature enables you to change most of the system statuses used in the SAP GUI transactions also on the SAP Web UI. In the maintenance order you can now set and change additional system statuses as follows: Do not Execute, Complete (Business), Cancel Business Completion, Lock, Unlock, Set Deletion Flag, and Reset Deletion Flag. You can set these system statuses not only directly in the maintenance work order but in the Order List as well.

 

For inspection rounds, you can assign technical objects and assemblies at operation level. In the operation details, you can enter measuring points as production resources/tools for the technical objects that you have assigned at operation level.

 

You can assign technical objects and material using a structure list. This feature enables you to display structure lists for technical objects on the SAP Web UI for Plant Maintenance. Structure lists not only make it easier to find technical objects and materials in orders, notifications, task lists, and maintenance plans, but they also provide essential information about the technical objects and materials. You can display structure lists for any technical objects that are part of a hierarchy.

 

The new list ATS component is implemented here as well. We have switched all List Component to the new List ATS Component technology within the whole EAM application. The List ATS (ABAP Table Services) component provides you with an extended range of features, including personalization features, and advanced sorting and filtering functions.

 

The personalizing feature enables you to work more easily with tabular lists in maintenance orders, notifications, task lists, and maintenance plans. You can search for table entries and the search result is then highlighted in the list. You can have the system add up the table entries in numeric table columns and export the tables to a spreadsheet. You can personalize the view of the table by displaying and hiding the table columns, as well as sorting, grouping, and
filtering the table entries and then save your personal settings as your own view.

 

You will have the opportunity to discuss these topics with our experts during the International SAP Conference on Asset Management in Amsterdam (Netherlands) on October 7th and 8th 2014 - find details here!

 

See my earlier blog post about Simplification in EAM - Quickviews

See my earlier blog post about Simplification in EAM - Notifciations

 

In my next posting I will do a short summary what we did with respect to Simplification in EAM and where to find more information on these topics. Coming soon!

During the recent development cycle SAP addressed the topic of Simplification in Enterprise Asset Management. The focus of the Simplification project was on enhancing the Web user interface with new and rich functionality as well as using the newest features of the underlying Web Dynpro ABAP technology. In this project different areas were addressed. These improvements enable maintenance planners and workers to use the EAM Web user interface to do their jobs more efficiently.

 

This series will cover some of them and explain what is possible now in EAM via the Web user interface. All these topics are bundled in the EhP7 Business Function “LOG_EAM_SIMPLICITY_3” and do not require any additional license on top of the existing enterprise foundation license. 

 

New features in the Web user interface for the Maintenance Notification

You can assign a task list to the maintenance notification. If this notification is later assigned to an order, the system copies the operations of the task list to the order.

 

The user can create long texts directly in the malfunction data, task data, and in the activities, and edit the long texts in a popup.

You can create notifications using a template (reference notification). When you create a notification by copying an existing notification, you can specify whether you want the linked documents to be copied to the new notification as well.

 

Up to now, some of the system statuses that you were able to set in the SAP GUI transactions for orders and notifications could only be displayed on the SAP Web UI for Plant Maintenance. This feature enables you to change most of the system statuses used in the SAP GUI transactions also on the SAP Web UI. In the maintenance notification you can now set and change additional system statuses as follows: Put in Process Again, Set Deletion Flag, and Reset Deletion Flag. You can set additional statuses not only directly in the notification, but also in the Notification List.

 

You can assign technical objects using a structure list. This feature enables you to display structure lists for technical objects on the SAP Web UI for Plant Maintenance. Structure lists not only make it easier to find technical objects and materials in orders, notifications, task lists, and maintenance plans, but they also provide essential information about the technical objects and materials. You can display structure lists for any technical objects that are part of a hierarchy.

 

The new list ATS component is implemented here as well. We have switched all List Component to the new List ATS component technology within the whole EAM application. The List ATS (ABAP Table Services) component provides you with an extended range of features, including personalization features, and advanced sorting and filtering functions.

 

See my earlier blog post about Quickviews

In my next posting I will elaborate what is new in the area of maintenance orders. Coming soon!

During the recent development cycle SAP addressed the topic of Simplification in Enterprise Asset Management. The focus of the Simplification project was on enhancing the Web user interface with new and rich functionality as well as using the newest features of the underlying Web Dynpro ABAP technology. In this project different areas were addressed. These improvements enable maintenance planners and workers to use the EAM Web user interface to do their jobs more efficiently.

This series will cover some of them and explain what is now new in EAM. All these topics are bundled in the EhP7 Business Function “LOG_EAM_SIMPLICITY_3” and do not require any additional license on top of the existing enterprise foundation license.

 

New features in the Web user interface for the Quickviews

 

You are looking for an easy way to view important object information without leaving the actual screen?

 

On the SAP Web UI for Plant Maintenance you are now able to display so called “Quickviews” for maintenance documents, technical objects, materials, and long texts that are assigned to orders, notifications, task lists, and maintenance plans.

 

A Quickview is a read-only UI element which allows the user, at runtime, to view additional information (not displayed on the current screen) about an object without having to navigate to other screens. Like a tooltip, a Quickview appears (and disappears) on the UI during a mouse-over action by the user and shows the most important and/or most useful information regarding that object.

 

Quickviews are available for the following Enterprise Asset Management objects:

  • Technical Objects (functional location / equipments) - Quickviews for the superior technical objects and the installed pieces of equipment
  • Notifications -  Quickviews for the technical objects, the assigned orders, the activities and the long text
  • Maintenance Orders - Quickviews for the technical objects, the assigned notifications, the materials and the long texts
  • Maintenance Plans - Quickviews for the technical objects and the maintenance plan (on the General Data tab of the maintenance item
  • Materials
  • Long Texts


Example for the technical object Quickview:

Quickview_Equi_v01.jpg

Quickviews appear as separate windows during a “mouse over” and can provide information as well as links. In the Quickview for a piece of equipment, for example, the category, manufacturer, location, and status information are displayed as well as a link to the functional location where it is installed.

 

You can configure each individual Quickview to display certain information for the users. You can also suppress Quickviews if you do not want them to appear.

Quickview_Overview_v01.jpg

This Quickview functionality is part of the EhP7 Business Function “LOG_EAM_SIMPLICITY_3” and does not require any additional license on top of the enterprise foundation license.

 

In my next posting I will elaborate what is new in the area of maintenance notifications. Coming soon!

2014-08-19_20-19-47.jpg

 

ASUG's EAM Community has just announced a four part webcast series that will run from September to December 2014.

 

Maintenance has always been mobile,  now you can learn about  " EAM  and Mobile " during these sessions.

 

Here are the webcast details and registration links for what should be very informative sessions that are open to ASUG members.

 

Take Enterprise Asset Management Where It Matters Most with Mobile

 

Transform the way you manage your assetā€intensive business. With SAP Enterprise Asset Management (EAM) mobile apps, you can improve business processes and executions, enhance safety and compliance, and give field workers the power to collaborate in real time. Participate in this four-part webcast series on mobile EAM with SAP product experts and EAM industry leaders to learn about current offerings, customer stories, best practices, and future innovations in assetā€intensive industries.

 

Slide1.jpg

 

SAP Mobile Enterprise Asset Management (EAM) - Today, Roadmap, and Futures

 

Date: Tuesday, September 9, 2014

Time: 12:00 p.m. ET

Duration: 60 minutes

 

Field workers and maintenance technicians are always on the move. They require real-time access to information about assets, inventory, and work orders in dynamic environments. Asset-intensive industry leaders are looking to mobile and other innovative technologies for process improvement and execution, enhanced safety and compliance, and real-time collaboration among operations, maintenance, logistics, services, and support.

 

Attend this webcast with Patrick Flaherty, SAP Mobile Field Service & EAM Expert, to learn about SAP’s current solutions, the roadmap, and the future of mobile EAM.

 

Register Now

 

 

 

Untether Field Workers with Augmented Reality

 

Date: Wednesday, October 8, 2014

Time: 12:00 p.m. ET

Duration: 60 minutes

 

The opportunity to untether field workers is here. With augmented reality, field service technicians are enabled with a “hands free” experience through visual enterprise models, gesture or touch events, voice recognition, and remote-expert calling to perform their tasks and operations.

 

Attend this webcast with SAP augmented reality experts to learn what augmented reality is all about, SAP’s current solutions for field workers, and customer use cases and co-innovation stories.

 

Register Now

 

 

 

Mobile EAM Customer Spotlight

 

Date: Wednesday, November 5, 2014

Time: 12:00 p.m. ET

Duration: 60 minutes

 

More than 600 customers around the globe have deployed mobile EAM solutions from SAP to streamline asset management and realize dramatic operational efficiencies in the workplace. According to SAP performance benchmarking and customer reference studies, mobile EAM customers have increased labor productivity by up to 50% and reduced production down-time and delays by as much as 30%.

 

Attend this Customer Spotlight session on mobile EAM to learn about real-world SAP EAM mobile deployments and best practices.

 

Register Now

 

 

 

Plan Now for the Future of Mobile EAM

 

Date: Wednesday, December 3, 2014

Time: 12:00 p.m. ET

Duration: 60 minutes

 

Mobile solutions have already changed how people work and assets are managed to drive operational excellence. The next generation of mobile technologies including devices, wearables, and augmented reality, will create opportunities to increase asset performance and reliability.

 

Attend this session with Erik Schrampf, Mobile Solution Management for EAM/Field Service (Syclo) Mobile Apps, to learn about the future of mobile EAM, including product roadmaps and customer co- innovation plans.

 

Register Now

Perhaps for the reason of being associated with many SAP objects, the report making on classification process, is not easier using the related tables.  Because of this, sometime back the author took help of a Logical Database (EQI) and Infoset Query to develop a report on Equipment vs Class. Here LDB helped to resolve the complications of retrieving the Class for Equipment or Functional Location. OK ! That job was done so and we got a useful report. Time passed on and we put the values into the characteristics of several thousands of Technical objects as under .

 

IE02

ie02.JPG

 

Then I started feeling a requirement for a report which upon giving Equipment number as input, would bring me the Class name, Characteristics assigned to this class and then the respective values of these characteristics. Again I sat for developing an infoset query.  This time I could understand that it is not going to be easy. I need to use 3 Function Modules and write the coding. Enough time spent, but Infoset queries at such complicated times push be to full pledged ABAP report program. So I started, researched for FMs to retrieve the Classification and Characteristic details and ultimately could succeed in getting the output I desired.

 

The objective of this blog is to share this result with the forum, so that needy members would be benefitting. Also if I chose to explain how I coded it will be a long one and full of technical things and quite likely to be boring. So what I thought to do is explain briefly and give the code, so that you will be able to assign your own Tcode for it and use.

 

Report is mainly based on these two FMs

 

Function ModulesGives you in a table
ALM_ME_CLASS_CHAR_GETDETAILRetrieves the details of all Characteristics of the inputted Equipment
BAPI_OBJCL_GETCLASSESRetrieves the details of Values of above characteristics.

 

There was lot of further treatment in the code to get the desired output. So we now see the Selection screen.

 

 

The Selection Screen

selscreen.JPG

Here you can see that apart from Equipment number I’d opted for Class and Planner Group in the Selection screen, so that the output would bring the Class/characteristics values of multiple equipments belong to this criterion.

 

 

Then,

 

The Output

Output.JPG

 


Because there is no such standard report available, it was a sense of accomplishment the moment I arrive at the above output. Hope members too find it useful.


Last but not the least, the code is here: Code for report on Equipment vs Class vs Characteristic vs Values .

Based on this code as Driver program, a smartform has been developed later: Screen-shot of Smartform




Good luck

KJogeswaraRao


Enterprise Information Management (EIM) solutions helps business better manage big data, ensure accurate analytics, and improve governance, with timely, consistent, and trustworthy information at every level of the enterprise. With Information Steward, and EIM technology solution, business can understand and analyze the trustworthiness of the enterprise information, get continuous insight into the quality of the vast amount of data, and facilitate informed decision making and streamline business processes. It can also help model the information architecture to visualize business needs, and ensure correct and consistent data.

 

Enterprise Asset Management (EAM) is a industry domain focused software helping business manage physical assets, increase operational efficiencies, and better manage capital expenditures throughout the asset lifecycle. Asset is an important piece of enterprise data.

 

How to make Information Steward work with Enterprise Asset Management (EAM) to manage the asset data? How to make the EIM core technology works with the industry solution? You may already know that Information Steward can manage the Customer, Material, and Supplier data domains. The SAP Information Steward rapid-deployment solution provides predefined contents for that. What about the Asset data domain? You can use the SAP Asset Data Quality rapid-deployment solution!

 

The SAP Asset Data Quality rapid-deployment 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.

 

Now The SAP Asset Data Quality rapid-deployment solution can work with Information Steward 4.2 version. The note 1733333 for the RDS has been updated for IS 4.2 support, and three updated documents are attached to this note.

 

Access SAP Asset Date Quality rapid-deployment solution from Service Market Place. Download from the Download Center, following the path as below:

-->software downloads

-->sap software download center

-->Installations and Upgrades

-->Browse our Download Catalog

-->SAP Rapid Deployment solutions

-->SAP Asset Data Quality rapid deployment solution

-->SAP RDS IS CONTENT V2

      --># OS independent

     -->ISCONTENT02_0-10012110.ZIP

  -->SAP RDS DS CONTENT V3

     --># OS independent

     -->SAPRDSDSCONTENT06_0-10012109.ZIP

Time is money

This is true for the implementation of a sandbox- or test systems too. To check the capabilities of the SAP Enterprise Asset Managment solution in advance of or during implementation projects causes effort in form of time and resources.

 

To test new EAM functionality or new EAM processes in a sandbox you need to implement up-to-date Enterprise Asset Management functionality, efficient resource and demand planning (like SAP Multiresource Scheduling)  and a mobile app for order and timesheet management for your maintenance processes (like SAP Work Manager). Then you need to create the necessary master data to validate or test the envisaged processes. To establish all this you need a system, time and the resources with the necessary knowledge in EAM.

 

SAP now delivers a vehicle to make this process much faster and easier for customers and/or partners. Using the SAP Cloud Appliance Library (CAL) you will get a predefined sandbox in a very easy way. The SAP Cloud Appliance Library is an on-demand SAP HANA Cloud solution. It is hosted on SAP Cloud to deliver SAP Enterprise Asset Management content as a software appliances directly into the Amazon cloud accounts of existing customers.

 

Going this way, test drive Enterprise Asset Management in the cloud offers the opportunity to you, to spend your time on the evaluation and innovation and not worry about the hassle of setting up and configuring your SAP solution.

 

That means:

  • What you see is what you get: Test drive the solution in the cloud before it is implemented in your system
  • Clean demo system with configuration and sample data
  • Jump start your evaluation project (e.g. a PoC) with a ready-to-use demo system

 

What‘s included?

  • Fully activated virtual appliance of a configured SAP ERP system with sample data
  • End-to-end business process integrating plant maintenance in SAP ERP with SAP Multiresource Scheduling and SAP Work Manager
  • Customizable to your requirements
  • Ready-to-use for your Proof-of-Concept or system demo

 

Where to acccess?

 

Want to learn more?

 

    During PM implementations the masterdata is collected from various Plants / Plant Sections of the client, arranged in excel sheets and uploaded by the Core-Team through BDC  programs usually. This masterdata consists of the Asset Structure (IH01), Catalogs & Codes,  Maintenance Plans, Measuring Points etc. In large industries where the Asset structure runs into 100s of 1000s of equipments, we managed the uploading by giving authorizations to end-users selectively by creating and assigning suitable roles. The BOMs namely Bill of Materials is one such Masterdata, the author arranged for uploading by the respective end-users. For this purpose I developed one-stop Tcode through which user will be able to upload/update easily all sorts of BOMs namely:

     

    • Functional Location BOM (IB11,IB12)
    • Equipment BOM (IB01, IB02)
    • Material BOM (CS01, CS02).

     

    Let’s see the Tcode screen

    selscreen.jpg


    The above selection screen is self explanatory.  However, let me do it for you.

    There are 3 parts:

    1. GOS toolbar where all the excel templates are kept as attachments.
    2. The Upload new BOM section having 3 radio buttons for IB01, IB11 and CS01
    3. The Update existing BOM section having 3 radio button for IB02, IB12 and CS02.

     

    This screen is a simple radio button Call Transaction program. What we understand is this screen calls 6 programs one at a time (Radio button) as per the user’s choice. So the real BDC programs are those called programs. Let’s have individual screen-shots of these programs. (For IB01 and IB02)

     

    IB01

    Capture.JPG


    IB02

    2.JPG

     

     

    Rest of the screens (for IB11, IB12 and CS01, CS02) are similar.

     

    Here Mode of uploading there are 2 options

           A - All screen Mode

    N - No Screen Mode (Background) just like usual BDC programs.

     

     

    Though it is not related to the theme of the post, I am sharing the screen-shots of Excel templates of my program

     

    IB01, IB02

    ex1.JPG


    IB11, IB12

    ib11.JPG

     

    CS01, CS02

    cs01.JPG

     

    As you have seen, the Templates for Uploading and Updating a particular BOM is same. In fact very small modifications in the Upload programs created Update BOMs programs. In each BOM template I have given provision for 18 components. (These can be as many as per requirement) Also these templates are very specific to my programs. You will have your own templates depending upon the coding of your own batch program.

     

    The main all-in-one screen program  is a very simple report program (though looks like a dialog program). This has been another very useful idea to develop such user-friendly screen, so thought of sharing with the forum.

     

     

    Thank you

    KJogeswaraRao

    This blog is in continuation to my previous blog "LSMW for Master Data upload Simple Explanation (Part - 1)" - LSMW for Master Data upload Simple Explanation (Part - 1)

     

    We will continue here with Step 9 - Specify Files

     

    Step 9 – Specify Files:

     

    Before performing this Step, you need to create your File format with exact field sequence.

     

    For creating the Format, simply transpose your Excel File fields from column to Row as shown below:

    33.png

    (Here I have mentioned only Single line for data you should have all the data which you wish to create in one time as in screen shot below)

     

    Select only the Data from excel sheet and copy it to notepad file as shown below and Save:

    34.png

    Now in SAP, double click “Specify Files” in the Menu List screen which will guide you to the screen as shown below:

    35.png

    Double click on “Legacy Data - On the PC (Frontend)” which will pop-up the dialog box as shown below:

    36.png

    In File field select the Notepad File created, in the Name Field assign any desired name and make other selections exactly as shown in the screen and Press Enter, Save and Back.

     

    Step 10 – Assign Files:

     

    Double click “Assign Files” in the Menu List screen, which will guide you to the screen as shown below:

    37.png

    As we have single Structure and Single File, it is auto assigned to Structure. Just Press Save and Back

     

    Step 11 – Read Data:

     

    Double click “Read Data” in the Menu List screen, which will guide you to the screen as shown below:

    38.png

    Without making any changes to this screen, press execute button which will show the screen as below:

    39.png

    This will Show the exact number of total records/ Masters which you have mentioned in your notepad file. If this does not match the exact value, check your notepad and excel file for data. Once Confirmed, Press back twice

     

    Step 12 – Display Read Data:


    Double click “Display Read Data” in the Menu List screen, will pop-up a dialog box as shown below:

    40.png

    Without making any changes to this screen press enter, which will show the screen as below:

    41.png

    This screen is displaying all the Master Data Records which are read from your notepad file. Double Clicking any record will show Field-wise Data where you can check the correctness of your data (this step is not mandatory).

    Once confirmed press back twice.

     

    Step 13 – Convert Data:


    Double click “Convert Data” in the Menu List screen, which will guide you to the screen as shown below:

    43.png

    Without making any changes to this screen, press execute button which will show the screen as below:

    44.png

    This will Show the exact number of total records/ Masters which are converted from your notepad file to Structure. If this does not match the exact value, check your notepad and excel file for data. Once Confirmed, Press back twice

     

    Step 12 – Display Convert Data:

     

    Double click “Display Convert Data” in the Menu List screen, will pop-up a dialog box as shown below:

    45.png

    Without making any changes to this screen press enter, which will show the screen as below:

    46.png

    This screen is displaying all the Master Data Records which are read from your notepad file. Double Clicking any record will show Field-wise Data where you can check the correctness of your data (this step is not mandatory).

    Once confirmed press back twice.

     

    Step 13 – Create Batch Input Session:

     

    Double click “Create Batch Input Session” in the Menu List screen, which will guide you to the screen as shown below:

    48.png

    Make the selections as per shown in the screen above and press execute. This will guide you to screen as shown below:

    49.png

    This will display the number of transactions saved for execution. This all fields should be in green. If any record is in red, please check your entries again. If all records are green, press back twice.

     

    Note: For some masters or for recording method Step 13 would show a simple screen where you need to tick “Keep Batch Input Session” and execute.

     

    Step 13 – Create Batch Input Session:

     

    Double click “Run Batch Input Session” in the Menu List screen, which will guide you to the screen as shown below:

    50.png

    This screen can also be executed through SM35.


    Here select the record you want to process and press9.pngwhich will pop-up a dialog box as shown below:

    51.png

    Processing Mode:

     

    First Option “Process/ foreground” will guide you to each field of each screen of your Master records.

     

    Second option “Display errors only” will process your program in Background but will stop at Errors in any Field of any Screen which you can change.

     

    Third Option “Background” will process your program completely in background and will update the errors at last.

     

    (Recommended to use “Display errors only” option)

     

    Additional Functions

     

    Select the “Extended Log”, “Expert Mode” and “Dynpro Standard Size” options.

     

    Once made the above selections, press process.

     

    Once all the data are uploaded will pop-up a dialog box as shown below:

    52.png

    Pressing “Session overview” will show the session details and “Exit Batch input” will exit the transaction.


    Here it completes the Legacy Data Migration Workbench (LSMW) process.



    Hope I have clarified the process very clearly.



    (This is the First time I have written a blog. Request you to please post your honorable comments).

    The LSMW (Legacy System Migration Workbench) is a tool based on SAP software that supports single or periodic data transfer from non-SAP to SAP systems (and with restriction from SAP to SAP system). Its core functions are:

    • Importing legacy data from PC spreadsheet tables or sequential files.
    • Converting data from its original (legacy system) format to the target (SAP) format
    • Importing the data using the standard interfaces of SAP (IDoc inbound processing, Batch Input, Direct Input).

     

    (This blog only explains how to create/ change Master data in SAP by using Standard Programs or recordings. I have not covered BAPI and IDoc method to make it simple and easy)

     

    Generally, people have questions in mind as how to create an LSMW project, which method should be used to upload the master data and how to use and what all master data can be uploaded through LSMW.

     

    LSMW – Legacy Data Migration Workbench

     

    I am dividing the whole process of creating a Project, Subproject & Object for uploading the Master Data and its upload procedure in different steps as explained below:

     

    Step 1 – Creating Project, Subproject and Object:

     

    For using LSMW tool, first step you need to do is Create Project, Sub Project and Object as shown in the screen below:

    1.png

    Here, Project can have multiple Subprojects and in turn Subprojects can have multiple Objects as explained below:

     

    Create Project

    Give the desired name of data migration Project (For ex: Module name as I have taken “ZPM” for Plant Maintenance Module)

     

    Create Subproject

    Give the desired name of data migration Subproject (For ex: Master’s name as I have taken “EQUIP” for Equipment Master)

     

    Create Object

    Give the desired name of data migration Object (For ex: Master’s name as I have taken “CREATE” for Creating Equipment Master)

     

    Step 2 – Selecting Menu Items:

     

    Once Project, Subproject and Objects are created, pressing enter would generate the screen which includes all the menu items for both Master upload as well as IDoc updation which we might not require. Let us select the menu items which are required only for Master uploads.

     

    Selecting Menu Items

     

    First of all, pressing the User Menu button would guide you through selecting and de-selecting the Menu items.

    Please tick the required Items as shown in the screen below:

    6.png

    Now, the screen would display only the selected Menu Items which we require for building and executing our LSMW program as shown below:

    7.png

    Click the button “Double Click = Display” which would make it to “Double Click=Change” which means it will allow all the Menu Items to open in Change mode on double clicking else every item is in display mode by default.

     

    Henceforth, we will see each Menu Item in detail as an individual step.

     

    Step 3 – Maintain Object Attributes:

     

    This Menu Item defines the procedure we adopt for our program which could be:

    1. Standard Batch/ Direct Input
    2. Batch Recording
    3. Business Object Method (BAPI)
    4. IDoc (Intermediate Document)

     

    For defining the procedure, double click on the First option “Maintain Object Attributes”. The screen below shows how to select the method:

    9.png

    As mentioned earlier, this blog covers explanation of only first two methods to make it simple and easy.

    (Believe me most of the Masters gets covered in this two methods.)

     

    Method 1 – Standard Batch/ Direct Input

     

    In this method, we are simply selecting the standard program defined by SAP for different Masters (most of the Masters are listed here):

     

    Click on Object to select the program then click on Method to select the method (For ex: Create/ Change) as shown in screen below:

    10.png

    Once selected, save this method.

    Method 2 – Batch Input Recording

     

    This method, involves creating a recording for a specific Master transaction Creation/ Change.

     

    We would select this method when we require only specific fields to be created/ changed inside the Master screen.

    Creating a recording is explained below:

     

    Click on3.pngbutton and then click on4.png(Recordings: Overview) button which would guide to the Recording screen. Here press Create button which will show the screen as below:

    12.png

    Fill in the desired Recording Name and description as shown and press Enter and input the Transaction code as shown in the next screen:

    13.png

    On pressing Enter, system will start the transaction screen as shown below:

    14.png

    Perform the recording for the transaction (i.e., input all the fields you require to be taken into account for batch input).

     

    Remember to save the transaction to complete the recording procedure as saving is also getting recorded.


    On pressing save, you will see all the fields recorded as shown below:

    15.png

    Here press "Default All" button to populate the fields to be made available for batch input.

     

    This will show the exact field names against each field as shown in the screen below:

    16.png

    Saving this screen would guide user to the list of recordings. Here press back and select the recording in the Recording field as shown below and save:

    18.png

    This ends the Step 1 for creating the method for specific Master creation/ change.

     

    Step 4 – Object Overview and Field List:

     

    Before moving to the second Menu Item “Maintain Source Structures”, we would go for listing the fields and viewing the structuring of the fields by pressing the6.pngbutton in the Menu List Screen and then “List” button which would show the screen as below (for easiness I have used Method-1 i.e., Standard Batch/ Direct Input but list will be similar in both the cases only the fields would differ):

    19.png

    Here in the “Target Fields” section you will find all the fields (captured by Method-1 or Method-2).

     

    Please copy all the fields (except field TCODE and RECORDNAME which we don’t require to change while running our batch) and arrange the same in excel file as shown below:

    20.png

    By this you will be able to capture all the required fields in your excel file which ends the Step 4.

     

    Step 5 – Maintain Source Structures:

     

    Source Structure will have all the Source fields which are recorded or captured during Method definition.

     

    Double click on “Maintain Source Structures” to which will guide to screen of Source Structure creation

    Here press the create button which will ask for Source Structure Name and Description as shown below:22.png

    After entering the desired Source Structure name and Description, press enter and press Save.

     

    Step 6 – Maintain Source Fields:

     

    Source fields are the same which we have listed in Step 4.

     

    Before moving to this step, back to your excel sheet, change all field Types as below:

     

    CHARC
    DATSDDMY
    UNIT C
    TIMSC
    TIMSC

    23.png

    (This is to be done because the types defined in LSMW are different then field types in program or recording)

     

    Now, double click ”Maintain Source Fields” in the Menu List screen, which will guide you to the screen as shown below:

    24.png

    Press the7.png(Table Maintenance) button after selecting the Structure which will generate the field definition screen. Copy paste all the excel fields to the screen as shown below:

    25.png

    Press Save and Back and it will display the fields attached to the Source Structure as shown below:

    26.png

    Again press save button to save this Structure field relation.

     

    Step 7 – Maintain Structure Relations:

     

    This Step is for maintaining relation between Structure and Recording/ Standard Program.

     

    Double click “Maintain Structure Relations” in the Menu List screen, which will guide you to the screen as shown below:

    27.png

    Select the first Structure and press8.pngand the structure you have created will be automatically be selected as you have created only one structure. This will create the relationship between program and Structure as shown below:

    28.png

    Press Save and Back.

     

    Step 8 – Maintain Field Mapping and Conversion Rules:

     

    We have created the Structure to Program Relationship, now we need to create the mapping (Relationship) between Fields from Structure and Fields from Program/ Recording.

     

    Double click “Maintain Field Mapping and Conversion Rules” in the Menu List screen, which will guide you to the screen as shown below:

    29.png

    As we have copied the fields from the Program/ Recording itself as in Step 4, it will be easy to perform the field mapping in a simple step.

     

    Go to Extras à Auto Field mapping which will pop-up a dialog box as shown below:

    30.png

    Perform the selection exactly as shown in the screen above and press Enter.


    If you have any Date fields in your Field List, it will ask for your confirmation for every individual Fields as shown below and make selection as per your requirement (This is how system will interpret Date further throughout the program):

    31.png

    Press Enter for all the Date Fields and you will find the field mapping for all your Source Fields to Program/ Recording Fields as shown below:

    32.png

    Confirm all the Fields are mapped correctly and press Save and Back.

     

    Due to certain restrictions of blogs, this document covers the steps uptil "Maintain Field mapping and Conversion Rules" below steps,

    1. Specify Files

    2. Assign Files

    3. Read Data

    4. Display Read Data

    5. Convert Data

    6. Display Convert Data

    7. Create Batch Input Session

    8. Run Batch Input Session

     

    are convered in Part-2 of this document which can be found in the link below:

    LSMW for Master Data upload Simple Explanation (Part - 2)

    For many of the Functional people longtexts is a sort of complicated thing for the fact that there are no straight tables which store these lines. So, whenever we think of making some report displaying long texts, we generally stuck at the very initial stage of finding the source of this information. This document is aimed at clearing these concepts.

     

    We know the longtexts are very widely used within all SAP objects. For example in PM module, Longtexts associated with Notification Header, Order Header etc, also the Long texts associated with Catalog-Codes in Notifications, Operations in Orders, Measuring document related .

     

    In this post, we try to understand these concepts, through the longtexts of PM Order operations.

     

    So, let’s try and see how we reach the Long text lines of an Order operation.

    Essence of this document is centered at using a Function Module named READ_TEXT.  First let’s have a look at what this FM gives? For this, run Tcode SE37.

    se37.JPG

     

    Give FM name in the Function Module field and Hit function key F8 or Click on Execute button shown above.

    se37_1.JPG

     

    Now, here in the above screen, when we

    1. Enter the values for the fields marked Green
    2. Press Execute button

    We get the long text lines into the table named LINES at the bottom (marked Red).

     

    Now what are these fields we need to fill and where we will find these? The answer comes from the Order operation longtext page. In our example we have taken operation 0020 of an Order as shown below .

    1.JPG

    Here, we enter into the long text page upon clicking on the Longtext icon above. Now in the Longtext page click on GoTo --> Header  in the menubar.

    1a.jpg

     

    Now we get the pop-up below, showing these field values required for SE37.

    2.JPG

     

    Let’s see the relation between the SE37 screen and the Order Longtext screen fields through the following picture. (The value in ‘Client’ field of SE37 need not be filled. System identifies and fills it).

    2a.jpg

     

    Here, we understand all the field values except for one i.e. the TEXTNAME. The understood fields are namely:

     

    Field nameValueRemarks
    LANGUAGEENConstant as per your system
    TEXTIDAVOTConstant for Order Operation longtext
    TEXTOBJECTAUFKConstant for Order related longtext

     

    What we need to understand is the value of TEXTNAME i.e., 400100140302700000002. Let’s see how this comes. Let's see this number this way.

     

    400100140302700000002

     

    First 3 characters (400) is the client number of the SAP (on which you are working)

    Next 10 characters (1001403027) form the AUFPL field value of the operation

    Next 8 characters (00000002) indicate the Operation number APLZL

     

    Client number we always are aware of. Other two field values we should take from table (view) VIAUF_AFVC by inputting the Order number. Means, run Tcode SE16, give value VIAUF_AFVC and hit function key F7 .

    3.JPG

     

    Enter the Order number and Execute (F8).

    4.JPG

     

    We get this results screen.

    5.JPG

    Here as per the operations tab of the Order we see 3 records one for each operation.  Our operation in question is no.2. Let’s pick-up the corresponding values of AUFPL and APLZL from here.

     

    So what I want to say is, the ABAPer passes the values of Orders from the Selection screen (of the ZTcode he develops) and extracts these values from the table and concatenates (joins) all the 3 vlaues together into TEXTNAME and executes the Function Module alongwith other values (Language, TextId, TextObject) to get the Longtext lines through the Table LINES of the Function Module.

     

    Now let’s execute the FM READ_TEXT by filling these values.

    6.JPG

     

    See what we got

    7.JPG

     

    The FM READ_TEXT has given us all the 4 lines present in the Operation2 text . Now our ABAPer would use this info in his code for long text report.

     

    Hope things are clear.

     

    Further:

    The values of TextId, TextObject vary as to which SAP object the Longtext belongs, so as the constituents of TextName field value also. Here I am attempting to tabulate few such examples  of SAP-PM area for the benefit of members.

     

    Long Text Associated withTEXTID

    TEXT

    OBJECT

    TEXTNAME parts*Remarks
    Notification Header TextLTXTQMELQMNUM (Notifn no )
    Item Text in Catalogs&CodesLTXTQMFEQMNUM + POSNRPOSNR from  VIQMFE table
    Cause Text in Catalogs&CodesLTXTQMURQMNUM + QURNUMQURNUM from  VIQMUR table
    Task Text in Catalogs&CodesLTXTQMSMQMNUM + QSMNUMQSMNUM from  VIQMSM table
    Activity Text in Catalgs&CodesLTXTQMMAQMNUM + QMANUMQMANUM from  VIQMSM table
    PM order Header TextKOPFAUFKClientNo + AUFNR (Order)
    Measuring DocumentLTXTIMRGMDOCM (Document no)

     

    *The QMNUM, AUFNR values should be preceded by the leading zero's (like 004300093626)

     

    Easy retrieving of Longtexts in Smartforms

    The information so far is more relevant to ALV reporting (though it works for smartforms also). In Smartforms, there is a convenient way of retrieving long texts, i.e., through include text. We declare the text type as Include text which gives us the provision of filling the TEXTNAME, LANGUAGE, TEXTID, TEXTOBJECT etc. As the the loop runs the TEXTNAME changes according to the SAP object number the respective longtext is retrieved. In the picture below an example for Notification Longtext in smartforms is given.

    sf.JPG

     

     

    Related technical info

    There is a table named STXH which stores the Text Header details. Here you get the number of text lines in the long text upon inputting the field values such as TDID, TDOBJECT, TDNAME etc. The following Selection screen (SE16) and the output are self explanatory .

     

    Capture.JPG

    Capture1.JPG



    So, that's everything on this subject, which I had been thinking of documenting for the benefit of the forum, since sometime. Hope members find it useful.

     

     

    Thank you

    KJogeswaraRao

     

     

    PS: Members mght now have understood that though PM Objects have been illustrated here, this post applies to Longtexts of other module objects also.


    A Number range is a Group of numbers to which the unique-Id created for an SAP Object belongs. In each module we have masterdata having SAP objects such as Equipment, Notification, Order, Measuring Point, Maintenance Plans etc in PM, Material number, Material Document, Purchase Requisition, Purchase Order in MM, Sales Order, Sold-to-party etc in SD, Production Order in PP, Inspection lots in QM and the list is long. This document is intended to give basic concepts of Number Ranges we need to create during the Configuration of various modules in the implementation time and after. In this document we try to understand these things through a Plant Maintenance object, namely Equipment.

     

    Before starting our job related to Equipment, let’s understand few generic things about Number Ranges.

     

    Types of Number Ranges

    There are 2 categories of number ranges:

    Internal numbers:  These are purely numbers. System generates the number (within the range you’ve specified) next to the immediate previous allotted number.

    External numbers: This is where the person creating the SAP object (e.g., Equipment) is required to enter his choice of number. This will be as per the alpha-numeric pattern he has already declared while creating the number range.

     

    T-Codes

    There are configuration paths in each module for respective objects to Define respective number ranges. Also many objects have Tcodes. Here we see the Tcodes for Defining number ranges in PM module .

     

    SAP-PM ObjectTcode

    Equipments

    OIEN

    Notification

    IW20

    PM Order

    OION

    Maintenance Tasklists

    OIL0, OIL4, OIL5

    Maintenance Plans

    IP20

    Maintenance Items

    IP21

    Measuring Points

    IK09
    Measuring DocumentsIK19
    RevisionDIWPS_REVNRS

     

     

    Let’s first see the Internal Number Range

    We know that there are different categories for each SAP object.

     

    Few examples:

    SAP ObjectCategory
    EquipmentEquipment Category
    NotificationNotification Type
    Maintenance OrderOrder Type
    Measuring PointMeasuring Point Category

     

    In the number ranges configuration-screen you get these Categories, where you need to assign this category/type to a particular number range group. Where from these Groups come? These Groups are nothing but the Number ranges we need to create. One Number range group for one or more Categories of SAP Object, (i.e., Equipment in present case). See this picture:

    1.JPG

     

    Here Groups are Test, Standard Number range, Mechanical Equipment, Electrical Equipment, Instrumentation.  Under each group different categories of Equipments are seen.

     

    Now let’s start how to create a new internal number range for an Equipment and assign few categories to it.

     

    Tcode OIEN

    2.JPG

     

    Click on the Groups icon. to arrive at the picture referred in the beginning.  Here you use the menu GoTo --> Insert OR

    hit F6 function key to get this pop-up

    3.jpg

     

    Now, Give a title to the Group (Say Demo), give some number range say 000000000010000000  to   000000000019999999  to the Group and upon clicking the Add icon, system might give you the following error messages, telling that this range is interfering with some other Group already existing. i.e., some overlap between.

    olap.JPG

    (In case no such overlap is there, then the Group will be created)

     

    Assuming that overlapping is there, identify the overlapping Group, tick-in the checkbox and go to the maintain screen like below.

    5.jpg

     

    6.JPG

    See here upper range 000000000019999999  has been modified as 000000000014999999.

     

    Means we have freed numbers from 000000000015000000 to  000000000019999999. Now again GoTo  --> Insert and repeat the New Group (Demo) creation. Now it will be accepted.

    7.JPG

     

     

    Thus,we have created a Group named Demo. See this is visible in the list of Groups.

    8.JPG

     

    Now we will try to assign one Equipment category to our new Group.Let’s suppose, we want to shift Category G Equipments to this new Number Range.  For this follow this procedure.

     

        1.Mouse click on the Category G in the present position where it is .

          

        2.Tick the check box of the target Group, here it is Demo like this

          

        3. Then click on these icons in these sequence (first 1 and then 2)

         

    Now your Category G is there in the Group Demo.

     

     

    Everything has been done. Now the Category G Equipments when created through IE01 will be given the numbers specified here.

     

    Let's learn about Few clicking sequences for Assigning and Not Assigning the Categories to Groups.

     

    Case1: Unassigning a Category from any Group.

    Let’s suppose I want to unassign Category H . Means I want to bring it to the Not assigned list at the bottom. Follow this mouse click sequence.

    13.JPG

     

    Means

        1.Click on letter H (Remember the checkbox of this Group should not be ticked-in)

        2.Then click on the icon at the top.

        3. Then on Not Assigned at the bottom

          

     

       4. Then on icon at the top.

     

    You’ll find the letter H is in the Not Assigned list like this.

    14.JPG

     

     

    Case2: Assigning a Category from 'Not Assigned' to any Group.

    Let’s suppose we want to assign Category T to Group Demo .

     

    Follow this Mouse click sequence shown here.

    18.JPG

     

    Means

         1.Click on the letter T in the Not Assigned list

         2.Then click on the icon

         3.Then Tick the Checkbox of group Demo

         4.Then finally on at the top.

     

    You’ll find the Category T has been assigned to group Demo.

    19.JPG

     

     

    Now let see the External number Range.

    The process is almost same except for you’ll be providing Character format for number range.  A typical External number range format can be AAAAAAAAAAAA – ZZZZZZZZZZZZ. Here even you use numbers they are treated as characters. In case you need have Alpha Numeric then you can have ranges like 01AAAAAAAAAA – 99ZZZZZZZZZZ. Here first 2 places will be having numeric features. You can make use of characters like / also.

     

    Important:

    For alphanumeric external number ranges in Equipments you need to have the following setting in the SPRO of Equipment Categorisation.

     

    Path:

    20.JPG

     

    Setting

    21.JPG

     

    See,  for Alpha numeric number Ranges the Checkbox under column a should not be ticked-in.

     

    Note:

    Though concepts were explained with Equipment number as example, there is an identical dealing with all other number ranges, irrespective of which module does it belong to.

     

    Also few members might be thinking of Tcode SNRO.  Well, that is a different subject. SNRO creates a Number Range which can be used in fields like Order Text, Notification text etc.  through a FM known as 'NUMBER_GET_NEXT' , during the situations of auto-numer generating.

     

    So friends, that’s about the Number Ranges from my side. Hope members find this post too useful.

     

     

    Thank you

    KJogeswaraRao

    In the very early stages of implementation, several years ago, standard reports and processes were not satisfying the needs of customers. To fulfill the process needs, I started exploring use of User Exits ( as mentioned in several blogs ). Like-wise for missing fields in standard reports, I opted for Queries and begun to learn this. One of such very early custom reports has been discussed here where I had to make a Z version of IW28.

     

    The Specifics of the need

    The need arose, when management wanted to compare the Preventive maintenance hours spent on a critical machine with the Breakdown Hrs for certain period of operation. We have in IW28 the Breakdown Hrs only , field AUSZT (usually M2 notifications), but not any field giving this duration for M3 Notifications i.e., Preventive Hours. I remember this triggered my Technical journey.

     

    The Action

    Built a Query based on Infoset using tables VIQMEL and CRHD as shown below (CRHD table is required in case we want Main Work Center in the output, otherwise VIQMEL alone is sufficient.

    join.JPG

     

    An o field MntHr (Prevetive maint Hrs) was created in Extras and the following code was given in the code section.

    MntHr.JPG

     

    You might have understood that we maintained the Start/end Details of M3 Notifications in the Required Start/End Date/time fields ans we wanted the duration of these time stanps.

     

    And, we designed this report with the field we computed Mnt(Hr) and the standard field BDn(Hr) adjacent to each.

     

    report.jpg

    So this task has been fulfilled. The Tcode given was ZIW28,

     

    Then after sometime, we taught customers, how to use the Create Notification menu in the Action Box of a Notification, which in return given rise to another such report requirement. User wanted a report where both Extended Notification (QMNUM) and the Reference (Parent) Notifications (QWRNUM) are available. Though these two fields are part of VIQMEL table, the standard IW28 is not having this Reference Notification number (QWRNUM) field.

     

    So with a similar Infoset as that of first case, I created a report required which as under. (In this case there is no need of Additional fields & calculations). Here is the report.

    rep2.jpg

     

    The first report was very significant for analysis of maintenance functions and so it is very much called (hyper linked) by several other custom reports.

     

    This post is just to share about another common SAP situation, where Infoset queries came to rescue. Forgot to tell you that I named the 2nd report (Tcode) as ZIW28A.

     

     

    Thank you.

    Jogeswara Rao K

    Actions

    Filter Blog

    By author:
    By date:
    By tag: