Using Concept Logging
Purpose of concept logging
An alternate way to troubleshoot is to turn on the concept log for a job in the server view, or admin pages in a cloud environment. Once activated, run the program and then view the concept log written to the job log. Important information within the job, for example, selected field values, are written to the log as a readable text.
How to activate concept logging
The role M3BE-FndAdmin is required to configure logging and log levels for jobs for other users. Users with the role M3BE-FndUser can view their own jobs and job logs, but require the role M3BE-LogEnabler to also configure logging and log levels.
- Click Administration Tools > Business Engine Jobs.
- Right-click or mark a job from the list and select Logging > Configure Logging to edit,
add, or delete log configuration for the job.
- Under Log levels, select the levels to enable logging for.
- Under Components, select the components to enable logging for.
- Under Concepts, select Enable Concepts to enable concept logging and use the drop-down to select the concept names to enable.
- Under Other Settings, use Backlog size to select the number of log entries to keep in the backlog, or select Log to file to save all log entries to a file on the host where the job is running. The file will contain all log entries, not only the backlog, and will be prefixed by "JOBLOG-". It can be downloaded on the Business Engine Logs page.
- Click Save to save the log configuration or click Delete to delete an existing log
configuration.Note: A log configuration is active for 4 hours and will then be automatically removed from the job.
- Right-click or mark a job that has logging configured and select Logging > View log
to view the backlog of the job.
- Optionally, you can disable the Refresh automatically check box to stop refreshing the backlog while viewing it.
- Filter by Time, Level, or Message to display specific log entries.
- Click Export to download the displayed log entries as text file.
How to access the logs
Viewing and downloading logs can be useful when troubleshooting problems in an M3 Business Engine application. You must be connected to the role M3BE-FndUser or M3BE-FndAdmin to access Administration Tools > Business Engine Logs from the Infor M3 menu in Infor OS Portal or Infor Ming.le. The role M3BE-FndAdmin is required for viewing logs for other users.
- Click Administration Tools > Business Engine Logs.
- Filter by File name, Last modified, or Size to find the log that you wish to view.
- Mark the file from the list and select the download icon at the top left to download the
file.
To view the content of the file, open it in a text editor, for example Notepad.
Concept Logs
| Concept log | Description |
|---|---|
| mvx.applicationFoundation.xmlByStructure | Application foundation, creation of XML file based on user defined XML structure. Done in cCRMNGRP. |
| mvx.applicationFoundation.initialLoad | Application foundation, initial load logging. Done in EVS007Sbm. |
| mvx.archiving.finance | Archiving, finance. Used when financial data is archived. |
| mvx.fin.tax.avataxDetails | Logging of information from the utlity program cAvaTax, which handles calls and responses to and from Avatax. |
| mvx.manageCheckDigit | Manage Check digit. |
| mvx.fim.logCenPos | Log CenPos XML message. |
| mvx.sce.whm.deliveryManager | Supply chain execution, delivery manager. The concept log will provide the following information: Direction, referenceOrderCategory, processedDeliveries, deliveryLineMissing, orderMissing, orderComplete, orderLock, dispatchPolicyMissing, autoLevel5, allocationInProgress, outboundDeliveryInProgress, orderNotAuthorizied, customerOrderStop, customerStop, prepaymentStop, and inboundDeliveryInProgress. For each of the above categories, there is a counter that will register how many times any of the above conditions have occurred. |
| mvx.sce.edc.EventTrigger | Supply chain execution, event based document control, event trigger. Logging of the trigger detection part. |
| mvx.eventSubscription.alerts | Event subscription, alerts. Event Hub subscription processing - triggering alerts, i.e. emails. Done in autojob CMS911. |
| mvx.eventSubscription.log | Event Hub subscription processing - triggering event logging. Done in autojob CMS912. |
| mvx.eventSubscription.tableUpdate | Event subscription, table update. Event Hub subscription processing - triggering table update. Done in autojob CMS910. |
| mvx.eventSubscription.api | Event subscription, API. Event Hub subscription processing - calling M3 APIs based on event subscription. Done in autojob CMS913. |
| mvx.eventSubscription.webServices | Event subscription, web services. Event Hub subscription processing - calling web services based on event subscription. Done in autojob CMS949. |
| mvx.eventSubscription.compositeEvents | Event subscription, composite events. Event Hub subscription processing - triggering event logging. Done in autojob CMS912. |
| mvx.sce.transport.FreighRateCreation | Supply chain execution, transport, freight rate creation. |
| mvx.sce.transport.InboundDeliveryStatusAtReceipt | Logs the reference and status of a purchase order line during creation of inbound delivery. |
| mvx.import.debug | System foundation, import functions EVS101 and EVS102. |
| mvx.systemFoundation.JobManager | System foundation, job manager. CMNGJOB |
| mvx.korean.taxinvoice.xml | Korean tax invoices, print out generated XML, handled in cTaxInvoiceXML. |
| mvx.korean.taxinvoice.json | Korean tax invoices, print out JSON parameters, handled in cTaxInvoiceCOM. |
| mvx.man.process | Process manufacturing related functions in MAN area. |
| mvx.mi.timing | Measure execution time for MI transactions. |
| mvx.msf.crs.applicationMessage | Application foundation, application message. Gets data on how an application message is generated. Done in CRS428. |
| mvx.msf.crs.asj.controller | Application foundation, M3 BE ASJ controller. Done in CMONASJ. |
| mvx.msf.crs.asj.imq | Application foundation, IMQ autostart job framework. Done in IMQAutoStartJob. |
| mvx.msf.crs.asj.manager | Application foundation, M3 BE ASJ manager. Done in cCMAsjManager. |
| mvx.msf.crs.configList.dbAccess | Application foundation, generation of configurable lists. Done in cCRMNGVW. |
| mvx.msf.crs.configList.subfileGen | Application foundation, generation of configurable lists. Done in cCRMNGVW. |
| mvx.msf.crs.infoBrowserMI | Information browser MI logging. Done in CMS100MI. |
| mvx.msf.crs.infoBrowser.processBookmark | Retrieves information about data that cause Invalid bookmark error in CMS100. Done in CMS100. |
| mvx.msf.crs.queryBuilder | Application foundation, query builder. Done in {@link cCMQueryBuilder}. |
| mvx.msf.crs.taskManager | Application foundation, load management logging. Done in {@link cCMTaskManager}. |
| mvx.msf.env.selectJobAttr | Application foundation, select job attribute. Done in MNS230. |
| mvx.msf.out.outputter.writer | Output Management, writer logging. Done in {@link cOutputter}, {@link cCsvOutputter} and {@link cXmlOutputter}. |
| mvx.msf.sec.gdpr.searchExecute | Security, GDPR search and execute logging. Done in {@link CMS210Sbm} and {@link CMS210Fnc}. |
| mvx.app.util.PFIAsyncTrigger | |
| mvx.pcm.timing | PCM integration, timing of web service calls. |
| mvx.pcm.data | PCM integration, printout of attributes and values returned from PCM. |
| mvx.pdm.process | Process manufacturing related functions in PDM area. |
| mvx.rental | Rental - general. |
| mvx.sce.transport.RouteSelection | Supply chain execution, transport, route selection. |
| mvx.sce.whm.RetrievePutAwayLocation | This concept log is interesting to run for one put-away location retrieval, in
order to understand why some locations were excluded from the search, and understand
the proposition from M3. For example, open 'Purchase Order. Receive Goods' (PPS300) and check the location proposed on the E panel. Note: Do not
run the concept log for more than for one search as the log would not be adequate
for analysis.
|
| mvx.sls.invoicing.TaxCalculation | Customer order, sales tax calculation during invoicing. |
| Service Requirements Planning (SRP) / (MOS950) | The different concept logs under mvx.mai.srp are intended to be used for
solving problems related to the service requirements planning calculation. The most
common kinds of questions that arise in this area are: 1) I have set all my data up for a scheduled service but no work request appears in 'Work Request. Open' (MOS170) - why? 2) A work request comes out at date x when I expected it to be at date y - why? All severe errors detected in the setup of basic data are logged under the "basics" concepts. The recommended workflow, if you do not know exactly what you are looking for, is to add concepts one by one, by the order of their sequence numbers. For example, start with 01triggers, re-running the case after each concept has been added. |
| mvx.mai.srp.basics.01triggers | Logs the input parameters by which the SRP calculation was invoked. Also logs the update of trigger records for the next calculation date. Useful for monitoring of the SRP calculation when running as autojob, that is, "continuous net change". |
| mvx.mai.srp.basics.02objects | Logs the IDs of all serialized items and positions that are discovered during the loop through the as-built list for the operational unit or site. |
| mvx.mai.srp.basics.03services | Logs all scheduled services that are discovered for each object, and whether they qualify for calculation. |
| mvx.mai.srp.basics.04calculation | Logs the major calculation steps for each service. Intermediate calculation results are logged for the first 10 service dates. |
| mvx.mai.srp.details.05objects | Logs details about each object, which is a serialized item or position. Should always be used together with 02objects. |
| mvx.mai.srp.details.06services | Logs details about each service. Should always be used together with 03services. |
| mvx.mai.srp.details.07calculation | Logs all details of the calculation. Intermediate calculation results are fully logged. |
| mvx.mai.srp.details.08operationplan | Logs the retrieval of operation plan from 'Operation Plan. Open' (MOS380). Should be used only if non-calendar meters are your primary focus. |
| mvx.mai.srp.details.09workrequestupdate | Logs the update of calculation results to 'Work Request. Open' (MOS170) and 'Equipment. Open Service History' (MOS180), including the effect of suppression. This is the only "details" concept needed when no work requests appear in 'Work Request. Open' (MOS170) despite all data being set up. Otherwise the "basics" concepts should be sufficient. |
| mvx.SupplierRebateOnSalesAgr | Supplier rebate on sales agreement. |
| mvx.toolcreation | Tool creation. |
| mvx.sce.tei.TransferCreation | Supply chain execution, TEI transfer creation. Logging of the detection and creation part of a TEI transfer. |
| mvx.fim.tax.vertex | Logging of information about response time in various steps when submitting a call to Vertex and receiving a reply. |
| mvx.fim.tax.vertex.details | Logging of detailed information in Vertex requests and replies. |
| mvx.msf.sec.eSignature | Logs error in failed e-signature process from API SES450MI.PrcEsignature. |