here is information showing a fully functioning free energy generator.this is info you need to build it. its a kit. some people call it a bedini circuit or a ssg circuit. ssg stand for simpl…Full description
here is information showing a fully functioning free energy generator.this is info you need to build it. its a kit. some people call it a bedini circuit or a ssg circuit. ssg stand for simpl…Description complète
fiori
How to Enable Multi-Origin Capability in SAP FIORI Apps
Descrição: SAP Fiori
Fiori
Building SAP Fiori-like UIs With SAPUI5 in 10 Exercises
SAP UI5, SAPUI5, SAP Fiori, SAP HTML5, SAP OData, SAPUX, SAPX03, SAPX04, SAPX05, GW100Full description
SAP UI5, SAPUI5, SAP Fiori, SAP HTML5, SAP OData, SAPUX, SAPX03, SAPX04, SAPX05, GW100
SAP
Fiori
SAP Fiori SecurityFull description
Full description
SAP Fiori ArchitectureFull description
basics of fiori for non technical
FIORI Launch padFull description
UX215 - How to Build Fully Functional Fiori Apps Without Coding for SAPUI5 Gairik Acharya Technical Architect IBM
TOPICS 1
Scope
2
CDS View Concept
3
Annotation Concept
4
Development Steps
5
Detailed Steps
6
Further Links
SCOPE OF THIS SESSION In Scope
ABAP
CDS View based data modeling
Annotation
based
SAPUI5 application
Out of Scope
SAPUI5
based development
SAPUI5/Fiori
Application Enhancement
Fiori
Smart Template Application
Detailed explanation
on NW Gateway/OData
TOPICS 1
Setting the expectations
2
CDS View Concept
3
Annotation Concept
4
Development Steps
5
Detailed Steps
6
Further Links
CDS VIEW – CONCEPT •
Next generation of data definition and access for database-centric applications
•
Optimized application programming model for all domains
•
Technically an extension to SQL
•
CDS includes – Data Definition Language (DDL) – Query language (QL) – Data control language ( DCL)
CDS FAMILY
DDL •
•
Data Modeling and Retrieval Source Code based Editor
QL •
•
Consume CDS entities via Open SQL
Parameters can be passed to handle dynamic content
DCL •
•
Define authorizations for CDS View
Integrates with classic authorization concept
CDS VIEWS – DDL
TOPICS 1
Setting the expectations
2
CDS View Concept
3
Annotation Concept
4
Development Steps
5
Detailed Steps
6
Further Links
CDS ANNOTATION Add itional metadata
Annotation
can be evaluate d by ABA P Runtime, SADL or Analytic Engine
Starting from
7.5, there a re many types o f annotation s. UI, Search, Semantics, Odata, ObjectModel and Consump tion annotations are relevant for this sessio n
mostly
TOPICS 1
Setting the expectations
2
CDS View Concept
3
Annotation Concept
4
Development Steps
5
Detailed Steps
6
Further Links
DEVELOPMENT STEPS : PREREQUISITES SAP Neweaver Version
7.5 SP01 and above
Database
Any
ADT
WEB IDE
HANA Cloud Connector ( HCC )
SAP_BC_DWB_ABAPDEVELOPER
SAP_BC_DWB_WBDISPLAY
/IWFND/RT_DEVELOPER
ABAP CDS Views
BOPF programming model ( for transactions scenarios)
OData Service using the transaction /IWFND/MAI NT_SERVICE
Smart Template application
and navigation in the launchpad designer
Add Semantics Link the CDS views with
Define the
annotations
associations Add Search or
relationship between various data sources Determine the number of
any other annotations**
levels/hierarchy Plan for final
In CDS Views,
number of fiori apps to be created
use annotation to create OData Service ( use tx SEGW) if multilevel CDS views, use SEGW to create OData
Add additional
annotations if required
Test the
OData Service
Adjust
Mainfest.json file if required Adjust the
translations( i18N) if required Deploy the app to
UI5 repository
Test the app in
fiori Launchpad (use Launchpad url )
TOPICS 1
Setting the expectations
2
CDS View Concept
3
Annotation Concept
4
Development Steps
5
Detailed Steps
6
Further Links
DATA MODELING Data Modeling
Define CDS View
Add Annotation
Activate ODATA Serv.
Create Smart Template
Configure Launchpad
Requirement : Create 2 fiori applications. First one should display the list of Customers and second one will display list of sales orders with header, items, partners and schedule lines. 2 apps can be run individually or one can navigate from the customer list to sales order list.
Data Sources 1. 2. 3. 4. 5.
Cus tom er Mast er Sales Ord er Header Sales Order Header Sales Order Item, Sales Order Partner Sales Ord er Ite m Sales Ord er Schedul e line Sale s O rd er Part ne r Sale s Ord er Sc he dul e lin e
DETERMINE CDS VIEWS Define CDS View
Data Modeling
Add Annotation
Activate ODATA Serv.
Create Smart Template
Configure Launchpad
Requirement : Create 2 fiori applications. First one should display the list of Customers and second one will display list of sales orders with header, items, partners and schedule lines. 2 apps can be run individually or one can navigate from the customer list to sales order list.
CDS Views and Association 1. 2. 3.
Cus tom er Mast er Sales Ord er Hea der
[0..*] Sales Orde r Header [1..*] Sales Ord er Ite m, [1..*] Sales Ord er Partne r
4. 5. 6.
Sales Order Item [1..*] Sales Order Sched ule line Sale s O rd er Part ne r Sale s Ord er Sc he dul e lin e
DEFINE CDS VIEWS – LIVE DEMO Data Modeling
Define CDS View
Add Annotation
Activate ODATA Serv.
Create Smart Template
Configure Launchpad
Live Demo
Customer
Sales Header
Sales Item
Scheduled Line
Partner
IDENTIFY LIST OF ANNOTATIONS REQUIRED Data Modeling
Define CDS View
Add Annotation
Activate ODATA Serv.
Create Smart Template
Configure Launchpad
Requirement : Customer Data , Sales Order Data should display in list table and will have the possibilities of configuring columns to be displayed. There should be filter criteria for each screen. Count should be displayed. Currency key should be linked to the amount fields. Displaying sales value for each sales area using a chart will be a bonus. A rating indicator would be helpful based on sales order value. Additionally, we want to configure some of the drop-down help to be configured from an existing custom table. For navigation, more than one customers can be selected to view the sales orders for all of them
Required Annotations 1. @UI. Line ite m for li st tab les , nav iga tion 2. @UI.selectionField to determine filter 3. @UI. Cha rt to dis pla y chart 4. @O bje ct Mod el Valu e he lp 5. @Seman tic s Cur ren cy fields 6. @OD ata OData ser vic e creation** *
*** If you have multi level CDS associations ( e.g., header item scheduled lines ), t hen OData service should be created using SEGW and not using annotation
APPLY BASIC UI ANNOTATIONS– LIVE DEMO Data Modeling
Define CDS View
Add Annotation
Activate ODATA Serv.
Create Smart Template
Configure Launchpad
Live Demo
Customer
Sales Header
Sales Item
Scheduled Line
Partner
APPLY MORE ANNOTATIONS– LIVE DEMO Define CDS View
Data Modeling
Add Annotation
Activate ODATA Serv.
Create Smart Template
Additional Annotations 1.
@UI. Identif icatio n
2.
@UI. Cha rt
To displa y inform ation in the object view page
3.
@Ob jec tMod el
4.
@Semantics
5.
@Objec tModel
6.
@UI.se lectio nField
7.
@UI. line item.t ype ( #FO R_ACTIO N ) for defining Action button
SMART TEMPLATE-LIST REPORT & OBJECT VIEW Data Modeling
23
Define CDS View
Add Annotation
Activate ODATA Serv.
Create Smart Template
Configure Launchpad
CREATE SMART TEMPLATE Data Modeling
Define CDS View
Add Annotation
Activate ODATA Serv.
Select the name and Title
Create Smart Template
Select the backend system and OData service
Configure Launchpad
Select the Annotation ( should automatically be selected )
Select the Entity Set and if required navigation property
Follow-on (Optional )Actions Adjust local annotation file to change the display/navigation Adjust manifest.json file for navigation or other configuration
APPLY ANNOTATIONS– LIVE DEMO Data Modeling
Define CDS View
Add Annotation
Live Demo
Activate ODATA Serv.
Create Smart Template
Configure Launchpad
CONFIGURE LAUNCHPAD Data Modeling
Define CDS View
Add Annotation
Activate ODATA Serv.
Create Smart Template
Configure Launchpad
1.
De ploy t he a pp f ro m WE B ID E to SAPUI5 repository
2.
Not e do wn t he a pp n ame an d the component name
