Functionality
This function module is the task API for screen generation and itshandling. This applies to new extensions for the aApplication object,Business Partner Relationship (BUPR), generated through the EasyEnhancement Workbench (EEW).
The table control and filter fields appear on the screen in allscenarios for extensions with 1:N cardinality. However, in the case of1:1 cardinality only fields are generated.
In the case of BUPR extensions for the cardinality types 1:1 and 1:N,this task API defines the following objects:

• The BDT function group


• The following BDT event function modules:

ISSTA - Initializes the global variables and retrieves the relevantcontrol information.
ISDAT - Reads the tables that are owned by the application and notes thedata in the update memory as both the new and the old status.
DTAKE - In the BDT, data is saved in several steps. In the first step,this BDT event function module, which owns the table, writes the datafrom its current memory to its global memory.
DSAVC - Prepares the global memory for saving the data. This BDT eventfunction module executes all actions for which errors may occur.
DSAVE - Writes the data from the global memory to the database.,,
FCODE - Handles the function codes corresponding to the elements of thenewly generated screen.
XCHNG - Determines whether data has been changed.
DINP2 - Fills out data fields.
DLVE2 - Initializes the global memory.
CHGD1 - Recognizes the data in the dialog lists that belongs to theobject instance currently being edited and transfers the relevant objectclasses and object values to the BDT without further information.
CHGD4 - Decides for each item whether it is relevant or not. If it isrelevant, you can change the item display using different returnparameters.
CHGD3 - Changes the document headers based on the values transferred bythe applications.
RDELM - Deletes local memory 1.
RPRDR - Fills local memory 1 from local memory 2 or from the database.
RTAKE - Transfers data to local memory 2.
APPLC - Checks the direction of flow either from SAP GUI or from theAPI.

• The following function modules:

MEMORY_GET
TABLE_GET

• Business Add-in (BAdI) - Whenever the time validity of the parent is
changed, this BAdI is used to accordingly adjust the time validity ofthe extension.
The API reads the following entries of the table IT_EXTENSIONDEF:
Parameter Name,,Description
FLD_GRP_LOW,,Lower limit for the field group
FLD_GRP_HIGH,,Upper limit for the field group
DEV_LAYER,,Development Level
CARDINALITY,,Cardinality (1:1 or 1: N) of the extension
The API reads the following entries of the table CT_TASKPARAMLIST
:
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.
DTEL,,Name of the data element for the field. This parameter is thechild of the FIELD parameter.
APPLI,,Application name for the extension
STRUC,,Read structure of the generated table
STRUC_KEY,,Key structure of the generated table
STRUC_API,,API structure of the generated table
STRUC_CHD,,Change document structure name
STRUC_UPD,,Update structure of the generated table
STRUC_MEM,,Memory structure name
STRUC_DX_TABLE,,Name of the data table type for data exchange. Thisparameter is the child of the STRUC_DX parameter.
STRUC_DX_LINE_TYPE,,Name of data structure for data exchange. Thisparameter is the child of the STRUC_DX_TABLE parameter.
DOMA,,Name of the domain for the field. This parameter is the child ofthe DTEL parameter.
CHECKTABLE,,Name of the Check table. This parameter is the childof the FIELD parameter.
CD_INCLUDE,,Name of the change document include
CD_FORM_NAME,,Name of the change document form
CHDOC,,Name of the change document object
APIMEMORYGET,,Name of the API in the BDT, which is called by theCallback API to retrieve data from the BDT memory. This parameteris the child of the TABL parameter.
The task API reads the following entries of the ApplicationsKnowledge Base table (OXT_ER_KNOWLEDGE):
Node1,,Node2,,Parameter Name,,Description
DDICGEN,,INCLUDEDI,,STRUCDI,,Name of the main Direct Input structure
DDICGEN,,INCLUDEKEY,,DATETO,,Name of the Valid To field in thegenerated table
DDICGEN,,INCLUDEFIELD,,DATEFROM,,Name of the Valid From field inthe generated table
SCREENGEN_TD,,SCREENTC_TD,,Main program name,,Parameter name containsthe main program name where the screen template for table controls isavailable. The parameter value contains the screen number.
CODEGEN,,OBJECTINFO,,HEADFRAME,,First entry in the table TBZ3Ifor every new Customer Data tab that is created
CODEGEN,,OBJECTINFO,,%OBJECTIDENT1%,,Contains the existing key of theparent table
CODEGEN,,OBJECTINFO,,%OBJECTIDENT2%,,Contains the existing keys of theparent table
CODEGEN,,OBJECTINFO,,%OBJECTIDENT3%,,Holds the existing keys of theparent table
CODEGEN,,OBJECTINFO,,%OBJECTIDTAB%,,Parent table of the applicationobject
CODEGEN,,OBJECTINFO,,STDSCREENSEQ,,Standard screen sequence to which thenewly generated BDT screen is attached.
CODEGEN,,OBJECTINFO,,FUGR_TD,,Function group of the templates used forgeneration.
SCREENGEN_TD,,SCREENDATS_TD,,Main program name,,Screen templates to beused for 1:1 BUPR extensions
SCREENGEN,,SCREENCHAR_TD,,Main program name,,Screen templates to be usedfor 1:1 BUPR extensions
SCREENGEN_TD,,SCREEN_TD,,MODULINCLUDE,,Include name
The task API updates the table CT_TASKPARAMLIST with thefollowing entries:
Parameter Name,,Description
STRUC_DI,,Direct Input structure
GEN_NEW,,Ensures that the ARCH_DEF entry is not made in theCT_TABLE_ENTRIES by the Business Add-In used by BDT, as this is done inthe Archiving task API.