The Naming of the objects is not a mandatory task. But the best practice is to follow the Naming Conventions of the objects. It means following a naming rule to make it easier for the developer to understand. Below, I have written some rules with examples.
Table of Contents
Understand the RAP Objects with their Naming Conventions
Here, the object or the contest is related to a "Sales Order", and the module of the object is "SD". Always follow the current organization's Naming rules, they may be different from here.
| Objects Description | Object Name |
| Database Table / BO | ZSD_T_Sales_Order / ZSD_Sales_Order_T |
| Draft Table | ZSD_DT_Sales_Order / ZSD_Sales_Order_DT |
| Table Type | ZSD_TT_Sales_Order / ZSD_Sales_Order_TT |
| Structure | ZSD_S_Sales_Order / ZSD_Sales_Order_S |
| Interface View / Root View | I_Sales_Order |
| Consumption View / Projection View | C_Sales_Order |
| Meta Data | C_Sales_Order |
| Behaviour For Interface View | I_Sales_Order |
| Behaviour For Consumption View | C_Sales_Order |
| Behaviour Class / Behaviour Pool Class | I_BP_Sales_Order |
| Service Defination | UI_Sales_Order |
| Service Binding | UI_Sales_Order_V2 / UI_Sales_Order_V4 |
Understand the SAP Package flow alignment with its Naming
Step-1 Development Package (Predefined Package) -> Main Package.
Step-2 Main Package -> Sub Package (Main Object) -> Objects (Child Objects) (RAP Object, Ex- CDS View).
Step-3 Main Package with Module Name -> Sub Package with Object Name -> Child Objects.
Example: ZPK_SD_Google (Main Package) -> ZPK_Sales_Order_Report or ZSD_Sales_Order_Report (Sub Package or Main Object) -> I_Sales_Order.
Explanation: ZPK_SD_Google (Main Package)- PK means Package, SD means Sales and Distribution Module, Google Means Client Name.
Thanks For Reading.
Read More