Let us look at the maintenances that need to be performed for setting up a new service offering. There are multiple objects that are put together to enable a new service. The following diagram provides the details of the relationship between these objects:
Each of these tables has the following columns as a standard configuration for life cycle management through administration screens. The column details are as follows:
Column Name |
M / O |
Type |
Purpose |
|---|---|---|---|
OD_MAKER_ID |
O |
String |
The underlying ID of the maker who initiated this product / sub product request. |
OD_MAKER_DATE |
O |
Date |
This is the date / time stamp when the maker initiated this request. |
OD_MAKER_NAME |
O |
String |
This is the name of the Maker that should be displayed if there are any inquiries in the Administration module. |
OD_AUTH_ID |
O |
String |
The underlying ID of the Authorizer who authorized this product / sub product request. |
OD_AUTH_DATE |
O |
Date |
This is the date / time stamp when the authorizer authorized this requests. |
OD_AUTH_NAME |
O |
String |
This is the name of the Authorizer that should be displayed if there are any inquiries in the Administration module. |
OD_STATUS |
M |
String |
This is the status of this product / sub product definition. Possible value is:
|
While managing the storage of each of the objects defined in the next section, ensure that the columns mentioned in this table are also considered.