Task Management Integration Jobs

KB Article • 5/5/2025 • 15 min read

In the EAM application, Integration jobs can be scheduled for a specific duration to run and execute. When the integration task is on run, the related functional data will be updated in the database. Users can schedule and run the following integration jobs in the Task Management Portal.

Integration Jobs

Integration jobs are automated processes designed to enable the transfer of data between diverse systems or components. Our integration solutions support two methodologies: API and Batch jobs.

Batch Jobs: Exchange data via files (data format: XML) at a predefined interval.
API: Exchange data online/synchronous using API (data format: XML)

The same validation would apply to both of the above methods.
The document explains the jobs with reference to batch jobs. Having said that, while utilizing the API, the job name specified for batch processing remains the same and needs to be provided as input.

Types of integrated jobs

Export Job: An export job involves extracting data from a source system, formatting it, and transmitting it to a target system or destination.
Example: Exporting requisition data to an ERP system.

Import Job: An import job entails receiving data from an external source, validating it, and integrating it into a target system or database.
Example: Importing new stock arrivals or inventory adjustments from a supplier’s system into the inventory management system.

Steps followed for all Integration jobs

Receive File: Data is received from the source system, whether through direct transfer, file upload, or API request.
Validate: The received data is validated to ensure it meets the specified format, quality, and integrity standards.
Process: Validated data is processed according to predefined rules, transformations, or logic to prepare it for integration into the target system.
Send Acknowledgment (Ack) Back: Both import and export jobs have Ack.
- For an Import Job: An acknowledgment (Ack) is generated to confirm receipt of the data and communicate the outcome of processing back to the source system.
- For Export Jobs: The external system generates an Ack to confirm receipt of the data and communicate with us.

Import Jobs

