Hierarchy
BBPCRM (Software Component) BBPCRM⤷
CRM (Application Component) Customer Relationship Management⤷
CRM_APPLICATION (Package) All CRM Components Without Special Structure Packages⤷
FBK (Package) Vendors
Basic Data
| Data Element | DISPW |
| Short Description | Planned currency for cash management and forecast |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | WAERS | |
| Data Type | CUKY | Currency key, referenced by CURR fields |
| Length | 5 | |
| Decimal Places | 0 | |
| Output Length | 5 | |
| Value Table | TCURC |
Further Characteristics
| Search Help: Name | ||
| Search Help: Parameters | ||
| Parameter ID | FDW | |
| Default Component name | PLANNED_CURRENCY | |
| Change document | ||
| No Input History | ||
| Basic direction is set to LTR | ||
| No BIDI Filtering |
Field Label
| Length | Field Label | |
| Short | 10 | Currency |
| Medium | 20 | Planned currency |
| Long | 33 | Planned currency |
| Heading | 7 | Curr. |
Documentation
Definition
Key of the currency in which amounts are managed in the system. If the currency key is different from the local currency key of the company code, then the system also manages the amount fields for memo records or postings in the foreign currency.
In the cash management and forecast, the update is made in the document currency; in sub-ledger accounts, it may be made in the alternative payment currency if necessary.
Exception:
- Postings to bank accounts (without open item management) are updated in the G/L account currency. These postings are usually the result of the account statement being created.
Pre-posted transactions (such as parked documents, payment orders, payment requests, plan values from Treasury, and cash management advice notes) are updated in the document currency, however, because the transactions will become postings at a date in the future, and so still involve a currency risk. In addition, these transactions are not managed on an open item basis and so the concatenation logic cannot be divided up by means of open item management.
History
| Last changed by/on | SAP | 19990326 |
| SAP Release Created in |
