Rough Guideline for DDIC maintenance (Tables) Also applicable to all DDIC objects. Go to SE11 transaction.

Depending on what you want to do, either Create/Change/Display.

Type in the table description

Depending on the type of table to be created, select appropriately the Delivery Class. For our project, ‘A’ is meant for Master & Transactional Tables, ‘C’ is solely meant for Parameter Tables. Important Notes: When selecting ‘A’ the table MUST have a Client field.

Select the Data Browser/Table View Maint. option. For Master/Transaction tables, it MUST be Display/Maintenance Allowed with Restrictions and for Parameter Tables, it must be Display/Maintenance Allowed. Important Note: If Display/Maintenance Not Allowed is selected, even SE16/SE17 transaction cannot view the data.

Save the changes. Again make sure all DDIC object must go to Z001 Package.

Click on the Technical Settings push-button.

Select the Data Class, Master table should be APPL0, Transactional table should be APPL1 and Parameter table should be APPL2. We’d try to follow this convention as closely as possible, but potentially there will be tables currently in e-CIBS which does not follow this convention.

Select the appropriate Size Category, this part is quite difficult to manage, but just provide a rough estimation.

For the buffering part, for parameter tables, you should choose Buffering Switched On but not for Master/Transaction. Buffering Type, should be Fully Buffered for parameter tables, but none for Master/Transaction tables. Save the changes.

Click on the Fields Tab Strips.

Fill in the related/required fields in the Field column and also in the Data Element column. Provided the Data Element is/are already existed. If not, then the system will prompt for an error due to the non-existence of respective Data Elements. What can be done is to double-click at the respective Data Elements and system will automatically prompt whether do you want to created the respective Data Element or not. Click Yes to continue creation of the new Data Element.

The above shows a sample of the Data Elements. If the Domain used also is new, just double-click at the Domain field and the system will prompt to create the respective Domain name. Click Yes to proceed with the creation of the new Domain.

Sample Domain

For each of the field(s), click once on the respective field name, e.g. CLIENT field and click on the Foreign Key push-button. This is to assign the Foreign Key relationship.

For common field(s) the system will prompt a proposal of the Foreign Key option. Click Yes to proceed.

System will proposed a summary screen above to confirm whether do you agree or not with the proposals. If yes, then proceed to start changing the Semantic Attributes.

Choose the appropriate Foreign Key Type, for us normally we will choose Key/Fields Candidate if appropriate. Choose the appropriate Cardinality, for us, Client field will always be 1:CN, for Station Code, 1:CN and the rest of the field depends on how strict we would want to be. The lesser will be C:CN.

Always check the Foreign Key relationship before completing the transaction.

If the system cannot proposed anything, the above screen appear.

Type in the tables name and click on the Generate proposals push-button.

Check the Foreign Key relationship.

Same as the above

Check Foreign Key assignment

Activate the table.

Sign up to vote on this title
UsefulNot useful