Skip to end of metadata
Go to start of metadata

 

 

 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:

1019327 - FMDERIVE and the new FINBASIS transportation tool  

and

1166677 - FINBASIS/SEM-BW customizing transports - errors & help  


 FAQs



ProblemSolution

Error 'No suitabe RFC found' during transport

Check the long text of error FINB_TR032.

Read note 912369 FINB_TR_DEST, after import failures, transport errors

Client copy ends with message 'Postprocessing required'
FINB_TR_CC_EXIT_TARGET Post-Processing Required

Check note 1235955 - Client Copy: Derivation rule tables are not copied

To see if there are inconsistencies in the derivation strategies, execute report ABADRCHECK in the source system.
If it finds inconsistencies, execute it with option 'DELSTEPS' to remove them.

error ABADR013:

Access routines for the derivation rule could not be generated

  1. Enter your FM derivation strategy (transaction FMDERIVE), select the derivation rule (double click) and go to Menu -> Extras -> Regeneration
  2. To see if there are inconsistencies in the derivation strategies, execute report ABADRCHECK in the source system.
    If it finds inconsistencies, execute it with option 'DELSTEPS' to remove them.
      Also check note:
1730981 - Error ABADR013 or Runtime Error in SAPMABADR: Exception condition "SYSTEM_ERROR" raised  

LOAD_PROGRAM_NOT_FOUND

  1. Execute your FM derivation strategy transaction where you are receiving the runtime error (dump), select the derivation rule (double click) and go to Menu -> Extras -> Regeneration
  2. o see if there are inconsistencies in the derivation strategies, execute report ABADRCHECK in the source system.
    If it finds inconsistencies, execute it with option 'DELSTEPS' in all clients to remove them.
      Also check note:
1730854 - Runtime error 00341: LOAD_PROGRAM_NOT_FOUND  

FMDERIVE* tables deleted, not copied

FMDERIVE* table definition missing locally

  1. Implement Note : 1785263 - FMDERIVE00* tables deleted during after import process in source and target systems
  2. These missing/deleted tables do not represent a problem at the client copy time, but if you need these tables you can:
      1. Create the tables manually in the target system from the source system, that is transport the definition manually from source to target.
      2. Repeat the client copy.
  3. If you use FINBASIS releases 605,736,747,748 or S4CORE 101 to 103, Implement Note 2848604  -Tables FMDERIVExxx, FMAVCATGRxxx, FMGLFLEXx are missing after Client Copy

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:

2309831 - FINBASIS transport tool client cascade logic ends with errors during support package post processing

2556616 Difference in signature of function module FINB_TR_AFTER_IMP_EXEC between ECC and S/4HANA version

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).
If the dump relates to PSM-FG derivation strategies, make sure Note 2438171 - Remote client copy fails with dump DYNPRO_SEND_IN_BACKGROUND is implemented



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:

1675451 - How to analyze differences in derivation strategies


Useful Tables / Tcodes / Reports


Tables:
TABADRS: Derivation Steps
TABADRSF: Steps and fields
T000 for proper logsys identification

Transaction codes:

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

Reports:

ABADRCHECK


Related Content:


Related Documents


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 -

1231815 - Predefined FMDERIVE tables are renamed during transport/CC

1235955 - Client Copy: Derivation rule tables are not copied

1675451 - How to analyze differences in derivation strategies

1785263 - FMDERIVE00* tables deleted during after import process