Show TOC

Function documentationTransaction Log Report Locate this document in the navigation structure

 

You use this report to audit and diagnose a system activity during the reception, processing and response of requests sent to SAP ME.

Prerequisites

You have configured logging in Transaction Log Maintenance (see Transaction Log Maintenance).

The maximum number of records returned by the report is limited by the global system setting max.records.for.report, which is configured in System Setup Maintenance (see System Setup Maintenance).

Caution Caution

The transaction logging impacts performance of SAP ME. Turn off the transaction logging when complete.

End of the caution.

Features

Selection

The search parameters for the report include the following:

  • Type: The type of transaction, such as Data Exchange or Web service. Only transaction records for the specified type will be displayed in the report results. A logical type of All is also available for searching for transactions of any type.

  • Name: Transactions of a given type are further categorized by name. Names are case sensitive and support partial matches using the asterisk “*” wildcard character.

    Data Exchange Names

    Data exchange transaction names are formatted according to the following convention:

    <action>.<object>

    The exchange action can be either IMPORT, EXPORT, or DELETE. The action object can be any SAP ME entity, such as ITEM, OPERATION, and BOM. For example, IMPORT.ITEM.

    If a data exchange message contains more than one action, the first action found will be displayed in the report results. Any additional actions will be displayed in the attribute table on the transaction details screen (the transaction details screen is described later in this document).

    Production XML Names

    Production XML transaction names are represented as the production action that was taken. Valid production actions include the following: ALARM, ALARMCLEAR, ASSEMBLE_COMPONENTS, CHANGE_PRODUCTION, COMPLETE, CONTAINER, NC_INCIDENT_DONE, NC_LOG, NC_LOG_COMPLETE, PARAMETRIC, PLACE_HOLD, PLACE_FUTURE_HOLD, RELEASE_HOLD, REMOVE_FUTURE_HOLD, RESOURCE_STATE_CHANGED, SCRAP, SERIALIZE, SIGN_OFF, SITE2SITE, SPLIT, START, WIP_CHANGE.

    Web Service Names

    Web service names are formatted according to the following convention:

    For example, ItemWebService.findItemByBasicData

    Due to technical constraints, values for service and operation reflect the internal SAP ME API service and operation names, not the Web service name and operation as defined in the WSDL. Internal service and operation names are provided in the table below:

    Internal Service

    Operation

    BOMWebService

    createBOM, changeBOM, updateBOM, deleteBOM, findBOMByBasicData

    ItemWebService

    createItem, changeItem, updateItem, deleteItem, findItemByBasicData

    NCCodeWebService

    createNCCode, changeNCCode, updateNCCode, deleteNCCode, findNCCodeByBasicData

    NextNumberWebService

    createNextNumber, changeNextNumber, updateNextNumber, deleteNextNumber, findNextNumberByBasicData

    OperationWebService

    createOperation, changeOperation, updateOperation, deleteOperation, findOperationByBasicData

    ProductionAlarmWebService

    sendAlarm, clearAlarm, readAlarm

    ProductionOrderWebService

    createProductionOrder, changeProductionOrder, updateProductionOrder, findProductionOrderByBasicDataQuery

    ProductionWebService

    wipChange, startByItem, split, serialize, signoff, scrap, logParametricData, pack, logNC, logNCComplete, logNCIncidentDone, complete, assembleComponents, start, changeProduction, alarm, placeImmediateHold, removeImmediateHold, placeFutureHold, removeFutureHold, addInventoryReceipt, updateInventory, changeEquipmentStatus

    ResourceWebService

    createResource, changeResource, updateResource, findResourceByBasicData

    RouterWebService

    createRouter, changeRouter, updateRouter, deleteRouter, findRouterByBasicData

    ShopOrderWebService

    createShopOrder, changeShopOrder, updateShopOrder, deleteShopOrder, findShopOrderByBasicData

    WorkCenterWebService

    createWorkCenter, changeWorkCenter, updateWorkCenter, deleteWorkCenter, findWorkCenterByBasicData

  • Status: The transaction status indicates the current state of the transaction.

    Transactions may have one of three possible states:

    Fail: The transaction has failed due to a system or business error

    Pending: The transaction has not yet completed

    Success: The transaction has completed without error

  • Minimum Elapsed Time: The minimum elapsed time allows you to filter transactions by total execution time (in milliseconds). Transactions with an execution time below the minimum elapsed time are not displayed in the report. This field is defaulted to 0 if no value is specified.

  • Date Range: The date range allows you to filter transactions based on a time period as set by the start and end time fields. Transactions that are started within the time period are displayed in the report.

  • Attributes: Additional search criteria may be specified in the form of transaction payload attributes. An attribute is a case-sensitive name/value pair representing a transaction input value found in the request payload.

    Example Example

    Most requests to SAP ME include a value for SITE. If you want to see all transactions that occurred for the site PLANT1, you insert an attribute with the name “SITE” and value “PLANT1” into the report attribute criteria. If you wanteto see all transactions for the PLANT1 site for a specific user, say “TED”, you add a second attribute with the name “USER” with a value of “TED”. Not all inputs available in a given payload may be used as search criteria. For each transaction type there is a subset of attributes that may be used for searching. The following table lists the attribute names available for each transaction type:

    Transaction Type

    Attributes

    Production XML (includes standard production, clock-in/out, and parametric messages)

    SFC, INVENTORY_ID, RESOURCE, OPERATION, WORK_CENTER, NC_CODE, ITEM, SITE, BOM, USER, ACTIVITY_ID, CUSTOMER, CLOCK_ID, CLOCK_WHEN

    Data Exchange

    Key fields for the imported, exported, or deleted object

    Web Services

    SFC, RESOURCE, OPERATION, REVISION, NC_CODE, ITEM, SITE, SITE_BO, BOM, USER, ACTIVITY_ID or any required field within the request object (consult schema definitions to determine which fields are required)

    End of the example.
Output

The results include the following data:

  • Status (All, Fail, Pending, Success)

  • Start time

  • Elapsed time details

  • Attribute name and value

  • Log payload

  • Log result