SAP ABAP IMG Activity BC_ADK_ROUT_BADI (BAdI: Archive Routing)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-CCM-ADK (Application Component) Archive Development Kit
     ⤷ S_ARCH_ROUTING (Package) Archive Routing
IMG Activity
ID BC_ADK_ROUT_BADI BAdI: Archive Routing  
Transaction Code S_BCE_68002213   (empty) 
Created on 20041222    
Customizing Attributes BC_ADK_OPTIONAL   Data Archiving - Optional Activity 
Customizing Activity BC_ADK_ROUT_BADI   BAdI: Archive Routing 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name ARCH_ROUTING_EXTERN    

Use

This Business Add-In (BAdI) is used in the data archiving component Data Archiving (BC-CCM-ADK).

You can use this BAdI to replace the standard Archive Routing process with your own coding.

An active implementation of this BAdI completely replaces Archive Routing for the corresponding archiving object. The system then uses neither the routing rules entered in Customizing for Archive Routing, nor the content repository entered in technical Customizing (V_ARC_USR). Also, any application-specific extensions are not taken into consideration. The basic concept, however, remains intact and the content repository, the logical file name, or the path extension is still determined based on the selection variant of the write program.

The BAdI is always called when Archive Routing is executed:

  • When an archiving session is started (for ADK and XML archiving)
  • When you store an archive file (only in ADK archiving)
  • When an archive file is stored (only for ADK-based archiving)

The BAdI has four methods:

Requirements

Standard settings

The standard does not have an active implementation for this Business Add-In.

The BAdI is filter-dependent. You can create a separate implementation for each archiving object.

Activities

After you call the IMG activity, the system displays a dialog box where you enter a name for the implementation.

If implementations of this Business Add-In have already been created, the system displays them in a dialog box. You then choose one of them by choosing Create, and continue as follows:

  1. In the dialog box, enter a name for the implementation of the Add-In and choose Create.
    The system displays the initial screen for creating Business Add-In implementations.
  2. On this screen, enter a short description for your implementation in the Implementation Short Text field.
  3. If you choose the Interface tab, you will notice that the system has populated the Name of the Implementing Class field automatically, by assigning a class name based on the name of your implementation.
  4. Save your entries and assign the Add-In to a package.
  5. To edit a method, double-click its name.
  6. Enter your implementation code between the method <Interface Name>~<Name of Method>. and endmethod. statements.
  7. Save and activate your code. Navigate back to the Change Implementation screen.
    Note: You can also create an implementation for an Add-In and not activate it until later. If you want to do this, do not perform the following step:
  8. Choose Activate.
    When the application program is executed, the code you created is run through.

Example

For sample coding for this BAdI, see the implementation for the method PARAMS2CREP. To display the sample coding, choose Goto -> Example Coding -> Display.

Activating this implementation for archiving object SD_VBAK would have the following effects:

  • The user is forced to enter exactly one sales organization. It is not possible to make mulitple entries, or to enter samples or intervals.
  • The user is forced to enter exactly one interval for the selection of the creation date. The interval must always contain exactly one calendar year. It is not possible to archive across years, nor is it possible to archive only part of a year.
  • The content repository used to store the archive files has the following structure: "CR<Sales Organization><year created>". Due to this restriction, you can easily determine a unique content repository for each archiving session.
    This coding does not, however, check whether this Content Repository exists.

For more information, see:

Method
PARAMS2CREP
PARAMS2PATH_EXTENSION
ALL_PATHEXTS_GET

Business Attributes
ASAP Roadmap ID 257   Create User Exits 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Maintenance Objects
Maintenance object type E   Business Add-In - Definition 
History
Last changed by/on SAP  20041227 
SAP Release Created in 700