Component Customisation - EAMS_WDA_ORDNTF_OIF error

[#1]

Hi

Looking for some help with this please. I am trying to customise Change Maintenance Order WDA app in S/4HANA Public Cloud, and when entering the customisation prior to even trying to do what I am intending there are multiple errors as per screen shot. Has anyone tried to customise this and had these issues, if so how did you resolve?

My intention is the hide the "Create Follow-on Order" from the Additional Functions dropdown, doing this as the restrictions around work order type do not stop a user from creating YA02 in any app, this is just to remove the ability from this app.

Thanks

Chris

[AndreasMuno]

Hi Chris,

thanks for the detailed explanation and the screenshot.

From your description and the error list, two things stand out:

• You’re in the WDA configuration for component EAMS_WDA_ORDNTF_OIF (Change Maintenance Order).
• Even before you apply your actual change, you already see several FPM/Floorplan Manager errors, including:
  • “The name contains invalid characters, valid characters are A‑Z, 0‑9, _, and /”
  • “UIBB key is not valid (Component FPM_LIST_UIBB_ATS, Config ID EAMS3_WDC_DIR_LINK_LI_CFG, Instance ID …)”
  • “Error at instantiation of component FPM_LIST_UIBB_ATS with config ID EAMS3_WDC_DIR_LINK_LI_CFG”

1) First isolate / clean up the existing configuration errors

Before trying to hide Create Follow‑on Order, I’d try to verify whether these errors are:

• Already present in the standard configuration, or
• Introduced only when you start working with your custom configuration (copy / Z‑config).

Some checks you can run:

1. Open the standard configuration again without any custom copy
   • If the same “UIBB key is not valid” and “invalid characters” errors already appear, then there may be an inconsistency in the delivered configuration, and that needs to be clarified first (e.g. via internal analysis or SAP channels), before doing any enhancement.
   • If the standard config is clean and the errors only show after working with your own config ID, then the issue is very likely in your custom configuration name or in a referenced UIBB key.
2. Re‑check the IDs you entered manually
   • The error text explicitly says: “valid characters are A‑Z, 0‑9, _, and /”.
   • Double‑check that:
     • The configuration ID you are using (and any child UIBB configuration IDs) only use these characters, and
     • There is no leading/trailing blank or hidden character in the field (sometimes this can trigger “invalid name” symptoms).
3. Verify the UIBB configuration actually exists and is active
   • For FPM_LIST_UIBB_ATS with config ID EAMS3_WDC_DIR_LINK_LI_CFG, check in the FPM / Web Dynpro configuration tools that:
     • This configuration is present,
     • It is active, and
     • It is reachable from your main component configuration (no typo in the key).

If the UIBB configuration is missing or inactive, the framework will typically raise exactly the sort of “UIBB key is not valid” instantiation errors you are seeing.

2) Approaches to hide “Create Follow‑on Order” in S/4HANA Cloud Public Edition

Your functional goal is to prevent users from creating YA02 follow‑on orders from this WDA app, because document type restrictions don’t fully protect you.

On S/4HANA Cloud Public Edition in general, the recommended direction is to prefer standard configuration, authorizations, and clean‑core extensibility over deep UI framework changes. 

With that in mind, you basically have these options:

1. Authorization / role-based approach (if there is a suitable auth check behind the action)
   • If the Create Follow‑on Order action is tied to an authorization object or business role (e.g. users who cannot create YA02 at all), that is usually the cleanest solution.
   • In that case you’d:
     • Make sure only a dedicated role can create YA02, and
     • Remove that role from users who should not see/use this capability.
2. UI-level hiding via configuration / personalization (if exposed by the framework)
   • In some WDA / FPM applications, toolbar or menu actions can be hidden through:
     • Configuration of the toolbar schema / action schema, or
     • Switching off the corresponding UIBB / action in the FPM configuration.
   • The errors you are seeing need to be resolved first, though – otherwise your configuration is in an inconsistent state and further changes may not behave predictably.
3. Re‑evaluate whether a different, more “cloud‑aligned” app could be used
   • SAP’s guidance for S/4HANA Cloud Public Edition is to:
     • Use standard processes and apps as far as possible and
     • Limit heavy UI framework modifications, especially in classic technologies, to reduce upgrade risk and rework. 
   • If there is a Fiori app or alternative process where you can control the follow‑on creation more cleanly (e.g. via restrictions and app-level authorizations), that may be easier to maintain over time.

3) Suggested next steps you could try

Given what we can see from the screenshot only:

1. Clarify the baseline:
   • Confirm whether the standard EAMS_WDA_ORDNTF_OIF configuration is error‑free.
   • If errors exist even in the standard, resolve those first.
2. Check your custom config IDs / keys:
   • Ensure all IDs involved in your copied configuration (main component config + any UIBBs for FPM_LIST_UIBB_ATS) use only A‑Z, 0‑9, _ , / and actually exist.
   • Correct any typos or recreate the configuration if necessary.
3. Once the config is clean, try hiding the action:
   • Look for the toolbar / action configuration entry that corresponds to Create Follow‑on Order and try setting it to “not visible” (or remove it from the schema), if the framework allows that.
   • After the change, test with a business user role to make sure the option is really gone and there are no side effects.

If you can share whether you copied the configuration or changed the standard, the community might be able to give more targeted hints or screenshots of a working config.

---

Note on AI assistance
This answer was prepared with the help of an AI assistant based on publicly available SAP guidance and your question text, and should be double‑checked against your system configuration and official SAP documentation before applying in a customer environment. 

If this response helps you move forward, please consider marking it as accepted so others with a similar question can find it more easily.