Task Name	Internal Task	Expected Behavior	Job Description
Supplier Import	NA	Import supplier master data.	In many cases, the supplier master is maintained in the financial system. A client using EAM requisitions, purchasing, and/or invoice matching modules will need a copy of the supplier master stored in the system. The Supplier Interface automates the process of adding or updating suppliers in the financial system and making corresponding changes in the EAM system.
Work Order Standard Import	NA	Import new WO.	The task involves importing new work orders into EAM from an external system. Upon creation, an acknowledgment is sent to the external system. The integration supports creating work orders based on alarms, existing standard requests or master plans, or information provided in a file. Tasks and subtasks from associated standard requests or master plans are copied, along with various information such as resources, requisitions, and instructions.
Inventory Import	NA	Import item master data.	The task involves importing item master data into EAM from an ERP/MES/MDM/External system. It ensures quantity adjustments are reflected in EAM for inventory issued or returned, either associated with work orders or permanent items. Transactions are interfaced with EAM, updating requisitions and quantities on hand. Price or other item information updates for permanent items can also be sent to EAM, affecting subsequent issues and returns.
MeterReading Import	NA	Import existing meter readings	Integrate meter readings into EAM to trigger PM generation based on meter reading thresholds. Readings from PLC or other tracking systems are imported into EAM and associated with equipment identifiers. XML file format is used for reading imports.
WorkOrder Alarm Import	NA	Create a new WO using the Alarm code	This integration enables the creation of work orders in EAM based on alarm codes from an equipment monitoring system. A designated standard request or master plan serves as the basis for the work order, with associated tasks and subtasks copied as needed. EAM sends an acknowledgment to the external system upon creation, preventing duplicate work order submissions.
Inventory IssueReturn Import	NA	Import Issue/Return/adjust inventory transaction from an external system	This integration facilitates the issue and return of MRO inventory in the ERP system, which is interfaced with EAM to ensure accurate inventory tracking and cost posting to associated work orders. Inventory issues and returns not associated with an EAM work order won’t be sent to EAM. On the other hand, inventory issues and returns associated with an EAM work order will be interfaced with EAM. Permanent item replenishment and price updates are managed in the ERP, with EAM quantities and costs updated accordingly. The update of the cost on the item will not affect any historical data, but it will be the cost used for any subsequent issues/returns for the items in EAM.
Purchase Order	This integration facilitates the transfer of purchase orders and, optionally, receipts from a customer’s ERP application to EAM. It ensures that work order costs and inventory quantities are updated in EAM, with two steps executed: loading XML files into the EAM purchasing interface table and updating EAM with ERP information.
	PO Import	Import Xorr (Requisition Received), Xorc (Requisition Cancelled, Xpoi (PO import), Xpoc (Cancel PO import), Xpco (change order PO import), and Xrecp transaction (PO Receipt) from an external system to the EAM (in_trans_from_ purch table).
	PO Import- BatchProcessing	Batch processing of data from in_trans_from_purch table to the actual module tables. This is an internal process within EAM. If there are any errors, an email will be sent to the customer-configured email ID.
Validation code Import	This integration allows customers to manage validation codes in EAM via an interface. Supported codes include Account, Area, Department, Employee Dept, Freight Code, ISO9000, Item Class, Payment Terms, Project, Stores Account, and Unit of Measure. An XML file with validation code information can be read, and each transaction will be acknowledged as successful or an error.
	ValCode30 Import	Import any other validation code master data (other than freight payment terms) to be stored in the sy_ code_30 table.


	ValcodeFC Import	Import freight code validation code data to EAM.
	ValcodePT Import	Import Payment terms code validation code data to EAM.
Equipment	NA	In many cases, the equipment master is maintained in the MES or any external system. The equipment Interface automates the process of adding or updating equipment in the external system and making corresponding changes in the EAM system.
Non PO receipt transaction	NA	This interface is used mainly when the transfer of PO information is not possible between EAM and the financial system, and still, PO receipt information needs to be known to EAM. In that case, this interface shall send the receipt data, and the system won’t validate the PO#, and quantities would be updated in EAM

Export Jobs

Task Name	Internal Task	Job Description
General Ledger Export	The task involves integrating store activity information from EAM to an ERP system for general ledger entry creation. The task consists of integrating store activity information from EAM to an ERP system for general ledger entry creation. Depending on the integration type the customer chooses, if acknowledgments cannot be sent, they will be considered processed. If acknowledgments are expected, they will be generated for processed data, and updates will be made to logs based on extraction status. The integration includes item activities and assumes that receipt activity is managed separately.
	GL Extract NoAck	The primary purpose of the job is to collect all eligible data from the last run, consolidate it in a specific folder, and export the data without expecting acknowledgment (Ack) confirming receipt and processing. After the data extraction, it is internally marked as processed (where processed=1). This ensures that the same records are not exported again in subsequent runs. The information about the extracted data is then updated in the in_log_ material to keep track of processed data and prevent duplication.
	GL Extract With Ack	The primary purpose of the job is to collect all eligible data from the last run, consolidate it in a specific folder, export the data, and wait for an acknowledgment (Ack) indicating whether the data has been received and processed. It generates an acknowledgment (Ack) upon processing (where processed=0), updates the extraction date to indicate that the data has been exported, and resends data if acknowledgment is not received.
	GL Extract Ack Import	This job handles data acknowledgments (ACKs). When data is exported to a system, an ACK is expected from that system, indicating whether the exported data was successfully processed or not. The acknowledgments are stored in an ACK table for reference. Upon receiving an acknowledgment that the export was successful, the job updates the status of the exported data in the in_log_material. This update indicates that the data has been successfully sent and processed. Consequently, the same record won’t be sent again in subsequent runs. After processing the ACK, a notification is sent to the customer informing them of the outcome of the data processing. This notification likely includes details on which records were successfully processed and which failed.

GL Extract Ack Import and GL Extract with Ack are interconnected jobs designed to facilitate efficient data exchange between systems.
The GL Extract No Ack job operates independently. If customers choose not to provide acknowledgment, only the GL Extract No Ack job will be visible in their UI.
However, if they agree to provide acknowledgment, then GL Extract Ack Import and GL Extract with Ack will be visible in their UI. Customers can choose this option based on their integration preferences with EAM.

This also applies to all other Export jobs mentioned below; based on the features they have selected, specific internal jobs will be accessible in their user interface (UI). If users choose acknowledgment, the Data Extract Acknowledgment Import and Data Extract with Acknowledgment will be visible in their UI. If not, only Data Extract No Acknowledgment will appear in their UI.

Task Name	Internal Task	Job Description
Equipment Export	The integration facilitates the ongoing synchronization of equipment data between the EAM system and the customer’s asset management system via extract files. The customer will be responsible for the application to support successfully importing this data to the receiving system. The integration extracts information only for equipment that has been either updated or newly added since the last execution of the integration process.
	Equipment Extract NoAck	The job aims to extract eligible data from the last run, consolidate it in a folder, and export it without expecting an acknowledgment. The extracted data is internally marked as processed (where processed=1) to avoid duplication in future runs. The date and time of transmission are updated.
	Equipment Extract With Ack	The job’s primary purpose is to collect eligible data from the last run, consolidate it in a specific folder, export it, and wait for an acknowledgment (Ack). It generates an Ack upon processing (where processed=0). The date and time will be updated to indicate that the data has been exported and resend data if acknowledgment is not received.
	Equipment Extract Ack Import	This job handles data acknowledgments (ACKs). When data is exported to a system, an ACK is expected from that system, indicating whether the exported data was successfully processed or not. The acknowledgments are stored on an ACK table for reference. Upon receiving an acknowledgment that the export was successful, the acknowledged date/time will be updated, and the same record won’t be sent again in subsequent runs. After processing the ACK, a notification is sent to the customer informing them of the outcome of the data processing. This notification likely includes details on which records were successfully processed and which failed.
Work Order Export	This integration allows for managing work order activity in EAM and providing completion information to the external system that created the work order. Successfully importing this data to the external system is the customer’s responsibility. Work orders need to be extracted from EAM when an externally initiated work order is completed or canceled.
	Work Order Extract NoAck	The job aims to extract eligible data from the last run, consolidate it in a folder, and export it without expecting an acknowledgment. The extracted data is internally marked as processed (where processed=1) to avoid duplication in future runs. The date and time of transmission are updated.
	Work Order Extract With Ack	The job’s primary purpose is to collect eligible data from the last run, consolidate it in a specific folder, export it, and wait for an acknowledgment (Ack). It generates an Ack upon processing (where processed=0). The date and time will be updated to indicate that the data has been exported and resend data if acknowledgment is not received.
	Work Order Extract Ack Import	This job handles data acknowledgments (ACKs). When data is exported to a system, an ACK is expected from that system, indicating whether the exported data was successfully processed or not. The acknowledgments are stored on an ACK table for reference. Upon receiving an acknowledgment that the export was successful, the acknowledged date/time will be updated, and the same record won’t be sent again in subsequent runs. After processing the ACK, a notification is sent to the customer informing them of the outcome of the data processing. This notification likely includes details on which records were successfully processed and which failed.


PO Receipt Export	To integrate receipt activity from EAM to an XML formatted file for matching invoices. Depending on the integration type the customer chooses, if acknowledgments cannot be sent, they will be considered processed. If acknowledgments are expected, the receiving system will return an acknowledgment of the transaction receipt and identify any errors related to the integration.
	Receipt Extract NoAck	The job aims to extract eligible data from the last run, consolidate it in a folder, and export it without expecting an acknowledgment. The extracted data is internally marked as processed to avoid duplication in future runs. The date_extracted will be updated.
	Receipt Extract With Ack	The job’s primary purpose is to collect eligible data from the last run, consolidate it in a specific folder, export it, and wait for an acknowledgment (Ack). It generates an Ack upon processing. The date will be updated to indicate that the data has been exported and resend data if acknowledgment is not received.
	Receipt Extract Ack Import	This job handles data acknowledgments (ACKs). When data is exported to a system, an ACK is expected from that system, indicating whether the exported data was successfully processed or not. The acknowledgments are stored on an ACK table for reference. Upon receiving an acknowledgment that the export was successful, the job updates the status of the exported data in the date_extracted column in in_log_ material and in the in_log_material_ack table. This update indicates that the data has been successfully sent and processed. Consequently, the same record won’t be sent again in subsequent runs. After processing the ACK, a notification is sent to the customer informing them of the outcome of the data processing. This notification likely includes details on which records were successfully processed and which failed.
Purchase Order Export	Extract purchase order information from EAM and interface it to your ERP system for invoice matching. The interface will extract the PO from EAM and transfer it to an XML file. Depending on the integration type the customer chooses, if acknowledgments cannot be sent, they will be considered processed. If acknowledgments are expected, the receiving system will return an acknowledgment of the receipt of the PO and identify any errors related to the integration.
	PO Extract NoAck	The primary purpose of the job is to collect all eligible data from the last run, consolidate it in a specific folder, and export the data without expecting acknowledgment (Ack) confirming receipt and processing. After the data extraction, it is internally marked as processed (where processed=1). This ensures that the same records are not exported again in subsequent runs. The information about the date_transmitted and time_ transmitted is then updated in the po_ purchase_order_extract table to keep track of processed data and prevent duplication.
	PO Extract With Ack	The primary purpose of the job is to collect all eligible data from the last run, consolidate it in a specific folder, export the data, and wait for an acknowledgment (Ack) indicating whether the data has been received and processed. It generates an acknowledgment (Ack) upon processing (where processed=0), date_transmitted and time_transmitted will be updated to indicate that the data has been exported, and resends data if acknowledgment is not received.
	PO Extract Ack Import	This job handles data acknowledgments (ACKs). When data is exported to a system, an ACK is expected from that system, indicating whether the exported data was successfully processed or not. The acknowledgments are stored on a po_ purchase_order_extract_acks table for reference. Upon receiving an acknowledgment that the export was successful, the job updates the status of the date_ acknowledged and time_ acknowledged in the po_purchase_ order_extract table. This update indicates that the data has been successfully sent and processed. Consequently, the same record won’t be sent again in subsequent runs. After processing the ACK, a notification is sent to the customer informing them of the outcome of the data processing. This notification likely includes details on which records were successfully processed and which failed.