- Home
- Modules
- SAP SD
SAP SD: from the sales order to the cash
Sales and Distribution, explained for users and for consultants from other modules.
12345Harbor Foods Ltd · Sold-to 10023010 · TAN · 40 CS2,800.0020 · TAN · 25 CS1,950.00Net valueUSD 4,750.00VA03- Standard order
12345Completed - Outbound delivery
80004711Completed - Goods issue
4900021337Completed - Invoice
90003520Completed - Journal entry
9400000917Not cleared
Overview
What SD is, if you have never worked with it
SAP SD, Sales and Distribution, is the part of SAP that runs the sell side of a company. It records what the customer asked for, works out the price and the tax, checks stock and credit, ships the goods and issues the invoice. In SAP S/4HANA, SAP’s courses call the area simply Sales, but transactions, tables and almost everyone on a project still say SD.
This page is for the people who work around SD without being SD consultants: key users in sales, shipping and billing, and FI, CO, MM or tax consultants who keep meeting SD documents. It follows one order from the customer to the cash, shows what each step posts in the books and lists the transactions worth knowing.
- SAP ECC 6
- SAP S/4HANA
- SAP S/4HANA Cloud
VA01VL01NVF01Use the User | Consultant switch at the top of the page to show or hide the technical layer: Customizing transactions, tables and the settings behind each step.
The sell side of SAP
SD covers the order-to-cash cycle: quotation, order, delivery, invoice and, through FI, the payment. SAP’s own best-practice version of the classic flow is scope item BD9, Sell from Stock.
Source: SAP Learning, sell from stockShipping is shared with LE
Deliveries, picking and goods issue belong technically to Logistics Execution (LE), but users see them as part of SD. In SAP’s R/2 system, launched in 1979, a single module called RV covered both.
Source: Wikipedia, SAP R/2Every invoice is an FI posting
Saving a billing document creates the journal entry for receivables, revenue and tax, with revenue accounts found by the same condition technique SD uses for prices. That is why FI and CO consultants meet SD every month-end.
Source: SAP Community, FI-SD integration
Who SD talks to
An SD document is rarely alone. Each step reads or writes data that belongs to another module, which is why a “sales problem” so often ends up on an FI or MM desk.
- MMStock and material masterAvailability, valuation of the goods issue, sales views of the material.
- LE / EWMShipping and warehouseOutbound deliveries, picking, packing, goods issue, transport.
- FI-ARReceivablesThe open item each invoice creates, payments, dunning.
- FI-GLRevenue and taxRevenue, sales deductions, freight and output tax accounts.
- CO-PAMargin analysisRevenue and cost by customer, product, region and channel.
- FIN-FSCMCredit managementCredit limits and credit blocks on orders and deliveries.
Organizational structure
Who sells, through which channel, from where
Before the first order, SD needs to know who is selling, how the goods reach the customer and where they ship from. These units decide prices, document types and, through the company code, where revenue lands. Pick a unit to see what it means and why FI cares.
Financial accounting
Company code
The legal entity FI keeps a complete set of books for. SD does not create it, but every sale ends up in one: the company code of the sales organization that sold it.
Example: BR01, the Brazilian subsidiary
Why FI cares
Revenue, receivables and output tax of a billing document post in the company code of its sales organization. Closing, reporting and tax returns all start here.
CustomizingOX02OVX3
The Customizing transactions for each unit are in the Consultant view.
Sales
Sales organization
The unit responsible for selling: it signs with the customer, owns the prices and answers for the sale, returns included. A sales organization belongs to exactly one company code, while a company code can have several sales organizations.
Example: BR10 Domestic sales, BR20 Export sales
Why FI cares
The link sales organization to company code is what tells FI where revenue belongs. Splitting sales organizations by country or business is often a finance decision, not only a sales one.
CustomizingOVX5OVX3
The Customizing transactions for each unit are in the Consultant view.
Sales
Distribution channel
How products reach the customer: wholesale, retail, e-commerce, direct sales. The same customer can buy through two channels and get different prices, terms and document types in each.
Example: 10 Wholesale, 20 Retail, 30 E-commerce
Why FI cares
Often a characteristic in margin analysis, so management can compare margins by channel. Adding a channel late means maintaining customer data and prices again for it.
CustomizingOVXIOVXK
The Customizing transactions for each unit are in the Consultant view.
Sales
Division
A product line, such as beverages or packaging. Each material carries one division in its master data, and responsibility, prices and statistics can be split by it.
Example: 01 Beverages, 02 Packaging
Why FI cares
A common business area or segment driver in reporting, and another margin analysis characteristic.
CustomizingOVXBOVXA
The Customizing transactions for each unit are in the Consultant view.
Sales
Sales area
Sales organization + distribution channel + division. It is the key SAP uses for customer sales data such as payment terms, shipping conditions and pricing procedure, for the document types allowed and for pricing procedure determination.
Example: BR10 / 10 / 01: domestic wholesale of beverages
Why FI cares
Customer sales data per sales area holds the account assignment group that revenue account determination (VKOA) reads, so two sales areas can post the same customer to different revenue accounts.
CustomizingOVXGOVKK
The Customizing transactions for each unit are in the Consultant view.
Internal sales structure
Sales office and sales group
The internal organization of sales: offices, such as branches or regions, and groups, the teams of sales people in them. Optional, but useful for responsibility and reporting.
Example: Office São Paulo, group Key accounts
Why FI cares
Available as characteristics in margin analysis and sales reporting, which is the usual reason to set them up.
CustomizingOVX1OVX4
The Customizing transactions for each unit are in the Consultant view.
Logistics
Plant
Where the goods come from: a factory or a warehouse. A plant belongs to one company code and is linked to the combinations of sales organization and distribution channel that may sell from it.
Example: 1000 Main factory, 1100 Regional warehouse
Why FI cares
Goods issue is valued in the plant’s valuation area and posted in the plant’s company code. If that differs from the selling company code, the sale is intercompany and needs intercompany billing.
CustomizingOX10OVX6
The Customizing transactions for each unit are in the Consultant view.
Logistics
Shipping point
The place where deliveries are processed, such as a loading dock or a shipping team. Every outbound delivery has exactly one shipping point, found from the plant, the shipping conditions and the loading group.
Example: Dock 1 at the main factory
Why FI cares
No direct FI impact. It decides who ships and when, which in turn decides when goods issue, and the cost of goods sold, are posted.
Org units as configured in a standard SAP system. Sources: SAP Learning, condition technique (pricing procedure per sales area); SAP Community, FI-SD integration; definition and assignment transactions from a published SD enterprise structure guide.
The SD process
Follow one order from the customer to the cash
Eight steps of the classic sell-from-stock flow. Each one creates a document that copies data from the one before, and together they form the document flow you see in VA03. Pick a step to see what happens, where you see it, what it posts in the books and, in the Consultant view, what sits under the hood.
Step 1 of 8 · What happens
The customer asks: inquiry and quotation
Many sales start with a question: what would 500 cases cost, delivered next month? SD can record it as an inquiry and answer with a quotation that has prices, validity dates and terms. When the customer accepts, the order is created with reference to the quotation and copies its data, so nothing is typed twice.
Who: Sales representative
Where you see it
Quotations are created in VA21 or the Manage Sales Quotations - Version 2 app; inquiries in VA11. Because the order references the quotation, the document flow later shows where the deal began.
VA21VA11Manage Sales Quotations - Version 2
Under the hood
Inquiry and quotation are sales document types IN and QT, document categories A and B. Copying from quotation to order is set in VTAA by source and target document type, at header, item and schedule line level, with copying requirements and data transfer routines kept in VOFM.
VOV8VTAAVOFM
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: No posting. Quotations can feed sales reporting, but nothing reaches FI.
Sources: SAP Learning, sell from stock and copying control; SAP Help, setting copy control.
Step 2 of 8 · What happens
The sales order is entered
The order is the heart of SD. From the customer, the material and the sales area, SAP proposes the partners (sold-to, ship-to, bill-to, payer), the terms of payment, prices and taxes, an item category for each line and schedule lines with dates and quantities. Anything mandatory that is missing goes to the incompletion log.
Who: Customer service or sales back office
Where you see it
VA01 to create, VA02 to change, VA03 to display; in Fiori, Manage Sales Orders - Version 2 or Create Sales Orders. VA05 lists orders by customer, material or date.
VA01VA03VA05Manage Sales Orders - Version 2
Under the hood
The order type (VOV8) and item category determination (VOV4) drive most of the behaviour. Pricing procedure determination (OVKK) uses the sales area, the document pricing procedure and the customer pricing procedure. Header, items and schedule lines are VBAK, VBAP and VBEP; pricing results go to PRCD_ELEMENTS in S/4HANA, KONV in ECC.
VOV8VOV4OVKKV/08PRCD_ELEMENTS
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: No posting yet. With credit checks active, the open order value already counts toward the customer’s credit exposure.
Sources: SAP Learning, condition technique and data model simplifications; SAPSTACK SD transaction list.
Step 3 of 8 · What happens
Stock and credit are checked
When the order is saved, the availability check (ATP) confirms how much can be delivered and when, and writes it into the schedule lines. The credit check compares the order with the customer’s credit limit and open items. An order can be saved with nothing confirmed or with a credit block, and that is where many “lost” orders hide.
Who: SAP, automatically; a credit analyst if the order is blocked
Where you see it
Confirmed quantities and dates are on the schedule lines in VA03. VA14L lists orders blocked for delivery; the Sales Order Fulfillment – Analyze and Resolve Issues app gathers order, delivery and billing issues in one place.
VA03VA14L
Under the hood
In S/4HANA the credit check runs in SAP Credit Management: master data in UKM_BP, credit cases in UKM_CASE, while FD32 and the classic credit tables are gone. With advanced ATP, backorder processing (BOP) recalculates confirmations with strategies such as win, gain, redistribute, fill and lose, and the classic V_V2 can no longer be used for those materials.
UKM_BPUKM_CASEMonitor BOP Run
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: No posting. Credit exposure is updated, which is what the credit check reads.
Sources: SAP blog, conversion of credit management to SAP S/4HANA; SAP Learning, backorder processing; SAP PRESS, SAP S/4HANA Sales.
Step 4 of 8 · What happens
The outbound delivery is created
When the goods are due to ship, an outbound delivery is created from one or more orders. It belongs to one shipping point and one ship-to party, and it is the document the warehouse works with. Deliveries are usually created in bulk from the list of orders due for delivery, not one by one.
Who: Shipping team or a background job
Where you see it
VL10A lists the orders due for delivery and creates the deliveries; VL01N creates one for a single order; VL06O, the outbound delivery monitor, follows them afterwards.
VL10AVL01NVL06O
Under the hood
Delivery type LF (OVLK) and copy control from order to delivery (VTLA) decide what is copied. The shipping point comes from plant, shipping conditions and loading group. Header and items are LIKP and LIPS; in S/4HANA their statuses live in these tables instead of VBUK and VBUP.
OVLKVTLALIKPLIPS
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: No posting.
Sources: TestingBrain SD transaction list; SAP Help, setting copy control; SAP Learning, data model simplifications.
Step 5 of 8 · What happens
The goods are picked and packed
The warehouse picks the goods, records the picked quantities in the delivery and, if needed, packs them into handling units. In companies with SAP Extended Warehouse Management (EWM), the work happens in the warehouse system and the result comes back to the delivery.
Who: Warehouse
Where you see it
Picked quantities are on the delivery in VL02N; VL06P lists deliveries waiting for picking.
VL02NVL06P
Under the hood
Whether an item must be picked is set per delivery item category. Batches, serial numbers and handling units are added on the delivery, and partial picking leads to partial deliveries or a later delivery for the rest.
LIPSVL06P
Customizing, tables and the settings behind this step are in the Consultant view.
No postingIn the books: No posting.
Sources: SAPSTACK and TestingBrain SD transaction lists.
Step 6 of 8 · What happens
Goods issue: the goods leave
Posting goods issue is the moment the goods leave: stock goes down, ownership passes to the customer and the cost of goods sold is posted. After goods issue, the delivery is due for billing. A mistake here is not deleted but reversed.
Who: Shipping team
Where you see it
Post goods issue from VL02N, or in bulk from VL06O; reverse it with VL09.
VL02NVL06OVL09
Under the hood
Goods issue posts movement type 601. The G/L accounts come from MM account determination (OBYC): inventory from key BSX, cost of goods sold from key GBB with account modifier VAX. In S/4HANA the material document is stored in MATDOC.
OBYC601MATDOC
Customizing, tables and the settings behind this step are in the Consultant view.
FI postingIn the books: Journal entry: debit cost of goods sold, credit inventory, at the material’s cost. Revenue is not posted yet.
Sources: SAPSTACK SD transaction list; SAP Learning, sell from stock (cost of goods sold at goods issue).
Step 7 of 8 · What happens
The invoice is created and posted
Billing turns the delivery, or the order for services, into an invoice. Most companies run it in bulk from the billing due list, which also combines several deliveries into one invoice when the header data allows. Saving the billing document creates the journal entry in FI and, in Brazil, the nota fiscal.
Who: Billing clerk or a nightly job
Where you see it
VF04 is the billing due list, VF01 bills one document and VF03 displays it with the accounting documents behind it. In Fiori: Create Billing Documents and Manage Billing Documents.
VF04VF01VF03Create Billing Documents
Under the hood
Billing type F2 (VOFA) and copy control delivery to billing (VTFL). Revenue accounts come from VKOA through procedure KOFI00, by account key: ERL revenue, ERS sales deductions, ERF freight, MWS output tax. A posting block or an account determination error stops the hand-over to FI; VFX3 lists those documents.
VOFAVTFLVKOAVFX3VBRK
Customizing, tables and the settings behind this step are in the Consultant view.
FI postingIn the books: Journal entry: debit the customer, credit revenue and output tax, with discounts on their own account. Try it in the simulator below.
Sources: SAP Community, FI-SD integration; SAP Help, Nota Fiscal handling in SD; SAP Learning, sell from stock.
Step 8 of 8 · What happens
The customer pays
The last step belongs to FI: the incoming payment clears the open item the invoice created, by hand, from the bank statement or by lockbox. Late payers go to dunning. Once the item is cleared, the order-to-cash cycle is complete and the credit exposure goes down.
Who: Accounts receivable
Where you see it
FBL5N shows the customer’s open and cleared items, and F-28 posts an incoming payment. In VA03, the document flow then shows the journal entry as cleared.
FBL5NF-28VA03
Under the hood
The terms of payment copied from the order set the due date and any cash discount. Clearing is pure FI-AR; for SD it only changes the status of the accounting document in the document flow.
FBL5NF-28
Customizing, tables and the settings behind this step are in the Consultant view.
FI postingIn the books: Journal entry: debit bank, credit customer. The receivable from billing is cleared.
Source: SAP Learning, sell from stock (payment and clearing).
The three blocks every SD user should know
Most “my order is stuck” calls end at one of these. A block can come from the document type, the customer master, a user or the credit check, and each one stops a different step.
- Stops the deliveryDelivery blockSet on the order header or schedule line, by hand or from the customer master. The order exists, but no delivery can be created until someone removes it.
- Stops the invoiceBilling blockSet on the header or an item, often for prices still to be agreed or for credit memo requests waiting for approval. Goods can ship; the invoice waits.
- Stops everything after the orderCredit blockSet by the credit check when the customer is over the limit or has overdue items. Only a credit analyst can release it, which is why credit and sales often meet.
Try it
From the price to the journal entry
This is the part FI consultants ask about most. Every line of an SD price is a condition, and every condition that posts carries an account key that revenue account determination turns into a G/L account. Change the order below and watch the price, the invoice’s journal entry and the margin move together.
The order
Example: 10 PC, 5% discount, freight 50.00, 10% output tax.
Price 100.00 and cost 62.00 per piece, in USD. Examples only.
The conditions tab, as SAP shows it
| Cond. | Name | Rule | Value | Key |
|---|---|---|---|---|
PPR0 | Price | 100.00 × 10 PC | 1,000.00 | ERL |
K007 | Customer discount | −5% | −50.00 | ERS |
| Net value of goods | Subtotal | 950.00 | ||
KF00 | Freight | Fixed per order | 50.00 | ERF |
| Net value | Goods + freight | 1,000.00 | ||
MWST | Output tax | 10% of net value | 100.00 | MWS |
| Total for the customer | Net + tax | 1,100.00 | ||
VPRS | Cost (statistical) | 62.00 × 10 | 620.00 | — |
| Profit margin | Net value − cost | 380.00 |
Billing document 90003520 → journal entry
| Account | Key | Debit | Credit |
|---|---|---|---|
| Customer (receivable) | — | 1,100.00 | |
| Sales deductions | ERS | 50.00 | |
| Revenue | ERL | 1,000.00 | |
| Freight revenue | ERF | 50.00 | |
| Output tax | MWS | 100.00 | |
| Total | 1,150.00 | 1,150.00 |
Debits equal credits. The G/L accounts come from VKOA, by account key.
Goods issue → journal entry
| Account | Key | Debit | Credit |
|---|---|---|---|
| Cost of goods sold | GBB-VAX | 620.00 | |
| Inventory | BSX | 620.00 |
Posted at goods issue, before the invoice, with accounts from MM account determination (OBYC).
The margin on this order
Net revenue1,000.00
Cost of goods sold−620.00
Gross margin380.00
38.0% of net revenue. Output tax is not revenue, so it does not count in the margin.
Condition types from SAP’s classic standard pricing procedure; in SAP S/4HANA Cloud the standard price condition is PPR0, shown here, where older systems use PR00. Real procedures have many more steps, and which G/L accounts the keys reach depends on your VKOA settings. Sources: SAP Learning, condition technique and condition types; SAP Community, FI-SD integration (account keys ERL, ERS, ERF and MWS, procedure KOFI00).
Quick test
Why is my order stuck?
Eight calls every SD support team knows by heart. Guess the cause first, then open the card to see it, the fix and who acts.
- Availability
- Credit
- Missing data
- Shipping
- Accounting
- Output
The order is saved, but the schedule line confirms 0 piecesShow the answer
AvailabilityThe availability check found no stock or planned receipt for the requested date, so nothing is confirmed and nothing can be delivered. Check the schedule lines in VA03; with advanced ATP, a backorder processing run can confirm it later.
Who acts: Customer service, then planning
The order header says “credit block”Show the answer
CreditThe credit check failed: the limit is exceeded or the customer has overdue items. No delivery can be created until a credit analyst releases the order, in S/4HANA through SAP Credit Management (UKM_CASE) or VKM1.
Who acts: Credit analyst
A pop-up warns that the document is incompleteShow the answer
Missing dataA field the incompletion procedure marks as required is empty, such as the customer’s PO number or the incoterms. Depending on the setting, it blocks delivery, billing or both. The incompletion log in the order lists the fields, and V.02 lists every incomplete order.
Who acts: Customer service
The price is zero and the item shows a pricing errorShow the answer
Missing dataNo condition record was found for the price condition along its access sequence, for this customer, material or sales area. Create one with VK11; the pricing analysis in the item conditions shows every access SAP tried and why each failed.
Who acts: Pricing team
The delivery is packed, but VF04 does not show itShow the answer
ShippingGoods issue has not been posted. In the usual copy control a delivery item is billed only after goods issue, so post it from VL02N or VL06O. If goods issue is done, look for a billing block on the order or the delivery.
Who acts: Shipping, then billing
The invoice exists, but there is no journal entryShow the answer
AccountingThe billing document did not reach FI. Posting status A means it is blocked for accounting; B means account determination failed, usually a missing VKOA entry. Fix the cause, then release it with the green flag in VF02 or from VFX3.
Who acts: Billing clerk and FI
The delivery cannot be deletedShow the answer
ShippingGoods issue has been posted, so the stock has already left in the books. Reverse the goods issue with VL09 first; then the delivery can be changed or deleted in VL02N.
Who acts: Shipping
The customer never received the invoice PDFShow the answer
OutputNo output was determined or sent. In S/4HANA, billing uses the new output management by default, while classic NAST output can still be switched on. Check the output of the billing document, fix the determination and send it again.
Who acts: Billing clerk, then an SD consultant
Sources: SAP Community, billing posting status A and B, and billing before goods issue (VTFL requirement 004); SAP blog, conversion of credit management to SAP S/4HANA; SAP Learning, output management in billing and backorder processing; TestingBrain, SAPSTACK and Tutorialspoint SD transaction lists.
Speak SD
The codes SD people use
SD consultants talk in codes: “it’s an OR with a TAS item, so there’s no LF, we bill it with F2”. These are the standard ones you will hear in meetings and see on every screen. Your company may copy and rename them, usually with a Z in front.
How it is chosen: The user picks the sales document type when creating the document (VA01, VA21, VA11); its settings in VOV8 decide numbering, checks and the default delivery and billing types.
How it is chosen: Item category = sales document type + item category group of the material (such as NORM or BANS) + usage + higher-level item, set in VOV4. It decides pricing, billing relevance and whether schedule lines exist.
How it is chosen: Schedule line categories are defined in VOV6 and assigned in VOV5, by item category + MRP type of the material. They decide the movement type, whether requirements go to planning and whether the item is checked for availability.
How it is chosen: The delivery type is proposed by the sales document type, or by the purchase order for stock transfers, and set up in OVLK.
How it is chosen: The billing type is proposed from the sales document type or the delivery, through copy control (VTFA, VTFL), and set up in VOFA, which also names its cancellation type.
INInquiryA customer question, with no commitment on either side.QTQuotationA binding offer with prices and a validity period.ORStandard orderThe everyday order: delivered, then billed.RORush orderDelivery created as soon as the order is saved, billed afterwards.CSCash saleThe customer pays and takes the goods; the invoice prints at once.REReturnsGoods coming back; leads to a returns delivery and a credit.CRCredit memo requestAsks for a credit, often with a billing block until approved.DRDebit memo requestAsks for an extra charge to the customer.KBConsignment fill-upStock moved to the customer’s site, still yours.KEConsignment issueThe customer uses consignment stock and is billed for it.TANStandard itemPriced, delivered and billed from the delivery.AGNQuotation itemThe item of a quotation.AFNInquiry itemThe item of an inquiry.TANNFree-of-charge itemDelivered but not priced, such as a free sample.TASThird-party itemA vendor ships straight to your customer; a purchase requisition replaces the delivery.TABIndividual purchase orderBought specially for this order and shipped through your warehouse.RENReturns itemThe item of a returns order.KBNConsignment fill-up itemMoves stock into customer consignment.KENConsignment issue itemIssues consignment stock to the customer.CPMRPPasses the requirement to material planning; the usual line for stock items.CNNo MRPNo requirement for planning.CSThird partyCreates a purchase requisition for the vendor; no goods movement of your own.CBIndividual purchase orderRequisition for goods bought for this order.DNReturnsSchedule line of a returns item.LFOutbound deliveryThe standard delivery to a customer.LRReturns deliveryGoods coming back from a returns order.NLReplenishment deliveryStock transfer between plants, from a stock transport order.LODelivery without referenceA delivery with no sales order behind it.F2InvoiceThe standard invoice for delivered goods.F1Order-related invoiceBilled straight from the order, for services and items with nothing to ship.F5Pro forma for orderFor customs or advance payment; never posted to FI.F8Pro forma for deliveryPro forma from the delivery; never posted to FI.G2Credit memoFrom a credit memo request.L2Debit memoFrom a debit memo request.RECredit for returnsCredit after a returns order.S1Invoice cancellationCreated by VF11; reverses an F2 in FI.IVIntercompany invoiceBills the selling company code from the delivering one.
The screen says OR, but the database stores TA. SAP converts the code for display with conversion exit AUART and table TAUUM; the credit memo request CR is stored as G2. Extracts and interfaces that skip the conversion show the internal codes. Source: SAP Community
Reference
The SD transactions people actually use
SD transactions follow a pattern: VA for sales documents, VL for deliveries, VF for billing, VK for prices, V/ and OV for Customizing. Start here shows the ones worth bookmarking; FI/CO bridge collects what FI, CO and credit people touch; the last column says what changed in SAP S/4HANA. Type a code or a word to search all of them.
| Code or app | For | What it does | Who opens it | ECC / S/4HANA |
|---|---|---|---|---|
VA01 | User | Create a sales order: customer, material, quantity; SAP proposes partners, prices, taxes and dates. | Customer service | ECC + S/4HANA |
VA02 | User | Change a sales order: quantities, dates, blocks, reasons for rejection. | Customer service | ECC + S/4HANA |
VA03 | User | Display a sales order. The document flow shows every follow-on document and its status, down to the journal entry. | Everyone | ECC + S/4HANA |
VA05 | User | List sales orders by customer, material or date. | Sales, customer service | ECC + S/4HANA |
VA21 | User | Create a quotation; VA22 changes, VA23 displays and VA25 lists them. | Sales | ECC + S/4HANA |
VA11 | User | Create an inquiry; VA12 changes and VA13 displays it. | Sales | ECC + S/4HANA |
VA41 | User | Create a contract; VA42 changes and VA43 displays it. | Sales | ECC + S/4HANA |
VA14L | User | Sales documents blocked for delivery. | Customer service, credit | ECC + S/4HANA |
V.02 | User | List of incomplete sales orders. | Customer service | ECC + S/4HANA |
VL10A | User | Sales orders due for delivery: select them and create the deliveries in bulk. | Shipping | ECC + S/4HANA |
VL01N | User | Create an outbound delivery with reference to one sales order. | Shipping | ECC + S/4HANA |
VL02N | User | Change a delivery: picked quantities, batches and the Post Goods Issue button. | Shipping, warehouse | ECC + S/4HANA |
VL06O | User | Outbound delivery monitor: deliveries for picking, goods issue or confirmation, with collective processing. | Shipping | ECC + S/4HANA |
VL06P | User | Outbound deliveries waiting for picking. | Warehouse | ECC + S/4HANA |
VL09 | User | Reverse the goods issue of a delivery. | Shipping | ECC + S/4HANA |
VF04 | User | Billing due list: bill many deliveries and orders at once, combining them where the data allows. | Billing | ECC + S/4HANA |
VF01 | User | Create a billing document for one delivery or order. | Billing | ECC + S/4HANA |
VF02 | User | Change a billing document; the green flag releases it to accounting. | Billing, FI | ECC + S/4HANA |
VF03 | User | Display a billing document and the accounting documents behind it. | Everyone | ECC + S/4HANA |
VF11 | User | Cancel a billing document. It creates a cancellation document instead of deleting the invoice. | Billing | ECC + S/4HANA |
VK11 | User | Create condition records: prices, discounts, surcharges. VK12 changes and VK13 displays them. | Pricing team | ECC + S/4HANA |
BP | User | Business partner: create and change customers. Replaces XD01, VD01 and FD01. | Master data team | S/4HANA |
XD03 | User | Display a customer centrally. | Master data team | ECC · S/4HANA: BP |
VKM1 | User | Blocked SD documents (credit). Still available next to SAP Credit Management. | Credit analysts | ECC + S/4HANA |
OVX3 | Consultant | Assign a sales organization to its company code. | SD and FI consultants | ECC + S/4HANA |
OVXG | Consultant | Set up sales areas: sales organization, distribution channel, division. | SD consultants | ECC + S/4HANA |
OVX6 | Consultant | Assign plants to sales organization and distribution channel. | SD consultants | ECC + S/4HANA |
VOV8 | Consultant | Sales document types: numbering, checks, blocks, default delivery and billing types. | SD consultants | ECC + S/4HANA |
VOV7 | Consultant | Item categories: pricing, billing relevance, schedule lines allowed. | SD consultants | ECC + S/4HANA |
VOV4 | Consultant | Item category determination: document type + item category group + usage + higher-level item. | SD consultants | ECC + S/4HANA |
VOV6 | Consultant | Schedule line categories: movement type, planning and availability check. | SD consultants | ECC + S/4HANA |
VOV5 | Consultant | Schedule line category determination: item category + MRP type. | SD consultants | ECC + S/4HANA |
OVLK | Consultant | Delivery types. | SD and LE consultants | ECC + S/4HANA |
VOFA | Consultant | Billing types: numbering, cancellation type, posting block, account determination procedure. | SD consultants | ECC + S/4HANA |
VTAA | Consultant | Copy control sales document to sales document, such as quotation to order. | SD consultants | ECC + S/4HANA |
VTLA | Consultant | Copy control sales document to delivery. | SD and LE consultants | ECC + S/4HANA |
VTFA | Consultant | Copy control sales document to billing (order-related billing). | SD consultants | ECC + S/4HANA |
VTFL | Consultant | Copy control delivery to billing (delivery-related billing). | SD consultants | ECC + S/4HANA |
VOFM | Consultant | Routines for copying requirements, data transfer and pricing. Changing them needs ABAP. | SD consultants, developers | ECC + S/4HANA |
V/06 | Consultant | Condition types. | SD consultants | ECC + S/4HANA |
V/07 | Consultant | Access sequences: the order in which condition tables are searched. | SD consultants | ECC + S/4HANA |
V/08 | Consultant | Pricing procedures: condition types, subtotals, requirements and account keys. | SD and FI consultants | ECC + S/4HANA |
OVKK | Consultant | Pricing procedure determination: sales area + document pricing procedure + customer pricing procedure. | SD consultants | ECC + S/4HANA |
OVA2 | Consultant | Incompletion procedures: required fields and what is blocked while they are empty. | SD consultants | ECC + S/4HANA |
NACE | Consultant | Classic output determination (NAST) for print, e-mail and EDI. | SD consultants | ECC + S/4HANA |
Output Parameter Determination | Consultant | App that sets output rules in BRF+ for the new output management, which billing uses by default. | SD consultants | S/4HANA |
OVA8 | Consultant | Classic SD credit checks per credit control area. | SD and FI consultants | ECC · S/4HANA: SAP Credit Management |
VKOA | FI/CO bridge | Revenue account determination: account key + customer and material account assignment groups → G/L account. | FI and SD consultants | ECC + S/4HANA |
VFX3 | FI/CO bridge | Billing documents blocked for accounting or with posting errors; release them to FI. | FI, billing | ECC + S/4HANA |
OBYC | FI/CO bridge | MM account determination: inventory (BSX) and cost of goods sold (GBB, modifier VAX) at goods issue. | FI and MM consultants | ECC + S/4HANA |
OVK1 | FI/CO bridge | Tax categories per country for output tax, read in pricing. | FI and tax | ECC + S/4HANA |
FTXP | FI/CO bridge | Tax codes and rates behind the output tax conditions. | FI and tax | ECC + S/4HANA |
UKM_BP | FI/CO bridge | Credit master data: limit, risk class, credit segment. | Credit analysts, FI | S/4HANA |
UKM_CASE | FI/CO bridge | Credit cases, used to process blocked sales documents. | Credit analysts | S/4HANA |
FD32 | FI/CO bridge | Classic customer credit management. | Credit analysts | ECC · S/4HANA: UKM_BP |
FBL5N | FI/CO bridge | Customer line items: open and cleared receivables from billing. | AR, FI | ECC + S/4HANA |
F-28 | FI/CO bridge | Post an incoming payment and clear the customer’s open item. | AR | ECC + S/4HANA |
KE30 | FI/CO bridge | Profitability reports: revenue and margin by customer, product, region. | Controlling | ECC + S/4HANA |
VF44 | FI/CO bridge | Classic SD revenue recognition. | FI | ECC · S/4HANA: SAP RAR |
VBO1 | FI/CO bridge | Create a rebate agreement (classic SD rebates). | Sales, FI | ECC · S/4HANA: condition contracts |
WCOCO | FI/CO bridge | Condition contracts for settlement management, the S/4HANA successor of SD rebates. | Sales, FI | S/4HANA |
| Manage Sales Orders - Version 2 | Fiori app | Find, create and change sales orders, with a link to the customer 360° view. | Customer service | S/4HANA |
| Create Sales Orders | Fiori app | Guided entry of a sales order. | Customer service | S/4HANA |
| Import Sales Orders | Fiori app | Create sales orders from an Excel file. | Customer service | S/4HANA |
| Manage Sales Quotations - Version 2 | Fiori app | Create and follow quotations. | Sales | S/4HANA |
| Sales Order Fulfillment – Analyze and Resolve Issues | Fiori app | One dashboard of order, delivery, supply and billing issues. | Customer service | S/4HANA |
| Track Sales Order Details | Fiori app | Where an order stands in order, supply, delivery and billing. | Customer service, sales | S/4HANA |
| Manage Customer Returns | Fiori app | Returns, including third-party returns and inspection at the customer’s site. | Customer service | S/4HANA |
| Create Billing Documents | Fiori app | Bill deliveries and orders that are due. | Billing | S/4HANA |
| Manage Billing Documents | Fiori app | Find and process billing documents. | Billing | S/4HANA |
| Manage Billing Document Requests | Fiori app | Billing requests from outside SAP, uploaded from Excel. | Billing | S/4HANA |
| Manage Duplicate Sales Documents | Fiori app | Review and reject sales documents entered twice. | Customer service | S/4HANA |
| Customer - 360° View | Fiori app | One page about a customer, opened from Manage Sales Orders. | Sales, AR | S/4HANA |
| Monitor BOP Run | Fiori app | Results of backorder processing runs in advanced ATP. | Planning, customer service | S/4HANA |
| Joule | Fiori app | Ask “What is the status of sales order 12345?” in SAP S/4HANA Cloud Public Edition. | Everyone | S/4HANA |
VBAK | Table | Sales document header; in S/4HANA it also holds the header statuses that were in VBUK. | Consultants | ECC + S/4HANA |
VBAP | Table | Sales document items, with the item statuses in S/4HANA. | Consultants | ECC + S/4HANA |
VBEP | Table | Schedule lines: confirmed dates and quantities. | Consultants | ECC + S/4HANA |
VBFA | Table | Document flow: predecessor and follow-on documents. | Consultants | ECC + S/4HANA |
VBPA | Table | Partners of SD documents: sold-to, ship-to, bill-to, payer. | Consultants | ECC + S/4HANA |
LIKP / LIPS | Table | Delivery header and items. | Consultants | ECC + S/4HANA |
VBRK / VBRP | Table | Billing header and items; VBRK-RFBSK is the posting status to FI. | Consultants | ECC + S/4HANA |
KNVV | Table | Customer sales data per sales area. | Consultants | ECC + S/4HANA |
PRCD_ELEMENTS | Table | Pricing results of documents; old KONV data can be read with CDS view V_KONV_CDS. | Consultants | S/4HANA |
KONV | Table | Pricing results in a cluster table. In S/4HANA it is only a structure. | Consultants | ECC · S/4HANA: PRCD_ELEMENTS |
VBUK / VBUP | Table | Header and item statuses of SD documents. | Consultants | ECC only |
VAKPA / VAPMA | Table | Sales document index tables by partner and by material. | Consultants | ECC only |
KONH / KONP | Table | Condition record header and items; the condition tables themselves are A001, A002 and so on. | Consultants | ECC + S/4HANA |
TAUUM | Table | Conversion of sales document types between internal and display codes, such as TA and OR. | Consultants | ECC + S/4HANA |
UKMBP_CMS | Table | Credit master data in SAP Credit Management, in place of KNKK. | Consultants | S/4HANA |
Nothing matches. Try another word, or pick All.
Standard codes, cross-checked with the SAPSTACK, TestingBrain and Tutorialspoint SD lists, a published SD enterprise structure guide, SAP Help and SAP Learning; S/4HANA changes from SAP Learning, SAP PRESS and the SAP blogs on credit management, output management and the business partner. Fiori app names follow SAP Learning and SAP PRESS. Projects can hide transactions or rename apps, so check your own system before you write them into a manual.
ECC to S/4HANA
What changed in SD with SAP S/4HANA
The order, delivery and billing chain is the same as in SAP ECC. What changed is around it: master data, credit, rebates, revenue recognition, output and the tables underneath. If your company is moving from ECC, these are the cards to read.
Customer master
ECCXD01, VD01 and FD01 for customers.
S/4HANABusiness partner (BP) with customer roles; customer–vendor integration is mandatory.
The separate customer transactions are not available in S/4HANA; BP is the user interface.
Source: SAP blog, business partner and CVI (2016)Credit management
ECCSD credit management: FD32, credit checks in OVA8, VKM transactions.
S/4HANASAP Credit Management (FSCM): UKM_BP and UKM_CASE.
VKM1 and VKM4 are still available; KNKK and the other classic credit tables are obsolete.
Source: SAP blog, credit management in S/4HANA (2020)Rebates
ECCRebate agreements (VBO1) and the rebate index VBOX.
S/4HANACondition contracts and settlement management.
Existing agreements can be processed until the end of their validity and are then closed.
Source: SAP PRESS, SAP S/4HANA SalesRevenue recognition
ECCSD revenue recognition with VF44.
S/4HANASAP Revenue Accounting and Reporting (RAR).
SAP Note 2733866 is the migration guide from SD revenue recognition to RAR.
Source: SAP Community, VF44 in S/4HANAPricing results
ECCCluster table KONV.
S/4HANATransparent table PRCD_ELEMENTS, with longer fields.
KONV remains only as a structure; old data can be read with the CDS view V_KONV_CDS.
Source: SAP Learning, data model simplificationsStatus and index tables
ECCVBUK, VBUP and index tables such as VAKPA and VAPMA.
S/4HANAStatuses in VBAK, VBAP, LIKP, LIPS and VBRK; index tables removed.
Custom reports that read VBUK, VBUP or the index tables must be adapted.
Source: SAP Learning, data model simplificationsDocument category
ECCVBTYP, one character.
S/4HANAVBTYPL, four characters.
Custom code that assumes a one-character document category must be checked.
Source: SAP Learning, data model simplificationsOutput
ECCNAST output, configured in NACE.
S/4HANANew output management, the default for billing.
The legacy frameworks are still available, and billing can switch back to NAST.
Source: SAP blog, output management (2016)Availability check
ECCClassic ATP and rescheduling with V_V2.
S/4HANAAdvanced ATP with backorder processing (BOP).
For materials under advanced ATP, CO06, V_RA and V_V2 can no longer be used.
Source: SAP Learning, backorder processingForeign trade
ECCSD foreign trade (SD-FT).
S/4HANASAP S/4HANA for international trade.
SAP Global Trade Services stays a separate product with its own license.
Source: SAP PRESS, SAP S/4HANA SalesUser experience
ECCSAP GUI transactions.
S/4HANAFiori apps next to the transactions, and Joule in the cloud.
Sales Order Fulfillment – Analyze and Resolve Issues shows order, delivery, supply and billing issues on one screen.
Source: SAP PRESS, SAP S/4HANA Sales
Brazil
SD in Brazil: every invoice is also a nota fiscal
Elsewhere, an SD invoice is a commercial document. In Brazil, the legal document is the nota fiscal, and SD is where it is born: billing creates it, pricing calculates its taxes and the NF-e must be authorized before the goods can travel.
- Billing
Billing creates the nota fiscal
SD billing can create the nota fiscal automatically, one for each billing document. That is why, in Brazil, a delivery that needs a nota fiscal must also be relevant for billing.
Source: SAP Help, Nota Fiscal handling in SD - CFOP and taxes
Decided in the sales document
The CFOP, the fiscal operation code on every nota fiscal, is determined in SD, and ICMS, IPI, PIS and COFINS are calculated in the pricing procedure and copied into the nota fiscal. A wrong tax in Brazil is very often an SD condition problem.
Source: SAP Help, CFOP determination in SD - NF-e
Authorized before the truck leaves
The NF-e XML goes to the state tax authority for authorization, through SAP DRC, the older SAP GRC NF-e or a partner tool, and the goods travel with the DANFE. The consumption tax reform now adds CBS and IBS to the same documents.
Related: Brazil tax reform on this site
Documented, but little known
15 tips for users and consultants
Each tip comes from SAP Learning, SAP Help, an SAP blog or a published source, linked under the tip.
- 01Users
The document flow answers most questions
In any SD document, the document flow shows every predecessor and follow-on document with its status, including the journal entry and whether it is cleared. In S/4HANA a process overview combines flow and status on one screen.
VA03VL03NVF03
- 02Users
Find stuck orders without opening them
VA14L lists sales documents blocked for delivery and V.02 lists incomplete orders. In S/4HANA, Sales Order Fulfillment – Analyze and Resolve Issues gathers order, delivery, supply and billing issues in one dashboard.
VA14LV.02
- 03Users
Never delete: reverse
A goods issue is reversed with VL09 and an invoice is cancelled with VF11, which creates a cancellation document. Both keep the audit trail, and both must happen before the delivery or order can be corrected.
VL09VF11
- 04Users
Bill in bulk, not one by one
The billing due list bills every delivery and order that is due in one run and, where the data allows, combines several of them into one invoice. Most companies schedule it as a nightly job.
VF04
- 05Users
Ask Joule where the order is
In SAP S/4HANA Cloud Public Edition, Joule answers “What is the status of sales order 12345?” by checking order, supply, delivery and billing, explaining any issue and linking to the right app.
Joule
- 06Consultants
Why extracts show TA instead of OR
Sales document types are converted for display by conversion exit AUART using table TAUUM: TA is shown as OR and G2 as CR. Extracts and interfaces that skip the conversion see the internal codes, a classic BW surprise.
TAUUM
- 07Consultants
KONV is not where you think in S/4HANA
Pricing results moved to PRCD_ELEMENTS, with longer fields and its own decimal precision. KONV remains only as a structure, and the CDS view V_KONV_CDS reads old data. Custom code must use the new access.
PRCD_ELEMENTSV_KONV_CDS
- 08Consultants
VBUK and VBUP are gone
Header and item statuses now sit in VBAK, VBAP, LIKP, LIPS and VBRK; the index tables VAKPA, VAPMA, VLKPA, VLPMA, VRKPA and VRPMA are no longer used, and VBTYP became the four-character VBTYPL.
VBAKVBTYPL
- 09Consultants
Copy control lives in three levels and in ABAP
Copy control is set for header, item and schedule line. Its copying requirements and data transfer routines are ABAP routines kept in VOFM, so changing them needs a developer.
VTAAVTFLVOFM
- 10Consultants
With advanced ATP, forget V_V2
Once advanced ATP is active for a material, CO06, V_RA and V_V2 can no longer be used. Backorder processing replaces them, with confirmation strategies win, gain, redistribute, fill and lose.
Monitor BOP Run
- 11FI/CO
Read the posting status before anything else
VBRK-RFBSK tells you why an invoice has no journal entry: A is blocked for forwarding to FI, B is an account determination error. Once a document is in B, correcting the error lets it post on release.
VF02VFX3
- 12FI/CO
KOFI only works without a CO assignment
The standard account determination type KOFI, in procedure KOFI00, carries requirement 2, so it applies only when there is no CO account assignment. Its accesses use customer and material account assignment groups and the account key.
VKOAKOFI00
- 13FI/CO
Credit moved to FSCM
FD32 became UKM_BP, blocked orders are handled through credit cases (UKM_CASE), and the tables KNKK, KNKA, T042B, T042P and T691B are obsolete. VKM1 and VKM4 still work.
UKM_BPUKM_CASEVKM1
- 14FI/CO
VF44 is obsolete in S/4HANA
SD revenue recognition is not available in S/4HANA; SAP RAR replaces it and supports IFRS 15. SAP Note 2733866 is the migration guide from SD revenue recognition to RAR.
VF44
- 15FI/CO
Rebates become condition contracts
Existing SD rebate agreements can be processed only until the end of their validity and then closed with a final settlement. New ones are condition contracts in settlement management, maintained in WCOCO.
VBO1WCOCO
Myths
Things people get wrong about SD
Myth
SD is just typing orders.FactSD decides the price, the tax, the revenue account, the credit check and the margin analysis segment. Every billing document is a journal entry in FI.
Myth
Delivered means invoiced.FactBilling is a separate step. Until the billing due list runs, there is no revenue and no receivable, even if the goods left days ago.
Myth
The price is kept in the material master.FactPrices are condition records, kept with VK11 and found by the condition technique. The material master only carries groupings that the conditions use.
Myth
A wrong invoice can simply be deleted.FactA posted invoice is cancelled with VF11, which creates a cancellation document. The original and the cancellation both stay on record.
Myth
XD01 still creates customers in S/4HANA.FactThe business partner is mandatory: customers are created and changed in BP, and the separate customer transactions are not available.
Myth
SD credit management works the same in S/4HANA.FactIt was replaced by SAP Credit Management (FSCM). Credit master data is in UKM_BP and the classic credit tables are obsolete.
Myth
OR is the order type stored in the database.FactThe database stores TA. OR is the display code, converted with conversion exit AUART and table TAUUM.
Myth
Rebates work in S/4HANA as they did in ECC.FactNew rebates are condition contracts in settlement management. Old agreements only run to the end of their validity.
Evolution
From R/2’s RV module to Joule
SD is one of SAP’s oldest areas, and it shows: many of its codes still carry the German of the 1970s. Gold dots mark the S/4HANA era.
- 1979SAP R/2SAP launches R/2. Sales and distribution run in a module called RV, which also covers what is today Logistics Execution.
- 1992SAP R/3R/3 brings SAP to client-server computing. SD becomes one of its core modules, with the chain of order, delivery and billing documents still used today.
- ECC 6SAP ERP 6.0For most consultants this is classic SD: FD32 for credit, VBO1 for rebates, VF44 for revenue recognition, KONV for prices.
- 2015SAP S/4HANAThe business partner becomes mandatory, and the sales data model is slimmed: VBUK, VBUP and the index tables disappear and KONV gives way to PRCD_ELEMENTS.
- LaterS/4HANA releasesCredit management moves to FSCM, SD rebates to condition contracts, SD revenue recognition to SAP RAR and foreign trade to international trade. Billing gets the new output management.
- 2022Scope item 5MQSell from Stock with Valuated Stock in Transit joins the classic BD9 Sell from Stock in SAP’s best practices.
- TodayJouleIn SAP S/4HANA Cloud, Joule checks a sales order across order, supply, delivery and billing and points to the app that fixes the issue.
Why so many V’s
V is for Vertrieb, German for sales. It is why SD transactions start with V (VA, VL, VF, VK), why the sales order program is SAPMV45A and why the classic standard pricing procedure is called RVAA01.
Document categories you will meet
| VBTYP | Document |
|---|---|
| A / B | Inquiry / quotation |
| C | Sales order |
| H | Returns |
| J | Outbound delivery |
| M / N | Invoice / invoice cancellation |
| O / P | Credit memo / debit memo |
In SAP S/4HANA the field grew from one character (VBTYP) to four (VBTYPL). Source: SAP Learning, data model simplifications.
The questions people ask most
What does SD stand for, and is it still called that?
Sales and Distribution. SAP’s training for SAP S/4HANA calls the area Sales, but the transactions, the tables and almost everyone on a project still say SD.
What is the difference between SD, LE and MM?
SD sells: orders, prices, billing. LE, Logistics Execution, ships: deliveries, picking, goods issue, transport. MM buys and keeps the stock. The outbound delivery sits between SD and LE, which is why many people count it as SD. In the old R/2 system, a single module called RV covered both SD and what is now LE.
What is a sales area, and why does it matter?
The combination of sales organization, distribution channel and division. Customer sales data such as payment terms, pricing procedure and account assignment group are kept per sales area, so the same customer can have different terms, prices and even revenue accounts in different channels.
Where does the price in an order come from?
From condition records found by the condition technique. SAP determines the pricing procedure from the sales area, the document type and the customer. Each condition type in it has an access sequence that searches condition tables, usually from the most specific key to the most general, until a valid record is found. Prices are kept with VK11, not in the material master.
Why can’t I delete an invoice?
Because a posted billing document is an accounting document with a legal number. You cancel it with VF11, which creates a cancellation document that reverses the journal entry; the original and the cancellation both stay on record. Then correct the order or the delivery and bill again.
Why doesn’t my billing document have a journal entry?
Look at its posting status. Status A means it is blocked for accounting, often by a posting block on the billing type; status B means account determination failed, usually because VKOA has no G/L account for that combination. After the fix, release it with the green flag in VF02 or from VFX3.
What is copy control?
The rules for creating one document from another: quotation to order (VTAA), order to delivery (VTLA), order to billing (VTFA) and delivery to billing (VTFL). They are set at header, item and schedule line level, with copying requirements that must be met and data transfer routines that decide which fields are copied.
Order-related or delivery-related billing: what is the difference?
Delivery-related billing invoices what was shipped, from the delivery, and is the norm for goods. Order-related billing invoices directly from the order, for services, credit and debit memo requests and other items with nothing to ship. The item category decides which applies.
What is a third-party order?
An order your vendor delivers straight to your customer. Item category TAS creates a purchase requisition instead of a delivery, the goods never pass through your warehouse, and the customer is billed once the vendor’s invoice or goods receipt is recorded, depending on the setting.
What changed for SD in SAP S/4HANA?
The business partner replaced the customer transactions; credit management moved to SAP Credit Management; SD rebates gave way to condition contracts and SD revenue recognition to SAP RAR; the data model lost its status and index tables; pricing results moved to PRCD_ELEMENTS; billing uses the new output management by default; and advanced ATP added backorder processing. The order, delivery and billing chain itself stayed the same.
Which SD tables should I know?
VBAK, VBAP and VBEP for orders; LIKP and LIPS for deliveries; VBRK and VBRP for billing; VBFA for the document flow; VBPA for partners; KNVV for customer sales data; and PRCD_ELEMENTS for pricing results in S/4HANA, KONV in ECC.
How does SD feed profitability reporting?
The billing document sends revenue, sales deductions and quantities to margin analysis by customer, product and the other market segment characteristics, so management can see results by customer, product, region or channel.
Why do extracts and interfaces show TA when the screen says OR?
Sales document type codes are converted for display. The database keeps the internal code TA, and conversion exit AUART shows it as OR using table TAUUM; the credit memo request G2 appears as CR in the same way. Anything that reads the raw data, such as a BW extraction, sees the internal codes.
Related pages
References
Checked in November 2026. SAP knowledge base articles and SAP Notes need an SAP for Me login. Transaction lists from partner sites can lag behind your release; check names in your own system.
- Simplifications to the data model for SAP S/4HANA Saleslearning.sap.com
- Executing a standard sales from stock processlearning.sap.com
- Introducing the condition techniquelearning.sap.com
- Configuring copying control for sales documentslearning.sap.com
- Basic understanding of backorder processing (BOP)learning.sap.com
- Checking sales order status with Joulelearning.sap.com
- Configuring condition types for pricing elementslearning.sap.com
- Output management for billing documentslearning.sap.com
- Setting copy controlhelp.sap.com
- Nota Fiscal handling in SDhelp.sap.com
- CFOP determination in SDhelp.sap.com
- Key functionality of SAP S/4HANA Salesblog.sap-press.com
- Conversion of credit management to SAP S/4HANA (2020)blogs.sap.com
- Simplification item: output management (2016)blogs.sap.com
- Simplification item: business partner and CVI (2016)blogs.sap.com
- SAP S/4HANA FI-SD integration: revenue account determinationSAP Community
- Billing document posting status A and BSAP Community
- Billing only after goods issue (VTFL requirement 004)SAP Community
- Sales document type TA shown as OR (TAUUM)SAP Community
- Revenue recognition via VF44 in S/4HANASAP Community
- Price conditions PPR0 and PR00SAP Community
- SAP SD transaction codessapstack.com
- SAP SD transaction codestestingbrain.com
- SD enterprise structure: definitions and assignmentsmohanranga.squarespace.com
- Incompletion log (OVA2, V.02)tutorialspoint.com
- Schedule line categories (VOV6, VOV5)guru99.com
- SD tax determination (OVK1)guru99.com
- Rebate agreements become condition contracts (WCOCO)consilio-gmbh.de
- SAP R/2en.wikipedia.org