Hierarchy
⤷ CA-GTF-COR (Application Component) Correspondence Tool
⤷ FS_CORR_RECEIVER (Package) Recipient Management
Basic Data
Data Element | RCV_DTE_DYN_REC_DET_FILTER_ID |
Short Description | BAdI Filter Value for Dynamic Recipient Determination |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | RCV_REC_DET_EXT_FILTER_ID | |
Data Type | CHAR | Character String |
Length | 20 | |
Decimal Places | 0 | |
Output Length | 20 | |
Value Table | TRCV_FILTERID_CS |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | Filter Val |
Medium | 15 | BAdI Filter Value |
Long | 20 | BAdI Filter Value |
Heading | 20 | BAdI Filter Value |
Documentation
Definition
The filter value is used as the filter for Business Add-In (BAdI) RCV_DYN_REC_DETERMINATION.
Use
There are various customer enhancements for dynamic recipient determination of the RCV_DYN_REC_DETERMINATION BAdI, and you want to include these in your processes. For each customer enhancement you want to use, define at least one BAdI filter value for dynamic recipient determination and assign the BAdI filter values to it. As a result, the filter values become visible in rule processing and they can be assigned to the various processes. Once you have assigned the appropriate BAdI implementation to each filter value (see the BAdI documentation), the system can determine recipients dynamically for each process.
Dependencies
Along with static recipient determination, your processes need to have dynamic (algorithmic) recipient determination. In that case, you have to specify that dynamic recipient determination is allowed in the control parameters for recipient determination.
Example
History
Last changed by/on | SAP | 20110908 |
SAP Release Created in | 710 |