The Maintenance Planning Process entails the creation or request for a task to be executed, the planning thereof, the allocation and execution of the task and the feedback of all relevant data. Execution Work Orders can originate from two sources:

  • Ad Hoc: An Ad Hoc Work Order refers to a work order that is created as a result of an unforeseen maintenance task having to be performed. In spite of the initiation of the work being Ad Hoc (not foreseen), it does not mean that the work has not been pre-planned - Event templates can have been created for the work.
  • Planned: Equipment manufacturers prescribe maintenance events to prevent incipient failures before they occur or before they develop into major failure. These Work Orders will all be transferred from the Forecasted Maintenance Schedule.

These forms allow you to manage work-in-progress (WIP). All uncompleted tasks in WIP are visible and colour coded according to status of the task (based on your choice of colour codes – see Status Codes). Resources can be maintained – added or deleted, quantities changed, and specific resource allocation can be done. Work orders can be released for work completion and detail data capture of feedback for each Work order and task is available.

Definition of Preventative Maintenance

Preventative Maintenance: This is a set of predefined events or tasks (activities) that are performed on plant equipment, machinery, and systems before the occurrence of a failure, in order to protect them and to prevent or eliminate any degradation in their operating conditions.

The preventative maintenance is carried out at pre-determined intervals or according to prescribed criteria and intended to reduce the probability of failure or the degradation of the functioning and the effects limited on equipment (vehicles, forklifts, plant machines) or facility (plants, mines or factories).

The advantage of applying preventive maintenance activities is to ensure:

  • That machines, equipment and facilities will not have failures that would cause serious production losses;
  • That the tasks includes replacements, adjustments, major overhauls, inspections and lubrications on the correct instance and time;
  • The aim of preventative maintenance is to maintain machines, equipment and facilities in such a condition that breakdowns and emergency repairs are minimised.

The following outside factors have an effect on the effectiveness of preventative maintenance:

  • Adequate number of resources in maintenance sections in order to perform this type of maintenance;
  • Correct choice of production equipment and machinery that is suitable for the working environment and that can tolerate the workload of this environment;
  • Ensure required resource qualifications and skills, which can be gained through training;
  • The support and commitment from executive management to the process and the necessary policies and procedures are in place;
  • Proper planning and scheduling of preventative maintenance programme.

The basic steps of Preventative Maintenance Planning

  1. Create and setup of Organisation Base Setup
  2. Create and setup of Vehicle/Equipment Object for use in Preventative Maintenance
  3. Create and setup of Event templates specifically for Preventative Maintenance
  4. Create and setup of a Specific
  5. Create, setup and process of Forecasting
  6. Transfer process to Execution
  7. Create and process of Execution Work Order
  8. Create and process of Feedback
  9. Create and process of Invoicing

Step 1 - Organisation Base Setup

Organisation structure covers many of the default integration parameters used downstream in 360° Strategic Asset Management. By definition the organisation structure define all the rules how one organisation interfaces with another organisation within 360° Strategic Asset Management, as well as how the stock reservation, billing, financial accounting, etc. will be done for a certain organisation or organisation unit.

It is also important to setup physical locations in which an organisation is located. In principle it is possible for an organisation to be distributed across various physical locations. If AX Integration is on the Locations will be setup in Stock and Warehouse Management Module of standard AX.

Within the organisation structure functionality, the focus is on maintenance, service requests, equipment/operations management, contract management and the organisation allocation is driven by the organisational responsibility. All maintenance, operational and contract events within 360° Strategic Asset Management 360° Strategic Asset Management are related to a 360° Strategic Asset Management Organisation. These events must be allocated to an organisation and the organisation “supply” a vast amount of the defaults used in the creation of a new event.

Objectives

The following base setup functionalities should be identified and done as pre-requisites for the major processes as part of the optimal use of 360° Strategic Asset Management product.

  • Create, define and setup status codes and sequences of each
  • Create and define the Generic setup:
    • Setup of number sequence (Part of Organisation Administration)
    • Setup of general use information (Working Calendar, ERP integration, default service item)
    • Setup infrastructure (Report Server and SMS Service)
    • Setup integration (Integration properties for person, facility and support equipment)
    • Setup of account information (General ledger accounts)
    • Setup of journal names (Journal names in general ledger)
    • Setup of project integration (Valid project groups in Project Management and Accounting)
    • Setup of default accounting organisation (Valid organisation in Objects)
  • Create and define base characteristics and characteristic groups
  • Automatic process of application base data integration from standard AX:
    • UOM Codes
    • Currency
    • Resources (Product Master)
    • Warehouses
  • Create base interest rate data for the company

