how to create fpm based on sadl using act - sap q&a · how to create fpm based on sadl using...

SAP NetWeaver

How-To Guide

How To Create FPM Application consuming CDS view using ACT

Applicable Releases:

SAP NetWeaver AS ABAP 7.4 SP5

Target Audience:

FPM Developers

Version 1.0

February 2014

i

© Copyright 2014 SAP AG or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP AG and its affiliated companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and other countries. Please see http://www.sap.com/corporate-en/legal/copyright/index.epx#trademark for additional trademark information and notices.

SAP NetWeaver “How-to” Guides are intended to simplify the product implementation. While specific product features and procedures typically are explained in a practical business context, it is not implied that those features and procedures are the only approach in solving a specific business problem using SAP NetWeaver. Should you wish to receive additional information, clarification or support, please refer to SAP Consulting.

Any software coding and/or code lines / strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or grossly negligent.

Disclaimer:

Some components of this product are based on Java™. Any code change in these components may cause unpredictable and severe malfunctions and is therefore expressively prohibited, as is any decompilation of these components.

Any Java™ Source Code delivered with this product is only to be used by SAP’s Support Services and may not be modified or altered in any way.

http://www.sap.com/corporate-en/legal/copyright/index.epx%23trademark

http://www.sap.com/corporate-en/legal/copyright/index.epx%23trademark

ii

Document History

Document Version Description

1.00 First official release of this guide

iii

Typographic Conventions

Type Style Description

Example Text Words or characters quoted from the screen. These include field names, screen titles, pushbuttons labels, menu names, menu paths, and menu options.

Cross-references to other documentation

Example text Emphasized words or phrases in body text, graphic titles, and table titles

Example text File and directory names and their paths, messages, names of variables and parameters, source text, and names of installation, upgrade and database tools.

Example text User entry texts. These are words or characters that you enter in the system exactly as they appear in the documentation.

<Example text> Variable user entry. Angle brackets indicate that you replace these words and characters with appropriate entries to make entries in the system.

EXAMPLE TEXT Keys on the keyboard, for example, F2 or ENTER.

Icons

Icon Description

Caution

Important

Note

Recommendation or Tip

Example

iv

Table of Contents

1. Scenario ................................................................................................................................ 1

2. Background Information ..................................................................................................... 1

2.1 Application Creation Tool (ACT) ................................................................................... 1 2.2 Service Adaptation Definition Language (SADL) and Business Entities ...................... 1 2.3 Core Data Services (CDS) for ABAP............................................................................ 1 2.4 Data Model of Sample Application ............................................................................... 2 2.5 Output of the Sample Application ................................................................................. 2

3. Prerequisites ........................................................................................................................ 3

4. Step-by-Step Procedure ...................................................................................................... 4

4.1 Creating a FPM Application using ACT (with CDS view as business entity model) .... 4 4.1.1 Opening Application Creation Tool (ACT) ....................................................... 4 4.1.2 ACT Step 1 – Enter Floorplan Objects ............................................................ 6 4.1.3 ACT Step 2 – Set Business Entity ................................................................... 7 4.1.4 ACT Step 3 – Join Associated Entities ............................................................ 7 4.1.5 ACT Step 4 – Define UI Structure .................................................................... 7 4.1.6 ACT Step 5 – Assign Package and Transport Request .................................. 8 4.1.7 Executing the application ................................................................................. 9

4.2 Modifying Application, Component and GUIBB Configuration ................................... 11 4.2.1 Remove Search Component ......................................................................... 11 4.2.2 Add the Result List Component ..................................................................... 12 4.2.3 Wiring the components .................................................................................. 15 4.2.4 Changing the Titles and the Panel Rendering Types for the components .... 20 4.2.5 Changing Chart Component Configuration.................................................... 21 4.2.6 Changing GUIBB List Component Configuration .......................................... 24 4.2.7 Executing the application ............................................................................... 27

5. Appendix ............................................................................................................................ 27

5.1 Appendix A – Abbreviations ....................................................................................... 27 5.2 Appendix B – Calculating Dunning Levels for Sales Order Invoices .......................... 28 5.3 Appendix C – References ........................................................................................... 28

