Customise ESS BP

[Former Member]

Hi All,

I have a very small confusion; your quick response

will be of much help!!!

I have (NWDI) track with ESS BP imported in it, now

if I need to enhance SAP provided functionality will I

modify do customizing with the standard SC in the track

and this will directly affect the standard ESS role/iView

in portal.

I think we should not follow the above said process and

alter the standard iView in the standard ESS role.

If we think the above point is correct, then can any one

please tell me how I should proceed enhancing the standard

ESS webdynpro DC?

Without effecting any thing in standard ESS role and create

new iView in my PCD folder as per the enhanced WDP application?

Thanks,

SJ

[Former Member · Accepted solution]

Sushil,

The right way to do is to have 2 tracks...one for modifications ...and one kept unchanged for backup and comparison later on....

For your second query....iviews and Webdynpro DC's are 2 separate things so if you modify the webdynpro code through NWDI ...both standard and custom(if you copy) will pickup the same code residing in NWDI DTR...but it's recommended to create copy of the standard ESS iviews and role so that you change it's properties and do some personalization...

Shikhil

[Former Member · Accepted solution]

Hi

Thanks for the reply!!!

Now considering a scenario where I have

brought ESS/COD application to NWDS via NWDI.

If i enhance COD app.. add few UI elements to it,

and check in the code again to DTR and deploy the

application on Portal.

1 .When I look at standard ESS COD iView, I will

see the enhanced COD application (correct me if I am right)?

2. If I donu2019t want to disturb COD application that ESS standard

COD iView is using, what is the process I should follow?

I understand --> I will have to ask Portal admin to create a copy

of existing track and if I do any changes to COD WebDnP application

though the newly created track and check in the code and then deploy

to Portal, this will not effect the COD standard application and iView.

Then I will have to create new iView and access enhanced COD application.

_____________________________________________________________________

My requirement is, I have to enhance few ESS WD App... and the

enhancement should not disturb any thing in the standard ESS role,

how do I achieve this?

Thanks for all your time.

Cheers,

SJ

[Former Member · Accepted solution]

Sushil,

1 .When I look at standard ESS COD iView, I will

see the enhanced COD application (correct me if I am right)? --- yes you are right

2. If I donu2019t want to disturb COD application that ESS standard

COD iView is using, what is the process I should follow? --- there is no such process,without disturbing standard one,you cannot do

I understand --> I will have to ask Portal admin to create a copy

of existing track and if I do any changes to COD WebDnP application

though the newly created track and check in the code and then deploy

to Portal, this will not effect the COD standard application and iView.

Then I will have to create new iView and access enhanced COD application.

_____________________________________________________________________

My requirement is, I have to enhance few ESS WD App... and the

enhancement should not disturb any thing in the standard ESS role,

how do I achieve this?

There is no way in java to create a copy of DC without disturbing the standard code

Thanks

Bala Duvvuri

[Former Member · Accepted solution]

Sushil,

Both the standard and the copied iviews will point to the same Webdynpro Application....so any changes in webdynpro will be reflected to both of them .....and as Bala said there is no way to create a copy of the standard webdynpro DC and make modifications to it....

Shikhil

[Former Member · Accepted solution]

Hi Guys,

Thanks for all your reply's.

I will try to get little more info on this topic and mark the thread as resolved.

Cheers,

Sushil Jain

[Former Member · Accepted solution]

Hi Bala,

for your point in Bold... please look at the blog below.... do you thing we can follow this for ESS enhancement?

[https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3096] [original link is broken] [original link is broken] [original link is broken];

[Former Member · Accepted solution]

I was also in impression like ....

If I simply copy the original SC from track for e.g. ESSERVIC to another track for e.g. ESSCUSTM and start customizing from ESSCUSTM.

I could achieve this.......

I am sorry for extending this thread; i just need to be 100% sure before moving ahead with the enhancements...

Cheers,

Sushil Jain

[Former Member]

Hi,

Yes, its right we have to modify the standard BP. There is no other option. I have got this detail written in NWDI Cook Book for XSS...

I mark this thread as resolved...

Cheers,

Sushil

FROM : NWDI Cookbook for XSS

Customers

Motivation: why this guide?

When XSS source-code delivered by SAP is modified by customers, the import of the next support

package will result in conflicts (between the modified customer versions and the new SAP

versions). While NWDI supports merging of source files through text-based merge tools, the

Web Dynpro elements that are in conflict require model-based merge tools (which can merge

logical objects spanning multiple files). These model-based merge tools are not yet available.

Hence, NWDI recommends an alternative process that will help customers avoid a situation

where un-resolvable conflicts are created after the import of a Support Package. This guide

describes this alternate process of configuring and using the NWDI landscape.

This guide will explain the track landscape and the process how to adjust the modifications during

the update/upgrade process.