📢 🚀 Latest release provides a Cloud Run Job that Agentifies attachments stored in the Content Repository by synchronizing Repository data to Vertex AI Data Store. With a single click you can link the Data store with Google Cloud Agentspace for a seamless search experience of your enterprise data
📢 🚀Annoucing the GA version of the Content Server Solution - Released as part of ABAP SDK V1.10, which replaces this sample solution
IMPORTANT: If you are already using the solution from this repo then refer to the migration guide 📖 to learn more: Migrate from Open Source to GA version available with ABAP SDK V1.10This repo remains as a reference if you are an existing user or want to experiment by adding your own customizations. The standalone Archive to BigQuery feature is also only avaialable in this repo.
📢 🚀Annoucing Archive to BigQuery feature, powered by BigQuery Toolkit for SAP
Important
With the release of the ABAP SDK for Google Cloud V1.10 the solution contained in this repository is no more required to implement Google Cloud Storage as Content Server .
Google Cloud Storage as Content Server can be directly implemented using the Handler Class for the SICF node shipped implicitly with the ABAP SDK for Google Cloud V1.10
Most importantly, if you are using the solution from this repository you can consider moving to the GA solution available in the ABAP SDK. Please refer to the migration guide for for more info: Migration Guide
This repository will still be kept alive for documentation purposes.
This solution utilizes Google Cloud Storage as a content repository to store SAP attachments and archive the data
This solution is built on top of ABAP SDK for Google Cloud. Therefore your SAP system should have the latest version of the SDK (Version 1.7 or later) installed to proceed ahead. All the required configuration for the SDK to connect to Google Cloud APIs should be set-up following the SDK’s authentication guide.
On your Google Cloud project enable the Google Cloud storage API and set up a bucket with nearline storage.
Note : The Service Account that you have configured in the Client Key configuration should have the IAM roles Storage Object Creator roles/storage.objectCreator and Storage Admin roles/storage.admin
Step 1: Follow the Release Instructions to import the solution into your SAP system.
Step 2: Create a background user (user id: ARCHIVEUSER) to invoke the SICF HTTP Handler class during runtime.
Step 3: Create SICF Node for ArchiveLink
Step 4: Configure the SICF node
- Configure the user created in the SICF node along with password
- Mark procedure as “Required with Logon Data”
Step 5: Configure the HTTP handler Class
Configure the HTTP handler class that is provide with this repository: ZGOOG_CL_CONTENT_REPO_GCS
Step 6: Setup content server for Cloud Storage
Go to transaction OAC0 and create an entry for a new content server.
Step 7: Link Business Object with Content Repository
- Go to TCode
OAC3to setup your business object to be stored in GCS through the Archivelink content repository setup done above, - Here is an example to save Purchase Orders.
Step 8: Configure Google Cloud Content Server for SAP
Configure below in table ZGOOG_CONT_REPO provided with this repository by going to transaction SM30
- Content repository created in SAP
- ABAP SDK for Google Cloud Client Key.
- Google Cloud Storage repository name, where you want to store/archive SAP content.
You are now all set to start using Google Cloud Storage as Content Server.!!
The new BigQuery Toolkit for SAP lets you archive SAP table data directly into BigQuery. Query archived data using familiar SE16/N-like functionality within BigQuery Studio and Looker, and leverage BigQuery ML to unlock powerful insights.
- Install and configure the latest (V1.9 or above) version of ABAP SDK for Google Cloud
- Configure BigQuery Toolkit for SAP. Make a note of Data Transfer Key configured in Tcode
/GOOG/BQTR_SETTINGS - Configure entries in table
ZGOOG_ARCH_BQusing SM30Column Value Archiving Object Name of the archiving object for which the data should be replicated to BigQuery Data Transfer Key BigQuery Data Transfer Key from Tcode /GOOG/BQTR_SETTINGSIs Setting Active Flag Enabling this write archive data to BigQuery - When you run the Archive Delete Program, the implementation
ZGOOG_BADI_ARC_WRITE_TO_BQof BADI definitionARC_DEL_FINISHEDwill automatically send the archive data to BigQuery. - Alternatively, you can also use program
ZGOOG_R_BQ_WRITE_ARCHIVE_DATAto manually select and write archive data to BigQuery.
Note
BADI ARC_DEL_FINISHED is only available in systems with SAP_BASIS component 740 and above.
Refer to note 3063034 for more details.
If your system is not compatible, you can exclude the implementation ZGOOG_BADI_ARC_WRITE_TO_BQ when importing.
To learn more, you can watch the following YouTube Videos:
Tip
You can also read more on how to archive data to Cloud Storage with Archive Administration Transaction SARA in the Medium blog Archive your SAP Data to Google’s Cloud Storage
Happy Learning!!










