Functionality
This function module is the task API to define the data dictionaryobjects (DDIC) for the new extension. These objects are generated in theEasy Enhancement Workbench (EEW) for extensions of application objects,like Business Partner (BUPA) or Business Partner Relationship (BUPR).

• The task API generates the name for the application. This name is used
in Business Data Toolset (BDT) as an internal identifier for theextension.

• The task API defines the new table for the extension and the following
fields for the table:
Parent object keys - For example, in the case of a business partner, thekeys are CLIENT and PARTNER and in the case of a businesspartner relationship, the keys are CLIENT, RELTYP,PARTNER1 and PARTNER2.
Time validity fields
Other fields for the extension that you have entered through the wizard

• The task API defines a new structure for change document. This structure
is typically defined by the ChangeDocument API. However, if the change document API is not included inthe EEW, this structure will not be generated. Since this structure isrequired by other APIs, this structure will also be generated by theDDIC task API.

• If you have selected the Check Table indicator for a field while
creating the extension using the Wizard, the task API also defines thefollowing objects for the field:
Check table
Text table for the Check table
Check table function module
Text table function module
Maintenance view for the Check table

• The task API defines the Update API. This API is called to update
the database.
In addition to the standard entries provided by the generic wizard, thetask API also reads the following entries of the table
IT_EXTENSIONDEF:
Parameter Name,,Description
TIME_CONSTRAINT,,Time constraint (With Gaps, No Gaps or Time Validity)of the extension
TIME_DEPENDENCY,,Time dependency (time dependent or time independent) ofthe extension
CARDINALITY,,Cardinality (1:1 or 1: N) of the extension
The task API reads the following entries of Applications KnowledgeBase table (OXT_ER_KNOWLEDGE) to define the parent object keys andtime validity fields for the new table:
Node1,,Node2,,Parameter Name,,Description
DDICGEN,,INCLUDEKEY,,DATETO,,New key field to be added
DDICGEN,,INCLUDEPARENTKEY,,RELTYPE,,New parent key field to be added(only in case of BUPR)
DDICGEN,,INCLUDEFIELD,,DATEFROM,,New field to be added
DDICGEN,,EXCLUDEPARENTKEY,,DATETO, REL_NUMBER,,If a key field in theparent table is not required in the extension, then there should be anentry with this parameter name and parameter value as the key field ofthe parent (only in case of BUPR).
DDICGEN,,REFFIELD,,CURR, QUAN,,Any field to be added as a referencefield to another field
DDICGEN,,DATA_ELEMENT,,DATEFROM, DATETO, QUAN, RELTYPE, UNIT, CURR, CUKY
,,The data element of the field added through the knowledge base has tobe made available here. The parameter name should be the same as theparameter name in INCLUDEKEY, INCLUDEPARENTKEY, INCLUDEFIELD orREFFIELD.
DDICGEN,,DATA_ELEMENT,,RELTYPE,,The data element of the field addedthrough the knowledge base has to be made available here. The parametername should be the same as the parameter name in INCLUDEKEY,INCLUDEPARENTKEY, INCLUDEFIELD or REFFIELD (only in case of BUPR).
DDICGEN,,DOMAIN,,DATEFROM, DATETO, QUAN, RELTYPE, UNIT, CURR, CUKY,,Thedomain of the field added through the knowledge base has to be madeavailable here. The parameter name should be the same as the parametername in INCLUDEKEY, INCLUDEPARENTKEY, INCLUDEFIELD or REFFIELD.
DDICGEN,,DOMAIN,,RELTYPE,,The domain of the field added through theknowledge base has to be made available here. The parameter name shouldbe the same as the parameter name in INCLUDEKEY, INCLUDEPARENTKEY,INCLUDEFIELD or REFFIELD (only in case of BUPR).
The task API updates the:

• Table CT_GOX_HEADER with the details of the objects to be
generated

• Table CT_TASKPARAMLIST with the following information:

Parameter Name,,Description
TABL,,Name of the generated table
FIELD,,Name of the field for the generated table. All fields of thetable use this parameter. This parameter is the child of the TABLparameter.
ROWGUID,,Row GUID of the field. This parameter is the child of the FIELDparameter.
ISKEY,,Key field information of the field. This parameter is the childof the FIELD parameter.
DTEL,,Name of the data element for the field. This parameter is thechild of the FIELD parameter.
DOMA,,Name of the domain for the field. This parameter is the child ofthe DTEL parameter.
PARENT_KEY,,Parent key information of the field. This parameter is thechild of the FIELD parameter.
Note: The value of the parameter PARENT_KEY is marked as 'X' forparent key fields.
KEY_LENGTH_CHANGED, Parameter Value - 'X',,Information about the changein the length of the key field, in case you change the same duringregeneration of the extension using the wizard.
STRUC_CHD,,Details of the new structure for change document. Thisparameter is the child of the TABL parameter.
CHECKTABLE,,Name of the Check table. This parameter is the childof the FIELD parameter.
APICHECKFUNC,,Name of the Check table function module. Thisparameter is the child of the FIELD parameter.
APITEXTFUNC,,Name of the Text table function module. Thisparameter is the child of the FIELD parameter.
FUNCTION_GROUP,,Name of the function group containing the UpdateAPI. This parameter is the child of the TABL parameter.
APIUPDATE,,Name of the Update API. This parameter is the childof the TABL parameter.
REFFIELD,,Name of the field, which is the reference field for a field.This parameter is the child of the FIELD parameter.
SEMANTICAL_KEY,,Semantical key of the table, which is not a key field inthe table. This is required in usages like BW. This parameter is thechild of the FIELD parameter.