Definition of Base Setup

The 360° Strategic Asset Management general base setup will be used as base configuration throughout the application and assist in determining whether or not the configuration will be necessary for your particular implementation. Ensure that you create a contract/rental organisation in the base setup and for lease contracts the payment base rate setup is required per company.

For more create process detail of base setup process, refer back to Base Configuration

Step 2 - Managed Objects (Vehicles/Equipment/Property)

Create and Setup of a Transport Object

For more detail definition and setup of objects, refer back to About Transport Object Definition

- OR -

Click here for the step by step - Create a Vehicle Object Structure

NOTE

The steps for the creation of objects are the same, but all objects must have the indicator ticked "Available on contracts" in order to use object for contract event templates, specific assets to be used on contract.

Step 3 - Setup Event Template for Maintenance Planning

Event templates plays a role in the Organisation and the scheduling of services, materials, equipment and resources to assist in the administration and process flow.

This function is used to define a generic Event Template in terms of identification, duration, costs, status, frequency, etc.

Events or standard resource lines must be defined for all tasks that are performed repetitively, items/resources that occurs on the work order as a standard, for example a specific vehicles' items used on a minor service.

Defined Event Templates are used as a library of tasks, which facilitate uniform tasks for budgeting and task history analysis. It is also a method to do life cycle planning.

Objectives

The Objectives are:

  • To define and setup event definitions which will be used within an organisation for specific objects;
  • To define and setup event types;
  • To understand why and how to define the create of event templates for objects

Definition Event Templates

An event template determines the basic composition for a contract task to be used on an object or service type and contains information about required resources, activities and organisations that can perform the task. Once established, the template can be called and re-called from the library of event templates) instead of the registration of every single task as and when required.

These defined tasks are used as standard templates to facilitate uniform task execution and task history analysis. It is also a means to do life cycle planning.

Setup of Event Definition

Event definition is used to define the setup of default event templates regarding any instance or occurrence of tasks. Execution events can be a specified condition/action and the commencement of default proceedings. A execution event can in principle be all the standard tasks that occur on the work order during the period of the execution order.

Every event can consist of a number of activities (procedure step). An event activity is an action to be performed by a person or persons, as well as the tasks that are involved in a specific event. Example of event activities for a vehicle's standard services:

  • Lube Service (Normally your 10000km interval service)
  • A-Type Service (Normally your 20000km interval service)
  • B-Type Service (Normally your 90000km interval service)

When defining the event definition for execution planning, the execution type can be defined as one of following types or selected "Not Applicable":

  • Full maintenance contract
  • Preventative maintenance agreement
  • Long term rental with full maintenance
  • Long term rental with preventative maintenance agreement
  • Used rental

Setup of Event Object

After object assets are identified and the hierarchy or structure of each have been defined, it is essential that pre-determined events are then defined in order to maintain, optimise and fully utilise their facility.

Industries will also need the capability not only to create and fulfill predetermined events but will also need the ability to create additional events pertaining to their physical assets which are of an Ad-Hoc nature. (Ad-Hoc is a Latin phrase which means "for this purpose", unscheduled.)

No matter the event, key information is required to ensure the events can happen successfully and in the most efficient manner as possible.

Event Object Tasks should be defined for all tasks that are performed repetitively. The latter can include service tasks (for example: insurance, monthly rental, monthly usage, delivery, collection) which occurs frequently.

For the explanation of the setup of event objects that are link to an event definition we will use the minor servicing of a vehicle.

In the event definition task for an execution order the setup is for example the servicing of a vehicle event. This event has a number of actions against it that will define the standard service item lines.

With the creation of event objects more than one object (vehicle, equipment, etc.) can be linked to an event template (definition). Example of event object linked to a template:

The event object has the following setup tasks:

  • Event Budget reflects the resource requirements/standard service items to be used to execute the event and is influenced by the requirements of the object (availability, serviceability). If the owner has insufficient capacity to support the vehicle or equipment, certain selected support elements can be routed to other organisations or work can be performed by contractors and sub-contractors.
  • Event characteristics are used to define event activities or to define characteristics for feedback by type execution order or contract. This form is used to define the characteristics for a specific event object. Specific characteristics will be allocated to a specific item in an event.
  • Event Permits is specific permits or certificates of event resources/items. If permits are specified for an event, the system will validate that the required permits are issued and linked to a task before a job may be executed.

