Transaction OAC0 Guide

OAC0 is where you register FileRelay as an external content server in SAP.

Before you start

• A FileRelay deployment with a workspace (see Quick start).
• An ArchiveLink source in FileRelay with a chosen Repository ID.
• The FileRelay endpoint hostname (from workspace settings — typically your org domain, e.g. filerelay.acme.internal).
• SAP authz for OAC0 (usually S_ADMI_FCD).

Configure

1. Run transaction OAC0.

   REPLACE: Screenshot of the OAC0 initial screen

2. Click Create (or F5).

3. Fill in:

Field	Value	Notes
Content Rep.	Z1	Must match the FileRelay source Repository ID exactly (case-sensitive, 2–10 chars).
Description	FileRelay - Production	Free text.
Document Area	ArchiveLink
Storage Type	HTTP content server
HTTP Server	filerelay.acme.internal	Hostname only — no https:// prefix.
Port	443
HTTP Script	ContentServer	No leading slash.
Protocol	HTTPS

REPLACE: Screenshot of the filled-in OAC0 detail screen

4. Save (Ctrl+S).

5. Test Connection — select the row → menu Repository → Connection Test. Green status with FileRelay server info = working.

Full field reference

Field	Tech name	Required	Notes
Content Rep.	ARCHIV_ID	✓	Repository ID, case-sensitive
Description	DESCRIPT		Free text
Document Area	DOC_AREA	✓	ArchiveLink
Storage Type	STOR_TYPE	✓	HTTP content server
HTTP Server	HTTP_SERVER	✓	Hostname only
Port	HTTP_PORT	✓	443
HTTP Script	HTTP_SCRIPT	✓	ContentServer
Protocol	PROTOCOL	✓	HTTPS
SSL Certificate	CERTIFICATE		Managed by SAP ICM
Version	VERSION	auto	ArchiveLink protocol, typically 0047

Common mistakes

• Case — Z1 ≠ z1. The FileRelay source and OAC0 entry must match exactly.
• HTTP Server with protocol prefix — relay.filerelay.com is correct; https://relay... is not.
• HTTP Script with slash — ContentServer is correct; /ContentServer is not.

Deeper testing with CSADMIN

CSADMIN is the test harness:

1. Open CSADMIN → select your repository.

2. Run tests in order:

   • Server Info — basic connectivity + FileRelay version.
   • Certificate Send — push SAP's system cert to establish trust (see Certificate Management).
   • Create / Get — round-trip a test document.

   REPLACE: Screenshot of a successful Server Info test

Troubleshooting

Problem	Check
Connection test fails	SAP app server can reach FileRelay on 443; proxy in SICF; ICM is up and HTTPS-capable.
"Repository not found"	Content Rep. ID matches FileRelay source repo_id exactly (case); source is Active.
HTTPS / cert errors	SAP trusts the FileRelay SSL chain — import CA certs in STRUST.

Next steps

• SAP ArchiveLink Setup
• Certificate Management
• Connections Overview