'Update Order user-status upon Save of Notification or Order' : Obviously we are talking about linked Notification and Order Scenario.

Dear Friends,

To my approximation I gave around 150 enhancement solutions so far while answering the queries. Among these I felt like documenting few (7 so far) because of their complex and interesting nature. I felt that the present one too is of similar nature and forum will be benefited if it is presented in the form of a technical blog.

So here it is:.......

It is about a recent call for help, where the member was seeking solution for her requirement which was expressed as:  "When particular Task  is open in the Notification, how to update the user status in IW31/32 on Service Order . Please Suggest." .

I felt this is another opportunity to contribute few lines of enhancement code to the forum. I gave the solution ie., the user-exit and the code. The code reads the System status of the Notification, if it finds OSTS (outstanding task) then it sets a specific user status (say ABCD) to the Order, obviously during Save (of Order as the requirement sounded).

The member then clarifies like: "No no, I do not want during Order Save, It to happen while Notification Save".  Then I gave that solution too, other user-exit, and corresponding code obviously.

So here we are going to see both the solutions for

1. Updating Order User-status during Order Save if Notification has outstanding tasks. (user-exit IWO10009,  F/exitEXIT_SAPLCOIH_009)
2. Updating the Order User-status during Notification Save if Notification has outstanding tasks. (user-exit QQMA0014,  F/exitEXIT_SAPMIWO0_020)

Before we see the individual solution codes for both of these, let's first look at the logic.

• The start point is to know whether any outstanding Task is there in the Notification. This means Notification system status will have OSTS value.
• To know this we need to use function module STATUS_READ. The input to this fm is Notification OBJNR value which we get from QMEL or VIQMEL table.
• But the output from the above fm will be in code (not in text format OSTS). We need to know this code for our coding. This is known from table TJ02T when we input value 'OSTS' in the field 'TXT04'  and 'E' in field SPRAS. We get the value as 'I0158' . (This common for you, me and for all others)
• So in the code we need to tell to update the Order status to 'ABCD' if the Notification user status code is 'I0158'.
• We need to use function module 'STATUS_CHANGE_EXTERN' to update the Order user-status.
• This fm works OBJNR value of Order as input which is
  • Readily available as a field in the Import structure (caufvd_imp) of the user-exit if it is case1 above
  • Need to get it from table AUFK if it is case2..
• But this fm too needs code only not the text of user status (ABCD) to set it in Order. So how do we get it?
• We get it from table TJ30T by inputting the Status profile of Order in field STSMA, value 'ABCD' in field TXT04 and value 'E' in field SPRAS. Let's assume we got this as 'E0004'.
• Now we are ready for coding.

If it is the case1, ie., Updating Order User-status during Order Save if Notification has outstanding tasks, we need to put the following code in include ZXWOCU07.

And the code is:

DATA:i_stat  LIKE jstat OCCURS 0 WITH HEADER LINE,

      l_objnr TYPE j_objnr.

SELECT SINGLE objnr FROM viqmel INTO l_objnr WHERE qmnum = caufvd_imp-qmnum.

CALL FUNCTION 'STATUS_READ'

   EXPORTING

     objnr       = l_objnr

     only_active = 'X'

   TABLES

     status      = i_stat.

LOOP AT i_stat.

   IF i_stat-stat = 'I0158'.

     CALL FUNCTION 'STATUS_CHANGE_EXTERN'

       EXPORTING

         objnr       = caufvd_imp-objnr

         user_status = 'E0004'

         set_inact   = ' '.

   ENDIF.

ENDLOOP.

If it is case2: Updating the Order User-status during Notification Save if Notification has outstanding tasks, we need to use the code below in the include ZXQQMU20.