5.3.1 ABAP Development Tools Tutorials - Learn how to use ABAP in Eclipse .... 28 5.3.2 The NetWeaver Enterprise Procurement Model - An Introduction ................ 28 5.3.3 Creating FPM Applications with the ACT ....................................................... 29 5.3.4 Creating FPM Applications based on SADL Entities using the ACT ............. 29

5.4 Appendix D – Link to ABAP for SAP HANA Reference Scenarios ............................ 29

How To Create FPM based on SADL using ACT

March 2014 1

1. Scenario

After reading this guide, you will be able to create a Floorplan Manager (FPM) application consuming Core Data Services (CDS) view. The application will be created using Application Creation Tool (ACT). ACT allows you to create the complete application declaratively, i.e., zero coding, thereby significantly reducing the efforts. This guide will assist you to:

Create a FPM application using ACT

Consuming Core Data Services (CDS) view as data model

Adding Charts to the FPM Application by changing the FPM configurations

2. Background Information

2.1 Application Creation Tool (ACT)

The Floorplan Manager (FPM) Application Creation Tool (ACT) significantly reduces the effort involved in creating a new FPM application.

The tool itself is a Web Dynpro application, provided by FPM, which allows application developers to create FPM applications and their corresponding configurations for all available Floorplans (OIF, GAF, and OVP).

The ACT also allows you to create applications for adaptable FPM components, that is, it allows you to create context-based adaptations for your application.

2.2 Service Adaptation Definition Language (SADL) and

Business Entities

The Floorplan Manager (FPM) framework contains several application wizards to create various types of FPM applications. There is a wizard for creating FPM applications based on Service Adaptation Definition Language (SADL) entities. This wizard creates a simple application consisting of a search page, that is, a page containing a section for the search criteria and a section for the search results. The wizard also helps the FPM developer to add charts to the UI.

SADL is a framework, which enables consumption of different business object models, and other entity-based models, in particular DDIC tables and views, in a uniform way. Detailed knowledge of the modeling frameworks, such as Business Object Process Framework (BOPF) or (Business Object Layer) BOL is not required; the SADL entity model provides all the required information to the UI. In ACT, SADL entities are known to be Business Entities.

With SADL, it is possible to push down queries directly to the database itself, thereby improving response cycle times, and, with suitable databases, very large amounts of data (millions of records) can be retrieved and displayed quickly.

.

2.3 Core Data Services (CDS) for ABAP

Core Data Services (CDS) enhance SQL to allow defining and consuming semantically rich data models, thereby improving consumption, performance and interoperability. CDS simplifies and harmonizes the way you define and consume your data models, regardless of the consumption technology. CDS in ABAP provides you with a data definition language (DDL) for defining semantically rich database tables/views (CDS entities) and user-defined types in the database.

For several years for now, it is possible to define views in the ABAP Dictionary, but these views are quite restricted. For example, you can only define inner join for database views. Outer joins are available only for help and maintenance views. However, it is not possible to perform aggregations in views or define nested views. With ABAP 7.4 SP05, a new editor is available to define views directly in


March 2014 2

the Eclipse-based ABAP development environment. With this Source-based editor you can define CDS entities, which can be consumed in ABAP programs using Open SQL.

The CDS View building provides another way of code pushdown using features that are similar as in Open SQL. With CDS View building it is possible to define

1. Projections, aggregations, and groupings

2. Use expressions (like CASE), SQL built-in functions

3. UNION and UNION ALL and non-equi INNER JOINs

4. Nesting of Views with associations between the View entities (associations can be consumed in the WHERE clause as well as in expression in Open SQL queries)

2.4 Data Model of Sample Application

Before getting started, you must generate data related to Enterprise Procurement Model (EPM). You can use the transaction SEPM_DG_OIA to generate the data for EPM model. For more information about EPM, see http://scn.sap.com/docs/DOC-31458

