FB01 Mass Upload: Post SAP Documents with Posting Keys from Excel

The posting key is the instruction

In PostNow.ai's FB01 template the posting key is carried by the line's table and the amount's sign; on the FB01 screen you type it. Either way it decides three things, as SAP's own definition puts it: the account type of the line, debit or credit, and which fields the line accepts. These are the keys of the standard system; your FI team can define more in OB41.

Why a wrong key is worse than a wrong amount. A wrong amount usually breaks the balance and SAP stops the document. Swap 40 and 50 on two G/L lines of the same value and the document still balances: it posts, and both accounts move the wrong way. The same trap sits in a signed amount column, where a lost minus sign flips a line. Review one posted document per key pattern in FB03 after the first run, and compare debit and credit totals separately, not only the net.

The FB01 header: company code, dates and any document type

A PostNow.ai FB01 template puts the header on the H row: company code, document date, posting date, document type, currency, reference and header text, mapped to DOCUMENTHEADER with business transaction RFBU. FB01 lets you choose the document type, and that choice has consequences.

• The document type limits the account types. Each document type allows a set of account types (customer, vendor, G/L, asset, material), maintained in OBA7. A vendor line in a document type that allows only G/L accounts stops with F5 243 "Account type … is not defined for document type …", however correct the keys are.
• The document type picks the number range. The posted document takes its number from the range assigned to its type, so documents of different types can land in different ranges. Ask FI which type they want for each kind of posting before the template is published.
• The period must be open for every account type in the document. OB52 opens periods by account type, with + for all. A document with G/L and vendor lines needs both open on its posting date.
• One currency per document. The currency sits on the H row and is sent with every line's amount.

Mixed G/L, vendor and customer lines in one document

PostNow.ai sends a mixed FB01 document as one BAPI call, and SAP either posts all its lines under one document number or none. This is the case FB01 exists for: a recharge that bills a customer and books revenue, a vendor rebate offset against cost, or a netting of a customer and a vendor that are the same business partner. The mapping decides which table each row lands in, so lay the template out so that a G/L row fills only ACCOUNTGL, a vendor row only ACCOUNTPAYABLE and a customer row only ACCOUNTRECEIVABLE.

• Give each table its own columns. PostNow.ai builds a line in a table from every row in which a cell mapped to that table holds a value. One shared item text or assignment column mapped to ACCOUNTGL would therefore add a G/L line to any vendor or customer row where it holds a value. Map item number, assignment and text once per table and fill them only on that table's rows; the item number for CURRENCYAMOUNT is filled on every row.
• Prove each document pattern first. Simulate one document of every pattern the file contains, then post those few in a test client and open them in FB03 to check every line sits on the intended account and side, before the whole file runs.
• Give vendor and customer lines their own terms. Payment terms and baseline date sit on the sub-ledger line (PMNTTRMS, BLINE_DATE), not on the header. Map them wherever the file's terms differ from the vendor or customer master record.
• Keep CO objects on G/L lines. A cost center or order belongs on the expense or revenue line; vendor and customer lines post to their reconciliation account and take no cost center.
• Put the same reference everywhere it is searched. The header reference and each sub-ledger line's assignment field are what AP and AR use to find and clear these items later.
• Check the zero sum per document before Simulate. A SUMIF on Document Ref over the signed amount column must return 0.00 for every document, counting G/L, vendor and customer lines together.
• Stay under 999 lines per document. Above that SAP stops with F5 727 "Maximum number of items in FI reached".

Recording FB01 screens (SHDB)

PostNow.ai can post FB01 from a recording when the document must carry the keys from your file as typed: own posting keys, special G/L types the BAPI refuses, or a team that wants the screen logic. FB01 runs on classic screens of program SAPMF05A, which batch input handles well, and PostNow.ai's Simulate presses FB01's own Simulate function in place of Save. PostNow.ai logs in to SAP GUI only on the user's own computer, with the user's own stored login, when the user starts the action (Record, Run, Debug or Call Transaction); never on a server, never unattended.

• The next line is keyed on the current screen. The first screen (0100) holds the header plus the first line's posting key and account (RF05A-NEWBS, RF05A-NEWKO). Each line screen (0300 for a G/L line, with other screens for vendor and customer lines) holds that line's amount and, at the bottom, the key and account of the line after it.
• Lay out the sheet to match. The recorded line block repeats once per detail row, so each D row needs its own amount and the next row's key and account. Two helper columns that read the row below do this; leave them empty on the last line so Save follows.
• The key decides the next screen. A vendor line opens a different screen from a G/L line, and a cost center can open a coding block popup. Record one document with every line type the file will contain, in the order the file uses, and keep every document in the file to that same sequence; a different pattern needs its own recording.
• Prove the loop with Debug. Debug replays the recording in the foreground so you can watch a two-line and a five-line document go through before the first Simulate of the whole file.

