| Parameter | Reference | Type | Length | Text |
|---|---|---|---|---|
| E_ABORT_CHECK | BOOLE | u | 1 | |
| E_CHNG_FLAG | BOOLE | u | 1 | |
| E_USERFIELDS | VIMI01_CI | u | 1 |
|
DEFINE &TEXT& = 'RU user fieds: data transfer in CustFunctGroup' DEFINE &EVENT& = '00700182' DEFINE &EVENT2& = '00700182' DEFINE &EVENT3& = '00700183' DEFINE &EVENT1& = '00700181' DEFINE &EVENT0& = '00700180' DEFINE &PROGNAME& = 'SAPLFV7E' DEFINE &SCREEN& = '900' DEFINE &STRUCTURE& = 'CI_VIMI02' DEFINE &BEREICH& = 'Rental unit' DEFINE &TYPE& = 'PROCESS' INCLUDE FI_OPEN_FI_DOCUMENTATION_1 OBJECT DOKU ID TX The Business Transaction Events &EVENT0& to &EVENT3& form the interfaceof the SAP program &PROGNAME& (&BEREICH& master data) to the customerfunction group that implements the customer user fields. You check thatthese customer user fields have been created by assigning the BTEEvent0 to a function module in the customer name range in tableTPS34. For an exact description of all steps necessary to include theuser fields, refer to general text If customer user fields have been created, call the assigned functionmodules in PAI of screen &SCREEN&, program &PROGNAME&. The export parameters of this event are: E_USERFIELDS: In this structure, the user fields are copied to programProgname. you must have created customer user fields in structureStructure. E_CHNG_FLAG: This determines if event &EVENT3& is triggered when themaster data records are saved. Changes to customer tables are updatedhere. E_ABBRUCH_PRUELAUF: The screen for the user fields are called in thebackground before saving. All input checks of the respective PAI thatare not ON_REQUEST are then carried out. If you want to cancel save dueto inconsistent data, you have to set this flag. |