VA01 (Create Sales Order) TCode in SAP

An agreement between a seller and a customer concerning the sale and delivery of goods, as well as any services that are associated with these processes, on a specific date, for a specific quantity, and for a specific price.

An agreement between a seller and a customer, where the seller agrees to supply a defined amount of products for an agreed price by a specified date. To facilitate a flexible sales process, SAP Anywhere supports the following three types of sales order: 1) Sell: sell products to a customer; 2) Return: customer returns product(s) to the seller; 3) Exchange: customer exchanges product(s) with the seller.

An order from a customer for the delivery of a material or set of materials.

An order for certain Services issued by PARTNER to SAP for the benefit of a specific End User.

A customer request to the company for delivery of goods or services at a certain time. The request is received by a sales area that is then responsible for fulfilling the contract.

An agreement between an organization and a customer, where the organization agrees to supply a defined amount of products for an agreed price by a specified date.

The process in which the price elements of a priced document are calculated in the Price Calculation service.

The process of defining a price model for subscription products.

A process for determining pricing details. The pricing function defines product-related and business partner-related standard or individual prices for contracts and business partners and also the rules according to which these prices can be combined and passed on.

Component of SAP Retail that groups functions for managing sales prices in connection with the value chain of a trading company. The following functions are part of pricing: Sales price calculation Market-basket price calculation Pricing document processing Pricing worklist Price overview

The process of calculating an amount based on various price components and quantities. &Example& A deal has two price components: an energy price and a transaction fee. During pricing, a total price is calculated based on the individual prices and energy quantity.

Process for determining price information. The system uses condition technique for pricing to determine the relevant price information for a business process from condition records.

The process used to determine prices, discounts, and surcharges. The system determines prices, discounts, and surcharges by applying predefined rules based on relevant data stored in master data like price or discount lists. The system takes into account also prices, discounts, and surcharges that are entered manually.

Method for determination of prices using the conditions technique.

Execution of an ABAP program using a transaction code. The following types of transactions are available: Dialog transactions, report transactions, parameter transactions, variant transactions, and OO transactions. A transaction is started by entering the transaction code in the command field on the standard toolbar or by using the statements CALL TRANSACTION or LEAVE TO TRANSACTION.

Logical R/3 process. From the user perspective, a transaction represents a unit (such as a change to a customer address or the execution of a program). From the ABAP programming perspective, a transaction one of two ways in which a user can call an ABAP program. The other method is to execute an executable program (or report).

Specific type of data containing information about an exchange such as a purchase. It must contain at least a session identifier and an item that is the object of the exchange.

A company card expense transaction imported from the card provider.

The event-controlled representation of a condition that triggers an immediate posting if an activity occurs in the contract, such as a change to the contract master date, or the posting of a payment item.

An activity or event related to a loyalty member, which is processed by the rules defined in the loyalty program.

Any sequence of actions performed by a user that could contribute to providing recommendations to a customer. For example, a business action in which a payment card is used to purchase goods or services, or the clickstream performed by a user to navigate to an item detail page.

The original sales (or other event) data, which includes sub-line data (who it was sold to, amount, and so on) on an order. Used as the basic undata for compensation processing in SAP Commissions.

The classification of postings in various SAP application components based on various business points of view. &EXAMPLE& Enter an invoice Post a goods receipt Create a confirmation Transactions are used to control the data flow between various application components.

A transaction, for example, cost estimation creation, and interest or inflation rate adjustment, for processing obligations, such as asset retirement obligations.

Groups together various accounting documents within a down payment chain. The transaction category determines which documents can be grouped together.

Transactions represent payments that occur at a bank. LMS uses a number of user-definable types of transactions such as anticipated, pending, expected, and actual.

A transaction is a change to an application or change option, which is executed online by a user, or in the background by the system, in a business process. This affects the Application or Change Option business object, and has the following properties: The change creates a new status in the Application or Change Option business object or creates a journal entry in the application or change option journal can be uniquely identified in the business object and in the journal, using the key policy number, contract number and journal number.

(ICM) An umbrella term for the events that may be triggered by a credentials check.

An information packet inside an EDIFACT market message. A transaction, together with the sender and receiver information from the message header, can be processed independently.

An action type that is used to define the URL of an external or internal application.

(MFG-LPO) An event that causes a change in material inventory.

The transaction action step type instantiates a transaction on the Agentry client and defines what screen set to display the transaction instance in.

A single unit payment instruction that will be initiated by a Corporate Subscriber and executed at the Financial Services Subscriber or a single unit statement sent by a Financial Services Subscriber to the Corporate Subscriber.

A business action in which a payment card is used to purchase goods or services. The merchant is credited and money is collected from the cardholder or issuing bank.

A sequence of information exchange treated as a unit so all related data is changed in its entirety. For example, an order transaction involves checking an inventory database, confirming the availability of the item, placing the order, and confirming the order. This ensures that order and inventory data is modified consistently.

(BC-UPG-OCS) Set of software objects delivered together. A delivery comprises one or more delivery components. Deliveries are used both in installations and for support packages, upgrades, pilots, CRTs, and so on. Dependencies can arise between separate deliveries and in these cases only certain combinations of deliveries produce a functioning system.

The process for receiving, sending, or transferring goods, whether inbound or outbound.

A verification notice in the form of a marketing document used to confirm that the shipment of goods or services from the seller to the buyer has occurred.

The arrival of goods at a destination.

The process of determining charges for subscriptions to digital products and collecting the charges in bills.

