Using the External Scheduling Interface session

You can use the External Scheduling Interface (tppss2231m000) session to export a project to the external scheduling package (ESP). A XML file is used to export the data. Note You can also import a project to the LN application, using a XML file, after you optimize the planning process in the respective scheduling package.

You can also use this session to:

Import or export multiple projects from or to an external scheduling package.
Only export the calendars defined in these sessions:
- Calendars for External Packages (tcccp0181m000)
- Employees (tccom0501m000)
- Trade Groups (tppdm0530m000)
- Equipment (tppdm0112s000)

These are the options that are available in the session:

Export

Use this option to transfer the general project information to the ESP.

This project information is exported to the XML or used in the process to create the XML file:

Start Date and Finish Date of the project
Description
Calendar and Availability Type
Currency for the External Scheduling Package
Time zone of the Company

Important!

The ESP requires a project Start and Finish date and the Duration (calculation based on the start and finish date including a Calendar and Availability Type combination). However, in Infor LN these fields are not mandatory. In this scenario, the session is used to determine the default date. It is recommended that you include this data in the application to reduce the amount of work required to rearrange tasks in the ESP.

The Activities and Budget Lines (Tasks), Standard Costs Objects, project related Cost Objects (Resources), and Calendars data can also be exported to the ESP.

Activities and Budget Lines (Tasks)

This data is exported to the ESP from the Activities (tppss2100m000) session:

Identification information such as Activity, Budget Status and the related activity lines.
Scheduling information such as Scheduled Start Date and Scheduled Finish Date, Calendar, Duration (calculated), work, and the Milestone. The relations as defined in the Activity Relationships (tppss2510m000) session are also transferred. Note: Check the appendix for the exact mapping of the LN information to the XML file.
Progress information such as Actual Start Date, Actual Finish Date, and the Schedule Percentage Complete.
Costing information such as Quantity, cost , and amount.

If a task calendar does not exist or is not configured correctly, the project calendar data is used to calculate the scheduling information. However, the application displays a warning.

By default, all budget lines are exported to the ESP, but it is possible to configure project specific restrictions using the Transfer Assignment option in the session. The values are defaulted from the Project Planning Parameters (tppss0100s000) session. If the resources of a specific cost type are not exported, the corresponding budget lines cannot be included. For example, if Equipment is not included as a resource type, the corresponding budget lines for equipment also cannot be selected for export. It is recommended that you only export cost types and cost objects for which a value is specified in the scheduling package and that are required for planning.

See To use a plan.

Project Cost Objects and Standard Costs Objects (Resources)

Cost objects are included in the export only if the cost type is selected and if the Used in Schedule option is selected in the respective cost object sessions. Using these options, it is possible to prevent that cost objects that are not required are included in the XML to ensure that the files are manageable.

This data is exported to the ESP:

Identification information specified in the Transfer Resource group box such as the resource type and cost object.
Scheduling information such as the Calendar.
Costing information such as the sales price and cost rate.
Additional information such as employee information, user account, and email address from the Employees (tccom0501m000) session.

Restrictions for the export of Cost Objects and other resources:

Cost Object/Resource	Restriction in Cost Object	Restriction Session option “Transfer Resources”
Employees	Used in Schedule = Yes	Employees = Yes
Trade Group	Not Applicable	Trade Group = Yes
Standard Labor	Used in Schedule = Yes	Labor Cost Object = Yes
Project Labor	Related to selected project	Labor Cost Object = Yes
Standard Equipment	Used in Schedule = Yes	Equipment = Yes
Project Equipment	Related to selected project	Equipment = Yes
Standard Subcontracting	Used in Schedule = Yes	Subcontracting = Yes
Project Subcontracting	Related to selected project	Subcontracting = Yes
Standard Sundry Costs	Used in Schedule = Yes	Sundry Costs = Yes
Project Sundry Costs	Related to selected project	Sundry Costs = Yes

Assignments (Budget Lines)

Activity budget lines are used to define the demand for resources that are required to accomplish a task. This demand can be expressed in units such as pieces (material, subcontracting, or sundry), or in a time unit such as hours (equipment, labor, and subcontracting).

Example

For a labor line with cost objects, Labor, Employees = ARNOPNT, and Trade Group = AP.

The sequence in which the cost object is evaluated and transferred is Labor, Employee, and Trade Group. You can use the options in the Transfer Resource group box to determine, if a cost object level must be skipped.

Note:

The Labor Cost Object check box must be selected to specify the cost object Labor.
If the Transfer Resource data is cost object, Labor and resource is located and assigned to the same. However, if the Employees and Trade Group check box is selected, but the employee is not linked to the Activity Budget Labor Line, a resource is not assigned to the budget line in the ESP. An error message is also displayed during the export.
The Employees and Trade Group check boxes are optional.

Conclusion:

Cost object of the type, Labor must be linked to an assignment. For a cost object of the type, Employees and Trade Group, the Employees and Trade Group check boxes are not selected, the resource cannot be located in the Activity Budget Labor Line. Additionally, it is possible that the session detects an empty Trade Group or Employee field, and an error message is generated.