• Commento ufficiale

  

  Abby Steere

  • 6 agosto 2025 18:50

  If you missed the live session, here is a recap of some of the questions we discussed! 

  • Question: Can you speak to how the client generated the extract from SAP and what middleware process was used to drop the file in SFTP? Additionally, did the client face any challenges with hierarchy formatting, given SAP can use a tree structure?
  • Answer: The generation of the extract from SAP and the middleware process used to drop the file in the SFTP server were outside the Workiva ecosystem. Generally, scripting tools are used for this. Regarding hierarchy formatting, the client did face challenges due to SAP's tree or parent-child hierarchy structure. A custom query was built to navigate and flatten this hierarchy for roll-ups.

   

  • Question: Why did you not use SAP S/4HANA, which would have better user interfacing and controls over consolidation steps?
  • Answer: Using an SFTP server was a security decision by the client, who was not comfortable with a direct integration to their SAP system. This intermediary step also gave them more control over data reconciliation, ensuring data was in its final state before being loaded into Workiva.

   

  • Question: Can you speak more on how you moved the decrypted data from the one chain to multiple workspaces using API grants?
  • Answer: Within a single workspace, multiple Workiva connectors were created, each configured with the client ID and secret of a different target workspace. Data extraction and decryption happened in one integration and chains environment. The "load data to Wdata template" was then leveraged with the specific Workiva connector for each target workspace to land the decrypted data.

   

  • Question: How did you ensure the completeness and accuracy of the data to ensure end users could be comfortable with the end result? What checks were put in place? Any challenges you faced?
  • Answer: The team worked with the client on data reconciliation using formulas to ensure consistency between adjustments and source system information. Validation steps were not built into Workiva chains as the client had their own tools within the formulas side of the platform for this purpose.

   

  • Question: Did a Workiva query flatten the parent-child hierarchy, or did the logic just navigate the hierarchy to produce the correct mapped output?
  • Answer: A Workiva query was used to navigate the hierarchy and produce a trial balance data output that made sense. It can repeat rows for each parent hierarchy an account belongs to, mapping a root-level general ledger account to every level of the hierarchy within the query output, using the SAP mapping file.

   

  • Question: Can you show the configuration of the connectors, and can you share these workflows with folks?
  • Answer: The actual configuration of individual connectors cannot be shown, but information on how to set up a Workiva connector (which involves configuring it with the target workspace's client ID and secret) can be shared. The workflows are templatized and can likely be shared.

   

  • Question: How long was the implementation, and were there any other connectors used that we haven't talked about already?
  • Answer: The implementation was approximately 8 to 9 months, a comprehensive and iterative process. Handlebars was also used for notifications, dynamically providing information on chain errors or successes via email.

   

  • Question: What was the process of enabling the customers, what was provided, things like that, or the plan in a little bit more detail?
  • Answer: The enablement process takes a slow approach, starting with sessions on Wdata tables and queries tailored to their use case. This includes showing them how their specific tables and queries are built. Then, they slowly navigate into the chains workspace, with a focus on detailed chain descriptions for each node to clearly explain what is occurring (e.g., "This is converting your control sheet data to CSV format for filtering purposes").

   

  • Question: Were you maintaining Wdata tables in each workspace for imported data? If yes, then how were you referring to them in a central workspace?
  • Answer: Wdata tables did exist within each target workspace. They were referenced by their specific table IDs, as long as the Workiva connector used had an API grant associated with that workspace.

   

  • Question: If all the files were pulled from SFTP for multiple workspaces, did it not slow down the process to import the data in Wdata tables, since it would be iterating through all the files present in SFTP? If you faced this issue, how did you overcome it?
  • Answer: The typical approach is to avoid iterating through all files in an SFTP in one command. Instead, an identifier is used within the List Directory command (e.g., regular expression) to look for a specific file (e.g., "File X") and download only that one to the target table. This prevents slowdowns from processing all files.

   

  • Question: What would be the complexity to establish an SAP S/4HANA connection, disregarding SFTP?
  • Answer: The complexity largely depends on having a team with a strong understanding of their SAP S/4HANA source system. If there is a great understanding and a good administrator for the source system, it will be easier to integrate with Workiva.

   

  • Question: Can clients run financial statements for multiple entities concurrently?
  • Answer: Yes, the solution allowed for this. Clients could have a financial statement for each individual entity, using one query per entity. The query could specify the needed entity from the transactions table, enabling a scalable solution for adding more entities.

   

  • Question: How do you write complex SQL in Wdata? What Workiva support do we have to write complex SQL (e.g., DECLARE/SET SQL statement has error, Query not valid)?
  • Answer: Within the query builder tool, there is an "advanced SQL mode" that allows for more statements not typically supported by the standard query builder. Presto SQL syntax is supported, and documentation links for valid syntax are available. Workiva can provide assistance if there is an engagement, but there isn't specific support for learning or writing advanced SQL outside of that.

   

  • Question: How to target a specific file in SFTP dynamically?
  • Answer: When executing a list directory command, you can specify the exact file using a regular expression. The recommendation is to pass this data via a control sheet, so the list directory command looks for a particular file matching the identifier passed in. The output of this command is then used in the download file command. This would be a good topic for a future hands-on workshop.

   

  • Question: Can the same Workiva chain be used to run reports for multiple entities in parallel based on their individual reporting schedules?
  • Answer: Yes, it is possible. Implementations have been built with different reporting schedules that can be dynamically tailored to consider blackout periods or different fiscal year-ends. This involves advanced chain building and setting up a control sheet to determine if a chain should run during a specific fiscal period.

   

  • Question: Did you have multiple list directory commands looking for specific named files?
  • Answer: Multiple chains would run concurrently. The list file command would be a sub-chain of a top-level chain, passing a particular field into the sub-chain and then executing a list directory command within it. These commands operate concurrently in a parallel process to ingest a large volume of files simultaneously. So, while technically it's the same command, it's executing multiple times concurrently.

   

  • Question: What is the requirement needed to establish SFTP connection? Is it just Whitelist domain and open port?
  • Answer: The basic requirements for an SFTP connection are the host, port, username, and password. Additionally, if a private key is required to access the SFTP, that can also be configured within the connector.

   

  • Question: Did you use a ground runner at all?
  • Answer: No, a ground runner was not used. This implementation leveraged a cloud runner because their system was not on-premise, allowing access to the SFTP server via the cloud runner.

   

  • Question: Can we upload Excel files directly to Workiva as a spreadsheet without having to pass through Wdata? For example, if I want to upload it only for an approval process, no modification needed.
  • Answer: Yes, it is possible to import spreadsheets directly into the Workiva platform. There is also a legacy functionality called Wdesk Sync that allows syncing an Excel spreadsheet directly into a Workiva spreadsheet.

   

Accedi per aggiungere un commento.