btp-abap-environment

Name: btp-abap-environment
Author: likweitan

28stars11forks

How to install btp-abap-environment?

likweitan/abap-skills/btp-abap-environment

$npx -y skills add likweitan/abap-skills --skill btp-abap-environment

Installs into the current project.

Summary

Help with SAP BTP ABAP Environment setup and development including service instance creation, ADT connectivity, communication arrangements, communication scenarios, inbound/outbound services, destination configuration, identity and access management, software components, and firs

Files · 1

View on GitHub

SKILL.md

1	# SAP BTP ABAP Environment
2
3	Guide for setting up and developing in the SAP BTP ABAP Environment (Steampunk).
4
5	## Workflow
6
7	1. Determine the user's goal:
8	- Setting up a new ABAP Environment instance
9	- Connecting ADT to the BTP ABAP system
10	- Configuring communication arrangements for integrations
11	- Creating a first ABAP Cloud project
12	- Managing software components and packages
13	- Setting up outbound/inbound connectivity
14
15	2. Identify the phase:
16	- Initial provisioning and setup
17	- Developer onboarding
18	- Integration configuration
19	- Application development
20
21	3. Guide implementation step by step
22
23	## Setup Overview
24
25	### Prerequisites
26
27	\| Requirement \| Description \|
28	\| ------------------- \| ----------------------------------------------------- \|
29	\| SAP BTP Account \| Global account with entitlements for ABAP Environment \|
30	\| Subaccount \| Cloud Foundry-enabled subaccount \|
31	\| ADT \| Eclipse with ABAP Development Tools installed \|
32	\| User \| Platform user with Space Developer role \|
33	\| Entitlements \| `abap/standard` or `abap/saas_oem` service plan \|
34
35	### Service Instance Creation
36
37	1. Navigate to BTP Cockpit → Subaccount → Cloud Foundry → Spaces
38	2. Create service instance:
39	- Service: ABAP Environment
40	- Plan: standard
41	- Instance name: e.g., `my-abap-instance`
42	3. Provide parameters (JSON):
43
44	```json
45	{
46	"admin_email": "admin@example.com",
47	"description": "Development ABAP System",
48	"is_development_allowed": true,
49	"sapsystemname": "DEV",
50	"size_of_runtime": 1,
51	"size_of_persistence": 4
52	}
53	```
54
55	4. Create a service key for ADT connectivity
56
57	### Connecting ADT to BTP ABAP
58
59	1. In Eclipse/ADT: File → New → ABAP Cloud Project
60	2. Select SAP BTP ABAP Environment
61	3. Enter the service key (JSON) or service instance URL
62	4. Authenticate via browser (SAP Identity Authentication)
63	5. Project is created — start developing
64
65	## System Architecture
66
67	```
68	SAP BTP Subaccount
69	└── Cloud Foundry Space
70	└── ABAP Environment Service Instance
71	├── ABAP System (development/production)
72	├── Software Components (ZLOCAL, custom)
73	├── Communication Arrangements (integrations)
74	└── Business Services (OData, RFC)
75	```
76
77	## Software Components
78
79	\| Component \| Description \|
80	\| --------- \| ----------------------------------------------------------------------------- \|
81	\| `ZLOCAL` \| Local development — not transportable (like `$TMP`) \|
82	\| Custom \| Transportable components — managed via gCTS or Manage Software Components app \|
83
84	### Creating a Software Component
85
86	1. Open the Manage Software Components Fiori app
87	2. Click Create (or use the `+` button)
88	3. Enter:
89	- Name: `Z_MY_COMPONENT`
90	- Description: e.g., "My Custom Component"
91	- Type: Development
92	4. Clone the component to make it available in ADT
93	5. Create packages within the component
94
95	### Package Structure
96
97	```
98	Z_MY_COMPONENT (Software Component)
99	└── Z_MY_APP (Structure Package)
100	├── Z_MY_APP_MODEL (Sub-package: CDS views, database tables)
101	├── Z_MY_APP_BIZ (Sub-package: business logic, RAP BOs)
102	└── Z_MY_APP_SRV (Sub-package: service definitions, bindings)
103	```
104
105	## Communication Management
106
107	### Concepts
108
109	\| Artifact \| Purpose \|
110	\| ----------------------------- \| ------------------------------------------------------------ \|
111	\| Communication Scenario \| Template defining inbound/outbound services and auth methods \|
112	\| Communication System \| Represents the external system (host, port, credentials) \|
113	\| Communication Arrangement \| Binds scenario + system + user, activating the integration \|
114	\| Communication User \| Technical user for inbound communication \|
115
116	### Creating a Communication Scenario
117
118	```abap
119	"Defined via ADT: New → Other → Communication Scena

People who liked this also viewed

6 picks

Type

btp-abap-environment

28stars11forks

View on GitHub

How to install btp-abap-environment?

likweitan/abap-skills/btp-abap-environment

$npx -y skills add likweitan/abap-skills --skill btp-abap-environment

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# SAP BTP ABAP Environment
2
3	Guide for setting up and developing in the SAP BTP ABAP Environment (Steampunk).
4
5	## Workflow
6
7	1. Determine the user's goal:
8	- Setting up a new ABAP Environment instance
9	- Connecting ADT to the BTP ABAP system
10	- Configuring communication arrangements for integrations
11	- Creating a first ABAP Cloud project
12	- Managing software components and packages
13	- Setting up outbound/inbound connectivity
14
15	2. Identify the phase:
16	- Initial provisioning and setup
17	- Developer onboarding
18	- Integration configuration
19	- Application development
20
21	3. Guide implementation step by step
22
23	## Setup Overview
24
25	### Prerequisites
26
27	\| Requirement \| Description \|
28	\| ------------------- \| ----------------------------------------------------- \|
29	\| SAP BTP Account \| Global account with entitlements for ABAP Environment \|
30	\| Subaccount \| Cloud Foundry-enabled subaccount \|
31	\| ADT \| Eclipse with ABAP Development Tools installed \|
32	\| User \| Platform user with Space Developer role \|
33	\| Entitlements \| `abap/standard` or `abap/saas_oem` service plan \|
34
35	### Service Instance Creation
36
37	1. Navigate to BTP Cockpit → Subaccount → Cloud Foundry → Spaces
38	2. Create service instance:
39	- Service: ABAP Environment
40	- Plan: standard
41	- Instance name: e.g., `my-abap-instance`
42	3. Provide parameters (JSON):
43
44	```json
45	{
46	"admin_email": "admin@example.com",
47	"description": "Development ABAP System",
48	"is_development_allowed": true,
49	"sapsystemname": "DEV",
50	"size_of_runtime": 1,
51	"size_of_persistence": 4
52	}
53	```
54
55	4. Create a service key for ADT connectivity
56
57	### Connecting ADT to BTP ABAP
58
59	1. In Eclipse/ADT: File → New → ABAP Cloud Project
60	2. Select SAP BTP ABAP Environment
61	3. Enter the service key (JSON) or service instance URL
62	4. Authenticate via browser (SAP Identity Authentication)
63	5. Project is created — start developing
64
65	## System Architecture
66
67	```
68	SAP BTP Subaccount
69	└── Cloud Foundry Space
70	└── ABAP Environment Service Instance
71	├── ABAP System (development/production)
72	├── Software Components (ZLOCAL, custom)
73	├── Communication Arrangements (integrations)
74	└── Business Services (OData, RFC)
75	```
76
77	## Software Components
78
79	\| Component \| Description \|
80	\| --------- \| ----------------------------------------------------------------------------- \|
81	\| `ZLOCAL` \| Local development — not transportable (like `$TMP`) \|
82	\| Custom \| Transportable components — managed via gCTS or Manage Software Components app \|
83
84	### Creating a Software Component
85
86	1. Open the Manage Software Components Fiori app
87	2. Click Create (or use the `+` button)
88	3. Enter:
89	- Name: `Z_MY_COMPONENT`
90	- Description: e.g., "My Custom Component"
91	- Type: Development
92	4. Clone the component to make it available in ADT
93	5. Create packages within the component
94
95	### Package Structure
96
97	```
98	Z_MY_COMPONENT (Software Component)
99	└── Z_MY_APP (Structure Package)
100	├── Z_MY_APP_MODEL (Sub-package: CDS views, database tables)
101	├── Z_MY_APP_BIZ (Sub-package: business logic, RAP BOs)
102	└── Z_MY_APP_SRV (Sub-package: service definitions, bindings)
103	```
104
105	## Communication Management
106
107	### Concepts
108
109	\| Artifact \| Purpose \|
110	\| ----------------------------- \| ------------------------------------------------------------ \|
111	\| Communication Scenario \| Template defining inbound/outbound services and auth methods \|
112	\| Communication System \| Represents the external system (host, port, credentials) \|
113	\| Communication Arrangement \| Binds scenario + system + user, activating the integration \|
114	\| Communication User \| Technical user for inbound communication \|
115
116	### Creating a Communication Scenario
117
118	```abap
119	"Defined via ADT: New → Other → Communication Scena

People who liked this also viewed

6 picks

Type