For more detail information of Event Templates, refer back to Setup of Event Templates

The following is an example of a vehicle A-service Event Template:

1.      The following example of the Event Definition is the default content for a specific vehicle type.

 

2.      The above example of the Event Object tasks. Event Object Tasks should be defined for all tasks that are performed repetitively.

 

 

  1. The above example of the Event Budget tasks. The budget reflects the resource requirements to be used to execute the event and is influenced by the serviceability requirements of the equipment. If there are insufficient capacity to support the equipment, certain selected support elements can be routed to other organisations or work can be performed by contractors and sub contractors.
  2. To execute an event, resource availability needs to be verified against the requirements. The following resource budgets needs to be managed:
    1. Trade Budget: The trade budget deals with the skill of the person required to perform the event. The budgeted requirement for the event versus actual available trades can be compared to determine if trade shortages exists. From this management can decide to:
      • Continue and execute the event
      • Postpone the event for a later date
      • Make use of contractors to supplement own trades and perform the event
    1. Location Budget: A typical location required to perform an event is a workshop with service bays. The booking of a service bay needs to be controlled to ensure its availability for an event. The budgeted requirement for the event versus actual available facilities can be compared to determine if a shortage exists.
    2. Support Equipment: If specific support and test equipment (tools) will be need then it should be booked to perform an event and the budgeted requirement for the event versus actual available support and test equipment can be compared to determine if shortages exists.
    3. Material Budget: Material can be defined as all spare parts, consumables and related inventories reserved to perform an event. Material reservation against an event will remove the stock from the open balance to reflect the allocation. This provides full visibility to the material planner in order to have control over the stated requirements versus available stock.
    4. Services Budget: The user can book an already accredited contractor against an event.

 

  1. The above is the Setup Menu options for Event Objects.

 

  1. The above example of the Event Intervals. Event intervals are the scheduling of tasks. This could be Calendar, meter or both depending on the type of object. This is used to define the interval/s for programmable events. Multiple intervals may be defined per event.

The following is an example of a vehicle B-service Event Template:

 

  1. The above is an example of the Event Budget tasks. This tasks on the A-service will be different from the tasks of the B-service.

 

  1. The above is an example of the Event Budget tasks. This tasks on the A-service will be different from the tasks of the B-service, but some of them might be the same, for example "oil change", etc.
  2. The above example of the Event Action tasks. An event action is an action task to be performed and needs to be certified by a skilled worker, but is not considered important enough to be classified as an individual event. Actions can also be used to identify safety procedures per event. Event Actions should be defined for all the different actions that are used repetitively for this specific event.

 

  1. The above is an example of the Event Intervals. Multiple intervals may be defined per event. The forecasting function will forecast a planned occurrence for the unit of measure that will cause the earliest occurrence.

 

  1. The above is an example of a related event and event ageing link to an event object. In this instance the A-service is a related event to the B-service and the event ageing will be used for the suppression of the event with regard to when it will happened.

Step 4 - Setup Specific for Maintenance Planning

The specific object register is crucial in defining how a specific instance of this object will be managed throughout its life cycle.

Equipment Register: Specifics can be specific detail to a part, item, person, etc. This function will open a form displaying the only information of type Equipment and its lower level structure in a tree view format. This function is also used to update the specific structure for the equipment type in accordance with the generic structure. It should only be necessary to use this function if the generic configuration structure template of the object type has been changed. Tangible properties (asset) which include things such as various equipment types, mobile equipment, etc. which is used in the operations of a business. Examples of equipment include vehicles (light and heavy), passenger aircrafts, helicopters, ground moving equipment, support equipment, etc. Equipment can be in a pipeline i.e. in a warehouse, technical store, in reception, in production, in maintenance, in operation or in the process of disposal. Maintaining the Equipment register enables the organisation to manage its inventory across the entire pipeline. This implies that control is gained over the inventory items between measuring points in a particular path, expressed in quantitative and/or financial terms.

Objectives of Specific Register:

The Objectives are:

  • To define and setup specifics for equipment, facilities, vehicles, personnel, livestock, etc. (Assets)
  • To classify specifics into groups
  • To link the physical asset to an specific type, organisation and events
  • To understand why and how to manage the activities and details pertaining to the registered physical assets
  • Maintain specific structures

