You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 2 Next »
Menu
Authorization objects
Addresses
STAADR / STAADRA / STAADRD / STAADRK / STADRG / STAADRP
Address blocks
STAADRBL
Address label
STAADR
Address types
STAADRTYP
Banks
Industry sector
STABRANCHEN
Release credit limit
STAKREDIT_FREIG
Interests
STAHOBBY / STASPORT
Classifications
STAKLAS
Account types
STAKTOTYP
Open est. invoice amounts
STASAMMEL_OP
QM Classifications
STAQMABC
Sales status
STASALESSTATUS
Sales representative
STAVERTRETER
Templates address quotations
STAOFFPO_TEMPKO
Type of certification
STAQMZERT
Tab / Function
Input
Altern. address layout
STAADRLAYOUT
Airfreight
STAADRAIRFREIGHT
Form sets
STAADRFORMSET
Billing codes
STAADRAART
Order templates
STAADRVORLAGEN
General
ADRERWEITERT
Sales (block tab)
ADRERWSALES_NO
Accounting
ADRFIBU
Credit limit / Dunning process
ADRKREDITLIMIT
Open items (local menu)
EAOPBETRAG
Partner
ADRPARTNER
Private contact data
PARTNERPRIVAT
Traffic area
STAADRFAHRT / STAADRFAHRTZIEL
Memo
STAADRMEMO
Quotations
STAADROFFKO
Customs
ADRATLAS
NCTS
ADRNCTS
AES
ADRAES
Warehouse
ADRLAGER
Security
ADRSECURITY
eFile
ADRAKTE
eFile: Delete entries
AUFEAKTELOESCHEN
Convert addresses
ADRKTOCHANGE
Using a database entry in the global_sett_t table, it is possible to block individual fields of the Input sub tab in ADDRESSES for processing.
The entry ADR_PROTECT can be set for this in global_sett_t.
The fields to be blocked are entered as the value, separated by semicolons.
INSERT INTO global_sett_t(id, schluessel, wert) VALUES (null, 'ADR_PROTECT', 'adr_art;adr_nr;name_1;name_2;name_3;plz_strasse;strasse;plz_postfach;postfach;fk_ort_mc;ort;orttl;subdivision;fk_land_sch;kz_historie;global_id;');
The fields are ALWAYS blocked, so there is no difference between the address types/clients or similar !