For creating the application, use the CDS view SEPM_CDS_OPEN_INVOICE_REDUCED. This CDS view fetches all the Open Sales Orders – Sales Orders whose payment is yet to be made by the Buyers. Buyer Name, Dunning Level, Overdue Invoice Amount, Currency are some of the details retrieved for each of the Sales Order. Each Sales Order can have one or more Sales Order Items and the invoice amount can be in different currencies. For a given Sales Order ID the data is grouped by Currency and the aggregated invoice amount is displayed.

2.5 Output of the Sample Application

At the end of this guide you will be able to create an FPM application which looks similar to following screenshot:

The table below provides description for each marked section/functionality:

Number Description

1 This panel displays a pie chart showing the number of open sales orders for each of the Dunning Levels. You can drill down to find more details for a given dunning level. Upon selecting a particular dunning level in the chart; it filters all the Buyers with

http://scn.sap.com/docs/DOC-31458


March 2014 3

Number Description

Open Sales Orders belonging to the selected dunning level as shown in section 2. Also, section 3 displays those Open Sales Orders with the selected dunning level.

2 This panel displays a pie chart showing the Buyers with Open Sales Orders of the selected dunning level in section 1. On initial load, only the chart with dunning level as in section 1 is displayed. When you, as an Account Receivable Accountant, click on any slice of the Dunning Level pie chart, this chart is displayed. It displays only those buyers who have Open Sales Orders with the selected Dunning Level. It is also used to filter down the Open Sales Order list further. When you select any buyer from this chart, list displays only those Open Sales Orders which belongs to the selected buyer as shown in section 3.

3 This section displays all the Open Sales Orders, grouped by sales order ID. This section also displays Buyer Name, Current Dunning Level, Currency, and Gross Amount. A Sales Order can have one or more sales order items in different currencies. The list displays the total overdue amount grouped by currency for a given Sales Order ID.

4 This list will display the Open Sales Orders grouped by Sales Order ID and hence only Sales Order ID is displayed by default. Expand the list to see more details such as Buyer Name, Currency, and Gross Amount. Also, as explained above the sales order list is controlled by the filtering as applied in section 1 and/or section 2.

When the application is initially launched the following information is displayed:

The chart shows the number of Open Sales Orders grouped by Dunning Level.

The list displays all the Open Sales Orders.

When one of the sectors of the Dunning Level chart is selected, the application enables the following drill down:

The Buyers chart shows all the Buyers with the Open Sales Order of the selected Dunning Level.

The list displays only the Open Sales Orders with the selected Dunning Level.

When one of the sectors of the Buyers chart is selected, further drill down is enabled:

The Open Sales Orders in the list is further filtered based on the selected Buyer.

The list displays only those Open Sales Orders with the selected Dunning Level and for the selected Buyer.

With ACT, it is possible to create or model the above FPM application with zero coding.

3. Prerequisites

1. Knowledge of FPM

2. SAP NetWeaver (NW) version 7.4 SP5 or higher is installed

3. Knowledge of working with ABAP Development Tools (ADT)

4. Knowledge of NW Reference Scenario, Enterprise Procurement Model (EPM) will be useful

5. Knowledge of ABAP Core Data Services (CDS) and CDS View Building will be useful

6. Using ADT, connect to the ABAP system and create an ABAP project in the Project Explorer [ABAP Perspective]. Refer to this link to follow step- by- step process http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10e2502e-29f4-2f10-ab9a-d34504de3ed7&overridelayout=true

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10e2502e-29f4-2f10-ab9a-d34504de3ed7&overridelayout=true

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10e2502e-29f4-2f10-ab9a-d34504de3ed7&overridelayout=true


March 2014 4

4. Step-by-Step Procedure

4.1 Creating a FPM Application using ACT (with CDS view

as business entity model)

4.1.1 Opening Application Creation Tool (ACT)

1. Create the application either in the $TMP packageor in the package of your choice.

2. Right- click the package.

3. Choose New>Other ABAP Repository Object.

4. In New ABAP Repository Object wizard, choose Web Dynpro > Floorplan Manager Application.


March 2014 5

5. Choose Next.

6. In the Type list, choose the application type as Wizard for Creating FPM Apps Based on Business Entities.


