Show TOC

 Creating Correspondence Types and Their Events

Use

You want to create a correspondence type with its related correspondence-type-specific events in the context of the event concept, Business Add-In in Enhancement Framework .

Prerequisites

You clarified what data is needed for creating correspondence and which references and data you want to be stored in the correspondence container.

You meet all prerequisites for optical archiving.

You created application-specific events for your application, as described in Creating the Correspondence Request .

You are familiar with the concept of Business Add-Ins (BAdI) in Enhancement Framework .

Procedure

Report RFKKCORR_UTL_GENERATE_COTYP assists you in creating the definition of the correspondence type and the development objects of correspondence-specific events for the event concept Business Add-In in Enhancement Framework .

First use the Analyze Only function. This allows you to execute the report as often as you like and to check your entries. In its current version, the report does not delete any existing objects. To have reproducible results, we recommend that you create a report variant for each correspondence type.

  1. Start report RFKKCORR_UTL_GENERATE_COTYP and familiarize yourself with the necessary entries.

  2. Enter the correspondence type you want to create and start the report.

    The log contains information on any conflicts there might be with existing objects.

    If the definition of the correspondence type does not exist already, you can proceed as described below.

  3. Make the necessary entries and save them in your report variant.

    The following entries are required for creating a complete, new correspondence type:

    • Correspondence Name

    • Application area

    • Application indicator

    • Archive Structure (if applicable and if it exists)

    • BAdI Definition Name

    • Application Form (if you want an application form to be provided as a sample)

    • Enhancement Spot

      If you do not enter an enhancement spot, the system uses the BAdI definition name as the name of the enhancement spot. In the case of an existing enhancement spot, the BAdI is added to it.

    • Interface for BAdI Definition

    • Interface for Creating Correspondence Requests (if applicable and if it exists)

      Otherwise the system adds the method for creating correspondence requests to the interface of the BAdI definition.

    • Default Implementation of the BAdI

    • Use Cluster (if you want data to also be stored in a cluster)

    • Own Archiving Object (if you want to enable the documents created using the correspondence type to be optically archived, and you do not want the archiving object of the correspondence tool (BUS4401) to be used for this)

    • Package in which the development objects are entered

    • Generate Transport Request (if you want a new transport request to be created)

      Later you can also select an existing request.

  4. Run the report.

    The log again contains information on any conflicts there might be with existing objects. It also tells you if your entries are sufficient for generating the development objects, and if they meet your specifications.

  5. If generating the objects is possible, now choose the Analyze and Generate function. You cancel the log display by choosing with the quick info text Back. This starts the generation of the development objects and creation of the definition of the correspondence type. In the dialog box that appears, you have a final opportunity to prevent the generation. After that point, the system creates the following objects:

    • Interface for BAdI definition

    • Class of default implementation

    • Enhancement spot

    • BAdI definition

    • Definition of correspondence type

      The system displays the generated development objects in the ABAP Workbench . There you make any necessary modifications and additions and then activate the objects.

      You confirm all dialog boxes in accordance with your specifications and leave the ABAP Workbench by choosing with the quick info text Back . Once those steps are complete, and processing continues, you receive a log about the created or changed objects.

      If the development objects that were created do not meet your requirements, you can delete them and repeat the procedure using different values. When you repeat the procedure, the system displays the existing development objects, using the ABAP Workbench , and shows where you can change and activate them.

  6. Check and complete Customizing settings for the correspondence type. In Customizing for Correspondence, choose Start of the navigation path Cross-Application Components Next navigation step General Application Functions End of the navigation path :

    • Define Correspondence Types

    • Define Standard Form Classes for Correspondence

    • Define Application Forms for Correspondence

    • Archiving -> Define Archives for Paper Records

Result

You created or modified the development objects for correspondence-type-specific events and created or modified the definition of the correspondence type.