Fellow Vector

Yes, we grant every organisation a 30-day free trial. Head over to our licensing portal, Fellow Marble, and create your account.

Follow the steps to create your user and organisation, then head over to the License Store to "purchase" your trial. Then head over to the main page where you can select Vector and claim the trial as your user license. This is also where you can download Fellow Vector.

Fellow Vector is Windows only and requires at least windows 7 to operate.

Fellow Vector is natively compatibale with on-prem SAP systems as they come by default with RFC (Remote Function Call) functionality.

SAP has made mention of a RFC adapter for SAP Cloud, however we have not yet had the opportunity to test.

After installing Fellow Vector you can start playing around immediately. Manually connect to a SAP system and start exporting to CSV.

However, to make your experience better we would suggest installing the following applications:

• SAP Logon: this will allow you to register your SAP systems in SAP Logon and use them directly in Vector
• Microsoft SQL Server: using SQL will unlock a lot of additional features of Vector that make life much easier (SQL filtering, automatic horizontal segment merging, etc.). We suggest you start with the MS SQL Server Express edition on your local device.

Yes, we would suggest you use your QA or Pre-Prod environment first to test the effects of Vector on your system.

We have extensively tested the performance impact of Fellow Vector on multiple SAP systems and found it to be of minimal impact. However, each SAP system is different so we highly encourage you to perform your own performance testing before using Vector in production.

Definitely not! Fellow Vector ONLY uses read functions from the RFC library.

Not by default. In the settinngs page of Fellow Vector we offer two standard RFC functions to fetch your data.

We offer a custom Z function to catch a specific scenario where the standard "BBP_RFC_READ_TABLE" RFC function returns duplicate rows. By default this function does not exist in SAP. To fix the duplicate issue, the SAP team should create a duplicate of the "BBP_RFC_READ_TABLE" function, name it "ZBBP_RFC_READ_TABLE" and have them add "ORDER BY PRIMARY KEY" as a sorting clause.

This is an important one! Your SAP user determines if you have access to the data you wish to extract and the RFC functionalities of SAP.

Your user should have the following "DISPLAY ONLY" access rights:

• Authorization Object S_RFC:
  • RFC_TYPE: FUGR
  • RFC_NAME: *
  • ACTVT: Activity 16 (Execute)
• Authorization Object S_TABU_DIS:
  • DICBERCLS: *
  • ACTVT: Activity 03 (Display Table Content)
• We also suggest you request access to SE16(N) to validate table row counts after extraction for completeness sake.

Sure you can, we offer three options in the settings menu to pseudonomyze your data:

• No Secret: no salt is added to the pseudonomyzed fields. This means values will be consistently hashed to the same output on each instance of Fellow Vector. This is considered the least strong level of pseudonymization.
• System Secret: fields are hashed using a salt for your specific PC. This means scrambling of a value remains consistent between extractions on your device. Use this if:
  • - you wish to always get the same scrambled values accross extractions and your device is the only one that exports the data
  • - you just need consistent scrambling during an extraction, but it not required that values stay consistent through follow-up extractions
• Domain Secret: fields are hashed using a salt for the domain your PC belongs to. This means scrambling of a value remains consistent between extractions on device that belong the same PC domain. Use this if you wish to always get the same scrambled values accross extractions and devices that belong to the same domain as your PC
• Custom Secret: fields are hashed using your custom salt. This means you can control scrambling of a value based on your needs:
  • - you wish to have control over a project-by-project pseudonyzation of field. Some might require a cross-extraction consistent key and some a per extraction basis key.
  • - you just need consistent scrambling during extractions, but you use multiple devices that do not belong to a single domain (e.g. client extractions in combination with consultant extractions)


You can set fields for pseudonymization in the extraction builder by clicking the "eye" icon next to the field name. Alternatively, you can build an custom XML extraction file and add the required fields to the pseudonymize tag.

After installing Vector, perform the following steps:

• If not yet done, sign in with your Fellow Marble account
• Connect to a SAP system
• When exporting to a local or Azure SQL, connect to the instance. For CSV, select an output directory
• From the two options, select New Table
• Provide the table name your wish to extract (e.g. T001)
• Select the list of fields you are interested in
• If you wish to pseudonymise any field, click the "eye" icon next to the field name
• If you wish to use a slicer, provide the field and slicing values
• If you wish to use a filter, provide the filter details
• Click the little floppy disk icon to Save
• You can add more tables if you with or export this extraction to XML so you can reuse it later on
• Switch the mode on top from Prepare to Extract
• Click the play button to start extracting

After installing Vector, perform the following steps:

• If not yet done, sign in with your Fellow Marble account
• Connect to a SAP system
• When exporting to a local or Azure SQL, connect to the instance. For CSV, select an output directory
• From the two options, either select New Table to build a new list of tables to export or select Upload Profile if you have already built your list
• Once you have a list of tables ready, feel free to make adjustments by clicking on the table name
• Click the little floppy disk icon to Save any changes in the editor
• You can add more tables if you with or export this extraction to XML so you can reuse it later on
• Switch the mode on top from Prepare to Extract
• Click the play button to start extracting

In the settings screen, we offer a custom Z function to catch a specific scenario where the standard "BBP_RFC_READ_TABLE" RFC function returns duplicate rows. By default this function does not exist in SAP. To fix the duplicate issue, the SAP team should create a duplicate of the "BBP_RFC_READ_TABLE" function, name it "ZBBP_RFC_READ_TABLE" and add "ORDER BY PRIMARY KEY" as a sorting clause.

Then simply switch to using the "ZBBP_RFC_READ_TABLE" function for your extraction and all should be well.