March 2014 6

7. Choose Finish.

The Application Creation Tool (ACT) appears in the editor area, displaying Step 1.

4.1.2 ACT Step 1 – Enter Floorplan Objects

1. Enter Web Dynpro Application name as OPEN_ITEM_ANALYSIS.

2. Choose Apply Namespace and enter your preferred namespace. (namespace is optional). For our sample application, you can enter namespace as ZSAP_. As soon as you enter the namespace as ZSAP_ and choose OK, you will see that Web Dynpro Application name is changed to ZSAP_OPEN_ITEM_ANALYSIS. Also, the wizard will automatically provide the name for Application Configuration and Floorplan Configuration as ZSAP_OPEN_ITEM_ANALYSIS. (Optionally, you can also change the Application Configuration and Floorplan Configuration names). Enter a suitable description wherever asked in the Step 1 Screen.

3. Choose Next to proceed to Step 2 of ACT.


March 2014 7

4.1.3 ACT Step 2 – Set Business Entity

1. In the Business Entity Source list, choose Core Data Services.

2. In the Business Entity field, enter SEPM_CDS_OPEN_INVOICE_REDUCED. (You can also search for the CDS view using F4/search help also).


4.1.4 ACT Step 3 – Join Associated Entities

For this application, there is no action required in this step. This will be required when you want to have associated entities also in the view. For example, if you have chosen Data Dictionary as Business Entity Source and SFLIGHT as Business Entity in the previous step of Setting Business Entity then this current step of Joining Associated Entities would have shown you all the other entities in the association hierarchies. You can then choose the associated entities that you need in the FPM application.

For the sample application referred in this guide, as already mentioned, no action is required in this step.

Choose Next to proceed to Step 4 of ACT.

4.1.5 ACT Step 4 – Define UI Structure

In this step, you need to provide configuration details for the Search Component and Result List Component. Additionally, you can also add the Chart Component. (You need to add two chart components for the sample application).

1. Enter the Search Component Configuration Name as ZSAP_OIA_SRCH_CFG and provide a suitable description.

2. Enter the Result List Component Configuration Name as ZSAP_OIA_RES_LST_CFG and provide a suitable description.

3. Choose Add Chart button to add a chart component.


March 2014 8

4. Enter the Chart Component Configuration Name as ZSAP_OIA_DUN_LVL_CFG and enter a suitable description.

5. Enter the Chart Title as Dunning Level.

6. Enter the Dimension as DUNLEV_DESCR. This field of the CDS view provides descriptive text to the Dunning Level and to the Sales Order Invoice Header (SNWD_SO_INV_HEAD) field CURRENT_DUNNING_LEVEL. In the CDS view, the descriptive text is fetched from dunning level text table SEPM_OIA_DUNLEVT.

7. Retain the Measure as FPM_SADL_CHART_COUNT. This is an auto generated field, which helps to determine the count of a particular field in the output structure. In this case it helps to determine the number of Open Sales Orders with a given Dunning Level.

8. Choose Add Chart button to add another chart component.

9. Enter the Chart Component Configuration Name as ZSAP_OIA_BUYER_CFG and provide a suitable description.

10. Enter the Chart Title as Buyers.

11. Enter the Dimension as COMPANY_NAME.

12. Retain the Measure as FPM_SADL_CHART_COUNT. This is an auto generated field, which helps to determine the count of a particular field in the output structure. In this case it helps to determine the number of Open Sales Orders for a given Buyer.


4.1.6 ACT Step 5 – Assign Package and Transport Request

1. In this step, you have to assign Request/task. As our sample application is being created in $TMP, no action is required in this step.


March 2014 9

2. Choose Save.

A success message appears that Web Dynpro application and configuration were successfully created. In addition to the message, two links are also provided. One for editing the configuration using Flexible UI Designer (FLUID) [Link Text – Edit Configuration (FLUID)] and other link for executing the application itself [Link Text - Execute Application].

To view all the ACT created FPM artifacts, expand the $TMP package in the Project Explorer to view (You may have to refresh the package to see the objects under the package).

