SoftTech AI Registry
SAP · SAP S/4HANA Cloud

Create Sales Orders – AI-Assisted Extraction

SAP Fiori app F8947 in which an internal sales representative uploads a customer purchase order file; the system uses SAP Document AI (Embedded Edition) to extract the file contents into a newly created sales order request and to propose values for its fields. Converting the request into an actual sales order is a separate user action.

Recorded characteristics

Function
SAP documents app F8947 ("Create Sales Orders - AI-Assisted Extraction") as follows: "With this app, you as an internal sales representative can create sales orders from purchase order files. After a file is uploaded, the system automatically extracts file information into a sales order request and proposes values for sales order request fields (for example, by determining the sold-to party based on extracted data). You can later convert the sales order request into a sales order." The documented sequence is: purchase order file uploaded by the user -> the system creates a sales order request (one per uploaded file, with the uploaded file attached) and starts data extraction using SAP Document AI (Embedded Edition) -> the system proposes values for sales order request fields and checks data completeness -> the user reviews, corrects or completes the request, and may simulate order creation -> the user explicitly creates the sales order from the request. SAP defines a sales order request as "basically a sales order draft that serves the purpose of preparing a sales order. It represents a preceding document of the sales order, but is not part of the document flow from the business perspective." The AI-assisted extraction step populates that request; SAP does not document the AI creating the final sales order.
Data access
Input: a customer purchase order file uploaded by the internal sales representative in PDF, JPG, JPEG, TIF, TIFF or PNG format. A company code must be entered before upload (auto-filled where a unique default exists in SAP Fiori launchpad user settings). SAP Document AI stores the document files received from the app; they can be deleted manually in the SAP Document AI workspace. Directly extracted from the file (per SAP's predelivered proposal rules): requested quantity; unit-of-measure data (extracted value, optionally with an ISO value); purchase order number; purchase order date; purchase order item; requested delivery date (header and item); extracted sold-to party address (name plus full address); extracted ship-to party address; extracted product-related data (extracted product, extracted customer material, extracted description); extracted currency. Determined or proposed by the system from extracted data rather than read literally from the file: sold-to party (from order creation history, or from customer master); ship-to party (same two routes); product (from order creation history, or from product/customer material master); sales area (sales organization/distribution channel/division, determined from sold-to party, product data, or ship-to party); unit of measure (mapped from extracted/ISO value against Check Units of Measurement configuration); customer reference (copied from extracted purchase order number); customer reference date (from extracted purchase order date); customer material; document currency (extracted currency converted to an internal key, otherwise derived from the company code). Sales order type is defaulted to the SAP-predelivered value OR (standard order). No predelivered proposal rules exist for sales group or sales office. Master-data determination uses exact or fuzzy searches of extracted data and validates candidate records against existing sales order request data; where multiple records are validated, the top record is proposed and the others are persisted as potential records for use in the BAdI.
Actions
Can take actions
External actions
Unknown
Human confirmation
Conditional
Permission basis
Not established
Administrative control
Documented controls: - Scope items: SAP names scope item 7ED as a prerequisite on the app page, and the 2602 What's New entry records scope item 7TC (Integration with SAP Document AI); setting up 7TC requires the SAP_BR_ADMINISTRATOR business role and an active 7TC scope item, checked via Manage Your Solution or SAP Central Business Configuration. - Schema activation: the Extraction of Purchase Order (SALES_ORDER_REQUEST_EXTRACTION) schema must be activated in the Manage Document AI Schema Registration Subscriptions app (F8996), and "must be activated in each tenant where you want to use the Create Sales Orders - AI-Assisted Extraction app". - Access control: the IAM app Create Sales Orders - AI-Assisted Extraction (F8947_TRAN) must be assigned; instant learning additionally requires business catalog Sales - AI-Assisted Extraction for Sales Order Creation (SAP_SD_BC_SO_DOCUMENTAI_PC) and Document AI workspace write access granted through Identity Authentication on SAP BTP, where administrators can refine authorization policies with restrictions (for example by document type or company code). - Key-user configuration: the configuration activity Adapt Settings by Company Code enables a duplicate-file check and defines whether the ship-to party is required for order creation; organizational assignment of sales organization to company code is maintained in Set Up Organizational Structure. - Extraction tuning: with Admin or SchemaAdmin authorization in the SAP Document AI workspace, the standard Sales_Order_Request schema (version 1) processing settings allow changing the large language model used for document processing and adding tailored prompts for the schema or individual fields; only text processing mode is allowed. Reviewers can correct extractions in the workspace, with instant learning applied by default on confirmation. - Extensibility: custom fields on Sales: Sales Order Request and Sales Order Request Item, and custom logic through BAdIs/behaviour definition extensions.
Default state
Disabled
Availability
SAP S/4HANA Cloud Public Edition. The What's New entry records the app as new and "Valid as Of SAP S/4HANA Cloud Public Edition 2602", with application component SD-SLS-IMP-DOX (Sales Document Creation Based on Unstructured Data), no functional localization, and scope item 7TC. The app documentation is currently published under version 2608 (latest). Supported device types are desktop and tablet.
Licensing
SAP states: "To access this generative AI feature within SAP S/4HANA Cloud Public Edition, an additional entitlement and authorization may be required. Please consult your SAP account executive for more information." Setting up integration with SAP Document AI requires a purchased SAP Document AI licence, an SAP BTP global account with a Cloud Foundry subaccount, an SAP Cloud Identity Services tenant, a service instance of SAP Document AI, embedded edition, and a subscription to the SAP Document AI workspace. SAP S/4HANA Cloud Public Edition and SAP BTP must use the same Identity Authentication service instance, and the tenant-to-service-instance mapping must be 1:1. No pricing is documented here.
External model or provider
SAP Document AI (Embedded Edition). SAP states the AI-Assisted Extraction app uses SAP Document AI (Embedded Edition) for data extraction, whereas Create Sales Orders - Automatic Extraction uses SAP Document AI (Base Edition), and that the Embedded Edition "supports more languages and smarter document processing capabilities" than the Base Edition. SAP does not identify an underlying foundation model or model provider; it documents only that a schema administrator can change the large language model used for document processing in the Sales_Order_Request schema's processing settings. The underlying model is therefore not established.
Limitations and uncertainty
- The record covers extraction into, and population of, a sales order request. It does not cover creation of the final sales order, which SAP documents as a separate user action ("You can later convert the sales order request into a sales order"), possible only when request data is complete and no failed simulation stands. - The registry distinguishes directly extracted values from values determined or proposed by the system (for example sold-to party, product and sales area are determined from order creation history or master data, not copied from the file). - Extraction accuracy is not guaranteed: SAP publishes guidance on improving it (schema tuning, prompts, instant learning), documents a retry for failed extraction, and notes the extraction service "may occasionally mix up the extracted product and extracted customer material". If no unit of measure can be extracted or determined, both requested quantity and UoM are left empty. SAP recommends double-checking the ship-to party, which is not a required field by default and, if left empty, may differ in the created sales order from the purchase order file. - Incomplete requests must be edited manually by the user; refreshing a request from new extractions deletes all existing data including manual changes. - Supported upload formats are documented (PDF, JPG, JPEG, TIF, TIFF, PNG). SAP does not publish an app-specific language list; the Embedded Edition language page is shared with the Premium Edition and its table is introduced as the languages the premium edition service plan supports, so an app-specific supported-language list is not established. - Runtime identity is not established: SAP documents the human authorizations required (IAM app F8947_TRAN, business catalog SAP_SD_BC_SO_DOCUMENTAI_PC, BTP authorization policies) but does not state under which identity the extraction service itself operates. - External action capability is recorded as unknown: the app operates within SAP S/4HANA Cloud, and while SAP Document AI stores the uploaded document files, SAP does not document this capability performing a state-changing action in a separate external business system. - Only a limited number of sales order types can be created through the app.

Evidence