We wish to prevent users creating transactions (Purchase Orders, timesheets & expenses sheets) and link them to a Project Activity, where the corresponding Cost Element has not been set up. Example;

Project ID: 100763

Sub Project: Design

Activity: A (design labour)

Cost Element: Labour

When anyone books time to this activity the project transaction will register to Cost Element ‘Labour’ which then ensures this cost shows in the correct place on our Project Forecast. This is ok.

However, if we raise a purchase order, we have this going to another Cost Element called ‘Materials’. If there is no cost element for ‘Materials’ against this activity, we would like to restrict users being able to create purchase orders against the activity in the first place.