Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM-BF-CAT (Application Component) Catalogs⤷
QSKT (Package) QM Basic Data: Catalog Data
Basic Data
| Data Element | QKZNACHVB |
| Short Description | Indicator: function module called after posting |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | QKZ | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| Value Table |
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 | AfterPost. |
| Medium | 15 | After posting |
| Long | 20 | Call after posting |
| Heading | 7 | AftrPst |
Documentation
Use
If the indicator is set, the dialog transaction is only accessed after saving the function module for the follow-up action and after COMMIT WORK.
If the indicator is not set, this function module is only accessed before COMMIT WORK.
Dependencies
If you set the indicator to access changed data, you must also set the indicator Synchronous update.
Explanation
The indicator is not set, the follow-up action starts before COMMIT WORK:
The function module is performed in the same LUW (logical unit of work) as the dialog transaction. As a result, it cannot contain COMMIT WORK.
Note that the data for the current dialog transaction is still not available on the database, if you want to print a text using a function module for example.
Information can be returned using the log table in the function module interface.
Examples:
- Send a mail with specified contents.
- Update a user-defined table with the given data.
The indicator is set, the follow-up action starts after COMMIT WORK:
The function module is performed in a second LUW.
If data changes should be made, the function module must contain a COMMIT WORK, and new locks may have to be set. The information in the log table is not saved.
The indicator Synchronous update is important in this instance. This indicator must be set. This means that synchronous update is in use when the follow-up action module reads data from the database, that was created or changed in the dialog transaction (in the first LUW), since the data is only written to the database in the update task.
Examples:
- Accessing a follow-up action: CALL TRANSACTION..., LEAVE TO TRANSACTION
- Start of a report, for example, for printing a report with contents that come from the dialog transaction
- Classification of batch data using data from the dialog transaction
History
| Last changed by/on | SAP | 20010221 |
| SAP Release Created in |
