About Cost Center for Aviation Maintenance

Explanation

In Maintenance Execution, the Cost Center on a work package or task comes from the Issue To Account value defined in CAMO. The Cost Center is shown in the Pre-Posting dialog and is carried through to finance transactions when costs are reported.

The Cost Center is read-only in Maintenance Execution. To change it, update the Issue To Account in CAMO and republish the work package or task to Maintenance Execution.

Accounting Setup Requirement

When Issue To Account is mapped to the Cost Center in pre-posting, the system uses the code part (B–J) that has Logical Code Part set to Cost Center for the company that owns the work package site. This setup is mandatory: whichever code part you use as cost center must have Logical Code Part set to Cost Center. If it is not configured, Issue To Account values from CAMO cannot be stored in pre-posting.

Configure code parts in IFS Financials before using Maintenance Execution finance. See Define Code Parts.

Where Issue To Account Is Defined in CAMO

Issue To Account can be set at three levels in CAMO:

• Aircraft - mandatory; every aircraft has a value
• Work Package - optional
• Task Definition - optional

How the Cost Center Is Resolved

When a work package or task is published from CAMO to Maintenance Execution, the system resolves the Cost Center using the following hierarchy:

Work package

If Issue To Account is set on the CAMO work package, that value is used. If not, the aircraft-level value is used.

Task

If Issue To Account is set on the CAMO task, that value is used. If not, the work package value is used. If the work package also has no value, the aircraft-level value is used.

Fault and ad hoc tasks

For corrective tasks on faults and ad hoc tasks, the Cost Center is inherited from the parent work package when one is available. If the work package has no Issue To Account value, the aircraft-level value is used.

When Values Change

• Change in CAMO after publish: When Issue To Account is updated in CAMO on a work package or on any task in the work package and republished, Maintenance Execution updates the Cost Center on the affected work package or task. This applies to work packages in In Work or Complete status where Use Maintenance Execution Module (MEX) is selected in CAMO.
• Inherited values: If a task or work package has no own Issue To Account and inherits its Cost Center from a parent level, a change to the parent value in CAMO is reflected on the inheriting records after republish.
• Requirement or block change after task creation: If Issue To Account changes on a requirement or block after tasks were already created, only new tasks created from that requirement or block receive the new value. Existing tasks are not changed retroactively.
• Commercial closure: Once a task reaches commercial closure in Maintenance Execution, no further Issue To Account changes are accepted.