Hierarchy
SAP_ABA (Software Component) Cross-Application Component⤷
CA-GTF-BS (Application Component) Business Application Support⤷
FCUR (Package) Expiring Currencies
IMG Activity
| ID | ACC_CA_N_U_AOEXW | Define warning and error dates |
| Transaction Code | S_P99_41000081 | (empty) |
| Created on | 19990429 | |
| Customizing Attributes | ACC_CA_N_U_AOEXW | Define warning and error dates |
| Customizing Activity | ACC_CA_N_U_AOEXW | Define warning and error dates |
Document
| Document Class | SIMG | Hypertext: Object Class - Class to which a document belongs. |
| Document Name | ACC_CA_N_U_AOEXW |
In this IMG step you can enter for each of the expiry reasons you have defined the predefined SAP object types as required, e.g. sales order. You can also enter a date for a warning and/or error message for each link between expiry reason and object type.
If you enter a warning and error date for the link, take care that
- the warning date is earlier than the error date
- in case of expiring EMU participating currencies the error date is earlier or the same as the anticipated expiry date of 06.30.2002
For company code-dependent object types you can also enter the company code for which the warning and error date checks are to take place. If you do not enter a company code for a company code-dependent object type, the warning and error date checks are made for all company codes. If the object type is not company code-dependent, the system does not run the check on a company code level and you cannot restrict the check to a company code. Entering a company code for the object type concerned results in an error message.
You can leave the fields for both the object type and the company code blank. This serves as a placeholder and means that the entry is valid for any object type and and company code.
When creating an object of object type "OBJECT" in company code "BUKR" a check is made with the following ranking against the entries of an expiry reason:
1. If an entry for object OBJECT and company code BUKRS is found, then this is taken.
2. If this is not the case, a search is made for the object type OBJECT and empty company code.
3. If this is not found, a check is made whether an entry exists with empty object type and company code BUKRS.
4. If this also does not exist, a search is made for an entry with empty object type and empty company code is made.
5. If none of the entries 1 to 4 have been maintained, a warning or error message is issued.
The entries are sorted according to this ranking automatically after saving. The entries with filled object type and company code at the top, the generic entries with empty fields at the bottom.
The check is always made against the entry that "fits the best", i.e. that is the nearest to the top of the list.
If the warning date has been reached, a warning is issued when creating or changing an object that informs you that the currency being used is expiring. The user can change the currency at this point, but he must not do so.
If the error date has been reached, an error message is issued and the user is forced to enter a valid currency, if this is a dialog transaction. For non-dialog transactions the entry is corrected to the new currency without the user having to enter it manually.
Business Attributes
| ASAP Roadmap ID | 201 | Make global settings |
| Mandatory / Optional | 3 | Nonrequired activity |
| Critical / Non-Critical | 2 | Non-critical |
| Country-Dependency | A | Valid for all countries |
Assigned Application Components
| Documentation Object Class | Documentation Object Name | Current line number | Application Component | Application Component Name |
|---|---|---|---|---|
| SIMG | ACC_CA_N_U_AOEXW | 0 | HLB0006312 | Business Application Support |
Maintenance Objects
| Maintenance object type | C | Customizing Object |
| Assigned objects | ||||||
|---|---|---|---|---|---|---|
| Customizing Object | Object Type | Transaction Code | Sub-object | Do not Summarize | Skip Subset Dialog Box | Description for multiple selections |
| V_TCURY | V - View | OEXW |
History
| Last changed by/on | SAP | 19990901 |
| SAP Release Created in |