Recording rules, OK-codes and loops are in the SAP BDC recording guide. For multi-line documents in standard keys, the BAPI route above needs no screen sequence at all, which is why PostNow.ai's FB01 template uses it.

Reverse FB01 documents: FB08, F.80 or a reversal file

PostNow.ai reverses posted documents in bulk with a second template, one row per document with its reversal reason and reversal posting date: the free FB08 reversal template on BAPI_ACC_DOCUMENT_REV_POST, or a recording of FB08 with document number, company code and fiscal year as columns. In SAP itself, FB08 reverses one document at a time and F.80 reverses a selection of documents in one run.

• The reversal BAPI needs the object key, not the document number. For documents posted through BAPI_ACC_DOCUMENT_POST that is object type BKPFF and the 18-character OBJ_KEY returned at posting; map $OBJ_KEY to a result column when you post.
• Prove the route on a few documents first. SAP Community answers differ on whether BAPI_ACC_DOCUMENT_REV_POST accepts BKPFF documents; some report RW messages such as "Reversal in component Financial Accounting not possible". Reverse three documents in a test client and check them in FB03; if SAP refuses them, the FB08 recording or F.80 does the same job.
• Cleared lines stop a reversal. Once a vendor or customer line from the document has been cleared, SAP refuses the reversal with "Document already contains cleared items - reversal not possible" until the clearing is reset (FBRA).
• A correction document mirrors the keys. Where FB08 cannot apply, for a partial correction or a shape change, post a new FB01 document whose lines flip each key (40 becomes 50, 31 becomes 21) on the same accounts, and carry the original document number in the reference so the two can be found together.

FB01 in S/4HANA

PostNow.ai uses the same FB01 template on S/4HANA: FB01 and BAPI_ACC_DOCUMENT_POST are both there, and the posted document lands in the Universal Journal. What changes is mostly what your configuration makes mandatory.

• One line item table. The universal journal entry replaces the separate FI and CO documents, and its line items are written to table ACDOCA (SAP Help). FB03 shows the document as before.
• Customers and vendors are business partners. The customer and vendor numbers in the file are the ones CVI keeps in sync with each business partner; a partner without the customer or vendor role has no account to post to.
• Profit center and segment. Many S/4HANA systems require a profit center on every G/L line, and the segment is usually derived from it. Add the profit center column even where ECC did not ask for it.
• Asset lines bring Asset Accounting's checks. An FB01 line with key 70 or 75 posts through the new asset accounting logic, with its own FAA_POST messages, for example on the technical clearing account. Prove asset lines on Simulate with your asset accountant; the assets themselves are created first, as in mass create assets in SAP (AS01).
• API mode. PostNow.ai can also post through SAP's SOAP service Journal Entry - Post (Synchronous) (JournalEntryCreateRequestConfirmation_In), which takes G/L, customer (debtor) and supplier (creditor) items, with a test-run flag for Simulate. Each item carries a debit/credit code that must match the amount's sign. SAP Help documents it for S/4HANA Cloud under communication scenario SAP_COM_0002; on premise, Basis exposes it in SOAMANAGER.

What to plan for in an FB01 mass upload

PostNow.ai posts through SAP's accounting BAPI, so SAP's own posting key, account type, period and field status checks decide every result.

• Run SAP's checks in Simulate. Validate checks formats, lengths and allowed values in Excel; balance, account type, period and field status checks start when SAP sees the document in Simulate.
• Review the sides after the first run. A swapped key or a lost minus sign posts cleanly when the document still balances. Open one posted document per key pattern in FB03 and compare debit and credit totals with the source separately.
• Keep re-runs in the same workbook. The re-post check reads this sheet's Run Log. A copied file with the same documents has no Run Log, so look the references up in the GL Line Items 360 report before posting it.
• Check UNKNOWN rows in SAP first. Look the reference up in FB03; post the row again only if the document is not there.
• Keep the PostNow.ai portal reachable on approval-controlled runs. When an approval policy covers the template, Run waits for an approver to approve that exact data, and the submitter cannot approve their own run. The check asks the portal at Run; if the portal cannot be reached, the run goes ahead without the approval step.

Making a template like this repeatable for a team (designers who build, operators who only run, a published template in the central library) is covered in Excel to SAP automation.

Frequently asked questions