definition load for a global class (6.20 SP25) required?
Die Frage ist als "gelöst" markiert. Den entsprechend Beitrag findest du hier.
5 Beiträge
•
Seite 1 von 1
5 Beiträge
Seite 1 von 1
Does anyone know if there is a setting for allowing or not allowing the direct access to components of global classes in ABAP OO?
The same source code on one machine (WAS 6.20 SP25) works without any problems and generates syntax error on another one with the same release and SP. We have just got a new test environment which for soem reason doesn't accept the source code form DEV system.
The error message:
Direct access to components of the global class /SAPDII/CL_VMS_ACTION
is not possible (CLASS /SAPDII/CL_VMS_ACTION DEFINITION LOAD statement is missing).
P.S. Selbstverstaendlich jede Antwort in DE oder EN ist gern gesehen
The same source code on one machine (WAS 6.20 SP25) works without any problems and generates syntax error on another one with the same release and SP. We have just got a new test environment which for soem reason doesn't accept the source code form DEV system.
The error message:
Direct access to components of the global class /SAPDII/CL_VMS_ACTION
is not possible (CLASS /SAPDII/CL_VMS_ACTION DEFINITION LOAD statement is missing).
P.S. Selbstverstaendlich jede Antwort in DE oder EN ist gern gesehen
gesponsert ⓘ
Stellenangebote auf ABAPforum.com schalten
kostenfrei für Ausbildungsberufe und Werksstudenten
kostenfrei für Ausbildungsberufe und Werksstudenten
Hi,
It seems that in your sourcecode where you try to use the mentioned class the following statement is missing:
Insert above statement before creating instance of this class.
Regards,
Steff
It seems that in your sourcecode where you try to use the mentioned class the following statement is missing:
Code: Alles auswählen.
CLASS CL_VMS_ACTION DEFINITION LOAD.
Regards,
Steff
Hi,
adding this statement is an obvious solution ... but, the whole application in DEV is written without it and it works. Now after transporting the development to TST wthe problem occured.
We would have to trace every possible place in DEV, where we would have to add it, whiche is a considerable effort.
I would rather try to find out WHY it happens?
thanks
adding this statement is an obvious solution ... but, the whole application in DEV is written without it and it works. Now after transporting the development to TST wthe problem occured.
We would have to trace every possible place in DEV, where we would have to add it, whiche is a considerable effort.
I would rather try to find out WHY it happens?
thanks
Beitrag
von Frank Dittrich (Expert / 674 / 0 /
15
)
»
I'm sure the CLASS /SAPDII/CL_VMS_ACTION DEFINITION LOAD statement exists in the DEV system. May be it's in an include, and the other system still uses an older version of this include.
I suggest you do a global search for CL_VMS_ACTION (just in case the / in the prefix is causing trouble) in the source code of your main program.
I'm sure there's a CLASS /SAPDII/CL_VMS_ACTION DEFINITION LOAD statement somewhere.
(If the text search doesn't find this statement, may be it's included in a macro definition ...)
Frank
I suggest you do a global search for CL_VMS_ACTION (just in case the / in the prefix is causing trouble) in the source code of your main program.
I'm sure there's a CLASS /SAPDII/CL_VMS_ACTION DEFINITION LOAD statement somewhere.
(If the text search doesn't find this statement, may be it's included in a macro definition ...)
Frank
Hi Frank,
It can't be, because the TST is build on transports from DEV. So the source code should be the same.
It's not only CL_VMS_ACTION which caused this problem. In any place where we used parameters from global classes in DEV we had the same problem. We have already solved it by analyzing the code and adjusting it accordingly (adding the DEFINITION LOAD) in DEV and transporting to TST. We had like 30 occurences for about 10 classes (SAP standard and Custom ones).
I still don't know why TST behaves different, but at least we have a working application.
thanks, Jan
It can't be, because the TST is build on transports from DEV. So the source code should be the same.
It's not only CL_VMS_ACTION which caused this problem. In any place where we used parameters from global classes in DEV we had the same problem. We have already solved it by analyzing the code and adjusting it accordingly (adding the DEFINITION LOAD) in DEV and transporting to TST. We had like 30 occurences for about 10 classes (SAP standard and Custom ones).
I still don't know why TST behaves different, but at least we have a working application.
thanks, Jan
Seite 1 von 1
Vergleichbare Themen
0
Antw.
Antw.
5649
Views
Views
Fehlerhafte interne Währung in Zahlungsdatei nach Upgrade auf EHP7 SP25
von Doobie » 29.11.2023 15:45 • Verfasst in Financials
von Doobie » 29.11.2023 15:45 • Verfasst in Financials
6
Antw.
Antw.
31511
Views
Views
ALV OO Set_table_for_first_display Load Layout YES/Change NO
von RIG » 29.01.2018 14:36 • Verfasst in ABAP® für Anfänger
von RIG » 29.01.2018 14:36 • Verfasst in ABAP® für Anfänger
2
Antw.
Antw.
1322
Views
Views
PDF Dokument im SAP global abspeichern
von ABAPlerv » 15.06.2022 13:05 • Verfasst in ABAP® für Anfänger
von ABAPlerv » 15.06.2022 13:05 • Verfasst in ABAP® für Anfänger
1
Antw.
Antw.
417
Views
Views
Frage die ABAP Experten
Über diesen Beitrag
Die Frage ist als "gelöst" markiert. Den entsprechend Beitrag findest du hier.
Unterstütze die Community und teile den Beitrag für mehr Leser und Austausch
Aktuelle Forenbeiträge
Custom logic - Feld wieder initialisieren (BADI CRMS4_SERV_CUST_H_MODIFY)
vor 6 Tagen von JanR 1 / 1776
vor 6 Tagen von JanR 1 / 1776
Newsletter Anmeldung
Keine Beiträge verpassen! Wöchentlich versenden wir lesenwerte Beiträge aus unserer Community.Die letzte Ausgabe findest du hier.
Aktuelle Forenbeiträge
Custom logic - Feld wieder initialisieren (BADI CRMS4_SERV_CUST_H_MODIFY)
vor 6 Tagen von JanR 1 / 1776
vor 6 Tagen von JanR 1 / 1776
Unbeantwortete Forenbeiträge
Custom logic - Feld wieder initialisieren (BADI CRMS4_SERV_CUST_H_MODIFY)
vor 6 Tagen von JanR 1 / 1776
vor 6 Tagen von JanR 1 / 1776
F6862 - Stücklistenpositionen Massenhinzufügen ohne Änderungsnummer
April 2026 von Radinator 1 / 57912
April 2026 von Radinator 1 / 57912
HR Forms (SAP HCM): Anwenderdokumentation, Anleitung oder Schulungsunterlagen gesucht
April 2026 von PatHei 1 / 30997
April 2026 von PatHei 1 / 30997