Show TOC

Function documentationManual Correspondence Creation

 

You can create targeted correspondence manually in a Web Dynpro application.

Integration

In Financial Customer Care (FCC), you can create correspondence manually in the documentation view. You can access this view from the navigation bar or from the transaction for processing collection work items.

Prerequisites

You have defined correspondence templates for creating correspondence manually. (See Customizing for Contract Accounts Receivable and Payable under Start of the navigation path Basic Functions Next navigation step Correspondence End of the navigation path).

Features

The Web Dynpro application provides a framework with which you can:

  • Create correspondence manually and send it to the relevant recipients

  • Request inbound correspondence (only in the industry component Public Sector Contract Accounts Receivable and Payable (PSCD))

You enter the information required to create and request the correspondence in a guided procedure.

By configuring the relevant ISR scenario, you can check and approve the correspondence by workflow. (See the SAP Easy Access screen: Start of the navigation path Office Next navigation step Workplace End of the navigation path).

You print using the print workbench.

To make it easier to create and print correspondence that has a template based on an ISR scenario with PDF, SAP provides generic correspondence type 0400. To meet your own specific requirements, you can define your own correspondence types using the events 0781 and 0782. After the correspondence entries have been created in the correspondence container, you can trigger the printing of the correspondence in one of these ways:

  • As single print, on the SAP Easy Access screen, by choosing Start of the navigation path Account Next navigation step Further Information Next navigation step Correspondence History End of the navigation path

  • As mass printing, on the SAP Easy Access screen, by choosing Start of the navigation path Periodic Processing Next navigation step For Contract Accounts Next navigation step Correspondence Next navigation step Print End of the navigation path

You can load outbound and inbound correspondence into the Document Management Service (DMS). Depending on your system settings, you can, for example, load the image of printed correspondence to DMS and link it to the application object that triggered the correspondence. In a similar way, you can, upon request, load inbound correspondence to the DMS, and link it to the appropriate application object.

Using the following parameters, you can integrate the guided procedure in other Web Dynpro applications:

Name of the Web Dynpro application

FKK_WDY_CORR_MANUAL

Name of configuration of the Web Dynpro application

CORR_MANUAL_GAF_CONF

Name of the Web Dynpro component

FKK_WDY_CORR_MANUAL

You have the following enhancement options:

Step of Web Dynpro guided procedure

Enhancement option

1

The BAdI definition BADI_APPOBJ derives the master data set based on the application object ID and application object type. If you are using the industry component Public Sector Contract Accounts Receivable and Payable Inbound Correspondence, you can define this derivation in Customizing under Start of the navigation path Business Transactions Next navigation step Inbound Correspondence Next navigation step Inbound Correspondence (Enhanced) Next navigation step Define Inbound Correspondence Request Derivation Setting End of the navigation path.

2

You can implement the logic for deriving the correspondence address at event 0770.

3

The BAdI of the ISR scenario provides the following events for enhancements:

  • LOAD_DATA_EVENT

    This event runs in steps 2 and 3.

  • REFRESH_DATA_EVENT

    This event runs after the event of the Web Dynpro add-on; you can enhance the correspondence creation step in the Web Dynpro interface IF_FKK_WDY_CORR_ADDON.

  • CHECK_DATA_EVENT

    This event runs in steps 3 and 4.

In event 0787, you can derive the contents for individual correspondence recipients (such as, address in PDF-based form).

Activities

You make settings for the approval workflow as follows:

  1. In Customizing, choose Start of the navigation path Cross-Application Components Next navigation step Internet/Intranet Services Next navigation step Internal Service Request Next navigation step Scenario Definition Next navigation step Define Scenarios End of the navigation path.

  2. Create a scenario for the application MC (Manual Correspondence).

  3. At the Version level, enter Entry Using Adobe PDF as the Entry Type in Web.

    If you want the workflow to start before an entry is created in the correspondence container, enter CW as the Notification Type.

    (If you do not want to use a workflow, enter CD as the Notification Type. )

  4. Enter the Adobe form and the interface.

  5. At the Characteristics level, enter the characteristics for the interface of the interactive forms. Enter a function module for loading the correspondence data. If you want to use the data of the correspondence header (master data set, application object), define a characteristic of the type FKK_CORRM_EXTERNAL_DATA.

  6. Define a BAdI for additional functions (such as, generating address data).

  7. Generate the interactive form and create the layout for the correspondence.

  8. Choose the Additional Data for Scenario pushbutton. In the Create Notification field, enter workflow template WS31000009 for the ISR standard workflow.

  9. Choose the Assignment of Processors pushbutton to enter the users who are allowed to approve the correspondence requests.

  10. Activate the linkage for the ISR notification event CLOSED. To do so, on the SAP Easy Access screen, choose Start of the navigation path Tools Next navigation step Business Workflow Next navigation step Development Next navigation step Definition Tools Next navigation step Events Next navigation step Event Linkages Next navigation step Type Linkages End of the navigation path.