Project Selection (tppss2140m000)

Field Information

User

The logon code of the user who defines the project - connection node combination that can be scheduled for import/ export.

Note: This value is defaulted with the current user.

Multiple Import/Export

If this check box is selected, the specific project - connection node combination is selected for scheduling an import/ export of the project data.

Note: 

You can link only one project to an XML file.

LN clears this check box when you click the Reset Selection button in the External Scheduling Interface (tppss2231m000) session. However, you can select this check box.

Project

The code of the project that must be imported/ exported.

Plan

The default plan that is used to create the project - connection node combination.

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 LN to a project in the external scheduling package, this node is not specified.

Note: 

To select an activity as the connection node, these 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.

Client XML Filename

The name of the XML file with which the selected project is imported/ exported.

Note: When you import the project data from an external scheduling interface in a LN UI environment, the files must be validated against the project.

Synchronized by

The code of the user who synchronizes the LN project data with the external scheduling package data.

Synchronization Date

The date when the LN project data is synchronized with the external scheduling package data.

User ESP

The code of the user who accesses the external scheduling package data.

Project Creation User

The code of the user who creates the project.

Use LN Calendars

If this check box is selected, LN calendar data is exported to the external scheduling interface.

If this check box is cleared, 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 default calendar used by the external scheduling package.

Task Name based on

The activity related data on which the task name of the ESP is based.

Allowed values

Code

Based on Activity codes and Budget line cost object.

Description

Activity descriptions and Budget line cost object descriptions.

Activity Code Custom Field Text

The custom text field in the ESP in which the activity code is specified.

Activity Description Custom Field Text

The custom text field in the ESP in which the activity description is specified.

Activity Primary Key Custom Field Text

The custom text field in the ESP in which the activity primary key is specified.

OBS Code

The code of the organization breakdown structure defined for the activity that is linked to the project.

OBS Mapping to Outline Code 1-10

The outline code value that must be mapped to the organization breakdown structure (OBS) code. These outline codes are synchronized with the organization breakdown structure in 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 project is scheduled for import/ export.

Company Name

The name of the company in which the project is scheduled for import/ export.

Client Name

The name of the server in which external scheduling package is run.