The functionality Inbound Correspondence is used to determine the due date by which a business partner is obliged to submit a declaration (e.g. a tax demand)
Transactions
| FMCAINCOC | Create Inbound Correspondences |
| FMCAINCOH | Process Inbound Correspondence |
| FMCAM1 | Generate Inbound Correspondences |
| FPCODU | Correspondence Dunning |
| FPCODUH | Correspondence Dunning History |
|
Transaction
|
Description
|
|---|
Customizing
- FICAIMG → Contract Accounts Receivable and Payable → Business Transactions → Inbound Correspondence
- FICAIMG → Contract Accounts Receivable and Payable → Business Transactions → Inbound Correspondence Dunning
Mass activities
The following two entries from table TFK090A are relevant:
| CODU | 1746 | 1747 | FPCODU | Mass Activity: Dunning Correspondence |
| P700 | P700 | P701 | FMCAM1 | Generate Inbound Correspondences |
|
AKTYP |
EVE_ITVL |
EVE_PARA |
TCODE |
AKTXT
|
|---|
FI-CA-Events
|
Event
|
Description
|
|---|---|
| 0759 | Inbound Correspondence: General Actions |
| 0761 | Inbound Correspondence: Reminder Days Before Due Date |
| 1746 | Mass Activity: Dunning Incoming Correspondence |
| 1747 | Mass Activity: Dunning Incoming Correspondence, Move Params |
| P100 | PSCD Inbound Correspondence: Due Date |
| P101 | PSCD Inbound Correspondence: Additional Data |
| P700 | PSCD Mass Activity: Inbound Correnspondence |
| P701 | PSCD Inbound Correspondence: Parameter Shift |
| P702 | PSCD Inbound Correspondence: Print Form |
| P703 | PSCD Inbound Correspondence: Generate Form |
| P704 | PSCD Inbound Correspondence: Notification |
| P705 | PSCD Inbound Correspondence: Re-Generation |
| P710 | PSCD Inbound Correspondence: Generation |
| P711 | PSCD Inbound Correspondence: Follow-up Actions After Gener. |
| P712 | PSCD Inbound Correspondence: Sample Document |
Posting Areas
| P052 | Activate Enhanced Inbound Correspondence | Enhancement Active | ACTIVE |
| P053 | Settings for Enhanced Inbound Correspondence | Reminder Letter, Period-independent, Automatic Adjustment | REMINDER, PERIOD_INDEPENDENT, AUTOM_ADAPT |
|
Posting Area
|
Description
|
Available Functions
|
Techn. Field Names
|
|---|
Technical information
Package
| FKKC | Contract Accounts Receivable and Payable: Correspondence |
| FKKCORR | Correspondence Tool |
| FMCAD | PSCD: Inbound Correspondence |
|
Package
|
Description
|
|---|
Function Groups / Programs
| FKK2_IN | SAPLFKK2_IN | FI-CA Correspondence: Inbound Corresp. |
| FKK2_IN_DU | SAPLFKK2_IN_DU | FI-CA Corresp.: Inbound Corresp. Dunning |
| FKKCORR_CUSTOM | SAPLFKKCORR_CUSTOM | Correspondence: Customizing Access |
| FMCA_INCORR | SAPLFMCA_INCORR | PSCD: Inbound Correspondence |
| FMCA_INCORR_CAL | SAPLFMCA_INCORR_CAL | PSCD:Calendar for Inbound Correspondence |
|
Function Group
|
Program
|
Description
|
|---|
Tables
| DFKKCOHINCORR | Correspondence – Data for Inbound Correspondence |
| DFMCA_INCORR_CR | Generated Inbound Correspondence Request for Category/Period |
| TFK_INCORR | Inbound Correspondence Categories |
| TFK_INCORR_REFTY | Reference Type for Correspondence |
| TFMCA_INCORR_FRM | Relationship Between Inbound Corr. Category and Form Type |
| TFMCA_INCORR_PER | Period Definition for Inbound Correspondence |
| TFMCA_INCORR_PR | Preprints for Inbound Correspondence |
| TFMCA_INCORR_PRT | Description on Forms for Inbound Correspondence |
| TFMCA_INCORR_RL | Time-Dependent Definition of Enhanced Inbound Correspondence |
| TFMCA_INCORR_RVP | Assignment of Inbnd Corresp. Category to VKTYP and PSOBTYP |
|
Table
|
Description
|
|---|
Reports
| RFKKCO06 | Correspondence Dunning History | FPCODUH |
| RFMCA_INCORR_CANCEL | Reverse Inbound Correspondence Requests | n/a |
| RFMCA_INCORR_CHECK_CUST | Check Customizing for Enhanced Inbound Correspondence | n/a |
| RFMCAP700 | Process Inbound Correspondence | FMCAINCOH |
| RFMCAP700_CREATE | Generate Inbound Correspondences | FMCAINCOC |
|
Report
|
Description
|
Transaction
|
|---|
Function Modules
| FKK_CORR_DUNN_REVERSE | Reverse Correspondence Dunning |
| FKK_CORR_DUNN_SELECT | Select Correspondence Dunning |
| FKK_CORR_DUNNING_DESIRED | Check if Correspondence Dunning is desired? |
| FMCA_INCORR_CREATE_MASS | Massenerzeugung von Eingangskorrespondenzanforderungen |
| FMCA_INCORR_CREATE_SINGLE | Erzeugen einer einzelnen Eingangskorrespondenzanforderung |
| FMCA_INCORR_ENH_ACTIVE | Erweiterte Eingangskorrespondenzen aktiv ? |
| FMCA_INCORR_GET | Gibt eine Eingangskorrespondenz zurück |
| FMCA_INCORR_HISTORY | Eingangskorrespondenzhistorie |
| FMCA_INCORR_SELECT | Selektiert zu Kriterien (Struktur FMCA_INCORR) |
|
Function Module
|
Description
|
|---|
Message Class
FMCA_INCORR
Authorization Object
P_CORR
Archiving Object
- CORRSPND
- FI_MKKCORR
Inbound Correspondence (Conventional)
You use this function to determine the due date by which a business partner is obliged to submit a declaration (for example, a tax demand) unprompted. To do this, you specify the control data for inbound correspondence in a contract object. In the case of an obligation to submit declaration, a data record is generated which you can use as Inbound Correspondence for further processing.
Inbound correspondence is completed (fulfilled) as soon as a reply to the request has been received and the date of receipt has been entered. In addition to this confirmation of received correspondence, you can also set a deferral date or a dunning block indicator for the inbound correspondence. You can use the correspondence dunning run to select correspondence which arrives after the due date and generate the necessary dunning notice using the correspondence print. It is also possible to generate reminders for inbound correspondence within a dunning run.
You have to make the settings in Customizing for inbound correspondence under Financial Accounting → Contract Accounts Receivable and Payable → Business Transactions → Inbound Correspondence →
Define Status for Creating Inbound Correspondence
Define tolerance of due date for inbound correspondence
Define Inbound Correspondence for Shortened Periods
IMG activities for Dunning Inbound Correspondence
If you have activated the enhanced inbound correspondence, you can no longer create new conventional inbound correspondence.You can however still display and process those that already exist.
Process Flow
The following section lists the steps you need to carry out for inbound correspondence and the functions you can use.
The diagram below shows the functional connection between master data objects (contract objects), the table entries (data records for inbound correspondence) in the correspondence history and the executable activities.
Activating and Setting Up Inbound Correspondence
You specify the obligation for inbound correspondence at contract object level by choosing a period interval (for example, weekly, monthly or yearly) for the inbound correspondence.
For more information, see Controlling Inbound Correspondence .
Generating Inbound Correspondence
When you run this program, the settings for inbound correspondence data in the contract objects are taken into account and current (new) entries are generated as data records in the correspondence history.There are two ways of generating inbound correspondence:
You execute a mass run for more than one contract object at the same time.
You can find more information under Mass Run: Generating Inbound Correspondence
You generate inbound correspondence specifically for a single contract object.
For more information, see Individual Maintenance: Inbound Correspondence in the Contract Object .
Editing Inbound Correspondence
You edit inbound correspondence in the correspondence history. There are two ways of editing inbound correspondence:
You can edit general correspondence history for several contract objects at the same time.
For more information, see Edit Correspondence History .
You can edit a specific contract object in the inbound correspondence history.
For more information, see Maintaining Inbound Correspondence History .
Execute Correspondence Dunning Run
You can generate reminders or dunning with this mass run according to the correspondence dunning run category for inbound correspondence.
You can find more information under Generating Correspondence in Mass Run .