The code is:

  DATA:i_stat  LIKE jstat OCCURS 0 WITH HEADER LINE,

        l_objnr TYPE j_objnr.

   SELECT SINGLE objnr FROM aufk INTO l_objnr WHERE aufnr = i_viqmel-aufnr.

   CALL FUNCTION 'STATUS_READ'

     EXPORTING

       objnr       = i_viqmel-objnr

       only_active = 'X'

     TABLES

       status      = i_stat.

   LOOP AT i_stat.

     IF i_stat-stat = 'I0158'.

       CALL FUNCTION 'STATUS_CHANGE_EXTERN'

         EXPORTING

           objnr       = l_objnr

           user_status = 'E0004'

           set_inact   = ' '.

     ENDIF.

   ENDLOOP.

Note:

• Though already mentioned in the logic points above, I want to remind about the 'E0004' code used in the codes above. you have to get this value from table TJ30T by inputting your Order status profile in field STSMA, the user-status to be set in Order in field TXT04 and  'E'  in field SPRAS.
• Both the codes I tested before posting to that discussion. If you are going to use, test well for its satisfactory working in the Dev servers.

.....And thus we arrive at the end of this post..

Thank you and Regards

KJogeswaraRao

Friends,

This subject is one, which is a frequently asked nature and the documentation of which is pending from my side since long. When I rebuilt the first infostructure (S070) around 3years ago, my learning started on this subject.  As you know learning does not happen in a single stroke, it took considerable time to know about various aspects of LIS rebuilding. I had been replying to queries within the knowledge I had. I delayed documenting of the same until now, with an objective of content enrichment. This post might not be touching 100% aspects on the subject, but I know that this is the requirement zone of most of the SAP-PM user / consultant.

So the objective is to

Share my knowledge about how I rebuild SAP-PM infostructures whenever need arises.

I understood the LIS tables this way:

• LIS, namely the Logistic Info Structureis atable having rows with aggregated values of data from regular tables.
• Means, when users create Notifications, each Notification data is stored in tables such as QMEL, QMFE, QMSM, QMUR, QMMA and so on, as one row for each Notification. Similarly in case of Orders the data is filled in tables AUFK, AFIH, AFVC, AFRU and so on. These are the regular tables I am referring to as.
• Now about how the LIS is related to these tables? For example my QMEL table is having 10,000 rows of Breakdown Notification, which were created on say 100 Equipments, then the related LIS namely S070 will be containing the summery data for these 100 Equipments month-wise. Means here the rows will far less than 10,000, because these give Equipment-wise totals for a period. Hope you could follow.
• And then, how this LIS table is filled? Beginners often expect to see the data changes in LIS related tcodes (PMIS reports in our context) as soon as a Notification attains NOCO. But it does not happen so. A standard LIS update frequency is set via tcode OMOS which usually is Monthly. We can change it to as frequent as Daily in these settings. (But it is a rare practice to alter).
• Here comes the need of Re-build. Suppose there is a business requirement in the last days of a month to see the upto-date PMIS reports on Breakdowns like MCJB, MCJC, MCI4 etc. including the current month then, I will need to update the LIS S070 manually. In such case the present post helps.
• And most importantly, the rows of a LIS with version value '000'  only are considered for the PMIS reports. (This applies to LIS based reports of other modules also)

The Objects of Re-building Infostructure in SAP-PM:

The tcodes involved here are OLPM  and  OLIX .

Before we see what these tcodes are about, we see the LIS list relevant to SAP-PM. These are:

(Expecting not to receive any queries here on specific LIS of the above list, as this is not the present topic)

OLPM

• OLPM is a tcode used to set-up a version for PM Infostructures whose list is shown above. Now we see what is a version in LIS table:
• A version is a 3char field in the LIS table. Rows with version value '000'  are meant for reports. In the process of rebuilding, often we create temporary versions with values like '&(0' , '&(1' .  I repeat here, for PMIS reports only the rows with version value '000' matter. There is no role of rows with version values other than '000'  those are existing in the LIS table.
• Coming back to OLPM tcode, it is a tool to set up a version --> A temporary version or a reports version ('000').

OLIX

Then tcode OLIX is used to:

• Delete a version from a Infostructure. (Option Copy version)
  
