Docs / Getting Started
Configuration Transport
ASAPIO-specific configuration is stored in namespace tables with delivery classes that do not always auto-record changes. Therefore, transports must be prepared deliberately.
Overview
Most ASAPIO customizing is system-specific. Transport requests should include exactly the entries required for downstream systems.
Via Event Studio
- Open Interfaces in table view.
- Select interface rows.
- Execute Transport Interface Configuration.
- Assign/create transport request and confirm object collection.
Via SAP GUI
- Open SE09 and create/open a workbench transport.
- Open task object list and switch to edit mode.
- Add table objects with Program ID
R3TR, Object TypeTABU, Object Name = table name. - Use table key
*for all entries, or maintain explicit keys for selective transport.
ASAPIO Configuration Tables
| Table | Purpose |
|---|---|
/ASADEV/AMR_EVEN | Load events |
/ASADEV/ACI_ADPT | Cloud adapter definitions |
/ASADEV/AMR_CODE | Codepages |
/ASADEV/AMR_CONN | Cloud instances |
/ASADEV/ACI_SHDE | Attributes per cloud instance |
/ASADEV/ACI_CNST* | Global constants |
/ASADEV/ACI_GLOB | Global function activation |
/ASADEV/ACI_DEFA | Default values |
/ASADEV/ACI_EMAP | Error and return code mapping |
/ASADEV/AMR_OBJ | Outbound objects |
/ASADEV/ACI_HATT | Header attributes |
/ASADEV/ACI_XML | XML mapping fields |
/ASADEV/AMR_OB_I | Inbound objects |
/ASADEV/ACI_MDOC | Inbound field mapping |
/ASADEV/ACI_FGUN | Fieldglass UoM mapping |
/ASADEV/ACI_FGPL | Fieldglass plants |
/ASADEV/ACI_FGRM | Fieldglass role mapping |
/ASADEV/ACI_FGCC | Fieldglass company codes |
/ASADEV/DATA_EVE | Event Studio event definitions |
ASAPIO Payload Design Tables
| Table | Purpose |
|---|---|
/ASADEV/DYN_VIEW | Payload design definitions |
/ASADEV/DYN_VERS | Payload design versions |
/ASADEV/DBJT_INP | Join input metadata |
/ASADEV/DBJC_INP | Join condition metadata |
/ASADEV/DYN_FLDS | Payload fields |
/ASADEV/DBAN_INP | Additional input metadata |
/ASADEV/ACI_PD_S | Payload Designer settings |
/ASADEV/ACI_PD_U | Payload Designer user settings |
Multi-Client Systems
Use SCC1 to move transport requests from customizing client to test client when required.
First-Time Transport
For first-time landscape rollout, transport both workbench and customizing requests so BC set auto-configuration and manual customizing are both available in target systems.