Ansicht
Dokumentation
BAPI_BUS1092_SAVREPMUL - EHS: Saving Replicated Reports
SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up TXBHW - Original Tax Base Amount in Local CurrencyThis documentation is copyright by SAP AG.
Functionality from the Viewpoint of the Caller
The method BAPI_BUS1092_SAVREPMUL is used by a system in order to replicate or modify the business object report from another system. The method is used in Application Link Enabling (ALE). Distribution takes place asynchronously.
In the source system, the function module C14ALR_ALE_BUS1092_SAVREPMUL, which is generated from the interface of the existing function module, is used to trigger distribution. An example of this is the function module BAPI_BUS1092_REPLICATE.
Notes
There is a checkbox structure for each report data table. The only fields in the report data table that are changed are those that have an X in the corresponding check field in the checkbox structure. The field names in the data string and in the checkbox structure are identical.
| REP_HEADER_TAB | REP_HEADERX_TAB |
| REP_SUBJOIN_TAB | REP_SUBJOINX_TAB |
| REP_SYMBOLS_TAB | REP_SYMBOLSX_TAB |
| REP_APLOBJ_TAB | REP_APPLOBJX_TAB |
Rough Description of the Flow Logic
Preconditions
- The Customizing tables for the object report must be set in the target system.
- If you want to use engineering change management in the target system, the relevant change numbers you used for editing reports must be created in the target system.
Procedure
At the start, you can use a user exit to edit additional data before posting or to carry out parameter filtering.
Before the reports can be posted, the corresponding report categories, generation variants, and languages must be checked in the system and then created or changed. Specifications and documents used in the report must also be checked and created or changed if necessary.
All new reports are created using the method BAPI_BUS1092_CREATE, taking into account the checkbox structures.
For all existing reports, the system checks whether each data record already exists in the system. It does this using the logical system and the key values of the fields RECN and ACTN in the source system.
All known phrases are changed using the method BAPI_BUS1091_CHANGE. Here the checkbox structures are taken into account.
Subsequent Conditions
The documents specified in the interface are posted in the database.
If an error occurs, it is described in the RETURN parameter or the parameter contains a reference to the application log.
Possible Exceptions
None
Further information
- BAPI programming guide
- ALE programming guide
Parameters
ALEPOINTERCHANGE_NUMBER
COMPLETE_REPORT
DELETE_DATA
EXTENSION1_TAB
EXTENSION2_TAB
KEY_DATE
MULTLANGU_PARAMS
RECORD_SPLITT
REP_CS
REP_CSP
REP_HEADER
REP_HEADERX
REP_SUBJOIN
REP_SUBJOINX
REP_SYMBOLS
REP_SYMBOLS_COND
RETURN
SENDER
Exceptions
Function Group
1092PERFORM Short Reference ABAP Short Reference
This documentation is copyright by SAP AG.
Length: 5170 Date: 20240523 Time: 105409 sap01-206 ( 71 ms )