4.1.7 Executing the application

1. To execute the application, you can either choose the link Execute Application OR right-click FPM Application Configuration ZSAP_OPEN_ITEM_ANALYSIS in the Project Explorer and choose Run As > Web Dynpro ABAP Application.

2. The application is launched inside ADT. It will have search criteria, a result list, and two charts. Initially no data will be loaded. Choose Search button to see result and two charts. The UI will appear as in the screenshots below look as displayed in the screenshots below:


March 2014 10

The data may differ according to the data generation done using transaction SEPM_DG_OIA. In the screenshot above, the chart for Dunning Level displays only one level because the Dunning Levels are not calculated for the open sales orders. See Appendix B to understand how to run the Dunning Level calculation. [Running dunning level calculation is optional for this guide. It is only needed if you want to see multiple dunning levels in the chart as shown in the snapshot below.]


March 2014 11

The

4.2 Modifying Application, Component and GUIBB

Configuration

As a next step, modify the configurations generated in Step 4.1. As part of this step, remove the Search Component altogether and use the charts itself as filter criteria for the result list. Charts will be used like a drill down capability for the Open Sales Order list.

To get the end results as specified above, some minor changes must be done to the configurations.

4.2.1 Remove Search Component

1. Double- click the floorplan configuration ZSAP_OPEN_ITEM_ANALYSIS in the Project Explorer view. This will open the floorplan configuration in-place in ADT.


March 2014 12

2. In the component configuration page, choose Edit..

3. In Overview Page Schema tab, select the row with section FPM_SADL_SEARCH and choose Delete.

4. Choose OK to confirm the deletion.

4.2.2 Add the Result List Component

1. To add a section, choose


March 2014 13

In the Attributes of Section panel, enter the Section ID as OIA_LIST.

2. In the Overview Page Schema, select the row with Section ID OIA_LIST (if the row is not already selected), and add List Component UIBB to the section by choosing button UIBB> List Component.


March 2014 14

3. Enter Config ID for the List Component as ZSAP_OIA_RES_LST_CFG, using the Attributes of UIBB Panel. (This configuration was created when you were creating application using ACT in the Step 4.1.5)


March 2014 15

4. Choose Save.

4.2.3 Wiring the components

1. Choose the Wire Schema tab. Select all the rows that are listed down in Wire Schema list and choose Delete.

2. Choose Graphical Wire Editor.

3. If the SAP Graphical editor window appears, choose Run..


March 2014 16

