Title and Copyright Information
Manage Application Implementation: Overview
Who Will Use the Setup and Maintenance Work Area: Points to Consider
2 Gathering Your Implementation Requirements
Related Documents: Explained
Feature Choices: Explained
FAQs for Gathering Your Implementation Requirements
What's an offering?
What's a feature?
What happens if Enable for Implementation is selected for an offering?
What's a business process?
3 Managing an Application Implementation
Implementation Projects: Explained
Implementation Project Task Lists: Explained
Predecessor Tasks: Explained
Completing Tasks not in an Implementation Project: Points to Consider
Assigning Setup Tasks: Explained
Executing Setup Tasks: Explained
Task List Scope: Explained
Monitoring an Implementation Project: Explained
Maintaining Setup Data: Explained
Business Object Dependencies: Explained
FAQs for Managing an Application Implementation
What's a setup task list?
What's a setup task?
When does a dependency need to be defined for a business object?
What happens if a task is assigned to more than one person?
Why did my implementation project omit the tasks for a new functional area or feature I enabled on the Configure Offerings page?
Why does each offering include common tasks?
When does it make sense to customize a task list?
When does a duplicate common task need to be deleted from the task list to avoid duplicating setup data?
What happens if I create a custom task and add it to an existing implementation project?
How can I see what types of setup data I enter using an implementation project?
What happens if I assign more than one user to the same task?
Why did the task not show as completed when I returned to my assigned task list after entering data?
Why did a common task I already performed and set to completed not show as completed in every instance of the task across multiple implementation projects?
When does it make sense to create an implementation project to make changes to my setup data?
When does a task need to be required?
What's an implementation project?
4 Importing and Exporting Setup Data
Configuration Packages: Explained
Exporting and Importing Setup Data: Explained
Customizing Configuration Packages: Points to Consider
Business Objects Marked as Scope Parameters: How They are Exported
Business Object Import Sequence: Explained
Export Scope: Explained
FAQs for Importing and Exporting Setup Data
What happens if I upload a different version of the same configuration package?
How can I export or import an implementation project without the associated setup data?
What happens if I modify a configuration package that I recently created?
How can I see what setup data is transferred when I export a configuration package?
How can I exclude any business objects from exporting or change the import sequences?
Why did the export process not raise any errors when it did not export any data?
Why did import errors appear when no data to import is found?
When does export or import show errors at the data level as opposed to the system level?
What happens if my import process remains in the User Action Required status?
How can I view the associated business object hierarchy?
How can I view and print any errors generated by an import or export process?
How can I cancel an export or import process that I submitted?
When does it make sense to create multiple configuration packages from the same implementation project?
Why does the configuration package contain some scope values by default?
What's a setup business object?
Scripting on this page enhances content navigation, but does not change the content in any way.