Transport/backup of configuration data
Overview
ASAPIO-specific configuration data is stored in tables in /ASADEV/ namespace, with a delivery class that does not automatically record new or changed entries. Reason is that most customizing is system-specific and needs to be changeable locally.
Create transport request
To transport configuration settings, you are required to add the desired tables manually to a transport request.
- Go to transaction SE09,
- Create or open the desired workbench transport,
- Double-click on the task and go to tab “Objects”,
- Switch to ‘Edit’ mode.
- You can add tables by choosing
- “Program ID” as “R3TR”,
- “Object Type” as “TABU”,
- “Object Name” = the table name you want to add to the transport.
- To add all entries of the table to the transport you can enter “Table Keys” as “*” with the “Function” button.
If you want to only transport specific entries from the table, please enter the key of the entry you like to transport.
ASAPIO configuration tables
The following tables in ASAPIO namespace keep relevant configuration data:
Table Name | Purpose / Description |
---|---|
/ASADEV/AMR_EVEN | Load Events (Fieldglass, SAP Event Mesh) |
/ASADEV/ACI_ADPT | Cloud Adapter (FG_CON_N, WS_IN, SAP_EM) |
/ASADEV/AMR_CODE | Codepages |
/ASADEV/AMR_CONN | Cloud Instance |
/ASADEV/ACI_SHDE | Attributes per Cloud Instance |
/ASADEV/ACI_CNST*
|
Definition of Global Functions |
/ASADEV/ACI_GLOB | Activation of Global Functions / Constants |
/ASADEV/ACI_DEFA | Default values |
/ASADEV/ACI_EMAP | Handling of Return codes / Error messages |
/ASADEV/AMR_OBJ | Outbound Objects |
/ASADEV/ACI_HATT | Header Attributes of Replication Objects |
/ASADEV/ACI_XML | XML Mapping fields |
/ASADEV/AMR_OB_I | Inbound Objects |
/ASADEV/ACI_MDOC | Inbound Object field mapping |
/ASADEV/ACI_FGUN | Unit of Measurement conversion FG <-> SAP |
/ASADEV/ACI_FGPL | Relevant plants for Fieldglass |
/ASADEV/ACI_FGRM | Role Mapping |
/ASADEV/ACI_FGCC | Relevant company codes for SAP Fieldglass |
/ASADEV/ACI_ARCC |