A subprocess of the overall billing process. Billing takes place after input processing and before output processing. It transfers one or more billing due list items to a billing document.

Automatic billing and invoicing of a company’s services.

A process that checks for items that a customer is expected to pay for within a specified billing period, then triggers open item creation (or open item change, in the case of backdated changes) in an open item management system. The process initially occurs at the end-of-day processing upon account creation, then periodically, to request payment on a loan item.

Function that can be used to settle tax receivables (or submissions and charges receivables). In the first step for this, billing documents are created containing the amount of the open receivable and, if applicable, interest due and penalty charges. Invoicing and posting documents are then created from the billing documents in Contract Accounts Receivable and Payable.

Function used to bill for the utility services provided by a utility company.

Any primary window in a session or the total sum of the content of a window in Microsoft Windows that represents an SAP system.

Each primary window in a session.

A Screen is the UI piece upon which fields, buttons, and other controls are displayed. It is the entire screen that the user is looking at on his/her device

A standard R/3 function used to leave the current task or application area. If data may be lost, the SAP System prompts you to save your work.

Program interface at which additional methods can be inserted without modifying the original object. Java component comparable to Business Add-Ins, User Exits, Customer Function Calls. Exemplary exits in SAP Collaborative Room Document Status and Document Management: Prepare exit Precondition exit Processed exit Version numbering exit

A step that facilitates premature termination of the action.

A way to purchase Emarsys SMS. It is paid for using pre-paid credit that is purchased through the Emarsys Success Manager in the local currency, which is then converted into one of the following: USD, EUR, KHD.

The dashboard metrics which take input values from Commissions UI. The display names in the dashboard do not store any keywords in Commissions UI instead considers the value specific to Commission UI. For example: When Administrator selects metric type as Measures, he can choose the following values with respect to metric type Measures: Measurement rule name, Measurement Value, etc.

An amount granted for use as part of an allowance.

A quantitative measure that defines the student learning time required for a module.

An amount awarded by an employer to an employee as a benefit. Credit can be used by employees to cover plan costs. Depending on company policy, excess credit or a portion of it can be paid to employees in their paycheck.

An arrangement for the deferred payment of goods and services.

The unknown underlying cause of an incident or incidents. The business transaction used to log such a cause.

A pricing procedure defines how values posted in the SAP system are calculated. A pricing procedure can consist of the following types of rows: Base rows, which contain the amount or quantity to which overhead is applied Calculation rows, which contain a percentage rate to be applied to the base lines Totals rows, which contain a sum of base amounts and calculated amounts Pricing procedures are used in Profit Center Accounting to calculate transfer prices.

A rule type for pricing. The pricing procedure defines the conditions permitted for a document and the sequence in which the system takes these conditions into account during pricing. A standard pricing procedure is defined in the standard SAP system. It contains conditions most commonly used. These include material prices, discounts, and surcharges, such as freight, or tax.

A rule type for pricing. Pricing procedure determines the gross value the customer has to pay for certain goods or services they want to receive on a certain day at a certain place. All steps for price calculation in sales and service documents are defined within the pricing procedure.

A change in the basic version of a product that occurs when details are omitted or added, and which can be related to the form, composition and properties.

A deriviation of a content version. Variants are semantically the same as the content version, but the content is in a different language or a different technical format.

Template for designing a report. You can define as many variants as you like for each report. There are several design elements available.

A non-content-related version type. As well as different content versions, a document can also exist in different languages or formats, these documents are known as variants.

A set of predefined input field values that the system offers when you want to execute a BCV object (query view, or dashboard) in the BCV cockpit.

A set of filter settings and input parameters for a KPI or a report. Variants are global in nature and can be created without reference to a particular KPI or report.

An instance of a presentation that contains drilled-down data for specific variables. &Example& Instances can be created for different countries, regions, periods, etc.

Summary of all settings for performing a business-based and consistent profitability analysis. The following settings are made in the variant: Selection of required characteristics Selection of required basic key figures Definition of calculated key figures (such as those for contribution margins)

Materials that differ only in certain characteristics such as color or size. Variants of a material are grouped together as a generic material, for which a material master record is created. A separate master record is also created for each variant.

One of several instances of a text block or a template that allows for use in different business scenarios as well as localization, translation, and so on.

Combination of settings for a module of the program for automatic commitment creation. These module-specific variants are assigned to a run variant which controls the commitment run in the program for automatic commitment creation.

One configuration of a product created by selecting items from a maximum variant base.

A term used in a specific context that shares the same definition as all other terms in the entry. The product version options, release, country and component at term level, specify the context in which the term is used.

A point in an SAP program where a customer's own program can be called. In contrast to customer exits, user exits allow developers to access and modify program components and data objects in the standard SAP System. On upgrade, each user exit must be checked to ensure that it conforms to the standard system. There are the following types of user exit: User exits that use INCLUDEs - These are customer enhancements that are called directly in the program. User exits that use tables - These are used and managed using Customizing.

A technology that allows you to enhance EH&S functions according to customer requirements without making modifications. User exits are managed in Customizing. A user exit comprises a user exit category, which specifies the place where a user exit is called, and a user exit name with a reference function module assigned to it. Customers can either use the reference function module unchanged or use it as a template for defining their own logic. With a user exit, the system can call a number of active function modules simultaneously. This feature is used, for example, to extend searches for EH&S objects (user exits of the category <*_QUERY>). User exits in SAP EH&S are different from the user exits defined under the application component Customer Enhancements (BC-DWB-CEX).