Alternate Path & Node Mappings

* = Required

Alternate Paths

Name

Description

Type

Values

AutoBuildLinearPath

A boolean value that triggers whether or not APS will automatically construct a simple linear path based on the available Operations Boolean True:
APS will automatically build a simple, linear path.

False:
APS will require the user to manually define the Operation flow.

AutoUse

This will determine when APS will choose an Alternate Path Node to automatically use for the Operation flow.

- IfCurrent:
The path is chosen only if it’s marked as CurrentPath.

- Regular Release:
The Path is released, as usual, based on the optimize settings, activity JIT start dates, etc.

- ReleaseOffsetFromDefaultPathsLatestRelease:
A TimeSpan that defines when the path becomes eligible for automatic selection. The Alternate Path will not be used before the default path’s release date + AutoUseReleaseOffsetDays.

String IfCurrent

Regular Release

ReleaseOffsetFromDefaultPathsLatestRelease

AutoUseReleaseOffsetDays

Defines the number of days when the path becomes eligible for automatic selection. The alternate path will only be usable after the default path's release date + this number of days.  Double  

ExternalId*

The identifier for the Alternate Path. String  

JobExternalId*

The identifier for the Job to which the Alternate Path will be associated. String  

MoExternalId*

The identifier for the Manufacturing Order to which the Alternate Path will be associated String  

Name

Identifies the AlternatePath. String  

Preference

These values can be used in different ways by custom algorithms and serve as a visual indicator to the planner. Int32  

Alternate Path Nodes

Name

Description

Type

Values

AllowManualConnectorViolation

If true, operations can be moved to resources that are invalid based on the predecessor resource connectors. This can be used to allow a temporary violation which is flagged to give users more flexibility to manually reconcile as well as make exceptions.  Boolean  

AutoFinishPredecessor

Specifies when the predecessor operation status will be automatically changed to "Finished".

- NoAutoFinish: Users must manually change the status to finish.

- On Successor Setup Start: The predecessor operation will be set to finished when the Setup span of the successor operation starts.

- On Successor Run Start: The predecessor operation will be set to finished when the Run span of the successor operation starts.

- On Successor Post-Processing Start: The predecessor operation will be set to finished when the Post-Processing span of the successor operation starts.

- On Successor Finish: The predecessor operation will be set to finished when its successor operation is complete. 

String NoAutoFinish
OnSuccessorSetupStart
OnSuccessorRunStart
OnSuccessorPostProcessingStart
OnSuccessorFinish

IgnoreInvalidSuccessorOperationExternalIds

If true, invalid successor operations will be ignored.  Boolean  

JobExternalId*

The identifier of the job associated with Path. String  

MaxDelayHrs

Total hours operation can be delayed after the end of the predecessor. Double  

MoExternalId*

The identifier of the manufacturing order associated with path.  String  

OverlapPercentComplete

Specifies the percentage of the predecessor operation that must be completed before the successor operation can start when using PercentComplete Overlap Type.  Decimal  

OverlapSetups

Whether successors can start setting up before the setup is complete on this operation. Boolean  

OverlapTransferHrs

Specifies the number of hours that must pass after the start of the predecessor operation before the successor operation can start when using TransferSpan Overlap Type.  Double  

OverlapType

When using overlapping operations, an operation does not have to wait for its predecessor to finish completely before it can begin.

- No Overlap: The entire predecessor operation must complete before the successor operation can begin.

- Transfer Qty: The successor operation can begin once the first operation has produced a specified quantity (specified in the OverlapTransferQty field in the Operation Mappings).

- Transfer Span: Successor can begin after the first has been running for a specified time (specified in the OverlapTransferHrs field of the Alternate Path Node Hrs).

- At First Transfer: Successor can start once a specified number of items is produced and transferred to inventory (specified in the TransferQty field in the item mappings)

- Transfer Span After Setup: Successor can begin after the OverlapTransferHrs plus any setup time.

- Percent Complete: Successor can begin after the predecessor operation has been completed to a percent specified in the OverlapPercentComplete field in the Alternate Node Mappings.

 

String NoOverlap
TransferQty
TransferSpan
TransferSpanBeforeStart
AtFirstTransfer
TransferSpanAfterSetup
PercentComplete

PathExternalId*

The identifier of the path. String  

PredecessorOperationExternalId*

The identifier of the predecessor operation associated with path. String  

SuccessorOperationExternalId

Successor Operation ID associated with Path String  

TransferHrs

Specifies the number of hours that it takes for the items to be transferred from the predecessor operation to the successor operation. The successor cannot start until this time passes. Note: When used in combination with OverlapTransferSpan, the effect is additive. Double  

UsageQtyPerCycle

The quantity of the operation that is needed for each cycle of the successor operation. This is used for calculating when a successor activity can start in an overlap situation.  Double