SAP ABAP Data Element TB_OBLRECO (Counterconfirmation required?)
Hierarchy
☛
SAP_APPL (Software Component) Logistics and Accounting
⤷ TR (Application Component) Treasury
⤷ FTA_CORE (Package) TR-CORE: Former Objects from FTA (Applic. Dev. TR General)
⤷ TR (Application Component) Treasury
⤷ FTA_CORE (Package) TR-CORE: Former Objects from FTA (Applic. Dev. TR General)
Basic Data
Data Element | TB_OBLRECO |
Short Description | Counterconfirmation required? |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | XFELD | |
Data Type | CHAR | Character String |
Length | 1 | |
Decimal Places | 0 | |
Output Length | 1 | |
Value Table |
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 | Count.con. |
Medium | 19 | Counterconf. req. |
Long | 23 | Counterconf. required |
Heading | 1 | C |
Documentation
Definition
This entry allows you to control whether counterconfirmation from the business partner and Customizing settings in 'Define correspondence activities' are required.
Only if the setting has been made in both the relevant Customizing entry and in the standing instructions of the business partner is the 'Counterconfirmation required' status set in the transaction. An external correspondence type is a basic prerequisite for the counterconfirmation process.
A counterconfirmation (change of status to 'reconciled') is only possible if the outgoing confirmation has already been carried out.
Correspondence planned records can also be created manually. You can also set the 'Counterconfirmation required' parameter.
History
Last changed by/on | SAP | 20011002 |
SAP Release Created in |