Collect BRFplus functions for the product to be transported

The BRFplus functions assigned to the product version or its attributes are determined in this step. When the BRFplus functions are distributed, the system ignores any functions that are defined as being inactive in the product and does not distribute them in the target system.

Check all functions for syntax and consistency errors and future changes

Distribution of BRFplus functions always observes the most recent version of the BRFplus function in each case. If execution-relevant future changes are available for one of these functions, the system displays a corresponding error message in the transport log. The transport cannot be performed in this case. A new product version must first be generated for the product using the most recent version of the BRFplus function. The system then performs a syntax check for all functions. If one of the functions contains an error, the product transport cannot be performed and is terminated with a corresponding error message in the log.

Simulation of Function Distribution

To check whether functions can be distributed, in the next step, the system performs a simulation of BRFplus distributiion for all BRFplus functions in the target system. It specifically checks dependencies of other functions or DDIC objects. It can for example be the case that a static ABAP method is used in a BRFplus expression, which does not (yet) exist in the target system. The simulation prevents the product transport being performed here using error messages in the log and therefore avoids inconsistencies being created in the target system. The simulatuion does not change any productive data in the target system and all process steps required are performed in separate objects. Productive operations are never affected by this.

Distribution of Functions to the Target System

Following a successful simulation of the distribution of all BRFplus functions linked to the product, the actual distribution is performed in the final step. Assigning an individual time stamp for each function distributed and storing this time stamp in the product in the target system ensures that the correct version of the BRFplus function is uniquely assigned. This ensures specifically that importing product versions whose validity starts on a future date does not affect existing versions of the product or other products or BRFplus functions that they have reused.