cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 
Read only

Phase control possible between phase 5&6??

Egbert_de_Jong
Participant
0 Likes
340

Hi All

We are live in sap4hana public cloud since 1/5/25 and use EAM to the max

Our consultant highlighted we can not have phase control between phase 5&6. As a result we have 

- 1 phase control which is overkill

- 1 phase control we DO want but do not have (teamlead approval of WOs before PRs are issued/wo is released)

I read everywhere (e.g. below) you can just add phase controls. Can someone confirm this and are there nuances we should be aware of (e.g. linked to C&P process, PR to PO process)?

https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/asset-management-in-sap-...

Accepted Solutions (1)

Accepted Solutions (1)

dawid90
Active Participant

Dear @Egbert_de_Jong,

Yes in Public Cloud you can add more phase control codes and use them to put a gate between phase 5 & 6. Your consultant is right that you can’t change the phases themselves, but you can configure extra phase control codes to block the transition at that point and use them for team-lead approval.

The phase model is predefined and cannot be changed you can’t insert a new Phase 5.5.

For phase-based orders you can use phase control codes to control the movement between subphases/phases. If a phase control code is active, the system won’t let the order move to the next subphase/phase until that code is removed.

More details below:

https://community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/phase-control-codes-for-...

You wrote: ā€žteamlead approval of WOs before PRs are issued / WO is releasedā€

In standard phase-based maintenance:

  • The order flows through the 9 phases
  • PRs for external services/non-stock materials can be configured to be created either when the order is saved or when it is released.

To make team-lead approval a hard gate before PRs and release, you typically combine:

  1. Phase control codes
  2. and PR creation trigger set to order release, not order save.

Activity in CBC- Define Phase Control Code for Maintenance Orders(103676):

Define Authorization Keys

Create an auth key for team leads, for example:

dawid90_0-1763383029618.png

Assign Entities to Order Types:

dawid90_1-1763383029619.png

 

Define Phase Control Codes

For Order Type = YA01, Entity = Order Header create:

  • Phase Control Code: TLA
  • Description: Team Lead Approval
  • Authorization Key: TLA
  • Initially Active, so every new YA01 order starts with TLA active on the header

dawid90_2-1763383029619.png

Define Phase Controls

  1. Phase control key = Block
  2. Process Phase: choose Scheduling.
  3. Process Subphase: choose Ready for Scheduling (Order).
  4. Subphase Description will fill automatically.

Effect

  • With TLA active on the header:
    • the system will not allow the order to move into Scheduling / Ready for Scheduling (Order)
    • Planners can work through Preparation (phase 5), but they cannot submit the order to Scheduling (phase 6) until someone removes TLA.

This is exactly your gate between phase 5 and 6.

Alternative:

  • App Manage Workflows for Maintenance Orders

https://fioriappslibrary.hana.ondemand.com/sap/fix/externalViewer/#/detail/Apps('F4989')/S35

  • You can configure an approval step for certain order types/plants/values.
  • When an order is submitted for approval, it gets system status ORAR (Order Approval Required) and cannot be released until approved

Workflow is often nicer for business users because they get tasks in My Inbox instead of hunting for orders with a certain phase control code.

Best Regards,

Dawid

 

 

Egbert_de_Jong
Participant
0 Likes
@David90 - thanks for the elaborate answer, much appreciated - this really helps! i assume btw you took into account SAP Public Cloud and not just SAP Private
dawid90
Active Participant
0 Likes
Yes, 100% Public Cloud

Answers (0)