Definition of Specific

Management requires information at strategic level to plan object utilisation. Every object is registered and their statuses are monitored. The specific, rental and operational statuses of an object must be known to make informed decisions with respect to its rental and/or operational utilisation while taking cognisance of the current status and historical performance. Various functionalities on 360° Strategic Asset Management allow the owner to gain access to the necessary information.

Use this process to create and maintain a list of specifics for an object. Specifics can be specific detail to a part, item, person, etc. This function will open a form displaying the selected object and its lower level structure in a tree view format. This function is also used to update the specific structure in accordance with the generic structure. It should only be necessary to use this function if the generic configuration structure template of the object type has been changed.

Setup of Specific Register

The process is initiated when an instruction is received to register a new, or maintain a current specific object. Firstly, it must be classified into a group. An object group is made up from similar object types e.g. aircraft, vessels, motor vehicles, manufacturing equipment, etc. The current status of all the registered objects needs to be maintained as this can influence the intended utilisation of your specific objects.

Before you can release specific equipment for a job or rent it on contract it is important to take cognisance of its current status with respect to the following:

  • Is the specific object available for rental period?
  • Are there any open work orders against the equipment? If so, will the work order influence the intended application of the equipment?
  • Will any warranties be violated when the equipment is utilised to perform the intended job?
  • Are all the required equipment accessories available to perform the intended job?
  • Are the necessary permits still valid and current to perform the intended job with the equipment?
  • Have all the scheduled maintenance tasks been performed on the equipment, or will one become due during the contract period?
  • Will the equipment be capable of performing the intended job according to the registered parameters?

Setup of a new specific structure

Use this form to create and maintain a list of specifics for an object. Specifics can be specific detail to a part, item, person, etc. This function will open a form displaying the selected object and its lower level structure in a tree view format. This function is also used to update the specific structure in accordance with the generic structure. It should only be necessary to use this function if the generic configuration structure template of the object type has been changed.

For more detail information to create Specific Structure for an Equipment Specific, refer back to Setup and Maintain of Specific Register

Example of a vehicle specific structure:

 

Setup of Characteristics

With the setup of characteristics to a specific object, you will allocate characteristics that will define the object uniquely. For more detail information to create Specific Characteristic, refer back to Setup and Maintain of Specific Characteristic

Setup of Ageing

This function displays the current ageing status of the specific. The data displayed is the current meter reading, cumulative meter reading, the reading when installed in the current position and the reading of the parent when it was installed. The mentioned data is displayed for each UOM applicable to the specific. Ageing parameters are used to measure and record the age of specific meters and current values, for scheduling of maintenance or administration. Object structure ageing data is setup for a certain position in the structure. If a source structure is defined the item installed in the selected position will inherit ageing data from the source position. If a source is not defined the item is seen as having its own meter data against which usage feedback is done.

For more detail information to create Specific Ageing, refer back to Setup and Maintain of Specific Ageing

Setup of Plan Usage

It is important that the servicing and maintenance of the equipment (air conditioner) is scheduled on the intervals that is required. For the forecast scheduling to work, the future planned usage or utilisation of the specific object has to be defined. The records entered for this specific may never overlap and no gaps may exist between the entries. For example: If a vehicle will be used for 6 months with a planned kilometer usage of 15 000km, and then for 1 month it will not be used, and then again for 1 year with a planned usage of 30 000km. Add an entry for the first instance with a 6 month period and a planned usage of 15 000km. Add a second entry with a 1 month period and a planned usage of zero kilometers. Then add a third entry with a 1 year period and a planned usage of 30 000km.

For more detail information to create Specific Plan Usage, refer back to Setup and Maintain of Specific Plan Usage

Setup of Resources

Specific resources can be allocated to a specific, for example a person (trades) and assets. With AX integration ON, this table will be updated on regular intervals from the following AX standard tables and 360° Strategic Asset Management tables:

  • Customers (Customer table – Sales Ledger)
  • Facilities (Specific Structure table –360° Strategic Asset Management)
  • Fixed assets (Assets table – Fixed Assets)
  • Items (Items table, released only – Product Information Management)
  • Service Items (Items table, released only – Product Information Management)
  • Suppliers (Vendor table – Purchase Ledger)
  • Support Equipment (Specific Structure table – 360° Strategic Asset Management)