• Copy a source version to a Target version. (Option Delete version)
• Copy a source version to a Target version and at the same time delete the source version. (Option Copy + delete)

NOTE:

OLIX tcode is common across LIS of all SAP modules for the purpose of above listed functions, but OLPM is exclusively for SAP-PM and every LIS of other modules will have its own tcode equivalent to OLPM.

Now about How the LIS is re-built

Suppose I am in a situation already described as an example in the beginning, where I can not wait for OMOS scheduled update of LIS to happen and I need to do it manually say for LIS S070. (Another example situation can be an inconsistency in PMIS reports, which could force you to re-build the LIS).

Step1 OLPM

• Save under version : We gave temporary version name &(0 . In case rows already existing in LIS with this version value, system asks you whether to delete, you should accept this OR you should give a new version name such as &(1 .
• Number of Parallel processes: Put value 1 here.
• Block all documents : Better Tick this to prevent creation of more data by users during this re-build, which would not reflect in the PMIS reports. For example during this run with with this Tick, if you create any Notification it will be prevented from Saving by throwing an error message like this:

(It is a different mater that, such Notification numbers are lost forever. You will not find this Notification number in the system. And the next successful Notification number will be a number next to this number. )

• Now Execute .
  

My experience here is that this step is the time consuming one. My system takes about 90 to 120 min for this task where the related tables have around 2000K records. Then it displays the information like this one.

Step2 OLIX

Now you are ready with a Temporary version records to be copied to Final version namely '000'.

• As a first step here, use the Delete version option > Give value '000'  in the field > Give value '000' in the Source version and Execute. With this act you are deleting all '000' rows from the LIS. If this is not done your present rebuild will double the statistics in the PMIS reports.
• Now come back to the initial screen of OLIX and click on Copy + delete. In the next screen ensure that you have &(0 your temporary version in the Source version field and 000 in the Target version field. See this picture.

• NowExecute .

This step will not take much time (under 5 min). You get information similar to the above picture in the case of OLPM.

That's all, the Re-build is complete.

Note:

I have experimented the following way by reducing the role of OLIX.

• First I deleted the version 000 using OLIX.
• Then I executed OLPM in the same manner as explained above buy with Save under version as '000' . This means without creating a Temporary version and copying it to Target version '000' in OLIX, we are creating '000' directly using OLPM.
• I found no issues.
• But it is believed that above mentioned procedure of Temporary version Copying to '000' version using OLIX is believed to be the Best practice.

I think the job is done and it is time to stop.  Hope members will be benefited with this write-up.

Here is a related post after knowing the above concepts:  Hierarchical Equipment Availability Calculations on F/Locns

Regards

KJogeswaraRao

Hi All,

Within this blog,I intend to share in brief on "Business Process Master List" in SAP PM. This will guide on how to prepare a BPML and it will be useful to all.

With Regards,

PS R

https://blogs.saphana.com/2016/06/21/sap-esri-user-conference

SAP is attending the Esri User Conference and showcasing spatial solutions - also in the business context of SAP EAM. Please read this blog.

this  brief blog is dedicated to EAM planers who often miss the capability to copy components within the plant maintenance order.

This has been an missing quite some time and is available Now within the EAM Web User Interface.

This new feature is all about simple user Interaction and ease of use with the following benefits

• No retyping of vendor specific attributes like contract number , contract item , supplier
• No retyping of user / order specific attributes unloading point, recipient
• No retyping of component longtext

via this new features planers can now work more efficiently.

You find this new feature  in Innovation Discovery under the Innovation

"Enterprise search" functionality plus Master Data Information Center within the SAP Enterprise Asset Management solution"

here you find:

• Demo
• Screenshot
• PDF Document summarizing the innovations and how to activate

i hope you enjoy this new feature

thanks

Stephan

Hello

as you are aware within EAM we are using extensively the enterprise search capabilities

you find these within Innovation Discovery

• Enterprise search functionality and a master data information center within the SAP Enterprise Asset Management solution
• Usability improvements in the SAP Enterprise Asset Management Solution

As we got quite some questions from the customers how to set up Enterprise Search we now created an How To Guide which hopefully answers most of your questions how to set up / improve  this powerful search to suite the users need

How-To Guide Enterprise Search in EAM

thanks

Stephan

Digital Transformation in Asset Management – Connect, Collaborate, Predict, and Simulate

Join us in The Hague on November 3–4, for a unique mix of SAP solution insight, real-life customer case studies, and networking opportunities with experienced practitioners from a diverse range of asset intensive organizations.

We are delighted to announce that the agenda for the International SAP Conference on Asset Management is now available for download. The unique format of this event allows you to meet with business leaders and learn from a diverse range of SAP customers, such as Trenitalia, Dong Energy, German Railways (DB System GmbH), and Royal Dutch Shell to name a few. Download the agenda now.

For the first time, this year’s conference will be part of the International SAP Conferences on Extended Supply Chain, featuring six co-located SAP conferences covering environment, health and safety, product lifecycle management, manufacturing, supply chain, and portfolio and project management. Register for one conference and move freely across all six.

Event highlights include:

• Strategic insight and road maps from SAP industry executives plus guidance and expertise from solution management at SAP
• The chance to learn from a diverse range of customers through business-focused case studies
• A vibrant exhibition that will feature valued SAP partners, live demos, and the opportunity to meet privately with our executive team and global solution experts
• A networking and evening event providing an opportunity to network with peers, SAP leadership, and valued partners
• Dive deeper into the topics during the pre-conference workshops, on the morning of Thursday, November 3, to gain a comprehensive understanding of the solutions available, best-in-class approaches, and useful takeaways

This annual event presents a world-class networking and learning opportunity.

Registration is now open. Be sure to secure your place now and remember, registration for one event gives you the opportunity to move freely across our International SAP Conferences on Extended Supply Chain.

Please feel free to contact the event team at info@tacook.com or +44 121 200 3810 should you have any questions.

We look forward to seeing you and your colleagues in The Hague!

Around the world, OEMs and equipment operators are investing in advanced automation technologies with the hope of reducing downtime, lowering costs, and accelerating operations. Among other things, production equipments can work fast and accurately, and they never need a coffee break.

But whether you’re using the latest automation technology or you still rely on human know-how, your operations come to a standstill when equipment goes down. As more manufacturers embrace the Digital Economy, equipment maintenance and service only becomes more important.

The good news is that technologies and techniques available today are making predictive maintenance truly achievable — for OEMs and equipment operators with the foresight to implement innovative new strategies.

Replacing Best Guess with Big Data

In the past, manufacturers managed the maintenance and service of their production lines through experience and gut feel. After mass-producing the same product over and over, you got a sense of when things might go wrong and when equipment needed to be serviced.

But as manufacturing grew more complex and distributed, gut feel was no longer enough. You needed technology to help you move from best guess to best practice, inching toward preventive maintenance that set your operations on a fixed schedule of service and repair.

Yet in today’s Digital Economy — with its extended supply chains, individualized products, and requirements for true customer centricity— preventive maintenance is no longer enough. Successful asset operators are now moving to a more mature predictive maintenance strategy.

Predictive maintenance helps reliability engineers reduce maintenance costs and unplanned downtimes by predicting failures long before they happen. Analyzing large amounts of sensor data from equipment and merging that data with business information can yield insights never before possible.

What’s more, by augmenting existing service processes with remote diagnostics, equipment manufacturer can better understand root-cause failures and improve product quality. They can also deliver differentiating and higher-margin services to their customers.

For example, one SAP client transitioned from merely making equipment to offering equipment as a service in a pay-per-use scenario. In the past, the company made and sold industrial air compressors. Today, it still makes the compressors, but its primary offering is the compressed air itself. Rather than buy the machines, its customers pay for the compressed air the machines produce.

But the only way the company could implement this innovative business model is through remote service management. This approach optimized service processes to achieve competitive advantage and more profitable service revenues.

Another SAP client, a leading provider of transportation services, dramatically improved the reliability of train operations and thereby improved customer service. Today, the company combines IoT sensors to capture 700 terabytes (TB) of data with advanced analytics to define business rules that drive predictive maintenance processes. Expected result is the reduction of its €1.3 billion annual maintenance costs by at least 8 percent.

Integrating Data for Business Results

Imagine if you could achieve similar results in your organization. Fortunately, the technology to achieve these outcomes is increasingly available.

The cost of IoT sensors has decreased dramatically over the past few years. The wireless services to connect sensors with centralized data repositories are becoming commoditized. Cloud-based infrastructures, which minimize capital expenditures and rationalize operational expenditures, are available around the world. And an in-memory computing platform that enables real-time data analytics is becoming a business requirement across industries.

Manufacturers now need to integrate these technologies into their business processes. It’s not enough to implement technologies standalone and expect results — because operational data doesn’t necessarily tell you which actions to take to achieve transformational improvements. Integrating shop-floor data with business information and processes is where you can achieve real value.

At a tactical level, you can begin to automate parts replenishment and service dispatch, dramatically reducing maintenance costs and increasing uptime. At a strategic level, you can begin to achieve business insights that lead to processes and models that help you outmaneuver the competition.

Fortunately, predictive maintenance and service needn’t be a Bing Bang approach in which you bet everything on an uncertain outcome. Start by collaborating with your CTO, your lines of business, and your maintenance operations to identify specific use cases that will generate the most business value. As you gain experience, you can move on to projects that involve more complexity but that promise even greater results.

Objective :

The main objective of this blog is to explain how scheduling parameters influence on the calculation of the plan date in preventive maintenance - time based single cycle plan.

Scheduling Parameters:

we maintain the scheduling parameters for the single cycle plan directly in the maintenance plan as shown below

Scheduling Indicator is the basis for calculating the planned dates:

Time : The calculation basis for the month is always 30 days; all calendar days are counted. Example: Cycle 1 month, start of cycle July 9th results in a plan date of August 8th.

Time Key date:The calculation basis is the effective days of a month.Ex:Cycle 1 month, start of cycle July 9th results in a plan date of August 9th.

Time-factory calendar is the basis for the month is always 30 days; only the factory calendar days are counted. Ex: Cycle 1 month, factory calendar Saturday/Sunday/public holiday free,start of cycle July 9th results in a plan date of August 22nd. Selecting factory calendar as German standard 01.

Call control parameter

Completion requirement:If you select the completion requirement check box then the system will generate subsequent orders once the previous order has been completed.It will give a pop-up message like one which is shown below.

Scheduling Period:

It is used to create a preview of the pending maintenance dates. It gives the period of the preview in days,months, or years.For example if you want to have a preview for the entire 12 months for a maintenance plan set the scheduling period to 12 months. Below screen shots shows the scheduling period of a maintenance plan with a monthly cycle, a start date of July 9th and a scheduling period of 12 months.

                      Maintenance Plan with scheduling period

Call Horizon:

We use the call horizon to specify in percentage when an order should be created for a calculated maintenance date.The date as of which the order can be created is known as the maintenance call date. Following screen shots shows the behavior for a cycle plan of one month with 90%, 100% & 0% call horizon settings.

Above is the scheduling period with call horizon 90%

Above is the scheduling period with call horizon 100%

Above is the scheduling period with call horizon 0%

With 90% & 100 % settings, the scheduling list of the maintenance plan has the hold status.

In practice, If you want the call horizon to control the maintenance call directly, than set 0% for cycles which are shorter than one year and if cycles are longer than one year, set the call horizon to a high percentage value (>80%) to ensure that orders are not created too early and remain in the system too long.

I hope this blog will help & for any suggestions plz. feel free.

In part-II ,I am going to share on Data determination which includes shift factor, tolerance & cycle modification factor.

Thanks,

PS R