O2C 404 · AT THE KEYBOARD
O2C Configuration Workbench
Configure and prove one standard stocked-product order from sales-area determination through delivery, post goods issue, billing, and the customer open item.
WORKBENCH ENVELOPE
One minimum configuration spine
Extensions stay outside the spine until the standard stocked-product flow posts and reconciles.
Included
- One company code, sales area, delivering plant, shipping point, customer, and stocked material
- Standard sales order, item, schedule line, pricing, ATP, delivery, PGI, billing, and FI integration
- Classic SAP GUI transactions plus S/4HANA persistence and credit-management notes
- Configuration transport boundaries and transactional proof
Not included yet
- Advanced returns, third-party, intercompany, make-to-order, free goods, listing/exclusion, substitutions, rebates, and packing design
- Country-specific tax procedures, statutory forms, and localization
- Advanced ATP product allocation and specialized warehouse execution
- Custom routines, exits, BAdIs, interfaces, roles, migration, and production cutover
CONFIGURATION WORKBENCH
Build the organizational path
The sales order can identify who sells, which company records the value, which plant fulfils, and which shipping point executes.
SPRO / IMG path
Enterprise Structure → Definition → Sales and Distribution → Define, copy, delete, check Sales Organization / Distribution Channel / Division
Enterprise Structure → Assignment → Sales and Distribution → Assign Sales Organization to Company Code; Set Up Sales Area; Assign Sales Organization–Distribution Channel–Plant
Enterprise Structure → Definition → Logistics Execution → Define, copy, delete, check Shipping Point
Enterprise Structure → Assignment → Logistics Execution → Assign Shipping Point to Plant
Transactions
OVX5Define sales organizationOVXI / OVXBDefine distribution channel / divisionOVX3 / OVXGAssign company code / set up sales areaOVX6NAssign delivering plant to sales organization and channelOVXD / OVXCDefine shipping point / assign it to plantTVKOTVTWTSPATVTATVKWZTVSTMaintain in this order
- Create or copy the project sales organization, distribution channel, and division. Confirm currency, calendar, and statistics settings rather than accepting inherited values.
- Assign the sales organization to the company code, create the sales-area combination, and assign the delivering plant to the sales organization and distribution channel.
- Define the shipping point and assign it to the plant. Do not describe OVXC as a sales-area assignment.
- Record every organizational key in a dependency sheet before extending customer and material master data.
The intended sales area is available, the material can use the delivering plant, and the order item can determine organizational context without manual structural overrides.
If it fails, check here first
- Sales area unavailable: inspect TVTA and the sales-organization/company-code relationship.
- Plant cannot deliver: inspect TVKWZ for the sales organization and distribution channel combination.
- Shipping point remains blank: first prove plant, shipping condition, and loading group before changing OVL2.
CONFIGURATION WORKBENCH
Prepare executable master data
Customer, material, price, stock, and accounting views contain the inputs that configuration expects.
SPRO / IMG path
Cross-Application Components → SAP Business Partner → Business Partner → Basic Settings → Number Ranges and Groupings
Cross-Application Components → Master Data Synchronization → Customer/Vendor Integration → Business Partner Settings → Settings for Customer Integration
Logistics – General → Business Partner → Customers → Control → Define Account Groups and Field Selection
Logistics – General → Material Master → Basic Settings → Material Types
Transactions
BPMaintain BP roles, customer company-code data, and sales-area dataMM01 / MM02Create or extend material sales, plant, MRP, valuation, and accounting viewsVK11 / VK13Create / display pricing condition recordsMMBEConfirm unrestricted stockBUT000KNA1KNVVKNVPMARAMVKEMARCMBEWMaintain in this order
- Extend the business partner to the customer roles required by the target release, then maintain company code, reconciliation account, payment terms, sales area, partner functions, shipping condition, and tax classifications.
- Extend the material to sales organization/channel, delivering plant, storage, MRP, valuation, and accounting views. Maintain item-category group, loading group, checking group, tax classification, and valuation class.
- Create a controlled price record and confirm its validity dates, currency, unit, scale, and release status.
- Load or post known unrestricted stock and record the expected material valuation before running the integrated test.
The payer has financial and sales data, the material is sellable and deliverable from the plant, a valid condition record exists, and the test quantity is visible as unrestricted stock.
If it fails, check here first
- Customer rejected in VA01: check BP role synchronization, sales-area extension, partner functions, and company-code data.
- Material rejected or plant absent: check MVKE/MARC extensions, sales status, and plant assignment.
- Price or ATP missing: distinguish missing master data from incorrect Customizing before editing procedures.
CONFIGURATION WORKBENCH
Control the sales document
The order type, item category, and schedule line determine a delivery-relevant, requirements-relevant standard item.
SPRO / IMG path
Sales and Distribution → Sales → Sales Documents → Sales Document Header → Define Sales Document Types
Sales and Distribution → Sales → Sales Documents → Sales Document Item → Define Item Categories; Assign Item Categories
Sales and Distribution → Sales → Sales Documents → Schedule Lines → Define Schedule Line Categories; Assign Schedule Line Categories
Sales and Distribution → Sales → Maintain Copying Control for Sales Documents
Transactions
VOV8Configure sales document typeVOV7 / VOV4Configure / determine item categoryVOV6 / VOV5Configure / determine schedule line categoryVN01Maintain SD document number rangesVTAAQuotation-to-order copy control when quotation is in scopeTVAKTVAPTVEPTVEPZT184TVCPAMaintain in this order
- Copy the closest standard order type and review number range, document category, reference requirements, delivery and billing blocks, pricing-procedure indicator, credit settings, and requested-delivery-date behavior.
- Copy the appropriate item category and explicitly decide pricing, schedule-line permission, delivery relevance, billing relevance, returns behavior, and completion rules.
- Copy the schedule line category and decide ATP, transfer of requirements, movement type, delivery relevance, and procurement behavior.
- Maintain item-category and schedule-line determination, then test the derived result rather than forcing categories manually in VA01.
The order derives the intended item and schedule-line categories, accepts the customer and material, produces a confirmed schedule, and becomes eligible for delivery.
If it fails, check here first
- Wrong item category: inspect sales document type, material item-category group, usage, and higher-level item in VOV4.
- No schedule line: confirm the item category allows schedule lines and inspect VOV5 determination.
- Order cannot progress: inspect rejection, blocks, incompletion, credit status, and overall/item delivery status before copy control.
CONFIGURATION WORKBENCH
Make partners and completeness enforceable
The correct sold-to, ship-to, bill-to, and payer are determined, while missing business-critical data blocks the intended follow-on step.
SPRO / IMG path
Sales and Distribution → Basic Functions → Partner Determination → Set Up Partner Determination
Sales and Distribution → Basic Functions → Log of Incomplete Items → Define Incompletion Procedures
Sales and Distribution → Basic Functions → Log of Incomplete Items → Assign Incompletion Procedures
Transactions
VOPANDefine partner functions, procedures, and assignmentsOVA2Define incompletion proceduresVUA2 / VUP2 / VUE2Assign procedures to header, item, and schedule lineVUA4 / VUP4Assign delivery incompletion proceduresTPARTPAERTKUPATVUVTVUVFTVUVSVBUVMaintain in this order
- Define the partner procedure and mark which functions are mandatory, changeable, or sourced from another partner.
- Assign the partner procedure to the customer account group and sales document type; confirm that BP partner data provides the expected source relationships.
- Define incompletion groups and fields with the correct screen and status group. Decide whether missing data blocks delivery, billing, pricing, or only warns.
- Assign procedures at header, item, schedule-line, delivery-header, and delivery-item levels only where the business consequence is understood.
All four core partners are explainable. Removing a mandatory test field creates the intended incompletion entry and blocks only the designed follow-on action.
If it fails, check here first
- Partner missing: separate customer-master partner assignment from document-procedure determination.
- Field appears incomplete but does not block: inspect the status group and its delivery/billing relevance.
- Unexpected incompletion entry: verify table/field, screen assignment, and whether the field is populated at header or item level.
CONFIGURATION WORKBENCH
Build and prove pricing
The order derives a pricing procedure and explains each price, discount, freight, and tax component through condition analysis.
SPRO / IMG path
Sales and Distribution → Basic Functions → Pricing → Pricing Control → Define Condition Tables
Sales and Distribution → Basic Functions → Pricing → Pricing Control → Define Access Sequences; Define Condition Types
Sales and Distribution → Basic Functions → Pricing → Pricing Control → Define and Assign Pricing Procedures
Sales and Distribution → Basic Functions → Taxes → Define Tax Determination Rules
Transactions
V/05 / V/07Condition tables / access sequencesV/06 / V/08Condition types / pricing proceduresOVKKPricing procedure determinationVK11 / VK12 / VK13Create / change / display condition recordsOVK1 / OVK3 / OVK4Tax category and customer/material tax-classification valuesT681T682IT685AT683ST683VKONHKONPPRCD_ELEMENTSMaintain in this order
- Copy or define the condition table and access sequence only when standard keys cannot express the requirement. Put the most specific valid access before broader fallbacks.
- Copy the condition type and review calculation type, plus/minus, manual-entry rules, scales, validity, exclusion, account key, and whether it contributes to the net value.
- Copy the pricing procedure, sequence the condition types, and maintain requirements, subtotals, statistical indicators, account keys, and mandatory conditions.
- Maintain OVKK for sales area + document pricing procedure + customer pricing procedure, create a controlled VK11 record, and use condition analysis to prove every access.
The intended procedure is determined, the expected access finds the valid record, mandatory conditions are present, tax is explainable, and net value reconciles.
If it fails, check here first
- No pricing procedure: inspect sales area, VOV8 document pricing procedure, BP customer pricing procedure, and OVKK.
- Condition not found: inspect access sequence, key values, validity, release status, scales, exclusion, and the condition-analysis message.
- Billing value changes unexpectedly: inspect VTFL pricing type and whether pricing is copied or redetermined.
CONFIGURATION WORKBENCH
Configure ATP and transfer of requirements
The order checks the intended supply elements, produces defensible confirmed dates and quantities, and transfers demand to planning.
SPRO / IMG path
Sales and Distribution → Basic Functions → Availability Check and Transfer of Requirements → Availability Check → Availability Check with ATP Logic or Against Planning
Sales and Distribution → Basic Functions → Availability Check and Transfer of Requirements → Transfer of Requirements → Determination of Requirements Types / Classes
For activated aATP: Cross-Application Components → Advanced Available-to-Promise → Product Availability Check
Transactions
OVZ2 / OVZ9Checking group behavior / scope of availability checkVOV6Schedule-line ATP and requirements settingsOVZI / OVZG / OVZHRequirements-type and requirements-class controlMM02Maintain material checking group on MRP 3CO09 / MD04Inspect ATP situation / stock-requirements listT441VTMVFTVEPTVEPZT459KT459AVBBEMaintain in this order
- Decide whether the scenario uses classic ATP or activated aATP before copying settings; their IMG placement and available scope options differ by release.
- Maintain the checking group and the order checking rule scope, including stock, receipts, requirements, safety stock, replenishment lead time, and special scenarios.
- Enable ATP and transfer of requirements in the schedule line, then verify requirements-type and requirements-class determination.
- Maintain the material checking group and test with known stock plus a competing requirement so the confirmation result is observable.
The requested and confirmed quantities differ only for explainable supply reasons, and the sales requirement appears in planning with the intended class.
If it fails, check here first
- No ATP check: inspect material checking group, schedule-line ATP flag, item/schedule determination, and activated aATP status.
- Wrong confirmation: inspect OVZ9 scope, plant, checking rule, replenishment horizon, competing requirements, and unit/date conversion.
- No planning requirement: inspect transfer-of-requirements flag and requirements-type/class determination.
Release-sensitive: SAP S/4HANA 2023 introduced ATP-category changes for activated advanced ATP scopes. Reconfirm OVZ2/OVZ9 behavior after an upgrade rather than copying screenshots from an older release.
CONFIGURATION WORKBENCH
Connect SD to SAP Credit Management
Sales orders and deliveries call the intended check rule, update exposure, and create an explainable block or documented decision.
SPRO / IMG path
Financial Supply Chain Management → Credit Management → Credit Risk Monitoring → Credit Limit Check → Define Checking Rules
Financial Supply Chain Management → Credit Management → Integration with Accounts Receivable Accounting and Sales and Distribution → Integration with Sales and Distribution → Assign Sales Documents and Delivery Documents
Sales and Distribution → Basic Functions → Credit Management / Risk Management → Credit Management → Define Automatic Credit Control
Transactions
BP (role UKM000)Maintain credit profile, segment, limit, risk class, and check ruleOVAK / OVADActivate credit check and credit group for sales / delivery documentsOVA8Define automatic credit control and SAP Credit Management activationVA01 / VKM1Trigger the check / review blocked sales documents where the classic worklist is enabledUKMBP_CMSUKMBP_CMS_SGMVBAK-CMGSTVBAK-CMPS_CMLIKP-CMGSTMaintain in this order
- Configure the credit segment, check rule, check steps, reactions, horizons, and overdue or maximum-document-value parameters required by policy.
- Maintain BP credit profile and segment data, including limit, risk class, and check rule. Confirm that the payer resolves to the intended credit account.
- Assign the sales and delivery document categories and credit groups in OVAK/OVAD; activate SAP Credit Management in OVA8 with the supported reaction.
- Run one passing and one failing order, then prove exposure update, block status, release authority, and recheck behavior after a value change.
A passing order updates exposure and proceeds. A failing order shows the failed step, sets the designed status/block, and can be released only through the governed path.
If it fails, check here first
- No check triggered: inspect OVAK/OVAD, OVA8 activation, credit control area/segment determination, payer/credit account, and BP role data.
- Unexpected failure: inspect the check rule and step parameters, exposure composition, overdue items, horizon, currency, and exceptions.
- Order released but still blocked: inspect recheck timing, delivery credit group, document status, and whether a new value or date change retriggered the check.
Release-sensitive: S/4HANA uses SAP Credit Management integration; simple credit checks are no longer the supported design. Apps and blocked-document transactions vary by release and UI scope.
CONFIGURATION WORKBENCH
Configure delivery and post goods issue
The confirmed order creates the correct delivery, supports warehouse completion, posts movement 601 or the designed equivalent, and records inventory and COGS.
SPRO / IMG path
Logistics Execution → Shipping → Basic Shipping Functions → Shipping Point and Goods Receiving Point Determination
Logistics Execution → Shipping → Deliveries → Define Delivery Types; Define Item Categories for Deliveries
Logistics Execution → Shipping → Copying Control → Specify Copy Control for Deliveries
Materials Management → Valuation and Account Assignment → Account Determination → Account Determination Without Wizard → Configure Automatic Postings
Transactions
OVSF / OVSX / OVL2Shipping conditions / loading groups / shipping-point determination0VLK / 0VLPDelivery type / delivery item categoryVTLASales-order-to-delivery copy controlOBYCAutomatic inventory offset account determinationVL01N / VL02N / VL03NCreate / change and PGI / display deliveryTVSTZTVLKTVLPTVCPLT030LIKPLIPSMATDOCACDOCAMaintain in this order
- Maintain shipping condition, loading group, and OVL2 determination for delivering plant + shipping condition + loading group → shipping point.
- Copy the delivery type and item category, then review number range, order requirements, picking/packing relevance, storage-location behavior, movement type, and incompletion.
- Maintain VTLA header and item copy control, including requirements, quantity rules, data-transfer routines, and status update.
- Validate OBYC for the actual valuation grouping, valuation class, transaction key, and account modifier produced by the movement. Treat GBB/VAX or VAY as observed outcomes, not universal constants.
The delivery copies the confirmed quantity, PGI reduces the intended stock, MATDOC records the movement, and ACDOCA shows balanced inventory and COGS impact.
If it fails, check here first
- No delivery: inspect due date, confirmation, delivery relevance, blocks, incompletion, and VTLA requirement routines.
- No shipping point: inspect plant, BP shipping condition, material loading group, and OVL2 combination.
- PGI/account error: inspect delivery status, stock/batch/serial, posting period, movement/account modifier, valuation class, OBYC, and G/L extension.
CONFIGURATION WORKBENCH
Configure billing and financial proof
The goods-issued delivery becomes billing due, creates the intended invoice, posts revenue/tax and the customer receivable, and leaves a traceable open item.
SPRO / IMG path
Sales and Distribution → Billing → Billing Documents → Define Billing Types
Sales and Distribution → Billing → Maintain Copying Control for Billing Documents → Delivery Document to Billing Document
Sales and Distribution → Basic Functions → Account Assignment/Costing → Revenue Account Determination
Financial Accounting → Accounts Receivable and Accounts Payable → Business Transactions → Incoming Payments
Transactions
VOFAConfigure billing typeVTFLDelivery-to-billing copy control and pricing typeVKOARevenue account determination recordsVF04 / VF01 / VF03Billing due list / create / display billing documentFB03 / FBL5N / F-28Display FI document / customer items / post and clear incoming paymentTVFKTVCPFT683ST685KONPVBRKVBRPBKPFACDOCAMaintain in this order
- Copy the billing type and review document category, number range, posting block, cancellation type, account-determination procedure, output approach, and FI posting behavior.
- Maintain VTFL header and item control, including source/target types, requirements, quantity rule, pricing type, data transfer, and billing-quantity basis.
- Maintain revenue account determination procedure and VKOA records for the chosen access using chart of accounts, sales organization, customer/material account-assignment groups, and account key.
- Create billing, inspect the accounting document and open item, then post a controlled incoming payment and prove the clearing document.
Billed quantity equals PGI quantity, pricing and tax reconcile, the FI document balances customer/revenue/tax, the open item appears, and payment clearing closes it.
If it fails, check here first
- Not billing due: inspect PGI status, billing relevance, billing block, billing date, and VTFL requirements.
- Unexpected split/value: inspect split analysis, payer and header fields, VTFL pricing type, copied conditions, tax, exchange rate, and quantity basis.
- No accounting document: inspect posting status and log, VKOA access, account keys, customer reconciliation account, tax account, G/L extension, and posting period.
Release-sensitive: Output configuration differs materially between classic NAST/NACE and S/4HANA Output Management. Choose one release-appropriate branch and document it separately; do not mix both in the minimum spine.
TRANSACTIONAL PROOF
One configuration chain, one reconciled transaction
Settings are not evidence. Run the complete chain and reconcile every successor.
Controlled test data
- BP customer extended to company code and sales area with payer, shipping condition, tax, payment terms, and reconciliation account
- Material extended to sales, plant, MRP, valuation, and accounting views with item-category group, loading group, checking group, and valuation class
- Valid price/tax records, known unrestricted stock, open posting periods, and expected G/L accounts
- 01VA01 / VA03
Order, item, schedule line, price, ATP, partners, shipping point, credit, and incompletion are explainable.
- 02VL01N / VL02N
Delivery copies the intended quantity; pick/pack completes and PGI reduces the expected stock.
- 03Material document / FB03
Movement and accounting references show the correct plant, valuation, inventory credit, and COGS debit.
- 04VF04 / VF01 / VF03
Billing quantity and value reconcile to fulfilment; output and accounting status are complete.
- 05FBL5N / F-28
Customer receivable is visible, payment posts, and the invoice clears through a traceable clearing document.
TECHNICAL REFERENCES
Verify against the target release
These SAP product-assistance pages anchor the configuration concepts. The IMG in the target system remains authoritative for its installed release and scope.
Apply the workbench inside workshops, testing cycles, cutover decisions, defects, and stabilization.