Steps to Create Table Maintenance in SAP FIORI

 

Step 1: Create an OData Service

1. Open SEGW (Gateway Service Builder):

   • T-code: SEGW.
   • Create a new project for your table maintenance (e.g., Z_TABLE_MAINTENANCE).

2. Create Entity Type:

   • In the Data Model section, right-click on Entity Types and choose Create.
   • Define the Entity Type based on your SAP table (e.g., MARA).

3. Create Entity Set:

   • Right-click on Entity Sets and create an entity set that corresponds to the table (e.g., MaterialSet for MARA).
   • Map the entity type to the entity set.

4. Generate Runtime Objects:

   • Once your data model is complete, right-click on the project and choose Generate Runtime Objects.

5. Implement CRUD Operations in DPC_EXT:

   • Navigate to SE80 or SE24 to access the DPC_EXT class (Data Provider Class Extension).
   • Implement the CRUD methods like CREATE_ENTITY, UPDATE_ENTITY, DELETE_ENTITY, and GET_ENTITYSET to handle the operations for your SAP table.

6. Register and Activate the OData Service:

   • Go to T-code /IWFND/MAINT_SERVICE to register and activate your OData service.
   • Test the service by accessing /sap/opu/odata/sap/<SERVICE_NAME>/ to verify that the service is working as expected.

---

Step 2: Create a Fiori Elements App (List Report App)

1. Set up SAP Web IDE or Business Application Studio:

   • Open SAP Web IDE or SAP Business Application Studio (BAS) to create your app.

2. Create a New Project:

   • From the welcome screen, select New Project from Template.
   • Choose SAP Fiori Elements – List Report Application template.

3. Provide OData Service Information:

   • Select the system and service you created in SEGW (e.g., Z_TABLE_MAINTENANCE_SRV).
   • Select the Entity Set created for your table (e.g., MaterialSet for MARA).

4. Configure the List Report and Object Page:

   • Define your list report settings like filters and table columns.
   • Configure the Object Page for detail views.

---

Step 3: Enable Editing (CRUD Operations)

1. Edit the manifest.json:
• Ensure that the app allows editing by setting the necessary flags in the manifest.json.

"sap.ui.generic.app": {

    "pages": {

        "ListReport|MaterialSet": {

            "entitySet": "MaterialSet",

            "component": {

                "name": "sap.suite.ui.generic.template.ListReport",

                "settings": {

                    "editable": true,

                    "defaultCreateEnabled": true,

                    "defaultDeleteEnabled": true,

                    "defaultUpdateEnabled": true

                }

            }

        },

        "ObjectPage|MaterialSet": {

            "entitySet": "MaterialSet",

            "component": {

                "name": "sap.suite.ui.generic.template.ObjectPage",

                "settings": {

                    "editableHeaderContent": true

                }

            }

        }

    }

}

2. Configure the CDS View (if used):
   • If you are using a CDS view, ensure that you annotate the fields appropriately for editing using annotations like @UI.fieldGroup for forms and @UI.lineItem for table display.

---

Step 4: Deploy to SAP Fiori Launchpad

1. Deploy the Fiori App to the ABAP Repository:

   • In SAP Web IDE or BAS, right-click on the project and select Deploy > Deploy to ABAP Repository.
   • Provide your SAP system details and select the package and transport request.

2. Configure the Fiori Launchpad:

   • Access the Fiori Launchpad Designer using the T-code /UI2/FLPD_CUST.
   • Create a new Catalog and Group.
   • Define a new Tile for the app in the catalog.
   • Set up Target Mapping to link the tile to your deployed Fiori app by entering the Semantic Object and Action.

3. Assign the Tile to a Role:

   • Use PFCG to create a new role or update an existing role.
   • Assign the catalog or tile to the user roles that will have access to the app.

---

Step 5: Assign Roles and Access in Fiori Launchpad

1. Assign Roles to Users:
   • In PFCG, add the catalog or group to the role and assign the role to the relevant users.
   • Users assigned with the role will see the app tile in the Fiori Launchpad.

---

Step 6: Test and Use the App

