Additional cheks when status change SM 7.1

[Former Member]

Hi all!

I need to check:

When status of SMIN is setting to Confirmed, system checks if there is open SMCR to this SMIN is exist, then prevent saving with this status till all corresponding SMCR's are closed.

I think the better way is to coding in SMIN's BSP application... but don't know wich method is better for this.

Regards Dan

[Former Member · Accepted solution]

Hi,

you not required any coding, but with little customizing with the method SET_PREDOC this can be done.

SET_PREDOC usually involved in change request management, where you can close the CR automatically when the associated change document closed.

But I havent tried this with Incident management sceanraio.

By luck I got one below scenrio, please try out

http://scn.sap.com/thread/1311456

Thanks,

Jansi

[Former Member · Accepted solution]

Hello Jansi,

About closing CR automatically after change document closed, i have alrdy done this and its working fine.

And My SMCR do closing SMIN automatically.

But i wont not this now, I need do additional cheks:

for example:

Im in SMIN and setting status confirmed, so when i choose this status i want( immediately or after save ) system checks corresponding open transactions e.g. SMCR if there any open -> Stop processing with message e.g. "close all corresponding transactions" .

p.s. where do i find SET_PREDOC? searched in action profiles there is no such action...should i create it ?

Regards

Dan

[Former Member · Accepted solution]

Hi,

yes, SET_PREDOC is action name, , its available in 7.1 too

please check in spro -> solutiom manager -> capablities -> change management -> change management frame work -> actions o n chae reuest -> actions depending on status,

BTW,

If you already done auto closing, then select that particular action, define the condition for CR status.

if CR status is this, the set the doc status of Incident to this, else the other value? have you tried to set any conditions on the actions, which linking service desk ticket and change management ticket?

other way if you want to use coding, find the related fm. by setting the break point on the methods defined in the action.Please check out

Thanks,

Jansi

[Former Member · Accepted solution]

Hi,

Yes i tried working with Auto closing,

Transaction Type ZMCR

Status Profile   ZMCRHEAD

User status      E0006

Specify Required Status Values for Successor

proc. type = ZMHF    statprof ZMHFHEAD    min. status E0008

so now, if i try to close SMCR how do this work? i try it anyway...thanks...

about coding, i did found methods in BSP application in required view ... like DO_VALIDATE_INPUT or SET_LCSTATUS.

I wounder using SET_PREDOC is better than BSP application - enhancing ??

yeah and how do i find related fm. for e.g. in SMIN where statuses are setting by hands not by actions ?

Thanks

Dan

[Former Member · Accepted solution]

ahh and one thing i forgot...

Even in charm configuration, how do i prevent of closing e.r. ZMCR if i have 2 or more related ZMHF's ??

Regards Dan

[mich_vollmer · Accepted solution]

Hi Dan,

you define that via the minimal user status of the successor (in case of a RfC the change documents are the successors) customizing. It defines which user status the successors qualify to set a user status in the predecessor with SET_PREDOC,

Its in the IMG activity 'Make Settings for Change Transaction Types'

E0005 is the user status 'Implemented' for SMCR. It's set only if the follow on change documents have these user status....

Hope that helps...

best regards,

Michael

[Former Member · Accepted solution]

Hi Michael.

Yes its worked!! thanks. The reason was my Z-transaction...copied entries to Z from standard and ok now.

Last thing i need is to implement condition checks according  to status in IT service management for ZMIN( SMIN ) tr. type,

In charm configuration we can assign conditions to user-status is there a way to use this for SMIN tr. type?

The only way i know how to implement conditions is CONTAINER_PPF badi... but mb there is more ways??

p.s. question 50% answered now

Regards

Dan

[mich_vollmer · Accepted solution]

Hi Dan,

sorry I didn't answer but I was on vacation...I assume, you mean to use the ChaRM consistency checks, right? Or the PPF conditions?

The ChaRM consistency checks are part of the ChaRM framework which is implemented when you set the user status via PPF action, PPF implementation HF_SET_STATUS and the PPF F action implementation HF_CHECK_STATUS (which checks that the document is consistent).

In Incident Management, you set the user status directly in the document, not via PPF action.

But it is possible to set it via PPF action as well. You would need to customized a PPF action which sets the user status for your incident. As container element use USER_STATUS and the relevant E- user status. You can check how it is done in the SMCR action profile...

