ESP Project Overview (tppss2531m000)
Use this session to view the project data linked to the external scheduling package. You can view the activity information, ownership and the project - connection node combinations. You can also view the projects that are scheduled for import/ export.
You can also use the Activities (tppss2100m000) session to view the project hierarchy.
Field Information
- Project
-
The code of the project.
- Plan
-
The plan that must be used for the import/ export.
- Connection Node
-
The activity or node of the Infor LN Project that must be connected to the activity or node of a project in the external scheduling package. If you link a complete project in Infor LN to a project in the external scheduling package, this node is not specified.
Note:To select an activity as the connection node, the following are the constraints:
- The child activity of a project cannot be selected as the connection node, if the related higher level or lower level activity is selected as the connection node by another planner in the external scheduling package.
- Only one planner is the owner of the connection node, and can use the scheduling interface for this node.
- The selected connection node cannot be a milestone.
- Synchronized by
-
Indicates the application that synchronizes the project data as part of the integration.
Allowed values
- Infor LN
-
The project data is synchronized by Infor LN.
- External Scheduling Package
-
The project data is synchronized by the external scheduling package (ESP).
- Not Applicable
- Synchronization Date
-
The date when the Infor LN project data is synchronized with the external scheduling package data.
- Synchronization Status
-
The status of the synchronization process of Infor LN project data with the external scheduling package data.
Allowed values
- Initial: Infor LN project data yet to be exported or imported to XML.
- Synchronized: Infor LN project data is completely and successfully synchronized (export or import) with the external scheduling package. For export, the Synchronized by field is set to Infor LN. For Import, the Synchronized by field is set to External Scheduling Package
- Modify: Infor LN project data is modified after the last synchronization with the external scheduling package.
- User ESP
-
The code of the user who accesses the external scheduling package (ESP) data.
Note: You can select another user (planner) to access the external scheduling (ESP) data and import a schedule to Infor LN. There is no requirement to disconnect the ESP using the Disconnect option in the Action menu for selecting a new user. - Project Creation User
-
The code of the user who creates the project.
- Use LN Calendars
-
If this check box is selected, Infor LN calendar data is exported to the external scheduling interface.
If this check box is cleared, Infor LN calendar data is not exported to the external scheduling package (ESP). Effectively, the size of the calendar data in the exported XML file is reduced. Planning date and the duration is scheduled based on the external scheduling package (ESP) calendar.
- Availability Type ESP
-
The default availability type used by the external scheduling package.
- Calendar ESP
-
The code of the calendar used by the external scheduling package.
- Simulated Start Date
-
The date and time when the project is scheduled to start.
Note: This value is defaulted from the ESP, if not defined in Infor LN and can be used for further planning. - Simulated Finish Date
-
The date and time when the project is scheduled to start.
Note: This value is defaulted from the ESP, if not defined in Infor LN and can be used for further planning. - Simulated Duration
-
The expected time required for the project to be executed.
Note: This value is defaulted from the ESP, if not defined in Infor LN and can be used for further planning. - Time Unit for Hours ESP
-
The time unit in which duration is expressed.
- OBS
-
The code of the organization breakdown structure that is linked to the project.
- OBS Mapping to Outline Code 1-10
-
The outline code that must be mapped to the organization breakdown structure (OBS) code in Infor LN. For example, an external scheduling package such as Microsoft Project allows for 10 outline code system for tasks. This captures the outline code system that must be used. These outline codes are then synchronized with the organization breakdown structure in Infor LN, manually.
Note: Default value is 1. - OBS Description
-
The description or name of the code.
- Company
-
The code of the company in which the Infor LN project data is imported/ exported to the external scheduling package.
- Company Name
-
The name of the company in which Infor LN project data is imported/ exported to the external scheduling package.
- Client Name
-
The name of the server from/ to which the Infor LN project data is imported/ exported to the external scheduling package.