1. Test CRUD Operations:
   • Access the Fiori Launchpad as the user.
   • Click on the app tile and test the CRUD operations (Create, Update, Delete) for the SAP table.
   • Verify that you can maintain the SAP table's data directly from the Fiori UI.

---

By following these detailed steps, you will be able to create a Fiori app that allows users to maintain (Create, Update, Delete) data in an existing SAP table through the SAP Fiori Launchpad without using SE11 or SE80 directly.

How to Change Cost Center in Accounting Document

Changing the KOSTL (Cost Center) field in the BSEG table using a BAPI is not directly possible since BSEG is a line-item table and is managed by SAP standard transactions. The BSEG table is updated indirectly through various financial postings and cannot be directly modified using a standard BAPI.

Alternative Approach:

If you need to change the cost center in financial documents, the correct approach would involve reversing the original document and posting a new document with the correct cost center. However, if your goal is to correct or change the cost center without reversing and reposting the document, consider using the following methods:

1. Use BAPI for Document Reversal and Reposting

• BAPI_ACC_DOCUMENT_REV_POST: This BAPI is used to reverse the original accounting document.
• BAPI_ACC_DOCUMENT_POST: This BAPI allows you to repost the document with the correct cost center.

2. Use a Direct Update via a Custom ABAP Program (Not Recommended)

• Directly updating the BSEG-KOSTL field is not advisable since it can lead to inconsistencies in the database and violates SAP’s data integrity principles.

3. Use Special Purpose BAPIs

• In specific cases, you may use specialized BAPIs related to the type of posting, such as:
  • BAPI_ACC_GL_POSTING_REV_POST: If dealing with General Ledger documents.
  • BAPI_ACC_INVOICE_RECEIPT_POST: For invoices and vendor-related postings.

Conclusion

Direct modification of BSEG-KOSTL via a standard BAPI is not supported. The best approach involves reversing the original document and posting a corrected version using standard BAPIs, ensuring that data integrity is maintained within the SAP system.

How to Find an Enhancement from a Function Module?

 To find the enhancement name associated with a specific function module in SAP, you can follow these steps:

1. Using Transaction Code SMOD

• Step 1: Go to transaction code SMOD.
• Step 2: In the initial screen of SMOD, click on the "Find" button (or press Ctrl + F).
• Step 3: In the search screen, enter the function module name (e.g., EXIT_SAPF110S_001) in the "Function Module" field.
• Step 4: Execute the search.
• Result: The system will display the enhancement(s) that include this function module.

2. Using Transaction Code SE80 (Object Navigator)

• Step 1: Go to transaction code SE80.
• Step 2: In the Object Navigator, select "Repository Browser."
• Step 3: Enter the function module name (e.g., EXIT_SAPF110S_001) in the field and press Enter.
• Step 4: Once the function module is displayed, double-click to open it.
• Step 5: Scroll down to the "Attributes" tab where the "Enhancement" field is displayed.
• Result: The enhancement name related to the function module will be shown in this field.

3. Using Transaction Code SE37

• Step 1: Go to transaction code SE37 to open the Function Builder.
• Step 2: Enter the function module name (e.g., EXIT_SAPF110S_001) and click "Display."
• Step 3: Navigate to the "Attributes" tab to view the enhancement name under the "Package" information.
• Result: The enhancement name will be linked to the function module in the "Enhancement" field.

4. Using Transaction Code SE93 (Transaction Code Search)

• Step 1: Go to transaction code SE93.
• Step 2: Search for the transaction associated with the function module.
• Step 3: Once you find the transaction, use the transaction code to determine the enhancement related to the transaction and function module.

5. Using ABAP Code (Advanced)

• Step 1: You can write a custom ABAP report to search for the enhancement name linked to a function module by querying the TADIR table (which contains development objects) and MODSAP (which contains modifications).
• Example Code:

  SELECT SINGLE * FROM MODSAP
  WHERE FUNCNAME = 'EXIT_SAPF110S_001'.
  

• Step 2: Run the report to get the enhancement name.

Conclusion

The enhancement name related to a function module can be found through SAP's standard transactions like SMOD, SE80, SE37, or by writing a small ABAP program. Each method provides a way to trace the connection between function modules and their corresponding enhancements, allowing you to extend or modify standard SAP functionality as needed.