or was the question how to implement a user-status dependent PPF condition, meaning you already have a PPF action and want to make it user status dependent?

hope that helps...

Michael

[Former Member · Accepted solution]

Hi Micheal !

Thanks for response, was on vacation too.

Nope im not using PPF actions/conditions. I want insert some checks right after user changes status directly.

I mentioned that when you switching status, there some cheks e.g. consistensy and more.

My users alrdy trained to switch status manually, so PPF is not actual for me

Regards Dan

[mich_vollmer · Accepted solution]

Hi Daniyar,

in general there is the BADI 'CRM_ORDER_STATUS' where you can implement checks when the save is done. Bit I understand from a colleague there is some customizing implemented which checks for specific fields if they are filled before the status can be changed. Maybe that's enough already, depends on your requirement. I do not know the customizing as I am from the ChaRM area but could inquire if I know your requirement,

Michael

[Former Member · Accepted solution]

Hi Micheal, thanks for the badi. I think there is no standard customizing for this checks in my case.

But there is a couple solutions like BADI and enhancing crm web ui object t/c BSP_WD_CMPWB.

So thanks everyone, will try some of these.

Best regards

Dan

[Former Member · Accepted solution]

Hi Daniyar,

We've got the same required over here.

Can you quickly explain me how you've solved this check (SMIN only confirmed when all underlying SMCR are closed)?

Thanks in advance !!

Regards,

Pieter de Zeeuw

[Former Member · Accepted solution]

Hi Pieter de Zeeuw, sorry for delay

There is no standard customizing for this yet, we postponed this for next year.

The best solution is to Enhance BSP application that use SMIN ( or ZMIN ).

There you can write some ABAP in event e.g. ON SAVE. And more you can insert messages in top of the SMIN with links to SMCR's that not yet confirmed.

There is many solution e.g. Schedule Email notifications or insert it in to BADI e.g. CONTAINER_PPF

But best i think is enhancing BSP -  AIC_INCIDENT_H

view - AIC_INCIDENT_H/IncidentHeaderEF

If you need some instructions on how do it just ask ...

Regards Dan

[Former Member · Accepted solution]

Hi Readers

I have the same situation. Our users are confirming incidents (ZMIN) when Change Requests (ZZCR) are still open. Please post instructions on how to resolve this (i.e prevent users from confirming an Incident, if a follow-on document is still open.

If anyone can assist, please also advise how to 'un-confirm' an incident, so an administrator can confirm, or Reject the Change Request?

Thanks, Rob

[mich_vollmer · Accepted solution]

Dear Rob,

incident does not use the ChaRM Framework per default, meaning they set the user status directly.

And there is not customizing forbidding the user status to be set in case it's set manually. Only via the SET_PREDOC functionality which runs via the ChaRM Framework.

You could customize PPF actions with SET_HF_STATUS to set the user status via the ChaRM Framework. Some customers do that. Then it would be possible.But you have to change the user status field to display then, otherwise the user can change it there as well.

Best,

Michael

PS: You can use this customizing if you use the ChaRM Framework

[alex_koopman · Accepted solution]

Hi Michael, a year ago the requirement of closing an Incident only when all related RfC's are confrimed, was not implemented. Do you know whether this is now realized in SP10?

Regards, Alex

[Former Member · Accepted solution]

Hello, Dan!

I have the same requirements.
Could you explain how to make checking RfC status before incident close?

Thanks!

Yuliya

[former_member187281 · Accepted solution]

Good day:

I am planning to test Michael's Solution to change the document to confirm via ChaRM framework.  The challenge today is to add the Action button to the RfC.  I have to find that out.  However this will be time  consuming passing all statuses to Actions and creating all permutations.

Joyca Vernickt provides an interesting band-aid solution that basically still allows you to close the RfC with a warning or not error message at all.

Please check this out and thanks from here to Joyca for her quick assistance.

Regards,

Juan

[former_member187281 · Accepted solution]

We did not have to go that far from now.

Last week SAP released note 2191039 which resolves our problems in the sense that the ABAP code of the method they modified, checks if the predecessor is in status 'FINI'.  If it is, the code does not bother on checking more and conditions become true.  That is more or less.

https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F6465...

We tried and it works as expected.

Many thanks specially to Michael Vollmer.   I am just impress about the care from SAP.

Regards,

Juan