Hello,
The previous post has some interesting links how to extend the standard SAP dictionary.
Included in this post some of the things that I pay attention to when extending tables and views.
1/
Always try to use Customer Includes in standard SAP objects when they exist.
2/
When there is no Customer Include make use of an append structure to add your own fields.
3/
Never change the standard SAP object (table or structure) immediately (apply 1/ or 2/).
4/
When you add extra fields via 1/ or 2/ make sure you start these fields with a Z however this is not mandatory I always use Z-fields in append structures and customer includes.
When you use field names in the namerange of SAP there is always a risk in future SAP releases that you will have duplicate fields (when SAP provides your fieldname in a new version).
With duplicate fields in DDIC objects always problems during conversion and to repair it, try to avoid it.
5/
Pay special care when extending tables that have a lot of data in it.
Especially when the extension takes places (eg via customer include) in the middle of the object there is a change that table data needs to be converted.
Table conversion can take a lot of time, especially on big tables.
This is very often forgotten, normally in DEV and QA everything goes fine, once the transport goes to PRD the problems start (conversion problems, long conversion times, undo problems on database level, ...).
Therefor make sure before you transport to PRD you analyse the table in PRD , ask one of the BC guys for standby to check DB and also have a look at how table conversions work in tcode SE14.
Hope this is usefull.
Wim
Bluesky
