FMDERIVE and FINBASIS Transport tool
The main difference between old transport method and FINBASIS tool is only a container is written to the request. The header entry (table TABADRH) of the derivation strategy is added into the container within the transport request. All of the other objects that are required for the derivation strategy are added into the container only when the transport is released. The originating system then transports the container to the target system.
For more information you can access to note:
Error 'No suitabe RFC found' during transport
Check the long text of error FINB_TR032.
Client copy ends with message 'Postprocessing required'
To see if there are inconsistencies in the derivation strategies, execute report ABADRCHECK in the source system.
Access routines for the derivation rule could not be generated
FMDERIVE* tables deleted, not copied
FMDERIVE* table definition missing locally
Error 'Incompatible Call Rejected, see note 2295840' during transport or Client Copy, or errors stating that function FINB_TR_AFTER_IMP_EXEC is blacklisted in S/4HANA
Refer to Notes:
|Client copy ends with error DYNPRO_SEND_IN_BACKGROUND|
The error can occur if there is some inconsistent entry in table TABADRH (e.g. missing strategy name in field ABADRENV).
Tips and tricks
- Compare FMDERIVE strategies: Execute transaction FMCOMPARESTRATEGY or report RFFMCOMPARE_STRATEGY. If you do not have it in your system, please refer to note:
- Predefined tables (FMDERIVE001-FMDERIVE009) are renamed during client copy or transport, this way if any Z code is pointing them it should be changed in order not to get errors. Refer to note:
1231815 - Predefined FMDERIVE tables are renamed during transport/CC
Useful Tables / Tcodes / Reports
TABADRS: Derivation Steps
TABADRSF: Steps and fields
T000 for proper logsys identification
FINB_TR_CATA: Attributes for Transport Objects. 'DERI' for PSM derivations
FINB_TR_DEST: RFC Destination for transport methods (connected to SM59-ABAP connections. You need to have a non-dialog user, and there should be no language set
FINB_TR_DISPLAY to see the content of a transport request(keep in mind whether the request is released or not)
SCC3: Client copy log
Other related Notes/KBAs
1019327 - FMDERIVE and the new FINBASIS transportation tool
1166677 - FINBASIS/SEM-BW customizing transports - errors & help
2315816 - FMDERIVE transport (overview)
1661776 - How to transport Derivation Strategy - Best Practice -