Best SAP Excel Add-ins Compared for Posting, Reporting and Planning

1. PostNow.ai: the SAP Excel add-in for posting and reporting

PostNow.ai is an SAP Excel add-in that posts to SAP and reads from it in the same workbook, on ECC and S/4HANA. A designer maps a template once to a BAPI or a recorded transaction. Operators fill rows, Validate, Simulate and Run, and SAP's document number or message lands beside each row, under the user's own SAP login.

The ribbon, dialogs and Run Log reasons are available in English, German and French.

Posting through a BAPI or a recorded transaction

Posting through a BAPI or a recorded transaction is a choice the designer makes per template, and both run SAP's own business logic. The BAPI vs BDC guide explains the trade-off; this is the short version.

1. Pick the route. Take the BAPI where one covers your fields: BAPI_PO_CREATE1 for purchase orders, BAPI_INCOMINGINVOICE_CREATE for MIRO invoices, BAPI_MATERIAL_SAVEDATA for materials. Record the transaction where a field exists only on a screen. The BDC recording guide covers recordings that replay reliably.
2. Map and set field rules. Drag Excel columns onto BAPI or screen fields, or use Auto Map; for BAPIs, Mapping AI proposes matches from a sample file's column headers only. X structures such as POITEMX are filled for you. Each field can carry leading zeros, a date format, a default and an allow-list.
3. Decide the document shape. H/D marker column or flat rows with a split column. Recordings can also carry conditional blocks that process a screen only when a column has a value.
4. Prove it, then publish. Simulate and a pilot of ten rows in a test client. Publish produces a workbook that is run-only for everyone, designers included, or puts the template in the portal's central library.

BAPI posting uses standard function modules over RFC. Recorded templates run through PostNow.ai's ZPOSTNOW_* recording objects, and reports and Mass Change downloads use the read-check function module ZPOSTNOW_READ_JOIN. Basis imports those objects once per system, like any other Z transport.

Reporting and export to Excel

Reporting and export to Excel in PostNow.ai produce a formatted workbook rather than a raw dump. A report downloads as Data only (a formatted table with a run header of report, SAP system, user, run time and filters), Data + Analytics (adds a dashboard sheet with KPI tiles and native Excel charts) or Data + Analytics + Pivot (adds a PivotTable and PivotChart with slicers). The export SAP data to Excel guide compares this with ALV export, SE16N and SAP Query.

The walkthrough above maps an FB50 journal to BAPI_ACC_DOCUMENT_POST, validates the rows, posts them and reads the document numbers back into the workbook.

Designer and operator roles, approvals and audit in PostNow.ai

PostNow.ai separates the person who builds a template from the people who run it, can hold a Run until someone else approves the exact data, and records every outcome in the workbook, the portal and SAP. The role split is enforced in the ribbon.

Designer and operator roles

• Designers record transactions, map BAPIs, set field rules, loops and conditions, build chains and SAP queries, and publish. AI Query Pilot, which turns a plain-English question into a query, is a designer tool.
• Operators get a run-only ribbon: open a published workbook or a library template, fill rows, Validate, Simulate if allowed, Run, Retry Failed, and run reports from the Report Library, My Reports and Team Reports. Authoring stays with designers.
• Per-user switches in the portal turn Reports, Posting, Mass Change, Debug, Schedule and Simulate on or off for each person, whatever their role.

Approvals and audit trail

• Approvals. When an approval policy in the portal covers a template, the operator submits the rows for review and the approver sees them as a grid in the portal. The approval is tied to a SHA-256 fingerprint of the data, so editing a cell after approval starts a new request. Submitter and approver are always two different people.
• Run Log in the workbook. Each row keeps SAP's message, the document number and the SAP user, time and system that posted it.
• Central Posting Audit. Every run's per-document outcome (transaction, template, SAP system, client and user, success or message, document number) goes to the portal, and a local bdc_audit.csv is kept on the PC.
• SAP's own trail. Because posting goes through BAPIs and CALL TRANSACTION, SAP writes its usual change documents and document headers under the person who posted.

For how teams organise templates, libraries and handovers around these roles, see Excel to SAP automation.

How to choose an SAP Excel add-in by job

Choose an SAP Excel add-in by the job your team does every week: post data into SAP, analyse SAP data, or plan. PostNow.ai covers posting into ECC and S/4HANA plus operational reports; SAP's analytics add-ins cover BW, HANA and SAP Analytics Cloud; the IBP add-in covers supply planning. Many companies run two of them side by side.

For posting, also compare the add-in against SAP's own upload routes in the SAP mass upload guide, which lists the BAPI or transaction to use object by object.

Checklist before the first PostNow.ai user goes live

PostNow.ai inherits every SAP authorisation decision you make, so most of this list is SAP work: named users, transports, RFC and table authorisations, the RFC SDK on each PC and approval policies. Tick each item in every system from development to production.

• Named users only. Have two users with different company codes run the same report. If they see the same rows, a shared account is in use.
• Transport imported in every system: the ZPOSTNOW_* objects for recordings and ZPOSTNOW_READ_JOIN for reads.
• S_RFC scoped to named function groups.
• S_TABU_NAM preferred over broad S_TABU_DIS groups. Anything a user can show in SE16 they can also pull into Excel.
• Tables without org fields reviewed. Vendor and customer master tables such as LFA1, LFBK and KNA1 carry none of the organisational fields, so table-level authorisation is the control that applies.
• RFC SDK on every PC at C:\SAP\nwrfcsdk, or the path passed to the MSI.
• Scripting decision made for designers who record, users who run recorded templates, Debug or open documents, and testers with SAP GUI steps.
• Approval policies set for the templates that need a second pair of eyes, before operators get the Posting switch.
• S/4HANA objects re-tested. In S/4HANA, XK01 and XD01 redirect to transaction BP, so rebuild vendor and customer templates on the business partner and re-test them in an S/4HANA quality system.