Show TOC Start of Content Area

Procedure documentation Using Business Objects from the Enterprise Services Framework  Locate the document in its SAP Library structure

Use

Web Dynpro is the user interface technology for applications using data out of an Enterprise Services Repository. Using the Web Dynpro model interface, the user directly connects against an SAP system which contains the repository with business object nodes and compound service interfaces. The Enterprise Services Model is the interface to an Enterprise Services Framework backend. The resulting Web Dynpro model classes can be used to consume the service data within a Web Dynpro application or a user interface building block. Initially, a Visual Composer Language model is exported from a Visual Composer development server.

Prerequisites

      Java Engine including Visual Composer and Development Server are installed, same is true for Developer Studio

      Knowledge of system information for the backend system which contains the Enterprise Services Repository you have to use data out of

      Generic display user for the backend system

      Detailed knowledge about backend object data

      Web Dynpro Project with Web Dynpro Development Component is available

Procedure

       1.      From the model importer, choose EnterpriseServices Model.

       2.      To create the model interface from a service module definition in an SAP backend that means if the business objects are stored in an SAP backend, select the corresponding option from the import wizard. For import of business objects from Visual Composer, select the Visual Composer import option and browse to the file system.

       3.      For the import of SAP backend business objects, you only need to select the objects you want to generate the model for. Using Visual Composer objects, you pick the exported *.vcl.zip file and logon to the Enterprise Service Repository system.

       4.      Analyse the export log, especially the warnings issued regarding suppression of colliding names, e.g. aggregations and associations colliding with property names or property names colliding with base class names.

End of Content Area