Session ID: 10368

Abstract: This customer case study is about a customer that was using carry-over functionality from E-Business Suite 11.5.10 where each maintenance activity had its own schedule. They had customized considerably to defer major maintenance that would otherwise be scheduled close to a minor maintenance. Learn how the customer got rid of all the chaos that was created due to this legacy customization and end-dated activity based schedules

Objective 1: Migration from activity-based scheduling to asset-based scheduling

Objective 2: Enhanced suppression and deferral functionality

Objective 3: Tips and tricks to getting rid of legacy customizations

Audience: Applications End User