SAP Sales: Key Elements and Document Structure

Sales Area Elements

• Sales Organization, Distribution Channel, and Division constitute a sales area.

Levels in a Sales Document

• A sales document comprises three levels: header, item, and schedule line.

Sources of Information for Document Data in Sales

• Master data and customizing serve as information sources for document data in Sales.

Linking SAP Business Partner and Customer Master Data

• Customer-Vendor Integration is required to link the SAP business partner and customer master data.

Deriving Incoterms in a Sales Order

• The incoterms in a sales order are derived from the sold-to party.

Customer-Vendor Integration Requirement

• Account Group/Number Range Mapping must be set up for Customer-Vendor Integration.

SAP Business Partner Statement

• A SAP Business Partner is uniquely assigned to one business partner category.

Sales Document Type Control

• A sales document type controls the number assignment, default billing type, and default delivery type.

Requested Delivery Date

• The settings in the sales document type dictates the requested delivery date.

Item Category Control

• The item category controls whether pricing and billing is carried out.

Bill-of-Material Statement

• When determining sub-items, the system requires knowing the item category of the higher-level item.

Elements to Determine Item Category

• Item category can be determined by the sales document type, item category group, item usage and item category of the higher-level item.

Schedule Line Category Control

• Schedule line category controls the goods movement type and delivery relevance.

Schedule Line Categories Statement

• A schedule line category can be used even if you do not deliver goods, like for any service item.

Elements to Determine Schedule Line Category

• Item category and MRP type can be used to determine the schedule line category.

Blocks in a Sales Order

• You can set a billing block on order header and item level, additionally a delivery block on the order header and schedule line level.

Defining Business Data at Item Level

• Defining business data at the item level enable creating documents with different business data at the header and item level.

Canceling an Order

• A reason for rejection needs to be assigned to cancel an order.

Limiting Choices for Reason for Rejections

• Assigning reasons to specific sales document types and sales organizations will limit the choices for reason for rejections in sales processing.

Information on Copied Source Document

• The process flow and document flow have information on what has been copied from the source document to the target document.

Copying Control

• Copying requirements can be maintained in copying control.

Levels Used in Copying Control

• Copying control for sales documents can be configured at the header, item, and schedule line level.

Creating a Sales Document with Reference

• A sales document can be created from another existing sales document if it is set up for it in copying control.

Configuring Header Level of Copy Control

• In header copy control, copying requirements and a complete reference indicator can be specified.

Partner Function Procedure

• You can determine which partner functions have to be entered (mandatory functions).

Purpose of Business Functions for Multiple Address Handling

• Purpose of the business functions for multiple address handling in SAP S/4HANA Sales is to enable the storage of multiple addresses per customer master record.

Configuring Elements in a Partner Function Procedure

• Partner functions and the sources to determine partners can be configured.

Examples of Output Parameters

• Examples of output parameters include the Channel, Output Type, and Form Template.

Statements Concerning the Maintenance of Business Rules

• Include and Exclude conditions can be defined.
• If an Exclude condition is false, the result of the row is returned or the row is further evaluated.
• If an Include condition is true, the result of the row is also returned or evaluated further.

Location of Output Parameters for an Output Set

• The necessary output parameters for an output are set in several decision tables.

Determining Output in Relation to a Sales Document

• The output type, receiver, and channel must be determined to issue an output in relation to a sales document.

SAP S/4HANA Output Control Support

• SAP S/4HANA output control supports outputs in relation to sales documents keeping informed the business partners who do not have access to the sales document and enables an order confirmation to be automatically print when saving the order.

Fundamental Settings in Customizing of SAP S/4 HANA Output Control

• Foundational settings include the definition of business rules for output parameter determination and the assignment of custom form templates to the output types.

Statements in Relation to Decision Tables

• Decision tables consist of condition and result columns.
• Decision tables are used to determine the various output parameters
• It's possible to add additional condition columns.

Statements Correct with Respect to Determination Steps

• In each decision table, the entries are processed from left to right and from top to bottom.
• It is possible for the processing of a determination step to output multiple output parameters

Mandatory Requirement for Issuing an Order Confirmation

• A mandatory requirement for issuing an order confirmation is that the order has output parameters.

Statements Correct in Relation to Output Types

• The standard system covers all requirements for output types.
• An output type describes the deed to interact with business partners.

Access Sequence Statements

• If an access sequence is assigned to a text type, the text for this text type can be procured automatically, and can be entered during document processing
• If no access sequence is assigned to a text type, text for the text type can be entered during document processing.

Statements Regarding Text Determination Analysis

• Determination analysis enables the user to analyze the origin of the texts of a sales document and also links them to customizing.

Basic Ideas of Text Control

• Text control saves information into texts inside of sales documents.
• Text control can maintain texts in text types or text IDs

Connection with the Transfer of Texts

• When texts are copied to the sales document, they can be displayed and edited in a pop-up.
• Text can be duplicated or referenced during takeover.

Text Storage in a Sales Document

• Texts can be entered in the sales document header.
• Texts can be entered in the sales document item.

Statements Related to Text Control

• Text of a text type can be maintained in different languages.
• If a text type does not contain a text, the sales document may be incomplete.
• A data transfer routine can be assigned in an access sequence at an access.

Prerequisite for Entering Text in Sales Document Header

• At least one text type (or TEXT ID).
• A text determination procedure needs to be assigned to the sales document type.

SAP S/4HANA Sales Process Step

• A step leads to a document being created.

Examples of Types of Billing Documents

• Credit memo, debit memo and invoice are all examples of types of billing documents in SAP S/4HANA.

Confirmed Date for a Procured Service

• The confirmed date can be found on schedule line level.

Standard Levels Available in a Sales Order

• Header, item, and schedule line are the standard levels.

Scheduling Agreement Statement

• Scheduling agreement contains fixed delivery dates and quantities.

Quantity Contracts

• A quantity contract does not contain any schedule lines and delivery quantities.
• A quantity contract can also contain a value limit

Item Category Determination for General Value Contract

• Item category determination for WK1 is done with the help of item usage (VCTR).

Options to Limit the List of Products Within a Value Contract

• Assign an assortment model.
• Assign a product hierarchy.

Value Contract Statements

• A value contract specifies that your customer agrees to purchase a fixed value (target amount) of goods and services during a defined period.
• A value contract requires release orders.

"Incompletion Messages" Field in a Sales Document Type

• Determines if an incomplete message type can be saved.

Incompletion Procedure

• An incompletion procedure can be set up with any field you require to be filled out in the sales document.

Ways to Access the Incompletion Log for a Sales Order

• Manually via the menu structure.
• Automatically, when trying to save an incomplete sales order.

Correct Sequence of Process Steps Working with Incomplete Sales Documents

• Enter selection criteria on the selection screen, call up the list of incomplete documents, access an incomplete document, complete an incomplete document, and return to the list of incomplete documents.

Determination of Further Processing Options for Document Field

• The status group assigned to the field determines what further processing options are available.

Document Levels for Fields

• The procedure can be done on header, item and/or schedule line level.

Setting up the Incompletion Procedure

• You can set up the incompletion procedure, so the system goes directly from the incompletion log to various views to edit the incomplete data, by setting up the screens/views in Customizing.

Configuring Incompletion Messages Field

• Through Customizing, you can control whether incomplete sales documents can be saved or not.