Kontakt

Ansicht
Dokumentation

SFW_TRANSP_EXT_BCSET_ENTRIES - Transport BC sets entries for Switched on Enterprise Extensions

SFW_TRANSP_EXT_BCSET_ENTRIES - Transport BC sets entries for Switched on Enterprise Extensions

RFUMSV00 - Advance Return for Tax on Sales/Purchases   BAL Application Log Documentation  
This documentation is copyright by SAP AG.
SAP E-Book

Purpose

This report can be used to unpack classic BC sets related to switched-on Enterprise Extensions in the current system and transport the BC set entries to a productive system where the Enterprise Extensions are already switched on.

There are 2 possible scenarios where this report is useful:

  1. Switch Framework settings cannot be transported to productive system because not all business functions in the DEV or QA system can be activated in target system. This target system contains at least one client with client-role 'Production'.
    Since it is not possible to use online transaction to activate BC sets in a productive system, this report can be used in source system in order to transport all BC set entries for the switched on Enterprise Extensions
  2. Switch Framework Settings were imported in a productive system activation of the classic BC sets failed.
    BC set activation errors are found in the transport log for Phase 'Method Execution' (after import).
    This report has to be executed in the source system where the Switch Framework transport was created.
    Extension BC set entries have to be transported to the target system where the BC set activation failed.

Integration

Bridges the gap between Switch Framework Enterprise Extension activation and its classic BC set activation in a productive system.

This report is a complement to online BC set activation (transaction SCPR20) and can be used to avoid activating manually all the necessary BC sets.

This report can be executed directly from transaction SE38/SA38 in foreground or in background or through transaction SFW1 by selecting option 'Activate Dependent BC sets' when a switch from an Enterprise Extension is displayed.

Activation logs can be displayed from:

  • transaction SFW1, using menu: Goto-> BC-Set Logs
  • transaction SFW5, using menu: Goto-> BC Set Logs

Prerequisites

Enterprise Extensions are already switched on in the current system.

Features

Selection

  • List Selection,,All Switched on Extensions - or - Selected Switched on Extensions
  • Extensions: ,,,,Enterprise Extensions can be selected in case Enterprise Extensions switched on in the source are different than the ones in the target system.

    For example, in your development system you have switched on extensions which are not yet switched on in your production system. In this case, you do not want to transport these BC set entries to your production system. Therefore, you have to select a range of Enterprise Extensions for which the BC set entries have to be transported to a productive system.
    BC set names follow this naming convention: -AKH, -MENU, -IMG
  • Request/Task:,,Transport request in which the BC set entries are recorded. If not supplied, the user will be requested to choose an existing one or to create a new one.
  • Log:,,,,,,File log is written and can be displayed immediately. Otherwise, BC set logs can be displayed from transaction SFW1 - Maintain Switches. Use menu Goto-> BC-Set Logs

Standard Variants

None

Output

  • Entries in transport request
  • File log which can be displayed immediately or using transactions SFW1 and SFW5 later on, , as well as general file log display (transaction AL11).

Activities

Example






ROGBILLS - Synchronize billing plans   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by SAP AG.

Length: 3998 Date: 20240601 Time: 183702     sap01-206 ( 66 ms )