I am implementing the ESS Address service for UK, system Portal 7.0, business package ESS 1.41, ECC 6.0 (EnhP4).
why do I need to specify the 'URL of PCD page' for my resource EMPLOYEE_ADDRESS_UK_SERVICE_13?
the resource object EMPLOYEE_ADDRESS_UK_SERVICE_13 is already pointing to the correspondent web dynpro object sap.com/essgbaddr/Per_Address_GB_13, so why does SAP need the URL of PCD page? isn't web dynpro object enough??? the web dynpro objects are unique anyway.....
Thanks,
Tiberiu.
>
Tiberiu Sasu wrote:
> I am implementing the ESS Address service for UK, system Portal 7.0, business package ESS 1.41, ECC 6.0 (EnhP4).
> why do I need to specify the 'URL of PCD page' for my resource EMPLOYEE_ADDRESS_UK_SERVICE_13?
>
> the resource object EMPLOYEE_ADDRESS_UK_SERVICE_13 is already pointing to the correspondent web dynpro object sap.com/essgbaddr/Per_Address_GB_13, so why does SAP need the URL of PCD page? isn't web dynpro object enough??? the web dynpro objects are unique anyway.....
>
> Thanks,
> Tiberiu.
Hello Tiberiu,
in case the Homepage Framework is embedded into a Portal only the PCD Object is used. In this case a Portal-Navigation is triggered to call the resource object based on its PCD-Location. Just in case the Homepage Framework is in standalone mode, the Web Object matters.
So basically if you always call your Homepage Framework within a portal you can leave the Web Object Field empty.
regards,
Markus
Hi Markus
thank you for responding to my question. Just our of curiosity, what is a typical 'standalone' implementation of Homepage framework (one that does not use SAP Portal)?
Regards,
Tiberiu
>
Tiberiu Sasu wrote:
> Hi Markus
> thank you for responding to my question. Just our of curiosity, what is a typical 'standalone' implementation of Homepage framework (one that does not use SAP Portal)?
>
> Regards,
> Tiberiu
The standalone mode has no pracical value these days, as you need a Portal to run the Java-based Self Service Applications anyway.
The Homepage Framework was originally introduced with ERP 2004 (Netweaver 2004). At this time the ESS Web Dynpro Components didnt need a portal, just a plain SAP Netweaver 2004 (6.40) Java Stack.
regards,
Markus