Ansicht
Dokumentation
BURX_OXT_TASK_GEN_BDT - Task API for BDT (Business Data Toolset)
CL_GUI_FRONTEND_SERVICES - Frontend Services RFUMSV00 - Advance Return for Tax on Sales/PurchasesThis documentation is copyright by SAP AG.
Functionality
This function module is the task API for screen generation and its handling. This applies to new extensions for the aApplication object, Business Partner Relationship (BUPR), generated through the Easy Enhancement Workbench (EEW).
The table control and filter fields appear on the screen in all scenarios for extensions with 1:N cardinality. However, in the case of 1: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 relevant control information.
- ISDAT - Reads the tables that are owned by the application and notes the data 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 data from its current memory to its global memory.
- DSAVC - Prepares the global memory for saving the data. This BDT event function 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 the newly 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 the object instance currently being edited and transfers the relevant object classes and object values to the BDT without further information.
- CHGD4 - Decides for each item whether it is relevant or not. If it is relevant, you can change the item display using different return parameters.
- CHGD3 - Changes the document headers based on the values transferred by the 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 the API.
- 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 of the 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 the table use this parameter. This parameter is the child of the TABL parameter. |
| DTEL | Name of the data element for the field. This parameter is the child 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. This parameter is the child of the STRUC_DX parameter. |
| STRUC_DX_LINE_TYPE | Name of data structure for data exchange. This parameter is the child of the STRUC_DX_TABLE parameter. |
| DOMA | Name of the domain for the field. This parameter is the child of the DTEL parameter. |
| CHECKTABLE | Name of the Check table. This parameter is the child of 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 the Callback API to retrieve data from the BDT memory. This parameter is the child of the TABL parameter. |
The task API reads the following entries of the Applications Knowledge 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 the generated table |
| DDICGEN | INCLUDEFIELD | DATEFROM | Name of the Valid From field in the generated table |
| SCREENGEN_TD | SCREENTC_TD | Main program name | Parameter name contains the main program name where the screen template for table controls is available. The parameter value contains the screen number. |
| CODEGEN | OBJECTINFO | HEADFRAME | First entry in the table TBZ3I for every new Customer Data tab that is created |
| CODEGEN | OBJECTINFO | %OBJECTIDENT1% | Contains the existing key of the parent table |
| CODEGEN | OBJECTINFO | %OBJECTIDENT2% | Contains the existing keys of the parent table |
CODEGEN,,OBJECTINFO,,%OBJECTIDENT3%,,Holds the existing keys of the parent table
| CODEGEN | OBJECTINFO | %OBJECTIDTAB% | Parent table of the application object |
| CODEGEN | OBJECTINFO | STDSCREENSEQ | Standard screen sequence to which the newly generated BDT screen is attached. |
| CODEGEN | OBJECTINFO | FUGR_TD | Function group of the templates used for generation. |
| SCREENGEN_TD | SCREENDATS_TD | Main program name | Screen templates to be used for 1:1 BUPR extensions |
| SCREENGEN | SCREENCHAR_TD | Main program name | Screen templates to be used for 1:1 BUPR extensions |
| SCREENGEN_TD | SCREEN_TD | MODULINCLUDE | Include name |
The task API updates the table CT_TASKPARAMLIST with the following entries:
| Parameter Name | Description |
|---|---|
| STRUC_DI | Direct Input structure |
| GEN_NEW | Ensures that the ARCH_DEF entry is not made in the CT_TABLE_ENTRIES by the Business Add-In used by BDT, as this is done in the Archiving task API. |
Example
Notes
Further information
Parameters
CT_GOX_HEADERCT_POSTPROC
CT_TABLE_ENTRIES
CT_TASKPARAMLIST
IT_EXTENSIONDEF
IT_GOX_HEADER_OLD
IT_TAB_HEADER_OLD
IV_MODE
IV_NAMESPACE
IV_NSPCSHT_CUS
IV_NSPCSHT_DEV
T_RETURN
Exceptions
SEMANTICAL_ERRORTECHNICAL_ERROR
Function Group
BUX_OXT_TASKAddresses (Business Address Services) ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 12097 Date: 20240523 Time: 152719 sap01-206 ( 92 ms )
