U7 - Japan-spezifische Entwicklungen
The following messages are stored in message class U7: Japan-spezifische Entwicklungen.
It is part of development package EE20_JBP in software component IS-U-BI. This development package consists of objects that can be grouped under "IS-U: Japanese Billing Preriod".
It is part of development package EE20_JBP in software component IS-U-BI. This development package consists of objects that can be grouped under "IS-U: Japanese Billing Preriod".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Constellation of Meter Readings Not Permitted |
| 001 | Error: System table &1 for key &2 (incorrect fixed value &3) |
| 002 | Error: System table &1 for key &2 (incorrect variable &3) |
| 003 | Meter reading reasons (&1) not permitted (see key &2) |
| 004 | BillPeriod &1 oper.group &2 MR scen &3: No resolutions for dialog |
| 005 | Bill.period &1 oper.group &2 MR scen. &3: No resolutions for mass proc. |
| 006 | Action terminated -> No selection made |
| 007 | Bill.per. &1 oper.grp &2 scen. &3 resolut. &4: No entries in ESOLEXEC |
| 008 | Billing period &1: No entries in EMRCLASS |
| 009 | Change billing period &1 <> &2 (meter readings &3 &4) |
| 010 | Activity day &1: Conflict with too many meter reading results (&2) |
| 011 | Activity day &1: Unnecessary Meter Reading Results (&2) (vs technology) |
| 012 | Activity day &1: Too many meter reading results (&2) |
| 013 | Activity day &1: Too many meter reading results and move-in/installation |
| 014 | Billing period &1: No entries in ERESOL |
| 015 | Activity day &1: unnecessary meter reading results (&2) (vs. billed/slg) |
| 016 | Activity Day &1: Unnecessary MR Results (&2) (vs. Move-In/Inst) |
| 017 | Reading error EMRCLASS (billing period &1 MR reason &2) (MR document &3) |
| 018 | MR document &1 MR reason &2 (insert opergroup &3 not poss. due to &4) |
| 019 | Activity day &1: Too many conflicts (-> reduce complexity) |
| 020 | Internal reading error field string &1 in &2 &3 |
| 021 | No entries in Customizing table &1 |
| 022 | Billing period cannot be changed at the moment |
| 023 | Billing period cannot be maintained for SBP at the moment |
| 024 | All division categories must have the same Customizing for JBP |
| 025 | Division category &1 is missing from billing period Customizing |
| 026 | Second meter reading for &1 not found |
| 027 | Too many technical meter readings in one activity day |
| 028 | No entries in system tabel &1 |
| 029 | Inpermissible call from &1 |
| 030 | No entries in system table &1 for billing period &2 |
| 031 | Billing period &1 MR reason &2: Error reading &3 |
| 032 | Error during &1 in &2 (access key &3) |
| 033 | Meter reading reason &1 not included in routine &2, include &3 |
| 034 | Inst. &1 sched. bill. date &2: End of billing period not determined |
| 035 | Division category &1 is missing from billing period Customizing |
| 036 | Billing order for &1 cannot be processed |
| 037 | BillPeriod &1 (register)is not the same as bill. period &2 (MeterReading) |
| 038 | Billing period &1 (meter reading &2) different to bill. period &3 (MR &4) |
| 039 | BillPeriod JBP: Field ADATREAL in MR document &1 is inconsistent |
| 040 | Meter reading document &1 has different billing period to MR document &2 |
| 041 | Billing period &1: No entries in ERESOL_CUST |
| 042 | Incomplete setting |
| 043 | Equi no. &1 scheduled MR date &2: Indefinite end of billing period |
| 044 | From date &1 (meter reading &2) later than to date &3 (meter reading &4) |
| 045 | Check OK: Resolution for Dialog Found |
| 046 | Check OK: Resolution for Mass Processing Found |
| 047 | Variant &4 bill. period &1 operand group &2 MR scen. &3: No solutn dialog |
| 048 | Variant &4, billper. &1 oper group &2, MR screen &3: No solutions mass R |
| 049 | Billing Periods not identical for all division categories |
| 050 | Too many MRs that trigger billing vs. technical MRs (reason &1) |
| 051 | Meter reading &1 (reason &2) conflicts with meter reading &3 (&4) |
| 100 | A division is required in the division-dependent shift |
| 150 | Conflict with meter reading results already entered in the system |