You need to set up the adaptation transport organizer (ATO) in your system
landscape.
Prerequisites
For more information about system requirements, see SAP Note
2283716 .
You have maintained the following authorization fields in the transaction
Role Maintenance
(
PFCG) for the object
S_DEVELOP:
Authorization Field Description
|
Your Entry
|
Package
|
Either a specific package that you want to use for ATO, or an
* for all packages
|
Object Type
|
DEVC
|
Object Name
|
Same name as the package name
|
ABAP Program Authorization Group
|
Nothing specific
You can enter a dummy entry here.
|
Activity
|
|
Context
Some SAP Fiori apps require the ATO to be set up before these apps can be used as
desired. For more information about what apps require the setup of the ATO, please refer
to the implementation information of the individual apps.
Procedure
- Open the back-end transaction ATO Setup
(S_ATO_SETUP) or start the IMG
activity using the transaction
SPRO.
- Check if the ATO is configured for this system.
If ATO is not configured, proceed with the steps 3 to 7.
- Choose whether you want to use a prefix or a namespace for your
packages and transports.
Option |
Description |
Prefix <PREFIX_> |
Describes a custom prefix that is used for your packages and
transports. Example:
ZZ1_<Generated Name of
Object>
|
Namespace /<NAMESPACE>/ |
Describes a custom namespace that is used for your packages and transports.
Example:
/<NAMESP>/<Generated Name of
Object> |
- Define a local package where
extension items (ABAP objects) are initially stored.
ABAP objects located in this package can later be
transported to a target system after a reassignment. The
local package needs to be assigned to the software
component "Local".
Example:
$YATO_KEY_USER_LOCAL
- Define a sandbox package where
extension items (ABAP objects) are stored that are created
locally.
ABAP objects located in this package are created locally
and will never be transported. The sandbox package needs
to be assigned to the software component "Local".
Example:
$YATO_KEY_USER_SANDBOX
- Enter a sandbox prefix to distinguish
ABAP objects that must not be transported to the production
system.
- Finish the setup.
Option |
Description |
Setup with default data |
Use this option when you set up the ATO for the first time without having
specific requirements such as a predefined namespace or package.Note
This setup option is recommended for development systems.
|
Setup with specific data |
Use this option to set up the ATO with the data that you defined in this transaction.Note
This setup option is recommended for development systems.
|
Setup read only |
Use this option if users need to be able to open and see SAP Fiori apps that require
the ATO, but do not need to work with these apps. Example If this
setup option is chosen, users can open the SAP Fiori app Custom
Fields and Logic, but cannot create or modify custom fields or
logic.
|