Asset Management Fiori App using ABAP RESTful Application Programming Model(RAP) - Draft Enabled

Description

This repository contains code for Asset Management system using ABAP RESTful Application Programming Model (RAP) in SAP Cloud Platform, ABAP environment.

Hello Team,

Welcome the Usecase start up guide.

Steps to Run :

1. Configure ABAP Cloud Platform in your personal Eclipse IDE https://developers.sap.com/tutorials/abap-environment-trial-onboarding.html

2. Search for a package ZLCASE_V2(ready to run App) in ABAP cloud environment (There are few chances of not finding the package because of distributed instance for trial cloud infrastructure. I have lost my entire package and by my luck i had it in my Git).

   If Package not found , do the below steps

   Clone your project into your Custom Package(Total 53 Artifacts)

   Some times even though the log shows 53 , only less files get imported into package. Inference is already files are available in system and locked to a request.

   

3. Do activation as per below order to avoid error. Due to some reason even though Mass activation list all aritifacts , it end up not activating all. Select all aritifacts in below listed folder(mass activation within a folder) and activate folder by folder.

   • Domains
   • Data Element
   • Database Tables
   • Data Definitions
   • Metadata Extensions
   • Classes
   • Behavior Definitions
   • Service Definitions
   • Service Bindings

4. Just to avoid any unexpected error, just make sure all artifacts are activated in its respective folders.

5. Publish the service Binding and preview the App from the Root BO/View

6. Run ABAP class ZCL_GENERATE_ASSET_DATA(Make sure classes are active too) to populate table zmarket_t(Market Value Help) and ZPRODSTAT_T (Status Value Help)

Ready to run 👍

Common and easy fix errors :

• Missing Value help/Smart Filter in List Report(ME View activation) , just cross check after publishing the Service Binding
• No data in Value Help (Run the Data generation class ZCL_GENERATE_ASSET_DATA)
• Unable to publish service binding (Activate in bottom up fashion starting with data element ending with service definition)
• Stuck with some TR issues or unable to delete (Add transport manager view in Eclipse and manage your task and TR appropriately )
• Always import into a clean package to avoid confusion

Technical Design

Behavior

It briefly defines the scope of business logic to be implemented.

Content Manager Role

Entity	Behavior
Asset	Operations: Create, update, delete Action: create assets by template Validations: validate editable input fields Feature Control: Static and dynamic field control

Product Group Manager Role

Entity	Behavior
Asset	Operations: Action: Archive Asset Action: Revert Asset Feature Control: Dynamic action control

Local Market Manager Role

Entity	Behavior
Asset	Read operations only

Projection Layer in Asset Scenario

Expected UX

Content Manager Role

Screen 1 :

Screen 2 :

Product Group Manager Role

Screen 1 :

Local Market Manager Role

Screen 1 :

For any queries, reachout to me at vishnucta@gmail.com