For more detail information to create Specific Resources, refer back to Setup and Maintain of Specific Resources

Setup of Permit

If a valid permit is needed for this specific, create the permit type and allocate to the specific. This is applicable to all types of licenses, certificates.

For more detail information to create Specific Permit, refer back to Setup and Maintain of Specific Permit

Create options from Specific

From a specific you can create one of the following:

  • Contract
  • Execution/Operation
  • Failure
  • Incident
  • Warranty Claim

Functions for a Specific

The following functions can be done on a specific:

  • Change Parameters
  • Exchange Process

Summary function on Specific

This function will allow the user to VIEW the all records created for the selected specific in:

  • Contract
  • Execution/Operation
  • Failure
  • Incident
  • Warranty
  • Permits

Enquiries on Specifics

From the enquiries function the user will be allowed to view certain graphs, reports and history for the selected specific.

Step 5 - Forecasting (Scheduling)

Utilising an equipment to execute requires careful planning and is dependent on other occurrences which might influence its availability. As for maintenance scheduling, the equipment can also be scheduled to perform a task. Aspects that requires consideration when scheduling equipment utilisation includes:

  1. Equipment utilisation: The forecasted usage for the equipment.
  2. Equipment exchange plan: The rotation of equipment over an extended period of time.
  3. Modification status of equipment: The status of modification embodiment on the equipment.
  4. Event history: Type of events that have been performed on the equipment in the past.
  5. Scheduled events: Scheduled maintenance events against the equipment for the short to medium term.
  6. Events included in schedule: The user may select which events must be included in the forecasting. The following values are available for selection:
    • Preventative Maintenance - If Preventive Maintenance is selected, the forecasting process will only forecast events identified as PLANNED events in the Event Template function. The firm interval will be used.
    • Corrective Maintenance - If Corrective Maintenance is selected, the forecasting process will only forecast events identified as AD-HOC events in the Event Template function. The budget interval will be used.

Setup of Forecasting:

The Forecasting process is used to schedule preventative maintenance occurrences for events within a specific time period. The results of the forecasting process are displayed on a pegboard. The forecast parameter form provides the means to setup the input parameters required for the Forecasting process. All the planned events associated with specified object and/or specific structures will be scheduled.

The selected calendar is used to identify the working times and days for the events. The end date specifies the end of the forecasting period and no further occurrences will be scheduled once this date has been reached. The end date selected has to be within the period that was setup on the event template for the specific object.

Other parameters that can be specified to narrow the forecasting selection are the owner organisation, allocated organisation and the current location of the specific structure. The Forecasting process is run as a service and the recurrence detail must be specified in order for the service to determine when the process should be run. In the case where no details are provided the service will execute the process at the interval as specified when the service was installed.

The alternative is to provide the recurring ranges and patterns on the recurrence tab. The range of the recurrence will indicate when the service must first start running the Forecasting process and when the service must stopping running the Forecast process. The process can be executed on a daily/weekly/ monthly/yearly basis. The following recurring patterns are available for selection:

  • Daily – If the daily option is selected an interval must be entered and indicate if the process must only be run on weekdays. The user must specify the interval to indicate the particular period of days between executing the Forecast process.
  • Weekly – Select the days of the week on which the process must be run. The user must specify the interval to indicate the particular period of weeks between executing the Forecast process.
  • Monthly – In case the Month/Week/Day check box is not selected the user must specify the week in the month, week day and interval the process must be executed. If the above mentioned check box is selected the day of the month and interval must be provided.
  • Yearly – In case the Year/Month/Week/Day check box is not selected the user must specify the week in the month, week day and/or the specific month. In case the check box is selected, then the number of the day in the month and/or the month must be provided.

As soon as the parameters have been entered, the next step will be to validate the correctness of the data via the Setup -> Validate data button. The results of the validation process can be viewed in the error log. Checking the data before forecasting is important as this will give an indication of errors that will prohibit the successful forecasting of events en will ensure more accurate results.

The Forecasting button will indicate immediate processing and whilst polling the queue the service will then determine that the process must be run immediately. The results i.e. the scheduled occurrences of the events can be viewed via the Forecasting register button. The status and progress information of the current Forecast is displayed on the Forecast status log form. All errors and warning messages generated during forecasting which either influenced the results or prevented events to be scheduled are written to the error log. These entries can be viewed on the error log form.

