Change Request and Buttons missing when using custom Configuration

[former_member196830]

Dear experts,

I'm configuring the Vendor Like UI for MDG that uses the application BS_OVP_BP and configuration BS_OVP_SP_LVC.

I deep-copied BS_OVP_SP_LVC into a new one ZK_BS_OVP_SP_LVC and did no changes at all.

When the system is configured to use the original SAP configuration BS_OVP_SP_LVC everything looks OK:

and the Buttons and the Change Request section appear properly

The issue comes when I flip the configuration for the application to my newlly copied one:

in this case the actual webdynpro configuration opens, but the Buttons and the Change Request section are missing.

Is there anything I can do to have my configuration work properly and see the buttons and the CR section?

Am I missing something?

Thanks in advance,

Boris

[michael_theis · Accepted solution]

Hi Boris,

first of all you should consider that a copy of the UI configuration is not really recommended since you cut the rope to SAP delivered bug fixes for the user interfaces. These are not applied to copied UIs which meanst that you will have additional effort the synch your local copies.

Regarding your issue, you most probably missed the following: Referering to the how-to document on BP extension, an OVP consists of three parts:

[...] The main application configuration is BS_OVP_CU. Starting this application the overview page BS_CU_OVP is called with the application specific communicator setting as
defined in BS_OVP_CU. [...]

If you deep-copy the UI starting from the application configuration, this copy includes only the application and the UI configuration. You do not copy the communicator settings. One task of the communicator settings is defining how-to include the change request UIBB during runtime...

Best regards

Michael

[former_member196830 · Accepted solution]

Hi Michael,

You are right... that's what seems to be the issue in my case.

I don't really want to deep-copy the configuration, but I need to have two different screens appearing for the different roles. The initial Requestor screen should only contain a few of the screens, while the Master Data Specialist screen should have all the fields.

I currently have the Master Data Specialist screen with all the fields we need, but I'm looking for an easy way to have a simple screen for the Requestor.

The fact that I can specify different configurations for the CR step lead me to the conclusion that I can simply copy the configuration, simplify it and assign it to the initial submission step 00.

That's when I hit the issue.

Is there another way of approaching this instead of copying the configuration?

Thanks in advance,

Boris

[michael_theis · Accepted solution]

Hi Boris,

actually this use case should be covered using a combination of the lean vendor request and vendor like UI:

The requestor starting the change request uses the lean UI having just a few fields. Once the CR is submitted, all further steps are executed with the Vendor Like UI. This UI configuration change can be added to CR Types, using the step dependent UI configurations.

Is this not sufficient for your use case?

Best regards

Michael

[former_member196830 · Accepted solution]

Hi Michael,

What you are saying totally makes sense...

I'll try to reconfigure and simplify both screens and see where that will take me.

My mistake was that I started with the Lean Vendor UI and configured it to be the main screen that has the fields for all steps. That lead me to the need to have an even simpler screen that would serve for the initial request.

I'll reconfigure both screens as you suggested and have the Lean Vendor UI as my initial request step, and also simplify the Vendor UI screen to be the Data Specialist and Approver screen.

I'm sure that this will work as both screens in this case would be SAP standard ones and the CR section would appear there. Also the next releases would be compatible and work if we go through an upgrade.

Best regards,

Boris

[Former Member]

Hello Boris,

Did you solve this issue?

Even we have the same requirement of removing the CR_Section from the OVP application of MDG -material.

The requirement has no lean UI which needs to be displayed, Only one single UI which do not have the CR_SECTION itself and everyone have the same UI.

The issue is the buttons are missing when i hide the UIBB of CR_SECTION.

Is there any solution for this?

Thank you in advance.

Shaila.

[michael_theis]

Hi Shaila,

one task of the CR section is controlling the buttons. Therefore it is not recommended to remove the same. The CR is always a part of master data governance!

Best regards

Michael

[Former Member]

Hi Michael,

Thank you for your response.

So do we have any solution to atleast hide the UIBB for change request activity of 'create' ?

Regards,

Shaila.

[Former Member]

Hi Michael,

Can you please check my thread http://scn.sap.com/thread/3469202 for a different issue.

Thank you,

Shaila.

[former_member193063]

Hi Boris,

Refer the below link;

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

Thanks

Nikhilesh

[former_member196830]

Thank you for your reply Nikhilesh,

Unfortunately, in my case the Workflow is not yet triggered... I get that on the initial screen and I cannot even submit the request to the workflow as the button Submit is missing. Also the CR Description cannot be specified. I believe this is a different problem.

Regards,

Boris

[praveenkumar_kadi]

Boris,

Two things you may need to check if not already checked.:

1. MDG Config for action s to display on the screen.

Typically all those buttons are configured in MDG under below scetions  Define actions and step types

2. The UI Zconfiguration you created - basically you may need to check going to OVP config and in the section all the way down - toolbar scema, where you have degfault buttons assigned to that UI. check visibility etc.

Thanks

Praveen

[former_member196830]

Hello Praveen,

I checked those settings, but nothing there is related to using my copied configuration.

As I mentioned before, everything works just fine when using the standard SAP configurations like BS_OVP_SP_LVC, BS_OVP_SP or BS_OVP_SP_VL

If I copy any of them and set the system to use the new one, it also works, but misses the Change request section. I can't seem to find a solution to this, so I opened an OSS message.

Let's see where that takes us.

Regards,

Boris