Extraction (Properties)

Which technical user does each interface run under? (e.g. into a Communication User property)

• SAP_SOAP → AuthenticationMethod.Basic.Username:PROPERTY:BINDING

• SAP_RFC and SAP_IDOC → RFCDest:EXTERNAL:USERNAME

• RESOURCE → USER:Username for Cloud Integration credentials, BTPDestination:AuthenticationUser for BTP destinations

Which interfaces go out through a proxy? (e.g. into a Web Proxy property)

• SAP_SOAP → ProxyHost:PROPERTY:BINDING

• SAP_RFC → RFCDest:ABAP_HTTP:GATEWAYHOST - on HTTP destinations this field holds the proxy

• SAP_RFC and SAP_IDOC → RFCDest:EXTERNAL:GATEWAYHOST - external destinations store their proxy in the same field

Which interfaces reach on-premise systems through the Cloud Connector? (e.g. into a Cloud Connector Location ID property from externalized parameters)

• SAP_IS_CI → Configuration:LocationID, use the exact parameter name configured in the iFlow, e.g.Configuration:Location ID

Which SAP Gateway does each registered RFC server run on? (e.g. into an RFC Gateway Host property)

• SAP_RFC and SAP_IDOC → RFCDest:TCP_IP:GATEWAYHOST

Which connections have weak or no authentication?

• RESOURCE → BTPDestination:AuthenticationType, then filter the property in your Interface catalog for e.g. NoAuthentication

• SAP_SOAP → AuthenticationMethod:PROPERTY:BINDING

Match a technical interface to its planning ticket (e.g. into a Global Interface ID property)

• PLANNED → Metadata:Key, for example WIB-6

On the other platforms that key is not a field, so it has to come from the name or description - see ID from Description/Name.

Harmonize systems (Systems context)

• SAP_IDOC → EDIPHONE:NAME

• SAP_IS_CI → Package:Tag:YourTagName

• EAM → Metadata:Name

A complete example for the first use case above and can be extended platform by platform.

1. Create the property

Go to Settings → Properties → Overview, open the Interface tab, click + and enter:

• Name: Communication User

• Format: STRING

Click Save.

2. Create the first rule

Go to Settings → Properties → Extraction, open the Copy from Field tab and leave the context selector on Interfaces. Click + and fill in:

Click Save.

3. Run the job (from Settings → Properties → Overview or in your designated Data Source)

SAP_SOAP is read from data already stored in Integration Cockpit, so the INVENTORY job applies this rule (see Apply and Validate). Start it from your specific Data Source or click the Update Inventory button found in the Properties Overview.

4. Check the result

Go to Inventory → Interfaces → by Property, select Communication User and click Next. Every SAP_SOAP interface whose service binding uses basic authentication now shows its technical user.

5. Extend to the other platforms

The same property can be filled from every platform - add one rule per interface type, all pointing at Communication User:

After the next INVENTORY run you have one property that answers "which technical user does this interface run under" across your whole landscape - and you can filter or export by it.

```
# Extract 8-digit numeric IDs (like Global Interface IDs)
# Search Pattern: GLIF
\d{8}
# Example: "SAP_ORDER_GLIF_12345678_PROCESS" → extracts "12345678"

# Extract a 6-digit ID in brackets - the digit count is up to you
# Search Pattern: \(
\d{6}
# Example: "Active Directory (260051)" → extracts "260051"

# Extract IDs that are separated by a space, colon or hyphen
# Search Pattern: GLIF
\b\d{8}\b
# Example: "Order export GLIF 12345678" → extracts "12345678"
# \b does not apply next to underscores - use the pattern above for SAP_GLIF_12345678

# Extract only part of a match using a capture group
# Search Pattern: ExternalID=
[A-Z]{2,4}-(\d+)
# Example: "ExternalID=SYS-4711" → extracts "4711", not "SYS-4711"

# Extract a fixed-length ID that follows a label
# Search Pattern: InterfaceID:
\b.{9}\b
# Example: "...InterfaceID: 4711-1234" → extracts "4711-1234"
# A different length yields no value

# Extract a planning key that follows a label
# Search Pattern: Interface ID:
[A-Z]{2,4}-\d+
# Example: "Order export - Interface ID: WIB-6" → extracts "WIB-6"

# Extract a ticket key that is not always labelled
# Search Pattern: ^
[A-Z]{2,5}-\d+
# Example: "Jira #WIC-1456", "WIC-1257" and "for WIC-638" all yield the key

# Extract alphanumeric codes with prefix
# Search Pattern: ^
[A-Z]{2,4}-\d{4,8}
# Example: "Interface CRM-20240115 export" → extracts "CRM-20240115"

# Extract an ID at the end of the name
# Search Pattern: ^
\d+$
# Example: "TRUSTING@ALM_ALM_0090110740" → extracts "0090110740"

# Extract GUID patterns
# Search Pattern: ^
[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}
# Example: "Interface_a1b2c3d4-e5f6-47a8-9b0c-d1e2f3a4b5c6" → extracts the GUID

```
# Extract domain/business area from interface names
# Search Pattern: ^
(Finance|HR|Sales|Logistics|CRM|ERP)
# Example: "Finance_CustomerData_API" → extracts "Finance"