Once the forecast process is COMPLETE, the forecast record can be transferred from the forecast register to the Execution. Select the forecast record to be transferred to execution in forecast register, click on the “create button”, select if a work order or work pack must be created. (Work order is a single task selected for an execution order, and a Work Pack is the allocation of multiple work orders to a specific work pack to be executed.)

For more detail information to setup the Forecasting, refer back to Setup of forecasting (Scheduling)

Step 6 - Maintenance Execution

The forecasted event that was transferred from forecasted maintenance schedule has created an Execution Work Order in the Maintenance Planning form. Open the maintenance planning form and find the execution order by searching for the execution id that was created. The Maintenance Planning process consists of several functions. The process entails the creation or request for a task to be executed, the planning thereof, the allocation and execution of the task and the feedback of all relevant data. Execution Work Orders can originate from two sources:

  • Ad Hoc: An Ad Hoc Work Order refers to a work order that is created as a result of an unforeseen maintenance task having to be performed. In spite of the initiation of the work being Ad Hoc (not foreseen), it does not mean that the work has not been pre-planned - Event templates can have been created for the work.
  • Planned: Equipment manufacturers prescribe maintenance events to prevent incipient failures before they occur or before they develop into major failure. These Work Orders will all be transferred from the Forecasted Maintenance Schedule.

These forms allow you to manage work-in-progress (WIP). All uncompleted tasks in WIP are visible and colour coded according to status of the task (based on your choice of colour codes – see Status Codes). Resources can be maintained – added or deleted, quantities changed, and specific resource allocation can be done. Work orders can be released for work completion and detail data capture of feedback for each Work order and task is available.

For more detail information of the Maintenance Process, refer back to Maintenance Process

Step 7 - Feedback Process

The main purpose of this function is to provide feedback on work orders in progress. Feedback can be done on all resources linked to the work order. This includes:

  • Hours used per individual person (for example: Contractor, Tradesman/Technician)
  • Hours used per individual Facility and Special Tools/Equipment
  • Quantity material used
  • Revenue spent per contractor
  • Revenue spent on other unclassified resources
  1. The Work Order on which feedback must be done must be selected in the field primary ID that identifies the Work Order No. Only jobs in a status of “In Progress” will be available for selection. After a Work Order was selected for feedback the related detail for the selected Work Order will be displayed.

 

  1. The upper section provides information on the maintenance execution whilst the lower section displays in tabular form resource information.
  2. Once the actual duration, quantities are added to the feedback of the resources used, “Commit Feedback” can be pressed to process the actual feedback.
  3. After feedback is committed the status of the execution order can be changed to “Complete” that indicates that the work is completed.
  4. If the work is not complete, the user can make the decision to process an “interim invoice”.

Process Interim Invoice:

  1. On the execution specific line, select from the “Create” button the function “Post Journals”. This is the financial transactions that will post the journals to the Project table if project integration is on, or to the Sales Orders.
  2. Select “Enquiries” under “Financial transactions” and the user will find the posted journals.
  3. From Projects/Sales Orders an invoice can be generated for the customer.

Step 8 - Process Invoice (Billing) and Generate Invoice

Generate Invoices from Sales Orders:

If the work is completed the status of the execution specific line can be changed to “Complete”. If all the feedback is done and completed on this execution order, the execution order’s status can be changed to “Financial Complete”. The system will automatically run the financial transactions to create the journals for the invoicing process. The posted journals will be in Projects (if project integration is on) or in Sales Orders. Select “Enquiries” under “Financial transactions” and the user will find the posted journals. The accounting department can now make the decision to generate the “Invoice” for the customer.

If the work order posting is completed for the billing period, the Invoice/s has to be generated from the sales orders. The posted journals will be in Sales Orders. The accounting department can now make the decision to generate the “Invoice” for the customer. The following is the process for generating an invoice in Sales Ledger.

For more detail information to do Generate Invoices from Sales Orders, refer back to Generate Invoices from Sales Orders

Generate Invoices from Projects:

Still to be done

For more detail information to do Generate Invoices from Projects, refer back to Generate Invoices from Projects

Step 9 - Finalise the Execution Order

Execution Order Finished:

When the status of the execution is changed to financial complete, and all the open financial transactions on the project/sales order are closed, the execution order status can be changed to “Finished” that will indicate that this execution order is finalised.

See also

The following is the link to the standard generic setup of the different functions:

Setup of Object

About Specific Register

About Maintenance Planning

About Feedback