certificacion sd configuring

Sales Area Elements

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

Sales Document Levels

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

Sources of Document Data in Sales

• Possible sources of information for document data in Sales are master data and customizing.

SAP Business Partner and Customer Master Data

• Customer-Vendor Integration needs to be set up to link the SAP business partner and customer master data.
• The incoterms in a sales order are derived from the sold-to party.
• You have to set up an Account Group/Number Range Mapping for the Customer-Vendor Integration.
• A Business Partner is uniquely assigned to one business partner category.

Sales Document Types

• A sales document type controls the number assignment, the default billing type, and the default delivery type.
• The requested delivery date results from the settings in the sales document type.

Item Categories

• The item category controls whether pricing and billing can be carried out.
• When sub-items are determined, knowing the item category of the higher-level item is required.
• An item category is determined by the sales document type, item category group, item usage and item category of the higher-level item.

Schedule Line Categories

• The schedule line category controls the goods movement type and delivery relevance.
• A schedule line category can be used even if goods are not delivered, like for any service item.
• The item category and MRP type determine the schedule line category.

Sales Order Blocks

• 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 the item level allows for creating documents with different business data at the header and item level.
• To cancel an order, a reason for rejection is needed.
• Choices for rejection reasons in sales processing can be limited by assigning reasons to specific sales document types and sales organizations.

Copying Sales Documents

• The process flow and the document flow contain information on what has been copied from the source document to the target document.
• Copying requirements can be maintained in copying control.
• Copying control for sales documents can be configured at the header, item, and schedule line level.
• A sales document can only be created with reference to another existing sales document if it's set up for it in copying control.
• In header copy control, you can specify copying requirements and a complete reference indicator.
• The pricing type field is set at the item level and the proposed schedule line category is defined at the schedule line category.

Partner Functions

• It is possible to determine which partner functions are mandatory.
• Multiple address handling in SAP S/4HANA Sales enables the storage of multiple addresses per customer master record.
• The partner functions and the sources to determine partners can be configured in a partner function procedure.

Output Control

• Examples of output parameters include the Channel, Output Type, and Form Template
• Include and Exclude conditions can be defined when maintaining business rules.
• If an Exclude condition is false, the result of the row is returned or further evaluated.
• When an Include condition is true, the result of the row is also returned or evaluated further.
• Necessary output parameters are set in several decision tables.
• To issue an output in relation to a sales document, determining the output type, the receiver of the output, and the channel of the output is necessary.
• SAP S/4HANA output control supports the processing of business transactions by providing the ability to issue outputs related to sales documents for business partners without sales document access, and also allows an order confirmation to be automatically printed when saving the order.
• Foundational settings when customizing SAP S/4HANA output control include the definition of business rules for output parameter determination, as well as the assignment of custom form templates to the output types.
• Decision tables are used to determine various output parameters such as output type, recipient, form template, and consist of condition and result columns, and allow for adding additional condition columns.
• Entries are processed from left to right and from top to bottom, and it's possible for the processing of a determination step to output multiple output parameters in each decision table.
• A mandatory requirement for issuing an order confirmation is that the sales order requires output parameters.
• The standard delivery covers the entire requirements for output types and the output type describes the deed that is used to interact with business partners based on the sales document.

Text Control

• With an access sequence assigned to a text type in the text determination procedure, the text for this text type can be procured automatically.
• Without an access sequence assigned to a text type in the text determination procedure, text for this text type can be entered during document processing.
• Text determination analysis enables analysis of the texts' origin in a sales document or failed transfers as well as jumping to Customizing of text control.
• SAP S/4HANA text control supports saving information in the form of texts in the sales document and maintaining texts in text types or text IDs.
• Copied texts in sales documents can be displayed and edited in a pop-up window, and text can be duplicated or referenced during takeover.

Texts in Sales Documents

• Texts can be entered in the sales document header and item.
• Text of a text type can be maintained in different languages.
• The sales document may be incomplete if a text type doesn't contain text.
• A data transfer routine can be assigned in an access sequence at an access.
• A prerequisite for entering text in the sales document header is at least one text type (or TEXT ID), and the sales document type has to be assigned to a text determination procedure.

Billing Documents

• A step in a process often leads to a document being created in the SAP S/4HANA Sales system.
• Credit memo, debit memo and invoice are examples of billing documents.

Sales Orders

• Confirmed dates for a procured service are found on the schedule line level of the sales order.
• Header, item, and schedule line make up the standard levels available in a sales order.

Scheduling Agreements & Quantity Contracts

• A scheduling agreement contains fixed delivery dates and quantities.
• Quantity contracts do not contain any schedule lines and delivery quantities, but can contain a value limit.

Value Contracts

• The item category determination for the General value contract (WK1) is done with the item usage (VCTR).
• The lists of purchasable products within a value contract can be limited with an assortment model and/or a product hierarchy.
• Value contracts specify that a customer agrees to purchase a fixed value of goods and services during a defined period and requires release orders.

Incompletion Logs

• The "incompletion messages" field in a sales document type determines whether an incomplete sales document of this type can be saved or not.
• An incompletion procedure can be set up with any field required to be filled out in the sales document.
• Accessing the incompletion log can be done manually via the menu structure within the sales order, or automatically when attempting to save an incomplete sales order.
• The proper sequence of steps when working with incomplete sales documents is: Enter selection criteria -> Call up list of incomplete documents -> Access and Complete the document -> Return to the list.
• Further processing options are dictated by the status group tied to a field in the incompleteness procedure.
• Incompletion procedures can be done on the header, item, and/or schedule line level.
• The incompletion procedure can direct the system to various views where the incomplete data can then be edited.
• In Customizing for sales document types, one can control whether sales documents can be saved via the incompletion messages field.