# Extract environment indicators
# Search Pattern: ^
(DEV|TEST|PROD|QAS|STAGING)
# Example: "SAP_CRM_PROD_Interface" → extracts "PROD"

# Extract version numbers
# Search Pattern: ^
(v?\d+\.\d+\.\d+)
# Example: "PaymentAPI_v2.1.3" → extracts "v2.1.3"
```

```
# Find the label that precedes the ID
GLIF
# Example: Matches "HR_GLIF_12345678", extraction continues after "GLIF"

# Find a label regardless of upper or lower case
(?i)GLIF
# Example: Matches "HR_GLIF_12345678" and "hr_glif_12345678"

# Find a marker used in descriptions
##
# Example: Matches "This is demo interface ##47111234"

# Find a labelled ticket or interface ID
Jira #
# Example: Matches "Order import (Jira #WIC-1456)"

# Find a label written with an equals sign
Cockpit ID=
# Example: Matches "Cockpit ID=IF-0815: order export"

# Search the whole text, without a label
^
# Example: Matches every interface, the extract pattern then searches the entire text

# Leaving the Search Pattern empty extracts nothing - always use ^ instead
```

• Syntax: Fieldname:Type:Subject

• Authentication Examples:

  • AuthenticationMethod:PROPERTY:BINDING → Extract the configured authentication method

  • AuthenticationMethod.Basic.Username:PROPERTY:BINDING → Extract basic auth username

  • AuthenticationMethod.X509.Keystore.View:PROPERTY:BINDING → Extract the certificate keystore view

• Proxy Configuration Examples:

  • ProxyHost:PROPERTY:BINDING → Extract proxy server hostname

  • ProxyPort:PROPERTY:BINDING → Extract proxy port number

  • ProxyUser:PROPERTY:BINDING → Extract proxy username

• Service Configuration Examples:

  • URLHost:PROPERTY:BINDING → Extract service endpoint hostname

  • URLPath:PROPERTY:BINDING → Extract service endpoint path

  • URLProtocol:PROPERTY:BINDING → Extract protocol (http/https)

  • URLPort:PROPERTY:BINDING → Extract service endpoint port

• Technical Configuration Examples:

  • TLSType:PROPERTY:BINDING → Extract the TLS type

  • InactivityTimeout:PROPERTY:BINDING → Extract timeout configuration

  • SERVICE_GROUP:PROPERTY:BINDING → Extract the service group

• Syntax: RFCDest:RFCType:Option

• RFCType restricts the rule to one kind of destination:
  ABAP, ABAP_DRIVER, ABAP_HTTP, EXTERNAL, INTERNAL, LOGICAL, QRFC, TCP_IP

• Connection Configuration Examples:

  • RFCDest:TCP_IP:GATEWAYHOST → Extract SAP Gateway hostname

  • RFCDest:TCP_IP:GATEWAYPORT → Extract the SAP Gateway service, for example sapgw00

  • RFCDest:ABAP:HOST → Extract SAP application server hostname

  • RFCDest:ABAP:SYSTEMID → Extract SAP system ID

  • RFCDest:EXTERNAL:PORT → Extract the connection port

  • RFCDest:ABAP:PATH → Extract the connection path

• Proxy Configuration Examples:

  • RFCDest:EXTERNAL:GATEWAYHOST → Extract the web proxy of an external destination

  • RFCDest:ABAP_HTTP:GATEWAYHOST → Extract the web proxy of an HTTP destination

• Authentication Examples:

  • RFCDest:EXTERNAL:USERNAME → Extract RFC connection username

  • RFCDest:ABAP:USER → Extract the connection user

  • RFCDest:ABAP:CLIENT → Extract SAP client number

• Technical Configuration Examples:

  • RFCDest:ABAP:SSL → Extract the SSL setting

  • RFCDest:EXTERNAL:WORKINGDIRECTORY → Extract the working directory

Syntax: EDIPHONE:FieldName

• Partner Identification Examples:

  • EDIPHONE:PartnerNumber → Extract the IDoc partner number, e.g. 0000004711

  • EDIPHONE:PartnerType → Extract the partner type, e.g. LI or LS

• Contact Detail Examples:

  • EDIPHONE:NAME → Extract the contact name stored in the partner profile

  • EDIPHONE:TEL_NUMBER → Extract the contact telephone number

  • EDIPHONE:COMPANY → Extract the company / organization

EDIPHONE refers to the EDI phone/fax details of the IDoc partner profile in SAP (WE20). PartnerNumber and PartnerType identify the partner, typically the logical system, while NAME, TEL_NUMBER and COMPANY contain the associated contact details. Use PartnerNumber for an ID property. Field names are case-sensitive and must be written exactly as shown above.

In the Interfaces context, all five fields are available and both inbound and outbound partner profiles are evaluated. In the Systems context, only NAME, TEL_NUMBER and COMPANY are available. PartnerNumber and PartnerType identify the partner from which the system is created and are not available as system properties. Use one rule per field, as a second rule for the same field replaces the first.

For SAP Cloud Integration interfaces, values can be read from externalized iFlow parameters maintained in the Configure view:

• Syntax: Configuration:ParameterName

• Connection Configuration Examples:

  • Configuration:LocationID → Extract the Cloud Connector location ID

  • Configuration:Address → Extract the endpoint address

  • Configuration:ProxyType → Extract the proxy type

• Technical Configuration Examples:

  • Configuration:Timeout → Extract the timeout configuration

  • Configuration:Credential Name → Extract the referenced credential

---

Values can also be read from custom tags defined on the Integration Package:

• Syntax: Package:Tag:TagName (System properties only)

  • Package:Tag:SystemID → Extract the value of the SystemID custom package tag and map it to a system property (e.g. System ID Harmonized)

This is useful for consistent system assignment across all interfaces in a package. The tag must exist on the package, and the tag name is case-sensitive.

For planned interfaces, values are read from the connected planning tool. Available fields depend on the source tool.

• Jira: Key, Title, Status, Due Date, Description, Assigned To, Label(s), Parent, Type, ID, Created, Changed, Confluence

• Azure DevOps: Parent (other work item fields are currently not available)

• SAP Integration Assessment: Interface Request, Interface Request Status, Interface Request Style, Business Solution Request, Domain, Selected Technology 1, Selected Technologies Coverage 1 (continues with 2, 3, etc. for additional technologies)

• Syntax: Metadata:FieldName

• Examples:

  • Metadata:Key → Extract the planning ID (e.g. into Global Interface ID)

  • Metadata:Due Date → Extract the planned date (e.g. into Go-Live Date)

  • Metadata:Status → Extract the project status (e.g. into Project Status)

  • Metadata:Domain → Extract the business domain (SAP Integration Assessment)

For resources, values can be read from the Security Material of the SAP Cloud Integration tenant:

• Syntax: USER:FieldName

  • USER:Username → Extract the user name stored in the credential

  • USER:Name → Extract the name of the credential artifact

  • USER:Description → Extract the description

  • USER:DeployedBy → Extract who deployed the credential

Values can also be read from SAP BTP destinations. This requires a BTP data source with the Destination product enabled:

• Syntax: BTPDestination:FieldName

• Authentication Examples:

  • BTPDestination:AuthenticationUser → Extract the configured user

  • BTPDestination:AuthenticationType → Extract the authentication method (e.g. BasicAuthentication, CONFIGURED_USER, NoAuthentication)

• Connection Configuration Examples:

  • BTPDestination:URLHTTP → Extract the destination URL

  • BTPDestination:HostRfc → Extract the RFC host

You can also write an authentication method instead of a field name to read the user only for destinations using it, for example BTPDestination:CONFIGURED_USER.

In the Systems context, values can be read from the metadata delivered by your EAM tool (LeanIX, Luy, Bee360).

• Syntax: Metadata:FieldName

  • Metadata:Name → Extract the system name (e.g. into System ID Harmonized)

  • Metadata:App owner → Extract the application owner (e.g. into System Owner)

  • Metadata:ID → Extract the external system ID (e.g. into Fact Sheet ID (LeanIX))

  • Metadata:Type → Extract the system type (e.g. into Fact Sheet Type (LeanIX))

Field names come from your EAM tool, so the available names depend on which fields you expose there.