SAP ABAP Data Element CBGLE_USERACTION (User Action)

Hierarchy

☛ EA-APPL (Software Component) SAP Enterprise Extension PLM, SCM, Financials
   ⤷ EHS-SAF (Application Component) Product Safety
     ⤷ CBGLM (Package) EHS: Global Label Management

Basic Data

Data Element	CBGLE_USERACTION
Short Description	User Action

Data Type

Category of Dictionary Type	D	Domain
Type of Object Referenced		No Information
Domain / Name of Reference Type	CCGLD_USERACTION
Data Type	CHAR	Character String
Length	30
Decimal Places	0
Output Length	30
Value Table	CCGLC_USERACTION

Further Characteristics

Search Help: Name
Search Help: Parameters
Parameter ID
Default Component name
Change document	☐
No Input History	☐
Basic direction is set to LTR	☐
No BIDI Filtering	☐

Field Label

	Length	Field Label
Short	10	Action
Medium	20	User Action
Long	31	User Action
Heading	31	User Action

Documentation

Definition

Describes an event within Global Label Management that was triggered by the user.

Use

You specify the log level using the specified user actions.

Change Logging for "Label Printing"

The following user action is available for label printing and does not have to be assigned to a labeling scenario:

• MANUAL_PRINT_DIALOG: Call label printing
• Triggered when label printing is called

The following user actions are available for change logging in label printing and must be assigned to a labeling scenario. User actions that are not assigned to a labeling scenario are ignored or not displayed during change logging:

• FILTER_CRITERIA: Countries/mode of transport
• Triggered as soon as the user changes the countries or mode of transport in label printing
• OED_SCENARIO: User input scenario
• Triggered as soon as the user changes a user input in label printing that is based on a labeling scenario.
• OED_TEMPLATE: User input template
• Triggered as soon as the user changes a user input in label printing that is based on a label template.
• ONLY_MARKED_OED: User input with indicator
• Supplements the user actions OED_SCENARIO and OED_TEMPLATE and is only taken into consideration if one of these user actions has been defined for the specific labeling scenario.
• Static logging is activated, that is, irrespective of the changes made, an entry is made in the application log for all user entries marked log.
• LABEL_INFO: Number/report language
• Triggered as soon as the user changes the number of labels or language key in label printing
• SERIAL_NUMBER: Sequence number
• Triggered as soon as the user changes the sequence numbers in label printing
• PRINT: Trigger print
• Triggered as soon as the user starts printing in label printing
• PREVIEW: Call preview
• Triggered as soon as the user starts the label preview

Change Logging for Processing Print Requests and Print Request Bodies

The following user actions are available for processing print requests and print request bodies and must be assigned to a labeling scenario. User actions that are not assigned to a labeling scenario are ignored or not displayed during logging:

• PRTREQ_CANCEL_PRINTING:    Cancel printing of the print request
• Triggered when a print request with the status Print request is being printed... (ID) or Print request ready for printing (ZD) is canceled. The cancellation is carried out by calling the WWI server.
• PRTREQ_CHANGE: Change print request
• Triggered when the print request data is changed
• PRTREQ_CHECK: Check print request
• Triggered when the print request is checked
• PRTREQ_CONTENT_GET: Print request preview
• Triggered when the content of the document is displayed using the preview
• PRTREQ_CONTENT_PRINT: Print print request
• Triggered when the document is printed
• PRTREQ_CREATE: Create print request
• Triggered when the print request is created
• PRTREQ_DELETE: Delete print request
• Triggered when the print request is deleted
• PRTREQ_PROCESS: Process print request
• Triggered when the print request is processed
• PRTREQ_READ: Read print request
• Triggered when the print request is read
• PRTREQ_REORG: Reorganize print request
• Triggered when the report RCBGL_PRINTREQUEST_REORG is executed
• PRTREQ_STATUS_RET: Print request status
• Triggered when the status of the print request is called
• PRTREQ_UNLOCK: Unlock print request
• Triggered when the print request is unlocked
• A data lock is set when a print request is processed by a different user, for example. In this case, the data record cannot be changed by another user.
• PRTREQBODY_DELETE: Delete print request body
• Triggered when the print request body is deleted
• PRTREQBODY_DET: Determine print request body
• Displayed when the print request body is created
• PRTREQBODY_PROCESS: Process print request body
• Triggered when the print request body is processed
• PRTREQBODY_READ: Read print request body
• Triggered when the print request body is read
• PRTREQBODY_RESTART: Reprocess print request body
• Triggered when the print request body is created again
• PRTREQBODY_UNLOCK: Unlock print request body
• Triggered when the print request body is unlocked
• A data lock is set when a print request body is processed by a different user, for example. In this case, the data record cannot be changed by another user.
• PRTREQBODY_UPDATE: Update print request body
• Triggered when the print request body data is updated
• PRTREQBODY_VERPROC: Check print request body
• Triggered when the print request body is created for the label check

The following general parameters are available in the input help for the user action. They can be assigned to a labeling scenario:

• ALL: All changes
• All changes and assigned user actions are logged.
• If you assign this parameter to a labeling scenario, the changes are logged for all user actions that are assigned to this labeling scenario.
• OFF: Log deactivated
• Changes are not logged for the assigned user actions and changes.
• If you assign this parameter to a labeling scenario, no changes are logged for all user actions that are assigned to this labeling scenario.
• This parameter has a higher priority than the ALL parameter. This means that, if both parameter values are assigned to a labeling scenario, the ALL parameter takes effect first.

Dependencies

Example

History

Last changed by/on	SAP	20130529
SAP Release Created in	700