EAM: Activity API Debug File (full path)
\nEAM: Activity API Debug File Directory
\nEAM: Activity API Debug File Name
\nEAM: Activity API Debug Option
\nEAM: Asset hierarchy description length
\nEAM: Debug PM Scheduling
\nEAM: Debug Profile Option
\nEAM: Maintenance Work Request Options
\nEAM: Object Instantiation API Log File (full path)
\nEAM: Object Instantiation API Log File Directory
\nEAM: Object Instantiation API Log File Name
\nEAM: Object Instantiation API Log Option
\nEAM: PM Debug File (including complete file path)<\/p>\n
<\/p>\n
Profile Options PO: Enable Direct Delivery To Shop Floor<\/strong> EAM: Activity API Debug File (full path) EAM: Activity API Debug File Directory EAM: Activity API Debug File Name EAM: Activity API Debug Option EAM: Asset hierarchy description length EAM: Debug PM Scheduling EAM: Debug Profile Option EAM: Maintenance Work Request Options EAM: Object Instantiation API Log File (full path) EAM: Object Instantiation API Log […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[16],"class_list":["post-26","post","type-post","status-publish","format-standard","hentry","category-oracle-e-is-yonetim-sistemi","tag-oracle-eam-parametreleri"],"_links":{"self":[{"href":"https:\/\/enginhafizoglu.com\/index.php?rest_route=\/wp\/v2\/posts\/26","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/enginhafizoglu.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/enginhafizoglu.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/enginhafizoglu.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/enginhafizoglu.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=26"}],"version-history":[{"count":7,"href":"https:\/\/enginhafizoglu.com\/index.php?rest_route=\/wp\/v2\/posts\/26\/revisions"}],"predecessor-version":[{"id":32,"href":"https:\/\/enginhafizoglu.com\/index.php?rest_route=\/wp\/v2\/posts\/26\/revisions\/32"}],"wp:attachment":[{"href":"https:\/\/enginhafizoglu.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=26"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/enginhafizoglu.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=26"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/enginhafizoglu.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=26"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\nEAM: Debug PM Scheduling<\/strong>
\nThis profile option indicates whether debug mode is enabled for PreventiveMaintenance
\nScheduling processes. The profile option is visible and changeable at the User level; it is
\nvisible and changeable at System Administrator\u2019s User, Responsibility, Application, and
\nSite levels. The debug mode enables a tracing feature and causes additional messages to
\nbe printed to a log file. The default value is Yes. The internal name of the profile option
\nis EAM_DEBUG_PM_SCHED. Available values are as follows:
\n\u2022 Yes – System is operating in debug mode
\n\u2022 No – System is operating in normal mode
\n\u2022 Blank (no value) – Equivalent to No
\nEAM: PM Debug File (including complete file path)<\/strong>
\nThis profile option indicates the directory location where debug files will be created if
\ndebug mode is enabled. The profile option is visible and changeable at the User level; it is
\nvisible and changeable at System Administrator\u2019s User, Responsibility, Application, and
\nSite levels. The internal name of the profile option is EAM_DEBUG_FILE. The default
\nvalue is a file path inserted by the auto-configuration utility, executed during the
\ninstallation of the application, and appended by the file name, viz.eampmeng.log.
\nEAM: Activity API Debug File Directory<\/strong>
\nThe Activity API is called in eAM when a new Activity is created from either a Work
\nOrder or Activity. This profile option indicates the debug file directory that the debug
\nlog will reside, if debugging is enabled for the Activity API. For example, If the profile
\noption, EAM: Activity API Debug Option, is set to Yes, the log of the activity process
\nis saved in the directory determined by the path designated in the current profile
\noption. This profile option is visible and changeable at the User level; it is visible and
\nchangeable at System Administrator\u2019s User, Responsibility, Application, and Site levels.
\nEAM: Activity API Debug File Name<\/strong>
\nThe Activity API is called in eAM when a new Activity is created from either a Work
\nOrder or Activity. This profile option indicates the debug file name that resides in the
\ndebug file directory, if debugging is enabled for the Activity API. For example, If the
\nprofile option, EAM: Activity API Debug Option, is set to Yes, the log of the activity
\nprocess is saved in the directory determined by the path designated by the EAM: Activity
\nAPI Debug File Directory profile option. The name of the file that includes the activity
\nprocess log is determined by the current profile option. This profile option is visible
\nand changeable at the User level; it is visible and changeable at System Administrator\u2019s
\nUser, Responsibility, Application, and Site levels.
\nEAM: Activity API Debug Option<\/strong>
\nThe Activity API is called in eAM when a new Activity is created from either a Work
\nOrder or Activity. This profile option indicates whether debugging is enabled for the
\nActivity API. This profile option is visible and changeable at the User level; it is visible
\nand changeable at System Administrator\u2019s User, Responsibility, Application, and Site
\nlevels.
\nEAM: Debug Profile Option<\/strong>
\nThis profile option is used by multiple eAM processes. If this profile is enabled, the log
\nof these processes is collected. These processes include the following:
\n\u2022 Asset Number Import Program – the log is visible in the Concurrent Program log
\n\u2022 Asset Downtime Process – the log is visible in the Concurrent Program log
\n\u2022 Asset Genealogy Import Process – the log is visible in the Concurrent Program log
\n\u2022 Work Order Business Object API
\nThis profile option is visible and updateable at the User level; it is visible and updateable
\nat System Administrator\u2019s User, Responsibility, Application, and Site levels.
\nEAM: Object Instantiation API Log File Directory<\/strong>
\nThe Object Instantiation API is called when a new asset number is created via the Asset
\nNumber window or if the Instantiate button is chosen within the Rebuildable Serial
\nNumber window. This profile option indicates the debug file directory that the debug
\nlog will reside, if debugging is enabled for the Object Instantiation API. For example, If
\nthe profile option, EAM: Object Instantiation API Log Option, is set to Yes, the log of
\nthe activity process is saved in the directory determined by the path designated in the
\ncurrent profile option. This profile option is visible and changeable at the User level; it is
\nvisible and changeable at System Administrator\u2019s User, Responsibility, Application, and
\nSite levels.
\nEAM: Object Instantiation API Log File Name<\/strong>
\nThe Object Instantiation API is called when a new asset number is created via the Asset
\nNumber window or if the Instantiate button is chosen within the Rebuildable Serial
\nNumber window. This profile option indicates the debug file name that resides in
\nthe debug file directory, if debugging is enabled for the Object Instantiation API. For
\nexample, If the profile option, EAM: Object Instantiation API Log Option, is set to
\nYes, the log of the activity process is saved in the directory determined by the path
\ndesignated by the EAM: Object Instantiation API Log File Directory profile option. The
\nname of the file that includes the activity process log is determined by the current profile
\noption. This profile option is visible and changeable at the User level; it is visible and
\nchangeable at System Administrator\u2019s User, Responsibility, Application, and Site levels.
\nEAM: Object Instantiation API Log Option<\/strong>
\nThe Object Instantiation API is called when a new asset number is created via the Asset
\nNumber window or if the Instantiate button is chosen within the Rebuildable Serial
\nNumber window. This profile option indicates whether debugging is enabled for the
\nActivity API. This profile option is visible and changeable at the User level; it is visible
\nand changeable at System Administrator\u2019s User, Responsibility, Application, and Site
\nlevels.
\nProfile Options in Other Applications
\nProfiles that help the eAM integration with other Oracle Applications are listed below. If
\nyou are implementing other Oracle Applications, you will need to set up additional
\nprofile options as appropriate. Please refer to the applications\u2019 respective user\u2019s guides
\nor implementation manuals for more details.<\/p>\n
\nKendisi \u00e7ok \u00f6l\u00fcmc\u00fcl bir parametredir.<\/strong>
\nThis profile option is a prerequisite for an eAM User to create Purchase Requisitions
\nfor Direct Items via Oracle Purchasing and iProcurement. This profile option must be
\nset to Yes if you need to create Purchase Requisitions using Oracle Purchasing and
\niProcurement applications.<\/p>\n","protected":false},"excerpt":{"rendered":"