Customer - Sap
CUSTOMERSAP Implementation Guide: IconsSAP ECTR for SAP S/4HANA 1.1
DOCUMENT HISTORYNoteBefore you start the implementation, make sure you have the latest version of this document.This guide is valid as of SAP ECTR for SAP S/4HANA 1.1.6.0The latest version is available on SAP Help Portalhttps://help.sap.com/docs/SAP ENGINEERING CONTROL CENTER S4HANAVersionDateChange1.02019-05-29Initial creation2.02019-11-21"Icons for Folders" section optimized3.02020-07-02 “Icons for Equipment” section optimized “Icons for Function Location” section optimized “Special Cases” section optimized4.02021-07-08 "Document Icons and Their Statuses" sectionoptimized5.02022-07-14 New Template2
TABLE OF CONTENTS11.1SAP ECTR FOR SAP S/4HANA ICONS . 4DOCUMENT ICONS AND THEIR STATUSES . 41.1.1SPECIAL CASES . 61.21.31.41.5MATERIAL ICONS AND THEIR STATUSES . 6FOLDER ICONS AND THEIR STATUSES . 7CHANGE NUMBER ICONS AND THEIR STATUSES . 7APPLICATION STRUCTURE . 822.12.22.32.42.52.62.72.8CONFIGURATION OF ICONS . 9ICONS FOR DOCUMENTS . 9ICONS FOR MATERIALS . 14ICONS FOR CHANGE NUMBERS . 15ICONS FOR BILLS OF MATERIALS . 16ICONS FOR EQUIPMENT . 16ICONS FOR FUNCTION LOCATIONS . 17ICONS FOR FOLDERS . 18ICON COLOR CHANGE FOR STATUS CHANGE . 202.8.12.8.22.8.32.9COLOR DEFINITIONS FOR DOCUMENTS . 20COLOR DEFINITIONS FOR MATERIALS . 20COLOR DEFINITIONS FOR EQUIPMENT . 21ICON MAPPING USING A TEXT FILE . 22Icon Guide3
1SAP ECTR FOR SAP S/4HANA ICONSPNG or GIF graphics in the formats 16x16, 24x24 or 32x32 pixels are used for icons. You receive a large setof icons that can be combined. Customer-specific icons can be created with any graphics program.1.1 Document Icons and Their StatusesEach document has one or more icons that provide users with information about the status of the document,for example, whether the document is available for editing or whether a material has been assigned.In the standard system, each document has seven icons.These icons are described in more detail below:Examples of icon positions (for NX)1234567Icon Position 1: Document IconsIconDescriptionIconDescriptionPartPart with "dirty flag"AssemblyAssembly with "dirty flag"Assembly with inconsistent classificationPart with inconsistent classificationDirty FlagSAP ECTR for SAP S/4HANA allows you to create documents without starting an authoring system andcreating an original document there. Documents that are created without the direct use of an authoringsystem are denoted by a dirty flag. The dirty flag is a yellow overlay triangle in the document icon.This indicates that the integration with the authoring system still has to update the document. The updateinvolves the attributes and/or internal references to the original document. Authoring system integrationautomatically updates the document when opening it and subsequently when saving it.Icon Position 2: Status and External ReferencesIconIcon GuideDescriptionIconDescriptionThe document does not have more recentversions or external references.The document has more recent (unreleased)versions but does not have external references.The document has more recent (released)versions but does not have externalreferences.The document has external references.4
Icon Position 3: Status of Master OriginalIconDescriptionIconDescriptionThe document is available for editing.The document is in editing status. The user ofthe document is not the login user.The document is open for editing.The document is checked out by anotherprocessor.The document is in release status.The document is in lock status.Markup display for documents in theOriginals containerIcon Position 4: Status of Additional OriginalsIconDescriptionAn additional original exists.Icon Position 5: Material AssignmentIconDescriptionIconDescriptionA material has been assigned to thedocument.Multiple materials have been assigned to thedocument. None are denoted as exclusive.Multiple materials are assigned to thedocument.Link to non-existing materials in document.Symbol for configurable materials.Icon Position 6: Assigned Dependent DocumentsIconDescriptionDependent documents are assigned tothe document.IconDescriptionObsolete dependent documents are assigned tothe document.Icon Position 7: NotesIconDescriptionNotes are assigned to the documentIcon Guide5
1.1.1Special CasesAssemblies WindowIn the Assemblies window, the document icons can indicate further statuses.Icon Position 1: Document IconsIconDescriptionThis position is marked in the SORTF fieldin such a way that it can be suppressedwhen the material BOM is derived.Missing AuthorizationIf there are no authorizations to view a document, the documents are marked with triangle icons.IconDescriptionIf there is no authorization on a document, this is indicated by triangle icons inthe respective icon positions.1.2 Material Icons and Their StatusesEach material has one or more icons that provide users with information about the material, for example,whether the material has a material BOM or object links.In the standard system, each material has four icons.These icons are described in more detail below:Examples of Icon Positions1234Icon Position 1: Material Icon (Depending on the Material Type)IconDescriptionDefault material icon if no specific icon isdefined for the material typeIcon Guide6
Icon Position 2: Object Links to DocumentsIconDescriptionThe material has at least one link todocuments.Icon Position 3: Bills of MaterialIconDescriptionThe material has a material BOM.Icon Position 4: Material Display (Only in the Linked Objects Container)IconDescriptionIconThe material is not displayed but is thedefault material for operations.DescriptionThe material is displayed.Icon -Position 6: NotesIconDescriptionNotes are assigned to the material.1.3 Folder Icons and Their StatusesAll folders in SAP ECTR for SAP S/4HANA can be denoted as active. Active folders have different icons tostandard folders.Folder IconsIconDescriptionIconFolderDescriptionActive Folder1.4 Change Number Icons and Their StatusesAll change numbers in SAP ECTR for SAP S/4HANA can be denoted as activated or deactivated.Change Number IconsIconDescriptionChange number (deactivated)Icon GuideIconDescriptionChange number (activated)7
1.5 Application StructureMenu BarIconDescriptionIconDescriptionPossibilities to manage the tree structureRestores the view in the Application StructureWindowDocument existsDocument doesn't existOriginal is locally (CAD or Session)modified.Original is out-of-date. Newer Save-Counter inSAP-SystemPending conflict: original is locallymodified and another user has checked itout.Conflict: Original is out-of-date, original is locallymodifiedLinked material for DIR doesn t exists.Shows all originals with a green traffic lightShows all originals with an orange trafficlightShows all originals with a red traffic lightShows originals with need for action:orange traffic light, red traffic light, locallymodified, doesn't exist, out-of-date,pending conflict, conflictRestores all active filtersDocument IconsAn additional icon indicating the loading status of the assembly or components is displayed in the applicationstructure.IconDescriptionThe document is fully loaded in theapplication.IconDescriptionThe document is partially loaded in theapplication.The document is not loaded in theapplication.Icon Guide8
2CONFIGURATION OF ICONS2.1 Icons for DocumentsAll icons for the document are determined and defined using the same mechanism. They are defined in theDType in the corresponding definition file using the icon and icondef elements: %PLM INSTDIR%/customize/config/dtype.xml%PLM INSTDIR%/ appl /customize/config/dtype.xmlExample icon icondef icon position "1"icon group "default"icon identifier "tree/ugs/ (TYPE) (SUBTYPE) (FAMILY)"/ icondef icon position "2"icon group "default"icon identifier "flag/flag version (HER) (HNV) (HRV)"/ icondef icon position "3"icon group "default"icon identifier "flag/flag primaryfiles moe (MOE)moc (MOC) iu (IN USE BY OTHER)"/ icondef icon position "4"icon group "default"icon identifier "flag/flag addfiles aoe (AOE) aoc (AOC)iu (IN USE BY OTHER)"/ icondef icon position "5"icon group "default"icon identifier "flag/flag material (MATX) (MSTA)"/ /icon The icon ID read from the DType must be fully qualified. The ID must contain the path and the icon name.The icons are stored in the images.jar Java archive in the following directory:%PLM INSTDIR%/basis/classes%PLM INSTDIR%/ appl /basis/classesThe directory is located in the CLASSPATH. For customer-specific icons, a corresponding Java archive isprovided in the following directory:%PLM INSTDIR%/customize/classes%PLM INSTDIR%/ appl /customize/classesWithin the icon name, you can use placeholders, which the program replaces dynamically.Valid placeholders are:PlaceholderDescriptionValues after conversion (TYPE)Document / dependent documentm, n (SUBTYPE)Assembly / Part / Drawinga, p, d (FAMILY)Part family templateg generic/template,i instance/member,Icon Guide9
PlaceholderDescriptionValues after conversion' ' (empty string) no family part (DOCTYPE)Document typeThe value corresponds to thedocument type of the document. (APPLTYPE)Type of document, information inthe RES4 field before the colonThe value corresponds to theprimary application type (RES4). (APPLROLE)Returns the object type, informationin the RES4 field after the colonValid values can be taken from thedescription of the RES4 field in thisguide. (STATUS)Document statusThe value corresponds to thestatus of the document. (OWNER)The owner (user) of the documentcorresponds to the SAP user1 (yes), 0 (no) (AUTHGR)Authorization group on thedocumentIf no authorization group has beenassigned, the value corresponds tothe name of the authorization groupor an empty string. (HAUTHGR)Document has an authorizationgroup1 (yes), 0 (no) (HECN)Document has a change number1 (yes), 0 (no) (MOE)Master Original Exits1 (yes), 0 (no) (MOC BY OTHER)Master original is open for editingand the owner (user) of thedocument does not correspond tothe SAP user1 (yes), 0 (no) (MOC)Master original is open for editing1 (yes), 0 (no) (AOE)Additional original exists1 (yes), 0 (no) (AOC)Additional original is open for editing1 (yes), 0 (no) (IN USE BY OTHER)Document is in an O-Flag status(open for editing) and the owner(user) of the document does notcorrespond to the SAP user1 (yes), 0 (no) (MAT)Document has an object link to amaterialmat, sign off, nomat (objectlink to non-existing material) (MATX)Document has a materialassignment0 no material,1 open material,2 correct material (MAT AMB)Document has multiple/non-uniquematerial assignments.' ' (empty string) no materialassignment or one materialassignments several material assignments,one is markedIcon Guide10
PlaceholderDescriptionValues after conversiona several material assignmentswithout a marked material (MSTA)Material statusThe value corresponds to thestatus of the material or an emptystring (VALID)Validity of the document. Validitystatements can be made forreleased documents.' ' (empty string) document isnot released, no statement can bemade in relation to the validity.v (valid) valid today, thecurrent date is between "Validfrom" and "Valid to"f (future) not valid yet, thecurrent date is before "Valid from."p (past) no longer valid, thecurrent date is after "Valid to." (DRAW)Document has dependent documentlinksdraw, sign off (HER)Document has external references1 (yes), 0 (no) (HNV)Document has more recent versions1 (yes), 0 (no) (HRV)Document has released versions1 (yes), 0 (no) (NM OLD)For dependent documents:The current document is no longerup-to-date.For documents:One of the assigned dependentdocuments is no longer up-to-date.If the corresponding document wasedited after the dependentdocument, the dependent documentis no longer up-to-date. The sortfield of the document structure takesinto account relations between themaster and dependent document ofrelationship type ':DC'.0 dependent document is up-todate1 dependent document isobsolete; the corresponding masterdocument was edited after thedependent document. (CONVSTA)Status of the last conversion(only in connection with theconversion server from theframework)free waitrun in processdone doneskip ignorederror with errors (CUSTOM[ customer property ])Makes it possible to use a customerproperty to define icons.The value of the customer propertyspecified in customer property is useddirectly for the icon definition. Youcan use any information from theSAP system to define icons.Value of the customer property (RES1)RES1 field (DRAW table)Value of the RES1 field for thedocumentIcon Guide11
PlaceholderDescriptionValues after conversion (RES2)RES2 field (DRAW table)Value of the RES2 field for thedocument (RES3)RES3 field (DRAW table)Value of the RES3 field for thedocument (NORMPART)RES4 field (Table DRAW). Checkfor the letter "N" in theAPPLICATIONROLE (all by colon).1 (Yes), 0 (No)ExamplesThe placeholders result in a large number of combinations as possible icon names.IconIcon IDResulting icon name1st icon:Document icontree/ugs/ (TYPE) (SUBTYPE) (FAMILY)tree/ugs/mptree/ugs/matree/ugs/np.2nd icon:Status and externalreferencesflag/flag version (HER) (HNV) (HRV)flag/flag version 000flag/flag version 010flag/flag version 011flag/flag version 100flag/flag version 110flag/flag version 1113rd icon:Status of the originalflag/flag primaryfiles moe (MOE)moc (MOC) iu (IN USE BYOTHER)flag primaryfiles moe1 moc0 iu0flag primaryfiles moe1 moc1 iu0flag primaryfiles moe1 moc0 iu1flag primaryfiles moe1 moc1 iu1flag primaryfiles moe0 moc0 iu0flag primaryfiles moe0 moc0 iu14th icon:Status of additional originalsflag/flag addfiles aoe (AOE) aoc (AOC) iu (IN USE BY OTHER)flag addfiles aoe1 aoc0 iu0flag addfiles aoe1 aoc1 iu0flag addfiles aoe1 aoc0 iu1flag addfiles aoe1 aoc1 iu1flag addfiles aoe0 aoc0 iu0flag addfiles aoe0 aoc0 iu15th icon:Material assignmentflag/flag material (MATX) (MSTA)flag/flag material 0flag/flag material 1flag/flag material 201flag/flag material 2026th icon:Assigned drawingflag/flag (DRAW)flag/flag drawflag/flag sign offOnce the placeholders have been replaced, the resulting icon names are available in lower case letters. Thesystem searches for these icon names within the CLASSPATH. If customer-specific images are integratedusing the cust classpath, for example, a customer-specific icon called mp.gif must be available in thefollowing path:%PLM INSTDIR%/customize/classesIcon Guide12
If the definition of the first icon is missing in the DType or the icon cannot be found, the default doctype is used for this document icon. The file is located in the "tree" directory. If an application type is stored in thedocument, it is stored in directory tree/ appl.type .Icon GroupThe icon group makes it possible to use icons status-specifically.The group is defined status-specifically in the default settings file default.txt via the following preferencevariable:plm.icon.group.doc. status Exampleplm.icon.group.doc.FR releasedplm.icon.group.doc.ER engrelIn the DType definition, the assignment of the icons is then specified dependent on the status as inthe following example: icondef icon position "3"icon group "default"icon identifier "flag/flag lock (AOE) (AOC) (IN USE BY OTHER)"/ icondef icon position "3"icon group "released"icon identifier "flag/flag released"/ icondef icon position "3"icon group "engrel"icon identifier "flag/flag engrel"/ In the above example, it was defined that the third icon shows a different icon depending on the icon group.If the document is in status FR, icon group released is determined. From the DType, the following definitionis used instead of the default definition: icondef icon position "3"icon group "released"icon identifier "flag/flag released"/ The default definition can be redefined using variable plm.icon.group.default.NoteThe icon groups are of a general nature and only depend on the status. If an icon group is defined inthe preference variables, the icon group must be defined in every DType.Icons for Files in the Originals ContainerSAP ECTR for SAP S/4HANA generically determines the icon name for the files in the Originals containeraccording to the following pattern:tree/file/obr tree file Workstationapplication der Datei Example of an icon name for a PDF file as an additional original with workstation application "PDF":tree/file/obr tree file pdfThe Java archive images.jar contains the icons for some workstation applications. If additional icons arerequired for customer-specific workstation applications, you can add the icons using an icon mapping entry inthe customer mapping table.Icon Guide13
2.2 Icons for MaterialsA material can have up to five icons that are defined using preference variables.They are defined in the following preference file:%PLM INSTDIR%/customize/config/default.txtThe following preference variables are used:plm.mat.icon.1 flag/flag mat (MTYPE) (LVORM)plm.mat.icon.2 flag/flag obj links (HOL)plm.mat.icon.3 flag/flag bom (ANY BOM) (VAR BOM)plm.mat.icon.4 flag/flag variant (CL200) (CL300)plm.mat.icon.5 flag/flag preferred (PREF)plm.mat.icon.6 gos note flag (HGN)The fifth material icon is reserved for the display of the preferred material in the linked objects containerand is only displayed in the container.The icon ID read from the preference variable must be fully qualified. The icons are stored in the images.jarJava archive in the following directory:%PLM INSTDIR%/basis/classesThe directory is located in the CLASSPATH. For customer-specific icons, a corresponding Java archive isprovided in the following directory:%PLM INSTDIR%/customize/classesWithin the icon name, you can use placeholders, which the program replaces dynamically.Valid placeholders are:PlaceholderDescriptionValues after conversion (MTYPE)Material typeMaterial type as a string, forexample "FERT" (CONF)Configurable material1 (Yes), 0 (No) (HOL)Has object link to document1 (Yes), 0 (No) (HSM)Has a follow-up material in a plant.Material data field MARA-KZNFM ischecked for this purpose.1 (There is a follow-up material, i.e.MARA-KZNFM "X") (ANY BOM)Has any Bill of Material1 (Yes), 0 (No) (VAR BOM)Has a variant Bill of Material1 (Yes), 0 (No) (CL200)Is classified with class type 2001 (Yes), 0 (No) (CL300)Is classified with class type 3001 (Yes), 0 (No) (PREF)Is the preferred material(this icon is only displayed in theobject link container)0 (no)1 (yes, icon: green checkmark)2 (first returned material fromfunction module, icon: "1") (LVORM)Has deletion flag1 (yes), 0 (no or field MARA-LVORMin /DSCSAG/SEL FIELDS has notIcon Guide14
PlaceholderDescriptionValues after conversionbeen configured for the materialdata) (CUSTOM[ customer property ])Makes it possible to use a customerproperty to define icons.The value of the customer propertyspecified in customer property is useddirectly for the icon definition. Youcan use any information from theSAP system to define icons.Value of the customer property2.3 Icons for Change NumbersA change number can have several icons that are defined using preference variables.The definition is set in the following default settings file:%PLM INSTDIR%/customize/config/default.txtThe following preference variables are used:plm.ecm.icon. 1.n Iconname Here, 1.n is the sequence number of the icons, which are arranged from the left to the right. The firsticon is always the main icon that represents the object type change number. Additional icons from thesecond icon position onwards are used to display the additional properties of the change number.Exampleplm.ecm.icon.1 obr ecmplm.ecm.icon.2 statusicon (STATUS)plm.ecm.icon.3 relkeyicon (RELKEY)If no icon mapping is used, the icon ID read from the preference variable must be fully qualified. The iconsare stored in the images.jar Java archive in the following directory:%PLM INSTDIR%/basis/classesThe directory is located in the CLASSPATH. For customer-specific icons, a corresponding Java archive isprovided in the following directory:%PLM INSTDIR%/customize/classesWithin the icon name, you can use placeholders, which the program replaces dynamically.Valid placeholders are:PlaceholderDescriptionValues after conversion (STATUS)Status of the change numberThe value corresponds to thestatus of the change number (RELKEY)Release keyThe value corresponds to therelease key of the change number (CUSTOM[ customer property ])Makes it possible to use a customerproperty to define icons.The value of the customer propertyspecified in customer property is usedValue of the customer propertyIcon Guide15
PlaceholderDescriptionValues after conversiondirectly for the icon definition. Youcan use any information from theSAP system to define icons.You can use the icon mapping tables to convert the icon names from the preference variables into iconnames from Java archive images.jar.If the main icon is redefined, you must make a corresponding entry in the icon mapping table. Otherwise thedefault icon will always be used.2.4 Icons for Bills of MaterialsThe icon for the Bill of Material (BOM) can be defined using a preference variable.The definition is set in the following default settings file:%PLM INSTDIR%/customize/config/default.txtThe following preference variable is used:plm.bom.icon.1 Iconname The icon represents the Bill of Material object type. Theoretically, additional icons are possible from thesecond icon item position. However, the icons do not provide any additional information because noplaceholders have been defined for the Bill of Material yet.Exampleplm.bom.icon.1 tree/bomThe icon ID read from the preference variable must be fully qualified. The icons are stored in the images.jarJava archive in the following directory:%PLM INSTDIR%/basis/classesThe directory is located in the CLASSPATH. For customer-specific icons, a corresponding Java archive isprovided in the following directory:%PLM INSTDIR%/customize/classesYou can use the mapping tables to convert the icon names from the preference variables into icon namesfrom Java archive images.jar.2.5 Icons for EquipmentThe definition is set in the following default settings file:%PLM INSTDIR%/customize/config/default.txtThe following preference variable is used:plm.equi.icon. 1.n Iconname Here, 1.n is the sequence number of the icons, which are arranged from the left to the right. The firsticon here is always the main icon that represents the object type equipment. Additional icons from thesecond icon position onwards are used to display the additional properties of the equipment. If no icondefinition is available, SAP ECTR for SAP S/4HANA uses a default icon for the equipment.Exampleplm.equi.icon.1 flag/flag equi (EQTYPE) (SYSSTATUS[INAK])plm.equi.icon.2 flag/flag userstatus (USRSTATUS[0003])If no icon mapping is used, the icon ID read from the preference variable must be fully qualified. The iconsare stored in the images.jar Java archive in the following directory:Icon Guide16
%PLM INSTDIR%/basis/classesThe directory is located in the CLASSPATH. For customer-specific icons, a corresponding Java archive isprovided in the following directory:%PLM INSTDIR%/customize/classesYou can use placeholders, which the program converts dynamically.Valid placeholders are:PlaceholderDescriptionValues after conversion (EQTYPE)Equipment typeID of the equipment category (SYSSTATUS[ status ])Check whether the system status status is set.1 (Yes), 0 (No) (USRSTATUS[ status ])Check whether the user status status is set.1 (Yes), 0 (No)You can use the icon mapping table to convert the icon names from the preference variables into icon namesfrom Java archive images.jar.2.6 Icons for Function LocationsIcons are defined in the following preconfiguration file:%PLM INSTDIR%/customize/config/default.txtThe following preference variable is used:plm.floc.icon. 1.n Iconname 1.n is the sequence number of the icon. The numbers are counted from left to right. The first icon isalways the main icon that represents the Functional Location object type. The other icons display otherproperties of the functional location. If an icon is not defined, SAP ECTR for SAP S/4HANA uses a standardicon for the functional location.Exampleplm.floc.icon.1 flag/flag floc (FLOCTYPE)If icon mapping is not used, the icon ID read from the preference variable must be fully qualified. The iconsare stored in the Java archive images.jar in the following directory:%PLM INSTDIR%/basis/classesThe directory is in the CLASSPATH. Customer-specific icons can be stored in a corresponding Java archiveunder:%PLM INSTDIR%/customize/classesYou can use placeholders that the program converts dynamically.Valid placeholders are:PlaceholderDescriptionValues after conversion (FLOCTYPE)Type of functional locationID of the functional location type (CUSTOM[ customer property ])Enables a customer property to beused to define the icon.Value of the customer propertyIcon Guide17
PlaceholderDescriptionValues after conversionThe value in customer property is used todefine the icon.To define a customer-specific icon,any information from the SAPsystem can be used.The icon mapping table is used to convert the icon names from the preference variables to icon names fromthe Java archive images.jar.2.7 Icons for FoldersIcons are defined in the following preconfiguration file:%PLM INSTDIR%/customize/config/default.txtThe following preference variable is used:plm.fld.icon. 1.n Iconname 1.n is the sequence number of the icon. The numbers are counted from left to right. The first icon isalways the main icon that represents the Folder object type. The other icons display other properties of thefolder. If an icon is not defined, SAP ECTR for SAP S/4HANA uses a standard icon for the folder.Exampleplm.fld.icon.1 tree.folder ACT (ACTIVE) OWN (OWNER) LOCK (IS LOCKED)If icon mapping is not used, the icon ID read from the preference variable must be fully qualified. The iconsare stored in the Java archive images.jar in the following directory:%PLM INSTDIR%/basis/classesThe directory is in the CLASSPATH. Customer-specific icons can be stored in a corresponding Java archiveunder:%PLM INSTDIR%/customize/classesYou can use placeholders that the program converts dynamically.Valid placeholders are:PlaceholderDescriptionValues after conversion (FLDTYPE)Folder typeValue corresponds to thedocument type of the folder DIS (STATUS)Folder statusValue corresponds to the status ofthe folder DIS (OWNER)Own folder in SAP ECTR for SAPS/4HANA, the owner (OWNER) of thedocument is the SAP user1 (Yes), 0 (No) (ACTIVE)Active folder1 (Yes), 0 (No) (HGN)Folder has GOS notes1 (Yes), 0 (No) (IS LOCKED)Folder is locked1 (Yes), 0 (No)Icon Guide18
PlaceholderDescriptionValues after conversion (CUSTOM[ customer property ])Enables a customer property to beused to define the icon. The valuespecified in customer property is useddirectly to define the icon. Byimplementing the BAdI for customerproperties, you can use anyinformation from the SAP system todefine icons for specific customers.Value of the customer propertyThe icon mapping table can be used to convert the icon names from the preference variables to icon namesfrom the Java archive images.jar.Configuration ExamplesDefinition in the file default.txt:# Definition of the folder icons. If at least plm.fld.icon.1 is defined this icon# definition replaces the implicit setting of the folder icon.# This definition applies only to standard ECTR folders and doesn't affect task folders# or classification folders.# The following placeholders can be used to define icon names for the different# folder states:# (FLDTYPE)Folder type (possible value: document type of the folder DIR)# (STATUS)Folder status (possible value: status of the folder DIR)# (OWNER)0/1)Own folder in ECTR - folder owner current SAP user (possible values:# (ACTIVE)Active folder (possible values: 0/1)# (HGN)Folder has GOS
All folders in SAP ECTR for SAP S/4HANA can be denoted as active. Active folders have different icons to standard folders. Folder Icons Icon Description Icon Description Folder Active Folder 1.4 Change Number Icons and Their Statuses All change numbers in SAP ECTR for SAP S/4HANA can be denoted as activated or deactivated. Change Number Icons
SAP ERP SAP HANA SAP CRM SAP HANA SAP BW SAP HANA SAP Runs SAP Internal HANA adoption roadmap SAP HANA as side-by-side scenario SAP BW powered by SAP HANA SAP Business Suite powered by SAP HANA Simple Finance 1.0 2011 2013 2014 2015 Simple Finance 2.0 S/4 HANA SAP ERP sFin Add-On 2.0
SAP Certification Material www.SAPmaterials4u.com SAP Certification Material for SAP Aspirants at Low cost Home Home SAP Business Objects SAP BPC CPM SAP BPC 7.0 SAP EWM SAP GTS SAP Public Sector SAP Real Estate SAP FSCM SAP FI/CO SAP AC - FI/CO SAP BI 7.0 SAP CRM 5.0
SAP Master Data Governance SAP Information Steward SAP HANA smart data integration SAP Data Hub SAP Cloud Platform Big Data Services SAP HANA, platform edition SAP Vora Customer Experience IoT Workforce Engagement SAP Cloud for Customer SAP Commerce SAP Marketing SAP Asset Intelligence Network SAP Predictive Maintenance and Service SAP .
Customer Roadmap to SAP Simple Finance - Example " Adopting SAP Simple Finance is a journey - start early" Side-by-side SAP HANA Acceleration SAP HANA accelerators, BW, BPC, GRC SAP Business Suite on SAP HANA SAP ERP on SAP HANA SAP ERP in SAP HANA Enterprise Cloud SAP Accounting Powered By SAP HANA Simple Finance add-on/
SAP TM Notifier Sybase Mobile Workflow 2.1 SAP Sales Pipeline Simulator SAP Customer Financial Fact Sheet SAP Authenticator SAP Work Manager for Maximo SAP CRM SERVICE MANAGER SAP Cloud for Customer SAP GRC Access Approver SAP Manager Insight SAP Commissions Check SAP Mobile
SAP HANA Appliance SAP HANA DB In-Memory A io BI Client non-ABAP (SAP supported DBs) SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Suite SAP Business Warehouse SAP HANA DB r In-Memory Source Systems SAP LT Replication Ser
ALE/RFC Setup 88 SAP System Type 88 SAP IDoc Version 88 Program ID (SAP to e*Gate) 88 SAP Load Balancing Usage (e*Gate to SAP) 89 SAP Application Server (e*Gate to SAP) 89 SAP Router String (e*Gate to SAP) 90 SAP System Number (e*Gate to SAP) 90 SAP Gateway Ho
SAP Business Suite SAP BW SAP Apps Partner Apps SAP HANA PLATFORM Planning and Calculation Engine Real-Time Replication Services Information Composer & Modeling Studio SAP UI HTML5 Mobile SAP BI 4 SAP ERP SAP CRM SAP SCM SAP PLM SAP SRM SAP Netweaver Predictive Analytics & Business Function Libraries In-Memory
