Prerequisites & Access

What must be in place in the SAP system and in BTP before the first retrieval can run.

In the SAP system

PrerequisiteWhyVerification
Release ≥ 2302 (on-premise or private cloud)The Contract Accounting APIs that deliver the open item are available as of this release.System status
OData services active (/IWFND/MAINT_SERVICE): API_BUSINESS_PARTNER, CONTRACTACCOUNT_0001, CADOCUMENTMANAGE_0001, API_CABUSPARTINVOICE_0002, API_CABUSPARTPAYMENT_0002, CADUNNING_0001The six sources.$metadata reachable for each service
Technical user, read-onlyThe document and payment APIs could write. The user must not — display authorization for FI-CA documents, contract account, and business partner; no create, no change.POST to a service → 403
CDS view for installment payments with OData releaseThere is no standard API for future installments (see the CDS View page).Service in the catalog
QA system with the same servicesDevelopment and testing are done against QA, never against production.Access via a second destination

In SAP BTP

The Cloud Connector opens the system into BTP. A collector outside of BTP therefore needs a facade:

Which option is chosen is answered in the "System & Access" questionnaire; the rest of the setup is the same for both options.

Credentials

Credentials, certificates, and keys are never transmitted via the questionnaires or email. Bilendo provides a separate, secure channel; the IMS contains only the names of the secrets.