SAP Sales Area Elements and Document Data

Elements of a Sales Area

• A sales area consists of a Sales Organization, Distribution Channel, and Division.

Levels in a Sales Document

• The levels in a sales document are the sales document header, item, and schedule line.

Sources of Information for Document Data in Sales

• Master data and Customizing are possible sources of information for document data in Sales.

Linking SAP Business Partner and Customer Master Data

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

Deriving Incoterms in a Sales Order

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

Customer-Vendor Integration Requirements

• Setting up an Account Group/Number Range Mapping is necessary for the Customer-Vendor Integration.

SAP Business Partner Characteristics

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

Sales Document Type Control

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

Requested Delivery Date

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

Item Category Control

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

Bill-of-Material (BOM) Considerations

• When determining the sub-items of a BOM, the system needs to know the item category of the higher-level item.

Elements to Determine an Item Category

• An 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

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

Schedule Line Category Usage

• A schedule line category can be used even if goods are not delivered, such as for a service item.

Elements to Determine the Schedule Line Category

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

Blocks in a Sales Order

• A billing block can be set on the order header and item level; a delivery block can be set on the order header and schedule line level.

Defining Business Data at Item Level

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

Canceling an Order

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

Limiting Choices for Rejection Reasons

• Assigning reasons to specific sales document types and sales organizations limits the choices for rejection reasons in sales processing.

Gaining Information on Copied Elements

• The process flow and the document flow contain information on the elements copied from the source document to the target document.

Copying Control Maintenance

• 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 Sales Documents with Reference

• A sales document can be created with reference to another existing sales document only if copying control is set up for it.

Configuration Options at the Header Level of Copy Control

• In header copy control, it is possible to specify copying requirements and a complete reference indicator.

Partner Function Procedure

• In a partner function procedure, it can be determined which partner functions have to be entered (mandatory functions).

Business Functions for Multiple Address Handling

• The 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.

Elements that can be Configured 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.

Maintenance of Business Rules

• Within maintaining 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.
• When an Include condition is true, the result of the row is also returned or evaluated further.

Location of Output Parameters in SAP S/4HANA Output Control

• The necessary output parameters for an output in the SAP S/4HANA output control are set in several decision tables.

Output Determination in Sales Documents

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

SAP S/4HANA Output Control Support

• SAP S/4HANA output control supports the processing of business transactions by providing the ability to issue outputs related to sales documents, informing business partners that do not have access to sales documents, along with the feature to automatically print an order confirmation when saving the order.

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

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

Characteristics of Decision Tables

• Decision tables consist of condition and result columns
• Decision tables determine various output parameters, such as output type, recipient, form template
• It’s possible to add additional condition columns to a decision table.

Aspects of Determination Steps

• Entries are processed from left to right and top to bottom in each decision table.
• It's possible for the processing of a determination step to output multiple output parameters

Requirements for Issuing an Order Confirmation

• A mandatory requirement for issuing an order confirmation based on an order is that the order has to have output parameters

Aspects of Output Types

• The standard delivery covers all requirements for output types
• The output type describes the deed to interact with business partners based on sales documents.

Access Sequence Statements

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

Text Determination Analysis and Customization

• Text determination analysis enables analysis of the origin of texts in sales documents or failed text transfers
• It allows direct navigation to text control customization.

Basic Ideas of Text Control

• Information saved needs to be in the form of texts in the sales document.
• Texts are maintained in text types or text IDs

Connection regarding the Transfer of Texts

• When copied to sales documents, texts can be displayed and edited in a pop-up window as text can be duplicated or referenced during takeover.

Text Storage in Sales Documents

• Texts can be stored in the sales document header and item

Correct Text Control Aspects

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

Prerequisite for Text Entry in Sales Document Header

• Entering a text requires at least one text type (or TEXT ID).
• A text determination procedure must be assigned to the sales document type used to create the sales document

Document Creation in SAP S/4HANA Sales

• A step in a process in SAP S/4HANA Sales typically results in a document being created in the system.

Types of Billing Documents in SAP S/4HANA

• Credit memos, debit memos, and invoices are examples of billing documents.

Finding Confirmed Dates for a Procured Service

• Confirmed dates can be found on the schedule line level of a sales order for a procured service.

Standard Levels Available in a Sales Order in SAP S/4HANA

• The header, item, and schedule line are the standard levels available.

Scheduling Agreement Characteristics

• A scheduling agreement contains fixed delivery dates and quantities.

Quantity Contract Characteristics

• A quantity contract lacks schedule lines and delivery quantities.
• It can include a value limit.

Item Category Determination for General Value Contract

• Item category determination for the General value contract (WK1) is done with the item usage (VCTR).

Options to Limit Products in a Value Contract

• The list of products to buy with a value contract can be limited by assigning an assortment model or a product hierarchy.

Statements Regarding a Value Contract (Sales Document type WK1)

• The specific value contract says that the customer must buy goods and services for a fixed target amount during a period.
• Release orders are required

"Incompletion Messages" Field Determination

• Whether an incomplete sales document of this type can be saved or not is the determination.

Incompletion Procedure Requisites

• An incompletion procedure can be set up with any field requiring population in the sales document.

Accessing the Incompletion Log for a Sales Order

• The incompletion log can be accessed manually using the menu and automatically when saving an incomplete sales order.

Steps when working with incomplete sales order documents

• Enter selection criteria on the selection screen
• Call up the list of incomplete documents
• Access an incomplete document
• Complete an incomplete document
• Return to the list of incomplete documents

Factors Affecting Displaying a Sales Document type in a Document field

• The status group assigned to the field in the incompletion procedure is not filled out.

An Incompletion Procedure Options

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

Incompletion Procedure

• The system can go directly from the incompleition log to views which you can then edit the incomplete data,
• The sales documents types of the incomplation messages control can be saved or not.