[It may happen that the SAP Graphical Editor does not open in ADT because of issues related to security or any other problems. In that case, you can edit the floorplan configuration in browser itself by entering the link http://<ABAP_AS_Server_FQDN>:<port>/sap/bc/webdynpro/sap/configure_component?sap-language=EN&COMP_NAME=FPM_OVP_COMPONENT&CONFIG_ID=ZSAP_OPEN_ITEM_ANALYSIS&CONFIG_TYPE=00&CONFIG_VAR= in the Internet Explorer browser.]

You will get a Graphical Wire Editor as shown in thescreenshot below.

4. Using the Graphical Wire Editor, you can now specify the wiring between different components. Drag chart component ZSAP_OIA_DUN_LVL_CFG from the left side panel to the editor area.


March 2014 17

5. Drag chart component ZSAP_OIA_BUYER_CFG and list component ZSAP_OIA_RES_LST_CFG from the left panel to the main editor area.

6. Drag the Selection port of the chart component ZSAP_OIA_DUN_LVL_CFG to entry point of the chart component ZSAP_OIA_BUYER_CFG to connect the components.


March 2014 18

In the Connector Details window that appears,from the Connector Class list, choose the connector class CL_FPM_SADL_CONNECTOR .

7. Choose OK to complete the connection from the Dunning Level chart to the Buyer chart. This implies that on selection of any dunning level slice in the Dunning Level chart, the selection will be passed as filter criteria to the Buyer chart.


March 2014 19

8. Similarly, connect the Selection port of the chart component ZSAP_OIA_BUYER_CFG to entry point of the list component ZSAP_OIA_RES_LST_CFG. Choose the same connector class CL_FPM_SADL_CONNECTOR for connection. After connection, the Graphical Wire Editor appear as below:


March 2014 20

9. After wiring is complete, choose Done on the toolbar of the Graphical Wire Editor. This will close the Graphical Wire Editor and return to the component configuration of OVP floorplan component ZSAP_OPEN_ITEM_ANALYSIS.

10. Choose Save on the toolbar of the floorplan configuration. [After clicking on the Save button, you can close the browser, if you have been editing the FPM configuration in IE browser. Switch back to ADT.]

4.2.4 Changing the Titles and the Panel Rendering Types for

the components

1. Open the floorplan configuration ZSAP_OPEN_ITEM_ANALYSIS in ADT, if it is not already opened. To edit the configurationchoose Edit. For information about opening and editing, see first 2 sub-steps of section Remove Search Component.

2. Change the page Title to Open Item Analysis. This can be done in the Navigation tab in the left hand side panel.

3. In the Overview Page Schema tab in the main area, choose the row with the chart component with Config Id ZSAP_OIA_DUN_LVL_CFG. In the Attributes of UIBB section, select Rendering Type as With Panel from the drop down and set Title as Filter by Dunning Level.


March 2014 21

4. Change Rendering Type of chart component with Config Id ZSAP_OIA_BUYER_CFG to With Panel and set title for this component’s panel as Filter by Buyers. Follow the steps as mentioned in the previous step for other chart component.

5. Similarly, for the list component with Config Id ZSAP_OIA_RES_LST_CFG, change the Rendering Type to With Panel and set the title of panel as Open Sales Orders.

6. Choose Save on the toolbar of the floorplan configuration.

4.2.5 Changing Chart Component Configuration

The following sub-steps allow you to load the data when application starts itself.

1. In the Overview Page Schema tab in the main area, choose the row with the chart component with Config Id ZSAP_OIA_DUN_LVL_CFG.

2. Choose Configure UIBB n to go into the GUIBB configuration of the chart component.

3. Go to the General Settings tab and choose Feeder Class Parameters. The Edit Parameters dialog box appears.


March 2014 22

In the Retrieval list, choose Retrieve without request. Choose OK.


March 2014 23

4. Under Basic Settings tab (under General Settings), in the Selection Mode list, choose Single.


March 2014 24

5. Choose Save on the toolbar of the GUIBB component configuration of ZSAP_OIA_DUN_LVL_CFG.

6. Click the link OVP: ZSAP_OPEN_ITEM_ANALYSIS to go back to the floorplan configuration.

7. Repeat the above sub-steps of 2 to 6 for the GUIBB component configuration ZSAP_OIA_BUYER_CFG to bring about the same changes for the Buyer chart.

4.2.6 Changing GUIBB List Component Configuration

ACT provides default configurations during the creation of the FPM application. Use this section to change some of the default configurations such as changing the default title of the list data.

1. In floorplan configuration, in the Overview Page Schema, choose the row with the list component with Config Id ZSAP_OIA_RES_LST_CFG.

2. Choose Configure UIBB to go into the GUIBB configuration of the list component.

3. Choose Feeder Class Parameters under General Settings Panel to open the edit Parameters dialog.


March 2014 25

4. In the Retrieval list choose Retrieve without request.

5. Choose OK.

6. Choose Save on the toolbar of the GUIBB component configuration of ZSAP_OIA_RES_LST_CFG.

7. (Optional Step) Under General Settings:

i. Deselect the checkbox Table Is Search Result List.

ii. Remove text for Title.

iii. Deselect the checkbox Default ‘No Data’ Text.

iv. Enter No sales orders available for Custom ‘No Data’ Text.

v. Choose Enabled (Button in List Toolbar) from the drop down of Export to Spreadsheet.

vi. Choose Column Header for Filtering.

vii. Choose Sort and Group – Column Header for Sorting / Grouping.

viii. Choose Column Header for Aggregation.


March 2014 26

[Each Sales Order can have one or more Sales Order Items and the invoice amount can be in different currencies. Due to invoice amount being displayed in different currencies for each of the Sales Order, the user might want to see the list data grouped by Sales Order. Step 7 and 8 explains how to do the same]

8. In the General Settings toolbar, choose Default Sorting / Grouping from the the GUIBB Settings menu.

9. In the Sorting and Grouping dialog box, select the checkbox Group Column and choose Sort by as SO_ID. This will group the data by field SO_ID in the list.

10. Choose OK..

11. Collapse the panel General Settings and go to the List UIBB Schema tab.

12. Remove the rows with column headers DUNLEV_LANGU and DUNLEV_DESCR.


March 2014 27

13. Choose Save on the toolbar of the GUIBB component configuration of ZSAP_OIA_RES_LST_CFG.

4.2.7 Executing the application

1. To execute the application, either click on Execute Application link OR right- click on the FPM Application Configuration ZSAP_OPEN_ITEM_ANALYSIS in Project Explorer and choose Run As > Web Dynpro ABAP Application.

2. The application will run in the ADT. It will have two chart components displaying Dunning Level and Buyers and a result list. You can now run the application as mentioned in the section Error! Reference source not found..

5. Appendix

Appendi x

5.1 Appendix A – Abbreviations

Abbreviation Description

ADT ABAP Development Tools

EPM Enterprise Procurement Model

NW NetWeaver

ABAP AS ABAP Application Server

FPM Floorplan Manager

SADL Service Adaptation Definition Language

ACT Application Creation Tool

CDS Core Data Services

FLUID Flexible UI Designer

FQDN Fully Qualified Domain Name

IE Internet Explorer


March 2014 28

GUIBB Generic UI Building Block

UI User Interface

5.2 Appendix B – Calculating Dunning Levels for Sales

Order Invoices

If you want multiple dunning levels in the chart to be shown then run the reference FPM Application http:// <ABAP_AS_Server_FQDN>:<port>/sap/bc/webdynpro/sap/s_epm_oia?sap-wd-configId=S_EPM_OIA_ALVH in the browser and choose Run Dunning. This will calculate the dunning levels for Sale Order Invoices. If the sales orders are in different dunning levels then you can see multiple dunning level slices when you refresh the FPM app that you generated. To know more about this reference FPM Application, refer to the document on SCN at http://scn.sap.com/docs/DOC-47390 .

[The screenshot below refers to the reference FPM application, which must be launched to run the dunning run.]

5.3 Appendix C – References

5.3.1 ABAP Development Tools Tutorials - Learn how to use

ABAP in Eclipse ABAP Development Tools Tutori als - Learn how to use ABAP in Ecli pse


5.3.2 The NetWeaver Enterprise Procurement Model - An

Introduction EPM






March 2014 29

5.3.3 Creating FPM Applications with the ACT Creati ng FPM Applicati ons with the ACT

http://help.sap.com/saphelp_nw74/helpdata/en/08/1cd90cc855424eb8177365a122a8b7/content.htm?frameset=/en/37/34e660c83349d39922832760ed9c7b/frameset.htm

5.3.4 Creating FPM Applications based on SADL Entities

using the ACT Creati ng FPM Applicati ons based on SADL Entiti es usi ng the ACT

http://help.sap.com/saphelp_nw74/helpdata/en/37/34e660c83349d39922832760ed9c7b/content.htm?frameset=/en/37/34e660c83349d39922832760ed9c7b/frameset.htm

5.4 Appendix D – Link to ABAP for SAP HANA Reference

Scenarios

ABAP for SAP HANA Reference Scenario - http://scn.sap.com/docs/DOC-35518

ABAP for SAP HANA Reference Scenario: Implementing Open Items Analysis using SAP Floorplan Manager - http://scn.sap.com/docs/DOC-47390

ABAP for SAP HANA Reference Scenario: Implementing Mobile based Open Items Analysis Using SAP UI5 and SAP Gateway Foundation Component - http://scn.sap.com/docs/DOC-47388









www.sdn.sap.com/irj/sdn/howtoguides

how to create fpm based on sadl using act - sap q&a · how to create fpm based on sadl using...

Documents