| Parameter | Reference | Type | Length | Default | Optional | Text |
|---|---|---|---|---|---|---|
| I_DIALOG_MODE | BU_AKTYP | C | 2 | |||
| I_MAINDATA_LOCKED | BOOLE | u | 1 |
| Parameter | Reference | Type | Length | Text |
|---|---|---|---|---|
| E_KDYNNR | SYST-DYNNR | C | 4 | |
| E_REPID | SYST-REPID | C | 40 | |
| E_TABLE_FLAGS | FLAG_LEISTE_GE | v | 9 |
|
DEFINE &TEXT& = 'User fields BE : Initialization' DEFINE &EVENT& = '00700170'' DEFINE &TYPE& = 'PROCESS' INCLUDE FI_OPEN_FI_DOCUMENTATION_1 OBJECT DOKU ID TX The Business Transaction Events &EVENT0& to &EVENT3& form theinterfaces from SAP program SAPMF60D (building master data) to thecustomer function group that implements the customers' user fields. Thetest to verify if these customer user fields have been created is madeby assigning the BTE 00700170 to a function module in the customer namerange in the table TPS34. This assignment can be made using thetransaction FIBF. Refer to If customer user fields have been created, call the assigned functionmodules in PBO in screen 701, program SAPMF60D . The import parameters of the &EVENT& event are: I_DIALOG_MODE : The current dialog mode of the master data dialog iscopied. The significance of the copied values can be seen in the TBZ0Ktable. I_MAINDATA_LOCKED : This is flagged if there is a master data block. The export parameters are: E_KDYNNR : Copy the number of the screen in which the customer userfields were created. E_REPID :This parameter contains the program name in which thecustomer user fields are to be maintained. This can be queried with thesystem variable SY-REPID. E_TABLE_FLAGS: This field string contains the tables which are to beexported to &EVENT1& event from the program in the customer functiongroup. The components in the field string all have the type BOOLE and a |