ERP As-Is & To-Be Process Modeling 3

Question 1

In To-Be process modeling for an ERP, what is the significance of defining 'trigger events' for each process?

Accepted Answer

They establish what initiates a process, ensuring the ERP is configured to start workflows correctly

Answer

Trigger events define what starts a process (e.g., a purchase order received), which is critical for configuring ERP workflow automation.

Question 2

A company's As-Is order-to-cash cycle takes 14 days. The To-Be model targets 5 days. What type of analysis justifies this target in the business case?

Accepted Answer

Cycle time analysis and benchmarking against industry standards

Answer

Cycle time analysis combined with industry benchmarking provides evidence-based justification for To-Be cycle time reduction targets.

Question 3

Which technique involves assigning time and cost estimates to each step in the As-Is process to quantify the impact of inefficiencies?

Accepted Answer

Activity-based costing (ABC) applied to process steps

Answer

Activity-based costing assigns time and cost to each process activity, enabling quantification of current-state inefficiency costs.

Question 4

When the To-Be model requires a process that the ERP standard functionality does not support, what is the preferred first course of action?

Accepted Answer

Re-engineer the business process to fit standard ERP functionality

Answer

Best practice is to adapt the business process to standard ERP functionality (fit-to-standard) before considering customization.

Question 5

In a To-Be process model, an 'exception handling' path is best described as:

Accepted Answer

An alternate flow that manages non-standard scenarios outside the happy path

Answer

Exception handling paths in To-Be models define how the process responds when conditions deviate from the standard (happy path) scenario.

(ERP) Enterprise Resource Planning Certified Practice Test

(ERP) Enterprise Resource Planning Certified Practice Test

ERP As-Is & To-Be Process Modeling 3