FAGL_SWITCH_LEAD_LDG - Technische Umstellung der f�hrenden Sicht im neuen Hauptbuch
The following messages are stored in message class FAGL_SWITCH_LEAD_LDG: Technische Umstellung der f�hrenden Sicht im neuen Hauptbuch.
It is part of development package FAGL_SWITCH_LEADING_LEDGER in software component FI-GL-FL. This development package consists of objects that can be grouped under "Technical Changeover of Leading View in General Ledger (New)".
It is part of development package FAGL_SWITCH_LEADING_LEDGER in software component FI-GL-FL. This development package consists of objects that can be grouped under "Technical Changeover of Leading View in General Ledger (New)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Multiple active switch projects exist |
| 001 | You do not have authorization for activity &2 in plan &1 |
| 002 | Ledger &2 is defined as leading ledger (&1 is invalid) |
| 003 | Ledger &1 is not defined for application &2 &3 |
| 004 | Ledger &1 is not defined as new leading ledger |
| 005 | Business function FIN_GL_CHNG_LEAD_VAL is not active |
| 006 | A switch project is still active: &1 |
| 007 | Switch project is active and therefore cannot be deleted |
| 008 | Internal error |
| 009 | Check was run for: previous leading ledger &1 |
| 010 | Check was run for: future leading ledger &1 |
| 011 | Check was run for: date of switch &1 |
| 012 | Choose a non-leading ledger |
| 013 | Posting with ledger group &1 in year &2 is not possible |
| 014 | Switch project from year &1 is still active; check this project |
| 015 | Internal error: Activity &1 is not modeled |
| 016 | Switch project could not be activated |
| 017 | &1 is not a permitted transaction for this program |
| 018 | Prerequisites for switching leading ledger have not been met |
| 019 | This message does not have a long text |
| 020 | Switch project cannot be stopped; postings already exist |
| 021 | Switch project is active and cannot be changed |
| 022 | Execution |
| 023 | The requested exception &1 is not permitted |
| 024 | A switch project does not exist |
| 025 | Switch project &1 has an undefined status |
| 100 | Check on company code assignment |
| 101 | Ledger &1 is activated in all company codes |
| 102 | Ledger &1 is not activated in all company codes |
| 103 | Check on company codes |
| 104 | Check for company code &1 |
| 105 | Ledger &1 is not implemented in company code &2 |
| 106 | Documents exist in company code &1 as of fiscal year &2 |
| 107 | No documents exist in company code &1 as of fiscal year &2 |
| 108 | Local crcy type &1 inconsistent: old leadg ldgr: &2, new leadg ldgr: &3 |
| 109 | Matching fiscal year variant &1 in fiscal year &2 |
| 110 | Fiscal year start &1 is inconsistent: &2 &3 |
| 111 | Fiscal year end &1 is inconsistent: &2 &3 |
| 112 | Ledger-specific documents exist for Treasury/Loans components |
| 113 | Scenario &1 is not assigned to ledger &2 |
| 114 | Cannot change leading ledger; FI-AA (new) not active |
| 115 | Activity was not completed successfully |
| 116 | Date &1 is not start of fiscal year in company code &2 |
| 117 | No fiscal year variant is defined for company code &1 |
| 118 | Leading ledger was reset to &1 |
| 119 | Period start &1 in variant &2 differs from &3 variant &4 |
| 120 | Period end &1 in variant &2 differs from &3 variant &4 |
| 121 | Identical fiscal year start for variant &1 &2 in year &3 |
| 122 | Identical fiscal year end for variant &1 &2 in year &3 |
| 123 | Update of classic G/L accounting (GLT0) is no longer possible |
| 130 | Checking ledger-specific documents |
| 131 | Ledger-specific documents already exist in &2 in company code &1 |
| 132 | Ledger-specific documents in company code &1 checked successfully |
| 133 | Ledger-specific documents excluded from checks: |
| 134 | Exception defined for project start: Document &1 &2 &3 |
| 135 | Check scenarios |
| 140 | Ledger group check |
| 141 | Ledger group &1 changed by switch project |
| 199 | Ledger-specific documents excluded from checks: |
| 200 | Exception defined for project start: Document &1 &2 &3 |
| 201 | Switch project does not have the required status for this step |
| 202 | Activity was completed successfully |
| 203 | Activity was not performed successfully; see message log |
| 204 | This step is not required in the current status |
| 205 | Project status was changed; new status: &2 |
| 206 | &1: Lock is activated |
| 207 | &1: Lock is deactivated |
| 208 | &1: possible |
| 209 | &1: not possible |
| 210 | You have not confirmed |
| 221 | Leading ledger was switched from &1 to &2 |
| 222 | &1 is already the leading ledger |
| 223 | Ledger group &1: Representative ledger switched from &2 to &3 |